Equipment identifier generation method and device

Abstract

The embodiment of the invention provides an equipment identifier generation method and device, computer equipment, a computer readable storage medium and a computer program product, and relates to the technical field of equipment identifier codes, product electronic codes and Internet of Things codes. The method comprises the steps that in response to installation of a target application, multiple device codes are acquired from a client locally, and the coding types of the multiple device codes are different; generating a code query request according to the plurality of device codes; sending a code query request to a server, so that the server determines and returns a target device code from the plurality of device codes according to a preset repeated device code library; and under the condition that the target equipment code is received, generating a target equipment identifier for identifying the client according to the target equipment code. According to the technical scheme provided by the embodiment of the invention, the duplicate removal speed and accuracy of the device code can be improved, so that the uniqueness of the target device identifier can be ensured, and the generation efficiency of the device identifier can be improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the fields of device identification coding, product electronic coding, and Internet of Things coding technology, and in particular to a device identification generation method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] Service providers use device identifiers to identify clients using their services. Device identifiers can be used to address data collection and service precision. Device identifiers can be generated based on various client device IDs, such as IMEI, Android ID, and MAC address. However, these device identifiers may not be unique, resulting in the generation of identical device identifiers for different clients, making it difficult for service providers to accurately identify different clients.

[0003] It should be noted that the above content is not necessarily prior art, nor is it intended to limit the scope of patent protection of this application. Summary of the Invention

[0004] The embodiments of the present application provide a device identification generation method, apparatus, computer device, computer-readable storage medium, and computer program product to solve or alleviate one or more technical problems raised above.

[0005] One aspect of an embodiment of the present application provides a method for generating a device identifier, the method comprising: In response to installing the target application, obtaining multiple device codes from the client locally, where the multiple device codes are of different encoding types; generating a code query request according to the plurality of device codes; Sending the code query request to a server, so that the server determines and returns a target device code from the multiple device codes according to a preset repeated device code library; wherein the preset repeated device code library includes multiple repeated device codes, and the target device code is a code that does not belong to the multiple repeated device codes; When the target device code is received, a target device identifier for identifying the client is generated according to the target device code.

[0006] Optionally, generating a code query request according to the multiple device codes includes: Receiving a repeated device code file sent by the server; wherein the repeated device code file includes a plurality of highly repeated device codes, wherein the highly repeated device codes are repeated device codes having a number of repetitions exceeding a predetermined threshold; Determining one or more first device codes from the multiple device codes according to the repeated device code file, wherein the first device codes are all different from the multiple highly repeated device codes; Generate the code query request based on one or more first device codes Optionally, generating a code query request according to the multiple device codes includes: Acquire a plurality of highly repeated device codes from the installation package of the target application, wherein the highly repeated device codes are repeated device codes having a number of repetitions exceeding a predetermined threshold; Determining one or more second device codes from the plurality of device codes according to the repeated device code file, wherein the second device codes are all different from the plurality of highly repeated device codes; The code query request is generated according to one or more second device codes.

[0007] Optionally, the preset repetitive device code library is obtained according to the following operations: Acquire multiple daily active user logs, each of which corresponds to multiple codes of devices to be checked for duplicates of different coding types and an identifier of a device to be checked for duplicates; determining, based on the plurality of daily active user logs, a plurality of different recode-identification pairs to be checked; Determining a plurality of duplicate device codes based on the plurality of duplicate code-identification pairs to be checked and the corresponding plurality of daily active user logs, each duplicate device code corresponding to a plurality of different duplicate code-identification pairs to be checked; According to the plurality of repeated device codes, the preset repeated device code library is obtained.

[0008] Optionally, the method further includes: Generate an identification query request based on the target device identification at a preset time interval; Sending the identification query request to the server, so that the server returns a duplicate checking result according to a preset duplicate device identification library; If the duplicate checking result is a duplicate, the target device identifier is regenerated.

[0009] Optionally, the preset duplicate device identification library is obtained according to the following operations: Acquire multiple daily active user logs, each of which corresponds to multiple different types of to-be-checked duplicate device codes and a to-be-checked duplicate device identifier; Determining, based on the plurality of daily active user logs, a plurality of recode-identification pairs to be checked, each of the recode-identification pairs to be checked being different; Determine multiple duplicate device identifiers based on the multiple duplicate code-identification pairs to be checked and the corresponding multiple daily active user logs; wherein each duplicate device identifier corresponds to multiple different duplicate code-identification pairs to be checked, and the multiple duplicate device identifiers to be checked in the multiple different duplicate code-identification pairs to be checked have the same encoding type; According to the multiple duplicate device identifiers, the preset duplicate device code library is obtained.

[0010] Optionally, the method further includes: In the case that the target device code is not received, the target device identifier is generated according to a plurality of the device codes in accordance with a preset identifier generation rule.

[0011] Another aspect of an embodiment of the present application provides a device identification generating apparatus, the apparatus comprising: an acquisition module, configured to acquire, in response to installing the target application, a plurality of device codes from the client locally, wherein the encoding types of the plurality of device codes are all different; A first generating module, configured to generate a code query request according to the multiple device codes; a sending module, configured to send the code query request to a server, so that the server determines and returns a target device code from the multiple device codes according to a preset duplicate device code library; wherein the preset duplicate device code library includes multiple duplicate device codes, and the target device code is a code that does not belong to the multiple duplicate device codes; The second generating module is configured to generate a target device identifier for identifying the client according to the target device code when the target device code is received.

[0012] Another aspect of an embodiment of the present application provides a computer device, including: at least one processor; and a memory communicatively coupled 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 described above.

[0013] Another aspect of an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the computer instructions are executed by a processor, the method described above is implemented.

[0014] Another aspect of an embodiment of the present application provides a computer program product, including a computer program, which implements the above-mentioned method when executed by a processor.

[0015] The embodiments of the present application employing the above-mentioned technical solution may provide the following advantages: By querying a server for unique target device codes to generate target device identifiers, the server's big data query capabilities can be utilized to improve the speed and accuracy of deduplication of device codes, thereby helping to ensure the uniqueness of target device identifiers and improving the efficiency of device identifier generation, thereby enabling service providers to provide more accurate data statistics and data services. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The accompanying drawings illustrate exemplary embodiments and constitute a part of the specification. Together with the description of the specification, they serve to explain exemplary implementation of the embodiments. The illustrated embodiments are for illustrative purposes only and do not limit the scope of the claims. Throughout the drawings, the same reference numerals designate similar, but not necessarily identical, elements.

[0017] Figure 1 A diagram schematically illustrates an operating environment of a method for generating a device identifier according to a first embodiment of the present application; Figure 2 The following schematically shows a flow chart of a method for generating a device identification according to the first embodiment of the present application; Figure 3 Schematically shows Figure 2 Flowchart of sub-steps of step S202; Figure 4 Schematically shows Figure 2 Another sub-step flow chart of step S202; Figure 5 Schematically shows a newly added flow chart of the device identification generation method according to the first embodiment of the present application; Figure 6 Schematically shows another newly added flow chart of the device identification generation method according to the first embodiment of the present application; Figure 7 Schematically shows another newly added flow chart of the device identification generation method according to the first embodiment of the present application; Figure 8 Schematically illustrates a flow chart of constructing a preset duplicate device code library and a preset duplicate device identification library according to a device identification generation method according to an embodiment of the present application; Figure 9 The following schematically illustrates a process flow of generating a target device identifier when a client newly installs a target application according to a device identifier generation method according to an embodiment of the present application; Figure 10 Schematically illustrates a flow chart of a client periodically updating a duplicate target device identifier according to a device identifier generation method according to an embodiment of the present application; Figure 11 The following schematically illustrates an overall process flow diagram of a method for generating a device identifier according to an embodiment of the present application; Figure 12 The following schematically illustrates an exemplary application process of a method for generating a device identification according to an embodiment of the present application; Figure 13 A block diagram schematically shows a device identification generating apparatus according to the second embodiment of the present application; and Figure 14 The following schematically shows a hardware architecture diagram of a computer device according to the third embodiment of the present application. DETAILED DESCRIPTION

[0018] In order to make the purpose, technical solutions and advantages of this application more clear, the present application is further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0019] It should be noted that the descriptions of "first", "second", etc. in the embodiments of the present application are for descriptive purposes only and should not be understood as indicating or implying their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" or "second" may explicitly or implicitly include at least one of such features. In addition, the technical solutions between the various embodiments can be combined with each other, but this must be based on the fact that they can be implemented by ordinary technicians in this field. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by this application.

[0020] In the description of this application, it should be understood that the numerical labels before the steps do not indicate the order in which the steps are executed. They are only used to facilitate the description of this application and to distinguish each step. Therefore, they cannot be understood as limitations on this application.

[0021] First, an explanation of the terms used in this application is provided: IMEI: International Mobile Equipment Identity, a unique identification code assigned to mobile devices, used to identify mobile terminal devices.

[0022] DrmID: A unique identifier used to identify a device in a digital rights management (DRM) system. It's part of the MediaDrm class, part of the Digital Audio Rights Framework, and is used to track and protect copyrights.

[0023] MAC address (Media Access Control Address): A unique identifier for a network device interface. A MAC address is a 48-bit (6-byte) number assigned by the network device manufacturer to uniquely identify the device on the network.

[0024] Android ID: An identifier generated by the Android system to identify a device. It is generated when the device is first started. The Android ID may change after the device is reset (for example, restoring factory settings).

[0025] UUID (Universally Unique Identifier): is an algorithm standard for generating unique identifiers in distributed systems, consisting of a set of numbers, letters, and hyphens.

[0026] Hash algorithm: It is an algorithm that converts input data of arbitrary length into fixed-length output, the output is called a hash value or hash value.

[0027] Environmental perception sensors: These are devices that sense and measure various physical, chemical, or biological quantities in the surrounding environment and convert them into electrical signals or other readable forms. These sensors include light sensors (which sense light intensity), temperature sensors (which measure ambient temperature), humidity sensors (which detect air humidity), pressure sensors (which measure atmospheric pressure), and sonar sensors (which sense distance and obstacles).

[0028] CRC (Cyclic Redundancy Check Code) is a coding technique used to detect data errors during data transmission and storage. It treats the data as a very long binary number. A predefined generating polynomial is selected and then divided by the generating polynomial using modulo-2 division. The remainder is the CRC code.

[0029] Software package: A software program and its associated files, data, and configuration information are packaged into a single, distributable, and installable unit. This includes the software's executable files, library files, configuration files, help documentation, resource files, and scripts or tools for installing, uninstalling, and managing the software.

[0030] Daily active user logs: These are documents that record the behavior and related operations of active users on an app or platform on a given day. These logs include basic user identity data (such as account number and device ID), key behavior records (such as page browsing time, buttons clicked, and activities participated in), as well as detailed information such as operation time and network type used.

[0031] Secondly, to facilitate understanding of the technical solutions provided by the embodiments of this application by those skilled in the art, the following describes the relevant technologies: Generating unique device identifiers for mobile apps is a key technology for internet companies to achieve data statistics and service precision. Device identifier generation methods include generating device identifiers based on a combination of hardware identifiers and a hash algorithm, and dynamically selecting hardware identifiers based on priority to generate device identifiers and store them in a local cache.

[0032] The inventors discovered that, in order to ensure stability, the device identification generation scheme is based on the device ID (such as DrmID, IMEI, MAC, Android ID, UUID, etc.), but the device ID itself has a certain probability of duplication, resulting in a certain probability of duplication for the device identification generated based on the device ID. As a result, one device identification may correspond to multiple real devices, affecting the accuracy of data statistics and services provided to the client.

[0033] To this end, embodiments of the present application provide a technical solution for generating device identifiers. This technical solution (1) utilizes daily active user logs to accurately identify different real devices, effectively filtering out duplicate device codes and device identifiers that are reused for different real devices; and (2) utilizes big data technology to query and pre-set a library of duplicate device codes on a server, thereby improving the speed and accuracy of determining target device codes and the efficiency and effectiveness of device identifier deduplication. See below for details.

[0034] Finally, for ease of understanding, an exemplary operating environment is provided below.

[0035] like Figure 1 As shown, the operating environment diagram includes: server 2, clients (4A, 4B, ..., 4N).

[0036] The server 2 can be connected to the clients ( 4A, 4B, ..., 4N) via a network.

[0037] The server 2 may be a single server, a server cluster or a cloud computing service center.

[0038] Server 2 can provide target application-related software services, device code query services, device identification query services, etc. to the client.

[0039] Server 2 can be located in a single location, such as a data center, or distributed across different geographical locations (e.g., across multiple locations). Server 2 can provide services via a network. The network includes various network devices, such as routers, switches, multiplexers, hubs, modems, bridges, repeaters, firewalls, proxy devices, and / or the like. The network can include physical links, such as coaxial cable links, twisted pair cable links, fiber optic links, combinations thereof, and the like, or wireless links, such as cellular links, satellite links, Wi-Fi links, and the like.

[0040] Clients (4A, 4B, ..., 4N) can be configured to access content and services from server 2. Clients (4A, 4B, ..., 4N) can include electronic devices with or connected to display panels, such as mobile devices, tablets, laptops, workstations, virtual reality devices, gaming devices, digital streaming devices, vehicle terminals, smart televisions, set-top boxes, and the like. They can also include virtualized computing instances. Virtualized computing instances can include virtual machines, such as emulations of computer systems, operating systems, servers, and the like. A computing device can load a virtual machine based on a virtual image and / or other data defining the specific software (e.g., operating system, specialized applications, servers) used for the emulation. As demand for different types of processing services changes, different virtual machines can be loaded and / or terminated on one or more computing devices.

[0041] Clients (4A, 4B, ..., 4N) can be associated with one or more users. A single user can also use one or more of the clients (4A, 4B, ..., 4N) to access server 2. Clients (4A, 4B, ..., 4N) can travel to various locations and use different networks to access server 2.

[0042] The client (4A, 4B, ..., 4N) may include an interface. The interface may include a touchpad, a touch screen, a mouse, a keyboard, or other sensing elements. For example, the input element may be configured to receive user instructions, which may cause the client (4A, 4B, ..., 4N) to perform various operations, such as software installation operations.

[0043] It should be noted that the above devices are exemplary, and the number and type of devices can be adjusted in different scenarios or according to different needs.

[0044] The following describes the technical solutions of the present application through multiple embodiments, taking the client 4A as the execution subject. It should be noted that these embodiments can be implemented in various forms and should not be construed as being limited to the embodiments described here.

[0045] Example 1 Figure 2The flowchart of the device identification generation method according to the first embodiment of the present application is schematically shown.

[0046] like Figure 2 As shown, the device identification generation method may include steps S200 to S206, wherein: Step S200 : in response to installing the target application, obtaining a plurality of device codes from the client locally, wherein the encoding types of the plurality of device codes are all different.

[0047] Step S202: Generate a code query request based on the multiple device codes.

[0048] Step S204: Send the code query request to the server, so that the server determines and returns the target device code from the multiple device codes based on a preset duplicate device code library; wherein the preset duplicate device code library includes multiple duplicate device codes, and the target device code is a code that does not belong to the multiple duplicate device codes.

[0049] Step S206: upon receiving the target device code, generating a target device identifier for identifying the client according to the target device code.

[0050] The device identification generation method provided in this embodiment generates a target device identification by querying a server to obtain a unique target device code. Leveraging the server's big data query capabilities, the speed and accuracy of device code deduplication can be improved, thereby helping to ensure the uniqueness of the target device identification and improving the efficiency of device identification generation. This in turn enables software service providers to provide more accurate data statistics and data services.

[0051] The following combination Figure 2 , each step in steps S200~S206 and other optional steps are described in detail.

[0052] Step S200 In response to installing the target application, a plurality of device codes are obtained from the client locally, and the encoding types of the plurality of device codes are all different.

[0053] The client can be a "new device" that has not previously installed the target app. When a new device installs the target app for the first time, it will be identified as "installing the target app." The client can also be an "old device" that has previously installed the target app. When an old device reinstalls the target app after uninstalling it, or updates an older version of the target app, it will also be identified as "installing the target app."

[0054] The device code can be a client hardware or software code such as DrmID, IMEI, MAC, Android ID, or UUID. In some embodiments, the device code can also be an environment-related code generated by the client using a specific algorithm (such as a hash algorithm) based on environmental data collected by environmental sensors (such as a barometer, hygrometer, or light sensor) when installing the target application.

[0055] With user authorization, the device code can also be a behavioral pattern code generated by the client using sensors such as accelerometers and gyroscopes to collect user operating behaviors (such as shaking the device, rotating the device, etc.) in a short period of time before and after installation.

[0056] In some embodiments, when the client is a virtual client in a test environment or a simulator, the device code may also be a device code with real features simulated by the client through a virtual device code generator.

[0057] Step S202 , generating a code query request based on the multiple device codes.

[0058] In some embodiments, before generating a code query request, the acquired device codes can be preliminarily screened using an intelligent screening algorithm to eliminate codes with obvious problems (e.g., high repetition rates, codes that are easily tampered with, etc.). Pre-configured priority rules (e.g., priority rules based on device code reliability) can also be used to select one or more device codes with higher priority to generate a code query request.

[0059] In some embodiments, the device code may be encrypted when generating a code query request. Multiple device codes may also be sorted according to a predetermined code sequence to ensure that the server can more efficiently perform matching and retrieval when processing the code query request.

[0060] In some embodiments, the coding query request may also include verification information (such as CRC check code, hash value, geographic location information of the device, network connection information, etc.) or timestamp, etc., to enhance the accuracy and credibility of the coding query request.

[0061] In other embodiments, for "old devices" such as clients that are uninstalled and then reinstalled, the code query request may also include historical record information of the client obtained from the client's local cache, such as the change history of the device identification, the frequency of use of the client, etc., so that the server can determine the target device code based on the client's history and current device coding situation.

[0062] As mentioned above, before generating a code query request, the acquired device codes can be preliminarily screened. Several exemplary screening methods are provided below.

[0063] Method 1: In an optional embodiment, as Figure 3 As shown, step S202 includes: S300, receiving a repeated device code file sent by the server; wherein the repeated device code file includes a plurality of highly repeated device codes, and the highly repeated device codes are repeated device codes with a number of repetitions exceeding a predetermined threshold.

[0064] S302: Determine one or more first device codes from the multiple device codes according to the repeated device code file, where the first device codes are all different from the multiple highly repeated device codes.

[0065] S304: Generate the code query request according to the one or more first device codes.

[0066] In some embodiments, the client may proactively request the server to obtain the duplicate device code file when installing the target application, or the server may send the duplicate device code file to the client at a predetermined time period.

[0067] In some embodiments, the highly repeated device codes in the repeated device code file may be determined by the server based on logs reported by multiple clients, etc. The repeated device code file may also include information such as the number of repetitions or repetition probability corresponding to each highly repeated device code.

[0068] In some embodiments, the duplicate device code file may also include device characteristics such as the highly probable device model and operating system version associated with each highly duplicate device code. When determining the first device code, the client may also compare its own device characteristics with those associated with the highly duplicate device codes, and select the device code with the non-duplicate code and significantly different device characteristics as the first device code.

[0069] In other embodiments, after determining the first device code, the client may also directly generate a target device identifier according to the first device code.

[0070] In this embodiment, multiple device codes are screened based on the device codes with a high probability of duplication sent by the server. A first device code with a low probability of duplication is selected to generate a code query request. This simplifies the data in the code query request, reduces the workload of the server for code comparison, and thus improves the efficiency of code query.

[0071] Method 2: In an optional embodiment, as Figure 4 As shown, step S202 includes: S400: Acquire multiple highly repetitive device codes from the software package of the target application, where the highly repetitive device codes are repeated device codes with a number of repetitions exceeding a predetermined threshold.

[0072] S402: Determine one or more second device codes from the multiple device codes according to the repeated device code file, where the second device codes are all different from the multiple highly repeated device codes.

[0073] S404: Generate the code query request according to one or more second device codes.

[0074] In some embodiments, the software package can be an installation package or an update package. When the client installs or updates the target application, it obtains the highly repetitive device code from the installation package or update package. The software package can also be a function package. When the client downloads a specific function module, it obtains the highly repetitive device code from the function package.

[0075] In some embodiments, the highly repetitive device code can be encrypted and stored in the software package. When installing the target application, the client can parse the software package or request the server to obtain the corresponding decryption algorithm and key for decryption. The highly repetitive device code can also be compressed and stored in the software package, or distributed in different locations or modules of the software package.

[0076] The remaining storage and usage details of the highly repetitive device code, as well as the technical details of the second device code determination process, can be referred to in Method 1 and will not be described in detail here.

[0077] In this embodiment, the second device code used to generate the code query request is determined based on the highly repetitive device codes in the software package. The highly repetitive device codes stored in the software package can speed up the determination of the second device code and the generation of the code query request, thereby improving the efficiency of the device identification deduplication process.

[0078] Step S204 , sending the code query request to the server, so that the server determines and returns the target device code from the multiple device codes according to a preset repeated device code library; wherein the preset repeated device code library includes multiple repeated device codes, and the target device code is a code that does not belong to the multiple repeated device codes.

[0079] In some embodiments, after receiving the encoding query request from the client, the server can verify the client through digital certificates, token verification, etc.

[0080] In some embodiments, the preset duplicate device code library can be generated by a server through analysis and processing of device data collected from client access logs (including information such as device code, device type, operating system version, and geographic location). The server can also perform noise reduction and correction on the collected device data and use the processed device data to generate the preset duplicate device code library.

[0081] In other embodiments, the preset duplicate device code library may also be a pre-authorized third-party database. The preset duplicate device code library may also include abnormal data actively reported by users or clients.

[0082] In this embodiment, the server returns unique target device codes by querying a pre-set duplicate device code library. By leveraging big data technology, both server queries and the pre-set duplicate device code library can improve the speed and accuracy of determining target device codes, thereby increasing the efficiency and effectiveness of device identification deduplication.

[0083] As mentioned above, there are multiple ways to obtain the preset duplicate device code library. An exemplary method is provided below.

[0084] In an optional embodiment, if Figure 5 As shown, the preset repetitive device code library is obtained according to the following operations: S500: Acquire multiple daily active user logs, each of which corresponds to multiple codes of devices to be checked for duplicates of different coding types and a device identifier to be checked for duplicates.

[0085] S502: Determine a plurality of different recode-identification pairs to be checked based on the plurality of daily active user logs.

[0086] S504 : Determine multiple duplicate device codes based on the multiple duplicate code-identification pairs to be checked and the corresponding multiple daily active user logs, where each duplicate device code corresponds to multiple different duplicate code-identification pairs to be checked.

[0087] S506: Acquire the preset repeated device code library according to the multiple repeated device codes.

[0088] Daily active user logs can include user login logs, operation logs, and so on. After obtaining daily active user logs, the obtained log data can also be pre-processed, such as data cleaning, noise removal, and formatting. In other embodiments, device performance logs and network connection logs can also be integrated to obtain more comprehensive and complete device code and device identification data.

[0089] Device codes for duplicates of different encoding types can include software or hardware codes such as DrmID, IMEI, MAC, Android ID, and UUID. Each duplicate code-identification pair can include a device code and a device identifier. Multiple duplicate code-identification pairs generated by a daily active user log can have different encoding types.

[0090] For multiple duplicate code / identification pairs containing the same device code to be checked for duplicates, the information in the daily active user logs corresponding to each duplicate code / identification pair can be used to determine whether these daily active user logs come from different real devices. If they are different real devices, it can be determined that the device code is duplicated. For example, based on the multiple duplicate code / identification pairs to be checked and the corresponding multiple daily active user logs, determining multiple duplicate device codes may include: Determining, from the plurality of duplicate code-identification pairs to be checked, a first duplicate code-identification pair to be checked and a second duplicate code-identification pair to be checked, which have the same duplicate device code; Determining a plurality of first behavior information feature vectors (such as active time information, active geographic location information, etc.) and a plurality of first client information feature vectors (such as client hardware information, client software information, etc.) based on the daily active user log corresponding to the first to-be-checked recode-identification pair; and Determine a plurality of second behavior information feature vectors and a plurality of second client information feature vectors based on the daily active user log corresponding to the second to-be-checked recode-identification pair; determining a plurality of behavior information conflict vectors based on the plurality of first behavior information feature vectors and the plurality of second behavior information feature vectors; and determining a plurality of client information conflict vectors based on the plurality of first client information feature vectors and the plurality of second client information feature vectors; Determining a conflict score between the first to-be-checked re-encoding identifier pair and the second to-be-checked re-encoding identifier pair based on the multiple behavior information conflict vectors, the multiple client information conflict vectors, and a pre-configured conflict vector weight array; When the conflict score is not lower than a preset conflict threshold, it is determined that the device codes to be checked for duplicates in the first duplicate code identification pair to be checked and the second duplicate code identification pair to be checked are duplicate device codes.

[0091] In this embodiment, multiple duplicate device codes are determined based on daily active user logs to construct a preset duplicate device code library. Using these daily active user logs, different real devices can be accurately identified, effectively filtering out duplicate device codes that are reused for different real devices, thereby improving the integrity and comprehensiveness of the preset duplicate device code library.

[0092] Figure 8The following is a flow chart of constructing a preset duplicate device code library (and a preset duplicate device identification library described later) according to the device identification generation method of the embodiment of the present application. Figure 8 In the process, the server can build multiple device ID-Buvid relationship pairs (i.e., re-encoding-identification pairs to be checked) based on the collected DAU logs (i.e., daily active user logs), and build a duplicate device ID library (i.e., a preset duplicate device code library) based on the duplication (one device ID corresponds to multiple Buvids or one Buvid corresponds to more than two device IDs of the same type) and various conflict situations (such as active time conflicts, geographic location conflicts, hardware information conflicts, and software information conflicts, etc.).

[0093] Step S206 , when the target device code is received, a target device identifier for identifying the client is generated according to the target device code.

[0094] There may be one or more received target device codes. In some embodiments, a target device identifier may be generated based on the target device code with the highest priority among the target device codes according to a preconfigured priority. In other embodiments, when there are multiple target device codes, the target device identifier may be obtained by combining the multiple target device codes according to a pre-set or dynamically generated weight array.

[0095] In some embodiments, the target device identifier may also include a timestamp or version number information. After generating the target device identifier, the client may also report the generated target device identifier to the server through a daily active user log or other means.

[0096] In some embodiments, the client can also dynamically adjust the target device identifier generation logic and content based on changes in software or hardware status. For example, when it is detected that the client's geographic location has changed across cities, or the client has performed a major operation such as a system upgrade, the target device identifier is regenerated to ensure that the target device identifier accurately reflects the client's current status.

[0097] In this embodiment, the target device identification is generated based on the query of non-duplicate target device codes. The deduplicated target device codes can reduce the probability of duplicate generated target device identifications, help ensure the uniqueness of the target device identification, and thus improve the identification effect of the target device identification.

[0098] As mentioned above, after generating the target device identifier, the client can also adjust the content of the target device identifier. An exemplary adjustment method is described below.

[0099] In an optional embodiment, if Figure 6 As shown, the method further includes: S600: Generate an identification query request according to the target device identification at a preset time interval.

[0100] S602: Send the identification query request to the server, so that the server returns a duplicate checking result according to a preset duplicate device identification library.

[0101] S604: When the duplicate checking result is a duplicate, regenerate the target device identifier.

[0102] In some embodiments, the preset time interval can be a fixed value, such as 12 hours, one day, or one week. In other embodiments, the preset time interval can also be dynamically set based on factors such as device activity, frequency of use, and device type. For example, a shorter preset time interval can be set for device models with a high frequency or probability of repeated device identification.

[0103] In some embodiments, the preset duplicate device identifier library can be generated by a server through analysis and processing of device data collected from client access logs (including information such as device code, device type, operating system version, and geographic location). The server can also perform noise reduction and correction on the collected device data and use the processed device data to generate the preset duplicate device identifier library.

[0104] In some embodiments, the target device identifier can be regenerated by using the method for generating the target device identifier described above. Depending on the actual situation, other available methods can also be used to generate the target device identifier.

[0105] After regenerating the target device identifier, the client may also report the new target device identifier to the server through methods such as daily active user logs.

[0106] In this embodiment, the client proactively determines with the server whether a target device identifier is duplicated. After proactively confirming the duplicate, a new target device identifier is regenerated. This allows for detection of existing clients that have already generated target device identifiers, identifying and removing duplicate device identifiers from the existing client pool, thereby helping to ensure the uniqueness of the target device identifier and improving the efficiency and effectiveness of device identifier deduplication.

[0107] As mentioned above, there are multiple ways to obtain the preset duplicate device identification library. An exemplary method is provided below.

[0108] In an optional embodiment, if Figure 7 As shown, the preset duplicate device identification library is obtained according to the following operations: S700: Acquire multiple daily active user logs, each of which corresponds to multiple different types of device codes to be checked for duplicates and a device identifier to be checked for duplicates; S702, determining a plurality of re-code-identifier pairs to be checked based on the plurality of daily active user logs, wherein each re-code-identifier pair to be checked is different; S704: Determine multiple duplicate device identifiers based on the multiple duplicate code-identification pairs to be checked and the corresponding multiple daily active user logs; wherein each duplicate device identifier corresponds to multiple different duplicate code-identification pairs to be checked, and the multiple duplicate device identifiers in the multiple different duplicate code-identification pairs to be checked have the same encoding type; S706: Acquire the preset duplicate device code library according to the multiple duplicate device identifiers.

[0109] In some embodiments, daily active user logs may include user login logs, operation logs, etc. After obtaining daily active user logs, the obtained log data can also be pre-processed, such as data cleaning, noise removal, and formatting. In other embodiments, device performance logs and network connection logs can also be integrated to obtain more comprehensive and complete device code and device identification data.

[0110] In some embodiments, the device codes to be checked for duplicates of different coding types may include device software or hardware codes such as DrmID, IMEI, MAC, Android ID, and UUID. Each duplicate code-identification pair to be checked may include a device code to be checked for duplicates and a device identification to be checked for duplicates. The device codes to be checked for duplicates in multiple duplicate code-identification pairs generated by a daily active user log may all have different coding types.

[0111] In some embodiments, for multiple duplicate code / identification pairs containing the same device identifier to be checked for duplicates, where the device identifiers to be checked for duplicates have the same encoding type, a determination can be made based on the information in the daily active user logs corresponding to each duplicate code / identification pair to determine whether these daily active user logs are from different real devices. If they are from different real devices, the device identifiers can be determined to be duplicates.

[0112] For example, determining multiple duplicate device identifiers based on the multiple to-be-checked duplicate code-identification pairs and the corresponding multiple daily active user logs may include: Determine, from the plurality of duplicate code-identification pairs to be checked, a first duplicate code-identification pair to be checked and a second duplicate code-identification pair to be checked, which have the same duplicate device identifier to be checked and the same coding type of the duplicate device code to be checked; Determining a plurality of first behavior information feature vectors (such as active time information, active geographic location information, etc.) and a plurality of first client information feature vectors (such as client hardware information, client software information, etc.) based on the daily active user log corresponding to the first to-be-checked recode-identification pair; and Determine a plurality of second behavior information feature vectors and a plurality of second client information feature vectors based on the daily active user log corresponding to the second to-be-checked recode-identification pair; determining a plurality of behavior information conflict vectors based on the plurality of first behavior information feature vectors and the plurality of second behavior information feature vectors; and determining a plurality of client information conflict vectors based on the plurality of first client information feature vectors and the plurality of second client information feature vectors; Determining a conflict score between the first to-be-checked re-encoding identifier pair and the second to-be-checked re-encoding identifier pair based on the multiple behavior information conflict vectors, the multiple client information conflict vectors, and a pre-configured conflict vector weight array; When the conflict score is not lower than a preset conflict threshold, it is determined that the device identifiers to be checked for duplicates in the first duplicate code identifier pair to be checked and the second duplicate code identifier pair to be checked are duplicate device identifiers.

[0113] In this embodiment, multiple duplicate device identifiers are identified based on daily active user logs to construct a duplicate device identifier library. By extracting and processing data from daily active user logs, duplicate device identifiers can be identified based on actual usage, improving both accuracy and practicality. Furthermore, systematic data processing and analysis using the duplicate device identifier library enhances the quality and efficiency of device identifier management, contributing to more accurate data statistics and user services.

[0114] As mentioned above, upon receiving the target device code, the client generates a target device identifier based on the target device code. In actual use, the client may be unable to receive the target device code due to network fluctuations or other reasons. In this case, the client can also generate the target device code through other available methods. The following provides an exemplary generation method.

[0115] In an optional embodiment, the method further includes: generating the target device identifier according to a plurality of the device codes in accordance with a preset identifier generation rule when the target device code is not received.

[0116] In some embodiments, the preset identifier generation rule may generate a target device identifier based on multiple device codes using a specific algorithm (such as a hash algorithm). The preset identifier generation rule may also include using a machine learning model to learn characteristic patterns of the client (such as hardware information, software information, user behavior, etc.), and combining the learned characteristic patterns with multiple device codes to generate the target device identifier.

[0117] In other embodiments, the preset identifier generation rule may further include generating a target device identifier based on multiple device codes and timestamps or random numbers.

[0118] After generating the target device identifier, the client may also report the generated target device identifier to the server through methods such as daily active user logs.

[0119] In this embodiment, a target device identifier is generated based on multiple device codes. This can increase the information content in the target device identifier when the repeatability of the device code is not determined, thereby helping to reduce the probability of repeating the target device identifier and improving the effect of device identifier deduplication.

[0120] In order to make this application easier to understand, the following Figures 9 to 12 An exemplary application is provided, wherein: S11: The server obtains multiple daily active user logs from all active clients. S12: The server performs real device detection for situations where one device ID (device code) corresponds to two or more Buvids (device identifiers), or one Buvid corresponds to two or more device IDs of the same type, in multiple daily active user logs. S13, the server detects and determines multiple duplicate device IDs (i.e., duplicate device codes) and duplicate Buvids (i.e., duplicate device identifiers), and performs data filling to obtain a duplicate device ID library (i.e., a preset duplicate device code library) and a duplicate Buvid library (i.e., a preset duplicate device identifier library); S14, a certain video software B (i.e., the target application) is newly installed on client O; S15, client O receives the duplicate device code file sent by the server, and determines that the device's DrmID, IMEI, MAC, Android ID, UUID, etc. are not device IDs with a high probability of duplication based on the duplicate device code file and multiple highly duplicated device codes in the video software B package; S16, client O initiates a code query request to the server based on the device ID, such as DrmID, IMEI, MAC, Android ID, and UUID; S17, the server queries the duplicate device ID library and finds that the IMEI, MAC, and Android ID (i.e., the target device code) of client O are not duplicated with the codes in the duplicate device ID library, and returns the query result to client O; S18, client O generates client O's Buvid: 000001 (i.e., target device identifier) through a hash algorithm based on IMEI, MAC, and Android ID; S19, one week later, client O queries the server based on Buvid: 000001 generated in S18 whether duplication occurs; S20, the server queries and finds that the Buvid: 000001 of client O has been duplicated, and informs client O; S21, client O regenerates a new Buvid: 000002.

[0121] Example 2 Figure 13 The block diagram of the device identification generation device according to the second embodiment of the present application is schematically shown. The device can be divided into one or more program modules, one or more program modules are stored in a storage medium and executed by one or more processors to complete the embodiment of the present application. The program module referred to in the embodiment of the present application refers to a series of computer program instruction segments that can perform specific functions. The following description will specifically introduce the functions of each program module in this embodiment. Figure 13 As shown, the apparatus 1000 may include: an acquisition module 1100, a first generation module 1200, a sending module 1300, and a second generation module 1400, wherein: An acquisition module 1100 is configured to acquire, in response to the target application being installed, a plurality of device codes from the client locally, wherein the plurality of device codes are of different encoding types; A first generating module 1200 is configured to generate a code query request according to the multiple device codes; A sending module 1300 is configured to send the code query request to a server, so that the server determines and returns a target device code from the multiple device codes based on a preset duplicate device code library; wherein the preset duplicate device code library includes multiple duplicate device codes, and the target device code is a code that does not belong to the multiple duplicate device codes; The second generating module 1400 is configured to generate a target device identifier for identifying the client according to the target device code when the target device code is received.

[0122] As an optional embodiment, the first generating module 1200 is further configured to: Receiving a repeated device code file sent by the server; wherein the repeated device code file includes a plurality of highly repeated device codes, wherein the highly repeated device codes are repeated device codes having a number of repetitions exceeding a predetermined threshold; Determining one or more first device codes from the multiple device codes according to the repeated device code file, wherein the first device codes are all different from the multiple highly repeated device codes; The code query request is generated according to one or more of the first device codes.

[0123] As an optional embodiment, the first generating module 1200 is further configured to: Acquire a plurality of highly repeated device codes from the installation package of the target application, wherein the highly repeated device codes are repeated device codes having a number of repetitions exceeding a predetermined threshold; Determining one or more second device codes from the plurality of device codes according to the repeated device code file, wherein the second device codes are all different from the plurality of highly repeated device codes; The code query request is generated according to one or more second device codes.

[0124] As an optional embodiment, the apparatus 1000 further includes a repeated device code library acquisition module, configured to: Acquire multiple daily active user logs, each of which corresponds to multiple codes of devices to be checked for duplicates of different coding types and an identifier of a device to be checked for duplicates; determining, based on the plurality of daily active user logs, a plurality of different recode-identification pairs to be checked; Determining a plurality of duplicate device codes based on the plurality of duplicate code-identification pairs to be checked and the corresponding plurality of daily active user logs, each duplicate device code corresponding to a plurality of different duplicate code-identification pairs to be checked; According to the plurality of repeated device codes, the preset repeated device code library is obtained.

[0125] As an optional embodiment, the apparatus 1000 further includes a target device identification updating module: Generate an identification query request based on the target device identification at a preset time interval; Sending the identification query request to the server, so that the server returns a duplicate checking result according to a preset duplicate device identification library; If the duplicate checking result is a duplicate, the target device identifier is regenerated.

[0126] As an optional embodiment, the apparatus 1000 further includes a duplicate device identification library acquisition module, configured to: Acquire multiple daily active user logs, each of which corresponds to multiple different types of to-be-checked duplicate device codes and a to-be-checked duplicate device identifier; Determining, based on the plurality of daily active user logs, a plurality of recode-identification pairs to be checked, each of the recode-identification pairs to be checked being different; Determine multiple duplicate device identifiers based on the multiple duplicate code-identification pairs to be checked and the corresponding multiple daily active user logs; wherein each duplicate device identifier corresponds to multiple different duplicate code-identification pairs to be checked, and the multiple duplicate device identifiers to be checked in the multiple different duplicate code-identification pairs to be checked have the same encoding type; According to the multiple duplicate device identifiers, the preset duplicate device code library is obtained.

[0127] As an optional embodiment, the apparatus 1000 further includes a third generating module, configured to: In the case that the target device code is not received, the target device identifier is generated according to a plurality of the device codes in accordance with a preset identifier generation rule.

[0128] Example 3 Figure 14 The following schematically shows a hardware architecture diagram of a computer device 10000 suitable for implementing a device identification generation method according to the third embodiment of the present application. In some embodiments, the computer device 10000 may be a terminal device such as a smart phone, a wearable device, a tablet computer, a personal computer, a vehicle-mounted terminal, a game console, a virtual device, a workbench, a digital assistant, a set-top box, a robot, etc. In other embodiments, the computer device 10000 may be a rack server, a blade server, a tower server, or a cabinet server (including an independent server or a server cluster composed of multiple servers), etc. Figure 14 As shown, the computer device 10000 includes but is not limited to: a memory 10010, a processor 10020, and a network interface 10030 that can communicate with each other via a system bus. Memory 10010 includes at least one type of computer-readable storage medium, including flash memory, a hard disk, a multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic storage, a magnetic disk, an optical disk, and the like. In some embodiments, memory 10010 may be an internal storage module of computer device 10000, such as a hard disk or memory of computer device 10000. In other embodiments, memory 10010 may also be an external storage device of computer device 10000, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, a flash memory card, and the like equipped on computer device 10000. Of course, memory 10010 may also include both internal storage modules and external storage devices of computer device 10000. In this embodiment, the memory 10010 is generally used to store the operating system and various application software installed on the computer device 10000, such as the program code of the device identification generation method, etc. In addition, the memory 10010 can also be used to temporarily store various data that has been output or will be output.

[0129] In some embodiments, processor 10020 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other chips. Processor 10020 is typically used to control the overall operation of computer device 10000, such as performing control and processing related to data exchange or communication with computer device 10000. In this embodiment, processor 10020 is used to execute program code stored in memory 10010 or process data.

[0130] Network interface 10030 may include a wireless network interface or a wired network interface. Network interface 10030 is typically used to establish a communication link between computer device 10000 and other computer devices. For example, network interface 10030 is used to connect computer device 10000 to an external terminal via a network, establishing a data transmission channel and a communication link between computer device 10000 and the external terminal. The network may be a wireless or wired network such as an intranet, the Internet, the Global System of Mobile Communications (GSM), Wideband Code Division Multiple Access (WCDMA), a 4G network, a 5G network, Bluetooth, or Wi-Fi.

[0131] It should be pointed out that Figure 14 Only a computer device having components 10010 - 10030 is shown, but it should be understood that implementing all of the shown components is not a requirement, and more or fewer components may alternatively be implemented.

[0132] In this embodiment, the device identification generation method stored in the memory 10010 can also be divided into one or more program modules and executed by one or more processors (such as processor 10020) to complete the embodiment of the present application.

[0133] Example 4 An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the steps of the device identification generation method in the embodiment are implemented.

[0134] In this embodiment, computer-readable storage media include flash memory, hard disks, multimedia cards, card-type memories (e.g., SD or DX memories), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic storage, magnetic disks, optical disks, and the like. In some embodiments, the computer-readable storage medium may be an internal storage unit of a computer device, such as the computer device's hard disk or memory. In other embodiments, the computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, a flash memory card, and the like. Of course, the computer-readable storage medium may also include both the internal storage unit and external storage devices of the computer device. In this embodiment, the computer-readable storage medium is typically used to store the operating system and various application software installed on the computer device, such as the program code of the device identification generation method described in the embodiment. Furthermore, the computer-readable storage medium may also be used to temporarily store various types of data that has been output or is about to be output.

[0135] Example 5 An embodiment of the present application further provides a computer program product, including a computer program, which implements the method in the above embodiment when executed by a processor.

[0136] Obviously, those skilled in the art should understand that the modules or steps of the above-mentioned embodiments of the present application can be implemented using general-purpose computer devices. They can be concentrated on a single computer device or distributed on a network composed of multiple computer devices. Alternatively, they can be implemented using program codes executable by the computer device, so that they can be stored in a storage device and executed by the computer device. In some cases, the steps shown or described can be performed in a different order than herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the embodiments of the present application are not limited to any specific combination of hardware and software.

[0137] It should be noted that the above are only preferred embodiments of the present application and do not limit the scope of patent protection of the present application. Any equivalent structure or equivalent process transformation made using the contents of the description and drawings of this application, or directly or indirectly applied in other related technical fields, are also included in the scope of patent protection of the present application.

Claims

1. A method for generating a device identification, characterized in that: For a client, the method includes: In response to installing the target application, obtaining multiple device codes from the client locally, wherein the multiple device codes are of different encoding types; generating a code query request according to the plurality of device codes; Sending the code query request to a server, so that the server determines and returns a target device code from the multiple device codes according to a preset repeated device code library; wherein the preset repeated device code library includes multiple repeated device codes, and the target device code is a code that does not belong to the multiple repeated device codes; When the target device code is received, a target device identifier for identifying the client is generated according to the target device code.

2. The method according to claim 1, characterized in that Generating a code query request according to the multiple device codes includes: Receiving a repeated device code file sent by the server; wherein the repeated device code file includes a plurality of highly repeated device codes, wherein the highly repeated device codes are repeated device codes having a number of repetitions exceeding a predetermined threshold; Determining one or more first device codes from the multiple device codes according to the repeated device code file, wherein the first device codes are all different from the multiple highly repeated device codes; The code query request is generated according to one or more of the first device codes.

3. The method according to claim 1, characterized in that Generating a code query request according to the multiple device codes includes: Acquire a plurality of highly repeated device codes from the installation package of the target application, wherein the highly repeated device codes are repeated device codes having a number of repetitions exceeding a predetermined threshold; Determining one or more second device codes from the plurality of device codes according to the repeated device code file, wherein the second device codes are all different from the plurality of highly repeated device codes; The code query request is generated according to one or more second device codes.

4. The method according to claim 1, wherein The preset repetitive device code library is obtained according to the following operations: Acquire multiple daily active user logs, each of which corresponds to multiple codes of devices to be checked for duplicates of different coding types and an identifier of a device to be checked for duplicates; determining, based on the plurality of daily active user logs, a plurality of different recode-identification pairs to be checked; Determining a plurality of duplicate device codes based on the plurality of duplicate code-identification pairs to be checked and the corresponding plurality of daily active user logs, each duplicate device code corresponding to a plurality of different duplicate code-identification pairs to be checked; According to the plurality of repeated device codes, the preset repeated device code library is obtained.

5. The method according to claim 1, wherein The method further comprises: At a preset time interval, generating an identification query request according to the target device identification; Sending the identification query request to the server, so that the server returns a duplicate checking result according to a preset duplicate device identification library; If the duplicate checking result is a duplicate, the target device identifier is regenerated.

6. The method according to claim 5, characterized in that The preset duplicate device identification library is obtained according to the following operations: Acquire multiple daily active user logs, each of which corresponds to multiple different types of to-be-checked duplicate device codes and a to-be-checked duplicate device identifier; Determining, based on the plurality of daily active user logs, a plurality of recode-identification pairs to be checked, each of the recode-identification pairs to be checked being different; Determine multiple duplicate device identifiers based on the multiple duplicate code-identification pairs to be checked and the corresponding multiple daily active user logs; wherein each duplicate device identifier corresponds to multiple different duplicate code-identification pairs to be checked, and the multiple duplicate device identifiers to be checked in the multiple different duplicate code-identification pairs to be checked have the same encoding type; According to the multiple duplicate device identifiers, the preset duplicate device code library is obtained.

7. The method according to claim 1, characterized in that The method further comprises: In the case that the target device code is not received, the target device identifier is generated according to a plurality of the device codes in accordance with a preset identifier generation rule.

8. A device identification generating apparatus, characterized in that: The device comprises: an acquisition module, configured to acquire, in response to installing the target application, a plurality of device codes from the client locally, wherein the encoding types of the plurality of device codes are all different; A first generating module, configured to generate a code query request according to the multiple device codes; a sending module, configured to send the code query request to a server, so that the server determines and returns a target device code from the multiple device codes according to a preset duplicate device code library; wherein the preset duplicate device code library includes multiple duplicate device codes, and the target device code is a code that does not belong to the multiple duplicate device codes; The second generating module is configured to generate a target device identifier for identifying the client according to the target device code when the target device code is received.

9. A computer device, characterized in that: include: at least one processor; and a memory communicatively coupled 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.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, which, when executed by a processor, implement the method according to any one of claims 1 to 7.

11. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images