CN109495562B - Method and device for acquiring equipment identifier - Google Patents
Method and device for acquiring equipment identifier Download PDFInfo
- Publication number
- CN109495562B CN109495562B CN201811334106.XA CN201811334106A CN109495562B CN 109495562 B CN109495562 B CN 109495562B CN 201811334106 A CN201811334106 A CN 201811334106A CN 109495562 B CN109495562 B CN 109495562B
- Authority
- CN
- China
- Prior art keywords
- list
- equipment
- identifier
- identification
- matching
- 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
- 238000000034 method Methods 0.000 title claims abstract description 60
- 238000012216 screening Methods 0.000 claims abstract description 21
- 230000008569 process Effects 0.000 claims description 27
- 238000012545 processing Methods 0.000 claims description 13
- 235000014510 cooky Nutrition 0.000 claims description 8
- 238000001914 filtration Methods 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 8
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 210000001072 colon Anatomy 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a method and a device for obtaining equipment identification. Wherein, the method comprises the following steps: acquiring log information, wherein the log information comprises: various equipment identifiers of the equipment, different objects use different equipment to perform access operation; and screening multiple equipment identifications of the equipment based on at least one equipment list to determine whether each equipment identification is a correct identification. The method and the device solve the technical problem that the UV calculation is inaccurate because the device IDs used by a plurality of users are the same as each other because the media end does not successfully replace the real device IDs when the users access the Internet.
Description
Technical Field
The present application relates to the field of device identifier filtering, and in particular, to a method and an apparatus for obtaining a device identifier.
Background
Some custom device IDs are often received in the log, such as device ID values in macro-defined format such as IDFA _, _ IMEI _, { IDFA },% IMEI%, etc. There are many reasons for generating these macro definition format device IDs, mainly because when the user accesses the internet, the media end does not succeed in replacing the real device ID, resulting in the device IDs used by multiple users being the same; another reason is that media or other SDKs return default values of some devices, such as default values 00000000-.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
The embodiment of the application provides a method and a device for acquiring equipment identification, so as to at least solve the technical problem that the UV calculation is inaccurate because the equipment IDs used by a plurality of users are the same as each other because a media end does not successfully replace the real equipment ID when the users access the Internet.
According to an aspect of an embodiment of the present application, there is provided a method for obtaining a device identifier, including: acquiring log information, wherein the log information comprises: various equipment identifiers of the equipment, different objects use different equipment to perform access operation; and screening multiple equipment identifications of the equipment based on at least one equipment list to determine whether each equipment identification is a correct identification.
Optionally, the device list is a black list or a white list, where the device list includes at least one of the following: IDFA list, OpenUdid list, IMEI list, android ID list, Mac list.
Optionally, in a case that each device list is a blacklist, wherein, based on at least one device list, a plurality of device identifiers of a device are subjected to a screening process, and determining whether each device identifier is a correct identifier includes: matching the same type of equipment identification with the same type of equipment list in sequence; and under the condition that the equipment identification is matched with the identification information from the homogeneous equipment list, determining that the equipment identification successfully matched with the identification information is invalid.
Optionally, in a case that the device identifier is not matched with the corresponding identification information from the same type of device list, determining that the device identifier that is not successfully matched with the identification information is a correct identifier, and determining to perform UV calculation using the device identifier.
Optionally, in the process of sequentially matching the device identifiers with the device lists of the same type, if a matching failure occurs for the first time, it is determined that the device identifier that failed to match is a correct identifier, and it is determined that UV calculation is performed using the device identifier, and the device identifier is no longer matched with the other device lists.
Optionally, in a case that each device list is a white list, wherein, based on at least one device list, a plurality of device identifiers of a device are subjected to a screening process, and determining whether each device identifier is a correct identifier includes: matching the same type of equipment identification with the same type of equipment list in sequence; and under the condition that the equipment identification is matched with the corresponding identification information from the equipment list of the same type, determining that the equipment identification successfully matched with the identification information is a correct identification, and determining to use the equipment identification for UV calculation.
Optionally, in a case that the device identifier does not match the corresponding identification information from the homogeneous device list, it is determined that the device identifier that does not successfully match the identification information is an invalid identifier.
Optionally, in the process of sequentially matching the device identifiers with the device lists of the same type, if a successful matching condition occurs for the first time, it is determined that the successfully matched device identifier is a correct identifier, and it is determined that UV calculation is performed using the device identifier, and the device identifier is no longer matched with the other device lists.
Optionally, the screening, based on the at least one device list, multiple device identifiers of the device to determine whether each device identifier is a correct identifier includes: matching the equipment identification of the equipment with the IDFA list; under the condition of successful matching with the IDFA list, continuously matching the equipment identifier of the equipment with the OpenUdid list; under the condition of successful matching with the OpenUdid list, continuously matching the equipment identifier of the equipment with the IMEI list; under the condition of successful matching with the IMEI list, continuously matching the equipment identifier of the equipment with the android ID list; under the condition of successful matching with the android ID list, continuously matching the equipment identifier of the equipment with the Mac list; in case of successful matching to Mac list, UV calculation is performed using COOKIE.
According to another aspect of the embodiments of the present application, there is also provided an apparatus for obtaining a device identifier, including: the acquisition module is used for acquiring log information, wherein the log information comprises: various equipment identifiers of the equipment, different objects use different equipment to perform access operation; and the processing module is used for screening various equipment identifications of the equipment based on at least one equipment list and determining whether each equipment identification is a correct identification.
Optionally, the device list is a black list or a white list, where the device list includes at least one of the following: IDFA list, OpenUdid list, IMEI list, android ID list, Mac list.
Optionally, in a case that each device list is a blacklist, wherein, based on at least one device list, a plurality of device identifiers of a device are subjected to a screening process, and determining whether each device identifier is a correct identifier includes: the first matching module is used for sequentially matching the same type of equipment identification with the same type of equipment list; and the first determining module is used for determining that the equipment identifier successfully matched with the identification information is an invalid identifier under the condition that the equipment identifier is matched with the corresponding identification information from the homogeneous equipment list.
Optionally, the apparatus further comprises: and the second determining module is used for determining that the equipment identifier which is not successfully matched with the identification information is a correct identifier and determining to use the equipment identifier for UV calculation under the condition that the equipment identifier is not matched with the corresponding identification information from the homogeneous equipment list.
Optionally, the apparatus further comprises: and the third determining module is used for determining that the equipment identifier which fails to be matched is a correct identifier if the condition of matching failure occurs for the first time in the process that the equipment identifier is sequentially matched with the equipment lists of the same type, and determining that the equipment identifier is not matched with other equipment lists when the equipment identifier is used for UV calculation.
Optionally, in a case that each device list is a white list, where multiple device identifiers of a device are filtered based on at least one device list, and it is determined whether each device identifier is a correct identifier, the apparatus further includes: the second matching module is used for matching the identifiers of the devices of the same type with the lists of the devices of the same type in sequence; and the fourth determining module is used for determining that the equipment identifier successfully matched with the identification information is a correct identifier and determining to use the equipment identifier for UV calculation under the condition that the equipment identifier is matched with the corresponding identification information from the homogeneous equipment list.
Optionally, the apparatus further includes a fifth determining module, configured to determine, when the device identifier is not matched with the corresponding identification information from the device list of the same type, that the device identifier that is not successfully matched with the identification information is an invalid identifier.
Optionally, the apparatus further includes a sixth determining module, configured to, in a process that the device identifier is sequentially matched with the device lists of the same type, determine, if a successful matching condition occurs for the first time, that the successfully matched device identifier is a correct identifier, and determine that the device identifier is no longer matched with the other device lists when the device identifier is used for UV calculation.
Optionally, the apparatus further includes a third matching module, configured to match the device identifier of the device with the IDFA list; under the condition of successful matching with the IDFA list, continuously matching the equipment identifier of the equipment with the OpenUdid list; under the condition of successful matching with the OpenUdid list, continuously matching the equipment identifier of the equipment with the IMEI list; under the condition of successful matching with the IMEI list, continuously matching the equipment identifier of the equipment with the android ID list; under the condition of successful matching with the android ID list, continuously matching the equipment identifier of the equipment with the Mac list; and the calculation module is used for performing UV calculation by using COOKIE under the condition that the matching with the Mac list is successful.
According to still another aspect of the embodiments of the present application, there is further provided a storage medium, where the storage medium includes a stored program, and the program, when running, controls a device in which the storage medium is located to perform the above method for acquiring a device identifier.
According to still another aspect of the embodiments of the present application, there is provided a processor, configured to execute a program, where the method for acquiring a device identifier when the program is executed is as above.
In the embodiment of the present application, acquiring log information is adopted, where the log information includes: various equipment identifiers of the equipment, different objects use different equipment to perform access operation; the method comprises the steps of screening multiple equipment identifications of equipment based on at least one equipment list, determining whether each equipment identification is a correct identification mode, screening the obtained equipment identifications of the mobile equipment accessing the Internet through a preset equipment list, removing invalid equipment identifications, and enabling the invalid equipment identifications not to participate in final UV calculation, so that the technical effect of enabling the UV calculation to be more accurate in the process of calculating the UV is achieved, and the technical problems that the equipment IDs used by a plurality of users are the same and the UV calculation is inaccurate due to the fact that the media end does not successfully replace the real equipment IDs when the users access the Internet are solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a flowchart of a method for obtaining a device identifier according to an embodiment of the present application;
fig. 2 is a flowchart of another method for obtaining a device identifier according to an embodiment of the present application;
fig. 3 is a block diagram of an apparatus for acquiring a device identifier according to an embodiment of the present application;
fig. 4 is a block diagram of another apparatus for acquiring a device identifier according to an embodiment of the present application;
fig. 5 is a block diagram of another apparatus for acquiring a device identifier according to an embodiment of the present application;
fig. 6 is a block diagram of another apparatus for acquiring a device identifier according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. 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 application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In accordance with an embodiment of the present application, there is provided a method embodiment for obtaining a device identification, it should be noted that the steps illustrated in the flowchart of the drawings may be performed in a computer system such as a set of computer executable instructions, and that while a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than here.
Fig. 1 is a flowchart of a method for acquiring a device identifier according to an embodiment of the present application, and as shown in fig. 1, the method includes the following steps:
step S102, obtaining log information, wherein the log information comprises: and different objects use different devices to perform access operation.
UV is an abbreviation of Unique viewer and refers to a natural person accessing and browsing this web page through the internet, in this application, a mobile device ID is considered to be a natural person. The UV is a concept that reflects actual users, and each UV corresponds to an actual viewer more accurately than each IP. Using UV as a statistic, one can more accurately know how many visitors actually visited the corresponding web page per unit time.
In the process of actually calculating the UV, usually, when the user accesses the internet, the media side does not successfully replace the real device ID, so that the device IDs used by a plurality of users are the same, and the calculation of the UV is inaccurate, which is less than the access amount of the real user, and therefore, the devices with invalid device IDs need to be shielded, so that the calculation of the UV is more accurate.
And step S104, screening multiple device identifications of the devices based on at least one device list, and determining whether each device identification is a correct identification.
In some optional embodiments of the present application, when different users access the internet through different mobile devices, device identifiers of different mobile devices may be recorded in a log, and after obtaining the device identifiers in the log, the obtained device identifiers are screened through a device list, so as to remove invalid device identifiers. The device list stores multiple types of device identifiers.
Through the steps, the acquired equipment identifications of the mobile equipment accessing the Internet are screened through the preset equipment list, invalid equipment identifications are removed, the invalid equipment identifications do not participate in the final UV calculation, and the technical effect of enabling the UV calculation to be more accurate in the UV calculation process can be achieved.
In some optional embodiments of the present application, the device list in step S104 is a black list or a white list, where the device list includes at least one of the following: IDFA list, OpenUdid list, IMEI list, android ID list, Mac list.
An IDFA (identifier For Advertising, abbreviated IDFA) is a unique identifier associated with a device and can be used to open up advertisements between different apps. For example, when we search for a certain product in Taobao and then browse a web page by using a browser, the advertisement of the web page will show the advertisement of the corresponding product. An IDFA is a 16-ary 32-bit string that can be used for ad tracking.
UDIDs (Unique Device identifiers), which are Unique Device identifiers for devices, are often required by mobile advertisers and gaming network operators to identify player users and track user activity. OpenUdid is an open source solution for UDID.
The IMEI (International Mobile Equipment Identity, abbreviated as IMEI) is an abbreviation of an International Mobile Equipment Identity, commonly called "Mobile phone serial number", and is used for identifying each independent Mobile phone in the GSN Mobile network, and is equivalent to an Identity card number of the Mobile phone.
Android ID is a 64bit (16BYTES) number generated when the Android system is first started, and if the device is restored by the wipe, the ID will be reset (i.e., the Android ID will change).
The Mac list is a Mac Address list, where Mac is a short name of Media Access Control Address, a Media Access Control Address, also called an ethernet Address, and each mobile device has a unique Mac Address.
In the embodiment of the present application, the device identifier includes, but is not limited to, the IDFA value, the OpenUdid value, the IMEI value, the android id value, and the MAC address.
In some optional embodiments of the present application, in a case that each device list is a blacklist, wherein, based on at least one device list, a plurality of device identifiers of a device are subjected to a screening process, and it is determined whether the device identifier of each device is a correct identifier, the method includes: matching the same type of equipment identification with the same type of equipment list in sequence; and under the condition that the equipment identification is matched with the corresponding identification information from the equipment list of the same type, determining that the equipment identification successfully matched with the identification information is an invalid identification.
In some optional embodiments of the present application, in a case that the device identifier does not match the corresponding identification information from the list of devices of the same type, it is determined that the device identifier that does not successfully match the identification information is a correct identifier, and it is determined to perform UV calculation using the device identifier.
It should be noted that, only if all the device identifiers of the mobile device exist in the blacklisted device list, it can be determined that the device is a device whose device identifier is invalid, for example, the IDFA identifier, the OpenUdid identifier, the IMEI identifier, and the android id identifier of one device are all in the blacklisted device list, which indicates that the IDFA identifier, the OpenUdid identifier, the IMEI identifier, and the android id identifier of the device are invalid device identifiers, but the MAC address identifier of the device is not in the blacklisted device list, and the UV calculation can still be performed by using the MAC address of the device, so the device is still treated as a device whose device identifier is correct.
In some optional embodiments of the present application, in the process of sequentially matching the device identifiers with the device lists of the same type, if a matching failure occurs for the first time, it is determined that the device identifier that failed to match is a correct identifier, and it is determined that UV calculation is performed using the device identifier, and the device identifier is no longer matched with other device lists.
It should be noted that, when the obtained device identifiers are sequentially matched with the device list, when a matching failure occurs for the first time, it is indicated that the device identifier that fails to be matched is a correct device identifier, which may be used for UV calculation, and other device identifiers of the device are no longer matched with other device lists, which may reduce the calculation amount in the data processing process through this step.
According to an optional embodiment of the present application, in a case where each device list is a white list, wherein, based on at least one device list, a plurality of device identifiers of a device are subjected to a screening process, and it is determined whether each device identifier is a correct identifier, the method includes: matching the same type of equipment identification with the same type of equipment list in sequence; and under the condition that the equipment identification is matched with the corresponding identification information from the equipment list of the same type, determining that the equipment identification successfully matched with the identification information is a correct identification, and determining to use the equipment identification for UV calculation.
According to an optional embodiment of the present application, in a case where the device identifier does not match the corresponding identification information from the homogeneous device list, it is determined that the device identifier that has not successfully matched the identification information is an invalid identifier.
It should be noted that, if any device identifier of the mobile device is located in the white list device list, it can be determined that the device is a device with a correct device identifier, for example, as long as any device identifier of the device, including an IDFA identifier, an OpenUdid identifier, an IMEI identifier, an android id identifier, and an MAC address identifier, is located in the white list device list, the device identifier may be used to perform UV calculation, that is, only if all device identifiers of the mobile device are not in the white list device list, the device is determined to be a device with an invalid device identifier.
According to an optional embodiment of the present application, in the process of sequentially matching the device identifiers with the device lists of the same type, if a successful matching condition occurs for the first time, it is determined that the device identifier that is successfully matched is a correct identifier, and it is determined that UV calculation is performed using the device identifier, and the device identifier is no longer matched with other device lists.
It should be noted that, when the obtained device identifiers are sequentially matched with the device lists of the same type, when a successful matching occurs for the first time, the device identifier that is successfully matched is indicated as a correct identifier, which may be used for UV calculation, and other device identifiers of the device are no longer matched with other device lists, which may reduce the calculation amount in the data processing process through this step.
In some optional embodiments of the present application, the screening multiple device identifiers of the device based on the at least one device list to determine whether each device identifier is a correct identifier includes: matching the equipment identification of the equipment with the IDFA list; under the condition of successful matching with the IDFA list, continuously matching the equipment identifier of the equipment with the OpenUdid list; under the condition of successful matching with the OpenUdid list, continuously matching the equipment identifier of the equipment with the IMEI list; under the condition of successful matching with the IMEI list, continuously matching the equipment identifier of the equipment with the android ID list; under the condition of successful matching with the android ID list, continuously matching the equipment identifier of the equipment with the Mac list; in case of successful matching to Mac list, UV calculation is performed using COOKIE.
Fig. 2 is a flowchart of another method for acquiring a device identifier according to an embodiment of the present application, where, as shown in fig. 2, the flowchart includes the following steps:
step S1: starting;
step S2: loading a blacklist;
invalid device identifications are added to the device list through step S2, wherein the invalid device identifications (black list) mainly include the following types: default value of system device ID; default values remove colon, remove "_" variants; monitoring default values of macro parameters of the codes; other companies' variations on the default values. In addition, the invalid device identifier also includes a list of devices that occur too frequently, and a forged list of commonly used devices. The blacklist file format is as follows:
base＝$IMP_CB
idfa＝IDFA,00000000-0000-0000-0000-000000000000,000000000000-0000-0000-0000-00000000,
OpenUdid＝UDID,OUID
imei＝IMEI,000000000000000,111111111111111
AndroidID＝ANDROIDID,9774d56d682e549c
mac＝MAC,02:00:00:00:00:00,02％3A00％3A00％3A00％3A00％3A00,020000000000,2251CD3BA50F91633780758C5F9909E3
s3, reading the mobile equipment ID in the log;
reading different types of equipment identifications in the log, and sequentially selecting the different types of equipment identifications to be sequentially matched with the equipment identifications in the equipment list.
S4, determining that the device ID length is eligible and not in the IDFA blacklist, specifically, if the device ID length is eligible and not in the IDFA blacklist, determining that the IDFA identifier is a qualified IDFA identifier, and performing step S9, selecting the ID for further processing, i.e., determining that the IDFA identifier can be finally used for UV calculation; if the IDFA length of the device is not qualified or is in the IDFA blacklist, it is determined that the IDFA identification is an invalid IDFA identification, and step S5 is performed.
S5, determining that the device ID length satisfies the condition and is not in the OpenUdid blacklist, specifically, if the OpenUdid length of the device satisfies the condition and is not in the OpenUdid blacklist, determining that the OpenUdid identifier is a qualified OpenUdid identifier, and executing step S9, selecting the ID for further processing, that is, determining that the OpenUdid identifier can be finally used for UV calculation; if the OpenUdid length of the device does not meet the condition, or is in the OpenUdid blacklist, it is determined that the OpenUdid identifier is an invalid OpenUdid identifier, and step S6 is executed.
S6, judging whether the length of the equipment ID meets the condition and is not in the IMEI blacklist, specifically, if the length of the IMEI of the equipment meets the condition and is not in the IMEI blacklist, determining that the IMEI is a qualified IMEI, executing the step S9, selecting the ID for the next processing, namely determining that the IMEI can be finally used for UV calculation; if the IMEI length of the device is not eligible or is in the IMEI blacklist, it is determined that the IMEI identity is an invalid IMEI identity, and step S7 is executed.
S7, judging whether the length of the equipment ID meets the condition and is not in the android ID blacklist, specifically, if the length of the equipment ID meets the condition and is not in the android ID blacklist, determining that the android ID is qualified, executing the step S9, selecting the ID for further processing, and determining that the android ID can be finally used for UV calculation; if the length of the android id of the device does not meet the condition or is in the android id blacklist, the android id is determined to be an invalid android id, and step S8 is executed.
S8, judging whether the length of the equipment ID meets the condition and is not in a Mac blacklist, specifically, if the length of the equipment Mac meets the condition and is not in the Mac blacklist, determining that the Mac identifier is a qualified Mac identifier, executing a step S9, selecting the ID for further processing, and determining that the Mac identifier can be finally used for UV calculation; and if the Mac length of the equipment does not meet the condition or is in a Mac blacklist, determining that the Mac identifier is an invalid Mac identifier, and performing UV calculation by using COOKIE. COOKIE refers to data stored on the user's local terminal, and some websites store data on the user's local terminal for session control tracking in order to identify the user's identity, usually encrypted, also referred to as browser cache.
S9: selecting the ID for further processing;
and S10, ending.
Through the steps, the equipment identifications in the acquired log are screened through the equipment list, invalid equipment identifications are removed, and the condition that the invalid equipment identifications participate in UV calculation to cause inaccurate UV calculation results is avoided.
Fig. 3 is a block diagram of an apparatus for acquiring a device identifier according to an embodiment of the present application, and as shown in fig. 3, the apparatus includes:
an obtaining module 30, configured to obtain log information, where the log information includes: and different objects use different devices to perform access operation.
The processing module 32 is configured to perform a screening process on multiple device identifiers of the device based on the at least one device list, and determine whether each device identifier is a correct identifier.
It should be noted that, reference may be made to the description related to the embodiment shown in fig. 1 for a preferred implementation of the embodiment shown in fig. 3, and details are not described here again.
In some optional embodiments of the present application, the device list is a black list or a white list, where the device list includes at least one of the following: IDFA list, OpenUdid list, IMEI list, android ID list, Mac list.
Fig. 4 is a block diagram of another apparatus for acquiring a device identifier according to an embodiment of the present application, and as shown in fig. 4, the apparatus further includes:
and the first matching module 34 is configured to match the identifiers of the devices of the same type with the list of devices of the same type in sequence.
The first determining module 36 is configured to, in a case that the device identifier matches the corresponding identification information from the device list of the same type, determine that the device identifier that successfully matches the identification information is an invalid identifier.
And a second determining module 38, configured to, in a case that the device identifier does not match the corresponding identification information from the homogeneous device list, determine that the device identifier that does not successfully match the identification information is a correct identifier, and determine to perform UV calculation using the device identifier.
And a third determining module 40, configured to, in the process of sequentially matching the device identifiers with the device lists of the same type, determine, if a matching failure occurs for the first time, that the device identifier that fails to match is a correct identifier, and determine that UV calculation is performed using the device identifier, and the device identifier is no longer matched with the other device lists.
It should be noted that, in the embodiment shown in fig. 4, when each device list is a blacklist, the multiple device identifiers of the device are filtered based on at least one device list, and it is determined whether each device identifier is a correct identifier.
Fig. 5 is a block diagram of another apparatus for acquiring a device identifier according to an embodiment of the present application, and as shown in fig. 5, the apparatus further includes:
and the second matching module 42 is configured to match the identifiers of the devices of the same type with the list of the devices of the same type in sequence.
And a fourth determining module 44, configured to, in a case that the device identifier matches the corresponding identification information from the device list of the same type, determine that the device identifier that successfully matches the identification information is a correct identifier, and determine to perform UV calculation using the device identifier.
A fifth determining module 46, configured to determine, in a case that the device identifier does not match the corresponding identification information from the device list of the same type, that the device identifier that has not successfully matched the identification information is an invalid identifier.
A sixth determining module 48, configured to, in the process of sequentially matching the device identifiers with the device lists of the same type, determine, if a successful matching occurs for the first time, that the device identifier that is successfully matched is a correct identifier, and determine that, using the device identifier for UV calculation, the device identifier is no longer matched with the other device lists.
It should be noted that, in the embodiment shown in fig. 5, when each device list is a white list, the screening process is performed on multiple device identifiers of a device based on at least one device list, and it is determined whether each device identifier is a correct identifier.
Fig. 6 is a block diagram of another apparatus for acquiring a device identifier according to an embodiment of the present application, and as shown in fig. 6, the apparatus further includes:
a third matching module 50, configured to match the device identifier of the device with the IDFA list; under the condition of successful matching with the IDFA list, continuously matching the equipment identifier of the equipment with the OpenUdid list; under the condition of successful matching with the OpenUdid list, continuously matching the equipment identifier of the equipment with the IMEI list; under the condition of successful matching with the IMEI list, continuously matching the equipment identifier of the equipment with the android ID list; and under the condition of successful matching with the android ID list, continuously matching the device identification of the device with the Mac list.
And a calculation module 52, configured to perform UV calculation using COOKIE if matching with the Mac list is successful.
It should be noted that, in the embodiment shown in fig. 6, when each device list is a blacklist, the multiple device identifiers of the device are filtered based on at least one device list, and it is determined whether each device identifier is a correct identifier.
The embodiment of the application also provides a storage medium, which includes a stored program, wherein when the program runs, the device where the storage medium is located is controlled to execute the above method for acquiring the device identifier.
The storage medium stores a program for executing the following functions: acquiring log information, wherein the log information comprises: various equipment identifiers of the equipment, different objects use different equipment to perform access operation; and screening multiple equipment identifications of the equipment based on at least one equipment list to determine whether each equipment identification is a correct identification.
The embodiment of the application further provides a processor, wherein the processor is used for running the program, and the method for acquiring the device identifier is executed when the program runs.
The processor is used for executing the following programs: acquiring log information, wherein the log information comprises: various equipment identifiers of the equipment, different objects use different equipment to perform access operation; and screening multiple equipment identifications of the equipment based on at least one equipment list to determine whether each equipment identification is a correct identification.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
In the above embodiments of the present application, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed technology can be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units may be a logical division, and in actual implementation, there may be another division, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
The foregoing is only a preferred embodiment of the present application and it should be noted that those skilled in the art can make several improvements and modifications without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.
Claims (16)
1. A method for obtaining a device identifier, comprising:
obtaining log information, wherein the log information comprises: various equipment identifiers of the equipment, different objects use different equipment to perform access operation;
based on at least one equipment list, screening multiple equipment identifications of the equipment to determine whether each equipment identification is a correct identification, wherein the equipment list is a blacklist or a white list, and under the condition that the equipment list is the blacklist, matching the same kind of equipment identifications with the same kind of equipment list in sequence: under the condition that the equipment identification is matched with the corresponding identification information from the equipment list of the same type, the equipment identification which is successfully matched with the identification information is determined to be an invalid identification; under the condition that the equipment identification is not matched with the corresponding identification information from the same type of equipment list, determining that the equipment identification which is not successfully matched with the identification information is a correct identification;
the correct device identification is used for UV calculation and the device identification no longer matches the list of other devices.
2. The method of claim 1, wherein the device list comprises at least one of: IDFA list, OpenUdid list, IMEI list, android ID list, Mac list.
3. The method according to claim 1, wherein in the process of sequentially matching the device identifiers with the device lists of the same type, if the matching failure occurs for the first time, the device identifier which fails to match is determined to be the correct identifier, and it is determined that UV calculation is performed using the device identifier, and the device identifier is no longer matched with other device lists.
4. The method of claim 1 or 2, wherein, in a case that each device list is a white list, wherein the screening of the multiple device identities of the device based on at least one device list to determine whether each device identity is a correct identity comprises:
matching the same type of equipment identification with the same type of equipment list in sequence;
and under the condition that the equipment identification is matched with the corresponding identification information from the equipment list of the same type, determining that the equipment identification successfully matched with the identification information is a correct identification, and determining to use the equipment identification to perform UV calculation.
5. The method according to claim 4, wherein, in the case that the device identifier does not match corresponding identification information from the homogeneous device list, it is determined that the device identifier that has not successfully matched the identification information is an invalid identifier.
6. The method according to claim 5, wherein in the process of sequentially matching the device identifiers with the device lists of the same type, if the matching is successful for the first time, the device identifier which is successfully matched is determined to be the correct identifier, and it is determined that UV calculation is performed by using the device identifier, and the device identifier is no longer matched with other device lists.
7. The method of claim 2, wherein the screening the plurality of device identifiers of the device based on at least one device list to determine whether each device identifier is a correct identifier comprises:
matching the equipment identification of the equipment with the IDFA list;
under the condition that the matching with the IDFA list is successful, continuously matching the device identification of the device with an OpenUdid list;
under the condition that the OpenUdid list is successfully matched, continuously matching the equipment identifier of the equipment with the IMEI list;
under the condition that the IMEI list is successfully matched, continuously matching the equipment identifier of the equipment with an android ID list;
under the condition that the device identifier is successfully matched with the android ID list, continuously matching the device identifier of the device with a Mac list;
in case of successful matching with the Mac list, UV calculation is performed using COOKIE.
8. An apparatus for obtaining a device identifier, comprising:
an obtaining module, configured to obtain log information, where the log information includes: various equipment identifiers of the equipment, different objects use different equipment to perform access operation;
a processing module, configured to perform screening processing on multiple device identifiers of the device based on at least one device list, and determine whether each device identifier is a correct identifier, where the device list is a blacklist or a white list, and in a case where the device list is a blacklist, match the device identifiers of the same type with the device lists of the same type in sequence: under the condition that the equipment identification is matched with the corresponding identification information from the equipment list of the same type, the equipment identification which is successfully matched with the identification information is determined to be an invalid identification; under the condition that the equipment identification is not matched with the corresponding identification information from the same type of equipment list, determining that the equipment identification which is not successfully matched with the identification information is a correct identification; the correct device identification is used for UV calculation and the device identification no longer matches the list of other devices.
9. The apparatus of claim 8, wherein the device list comprises at least one of: IDFA list, OpenUdid list, IMEI list, android ID list, Mac list.
10. The apparatus of claim 8, further comprising:
and the third determining module is used for determining that the equipment identifier which fails to be matched is a correct identifier and determining that the equipment identifier is used for UV calculation when the matching failure condition occurs for the first time in the process that the equipment identifier is sequentially matched with the equipment lists of the same type, and the equipment identifier is not matched with other equipment lists any more.
11. The apparatus according to claim 8 or 9, wherein in a case where each device list is a white list, the apparatus performs a filtering process on multiple device identifiers of the devices based on at least one device list to determine whether each device identifier is a correct identifier, and the apparatus further comprises:
the second matching module is used for matching the identifiers of the devices of the same type with the lists of the devices of the same type in sequence;
and the fourth determining module is used for determining that the equipment identifier successfully matched with the identification information is a correct identifier and determining to use the equipment identifier for UV calculation under the condition that the equipment identifier is matched with the corresponding identification information from the homogeneous equipment list.
12. The apparatus of claim 11, further comprising:
and the fifth determining module is used for determining that the equipment identifier which is not successfully matched with the identification information is an invalid identifier under the condition that the equipment identifier is not matched with the corresponding identification information from the homogeneous equipment list.
13. The apparatus of claim 12, further comprising: and a sixth determining module, configured to, in the process of sequentially matching the device identifiers with the device lists of the same type, determine, if a successful matching occurs for the first time, that the successfully matched device identifier is a correct identifier, and determine that UV calculation is performed using the device identifier, where the device identifier is no longer matched with other device lists.
14. The apparatus of claim 9, wherein the apparatus comprises:
the third matching module is used for matching the equipment identifier of the equipment with the IDFA list; under the condition that the matching with the IDFA list is successful, continuously matching the device identification of the device with an OpenUdid list; under the condition that the OpenUdid list is successfully matched, continuously matching the equipment identifier of the equipment with the IMEI list; under the condition that the IMEI list is successfully matched, continuously matching the equipment identifier of the equipment with an android ID list; under the condition that the device identifier is successfully matched with the android ID list, continuously matching the device identifier of the device with a Mac list;
and the calculation module is used for performing UV calculation by using COOKIE under the condition that the matching with the Mac list is successful.
15. A storage medium, characterized in that the storage medium comprises a stored program, wherein the program controls a device on which the storage medium is located to execute the method for acquiring a device identifier according to any one of claims 1 to 7 when running.
16. A processor, characterized in that the processor is configured to run a program, wherein the program is configured to execute the method for obtaining a device identifier according to any one of claims 1 to 7 when running.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811334106.XA CN109495562B (en) | 2018-11-09 | 2018-11-09 | Method and device for acquiring equipment identifier |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811334106.XA CN109495562B (en) | 2018-11-09 | 2018-11-09 | Method and device for acquiring equipment identifier |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109495562A CN109495562A (en) | 2019-03-19 |
| CN109495562B true CN109495562B (en) | 2022-04-12 |
Family
ID=65694098
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811334106.XA Active CN109495562B (en) | 2018-11-09 | 2018-11-09 | Method and device for acquiring equipment identifier |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109495562B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110333997B (en) * | 2019-07-15 | 2023-11-10 | 秒针信息技术有限公司 | Method and device for fusing equipment use information |
| CN110943989B (en) * | 2019-11-29 | 2022-10-25 | 恩亿科(北京)数据科技有限公司 | Equipment identification method and device, electronic equipment and readable storage medium |
| CN112685064B (en) * | 2020-12-30 | 2024-03-22 | 南京擎盾信息科技有限公司 | Processing method and device for equipment identification, storage medium and electronic device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1936890A1 (en) * | 2006-12-21 | 2008-06-25 | International Business Machines Corporation | Method and system for network terminal identification |
| CN104767756A (en) * | 2015-04-15 | 2015-07-08 | 北京京东尚科信息技术有限公司 | Equipment information processing method, client side device and server side device |
| CN106488394A (en) * | 2016-10-19 | 2017-03-08 | 广东欧珀移动通信有限公司 | A kind of method and device of equipment connection |
| CN107094088A (en) * | 2016-11-10 | 2017-08-25 | 腾讯科技（深圳）有限公司 | A kind of loiter network device identification method, device and system |
| CN107343020A (en) * | 2016-04-08 | 2017-11-10 | 三星电子株式会社 | Electronic equipment and its external device control method |
| CN108427619A (en) * | 2018-03-13 | 2018-08-21 | 腾讯科技（深圳）有限公司 | Blog management method, device, computing device and storage medium |
-
2018
- 2018-11-09 CN CN201811334106.XA patent/CN109495562B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1936890A1 (en) * | 2006-12-21 | 2008-06-25 | International Business Machines Corporation | Method and system for network terminal identification |
| CN104767756A (en) * | 2015-04-15 | 2015-07-08 | 北京京东尚科信息技术有限公司 | Equipment information processing method, client side device and server side device |
| CN107343020A (en) * | 2016-04-08 | 2017-11-10 | 三星电子株式会社 | Electronic equipment and its external device control method |
| CN106488394A (en) * | 2016-10-19 | 2017-03-08 | 广东欧珀移动通信有限公司 | A kind of method and device of equipment connection |
| CN107094088A (en) * | 2016-11-10 | 2017-08-25 | 腾讯科技（深圳）有限公司 | A kind of loiter network device identification method, device and system |
| CN108427619A (en) * | 2018-03-13 | 2018-08-21 | 腾讯科技（深圳）有限公司 | Blog management method, device, computing device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109495562A (en) | 2019-03-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109495562B (en) | Method and device for acquiring equipment identifier | |
| US10929879B2 (en) | Method and apparatus for identification of fraudulent click activity | |
| CN108009844B (en) | Method and device for determining advertisement cheating behaviors and cloud server | |
| CN108206972A (en) | Direct broadcasting room popularity processing method, device, server and storage medium | |
| CN113127723B (en) | User portrait processing method, device, server and storage medium | |
| CN110033302A (en) | The recognition methods of malice account and device | |
| CN113572752A (en) | Abnormal flow detection method and device, electronic equipment and storage medium | |
| CN110290024B (en) | Method, device and equipment for testing strategy before online | |
| CN111723083B (en) | User identity recognition method and device, electronic equipment and storage medium | |
| CN110188276B (en) | Data transmission device, method, electronic device, and computer-readable storage medium | |
| CN111612085B (en) | Method and device for detecting abnormal points in peer-to-peer group | |
| CN115955332A (en) | Abnormal traffic filtering method and device for authentication system and electronic equipment | |
| CN109495350B (en) | Office data checking method, office data checking device and storage medium | |
| CN108696873B (en) | False user identification method and device | |
| US10764237B2 (en) | System and method for maintaining coherence of association across a network address change or reassignment | |
| CN110943989B (en) | Equipment identification method and device, electronic equipment and readable storage medium | |
| CN107241347A (en) | The analysis method and device of ad traffic quality | |
| WO2017149159A1 (en) | Counterfeit electronic device detection | |
| CN111008868A (en) | Advertisement monitoring method, system and computer readable storage medium | |
| CN112785315A (en) | Batch registration identification method and device | |
| CN107357795B (en) | Method and device for monitoring association degree between websites | |
| CN110830314B (en) | Method and device for determining abnormal traffic | |
| CN112559586A (en) | Method and system for acquiring home user characteristic data | |
| CN113923190A (en) | Method and device for identifying equipment identification jump, server and storage medium | |
| CN112188291B (en) | Method and device for identifying advertisement position abnormity |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201217 Address after: Room 2020, 2 / F, building 27, No. 25, North Third Ring Road West, Haidian District, Beijing 100098 Applicant after: Beijing minglue Zhaohui Technology Co.,Ltd. Address before: Room 9014, 9 / F, building 3, yard 30, Shixing street, Shijingshan District, Beijing 100041 Applicant before: ADMASTER TECHNOLOGY (BEIJING) Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |