TWI831575B - Blockchain platform system - Google Patents

Abstract

A blockchain platform system includes a center factory node, a retailer node, a bank node and at least three order-consensus nodes. The center factory node is communicatively connected with a center factory system. The retailer node is communicatively connected with a retailer system. The bank node is communicatively connected with a bank financing system. The center factory node, the retailer node, the bank node and these order-consensus nodes are configured to mutually maintain an alliance blockchain based on a smart contract.

Description

Blockchain platform system

This disclosure relates to a blockchain platform system, and in particular to a blockchain platform system that provides supply chain financial services.

Taiwan has a large number of small and medium-sized enterprises, accounting for approximately 97.6% of the total number of enterprises. Generally speaking, in a product supply chain, the central factory that mainly produces products will cooperate with upstream suppliers and downstream distributors. Taking car factories as an example, the central factory that produces vehicles usually cooperates with many upstream suppliers of vehicle parts and components and many downstream dealers responsible for selling vehicles. These upstream and downstream manufacturers are often smaller SMEs than central factories.

In order to speed up the flow of funds and increase the efficiency of production/sales, central factories and upstream and downstream manufacturers usually apply for various financing loans from banks to quickly recover funds, make follow-up investments or continue production plans. In order to carry out risk control, banks need to evaluate the content and objects of financing loans. Take the financing of accounts receivable (AR) as an example. From the time the central factory ships the goods to the dealer, until the dealer successfully sells the central factory's products, receivables will be generated for the central factory. accounts. Based on accounts receivable as the target, the central factory can propose financing service needs for accounts receivable to the bank. After the bank lends, it obtains the creditor's rights to the dealer, so the dealer's creditworthiness assessment is a key risk control point.

Since dealers are usually small and medium-sized enterprises, banks have difficulty or lack of willingness to carry out effective credit checks on dealers. This is because there are many possible dealers in the supply chain and their sizes are different, so it may be difficult to propose a business plan. Sales figures verified by accountants may lack professionals, and it is generally difficult to make credit data credible. If the bank refuses to acquire the dealer's claims due to risks, it may also refuse to provide financing services for the central factory's accounts receivable. This will require the central factory to wait until the sale is completed and the funds are recovered after each shipment, which will significantly reduce the central factory's cost. plant operating efficiency.

Supply Chain Finance (SCF) refers to banks providing financial services such as financing and lending between central factories, upstream suppliers and downstream distributors regarding accounts receivable and payables. According to the research report, there are high amounts of bankable and highly secure accounts payable in the global market. If banks can finance them and charge handling fees, supply chain finance can be a huge potential source of income for banks. In addition, banks have Financing the upstream and downstream supply chains will also help small and medium-sized manufacturers quickly recover funds for subsequent product production and sales, and improve the overall market efficiency.

In addition, as infectious diseases cause changes in the global manufacturing industry, manufacturing orders will tend to be short-term and urgent orders, and the most affected will be small and medium-sized enterprises in the supply chain. The operating environment will become increasingly difficult, and corporate funds and operations will Turnover will be more urgent and tight.

One aspect of this disclosure discloses a blockchain platform system, including a central factory node, a dealer node, a bank node, and at least three sorting consensus nodes. The central plant node communicates with the central plant system. The dealer node communicates with the dealer system. The bank node communicates with the bank financing system. Central factory nodes, dealer nodes, bank nodes and these sorting consensus nodes are used to jointly maintain the alliance blockchain according to smart contracts.

When the central factory system and the dealer system exchange shipping order information and invoice information, the central factory node and the dealer node jointly maintain the accounts receivable account book of the alliance blockchain based on the shipping order information and invoice information.

When the central plant system transmits an accounts receivable financing request to the bank financing system, the central plant node shares the accounts receivable ledger with the bank node, and the bank financing system is used to approve accounts receivable financing based on the accounts receivable ledger. The request generates financing approval confirmation and transfer operation. The central factory node and the bank node jointly maintain the financing transfer ledger of the alliance blockchain based on the financing approval confirmation and transfer operation.

It should be noted that the above description and subsequent detailed description are used to illustrate this case by way of embodiments and are used to assist in the explanation and understanding of the invention claimed in this case.

The following disclosure provides many different embodiments or examples for implementing various features of the present disclosure. Particular illustrations of components and arrangements are used in the following discussion to simplify the present disclosure. Any examples discussed are for illustrative purposes only and do not in any way limit the scope and significance of this disclosure or its examples. Where appropriate, the same reference numbers are used in the drawings and corresponding text to represent the same or similar elements.

Please refer to FIG. 1 , which illustrates a functional block diagram of a supply chain finance platform 100 according to some embodiments of the present disclosure. As shown in Figure 1, the supply chain finance platform 100 is used to establish a channel for sharing transaction information and providing financial services between central factories, dealers and banks.

As shown in Figure 1, the supply chain finance platform 100 includes a blockchain platform system 110, a central factory system 120, a dealer system 130 and a bank financing system 140. The blockchain platform system 110 is used to collect, save and summarize transaction information between the central factory system 120, the dealer system 130 and the bank financing system 140, thereby making the debt and credit data transparent, credible or automated, and reducing the bank's The difficulty of the credit verification process accelerates the process of banks providing supply chain financing services. The blockchain platform system 110 includes at least a central factory node N1, a dealer node N2, a bank node N3 and three sorting consensus nodes NC.

These central factory nodes N1, dealer nodes N2, bank nodes N3 and a plurality of sorting consensus nodes NC communicate with each other to form the alliance blockchain ALBC. The above-mentioned nodes are connected through a point-to-point method and are used to process blockchain transactions. In some embodiments, the central factory node N1, the dealer node N2, the bank node N3 and the plurality of sorting consensus nodes NC can be servers, computer hosts, laptops, tablets, smart phones, industrial computers, and the Internet of Things. device or other connected device with information processing capabilities.

In some embodiments, the ordering consensus node NC includes at least three ordering consensus nodes including the ordering consensus node NC1, the ordering consensus node NC2, and the ordering consensus node NC3. In other embodiments, these ordering consensus nodes NC are not limited to three. The blockchain platform system 110 may include more than three ordering consensus nodes NC, depending on the actual scale of the alliance blockchain ALBC.

In the embodiment of Figure 1, the central factory node N1 is communicatively connected to the central factory system 120. For example, the central factory system 120 can be a supply chain management (SCM) system or inventory management system set up at the central factory. system, order management system or other similar system within the central plant. The central factory user U1 (such as the central factory's purchasing personnel or other employees) can log in and operate the central factory system 120 to manage the central factory's orders, invoices, purchases, shipments, etc.

The dealer node N2 is communicatively connected to the dealer system 130. For example, the dealer system 130 may be an inventory management system, a sales management system, or other similar systems within the dealer set up at the dealer. The dealer user U2 (for example, the dealer's business personnel) can log in and operate the dealer system 130 . For smaller dealers, an independent dealer system 130 may not be set up, so that the dealer node N2 is directly connected to the mobile phone or personal computer held by the dealer's business personnel.

The blockchain platform system 110 shown in Figure 1 includes a single dealer node N2 to correspond to a single dealer, but this disclosure document is not limited to this. In other embodiments, if the central factory cooperates with multiple dealers at the same time, multiple dealer nodes N2 (not shown in the figure) can be set up in the blockchain platform system 110, respectively corresponding to multiple dealers. Business, in this embodiment, the central factory node N1 can establish different channels with different dealer nodes N2. The account information of the central factory node N1 and a certain dealer node N2 is only shared in the same channel and will not be shared. Will be read by nodes in other channels (such as other dealers).

The bank node N3 is communicatively connected to the bank financing system 140. For example, the bank financing system 140 may be a financing credit management system or other similar systems set up by the bank. Bank-side user U3 (for example, bank-side credit granting personnel) can log in and operate the bank financing system 140 .

The blockchain platform system 110 shown in Figure 1 includes a single bank node N3 to correspond to a single bank, but this disclosure document is not limited to this. In other embodiments, if the central factory cooperates with multiple banks at the same time, multiple bank nodes N3 (not shown in the figure) can be set up in the blockchain platform system 110, respectively corresponding to multiple banks. This implementation For example, the central factory node N1 or dealer node N2 can establish different channels with different bank nodes N3 respectively. The account information of the central factory node N1 or dealer node N2 and a certain bank node N3 is only shared in the same channel. , will not be read by nodes in other channels (such as other banks), thereby ensuring that the account information of the central factory or dealer will not be read at will by any bank.

In addition, the blockchain platform system 110 illustrated in Figure 1 exemplifies a single alliance blockchain ALBC established for a single central factory. Practical applications are not limited to this. The blockchain platform system 110 serves multiple users at the same time. When there are different central factories, the different central factories will each establish multiple independent alliance blockchain ALBC. In the embodiment of Figure 1, only one alliance blockchain ALBC is shown for simplicity of explanation.

In the following paragraphs, embodiments will be used to describe the detailed process of applying the blockchain platform system 110 to accounts receivable financing. Please also refer to Figure 2 , which illustrates a flow chart of the supply chain finance platform 100 and the blockchain platform system 110 in Figure 1 for controlling accounts receivable (AR) 200 .

As shown in Figures 1 and 2, the supply chain finance platform 100 first proceeds to step S210. When the central factory system 120 and the dealer system 130 exchange shipping order information and invoice information, the central factory node N1 and the dealer Node N2 jointly maintains the accounts receivable account AC1 of the alliance blockchain ALBC based on the shipping order information and invoice information. The accounts receivable ledger AC1 is used to register all shipping order information and invoice information that occur between the central factory and the dealer in the order of transaction time, and the information registered in the accounts receivable ledger AC1 is processed through blocks. The verification of the central factory node N1, dealer node N2 and sorting consensus node NC in the same channel of the chain platform system 110 is difficult to delete in the future.

Please also refer to FIG. 3 , which illustrates a flowchart of further detailed steps of step S210 in the control method 200 according to some embodiments of this disclosure document. In the embodiment shown in Figure 3, step S210 includes detailed steps S211 to S216. As shown in Figure 3, first, when the dealer user U2 intends to purchase goods from the central factory for subsequent sales, the dealer user U2 can send an order to the central factory system 120 through the dealer system 130, or in another embodiment , the dealer user U2 can also directly log in to the central factory system 120 through the account and password to place an order on it.

In step S211, the central factory system 120 receives the order from the dealer user U2. Then, after receiving the order, the central factory system 120 can start purchasing raw materials, producing products, warehousing products, and transporting them to the dealer. The above-mentioned relevant information on raw material procurement, product production, product warehousing, logistics transportation and delivery will be automatically posted or manually posted in the central factory system 120 by relevant personnel (such as central factory user U1).

In step S212, the central factory system 120 generates corresponding shipping order information and invoice information according to each completion stage of the above order, and provides it to the dealer system 130 to notify the dealer user U2.

When the dealer user U2 receives the notification, he can log in to the central factory system 120 to confirm whether the invoice information issued by the central factory is correct. If the invoice information is confirmed to be correct, in step S213, the central factory node N1 connected to the central factory system 120 can trigger the smart contract of the alliance blockchain ALBC to provide the shipping order information and invoice information to the dealer node. N2, and requires the endorsement of dealer node N2.

Please also refer to Figure 4, which illustrates a further flow chart of transmitting transaction messages between nodes in the alliance blockchain ALBC, obtaining endorsements, and writing into the accounts receivable ledger. In one embodiment, the smart contract includes blockchain code (chaincode). These blockchain codes can be software programs in the Fabric blockchain architecture to execute the smart contract according to the planned software logic. The blockchain program code mainly handles the business logic of smart contracts. All information to be recorded in the supply chain process must go through data verification, node endorsement and other processes before it can be written into the alliance blockchain ALBC.

As shown in Figure 4, in step S213a, the central factory system 120 sends transaction messages (such as shipping order information and invoice information) to the central factory node N1. In step S213b, the smart contract on the central factory node N1 is triggered. In step S213c, the transaction message (such as shipping order information and invoice information) is sent to at least one endorsement node related to the transaction message through the central factory node N1. In the example shown in Figure 4, the endorsement node includes the dealer node N2. This is because the transaction information is the shipping order information and invoice information between the central factory node N1 and the dealer node N2, so the endorsement node at least includes the dealer node N2. If the transaction message involves other transaction content, such as an application for bank financing, the endorsement node will include bank node N3.

In another embodiment, different transaction message contents may have different settings for the endorsement nodes involved. Depending on the content of the transaction message, the endorsement node includes at least one of the central factory node N1, the dealer node N2, and the bank node N3. See Table 1 below: Transaction messages Central plant node N1 Dealer node N2 Bank node N3 Dealer purchase order necessary necessary Non-essential Central factory responds to orders necessary necessary Non-essential Central factory responds to changes in order delivery date necessary necessary Non-essential The dealer responded agreeing to the change in delivery date. necessary necessary Non-essential Central factory shipping notice necessary necessary Non-essential The dealer replies with receipt and acceptance confirmation necessary necessary Non-essential The central factory provides invoices for payment requests necessary necessary Non-essential Dealer confirms account opening necessary necessary Non-essential Central factory participates in financing Non-essential necessary necessary Bank Financing Payment Notice necessary necessary necessary Dealer Financing Payment Notice necessary necessary necessary Bank Financing Repayment Cancellation Notice necessary necessary necessary Table 1

Table 1 is used to list an illustrative description of the allocation of necessary endorsement nodes and non-essential endorsement nodes in different transaction messages.

As shown in Figure 3, in step S214, the dealer node N2 checks whether the shipping order information and invoice information records are correct according to the records on the dealer system 130. If the verification is correct, the dealer node N2 endorses the shipping order. The information and invoice information are recorded correctly, and the endorsed result is sent back to the central factory node N1. As further shown in Figure 4, in step S214a, the endorsing node (in this example, the dealer node N2) calls the blockchain program code to perform transaction verification and generate at least one transaction verification result. In step S214b, the dealer node N2 transmits the transaction verification result back to the central factory node N1. In step S214c, the central factory node N1 can further transmit the transaction verification result back to the central factory system 120. Thereby, the central factory system 120 collects at least one transaction verification result through the central factory node N1, and determines whether the at least one transaction verification result passes the endorsement policy.

In some embodiments, the shipping order information and invoice information are generated and issued by the central factory node N1, and the central factory node N1 can automatically be recognized as endorsing the shipping order information and invoice information. In other embodiments, the central factory node N1 can also call the blockchain program code to read the records on the central factory system 120 to perform transaction verification. If it is confirmed to be correct, the transaction verification result will also be generated for endorsement.

In one embodiment, if a certain transaction message needs to be endorsed by the central factory node N1 and the dealer node N2, it is enough to collect the two nodes and verify that it is correct. In another embodiment, if a certain transaction message needs to be endorsed by the central factory node N1, dealer node N2 and bank node N3, if only two nodes are collected and verified correctly, it is judged that the endorsement policy has not been passed.

As shown in Figure 3, in step S215, the central factory node N1 transmits the endorsed shipping order information and invoice information record to the sorting consensus node NC. As further shown in Figure 4, in step S215a, the central factory system 120 transmits the endorsed shipping order information and invoice information record to the central factory node N1. In step S215b, the central factory node N1 transmits the endorsed shipping order information and invoice information record. The manifest information and invoice information records are sent to the sorting consensus node NC.

As shown in Figure 3, in step S216, the sorting consensus node NC performs consensus verification on the endorsed shipper information and invoice information records, and writes the results of the consensus verification (such as shipper information and invoice information) into Enter the accounts receivable ledger AC1 of the alliance blockchain ALBC. As further shown in Figure 4, in step S216a, the ordering consensus node NC calls the blockchain program code of the smart contract for consensus verification by the three ordering consensus nodes NC1, NC2 and NC3. In step S216b, the three sorting consensus nodes NC1, NC2 and NC3 return the shipping order information and invoice information records that have passed the consensus verification to the central factory node N1 and the dealer node N2, and write them into the alliance blockchain ALBC. The accounts receivable ledger AC1. As shown in Figure 4, the sorting consensus node NC pushes the transaction message to the central factory node N1, dealer node N2 or bank node N3 in the same channel. In this example, since the transaction message only involves the central factory node N1 and the dealer node N2, the sorting consensus node NC pushes the transaction message to the central factory node N1 and the dealer node N2. The central factory node N1 in the same channel Check again with the dealer node N2, and after confirming the transaction message, write the transaction message into the accounts receivable ledger AC1 in the alliance blockchain ALBC.

In one embodiment, the three sorting consensus nodes NC1, NC2 and NC3 use a majority consensus method to determine the correctness of the accounts receivable ledger AC1 (or the financing transfer ledger AC2). When more than half of the sorting consensus nodes NC1, NC2 and NC3 believe that the current shipping order information and invoice information are correct, the consensus-verified information can be written into the accounts receivable ledger AC1 of the alliance blockchain ALBC.

In one embodiment, the three sorting consensus nodes NC1, NC2 and NC3 are used to jointly maintain the writing order of the required information of the alliance blockchain ALBC according to the smart contract. For example, the transaction information that occurred first needs to be written first according to the time of its occurrence, and the transaction information that occurs subsequently needs to be written subsequently according to the time of its occurrence. All transaction information is recorded in the alliance blockchain in sequence according to time. In the accounts receivable ledger AC1 in ALBC, subsequent transaction information can only be added at the end of the accounts receivable ledger AC1, and the previously recorded transaction information cannot be overwritten or deleted. Therefore, the alliance blockchain ALBC The transaction information in the accounts receivable ledger AC1 can have a high degree of credibility and is convenient for bank user U3 to check.

When step S216 is completed, the transaction information between the central factory node N1 and the dealer node N2 is properly written into the accounts receivable ledger AC1. At this point, the central factory has shipped the product to the dealer, and the dealer starts selling. At this time, the central factory should receive the payment for the shipped product (accounts receivable), but dealers are usually not allowed in the supply chain. If you need to pay immediately, you can wait until the dealer starts selling for a period of time (such as 30 days, 45 days, 60 days or other agreed time). After the sales money is recorded in the account, it is not required until the payment period of accounts receivable expires. The dealer pays the central factory. Although such a situation can solve the financial pressure of dealers, for the central factory, production and shipment have been completed, but the funds cannot be recovered immediately, which can cause financial pressure on the central factory and prevent it from continuing to produce other products. At this time, the central factory can choose to apply for financing to the bank based on the accounts receivable that will be obtained in the future.

As shown in Figure 2, step S220 is executed. When the central plant system 120 transmits an accounts receivable financing request to the bank financing system 140, the central plant node N1 can share the accounts receivable ledger AC1 with the bank node N3.

Next, in step S230, the bank financing system 140 is used to approve the accounts receivable financing request according to the accounts receivable ledger AC1, and then generates financing approval confirmation and transfer operations. Please also refer to FIG. 5 , which illustrates a flowchart of further detailed steps of step S230 in the control method 200 according to some embodiments of this disclosure document. In the embodiment shown in FIG. 5 , step S230 includes detailed steps S231 to S234.

In step S231, the bank financing system 140 obtains the accounts receivable ledger AC1 from the bank node N3. In step S232, the bank financing system 140 is used to verify the authenticity of the order based on the shipping order information and invoice information records in the accounts receivable ledger AC1. For example, it can verify whether the dealer has actually placed the order and whether it is genuine. Whether there is a shipping record, whether there is a receipt record, whether a sales invoice is issued, etc., these shipping order information and invoice information will be recorded in the accounts receivable ledger AC1. The bank financing system 140 or its bank user U3 can easily verify whether the order actually exists, which can avoid being defrauded of financing by fictitious orders, and can also reduce the cost of performing financing credit reporting and speed up the process.

In step S233, the bank financing system 140 determines the approved interest and the approved amount for financing approval based on the payment term of the shipper information and the invoice amount of the invoice information in the accounts receivable ledger AC1. For example, the shorter the payment period, the lower the approved interest; the larger the invoice amount, the higher the approved amount, etc. The approved interest and amount in the financing approval determination can be determined by the bank financing system 140 based on the contents recorded in the accounts receivable book AC1 and the credit investigation results of the central factory and the dealer by the bank financing system 140 .

In step S234, the bank financing system 140 allocates the approved amount to the central plant account corresponding to the central plant node N1 to perform the transfer operation. In this embodiment, the bank financing system 140 may also transmit the approved interest and the approved amount to the central factory system 120 to notify the central factory user U1.

Then, when the bank financing system 140 issues financing, the accounts receivable held by the central factory (relative to the dealer) and its claims will be transferred to the bank. The bank will have the right to collect payment from the dealer. Therefore, each node in the blockchain platform system 110 needs to record its transaction information in detail to avoid subsequent disputes. As shown in Figure 2, step S240 is executed. The central factory node N1 and the bank node N3 jointly maintain the financing transfer account AC2 of the alliance blockchain ALBC based on the financing approval determination and transfer operation.

Please also refer to FIG. 6 , which illustrates a flowchart of further detailed steps of step S240 in the control method 200 according to some embodiments of this disclosure document. In the embodiment shown in FIG. 6 , step S240 includes detailed steps S241 to S245.

As shown in Figure 6, when the bank financing system 140 determines the financing approval and executes the transfer operation, step S241 is executed. The bank node N3 triggers the smart contract to provide the financing approval confirmation and transfer operation to the central factory node N1, and The central factory node N1 is required to endorse. Among them, for the detailed method of requiring the node to endorse the transaction information in step S241, you can refer to step S213 in Figure 3 and the embodiment in Figure 4. The two are similar, but the difference is that in step S241 It is initiated by the bank node N3 and requires endorsement by the central factory node N1. In step S213, it is initiated by the central factory node N1 and requires endorsement by the dealer node N2. Other technical contents are similar and will not be described again here.

At this time, the central factory system 120 (or the central factory user U1) can execute step S242 to check whether there is money credited to the central factory account, and check whether it matches the approved amount of the transfer operation.

When it is verified that the amount is entered into the account and is consistent with the approved amount, step S243 is executed, and the central factory node N1 is used to endorse the financing approval confirmation and transfer operation. Next, in step S244, the central factory node N1 transmits the endorsed financing approval determination and transfer operation to the sorting consensus nodes NC1, NC2 and NC3. In step S245, the sorting consensus nodes NC1, NC2, and NC3 are used to perform consensus verification of the financing approval determination and the transfer operation, and then the financing approval determination and transfer operation after consensus verification can be written into the alliance blockchain ALBC Financing transfer ledger AC2.

When step S245 is completed, the transaction information (financing approval confirmation and transfer operation) between the central factory node N1 and the bank node N3 is properly written into the financing transfer account AC2. At this time, the central factory has recovered the shipment payment and transferred the claims on the accounts receivable to the bank. Through the records in the financing transfer ledger AC2, the ownership of the creditor's rights can be clearly confirmed, and it can also be clearly determined which order it corresponds to. When the dealer needs to pay the sales amount when it is due in the future, the financing transfer ledger can be used AC2 record for repayment.

As shown in Figure 2, in step S250, the central factory node N1 shares the financing transfer account AC2 with the dealer node N2. After sales are made and invoices are issued in the dealer system 130, and when the sales amount is due for payment, the dealer system 130 remits the sales amount to the bank account corresponding to the bank node N3 according to the financing transfer account AC2. Through this, the dealer system 130 or the dealer user U2 can remit the sales amount to the bank account corresponding to the bank node N3, thereby repaying the claims on the previous accounts receivable. After the bank financing system 140 confirms that the money has been credited, the record of the creditor's rights can be canceled.

Please also refer to FIG. 7 , which illustrates a functional block diagram of a supply chain finance platform 700 according to some embodiments of the present disclosure. The supply chain finance platform 700 includes a blockchain platform system 710, a central factory system 720, a dealer system 730 and a bank financing system 740. The blockchain platform system 710 is used to collect, save and summarize transaction information between the central factory system 720, the dealer system 730 and the bank financing system 740, thereby making the debt and credit data transparent, credible or automated, and reducing the bank's The difficulty of the credit verification process accelerates the process of banks providing supply chain financing services. The blockchain platform system 710 includes at least a central factory node N1, a dealer node N2, a bank node N3, and three sorting consensus nodes NC, which are communicated with each other to form an alliance blockchain ALBC. In the embodiment of FIG. 7 , each of the central factory node N1 , the dealer node N2 , and the bank node N3 does not only include a single node.

As shown in Figure 7, the central factory node N1 includes the central factory main transaction node N1m and the central factory backup transaction node N1b. When the central factory main transaction node N1m is operating normally, its function is similar to the central factory node N1 in the previous embodiment of FIG. 1 . When the central factory's main transaction node N1m is abnormal, the central factory's backup transaction node N1b is activated to replace the central factory's main transaction node N1m.

As shown in Figure 7, the dealer node N2 includes the dealer's main transaction node N2m and the dealer's backup transaction node N2b. When the dealer main transaction node N2m is operating normally, its function is similar to the dealer node N2 in the previous embodiment of FIG. 1 . When the dealer's main transaction node N2m is abnormal, the dealer's backup transaction node N2b is activated to replace the dealer's main transaction node N2m.

As shown in Figure 7, bank node N3 includes the bank's main transaction node N3m and the bank's backup transaction node N3b. When the bank's main transaction node N3m is operating normally, its function is similar to the bank node N3 in the previous embodiment of Figure 1. When the bank's main transaction node N3m is abnormal, the bank's backup transaction node N3b is activated to replace the bank's main transaction node N3m.

Through the above embodiment, the business process of accounts receivable (AR) financing in the supply chain starts with the dealer initiating an order, placing an order with the central factory, the central factory shipping the goods, the dealer receiving and inspecting the materials, and notifying the central factory to issue an invoice. When requesting payment, the dealer confirms the invoice and transfers it to the ledger in the blockchain to the bank, which then provides the central factory with financing, obtains bank funds and pays interest. When the payment is due, the dealer pays it to the bank designated by the central factory. account. In the operation of the above-mentioned alliance chain, dealers assist the central factory in handling financing, accelerating financing and creating a win-win situation. For example, the central factory can obtain financing smoothly and quickly, and the central factory can also allow longer payment terms when shipping to dealers, easing the financial pressure on dealers.

Although specific embodiments of the present disclosure have been disclosed with regard to the above-described embodiments, these embodiments are not intended to limit the present disclosure. Various substitutions and modifications can be made in the present disclosure by those of ordinary skill in the relevant art without departing from the principles and spirit of the present disclosure. Therefore, the scope of protection of the present disclosure is determined by the appended patent claims.

100, 700: Supply chain finance platform 110, 710: Blockchain platform system 120, 720: Central factory system 130, 730: Dealer system 140, 740: Bank financing system N1: Central plant node N1m: Main trading node of the central factory N1b: Central factory backup transaction node N2: dealer node N2m: dealer’s main trading node N2b: dealer backup transaction node N3: bank node N3m: Bank’s main transaction node N3b: Bank backup transaction node NC, NC1, NC2, NC3: sorting consensus nodes ALBC: Alliance Blockchain AC1: Accounts receivable ledger AC2: Financing mobile ledger U1: Central factory user U2: dealer user U3: Bank user 200:Control method S210, S220, S230, S240, S250: steps S211, S212, S213, S214, S215, S216: steps S213a, S213b, S213c: steps S214a, S214b, S214c: steps S215a, S215b: steps S216a, S216b: steps S231, S232, S233, S234: steps S241, S242, S243, S244, S245: steps

In order to make the above and other objects, features and embodiments of the present disclosure more obvious and understandable, the accompanying drawings are described as follows: Figure 1 illustrates a functional block diagram of a supply chain finance platform according to some embodiments of the present disclosure; Figure 2 shows a flow chart of the supply chain finance platform and blockchain platform system in Figure 1 for controlling accounts receivable; Figure 3 illustrates a flowchart of further detailed steps in the control method according to some embodiments of this disclosure document; Figure 4 illustrates a further flow chart for transmitting transaction messages between nodes in the alliance blockchain, obtaining endorsements, and writing into the accounts receivable ledger; Figure 5 illustrates a flow chart of further detailed steps of another step in the control method according to some embodiments of the present disclosure; Figure 6 illustrates a flowchart of further detailed steps of another step in the control method according to some embodiments of the present disclosure; and Figure 7 illustrates a functional block diagram of a supply chain finance platform according to some embodiments of the present disclosure.

Domestic storage information (please note in order of storage institution, date and number) without Overseas storage information (please note in order of storage country, institution, date, and number) without

100: Supply chain finance platform

110:Blockchain platform system

120: Central plant system

130: Dealer system

140:Bank financing system

N1: Central plant node

N2: dealer node

N3: bank node

NC, NC1, NC2, NC3: sorting consensus nodes

ALBC: Alliance Blockchain

U1: Central factory user

U2: dealer user

U3: Bank user

AC1: Accounts receivable ledger

AC2: Financing mobile ledger

Claims (10)

A blockchain platform system that includes: A central factory node communicates with a central factory system; a dealer node communicating with a dealer system; and A bank node communicates with a bank financing system; At least three sorting consensus nodes, among which the central factory node, the dealer node, the bank node and the sorting consensus nodes are used to jointly maintain an alliance blockchain according to a smart contract, wherein: When the central factory system and the dealer system exchange shipping order information and invoice information, the central factory node and the dealer node jointly maintain the alliance blockchain based on the shipping order information and the invoice information. An accounts receivable ledger, When the central plant system transmits an accounts receivable financing request to the bank financing system, the central plant node shares the accounts receivable ledger with the bank node, and the bank financing system uses the accounts receivable to The ledger approval of the accounts receivable financing request generates a financing approval confirmation and a transfer operation. The central factory node and the bank node jointly maintain a financing transfer on the alliance blockchain based on the financing approval confirmation and the transfer operation. Ledger. The blockchain platform system as described in request item 1, wherein the central factory node and the dealer node jointly maintain the accounts receivable account book of the alliance blockchain through: When the central factory system receives an order, the central factory system generates the corresponding shipping order information and the invoice information based on the order and provides it to the dealer system. When the invoice information on the central factory system is logged in and confirmed , the central factory node triggers the smart contract to provide the shipping order information and the invoice information to the dealer node, and requires the dealer node to endorse, and The dealer node checks and endorses the shipping order information and the invoice information record based on the records on the dealer system, and sends them back to the central factory node. The central factory node transmits the endorsed shipping order information and invoice information records to the ordering consensus nodes, and after verification, the ordering consensus nodes write the shipping order information and the invoice information into the alliance blockchain The accounts receivable ledger. The blockchain platform system as described in claim 2, wherein the bank financing system generates the financing approval confirmation and the transfer operation through: The bank financing system obtains the accounts receivable ledger from the bank node, The bank financing system is used to verify the authenticity of the order based on the shipper information and the invoice information record in the accounts receivable ledger, The bank financing system determines the approved interest and approved amount for the financing approval based on the payment term of the shipment information and the invoice amount of the invoice information, and The bank financing system will allocate the approved amount to the central plant account corresponding to the central plant node to perform the transfer operation. As for the blockchain platform system described in request item 3, the central factory node and the bank node jointly maintain the financing transfer ledger through: When the bank financing system determines the financing approval and executes the transfer operation, the bank node triggers the smart contract to provide the financing approval confirmation and the transfer operation to the central factory node, and requires the central factory node to endorse, When the central factory system checks the approved amount from the central factory account, the central factory node endorses the financing approval determination and the transfer operation, and the central factory node endorses the financing approval confirmation and the transfer operation. It is sent to the sorting consensus nodes, and after verification, the sorting consensus nodes confirm the financing approval and write the financing transfer operation into the financing transfer ledger of the alliance blockchain. The blockchain platform system as described in request item 4, wherein the central factory node shares the financing transfer account book with the dealer node, and after the dealer system sells and issues invoices, when a sales payment arrives When making an installment payment, the dealer system will remit the sales amount to a bank account corresponding to the bank node based on the financing account book. The blockchain platform system as described in claim 1, wherein the ordering consensus nodes are used to jointly maintain the writing order of the required information of the alliance blockchain according to the smart contract. For the blockchain platform system described in claim 6, the ordering consensus nodes are further used to determine the correctness of the accounts receivable ledger and the financing transfer ledger in a majority consensus manner. The blockchain platform system described in claim 1, wherein the smart contract includes a blockchain program code, and the central factory system sends a transaction message to at least one endorsement node related to the transaction message through the central factory node, The at least one endorsement node calls the blockchain program code to perform transaction verification and generate at least one transaction verification result. The at least one endorsement node includes at least one of the central factory node, the dealer node and the bank node. The central factory The system collects the at least one transaction verification result through the central factory node, and determines whether the at least one transaction verification result passes an endorsement policy. The blockchain platform system as described in request item 8, wherein the central factory system transmits the transaction message passing the endorsement policy and the at least one transaction verification result to the sorting consensus nodes through the central factory node, and the sorting consensus nodes The consensus node performs consensus verification on the transaction message and the at least one transaction verification result. When the consensus verification passes, the ordering consensus nodes push the transaction message to the central factory node, the dealer node or the dealer node in the same channel. The bank node, the central factory node, the dealer node or the bank node in the same channel checks and confirms the transaction message again and then writes the transaction message into the alliance blockchain. The blockchain platform system as described in request item 1, wherein the central factory node includes: A central factory’s main trading node; and A central factory backup transaction node. When the central factory's main transaction node is abnormal, the central factory's backup transaction node is activated to replace the central factory's main transaction node; The dealer node contains: a dealer’s main trading node; and A dealer's backup transaction node. When the dealer's main transaction node is abnormal, the dealer's backup transaction node is activated to replace the dealer's main transaction node; The bank node contains: A bank’s main transaction node; and A bank backup transaction node. When the bank's main transaction node is abnormal, the bank's backup transaction node is activated to replace the bank's main transaction node.

Images