Data asset management method and device, electronic equipment and readable storage medium

Abstract

The invention provides a data asset processing method and device, electronic equipment and a readable storage medium, and the method is applied to a distributed transaction platform. The distributed transaction platform comprises a transaction node corresponding to each data asset exchange; the method comprises the steps of receiving a login request of a target user, and performing identity authentication on the target user based on the login request; and after the target user logs in successfully, submitting a data asset transaction request of the target user to a target data asset transaction node corresponding to a target data asset transaction based on the target data asset transaction selected by the target user from the plurality of data asset transactions, and the target data asset transaction node matches a target transaction object for the target user based on the data asset transaction request of the target user. Through the method, the efficiency of data asset transaction can be improved.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and in particular to a method, apparatus, electronic device, and readable storage medium for managing data assets. Background Technology

[0002] Data assets generally refer to data resources, recorded physically or electronically, that are legally owned or controlled by an enterprise or organization and can bring future economic benefits to the enterprise. Currently, when conducting data asset transactions, for example, if user A wants to sell their own data assets, user A can submit the data assets to one or more data asset exchanges, where other users can purchase them. Alternatively, if user B wants to purchase other users' data assets, user B needs to submit their purchase request to one or more data asset exchanges, where they can then purchase the data assets they need.

[0003] Currently, when user A submits their data assets to various data asset exchanges, user A needs to verify their identity on each exchange separately. Similarly, when user B submits their purchase request to various data asset exchanges, user B also needs to verify their identity on each exchange separately. Because users need to undergo multiple identity verifications, the data asset transaction process becomes redundant and cumbersome, potentially impacting transaction efficiency. Summary of the Invention

[0004] In view of this, the purpose of this application is to provide a data asset management method, apparatus, electronic device and readable storage medium, so that when a user conducts a data asset transaction, regardless of which data asset exchanges the transaction takes place, the user only needs to perform identity authentication once. This will improve the convenience of users when conducting data asset transactions, thereby improving the efficiency of data asset transactions.

[0005] In a first aspect, embodiments of this application provide a method for managing data assets, the method being applied to a distributed trading platform; the distributed trading platform includes trading nodes corresponding to each data asset exchange; the method includes:

[0006] Receive a login request from a target user, and perform identity authentication on the target user based on the login request;

[0007] Once the target user successfully logs in, based on the target data asset exchange selected by the target user from multiple data asset exchanges, the target user's data asset transaction request is submitted to the target data asset transaction node corresponding to the target data asset exchange, so that the target data asset transaction node matches the target user with a target transaction object based on the target user's data asset transaction request.

[0008] In conjunction with the first aspect, this application provides a first possible implementation of the first aspect, wherein, before receiving the login request of the target user and authenticating the target user based on the login request, the method further includes:

[0009] Receive a registration request sent by the target user's client; the registration request includes the target user's account ID; the registration request is generated based on the registration information entered by the target user on the registration page of the distributed trading platform displayed on the client.

[0010] Based on the registration request, a verification instruction message containing a verification code is sent to the target user's client; the verification instruction message is used to instruct the target user to input the verification code into the verification code input area in the registration page of the distributed trading platform within a specified time.

[0011] If feedback information indicating that the verification code input is complete is received from the user terminal within the specified time, it is determined whether the verification code entered by the target user is correct.

[0012] If the verification code entered by the target user is correct, a private key corresponding to the account ID is generated, the account ID and the private key are stored, and the private key is sent to the user's terminal, thus completing the registration.

[0013] In conjunction with the first possible implementation of the first aspect, this application provides a second possible implementation of the first aspect, wherein receiving a login request from a target user and authenticating the target user based on the login request includes:

[0014] Receive login requests containing account ID and private key sent by the target user's client;

[0015] Determine whether the account ID and private key contained in the login request are stored in the distributed trading platform;

[0016] If the account ID and private key contained in the login request are stored in the distributed trading platform, it indicates that the target user has successfully logged in.

[0017] In conjunction with the first aspect, this application provides a third possible implementation of the first aspect, wherein, when the target user is a seller, the data asset transaction request includes the data asset content, price range, and transaction target range of the data asset the seller intends to sell; and when the target user is a buyer, the data asset transaction request includes the data asset content, price range, and transaction target range of the data asset the buyer intends to purchase.

[0018] In conjunction with the third possible implementation of the first aspect, this application provides a fourth possible implementation of the first aspect, wherein, to enable the target data asset transaction node to match a target transaction object for the target user based on the target user's data asset transaction request, the following is provided:

[0019] The target data asset transaction node matches the target user's data asset transaction request with data asset transaction requests submitted by other users according to the importance of the data asset content, price range, and transaction object range contained in the data asset transaction request, thereby obtaining the data asset transaction matching degree between the target user and each of the other users; wherein, when the target user is a seller, the other users are buyers; and when the target user is a buyer, the other users are sellers; the importance of the data asset content, price range, and transaction object range contained in the data asset transaction request, from largest to smallest, is: data asset content, transaction object range, price range;

[0020] Based on the matching degree of data asset transactions between the target user and each of the other users, a target transaction object is matched for the target user from among the other users.

[0021] In conjunction with the fourth possible implementation of the first aspect, this application provides a fifth possible implementation of the first aspect, wherein the step of matching a target transaction object for the target user from the other users based on the data asset transaction matching degree between the target user and each of the other users includes:

[0022] Based on the order of data asset transaction matching degree from high to low for each of the other users, a preset number of other users are selected as candidate transaction objects.

[0023] The object information of the candidate transaction objects is sent to the user terminal of the target user, so that the target user can select the target transaction object from the candidate transaction objects;

[0024] Receive the object information of the selected target transaction object sent by the target user's client.

[0025] In conjunction with the first aspect, this application provides a sixth possible implementation of the first aspect, wherein, after the target data asset transaction node matches a target transaction object for the target user based on the target user's data asset transaction request, the method further includes:

[0026] Receive transaction condition information sent by the target user's client and receive transaction condition information sent by the target transaction object's client;

[0027] When the transaction condition information of the target user and the target transaction object are the same, the transaction condition information is reviewed to determine whether the transaction condition information meets the preset requirements;

[0028] When the transaction conditions information meets the preset requirements, the relevant rights of the data assets are transferred between the target user and the target transaction object based on the transaction conditions information.

[0029] Secondly, embodiments of this application also provide a data asset management device, which is applied to a distributed trading platform; the distributed trading platform includes trading nodes corresponding to each data asset exchange; the device includes:

[0030] The authentication module is used to receive login requests from target users and perform identity authentication on the target users based on the login requests;

[0031] The submission module is used to submit the target user's data asset transaction request to the target data asset transaction node corresponding to the target data asset exchange after the target user successfully logs in, based on the target data asset exchange selected by the target user from multiple data asset exchanges, so that the target data asset transaction node matches the target user with a target transaction object based on the target user's data asset transaction request.

[0032] In conjunction with the second aspect, embodiments of this application provide a first possible implementation of the second aspect, wherein the apparatus further includes:

[0033] A receiving module is used to receive a registration request sent by the target user's client; the registration request includes the target user's account ID; the registration request is generated based on the registration information entered by the target user on the registration page of the distributed trading platform displayed on the client.

[0034] The sending module is used to send verification instruction information containing a verification code to the target user's client based on the registration request; the verification instruction information is used to instruct the target user to input the verification code into the verification code input area in the registration page of the distributed trading platform within a specified time.

[0035] The judgment module is used to determine whether the verification code entered by the target user is correct if it receives feedback information from the user terminal indicating that the verification code input is complete within a specified time.

[0036] The registration module is used to generate a private key corresponding to the account ID if the verification code entered by the target user is correct, store the account ID and the private key, and send the private key to the user terminal to complete the registration.

[0037] In conjunction with the first possible implementation of the second aspect, this application provides a second possible implementation of the second aspect, wherein, when the authentication module receives a login request from a target user and performs identity authentication on the target user based on the login request, it is specifically used for:

[0038] Receive login requests containing account ID and private key sent by the target user's client;

[0039] Determine whether the account ID and private key contained in the login request are stored in the distributed trading platform;

[0040] If the account ID and private key contained in the login request are stored in the distributed trading platform, it indicates that the target user has successfully logged in.

[0041] In conjunction with the second aspect, this application provides a third possible implementation of the second aspect, wherein, when the target user is a seller, the data asset transaction request includes the data asset content, price range, and transaction target range of the data asset the seller intends to sell; and when the target user is a buyer, the data asset transaction request includes the data asset content, price range, and transaction target range of the data asset the buyer intends to purchase.

[0042] In conjunction with the third possible implementation of the second aspect, this application provides a fourth possible implementation of the second aspect, wherein the submission module, when used to enable the target data asset transaction node to match a target transaction object for the target user based on the target user's data asset transaction request, is specifically used for:

[0043] The target data asset transaction node matches the target user's data asset transaction request with data asset transaction requests submitted by other users according to the importance of the data asset content, price range, and transaction object range contained in the data asset transaction request, thereby obtaining the data asset transaction matching degree between the target user and each of the other users; wherein, when the target user is a seller, the other users are buyers; and when the target user is a buyer, the other users are sellers; the importance of the data asset content, price range, and transaction object range contained in the data asset transaction request, from largest to smallest, is: data asset content, transaction object range, price range;

[0044] Based on the matching degree of data asset transactions between the target user and each of the other users, a target transaction object is matched for the target user from among the other users.

[0045] In conjunction with the fourth possible implementation of the second aspect, this application provides a fifth possible implementation of the second aspect, wherein the submission module, when used to match a target transaction object for the target user from among the other users based on the data asset transaction matching degree between the target user and each of the other users, is specifically used for:

[0046] Based on the order of data asset transaction matching degree from high to low for each of the other users, a preset number of other users are selected as candidate transaction objects.

[0047] The object information of the candidate transaction objects is sent to the user terminal of the target user, so that the target user can select the target transaction object from the candidate transaction objects;

[0048] Receive the object information of the selected target transaction object sent by the target user's client.

[0049] In conjunction with the second aspect, this application provides a sixth possible implementation of the second aspect, wherein, after the target data asset transaction node is used to match a target transaction object for the target user based on the target user's data asset transaction request, it is further used to:

[0050] Receive transaction condition information sent by the target user's client and receive transaction condition information sent by the target transaction object's client;

[0051] When the transaction condition information of the target user and the target transaction object are the same, the transaction condition information is reviewed to determine whether the transaction condition information meets the preset requirements;

[0052] When the transaction conditions information meets the preset requirements, the relevant rights of the data assets are transferred between the target user and the target transaction object based on the transaction conditions information.

[0053] Thirdly, embodiments of this application also provide an electronic device, including: a processor, a memory, and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the memory via the bus, and when the machine-readable instructions are executed by the processor, the steps in any of the possible implementations of the first aspect described above are performed.

[0054] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps in any of the possible implementations of the first aspect described above.

[0055] This application provides a data asset processing method, apparatus, electronic device, and readable storage medium. Since the distributed trading platform contains trading nodes corresponding to each data asset exchange, when a target user conducts a data asset transaction, regardless of whether the target user wants to submit a data asset transaction request to one or multiple target data asset exchanges, the target user only needs to perform identity authentication once on the distributed trading platform to submit their data asset transaction request to each target data asset exchange. This eliminates the need for multiple identity authentications, thereby improving the convenience and efficiency of data asset transactions.

[0056] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0057] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0058] Figure 1 A flowchart illustrating a data asset management method provided in an embodiment of this application is shown;

[0059] Figure 2 This illustration shows the interaction between a distributed trading platform provided in this application, the user terminal of a seller's user, and the user terminal of a buyer's user;

[0060] Figure 3 A schematic diagram of the structure of a data asset management device provided in an embodiment of this application is shown;

[0061] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of this application is shown. Detailed Implementation

[0062] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0063] Considering that when User A submits their data assets to various data asset exchanges, User A needs to perform identity authentication on each exchange separately. Similarly, when User B submits their purchase request to various data asset exchanges, User B also needs to perform identity authentication on each exchange separately. Because users need to perform multiple identity authentications, the data asset transaction process becomes redundant and cumbersome, easily affecting the efficiency of data asset transactions. Therefore, embodiments of this application provide a data asset management method, apparatus, electronic device, and readable storage medium, so that when a user conducts a data asset transaction, regardless of which data asset exchanges the transaction takes place, the user only needs to perform identity authentication once. This improves the convenience of data asset transactions and thus increases the efficiency of data asset transactions. The following is a description through embodiments.

[0064] To facilitate understanding of this embodiment, a data asset management method disclosed in this application will first be described in detail. This method is applied to a distributed trading platform; the distributed trading platform includes trading nodes corresponding to each data asset exchange.

[0065] In this embodiment, each trading node in the distributed trading platform refers to a node with data processing capabilities. A data asset exchange refers to a venue or entity used for trading data assets. Each data asset exchange corresponds to one trading node, and one trading node can correspond to one or more data asset exchanges. For example, for a large data asset exchange, one trading node corresponds to one large data asset exchange. For a small data asset exchange, one trading node can correspond to multiple small data asset exchanges.

[0066] These include data assets such as the right to use and own databases, as well as the right to use and own training data. Different data asset exchanges can be located in different cities; for example, each city can have its own data asset exchange.

[0067] like Figure 1 As shown, the method includes the following steps S101-S102:

[0068] S101: Receive the login request from the target user and perform identity authentication on the target user based on the login request.

[0069] S102: After the target user successfully logs in, based on the target data asset exchange selected by the target user from multiple data asset exchanges, the target user's data asset transaction request is submitted to the target data asset transaction node corresponding to the target data asset exchange, so that the target data asset transaction node matches the target user with a target transaction object based on the target user's data asset transaction request.

[0070] In step S101, the target user's client displays the login page of the distributed trading platform. The target user enters their account ID and private key on the login page, thereby generating a login request on the client. The system receives the login request from the target user's client and performs identity authentication based on the login request.

[0071] In one possible implementation, before performing step S101, account registration can also be performed through the following steps S1001-S1004:

[0072] S1001: Receive a registration request sent by the target user's client; the registration request includes the target user's account ID; the registration request is generated based on the registration information entered by the target user on the registration page of the distributed trading platform displayed on the client.

[0073] In this embodiment, the target user's client displays a registration page for the distributed trading platform. The target user enters registration information, including their account ID, on this page, causing the client to generate a registration request containing the target user's account ID. The target user's account ID can be their name, ID card number, mobile phone number, or email address.

[0074] S1002: Based on the registration request, send verification instruction information containing a verification code to the target user's client; the verification instruction information is used to instruct the target user to enter the verification code into the verification code input area on the registration page of the distributed trading platform within a specified time.

[0075] In this embodiment, after receiving a registration request, the distributed trading platform sends a verification instruction containing a verification code to the target user's client based on the registration request. After receiving the verification instruction, the target user needs to enter the verification code into the verification code input area on the registration page of the distributed trading platform within a specified time.

[0076] S1003: If feedback information indicating that the verification code input is complete is received from the user terminal within the specified time, then determine whether the verification code entered by the target user is correct.

[0077] S1004: If the verification code entered by the target user is correct, generate the private key corresponding to the account ID, store the account ID and the private key, and send the private key to the user terminal. Registration is complete.

[0078] In this embodiment, after generating the private key corresponding to the account ID, the distributed transaction platform stores the account ID and the private key, and then sends the account ID and the private key to the user terminal to complete the account registration.

[0079] In one possible implementation, when performing step S101, identity authentication can be performed specifically according to the following steps S1011-S1013:

[0080] S1011: Receive a login request containing the account ID and private key sent by the target user's client.

[0081] In this embodiment, the target user's client displays the login page of the distributed trading platform. The target user enters their account ID and private key on the login page, thereby causing the client to generate a login request containing the account ID and private key.

[0082] S1012: Determine whether the account ID and private key contained in the login request are stored in the distributed trading platform.

[0083] In this embodiment, after receiving a login request from the user, it is determined whether the account ID and private key contained in the login request are stored in the distributed trading platform.

[0084] S1013: If the account ID and private key contained in the login request are stored in the distributed trading platform, it indicates that the target user has successfully logged in.

[0085] In this embodiment, if the account ID and private key included in the login request are stored in the distributed trading platform, it indicates that the target user has completed registration, and the target user logs in successfully. If the account ID and private key included in the login request are not stored in the distributed trading platform, it indicates that at least one piece of information in the target user's account ID and private key is entered incorrectly, or that the target user has not completed registration, and the target user logs in unsuccessfully.

[0086] In step S102, successful login of the target user signifies that the target user's identity authentication has been passed. At this point, based on the target data asset exchange selected by the target user from multiple data asset exchanges, the target user's data asset transaction request is submitted to the target data asset transaction node corresponding to the target data asset exchange. There can be one or more target data asset transaction nodes. After receiving the data asset transaction request submitted by the target user, the target data asset transaction node matches the target user with a target transaction object based on the request, thereby facilitating the transaction between the target user and the target transaction object regarding data assets.

[0087] Specifically, such as Figure 2 As shown, the target user in this embodiment can be either a seller or a buyer. Specifically, a seller wants to sell their own data assets, while a buyer wants to purchase data assets from other sellers.

[0088] In one possible implementation, when the target user is a seller, the data asset transaction request includes the data asset content, price range, and transaction target range of the data asset that the seller intends to sell. In this case, the target transaction target is usually a buyer user who falls within the transaction target range.

[0089] When the target user is a buyer, the data asset transaction request includes the data asset content, price range, and scope of counterparties for the data asset the buyer intends to purchase. In this case, the target counterparty is typically a seller who falls within the scope of counterparties.

[0090] In this embodiment, data asset content includes, for example, access permissions and usage periods for database X. The scope of transaction objects refers to the range of objects the target user wants to trade; for example, the target user might want to trade companies related to artificial intelligence. The price range refers to the price the target user wants to trade at. It's worth noting that the price range in this embodiment is actually measured in common currency, not virtual tokens. For example, the price range could be between 10,000 and 20,000 yuan.

[0091] In one possible implementation, when performing step S102 to match the target data asset transaction node with the target transaction object based on the target user's data asset transaction request, the specific steps S1021-S1022 can be performed as follows:

[0092] S1021: The target data asset transaction node matches the target user's data asset transaction request with the data asset transaction requests submitted by other users according to the importance of the data asset content, price range, and transaction object range contained in the data asset transaction request, thereby obtaining the data asset transaction matching degree between the target user and each other user; wherein, when the target user is a seller user, the other users are buyers users; when the target user is a buyer user, the other users are seller users; the importance of the data asset content, price range, and transaction object range contained in the data asset transaction request, from largest to smallest, is: data asset content, transaction object range, price range.

[0093] In this embodiment, when the target user is a seller, the target data asset transaction node matches the seller's data asset transaction request with the data asset content, price range, and transaction object range contained in the data asset transaction request submitted by each buyer, according to the importance of the data asset content, price range, and transaction object range contained in the seller's data asset transaction request, to obtain the data asset transaction matching degree between the seller and each buyer.

[0094] When the target user is a buyer, the target data asset transaction node matches the buyer's data asset transaction request with the data asset content, price range, and transaction object range contained in the buyer's data asset transaction request according to the importance of these factors, thus obtaining the data asset transaction matching degree between the buyer and each seller.

[0095] S1022: Based on the matching degree of data asset transactions between the target user and each other user, match the target transaction object for the target user from the other users.

[0096] In this embodiment, a preset number of other users are selected as candidate transaction objects according to the order of data asset transaction matching degree from high to low for each other user; wherein, the preset number is usually greater than or equal to 2.

[0097] The system sends the object information of candidate transaction objects to the target user's client, enabling the target user to select the target transaction object from among the candidate objects. Specifically, the target user can eliminate competitors from the candidate objects and then select the target transaction object from the remaining candidate objects. The system receives the object information of the selected target transaction object from the target user's client.

[0098] In one possible implementation, after step S102 is completed, the target asset can further conduct a data asset transaction with the target trading partner according to the following steps S1031-S1033:

[0099] S1031: Receive transaction condition information sent by the target user's client and receive transaction condition information sent by the target transaction object's client.

[0100] In this embodiment, after matching a target transaction partner with a target user, the target user and the target transaction partner negotiate and determine transaction conditions. These conditions may include the data asset transaction content and the data asset transaction price. The data asset transaction content could be, for example, the right to use database X.

[0101] S1032: When the transaction condition information of the target user and the target transaction object is the same, the transaction condition information is reviewed to determine whether the transaction condition information meets the preset regulations.

[0102] In this embodiment, after receiving transaction condition information sent by the target user's client and the target transaction object's client, if the transaction condition information of the target user and the target transaction object are the same, the transaction condition information is reviewed to determine whether it complies with preset regulations. The preset regulations refer to whether the transaction condition information is reasonable and legal.

[0103] S1033: When the transaction conditions information meets the preset requirements, the relevant rights of data assets are transferred between the target user and the target transaction object based on the transaction conditions information.

[0104] For example, when the data asset transaction content in the transaction conditions information is the transfer of the right to use database X, if the target user is the seller and the target transaction object is the buyer, then the right to use database X can be transferred to the target transaction object based on the transaction conditions information.

[0105] Based on the same technical concept, embodiments of this application also provide a data asset management device, which is applied to a distributed trading platform; the distributed trading platform includes trading nodes corresponding to each data asset exchange; such as Figure 3 As shown, the device includes:

[0106] Authentication module 301 is used to receive login requests from target users and perform identity authentication on the target users based on the login requests;

[0107] The submission module 302 is used to submit the target user's data asset transaction request to the target data asset transaction node corresponding to the target data asset exchange after the target user successfully logs in, based on the target data asset exchange selected by the target user from multiple data asset exchanges, so that the target data asset transaction node matches the target user with a target transaction object based on the target user's data asset transaction request.

[0108] Optionally, the device further includes:

[0109] A receiving module is used to receive a registration request sent by the target user's client; the registration request includes the target user's account ID; the registration request is generated based on the registration information entered by the target user on the registration page of the distributed trading platform displayed on the client.

[0110] The sending module is used to send verification instruction information containing a verification code to the target user's client based on the registration request; the verification instruction information is used to instruct the target user to input the verification code into the verification code input area in the registration page of the distributed trading platform within a specified time.

[0111] The judgment module is used to determine whether the verification code entered by the target user is correct if it receives feedback information from the user terminal indicating that the verification code input is complete within a specified time.

[0112] The registration module is used to generate a private key corresponding to the account ID if the verification code entered by the target user is correct, store the account ID and the private key, and send the private key to the user terminal to complete the registration.

[0113] Optionally, when the authentication module 301 receives a login request from a target user and performs identity authentication on the target user based on the login request, it is specifically used for:

[0114] Receive login requests containing account ID and private key sent by the target user's client;

[0115] Determine whether the account ID and private key contained in the login request are stored in the distributed trading platform;

[0116] If the account ID and private key contained in the login request are stored in the distributed trading platform, it indicates that the target user has successfully logged in.

[0117] Optionally, when the target user is a seller, the data asset transaction request includes the data asset content, price range, and transaction target range of the data asset the seller intends to sell; when the target user is a buyer, the data asset transaction request includes the data asset content, price range, and transaction target range of the data asset the buyer intends to purchase.

[0118] Optionally, when the submission module 302 is used to enable the target data asset transaction node to match a target transaction object for the target user based on the target user's data asset transaction request, it is specifically used for:

[0119] The target data asset transaction node matches the target user's data asset transaction request with data asset transaction requests submitted by other users according to the importance of the data asset content, price range, and transaction object range contained in the data asset transaction request, thereby obtaining the data asset transaction matching degree between the target user and each of the other users; wherein, when the target user is a seller, the other users are buyers; and when the target user is a buyer, the other users are sellers; the importance of the data asset content, price range, and transaction object range contained in the data asset transaction request, from largest to smallest, is: data asset content, transaction object range, price range;

[0120] Based on the matching degree of data asset transactions between the target user and each of the other users, a target transaction object is matched for the target user from among the other users.

[0121] Optionally, when the submission module 302 is used to match a target transaction object for the target user from among the other users based on the data asset transaction matching degree between the target user and each of the other users, it is specifically used for:

[0122] Based on the order of data asset transaction matching degree from high to low for each of the other users, a preset number of other users are selected as candidate transaction objects.

[0123] The object information of the candidate transaction objects is sent to the user terminal of the target user, so that the target user can select the target transaction object from the candidate transaction objects;

[0124] Receive the object information of the selected target transaction object sent by the target user's client.

[0125] Optionally, after matching a target transaction object for the target user based on the target user's data asset transaction request, the target data asset transaction node is further configured to:

[0126] Receive transaction condition information sent by the target user's client and receive transaction condition information sent by the target transaction object's client;

[0127] When the transaction condition information of the target user and the target transaction object are the same, the transaction condition information is reviewed to determine whether the transaction condition information meets the preset requirements;

[0128] When the transaction conditions information meets the preset requirements, the relevant rights of the data assets are transferred between the target user and the target transaction object based on the transaction conditions information.

[0129] Figure 4 A schematic diagram of an electronic device provided in this application embodiment includes: a processor 401, a memory 402, and a bus 403. The memory 402 stores machine-readable instructions executable by the processor 401. When the electronic device runs the above-described information processing method, the processor 401 and the memory 402 communicate through the bus 403. The processor 401 executes the machine-readable instructions to perform the steps of the method described in Embodiment 1.

[0130] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps described in Embodiment 1.

[0131] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the devices, electronic devices, and computer-readable storage media described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0132] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the coupling or direct coupling or communication connection shown or discussed may be through some communication interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0133] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0134] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0135] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0136] Finally, it should be noted that the above-described embodiments are merely specific implementations of this application, used to illustrate the technical solutions of this application, and not to limit them. The scope of protection of this application is not limited thereto. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this application. Such modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of protection of the claims.

Claims

1. A method for managing data assets, characterized in that, The method is applied to a distributed trading platform; The distributed trading platform includes trading nodes corresponding to each data asset exchange; the method includes: Receive a login request from a target user, and perform identity authentication on the target user based on the login request; Once the target user successfully logs in, based on the target data asset exchange selected by the target user from multiple data asset exchanges, the target user's data asset transaction request is submitted to the target data asset transaction node corresponding to the target data asset exchange, so that the target data asset transaction node matches the target user with a target transaction object based on the target user's data asset transaction request.

2. The method according to claim 1, characterized in that, Before receiving a login request from a target user and authenticating the target user's identity based on the login request, the method further includes: Receive a registration request sent by the target user's client; the registration request includes the target user's account ID; the registration request is generated based on the registration information entered by the target user on the registration page of the distributed trading platform displayed on the client. Based on the registration request, a verification instruction message containing a verification code is sent to the target user's client; the verification instruction message is used to instruct the target user to input the verification code into the verification code input area in the registration page of the distributed trading platform within a specified time. If feedback information indicating that the verification code input is complete is received from the user terminal within the specified time, it is determined whether the verification code entered by the target user is correct. If the verification code entered by the target user is correct, a private key corresponding to the account ID is generated, the account ID and the private key are stored, and the private key is sent to the user's terminal, thus completing the registration.

3. The method according to claim 2, characterized in that, The step of receiving a login request from a target user and authenticating the target user's identity based on the login request includes: Receive login requests containing account ID and private key sent by the target user's client; Determine whether the account ID and private key contained in the login request are stored in the distributed trading platform; If the account ID and private key contained in the login request are stored in the distributed trading platform, it indicates that the target user has successfully logged in.

4. The method according to claim 1, characterized in that, When the target user is a seller, the data asset transaction request includes the data asset content, price range, and transaction target range of the data asset the seller intends to sell; when the target user is a buyer, the data asset transaction request includes the data asset content, price range, and transaction target range of the data asset the buyer intends to purchase.

5. The method according to claim 4, characterized in that, To enable the target data asset transaction node to match a target transaction object for the target user based on the target user's data asset transaction request, including: The target data asset transaction node matches the target user's data asset transaction request with data asset transaction requests submitted by other users according to the importance of the data asset content, price range, and transaction object range contained in the data asset transaction request, thereby obtaining the data asset transaction matching degree between the target user and each of the other users; wherein, when the target user is a seller, the other users are buyers; and when the target user is a buyer, the other users are sellers; the importance of the data asset content, price range, and transaction object range contained in the data asset transaction request, from largest to smallest, is: data asset content, transaction object range, price range; Based on the matching degree of data asset transactions between the target user and each of the other users, a target transaction object is matched for the target user from among the other users.

6. The method according to claim 5, characterized in that, The step of matching a target transaction object for the target user from among the other users based on the data asset transaction matching degree between the target user and each of the other users includes: Based on the order of data asset transaction matching degree from high to low for each of the other users, a preset number of other users are selected as candidate transaction objects. The object information of the candidate transaction objects is sent to the user terminal of the target user, so that the target user can select the target transaction object from the candidate transaction objects; Receive the object information of the selected target transaction object sent by the target user's client.

7. The method according to claim 1, characterized in that, After the target data asset transaction node matches a target transaction object for the target user based on the target user's data asset transaction request, the method further includes: Receive transaction condition information sent by the target user's client and receive transaction condition information sent by the target transaction object's client; When the transaction condition information of the target user and the target transaction object are the same, the transaction condition information is reviewed to determine whether the transaction condition information meets the preset requirements; When the transaction conditions information meets the preset requirements, the relevant rights of the data assets are transferred between the target user and the target transaction object based on the transaction conditions information.

8. A data asset management device, characterized in that, The device is used in a distributed trading platform; The distributed trading platform includes trading nodes corresponding to each data asset exchange; the device includes: The authentication module is used to receive login requests from target users and perform identity authentication on the target users based on the login requests; The submission module is used to submit the target user's data asset transaction request to the target data asset transaction node corresponding to the target data asset exchange after the target user successfully logs in, based on the target data asset exchange selected by the target user from multiple data asset exchanges, so that the target data asset transaction node matches the target user with a target transaction object based on the target user's data asset transaction request.

9. An electronic device, characterized in that, include: The device includes a processor, a memory, and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is in operation, the processor communicates with the memory via the bus, and the machine-readable instructions, when executed by the processor, perform the steps of the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the method as described in any one of claims 1 to 7.

Images