Method and apparatus for determining a unique identifier of a device

Abstract

The present invention discloses a method and device for determining a unique device identifier. The method includes: detecting a unique identifier acquisition instruction triggered by a user for the device; the unique identifier acquisition instruction includes a first device identifier corresponding to the device and a user identifier corresponding to the user; the unique identifier acquisition instruction is used to acquire the unique device identifier corresponding to the device; according to the unique identifier acquisition instruction, determining whether there is a unique device identifier pre-stored in the device; when the determination result is yes, calling the unique device identifier; when the determination result is no, generating a unique device identifier corresponding to the device according to the unique identifier acquisition instruction, and calling the unique device identifier. It can be seen that the present invention can reduce the situation where the unique device identifier changes when the data corresponding to the device changes, improve the stability and accuracy of the unique device identifier, and is beneficial for business personnel to perform statistical analysis operations, thereby improving the convenience and statistical efficiency of business personnel in performing statistical analysis operations.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method and apparatus for determining a unique identifier of a device. Background Art

[0002] With the continuous upgrade of device systems (such as the Android system), official system protections for user privacy have become increasingly stringent, and hardware identifiers such as IMEI have been disabled. As a result, mobile client apps are unable to obtain the device's unique identifier through the device system's API. In the business development field, developers need to obtain the device's unique identifier for statistical analysis, including DAU and MAU statistics, behavioral statistics, and ad activation statistics.

[0003] Currently, the main method for obtaining a device's unique identifier is to obtain multiple key information of the device system, construct a device's unique identifier based on the multiple key information, and store the device's unique identifier in different directories of the mobile client (internal storage and external storage). Practice has shown that since existing mobile client apps cannot force mobile client users to authorize, the device's unique identifier cannot be saved to external storage. Therefore, in some cases, such as uninstalling the mobile client app or clearing user data, resetting the device label, etc., the device's unique identifier is prone to change. It can be seen that it is particularly important to provide a method that can solve the problem of the device's unique identifier being prone to change. Summary of the Invention

[0004] The technical problem to be solved by the present invention is to provide a method and apparatus for determining a unique identifier of a device, which can solve the problem that the unique identifier of a device is prone to change.

[0005] In order to solve the above technical problems, the first aspect of the present invention discloses a method for determining a unique identifier of a device, the method comprising:

[0006] Detecting a unique identification acquisition instruction triggered by a user for a device; the unique identification acquisition instruction includes a first device identification corresponding to the device and a user identification corresponding to the user; the unique identification acquisition instruction is used to obtain a device unique identification corresponding to the device;

[0007] Determining, according to the unique identifier acquisition instruction, whether there is a device unique identifier pre-stored in the device;

[0008] When it is determined that the device unique identifier pre-stored in the device exists, calling the device unique identifier;

[0009] When it is determined that the unique device identifier pre-stored in the device does not exist, according to the unique identifier acquisition instruction, generate the unique device identifier corresponding to the device, and call the unique device identifier.

[0010] As an optional implementation manner, in the first aspect of the present invention, the generating the unique device identifier corresponding to the device according to the unique identifier acquisition instruction includes:

[0011] According to the unique identifier acquisition instruction, obtain the device identifier set corresponding to the device; the device identifier set includes the second device identifier corresponding to the preset device identifier type;

[0012] For each of the second device identifiers, determine whether there is at least one first target device identifier in the pre-determined server table that matches the second device identifier;

[0013] When it is determined that there is at least one first target device identifier in the pre-determined server table that matches the second device identifier, determine the first target device identifier;

[0014] According to the first target device identifier, determine the first record data corresponding to the first target device identifier;

[0015] According to the first record data, determine the first primary key ID corresponding to the first record data;

[0016] Encrypt the first primary key ID to obtain the first device unique identifier corresponding to the first primary key ID, and determine the first device unique identifier as the unique device identifier corresponding to the device.

[0017] As an optional implementation manner, in the first aspect of the present invention, the method further includes:

[0018] When it is determined that there is no first target device identifier in the pre-determined server table that matches the second device identifier, determine the second record data corresponding to the device identifier set;

[0019] According to the second record data, determine the second primary key ID corresponding to the second record data;

[0020] Encrypt the second primary key ID to obtain the second device unique identifier corresponding to the second primary key ID, and determine the second device unique identifier as the unique device identifier corresponding to the device.

[0021] As an alternative implementation manner, in the first aspect of the present invention, for each of the second device identifiers, determining whether there is at least one first target device identifier that matches the second device identifier in a pre-determined server table includes:

[0022] For each of the second device identifiers, determining the matching degree between the second device identifier and the storage device identifiers in the pre-determined server table;

[0023] For each of the storage device identifiers, determining whether there is a first target device identifier whose matching degree is greater than or equal to a pre-determined matching degree threshold;

[0024] When it is determined that there is a first target device identifier whose matching degree is greater than or equal to the pre-determined matching degree threshold, determining that there is at least one first target device identifier that matches the second device identifier in the pre-determined server table;

[0025] When it is determined that there is no first target device identifier whose matching degree is greater than or equal to the pre-determined matching degree threshold, determining that there is no first target device identifier that matches the second device identifier in the pre-determined server table.

[0026] As an alternative implementation manner, in the first aspect of the present invention, before determining whether there is at least one first target device identifier that matches the second device identifier in the pre-determined server table for each of the second device identifiers, the method further includes:

[0027] According to the first device identifier included in the unique identifier acquisition instruction, determining whether there is at least one second target device identifier that matches the first device identifier;

[0028] When it is determined that there is at least one second target device identifier that matches the first device identifier, for each of the second target device identifiers, determining the device corresponding to the second target device identifier according to the second target device identifier;

[0029] Based on the devices corresponding to all the second target device identifiers, performing the operation of determining whether there is at least one first target device identifier that matches the second device identifier in the pre-determined server table according to the device identifier set.

[0030] As an alternative implementation manner, in the first aspect of the present invention, before calling the device unique identifier, the method further includes:

[0031] Based on the device identifier corresponding to the device and the user identifier, determine whether the user's corresponding user access relationship information meets the access permission conditions corresponding to the device unique identifier determined in advance; the device identifier corresponding to the device includes the first device identifier and the second device identifier;

[0032] When it is determined that the user access relationship information meets the access permission conditions, determine that the user has the permission to access the device unique identifier, and perform the operation of accessing the device unique identifier;

[0033] When it is determined that the user access relationship information does not meet the access permission conditions, output a corresponding access permission verification instruction according to the device unique identifier;

[0034] Receive the password sent by the user for the access permission verification instruction, and determine whether the password is consistent with the target password preset for the access permission verification instruction; the password is consistent with the target password means that the corresponding content and content format are consistent;

[0035] When it is determined that the password is consistent with the target password, determine that the user has the permission to access the device unique identifier, and perform the operation of accessing the device unique identifier.

[0036] As an optional implementation manner, in the first aspect of the present invention, the step of determining whether the user's corresponding user access relationship information meets the access permission conditions corresponding to the device unique identifier determined in advance according to the device identifier corresponding to the device and the user identifier includes:

[0037] If the user's corresponding user access relationship information is the user's corresponding user access level, determine whether the user's corresponding user access level is greater than or equal to the user access level threshold determined in advance according to the device identifier corresponding to the device and the user identifier;

[0038] When it is determined that the user access level is greater than or equal to the user access level threshold, determine that the user access relationship information meets the access permission conditions corresponding to the device unique identifier determined in advance;

[0039] When it is determined that the user access level is less than the user access level threshold, determine that the user access relationship information does not meet the access permission conditions;

[0040] If the user's corresponding user access relationship information is the user's corresponding user historical access times, determine whether the user's corresponding user historical access times are less than or equal to the user accessible times threshold determined in advance according to the device identifier corresponding to the device and the user identifier;

[0041] When it is determined that the historical retrieval times is less than or equal to the user-adjustable retrieval times threshold, it is determined that the user retrieval relationship information meets the retrieval permission condition;

[0042] When it is determined that the historical retrieval times is greater than the user-adjustable retrieval times threshold, it is determined that the user retrieval relationship information does not meet the retrieval permission condition.

[0043] A second aspect of the present invention discloses a device for determining a unique device identifier, the device comprising:

[0044] A detection module, configured to detect a unique identifier acquisition instruction triggered by a user for a device; the unique identifier acquisition instruction includes a first device identifier corresponding to the device and a user identifier corresponding to the user; the unique identifier acquisition instruction is used to acquire the device unique identifier corresponding to the device;

[0045] A judgment module, configured to judge whether there is a device unique identifier pre-stored in the device according to the unique identifier acquisition instruction;

[0046] A call module, configured to call the device unique identifier when the judgment module determines that there is the device unique identifier pre-stored in the device;

[0047] An identifier generation module, configured to generate the device unique identifier corresponding to the device according to the unique identifier acquisition instruction and call the device unique identifier when the judgment module determines that there is no device unique identifier pre-stored in the device;

[0048] As an optional implementation manner, in the second aspect of the present invention, the manner in which the identifier generation module generates the device unique identifier corresponding to the device according to the unique identifier acquisition instruction specifically includes:

[0049] According to the unique identifier acquisition instruction, obtain a device identifier set corresponding to the device; the device identifier set includes a second device identifier corresponding to a preset device identifier type;

[0050] For each of the second device identifiers, judge whether there is at least one first target device identifier matching the second device identifier in a pre-determined server table;

[0051] When it is determined that there is at least one first target device identifier matching the second device identifier in the pre-determined server table, determine the first target device identifier;

[0052] According to the first target device identifier, determine the first record data corresponding to the first target device identifier;

[0053] Determine a first primary key ID corresponding to the first record data according to the first record data;

[0054] Encrypt the first primary key ID to obtain a first device unique identifier corresponding to the first primary key ID, and determine the first device unique identifier as the device unique identifier corresponding to the device.

[0055] As an optional implementation manner, in the second aspect of the present invention, the manner in which the identifier generation module generates the device unique identifier corresponding to the device according to the unique identifier acquisition instruction specifically further includes:

[0056] When it is determined that there is no first target device identifier matching the second device identifier in the pre-determined server table, determine second record data corresponding to the device identifier set;

[0057] Determine a second primary key ID corresponding to the second record data according to the second record data;

[0058] Encrypt the second primary key ID to obtain a second device unique identifier corresponding to the second primary key ID, and determine the second device unique identifier as the device unique identifier corresponding to the device

[0059] As an optional implementation manner, in the second aspect of the present invention, the manner in which the identifier generation module determines whether there is at least one first target device identifier matching the second device identifier in the pre-determined server table for each second device identifier specifically includes:

[0060] For each second device identifier, determine the matching degree between the second device identifier and the storage device identifier in the pre-determined server table;

[0061] For each storage device identifier, determine whether there is a first target device identifier whose matching degree is greater than or equal to a pre-determined matching degree threshold;

[0062] When it is determined that there is a first target device identifier whose matching degree is greater than or equal to the pre-determined matching degree threshold, determine that there is at least one first target device identifier matching the second device identifier in the pre-determined server table;

[0063] When it is determined that there is no first target device identifier whose matching degree is greater than or equal to the pre-determined matching degree threshold, determine that there is no first target device identifier matching the second device identifier in the pre-determined server table.

[0064] As an alternative implementation, in the second aspect of the present invention, the manner in which the identification generation module generates the device unique identifier corresponding to the device according to the unique identifier acquisition instruction specifically further includes:

[0065] Before determining whether there is at least one first target device identifier matching the second device identifier in the pre-determined server table for each of the second device identifiers, determine whether there is at least one second target device identifier matching the first device identifier according to the first device identifier included in the unique identifier acquisition instruction;

[0066] When it is determined that there is at least one second target device identifier matching the first device identifier, for each of the second target device identifiers, determine the device corresponding to the second target device identifier according to the second target device identifier;

[0067] Based on the devices corresponding to all the second target device identifiers, perform the operation of determining whether there is at least one first target device identifier matching the second device identifier in the pre-determined server table according to the device identifier set.

[0068] As an alternative implementation, in the second aspect of the present invention, the device further includes:

[0069] A processing module, where the processing module includes the calling module or the identification generation module;

[0070] The determination module is further configured to, before the processing module calls the device unique identifier, determine whether the user access relationship information corresponding to the user satisfies the access permission condition corresponding to the device unique identifier determined in advance according to the device identifier corresponding to the device and the user identifier; the device identifier corresponding to the device includes the first device identifier and the second device identifier;

[0071] A determination module, configured to, when the determination module determines that the user access relationship information satisfies the access permission condition, determine that the user has the permission to call the device unique identifier, and trigger the processing module to execute the operation of calling the device unique identifier;

[0072] An instruction output module, configured to, when the determination module determines that the user access relationship information does not satisfy the access permission condition, output a corresponding call permission verification instruction according to the device unique identifier;

[0073] A receiving module, configured to receive the password sent by the user for the call permission verification instruction;

[0074] The determination module is further configured to determine whether the password is consistent with a target password preset for the call permission verification instruction; the consistency between the password and the target password means that the corresponding content and content format are consistent;

[0075] The determination module is further configured to, when the judgment module determines that the password is consistent with the target password, determine that the user has the permission to retrieve the device unique identifier, and trigger the processing module to execute the operation of retrieving the device unique identifier.

[0076] As an optional implementation manner, in the second aspect of the present invention, the manner in which the judgment module determines whether the user retrieval relationship information corresponding to the user satisfies the retrieval permission condition corresponding to the device unique identifier determined in advance according to the device identifier corresponding to the device and the user identifier specifically includes:

[0077] If the user retrieval relationship information corresponding to the user is the user retrieval level corresponding to the user, according to the device identifier corresponding to the device and the user identifier, determine whether the user retrieval level corresponding to the user is greater than or equal to a user retrieval level threshold determined in advance;

[0078] When it is determined that the user retrieval level is greater than or equal to the user retrieval level threshold, determine that the user retrieval relationship information satisfies the retrieval permission condition corresponding to the device unique identifier determined in advance;

[0079] When it is determined that the user retrieval level is less than the user retrieval level threshold, determine that the user retrieval relationship information does not satisfy the retrieval permission condition;

[0080] If the user retrieval relationship information corresponding to the user is the user historical retrieval times corresponding to the user, according to the device identifier corresponding to the device and the user identifier, determine whether the user historical retrieval times corresponding to the user are less than or equal to a user retrievable times threshold determined in advance;

[0081] When it is determined that the historical retrieval times are less than or equal to the user retrievable times threshold, determine that the user retrieval relationship information satisfies the retrieval permission condition;

[0082] When it is determined that the historical retrieval times are greater than the user retrievable times threshold, determine that the user retrieval relationship information does not satisfy the retrieval permission condition.

[0083] A third aspect of the present invention discloses another device unique identifier determination device, and the device includes:

[0084] A memory storing executable program code;

[0085] A processor coupled to the memory;

[0086] The processor calls the executable program code stored in the memory and executes a method for determining a unique device identifier disclosed in the first aspect of the present invention.

[0087] The fourth aspect of the present invention discloses a computer-readable storage medium storing computer instructions that, when called, are used to execute a method for determining a unique device identifier disclosed in the first aspect of the present invention.

[0088] Compared with the prior art, the embodiments of the present invention have the following beneficial effects:

[0089] In the embodiments of the present invention, a unique identifier acquisition instruction triggered by a user for a device is detected; the unique identifier acquisition instruction includes a first device identifier corresponding to the device and a user identifier corresponding to the user; the unique identifier acquisition instruction is used to acquire a unique device identifier corresponding to the device; according to the unique identifier acquisition instruction, it is determined whether there is a unique device identifier pre-stored in the device; when it is determined that there is a unique device identifier pre-stored in the device, the unique device identifier is called; when it is determined that there is no unique device identifier pre-stored in the device, according to the unique identifier acquisition instruction, a unique device identifier corresponding to the device is generated and the unique device identifier is called. It can be seen that the present invention can, when detecting an instruction to acquire a unique device identifier, directly call the unique device identifier or generate a unique device identifier according to the instruction for calling, which can reduce the situation where the unique device identifier changes when the data corresponding to the device changes (such as uninstalling the mobile client APP or clearing user data, resetting the device identifier, etc.), which is beneficial to improving the stability and accuracy of the unique device identifier, and thus is beneficial to the statistical analysis operations of business personnel. For example, business personnel can perform DAU statistics, MAU statistics, behavior statistics, and advertising activation statistics based on the unique device identifier, thereby improving the convenience and statistical efficiency of the statistical analysis operations of business personnel. BRIEF DESCRIPTION OF THE DRAWINGS

[0090] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention, and for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0091] Figure 1 is a flowchart showing a method for determining a unique device identifier disclosed in an embodiment of the present invention;

[0092] Figure 2It is a schematic flowchart of another method for determining a unique device identifier disclosed in an embodiment of the present invention;

[0093] Figure 3 It is a schematic structural diagram of a device for determining a unique device identifier disclosed in an embodiment of the present invention;

[0094] Figure 4 It is a schematic structural diagram of another device for determining a unique device identifier disclosed in an embodiment of the present invention;

[0095] Figure 5 It is a schematic structural diagram of yet another device for determining a unique device identifier disclosed in an embodiment of the present invention. Detailed implementation manners

[0096] In order to enable those skilled in the art to better understand the solution of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without making creative efforts belong to the scope of protection of the present invention.

[0097] The terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, device, product or terminal that includes a series of steps or units is not limited to the listed steps or units, but optionally further includes steps or units not listed, or optionally further includes other steps or units inherent to these processes, methods, products or terminals.

[0098] Referring to "embodiment" in this article means that a specific feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present invention. The phrase appears in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art will explicitly and implicitly understand that the embodiments described herein can be combined with other embodiments.

[0099] The present invention discloses a method and apparatus for determining a unique device identifier, which can, when detecting an instruction to obtain the unique device identifier, directly call the unique device identifier or generate a unique device identifier according to the instruction for calling. This can reduce the situation where the unique device identifier changes when the data corresponding to the device changes (such as uninstalling the mobile client APP or clearing user data, resetting the device identifier, etc.), which is beneficial to improving the stability and accuracy of the unique device identifier, and thus beneficial for business personnel to perform statistical analysis operations. For example, business personnel can perform DAU statistics, MAU statistics, behavior statistics, and advertising activation statistics based on the unique device identifier, thereby improving the convenience and statistical efficiency of the statistical analysis operations performed by business personnel. The following will be described in detail respectively.

[0100] Embodiment 1

[0101] Please refer to Figure 1 , Figure 1 which is a schematic flowchart of a method for determining a unique device identifier disclosed in an embodiment of the present invention. Among them, Figure 1 the described method can be applied to a device unique identifier determination apparatus, where the apparatus can include a server and / or a client. Among them, the server includes a cloud server (also known as the cloud) or a local server, and the embodiments of the present invention do not make any limitations. As Figure 1 shown, the method for determining a unique device identifier includes the following operations:

[0102] 101. Detect a unique identifier acquisition instruction triggered by a user for the device.

[0103] In an embodiment of the present invention, optionally, the unique identifier acquisition instruction includes a first device identifier corresponding to the device and a user identifier corresponding to the user; the unique identifier acquisition instruction is used to obtain the unique device identifier corresponding to the device. Optionally, the triggering method of the unique identifier acquisition instruction can be a timing triggering method or a manual triggering method, and the embodiments of the present invention do not make any limitations. Optionally, the triggering times corresponding to the timing triggering can be a single timing trigger or multiple timing triggers; the time settings corresponding to the multiple timing triggers can be regular time intervals or irregular time intervals, and the embodiments of the present invention do not make any limitations.

[0104] Optionally, the client detects a unique identifier acquisition instruction triggered by a user for the device. Optionally, the device can include at least one of Android devices, iOS devices, Windows phone devices, YunOS devices, FuntouchOS devices, symbian devices, BlackBerry devices, Palm devices, BADA devices, etc., and the embodiments of the present invention do not make any limitations.

[0105] 102. Obtain an instruction according to the unique identifier, and determine whether there is a device unique identifier pre-stored in the device. When the determination result is yes, trigger the execution of step 103; when the determination result is no, trigger the execution of step 104.

[0106] In an embodiment of the present invention, optionally, the client obtains an instruction according to the unique identifier, and determines whether there is a device unique identifier pre-stored in the device, and when the determination result is yes, triggers the cloud to execute step 103.

[0107] Optionally, the specific manner in which the device stores the device unique identifier is that the cloud sends the device unique identifier to the client, and the client receives the device unique identifier and stores it locally on the client.

[0108] 103. Invoke the device unique identifier.

[0109] In an embodiment of the present invention, optionally, the cloud invokes the device unique identifier. Optionally, invoking the device unique identifier can be used for DAU statistics, MAU statistics, behavior statistics, advertising activation statistics, etc., which are not limited in the embodiments of the present invention.

[0110] 104. Obtain an instruction according to the unique identifier, generate a device unique identifier corresponding to the device, and trigger the execution of step 103.

[0111] In an embodiment of the present invention, optionally, the device unique identifier can also be referred to as device_id, which is not limited in the embodiments of the present invention. Optionally, when it is determined that there is no device unique identifier pre-stored in the device, the server generates a device unique identifier corresponding to the device according to the unique identifier acquisition instruction.

[0112] It can be seen that implementing the method for determining a device unique identifier described in the embodiments of the present invention can, when detecting an instruction to obtain a device unique identifier, directly invoke the device unique identifier or generate a device unique identifier according to the instruction for invocation, which can reduce the situation where the device unique identifier changes when the data corresponding to the device changes (such as uninstalling the mobile client APP or clearing user data, resetting the device identifier, etc.), which is beneficial to improving the stability and accuracy of the device unique identifier, and thus beneficial to business personnel for statistical analysis operations. For example, business personnel perform DAU statistics, MAU statistics, behavior statistics, and advertising activation statistics, etc., based on the device unique identifier, thereby improving the convenience and statistical efficiency of business personnel for statistical analysis operations.

[0113] In an optional embodiment, in step 104, generating a device unique identifier corresponding to the device according to the unique identifier acquisition instruction may include:

[0114] Obtain an instruction according to the unique identifier, and obtain the set of device identifiers corresponding to the device; the set of device identifiers includes the second device identifiers corresponding to the preset device identifier types.

[0115] For each second device identifier, determine whether there is at least one first target device identifier in the preset server table that matches the second device identifier.

[0116] When it is determined that there is at least one first target device identifier in the preset server table that matches the second device identifier, determine the first target device identifier.

[0117] According to the first target device identifier, determine the first record data corresponding to the first target device identifier.

[0118] According to the first record data, determine the first primary key ID corresponding to the first record data.

[0119] Encrypt the first primary key ID to obtain the first device unique identifier corresponding to the first primary key ID, and determine the first device unique identifier as the device unique identifier corresponding to the device.

[0120] In this optional embodiment, optionally, the specific device identifiers included in the set of device identifiers depend on the device's operating system. For example, when the device's operating system is the Android system, the set of device identifiers includes at least one of device identifiers such as Android_id, oaid, mac, uuid (internal storage), uuid (external storage), IDFA, IDFV, IDFV + keychain, etc. The embodiments of the present invention do not make limitations.

[0121] Optionally, the server table is created by the server. One server has one server table. The primary key of the server table is an auto-increment sequence. The server table is a data set of many rows of data. Each row of data in the server table represents a record, and each record corresponds to a device. The embodiments of the present invention do not make limitations.

[0122] Optionally, the client obtains instructions based on the unique identifier and obtains the set of device identifiers corresponding to the device; the client uploads the set of device identifiers to the cloud, and triggers the cloud to determine whether there is at least one first target device identifier in the pre-determined server table that matches the second device identifier for each second device identifier; when the judgment result is yes, the cloud updates the remaining second device identifiers uploaded by the client to the server table, and updates the record corresponding to the operation of "the cloud determines whether there is at least one first target device identifier in the pre-determined server table that matches the second device identifier for each second device identifier, and the cloud determines that there is at least one first target device identifier in the pre-determined server table that matches the second device identifier" to the current table record of the corresponding device in the server table, and the current table record of the device is the first record data; the cloud determines the first primary key ID according to the first record data, encrypts the first primary key ID to generate the first device unique identifier, and determines the first device unique identifier as the device unique identifier corresponding to the device.

[0123] Optionally, the remaining second device identifiers are the first target device identifiers in the set of device identifiers that do not match the second device identifier in the pre-determined server table, and the embodiments of the present invention do not make limitations.

[0124] It can be seen that this optional embodiment can determine whether there is a first target device identifier in the server table that matches the second device identifier, perform the corresponding operation of generating the device unique identifier according to the situation that there is a first target device identifier in the server table, and determine the device unique identifier according to multiple device identifiers, improving the pertinence of the operation of generating the device unique identifier and the reliability of the determined device unique identifier, thereby improving the stability of the device unique identifier and reducing the occurrence of inaccurate R & D statistical operation results due to changes in the device unique identifier.

[0125] In another optional embodiment, the method further includes the following operations:

[0126] When it is determined that there is no first target device identifier in the pre-determined server table that matches the second device identifier, determine the second record data corresponding to the set of device identifiers;

[0127] According to the second record data, determine the second primary key ID corresponding to the second record data;

[0128] Encrypt the second primary key ID to obtain the second device unique identifier corresponding to the second primary key ID, and determine the second device unique identifier as the device unique identifier corresponding to the device.

[0129] In this optional embodiment, optionally, when it is determined that there is no first target device identifier in the pre-determined server table that matches the second device identifier, the cloud determines the device corresponding to the second device identifier as a new device; inserts the second device identifier uploaded by the client into the server table, and determines the operation of inserting the second device identifier uploaded by the client into the server table as a new inserted record. This new inserted record is the second record data, and a second primary key ID is determined according to the second record data; encrypts the second primary key ID to generate a second device unique identifier, and determines the second device unique identifier as the device unique identifier corresponding to the device.

[0130] It can be seen that this optional embodiment can perform corresponding operations for generating the device unique identifier according to the situation that there is no first target device identifier in the server table, improving the diversity of the operations for generating the device unique identifier, enriching the ways to generate the device unique identifier, and thus improving the determination efficiency of the device unique identifier.

[0131] In another optional embodiment, for each second device identifier, determining whether there is at least one first target device identifier in the pre-determined server table that matches the second device identifier may include:

[0132] For each second device identifier, determine the matching degree between the second device identifier and the storage device identifier in the pre-determined server table;

[0133] For each storage device identifier, determine whether there is a first target device identifier with a matching degree greater than or equal to the pre-determined matching degree threshold;

[0134] When it is determined that there is a first target device identifier with a matching degree greater than or equal to the pre-determined matching degree threshold, determine that there is at least one first target device identifier in the pre-determined server table that matches the second device identifier;

[0135] When it is determined that there is no first target device identifier with a matching degree greater than or equal to the pre-determined matching degree threshold, determine that there is no first target device identifier in the pre-determined server table that matches the second device identifier.

[0136] In this optional embodiment, further optionally, for a certain second device identifier, when it is determined that there is a first target device identifier with a matching degree greater than or equal to the pre-determined matching degree threshold, determine whether there are at least two first sub-target device identifiers with a matching degree greater than or equal to the matching degree threshold. When the determination result is yes, for all the first sub-target device identifiers, determine the first sub-target device identifier with the largest matching degree as the first target device identifier, and perform the above operation of determining that there is at least one first target device identifier in the pre-determined server table that matches the second device identifier.

[0137] In this optional embodiment, optionally, the matching degree threshold can be set to different values according to different situations. For example, the matching degree threshold is 80%, the matching degree threshold is 95%, etc., which are not limited in the embodiments of the present invention. Specifically, the larger the matching degree threshold is, the closer the matching degree is to the matching degree threshold, and the more accurate and reliable the determined unique device identifier is.

[0138] It can be seen that this optional embodiment can determine whether there is a first target device identifier in the server table by comparing the size relationship between the matching degree and the matching degree threshold, which improves the flexibility and rationality of the method for determining the existence of the first target device identifier in the server table, and further improves the efficiency of subsequent determination of the unique device identifier and reduces unnecessary useless operations.

[0139] In another optional embodiment, before determining whether there is at least one first target device identifier matching the second device identifier in the pre-determined server table for each second device identifier, the method may further include the following operations:

[0140] According to the first device identifier included in the unique identifier acquisition instruction, determine whether there is at least one second target device identifier matching the first device identifier;

[0141] When it is determined that there is at least one second target device identifier matching the first device identifier, for each second target device identifier, determine the device corresponding to the second target device identifier according to the second target device identifier;

[0142] Based on the devices corresponding to all the second target device identifiers, perform the above operation of determining whether there is at least one first target device identifier matching the second device identifier in the pre-determined server table according to the device identifier set.

[0143] In this optional embodiment, optionally, the first device identifier may include one or more of a device series identifier, a device model identifier, a device brand identifier, a device type identifier, etc., which are not limited in the embodiments of the present invention.

[0144] In this optional embodiment, optionally, when it is determined that there is no at least one second target device identifier matching the first device identifier, trigger the operation of determining the second record data corresponding to the device identifier set as described above.

[0145] It can be seen that this optional embodiment can determine whether there is at least one second target device identifier in the server table. When the determination result is yes, the subsequent operation of determining whether there is a first target device identifier is performed. When the determination result is no, the subsequent operation of determining the second record data is performed, streamlining the first target device identifier determination operation and reducing the unnecessary retrieval scope, improving the rationality and purposefulness of the device unique identifier generation operation, and thus facilitating the improvement of the efficiency of determining the device unique identifier.

[0146] Embodiment 2

[0147] Please refer to Figure 2 , Figure 2 which is a schematic flowchart of another method for determining a device unique identifier disclosed in an embodiment of the present invention. Among them, Figure 2 the described method can be applied to a device unique identifier determination device, where the device can include a server and / or a client. Among them, the server includes a cloud server (also known as the cloud) or a local server, which is not limited in the embodiments of the present invention. As Figure 2 shown, the method for determining a device unique identifier includes the following operations:

[0148] 201. Detect a unique identifier acquisition instruction triggered by a user for a device.

[0149] 202. According to the unique identifier acquisition instruction, determine whether there is a device unique identifier pre-stored in the device. When the determination result is yes, trigger the execution of step 203; when the determination result is no, trigger the execution of step 209.

[0150] 203. According to the device identifier and user identifier corresponding to the device, determine whether the user's corresponding user retrieval relationship information meets the retrieval permission conditions corresponding to the pre-determined device unique identifier. When the determination result is yes, trigger the execution of step 204; when the determination result is no, trigger the execution of step 206.

[0151] In an embodiment of the present invention, optionally, the device identifier corresponding to the device includes a first device identifier and a second device identifier.

[0152] 204. Determine that the user has the permission to retrieve the device unique identifier.

[0153] 205. Invoke the device unique identifier.

[0154] 206. Output a corresponding call permission verification instruction according to the device unique identifier.

[0155] In an embodiment of the present invention, optionally, the types of verification passwords corresponding to the call permission verification instructions include biometric password types and non-biometric password types.

[0156] Optionally, the manner of outputting the call permission verification instruction may include, but is not limited to, sending text messages, pushing information, sending pop-up windows, etc., which are not limited in the embodiments of the present invention.

[0157] 207. Receive the password sent by the user for the call permission verification instruction, and determine whether the password is consistent with the target password preset for the call permission verification instruction.

[0158] In the embodiments of the present invention, optionally, the consistency between the password and the target password means that the corresponding content and content format are consistent.

[0159] In the embodiments of the present invention, optionally, the target password can be set to different passwords according to the confidentiality level or importance of the device corresponding to the unique identifier of the device to be called. For example, the higher the confidentiality level or importance, the higher the complexity of the target password. The target password can also be set to the same password for different devices, which is not limited in the embodiments of the present invention.

[0160] 208. When it is determined that the password is consistent with the target password, determine that the user has the permission to retrieve the device unique identifier, and trigger the execution of step 205.

[0161] In the embodiments of the present invention, optionally, when it is determined that the password is inconsistent with the target password, it is determined that the user does not have the permission to retrieve the device unique identifier, and the user cannot retrieve the device unique identifier, and an inability to retrieve prompt is output. Optionally, the manner of outputting the inability to retrieve prompt may include, but is not limited to, at least one of outputting a prompt by phone call, outputting a prompt by text message / message notification, outputting a prompt by information pop-up window, and other ringtone / music reminder methods, which are not limited in the embodiments of the present invention.

[0162] 209. Generate the device unique identifier corresponding to the device according to the unique identifier acquisition instruction, and trigger the execution of step 203.

[0163] In the embodiments of the present invention, for other descriptions of steps 201, 202, 205, and 209, please refer to the detailed descriptions of steps 101-step 104 in Embodiment 1, and the embodiments of the present invention will not be elaborated herein.

[0164] It can be seen that when the embodiment of the present invention detects that an instruction for obtaining a device is required, it can directly call the device unique identifier or generate a device unique identifier according to the instruction for calling, which can reduce the situation where the device unique identifier changes when the data corresponding to the device changes (such as uninstalling the mobile client APP or clearing user data, resetting the device identifier, etc.), which is beneficial to improving the stability and accuracy of the device unique identifier, and thus is beneficial for business personnel to perform statistical analysis operations. For example, business personnel perform DAU statistics, MAU statistics, behavior statistics, and advertising activation statistics based on the device unique identifier, thereby improving the convenience and statistical efficiency of business personnel performing statistical analysis operations; in addition, it can also determine whether the user's retrieved relationship information meets the retrieval permission. If the judgment result is yes, the subsequent operation of retrieving the device unique identifier is performed. If the judgment result is no, it is determined again whether the user has the retrieval permission according to the password sent by the user, providing multiple verification methods for the user's retrieval permission, improving the efficiency of verifying the user's retrieval permission, and thus improving the accuracy of the determined user retrieval permission verification result and the intelligence of the device unique identifier determination device.

[0165] In an optional embodiment, in step 203, determining whether the user's retrieved relationship information corresponding to the user meets the retrieved permission condition corresponding to the device unique identifier determined in advance according to the device identifier and user identifier corresponding to the device may include:

[0166] When the user's retrieved relationship information corresponding to the user is the user's retrieved level, determining whether the user's retrieved level is greater than or equal to the retrieved level threshold determined in advance according to the device identifier and user identifier corresponding to the device;

[0167] When it is determined that the user's retrieved level is greater than or equal to the retrieved level threshold, it is determined that the user's retrieved relationship information meets the retrieved permission condition corresponding to the device unique identifier determined in advance;

[0168] When it is determined that the user's retrieved level is less than the retrieved level threshold, it is determined that the user's retrieved relationship information does not meet the retrieved permission condition;

[0169] When the user's retrieved relationship information corresponding to the user is the user's historical retrieval times, determining whether the user's historical retrieval times are less than or equal to the threshold of the retrievable times determined in advance according to the device identifier and user identifier corresponding to the device;

[0170] When it is determined that the historical retrieval times are less than or equal to the threshold of the retrievable times, it is determined that the user's retrieved relationship information meets the retrieved permission condition;

[0171] When it is determined that the historical retrieval times are greater than the threshold of the retrievable times, it is determined that the user's retrieved relationship information does not meet the retrieved permission condition.

[0172] In this alternative embodiment, optionally, the historical retrieval count of the user may be the number of times the user retrieves the unique identifier of a certain device within a certain historical time period, or may be the total number of times the user retrieves the unique identifiers of different devices within a certain historical time period. It may also be the number of times the user historically retrieves the unique identifier of a certain device, or may be the total number of times the user historically retrieves the unique identifiers of different devices. The embodiments of the present invention do not make any limitations in this regard.

[0173] In this alternative embodiment, optionally, the user retrieval level threshold may be set to different values according to the confidentiality level and / or importance level, etc. of the device and the unique identifier of the device, or the user retrieval level thresholds corresponding to different devices may all be set to the same value. The user adjustable retrieval count threshold may be set to different values according to the confidentiality level and / or importance level, etc. of the device and the unique identifier of the device, or the user adjustable retrieval count thresholds corresponding to different devices may all be set to the same value. The embodiments of the present invention do not make any limitations in this regard.

[0174] It can be seen that this alternative embodiment can determine whether the user has the retrieval permission for the device unique identifier in two ways: by comparing the user retrieval level or by comparing the user's historical retrieval count. This improves the diversity of the methods for determining whether the user has the retrieval permission for the device unique identifier and improves the reliability of the determined user retrieval permission judgment result. Furthermore, it improves the determination efficiency of the user retrieval permission judgment result and is beneficial to the efficiency of the subsequent user's retrieval permission verification operation for the device unique identifier.

[0175] Embodiment III

[0176] Please refer to Figure 3 , Figure 3 which is a schematic structural diagram of a device unique identifier determination device disclosed in the embodiments of the present invention. Among them, Figure 3 the described device may include a server and / or a client. Among them, the server includes a cloud server (also known as the cloud) or a local server. The embodiments of the present invention do not make any limitations in this regard. As Figure 3 shown, this device unique identifier determination device may include:

[0177] A detection module 301, configured to detect a unique identifier acquisition instruction triggered by the user for the device. The unique identifier acquisition instruction includes a first device identifier corresponding to the device and a user identifier corresponding to the user. The unique identifier acquisition instruction is used to acquire the device unique identifier corresponding to the device.

[0178] A judgment module 302, configured to judge whether there is a device unique identifier pre-stored in the device according to the unique identifier acquisition instruction.

[0179] The calling module 303 is used to call the device unique identifier when the judging module 302 determines that there is a device unique identifier pre-stored in the device.

[0180] The identifier generation module 304 is used to generate a device unique identifier corresponding to the device according to the unique identifier acquisition instruction and call the device unique identifier when the judging module 302 determines that there is no device unique identifier pre-stored in the device.

[0181] It can be seen that implementing Figure 3 The described device unique identifier determination device can, when detecting an instruction to obtain a device unique identifier, directly call the device unique identifier or generate a device unique identifier according to the instruction for calling, which can reduce the situation where the device unique identifier changes when the data corresponding to the device changes (such as uninstalling the mobile client APP or clearing user data, resetting the device identifier, etc.), which is beneficial to improving the stability and accuracy of the device unique identifier, and thus beneficial to the statistical analysis operations of business personnel. For example, business personnel can perform DAU statistics, MAU statistics, behavior statistics, and advertising activation statistics based on the device unique identifier, etc., thereby improving the convenience and statistical efficiency of the statistical analysis operations of business personnel.

[0182] In this optional embodiment, as an optional implementation manner, the manner in which the identifier generation module 304 generates a device unique identifier corresponding to the device according to the unique identifier acquisition instruction specifically includes:

[0183] According to the unique identifier acquisition instruction, obtain the device identifier set corresponding to the device; the device identifier set includes the second device identifier corresponding to the pre-set device identifier type;

[0184] For each second device identifier, judge whether there is at least one first target device identifier in the pre-determined server table that matches the second device identifier;

[0185] When it is judged that there is at least one first target device identifier in the pre-determined server table that matches the second device identifier, determine the first target device identifier;

[0186] According to the first target device identifier, determine the first record data corresponding to the first target device identifier;

[0187] According to the first record data, determine the first primary key ID corresponding to the first record data;

[0188] Encrypt the first primary key ID to obtain the first device unique identifier corresponding to the first primary key ID, and determine the first device unique identifier as the device unique identifier corresponding to the device.

[0189] It can be seen that implementing Figure 4The described device can determine whether there is a first target device identifier in the server table that matches the second device identifier, perform corresponding device unique identifier generation operations based on the presence of the first target device identifier in the server table, and determine the device unique identifier of the device according to multiple device identifiers, improving the pertinence of the device unique identifier generation operation and the reliability of the device unique identifier, thereby improving the stability of the device unique identifier and reducing the occurrence of inaccurate R & D statistics operation results due to changes in the device unique identifier.

[0190] In another optional embodiment, as an optional implementation manner, the specific way for the identifier generation module 304 to generate the device unique identifier corresponding to the device according to the unique identifier acquisition instruction further includes:

[0191] When it is determined that there is no first target device identifier in the pre-determined server table that matches the second device identifier, determine the second record data corresponding to the device identifier set;

[0192] According to the second record data, determine the second primary key ID corresponding to the second record data;

[0193] Encrypt the second primary key ID to obtain the second device unique identifier corresponding to the second primary key ID, and determine the second device unique identifier as the device unique identifier corresponding to the device.

[0194] It can be seen that implementing Figure 4 The described device can also perform corresponding device unique identifier generation operations based on the situation that there is no first target device identifier in the server table, improving the diversity of the device unique identifier generation operation, being able to enrich the ways of generating the device unique identifier, and thereby improving the determination efficiency of the device unique identifier.

[0195] In yet another optional embodiment, as an optional implementation manner, the specific way for the identifier generation module 304 to determine whether there is at least one first target device identifier in the pre-determined server table that matches each second device identifier includes:

[0196] For each second device identifier, determine the matching degree between the second device identifier and the stored device identifier in the pre-determined server table;

[0197] For each stored device identifier, determine whether there is a first target device identifier with a matching degree greater than or equal to the pre-determined matching degree threshold;

[0198] When it is determined that there is a first target device identifier with a matching degree greater than or equal to the pre-determined matching degree threshold, determine that there is at least one first target device identifier in the pre-determined server table that matches the second device identifier;

[0199] When it is determined that there is no first target device identifier with a matching degree greater than or equal to a pre-determined matching degree threshold, it is determined that there is no first target device identifier matching the second device identifier in the pre-determined server table.

[0200] It can be seen that implementing Figure 4 the described device can also determine whether there is a first target device identifier in the server table by comparing the relationship between the matching degree and the matching degree threshold, improving the flexibility and rationality of the method for determining the existence of the first target device identifier in the server table, thereby improving the efficiency of subsequent determination of the device unique identifier and reducing unnecessary useless operations.

[0201] In yet another alternative embodiment, as an alternative implementation manner, the specific manner in which the identifier generation module 304 generates the device unique identifier corresponding to the device according to the unique identifier acquisition instruction further includes:

[0202] Before determining whether there is at least one first target device identifier matching the second device identifier in the pre-determined server table for each second device identifier, according to the first device identifier included in the unique identifier acquisition instruction, determine whether there is at least one second target device identifier matching the first device identifier;

[0203] When it is determined that there is at least one second target device identifier matching the first device identifier, for each second target device identifier, determine the device corresponding to the second target device identifier according to the second target device identifier;

[0204] Based on the devices corresponding to all the second target device identifiers, perform the above operation of determining whether there is at least one first target device identifier matching the second device identifier in the pre-determined server table according to the device identifier set.

[0205] It can be seen that implementing Figure 4 the described device can also determine whether there is at least one second target device identifier in the server table. When the determination result is yes, perform the subsequent operation of determining whether there is a first target device identifier. When the determination result is no, perform the subsequent operation of determining the second record data, streamlining the operation of determining the first target device identifier and reducing the unnecessary search range, improving the rationality and purposefulness of the device unique identifier generation operation, and thus being beneficial to improving the efficiency of determining the device unique identifier.

[0206] In yet another alternative embodiment, as Figure 4 shown, the device may further include:

[0207] A processing module, where the processing module includes a call module 303 or an identifier generation module 304.

[0208] The determination module 302 is further configured to, before the processing module calls the device unique identifier, determine whether the user access relationship information corresponding to the user meets the access permission conditions corresponding to the device unique identifier determined in advance according to the device identifier and the user identifier corresponding to the device; the device identifier corresponding to the device includes a first device identifier and a second device identifier.

[0209] The determination module 305 is configured to, when the determination module 302 determines that the user access relationship information meets the access permission conditions, determine that the user has the permission to call the device unique identifier, and trigger the processing module to perform the above operation of calling the device unique identifier.

[0210] The instruction output module 306 is configured to, when the determination module 302 determines that the user access relationship information does not meet the access permission conditions, output a corresponding access permission verification instruction according to the device unique identifier.

[0211] The receiving module 307 is configured to receive the password sent by the user for the access permission verification instruction.

[0212] The determination module 302 is further configured to determine whether the password is consistent with the target password preset for the access permission verification instruction; the password being consistent with the target password means that the corresponding content and content format are consistent.

[0213] The determination module 305 is further configured to, when the determination module 302 determines that the password is consistent with the target password, determine that the user has the permission to call the device unique identifier, and trigger the processing module to perform the above operation of calling the device unique identifier.

[0214] It can be seen that the Figure 4 described device can also determine whether the user access relationship information meets the access permission. If the determination result is yes, the subsequent operation of calling the device unique identifier is performed. If the determination result is no, it is determined again whether the user has the access permission according to the password sent by the user, providing multiple ways to determine the user access permission verification, improving the efficiency of verifying the user access permission, and further improving the accuracy of the determined user access permission verification result, as well as improving the intelligence of the device unique identifier determination device.

[0215] In yet another alternative embodiment, as an alternative implementation manner, the manner in which the determination module 302 determines whether the user access relationship information corresponding to the user meets the access permission conditions corresponding to the device unique identifier determined in advance according to the device identifier and the user identifier corresponding to the device specifically includes:

[0216] When the user call relationship information corresponding to the user is the user call level corresponding to the user, according to the device identifier corresponding to the device and the user identifier, determine whether the user call level corresponding to the user is greater than or equal to the pre-determined user call level threshold;

[0217] When it is determined that the user call level is greater than or equal to the user call level threshold, it is determined that the user call relationship information meets the call permission conditions corresponding to the pre-determined device unique identifier;

[0218] When it is determined that the user call level is less than the user call level threshold, it is determined that the user call relationship information does not meet the call permission conditions;

[0219] If the user call relationship information corresponding to the user is the user's historical call times corresponding to the user, according to the device identifier corresponding to the device and the user identifier, determine whether the user's historical call times corresponding to the user are less than or equal to the pre-determined user callable times threshold;

[0220] When it is determined that the historical call times are less than or equal to the user callable times threshold, it is determined that the user call relationship information meets the call permission conditions;

[0221] When it is determined that the historical call times are greater than the user callable times threshold, it is determined that the user call relationship information does not meet the call permission conditions.

[0222] It can be seen that implementing Figure 4 The described device can also determine whether the user has the device unique identifier call permission by comparing the user call level or comparing the user's historical call times, which improves the diversity of the method for determining that the user has the device unique identifier call permission and improves the reliability of the determined user call permission judgment result. Furthermore, it improves the determination efficiency of the user call permission judgment result and is beneficial to the efficiency of the subsequent user's call device unique identifier permission verification operation.

[0223] Embodiment 4

[0224] Please refer to Figure 5 , Figure 5 which is a schematic structural diagram of another device unique identifier determination device disclosed in the embodiments of the present invention. Among them, Figure 5 The described device may include a server and / or a client. Among them, the server includes a cloud server (also known as the cloud) or a local server, which is not limited in the embodiments of the present invention. As Figure 5 shown, the device may include:

[0225] A memory 401 storing executable program code;

[0226] A processor 402 coupled to the memory 401;

[0227] Further, it may further include an input interface 403 and an output interface 404 coupled to the processor 402;

[0228] Among them, the processor 402 calls the executable program code stored in the memory 401 to execute the steps in the method for determining a unique device identifier described in Embodiment 1 or Embodiment 2.

[0229] Embodiment 5

[0230] An embodiment of the present invention discloses a computer-readable storage medium that stores a computer program for electronic data exchange. Among them, the computer program causes the computer to execute the steps in the method for determining a unique device identifier described in Embodiment 1 or Embodiment 2.

[0231] Embodiment 6

[0232] An embodiment of the present invention discloses a computer program product. The computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause the computer to execute the steps in the method for determining a unique device identifier described in Embodiment 1 or Embodiment 2.

[0233] The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed to multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art can understand and implement it without creative efforts.

[0234] Through the specific descriptions of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on such an understanding, the essence of the above technical solution, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, and the storage medium includes read-only memory (ROM), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), one-time programmable read-only memory (OTPROM), electrically-erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc memories, magnetic disk memories, tape memories, or any other medium that can be used to carry or store data and is computer-readable.

[0235] Finally, it should be noted that: The method and device for determining a unique device identifier disclosed in the embodiments of the present invention only disclose the preferred embodiments of the present invention, and are only used to illustrate the technical solutions of the present invention, rather than limiting them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims

1. A method for determining a unique identifier of a device, characterized in that, The method includes: Detecting a unique identifier acquisition instruction triggered by a user for a device; the unique identifier acquisition instruction includes a first device identifier corresponding to the device and a user identifier corresponding to the user; the unique identifier acquisition instruction is used to acquire a device unique identifier corresponding to the device; Judging whether there is a device unique identifier pre-stored in the device according to the unique identifier acquisition instruction; When it is judged that there is the device unique identifier pre-stored in the device, calling the device unique identifier; When it is judged that there is no device unique identifier pre-stored in the device, generating a device unique identifier corresponding to the device according to the unique identifier acquisition instruction, and calling the device unique identifier; And, the generating a device unique identifier corresponding to the device according to the unique identifier acquisition instruction includes: Acquiring a device identifier set corresponding to the device according to the unique identifier acquisition instruction; the device identifier set includes a second device identifier corresponding to a preset device identifier type; For each of the second device identifiers, judging whether there is at least one first target device identifier matching the second device identifier in a pre-determined server table; When it is judged that there is at least one first target device identifier matching the second device identifier in the pre-determined server table, determining the first target device identifier; Determining first record data corresponding to the first target device identifier according to the first target device identifier, where the first record data includes a record corresponding to the determination operation of the first target device identifier; Determining a first primary key ID corresponding to the first record data according to the first record data; Encrypting the first primary key ID to obtain a first device unique identifier corresponding to the first primary key ID, and determining the first device unique identifier as the device unique identifier corresponding to the device.

2. The method for determining the unique identifier of a device according to claim 1, characterized in that, The method further includes: When it is judged that there is no first target device identifier matching the second device identifier in the pre-determined server table, determining second record data corresponding to the device identifier set; Determining a second primary key ID corresponding to the second record data according to the second record data; Encrypting the second primary key ID to obtain a second device unique identifier corresponding to the second primary key ID, and determining the second device unique identifier as the device unique identifier corresponding to the device.

3. The method for determining the unique identifier of a device according to claim 1 or 2, characterized in that, The judging whether there is at least one first target device identifier matching the second device identifier in the pre-determined server table for each of the second device identifiers includes: For each of the second device identifiers, determining a matching degree between the second device identifier and a stored device identifier in the pre-determined server table; For each of the stored device identifiers, judging whether there is a first target device identifier with the matching degree greater than or equal to a pre-determined matching degree threshold; When it is determined that there is the first target device identifier whose matching degree is greater than or equal to the pre-determined matching degree threshold, it is determined that there is at least one first target device identifier in the pre-determined server table that matches the second device identifier; When it is determined that there is no first target device identifier whose matching degree is greater than or equal to the pre-determined matching degree threshold, it is determined that there is no first target device identifier in the pre-determined server table that matches the second device identifier.

4. The method for determining the unique identifier of a device according to claim 3, characterized in that, Before, for each of the second device identifiers, it is determined whether there is at least one first target device identifier in the pre-determined server table that matches the second device identifier, the method further includes: According to the first device identifier included in the unique identifier acquisition instruction, it is determined whether there is at least one second target device identifier that matches the first device identifier; When it is determined that there is at least one second target device identifier that matches the first device identifier, for each of the second target device identifiers, according to the second target device identifier, the device corresponding to the second target device identifier is determined; Based on the devices corresponding to all the second target device identifiers, the operation of determining whether there is at least one first target device identifier in the pre-determined server table that matches the second device identifier according to the device identifier set is performed.

5. The method for determining a unique identifier of a device according to claim 4, characterized in that, Before the device unique identifier is called, the method further includes: According to the device identifier corresponding to the device and the user identifier, it is determined whether the user call relationship information corresponding to the user meets the call permission condition corresponding to the pre-determined device unique identifier; the device identifier corresponding to the device includes the first device identifier and the second device identifier; When it is determined that the user call relationship information meets the call permission condition, it is determined that the user has the permission to call the device unique identifier, and the operation of calling the device unique identifier is performed; When it is determined that the user call relationship information does not meet the call permission condition, according to the device unique identifier, a corresponding call permission verification instruction is output; The password sent by the user for the call permission verification instruction is received, and it is determined whether the password is consistent with the target password pre-set for the call permission verification instruction; the password being consistent with the target password means that the corresponding content and content format are consistent; When it is determined that the password is consistent with the target password, it is determined that the user has the permission to call the device unique identifier, and the operation of calling the device unique identifier is performed.

6. The method for determining a unique identifier of a device according to claim 5, wherein, The determining whether the user call relationship information corresponding to the user meets the call permission condition corresponding to the pre-determined device unique identifier according to the device identifier corresponding to the device and the user identifier includes: When the user retrieval relationship information corresponding to the user is the user retrieval level corresponding to the user, according to the device identifier corresponding to the device and the user identifier, determine whether the user retrieval level corresponding to the user is greater than or equal to a pre-determined user retrieval level threshold; When it is determined that the user retrieval level is greater than or equal to the user retrieval level threshold, determine that the user retrieval relationship information meets the retrieval permission conditions corresponding to the pre-determined device unique identifier; When it is determined that the user retrieval level is less than the user retrieval level threshold, determine that the user retrieval relationship information does not meet the retrieval permission conditions; When the user retrieval relationship information corresponding to the user is the user's historical retrieval times corresponding to the user, according to the device identifier corresponding to the device and the user identifier, determine whether the user's historical retrieval times corresponding to the user are less than or equal to a pre-determined user retrievable times threshold; When it is determined that the historical retrieval times are less than or equal to the user retrievable times threshold, determine that the user retrieval relationship information meets the retrieval permission conditions; When it is determined that the historical retrieval times are greater than the user retrievable times threshold, determine that the user retrieval relationship information does not meet the retrieval permission conditions.

7. A device unique identifier determination device, characterized in that The device includes: A detection module, configured to detect a unique identifier acquisition instruction triggered by a user for a device; the unique identifier acquisition instruction includes a first device identifier corresponding to the device and a user identifier corresponding to the user; the unique identifier acquisition instruction is used to acquire the device unique identifier corresponding to the device; A judgment module, configured to judge whether there is a device unique identifier pre-stored in the device according to the unique identifier acquisition instruction; A call module, configured to call the device unique identifier when the judgment module determines that there is a device unique identifier pre-stored in the device; An identifier generation module, configured to generate the device unique identifier corresponding to the device according to the unique identifier acquisition instruction and call the device unique identifier when the judgment module determines that there is no device unique identifier pre-stored in the device; Moreover, the manner in which the identifier generation module generates the device unique identifier corresponding to the device according to the unique identifier acquisition instruction specifically includes: According to the unique identifier acquisition instruction, acquire a device identifier set corresponding to the device; the device identifier set includes a second device identifier corresponding to a pre-set device identifier type; For each of the second device identifiers, judge whether there is at least one first target device identifier matching the second device identifier in a pre-determined server table; When it is determined that there is at least one first target device identifier matching the second device identifier in the pre-determined server table, determine the first target device identifier; According to the first target device identifier, determine first record data corresponding to the first target device identifier, where the first record data includes a record corresponding to the determination operation of the first target device identifier; According to the first record data, determine a first primary key ID corresponding to the first record data; Encrypt the first primary key ID to obtain a first device unique identifier corresponding to the first primary key ID, and determine the first device unique identifier as the device unique identifier corresponding to the device.

8. A device unique identifier determination device, characterized in that, The device includes: A memory storing executable program code; A processor coupled to the memory; The processor calls the executable program code stored in the memory to execute a method for determining a device unique identifier according to any one of claims 1-6.

9. A computer storage medium, characterized in that, The computer storage medium stores computer instructions, which are used to execute a method for determining a device unique identifier according to any one of claims 1-6 when the computer instructions are called.

Images