User identification method and its device, computer storage medium, and electronic device

Abstract

The present disclosure relates to a user identification method, an apparatus thereof, a computer storage medium, and an electronic device. The user identification method includes: obtaining real-time usage behavior description data corresponding to a current user using any application program; determining whether the current user is a new user or an existing user according to the real-time usage behavior description data and historical usage behavior description data; determining a unique user ID assigned to the current user according to the determined result; synchronizing the unique user ID assigned to the current user to the unique user ID field of the real-time usage behavior description data corresponding to the current user, so that the same current user using all the application programs has the same unique user ID, thereby effectively identifying the same user using multiple application programs.

Description

Technical Field

[0001] This application relates to the technical field of data processing, and particularly to a user identification method and its device, a computer storage medium, and an electronic device. Background Art

[0002] Out of consideration for meeting different user needs, generally, multiple application programs need to be developed. In order to analyze the behaviors of users using all application programs, it is necessary to collect the behavior data of users using all application programs and establish a one-to-one correspondence with the users. Therefore, effectively identifying the same user using multiple application programs has become a technical problem to be solved urgently. Summary of the Invention

[0003] Embodiments of this application provide a user identification method and its device, a computer storage medium, and an electronic device to overcome or alleviate the above technical problems existing in the prior art.

[0004] The technical solution adopted by this application is as follows:

[0005] A user identification method is applied to assign a unique user ID to a user using an application program. The user identification method includes:

[0006] Obtain the real-time usage behavior description data corresponding to the current user using any application program;

[0007] Determine whether the current user is a new user or an existing user according to the real-time usage behavior description data and the historical usage behavior description data;

[0008] Determine the unique user ID assigned to the current user according to the determined result;

[0009] Synchronize the unique user ID assigned to the current user to the unique user ID field of the real-time usage behavior description data corresponding to the current user, so that the same current user using all the application programs has the same unique user ID.

[0010] Optionally, before obtaining the real-time usage behavior description data corresponding to the current user using any application program, it includes:

[0011] Generate the real-time usage behavior description data corresponding to the current user using the any application program according to the buried point data collected by setting buried points on the any application program.

[0012] Optionally, the determining whether the current user is a new user or an existing user according to the real-time usage behavior description data and the historical usage behavior description data includes:

[0013] Determine whether the current user is a guest user or a logged-in user according to the real-time usage behavior data;

[0014] In response to the current user being a guest user, determine whether the current user is a new guest user or an existing guest user according to the relative identity identifier in the real-time usage behavior data;

[0015] In response to the current user being a logged-in user, determine whether the current user is a new logged-in user or an existing logged-in user according to the login ID in the real-time usage behavior data;

[0016] Wherein, the existing user is the existing guest user or the existing logged-in user; the new user is the new guest user or the new logged-in user.

[0017] Optionally, determining the unique user ID assigned to the current user according to the determined result includes:

[0018] In response to the new user being a new logged-in user, determine the absolute identity characteristic identifier submitted by the new logged-in user when registering in any application, search for the unique user ID in the unique user ID registration data of the existing logged-in users that has a one-to-one correspondence with the absolute identity characteristic identifier, and use the found unique user ID as the unique user ID of the new logged-in user;

[0019] If no unique user ID in the unique user ID registration data of the existing logged-in users that has a one-to-one correspondence with the absolute identity characteristic identifier is found, generate a unique user ID for the new logged-in user to determine the unique user ID assigned to the current user, and generate unique user ID registration data for the new logged-in user as the unique user ID registration data corresponding to the current user.

[0020] Optionally, after searching for the unique user ID in the unique user ID registration data of the existing logged-in users that has a one-to-one correspondence with the absolute identity characteristic identifier and using the found unique user ID as the unique user ID of the new logged-in user, it includes: generating unique user ID registration data for the current user according to the real-time behavior description data of the current user and the found unique user ID, and adding it to the user table, where the user table is used to manage the unique user ID registration data.

[0021] Optionally, in response to the current user being a guest user, determining whether the current user is a new guest user or an existing guest user according to the relative identity identifier in the real-time usage behavior data includes: using the device ID and application identifier in the real-time usage behavior data as the relative identity identifier to compare with the device ID and application identifier in the historical usage behavior data. If they are the same, it is determined that the current user is an existing guest user; otherwise, it is determined that the current user is a new guest user.

[0022] Optionally, determining the unique user ID assigned to the current user according to the determined result includes:

[0023] In response to the new user being a new guest user, generating a unique user ID for the new guest user to determine the unique user ID assigned to the current user, and generating unique user ID registration data for the new guest user as the unique user ID registration data corresponding to the current user.

[0024] Optionally, generating a unique user ID for the new guest user includes: generating the unique user ID for the new guest user according to the occurrence time node of the startup event and the device ID in the real-time usage behavior data.

[0025] Optionally, determining the unique user ID assigned to the current user according to the determined result includes:

[0026] In response to the current user being an existing user, querying the unique user ID assigned to the existing user in the historical usage behavior description data and using the queried unique user ID as the unique user ID assigned to the current user.

[0027] Optionally, the method includes: determining the unique user ID registration data of the existing guest user that needs to be repaired according to the unique user ID registration data corresponding to the current user.

[0028] Optionally, determining the unique user ID registration data of the existing guest user that needs to be repaired according to the unique user ID registration data corresponding to the current user includes: comparing the unique user ID registration data corresponding to the current user with the unique user ID registration data of the existing guest user;

[0029] If the same fields between the unique user ID registration data corresponding to the current user and the unique user ID registration data of the existing visitor users correspond to all the preset registration keyword fields, it is determined that the unique user ID registration data of the corresponding existing visitor users needs to be repaired, and the unique user ID corresponding to the current user is used to replace the unique user ID in the unique user ID registration data to be repaired.

[0030] Optionally, the registration keyword fields include a device ID field and an application identifier field. If the same fields are the device ID field and the application identifier field, and the number of the unique user ID registration data of the corresponding existing visitor users is not greater than the set number threshold, the unique user ID registration data of the corresponding existing visitor users is used as the object to be repaired.

[0031] A user identification device is applied to assign a unique user ID to a user using an application. The user identification device includes:

[0032] A data acquisition unit is configured to acquire real-time usage behavior description data corresponding to a current user using any application;

[0033] A user determination unit is configured to determine whether the current user is a new user or an existing user according to the real-time usage behavior description data and the historical usage behavior description data;

[0034] A user ID determination unit is configured to determine the unique user ID assigned to the current user according to the determined result;

[0035] A user ID synchronization unit is configured to synchronize the unique user ID assigned to the current user to the unique user ID field of the real-time usage behavior description data corresponding to the current user, so that the same current user using all the applications has the same unique user ID.

[0036] A computer storage medium stores a computer executable program, and the computer executable program is run to implement any method of the embodiments of the present application.

[0037] An electronic device includes a memory and a processor. The memory is used to store a computer executable program, and the processor is used to run the computer executable program to implement any method of the embodiments of the present application.

[0038] In the embodiment of the present application, by obtaining the real-time usage behavior description data corresponding to the current user using any application; determining whether the current user is a new user or an existing user according to the real-time usage behavior description data and the historical usage behavior description data; determining the unique user ID assigned to the current user according to the determined result; synchronizing the unique user ID assigned to the current user to the unique user ID field of the real-time usage behavior description data corresponding to the current user, so that the same current user using all the applications has the same unique user ID, thus realizing the effective identification of the same user using multiple applications. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 It is a schematic diagram of the application scenario of the embodiment of the present application;

[0040] Figure 2A It is a schematic diagram of the process of a user identification method in this embodiment;

[0041] Figure 2B It is a schematic diagram of the process for determining whether the current user is a new user or an existing user in the embodiment of the present application;

[0042] Figure 3 It is a schematic diagram of the structure of the event table in the embodiment of the present application;

[0043] Figure 4 It is a schematic diagram of the structure of the user table in the embodiment of the present application;

[0044] Figure 5 It is a schematic diagram of the structure of a user identification device in the embodiment of the present application;

[0045] Figure 6 It is a schematic diagram of the structure of the electronic device in the embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0046] To make the technical problems, technical solutions and advantages to be solved by the present application clearer, the following will be described in detail with reference to the accompanying drawings and specific embodiments.

[0047] Figure 1 It is a schematic diagram of the application scenario of the embodiment of the present application; as Figure 1As shown, in this usage scenario, it includes a user group, multiple application programs with different functions, and devices on which the multiple application programs are installed. The user group can include logged-in users and guest users. The multiple application programs include Application 1, Application 2... Application N. The devices on which each application program is installed are respectively denoted as Device 1, Device 2... Device N, where N is an integer not less than 2. Here, a logged-in user specifically refers to a user who logs in to the application program using a registered account when using the application program, while a guest user refers to a user who does not use a registered account when using the application program, such as the situation of having no registered account due to not registering an account, or the situation of having a registered account but not logging in when using it.

[0048] In this embodiment, the quantity N mentioned is a general reference and not a unique limitation. Additionally, an application program includes any computer program product that can meet user needs, such as application programs suitable for the PC side and application programs suitable for mobile terminals.

[0049] In this embodiment, it is not limited that only one application program can be installed on each device. However, for the sake of convenience in explanation, this application takes the example of installing only one application program on each device for illustration.

[0050] In this embodiment, the multiple application programs are not particularly limited as long as user data is shared among these application programs. For example, they can be application programs with different functions of the same company, or application programs with the same function of different companies, or application programs with different functions of different companies.

[0051] Of course, it should be noted here that the above Figure 1 provided usage scenario is only an example and not a unique limitation.

[0052] Based on the above Figure 1 provided usage scenario, among the application programs, the unique user ID of the same user (also known as the user ID in the industry, which is the unique identifier of the user) is independent. That is, the same user has different unique user identifiers under different application programs, resulting in the behavior data of the same user under different application programs being independent of each other. As a result, it is impossible to obtain the complete behavior trajectory of the user under all application programs, leading to a relatively low accuracy rate and greater difficulty in analyzing the user behavior data.

[0053] Therefore, in the following embodiments of this application, a solution for user identification is provided to make the unique user ID of the same user in multiple application programs the same. Thus, when analyzing user behavior data, the complete behavior trajectory of the same user under all application programs can be obtained, improving the accuracy rate of analyzing user behavior data and reducing the analysis difficulty.

[0054] In this embodiment, the execution subject of the following user identification method may be an application server in the background.

[0055] Figure 2A FIG. is a schematic flowchart of a user identification method in this embodiment; the user identification method is applied to assign a unique user ID to a user using an application; specifically, as Figure 2A shown, the user identification method includes:

[0056] S201. Obtain real-time usage behavior description data corresponding to the current user using any application.

[0057] Optionally, in this embodiment, before obtaining the real-time usage behavior description data corresponding to the current user using any application, it includes: generating the real-time usage behavior description data corresponding to the current user using the any application according to the buried point data collected by the buried points set on the any application, so as to be obtained in step S201.

[0058] Here, the obtaining method is not limited. The application can push the real-time usage behavior description data to the application server (also known as push in the industry), or the application server can pull the real-time usage behavior description data from the application (also known as pull in the industry).

[0059] Exemplarily, in this embodiment, the buried point data may include, but is not limited to, the start event of the application, the login event of the application, the time node when the event occurs, the device ID corresponding to the device running the application, the application identification, the login ID corresponding to the login event, and the user type. The user type includes logged-in users and guest users. The login ID is used to represent the registered account of the user on the application, and the application identification is used to represent the product end used by the user.

[0060] Correspondingly, the real-time usage behavior description data includes an event field (corresponding to the start event of the application and the login event of the application), an event occurrence time node field, a device ID field corresponding to the device running the application, an application identification field, a login ID field corresponding to the login event, and a user type field, so as to save the start event of the application, the login event of the application, the time node when the event occurs, the device ID corresponding to the device running the application, the application identification, the login ID corresponding to the login event, and the user type collected above into the corresponding fields respectively, thereby accurately and comprehensively recording the usage correspondence relationship between the user and the product end through the real-time behavior data.

[0061] Exemplarily, if the startup event of the application occurs, the value of the event field is 10, and if the login event of the application occurs, the value of the event field is 11. The device ID saved in the device ID field is the identity identifier of the device, such as the MAC address, or the IP address, etc. The application identifier is distinguished by numbers, for example. If the user type is a logged-in user, the value of the user type field is 1, otherwise the value of the user type field is 0 or empty. It should be noted that the above is only an exemplary description for easy understanding and is not a unique limitation.

[0062] In addition, the real-time usage behavior description data further includes a unique user ID field, which is used to synchronize the unique user ID assigned to the current user to this unique user ID field after the unique user ID assigned to the current user is determined.

[0063] In this embodiment, since the user type field is included in the real-time usage behavior data, in some application scenarios, it is convenient to directly obtain the user type from the user type field. However, for example, for the case of always using the application without logging in, only the device ID can be collected, and the login ID will not be collected. Therefore, the user type can be indirectly determined by combining the device ID and the login ID in the corresponding fields of the real-time usage behavior data. In addition, for the case of always using the application without logging in, only the startup event of the application can be collected, and the login event of the application will not be collected. Therefore, the user type can be indirectly determined by combining the startup event and the login event in the corresponding fields. For this reason, the above real-time usage behavior description data can omit the user type field, or reserve the user type field in the real-time usage behavior description data, but the value of the user type field is always empty before it is used.

[0064] In this embodiment, the fields set in the above real-time usage behavior data are only examples and are not unique limitations. For example, the user type field can be omitted, or some fields can be set in other data.

[0065] S202. Determine whether the current user is a new user or an existing user according to the real-time usage behavior description data and the historical usage behavior description data.

[0066] In this embodiment, similar to the above-described real-time usage behavior description data, the historical usage behavior description data includes an event field of the application, an event occurrence time node field, a device ID field corresponding to the device on which the application runs, an application identification field, a login ID field corresponding to the login event, a user type field, and a unique user ID field, so as to save the start event of the application of the existing user, the login event of the application, the event occurrence time node, the device ID corresponding to the device on which the application runs, the application identification, the login ID corresponding to the login event, the user type, and the unique user ID to the corresponding fields respectively, thereby recording the usage correspondence relationship between the user and the product side through the real-time behavior data.

[0067] Different from the above historical usage behavior description data, in the real-time usage behavior description data, the unique user ID field does not save the unique user ID before step S204 is completed, or it can also be said that the value of the unique user ID field in the real-time usage behavior description data is in a state to be determined (or is called empty), while since the historical usage behavior description data is for existing users, therefore, the unique user ID field in the historical usage behavior description data has been filled with the unique user ID corresponding to the existing user, or it can also be said that the value of the unique user ID field in the historical usage behavior description data is in a determined state (or is called having a value).

[0068] Exemplarily, since the historical usage behavior description data is for existing users, and for the usage of the application, there will actually be multiple existing users. Additionally, considering that the historical usage behavior description data records the start event and login event of the application, and the occurrence of these events is based on time nodes, therefore, in this embodiment, each historical behavior description data records the behavior of existing users using the application with the event combined with the time node as a reference. Thus, all the historical behavior description data corresponding to all existing users on all applications are combined together to form an event table. In the event table, one historical behavior description data corresponds to one row in the event table, thereby realizing the effective management of the historical behavior description data corresponding to all existing users. For example, since each historical behavior data saves the application identification, statistical analysis can be performed based on the application identification to form an event time series representing the usage of the application, and user trajectory analysis can be carried out accordingly.

[0069] Here, it should be noted that an event table can also be formed based on the device ID, that is, the historical practical behavior description data corresponding to the same device ID constitutes a user table. Then the historical behavior description data corresponding to all existing users on all the above applications are combined together to form an event table, which is equivalent to combining the user tables corresponding to each device ID together to form a larger event table.

[0070] Figure 3 Schematic diagram of the structure of the event table of the embodiment of the present application; Figure 3 As shown, a piece of historical behavior description data corresponds to a row in the event table. In each event table, the table header is the event field of the application, the event occurrence time node field, the device ID field corresponding to the device running the application, the application identification field, the login ID field corresponding to the login event, the user type field, and the unique user ID field to save the corresponding values.

[0071] Wherein, illustratively, if the existing user is a visitor user, the value of the login ID field is empty. If the existing user is a login user, the value of the login ID field is such as the login ID.

[0072] Here, it should be noted that the historical behavior description data with completely identical data in the above fields are merged, and only one piece of historical behavior description data is retained, thereby saving storage space.

[0073] In addition, considering an application scenario, for an existing user with a login ID, after the existing user logs in to the application when using the application and then logs out of the application and continues to use the program, there will be one or more historical behavior description data (such as the so-called first historical behavior description data) in which the occurrence time node field of the application event stores the occurrence time node of the startup event, the device ID field stores the device ID, the application identification field stores the application identification, the user type field stores the user type as a guest user, and the unique user ID field stores the unique user ID assigned to the guest user; at the same time, there will be at least one historical behavior description data (such as the so-called second historical behavior description data) in which the occurrence time node field of the application event stores the occurrence time node of the login event, the device ID field stores the device ID, the application identification field stores the application identification, and the unique user ID field stores the unique user ID assigned to the logged-in user. And the device ID stored in the device ID field and the application identification stored in the application identification field in the first historical behavior description data and the second historical behavior description data are the same. Therefore, it can be determined that the unique user ID assigned to the guest user in the first historical behavior description data and the unique user ID assigned to the logged-in user in the second historical behavior description data substantially correspond to the same user, and this user is a logged-in user with a registered account on the application. Therefore, the unique user ID corresponding to the guest user is modified to the unique user ID corresponding to the logged-in user, thus realizing the merging of the unique user IDs. However, the values of other fields in the first historical behavior description data remain unchanged, so that the above-mentioned statistics based on the application identification can be performed, and the above-mentioned event time series representing the use of the application can be formed, and the user trajectory can be analyzed accordingly.

[0074] Figure 2B Schematic diagram of the process for determining whether the current user is a new user or an existing user in the embodiment of the present application; as Figure 2B shown, exemplarily, in this embodiment, determining whether the current user is a new user or an existing user according to the real-time usage behavior description data and the historical usage behavior description data includes:

[0075] S212. Determine whether the current user is a guest user or a logged-in user according to the real-time usage behavior data.

[0076] S222. In response to the current user being a guest user, determine whether the current user is a new guest user or an existing guest user according to the relative identity identifier in the real-time usage behavior data.

[0077] S232. In response to the current user being a logged-in user, determine whether the current user is a newly logged-in user or an existing logged-in user based on the login ID in the real-time usage behavior data.

[0078] Among them, the existing user is the existing guest user or the existing logged-in user; the new user is the new guest user or the new logged-in user.

[0079] Specifically, if the real-time usage behavior data includes a user type field, in S212, determining whether the current user is a guest user or a logged-in user based on the real-time usage behavior data includes: determining whether the current user is a guest user or a logged-in user according to the user type stored in the user type field. Thus, through the user type, it can be directly determined whether the current user is a guest user or a logged-in user.

[0080] In addition, if the real-time usage behavior data includes an event field, determining whether the current user is a guest user or a logged-in user based on the real-time usage behavior data includes: determining whether the current user is a guest user or a logged-in user according to the event stored in the event field. For example, if the event is only the startup event of the application, then the current user is a guest user; if the event is the login event of the application, then the current user is a logged-in user. Therefore, through the event stored in the event field, it can be indirectly determined whether the current user is a guest user or a logged-in user.

[0081] Furthermore, if the real-time usage behavior data includes a device ID field and a login ID field, determining whether the current user is a guest user or a logged-in user based on the real-time usage behavior data includes: determining whether the current user is a guest user or a logged-in user according to the device ID and login ID corresponding to the device ID field and the login ID field respectively. Specifically, for example, if only the device ID field stores a device ID, then the current user is a guest user; if at least the login ID field stores a login ID, or the device ID field also stores a device ID, then the current user is a logged-in user. Therefore, through the cooperation of the device ID and the login ID, it can be indirectly determined whether the current user is a guest user or a logged-in user.

[0082] Specifically, for tourist users, there is no effective login behavior when using the application. Therefore, the device ID is stored in the real-time usage behavior data, but the login ID is empty. Thus, in step S222, in response to the current user being a tourist user, determining whether the current user is a new tourist user or an existing tourist user based on the relative identity identifier in the real-time usage behavior data includes: using the device ID and application identifier in the real-time usage behavior data as the relative identity identifier to compare with the device ID and application identifier in the historical usage behavior data. If they are both the same, it is determined that the current user is an existing tourist user; otherwise, it is determined that the current user is a new tourist user. Since the relative identity identifier for determining existing and new tourist users is composed of the combined device ID and application identifier, only when the device ID and application identifier in the real-time usage behavior data are both the same as those in the historical usage behavior data will it be determined as an existing tourist user; otherwise, it will be determined as a new tourist user. Therefore, the incorrect merging of two tourist users using different applications is avoided.

[0083] Specifically, for logged-in users, after starting the application, they will use the registered account to log in to the application. Therefore, the login ID is saved in the real-time usage behavior data. For this reason, in S232, in response to the current user being a logged-in user, determining whether the current user is a new logged-in user or an existing logged-in user based on the login ID in the real-time usage behavior data includes: comparing the login ID in the real-time usage behavior data with the login ID in the historical usage behavior data. If they are the same, it is determined that the current user is an existing logged-in user; otherwise, it is determined that the current user is a new logged-in user. For this reason, by directly comparing the login IDs, it is possible to quickly and accurately determine whether the current user is a new logged-in user or an existing logged-in user. Additionally, it is also possible to determine that the current user is a logged-in user based on the event corresponding to the event field in the real-time usage behavior data. Or, if the login ID corresponding to the login ID field in the real-time usage behavior data is the user's registered account, it is determined that the current user is a logged-in user.

[0084] S203. Determine the unique user ID assigned to the current user according to the determined result.

[0085] Specifically, in this embodiment, determining the unique user ID assigned to the current user according to the determined result includes at least the following three possible situations:

[0086] (1) Situation 1

[0087] In response to the new user being a newly logged-in user, determine the absolute identity characteristic identifier submitted by the newly logged-in user when registering in any of the applications, search for the unique user ID that has a one-to-one correspondence with the absolute identity characteristic identifier in the unique user ID registration data of the existing logged-in users, and use the found unique user ID as the unique user ID of the newly logged-in user.

[0088] In this embodiment, the absolute identity characteristic identifier includes the characteristic identifier filled in by the same user when registering on multiple applications. This absolute identity characteristic identifier can be, for example, a mobile phone number, an ID number, or any other characteristic identifier that can directly associate the same user on multiple applications.

[0089] Specifically, in this embodiment, the absolute identity characteristic identifier can be saved in the registration information table and has a one-to-one correspondence with the login ID. In addition, for existing logged-in users, since the login ID also has a one-to-one correspondence with the unique user ID, therefore, the absolute identity characteristic identifier also has a one-to-one correspondence with the unique user ID.

[0090] Specifically, in this embodiment, for existing logged-in users, the unique user ID registration data includes the unique user IDs assigned to the same existing logged-in user on multiple applications, so that the same existing logged-in user using all the applications has the same unique user ID. In addition, as mentioned above, for existing logged-in users, since the unique user ID also has a one-to-one correspondence with the login ID, therefore, the unique user ID registration data can also include the login ID.

[0091] In addition, as mentioned above, considering that in some application scenarios, existing logged-in users do not log in to the application using the login ID when using the application, or are also called "fake tourist users". At this time, the existing logged-in user cannot be corresponded through the login ID. For tourist users, the device ID can be used as a relative identifier of their identity. Therefore, the unique user ID registration data can also include the device ID to merge these "fake tourist users" into the corresponding existing logged-in users.

[0092] Based on this, for existing logged-in users, referring to the field setting method described in the above historical usage behavior description data, the unique user ID registration data includes: a device ID field corresponding to the device running the application, an application identifier field, a login ID field corresponding to the login event, a user type field, a unique user ID field, and an absolute identity feature field. The unique user ID field stores the unique user ID assigned to the existing logged-in user, and the absolute identity feature field stores the absolute identity feature identifier of the existing logged-in user (such as a mobile phone number or an ID card number, etc.). For the descriptions of other fields, reference can be made to the records in the above embodiments.

[0093] It should be noted here that the fields included in the unique user ID registration data are for illustration and not unique limitations. In some application scenarios, some fields can be omitted in the unique user ID registration data. For example, considering that the historical usage behavior description data has a user type field and an application identifier field, therefore, the user type field and the application identifier field can be omitted in the unique user ID registration data. Here, the omitted fields are only for illustration and not unique limitations.

[0094] Exemplarily, since the unique user ID registration data is for existing logged-in users, and for the use of the application, there will actually be multiple existing logged-in users. Therefore, the unique user ID registration data corresponding to all existing logged-in users on all applications is combined together to form a user table. In the user table, a piece of unique user ID registration data corresponds to a row in the user table, which corresponds to an existing logged-in user, thus realizing the management of the unique user ID registration data corresponding to all existing logged-in users. Referring to the above division of the event table based on the device ID, the user table can also be managed based on the device ID. For example, all the unique user ID registration data corresponding to the same device ID forms a user table, and all the unique user ID registration data corresponding to all device IDs forms a larger user table.

[0095] Specifically, when maintaining the unique user ID registration data, duplicate removal processing can be performed on multiple unique user ID registration data with the same device ID, application identifier, user type, absolute identity feature identifier, and unique user ID, and only one piece of unique user ID registration data is retained, such as storing it in the user table, thereby saving storage space.

[0096] Figure 4 This is a schematic structural diagram of the user table in the embodiment of the present application; as Figure 4As shown, a unique user ID registration data corresponds to a row in the user table. Each unique user ID registration data includes a device ID field corresponding to the device running the application, an application identification field, a login ID field corresponding to the login event, a user type field, a unique user ID field, and an absolute identity feature field to store the corresponding values. The found unique user ID serves as the unique user ID of the newly added logged-in user.

[0097] The difference between the unique user ID registration data and the above historical behavior description data is that an absolute identity feature field is added, while the event field of the application is omitted. Thus, by combining the unique user ID registration data with the above historical behavior description data, the unique user ID of the newly added logged-in user on multiple applications can be determined.

[0098] If no unique user ID that has a one-to-one correspondence with the absolute identity feature identifier is found in the unique user ID registration data of the existing logged-in user, a unique user ID is generated for the newly added logged-in user to determine the unique user ID assigned to the current user, and a unique user ID registration data is generated for the newly added logged-in user to serve as the unique user ID registration data corresponding to the current user.

[0099] In this embodiment, when generating a unique user ID for the newly added logged-in user, the unique user ID of the newly added logged-in user can be generated according to the absolute identity feature in the unique user ID registration data and the time node of the login event in the real-time behavior description data. For data security considerations, the generated unique user ID is encrypted.

[0100] In this embodiment, since the unique user ID registration data and the real-time behavior description data have the same fields, the real-time behavior description data can transmit the values of the same fields (such as device ID, login ID, application identification, user type, etc.) to the unique user ID registration data, including the time node of the login event (or also called timestamp), to generate the unique user ID of the newly added logged-in user. Further, in this embodiment, when generating a unique user ID for the newly added logged-in user, the unique user ID registration data for the newly added logged-in user is inserted into the user table to achieve dynamic maintenance of the user table, or also called dynamic maintenance of the unique user ID registration data.

[0101] In addition, for the case of finding the unique user ID that has a one-to-one correspondence with the absolute identity feature identifier in the existing unique user ID registration data of logged-in users, and using the found unique user ID as the unique user ID of the newly added logged-in user, after that, according to the real-time behavior description data of the current user and the found unique user ID, unique user ID registration data for the current user can be generated and added to the user table to achieve dynamic maintenance of the user table, or in other words, dynamic maintenance of the unique user ID registration data.

[0102] Specifically, generating the unique user ID registration data for the current user according to the real-time behavior description data of the current user and the found unique user ID includes: inserting the device ID, application program identifier, user type, login ID, found unique user ID, and absolute identity feature of the real-time behavior description data of the current user into the corresponding fields of the unique user ID registration data to generate the unique user ID registration data for the current user.

[0103] (2) Case Two

[0104] In this embodiment, generating a unique user ID for the newly added tourist user includes: generating the unique user ID for the newly added tourist user according to the occurrence time node (or also called timestamp) of the startup event in the real-time usage behavior data and the device ID. For data security considerations, the generated unique user ID is encrypted.

[0105] Furthermore, in this embodiment, when generating a unique user ID for the newly added tourist user, the unique user ID registration data for the newly added tourist user is inserted into the user table to achieve dynamic maintenance of the user table, or in other words, dynamic maintenance of the unique user ID registration data.

[0106] Specifically, based on the real-time behavior description data of the current user and the generated unique user ID, unique user ID registration data for the current user is generated. Specifically, generating unique user ID registration data for the current user based on the real-time behavior description data of the current user and the generated unique user ID includes: adding the unique user ID generated from the device ID, application identifier, user type, and login ID field of the real-time behavior description data of the current user to the corresponding fields of the unique user ID registration data to generate unique user ID registration data for the current user. Since there is no login ID for newly added tourist users, the value of the login ID field in the real-time behavior description data of the current user is empty. Therefore, the value of the login ID field in the unique user ID registration data for the current user is synchronized to be empty. And the unique user ID registration data for the current user is added to the user table to achieve dynamic maintenance of the user table, or in other words, dynamic maintenance of the unique user ID registration data.

[0107] (3) In response to the current user being an existing user, query the unique user ID assigned to the existing user in the historical usage behavior description data, and use the queried unique user ID as the unique user ID assigned to the current user.

[0108] S204. Synchronize the unique user ID assigned to the current user to the unique user ID field of the real-time usage behavior description data corresponding to the current user, so that the same current user using all the applications has the same unique user ID.

[0109] Specifically, in this embodiment, the unique user ID assigned to the current user can be synchronized (or also referred to as returned) to the unique user ID field of the real-time usage behavior description data corresponding to the current user by filling.

[0110] For example, if the unique user ID registration data is managed based on the above user table, the user table can transmit the unique user ID assigned to the current user to the above event table and fill it into the unique user ID field in the real-time behavior description data corresponding to the current user.

[0111] In the above embodiment, if the existing unique user ID is directly used as the unique user ID of the current user, it is equivalent to merging the unique user ID of the current user with the existing unique user ID, so that the same user on multiple applications has the same unique user ID.

[0112] Based on the above embodiments, in another embodiment, after generating the unique user ID registration data corresponding to the current user, it may further include: determining the unique user ID registration data of existing guest users that needs to be repaired according to the unique user ID registration data corresponding to the current user.

[0113] Specifically, the determining the unique user ID registration data of existing guest users that needs to be repaired according to the unique user ID registration data corresponding to the current user includes: comparing the unique user ID registration data corresponding to the current user with the unique user ID registration data of existing guest users;

[0114] If the same fields between the unique user ID registration data corresponding to the current user and the unique user ID registration data of existing guest users correspond to all preset registration key fields, it is determined that the unique user ID registration data of the corresponding existing guest user needs to be repaired, and the unique user ID corresponding to the current user is used to replace the unique user ID in the unique user ID registration data to be repaired.

[0115] For example, if the registration key fields include a device ID field and an application identifier field, then if the same fields are the device ID field and the application identifier field, and the number of unique user ID registration data of the corresponding existing guest user is not greater than the set number threshold, the unique user ID registration data of the corresponding existing guest user is used as the object to be repaired. By combining the device ID field, the application identifier field, and the number threshold, it is possible to effectively target users who are actually registered users but are "false guest users" caused by not logging in to the application, avoiding incorrect merging of existing guest users and existing logged-in users who do not belong to "false guest users".

[0116] Specifically, in an application scenario, for example, considering that; the number threshold is set to 1, that is, the unique user ID registration data of this 1 existing guest user is used as the object to be repaired. Of course, here, the number threshold can be flexibly adjusted according to the application scenario and is not uniquely limited.

[0117] In addition, in the above embodiments, after step S204, the real-time usage behavior description data corresponding to the current user after the synchronization is added to the event table to dynamically maintain the event table.

[0118] Figure 5 It is a schematic structural diagram of a user identification device according to an embodiment of the present application; it is applied to assign a unique user ID to a user using an application, and the user identification device includes:

[0119] A data acquisition unit 501, configured to acquire real-time usage behavior description data corresponding to the current user using any application;

[0120] A user determination unit 502, configured to determine whether the current user is a new user or an existing user according to the real-time usage behavior description data and historical usage behavior description data;

[0121] A user ID determination unit 503, configured to determine a unique user ID assigned to the current user according to the determined result;

[0122] A user ID synchronization unit 504, configured to synchronize the unique user ID assigned to the current user to the unique user ID field of the real-time usage behavior description data corresponding to the current user, so that the same current user using all the applications has the same unique user ID.

[0123] Optionally, the data acquisition unit 501 is further configured to generate real-time usage behavior description data corresponding to the current user using any application according to the buried point data collected by the buried points set on the any application before acquiring the real-time usage behavior description data corresponding to the current user using any application.

[0124] Optionally, the user determination unit 502 is specifically configured to: determine whether the current user is a guest user or a logged-in user according to the real-time usage behavior data; in response to the current user being a guest user, determine whether the current user is a new guest user or an existing guest user according to the relative identity identifier in the real-time usage behavior data; in response to the current user being a logged-in user, determine whether the current user is a new logged-in user or an existing logged-in user according to the login ID in the real-time usage behavior data; wherein, the existing user is the existing guest user or the existing logged-in user; the new user is the new guest user or the new logged-in user.

[0125] Optionally, the user ID determination unit 503 is specifically configured to: in response to the new user being a newly logged-in user, determine the absolute identity characteristic identifier submitted by the newly logged-in user when registering in any of the applications, search for the unique user ID having a one-to-one correspondence with the absolute identity characteristic identifier in the unique user ID registration data of the existing logged-in users, and use the found unique user ID as the unique user ID of the newly logged-in user; if no unique user ID having a one-to-one correspondence with the absolute identity characteristic identifier is found in the unique user ID registration data of the existing logged-in users, generate a unique user ID for the newly logged-in user to determine the unique user ID assigned to the current user, and generate unique user ID registration data for the newly logged-in user to be used as the unique user ID registration data corresponding to the current user.

[0126] Optionally, after the user ID determination unit 503 also searches for the unique user ID having a one-to-one correspondence with the absolute identity characteristic identifier in the unique user ID registration data of the existing logged-in users and uses the found unique user ID as the unique user ID of the newly logged-in user, generate unique user ID registration data for the current user according to the real-time behavior description data of the current user and the found unique user ID, and add it to the user table, where the user table is used to manage the unique user ID registration data.

[0127] Optionally, the user determination unit 502 is specifically configured to: use the device ID and application identifier in the real-time usage behavior data as relative identity identifiers to compare with the device ID and application identifier in the historical usage behavior data. If they are the same, determine that the current user is an existing guest user; otherwise, determine that the current user is a newly added guest user.

[0128] Optionally, the user ID determination unit 503 is specifically configured to: in response to the new user being a newly added guest user, generate a unique user ID for the newly added guest user to determine the unique user ID assigned to the current user, and generate unique user ID registration data for the newly added guest user to be used as the unique user ID registration data corresponding to the current user.

[0129] Optionally, the user ID determination unit 503 is specifically configured to: generate the unique user ID for the newly added guest user according to the occurrence time node of the start event and the device ID in the real-time usage behavior data.

[0130] Optionally, the user ID determination unit 503 is specifically configured to: in response to the current user being an existing user, query the unique user ID assigned to the existing user from the historical usage behavior description data, and use the queried unique user ID as the unique user ID assigned to the current user.

[0131] Optionally, the apparatus includes a repair unit, configured to determine the unique user ID registration data of an existing guest user that needs to be repaired according to the unique user ID registration data corresponding to the current user.

[0132] Optionally, the repair unit is specifically configured to compare the unique user ID registration data corresponding to the current user with the unique user ID registration data of an existing guest user; if the same fields between the unique user ID registration data corresponding to the current user and the unique user ID registration data of an existing guest user correspond to all preset registration keyword fields, determine that the unique user ID registration data of the corresponding existing guest user needs to be repaired, and use the unique user ID corresponding to the current user to replace the unique user ID in the unique user ID registration data to be repaired.

[0133] Optionally, the registration keyword fields include a device ID field and an application identifier field. If the same fields are the device ID field and the application identifier field, and the number of records of the unique user ID registration data of the corresponding existing guest user is not greater than a set number threshold, the unique user ID registration data of the corresponding existing guest user is used as the object to be repaired.

[0134] The embodiment of the present application further provides a computer storage medium, on which a computer executable program is stored, and the computer executable program is run to implement the method according to any one of the embodiments of the present application.

[0135] The embodiment of the present application further provides a computer program product, on which a computer executable program is stored, and the computer executable program is run to implement the method according to any one of the embodiments of the present application.

[0136] Figure 6 is a schematic structural diagram of an electronic device in the embodiment of the present application; as Figure 6 shown, the electronic device includes: a memory 601 and a processor 602. A computer executable program is stored on the memory, and the processor is configured to run the computer executable program to implement the data processing method according to any one of the embodiments of the present application.

[0137] The above-described embodiments are merely specific implementation manners of the present application, used to illustrate the technical solutions of the present application, rather than limiting it. The protection scope of the present application is not limited thereto. Although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: any person skilled in the technical field of the present application within the technical scope disclosed by the present application can still modify the technical solutions recorded in the foregoing embodiments or can easily think of changes, or perform equivalent replacements on some of the technical features; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A user identification method, which is applied to assign a unique user ID to a user using an application. The user identification method includes: Obtaining real-time usage behavior description data corresponding to the current user using any application; Determining whether the current user is a new user or an existing user according to the real-time usage behavior description data and historical usage behavior description data; Determining the unique user ID assigned to the current user according to the determined result; Synchronizing the unique user ID assigned to the current user to the unique user ID field of the real-time usage behavior description data corresponding to the current user, so that the same current user using all the applications has the same unique user ID; Wherein, determining whether the current user is a new user or an existing user according to the real-time usage behavior description data and historical usage behavior description data includes: determining whether the current user is a guest user or a logged-in user according to the real-time usage behavior data; in response to the current user being a guest user, determining whether the current user is a new guest user or an existing guest user according to the relative identity identifier in the real-time usage behavior data; in response to the current user being a logged-in user, determining whether the current user is a new logged-in user or an existing logged-in user according to the login ID in the real-time usage behavior data; wherein, the existing user is the existing guest user or the existing logged-in user; the new user is the new guest user or the new logged-in user; The step of, in response to the current user being a guest user, determining whether the current user is a new guest user or an existing guest user according to the relative identity identifier in the real-time usage behavior data includes: using the device ID and application identifier in the real-time usage behavior data as the relative identity identifier to compare with the device ID and application identifier in the historical usage behavior data. If they are both the same, it is determined that the current user is an existing guest user; otherwise, it is determined that the current user is a new guest user; Determining the unique user ID assigned to the current user according to the determined result includes: in response to the new user being a newly logged-in user, determining the absolute identity characteristic identifier submitted by the newly logged-in user when registering in any of the applications, searching for the unique user ID that has a one-to-one correspondence with the absolute identity characteristic identifier in the registration data of the unique user IDs of the existing logged-in users, and using the found unique user ID as the unique user ID of the newly logged-in user; if no unique user ID that has a one-to-one correspondence with the absolute identity characteristic identifier is found in the registration data of the unique user IDs of the existing logged-in users, generating a unique user ID for the newly logged-in user to determine the unique user ID assigned to the current user, and generating registration data for the unique user ID of the newly logged-in user to be used as the registration data of the unique user ID corresponding to the current user; the absolute identity characteristic identifier includes a mobile phone number or an ID card number.

2. The method according to claim 1, characterized in that, Before obtaining the real-time usage behavior description data corresponding to the current user using any application, it includes: Generating the real-time usage behavior description data corresponding to the current user using any application according to the buried point data collected by the buried points set on any of the applications.

3. The method according to claim 1, characterized in that After searching for the unique user ID that has a one-to-one correspondence with the absolute identity characteristic identifier in the registration data of the unique user IDs of the existing logged-in users and using the found unique user ID as the unique user ID of the newly logged-in user, it includes: generating the registration data of the unique user ID for the current user according to the real-time behavior description data of the current user and the found unique user ID, and adding it to the user table, where the user table is used to manage the registration data of the unique user IDs.

4. The method according to claim 1, wherein Determining the unique user ID assigned to the current user according to the determined result includes: In response to the new user being a newly added guest user, generating a unique user ID for the newly added guest user to determine the unique user ID assigned to the current user, and generating registration data for the unique user ID of the newly added guest user to be used as the registration data of the unique user ID corresponding to the current user.

5. The method according to claim 4, wherein Generating the unique user ID for the newly added guest user includes: generating the unique user ID for the newly added guest user according to the occurrence time node of the startup event in the real-time usage behavior data and the device ID.

6. The method according to any one of claims 1-5, characterized in that, Determining the unique user ID assigned to the current user according to the determined result includes: In response to the current user being an existing user, querying the unique user ID assigned to the existing user in the historical usage behavior description data, and using the queried unique user ID as the unique user ID assigned to the current user.

7. The method according to claim 6, characterized in that The method includes: determining the registration data of the unique user ID of the existing guest user that needs to be repaired according to the registration data of the unique user ID corresponding to the current user.

8. The method according to claim 7, characterized in that, Determining the unique user ID registration data of an existing guest user that needs to be repaired based on the unique user ID registration data corresponding to the current user includes: comparing the unique user ID registration data corresponding to the current user with the unique user ID registration data of the existing guest user; If the same fields between the unique user ID registration data corresponding to the current user and the unique user ID registration data of the existing guest user correspond to all preset registration key fields, determine that the unique user ID registration data of the corresponding existing guest user needs to be repaired, and use the unique user ID corresponding to the current user to replace the unique user ID in the unique user ID registration data to be repaired.

9. The method according to claim 8, characterized in that, If the registration key fields include a device ID field and an application identifier field, and the same fields are the device ID field and the application identifier field, and the number of unique user ID registration data of the corresponding existing guest user is not greater than the set number threshold, then use the unique user ID registration data of the corresponding existing guest user as the object to be repaired.

10. A user identification device is applied to assign a unique user ID to a user using an application. The user identification device includes: A data acquisition unit for acquiring real-time usage behavior description data corresponding to a current user using any application; A user determination unit for determining whether the current user is a new user or an existing user according to the real-time usage behavior description data and historical usage behavior description data; A user ID determination unit for determining the unique user ID assigned to the current user according to the determined result; A user ID synchronization unit for synchronizing the unique user ID assigned to the current user to the unique user ID field of the real-time usage behavior description data corresponding to the current user, so that the same current user using all the applications has the same unique user ID; Among them, determining whether the current user is a new user or an existing user according to the real-time usage behavior description data and historical usage behavior description data includes: determining whether the current user is a guest user or a logged-in user according to the real-time usage behavior data; in response to the current user being a guest user, determining whether the current user is a new guest user or an existing guest user according to the relative identity identifier in the real-time usage behavior data; in response to the current user being a logged-in user, determining whether the current user is a new logged-in user or an existing logged-in user according to the login ID in the real-time usage behavior data; where the existing user is the existing guest user or the existing logged-in user; the new user is the new guest user or the new logged-in user; In response to the current user being a guest user, determining whether the current user is a new guest user or an existing guest user according to the relative identity identifier in the real-time usage behavior data includes: using the device ID and application identifier in the real-time usage behavior data as the relative identity identifier to compare with the device ID and application identifier in the historical usage behavior data. If they are both the same, it is determined that the current user is an existing guest user; otherwise, it is determined that the current user is a new guest user. Determining the unique user ID assigned to the current user according to the determined result includes: in response to the new user being a newly logged-in user, determining the absolute identity characteristic identifier submitted by the newly logged-in user when registering in any application, searching for the unique user ID that has a one-to-one correspondence with the absolute identity characteristic identifier in the unique user ID registration data of existing logged-in users, and using the found unique user ID as the unique user ID of the newly logged-in user; if the unique user ID that has a one-to-one correspondence with the absolute identity characteristic identifier is not found in the unique user ID registration data of existing logged-in users, generating a unique user ID for the newly logged-in user to determine the unique user ID assigned to the current user, and generating unique user ID registration data for the newly logged-in user as the unique user ID registration data corresponding to the current user; the absolute identity characteristic identifier includes a mobile phone number or an ID number.

11. A computer storage medium, on which a computer-executable program is stored, and the computer-executable program is run to implement the method according to any one of claims 1-9.

12. An electronic device, which includes a memory and a processor, the memory is used to store a computer-executable program, and the processor is used to run the computer-executable program to implement the method according to any one of claims 1-9.

Images