CN114119243A

CN114119243A - Pool financing management method, device, medium and electronic equipment based on block chain

Info

Publication number: CN114119243A
Application number: CN202111294959.7A
Authority: CN
Inventors: 赵文强; 李艳鹏; 陆旭明; 康林强
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2021-11-03
Filing date: 2021-11-03
Publication date: 2022-03-01

Abstract

The application provides a pool financing management method and device based on a block chain, which are applied to a business system, wherein the business system runs a plug-in pool financing service provided by an asset service platform; the method comprises the following steps: receiving a service calling request aiming at the pool financing service and initiated by the financing applicant; in response to the service invocation request, verifying whether the data format of the receivable data submitted by the financing applicant is matched with the standard data format based on the verification rule; and if the intelligent contracts are matched, the intelligent contracts which are deployed on the blockchain and correspond to the pool financing service are further called, and the pool financing service is provided for the financing applicant. By the technical scheme, the business system can be quickly accessed to the pool financing service after receiving the standardized accounts receivable data submitted by the financing application party.

Description

Pool financing management method, device, medium and electronic equipment based on block chain

Technical Field

The present application relates to the field of blockchain technologies, and in particular, to a method, an apparatus, a medium, and an electronic device for pool financing management based on blockchain.

Background

Pool financing means that enterprises do not need to additionally provide mortgage and guarantee, and only daily scattered small-amount accounts receivable are aggregated to form a relatively stable account receivable balance pool and a bank is transferred, so that financing of a certain proportion of money can be obtained.

For example, the enterprise may send one or more accounts receivable accounts approved by the bank to the bank, wherein the accounts receivable accounts are of different duration and amount, and the bank then finances the enterprise with a certain amount.

The receivable accounts refer to the amount that the enterprise should receive from the purchasing unit in the normal operation process due to the business of selling goods, products, providing labor and the like, and include tax due to the purchasing unit or the unit receiving the labor, various transportation and miscellaneous fees paid by the purchasing unit.

The receivable accounts represent the funds occupied by the purchasing units in the sales process of the enterprise, and the financing of the receivable accounts pool can account for various scattered accounts frequently occurring in the enterprise, ensure the fund mobility of the enterprise and help the enterprise to grow.

Disclosure of Invention

In view of the above, the present application provides a pool financing management method and device based on a block chain.

Specifically, the method is realized through the following technical scheme:

in a first aspect, the application provides a pool financing management method based on a block chain, which is applied to a business system, wherein the business system runs a plug-in pool financing service provided by an asset service platform; the pool financing service comprises a financing service provided for a financing applicant based on a receivable pool consisting of a plurality of receivable accounts of the financing applicant; the method comprises the following steps:

receiving a service calling request aiming at the pool financing service and initiated by the financing applicant; wherein the service invocation request includes receivable data submitted by the financing applicant; the business system stores configuration information which is issued by the asset service platform and corresponds to the pool financing service; the configuration information comprises a standard data format set for the accounts receivable data and a check rule for the accounts receivable data;

in response to the service invocation request, verifying whether the data format of the receivable data submitted by the financing applicant is matched with the standard data format based on the verification rule;

and if the intelligent contracts are matched, the intelligent contracts which are deployed on the blockchain and correspond to the pool financing service are further called, and the pool financing service is provided for the financing applicant.

In a second aspect, the present application further provides a block chain-based pool financing management device, which is applied to a business system, where the business system runs a plug-in pool financing service provided by an asset service platform; the pool financing service comprises a financing service provided for a financing applicant based on a receivable pool consisting of a plurality of receivable accounts of the financing applicant; the device includes:

the receiving unit is used for receiving a service calling request aiming at the pool financing service and initiated by the financing application party; wherein the service invocation request includes receivable data submitted by the financing applicant; the business system stores configuration information which is issued by the asset service platform and corresponds to the pool financing service; the configuration information comprises a standard data format set for the accounts receivable data and a check rule for the accounts receivable data;

the checking unit is used for responding to the service calling request and checking whether the data format of the receivable data submitted by the financing applicant is matched with the standard data format or not based on the checking rule;

The technical scheme provided by the embodiment of the application can have the following beneficial effects:

the asset service platform abstracts service logic according to a pool financing service scene, provides a plug-in pool financing service based on the logic, and issues corresponding configuration information to the service system according to the content of the pool financing service, so that the service system can quickly access the pool financing service after receiving standardized account receivable data submitted by a financing applicant. In the process, firstly, the scheme can be widely applied to various pool financing service scenes through the logic abstracted based on the pool financing service scenes; secondly, the access cost of a financing applicant can be reduced by providing a plug-in pool financing service, and the financing applicant only needs to provide standardized accounts receivable data; moreover, by setting configuration information corresponding to the pool financing service, more flexible service can be provided for the financing application party, dynamic configuration is realized for the whole flow of the pool financing service, and finally the financing application party can rapidly access the pool financing service according to preset configuration information after submitting standardized account receivable data.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

FIG. 1 is a schematic diagram illustrating the creation of an intelligent contract according to an exemplary embodiment of the present application;

FIG. 2 is a schematic diagram illustrating an invocation of an intelligent contract in accordance with an illustrative embodiment of the present application;

FIG. 3 is a schematic diagram illustrating the creation of an intelligent contract and invocation of an intelligent contract according to an exemplary embodiment of the present application;

FIG. 4 is a flow chart illustrating a block chain based method for pool financing management in accordance with an exemplary embodiment of the present application;

fig. 5 is a hardware block diagram of an electronic device in which a blockchain-based pool financing management apparatus is located according to an exemplary embodiment of the present application;

fig. 6 is a block diagram illustrating a block chain-based pool financing management apparatus according to an exemplary embodiment of the present application.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not 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.

It should be noted that: in other embodiments, the steps of the respective methods are not necessarily performed in the order shown and described in the present application. In some other embodiments, the method may include more or fewer steps than those described herein. Moreover, individual steps described in this application may be broken down into multiple steps for description in other embodiments; however, in other embodiments, multiple steps described in the present application may be combined into a single step for description.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

Currently, the pool financing products provided by banks can be oriented to various business fields, such as network freight, third-party logistics, shipping, and the like. The method aims at pool financing products in different business fields, does not have standardized flow design, and completes development and debugging work based on a business model.

For example, taking one of the business models as an example, the design logic of a pool financing product mainly comprises the following processes:

a user uploads accounts receivable and a certificate associated with the accounts receivable through an interface provided by a platform;

the platform links the received accounts receivable and the certificate associated with the accounts receivable to store the certificate, completes the verification of the certificate and links the verification result to store the certificate;

a user initiates an accounts receivable pledge through a pool financing product;

the pool financing product acquires accounts receivable, certificates related to the accounts receivable and verification results of the certificates according to accounts receivable needing pledge of a user, and further verifies the acquired data according to business needs;

the pool financing product pushes the data passing the verification to an account receivable pool;

a user initiates a financing application through a pool financing product;

the pool financing product is used for approving the financing application content by pushing the financing application to the bank.

It can be seen from the above flow that the service flow of the whole pool financing product is relatively long, which means that the whole flow needs to be performed once every time a service field is added to the pool financing product, and the steps of development, joint debugging, testing and the like are performed until the pool financing product is finally on-line.

Although there are differences in the business fields, the pool financing products for different business fields are generally the same on the whole technical link, so that each time a business field is added to access the pool financing product, a full-flow scheme is needed, which is not only tedious in flow and low in efficiency, but also consumes various resources additionally, which is not beneficial to reducing the cost.

In view of this, the present application provides a technical solution in which an asset service platform abstracts service logic according to a pool financing service scenario, provides a plug-in pool financing service based on the logic, and issues corresponding configuration information to a service system according to the content of the pool financing service, so that the service system can quickly access the pool financing service after receiving standardized account receivable data submitted by a financing applicant.

When the method is realized, the business system runs the pool financing service which is provided by the asset service platform and is in a plug-in mode; the pool financing service comprises a financing service provided for a financing applicant based on a receivable pool consisting of a plurality of receivable accounts of the financing applicant;

firstly, a service system receives a service calling request aiming at the pool financing service, which is initiated by the financing application party; wherein the service invocation request includes receivable data submitted by the financing applicant; the business system stores configuration information which is issued by the asset service platform and corresponds to the pool financing service; the configuration information comprises a standard data format set for the accounts receivable data and a check rule for the accounts receivable data;

secondly, the business system responds to the service calling request and verifies whether the data format of the receivable data submitted by the financing applicant is matched with the standard data format or not based on the verification rule;

and then, if the intelligent contracts are matched, the intelligent contracts which are deployed on the blockchain and correspond to the pool financing service are further called, and the pool financing service is provided for the financing applicant.

Through the technical scheme, the asset service platform abstracts the service logic according to the pool financing service scene, provides the pool financing service in a plug-in mode based on the logic, and issues the corresponding configuration information to the service system according to the content of the pool financing service, so that the service system can be quickly accessed to the pool financing service after receiving the standardized account receivable data submitted by a financing applicant.

In the process, firstly, the scheme can be widely applied to various pool financing service scenes through the logic abstracted based on the pool financing service scenes; secondly, the access cost of a financing applicant can be reduced by providing a plug-in pool financing service, and the financing applicant only needs to provide standardized accounts receivable data; moreover, by setting configuration information corresponding to the pool financing service, more flexible service can be provided for the financing application party, dynamic configuration is realized for the whole flow of the pool financing service, and finally the financing application party can rapidly access the pool financing service according to preset configuration information after submitting standardized account receivable data. The block chain or block chain according to one or more embodiments of the present application may specifically refer to a P2P network system having a distributed data storage structure, where the account book data in the block chain is distributed in temporally consecutive "blocks", and the latter block may include a data summary of the former block, and according to a specific consensus mechanism (e.g., POW, POS, DPOS, or PBFT), a full backup of data of all or part of nodes is achieved.

Blockchains are generally divided into three types: public chain (Public Blockchain), Private chain (Private Blockchain) and alliance chain (Consortium Blockchain). Furthermore, there may be a combination of the above types, such as private chain + federation chain, federation chain + public chain, and so on. It is contemplated that the embodiments provided herein can be implemented in a suitable type of blockchain.

Based on the basic characteristics of a blockchain, a blockchain is usually composed of several blocks. The time stamps corresponding to the creation time of the block are recorded in the blocks respectively, and all the blocks form a time-ordered data chain according to the time stamps recorded in the blocks strictly.

The data generated outside the chain can be constructed into a standard transaction (transaction) format supported by the blockchain, then the data is issued to the blockchain, the node devices in the blockchain perform consensus on the transaction, and after the consensus is achieved, the node devices serving as accounting nodes in the blockchain package the transaction into blocks, and the persistent evidence is stored in the blockchain.

The consensus algorithm supported in the blockchain may include:

the first kind of consensus algorithm, namely the consensus algorithm that the node device needs to contend for the accounting right of each round of accounting period; consensus algorithms such as Proof of Work (POW), Proof of equity (POS), Proof of commission rights (DPOS), etc.;

the second kind of consensus algorithm, namely the consensus algorithm which elects accounting nodes in advance for each accounting period (without competing for accounting right); for example, a consensus algorithm such as a Practical Byzantine Fault Tolerance (PBFT) is used.

As described above, regardless of which consensus algorithm is used by the blockchain, the accounting node of the current round may package the received transaction to generate a candidate block and send the generated candidate block or the block header of the candidate block to other node devices for consensus verification. If no problem is verified after the other node device receives the candidate block or the block header of the candidate block, the candidate block can be added to the end of the original block chain as the latest block, thereby completing the accounting process of the block chain. The transaction contained in the block may also be performed by other nodes in verifying the new block or block header sent by the accounting node.

In the field of blockchain, an important concept is Account (Account); taking an ether house as an example, the ether house generally divides an account into an external account and a contract account; the external account is an account directly controlled by the user and is also called as a user account; and the contract account is created by the user through an external account, the account containing the contract code (i.e. the smart contract).

Of course, for some blockchain models derived from the ethernet-based architecture (such as ant blockchains), account types supported by the blockchain may be further expanded, and are not particularly limited in this specification.

For accounts in a blockchain, the account status of the account is usually maintained through a structure. When a transaction in a block is executed, the status of the account associated with the transaction in the block chain is also typically changed.

In one example, the structure of an account typically includes fields such as Balance, Nonce, Code, and Storage. Wherein:

a Balance field for maintaining the current account Balance of the account;

a Nonce field for maintaining a number of transactions for the account; the counter is used for guaranteeing that each transaction can be processed only once, and replay attack is effectively avoided;

a Code field for maintaining a contract Code for the account; in practical applications, only the hash value of the contract Code is typically maintained in the Code field; thus, the Code field is also commonly referred to as the Codhash field.

A Storage field for maintaining the Storage contents of the account (default field value is null); for a contract account, a separate storage space is usually allocated to store the storage content of the contract account; this separate storage space is often referred to as the account storage of the contract account.

The storage content of the contract account is usually constructed into a data structure of an MPT (Merkle Patricia Trie) tree and stored in the independent storage space; in which, the Storage content based on the contract account is constructed into an MPT tree, which is also commonly referred to as a Storage tree. Whereas the Storage field typically maintains only the root node of the Storage tree; thus, the Storage field is also commonly referred to as the Storage root field.

Wherein, for the external account, the field values of the Code field and the Storage field shown above are both null values.

In a programmable blockchain, some complex logic can be created and invoked by users in a blockchain network by providing the user with the functionality of a Smart contract (Smart contract). A so-called smart contract is a program that can be executed on a blockchain triggered by a transaction.

In the programmable block chain, each node device can carry a virtual machine with complete graphic flexibility as an execution environment of an intelligent contract, and various complex logics can be realized through the virtual machine.

The intelligent contracts issued and called by the users in the block chain are run on the virtual machine. In fact, the virtual machine directly runs virtual machine code (virtual machine bytecode, hereinafter referred to as "bytecode"), so the intelligent contract deployed on the blockchain may be bytecode.

As shown in fig. 1, after Bob sends an intelligent contract creation transaction containing contract codes to the blockchain network, each node device may execute the transaction in the hosted virtual machine.

In fig. 1, the From field of the transaction is used To record the address of the account initiating the creation of the intelligent contract, the contract code stored in the field value of the Data field of the transaction may be the above byte code, and the field value of the To field of the transaction is a null account. After the nodes reach the agreement through the consensus mechanism, the intelligent contract is successfully created, and the follow-up user can call the intelligent contract.

After the intelligent contract is established, a contract account corresponding to the intelligent contract appears on the block chain, and the block chain has a specific address; for example, "0 x68e12cf284 …" in each node in fig. 1 represents the address of the contract account created; the contract Code (Code) and account store (Storage) will be maintained in the account store for that contract account. The behavior of the intelligent contract is controlled by the contract code, while the account storage of the intelligent contract preserves the state of the contract.

As mentioned above, the Data field containing the transaction that created the intelligent contract may hold the byte code of the intelligent contract. A bytecode consists of a series of bytes, each of which can identify an operation. Based on the multiple considerations of development efficiency, readability and the like, a developer can select a high-level language to write intelligent contract codes instead of directly writing byte codes. For example, the high-level language may employ a language such as Solidity, Serpent, LLL, and the like. For intelligent contract code written in a high-level language, the intelligent contract code can be compiled by a compiler to generate byte codes which can be deployed on a blockchain.

Taking the Solidity language as an example, the contract code written by it is very similar to a Class (Class) in the object-oriented programming language, and various members including state variables, functions, function modifiers, events, etc. can be declared in one contract. A state variable is a value permanently stored in an account Storage (Storage) field of an intelligent contract to save the state of the contract.

As shown in fig. 2, still taking the ethernet lane as an example, after Bob sends an intelligent contract invocation transaction to the ethernet lane network, each node device may execute the transaction in a mounted virtual machine.

In fig. 2, the From field of the transaction is used To record the address of the account initiating the intelligent contract invocation, the To field is used To record the address of the intelligent contract invocation, and the Data field of the transaction is used To record the method and parameters of the intelligent contract invocation. After invoking the smart contract, the account status of the contract account may change. Subsequently, a client may view the account status of the contract account through the accessed block link point (e.g., node 1 in fig. 2).

The intelligent contract can be independently executed at each node in the blockchain network in a specified mode, and all execution records and data are stored on the blockchain, so that after the transaction is executed, transaction certificates which cannot be tampered and lost are stored on the blockchain.

A schematic diagram of creating an intelligent contract and invoking the intelligent contract is shown in fig. 3. An intelligent contract is created in an Ethernet workshop and needs to be subjected to the processes of compiling the intelligent contract, changing the intelligent contract into byte codes, deploying the intelligent contract to a block chain and the like. The intelligent contract is called in the Ethernet workshop, a transaction pointing to the intelligent contract address is initiated, the EVM of each node can respectively execute the transaction, and the intelligent contract code is distributed and operated in the virtual machine of each node in the Ethernet workshop network.

The event mechanism of the intelligent contract is a mode for the interaction between the intelligent contract and the out-of-chain entity.

For intelligent contracts deployed on blockchains, direct interaction with out-of-chain entities is generally not possible; for example, the intelligent contract cannot generally send the call result of the intelligent contract to the call initiator of the intelligent contract point to point after the call is completed.

The call results (including intermediate results and final call results) generated during the call of the intelligent contract are usually recorded in the form of events (events) to the transaction log (transactions logs) of the transaction that called the intelligent contract, and stored in the memory space of the node device. The entity outside the chain which needs to interact with the intelligent contract can acquire the calling result of the intelligent contract by monitoring the transaction log stored in the storage space of the node equipment;

for example, in the case of an Etherhouse, the transaction log will eventually be stored in the MPT receipt tree described above as part of the receipt (receipt) of the transaction pen transaction that invoked the smart contract. And the entity outside the chain interacting with the intelligent contract can monitor the transaction receipts stored in the storage space of the node device on the MPT receipt tree and acquire the events generated by the intelligent contract from the monitored transaction receipts.

In a cross-chain scenario, multiple blockchains may implement cross-chain docking through cross-chain relays.

The cross-link relay can be respectively connected with the block chains through the bridging interfaces, and the cross-link data synchronization among the block chains is completed based on the realized data carrying logic.

The chain-crossing technology used for realizing the chain-crossing relay is not particularly limited in this specification; for example, in practical applications, a plurality of block chains can be connected by a chain-crossing mechanism such as side chain technology, notary technology, and the like.

After a plurality of block chains are connected in a butt joint mode through cross-chain relays, data on other block chains can be read and authenticated between the block chains, and intelligent contracts deployed on other block chains can be called through the cross-chain relays.

The inter-link relay is used only for transferring data between a plurality of block chains, and does not need to store the transferred data persistently or maintain the data state of the transferred data. In practical applications, the inter-link relay may be configured in a device, a node, a platform, or the like other than the plurality of block chains to which the inter-link relay is connected, or may be configured in a node device of the plurality of block chains to which the inter-link relay is connected, and is not particularly limited in this specification.

The intelligent contracts deployed on the blockchain can only access data contents stored on the blockchain generally; in practical applications, for some complex business scenarios implemented based on the intelligent contract technology, the intelligent contract may need to access external data stored on the data entity outside the chain.

In this scenario, the intelligent contract deployed on the blockchain can access data on the data entities outside the chain through the Oracle ora. Data entities outside the chain may include, for example, centralized servers or data centers deployed outside the chain, and so on.

It should be noted that the cross-link relay is used to connect two block chains, and the Oracle are used to connect the Oracle ora.

In practical application, when a predicting machine is deployed for an intelligent contract on a block chain, a predicting machine intelligent contract corresponding to the predicting machine can be deployed on the block chain; the intelligent contract of the prediction machine is used for maintaining external data sent to the intelligent contract on the block chain by the prediction machine; for example, external data sent by the predictive machine to the smart contract on the blockchain may be stored in the account storage space of the predictive machine smart contract.

When a target intelligent contract on the blockchain is called, external data required by the target intelligent contract can be read from the account storage space of the prediction machine intelligent contract to complete the calling process of the intelligent contract.

It should be noted that, when sending external data to the smart contract on the blockchain, the prediction engine may use an active sending method or a passive sending method.

In one implementation, the data entity outside the chain may send external data to be provided to the target intelligent contract to the intelligent contract of the language prediction machine after signing by using the private key of the language prediction machine; for example, the signed external data may be sent to the intelligent contract of the prediction machine in a periodic sending manner;

the intelligent contract of the language predicting machine can maintain a CA (certificate authority) certificate of the language predicting machine, after external data sent by a data entity outside a chain is received, a signature of the external data can be verified by using a public key of the language predicting machine maintained in the CA certificate, and after the signature passes, the external data sent by the data entity outside the chain is stored in an account storage space of the intelligent contract of the language predicting machine.

In another implementation, when a target intelligent contract on a blockchain is called, if external data required by the target intelligent contract is not read from an account storage space of the intelligent contract of the language predictive controller, the intelligent contract of the language predictive controller may interact with the language predictive controller by using an event mechanism of the intelligent contract, and the language predictive controller sends the external data required by the target intelligent contract to the account storage space of the intelligent contract of the language predictive controller.

For example, when a target intelligent contract on a blockchain is called, if external data required by the target intelligent contract is not read from an account storage space of the intelligent contract of the language predictive machine, the intelligent contract of the language predictive machine can generate an external data acquisition event, record the external data acquisition event into a transaction log of the transaction calling the intelligent contract, and store the transaction log into a storage space of a node device; the predicting machine can monitor a transaction log generated by the predicting machine intelligent contract stored in the storage space of the node equipment, respond to the monitored external data acquisition event after monitoring the external data acquisition event in the transaction log, and send the external data required by the target intelligent contract to the predicting machine intelligent contract.

Next, examples of the present application will be described in detail.

Referring to fig. 4, fig. 4 is a flowchart illustrating a block chain-based pool financing management method according to an exemplary embodiment of the present application, and as shown in fig. 4, the method includes the following steps:

step 401: receiving a service calling request aiming at the pool financing service and initiated by the financing applicant; wherein the service invocation request includes receivable data submitted by the financing applicant; the business system stores configuration information which is issued by the asset service platform and corresponds to the pool financing service; the configuration information comprises a standard data format set for the accounts receivable data and a check rule for the accounts receivable data;

step 402: in response to the service invocation request, verifying whether the data format of the receivable data submitted by the financing applicant is matched with the standard data format based on the verification rule;

step 403: and if the intelligent contracts are matched, the intelligent contracts which are deployed on the blockchain and correspond to the pool financing service are further called, and the pool financing service is provided for the financing applicant.

Wherein the business system runs a plug-in pool financing service provided by an asset service platform; the pool financing service includes providing financing services to financing applicants based on a receivables pool comprised of a plurality of receivables of the financing applicants.

It should be noted that the main processes of the pool financing service include an accounts receivable uplink, an accounts receivable pledge, and a financing application, which remain unchanged in the pool financing service provided for different business fields. However, the implementation details may not be the same for different business domains in each link. Therefore, the construction of pool financing products in the business field can be quickly realized by providing the plug-in pool financing service for enterprises, so that the pool financing products finally provided for different business fields are the same as a whole, but have differences in details.

In one illustrated embodiment, the business system runs a pool financing service plug-in provided by an asset service platform.

Specifically, by running a pool financing service plug-in provided by the asset service platform on the business system, a new business can be quickly accessed to the pool financing service.

For example, by providing a plug-in pool financing service for an enterprise, the enterprise can save the process of developing a business system butted with an asset service platform, save the labor and material cost of the enterprise, simultaneously save the link of joint debugging between the platform and the enterprise, and accelerate the speed of accessing the business to the pool financing service by the enterprise.

Furthermore, the operator of the asset service platform can realize wide and quick adaptation to different services by configuring the pool financing service plug-in, modifying the plug-in and adjusting the parameters of the plug-in.

In one illustrated embodiment, the pool financing service opens a configuration interface to the asset service platform; receiving a calling request aiming at the configuration interface sent by the asset service platform; wherein the invocation request includes configuration information generated by an operator for the pool financing service on the asset service platform; and responding to the calling request, and storing the configuration information in the service system.

Specifically, in order to configure the pool financing service, the business system may open a configuration interface to the asset service platform, so that the asset service platform may send a call request to the configuration interface opened by the business system, and store, in response to the call request, configuration information generated for the pool financing service by an operator on the asset service platform, which is carried in the call request.

When the business system stores the configuration information, the corresponding relation between the pool financing service and the configuration information can be recorded.

For example, the service system may store a plurality of configuration information, and different configuration information respectively corresponds to pool financing services for different service fields.

In addition, the operator of the asset service platform can also generate corresponding configuration information aiming at different links of the pool financing service. Similarly, the business system may record the corresponding relationship between different links and configuration information of the pool financing service.

For example, the business system may store configuration information corresponding to the receivable account uplink, the receivable account pledge, and the financing application, and record a corresponding relationship between each link and the configuration information.

In this embodiment, the service system may receive a service invocation request for the pool financing service initiated by the financing applicant.

The service invocation request may include, among other things, receivable data submitted by the financing applicant.

It should be noted that different links of the pool financing service correspond to different receivable data respectively.

Specifically, the business system may store configuration information corresponding to the pool financing service issued by the asset service platform; the configuration information may include a standard data format set for the accounts receivable data, and a validation rule for the accounts receivable data.

For example, an enterprise may send accounts receivable data to a business system, and the business system may determine configuration information corresponding to a pool financing service provided for the enterprise.

In addition, the financing applicant may initiate a service call request for the pool financing service to the service system through the client, or may initiate a service call request for the pool financing service through an interface provided by the service system, which is not limited in the present application.

In this embodiment, the business system may check, based on the check rule, whether a data format of the receivable data submitted by the financing applicant matches the standard data format in response to the service invocation request.

Specifically, the business system may determine, according to the receivable data submitted by the financing applicant, configuration information corresponding to the pool financing service provided for the financing applicant, so as to determine, based on a check rule for the receivable data in the configuration information, whether the receivable data submitted by the financing applicant matches a standard data format set for the receivable data in the configuration information.

Continuing with the example, to build a standardized pool financing service, the enterprise's receivables data should be submitted based on a standard data format. Therefore, after the business system determines the configuration information corresponding to the pool financing service, whether the receivable data submitted by the enterprise is in the standard data format or not can be judged according to the check rule aiming at the receivable data in the configuration information.

In the process, the standard format is set for the accounts receivable data, and the accounts receivable data are verified according to the preset rules, so that the standardization and standardization management of the data submitted by the financing applicant can be realized, the follow-up further processing according to the accounts receivable data is facilitated, and the condition that the follow-up process cannot be carried out due to the fact that the data format standards are not uniform is avoided.

In one example, the standard data format set for the accounts receivable data may be a core element of accounts receivable in the pool financing service, and includes at least: bill amount, bill acquirer, bill creator time, and bill status. That is, the pool financing service can be accessed as long as the above six elements are included.

Further, when checking the receivable data, judging whether the receivable data submitted by the financing applicant contains the six elements, if so, matching the data format of the receivable data with the standard data format.

In this embodiment, if the block chain is matched with the pool financing service, the intelligent contract corresponding to the pool financing service deployed on the block chain is further invoked to provide the pool financing service to the financing applicant.

The intelligent contract corresponding to the pool financing service is created by an operator according to the configuration information corresponding to the specific pool financing service and is deployed to the block chain.

In the above process, the main process of the pool financing service is summarized into a standardized process by summarizing the process of the pool financing service, and the processes are further abstracted to realize the separation of logic and data. Since the logic is fixed and the data is dynamic and standardized throughout the process, the above-mentioned processes of development, joint debugging, testing, etc. are no longer required when one business system accesses the pool financing service.

For example, one side of the asset management platform can develop the standardized flow described above into a plug-in, when one side of the business system needs to access the pool financing service, the plug-in can be directly installed, and then the operator of the asset management platform configures parameters through a background, so that the pool financing function is realized, and in the whole process, the user side does not need to develop programs.

By now it can be appreciated that a business system may be provided by installing a plug-in provided by the asset service platform, the plug-in including some standardized logic adapted to provide pool financing services for multiple business domains, but the logic also requires specific configuration information to be successfully run, and the configuration information is issued to the business system by the asset service platform. Subsequently, the user calls the plugin pool financing service in the business system to complete the operations of receivable account uplink, receivable account pledge, financing application and the like in the pool financing service.

The standardized logic mainly includes three aspects of receivable account chaining, receivable account pledge and financing application, which are described in detail below to explain how to implement receivable account chaining, receivable account pledge and financing application operations, thereby completing pool financing business.

In one illustrated embodiment, the pool financing service comprises an accounts receivable uplink service.

Further, in one illustrated embodiment, the accounts receivable data includes a plurality of accounts receivable held by the financing applicant, and a voucher associated with the accounts receivable.

For example, a financing applicant may submit multiple bills of lading, as well as tickets associated with each bill.

Specifically, the business system stores receivable account uplink configuration information corresponding to a receivable account uplink service issued by the asset service platform, where the receivable account uplink configuration information includes a standard data format set for the receivable account and a certificate associated with the receivable account, and a check rule for the receivable account and the certificate associated with the receivable account.

For example, after the financing applicant submits a plurality of bills and bills associated with the bills, it may be determined whether each bill includes the above six elements and whether the format of the bills meets the standard according to the checking rule.

In one embodiment shown, an intelligent contract corresponding to the account receivable uplink service and deployed on the blockchain is called, checking logic of the certificate is executed, and a checking result aiming at the certificate is determined; and issuing a plurality of accounts receivable, the certificate associated with the accounts receivable and the verification result of the certificate to the block chain for deposit and verification, wherein the accounts receivable and the certificate are held by the financing application party and submitted by the financing application party.

Specifically, before performing the receivables uplink operation, the certificate needs to be checked to determine whether the receivables are authentic.

For example, an intelligent contract corresponding to the accounts receivable uplink service, which is created by the asset management platform and deployed on the blockchain, may be invoked, a verification logic for the credential may be executed, the credential may be sent to a third-party organization for verification, and a verification result returned by the third party may be received to determine a verification result for the credential.

It should be noted that the data format of the verification result returned by the third party may be different, and a standard data format is also required to be configured for the verification result of the certificate.

Furthermore, a plurality of accounts receivable, the certificate associated with the accounts receivable and the verification result of the certificate, which are submitted by the financing applicant, are issued to the blockchain for evidence storage.

After the receivables are linked, a pledge for receivables designated by the financing applicant may be initiated.

In one illustrated embodiment, the pool financing service includes an accounts receivable pledge service.

Further, in one illustrated embodiment, the accounts receivable data includes an identification corresponding to accounts receivable for the pledge.

Specifically, the financing applicant may initiate a pledge for a specified accounts receivable by submitting a corresponding identification for accounts receivable requiring pledge.

Similarly, the business system stores receivable pledge configuration information corresponding to the receivable pledge service issued by the asset service platform, wherein the receivable pledge configuration information includes a standard data format set for the identifier and a check rule for the identifier.

For example, the identifier may be a data digest obtained by hashing six elements of accounts receivable, and after receiving a service call request for the accounts receivable pledge service, it is determined whether the identifier matches a standard identifier format based on a check rule for the identifier.

In one embodiment, calling an intelligent contract corresponding to the accounts receivable pledge service and deployed on the blockchain, executing capture logic, and acquiring accounts receivable corresponding to the identification, the certificate associated with the accounts receivable and the verification result of the certificate from the blockchain based on the identification corresponding to the accounts receivable for pledge;

executing filtering logic, and judging whether the accounts receivable corresponding to the identification, the certificate associated with the accounts receivable and the verification result of the certificate meet preset pledge conditions or not;

if so, the accounts receivable for the pledge is added to the accounts receivable pool.

Specifically, an intelligent contract created by the asset management platform according to the accounts receivable pledge service is deployed on the blockchain, and capture logic is executed by calling the intelligent contract, so that accounts receivable corresponding to the identification, a certificate associated with the accounts receivable and a verification result of the certificate can be acquired from the blockchain based on the identification of the accounts receivable for the pledge.

For example, by executing the capture logic, the accounts receivable specified by the financing applicant, the vouchers associated with the accounts receivable, and the verification results of the vouchers can be determined from the data deposited on the chain based on the data summaries of the accounts receivable specified by the financing applicant.

Although the financing applicant initiates a pledge for a specified receivable, it is still necessary to make a determination as to whether the specified receivable can be pledged. The asset management platform can set some filtering conditions for screening so as to remove accounts receivable which do not accord with the pledge conditions.

For example, the asset management platform may set a blacklist and a whitelist for the financing applicant to exclude users of the blacklist; for another example, the bill status in the six elements of the receivables can be screened, and only the created bill is pledged.

Further, executing filtering logic, and judging whether the accounts receivable corresponding to the identification, the certificate associated with the accounts receivable and the verification result of the certificate meet the preset pledge condition or not; and if so, adding the accounts receivable for the pledge to the accounts receivable pool, and finishing the pool entering operation of the accounts receivable.

In addition, after the accounts receivable in the accounts receivable pool are checked and sold, the accounts receivable needs to be deleted from the accounts receivable pool, and the operation of leaving the accounts receivable pool is completed.

It is worth noting that, for the purpose of protecting data privacy, the above block chain can be divided into a service chain used by a financing applicant and a financing chain used by an asset management platform.

In one illustrated embodiment, the blockchain includes a business chain for crediting the accounts receivable data and a financing chain for crediting the accounts receivable pool;

further, the receivable accounts for the pledge which are stored on the business chain and are used for the pledge are pushed to the financing chain in a cross-chain mode, and the receivable accounts for the pledge are added to a receivable account pool.

For example, the financing applicant can store accounts receivable, the certificate associated with the accounts receivable, and the verification result of the certificate to its own business chain, and after the financing applicant initiates the designated accounts receivable pledge, the designated accounts receivable and the certificate associated with the accounts receivable, and the verification result of the certificate are pushed to the financing chain across the chain, so as to protect the privacy of other accounts receivable data.

The method for pushing across chains is not limited in this application, and a person skilled in the art may use a method of calling a contract for pushing across chains, or may use a method of relaying across chains to implement across-chain docking to complete pushing.

In one illustrated embodiment, the financing chain comprises a federation chain co-established by the asset service platform and a financing provider.

Specifically, the financing provider may obtain the accounts receivable data according to the accounts receivable pool of the federation chain deposit certificate.

After the accounts receivable pledge and the accounts receivable pool are created, a financing application for the accounts receivable pool may be initiated by a financing applicant.

In one illustrated embodiment, the pool financing service includes a financing application service.

Further, in one illustrated embodiment, the receivables data includes financing application data.

Specifically, the business system stores account receivable financing application configuration information corresponding to the account receivable financing application service issued by the asset service platform, wherein the account receivable financing application configuration information comprises a standard data format set for financing application and a check rule for financing application.

For example, the standard data format for a financing application may include financing applicant, payee, and transaction information, such as freight carrier, driver, and waybill information.

In one embodiment shown, the intelligent contracts corresponding to the financing application service deployed on the blockchain are called, application logic is executed, and the financing application is submitted to a financing provider to be approved by the financing provider according to the financing application.

The intelligent contract corresponding to the financing application service created by the asset management platform can be deployed on a financing chain.

Specifically, the intelligent contract is called, the application logic is executed, the financing application is submitted to a financing provider, the financing provider carries out approval according to an accounts receivable pool formed by a plurality of accounts receivable of the financing applicant, and financing is sent to the financing applicant after approval is passed.

In one embodiment, the business system may be a logistics business system.

Further, in one embodiment shown, the logistics business system comprises a logistics business system for cross-border settlement.

It should be noted that, for other service links in the pool financing service, the receivable account uplink service, the receivable account pledge service and the financing application service may also be referred to, the asset service platform provides a plugin service according to the service logic, the asset service platform issues corresponding configuration information according to the service, and finally processes the receivable account data submitted by the financing application party, thereby providing a corresponding service and completing the operation of the link, which is not described herein again. Those skilled in the art can understand that only configuration information needs to be preset in the background by an operator of an asset service platform, and a business system can automatically operate according to standardized accounts receivable data submitted by a financing applicant and access to a pool financing service, so that transverse enabling and rapid copying of pool financing products in a business line are realized.

Through the technical scheme, the asset service platform abstracts the service logic according to the pool financing service scene, provides the pool financing service in a plug-in mode based on the logic, and issues the corresponding configuration information to the service system according to the content of the pool financing service, so that the service system can be quickly accessed to the pool financing service after receiving the standardized account receivable data submitted by a financing applicant. In the process, firstly, the scheme can be widely applied to various pool financing service scenes through the logic abstracted based on the pool financing service scenes; secondly, the access cost of a financing applicant can be reduced by providing a plug-in pool financing service, and the financing applicant only needs to provide standardized accounts receivable data; moreover, by setting configuration information corresponding to the pool financing service, more flexible service can be provided for the financing application party, dynamic configuration is realized for the whole flow of the pool financing service, and finally the financing application party can rapidly access the pool financing service according to preset configuration information after submitting standardized account receivable data.

Corresponding to the method embodiment, the application also provides an embodiment of the device.

Corresponding to the embodiment of the method, the application also provides an embodiment of a pool financing management device based on the block chain. The embodiment of the block chain-based pool financing management device can be applied to electronic equipment. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, as a logical device, the device is formed by reading, by a processor of the electronic device where the device is located, a corresponding computer program instruction in the nonvolatile memory into the memory for operation. From a hardware aspect, as shown in fig. 5, a hardware structure diagram of an electronic device where a pool financing management device based on a block chain is shown in an exemplary embodiment of the present application, except for the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 5, the electronic device where the device is located in the embodiment may also include other hardware generally according to the actual function of the electronic device, which is not described again.

Referring to fig. 6, fig. 6 is a block diagram of a block chain-based pool financing management apparatus according to an exemplary embodiment of the present application, and as shown in fig. 6, the block chain-based pool financing management apparatus 600 may be applied in the electronic device shown in fig. 5, and includes:

a receiving unit 601, configured to receive a service invocation request for the pool financing service, where the service invocation request is initiated by the financing applicant; wherein the service invocation request includes receivable data submitted by the financing applicant; the business system stores configuration information which is issued by the asset service platform and corresponds to the pool financing service; the configuration information includes a standard data format set for the accounts receivable data and a validation rule for the accounts receivable data.

A checking unit 602, configured to check, in response to the service invocation request, whether a data format of the receivable data submitted by the financing applicant matches the standard data format based on the checking rule.

And if the block chains are matched with the pool financing service, the calling unit 603 further calls the intelligent contract which is deployed on the block chain and corresponds to the pool financing service, and provides the pool financing service for the financing applicant.

In one embodiment, the business system runs a plug-in pool financing service provided by an asset service platform, comprising: the business system runs a pool financing service plug-in provided by the asset service platform.

In one embodiment, the pool financing service opens a configuration interface to the asset service platform;

the block chain-based pool financing management apparatus 600 further includes:

a storage unit 604, configured to receive a call request for the configuration interface sent by the asset service platform; wherein the invocation request includes configuration information generated by an operator for the pool financing service on the asset service platform; and responding to the calling request, and storing the configuration information in the service system.

In one embodiment, the pool financing service comprises an accounts receivable uplink service.

In one embodiment, the receivables data includes a plurality of receivables held by the financing applicant, and a voucher associated with the receivables.

Further, in an embodiment, the invoking unit 603 includes:

calling an intelligent contract which is deployed on the blockchain and corresponds to the account receivable uplink service, executing a verification logic of the certificate, and determining a verification result aiming at the certificate;

and issuing a plurality of accounts receivable, the certificate associated with the accounts receivable and the verification result of the certificate to the block chain for deposit and verification, wherein the accounts receivable and the certificate are held by the financing application party and submitted by the financing application party.

In one embodiment, the pool financing service includes an accounts receivable pledge service.

In an embodiment, the accounts receivable data includes an identification corresponding to accounts receivable for a pledge.

Further, in an embodiment, the invoking unit 603 includes:

calling an intelligent contract which is deployed on the blockchain and corresponds to the accounts receivable pledge service, executing capture logic, and acquiring accounts receivable corresponding to the identification, the certificate related to the accounts receivable and the verification result of the certificate from the blockchain based on the identification corresponding to the accounts receivable for pledge;

In one embodiment, the blockchain includes a business chain for crediting the accounts receivable data and a financing chain for crediting the accounts receivable pool;

specifically, the invoking unit 603 further:

and pushing accounts receivable for the pledge which is deposited on the business chain and is certified to the financing chain in a cross-chain manner, and adding the accounts receivable for the pledge to an accounts receivable pool.

In one embodiment, the financing chain comprises a federation chain co-established by the asset service platform and a financing provider.

In one embodiment, the pool financing service comprises a financing application service.

In one embodiment, the receivables data comprises financing application data.

Further, in an embodiment, the invoking unit 603 includes:

and calling an intelligent contract which is deployed on the blockchain and corresponds to the financing application service, executing application logic, submitting the financing application to a financing provider, and examining and approving the financing provider according to the financing application.

In one embodiment, the business system comprises a logistics business system.

In one embodiment, the logistics business system comprises a logistics business system for cross-border settlement.

The embodiments in the present application are described in a progressive manner, and the same/similar parts in the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. Especially, for the embodiments of the client device and the apparatus, since they are substantially similar to the embodiments of the method, the description is simple, and for the relevant points, refer to the partial description of the embodiments of the method.

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, wherein the modules described as separate parts may or may not be physically separate, and the parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.

The apparatuses, systems, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

Corresponding to the method embodiment, the present specification also provides an embodiment of an electronic device. The electronic device includes: a processor and a memory for storing machine executable instructions; wherein the processor and the memory are typically interconnected by an internal bus. In other possible implementations, the device may also include an external interface to enable communication with other devices or components.

In this embodiment, the processor is caused to:

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims

1. A pool financing management method based on a block chain is applied to a business system, and the business system runs a plug-in pool financing service provided by an asset service platform; the pool financing service comprises a financing service provided for a financing applicant based on a receivable pool consisting of a plurality of receivable accounts of the financing applicant; the method comprises the following steps:

2. The method of claim 1, the business system running a plug-in pooling financing service provided by an asset service platform, comprising:

the business system runs a pool financing service plug-in provided by the asset service platform.

3. The method of claim 2, the pool financing service opening a configuration interface to the asset service platform;

the method further comprises the following steps:

receiving a calling request aiming at the configuration interface sent by the asset service platform; wherein the invocation request includes configuration information generated by an operator for the pool financing service on the asset service platform;

and responding to the calling request, and storing the configuration information in the service system.

4. The method of claim 1, the pool financing service comprising an upper receivables service.

5. The method of claim 4, the accounts receivable data comprising a plurality of accounts receivable held by the financing applicant and a voucher associated with the accounts receivable.

6. The method of claim 5, the invoking of an intelligent contract corresponding to the pool financing service deployed on the blockchain to provide the pool financing service to the financing applicant, comprising:

7. The method of claim 6, the pool financing service comprising an accounts receivable pledge service.

8. The method of claim 7, the accounts receivable data comprising an identification corresponding to accounts receivable for a pledge.

9. The method of claim 8, the invoking of an intelligent contract corresponding to the pool financing service deployed on the blockchain to provide the pool financing service to the financing applicant, comprising:

10. The method of claim 9, the blockchain comprising a business chain for crediting the accounts receivable data and a financing chain for crediting the accounts receivable pool;

the adding the accounts receivable for the pledge to an accounts receivable pool, comprising:

11. The method of claim 10, the financing chain comprising a federation chain co-established by the asset service platform and a financing provider.

12. The method of claim 9, the pool financing service comprising a financing application service.

13. The method of claim 12, the receivables data comprising financing application data.

14. The method of claim 13, the invoking of an intelligent contract corresponding to the pool financing service deployed on the blockchain to provide the pool financing service to the financing applicant, comprising:

15. The method of any of claims 1-14, the business system comprising a logistics business system.

16. The method of claim 15, the logistics business system comprising a logistics business system for cross-border settlement.

17. A pool financing management device based on a block chain is applied to a business system, and the business system runs a plug-in pool financing service provided by an asset service platform; the pool financing service comprises a financing service provided for a financing applicant based on a receivable pool consisting of a plurality of receivable accounts of the financing applicant; the device includes:

18. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, carry out the steps of the method according to any one of claims 1 to 16.

19. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the method of any one of claims 1-16 by executing the executable instructions.