Account identification method and device, storage medium, product and electronic equipment

Abstract

The invention provides an account identification method and device, a storage medium, a product and electronic equipment, and the method is applied to the technical field of computers, and comprises the steps: obtaining a target initialization asynchronous command in a command database, obtaining a target user account corresponding to the target initialization asynchronous command, and storing the target user account corresponding to the target initialization asynchronous command; and obtaining a homologous relationship of the target user account in a user information database, obtaining a natural person identifier corresponding to the target user account, and creating a homologous model corresponding to the natural person identifier based on the homologous relationship, the homologous model being used for identifying at least one user account associated with the same natural person.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more particularly, to an account identification method, device, storage medium, product, and electronic device in the field of computer technology. Background Art

[0002] Users can register accounts on Internet platforms using different certificates, resulting in a situation where a natural person is associated with multiple different user accounts. To facilitate user information management and Internet information security, in the prior art, when a user logs in to an account, other accounts corresponding to the certificate of the user account can be queried on the corresponding platform to confirm the identity of the natural person. However, it can be understood that the number of accounts successfully registered on the Internet platform is huge, and user certificates often change. Confirming the identity of a natural person through real-time querying is inefficient, inaccurate, and not timely. Therefore, a convenient and accurate account identification method is needed. Summary of the Invention

[0003] Embodiments of this application provide an account identification method, device, storage medium, product, and electronic device. This method can determine the homology relationship by pulling offline data and querying the user information database, and establish a homology model corresponding to the natural person according to the homology relationship, facilitating the confirmation of associated user accounts through the homology model, and improving the convenience and accuracy of querying the homology relationship.

[0004] In a first aspect, embodiments of this application provide an account identification method, the method including:

[0005] Obtain a target initialization asynchronous command in a command database, and obtain a target user account corresponding to the target initialization asynchronous command;

[0006] Obtain the homology relationship of the target user account in a user information database, and obtain a natural person identifier corresponding to the target user account;

[0007] Create a homology model corresponding to the natural person identifier based on the homology relationship, where the homology model is used to identify at least one user account associated with the same natural person.

[0008] Through the above technical solution, it is possible to determine the homology relationship by pulling offline data and querying the user information database, and establish a homology model corresponding to the natural person according to the homology relationship, facilitating the confirmation of associated user accounts through the homology model, and improving the convenience and accuracy of querying the homology relationship.

[0009] In combination with the first aspect, in some possible implementation manners, before obtaining the target initialization asynchronous command in the command database, further include:

[0010] Clean the offline user data to obtain the user accounts in the offline user data;

[0011] Generate corresponding initialization asynchronous commands for each user account and save the initialization asynchronous commands in the command database.

[0012] Through the above technical solution, while ensuring the uniqueness of user accounts, it reduces data errors and redundancy, improves the efficiency of creating a homologous model, saves the initialization asynchronous commands in the database, and realizes the reasonable allocation of resources.

[0013] Combined with the first aspect, in some possible implementation manners, obtaining the target initialization asynchronous command in the command database includes:

[0014] Obtain the target initialization asynchronous command in the command database according to a preset speed.

[0015] Through the above technical solution, obtaining the target initialization asynchronous command in the command database according to a preset speed realizes speed control for retrieving the initialization asynchronous command, and further ensures the security and stability of the platform operation.

[0016] Combined with the first aspect, in some possible implementation manners, obtaining the homologous relationship of the target user account in the user information database and obtaining the natural person identifier corresponding to the target user account includes:

[0017] Obtain the natural person identifier corresponding to the target user account in the user information database;

[0018] Obtain the first user account corresponding to the natural person identifier, and generate the homologous relationship between the target user account and the first user account.

[0019] Through the above technical solution, determining the homologous relationship between user accounts according to the natural person identifier improves the accuracy of determining the homologous relationship and further improves the accuracy of the homologous model.

[0020] Combined with the first aspect, in some possible implementation manners, the method further includes:

[0021] Obtain the weak homologous relationship of the target user account in the user information database;

[0022] The creating the homologous model corresponding to the natural person identifier based on the homologous relationship includes:

[0023] Create the homologous model corresponding to the natural person identifier based on the homologous relationship and the weak homologous relationship.

[0024] Through the above technical solution, the historical traceability ability of the homologous model for the natural person associated user account is realized, the reliability and accuracy of the homologous model are further improved, and the risk control ability of the service platform is enhanced.

[0025] Combined with the first aspect, in some possible implementation manners, obtaining the weak homologous relationship of the target account in the user information database includes:

[0026] Obtaining the historical natural person identifiers used by the target user account in the user information database;

[0027] Obtaining the second user account corresponding to the historical natural person identifier, and generating a weak homologous relationship between the target user account and the second user account.

[0028] Through the above technical solution, determining the weak homologous relationship between user accounts according to the historical natural person identifier improves the accuracy of determining the weak homologous relationship and further improves the accuracy of the homologous model.

[0029] Combined with the first aspect, in some possible implementation manners, creating the homologous model corresponding to the natural person identifier based on the homologous relationship includes:

[0030] If there is no homologous model corresponding to the natural person identifier, creating a homologous model corresponding to the natural person identifier based on the homologous relationship;

[0031] If there is a homologous model corresponding to the natural person identifier, performing an update process on the homologous model corresponding to the natural person identifier based on the homologous relationship.

[0032] Through the above technical solution, judging whether there is a homologous model, and choosing to create a homologous model or update a homologous model, avoiding repeated creation of the homologous model, saving computing resources, and avoiding dispersion of the homologous relationship and improving the accuracy of the homologous model.

[0033] Combined with the first aspect, in some possible implementation manners, the method further includes:

[0034] Receiving the transaction data application information of the target user account and the target transaction data application value corresponding to the transaction data application information;

[0035] Using the homologous model to obtain other user accounts associated with the same natural person as the target user account, and obtaining the total transaction data application value of the other user accounts;

[0036] If the sum of the target transaction data application value and the total transaction data application value is less than the application quota threshold, passing the transaction data application information.

[0037] Through the above technical solution, a homologous model is used to obtain other user accounts of the same natural person, so as to trace the total transaction data application value of the natural person, avoid over-issuance of transaction data, and further improve the security of the service platform.

[0038] In a second aspect, an embodiment of the present application provides an account identification device, which includes:

[0039] An initialization command acquisition unit, configured to acquire a target initialization asynchronous command in a command database, and acquire a target user account corresponding to the target initialization asynchronous command;

[0040] A homologous relationship acquisition unit, configured to acquire the homologous relationship of the target user account in a user information database, and acquire a natural person identifier corresponding to the target user account;

[0041] A homologous model creation unit, configured to create a homologous model corresponding to the natural person identifier based on the homologous relationship, where the homologous model is used to identify at least one user account held by the same natural person.

[0042] In a third aspect, an embodiment of the present application provides a computer storage medium, which stores multiple instructions, and the instructions are suitable for being loaded and executed by a processor to perform the above method steps.

[0043] In a fourth aspect, an embodiment of the present application provides a computer program product, which stores multiple instructions, and the instructions are suitable for being loaded and executed by a processor to perform the above method steps.

[0044] In a fifth aspect, an embodiment of the present application provides an electronic device, which may include: a processor and a memory; wherein, the memory stores a computer program, and the computer program is suitable for being loaded and executed by the processor to perform the above method steps.

[0045] In one or more embodiments of the present application, a target initialization asynchronous command is acquired in a command database, a target user account corresponding to the target initialization asynchronous command is acquired, the homologous relationship of the target user account is acquired in a user information database, and a natural person identifier corresponding to the target user account is acquired. A homologous model corresponding to the natural person identifier is created based on the homologous relationship, and the homologous model is used to identify at least one user account associated with the same natural person. By pulling offline data and querying the user information database to determine the homologous relationship, and establishing a homologous model corresponding to the natural person according to the homologous relationship, it is convenient to confirm the associated user accounts through the homologous model, and the convenience and accuracy of querying the homologous relationship are improved. Description of the Drawings

[0046] To more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the accompanying drawings required for the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other accompanying drawings can be obtained based on these drawings.

[0047] Figure 1 It is a schematic diagram of a scenario for constructing a homologous model provided by an embodiment of the present application;

[0048] Figure 2 It is a schematic flowchart of an account recognition method provided by an embodiment of the present application;

[0049] Figure 3 It is a schematic flowchart of an offline cleaning process for user data provided by an embodiment of the present application;

[0050] Figure 4 It is a schematic flowchart of a process for obtaining homologous relationships provided by an embodiment of the present application;

[0051] Figure 5 It is a schematic flowchart of a process for obtaining weak homologous relationships provided by an embodiment of the present application;

[0052] Figure 6 It is a schematic flowchart of a process for updating a homologous model provided by an embodiment of the present application;

[0053] Figure 7 It is a schematic flowchart of a process for applying a homologous model provided by an embodiment of the present application;

[0054] Figure 8 It is a schematic structural diagram of an account recognition device provided by an embodiment of the present application;

[0055] Figure 9 It is a schematic structural diagram of an account recognition device provided by an embodiment of the present application;

[0056] Figure 10 It is a schematic structural diagram of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0057] The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, rather than all embodiments. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present application.

[0058] A natural person refers to a person with natural life, which can represent an individual who obtains the qualification of a civil subject based on natural birth. Nowadays, a natural person can also register accounts in different ways, so that a natural person can have multiple different accounts. For example, a natural person can use a mobile phone number, an email, or even the device number of the terminal device held to register different accounts. However, for the need to protect the security of the service platform and facilitate the management of platform accounts, it is necessary to identify the natural person identity of the user through the account and associate multiple accounts with the same natural person identity, so as to facilitate the tracing and management of account behaviors. For example, when a natural person registers an account, they need to fill in identity information, so that the service platform can determine that the accounts belong to the same natural person through the same identity information. Among them, the identity information can be a mobile phone number or an identity document number, etc. For example, in a service platform applied to a financial scenario, the application limit for transaction data of the same natural person is limited. Among them, the transaction data can be assets, tradable goods such as goods, or rights relationships such as bonds and stocks that can be transferred. When an account sends transaction data application information to the service platform to obtain transaction data from the service platform, the service platform can trace all the accounts corresponding to the natural person of this account to determine the situation of the natural person applying for transaction data through the accounts under their name, so as to determine whether to send transaction data to this account. If every time an account behavior is detected, the service platform queries all account information to trace the natural person, it will cause excessive computing pressure on the service platform server, and even cause the service platform to freeze and affect the normal use of users. And in real life, the identity information of a natural person may change, and the service platform cannot judge the relationship between different accounts through the identity information, and even wrongly identify them as two different natural persons.

[0059] The embodiment of the present application provides an account identification device, which can identify the homologous relationship between different accounts by creating a homologous model. Among them, the homologous relationship represents the relationship used to associate different accounts to the same natural person, and can also be called the same-person relationship. The homologous model is used to associate accounts with a homologous relationship. The account identification method provided by the embodiment of the present application can be implemented depending on a computer program and can run on an account identification device based on the von Neumann architecture. This computer program can be integrated in an application or run as an independent tool application. Please refer to Figure 1, This application provides a schematic diagram of a scenario for constructing a homologous model. The command database may contain initialization asynchronous commands corresponding to each user account. The initialization asynchronous commands are used to indicate the creation of a homologous model for the user account. After the account recognition device obtains the target user account corresponding to the initialization asynchronous command, it can obtain the relevant information of the target user account from the user information database. The relevant information summary may include the homologous relationship of the target user account, so as to create a homologous model according to the relevant information. After that, the account recognition device can directly use the homologous model to quickly determine the homologous relationship of the target user account, determine other accounts under the same natural person, and improve the efficiency of homologous relationship recognition. Among them, due to the huge workload of collecting user account information, the account recognition device can directly access the user information database of the service platform. The user information database may store the information of all user accounts registered on the service platform. The service platform may be the network platform on which the account recognition device is carried or other network platforms.

[0060] The following will describe in detail the account recognition method provided by this application in combination with specific embodiments.

[0061] Please refer to Figure 2 , This application provides a schematic flowchart of an account recognition method. As Figure 2 shown, the method of this application embodiment may include the following steps S102-S106.

[0062] S102, Obtain a target initialization asynchronous command in the command database, and obtain the target user account corresponding to the target initialization asynchronous command.

[0063] Specifically, the command database stores initialization asynchronous commands for each user account. The initialization asynchronous commands are used to indicate that the account recognition device establishes a homologous model for the user account. The asynchronous command reduces resource occupancy in a non-blocking manner. It can enable the account recognition device to continue to process other tasks without waiting for the operation to complete when performing operations, reducing the system waiting time. The account recognition device can obtain the target initialization asynchronous command in the command database. The target initialization asynchronous command is any initialization asynchronous command in the command database. It can be understood that after the account recognition device obtains the target initialization asynchronous command, it can delete the target initialization asynchronous command from the command database, and then obtain the target user account corresponding to the target initialization asynchronous command, that is, the target initialization asynchronous command is used to indicate the establishment of a homologous model for the target user account.

[0064] S104, Obtain the homologous relationship of the target user account in the user information database, and obtain the natural person identifier corresponding to the target user account.

[0065] Specifically, after obtaining the target user account, it is possible to search in the user information based on the target user account, so as to obtain the homologous relationship of the target user account. The homologous relationship may include other user accounts that belong to the same natural person as the target user account, and it is also possible to obtain the natural person identifier corresponding to the target user account. Among them, the natural person identifier may be the identity information of the natural person, and one natural person identifier corresponds to one natural person.

[0066] S106. Create a homologous model corresponding to the natural person identifier based on the homologous relationship. The homologous model is used to identify at least one user account associated with the same natural person.

[0067] Specifically, the account recognition device can create a homologous model corresponding to the natural person identifier based on the homologous relationship. One natural person corresponds to one homologous model. Since the homologous model is created based on the homologous relationship, the homologous model can be used to identify at least one user account associated with the same natural person.

[0068] In the embodiment of the present application, obtain the target initialization asynchronous command in the command database, obtain the target user account corresponding to the target initialization asynchronous command, obtain the homologous relationship of the target user account in the user information database, and obtain the natural person identifier corresponding to the target user account. Create a homologous model corresponding to the natural person identifier based on the homologous relationship. The homologous model is used to identify at least one user account associated with the same natural person. By pulling offline data and querying the user information database to determine the homologous relationship, and establishing a homologous model corresponding to the natural person according to the homologous relationship, it is convenient to confirm the associated user accounts through the homologous model, improving the convenience and accuracy of homologous relationship query.

[0069] Please refer to Figure 3 , which provides a schematic flow chart of user data offline cleaning for the embodiment of the present application. In one or more embodiments of the present application, the steps S202-S204 may be included before the step S102.

[0070] S202. Clean the offline user data to obtain the user accounts in the offline user data.

[0071] Specifically, the account recognition device can obtain the offline user data of the loaded network platform. The offline user data refers to the data that can still be collected, stored, and used when the user device is in the offline state, and may include the behavior records, preference settings, operation records, etc. of the user account. Then, the offline user data can be cleaned to obtain the user accounts in the offline data.

[0072] Optionally, the cleaning process may include processes such as removing duplicate data and correcting incorrect data, so as to remove duplicate user account records in the offline user data, ensure the uniqueness of each user account, and avoid problems of duplicate calculations during the subsequent creation of the homologous model.

[0073] S204. Generate corresponding initialization asynchronous commands for each user account and save the initialization asynchronous commands in the command database.

[0074] Specifically, corresponding initialization asynchronous commands can be generated for each user account obtained through the cleaning process. The initialization asynchronous commands are used to indicate the generation of a homologous model for the corresponding user account. Then, the generated initialization asynchronous commands can be saved in the command data, so that the homologous relationship asynchronous device dynamically schedules the initialization asynchronous commands according to the current operating conditions, realizes the reasonable allocation of system resources, and thus improves the overall performance.

[0075] In the embodiment of the present application, the offline user data is cleaned to obtain the user accounts in the offline user data. Corresponding initialization asynchronous commands are generated for each user account, and the initialization asynchronous commands are saved in the command database. By cleaning the duplicate and incorrect offline user data, while ensuring the uniqueness of the user accounts, data errors and redundancies are reduced, the efficiency of creating the homologous model is improved, and the initialization asynchronous commands are saved in the database, realizing the reasonable allocation of resources.

[0076] The account recognition device can save the initialization asynchronous commands corresponding to all user accounts in the command data. Therefore, the number of initialization asynchronous commands is huge. The account recognition device can control the fetching of the initialization asynchronous commands according to the operating conditions of the loaded network platform server and its own operating conditions, so as to realize the reasonable allocation of system resources.

[0077] In one or more embodiments of the present application, step S102 may include the following steps:

[0078] Obtain the target initialization asynchronous command in the command database according to the preset speed.

[0079] Specifically, the account recognition device can fetch the target initialization asynchronous command from the command database according to the preset speed. The preset speed may include that the account recognition device obtains a preset number of initialization asynchronous commands from the command database every preset time period. The target initialization asynchronous command is any one of the fetched initialization asynchronous commands. Among them, the preset speed, the preset time period, and the preset number can be the initial settings of the account recognition device, or can be set by the user or relevant staff.

[0080] Optionally, the preset speed can be related to the specific operation of the account recognition device, which can detect the current operation situation and adjust the preset speed based on the current operation situation, so as to control the speed of fetching the initialization asynchronous command, further ensuring the security and stability of the platform operation and avoiding affecting other normal operations of the platform.

[0081] In the embodiment of the present application, by obtaining the target initialization asynchronous command in the command database according to the preset speed, the speed control of fetching the initialization asynchronous command is realized, further ensuring the security and stability of the platform operation.

[0082] Since the homologous relationship represents the relationship used to associate different accounts to the same natural person, when the account recognition device obtains the homologous relationship in the user information database, it can first determine the natural person corresponding to the target user account, and then determine other user accounts associated with the natural person.

[0083] Please refer to Figure 4 , which provides a schematic flow chart of obtaining the homologous relationship in the embodiment of the present application. In one or more embodiments of the present application, the step S104 may include the following steps S302 - S304.

[0084] S302, obtain the natural person identifier corresponding to the target user account in the user information database.

[0085] Specifically, when the user account is registered, the corresponding natural person identifier can be filled in according to the requirements of the service platform. Among them, the natural person identifier can be the identity information of the natural person, such as the ID number, mobile phone number, etc. Therefore, the account recognition device can obtain the natural person identifier corresponding to the target user account in the user information database.

[0086] S304, obtain the first user account corresponding to the natural person identifier, and generate the homologous relationship between the target user account and the first user account.

[0087] Specifically, after obtaining the natural person identifier, the user accounts associated with the natural person identifier can be found in the user information database, and these accounts are confirmed as the first user accounts. That is, when the first user account is registered, the natural person identifier is also filled in. Therefore, both the target user account and the first user account are user accounts under the natural person identifier, and the account recognition device can generate the homologous relationship between the target user account and the first user account.

[0088] In an embodiment of the present application, a natural person identifier corresponding to a target user account is obtained from a user information database, a first user account corresponding to the natural person identifier is obtained, and a homologous relationship between the target user account and the first user account is generated. Determining the homologous relationship between user accounts through the natural person identifier improves the accuracy of determining the homologous relationship and further improves the accuracy of the homologous model.

[0089] In real life, the identity information of a natural person may change, that is, the natural person identifier will also change. A user can change the natural person identifier corresponding to a user account on a service platform, and the previously used and changed natural person identifier of the user can be referred to as a historical natural person identifier.

[0090] In one or more embodiments of the present application, the account identification method may further include the following steps:

[0091] Obtain the weak homologous relationship of the target user account from the user information database.

[0092] Specifically, in order to improve the accuracy of the homologous model and the historical traceability ability of the homologous model, in addition to obtaining the homologous relationship from the user information database, the account identification device can also obtain the weak homologous relationship of the target user account. The weak homologous relationship is the relationship between user accounts indicating that there has been a historical intersection between natural person identifiers, and can also be referred to as a weak same-person relationship. For example, if the natural person identifier of user account A is the same as the historical natural person identifier of user account B, or the historical natural person identifier of user account A is the same as the natural person identifier of user account B, it can be determined that there is a weak homologous relationship between user account A and user account B.

[0093] The step S106 may include the following steps:

[0094] Create a homologous model corresponding to the natural person identifier based on the homologous relationship and the weak homologous relationship.

[0095] Specifically, the account identification device can create a homologous model corresponding to the natural person identifier based on the homologous relationship and the weak homologous relationship, so that the homologous model can not only identify at least one user account currently associated with the same natural person identifier, but also call the weak homologous relationship to trace the user accounts previously associated with the natural person identifier.

[0096] In an embodiment of the present application, the weak homologous relationship of the target user account is obtained from the user information database, and a homologous model corresponding to the natural person identifier is created based on the homologous relationship and the weak homologous relationship. By establishing the homologous model in combination with the weak homologous relationship, the historical traceability ability of the homologous model for the user accounts associated with the natural person is realized, further improving the reliability and accuracy of the homologous model and enhancing the risk control ability of the service platform.

[0097] Please refer to Figure 5 , which provides an example schematic diagram for obtaining weak homologous relationships in the embodiments of the present application. In one or more embodiments of the present application, the step of obtaining the weak homologous relationship of the target user account in the user information database may include the following steps S402 - S404.

[0098] S402, obtain the historical natural person identifiers used by the target user account in the user information database.

[0099] Specifically, in addition to storing the natural person identifier currently associated with the user account, the user information database can also store the historical natural person identifiers used previously. Therefore, the account recognition device can obtain the historical natural person identifiers used by the target user account in the user information database, which is convenient for generating weak homologous relationships subsequently.

[0100] S404, obtain the second user account corresponding to the historical natural person identifier, and generate a weak homologous relationship between the target user account and the second user account.

[0101] Specifically, after obtaining the historical natural person identifier, the second user account corresponding to the historical natural person identifier can be obtained in the user information database. The current natural person identifier of the second user account can be this historical natural person identifier, or the historical natural person identifier of the second user account can be the same as the historical natural person identifier of the target user account. Therefore, there is a historical intersection between the natural person identifiers of the second user account and the target user account, and a weak homologous relationship between the target user account and the second user account can be generated.

[0102] In the embodiments of the present application, obtain the historical natural person identifiers used by the target user account in the user information database, obtain the second user account corresponding to the historical natural person identifier, and generate a weak homologous relationship between the target user account and the second user account. Determining the weak homologous relationship between user accounts through historical natural person identifiers improves the accuracy of determining the weak homologous relationship and further improves the accuracy of the homologous model.

[0103] Since the initialization asynchronous command is corresponding to the user account, and different user accounts may correspond to the same natural person identifier, there may be a situation where after obtaining the target user account corresponding to the target initialization asynchronous command, the natural person identifier corresponding to the target user account has already created a homologous model. To avoid repeatedly creating homologous models for the same natural person identifier and to avoid the situation of scattered and incomplete homologous relationships, after obtaining the natural person identifier of the target user account, it can be first determined whether a homologous model has been created for this natural person identifier.

[0104] Please refer to Figure 6, This is an example schematic diagram for updating a homologous model provided by an embodiment of the present application. In one or more embodiments of the present application, step S106 may include the following steps S502 - S504.

[0105] S502, If there is no homologous model corresponding to the natural person identifier, create a homologous model corresponding to the natural person identifier based on the homologous relationship.

[0106] Specifically, if the account recognition device has not created a homologous model for the natural person identifier, that is, there is no homologous model corresponding to the natural person identifier, a homologous model corresponding to the natural person identifier can be created based on the obtained homologous relationship.

[0107] Optionally, if there is no homologous model corresponding to the natural person identifier and a weak homologous relationship of the natural person identifier is obtained, a homologous model corresponding to the natural person identifier can be created based on the homologous relationship and the weak homologous relationship.

[0108] S504, If there is a homologous model corresponding to the natural person identifier, perform an update process on the homologous model corresponding to the natural person identifier based on the homologous relationship.

[0109] Specifically, if the account recognition device has already created a homologous model for the natural person identifier, that is, there is a homologous model corresponding to the natural person identifier, there is no need to repeatedly create a homologous model. Instead, an update process can be performed on the homologous model corresponding to the natural person identifier based on the obtained homologous relationship. For example, the homologous relationship between the target user account and the first user account can be added to the homologous model.

[0110] Optionally, if there is a homologous model corresponding to the natural person identifier and a weak homologous relationship of the natural person identifier is obtained, an update process can be performed on the homologous model corresponding to the natural person identifier based on the homologous relationship and the weak homologous relationship.

[0111] In an embodiment of the present application, if there is no homologous model corresponding to the natural person identifier, a homologous model corresponding to the natural person identifier is created based on the homologous relationship. If there is a homologous model corresponding to the natural person identifier, an update process is performed on the homologous model corresponding to the natural person identifier based on the homologous relationship. By determining whether there is a homologous model, choosing to create or update the homologous model avoids repeated creation of the homologous model, saves computing resources, and avoids dispersion of the homologous relationship, improving the accuracy of the homologous model.

[0112] After the homogenous model is created or updated for all user accounts, the created homogenous model can be used to identify homogenous relationships. For example, the target user account can be input into the homogenous model, and the homogenous model can determine other user accounts belonging to the same natural person as the target user account according to relevant homogenous relationships and / or weak homogenous relationships, which is convenient for tracing the behaviors of natural persons, thereby realizing the management of the service platform.

[0113] Please refer to Figure 7 , which provides an example schematic diagram of the application of the homogenous model for the embodiments of the present application. In one or more embodiments of the present application, the account identification method may further include the following steps S602-S606.

[0114] S602, receive the transaction data application information of the target user account and the target transaction data application value corresponding to the transaction data application information.

[0115] Specifically, when a user wants to apply for transaction data from the service platform, the user can send the transaction data application information to the service platform through the owned target user account. The transaction data application information contains the target transaction data application value desired by the user. Therefore, the transaction data application information can be used to request the service platform to distribute the transaction data that meets the target transaction data application value to the target user account. However, the service platform has a limited transaction data application quota for the same natural person. It is necessary to find the natural person corresponding to the target user account through the homogenous model and determine whether other associated accounts have applied for transaction data, so as to judge whether to pass the transaction data application information. Therefore, when the account identification device receives the transaction data application information of the target user account, it can obtain the target transaction application value corresponding to the transaction data application information.

[0116] S604, use the homogenous model to obtain other user accounts associated with the same natural person as the target user account, and obtain the total transaction data application value of the other user accounts.

[0117] Specifically, the homogenous model can be used to obtain other user accounts associated with the same natural person as the target user account, that is, the other user accounts are all user accounts found by the homogenous model that have a homogenous relationship with the target user account. Then, the total transaction data application value of the other user accounts can be obtained. The transaction data application value is the total value of the transaction data applied for by the other user accounts.

[0118] Optionally, the account recognition device or service platform may classify the transaction data application information, and for transaction data application information of different levels, different strictness levels of homologous relationship recognition methods may be adopted. For example, the transaction data application information may be divided into a first level and a second level. For the transaction data application information of the first level, the homologous model may only use the homologous relationship to obtain other user accounts. For the transaction data application information of the second level, the homologous model may use both the homologous relationship and the weak homologous relationship to obtain other user accounts. Adopting different strictness levels of homologous relationship recognition methods for transaction data application information of different levels makes the management of the service platform more flexible.

[0119] For example, if the transaction data application information belongs to the first level, the homologous user account corresponding to the target user account is obtained using the homologous relationship in the homologous model, and the homologous user account is determined as another user account associated with the same natural person as the target user account. If the transaction data application information belongs to the second level, the homologous user account corresponding to the target user account is obtained using the homologous relationship in the homologous model, and the weak homologous user account corresponding to the target user account is obtained using the weak homologous relationship in the homologous model. The homologous user account and the weak homologous user account are determined as other user accounts associated with the same natural person as the target user account.

[0120] S606, if the sum of the target transaction data application value and the total transaction data application value is less than the application quota threshold, the transaction data application information is passed.

[0121] Specifically, the sum of the target data application value and the total transaction data application value can be calculated. This sum value is the total value of the transaction data currently applied for by the natural person corresponding to the target user account. If the sum of the target transaction data application value and the total transaction data application value is less than the application quota threshold, it means that the transaction data applied for by the natural person corresponding to the target user account does not exceed the application quota threshold. Then, the transaction data application information can be passed, and the transaction data meeting the target transaction data application value is issued to the target user account. Conversely, if the sum of the target transaction data application value and the total transaction data application value is greater than the application quota threshold, it means that the transaction data applied for by the natural person corresponding to the target user account will exceed the application quota threshold. Then, the transaction data application information is not passed, and a quota insufficient prompt message is sent to the target user account to prompt the corresponding natural person that the transaction data application quota is about to reach the upper limit.

[0122] In an embodiment of the present application, transaction data application information of a target user account and a target transaction data application value corresponding to the transaction data application information are received. A homologous model is used to obtain other user accounts associated with the same natural person as the target user account, and the total transaction data application value of the other user accounts is obtained. If the sum of the target transaction data application value and the total transaction data application value is less than the application quota threshold, the transaction data application information is passed. By using the homologous model to obtain other user accounts of the same natural person to trace the total transaction data application value of the natural person, over-issuance of transaction data is avoided, and the security of the service platform is further improved.

[0123] The following will combine the attached Figure 8 - attached Figure 9 , and introduce the account identification device provided by the embodiment of the present application in detail. It should be noted that the account identification device in the attached Figure 8 - attached Figure 9 is used to execute the method of the embodiment shown in the present application Figures 1 - 7 . For the sake of convenience of description, only the parts related to the embodiment of the present application are shown. For the specific technical details not disclosed, please refer to the embodiment shown in the present application Figures 1 - 7 .

[0124] Please refer to Figure 8 , which shows a schematic structural diagram of an account identification device provided by an exemplary embodiment of the present application. The account identification device can be implemented as all or part of the device through software, hardware, or a combination of both. The device 1 includes an initialization command acquisition unit 11, a homologous relationship acquisition unit 12, and a homologous model creation unit 13.

[0125] The initialization command acquisition unit 11 is configured to obtain a target initialization asynchronous command in a command database and obtain a target user account corresponding to the target initialization asynchronous command;

[0126] The homologous relationship acquisition unit 12 is configured to obtain a homologous relationship of the target user account in a user information database and obtain a natural person identifier corresponding to the target user account;

[0127] The homologous model creation unit 13 is configured to create a homologous model corresponding to the natural person identifier based on the homologous relationship, and the homologous model is used to identify at least one user account held by the same natural person.

[0128] In this embodiment, a target initialization asynchronous command is obtained from a command database, a target user account corresponding to the target initialization asynchronous command is obtained, a homology relationship of the target user account is obtained from a user information database, and a natural person identifier corresponding to the target user account is obtained. A homology model corresponding to the natural person identifier is created based on the homology relationship, and the homology model is used to identify at least one user account associated with the same natural person. By pulling offline data and querying the user information database to determine the homology relationship, and establishing a homology model corresponding to the natural person according to the homology relationship, it is convenient to confirm the associated user accounts through the homology model, improving the convenience and accuracy of homology relationship query.

[0129] Please refer to Figure 9 , which shows a schematic structural diagram of an account recognition device provided by an exemplary embodiment of the present application. The account recognition device can be implemented as all or part of the device through software, hardware, or a combination of both. The device 1 includes a cleaning processing unit 14, an initialization command acquisition unit 11, a homology relationship acquisition unit 12, a weak homology relationship acquisition unit 15, a homology model creation unit 13, and an application amount judgment unit 16.

[0130] The cleaning processing unit 14 is configured to perform cleaning processing on offline user data to obtain user accounts in the offline user data;

[0131] Generate corresponding initialization asynchronous commands for each user account and save the initialization asynchronous commands in the command database.

[0132] The initialization command acquisition unit 11 is configured to obtain a target initialization asynchronous command from the command database and obtain a target user account corresponding to the target initialization asynchronous command;

[0133] Optionally, the initialization command acquisition unit 11 is specifically configured to obtain a target initialization asynchronous command from the command database according to a preset speed.

[0134] The homology relationship acquisition unit 12 is configured to obtain the homology relationship of the target user account from the user information database and obtain a natural person identifier corresponding to the target user account;

[0135] Optionally, the homology relationship acquisition unit 12 is specifically configured to obtain a natural person identifier corresponding to the target user account from the user information database;

[0136] Obtain a first user account corresponding to the natural person identifier, and generate a homology relationship between the target user account and the first user account.

[0137] The weak homology relationship acquisition unit 15 is configured to obtain the weak homology relationship of the target user account from the user information database;

[0138] Optionally, the weak homology relationship obtaining unit 15 is specifically configured to obtain the historical natural person identifier used by the target user account in the user information database;

[0139] Obtain the second user account corresponding to the historical natural person identifier, and generate a weak homology relationship between the target user account and the second user account.

[0140] The homology model creation unit 13 is configured to create a homology model corresponding to the natural person identifier based on the homology relationship, and the homology model is used to identify at least one user account held by the same natural person.

[0141] Optionally, the homology model creation unit 13 is specifically configured to create a homology model corresponding to the natural person identifier based on the homology relationship and the weak homology relationship.

[0142] Optionally, the homology model creation unit 13 is specifically configured to, if there is no homology model corresponding to the natural person identifier, create a homology model corresponding to the natural person identifier based on the homology relationship;

[0143] If there is a homology model corresponding to the natural person identifier, update the homology model corresponding to the natural person identifier based on the homology relationship.

[0144] The application amount judgment unit 16 is configured to receive the transaction data application information of the target user account and the target transaction data application value corresponding to the transaction data application information;

[0145] Use the homology model to obtain other user accounts associated with the same natural person as the target user account, and obtain the total transaction data application value of the other user accounts;

[0146] If the sum of the target transaction data application value and the total transaction data application value is less than the application amount threshold, pass the transaction data application information.

[0147] In this embodiment, offline user data is cleaned to obtain user accounts in the offline user data. Initial asynchronous commands are generated for each user account and saved in the command database. By cleaning duplicate and incorrect offline user data, while ensuring the uniqueness of user accounts, data errors and redundancies are reduced, and the efficiency of creating a homologous model is improved. Saving the initial asynchronous commands in the database realizes the reasonable allocation of resources. By obtaining target initial asynchronous commands from the command database according to a preset speed and obtaining the target user accounts corresponding to the target initial asynchronous commands, speed control for retrieving the initial asynchronous commands is achieved, further ensuring the security and stability of the platform operation. The natural person identifier corresponding to the target user account is obtained from the user information database, and the first user account corresponding to the natural person identifier is obtained to generate a homologous relationship between the target user account and the first user account. Determining the homologous relationship between user accounts through the natural person identifier improves the accuracy of determining the homologous relationship and further improves the accuracy of the homologous model. The historical natural person identifiers used by the target user account are obtained from the user information database, and the second user accounts corresponding to the historical natural person identifiers are obtained to generate a weak homologous relationship between the target user account and the second user accounts. Based on the homologous relationship and the weak homologous relationship, a homologous model corresponding to the natural person identifier is created. By establishing a homologous model in combination with the weak homologous relationship, the historical tracing ability of the homologous model for natural person-related user accounts is realized. If there is no homologous model corresponding to the natural person identifier, a homologous model corresponding to the natural person identifier is created based on the homologous relationship. If there is a homologous model corresponding to the natural person identifier, the homologous model corresponding to the natural person identifier is updated based on the homologous relationship. By judging whether there is a homologous model and selecting to create or update the homologous model, duplicate creation of the homologous model is avoided, computing resources are saved, and the dispersion of homologous relationships is avoided, improving the accuracy of the homologous model. The transaction data application information of the target user account and the target transaction data application value corresponding to the transaction data application information are received. Other user accounts associated with the same natural person as the target user account are obtained using the homologous model, and the total transaction data application value of the other user accounts is obtained. If the sum of the target transaction data application value and the total transaction data application value is less than the application quota threshold, the transaction data application information is passed. By obtaining other user accounts of the same natural person using the homologous model to trace the total transaction data application value of the natural person, over-issuance of transaction data is avoided, further improving the security of the service platform.

[0148] It should be noted that when the account identification device provided in the above embodiments executes the account identification method, only the division of the above functional modules is used for illustration. In actual applications, the above functions can be assigned to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the account identification device provided in the above embodiments and the embodiments of the account identification method belong to the same concept. The implementation process is detailed in the method embodiments and will not be repeated here.

[0149] The serial numbers of the embodiments of the present application are only for description and do not represent the advantages and disadvantages of the embodiments.

[0150] The embodiments of the present application also provide a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded and executed by a processor to perform the account identification method as described in the above Figures 1 - 7 embodiments shown. The specific execution process can be referred to Figures 1 - 7 the specific description of the embodiments shown and will not be repeated here.

[0151] The present application also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor to perform the account identification method as described in the above Figures 1 - 7 embodiments shown. The specific execution process can be referred to Figures 1 - 7 the specific description of the embodiments shown and will not be repeated here.

[0152] Please refer to Figure 10 , which shows a block diagram of the structure of an electronic device provided by an exemplary embodiment of the present application. The electronic device in the present application may include one or more of the following components: a processor 110, a memory 120, an input device 130, an output device 140, and a bus 150. The processor 110, the memory 120, the input device 130, and the output device 140 may be connected through the bus 150.

[0153] The processor 110 may include one or more processing cores. The processor 110 connects various parts within the entire electronic device using various interfaces and lines, and executes various functions of the terminal 100 and processes data by running or executing instructions, programs, code sets, or instruction sets stored in the memory 120, and by invoking data stored in the memory 120. Optionally, the processor 110 may be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), or programmable logic array (PLA). The processor 110 may integrate a combination of one or several of a central processing unit (CPU), a graphics processing unit (GPU), and a modem, etc. Among them, the CPU mainly processes the operating system, user interfaces, and application programs, etc.; the GPU is responsible for rendering and drawing display content; the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 110 and may be implemented separately by a communication chip.

[0154] The memory 120 may include random access memory (RAM) and may also include read-only memory (ROM). Optionally, the memory 120 includes a non-transitory computer-readable storage medium. The memory 120 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 120 may include a program storage area and a data storage area. Among them, the program storage area may store instructions for implementing the operating system, instructions for implementing at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc. The operating system may be the Android system, including a system developed based on the Android system in depth, the IOS system developed by Apple Inc., including a system developed based on the IOS system in depth, or other systems.

[0155] The memory 120 can be divided into an operating system space and a user space. The operating system runs in the operating system space, and native and third-party application programs run in the user space. To ensure that different third-party application programs can achieve good running effects, the operating system allocates corresponding system resources for different third-party application programs. However, there are also differences in the system resource requirements of different application scenarios in the same third-party application program. For example, in the local resource loading scenario, the third-party application program has a higher requirement for the disk read speed; in the animation rendering scenario, the third-party application program has a higher requirement for the GPU performance. Since the operating system and the third-party application program are independent of each other, the operating system often cannot timely perceive the current application scenario of the third-party application program, resulting in the operating system being unable to perform targeted system resource adaptation according to the specific application scenario of the third-party application program.

[0156] To enable the operating system to distinguish the specific application scenarios of third-party application programs, it is necessary to establish data communication between the third-party application programs and the operating system, so that the operating system can obtain the current scenario information of the third-party application programs at any time, and then perform targeted system resource adaptation based on the current scenario.

[0157] Among them, the input device 130 is used to receive input instructions or data. The input device 130 includes, but is not limited to, a keyboard, a mouse, a camera, a microphone, or a touch device. The output device 140 is used to output instructions or data. The output device 140 includes, but is not limited to, a display device, a speaker, etc. In one example, the input device 130 and the output device 140 can be integrated, and the input device 130 and the output device 140 are a touch display screen.

[0158] The touch display screen can be designed as a full-screen, a curved screen, or a special-shaped screen. The touch display screen can also be designed as a combination of a full-screen and a curved screen, or a combination of a special-shaped screen and a curved screen. The embodiments of the present application do not limit this.

[0159] In addition, those skilled in the art can understand that the structure of the electronic device shown in the above drawings does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the drawings, or combine some components, or have different component arrangements. For example, the electronic device also includes components such as a radio frequency circuit, an input unit, a sensor, an audio circuit, a Wireless Fidelity (WiFi) module, a power supply, and a Bluetooth module, which will not be elaborated here.

[0160] In Figure 10 the electronic device shown, the processor 110 can be used to call the homology relationship recognition application program stored in the memory 120 and specifically perform the following operations:

[0161] Obtain a target initialization asynchronous command in the command database, and obtain the target user account corresponding to the target initialization asynchronous command;

[0162] Obtain the homology relationship of the target user account in the user information database, and obtain the natural person identifier corresponding to the target user account;

[0163] Create a homology model corresponding to the natural person identifier based on the homology relationship, where the homology model is used to identify at least one user account associated with the same natural person.

[0164] In one embodiment, before the processor 110 executes to obtain the target initialization asynchronous command in the command database, the following operations are further performed:

[0165] Clean the offline user data to obtain the user accounts in the offline user data;

[0166] Generate corresponding initialization asynchronous commands for each user account, and save the initialization asynchronous commands in the command database.

[0167] In one embodiment, when the processor 110 executes to obtain the homology relationship of the target user account in the user information database and obtain the natural person identifier corresponding to the target user account, the following operations are specifically performed:

[0168] Obtain the target initialization asynchronous command in the command database according to a preset speed.

[0169] In one embodiment, when the processor 110 executes to obtain the homology relationship of the target user account in the user information database and obtain the natural person identifier corresponding to the target user account, the following operations are specifically performed:

[0170] Obtain the natural person identifier corresponding to the target user account in the user information database;

[0171] Obtain the first user account corresponding to the natural person identifier, and generate the homology relationship between the target user account and the first user account.

[0172] In one embodiment, when the processor 110 executes the account recognition method, the following operations are further performed:

[0173] Obtain the weak homology relationship of the target user account in the user information database;

[0174] When executing to create the homology model corresponding to the natural person identifier based on the homology relationship, the following operations are specifically performed:

[0175] Create a homology model corresponding to the natural person identifier based on the homology relationship and the weak homology relationship.

[0176] In one embodiment, when the processor 110 executes to obtain the weak homology relationship of the target account in the user information database, the following operations are specifically performed:

[0177] Obtain the historical natural person identifier used by the target user account in the user information database;

[0178] Obtain the second user account corresponding to the historical natural person identifier, and generate a weak homology relationship between the target user account and the second user account.

[0179] In one embodiment, when the processor 110 executes to create a homology model corresponding to the natural person identifier based on the homology relationship, the following operations are specifically performed:

[0180] If there is no homology model corresponding to the natural person identifier, create a homology model corresponding to the natural person identifier based on the homology relationship;

[0181] If there is a homology model corresponding to the natural person identifier, perform an update process on the homology model corresponding to the natural person identifier based on the homology relationship.

[0182] In one embodiment, when the processor 110 executes the account identification method, the following operations are further performed:

[0183] Receive the transaction data application information of the target user account and the target transaction data application value corresponding to the transaction data application information;

[0184] Use the homology model to obtain other user accounts associated with the same natural person as the target user account, and obtain the total transaction data application value of the other user accounts;

[0185] If the sum of the target transaction data application value and the total transaction data application value is less than the application quota threshold, pass the transaction data application information.

[0186] In this embodiment, offline user data is cleaned to obtain user accounts in the offline user data. For each user account, a corresponding initialization asynchronous command is generated and saved in the command database. By cleaning duplicate and incorrect offline user data, while ensuring the uniqueness of user accounts, data errors and redundancies are reduced, and the efficiency of creating a homologous model is improved. Saving the initialization asynchronous command in the database realizes the reasonable allocation of resources. By obtaining a target initialization asynchronous command from the command database according to a preset speed and obtaining the target user account corresponding to the target initialization asynchronous command, the speed control for fetching the initialization asynchronous command is achieved, further ensuring the security and stability of the platform operation. The natural person identifier corresponding to the target user account is obtained from the user information database, and the first user account corresponding to the natural person identifier is obtained to generate a homologous relationship between the target user account and the first user account. Determining the homologous relationship between user accounts through the natural person identifier improves the accuracy of determining the homologous relationship and further improves the accuracy of the homologous model. The historical natural person identifiers used by the target user account are obtained from the user information database, and the second user account corresponding to the historical natural person identifier is obtained to generate a weak homologous relationship between the target user account and the second user account. Based on the homologous relationship and the weak homologous relationship, a homologous model corresponding to the natural person identifier is created. By establishing a homologous model in combination with the weak homologous relationship, the historical traceability ability of the homologous model for natural person-related user accounts is realized. If there is no homologous model corresponding to the natural person identifier, a homologous model corresponding to the natural person identifier is created based on the homologous relationship. If there is a homologous model corresponding to the natural person identifier, the homologous model corresponding to the natural person identifier is updated based on the homologous relationship. By judging whether there is a homologous model and choosing to create or update the homologous model, duplicate creation of the homologous model is avoided, computing resources are saved, and the dispersion of homologous relationships is avoided, improving the accuracy of the homologous model. The transaction data application information of the target user account and the target transaction data application value corresponding to the transaction data application information are received. Using the homologous model, other user accounts associated with the same natural person as the target user account are obtained, and the total transaction data application value of the other user accounts is obtained. If the sum of the target transaction data application value and the total transaction data application value is less than the application quota threshold, the transaction data application information is passed. By using the homologous model to obtain other user accounts of the same natural person to trace the total transaction data application value of the natural person, over-issuance of transaction data is avoided, further improving the security of the service platform.

[0187] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above methods. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only memory, or a random access memory, etc.

[0188] The above-disclosed are only the preferred embodiments of the present application. Of course, the scope of the rights of the present application cannot be limited thereby. Therefore, equivalent changes made according to the claims of the present application still fall within the scope covered by the present application.

[0189] It should be noted that the information (including but not limited to user equipment information, user personal information, etc.), data (including but not limited to data for analysis, stored data, displayed data, etc.), and signals involved in the embodiments of this specification are all authorized by the user or fully authorized by all parties. And the collection, use, and processing of relevant data need to comply with relevant laws, regulations, and standards of relevant countries and regions. For example, the initialization asynchronous commands, user accounts, natural person identifiers, etc. involved in this specification are all obtained under full authorization.

Claims

1. An account identification method, characterized in that: The method comprises: Obtain a target initialization asynchronous command in a command database, and obtain a target user account corresponding to the target initialization asynchronous command; Acquire the homology relationship of the target user account in a user information database, and acquire the natural person identifier corresponding to the target user account; A homology model corresponding to the natural person identifier is created based on the homology relationship, and the homology model is used to identify at least one user account associated with the same natural person.

2. The method according to claim 1, characterized in that Before obtaining the target initialization asynchronous command in the command database, the method further includes: Cleaning the offline user data to obtain the user account in the offline user data; A corresponding initialization asynchronous command is generated for each user account, and the initialization asynchronous command is stored in a command database.

3. The method according to claim 1, characterized in that The step of obtaining the target initialization asynchronous command in the command database includes: Gets target initialization asynchronous commands from the command database according to a preset speed.

4. The method according to claim 1, characterized in that: The acquiring the homology relationship of the target user account in the user information database and acquiring the natural person identifier corresponding to the target user account includes: Obtaining a natural person identifier corresponding to the target user account in a user information database; A first user account corresponding to the natural person identifier is obtained, and a homology relationship between the target user account and the first user account is generated.

5. The method according to claim 1, characterized in that The method further comprises: Acquire the weak homology relationship of the target user account in the user information database; The creating a homology model corresponding to the natural person identifier based on the homology relationship includes: Based on the homology relationship and the weak homology relationship, a homology model corresponding to the natural person identifier is created.

6. The method according to claim 5, characterized in that The acquiring the weak homology relationship of the target account in the user information database includes: Acquire, from the user information database, historical natural person identifiers used by the target user account; A second user account corresponding to the historical natural person identifier is obtained, and a weak homology relationship is generated between the target user account and the second user account.

7. The method according to any one of claims 1 to 5, characterized in that: The creating a homology model corresponding to the natural person identifier based on the homology relationship includes: If there is no homology model corresponding to the natural person identifier, creating a homology model corresponding to the natural person identifier based on the homology relationship; If a homology model corresponding to the natural person identifier exists, the homology model corresponding to the natural person identifier is updated based on the homology relationship.

8. The method according to claim 1, characterized in that The method further comprises: Receiving transaction data application information of the target user account and a target transaction data application value corresponding to the transaction data application information; Using the homology model to obtain other user accounts of the same natural person associated with the target user account, and obtaining total transaction data application values ​​of the other user accounts; If the sum of the target transaction data application value and the total transaction data application value is less than the application quota threshold, the transaction data application information is approved.

9. An account identification device, characterized in that: The device comprises: An initialization command acquisition unit, configured to acquire a target initialization asynchronous command from a command database, and acquire a target user account corresponding to the target initialization asynchronous command; A homology relationship acquisition unit, used to acquire the homology relationship of the target user account in a user information database, and acquire the natural person identifier corresponding to the target user account; A homology model creation unit is used to create a homology model corresponding to the natural person identifier based on the homology relationship, and the homology model is used to identify at least one user account held by the same natural person.

10. A computer storage medium, characterized in that: The computer storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 8.

11. A computer program product, characterized in that The computer program product stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 8.

12. An electronic device, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps as claimed in any one of claims 1 to 8.

Images