Mobile device identifier management method and device

Abstract

The invention provides a mobile device identifier management method and device, and relates to the technical field of computer application, initial state device identifiers are calculated by collecting system-level factors, device-level factors, application-level factors and user-level factors of mobile devices corresponding to application programs, and device identifier server-side verification is carried out; when the initial state device identifier exists or does not exist in the device identifier server, calculating a temporary state device identifier and / or an abnormal state device identifier in the initial state device identifier; by comparing the temporary state equipment identifier with the final state equipment identifier of which the various factor information is completely acquired, determining the acquisition condition of the various factor information; according to the method, the collision reason of the equipment identifier is analyzed based on the abnormal state equipment identifier, and then the mobile equipment identifier is dynamically regulated and controlled, so that the operational capability of the equipment identifier is increased and the collision probability and expansion probability of the equipment identifier are reduced through various factor information and newly adding four different life cycle states to the equipment identifier.

Description

Technical Field

[0001] The present invention relates to the field of computer application technology, and in particular to a mobile device identification management method and device. Background Art

[0002] At present, the development of mobile device identification has been evolving with the replacement of mobile devices and the rapid development of mobile Internet. In the early stage, some hardware information that can be used to identify a mobile device has gradually exposed its limitations as the requirements for personal privacy information protection become higher and higher. In related technologies, as the requirements for personal privacy information protection become higher and higher, there are more and more device identification collisions and multiple device identifications caused by the inability to collect mobile device hardware information, and the device identification cannot be managed. Therefore, a mobile device identification management method is urgently needed. Summary of the invention

[0003] The present invention aims to solve one of the technical problems in the related art at least to a certain extent.

[0004] To this end, the first purpose of the present invention is to propose a mobile device identification management method, which increases the operational capability of the device identification and reduces the probability of device identification collision and expansion through various factor information and adding four different life cycle states to the device identification.

[0005] The second objective of the present invention is to provide a mobile device identification management device.

[0006] A third objective of the present invention is to provide an electronic device.

[0007] A fourth object of the present invention is to provide a non-transitory computer-readable storage medium storing computer instructions.

[0008] A fifth object of the present invention is to provide a computer program product.

[0009] To achieve the above object, a first aspect of the present invention provides a method for managing mobile device identification, the method comprising:

[0010] When the application is installed and started, the initial device identification is calculated by collecting various factor information of the mobile device corresponding to the application, and the various factor information and the initial device identification are sent to the device identification server for verification;

[0011] In the case where the initial state device identification exists on the device identification server, selecting the temporary state device identification and the abnormal state device identification from the initial state device identification according to the first similarity between the various factor information and the various factor information stored on the device identification server;

[0012] In the case that the initial state device identification does not exist in the device identification server, selecting the temporary state device identification in the initial state device identification according to the number of mobile devices found by the retrieval algorithm and the second similarity between the various factor information and the various factor information stored in the found mobile device;

[0013] By comparing the temporary state device identification with the final state device identification in which various factor information is fully collected in the temporary state device identification and the initial state device identification, the collection status of various factor information is determined;

[0014] Based on the abnormal device identification, the cause of the device identification collision is analyzed, and the mobile device identification is dynamically adjusted according to the collection situation and the cause of the device identification collision.

[0015] To achieve the above-mentioned purpose, a second aspect of the present invention provides a mobile device identification management device, the device comprising:

[0016] The first calculation module is used to calculate the initial state device identification by collecting various factor information of the mobile device corresponding to the application when the application is installed and started, and send the various factor information and the initial state device identification to the device identification server for verification;

[0017] A second calculation module is used to select a temporary state device identifier and an abnormal state device identifier from the initial state device identifier according to a first similarity between various factor information and various factor information stored in the device identifier server when the initial state device identifier exists in the device identifier server;

[0018] A third calculation module is used to select a temporary device identifier from the initial device identifier when the initial device identifier does not exist in the device identifier server, based on the number of mobile devices found by the retrieval algorithm and the second similarity between various factor information and various factor information stored in the found mobile device by the second similarity algorithm;

[0019] A determination module is used to determine the collection of various factor information by the SDK generating the device identification by comparing the temporary device identification with the final device identification in which various factor information is fully collected in the temporary device identification and the initial device identification;

[0020] A control module is used to determine the cause of the device identification collision by analyzing the abnormal device identification, and dynamically control the mobile device identification according to the collection situation and the cause of the device identification collision. To achieve the above purpose, the third aspect of the present invention proposes an electronic device, including: at least one processor; and a memory connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the method described in the first aspect.

[0021] In order to achieve the above-mentioned purpose, the fourth aspect of the present invention proposes a non-transitory computer-readable storage medium storing computer instructions, where the computer instructions are used to enable the computer to execute the method described in the first aspect.

[0022] In order to achieve the above-mentioned purpose, a fifth aspect of the present invention provides a computer program product, and when the computer program is executed by a processor, it implements the method described in the first aspect.

[0023] The mobile device identification management method, apparatus, electronic device, storage medium and computer program product provided by the embodiments of the present invention calculate the initial state device identification by collecting the system-level factors, device-level factors, application-level factors and user-level factors of the mobile device corresponding to the application, and perform device identification server-side verification; when the initial state device identification exists or does not exist on the device identification server, calculate the temporary state device identification and / or abnormal state device identification in the initial state device identification; determine the collection status of various factor information by comparing the temporary state device identification with the final state device identification with various factor information collected; analyze the cause of device identification collision based on the abnormal state device identification, and then dynamically adjust the mobile device identification, thereby increasing the operational capability of the device identification and reducing the probability of device identification collision and expansion through various factor information and adding four different life cycle states to the device identification.

[0024] Additional aspects and advantages of the present invention will be given in part in the following description and in part will be obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The above and / or additional aspects and advantages of the present invention will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0026] Figure 1 A flow chart of a method for managing mobile device identification provided by an embodiment of the present invention;

[0027] Figure 2A schematic diagram of a flow chart of another mobile device identification management method provided by an embodiment of the present invention;

[0028] Figure 3 A schematic diagram of a device identification state and its conversion provided by an embodiment of the present invention;

[0029] Figure 4 A schematic diagram of the structure of a mobile device identification management device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0030] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present invention, and should not be construed as limiting the present invention.

[0031] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in the present invention are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data need to comply with the relevant laws, regulations and standards of relevant countries and regions.

[0032] The following describes a method and apparatus for managing mobile device identification according to an embodiment of the present invention with reference to the accompanying drawings.

[0033] Figure 1 A schematic diagram of a flow chart of a method for managing mobile device identification provided by an embodiment of the present invention.

[0034] like Figure 1 As shown, the method comprises the following steps:

[0035] Step 101, when the application is installed and started, the initial device identification is calculated by collecting various factor information of the mobile device corresponding to the application, and the various factor information and the initial device identification are sent to the device identification server for verification.

[0036] Optionally, the factor information includes system-level factors, device-level factors, application-level factors and user-level factors, the system-level factors are information for distinguishing different mobile devices, the device-level factors are information for identifying mobile devices, the application-level factors are file information generated by each APP on each mobile device, and the user-level factors are identification information for identifying the same user.

[0037] In some embodiments, after the application is installed and started, if it is detected that the device identification field of the mobile device is empty or the device identification is the initially generated device identification or the device identification server requires the device identification to be updated, the SDK that generates the device identification collects various factor information of the mobile device corresponding to the application to calculate the initial state device identification, wherein when calculating the initial state device identification, the calculation weights of the system-level factors, device-level factors, application-level factors and user-level factors are different. Thus, the factors generated by the device identification are classified from the system-level factors, device-level factors, application (APP)-level factors and user-level factors and assigned different weights, further reducing the probability of device identification collision and expansion.

[0038] Furthermore, system-level factors may include, but are not limited to, a 64-bit hexadecimal string (AndroidID) generated by the system when the Android device leaves the factory, an advertising identifier (Identifier for Advertisers, IDFA), and a non-permanent device identifier (Open Anonymous Device Identifier, OAID), which are used to distinguish different mobile devices, but it is necessary to consider that this factor may be tampered with and may be randomly generated each time.

[0039] Furthermore, device-level factors include, but are not limited to, physical address (Media Access Control, MAC), International Mobile Equipment Identity (International Mobile Equipment Identity, IMEI), International Mobile Subscriber Identification Number (International Mobile Subscriber Identification Number, IMSI), etc.

[0040] Furthermore, the application (APP) level factor can obtain the file information generated by each APP on each mobile device in the APP directory through the software development kit (SDK) that generates the device identification, such as the APP version number, SDK version number, etc.

[0041] Furthermore, user-level factors include but are not limited to mobile phone numbers, ID numbers, etc., which are used to identify the same user, but it is necessary to consider the situation where the user has multiple devices.

[0042] Step 102, when the initial state device identification exists in the device identification server, select the temporary state device identification and the abnormal state device identification in the initial state device identification according to the first similarity between the various factor information and the various factor information stored in the device identification server.

[0043] In some embodiments, when the initial state device identification exists in the device identification server, according to the first similarity between various factor information and various factor information stored in the device identification server, a temporary state device identification and abnormal state device identification in the initial state device identification are selected. One implementation method can be: when the initial state device identification exists in the device identification server, enable the first similarity algorithm to calculate the first similarity between various factor information and various factor information stored in the device identification server; obtain the first temporary factor information whose first similarity is higher than the preset first threshold, and modify the initial state device identification corresponding to the first temporary factor information to the temporary state device identification; obtain the second temporary factor information whose first similarity is lower than the preset first threshold, and modify the initial state device identification corresponding to the second temporary factor information to the abnormal state device identification. In this way, the mobile device identification life cycle status monitoring is realized, and the daily operation and optimization capabilities are improved.

[0044] Furthermore, before verifying whether the initial state device identification exists on the device identification server, an initial state device identification anti-tampering check can also be performed. If the initial state device identification anti-tampering check passes, it is verified whether the initial state device identification exists on the device identification server, thereby preventing the initial state device identification from being tampered with and ensuring the reliability of the initial state device identification.

[0045] In addition, after the initial state device identification corresponding to the first temporary factor information is modified to the temporary state device identification, the temporary state device identification is returned to the SDK for generating the device identification; after the initial state device identification corresponding to the second temporary factor information is modified to the abnormal state device identification, various abnormal factor information corresponding to the abnormal state device identification is obtained, and the backup device identification is recalculated based on the various abnormal factor information, and returned to the SDK for generating the device identification. Through the SDK for generating the device identification, a variety of functions can be realized, including but not limited to application push, user behavior tracking, and application analysis.

[0046] Step 103, when the initial state device identification does not exist in the device identification server, the temporary state device identification in the initial state device identification is selected according to the number of mobile devices found by the retrieval algorithm and the second similarity between the various factor information and the various factor information stored in the found mobile device.

[0047] In some embodiments, when the initial state device identifier does not exist on the device identifier server, an implementation method of selecting a temporary state device identifier from the initial state device identifier based on the number of mobile devices found by the retrieval algorithm and the second similarity between various factor information and various factor information stored in the found mobile devices may be: when the initial state device identifier does not exist on the device identifier server, when the number of mobile devices found by the retrieval algorithm is less than or equal to a preset numerical threshold, the second similarity algorithm is started for each mobile device found one by one to calculate the second similarity between various factor information and various factor information stored in the found mobile devices; when the second similarity is higher than the preset second threshold and there is only one, the initial state device identifier with the highest second similarity is returned to the SDK that generates the device identifier; when the second similarity is higher than the preset second threshold and there are multiple mobile devices, the initial state device identifier is modified to a temporary state device identifier; when the second similarity is lower than the preset second threshold, the initial state device identifier is modified to a temporary state device identifier. Another implementation method is that when the initial state device identification does not exist in the device identification server, when the number of mobile devices found by the retrieval algorithm is greater than the preset numerical threshold, the second similarity algorithm is started for each mobile device found to calculate the second similarity between various factor information and various factor information stored in the found mobile device; when the second similarity is higher than the preset second threshold and there are multiple mobile devices, or when the second similarity is lower than the preset second threshold, the initial state device identification is modified to a temporary state device identification. In this way, the device identification status monitoring of the same mobile device when the device identification is updated is realized, and the probability of device identification expansion is reduced.

[0048] The preset numerical threshold may be 10, but is not limited thereto, and this embodiment does not make any specific limitation thereto.

[0049] Optionally, before verifying that the initial state device identification does not exist on the device identification server, an initial state device identification anti-tampering check may be performed. If the initial state device identification anti-tampering check passes, the retrieval algorithm is started to ensure the reliability of the initial state device identification.

[0050] Further, when the number of mobile devices is less than or equal to the preset numerical threshold N (N≤10), when the second similarity is higher than the preset second threshold and there are multiple mobile devices, the initial state device identification is modified to the temporary state device identification, and a device identification collision record is generated in the abnormal library; when the second similarity is lower than the preset second threshold, the initial state device identification is modified to the temporary state device identification, and the temporary state device identification is returned to the SDK for generating the device identification. In addition, when the number of mobile devices is less than or equal to the preset numerical threshold N (N>10), when the second similarity is higher than the preset second threshold and there are multiple mobile devices, the initial state device identification is modified to the temporary state device identification, and a device identification collision record is generated in the abnormal library, corresponding to the new device, but the scene of abnormal similarity calculation on the device identification server; when the second similarity is lower than the preset second threshold, the initial state device identification is modified to the temporary state device identification, and the temporary state device identification is returned to the SDK for generating the device identification. Thus, the same device is accurately selected in the device identification server when the device identification is updated or changed.

[0051] Step 104 , by comparing the temporary state device identification with the final state device identification in which various factor information is fully collected in the temporary state device identification and the initial state device identification, the collection status of various factor information is determined.

[0052] In some embodiments, the final device identification is obtained by verifying that all factors in the temporary device identification and the initial device identification are complete through the device identification server. Once all factors are verified, it is the final device identification.

[0053] Among them, when the application is installed and started, after the initial device identification is calculated by the SDK that generates the device identification, various factor information and the initial device identification are sent to the device identification server for verification. If the various factor information of the initial device identification is not fully collected, it will be a temporary device identification.

[0054] Step 105: Analyze the cause of the device identification collision based on the abnormal device identification, and dynamically adjust the mobile device identification according to the collection situation and the cause of the device identification collision.

[0055] In some embodiments, when there are abnormal device identifications, the cause of the device identification collision may be a device identification collision or the presence of multiple different device identifications, but for mobile devices with high similarity (first similarity or second similarity), the device identification and various factor information stored in the mobile device are placed in the exception library for manual analysis to determine the cause of the device identification collision and provide data support for subsequent optimization of the device identification.

[0056] The mobile device identification management method of the embodiment of the present invention collects system-level factors, device-level factors, application-level factors and user-level factors of the mobile device corresponding to the application program through the SDK that generates the device identification, calculates the initial state device identification, and performs device identification server-side verification; when the initial state device identification exists or does not exist on the device identification server, calculates the temporary state device identification and / or abnormal state device identification in the initial state device identification; determines the collection status of various factor information by comparing the temporary state device identification with the final state device identification in which various factor information is fully collected; analyzes the cause of the device identification collision based on the abnormal state device identification, and then dynamically adjusts the mobile device identification, thereby increasing the operational capability of the device identification and reducing the probability of device identification collision and expansion through various factor information and adding four different life cycle states to the device identification.

[0057] In order to clearly explain the above embodiment, this embodiment further provides a method for managing mobile device identification. Figure 2 A schematic flow chart of another mobile device identification management method provided by an embodiment of the present invention.

[0058] like Figure 2 As shown, the method may include the following steps:

[0059] Step 201, when the application is installed and started, the initial device identification is calculated by collecting various factor information of the mobile device corresponding to the application, and the various factor information and the initial device identification are sent to the device identification server for verification.

[0060] Step 202, when the initial state device identification exists in the device identification server, select the temporary state device identification and the abnormal state device identification in the initial state device identification according to the first similarity between the various factor information and the various factor information stored in the device identification server.

[0061] Step 203, when the initial state device identification does not exist in the device identification server, the temporary state device identification in the initial state device identification is selected according to the number of mobile devices found by the retrieval algorithm and the second similarity between the various factor information and the various factor information stored in the found mobile device.

[0062] Step 204 , by comparing the temporary state device identification with the final state device identification in which various factor information is fully collected in the temporary state device identification and the initial state device identification, the collection status of various factor information is determined.

[0063] Step 205: Analyze the cause of the device identification collision based on the abnormal device identification.

[0064] It should be noted that, for the specific implementation of steps 201 to 205, reference may be made to the relevant description in the above embodiments.

[0065] Step 206 , based on the collection of various factor information by the SDK for generating the device identification, optimizing the SDK for generating the device identification and the collection rules of various factor information.

[0066] In some embodiments, the system-level factors, device-level factors, application-level factors, and user-level factors can be adjusted based on the collection of various factor information by the SDK that generates the device identification, thereby optimizing the SDK that generates the device identification and the collection rules of various factor information.

[0067] Step 207 , based on the cause of the device identification collision, the device identification calculation algorithm, the first similarity algorithm, the second similarity algorithm, and the retrieval algorithm for calculating the initial device identification are optimized.

[0068] In some embodiments, the device identification collision may be caused by different mobile devices generating the same device identification.

[0069] Furthermore, the system-level factors, device-level factors, application-level factors and user-level factors can be dynamically spaced according to the specific application scenarios and requirements of the application to optimize the device identification calculation algorithm for calculating the initial device identification.

[0070] Furthermore, the first similarity algorithm, the second similarity algorithm, and the retrieval algorithm can be optimized by dynamically adjusting the weights of system-level factors and device-level factors in the similarity algorithm (the first similarity algorithm or the second similarity algorithm) and the weights of application-level factors and user-level factors in the retrieval algorithm.

[0071] The mobile device identification management method of the embodiment of the present invention collects the system-level factors, device-level factors, application-level factors and user-level factors of the mobile device corresponding to the application program through the SDK that generates the device identification, calculates the initial state device identification, and performs the device identification service end verification; when the initial state device identification exists or does not exist in the device identification service end, calculates the temporary state device identification and / or abnormal state device identification in the initial state device identification; by comparing the temporary state device identification with the final state device identification with various factor information collected, determines the collection of various factor information; analyzes the cause of device identification collision based on the abnormal state device identification, optimizes the SDK that generates the device identification and the collection rules of various factor information based on the collection of various factor information by the SDK that generates the device identification; optimizes the device identification calculation algorithm, the first similarity algorithm, the second similarity algorithm, and the retrieval algorithm for calculating the initial state device identification based on the device identification collision cause. Therefore, through various factor information and the addition of four different life cycle states to the device identification, the collection of various factor information and the cause of device identification collision are determined, and a sustainable operation management of mobile device identification is realized, thereby adapting to different platforms and mobile device requirements, while satisfying the protection of user privacy.

[0072] In summary, in order to better understand the present invention, the present invention also provides a device identification state and its conversion schematic diagram, such as Figure 3 As shown, specifically, when the application is installed and started, various factor information of the mobile device corresponding to the application is collected through the SDK that generates the device identification, the initial state device identification is calculated, and the various factor information and the initial state device identification are sent to the device identification server for verification (analyzing the collection of various factor information of each mobile device); the temporary state device identification and the final state device identification are verified by the device identification server, and the various factor information in the temporary state device identification is not fully collected, while the various factor information in the final state device identification is fully collected; among them, the temporary state device identification and the initial state device identification in which the various factor information is fully collected are all final state device identifications; in addition, based on the first similarity, the abnormal state device identification in the initial state device identification is selected. When there is an abnormal state device identification, the cause of the device identification collision may be a device identification collision or the existence of multiple different device identifications, but for mobile devices with high similarity (first similarity or second similarity), the device identification and the various factor information stored in the mobile device are placed in the abnormal library for manual analysis.

[0073] In order to implement the above embodiment, the present invention also proposes a mobile device identification management device.

[0074] Figure 4 A schematic diagram of the structure of a mobile device identification management device provided by an embodiment of the present invention.

[0075] like Figure 4 As shown, the mobile device identification management device 40 includes: a first calculation module 41 , a second calculation module 42 , a third calculation module 43 , a determination module 44 and a control module 45 .

[0076] The first calculation module 41 is used to calculate the initial state device identification by collecting various factor information of the mobile device corresponding to the application when the application is installed and started, and send the various factor information and the initial state device identification to the device identification server for verification;

[0077] The second calculation module 42 is used to select the temporary state device identification and the abnormal state device identification in the initial state device identification according to the first similarity between the various factor information and the various factor information stored in the device identification server when the initial state device identification exists in the device identification server;

[0078] The third calculation module 43 is used to select the temporary device identifier in the initial device identifier according to the number of mobile devices found by the retrieval algorithm and the second similarity between the various factor information and the various factor information stored in the found mobile device when the initial device identifier does not exist in the device identifier server;

[0079] The determination module 44 is used to determine the collection status of various factor information by comparing the temporary state device identification with the final state device identification in which various factor information is fully collected in the temporary state device identification and the initial state device identification;

[0080] The control module 45 is used to determine the cause of the device identification collision by analyzing the abnormal device identification, and dynamically control the mobile device identification according to the collection situation and the cause of the device identification collision.

[0081] Furthermore, in a possible implementation of an embodiment of the present invention, the factor information includes system-level factors, device-level factors, application-level factors and user-level factors. The system-level factors are information for distinguishing different mobile devices, the device-level factors are information for identifying mobile devices, the application-level factors are file information generated by each APP on each mobile device, and the user-level factors are identification information for identifying the same user.

[0082] Furthermore, in a possible implementation of an embodiment of the present invention, after the application is installed and started, when it is monitored that the device identification field of the mobile device is empty or the device identification is an initially generated device identification or the device identification server requires an update of the device identification, various factor information of the mobile device corresponding to the application is collected through the SDK that generates the device identification, and the initial device identification is calculated, wherein when calculating the initial device identification, the calculation weights of the system-level factors, device-level factors, application-level factors and user-level factors are different.

[0083] Further, in a possible implementation manner of the embodiment of the present invention, the second calculation module 42 is specifically configured to:

[0084] In the case where the initial state device identification exists in the device identification server, a first similarity algorithm is activated to calculate a first similarity between various factor information and various factor information stored in the device identification server;

[0085] Acquire first temporary factor information whose first similarity is higher than a preset first threshold, and modify the initial state device identifier corresponding to the first temporary factor information to a temporary state device identifier;

[0086] Second temporary factor information whose first similarity is lower than a preset first threshold is obtained, and an initial state device identifier corresponding to the second temporary factor information is modified to an abnormal state device identifier.

[0087] Further, in a possible implementation of the embodiment of the present invention, the third calculation module 43 is specifically configured to:

[0088] In the case where the initial state device identification does not exist in the device identification server, when the number of mobile devices found by the retrieval algorithm is less than or equal to the preset numerical threshold, the second similarity algorithm is started for each mobile device found, so as to calculate the second similarity between various factor information and various factor information stored in the found mobile device;

[0089] When the second similarity is higher than a preset second threshold and there is only one, returning the initial state device identifier with the highest second similarity to the SDK for generating the device identifier;

[0090] When the second similarity is higher than a preset second threshold and there are multiple mobile devices, modifying the initial state device identifier to a temporary state device identifier;

[0091] When the second similarity is lower than a preset second threshold, the initial state device identifier is modified to a temporary state device identifier.

[0092] Furthermore, in a possible implementation of the embodiment of the present invention, the device further includes:

[0093] A first optimization module is used to optimize the SDK for generating device identification and the collection rules of various factor information based on the collection of various factor information by the SDK for generating device identification;

[0094] The second optimization module is used to optimize the device identification calculation algorithm for calculating the initial device identification, the first similarity algorithm, the second similarity algorithm, and the retrieval algorithm based on the device identification collision cause.

[0095] The mobile device identification management device of the embodiment of the present invention calculates the initial state device identification through the system-level factors, device-level factors, application-level factors and user-level factors of the mobile device corresponding to the application, and performs device identification server-side verification; when the initial state device identification exists or does not exist on the device identification server, calculates the temporary state device identification and / or abnormal state device identification in the initial state device identification; determines the collection status of various factor information by comparing the temporary state device identification with the final state device identification with various factor information collected; analyzes the cause of device identification collision based on the abnormal state device identification, and then dynamically adjusts the mobile device identification, thereby increasing the operational capability of the device identification and reducing the probability of device identification collision and expansion through various factor information and adding four different life cycle states to the device identification.

[0096] In order to implement the above embodiment, the present invention further provides an electronic device, including:

[0097] at least one processor; and

[0098] a memory communicatively connected to the at least one processor; wherein,

[0099] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can perform the aforementioned method.

[0100] In order to implement the above embodiment, the present invention further proposes a non-transitory computer-readable storage medium storing computer instructions, where the computer instructions are used to enable the computer to execute the above method.

[0101] In order to implement the above embodiments, the present invention further provides a computer program product, including a computer program, wherein the computer program implements the above method when executed by a processor.

[0102] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0103] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of the present invention, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0104] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present invention includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present invention belong.

[0105] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute the instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purpose of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (electronic device), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing in other suitable ways if necessary, and then stored in a computer memory.

[0106] It should be understood that the various parts of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0107] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

[0108] In addition, each functional unit in each embodiment of the present invention may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0109] The storage medium mentioned above may be a read-only memory, a magnetic disk or an optical disk, etc. Although the embodiments of the present invention have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limiting the present invention. A person of ordinary skill in the art may change, modify, replace and modify the above embodiments within the scope of the present invention.

Claims

1. A method for managing mobile device identification, characterized in that: The method comprises: When the application is installed and started, the initial device identification is calculated by collecting various factor information of the mobile device corresponding to the application, and the various factor information and the initial device identification are sent to the device identification server for verification; In the case where the initial state device identification exists on the device identification server, selecting the temporary state device identification and the abnormal state device identification from the initial state device identification according to the first similarity between the various factor information and the various factor information stored on the device identification server; In the case that the initial state device identification does not exist in the device identification server, selecting the temporary state device identification in the initial state device identification according to the number of mobile devices found by the retrieval algorithm and the second similarity between the various factor information and the various factor information stored in the found mobile device; By comparing the temporary state device identification with the final state device identification in which various factor information is fully collected in the temporary state device identification and the initial state device identification, the collection status of various factor information is determined; Based on the abnormal device identification, the cause of the device identification collision is analyzed, and the mobile device identification is dynamically adjusted according to the collection situation and the cause of the device identification collision.

2. The method according to claim 1, characterized in that in, The factor information includes system-level factors, device-level factors, application-level factors and user-level factors. The system-level factors are information for distinguishing different mobile devices, the device-level factors are information for identifying mobile devices, the application-level factors are file information generated by each APP on each mobile device, and the user-level factors are identification information for identifying the same user.

3. The method according to claim 2, characterized in that After the application is installed and started, if it is detected that the device identification field of the mobile device is empty or the device identification is the initially generated device identification or the device identification server requires the device identification to be updated, the SDK that generates the device identification collects various factor information of the mobile device corresponding to the application and calculates the initial device identification. When calculating the initial device identification, the calculation weights of the system-level factors, device-level factors, application-level factors and user-level factors are different.

4. The method according to claim 1, characterized in that In the case where the initial state device identification exists in the device identification server, selecting the temporary state device identification and the abnormal state device identification in the initial state device identification according to the first similarity between the various factor information and the various factor information stored in the device identification server includes: In the case where the initial state device identification exists in the device identification server, a first similarity algorithm is activated to calculate a first similarity between various factor information and various factor information stored in the device identification server; Acquire first temporary factor information whose first similarity is higher than a preset first threshold, and modify the initial state device identifier corresponding to the first temporary factor information to a temporary state device identifier; Second temporary factor information whose first similarity is lower than a preset first threshold is obtained, and an initial state device identifier corresponding to the second temporary factor information is modified to an abnormal state device identifier.

5. The method according to claim 1, characterized in that In the case that the initial state device identification does not exist in the device identification server, selecting the temporary state device identification in the initial state device identification according to the number of mobile devices found by the retrieval algorithm and the second similarity between the various factor information and the various factor information stored in the found mobile device, includes: In the case where the initial state device identification does not exist in the device identification server, when the number of mobile devices found by the retrieval algorithm is less than or equal to the preset numerical threshold, the second similarity algorithm is started for each mobile device found, so as to calculate the second similarity between various factor information and various factor information stored in the found mobile device; When the second similarity is higher than a preset second threshold and there is only one, returning the initial state device identifier with the highest second similarity to the SDK for generating the device identifier; When the second similarity is higher than a preset second threshold and there are multiple mobile devices, modifying the initial state device identifier to a temporary state device identifier; When the second similarity is lower than a preset second threshold, the initial state device identifier is modified to a temporary state device identifier.

6. The method according to claim 5, characterized in that The method further comprises: In the case where the initial state device identification does not exist in the device identification server, when the number of mobile devices found by the retrieval algorithm is greater than a preset numerical threshold, the second similarity algorithm is started for each mobile device found, so as to calculate a second similarity between various factor information and various factor information stored in the found mobile device; When the second similarity is higher than a preset second threshold and there are multiple mobile devices, or when the second similarity is lower than a preset second threshold, the initial state device identifier is modified to a temporary state device identifier.

7. The method according to claim 3, characterized in that The method further comprises: Based on the collection of various factor information by the SDK generating the device identification, optimizing the SDK generating the device identification and the collection rules of various factor information; Based on the cause of the device identification collision, the device identification calculation algorithm for calculating the initial device identification, the first similarity algorithm, the second similarity algorithm, and the retrieval algorithm are optimized.

8. A device for managing mobile device identification, characterized in that: The device comprises: The first calculation module is used to calculate the initial state device identification by collecting various factor information of the mobile device corresponding to the application when the application is installed and started, and send the various factor information and the initial state device identification to the device identification server for verification; A second calculation module is used to select a temporary state device identifier and an abnormal state device identifier from the initial state device identifier according to a first similarity between various factor information and various factor information stored in the device identifier server when the initial state device identifier exists in the device identifier server; a third calculation module, configured to select a temporary device identifier from the initial device identifier according to the number of mobile devices found by the retrieval algorithm and the second similarity between the various factor information and the various factor information stored in the found mobile device, when the initial device identifier does not exist in the device identifier server; A determination module is used to determine the collection status of various factor information by comparing the temporary state device identification with the final state device identification in which various factor information is fully collected in the temporary state device identification and the initial state device identification; The control module is used to analyze the cause of the device identification collision based on the abnormal device identification, and dynamically control the mobile device identification according to the collection situation and the cause of the device identification collision.

9. The device according to claim 8, characterized in that in, The factor information includes system-level factors, device-level factors, application-level factors and user-level factors. The system-level factors are information for distinguishing different mobile devices, the device-level factors are information for identifying mobile devices, the application-level factors are file information generated by each APP on each mobile device, and the user-level factors are identification information for identifying the same user.

10. The device according to claim 9, characterized in that After the application is installed and started, if it is detected that the device identification field of the mobile device is empty or the device identification is the initially generated device identification or the device identification server requires the device identification to be updated, the SDK that generates the device identification collects various factor information of the mobile device corresponding to the application and calculates the initial device identification. When calculating the initial device identification, the calculation weights of the system-level factors, device-level factors, application-level factors and user-level factors are different.

11. The device according to claim 8, characterized in that The second calculation module is specifically used for: In the case where the initial state device identification exists in the device identification server, a first similarity algorithm is activated to calculate a first similarity between various factor information and various factor information stored in the device identification server; Acquire first temporary factor information whose first similarity is higher than a preset first threshold, and modify the initial state device identifier corresponding to the first temporary factor information to a temporary state device identifier; Second temporary factor information whose first similarity is lower than a preset first threshold is obtained, and an initial state device identifier corresponding to the second temporary factor information is modified to an abnormal state device identifier.

12. The device according to claim 8, characterized in that The third calculation module is specifically used for: In the case where the initial state device identification does not exist in the device identification server, when the number of mobile devices found by the retrieval algorithm is less than or equal to the preset numerical threshold, the second similarity algorithm is started for each mobile device found, so as to calculate the second similarity between various factor information and various factor information stored in the found mobile device; When the second similarity is higher than a preset second threshold and there is only one, returning the initial state device identifier with the highest second similarity to the SDK for generating the device identifier; When the second similarity is higher than a preset second threshold and there are multiple mobile devices, modifying the initial state device identifier to a temporary state device identifier; When the second similarity is lower than a preset second threshold, the initial state device identifier is modified to a temporary state device identifier.

13. The device according to claim 12, characterized in that The third calculation module is further specifically used for: In the case where the initial state device identification does not exist in the device identification server, when the number of mobile devices found by the retrieval algorithm is greater than a preset numerical threshold, the second similarity algorithm is started for each mobile device found, so as to calculate a second similarity between various factor information and various factor information stored in the found mobile device; When the second similarity is higher than a preset second threshold and there are multiple mobile devices, or when the second similarity is lower than a preset second threshold, the initial state device identifier is modified to a temporary state device identifier.

14. The device according to claim 10, characterized in that The device also includes: A first optimization module is used to optimize the SDK for generating device identification and the collection rules of various factor information based on the collection of various factor information by the SDK for generating device identification; The second optimization module is used to optimize the device identification calculation algorithm for calculating the initial device identification, the first similarity algorithm, the second similarity algorithm, and the retrieval algorithm based on the device identification collision cause.

15. An electronic device, characterized in that: include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 7.

16. A non-transitory computer-readable storage medium storing computer instructions, characterized in that: The computer instructions are used to cause the computer to execute the method according to any one of claims 1-7.

17. A computer program product, characterized in that The invention comprises a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 7.

Images