CN115099800A - Block chain based method and device for transferring poor asset data - Google Patents

Block chain based method and device for transferring poor asset data Download PDF

Info

Publication number
CN115099800A
CN115099800A CN202210759137.XA CN202210759137A CN115099800A CN 115099800 A CN115099800 A CN 115099800A CN 202210759137 A CN202210759137 A CN 202210759137A CN 115099800 A CN115099800 A CN 115099800A
Authority
CN
China
Prior art keywords
asset
data
bad
transferee
transferor
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210759137.XA
Other languages
Chinese (zh)
Inventor
莫逸红
刘旭进
田东超
赵光军
贺磊
赵栋
刘冲
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ant Blockchain Technology Shanghai Co Ltd
Original Assignee
Ant Blockchain Technology Shanghai Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ant Blockchain Technology Shanghai Co Ltd filed Critical Ant Blockchain Technology Shanghai Co Ltd
Priority to CN202210759137.XA priority Critical patent/CN115099800A/en
Publication of CN115099800A publication Critical patent/CN115099800A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

The embodiment of the specification provides a method and a device for transferring poor asset data based on a block chain. In the method, at an asset transferor, transmitting the bad asset data corresponding to the bad asset to a blockchain server, wherein the blockchain server is one of servers used for constructing a blockchain network; at a blockchain server, chaining bad asset data to a first blockchain; and after the asset transferor and the asset transferee achieve a transfer transaction consensus aiming at the undesirable asset, responding to a first data request sent by the asset transferee, and authorizing the asset transferee so that the asset transferee can acquire the undesirable asset data, wherein the first data request comprises first identity information of the asset transferee and the requested first data information.

Description

Block chain based method and device for transferring poor asset data
Technical Field
The embodiment of the specification relates to the technical field of block chains, in particular to a method and a device for transferring poor asset data based on the block chains.
Background
In the financial field, a financial institution may offer credit to individuals, businesses, etc., and a borrower returns the information to the financial institution on time and in quantity according to a predetermined term. If the borrower cannot return the interest on time and by volume, the loan can be classified as a bad property. For the bad assets, the financial institution can adopt a special person to urge to collect the bad assets so as to solve the problem of the bad assets. After a period of time, the problem that the bad assets cannot be solved, in order to avoid the bad assets affecting the bad rate of the financial institution, the financial institution can trade the bad assets to a third-party asset management institution, and the third-party asset management institution continues to urge to collect the bad assets. Through the transaction mode, the financial institution can obtain partial cash back, and the bad assets which are transacted do not belong to the standing account of the financial institution any more, so the bad rate of the financial institution is not influenced any more.
However, the transaction of the undesirable asset relates to the transfer of the undesirable asset data, and how to ensure the safe circulation of the data in the transfer process of the undesirable asset data is a problem to be solved.
Disclosure of Invention
In view of the foregoing, the present specification provides a method and apparatus for transferring bad asset data based on a blockchain. Through the technical scheme of the embodiment of the specification, the safety of data circulation of the poor asset data in the transfer process can be ensured by using the block chain technology.
According to an aspect of the embodiments of the present specification, there is provided a method for transferring bad asset data based on a blockchain, including: at an asset transferor, sending the bad asset data corresponding to the bad asset to a blockchain server, wherein the blockchain server is one of servers used for constructing a blockchain network; at the blockchain server, linking the bad asset data to a first blockchain; and after the asset transferor and the asset transferee achieve the transfer transaction consensus aiming at the undesirable asset, responding to a first data request sent by the asset transferee, and authorizing the asset transferee so that the asset transferee acquires the undesirable asset data, wherein the first data request comprises first identity information of the asset transferee and the requested first data information.
According to another aspect of embodiments of the present specification, there is also provided a blockchain-based method for transferring bad asset data, performed by a blockchain server, the blockchain server being one of servers used for constructing a blockchain network, the method including: responsive to receiving, from an asset transferor of a bad asset, bad asset data corresponding to the bad asset, uplink the bad asset data; and after the asset transferor and the asset transferee achieve a transfer transaction consensus aiming at the undesirable asset, responding to a first data request sent by the asset transferee, and authorizing the asset transferee so that the asset transferee acquires the undesirable asset data, wherein the first data request comprises first identity information of the asset transferee and the requested first data information.
According to another aspect of the embodiments of the present specification, there is also provided an apparatus for transferring bad asset data based on a blockchain, the apparatus being applied to a blockchain server, the blockchain server being one of servers used for building a blockchain network, the apparatus including: the uplink unit is used for responding to the bad asset data corresponding to the bad asset received from the asset transferor of the bad asset and uplink the bad asset data; and an authorization unit, after the asset transferor and the asset transferee reach a transfer transaction consensus aiming at the bad asset, responding to a first data request sent by the asset transferee, and authorizing the asset transferee so that the asset transferee acquires the bad asset data, wherein the first data request comprises first identity information of the asset transferee and the requested first data information.
According to another aspect of embodiments herein, there is also provided an electronic device, including: at least one processor, a memory coupled to the at least one processor, and a computer program stored on the memory, the computer program being executable by the at least one processor to implement a blockchain based method for transferring undesirable asset data as set forth in any of the above.
According to another aspect of embodiments herein, there is also provided a computer readable storage medium storing a computer program which, when executed by a processor, implements the blockchain-based method for transferring undesirable asset data as described above.
According to another aspect of embodiments of the present specification, there is also provided a computer program product comprising a computer program which when executed by a processor implements the blockchain-based method for transferring poor asset data as described above.
Drawings
A further understanding of the nature and advantages of the contents of the embodiments of the present specification may be realized by reference to the following drawings. In the drawings, similar components or features may have the same reference numerals.
FIG. 1 illustrates a schematic diagram of an example environment, according to embodiments of the present description.
Fig. 2 illustrates an example architectural diagram of a blockchain network in accordance with an embodiment of this specification.
Fig. 3 is a signaling diagram illustrating one example of a method for transferring bad asset data based on a blockchain in accordance with an embodiment of the present specification.
Fig. 4 shows a schematic diagram of one example of a consensus process according to embodiments of the present specification.
Fig. 5 is a diagram illustrating an example of formats of a pre-preparation message, a preparation message, and an acknowledgement message in a consensus process according to an embodiment of the present specification.
Fig. 6 illustrates a signaling diagram of one example of authorizing an asset transferor in accordance with an embodiment of the present description.
Figure 7 illustrates a flow chart of one example of a method for transferring bad asset data based on blockchain in accordance with an embodiment of the present description.
Fig. 8 is a flowchart illustrating an example of an apparatus for transferring bad asset data based on a blockchain according to an embodiment of the present specification.
Fig. 9 is a block diagram illustrating an electronic device for implementing an undesirable asset data transfer method in accordance with an embodiment of the present specification.
Detailed Description
The subject matter described herein will be discussed with reference to example embodiments. It should be understood that these embodiments are discussed only to enable those skilled in the art to better understand and thereby implement the subject matter described herein, and are not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the embodiments of the disclosure. Various examples may omit, substitute, or add various procedures or components as needed. In addition, features described with respect to some examples may also be combined in other examples.
As used herein, the term "include" and its variants mean open-ended terms, meaning "including but not limited to. The term "based on" means "based at least in part on". The terms "one embodiment" and "an embodiment" mean "at least one embodiment". The term "another embodiment" means "at least one other embodiment". The terms "first," "second," and the like may refer to different or the same object. Other definitions, whether explicit or implicit, may be included below. The definition of a term is consistent throughout the specification unless the context clearly dictates otherwise.
The block chain is a distributed shared account book and a database, and has the characteristics of decentralization, no tampering, trace keeping, backtracking, openness and transparency and the like. The data on the block chain is stored in the form of data blocks, and the data blocks are connected in time sequence to form a chain data structure. Each block in the chain of blocks is linked to the previous block by an included cryptographic hash, and each block further includes a timestamp, a cryptographic hash, and one or more transactions. The individual transactions in the block form a Merkle tree by hashing. In a Merkle tree, the lowest leaf node contains the underlying data, each intermediate node is a hash of its child node, the root node is a hash of its child node, representing the root of the Merkle tree, and the root node of the Merkle tree stores hash values representing all the data in the Merkle tree. When verifying whether a hash value is a transaction stored in the Merkle tree, quick verification can be performed by determining whether the hash value is consistent with the structure of the Merkle tree.
A blockchain network is a decentralized point-to-point network consisting of multiple computing nodes for managing, updating, and maintaining one or more blockchain structures. The types of blockchain networks may include public blockchain networks, private blockchain networks, and alliance blockchain networks, depending on the degree of openness of the nodes in the blockchain network.
The public blockchain network is a public network of participating entities, thousands of entities can cooperate in the public blockchain network, each entity operates at least one node in the public blockchain network, and accordingly, the consensus process in the public blockchain network is also completed by each node. In the consensus process, a node participating in the consensus signs a block to indicate that the node acknowledges the consensus for the block, and then the block that completed the consensus is added to the block chain of the block chain network. In addition, the public blockchain network supports public transactions, and the public transactions are shared among all nodes in the public blockchain network and are stored in the global blockchain after being identified by all the nodes. A global blockchain refers to a blockchain that is replicated across all nodes. Consensus in a blockchain network is supported by a consensus mechanism, which is an algorithm for blockchain transactions to achieve distributed consensus, which may include: proof of work (POW), proof of rights (POS), and proof of authority (POA).
The private block chain network only aims at a specific entity, and the read-write permission of each node in the private block chain network is strictly controlled. In addition, the threshold for joining the private blockchain network is high, and it needs to be allowed to join the private blockchain network to become one of the nodes, based on which, the private blockchain network is also commonly referred to as an allowed network, which limits who is allowed to participate in the network and the participation level in the network, for example, some nodes may participate in the uplink process of all transactions, and some nodes may only participate in the uplink process of a designated part of transactions. Various types of access control mechanisms may be used in private blockchain networks, such as voting of adding new entities by existing participants, regulatory agency control permissions, and the like.
The participating entities in the federated blockchain network are also private from each other and can be considered private networks of the participating entities. A federated blockchain network may be composed of several entities, each of which operates at least one node in the federated blockchain network. The consensus process in the federated coalition blockchain network is performed by authorized nodes, which may be all or part of the nodes in the federated coalition blockchain network, each of which signs a block to be uplinked to indicate a consensus acknowledgement for that block, which is then added to the blockchain.
FIG. 1 illustrates a schematic diagram of an example environment 100, according to embodiments of the present description. As shown in fig. 1, the example environment 100 allows entities to participate in a blockchain network 102. The blockchain network 102 may be, for example, a public, private, or alliance chain blockchain network. The example environment 100 may include computing devices 104, 106, 108, 110, 112 and a network 114. In an embodiment, the Network 114 may include a Local Area Network (LAN), Wide Area Network (WAN), the internet, or a combination thereof, and is connected to websites, user devices (e.g., computing devices), and backend systems. In an embodiment, the computing devices 104, 106, 108, 110, 112 may access the network 114 through wired and/or wireless communication.
In some cases, the computing devices 106, 108 may be nodes of a cloud computing system (not shown), or each computing device 106, 108 may be a separate cloud computing system, including multiple computers interconnected by a network and operating as a distributed processing system.
In an embodiment, the computing devices 104-108 may run any suitable computing system that enables them to act as nodes in the blockchain network 102. For example, the computing devices 104-108 may include, but are not limited to, servers, desktop computers, laptops, tablet computing devices, and smartphones. In an embodiment, the computing devices 104-108 can be affiliated with a related entity and used to implement a corresponding service, which can be used to manage transactions between an entity or entities, for example.
In one embodiment, the computing devices 104-108 respectively store a blockchain ledger corresponding to the blockchain network 102. The computing device 104 may be (or include) a web server for providing browser functionality that may provide visualization information related to the blockchain network 102 based on the network 114. In some cases, the computing device 104 may not participate in the block verification, but rather monitor the blockchain network 102 to determine when other nodes (which may include, for example, the computing devices 106 and 108) agree, and generate a corresponding blockchain visualization user interface accordingly.
In an embodiment, computing devices 110 and 112 may be client devices connected to blockchain network 102. For example, computing device 110 may be a terminal device at a medical facility platform and computing device 112 may be a terminal device at an advertising administration platform. Computing devices 110 and 112 may include, but are not limited to, servers, desktop computers, laptops, tablet computing devices, and smartphones.
In an embodiment, computing device 104 may receive a request initiated by a client device (e.g., computing device 110 or computing device 112) for a blockchain visualization user interface. In some cases, the nodes of the blockchain network 102 may also act as client devices, such that a user of the computing device 108 may send the request to the computing device 104 using a browser running on the computing device 108.
In response to the request, computing device 104 may generate a blockchain visualization user interface (e.g., a web page) based on the stored blockchain ledger and send the generated blockchain visualization user interface to the requesting client device. If blockchain network 102 is a private type or a federated type blockchain network, the request for the blockchain visual user interface may include user authorization information, which may be verified by computing device 104 before generating and sending the blockchain visual user interface to the requesting client device, and the corresponding blockchain visual user interface returned after verification.
The blockchain visualization user interface may be displayed on the client device (e.g., as may be displayed in user interface 116 shown in fig. 1). When the blockchain ledger is updated, the display content of the user interface 116 may be updated accordingly. Further, user interaction with user interface 116 may result in requests to other user interfaces, such as a search results page that displays a block list, block details, transaction list, transaction details, account list, account details, contract list, contract details, or results of a user conducting a search of the block chain network, and so forth.
Fig. 2 illustrates an example architectural diagram of a blockchain network in accordance with an embodiment of this specification.
As shown in fig. 2, blockchain server 220 is a blockchain link point or component thereof in blockchain network 214, and asset transferor 221 and asset transferee 223 may use a blockchain service platform, which may be made up of a plurality of blockchain servers, of which blockchain server 220 is one.
While the blockchain server 220 shown in fig. 2 connects one asset transferor 221 and one asset transferee 223 is provided as an example, while the undesirable asset transactions shown in fig. 2 are conducted between one asset transferor 221 and one asset transferee 223 is also provided as an example, blockchain server 220 may also be communicatively connected to a plurality of other participants, and each undesirable asset transaction may also be conducted between a plurality of asset transferors 221 and a plurality of asset transferees 223.
Asset transferor 221 and asset transferee 223 may use the blockchain service platform for the transfer of undesirable asset data through a client device that is communicatively coupled to blockchain server 220. Asset transferor 221 and asset transferee 223 are each communicatively coupled to blockchain server 220 via client devices through which transfer of objectionable asset data is conducted. In the process of transferring asset data between the asset transferor 221 and the asset transferee 223, the bad asset data to be transferred may be collected by the blockchain server 220, and the blockchain server 220, as a blockchain node in the blockchain network 214 or a component thereof, may link the collected bad asset data to the blockchain 216 for storage, so as to prevent the stored transaction data from being deleted or tampered, so as to ensure data security.
In one example, after the undesirable asset is traded to the asset transferee 223, the asset transferee 223 may delegate the asset disposition mechanism 225 of the third party to perform disposition such as collection of the undesirable asset, and the asset disposition mechanism 225 needs to perform disposition according to the related data information corresponding to the undesirable asset when performing disposition. Asset handling mechanism 225 may be communicatively connected to blockchain server 220 such that authorization of bad asset data may be requested through blockchain server 220.
Fig. 3 illustrates a signaling diagram of one example 300 of a method for transferring bad asset data based on blockchains in accordance with an embodiment of the present description.
As shown in fig. 3, at 310, at an asset transferor, the corresponding asset data for the asset may be obtained.
In embodiments of the present description, an asset transferor is a party that transfers an undesirable asset, and the asset transferor may include a financial institution such as a bank. The undesirable asset may be generated by the asset transferor, for example, a financial asset of the asset transferor may become a pending undesirable asset due to a overdue breach of repayment, and the like, and thus, ownership of the generated undesirable asset may be attributed to the asset transferor.
Each bad asset can correspond to bad asset data, the bad asset data can comprise credited asset data, the credited asset data is asset data after financial assets generated by user loan become bad assets, the credited asset data can comprise basic bad asset information and collection urging record information, the basic bad asset information can comprise debtor, amount, loan term, interest rate and the like, the collection urging record information can comprise time of each collection urging, amount of repayment and other information of collection urging and the like, and the other information of collection urging can comprise repayment willingness of a repayment person, time consumed by collection urging and the like.
In addition, the bad asset data may further include: pre-loan asset data, and in-loan asset data, etc. The pre-loan property data may include pre-loan property status data for the user, such as the status of funds, fixed property status, consumption status, etc. for each account the user has in advance of the loan. The property data in the loan may include property data during the period from the time the user loans to the time before the user is overdue, during which the user is in the payment stage, and thus, the property data in the loan may include a time point of each payment, an amount of each payment, a payment manner, and the like.
In one example, for a financial asset of the asset transferor, the execution process for each financial asset may include loan application, loan issuance, repayment, and the like. During the execution of the financial assets, corresponding asset data may be generated, and the generated asset data may include pre-loan asset data and in-loan asset data, such as loan application data, loan issuance data, repayment data, and the like, where the loan application data may include loan application data of the user, audit data of the financial institution, and the like, the loan issuance data may include time, manner, amount, and the like of loan issuance, and the repayment data may include time, amount, manner, and the like of repayment.
After the asset data is generated at the asset transferor, the asset transferor can chain the generated asset data to store the asset data in real time, thereby ensuring the security of the asset data and avoiding the asset data from being tampered.
In one mode of uplink, the asset transferor may send the generated asset data to the blockchain server, which uplinks the generated asset data to the first blockchain.
In another uplink mode, a blockchain integrator may be locally disposed at the asset transferor, and a second blockchain applied by the blockchain integrator is different from a first blockchain applied by the blockchain server. In the uplink mode, during the execution of the financial asset, the generated asset data may be linked to the second blockchain for storage by the local blockchain integrator.
In the above example, when a financial asset becomes a bad asset, asset data corresponding to the financial asset may be determined as bad asset data corresponding to a bad asset.
In one example, when a financial asset becomes a bad asset, asset data corresponding to the financial asset recorded on the second blockchain may be transferred as bad asset data onto the first blockchain by a cross-chain technique. In a chain crossing mode, the blockchain all-in-one machine is provided with a transaction conversion component for converting data to be subjected to chain crossing into format data in a unified format, so that when chain crossing operation is executed, the blockchain all-in-one machine can call the transaction conversion component to convert asset data to be subjected to chain crossing and stored on a second blockchain into format bad asset data in the unified format as bad asset data. And then, a contract communication protocol in a contract communication component is called through a cross-chain communication intelligent contract, the format poor asset data is sent to a block chain server on the first block chain, the block chain server can analyze the format poor asset data after receiving the format poor asset data to obtain the poor asset data, and the obtained poor asset data is linked to the first block chain.
By the above example, the asset data corresponding to the financial asset can be linked up in real time, and the efficiency of linking up the asset data is improved by linking up the local blockchain all-in-one machine. After the financial assets become the bad assets, the bad asset data on the second block chain is integrated and stored to the first block chain, and the block chain server can conveniently and uniformly manage the bad asset data of the bad assets.
At 320, the asset transferor may send the bad asset data to the blockchain server.
In one example, the objectionable asset data generated by the objectionable assets may be screened by a specified asset data type to screen out objectionable asset data that partially conforms to the specified asset data type. The specified asset data type may be a predetermined data type required to handle the undesirable asset, and in one example, the specified asset data type may include: creditor, debtor, time of occurrence of debt, amount, loan term, interest rate, and the like. The specified asset data type may be applicable to each of the different asset transferors by which a uniform type of data in the undesirable asset data from each of the asset transferors may be uplinked. After the undesirable asset data is screened out, the asset transferor may send the screened undesirable asset data to the blockchain server.
In this example, screening for bad asset data using a specified asset data type may screen out another portion of unnecessary data while ensuring that data required for bad asset handling can be uplink, reducing the amount of uplink data.
In another example, the asset transferor may send all of the collected asset data to the blockchain server so that all of the asset data can be stored in the uplinks.
At 330, at the blockchain server, the bad asset data can be linked up.
The blockchain server may pack the bad asset data into blocks and chain the packed blocks to a first blockchain. During block uplink, each block link point in the block chain network as a common node can perform common identification processing on the block, and after the common identification is achieved, the block is recorded on the first block chain.
Fig. 4 illustrates a schematic diagram of one example 400 of a consensus process according to embodiments of the present description. In the example of fig. 4, the accounting node (i.e., the master node) is R0, referred to hereinafter as the master node in this example. The determined consensus nodes (i.e., backup nodes) participating in consensus may include R1, R2, and R3, referred to hereinafter as backup nodes in this example. It should be noted that the consensus process shown in fig. 4, which includes 4 network nodes R0, R1, R2 and R3, is for illustrative purposes only, and the consensus process may include any suitable number of network nodes.
The main node R0 performs a consensus process with all consensus nodes participating in the consensus in the blockchain network, for example, the main node R0 performs a consensus process with the backup nodes R1, R2, and R3.
In the present disclosure, the consensus process may be implemented using PoW (workload proof algorithm), PoS (equity proof algorithm), PBFT (practical byzantine fault-tolerant algorithm), and the like. The following description will be made by taking the PBFT consensus process as an example.
As shown in fig. 4, the procedure of the PBFT consensus process includes: a Pre-preparation phase (Pre-preparation) 410, a preparation phase (preparation) 420, and a validation phase (Commit) 430.
Specifically, at 410, the master node R0 packages the transaction data to be recorded into the blockchain into a message m, then generates a Pre-prepare message Pre-prepare, and sends (e.g., broadcasts) the Pre-prepare message Pre-prepare to the backup nodes R1, R2, and R3 within a given time interval. The Pre-prepare message Pre-prepare indicates that master node R0 is initiating the consensus process.
In the embodiment of the present specification, as shown in fig. 5, the format of the Pre-preparation message Pre-preparation may be: < PRE-PREPARE, epoch, seq, D (m), signature-p >, m, j >. Here, "PRE-PREPARE" indicates a protocol identifier of the preliminary preparation message, "epoch" indicates an age in which R0 is the master node, "seq" indicates a proposed number of proposals to be agreed upon, "d (m)" indicates a digest of the request message set, "signature-p" indicates a signature of R0, "m" indicates specific contents of the request message (i.e., specific contents of each piece of authentication information in the block), and "j" indicates a node identifier of R0. Here, d (m) is obtained by performing hash calculation on each authentication information set in the block.
In the preparation stage 420, for each backup node (R1, R2, or R3), after receiving the Pre-preparation message Pre-preparation and detecting that the Pre-preparation message Pre-preparation is legitimate, the Pre-preparation message Pre-preparation may be stored in a local log, and a preparation message preparation for responding to the Pre-preparation message Pre-preparation may be generated and then broadcast to other nodes. The Prepare message Prepare indicates that the backup node has received the Pre-Prepare message Pre-Prepare from the primary node and is sending a reply in response to the Pre-Prepare message Pre-Prepare.
Accordingly, each backup node also receives preparation messages Prepare sent by other backup nodes. Taking backup node R1 as an example, after receiving the Prepare message Pre-Prepare sent by master node R0, backup node R1 broadcasts the generated Prepare message Pre-Prepare to master node R0, backup nodes R2, and R3. Accordingly, backup node R1 also receives Prepare message Prepare sent by primary node R0, backup nodes R2 and R3.
In this illustrative embodiment, the Prepare message Prepare broadcast by the backup node may be used to indicate the consensus commitment made by the backup node during the Prepare phase 420.
In this embodiment, as shown in fig. 5, the format of the preparation message Prepare may be: < PREPARE, epoch, seq, D (m), i, signature-i >. Here, "PREPARE" denotes a protocol identification of the preparation message PREPARE, "i" denotes a node identification of the node that transmitted the preparation message PREPARE, and "signature-i" denotes a signature of the node that transmitted the preparation message PREPARE. The meaning of "epoch", "seq", and "d (m)" in the preparation message Prepare is the same as that of "epoch", "seq", and "d (m)" in the aforementioned prepard message Pre-Prepare.
In the acknowledgement phase 430, when a network node receives a sufficient number of preparation messages Prepare from other network nodes, the network node determines that consensus has been reached. For example, if the primary node R0 or backup nodes R1, R2, or R3 receive qurum (e.g., 2f +1, where f represents the number of failed network nodes) Prepare messages Prepare, it is determined that consensus is achieved between the network nodes. The master node R0 or the backup node R1, R2 or R3 then broadcasts a confirmation message Commit to the other nodes.
In this embodiment, as shown in fig. 5, the format of the acknowledgment message Commit may be: < COMMIT, epoch, seq, D (m), p, signature-p >. Wherein "COMMIT" represents a protocol identification of the acknowledgment message COMMIT, "p" represents a node identification of a node that transmits the acknowledgment message COMMIT, and "signature-p" represents a signature of the node that transmits the acknowledgment message COMMIT. The meaning of "epoch", "seq" and "d (m)" in the acknowledgment message Commit is the same as that of "epoch", "seq" and "d (m)" in the aforementioned Pre-preparation message Pre-preparation.
In this illustrative embodiment, a node sends a confirmation message Commit and stores the confirmation message Commit in a local log to represent consensus commitments made by the node during the confirmation phase 430.
In one example, at the blockchain server, upon receiving the bad asset data, summary information extraction can be performed on the bad asset data, and the extracted summary information can serve as a brief description of the bad asset data. The blockchain server may then uplink the extracted summary information to the first blockchain. Summary information and poor asset data may be stored in association on the first blockchain.
In one example of associative storage, summary information may be recorded in the same block in association with the bad asset data. In addition, a corresponding relationship can be established between the summary information and the bad asset data, and the established corresponding relationship is recorded in a block where the summary information and the bad asset data are located.
In addition, the block chain server can visually display the summary information, and the displayed objects can comprise an asset transferor, an asset transferee, an asset disposal mechanism and the like. Through the visual display of the summary information, the content of each piece of bad asset data can be made clear, so that the bad asset data can be authorized and obtained in a targeted manner.
In one example, the undesirable asset to be transferred by the asset transferor may comprise a plurality of undesirable assets and, as such, the undesirable asset data transmitted by the asset transferor may comprise undesirable asset data for the plurality of undesirable assets.
In this example, at the blockchain server, a repayment rate for each of the plurality of undesirable assets may be estimated based on the undesirable asset data corresponding to the plurality of undesirable assets, and the repayment rate may be used to represent a probability that a repayment is possible.
In an estimation mode, the bad asset data corresponding to each bad asset may include data such as expenditure record, wealth record, consumption record and the like of the user, so that the repayment rate of the bad asset may be estimated according to at least one of the data such as expenditure record, wealth record, consumption record and the like in the bad asset data, wherein the wealth recorded in the wealth record may include real estate, deposits, stocks, funds and the like. Specifically, the more expenses in the expense record, the higher the repayment rate; the less the expenditure, the lower the repayment rate. The more wealth the user has in the wealth record, the higher the repayment rate is; the less the wealth, the lower the repayment rate. The more consumption in the consumption record, the higher the repayment rate; the less the consumption, the lower the repayment rate. In addition, the place of the user can be determined according to the consumption record, and the higher the place of the user is, the higher the repayment rate is; the more the place of presence is, the lower the repayment rate is.
After the repayment rate of each piece of the undesirable assets is estimated, the plurality of pieces of the undesirable assets can be sequenced according to the estimated repayment rate so as to obtain an undesirable asset sequence. In a sorting mode, sorting can be performed according to the sequence of repayment rate from high to low, and in the obtained bad asset sequence, the higher the ranking is, the higher the repayment rate is; the closer the rank is, the lower the repayment rate.
The blockchain server may provide the sequence of the undesirable assets to the asset transferee, so that the asset transferee may sequentially dispose of each undesirable asset in the sequence of the undesirable assets according to the sequence of the undesirable assets, for example, dispose of an undesirable asset with a higher repayment rate first and then dispose of an undesirable asset with a lower repayment rate. The provision of the sequence of undesirable assets may include the blockchain server transmitting the sequence of undesirable assets to the asset transferee and the blockchain server visually presenting the sequence of undesirable assets.
Returning to fig. 3, at 340, after the asset transferor agrees with the asset transferor on the transfer transaction for the undesirable asset, the asset transferor may send a first data request to the blockchain server.
In embodiments of the present specification, an asset transferor and an asset transferee may agree through a trading center to a transfer transaction for an undesirable asset. The trading center can be used for providing services such as asset trading service, transfer matching and online signing, and when an asset transferor and an asset transferee sign transfer trading combination aiming at the undesirable assets, the trading center can determine that the two parties reach transfer trading consensus aiming at the undesirable assets. When the asset transferor and the asset transferee achieve the transfer transaction consensus aiming at the bad asset, the transaction center can send transfer transaction achievement information to the block chain server, and the transfer transaction achievement information can comprise a copy of the transfer transaction contract, information of the asset transferor and the asset transferee and the like. The blockchain server may link transfer transaction achievement information to the first blockchain storage.
Further, the asset transferor may provide undesirable asset transfer requirements to the trading center before transfer transaction consensus is achieved. And then, the blockchain server can acquire the corresponding poor asset data of the poor asset to be transferred from the first blockchain, desensitize the acquired poor asset data, and send all or part of the desensitized poor asset data to the trading center, so that the trading center can match the asset transferee who transfers the trade according to the poor asset data.
After the asset transferor and the asset transferee agree on a transfer transaction for the undesirable asset, the asset transferee has the right to view the undesirable asset data recorded on the first blockchain. The first data request sent by the asset transferor may include first identity information of the asset transferor and the requested first data information, which may include the requested data type, by which the asset transferee determines the requested data.
After the blockchain server receives the first data request, at 350, the asset transferee may be authorized at the blockchain server.
In one authorization, a first intelligent contract is configured on a first blockchain, and the first intelligent contract is configured to perform an operation of verifying a data request. The first smart contract may authenticate a requesting principal of the data request, the requesting principal being a principal sending the data request, e.g., an asset transferor, and a data object, the data object being the requested data type. The data objects that different requesting principals are allowed to access may be different, e.g., the data that the asset transferor has access to is different from the data that the asset handling authority has access to, the asset transferor has access to all of the undesirable asset data for the transfer transaction, and the asset handling authority has access to only a portion of the undesirable asset data that is delegated to be handled.
The first intelligent contract may be configured with a verification policy, where the verification policy may include a white list, and the white list includes a request subject list allowing access and a data object list allowing access to each request subject, and in the white list, the request subject list may be set corresponding to the data object list, and each request subject is associated with a data object allowed to be accessed by the request subject.
In this authorization, the blockchain server may invoke a first intelligent contract to verify the first identity information and the first data information in the first data request in response to the first data request sent by the asset transferor. Specifically, the first intelligent contract performs a verification operation, the first identity information and the first data information may be respectively matched with a white list, and when the first identity information is matched with a request subject list recorded by the white list and the first data information is matched with a data object list correspondingly associated with the request subject matched in the white list, it may be determined that the verification is passed.
Upon verification, the asset transferor may be authorized so that the asset transferor may obtain authorized undesirable asset data.
In one example, the first intelligent agreement may confirm whether the asset transferor and the asset transferee agree with a transfer transaction for the undesirable asset before verifying the first data request, and the confirmation may include querying whether transfer transaction agreement information for the undesirable asset is recorded on the first blockchain, and if so, determining that the two parties agree with the transfer transaction, and then continuing to perform the operation of verifying the first data request.
FIG. 6 illustrates a signaling diagram of one example 600 of authorizing an asset transferor in accordance with an embodiment of the present description.
As shown in FIG. 6, at 610, the asset transferor may send a first data request to the blockchain server.
At 620, the blockchain server forwards the first data request to the asset transferor in response to the first data request sent by the asset transferor.
At 630, at the asset transferor, upon receiving the first data request, first authorization information may be generated to authorize the asset transferor based on the first identity information and the first data information carried in the first data request.
The first authorization information may include a signature of the asset transferor that is used to prove that the first authorization information originated from the asset transferor. In addition, the first authorization information may further include an authorization term, authorized party information, and the like.
In one example, the asset transferor may verify whether the first identity information and the first data information are consistent with the agreed content of the transfer transaction before generating the first authorization information, and if so, may generate the first authorization information; if not, no authorization is given.
In one example, the asset transferor can encrypt the asset data before sending the asset data to the blockchain server. Thus, the bad asset data linked up by the blockchain server is encrypted data. In this example, the first authorization information generated by the asset transferor includes a decryption key for decrypting the encrypted bad asset data.
In this example, the first authorization information carries the decryption key, so that only the authorized asset transferee can decrypt the encrypted data, and the authorized asset transferee can decrypt the encrypted data with the decryption key after acquiring the encrypted data from the first blockchain. The security of the bad asset data is further enhanced through the encryption process, and the bad asset data is prevented from being viewed by an unauthorized party.
At 640, the asset transferor sends the generated first authorization information to the blockchain server.
At 650, the blockchain server forwards the first authorization information to the asset transferee in response to receiving the first authorization information.
At 660, the asset transferor receives the first authorization information indicating that the asset transferor is authorized for the bad asset data.
Returning to FIG. 3, at 360, at the asset transferor, the bad asset data may be obtained from the first blockchain according to the authorization.
According to the technical scheme provided by the embodiment of the specification, the bad asset data is linked up, and the safety and the credibility of the bad asset data are ensured. In addition, the asset transferee can acquire the bad asset data from the first block chain in an authorization mode, and the safety of the bad asset data circulation is ensured.
In embodiments of the present description, the asset transferee, after obtaining the asset data, may dispose of each asset. In one manner of disposition, the asset transferee may delegate the third party's asset disposition authority to dispose. When the asset is disposed of by the asset disposal facility, the asset disposal facility needs to acquire the asset data of the asset to be disposed of.
In one example, the asset handling mechanism may send a second data request to the blockchain server to request authorization for data of the asset to be handled. The second data request may include second identity information of the asset handling mechanism and requested second data information, the second data information being related information to the pending asset data requested by the asset handling mechanism, the second data information may be used to characterize the pending asset data requested by the asset handling mechanism, the pending asset data being necessary data required by the asset handling mechanism to handle the bad assets, such as owed parties, debtors, amounts, interest rates, etc.
The blockchain server, in response to the second data request, may authorize the to-be-disposed asset data in the undesirable asset data to an asset disposition authority such that the asset disposition authority may perform undesirable asset disposition in accordance with the to-be-disposed asset data. The asset data to be disposed of may be partial data in the bad asset data, and for each bad asset, the asset data to be disposed of corresponding to the bad asset is partial data in the bad asset data corresponding to the bad asset, and is also necessary data required for disposing of the bad asset.
In one manner of authorization, the asset handling mechanism may send a second data request to the blockchain server. The blockchain server forwards the second data request to the asset transferor and the asset transferee in response to the second data request.
And generating second authorization information according to the second identity information and the second data information carried in the second data request at the asset transferor so as to authorize the asset handling mechanism. The second authorization information may then be sent to the blockchain server. The second authorization information may carry information such as signature information, authorization terms, authorization objects, and the like of the asset transferor.
And generating third authorization information according to the second identity information and the second data information carried in the second data request at the asset transferee so as to authorize the asset handling mechanism. The third authorization information may then be sent to the blockchain server. The third authorization information may carry information such as signature information, authorization terms, authorization objects, and the like of the asset transferee.
At the blockchain server, the second authorization information and the third authorization information may be received and forwarded to the asset handling mechanism. The asset disposition mechanism receives the second authorization information and the third authorization information, namely, the asset disposition mechanism obtains authorization, so that the asset disposition mechanism can obtain the asset data to be disposed from the first block chain according to the second authorization information and the third authorization information, and perform the bad asset disposition according to the asset data to be disposed.
In another manner of authorization, a second intelligent contract is configured on the first blockchain, the second intelligent contract being configured to perform an operation of verifying the second data request. The second smart contract may authenticate the request subject and the data object of the second data request. The data objects that different asset handling mechanisms that are the subject of the request allow access may be different.
The second intelligent contract may be configured with a verification policy, where the verification policy may include a white list, where the white list includes a list of request subjects allowed to access and a list of data objects each of which is allowed to access, and in the white list, the list of request subjects may be set corresponding to the list of data objects, and each request subject is associated with a data object which the request subject is allowed to access. The verification policy in the second intelligent contract may be configured by the asset transferor and the asset transferee such that the whitelist in the verification policy is a list verified via the asset transferor and the asset transferee.
In this authorization manner, the blockchain server may invoke a second smart contract to verify the second identity information and the second data information in the second data request in response to the second data request. Upon verification, the asset disposition authority may be authorized to cause the asset disposition authority to acquire the asset data to be disposed for bad asset disposition in accordance with the asset data to be disposed.
By setting an authorization mechanism for the asset handling mechanism, only the specified asset handling mechanism is allowed to check the specified bad asset data, and other unauthorized asset handling mechanisms cannot inquire the bad asset data, so that the safety of the bad asset data is improved, and the bad asset data is prevented from being leaked.
Fig. 7 illustrates a flow chart of one example of a method 700 for transferring bad asset data based on blockchain in accordance with an embodiment of the present description.
The method shown in fig. 7 may be performed by a blockchain server, which may be one of the servers used to construct a blockchain network.
As shown in fig. 7, at 710, the bad asset data is uplinked in response to receiving the bad asset data corresponding to the bad asset from the asset transferor of the bad asset.
At 720, after the asset transferor and the asset transferee agree to a transfer transaction for the undesirable asset, the asset transferee is authorized to obtain the undesirable asset data in response to a first data request sent by the asset transferee, wherein the first data request includes first identity information of the asset transferee and the requested first data information.
In one example, the first data request may be forwarded to the asset transferor in response to the first data request sent by the asset transferor, so that the asset transferor generates first authorization information according to the first identity information and the first data information carried in the first data request, authorizes the asset transferor, and sends the first authorization information to the blockchain server; the first authorization information may be forwarded to the asset transferor in response to receiving the first authorization information, such that the asset transferor obtains the bad asset data from the first blockchain in accordance with the first authorization information.
In one example, a first intelligent contract may be invoked to verify first identity information and first data information in a first data request in response to the first data request sent by an asset transferor; and authorizing the asset transferee when the verification passes so that the asset transferee can obtain the bad asset data.
In one example, the undesirable assets may include a plurality of undesirable assets. The method may further comprise: predicting the repayment rate of each bad asset according to the bad asset data corresponding to the bad assets; and sequencing the plurality of bad assets according to the estimated repayment rate to obtain a bad asset sequence, so that the asset transferee can dispose the plurality of bad assets according to the bad asset sequence.
In one example, the method may further comprise: and in response to a second data request sent by the asset handling mechanism delegated by the asset transferor, authorizing the to-be-handled asset data in the undesirable asset data to the asset handling mechanism so as to enable the asset handling mechanism to handle the undesirable asset according to the to-be-handled asset data, wherein the second data request comprises second identity information of the asset handling mechanism and the requested second data information for characterizing the to-be-handled asset data.
Fig. 8 is a flowchart illustrating an example of a device for transferring asset data that is bad based on a blockchain (hereinafter referred to as an asset data transfer device 800) according to an embodiment of the present specification.
The asset data transfer device 800 may be applied to a blockchain server, which may be one of servers for constructing a blockchain network.
As shown in fig. 8, the asset data transfer device 800 includes an uplink unit 810 and an authorization unit 820.
A uplink unit 810 configured to uplink the bad asset data in response to receiving the bad asset data corresponding to the bad asset from the asset transferor of the bad asset.
An authorizing unit 820 configured to, after the asset transferor and the asset transferee agree on a transfer transaction for the undesirable asset, authorize the asset transferee in response to a first data request sent by the asset transferee to make the asset transferee acquire the undesirable asset data, wherein the first data request includes first identity information of the asset transferee and the requested first data information.
In one example, the authorization unit 820 may be further configured to: responding to a first data request sent by an asset transferee, forwarding the first data request to the asset transferor so that the asset transferor generates first authorization information according to first identity information and first data information carried in the first data request to authorize the asset transferee, and sending the first authorization information to a block chain server; and responding to the received first authorization information, forwarding the first authorization information to the asset transferee so that the asset transferee acquires the bad asset data from the first block chain according to the first authorization information.
In one example, the authorization unit 820 may be further configured to: responding to a first data request sent by an asset transferee, and calling a first intelligent contract to verify first identity information and first data information in the first data request; and authorizing the asset transferee when the verification passes so that the asset transferee can obtain the bad asset data.
In one example, the undesirable assets may include a plurality of undesirable assets. The asset data transfer device 800 may further include: a repayment rate estimation unit and an asset sequencing unit.
The payment rate estimation unit may be configured to: and predicting the repayment rate of each bad asset according to the bad asset data corresponding to the plurality of bad assets. The asset ranking unit may be configured to: and sequencing the plurality of undesirable assets according to the estimated repayment rate to obtain an undesirable asset sequence, so that the asset transferee can dispose of the plurality of undesirable assets according to the undesirable asset sequence.
In one example, the authorization unit 820 may be further configured to: and in response to a second data request sent by the asset handling mechanism delegated by the asset transferor, authorizing the to-be-handled asset data in the undesirable asset data to the asset handling mechanism so as to enable the asset handling mechanism to handle the undesirable asset according to the to-be-handled asset data, wherein the second data request comprises second identity information of the asset handling mechanism and the requested second data information for characterizing the to-be-handled asset data.
Embodiments of a method and apparatus for transferring bad asset data based on blockchains according to embodiments of the present disclosure are described above with reference to fig. 1 through 8.
The device for transferring the bad asset data based on the blockchain in the embodiment of the present specification can be implemented by hardware, software or a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the storage into the memory for operation through the processor of the device where the software implementation is located as a logical means. In an embodiment of the present specification, the device for transferring the bad asset data based on the block chain may be implemented by an electronic device, for example.
Fig. 9 illustrates a block diagram of an electronic device 900 for implementing an undesirable asset data transfer method in accordance with an embodiment of the present specification.
As shown in fig. 9, the electronic device 900 may include at least one processor 910, a storage (e.g., non-volatile storage) 920, a memory 930, and a communication interface 940, and the at least one processor 910, the storage 920, the memory 930, and the communication interface 940 are connected together via a bus 950. The at least one processor 910 executes at least one computer-readable instruction (i.e., the elements described above as being implemented in software) stored or encoded in memory.
In one embodiment, computer-executable instructions are stored in the memory that, when executed, cause the at least one processor 910 to: responsive to receiving the bad asset data corresponding to the bad asset from the asset transferor of the bad asset, uplink the bad asset data; and after the asset transferor and the asset transferee achieve the transfer transaction consensus aiming at the undesirable asset, responding to a first data request sent by the asset transferee, and authorizing the asset transferee so that the asset transferee acquires the undesirable asset data, wherein the first data request comprises first identity information of the asset transferee and the requested first data information.
It should be appreciated that the computer-executable instructions stored in the memory, when executed, cause the at least one processor 610 to perform the various operations and functions described above in connection with fig. 1-8 in the various embodiments of the present description.
According to one embodiment, a program product, such as a machine-readable medium, is provided. A machine-readable medium may have instructions (i.e., elements described above as being implemented in software) that, when executed by a machine, cause the machine to perform various operations and functions described above in connection with fig. 1-8 in the various embodiments of the present specification.
Specifically, a system or apparatus may be provided which is provided with a readable storage medium on which software program code implementing the functions of any of the above embodiments is stored, and causes a computer or processor of the system or apparatus to read out and execute instructions stored in the readable storage medium.
In this case, the program code itself read from the readable medium can realize the functions of any of the above-described embodiments, and thus the machine-readable code and the readable storage medium storing the machine-readable code form part of the present invention.
Computer program code required for the operation of various portions of the present specification may be written in any one or more programming languages, including an object oriented programming language such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C + +, C #, VB, NET, Python, and the like, a conventional programming language such as C, Visual Basic 2003, Perl, COBOL2002, PHP, and ABAP, a dynamic programming language such as Python, Ruby, and Groovy, or other programming languages. The program code may execute on the user's computer, or on the user's computer as a stand-alone software package, or in part on the user's computer and in part on a remote computer, or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any network format, such as a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet), or in a cloud computing environment, or as a service, such as a software as a service (SaaS).
Examples of the readable storage medium include floppy disks, hard disks, magneto-optical disks, optical disks (e.g., CD-ROMs, CD-R, CD-RWs, DVD-ROMs, DVD-RAMs, DVD-RWs), magnetic tapes, nonvolatile memory cards, and ROMs. Alternatively, the program code may be downloaded from a server computer or from the cloud via a communications network.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
Not all steps and elements in the above flows and system structure diagrams are necessary, and some steps or elements may be omitted according to actual needs. The execution order of the steps is not fixed, and can be determined as required. The apparatus structures described in the foregoing embodiments may be physical structures or logical structures, that is, some units may be implemented by the same physical entity, or some units may be implemented by multiple physical entities separately, or some units may be implemented by some components in multiple independent devices together.
The term "exemplary" used throughout this specification means "serving as an example, instance, or illustration," and does not mean "preferred" or "advantageous" over other embodiments. The detailed description includes specific details for the purpose of providing an understanding of the described technology. However, the techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described embodiments.
Although the embodiments of the present disclosure have been described in detail with reference to the accompanying drawings, the embodiments of the present disclosure are not limited to the specific details of the embodiments, and various simple modifications may be made to the technical solutions of the embodiments of the present disclosure within the technical spirit of the embodiments of the present disclosure, and all of them fall within the scope of the embodiments of the present disclosure.
The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the description is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (22)

1. A blockchain-based method for transferring undesirable asset data, comprising:
at the location of the asset transferor,
sending the bad asset data corresponding to the bad assets to a blockchain server, wherein the blockchain server is one of servers used for constructing a blockchain network;
at the location of the blockchain server, a blockchain server,
uplink the bad asset data to a first blockchain; and
and after the asset transferor and the asset transferee reach a transfer transaction consensus aiming at the undesirable asset, responding to a first data request sent by the asset transferee, and authorizing the asset transferee so that the asset transferee acquires the undesirable asset data, wherein the first data request comprises first identity information of the asset transferee and the requested first data information.
2. The method of claim 1 wherein authorizing the asset transferor to obtain the undesirable asset data in response to the first data request sent by the asset transferor comprises:
at the blockchain server, forwarding a first data request sent by the asset transferor to the asset transferor in response to the first data request;
generating first authorization information at the asset transferor according to the first identity information and the first data information carried in the first data request so as to authorize the asset transferee, and sending the first authorization information to the block chain server;
at the blockchain server, in response to receiving the first authorization information, forwarding the first authorization information to the asset transferee; and
at the asset transferee, obtaining the undesirable asset data from the first blockchain in accordance with the first authorization information.
3. The method of claim 2, wherein prior to transmitting the bad asset data to the blockchain server, the method further comprises:
encrypting the bad asset data; wherein the first authorization information includes a corresponding decryption key.
4. The method of claim 1 wherein authorizing the asset transferor to obtain the undesirable asset data in response to the first data request sent by the asset transferor comprises:
responding to a first data request sent by the asset transferee, and calling a first intelligent contract to verify the first identity information and the first data information in the first data request; and
and when the verification is passed, authorizing the asset transferee so that the asset transferee can obtain the bad asset data.
5. The method of claim 1, wherein transmitting the bad asset data corresponding to the bad asset to a blockchain server comprises:
screening the bad asset data generated by the bad assets according to the specified asset data type; and
and sending the screened bad asset data to the block chain server.
6. The method of claim 5, wherein the specifying asset data types comprises: creditor, debtor, time of occurrence of debt, amount, loan term, and interest rate.
7. The method of claim 1, further comprising:
at the asset transferor, during execution of the financial asset, chaining the correspondingly generated asset data; and
and when the financial assets become the bad assets, determining the asset data as bad asset data corresponding to the bad assets.
8. The method of claim 7, wherein,
during the execution of the financial asset, the linking of the correspondingly generated asset data comprises:
during the execution process of the financial assets, the corresponding generated asset data is linked to a second block chain through a local block chain all-in-one machine; and
when the financial asset becomes the poor asset, determining the asset data as the bad asset data corresponding to the bad asset comprises:
when the financial assets become the bad assets, transferring the asset data recorded on the second block chain to the first block chain as the bad asset data through a chain crossing technology.
9. The method of claim 1, further comprising:
at the blockchain server, performing summary information extraction on the bad asset data; and
uplink the extracted summary information to the first blockchain, wherein the summary information is stored in association with the bad asset data on the first blockchain.
10. The method of claim 1, wherein the undesirable assets include a plurality of undesirable assets, the method further comprising:
at the block chain server, predicting the repayment rate of each bad asset according to the bad asset data corresponding to the bad assets; and
and sequencing the plurality of bad assets according to the estimated repayment rate to obtain a bad asset sequence, so that the asset transferee can dispose the plurality of bad assets according to the bad asset sequence.
11. The method of claim 1, further comprising:
at the blockchain server, in response to a second data request sent by an asset handling mechanism delegated by the asset transferor, authorizing to-be-handled asset data in the undesirable asset data to the asset handling mechanism to cause the asset handling mechanism to perform undesirable asset handling according to the to-be-handled asset data, wherein the second data request comprises second identity information of the asset handling mechanism and the requested second data information for characterizing the to-be-handled asset data.
12. The method of claim 11 wherein authorizing the to-be-disposed asset data in the undesirable asset data to the asset disposal mechanism in response to a second data request sent by an asset disposal mechanism delegated by the asset transferor to cause the asset disposal mechanism to dispose of undesirable assets in accordance with the to-be-disposed asset data comprises:
at the blockchain server, in response to a second data request sent by the asset handling mechanism, forwarding the second data request to the asset transferor and the asset transferee;
generating, at the asset transferor, second authorization information according to the second identity information and the second data information carried in the second data request to authorize the asset handling mechanism, and sending the second authorization information to the blockchain server;
generating, at the asset transferor, third authorization information from the second identity information and the second data information carried in the second data request to authorize the asset handling mechanism, and sending the third authorization information to the blockchain server;
forwarding, at the blockchain server, the second authorization information and the third authorization information to the asset handling mechanism; and
at the asset disposition authority, obtaining the asset data to be disposed from the first blockchain in accordance with the second authorization information and the third authorization information for undesirable asset disposition in accordance with the asset data to be disposed.
13. The method of claim 11 wherein authorizing the to-be-disposed asset data in the undesirable asset data to the asset disposal mechanism in response to a second data request sent by an asset disposal mechanism delegated by the asset transferor to cause the asset disposal mechanism to dispose of undesirable assets in accordance with the to-be-disposed asset data comprises:
in response to a second data request sent by the asset handling mechanism, invoking a second smart contract to verify the second identity information and the second data information in the second data request; and
upon verification, authorizing the asset disposition authority to cause the asset disposition authority to acquire the to-be-disposed asset data for undesirable asset disposition in accordance with the to-be-disposed asset data.
14. A blockchain-based method for transferring bad asset data is performed by a blockchain server, the blockchain server is one of servers used for constructing a blockchain network,
the method comprises the following steps:
responsive to receiving, from an asset transferor of a bad asset, bad asset data corresponding to the bad asset, uplink the bad asset data; and
and after the asset transferor and the asset transferee reach a transfer transaction consensus aiming at the undesirable asset, responding to a first data request sent by the asset transferee, and authorizing the asset transferee so that the asset transferee acquires the undesirable asset data, wherein the first data request comprises first identity information of the asset transferee and the requested first data information.
15. The method of claim 14 wherein authorizing the asset transferor to obtain the undesirable asset data in response to the first data request sent by the asset transferor comprises:
responding to a first data request sent by the asset transferee, forwarding the first data request to the asset transferor so that the asset transferor generates first authorization information according to the first identity information and the first data information carried in the first data request to authorize the asset transferee, and sending the first authorization information to the block chain server;
and responding to the received first authorization information, forwarding the first authorization information to the asset transferee so that the asset transferee acquires the bad asset data from the first block chain according to the first authorization information.
16. The method of claim 14 wherein authorizing the asset transferor to obtain the undesirable asset data in response to the first data request sent by the asset transferor comprises:
responding to a first data request sent by the asset transferee, and calling a first intelligent contract to verify the first identity information and the first data information in the first data request; and
and when the verification is passed, authorizing the asset transferee so that the asset transferee can obtain the bad asset data.
17. The method of claim 14, wherein the undesirable assets include a plurality of undesirable assets, the method further comprising:
predicting the repayment rate of each bad asset according to the bad asset data corresponding to the bad assets; and
and sequencing the plurality of bad assets according to the estimated repayment rate to obtain a bad asset sequence, so that the asset transferee can dispose the plurality of bad assets according to the bad asset sequence.
18. The method of claim 14, further comprising:
authorizing, in response to a second data request sent by an asset disposition authority delegated by the asset transferor, pending asset data in the undesirable asset data to the asset disposition authority to cause the asset disposition authority to perform undesirable asset disposition in accordance with the pending asset data, wherein the second data request includes second identity information of the asset disposition authority and the requested second data information characterizing the pending asset data.
19. A device for transferring bad asset data based on a block chain is applied to a block chain server, the block chain server is one of servers used for building a block chain network,
the device comprises:
the uplink unit is used for responding to the bad asset data corresponding to the bad asset received from the asset transferor of the bad asset and uplink the bad asset data; and
and the authorization unit responds to a first data request sent by the asset transferee and authorizes the asset transferee so that the asset transferee acquires the undesirable asset data, wherein the first data request comprises first identity information of the asset transferee and the requested first data information.
20. An electronic device, comprising: at least one processor, a memory coupled with the at least one processor, and a computer program stored on the memory, the at least one processor executing the computer program to implement the method of any of claims 14-18.
21. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 14-18.
22. A computer program product comprising a computer program which, when executed by a processor, implements the method of any one of claims 14-18.
CN202210759137.XA 2022-06-29 2022-06-29 Block chain based method and device for transferring poor asset data Pending CN115099800A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210759137.XA CN115099800A (en) 2022-06-29 2022-06-29 Block chain based method and device for transferring poor asset data

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210759137.XA CN115099800A (en) 2022-06-29 2022-06-29 Block chain based method and device for transferring poor asset data

Publications (1)

Publication Number Publication Date
CN115099800A true CN115099800A (en) 2022-09-23

Family

ID=83295213

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210759137.XA Pending CN115099800A (en) 2022-06-29 2022-06-29 Block chain based method and device for transferring poor asset data

Country Status (1)

Country Link
CN (1) CN115099800A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116228437A (en) * 2023-05-10 2023-06-06 布比（北京）网络技术有限公司 Asset transfer method, device, electronic equipment and storage medium

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116228437A (en) * 2023-05-10 2023-06-06 布比（北京）网络技术有限公司 Asset transfer method, device, electronic equipment and storage medium

Similar Documents

Publication Publication Date Title
US11281800B2 (en) Systems and methods for providing identity verification services
WO2020098845A2 (en) Data authorization based on decentralized identifiers
US20180075527A1 (en) Credit score platform
US11676117B2 (en) Blockchain compliance verification network
Guerar et al. A fraud-resilient blockchain-based solution for invoice financing
CN111989707B (en) Managing user rights for blockchain-based customs clearance services
US11188907B1 (en) ACH authorization validation using public blockchains
CN111418184A (en) Credible insurance letter based on block chain
US11599858B2 (en) Blockchain settlement network
US20220172198A1 (en) Real-time blockchain settlement network
US20220329436A1 (en) Token-based identity validation via blockchain
US20220311611A1 (en) Reputation profile propagation on blockchain networks
CN111417945A (en) Credible insurance letter based on block chain
CN115456773A (en) Payment control method, device, equipment and medium based on block chain
CN111433799A (en) Credible insurance letter based on block chain
CN111433798A (en) Credible insurance letter based on block chain
Dash et al. Artificial intelligence models for blockchain-based intelligent networks systems: Concepts, methodologies, tools, and applications
CN112074861A (en) Block chain based messaging service for time sensitive events
CN115099800A (en) Block chain based method and device for transferring poor asset data
US20200252408A1 (en) Graduated accounts using assertions
US20210056620A1 (en) Multi-lender credit history record blockchain
CN112074862A (en) Storage management based on message feedback
US20230092436A1 (en) Framework for demaraction of digital assets
CN114066451A (en) Method and system for managing fund transaction and electronic equipment
US20210233104A1 (en) Product exploration-based promotion

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination