User identification method, device, equipment and storage medium

By generating random user identification and determining the identification domain name, it is associated with the endless device logo of the terminal, solving the problem of accurately identifying users in different business applications in existing technologies, and realizing accurate user logos in cross -Internet business.

CN111984946BActive Publication Date: 2025-01-28SHENZHEN QIHOO INTELLIGENT TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202010812765.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-08-13
Publication Date
2025-01-28
Estimated Expiration
2040-08-13

Smart Images

  • Figure CN111984946B_ABST
    Figure CN111984946B_ABST
Patent Text Reader

Abstract

The present application discloses a user identification method, device and storage medium, the method comprising: when detecting that a target user uses a first application entity, obtaining a random user identification of the target user on the first application entity side; based on the random user identification, determining the identification domain name of the target user on the first application entity side, so that the preset target device managed by the management entity can access the identification domain name, and associating the identification domain name with the preset terminal unique device identification; receiving the preset target device managed by the management entity, associating the identification domain name with the preset terminal unique device identification, and reporting the first association information. The present application solves the technical problem that it is difficult to accurately and uniquely locate or uniquely identify users under the existing account system of different business applications.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a user identification method, device, equipment and storage medium. Background Art

[0002] With the continuous development of science and technology, especially computer technology, more and more technologies are applied in the field of artificial intelligence, but higher requirements are also put forward for technology, such as higher requirements for user identification.

[0003] Due to the restrictions on the permission control and privacy protection requirements of the Android and IOS systems for device identifiers, the business platform or functional entity within the smart device, namely the application software, cannot collect the MAC address and other permanent device identifiers (such as IMEI / MEID, IMSI, SIM and build serial number) of the smart device. This results in the account system of different Internet business applications on smart devices being disconnected, making it difficult to accurately and uniquely locate or identify users across Internet businesses. Summary of the invention

[0004] The main purpose of this application is to provide a user identification method, device and storage medium, aiming to solve the technical problem that it is difficult to accurately and uniquely locate or uniquely identify users under the existing account system of different business applications.

[0005] To achieve the above object, the present application provides a user identification method, which is applied to a terminal, wherein the terminal is in communication connection with a management entity, and the terminal includes a first application entity. The user identification method includes:

[0006] When it is detected that the target user uses the first application entity, obtaining a random user identifier of the target user on the first application entity side;

[0007] Based on the random user identifier, determine the identification domain name of the target user on the first application entity side, so that the preset target device managed by the management entity can access the identification domain name, and associate the identification domain name with the preset terminal unique device identifier;

[0008] The preset target device managed by the management entity is received, and the first association information is reported after the identification domain name is associated with the preset terminal unique device identifier.

[0009] Optionally, the step of determining, based on the random user identifier, an identifier domain name of the target user on the first application entity side includes:

[0010] The random user identifier and the preset domain name of the first application entity are combined according to a preset composition rule to form an identifier domain name of the target user at the first application entity side.

[0011] Optionally, after the step of receiving a preset target device managed by the management entity, associating the identification domain name with a preset terminal unique device identifier, and reporting the first association information, the method includes:

[0012] Acquire user information of the target user, wherein the user information includes a service expiration time of the first application entity for the target user;

[0013] The user information is sent to the management entity so that the management entity can complete various identifications of the target user in preset dimensions.

[0014] Optionally, before the step of acquiring a random user identifier of the target user on the first application entity side when detecting that the target user uses the first application entity, the method includes:

[0015] Generating a first asymmetric key on the first application entity side;

[0016] The first public key in the first asymmetric key is sent to the management entity, so that a preset target device of the management entity can subsequently authenticate the first application entity.

[0017] Optionally, the step of determining, based on the random user identifier, an identification domain name of the target user on the first application entity side, so that a preset target device managed by the management entity can access the identification domain name, and associating the identification domain name with a preset terminal unique device identifier includes:

[0018] Based on the random user identifier, determining an identifier domain name of the target user on the first application entity side;

[0019] Receive a second asymmetric key generated by the preset key system based on the identification domain name trigger, encrypt the random user identifier based on the private key in the second asymmetric key, provide the encrypted identification domain name for the preset target device managed by the management entity, and decrypt the random user identifier in the identification domain name based on the second public key in the second asymmetric key;

[0020] The management entity associates the decrypted random user identifier with a preset terminal unique device identifier.

[0021] Optionally, the step of determining, based on the random user identifier, an identification domain name of the target user on the first application entity side, so that a preset target device managed by the management entity can access the identification domain name, and associating the identification domain name with a preset terminal unique device identifier includes:

[0022] Based on the random user identifier, determine the identification domain name of the target user on the first application entity side, so that the preset target device managed by the management entity can access the identification domain name, and associate the identification domain name with the preset terminal unique device identifier;

[0023] The management entity verifies whether the identification domain name has been changed based on a preset MD5 verification method, and if it has not been changed, associates the identification domain name with a preset terminal unique device identifier.

[0024] Optionally, after the step of receiving a preset target device managed by the management entity, associating the identification domain name with a preset terminal unique device identifier, and reporting the first association information, the method includes:

[0025] Receiving user characteristic information of the user determined by the preset target device based on the first association information and second association information of other second application entities;

[0026] Targeted recommendations are made based on the user feature information.

[0027] Optionally, the step of performing targeted recommendation based on the user characteristic information includes:

[0028] Acquire a product feature representation vector of the first application entity, and acquire a user feature representation vector corresponding to the user feature information;

[0029] Based on the product feature representation vector and the user feature representation vector, a product recommendation is made to the target user.

[0030] The present application also provides a user identification method, which is applied to a preset target device of a management entity, wherein the management entity is in communication connection with a terminal, wherein the terminal includes a first application entity, and the user identification method includes:

[0031] When detecting the identification domain name of the first application entity side, associating the identification domain name with a preset terminal unique device identifier;

[0032] When the first application entity detects that the target user uses the first application entity, it generates a random user identifier of the target user, and based on the random user identifier, determines the identification domain name of the target user on the first application entity side for access by the preset target device managed by the management entity;

[0033] Accessing the identification domain name, and associating the identification domain name with a preset terminal unique device identifier;

[0034] After associating the identification domain name with the preset terminal unique device identifier, first association information is obtained, and the first association information is reported to the first application entity.

[0035] Optionally, after the step of associating the identification domain name with a preset terminal unique device identifier to obtain first association information, and reporting the first association information to the first application entity, the method includes:

[0036] Acquire second association information of other second application entities associated with the preset terminal unique device identifier;

[0037] user characteristic information of the user determined based on the first association information and second association information of other second application entities;

[0038] Targeted recommendations are made based on the user feature information.

[0039] The present application also provides a user identification device, which is applied to a terminal, the terminal is in communication connection with a management entity, the terminal includes a first application entity, and the user identification device includes:

[0040] A first detection module, configured to obtain a random user identifier of the target user on the first application entity side when detecting that the target user uses the first application entity;

[0041] A first determination module is used to determine the identification domain name of the target user on the first application entity side based on the random user identifier, so that the preset target device managed by the management entity can access the identification domain name, and associate the identification domain name with a preset terminal unique device identifier;

[0042] The first receiving module is used to receive the preset target device managed by the management entity, and report the first association information after associating the identification domain name with the preset terminal unique device identifier.

[0043] Optionally, the first detection module includes:

[0044] The composition unit is used to combine the random user identifier and the preset domain name of the first application entity according to a preset composition rule to compose the identification domain name of the target user at the first application entity side.

[0045] Optionally, the user identification device further includes:

[0046] A first acquisition module, configured to acquire user information of the target user, wherein the user information includes a service expiration time of the first application entity for the target user;

[0047] The first sending module is used to send the user information to the management entity, so that the management entity can complete various identifications of the target user in a preset dimension.

[0048] Optionally, the user identification device further includes:

[0049] A generating module, configured to generate a first asymmetric key on the first application entity side;

[0050] The second sending module is used to send the first public key in the first asymmetric key to the management entity, so that a preset target device of the management entity can subsequently authenticate the first application entity.

[0051] The first determining module comprises:

[0052] A second determination module, configured to determine an identification domain name of the target user on the first application entity side based on the random user identifier;

[0053] A second receiving module is used to receive a second asymmetric key generated by a preset key system based on the identification domain name trigger, encrypt the random user identifier based on a private key in the second asymmetric key, so that a preset target device managed by a management entity can access the encrypted identification domain name, and decrypt the random user identifier in the identification domain name based on a second public key in the second asymmetric key;

[0054] The management entity associates the decrypted random user identifier with a preset terminal unique device identifier.

[0055] Optionally, the first determining module further includes:

[0056] a determining unit, configured to determine, based on the random user identifier, an identification domain name of the target user on the first application entity side, so that a preset target device managed by the management entity can access the identification domain name, and associate the identification domain name with a preset terminal unique device identifier;

[0057] The management entity verifies whether the identification domain name has been changed based on a preset MD5 verification method, and if it has not been changed, associates the identification domain name with a preset terminal unique device identifier.

[0058] Optionally, the user identification device further includes:

[0059] A third receiving module, configured to receive user characteristic information of the user determined by the preset target device based on the first association information and second association information of other second application entities;

[0060] The first recommendation module is used to make targeted recommendations based on the user feature information.

[0061] Optionally, the first recommendation module includes:

[0062] an acquisition unit, configured to acquire a product feature representation vector of the first application entity, and acquire a user feature representation vector corresponding to the user feature information;

[0063] A recommendation unit is used to recommend products to the target user based on the product feature representation vector and the user feature representation vector.

[0064] The present application also provides a user identification device, which is applied to a preset target device of a management entity, wherein the management entity is in communication connection with a terminal, wherein the terminal includes a first application entity, and the user identification device includes:

[0065] A second detection module is used to associate the identification domain name with a preset terminal unique device identifier when detecting the identification domain name of the first application entity side;

[0066] When the first application entity detects that the target user uses the first application entity, it generates a random user identifier of the target user, and based on the random user identifier, determines the identification domain name of the target user on the first application entity side for access by the preset target device managed by the management entity;

[0067] An access module, used to access the identification domain name and associate the identification domain name with a preset terminal unique device identifier;

[0068] The reporting module is used to associate the identification domain name with the preset terminal unique device identifier to obtain first association information, and report the first association information to the first application entity.

[0069] Optionally, the user identification device further includes:

[0070] An acquisition module, used to acquire second association information of other second application entities associated with the preset terminal unique device identifier;

[0071] A third determining module, configured to determine user characteristic information of the user based on the first association information and second association information of other second application entities;

[0072] The second recommendation module is used to make targeted recommendations based on the user feature information.

[0073] The present application also provides a user identification system, which includes the above-mentioned terminal and the above-mentioned management entity.

[0074] The present application also provides a user identification device, which is a physical device. The user identification device includes: a memory, a processor, and a program of the user identification method stored in the memory and executable on the processor. When the program of the user identification method is executed by the processor, the steps of the user identification method as described above can be implemented.

[0075] The present application also provides a storage medium, on which is stored a program for implementing the above-mentioned user identification method. When the program of the user identification method is executed by a processor, the steps of the above-mentioned user identification method are implemented.

[0076] The present application obtains the random user identifier of the target user on the first application entity side when it is detected that the target user uses the first application entity; determines the identification domain name of the target user on the first application entity side based on the random user identifier, so that the preset target device managed by the management entity can access the identification domain name, and associates the identification domain name with the preset terminal unique device identifier; receives the preset target device managed by the management entity, associates the identification domain name with the preset terminal unique device identifier, and reports the first association information. In the present application, when it is detected that the target user uses the first application entity, a random user identifier is generated to generate an identification domain name, and then, the identification domain name is associated with the preset terminal unique device identifier for the preset target device managed by the management entity, and reports the association information, that is, in the present application, the user identifier of the business application is associated with the preset terminal unique device identifier by generating a domain name, so that different business applications can be connected based on the preset terminal unique device identifier to realize accurate unique positioning or unique identification of users in cross-Internet business, and solve the technical problem that it is difficult to accurately uniquely locate or uniquely identify users under the existing account system of different business applications. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0078] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0079] Figure 1 This is a flowchart of the first embodiment of the user identification method of the present application;

[0080] Figure 2A flowchart of the detailed steps after the step of receiving the preset target device managed by the management entity, associating the identification domain name with the preset terminal unique device identifier, and reporting the first association information in the user identification method of the present application;

[0081] Figure 3 This is a schematic diagram of the device structure of the hardware operating environment involved in the embodiment of the present application.

[0082] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0083] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0084] The present application embodiment provides a user identification method. In the first embodiment of the user identification method of the present application, refer to Figure 1 , applied to a terminal, the terminal is in communication connection with a management entity, the terminal includes a first application entity, and the user identification method includes:

[0085] Step S10, when it is detected that the target user uses the first application entity, obtaining a random user identifier of the target user on the first application entity side;

[0086] Step S20, based on the random user identifier, determining the identification domain name of the target user on the first application entity side, so that the preset target device managed by the management entity can access the identification domain name, and associating the identification domain name with the preset terminal unique device identifier;

[0087] Step S30: receiving a preset target device managed by the management entity, associating the identification domain name with a preset terminal unique device identifier, and then reporting first association information.

[0088] The specific steps are as follows:

[0089] Step S10, when it is detected that the target user uses the first application entity, obtaining a random user identifier of the target user on the first application entity side;

[0090] In this embodiment, it should be noted that the terminal is communicatively connected to the management entity, wherein the terminal may be a smart phone, an IPAD, or a PC and other terminals, wherein the terminal includes a first application entity and other second application entities, and in this embodiment, the application entity is a business application or business function usage entity, such as Youku (application 1), iQiyi (application 2) and other usage entities, and in this embodiment, the management entity is a network device (local area network device) such as a router, an optical modem, an electric power modem, and a switch, wherein the management entity is communicatively connected to the terminal.

[0091] When it is detected that the target user uses the first application entity, a random user identifier of the target user on the first application entity side is obtained.

[0092] The method of detecting whether the target user uses the first application entity is as follows:

[0093] Method 1: Determine whether the target user is logged in to use the entity. After determining that the target user is logged in to use the entity, further determine whether the target user is in the user interface of the use entity. If the target user is in the user interface of the use entity, determine that the target user is in the use state of the first application entity. If it is determined that the target user is not in the user interface of the use entity, determine that the target user is not in the use state of the first application entity.

[0094] Method 2: Determine whether the target user is logged in to the usage entity. After determining that the target user is logged in to the usage entity, further determine whether the usage entity is in the background running state. If it is determined that the usage entity is not in the background running state, determine that the target user is in the usage state of the first application entity. If it is determined that the usage entity is in the background running state, determine that the target user is not in the usage state of the first application entity.

[0095] In this embodiment, when it is detected that the target user uses the first application entity, a method of obtaining a random user identifier of the target user on the first application entity side includes:

[0096] Method 1: when it is detected that the target user uses the first application entity, a random user identifier of the target user on the first application entity side is obtained through an identifier generation rule preset in the first application entity;

[0097] Mode 2: When it is detected that the target user uses the first application entity, the random user identifier of the target user generated by the identifier generation system is received through the first application entity to obtain the random user identifier of the target user on the first application entity side.

[0098] In this embodiment, it should be noted that the first user entity can generate a random identifier for the user (the user's actual smart device end), such as the random identifier can be: yonghu1. In this embodiment, the random identifier can also be signed at the first user entity, specifically, using the private key signature to obtain qianming_yonghu1;

[0099] Alternatively, in this embodiment, the random identifier may also be signed by a third party at the first user entity, specifically, qianming_yonghu1 is obtained by signing with a private key;

[0100] Step S20, based on the random user identifier, determining the identification domain name of the target user on the first application entity side, so that the preset target device managed by the management entity can access the identification domain name, and associating the identification domain name with the preset terminal unique device identifier;

[0101] In this embodiment, after obtaining the random user identifier, the identification domain name of the target user on the first application entity side is determined based on the random user identifier. It should be noted that in this embodiment, the identification domain name can not only uniquely identify the target user, but also uniquely identify the first application entity, that is, the same user has different identification domain names on different application entity sides, and different users on the same application entity side have different identifiers.

[0102] Based on the random user identifier, a method for determining the identification domain name of the target user on the first application entity side may be: obtaining a first MD5 value corresponding to the random user identifier and a second MD5 value of the identification domain name on the first application entity side, and based on the first MD5 value and the second MD5 value, generating the identification domain name of the target user on the first application entity side according to a preset generation function (inputting the first MD5 value and the second MD5 value into the function and calculating).

[0103] The step of determining the identification domain name of the target user on the first application entity side based on the random user identifier includes:

[0104] Step S21: The random user identifier and the preset domain name of the first application entity are combined according to a preset composition rule to form an identifier domain name of the target user at the first application entity side.

[0105] In this embodiment, the random user identifier and the preset domain name of the first application entity are combined according to a preset composition rule to form an identification domain name of the target user on the first application entity side. The composition method can be a head-to-tail composition method or a fusion composition method. For example, a random identifier (qianming_yonghu1) and a "using entity" domain name (router.youku.com) are used to form an identification domain name, such as: qianming_yonghu1.router.youku.com.

[0106] Or, for example, a random identifier (qianming_yonghu1) and a "using entity" domain name (router.youku.com) are used to form an identification domain name, such as: qianming_yonghu1.youku.com.

[0107] Based on the random user identifier, determine the identification domain name of the target user on the first application entity side, so that the preset target device managed by the management entity can access the identification domain name, and associate the identification domain name with the preset terminal unique device identifier, wherein the management entity, such as a router's downstream device, accesses the domain name on the browser or APP side of the first user entity, qianming_yonghu1.router.youku.com. After the preset target device managed by the management entity accesses the identification domain name, it obtains the random user identifier in the identification domain name, and verifies the random user identifier to verify whether it is sent by the first user entity, rather than a forged identifier.

[0108] In this embodiment, the preset target device (or its subordinate device) managed by the management entity accesses the identification domain name and associates the identification domain name with the preset terminal unique device identifier. Specifically, for example, if the preset terminal unique device identifier is a MAC address, the identification domain name is associated with the MAC address, if the preset terminal unique device identifier is an IMEI / MEID address, the identification domain name is associated with the IMEI / MEID address, if the preset terminal unique device identifier is an IMSI address, the identification domain name is associated with the IMSI address, and if the preset terminal unique device identifier is a SIM address, the identification domain name is associated with the SIM address.

[0109] In this embodiment, the preset target device managed by the management entity accesses the identification domain name, associates the identification domain name with the preset terminal unique device identifier, and then encrypts the identification domain name. For example, the decrypted data is encrypted to obtain jiami_yonghu1.

[0110] It should be noted that, in this embodiment, the preset target device managed by the management entity also accesses other identification domain names of other application entities, and associates the other identification domain names with the preset terminal unique device identifier.

[0111] Step S30: receiving a preset target device managed by the management entity, associating the identification domain name with a preset terminal unique device identifier, and then reporting first association information.

[0112] In this embodiment, the first user entity receives the preset target device managed by the management entity, associates the identification domain name with the preset terminal unique device identifier, and then reports the first association information, that is, the first user entity activates a reporting service, that is, the first application entity side obtains the information of the preset terminal unique device identifier and the networking channel information through the activated reporting service, and the "management entity" transmits the identifier jiami_yonghu1 to the "user entity" through the interface to indicate that the user is surfing the Internet through the actual device of the management entity. In this embodiment, the first user entity receives the preset target device managed by the management entity, associates the identification domain name with the preset terminal unique device identifier, and then reports the first association information, thereby realizing the association with the terminal unique device identifier.

[0113] Reference Figure 2 , after the step of receiving the preset target device managed by the management entity, associating the identification domain name with the preset terminal unique device identifier, and reporting the first association information, the method includes:

[0114] Step S40, acquiring user information of the target user, wherein the user information includes a service expiration time of the first application entity for the target user;

[0115] In this embodiment, the terminal also obtains user information of the target user, specifically, obtains user information of the target user on the first user entity side, wherein the user information includes the service expiration time of the first application entity for the target user, specifically, for example, the membership expiration time of the target user, or the annual card expiration time of the target user. In addition, the user information also includes information such as the user's viewing content and viewing frequency.

[0116] Step S50: Send the user information to the management entity so that the management entity can complete various identifications of the target user in preset dimensions.

[0117] The user information is sent to the management entity so that the management entity can complete the various identifications of the target user in preset dimensions. That is, in this embodiment, the first user entity can provide the management entity with information such as the effective time or the expiration time of the user membership to complete all feature identifications of the target user. Specifically, the user information is sent to the management entity so that the management entity can complete the various feature identifications of the target user in preset dimensions such as interest dimension, type dimension, etc.

[0118] After the step of receiving the preset target device managed by the management entity, associating the identification domain name with the preset terminal unique device identifier, and reporting the first association information, the method includes:

[0119] Step S60, receiving user characteristic information of the user determined by the preset target device based on the first association information and second association information of other second application entities;

[0120] Step S70: making targeted recommendations based on the user characteristic information.

[0121] In this embodiment, the user characteristic information of the user determined by the preset target device based on the first association information and the second association information of other second application entities is also received, wherein, that is, in this embodiment, the management entity associates the association information of different user entities through the MAC address to obtain more complete user characteristic information of the target user, so as to make targeted recommendations based on the user characteristic information.

[0122] The present application obtains the random user identifier of the target user on the first application entity side when it is detected that the target user uses the first application entity; determines the identification domain name of the target user on the first application entity side based on the random user identifier, so that the preset target device managed by the management entity can access the identification domain name, and associates the identification domain name with the preset terminal unique device identifier; receives the preset target device managed by the management entity, associates the identification domain name with the preset terminal unique device identifier, and reports the first association information. In the present application, when it is detected that the target user uses the first application entity, a random user identifier is generated to generate an identification domain name, and then, the identification domain name is associated with the preset terminal unique device identifier for the preset target device managed by the management entity, and reports the association information, that is, in the present application, the user identifier of the business application is associated with the preset terminal unique device identifier by generating a domain name, so that different business applications can be connected based on the preset terminal unique device identifier to realize accurate unique positioning or unique identification of users in cross-Internet business, and solve the technical problem that it is difficult to accurately uniquely locate or uniquely identify users under the existing account system of different business applications.

[0123] Further, based on the first embodiment of the present application, another embodiment of the present application is provided. In this embodiment, when it is detected that the target user uses the first application entity, before the step of obtaining the random user identifier of the target user on the first application entity side, the method includes:

[0124] Step S01, generating a first asymmetric key on the first application entity side;

[0125] Step S02: sending the first public key in the first asymmetric key to the management entity, so that a preset target device of the management entity can subsequently authenticate the first application entity.

[0126] In this embodiment, a first asymmetric key (such as a pair of RSA certificates) is also generated on the first application entity side for identity verification with the management entity. Specifically, the first public key in the first asymmetric key is sent to the management entity for subsequent authentication of the first application entity by a preset target device of the management entity, wherein the identity authentication may be performed in the process of obtaining a random user identifier after the preset target device managed by the management entity accesses the identification domain name. The purpose of identity authentication through the first asymmetric key is to verify whether the random user identifier is sent by the user entity, rather than a forged identifier.

[0127] Among them, in this embodiment, the step of determining the identification domain name of the target user on the first application entity side based on the random user identifier so that the preset target device managed by the management entity can access the identification domain name, and associating the identification domain name with the preset terminal unique device identifier includes:

[0128] Step S22: determining the identification domain name of the target user on the first application entity side based on the random user identifier;

[0129] Step S23, receiving a second asymmetric key generated by the preset key system based on the identification domain name trigger, encrypting the random user identifier based on the private key in the second asymmetric key, so that the preset target device managed by the management entity can access the encrypted identification domain name, and decrypting the random user identifier in the identification domain name based on the second public key in the second asymmetric key;

[0130] The management entity associates the decrypted random user identifier with a preset terminal unique device identifier.

[0131] In this embodiment, a method for identity authentication is also provided. In this identity authentication method, the second asymmetric key is generated by triggering an identification domain name, and is generated by triggering a preset key system based on the identification domain name. Since the preset key system triggers the generation of the second asymmetric key based on the identification domain name, and encrypts the random user identifier based on the private key in the second asymmetric key, the first application entity side may not land or save the private key in the second asymmetric key, but directly encrypt the random user identifier, thereby improving the security performance. In addition, in this embodiment, the preset target device managed by the management entity accesses the encrypted identification domain name, and decrypts the random user identifier in the identification domain name based on the second public key in the second asymmetric key; wherein the management entity associates the decrypted random user identifier with the preset terminal unique device identifier to complete the association of the random user identifier with the preset terminal unique device identifier in a secure state.

[0132] In this embodiment, the identification domain name of the target user on the first application entity side is determined based on the random user identifier; the second asymmetric key generated by the preset key system based on the identification domain name is received, and the random user identifier is encrypted based on the private key in the second asymmetric key, so that the preset target device managed by the management entity can access the encrypted identification domain name, and the random user identifier in the identification domain name is decrypted based on the second public key in the second asymmetric key; wherein the management entity associates the decrypted random user identifier with the preset terminal unique device identifier. In this embodiment, the random user identifier is associated with the preset terminal unique device identifier in a secure state.

[0133] Further, another embodiment of the present application is provided. In this embodiment, the step of determining, based on the random user identifier, an identification domain name of the target user on the first application entity side, so that a preset target device managed by the management entity can access the identification domain name, and associating the identification domain name with a preset terminal unique device identifier, includes:

[0134] Step A1, based on the random user identifier, determining the identification domain name of the target user on the first application entity side, so that a preset target device managed by the management entity can access the identification domain name, and associating the identification domain name with a preset terminal unique device identifier;

[0135] The management entity verifies whether the identification domain name has been changed based on a preset MD5 verification method, and if it has not been changed, associates the identification domain name with a preset terminal unique device identifier.

[0136] In this embodiment, another embodiment of identity authentication is provided, in which the management entity verifies whether the identification domain name has been changed based on a preset MD5 verification method. Specifically, if it has not been changed, the identification domain name is associated with a preset terminal unique device identifier. If it has been changed, the step of associating the identification domain name with the preset terminal unique device identifier is not performed. The preset MD5 verification method may refer to placing a preset MD5 value and a corresponding identification domain name in an asymmetric key (including a private key and a public key) for corresponding verification by the management entity.

[0137] In this embodiment, the identification domain name of the target user on the first application entity side is determined based on the random user identifier, so that the preset target device managed by the management entity can access the identification domain name, and the identification domain name is associated with the preset terminal unique device identifier; wherein the management entity verifies whether the identification domain name has been changed based on a preset MD5 verification method, and if it has not been changed, the identification domain name is associated with the preset terminal unique device identifier. In this embodiment, the random user identifier is associated with the preset terminal unique device identifier in a secure state.

[0138] Further, based on the first embodiment of the present application, another embodiment of the present application is provided, wherein the step of performing targeted recommendation based on the user feature information includes:

[0139] Step B1, obtaining a product feature representation vector of the first application entity, and obtaining a user feature representation vector corresponding to the user feature information;

[0140] Step B2: recommending products to the target user based on the product feature representation vector and the user feature representation vector.

[0141] In this embodiment, a product feature set is first determined, and then a product feature representation vector of the first application entity is determined, wherein the product feature representation vector can be obtained by one-hot encoding. After obtaining the product feature representation vector, a user feature representation vector corresponding to the user feature information is obtained, wherein the feature set of the user feature information is first determined, and then a user feature representation vector corresponding to the user feature information is determined.

[0142] Based on the product feature representation vector and the user feature representation vector, a product is recommended to the target user. Specifically, the user's tag is first obtained based on the user feature representation vector, and then the product's tag is obtained based on the product feature representation vector. Based on the association between the preset product tag and the user tag, a product is recommended to the target user. Specifically, for example, if the user's tag is anime, Japan, and the tag of product a is anime, Hokkaido, Japan, then product a is recommended to the user. Furthermore, in this implementation, cross-Internet business advertising can be achieved.

[0143] In this embodiment, by obtaining the product feature representation vector of the first application entity and obtaining the user feature representation vector corresponding to the user feature information; based on the product feature representation vector and the user feature representation vector, product recommendations are made to the target user. In this embodiment, cross-Internet business advertising is implemented.

[0144] Further, another embodiment of the user identification method is provided. In this embodiment, a preset target device is applied to a management entity, the management entity is in communication connection with a terminal, the terminal includes a first application entity, and the user identification method includes:

[0145] When detecting the identification domain name of the first application entity side, associating the identification domain name with a preset terminal unique device identifier;

[0146] When the first application entity detects that the target user uses the first application entity, it generates a random user identifier of the target user, and based on the random user identifier, determines the identification domain name of the target user on the first application entity side for access by the preset target device managed by the management entity;

[0147] Accessing the identification domain name, and associating the identification domain name with a preset terminal unique device identifier;

[0148] After associating the identification domain name with the preset terminal unique device identifier, first association information is obtained, and the first association information is reported to the first application entity.

[0149] After the step of associating the identification domain name with the preset terminal unique device identifier to obtain first association information, and reporting the first association information to the first application entity, the method includes:

[0150] Acquire second association information of other second application entities associated with the preset terminal unique device identifier;

[0151] user characteristic information of the user determined based on the first association information and second association information of other second application entities;

[0152] Targeted recommendations are made based on the user feature information.

[0153] In this embodiment, when the management entity detects the identification domain name on the first application entity side, the management entity associates the identification domain name with the preset terminal unique device identifier; accesses the identification domain name and associates the identification domain name with the preset terminal unique device identifier; after associating the identification domain name with the preset terminal unique device identifier, first association information is obtained, and the first association information is reported to the first application entity, wherein, when the first application entity detects that the target user uses the first application entity, the first application entity generates a random user identifier of the target user, and based on the random user identifier, determines the identification domain name of the target user on the first application entity side, for access by the preset target device managed by the management entity. In the embodiment, the technical problem that it is difficult to accurately and uniquely locate or uniquely identify users under the existing account system of different business applications is solved.

[0154] In this embodiment, a user identification system is also provided, which includes the above-mentioned terminal and the above-mentioned management entity to solve the technical problem that it is difficult to accurately and uniquely locate or uniquely identify a user under the existing account system of different business applications.

[0155] Reference Figure 3 , Figure 3 It is a schematic diagram of the device structure of the hardware operating environment involved in the embodiment of the present application.

[0156] like Figure 3 As shown, the user identification device may include: a processor 1001, such as a CPU, a memory 1005, and a communication bus 1002. The communication bus 1002 is used to realize the connection and communication between the processor 1001 and the memory 1005. The memory 1005 may be a high-speed RAM memory or a stable memory (non-volatile memory), such as a disk memory. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0157] Optionally, the user identification device may also include a rectangular user interface, a network interface, a camera, an RF (Radio Frequency) circuit, a sensor, an audio circuit, a WiFi module, etc. The rectangular user interface may include a display screen (Display), an input submodule such as a keyboard (Keyboard), and the optional rectangular user interface may also include a standard wired interface and a wireless interface. The network interface may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).

[0158] Those skilled in the art will understand that Figure 3 The structure of the user identification device shown in the figure does not constitute a limitation on the user identification device, and may include more or less components than those shown in the figure, or combine certain components, or arrange the components differently.

[0159] like Figure 3 As shown, the memory 1005 as a storage medium may include an operating system, a network communication module and a user identification program. The operating system is a program that manages and controls the hardware and software resources of the user identification device, and supports the operation of the user identification program and other software and / or programs. The network communication module is used to realize the communication between the components inside the memory 1005, and the communication between other hardware and software in the user identification system.

[0160] exist Figure 3 In the user identification device shown, the processor 1001 is used to execute the user identification program stored in the memory 1005 to implement the steps of any one of the user identification methods described above.

[0161] The specific implementation of the user identification device of the present application is basically the same as the above-mentioned embodiments of the user identification method, and will not be repeated here.

[0162] The present application also provides a user identification device, and the present application also provides a user identification device, which is applied to a terminal, the terminal is in communication connection with a management entity, the terminal includes a first application entity, and the user identification device includes:

[0163] A first detection module, configured to obtain a random user identifier of the target user on the first application entity side when detecting that the target user uses the first application entity;

[0164] A first determination module is used to determine the identification domain name of the target user on the first application entity side based on the random user identifier, so that the preset target device managed by the management entity can access the identification domain name, and associate the identification domain name with a preset terminal unique device identifier;

[0165] The first receiving module is used to receive the preset target device managed by the management entity, and report the first association information after associating the identification domain name with the preset terminal unique device identifier.

[0166] Optionally, the first detection module includes:

[0167] The composition unit is used to combine the random user identifier and the preset domain name of the first application entity according to a preset composition rule to compose the identification domain name of the target user at the first application entity side.

[0168] Optionally, the user identification device further includes:

[0169] A first acquisition module, configured to acquire user information of the target user, wherein the user information includes a service expiration time of the first application entity for the target user;

[0170] The first sending module is used to send the user information to the management entity, so that the management entity can complete various identifications of the target user in a preset dimension.

[0171] Optionally, the user identification device further includes:

[0172] A generating module, configured to generate a first asymmetric key on the first application entity side;

[0173] The second sending module is used to send the first public key in the first asymmetric key to the management entity, so that a preset target device of the management entity can subsequently authenticate the first application entity.

[0174] The first determining module comprises:

[0175] A second determination module, configured to determine an identification domain name of the target user on the first application entity side based on the random user identifier;

[0176] A second receiving module is used to receive a second asymmetric key generated by a preset key system based on the identification domain name trigger, encrypt the random user identifier based on a private key in the second asymmetric key, so that a preset target device managed by a management entity can access the encrypted identification domain name, and decrypt the random user identifier in the identification domain name based on a second public key in the second asymmetric key;

[0177] The management entity associates the decrypted random user identifier with a preset terminal unique device identifier.

[0178] Optionally, the first determining module further includes:

[0179] a determining unit, configured to determine, based on the random user identifier, an identification domain name of the target user on the first application entity side, so that a preset target device managed by the management entity can access the identification domain name, and associate the identification domain name with a preset terminal unique device identifier;

[0180] The management entity verifies whether the identification domain name has been changed based on a preset MD5 verification method, and if it has not been changed, associates the identification domain name with a preset terminal unique device identifier.

[0181] Optionally, the user identification device further includes:

[0182] A third receiving module, configured to receive user characteristic information of the user determined by the preset target device based on the first association information and second association information of other second application entities;

[0183] The first recommendation module is used to make targeted recommendations based on the user feature information.

[0184] Optionally, the first recommendation module includes:

[0185] an acquisition unit, configured to acquire a product feature representation vector of the first application entity, and acquire a user feature representation vector corresponding to the user feature information;

[0186] A recommendation unit is used to recommend products to the target user based on the product feature representation vector and the user feature representation vector.

[0187] The present application also provides a user identification device, which is applied to a preset target device of a management entity, wherein the management entity is in communication connection with a terminal, wherein the terminal includes a first application entity, and the user identification device includes:

[0188] A second detection module is used to associate the identification domain name with a preset terminal unique device identifier when detecting the identification domain name of the first application entity side;

[0189] When the first application entity detects that the target user uses the first application entity, it generates a random user identifier of the target user, and based on the random user identifier, determines the identification domain name of the target user on the first application entity side for access by the preset target device managed by the management entity;

[0190] An access module, used to access the identification domain name and associate the identification domain name with a preset terminal unique device identifier;

[0191] The reporting module is used to associate the identification domain name with the preset terminal unique device identifier to obtain first association information, and report the first association information to the first application entity.

[0192] Optionally, the user identification device further includes:

[0193] An acquisition module, used to acquire second association information of other second application entities associated with the preset terminal unique device identifier;

[0194] A third determining module, configured to determine user characteristic information of the user based on the first association information and second association information of other second application entities;

[0195] The second recommendation module is used to make targeted recommendations based on the user feature information.

[0196] The specific implementation of the user identification device of the present application is basically the same as the embodiments of the above-mentioned user identification method, and will not be repeated here.

[0197] An embodiment of the present application provides a storage medium, and the storage medium stores one or more programs, and the one or more programs can also be executed by one or more processors to implement the steps of any of the above-mentioned user identification methods.

[0198] The specific implementation of the storage medium of the present application is basically the same as the above-mentioned embodiments of the user identification method, and will not be repeated here.

[0199] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0200] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0201] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0202] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A user identification method, characterized in that: Applied to a terminal, the terminal is in communication connection with a management entity, the terminal includes a first application entity, and the user identification method includes: When it is detected that the target user uses the first application entity, obtaining a random user identifier of the target user on the first application entity side; Based on the random user identifier, determine the identification domain name of the target user on the first application entity side, so that the preset target device managed by the management entity can access the identification domain name, and associate the identification domain name with the preset terminal unique device identifier; The step of determining the identification domain name of the target user on the first application entity side based on the random user identifier, so that the preset target device managed by the management entity can access the identification domain name, and associating the identification domain name with the preset terminal unique device identifier, includes: Based on the random user identifier, determining an identifier domain name of the target user on the first application entity side; Receive a second asymmetric key generated by the preset key system based on the identification domain name trigger, encrypt the random user identifier based on the private key in the second asymmetric key, so that the preset target device managed by the management entity can access the encrypted identification domain name, and decrypt the random user identifier in the identification domain name based on the second public key in the second asymmetric key; The management entity associates the decrypted random user identifier with a preset terminal unique device identifier; The preset target device managed by the management entity is received, and the first association information is reported after the identification domain name is associated with the preset terminal unique device identifier.

2. The user identification method according to claim 1, characterized in that: The step of determining the identification domain name of the target user on the first application entity side based on the random user identifier includes: The random user identifier and the preset domain name of the first application entity are combined according to a preset composition rule to form an identifier domain name of the target user at the first application entity side.

3. The user identification method according to claim 1, characterized in that: After the step of receiving the preset target device managed by the management entity, associating the identification domain name with the preset terminal unique device identifier, and reporting the first association information, the method includes: Acquire user information of the target user, wherein the user information includes a service expiration time of the first application entity for the target user; The user information is sent to the management entity so that the management entity can complete various identifications of the target user in preset dimensions.

4. The user identification method according to claim 1, characterized in that: Before the step of acquiring a random user identifier of the target user on the first application entity side when detecting that the target user uses the first application entity, the method includes: Generating a first asymmetric key on the first application entity side; The first public key in the first asymmetric key is sent to the management entity, so that a preset target device of the management entity can subsequently authenticate the first application entity.

5. The user identification method according to claim 1, characterized in that: The step of determining the identification domain name of the target user on the first application entity side based on the random user identifier, so that the preset target device managed by the management can access the identification domain name, and associating the identification domain name with the preset terminal unique device identifier, includes: Based on the random user identifier, determine the identification domain name of the target user on the first application entity side, so that the preset target device managed by the management entity can access the identification domain name, and associate the identification domain name with the preset terminal unique device identifier; The management entity verifies whether the identification domain name has been changed based on a preset MD5 verification method, and if it has not been changed, associates the identification domain name with a preset terminal unique device identifier.

6. The user identification method according to claim 1, characterized in that: After the step of receiving the preset target device managed by the management entity, associating the identification domain name with the preset terminal unique device identifier, and reporting the first association information, the method includes: Receiving user characteristic information of the user determined by the preset target device based on the first association information and second association information of other second application entities; Targeted recommendations are made based on the user feature information.

7. The user identification method according to claim 6, characterized in that: The step of performing targeted recommendation based on the user characteristic information includes: Acquire a product feature representation vector of the first application entity, and acquire a user feature representation vector corresponding to the user feature information; Based on the product feature representation vector and the user feature representation vector, a product recommendation is made to the target user.

8. A user identification method, characterized in that: A preset target device applied to a management entity, the management entity is in communication connection with a terminal, the terminal includes a first application entity, and the user identification method includes: When detecting the identification domain name of the first application entity side, associating the identification domain name with a preset terminal unique device identifier; When the first application entity detects that the target user uses the first application entity, it generates a random user identifier of the target user, and based on the random user identifier, determines the identification domain name of the target user on the first application entity side for access by the preset target device managed by the management entity; Accessing the identification domain name, and associating the identification domain name with a preset terminal unique device identifier; The step of accessing the identification domain name and associating the identification domain name with a preset terminal unique device identifier includes: Access the encrypted identification domain name, and decrypt the random user identifier in the identification domain name based on the second public key in the second asymmetric key; The second asymmetric key is generated by the first application entity receiving a preset key system triggered based on the identification domain name, and the encrypted identification domain name is obtained by the first application entity encrypting the random user identifier based on the private key in the second asymmetric key; After associating the identification domain name with the preset terminal unique device identifier, first association information is obtained, and the first association information is reported to the first application entity.

9. The user identification method according to claim 8, characterized in that: After the step of associating the identification domain name with the preset terminal unique device identifier to obtain first association information, and reporting the first association information to the first application entity, the method includes: Acquire second association information of other second application entities associated with the preset terminal unique device identifier; user characteristic information of the user determined based on the first association information and second association information of other second application entities; Targeted recommendations are made based on the user feature information.

10. A user identification device, characterized in that: Applied to a terminal, the terminal is in communication connection with a management entity, the terminal includes a first application entity, and the user identification device includes: A first detection module, configured to obtain a random user identifier of the target user on the first application entity side when detecting that the target user uses the first application entity; A first determination module is used to determine the identification domain name of the target user on the first application entity side based on the random user identifier, so that the preset target device managed by the management entity can access the identification domain name, and associate the identification domain name with a preset terminal unique device identifier; The first determination module is specifically configured to determine an identification domain name of the target user on the first application entity side based on the random user identifier; Receive a second asymmetric key generated by the preset key system based on the identification domain name trigger, encrypt the random user identifier based on the private key in the second asymmetric key, so that the preset target device managed by the management entity can access the encrypted identification domain name, and decrypt the random user identifier in the identification domain name based on the second public key in the second asymmetric key; The management entity associates the decrypted random user identifier with a preset terminal unique device identifier; The first receiving module is used to receive the preset target device managed by the management entity, and report the first association information after associating the identification domain name with the preset terminal unique device identifier.

11. The user identification device according to claim 10, characterized in that: The first detection module comprises: The composition unit is used to combine the random user identifier and the preset domain name of the first application entity according to a preset composition rule to compose the identification domain name of the target user at the first application entity side.

12. The user identification device according to claim 10, characterized in that: The user identification device also includes: A first acquisition module, configured to acquire user information of the target user, wherein the user information includes a service expiration time of the first application entity for the target user; The first sending module is used to send the user information to the management entity, so that the management entity can complete various identifications of the target user in a preset dimension.

13. The user identification device according to claim 10, characterized in that: The user identification device also includes: A generating module, configured to generate a first asymmetric key on the first application entity side; The second sending module is used to send the first public key in the first asymmetric key to the management entity, so that a preset target device of the management entity can subsequently authenticate the first application entity.

14. A user identification device, characterized in that: A preset target device applied to a management entity, the management entity is in communication connection with a terminal, the terminal includes a first application entity, and the user identification device includes: A second detection module is used to associate the identification domain name with a preset terminal unique device identifier when detecting the identification domain name of the first application entity side; When the first application entity detects that the target user uses the first application entity, it generates a random user identifier of the target user, and based on the random user identifier, determines the identification domain name of the target user on the first application entity side for access by the preset target device managed by the management entity; An access module, used to access the identification domain name and associate the identification domain name with a preset terminal unique device identifier; The access module is specifically used to access the encrypted identification domain name and decrypt the random user identifier in the identification domain name based on the second public key in the second asymmetric key; The second asymmetric key is generated by the first application entity receiving a preset key system triggered based on the identification domain name, and the encrypted identification domain name is obtained by the first application entity encrypting the random user identifier based on the private key in the second asymmetric key; The reporting module is used to associate the identification domain name with the preset terminal unique device identifier to obtain first association information, and report the first association information to the first application entity.

15. The user identification device according to claim 14, characterized in that: After the step of associating the identification domain name with the preset terminal unique device identifier to obtain first association information, and reporting the first association information to the first application entity, the apparatus includes: Acquire second association information of other second application entities associated with the preset terminal unique device identifier; user characteristic information of the user determined based on the first association information and second association information of other second application entities; Targeted recommendations are made based on the user feature information.

16. A user identification system, characterized in that: The user identification system comprises the user identification device according to claim 10 and the user identification device according to claim 14.

17. A user identification device, characterized in that: The user identification device comprises: a memory, a processor and a program stored in the memory for implementing the user identification method. The memory is used to store a program for implementing a user identification method; The processor is used to execute a program for implementing the user identification method to implement the steps of the user identification method according to any one of claims 1 to 7.

18. A storage medium, characterized in that: The storage medium stores a program for implementing the user identification method, and the program for implementing the user identification method is executed by a processor to implement the steps of the user identification method as claimed in any one of claims 1 to 7.

Citation Information

Patent Citations

  • Self-organized network

    CN102215226A

  • Internet globally unique identifier generation system and generation method thereof

    CN110727885A