CN112383510B - Method and device for uniquely identifying user association - Google Patents
Method and device for uniquely identifying user association Download PDFInfo
- Publication number
- CN112383510B CN112383510B CN202011147620.XA CN202011147620A CN112383510B CN 112383510 B CN112383510 B CN 112383510B CN 202011147620 A CN202011147620 A CN 202011147620A CN 112383510 B CN112383510 B CN 112383510B
- Authority
- CN
- China
- Prior art keywords
- user
- anonymous
- unique identifier
- registration
- new
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the application provides a method and a device for uniquely identifying user association, which comprises the following steps: acquiring an ID used by a current event, and judging whether the ID is registered or not; if the ID is judged not to be registered, generating a first anonymous ID and generating a first unique identifier for the ID; and when the first anonymous ID is detected to be registered, generating a first registration ID and logging in, associating the first anonymous ID with the first registration ID, and storing all behaviors of the user in a storage space corresponding to the first unique identifier. According to the method, the anonymous ID and the registration ID are bound in an associated mode, each client is allowed to have two IDs, the anonymous ID can record user behavior data under the condition that the user does not log in, the registration ID records user behavior data after the user logs in, after the anonymous ID and the registration ID are bound in an associated mode, the user behavior data recorded by the two IDs are considered to occur in the same user entity, only one user is counted during user correlation analysis, and more accurate user tracking can be achieved.
Description
Technical Field
The embodiment of the invention relates to the technical field of user equipment and account association, in particular to a method and a device for uniquely identifying user association.
Background
The existing user equipment binding scheme associates user login information with current equipment, ensures that events operated by the user and the user can be associated and inquired, confirms all actions of the user on the equipment and provides inquiry basis for user-related data such as funnels, reservations, sessions and the like involved in operation.
The prior art has the following defects: (1) When the same user logs in a plurality of devices, the operation data of the new device when the new device is not logged in cannot be associated; (2) The specific time for switching the equipment by the user cannot be confirmed, so that certain influence is caused on analysis; (3) When a plurality of platforms upload data, the data cannot be completely classified into the same user event; (4) Once a user associates with a device, it cannot be released, and it is theoretically more reasonable to have a dynamic association with device changes.
Disclosure of Invention
In order to solve the problems, according to the generated unique identification ID, all equipment behaviors can be associated as long as an account is logged in, the user information and events operated by the user can be associated for inquiry, all the behaviors of the user on the equipment are confirmed, and inquiry bases are provided for user-related data analysis such as funnels, retention and sessions involved in operation. The specific technical scheme is as follows:
the method for uniquely identifying the user association provided by the embodiment of the invention comprises the following steps:
acquiring an ID used by a current event, and judging whether the ID is registered or not;
if the ID is judged not to be registered, generating a first anonymous ID, generating a first unique identifier for the ID, and storing the user behavior corresponding to the current event in a storage space corresponding to the first unique identifier;
and when the first anonymous ID is detected to be registered, generating a first registration ID and logging in, calling an alias interface of the SDK, associating the first anonymous ID with the first registration ID, and storing all user behaviors after logging in a storage space corresponding to the first unique identifier.
Further, if the first registration ID logs out, the user behavior after logging out is still stored in the storage space corresponding to the first unique identifier.
Further, if it is detected that a new second registered ID that has already been registered is associated with the first anonymous ID, a new second unique identifier is generated, and the user behavior is stored in a storage space corresponding to the new second unique identifier.
Further, if it is detected that the second anonymous ID logged in by the new device is associated with the first registration ID, a new third unique identifier is generated, and the user behavior is stored in a storage space corresponding to the new third unique identifier.
Another aspect of the present application further provides a device for uniquely identifying a user association, which includes an obtaining module, configured to obtain an ID used by a current event, and determine whether the ID is registered;
the first generation module is used for generating a first anonymous ID if the ID is judged not to be registered, generating a first unique identifier for the ID, and storing the user behavior corresponding to the current event in a storage space corresponding to the first unique identifier;
and the association module is used for detecting that the first anonymous ID is registered, generating a first registration ID and logging in, calling an alias interface of the SDK, associating the first anonymous ID with the first registration ID, and storing all user behaviors after logging in a storage space corresponding to the first unique identifier.
Further, the system further comprises a log-out module, which is used for logging out the first registration ID, and the user behavior after logging out is still stored in the storage space corresponding to the first unique identifier.
Further, the system further comprises a new association detection module, configured to detect that a new second registered ID that has been registered is associated with the first anonymous ID, generate a new second unique identifier, and store the user behavior in a storage space corresponding to the new second unique identifier.
Further, the new device detecting module is configured to generate a new third unique identifier if it is detected that a second anonymous ID in which the new device logs in is associated with the first registration ID, and store the user behavior in a storage space corresponding to the new third unique identifier.
The embodiment of the application provides a method and a device for uniquely identifying user association, wherein the method comprises the following steps: acquiring an ID used by a current event, and judging whether the ID is registered or not; if the ID is judged not to be registered, generating a first anonymous ID, generating a first unique identifier for the ID, and storing the user behavior corresponding to the current event in a storage space corresponding to the first unique identifier; and when the first anonymous ID is detected to be registered, generating a first registration ID and logging in, calling an alias interface of the SDK, associating the first anonymous ID with the first registration ID, and storing all user behaviors after logging in a storage space corresponding to the first unique identifier. According to the method, each client is allowed to have two IDs, the anonymous ID can record user behavior data under the condition that the user does not log in, the registered ID records the user behavior data after the user logs in, and after the anonymous ID and the registered ID are bound in an associated mode, the user behavior data recorded by the two IDs are considered to occur in the same user entity and only count as one user when the user-related analysis such as events, funnels, retention and the like is carried out. Thus, if this approach is used accurately, more accurate user tracking can be achieved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below. It should be apparent that the drawings in the following description are merely exemplary and that other implementation drawings may be derived from the provided drawings by those of ordinary skill in the art without inventive effort.
The structures, ratios, sizes, and the like shown in the present specification are only used for matching with the contents disclosed in the specification, so that those skilled in the art can understand and read the present invention, and do not limit the conditions for implementing the present invention, so that the present invention has no technical significance, and any structural modifications, changes in the ratio relationship, or adjustments of the sizes, without affecting the functions and purposes of the present invention, should still fall within the scope of the present invention.
Fig. 1 is a flowchart of a method for uniquely identifying a user association according to an embodiment of the present application;
Detailed Description
The present invention is described in terms of specific embodiments, and other advantages and benefits of the present invention will become apparent to those skilled in the art from the following disclosure. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a flowchart of a method for uniquely identifying a user association according to an embodiment of the present application; the application provides a method for uniquely identifying user association, which comprises the following steps: acquiring an ID used by a current event, and judging whether the ID is registered or not;
if the ID is judged not to be registered, generating a first anonymous ID, generating a first unique identifier for the ID, and storing the user behavior corresponding to the current event in a storage space corresponding to the first unique identifier;
and when the first anonymous ID is detected to be registered, generating a first registration ID and logging in, calling an alias interface of the SDK, associating the first anonymous ID with the first registration ID, and storing all user behaviors after logging in a storage space corresponding to the first unique identifier.
Further, if the first registration ID logs out, the user behavior after logging out is still stored in the storage space corresponding to the first unique identifier.
The embodiment of the application mainly utilizes PIKA (a source opened by 360-odd tiger company) Redis-like storage system for storage, and because the bottom layer utilizes Redis-like real-time storage data service, a master-slave mechanism not only ensures real-time association of user equipment, but also has better disaster tolerance capability.
The method for uniquely identifying the user association can be used for associating and binding the anonymous ID and the registration ID, the anonymous ID can record user behavior data under the condition that the user does not log in, and the registration ID records the user behavior data after the user logs in. The user may associate the anonymous ID with the registration ID by invoking the alias interface.
One anonymous ID can be bound to only one registration ID, and the same one registration ID can be bound to only one anonymous ID. Specifically, if it is detected that a new second registration ID that has already been registered is associated with the first anonymous ID, a new second unique identifier is generated, and the user behavior is stored in the storage space corresponding to the new second unique identifier. And if the fact that the second anonymous ID logged in by the new device is associated with the first registration ID is detected, generating a new third unique identifier, and storing the user behavior in a storage space corresponding to the new third unique identifier. That is, when a user logs in by using a registered new account, the new account cannot be bound with the registered account already bound; if the user operates with a completely new device, the association is also unsuccessful if the account anonymous ID of the completely new device is associated with the registered ID that has been associated.
The following describes a mechanism of user identification in an actual scenario, see table 1, where table 1 is an association process table of a method for uniquely identifying user association provided in the embodiment of the present application, where:
TABLE 1
Transmitted xwho: the user ID used to indicate the current event may be an anonymous ID or a registration ID. If it is the ID association operation alias, both IDs will be sent simultaneously.
Whether or not to register the ID: whether the user ID of the current behavior is a registration ID.
The ark distict _ id: the unique identifier distributed to the user in the ark is a final basis for calculating the number of triggering users, funnels, retention and the like, and corresponds to a user _ id in an events table and an id field in a users table in the user-defined query.
The detailed procedure is described below:
a certain user newly installs App on the millet mobile phone and carries out a series of operations, the anonymous ID generated by the SDK is X, and the corresponding assigned ark distict _ ID is 1.
The user registers and logs in with a registration ID of a, where an alias interface of the SDK needs to be called, and at this time the ark will successfully associate the anonymous ID X with the registration ID a.
The user continues through a series of activities after logging in.
The user logs off and proceeds through a series of operations, the SDK does not invoke any method, and the ark still uses the registration ID a to identify the current user at this time.
The user logs in using an account B that is registered but not accessing the ark system, at which time the ark will attempt to associate X with B, and since X is already associated with a, the association will fail, and a new ark distint _ id will be assigned 2.
The user takes a series of actions using account B, where the arks all use the registration ID B to identify the user.
The user changes a brand-new apple mobile phone and carries out a series of operations, and since the user does not log in yet, the user is identified by the ark through the brand-new anonymous ID Y, and the corresponding assigned ark distint _ ID is 3.
The user logs in on the apple mobile phone by using an account A, at the moment, the ark tries to associate the anonymous ID Y with the registration ID A, and since A is already associated with X, association fails, but the user still switches to the user with A as the registration ID, and the corresponding ark distint _ ID is still 1.
Subsequent actions by the user on the iphone are identified by the registration ID a.
The embodiment of the application provides a method and a device for uniquely identifying user association, wherein the method comprises the following steps: acquiring an ID used by a current event, and judging whether the ID is registered or not; if the ID is judged not to be registered, generating a first anonymous ID, generating a first unique identifier for the ID, and storing the user behavior corresponding to the current event in a storage space corresponding to the first unique identifier; and when the first anonymous ID is detected to be registered, generating a first registration ID and logging in, calling an alias interface of the SDK, associating the first anonymous ID with the first registration ID, and storing all user behaviors after logging in a storage space corresponding to the first unique identifier. According to the method, each client is allowed to have two IDs, the anonymous ID can record user behavior data under the condition that the user does not log in, the registered ID records the user behavior data after the user logs in, and after the anonymous ID and the registered ID are bound in an associated mode, the user behavior data recorded by the two IDs are considered to occur in the same user entity and only count as one user when the user-related analysis such as events, funnels, retention and the like is carried out. Thus, if this approach is used accurately, more accurate user tracking can be achieved.
Another aspect of the present application further provides a device for uniquely identifying a user association, which includes an obtaining module, configured to obtain an ID used by a current event, and determine whether the ID is registered;
the first generation module is used for generating a first anonymous ID if the ID is judged not to be registered, generating a first unique identifier for the ID, and storing the user behavior corresponding to the current event in a storage space corresponding to the first unique identifier;
and the association module is used for detecting that the first anonymous ID is registered, generating a first registration ID and logging in, calling an alias interface of the SDK, associating the first anonymous ID with the first registration ID, and storing all user behaviors after logging in a storage space corresponding to the first unique identifier.
Further, the system further comprises a log-out module, which is used for logging out by the first registration ID, and the user behavior after logging out is still stored in the storage space corresponding to the first unique identifier.
Further, the system further comprises a new association detection module, configured to detect that a new second registered ID that has been registered is associated with the first anonymous ID, generate a new second unique identifier, and store the user behavior in a storage space corresponding to the new second unique identifier.
Further, the new device detecting module is configured to generate a new third unique identifier if it is detected that a second anonymous ID in which the new device logs in is associated with the first registration ID, and store the user behavior in a storage space corresponding to the new third unique identifier.
Although the invention has been described in detail above with reference to a general description and specific examples, it will be apparent to one skilled in the art that modifications or improvements may be made thereto based on the invention. Accordingly, such modifications and improvements are intended to be within the scope of the invention as claimed.
Claims (4)
1. A method of uniquely identifying a user association, comprising the steps of:
acquiring an ID used by a current event, and judging whether the ID is registered or not;
if the ID is judged not to be registered, generating a first anonymous ID, generating a first unique identifier for the ID, and storing the user behavior corresponding to the current event in a storage space corresponding to the first unique identifier;
when the first anonymous ID is detected to be registered, a first registration ID is generated and logged in, an alias interface of the SDK is called, the first anonymous ID and the first registration ID are associated, and all user behaviors after logging in are stored in a storage space corresponding to the first unique identifier;
if the fact that the registered new second registration ID is associated with the first anonymous ID is detected, a new second unique identifier is generated, and the user behavior is stored in a storage space corresponding to the new second unique identifier;
and if the fact that the second anonymous ID logged in by the new device is associated with the first registration ID is detected, generating a new third unique identifier, and storing the user behavior in a storage space corresponding to the new third unique identifier.
2. The method of claim 1, wherein if the first registration ID is logged off, the logged-off user behavior is still stored in the storage space corresponding to the first unique identifier.
3. The device for uniquely identifying the user association is characterized by comprising an acquisition module, a registration module and a processing module, wherein the acquisition module is used for acquiring an ID (identity) used by a current event and judging whether the ID is registered or not;
the first generation module is used for generating a first anonymous ID if the ID is judged not to be registered, generating a first unique identifier for the ID, and storing the user behavior corresponding to the current event in a storage space corresponding to the first unique identifier;
the association module is used for detecting that the first anonymous ID is registered, generating a first registration ID and logging in, calling an alias interface of the SDK, associating the first anonymous ID with the first registration ID, and storing all user behaviors after logging in a storage space corresponding to the first unique identifier;
the device also comprises a new association detection module used for generating a new second unique identifier when detecting that the new registered second registered ID is associated with the first anonymous ID, and the user behavior is stored in a storage space corresponding to the new second unique identifier;
and the new device detection module is used for generating a new third unique identifier when detecting that the second anonymous ID logged in by the new device is associated with the first registration ID, and the user behavior is stored in a storage space corresponding to the new third unique identifier.
4. The apparatus of claim 3, further comprising a log-out module, configured to log out the first registration ID, and the logged-out user behavior is still stored in the storage space corresponding to the first unique identifier.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011147620.XA CN112383510B (en) | 2020-10-23 | 2020-10-23 | Method and device for uniquely identifying user association |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011147620.XA CN112383510B (en) | 2020-10-23 | 2020-10-23 | Method and device for uniquely identifying user association |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112383510A CN112383510A (en) | 2021-02-19 |
| CN112383510B true CN112383510B (en) | 2022-10-11 |
Family
ID=74580823
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011147620.XA Active CN112383510B (en) | 2020-10-23 | 2020-10-23 | Method and device for uniquely identifying user association |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112383510B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116366329B (en) * | 2023-03-28 | 2024-09-20 | 加客云科技(河北)有限公司 | Method for identifying unique ID of user identity by third party SDK |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2005051463A (en) * | 2003-07-28 | 2005-02-24 | Mitsubishi Electric Corp | Anonymity database system |
| CN101873301A (en) * | 2009-04-22 | 2010-10-27 | 索尼株式会社 | Anonymous registration system and method |
| CN103118358A (en) * | 2012-11-16 | 2013-05-22 | 佳都新太科技股份有限公司 | Unique identification mobile phone user registration method |
| CN104364779A (en) * | 2012-06-13 | 2015-02-18 | 歌乐株式会社 | Service provision system, service computer, and terminal |
| CN104852926A (en) * | 2015-05-28 | 2015-08-19 | 北京奇艺世纪科技有限公司 | Method and device for registering account |
| CN107609469A (en) * | 2017-07-28 | 2018-01-19 | 北京建筑大学 | Community network association user method for digging and system |
| CN108156273A (en) * | 2017-12-14 | 2018-06-12 | 北京奇艺世纪科技有限公司 | A kind of anonymous ID generation methods, device and electronic equipment |
| CN110557363A (en) * | 2019-06-03 | 2019-12-10 | 北京城市网邻信息技术有限公司 | identity verification method, device and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120311036A1 (en) * | 2011-06-03 | 2012-12-06 | Huhn Derrick S | Friend recommendation system and method |
-
2020
- 2020-10-23 CN CN202011147620.XA patent/CN112383510B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2005051463A (en) * | 2003-07-28 | 2005-02-24 | Mitsubishi Electric Corp | Anonymity database system |
| CN101873301A (en) * | 2009-04-22 | 2010-10-27 | 索尼株式会社 | Anonymous registration system and method |
| CN104364779A (en) * | 2012-06-13 | 2015-02-18 | 歌乐株式会社 | Service provision system, service computer, and terminal |
| CN103118358A (en) * | 2012-11-16 | 2013-05-22 | 佳都新太科技股份有限公司 | Unique identification mobile phone user registration method |
| CN104852926A (en) * | 2015-05-28 | 2015-08-19 | 北京奇艺世纪科技有限公司 | Method and device for registering account |
| CN107609469A (en) * | 2017-07-28 | 2018-01-19 | 北京建筑大学 | Community network association user method for digging and system |
| CN108156273A (en) * | 2017-12-14 | 2018-06-12 | 北京奇艺世纪科技有限公司 | A kind of anonymous ID generation methods, device and electronic equipment |
| CN110557363A (en) * | 2019-06-03 | 2019-12-10 | 北京城市网邻信息技术有限公司 | identity verification method, device and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| "Traceable Anonymous Authentication and Key Exchange Protocol for Privacy-Aware Cloud Environments";Han-Yu Lin;《IEEE Systems Journal》;20180914;第13卷(第2期);第1608-1617页 * |
| "面向VANET的多层次匿名认证方案";姚汝贤;《中国科技论文》;20150723;第10卷(第14期);第1626-1631页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112383510A (en) | 2021-02-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107122258B (en) | Method and equipment for checking state code of test interface | |
| CN107480483B (en) | Account detection method and device | |
| CN106878108B (en) | Network flow playback test method and device | |
| CN107168845B (en) | Fault positioning method and device | |
| CN108038039B (en) | Method for recording log and micro-service system | |
| CN103685354A (en) | Method and device for testing based on RMI protocol | |
| CN103259688A (en) | Failure diagnosis method and device of distributed storage system | |
| CN112383510B (en) | Method and device for uniquely identifying user association | |
| CN111506496A (en) | Test data acquisition method and device, electronic equipment and storage medium | |
| CN110134583B (en) | Software testing and data processing method and device | |
| CN108282446B (en) | Method and apparatus for identifying scanner | |
| CN112698820B (en) | Unified monitoring management method and device for memory and switch and computer equipment | |
| CN105743725A (en) | Method and device for testing application programs | |
| CN107040546B (en) | Domain name hijacking detection and linkage handling method and system | |
| CN105847320A (en) | Resource obtaining method and device | |
| US10863347B2 (en) | Policy enhancement for mixed capability devices | |
| CN104468862B (en) | A kind of method, apparatus and system of IP address binding | |
| CN105791308B (en) | Method, device and system for actively identifying domain user login event information | |
| CN108255715B (en) | Test result processing method and terminal equipment | |
| CN112699000A (en) | Data processing method and device, readable storage medium and electronic equipment | |
| CN116170408A (en) | Domain name server analysis acceleration method and device | |
| US20190342448A1 (en) | Methods and devices for verifying a communication number | |
| CN112492598A (en) | WIFI network setting method and system, mobile terminal and storage medium | |
| CN110647474A (en) | Anti-interference method and device for automatic regression test, computer equipment and storage medium | |
| CN115168489B (en) | Data certification method and device based on blockchain |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 100015 Room 305, 3rd floor, building 25, 10 Jiuxianqiao Road, Chaoyang District, Beijing Patentee after: Beijing Analysys Digital Intelligence Technology Co.,Ltd. Address before: 100020 Room 305, 3rd floor, building 25, 10 Jiuxianqiao Road, Chaoyang District, Beijing Patentee before: BEIJING ANALYSYS THINK TANK NETWORK TECHNOLOGY Co.,Ltd. |