Account association method and device, equipment, medium and program product

Abstract

One or more embodiments of the invention provide an account association method and device, equipment, a medium and a program product, and the method comprises the steps: obtaining a first-class transaction data set of a first-class centralized account in a centralized transaction platform, determining a second type of transaction data set of a first type of decentralized account associated with the first type of centralized account in the decentralized transaction platform; when the transaction information between the first target transaction data in the first type transaction data set and the second target transaction data in the second type transaction data set is matched, the transaction information between the first target transaction data in the first type transaction data set and the second target transaction data in the second type transaction data set is matched; respectively determining a second type of centralized account transacting with the first type of centralized account in the first target transaction data and a second type of decentralized account transacting with the first type of decentralized account in the second target transaction data, and creating an association relationship between the second type of decentralized accounts and the second type of centralized accounts so as to realize association between the centralized accounts and the decentralized accounts.

Description

Technical Field

[0001] One or more embodiments of this specification relate to the field of information technology, and in particular, to an account association method, apparatus, device, medium, and program product. Background Art

[0002] With the emergence of decentralized trading methods, both parties can conduct transactions directly through decentralized protocols and blockchain technology. Decentralized trading methods have the characteristics of low transaction fees and fast transaction speeds, and are suitable for investment, payment and global financial activities.

[0003] However, due to the advantages of decentralized trading such as anonymity and few regional restrictions, it is often used illegally. Due to the decentralized nature, it is difficult to track the account owners involved in decentralized transactions, and it is impossible to accurately manage the compliance and risk of the decentralized transaction process. Summary of the Invention

[0004] In view of this, one or more embodiments of this specification provide the following technical solutions:

[0005] According to a first aspect of one or more embodiments of this specification, a method for associating accounts is provided, the method comprising:

[0006] Obtaining a first type of transaction data set of a first type of centralized account in a centralized trading platform, and, for a first type of decentralized account known to be associated with the first type of centralized account, determining a second type of transaction data set of the first type of decentralized account in the decentralized trading platform;

[0007] If transaction information between the first target transaction data in the first type of transaction data set and the second target transaction data in the second type of transaction data set matches, then respectively determining: the second type of centralized account in the first target transaction data that transacted with the first type of centralized account, and the second type of decentralized account in the second target transaction data that transacted with the first type of decentralized account;

[0008] An association relationship is created between the second-type decentralized account and the second-type centralized account.

[0009] According to a second aspect of one or more embodiments of this specification, an account association device is provided, the device comprising:

[0010] an acquisition module, configured to acquire a first type of transaction data set of a first type of centralized account in a centralized trading platform, and, for a first type of decentralized account known to be associated with the first type of centralized account, determine a second type of transaction data set of the first type of decentralized account in the decentralized trading platform;

[0011] a determination module configured to, if transaction information between first target transaction data in the first type of transaction data set and second target transaction data in the second type of transaction data set matches, respectively determine: a second type of centralized account in the first target transaction data that transacts with the first type of centralized account, and a second type of decentralized account in the second target transaction data that transacts with the first type of decentralized account;

[0012] A creation module is used to create an association relationship between the second type of decentralized account and the second type of centralized account.

[0013] According to a third aspect of one or more embodiments of this specification, a computing device is proposed, comprising: a processor; a memory for storing processor-executable instructions; wherein the processor implements the account association method described in the first aspect above by running the executable instructions.

[0014] According to a fourth aspect of one or more embodiments of this specification, a computer-readable storage medium is provided, on which computer instructions are stored. When the computer instructions are executed by a processor, the account association method described in the first aspect above is implemented.

[0015] According to a fifth aspect of one or more embodiments of this specification, a computer program product is proposed, including a computer program / instruction, which, when executed by a processor, implements the account association method described in the first aspect above.

[0016] It can be seen from the above embodiments that according to the scheme provided by one or more embodiments of this specification, a first type of transaction data set of a first type of centralized account in a centralized trading platform can be obtained, and for a first type of decentralized account known to be associated with the first type of centralized account, its second type of transaction data set in the decentralized trading platform is determined, so that when the transaction information between the first target transaction data in the first type of transaction data set and the second target transaction data in the second type of transaction data set matches, the second type of centralized account in the first target transaction data that trades with the first type of centralized account and the second type of decentralized account in the second target transaction data that trades with the first type of decentralized account are respectively determined, thereby creating an association relationship between the second type of decentralized account and the second type of centralized account, so as to realize the association between the centralized account in the centralized trading platform and the decentralized account in the decentralized trading platform, thereby facilitating the subsequent control of the centralized trading process and the decentralized trading process. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1This is a schematic diagram of an application scenario of an account association method provided by an exemplary embodiment.

[0018] Figure 2 This is a flowchart of an account association method provided by an exemplary embodiment.

[0019] Figure 3 It is a schematic diagram of a transaction process provided by an exemplary embodiment.

[0020] Figure 4 It is a schematic diagram of another transaction process provided by an exemplary embodiment.

[0021] Figure 5 It is a schematic diagram of another transaction process provided by an exemplary embodiment.

[0022] Figure 6 This is a schematic diagram of the overall flow of an account association method provided by an exemplary embodiment.

[0023] Figure 7 The present invention is a flowchart of a process of dividing an account into organizations provided by an exemplary embodiment.

[0024] Figure 8 It is a schematic structural diagram of a computing device provided by an exemplary embodiment.

[0025] Figure 9 It is a block diagram of an account association device provided by an exemplary embodiment. DETAILED DESCRIPTION

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

[0027] It should be noted that in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than those described in this specification. In addition, a single step described in this specification may be broken down into multiple steps for description in other embodiments, and multiple steps described in this specification may be combined into a single step for description in other embodiments.

[0028] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this manual are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and corresponding operation entrances are provided for users to choose to authorize or refuse.

[0029] With the popularization of the Internet and the development of e-commerce, transaction methods have undergone significant changes. Traditional offline transaction methods have gradually shifted to online transactions based on the Internet, greatly improving the convenience of the transaction process. As online transactions continue to gain popularity, online trading platforms have emerged to provide users with a convenient online trading environment. Users can use online trading platforms to transfer money, purchase goods, and so on.

[0030] In related technologies, a web2 trading platform managed by a centralized server can be built based on the second-generation Internet (web2) technology as an online trading platform for users to conduct online transactions. Users can register on the web2 trading platform, and the web2 trading platform can create a web2 account (also known as a centralized account) for the user through the centralized server, so that the user can perform a series of trading operations through the created web2 account. The web2 trading platform can verify the user's identity and process user requests through the centralized server. In addition, the user's account information and related data generated during the transaction process will also be recorded in the centralized server for subsequent analysis and management.

[0031] However, due to the centralized management of the web2 trading platform, the transaction process in the web2 trading platform lacks transparency, and the privacy and security of data are difficult to guarantee. Moreover, the transaction fees of the web2 trading platform are high and there are delays in the transaction process.

[0032] As a decentralized trading platform, third-generation internet (web3) trading platforms allow users to conduct transactions without centralized control and are gradually becoming a significant alternative to web2 trading platforms. Among related technologies, decentralized web3 trading platforms can be built based on blockchain technology. On web3 trading platforms powered by blockchain technology, users can create and manage their own web3 accounts (decentralized accounts), allowing them to conduct a range of transactions using their web3 accounts. The web3 trading platform utilizes blockchain technology to record and manage user account information and transaction data, enabling decentralized management of the transaction process.

[0033] Blockchains can optionally come in various types, including, but not limited to, public, private, and consortium blockchains. A public blockchain is a completely open blockchain network that anyone can join, view, and participate in transactions and verification processes. A private blockchain is a restricted blockchain network that only specific participants can join and use. Generally, private blockchains are controlled by a single organization or managed by a trusted entity, with data and transaction permissions subject to certain restrictions. A consortium blockchain, a type between public and private blockchains, can be jointly managed and controlled by multiple trusted parties. In short, public blockchains emphasize openness and decentralization, private blockchains emphasize centralized control and data privacy, and consortium blockchains fall somewhere in between, emphasizing collaboration and shared management among multiple organizations. Regardless of the type of blockchain, they can all be used to build decentralized trading platforms.

[0034] Optionally, the same user can maintain their own accounts on both the web2 trading platform and the web3 trading platform. Assets can be stored in both the web2 account on the web2 trading platform and the web3 account on the web3 trading platform. Optionally, the assets stored in the web2 account can be Category 1 assets, which can be traditional centralized financial assets such as funds, equity, bonds, etc. Category 1 assets are controlled and managed by financial institutions or web2 trading platforms, and users cannot directly access the underlying technology or control mechanisms; while the assets stored in the web3 account can be Category 2 assets, which can be digital assets such as decentralized financial assets and tokens. Category 2 assets can be stored on the blockchain and controlled by the user through their own private key.

[0035] Optionally, users can use their own web2 accounts to transfer funds to other users' web2 accounts on the web2 platform. The user as the recipient can use his web3 account to transfer funds to the web3 account of the initiating user on the web3 platform to realize cross-platform asset transactions.

[0036] However, due to the characteristics of the decentralized transaction process in the web3 platform, the transaction process in the web3 platform is difficult to monitor, and the transaction process in the web2 platform is difficult to correspond to the web3 platform, which makes it difficult to implement security monitoring and legitimacy monitoring of the transaction process. In view of this, one or more embodiments of this specification provide an account association method to help discover the association relationship between the centralized account in the centralized trading platform and the decentralized account in the decentralized trading platform, so that the transaction behavior in the centralized trading platform and the transaction behavior in the decentralized trading platform can be monitored based on the discovered association relationship, thereby improving the security of the transaction process and ensuring the legitimacy of the transaction process.

[0037] See also Figure 1 , Figure 1 This is a schematic diagram of an application scenario of an account association method provided by an exemplary embodiment. Figure 1 As shown, the application scenario can be composed of a centralized trading platform 101, a decentralized trading platform 102 and a computing device 103, wherein the computing device 103 can communicate with the centralized trading platform 101 through the network, and can also communicate with the decentralized trading platform 102 through the network.

[0038] In some embodiments, the centralized trading platform 101 can be implemented based on a centralized server. The centralized server can be a physical server containing an independent host, or a physical server cluster composed of multiple independent hosts, or a virtual server hosted by a host cluster, so as to realize the management and control of accounts and transaction processes through the centralized server.

[0039] In some embodiments, the decentralized trading platform 102 can be implemented using blockchain technology. For example, a blockchain system can be composed of multiple blockchain nodes to provide the necessary backend support for the decentralized trading platform. Alternatively, multiple blockchain nodes can form a blockchain network, in which one blockchain node can communicate with another blockchain node. Figure 1 The number of blockchain nodes shown in the figure is merely an example for illustration and does not constitute a limitation of this specification.

[0040] In some embodiments, the first user can log in to the centralized account 1 in the centralized trading platform 101 through the first terminal device to initiate a centralized transaction request through the first terminal device to trade with other centralized accounts (such as the centralized account 2 corresponding to the second user). The first terminal device can send the centralized transaction request to the centralized server of the centralized trading platform 101 to process the centralized transaction request through the centralized server to modify the account balances of the centralized account 1 and the centralized account 2 as the two parties to the transaction to realize the transaction between the centralized account 1 and the centralized account 2.

[0041] In some embodiments, each centralized account is associated with a decentralized account in the decentralized trading platform. For transactions in the centralized trading platform, corresponding transactions will occur in the decentralized trading platform. That is, according to the centralized trading process described above, a second user can log in to decentralized account 2 in the decentralized trading platform 102 through a second terminal device, and initiate a decentralized transaction request through the second terminal device to trade with decentralized account 1 corresponding to the first user. The second terminal device can send the decentralized transaction request to the corresponding blockchain node, which processes the decentralized transaction request and modifies the account balances of decentralized account 1 and decentralized account 2, the two parties to the transaction, to implement a decentralized transaction process corresponding to the centralized transaction process described above.

[0042] In some embodiments, the above transaction process can be: centralized account 1 uses the first type of assets to purchase the second type of assets from centralized account 2 on the centralized trading platform, and the decentralized account 2 corresponding to the centralized account 2 pays the second type of assets purchased by the centralized account 1 to the decentralized account 1 corresponding to the centralized account 1 on the decentralized trading platform to complete the transaction.

[0043] In some embodiments, the name of the centralized account is not limited, and it can be, for example, a "web2 transaction account"; the name of the decentralized account is not limited, and it can be, for example, a "web3 transaction account".

[0044] In some embodiments, the first terminal device and the second terminal device can both be PCs (Personal Computers), mobile phones, tablet devices, laptops, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smart watches, etc.), etc., and one or more embodiments of this specification do not limit this.

[0045] In some embodiments, computing device 103 may be a physical server comprising an independent host, or a physical server cluster consisting of multiple independent hosts, or a virtual server hosted by a host cluster. Optionally, computing device 103 may collect data from centralized trading platform 101 and data from decentralized trading platform 102 to determine the association between centralized accounts in centralized trading platform 101 and decentralized accounts in decentralized trading platform 102, thereby facilitating subsequent monitoring of trading activities in centralized trading platform 101 and decentralized trading platform 102.

[0046] The above is merely an illustrative description of the application scenarios of one or more embodiments of this specification and does not constitute a limitation on the application scenarios of the embodiments of this specification. In more possible implementations, the solutions provided by one or more embodiments of this specification can be applied to more scenarios involving centralized transactions and decentralized transactions. One or more embodiments of this specification do not limit the specific application scenarios.

[0047] After introducing the application scenarios of one or more embodiments of this specification, the optional implementation process of one or more embodiments of this specification will be introduced next.

[0048] See also Figure 2 , Figure 2 This is a flowchart of an account association method provided by an exemplary embodiment. Figure 2 As shown, the method includes:

[0049] Step 201: Obtain a first type of transaction data set of a first type of centralized account in a centralized trading platform, and, for a first type of decentralized account known to be associated with the first type of centralized account, determine its second type of transaction data set in the decentralized trading platform.

[0050] Optionally, the first type of transaction data set may include a set of transaction data generated when the first type of centralized account trades with other centralized accounts in a centralized trading platform.

[0051] Optionally, the first type of decentralized account associated with the first type of central account is known. Therefore, based on the known account association relationship, the second type of transaction data set of the first type of decentralized account associated with the first type of central account in the decentralized trading platform can be obtained.

[0052] Optionally, the second type of transaction data set may include a set of transaction data generated when the first type of decentralized account trades with other decentralized accounts in the decentralized trading platform.

[0053] Step 202: If the transaction information between the first target transaction data in the first type of transaction data set and the second target transaction data in the second type of transaction data set matches, then determine respectively: the second type of centralized account in the first target transaction data that conducts transactions with the first type of centralized account, and the second type of decentralized account in the second target transaction data that conducts transactions with the first type of decentralized account.

[0054] In some embodiments, the transaction information of the first target transaction data in the first category of transaction data set can be matched with the transaction information of the second target transaction data in the second category of transaction data set to determine whether the transaction information between the first target transaction data and the second target transaction data matches, so that the second category of centralized accounts and the second category of decentralized accounts can be determined when the transaction information between the first target transaction data and the second target transaction data matches.

[0055] It should be noted that the first target transaction data is generated by transactions between the first type of centralized account and the second type of centralized account, while the second target transaction data is generated by transactions between the first type of decentralized account and the second type of decentralized account. In other words, the accounts that transact with the first type of centralized account in the first target transaction data are the second type of centralized account, and the accounts that transact with the first type of decentralized account in the second target transaction data are the second type of decentralized account.

[0056] Step 203: Create an association relationship between the second type of decentralized account and the second type of centralized account.

[0057] In some embodiments, the second type of decentralized account and the second type of centralized account may be recorded as a set of mapping pairs to create an association relationship between the second type of decentralized account and the second type of centralized account.

[0058] Through the solution provided by the above embodiment, new account association relationships can be discovered based on the first type of centralized accounts and the first type of decentralized accounts with known association relationships, and the data between centralized trading platforms and decentralized trading platforms can be effectively integrated to overcome the limitations of single-chain transaction data analysis.

[0059] After introducing the basic implementation of the account association method provided by one or more embodiments of this specification, the optional implementation of one or more embodiments of this specification is introduced below.

[0060] In some embodiments, for step 201, when obtaining the first type of transaction data set of the first type of centralized account in the centralized trading platform, and, for the first type of decentralized account known to be associated with the first type of centralized account, determining its second type of transaction data set in the decentralized trading platform, when it is detected that the first type of centralized account and / or the first type of decentralized account triggers a transaction behavior, step 201 can be used to obtain the first type of transaction data set of the first type of centralized account in the centralized trading platform and the second type of transaction data set of the first type of decentralized account in the decentralized trading platform, but is not limited to this. The acquisition of the first type of transaction data set and the second type of transaction data set can also be triggered by relevant technical personnel according to technical requirements, and the acquisition of the first type of transaction data set and the second type of transaction data set can also be performed periodically, and so on. One or more embodiments of this specification do not limit the timing of obtaining the transaction data set.

[0061] In some embodiments, whether it is a centralized trading platform or a decentralized trading platform, the transaction information of each transaction will be recorded, and the recorded transaction information may at least include the account information of both parties to the transaction, so that based on the recorded account information of both parties to the transaction, a first type of transaction data set of a first type of centralized account can be obtained from the transaction data on the centralized trading platform, and a second type of transaction data set of a first type of decentralized account can be obtained from the transaction data on the decentralized trading platform.

[0062] In some embodiments, after obtaining the first category transaction data set and the second category transaction data set, transaction data matching can be performed based on the obtained first category transaction data set and the second category transaction data set, but not limited to this, the obtained first category transaction data set and the second category transaction data set can also be first subjected to data cleaning processing, so as to match transaction data based on the first category transaction data set and the second category transaction data set that have undergone data cleaning processing.

[0063] Optionally, the data cleaning process may include at least one of data deduplication, data format conversion, and data standardization, but is not limited thereto.

[0064] In some embodiments, regardless of whether data cleaning processing has been performed, when matching transaction data based on the first type of transaction data set and the second type of transaction data set, matching can be achieved based on transaction information of the transaction data.

[0065] In some embodiments, taking the process of matching the first target transaction data in the first category of transaction data set with the second target transaction data in the second category of transaction data set as an example, the transaction information of the first target transaction data can be compared with the transaction information of the second target transaction data to determine whether the first target transaction data and the second target transaction data match.

[0066] In some embodiments, the transaction information may include the transaction time and transaction amount, but is not limited thereto. The transaction information may also include more types of information, which is not limited in one or more embodiments of this specification.

[0067] In some embodiments, the transaction time of the first target transaction data and the transaction time of the second target transaction data can be unified into the same time measurement dimension, and the transaction amount of the first target transaction data and the transaction amount of the second target transaction data can be unified into the same asset measurement dimension, so that the transaction time of the first target transaction data and the transaction time of the second target transaction data are compared, and the transaction amount of the first target transaction data and the transaction amount of the second target transaction data are compared to determine whether the first target transaction data and the second target transaction data match.

[0068] In some embodiments, the trading time used in a decentralized trading platform is Coordinated Universal Time (UTC). The trading time used in a centralized trading platform can be a time zone standard time. For example, a centralized trading platform deployed in the East 8 District uses China Standard Time (CST), which is 8 hours later than UTC, i.e., CST = UTC+8. Alternatively, a centralized trading platform deployed in the West 5 District uses Eastern Standard Time (EST), which is 5 hours earlier than UTC, i.e., EST = UTC-5.

[0069] In some embodiments, when the transaction time of the first target transaction data and the transaction time of the second target transaction data are unified into the same time measurement dimension, the transaction time of the first target transaction data and the transaction time of the second target transaction time can be converted according to the time difference between the two transaction times. The transaction time of the first target transaction data can be converted according to the transaction time of the second target transaction time to unify the two transaction times into the time measurement method in the decentralized trading platform, or the transaction time of the second target transaction data can be converted according to the transaction time of the first target transaction time to unify the two transaction times into the time measurement method in the centralized trading platform.

[0070] In some embodiments, the transaction currency used in the centralized trading platform is traditional currency, and the transaction currency used in the decentralized trading platform is virtual currency. There will be a certain asset conversion ratio between traditional currency and virtual currency. The asset conversion ratio when traditional currencies of different currencies are converted into the same virtual currency may be different, and the asset conversion ratio when the same traditional currency is converted into virtual currencies of different currencies may also be different. In addition, for the conversion between a traditional currency and a virtual currency, the asset conversion ratio will also vary due to the account types of the two parties to the transaction. For example, for a normal account, the asset conversion ratio may be 7 to 7.5, while for an abnormal account, the asset conversion ratio will be higher.

[0071] In some embodiments, the asset conversion ratio between the transaction amount of the first target transaction data and the transaction amount of the second target transaction data can be determined based on the account type of the first type of centralized account in the first target transaction data and / or the account type of the first type of decentralized account in the second target transaction data. For example, if both the first type of centralized account and the first type of decentralized account are normal accounts, the asset conversion ratio between the transaction amount of the first target transaction data and the transaction amount of the second target transaction data can be determined to be 7 to 7.5; conversely, if at least one of the first type of centralized account or the first type of decentralized account is marked as an abnormal account, the asset conversion ratio between the transaction amount of the first target transaction data and the transaction amount of the second target transaction data will be determined to be a higher value. The specific value will be determined based on actual conditions, and one or more embodiments of this specification do not limit this.

[0072] In some embodiments, when unifying the transaction amount of the first target transaction data and the transaction amount of the second target transaction data into the same asset measurement dimension, the transaction amount of the first target transaction data and the transaction amount of the second target transaction time can be converted according to the asset conversion ratio between the two trading platforms. The transaction amount of the first target transaction data can be converted according to the transaction amount of the second target transaction time to unify the two transaction amounts into the asset measurement method in the decentralized trading platform, or the transaction amount of the second target transaction data can be converted according to the transaction amount of the first target transaction time to unify the two transaction amounts into the asset measurement method in the centralized trading platform.

[0073] In some embodiments, after the measurement dimensions of transaction time and transaction amount are unified through the above embodiments, the first target transaction data and the second target transaction data can be matched according to the transaction time and transaction amount after the unified measurement dimensions.

[0074] In some embodiments, if the first type of centralized account for transactions in the first target transaction data and the second type of centralized account for transactions in the second target transaction data are both one, then the transaction time of the first target transaction data after the measurement dimension is unified can be directly compared with the transaction time of the second target transaction data, and the transaction amount of the first target transaction data after the measurement dimension is unified can be compared with the transaction amount of the second target transaction data to determine whether the first target transaction time matches the second target transaction data based on whether the transaction time and transaction amount of the two meet the first condition.

[0075] In some embodiments, the first condition may be that the time difference between the transaction time of the first target transaction data and the transaction time of the second target transaction data meets a first threshold, and the transaction amount of the first target transaction data is consistent with the transaction amount of the second target transaction data. That is, if the time difference between the transaction time of the first target transaction data and the transaction time of the second target transaction data meets the first threshold, and the transaction amount of the first target transaction data is consistent with the transaction amount of the second target transaction data, then the first target transaction data and the second target transaction data are determined to match; conversely, if the time difference between the transaction time of the first target transaction data and the transaction time of the second target transaction data does not meet the first threshold, or the transaction amount of the first target transaction data and the transaction amount of the second target transaction data are inconsistent, then the first target transaction data and the second target transaction data are determined to be mismatched.

[0076] Optionally, the time difference satisfying the first threshold may mean that the time difference is less than or equal to the first threshold, and accordingly, the time difference not satisfying the first threshold means that the time difference is greater than the first threshold. Alternatively, the time difference satisfying the first threshold may mean that the time difference is less than the first threshold, and accordingly, the time difference not satisfying the first threshold means that the time difference is greater than or equal to the first threshold. The first threshold may be any value set according to actual needs, and one or more embodiments of this specification do not limit the value of the first threshold.

[0077] In some embodiments, if there are multiple first-type centralized accounts conducting transactions in the first target transaction data and these multiple first-type centralized accounts belong to the same organization, and / or if there are multiple first-type decentralized accounts conducting transactions in the second target transaction data and these multiple first-type decentralized accounts belong to the same organization, then the first transaction time and the second transaction time can be determined for comparison based on the transaction time of the first target transaction data and the transaction time of the second target transaction data after the measurement dimension is unified, and the first transaction amount statistical value and the second transaction amount statistical value for comparison can be determined based on the transaction amount of the first target transaction data and the transaction amount of the second target transaction data after the measurement dimension is unified, respectively. Based on the comparison result between the first transaction time and the second transaction time and the comparison result between the first transaction amount statistical value and the second transaction amount statistical value, whether the first target transaction time matches the second target transaction data is determined based on whether the second condition is met. It should be noted that regardless of whether there is one or more first-type centralized accounts and one or more first-type decentralized accounts, there is only one second-type centralized account and one second-type decentralized account for transactions therewith to ensure the accuracy and validity of the determined mapping relationship. The method for determining organizations and accounts within organizations will be described in detail below and will not be repeated here.

[0078] In some embodiments, the first transaction time can be determined based on the transaction time of at least one first-class centralized account in the first target transaction data, and the second transaction time can be determined based on the transaction time of at least one first-class decentralized account in the second target transaction data. For example, the latest transaction time among the transaction times of at least one first-class centralized account in the first target transaction data can be used as the first transaction time, and the latest transaction time among the transaction times of at least one first-class decentralized account in the second target transaction data can be used as the second transaction time; or, the earliest transaction time among the transaction times of at least one first-class centralized account in the first target transaction data can be used as the first transaction time, and the earliest transaction time among the transaction times of at least one first-class decentralized account in the second target transaction data can be used as the second transaction time; or, the earliest transaction time among the transaction times of at least one first-class centralized account in the first target transaction data can be used as the first transaction time, and the latest transaction time among the transaction times of at least one first-class decentralized account in the second target transaction data can be used as the second transaction time. The latest transaction time among the transaction times of at least one first-type centralized account of the first target transaction data can be used as the second transaction time; or, the latest transaction time among the transaction times of at least one first-type centralized account of the first target transaction data can be used as the first transaction time, and the earliest transaction time among the transaction times of at least one first-type decentralized account of the second target transaction data can be used as the second transaction time; or, any transaction time among the transaction times of at least one first-type centralized account of the first target transaction data can be used as the first transaction time, and any transaction time among the transaction times of at least one first-type decentralized account of the second target transaction data can be used as the second transaction time, and so on. One or more embodiments of this specification do not limit the method for determining the first transaction time and the second transaction time.

[0079] In some embodiments, a first transaction amount statistic may be determined based on the transaction amount of at least one first-type centralized account in the first target transaction data, and a second transaction amount statistic may be determined based on the transaction amount of at least one first-type decentralized account in the second target transaction data. For example, the transaction amounts of at least one first-type centralized account may be accumulated to obtain the total transaction amount of the at least one first-type centralized account as the first transaction amount statistic, and the transaction amounts of at least one first-type decentralized account may be accumulated to obtain the total transaction amount of the at least one first-type decentralized account as the second transaction amount statistic.

[0080] In some embodiments, the second condition may be that the time difference between the first transaction time and the second transaction time meets a second threshold, and the first transaction amount statistics are consistent with the second transaction amount statistics. That is, if the time difference between the first transaction time and the second transaction time meets the second threshold, and the first transaction amount statistics are consistent with the second transaction amount statistics, then the first target transaction data and the second target transaction data are determined to match; conversely, if the time difference between the first transaction time and the second transaction time does not meet the second threshold, or the first transaction amount statistics are inconsistent with the second transaction amount statistics, then the first target transaction data and the second target transaction data are determined to not match.

[0081] Optionally, the time difference satisfying the second threshold may mean that the time difference is less than or equal to the second threshold, and accordingly, the time difference not satisfying the second threshold means that the time difference is greater than the second threshold. Alternatively, the time difference satisfying the second threshold may mean that the time difference is less than the second threshold, and accordingly, the time difference not satisfying the second threshold means that the time difference is greater than or equal to the second threshold. The second threshold can be any value set according to actual needs, and the second threshold can be the same as or different from the first threshold. One or more embodiments of this specification do not limit the value of the second threshold.

[0082] For example, see Figure 3 , Figure 3 This is a schematic diagram of a transaction process provided by an exemplary embodiment. Figure 3 As shown, centralized accounts A1, A2, and A3 belonging to the same organization transfer funds to centralized account A4 on the centralized trading platform. The account associated with centralized account A1 on the decentralized trading platform is decentralized account B1, the account associated with centralized account A2 on the decentralized trading platform is decentralized account B2, and the account associated with centralized account A3 on the decentralized trading platform is decentralized account B3. If decentralized account B4 transfers funds to decentralized account B1 on the decentralized platform, if centralized account A1, centralized account A2, and centralized account A3 on the decentralized trading platform are transferred to decentralized account B1 on the decentralized platform, the centralized account A1 and centralized account A2 will be transferred to decentralized account B1 on the decentralized platform. If the time when centralized accounts A2 and A3 transfer funds to centralized account A4, and the time when decentralized account B4 transfers funds to decentralized account B1 meet certain conditions, and the total amount transferred from centralized accounts A1, A2, and A3 to centralized account A4 is consistent with the amount transferred from decentralized account B4 to decentralized account B1, then it can be determined that the transactions of centralized accounts A1, A2, and A3 transferring funds to centralized account A4, and decentralized account B4 transferring funds to decentralized account B1 match.

[0083] For example, see Figure 4 , Figure 4 is a schematic diagram of another transaction process provided by an exemplary embodiment, such as Figure 4As shown in the figure, centralized account A1 and centralized account A2 transfer funds to centralized account A3 on the centralized trading platform. The account associated with centralized account A1 on the decentralized trading platform is decentralized account B1, and the account associated with centralized account A2 on the decentralized trading platform is decentralized account B2. If decentralized account B3 transfers funds to decentralized account B4 on the decentralized platform, centralized account A1, centralized account A2 and centralized account A4 belong to the same organization, and the account associated with centralized account A4 on the decentralized trading platform is decentralized account B1. For centralized account B4, if the time when centralized accounts A1 and A2 transfer funds to centralized account A3, and the time when decentralized account B3 transfer funds to decentralized account B4 meet certain conditions, and the total amount transferred from centralized accounts A1 and A2 to centralized account A3 is consistent with the amount transferred from decentralized account B3 to decentralized account B4, then it can be determined that the transfers from centralized accounts A1 and A2 to centralized account A3 and the transfers from decentralized account B3 to decentralized account B4 are matched.

[0084] For example, see Figure 5 , Figure 5 This is a schematic diagram of another transaction process provided by an exemplary embodiment. Figure 5 As shown in the figure, centralized account A1 transfers money to centralized account A2 on the centralized trading platform. The account associated with centralized account A1 on the decentralized trading platform is decentralized account B1, and the account associated with centralized account A2 on the decentralized trading platform is decentralized account B2. If decentralized account B2 transfers money to decentralized account B1 and decentralized account B3 on the decentralized platform, the account associated with decentralized account B3 on the centralized trading platform is centralized account A3. Centralized account A1 and centralized account A3 belong to the same For an organization, if the time of the transfer from centralized account A1 to centralized account A2 and the time of the transfer from decentralized account B2 to decentralized accounts B1 and B3 meet certain conditions, and the amount transferred from centralized account A1 to centralized account A2 is consistent with the sum of the amounts transferred from decentralized account B2 to decentralized accounts B1 and B3, then it can be determined that the transfer from centralized account A1 to centralized account A2 and the transfer from decentralized account B2 to decentralized accounts B1 and B3 are matched.

[0085] In some embodiments, after determining that the first target transaction data and the second target transaction data match, the second type of centralized account in the first target transaction data that transacted with the first type of centralized account, and the second type of decentralized account in the second target transaction data that transacted with the first type of decentralized account, can be determined based on the transaction information of the first target transaction data and the transaction information of the second target transaction data. The transaction information may include the account information of both parties to the transaction, thereby enabling the determination of the second type of centralized account and the second type of decentralized account based on the transaction information of the corresponding transaction data.

[0086] In some embodiments, after determining the second type of centralized account and the second type of decentralized account, an association relationship can be created between the second type of decentralized account and the second type of centralized account through step 203 to achieve the association between the second type of decentralized account and the second type of centralized account.

[0087] In some embodiments, for a centralized account that is known to be associated with a decentralized account, if the centralized account is an abnormal account, the transaction behavior of the centralized account and the associated decentralized account can be monitored to effectively ensure transaction security.

[0088] In some embodiments, it is possible to determine whether the second type of centralized account is an abnormal account based on the account information of the second type of centralized account, so that if the second type of centralized account is an abnormal account, an alarm information is generated in response to the triggering of transaction behavior by the second type of centralized account and / or the second type of decentralized account.

[0089] In some embodiments, the association between abnormal centralized accounts and decentralized accounts can be recorded in a database so that subsequent transaction monitoring can be performed based on the association recorded in the database. That is, if a second-type centralized account is determined to be an abnormal account, the association between the second-type centralized account and the second-type decentralized account can be recorded in the database, so that transaction behavior can be monitored based on the association recorded in the database.

[0090] In some embodiments, the warning information may be used to prompt further verification of the transaction behavior of the second type of centralized account and / or the second type of decentralized account, but is not limited thereto.

[0091] See also Figure 6 , Figure 6 This is a schematic diagram of the overall flow of an account association method provided by an exemplary embodiment. Figure 6As shown, for a known mapping pair (i.e., an associated first-class centralized account and a first-class decentralized account), transactions can be obtained according to the first-class centralized account and the first-class decentralized account through step 601, and transactions can be matched based on the transaction time and transaction amount of the acquired transactions through step 602, so that the second-class centralized account and the second-class decentralized account can be obtained according to the matched transactions through step 603, and the new mapping pair (i.e., the associated second-class centralized account and the second-class decentralized account) can be obtained through step 604, so that it can be determined whether the newly found mapping pair is related to the abnormal account through step 605, and if it is determined that the newly found mapping pair is related to the abnormal account, the mapping pair recorded in the database can be updated through step 606. The detailed implementation process can be found in the introduction above and will not be repeated here.

[0092] In some embodiments, for centralized accounts that are known to be associated with decentralized accounts, they may also be divided into organizational groups to determine centralized accounts that belong to the same organization.

[0093] In some embodiments, for multiple first-type centralized accounts that are known to be associated with first-type decentralized accounts, the identity identification information of each first-type centralized account can be obtained; for any two first-type centralized accounts among the multiple first-type centralized accounts, if the identity identification information of these two first-type centralized accounts meets specified conditions, it can be determined that these two first-type centralized accounts belong to the same organization.

[0094] In some embodiments, tag information can be added to two first-category centralized accounts whose identity identification information meets specified conditions. The tag information can be used to indicate that the two first-category centralized accounts belong to the same organization, so that multiple centralized accounts belonging to the same organization can be quickly identified subsequently through the tag information.

[0095] It should be noted that if two first-type centralized accounts belong to the same organization, then the first-type decentralized accounts associated with these two first-type centralized accounts also belong to the same organization.

[0096] In some embodiments, the identity identification information may be the account's network address information, the device identification information of the transaction device used by the account, the account's network connection information, the account's registered address information, the account's active address information, etc., but is not limited thereto.

[0097] Optionally, the network address information of the account may be, but is not limited to, an Internet Protocol (IP) address of the account.

[0098] Optionally, the device identification information of the transaction device used by the account may be a unified machine identifier (UMID) of the transaction device used by the account, but is not limited thereto.

[0099] Optionally, the network connection information of the account may be used to indicate a wireless network to which the account is connected, for example, a Wireless Fidelity (WiFi) network to which the account is connected, but is not limited thereto.

[0100] Optionally, the registered address information of the account may be the village to which the registered address of the account belongs, but is not limited thereto.

[0101] Optionally, the active address information of the account may be the city to which the account's most frequently used login address belongs, but is not limited thereto.

[0102] Through the above embodiments, it is possible to timely perform organizational identification on centralized accounts that are known to be associated with decentralized accounts, thereby being able to timely discover multiple centralized accounts belonging to the same organization.

[0103] In some embodiments, if the same centralized account exists in two organizations, the two organizations can be merged.

[0104] In some embodiments, for multiple centralized accounts in the same organization, each centralized account can be considered to be associated with the decentralized accounts associated with other centralized accounts in the organization.

[0105] See also Figure 7 , Figure 7 This is a flowchart of a process for dividing an account into organizations provided by an exemplary embodiment. Figure 7 As shown, for a first-type centralized account that is known to be associated with a first-type decentralized account, step 701 can be used to count the first-type centralized accounts with the same identity identification information according to the identity identification information of the first-type centralized account, including network address information (such as IP), network connection information (such as WiFi), device identification information of the transaction device used (such as UMID), registered address information (which can be accurate to the village), and active address information (which can be accurate to the city). Thus, step 702 can be used to determine that the first-type centralized accounts with the same identity identification information belong to the same organization. The detailed implementation process can be found in the introduction above and will not be repeated here.

[0106] Through the above embodiments, the organizational division of centralized accounts with known associated decentralized accounts can be achieved, thereby realizing transaction monitoring in the organizational dimension, so as to effectively monitor multiple centralized accounts in the organization trading with a centralized account (i.e., centralized account M) on a centralized trading platform (i.e., many-to-one transactions), but the decentralized account corresponding to the centralized account M in the decentralized trading platform trades with decentralized accounts associated with other centralized accounts in the organization, or the decentralized account corresponding to the centralized account M in the decentralized trading platform trades with one of the above-mentioned multiple centralized accounts, further ensuring the security of the transaction process.

[0107] Corresponding to the aforementioned method embodiments, this specification also provides corresponding device embodiments and apparatus embodiments.

[0108] Figure 8 This is a schematic diagram of a computing device provided by an exemplary embodiment. Figure 8 At the hardware level, the computing device includes a processor 802, an internal bus 804, a network interface 806, a memory 808, and a non-volatile memory 810. Of course, it may also include hardware required for other tasks. One or more embodiments of this specification can be implemented based on software, such as the processor 802 reading the corresponding computer program from the non-volatile memory 810 into the memory 808 and then running it. Of course, in addition to software implementation, one or more embodiments of this specification do not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0109] This manual also provides an account association device, please refer to Figure 9 , Figure 9 is a block diagram of an account association device provided by an exemplary embodiment. The account association device can be applied to Figure 8 In the computing device shown, the technical solutions provided by one or more embodiments of this specification are implemented. The account association device may include:

[0110] Acquisition module 901 is configured to acquire a first type of transaction data set of a first type of centralized account in a centralized trading platform, and, for a first type of decentralized account known to be associated with the first type of centralized account, determine a second type of transaction data set of the first type of decentralized account in the decentralized trading platform;

[0111] a determination module 902 configured to, if transaction information between first target transaction data in the first type of transaction data set and second target transaction data in the second type of transaction data set matches, respectively determine: a second type of centralized account in the first target transaction data that transacted with the first type of centralized account, and a second type of decentralized account in the second target transaction data that transacted with the first type of decentralized account;

[0112] The creation module 903 is used to create an association relationship between the second type of decentralized account and the second type of centralized account.

[0113] In some embodiments, the transaction information includes at least the transaction time and transaction amount;

[0114] The device further comprises:

[0115] a processing module, configured to unify the transaction time of the first target transaction data and the transaction time of the second target transaction data into the same time measurement dimension, and unify the transaction amount of the first target transaction data and the transaction amount of the second target transaction data into the same asset measurement dimension;

[0116] The processing module is further used to compare the transaction time of the first target transaction data with the transaction time of the second target transaction data, and to compare the transaction amount of the first target transaction data with the transaction amount of the second target transaction data to determine whether the first target transaction data matches the second target transaction data.

[0117] In some embodiments, the first type of centralized account for transactions in the first target transaction data and the second type of centralized account for transactions in the second target transaction data are both one;

[0118] The processing module, when comparing the transaction time of the first target transaction data with the transaction time of the second target transaction data, and comparing the transaction amount of the first target transaction data with the transaction amount of the second target transaction data, to determine whether the first target transaction data matches the second target transaction data, is configured to:

[0119] If the time difference between the transaction time of the first target transaction data and the transaction time of the second target transaction data meets a first threshold, and the transaction amount of the first target transaction data is consistent with the transaction amount of the second target transaction data, it is determined that the first target transaction data matches the second target transaction data.

[0120] In some embodiments, there are multiple first-type centralized accounts performing transactions in the first target transaction data, and these multiple first-type centralized accounts belong to the same organization; and / or, there are multiple first-type decentralized accounts performing transactions in the second target transaction data, and these multiple first-type decentralized accounts belong to the same organization;

[0121] The processing module, when comparing the transaction time of the first target transaction data with the transaction time of the second target transaction data, and comparing the transaction amount of the first target transaction data with the transaction amount of the second target transaction data, to determine whether the first target transaction data matches the second target transaction data, is configured to:

[0122] Determining a first transaction time based on a transaction time of at least one first-type centralized account in the first target transaction data, and determining a second transaction time based on a transaction time of at least one first-type decentralized account in the second target transaction data;

[0123] Determining a first transaction amount statistical value based on the transaction amount of at least one first-type centralized account in the first target transaction data, and determining a second transaction amount statistical value based on the transaction amount of at least one first-type decentralized account in the second target transaction data;

[0124] If the time difference between the first transaction time and the second transaction time meets a second threshold, and the first transaction amount statistical value is consistent with the second transaction amount statistical value, it is determined that the first target transaction data matches the second target transaction data.

[0125] In some embodiments, the determination module 902 is further used to determine the asset conversion ratio between the transaction amount of the first target transaction data and the transaction amount of the second target transaction data based on the account type of the first type of centralized account in the first target transaction data and / or the account type of the first type of decentralized account in the second target transaction data.

[0126] In some embodiments, the apparatus further comprises:

[0127] A data cleaning module is used to perform data cleaning processing on the first type of transaction data set and the second type of transaction data set, wherein the data cleaning processing includes at least one of data deduplication, data format conversion and data standardization processing.

[0128] In some embodiments, the determining module 902 is further configured to determine whether the second type of centralized account is an abnormal account based on the account information of the second type of centralized account;

[0129] The device further comprises:

[0130] A generation module is used to generate an alarm message in response to the triggering of a transaction behavior by the second type of centralized account and / or the second type of decentralized account when the second type of centralized account is an abnormal account.

[0131] In some embodiments, the acquisition module 901 is further configured to acquire identity identification information of each of the plurality of first-type centralized accounts known to be associated with the first-type decentralized account;

[0132] The device further comprises:

[0133] A marking module is used to add marking information to any two first-type centralized accounts among the multiple first-type centralized accounts if the identity identification information of the two first-type centralized accounts meets specified conditions, where the marking information is used to indicate that the two first-type centralized accounts belong to the same organization.

[0134] In some embodiments, the identity identification information includes at least one of the following:

[0135] The account's network address information;

[0136] Device identification information of the transaction device used by the account;

[0137] The account's network connection information;

[0138] The account's registered address information;

[0139] The account's active address information.

[0140] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having certain functions. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email transceiver, game console, tablet computer, wearable device, or any combination of these devices.

[0141] In a typical configuration, a computer includes one or more processors (Central Processing Unit, CPU), input / output interfaces, network interfaces and memory.

[0142] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0143] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change random access memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. According to the definition in this article, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0144] In some embodiments, this specification also provides a computer program product, including a computer program, which, when executed by a processor of a computing device, implements the account association method provided in any embodiment of this specification.

[0145] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0146] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0147] The terms used in one or more embodiments of this specification are for the purpose of describing specific embodiments only and are not intended to limit one or more embodiments of this specification. The singular forms "a," "an," "the," and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0148] It should be understood that although the terms first, second, third, etc. may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when..." or "when..." or "in response to determining."

[0149] The above description is merely a preferred embodiment of one or more embodiments of this specification and is not intended to limit one or more embodiments of this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of one or more embodiments of this specification shall be included in the scope of protection of one or more embodiments of this specification.

Claims

1. A method for associating accounts, the method comprising: Obtaining a first type of transaction data set of a first type of centralized account in a centralized trading platform, and, for a first type of decentralized account known to be associated with the first type of centralized account, determining a second type of transaction data set of the first type of decentralized account in the decentralized trading platform; If transaction information between the first target transaction data in the first type of transaction data set and the second target transaction data in the second type of transaction data set matches, then respectively determining: the second type of centralized account in the first target transaction data that transacted with the first type of centralized account, and the second type of decentralized account in the second target transaction data that transacted with the first type of decentralized account; An association relationship is created between the second-type decentralized account and the second-type centralized account.

2. The method according to claim 1, wherein the transaction information includes at least the transaction time and transaction amount; The method further comprises: Unifying the transaction time of the first target transaction data and the transaction time of the second target transaction data into the same time measurement dimension, and unifying the transaction amount of the first target transaction data and the transaction amount of the second target transaction data into the same asset measurement dimension; The transaction time of the first target transaction data is compared with the transaction time of the second target transaction data, and the transaction amount of the first target transaction data is compared with the transaction amount of the second target transaction data to determine whether the first target transaction data matches the second target transaction data.

3. The method according to claim 2, wherein the first type of centralized account for transactions in the first target transaction data and the second type of centralized account for transactions in the second target transaction data are both one; The comparing the transaction time of the first target transaction data with the transaction time of the second target transaction data, and comparing the transaction amount of the first target transaction data with the transaction amount of the second target transaction data to determine whether the first target transaction data matches the second target transaction data, includes: If the time difference between the transaction time of the first target transaction data and the transaction time of the second target transaction data meets a first threshold, and the transaction amount of the first target transaction data is consistent with the transaction amount of the second target transaction data, it is determined that the first target transaction data matches the second target transaction data.

4. The method according to claim 2, wherein the first target transaction data includes multiple first-type centralized accounts for transactions, and these multiple first-type centralized accounts belong to the same organization; and / or, the second target transaction data includes multiple first-type decentralized accounts for transactions, and these multiple first-type decentralized accounts belong to the same organization; The comparing the transaction time of the first target transaction data with the transaction time of the second target transaction data, and comparing the transaction amount of the first target transaction data with the transaction amount of the second target transaction data to determine whether the first target transaction data matches the second target transaction data, includes: Determining a first transaction time based on a transaction time of at least one first-type centralized account in the first target transaction data, and determining a second transaction time based on a transaction time of at least one first-type decentralized account in the second target transaction data; Determining a first transaction amount statistical value based on the transaction amount of at least one first-type centralized account in the first target transaction data, and determining a second transaction amount statistical value based on the transaction amount of at least one first-type decentralized account in the second target transaction data; If the time difference between the first transaction time and the second transaction time meets a second threshold, and the first transaction amount statistical value is consistent with the second transaction amount statistical value, it is determined that the first target transaction data matches the second target transaction data.

5. The method according to claim 2, before unifying the transaction amount of the first target transaction data and the transaction amount of the second target transaction data into the same asset measurement dimension, the method further comprises: Based on the account type of the first type of centralized account in the first target transaction data and / or the account type of the first type of decentralized account in the second target transaction data, determine the asset conversion ratio between the transaction amount of the first target transaction data and the transaction amount of the second target transaction data.

6. The method according to claim 1, wherein after obtaining a first type of transaction data set of a first type of centralized account in a centralized trading platform and, for a first type of decentralized account known to be associated with the first type of centralized account, determining a second type of transaction data set in the decentralized trading platform, the method further comprises: Data cleaning is performed on the first-category transaction data set and the second-category transaction data set, wherein the data cleaning includes at least one of data deduplication, data format conversion, and data standardization.

7. The method according to claim 1, after creating an association relationship between the second type of decentralized account and the second type of centralized account, the method further comprises: Determining whether the second-type centralized account is an abnormal account based on the account information of the second-type centralized account; In the case that the second type of centralized account is an abnormal account, an alarm message is generated in response to the second type of centralized account and / or the second type of decentralized account triggering a transaction behavior.

8. The method according to claim 1, further comprising: For multiple first-type centralized accounts known to be associated with first-type decentralized accounts, obtain identity identification information of each of the first-type centralized accounts; For any two first-type centralized accounts among the multiple first-type centralized accounts, if the identity identification information of the two first-type centralized accounts meets the specified conditions, tag information is added to the two first-type centralized accounts, and the tag information is used to indicate that the two first-type centralized accounts belong to the same organization.

9. The method according to claim 8, characterized in that The identity identification information includes at least one of the following: The account's network address information; Device identification information of the transaction device used by the account; The account's network connection information; The account's registered address information; The account's active address information.

10. An account association device, comprising: an acquisition module, configured to acquire a first type of transaction data set of a first type of centralized account in a centralized trading platform, and, for a first type of decentralized account known to be associated with the first type of centralized account, determine a second type of transaction data set of the first type of decentralized account in the decentralized trading platform; a determination module configured to, if transaction information between first target transaction data in the first type of transaction data set and second target transaction data in the second type of transaction data set matches, respectively determine: a second type of centralized account in the first target transaction data that transacts with the first type of centralized account, and a second type of decentralized account in the second target transaction data that transacts with the first type of decentralized account; A creation module is used to create an association relationship between the second type of decentralized account and the second type of centralized account.

11. A computing device comprising: processor; A memory for storing processor-executable instructions; wherein the processor implements the steps of the method according to any one of claims 1 to 9 by executing the executable instructions.

12. A computer-readable storage medium having computer instructions stored thereon, wherein when the computer instructions are executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.

13. A computer program product comprising a computer program / instruction, which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 9.

Images