WO2021115197A1

WO2021115197A1 - Method for generating device identifier, electronic device, and computer readable medium

Info

Publication number: WO2021115197A1
Application number: PCT/CN2020/133777
Authority: WO
Inventors: 崔英林
Original assignee: 上海掌门科技有限公司
Priority date: 2019-12-10
Filing date: 2020-12-04
Publication date: 2021-06-17
Also published as: CN111046371A

Abstract

A method for generating a device identifier, an electronic device, and a computer readable medium. The method comprises: receiving feature information of at least one target application submitted by a client (201), wherein the at least one target application is a non-preinstalled application installed in the client; and if a device identifier having a degree of matching with the feature information of the at least one target application greater than or equal to a preset threshold does not exist in a device identifier library, generating a device identifier of the client on the basis of the feature information of the at least one target application (202). By means of the method, a unique identifier of a mobile device can be generated by using the feature information of an application without a permission restriction in the case that uniqueness hardware information of the mobile device of the client is shielded, thereby solving the uniqueness problem of the mobile device.

Description

Method for generating device identification, electronic device and computer readable medium

Technical field

This application relates to the field of computer technology, in particular to a method for generating a device identifier, an electronic device and a computer-readable medium.

Background technique

With the rapid development of the mobile Internet, mobile applications have also grown rapidly. Generally, mobile applications resolve the uniqueness of mobile devices by obtaining hardware information of mobile devices such as mobile phones (for example, IMEI (International Mobile Equipment Identity), UUID (Universally Unique Identifier), etc.) problem.

However, with the improvement of people's security awareness and attention to user privacy, the system authority of mobile devices has gradually tightened, and the hardware information that can uniquely identify the mobile device has been/will be blocked by the system, thus invalidating the traditional methods.

Summary of the invention

The embodiment of the present application proposes a method, an electronic device, and a computer-readable medium for generating a device identification.

In the first aspect, some embodiments of the present application provide a method for generating a device identification, applied to a server, and the method includes: receiving feature information of at least one target application submitted by the user, where at least one target application is A non-pre-installed application installed on the user end; if there is no device identification in the device identification library whose matching degree with the feature information of at least one target application is greater than or equal to the preset threshold, the user end is generated based on the feature information of the at least one target application Equipment Identity.

In the second aspect, some embodiments of the present application provide a method for generating a device identification, which is applied to a user end, and the method includes: acquiring characteristic information of at least one target application, wherein at least one target application is installed on the user end Non-pre-installed applications in, report the feature information of at least one target application to the server so that the server does not have a device identification whose matching degree with the feature information of at least one target application is greater than or equal to the preset threshold in the device identification library , Generating the device identification of the user terminal based on the characteristic information of the at least one target application.

In the third aspect, some embodiments of the present application provide an electronic device, including: one or more processors; a storage device, on which one or more programs are stored, when one or more programs are used by one or more The processor executes, so that one or more processors implement the method described in any one of the first aspect or the second aspect.

In the fourth aspect, some embodiments of the present application provide a computer-readable medium on which a computer program is stored, and when the computer program is executed by a processor, the method as described in any one of the first aspect or the second aspect is implemented .

The method, electronic device, and computer-readable medium for generating device identification provided by the above-mentioned embodiments of the present application receive the feature information of at least one non-preinstalled application submitted by the user terminal. If the device identification library does not exist with at least one target The device identification whose matching degree of the characteristic information of the application is greater than or equal to the preset threshold is to generate the device identification of the user terminal based on the characteristic information of at least one target application, so that the unique hardware information of the mobile device of the user terminal can be used The application feature information without permission restriction generates the unique identification of the mobile device, thereby solving the uniqueness problem of the mobile device.

Description of the drawings

By reading the detailed description of the non-limiting embodiments with reference to the following drawings, other features, purposes and advantages of the present application will become more apparent:

Fig. 1 is an exemplary system architecture diagram to which some embodiments of the present application can be applied;

Fig. 2 is a flowchart of an embodiment of a method for generating a device identification according to the present application;

3A and 3B are schematic diagrams of an application scenario of the method for generating device identification according to the present application;

Fig. 4 is a flowchart of another embodiment of a method for generating a device identification according to the present application;

Fig. 5 is a schematic structural diagram of an electronic device suitable for implementing some embodiments of the present application.

Detailed ways

The application will be further described in detail below with reference to the drawings and embodiments. It can be understood that the specific embodiments described here are only used to explain the related invention, but not to limit the invention. In addition, it should be noted that, for ease of description, only the parts related to the relevant invention are shown in the drawings.

It should be noted that the embodiments in the application and the features in the embodiments can be combined with each other if there is no conflict. Hereinafter, the application will be described in detail with reference to the drawings and in conjunction with the embodiments.

FIG. 1 shows an exemplary system architecture 100 to which an embodiment of the method for generating device identification or the method for returning resources of the present application can be applied.

As shown in FIG. 1, the system architecture 100 may include

terminals

101 and 102, a network 103, and a server 104. The network 103 is used to provide a medium for communication links between the

terminals

101 and 102 and the server 104. The network 103 may include various connection types, such as a wireless local area network, a mobile network, and so on.

The user can use the

terminals

101 and 102 to interact with the server 104 through the network 103 to receive or send messages and so on. Various communication client applications, such as instant messaging tools, social applications, browser applications, shopping applications, search applications, email clients, etc., may be installed on the

terminals

101 and 102.

The

terminals

101 and 102 may be hardware or software. When the

terminals

101 and 102 are hardware, they may be various mobile devices capable of installing client applications, including but not limited to smart phones, tablet computers, personal digital assistants (Personal Digital Assistant, PDA), and so on. When the

terminals

101 and 102 are software, they can be installed in the mobile devices listed above. It can be implemented as multiple software or software modules (for example, to provide distributed services), or as a single software or software module. There is no specific limitation here.

The server 104 may be a server that provides various services, for example, a background server that provides support for client applications running on the

terminals

101 and 102. The background server may process the received data such as feature information of non-preinstalled applications to generate unique device identifications of the

terminals

101 and 102.

It should be noted that the server 104 may be hardware or software. When the server 104 is hardware, it can be implemented as a distributed server cluster composed of multiple servers, or as a single server. When the server 104 is software, it can be implemented as multiple software or software modules (for example, software or software modules used to provide distributed services), or can be implemented as a single software or software module. There is no specific limitation here.

It should be noted that the method for generating a device identifier provided in the embodiment of the present application may be executed by the

terminals

101 and 102, and may also be executed by the server 104.

It should be understood that the numbers of terminals, networks, and servers in FIG. 1 are merely illustrative. According to implementation needs, there can be any suitable number of terminals, networks, and servers.

Continuing to refer to FIG. 2, a process 200 of an embodiment of the method for generating a device identification according to the present application is shown. The method for generating device identification can be applied to the server, and it can include the following steps 201 to 202:

Step 201: Receive feature information of at least one target application submitted by a user terminal.

In this embodiment, the executor of the method for generating device identification (for example, the server 104 shown in FIG. 1) can receive at least one submitted by the user (for example, the

terminals

101 and 102 shown in FIG. 1). Characteristic information of the target application. For example, the above-mentioned execution subject may receive the characteristic information of a first number of second applications (ie, target applications) submitted by the first application running on the above-mentioned user terminal. Wherein, the aforementioned at least one target application may be a non-preinstalled application installed in the user terminal. In addition, the at least one target application may include a first application (that is, the first application is also a non-preinstalled application). Here, pre-installed applications can refer to the client applications that come with mobile devices such as mobile phones when they leave the factory. The characteristic information of the application may refer to information that can reflect the relationship between the application and the mobile device, which may include but is not limited to at least one of the following information: installation time, upgrade time, application version and other information. The first number can be one, two, three, etc.

In some optional implementation manners of this embodiment, the characteristic information of the target application may include an installation time of the target application with a preset time accuracy. For example, the installation time of the target application is accurate to milliseconds, microseconds, etc.

Generally speaking, for the same application, there is a very low probability that different clients have the same installation time. In this implementation manner, by making the installation time more precise, the problem of the same installation time for different client terminals can be effectively avoided.

In some optional implementation manners of this embodiment, the feature information of the at least one target application described above may include the feature information of at least two target applications. This implementation can avoid the problem of two or more device identifications generated by the same user terminal due to the application being uninstalled and then installed.

In some optional implementation manners of this embodiment, the characteristic information of the target application may include the installation time and version information of the target application.

Since the target application may be automatically upgraded by the system or manually upgraded by the user, there may be a situation where the installation time of the same application installed on the same user terminal obtained twice before and after is different, and this implementation method obtains the installation time of at least two second applications , And increase the version dimension, so as to avoid the problem of two or more device identifications on the same user terminal due to application upgrades.

In some optional implementation manners of this embodiment, the aforementioned at least one target application may include all non-preinstalled applications installed in the user terminal.

In some optional implementation manners of this embodiment, the aforementioned at least one target application may include multiple preset non-preinstalled applications. For example, several or more than a dozen non-preinstalled applications whose mobile phone installation rate is greater than or equal to a preset value.

As the configuration and performance of mobile devices on the user side are getting higher and higher, the number of applications installed on the user side is also increasing. In this implementation manner, by acquiring characteristic information of a specific application, it is possible to avoid an increase in response time due to large-scale data collection and data reporting, thereby ensuring that the performance of the mobile device on the user side is not affected.

It should be understood that when the at least one target application mentioned above is a specific application list, there may be situations in which the user terminal only installs some of the applications in the application list. At this time, for applications that are not installed on the client side, their characteristic information can be set to a fixed value (for example, the installation time is set to 0) (or, it is also possible to receive only the characteristic information of applications installed on the client side).

Step 202: If there is no device identification in the device identification library whose matching degree with the feature information of the at least one target application is greater than or equal to a preset threshold, a device identification of the user terminal is generated based on the feature information of the at least one target application.

In this embodiment, the executor of the method for generating device identification (for example, the server 104 shown in FIG. 1) can perform the feature information associated with the device identification in the device identification library with the feature information received in step 201. Compare. Wherein, the device identification library may be a collection of device identifications stored locally or remotely (a server different from the execution subject) by the above-mentioned execution subject.

If there is no device identity in the device identity library whose matching degree with the feature information of the at least one target application is greater than or equal to the preset threshold (that is, the device identity of the user terminal does not exist in the device identity library), it may be based on step 201 The received feature information generates the device identification of the user end.

For example, if there is no device identification associated with at least the second number of the second application feature information in the feature information received in step 201 in the device identification library, the device identification of the user terminal may be generated based on the feature information received in step 201 . Here, the second number may be less than or equal to the first number. For example, the first number is three, and the second number can be two. Wherein, the ratio of the second quantity to the first quantity may be greater than or equal to a preset ratio, for example, 50%, 70%, and so on.

As an example, the feature information received in step 201 is {application A, installation time A; application B, installation time B; application C, installation time C}, and there is no usage feature information {application A, Installation time A; application B, installation time B; ...} or feature information {application A, installation time A; application C, installation time C; ...} or feature information {application B, installation time B; application C, installation Time C; ...} the generated device identification, then the feature information {application A, installation time A; application B, installation time B; application C, installation time C} can be used to generate the device identification of the client.

It should be noted that, although the foregoing example describes that the feature information associated with the device identification is compared with the feature information of the at least one target application to determine the degree of matching between the two, the application is not limited to this. Those skilled in the art can make settings according to actual application scenarios. For example, the degree of matching between the feature information associated with the device identifier and the feature information of the at least one target application can also be calculated by calculating the similarity between the two.

In some optional implementations of this embodiment, if there is a device identity in the device identity library whose matching degree with the feature information of the at least one target application is greater than or equal to a preset threshold (that is, the device identity library exists The device identification of the user end) to determine whether the feature information used to generate the device identification is the same as the feature information of the at least one target application; if they are different, the device identification of the user end can be associated with the feature information of the at least one target application. (That is, the associated feature information of the device identifier of the user end is updated to the feature information of the at least one target application mentioned above). On the contrary, if they are the same, there is no need to re-associate them.

For example, if there is a device ID in the device ID library that matches the feature information of at least the second number of the second application in the feature information received in step 201, the feature information used to generate the associated device ID is determined (or is Whether the feature information associated with the device identification of the user end is the same as the feature information received in step 201; if different, the device identification of the user end is associated with the feature information received in step 201.

As an example, the feature information received in step 201 is {application A, installation time A; application B, installation time B; application C, installation time C}, and the device identification D in the local device identification library of the server is based on the feature information { Application A, installation time A; Application B, installation time B; Application C, installation time C'} generated. The feature information for generating the device ID D is the same as the feature information received in step 201. The installation time of the two applications is the same, that is, the device ID D is the device ID of the user terminal. At this time, the device identification D can be associated with feature information {application A, installation time A; application B, installation time B; application C, installation time C}, instead of being associated with feature information {application A, installation time A; Application B, installation time B; Application C, installation time C'} are associated. Here, the installation time C is different from the installation time C'.

In some optional implementation manners of this embodiment, the method for generating a device identification may further include: receiving brand information submitted by a user terminal.

Corresponding to this implementation manner, step 202 may specifically include: if there is no device identification in the device identification library corresponding to the above-mentioned brand information that has a matching degree with the feature information of at least one target application greater than or equal to a preset threshold, the device identification based on step 201 is received The feature information of, generates the device identification of the user end, and adds the generated device identification of the user end to the device identification library corresponding to the brand information.

Due to the large number of mobile device manufacturers, different mobile device manufacturers can pre-install different client applications when they leave the factory. Therefore, it is necessary to set different specific application lists for different device manufacturers. For example, assuming that the mobile device of manufacturer A is pre-installed with applications a, b, and c, and the mobile device of manufacturer B is pre-installed with applications b, c, and d, the second application list for the mobile device of manufacturer A can be {application d, application e. Application f}, the second application list for the mobile device of manufacturer B may be {application a, application e, application f}. In this implementation manner, the mobile devices of different manufacturers can be more accurately identified through differentiated processing for different mobile device manufacturers.

Corresponding to the foregoing implementation manner, the method for generating a device identification may further include: if there is a device whose matching degree with the feature information of the at least one target application is greater than or equal to a preset threshold in the device identification library corresponding to the above-mentioned brand information Identification, (that is, the device identification of the user end exists in the device identification library), it is determined whether the feature information used to generate the associated device identification is the same as the feature information received in step 201; if they are different, the device identification of the user end can be The identification is associated with the characteristic information received in step 201.

Continue to refer to FIG. 3A and FIG. 3B, which show a schematic diagram of an application scenario of the method for generating a device identifier according to this embodiment. In this application scenario, first, as shown in FIG. 3A, three non-preinstalled applications are installed on the mobile phone 301, namely application A, application B, and application C. When the user clicks on the icon of the application A to start the application A, the application A pulls the list of applications installed in the mobile phone 301 and filters out the system pre-installed applications, thereby obtaining an application list containing the application A, the application B, and the application C. Application A reads the installation time (accurate to milliseconds) of application A, application B, and application C as the characteristic information 303 of the three applications and reports it to the server 302, as shown in FIG. 3B. After the server 302 receives the feature information 303, it compares the feature information 303 with the local device identification library of the server 302, and determines that there is no device identification associated with the installation time of two of the three applications in the device identification library. (That is, there is no device ID of the mobile phone 301), so the device ID of the mobile phone 301 is generated based on the feature information 303.

The method for generating device identification provided by the embodiment of the present application receives the feature information of at least one non-preinstalled application submitted by the user terminal. If the feature information of the at least one target application does not exist in the device identification library, the matching degree with the feature information of the at least one target application is greater than or The device ID equal to the preset threshold is used to generate the device ID of the user terminal based on the characteristic information of at least one target application, so that when the unique hardware information of the mobile device of the user terminal is shielded, the mobile device can be generated using the application characteristic information without permission restriction. The unique identification of the device, so as to solve the uniqueness problem of the mobile device.

Continuing to refer to FIG. 4, a process 400 of another embodiment of the method for generating a device identification according to the present application is shown. The method for generating a device identifier can be applied to a user terminal (for example, the

terminals

101 and 102 shown in FIG. 1), and it can include the following steps 401 to 402:

Step 401: Acquire feature information of at least one target application.

In this embodiment, the execution body of the method for generating device identification (for example, the first application running in the

terminals

101 and 102 shown in FIG. 1) can obtain at least one (for example, the first number) of targets. Feature information of the application (for example, the second application). Wherein, the aforementioned at least one target application may be a non-preinstalled application installed in the user terminal. The aforementioned at least one target application may include the first application (that is, the first application is also a non-preinstalled application). Here, pre-installed applications can refer to the client applications that come with mobile devices such as mobile phones when they leave the factory. The characteristic information of the application may refer to information that can reflect the relationship between the application and the mobile device, which may include but is not limited to at least one of the following information: installation time, upgrade time, application version and other information. The first number can be one, two, three, etc.

In some optional implementations of this embodiment, step 401 may specifically include: obtaining a list of applications installed in the mobile device; selecting at least one target application from the foregoing application list; and reading feature information of the foregoing at least one target application.

Optionally, selecting at least one target from the foregoing application list may specifically include: filtering the foregoing application list, excluding pre-installed applications in the system, and obtaining at least one target application.

Optionally, selecting at least one target from the above-mentioned application list may specifically include: filtering the above-mentioned application list to exclude pre-installed applications in the system; and selecting at least one target whose installation amount is greater than or equal to a preset value from the filtered application list Target application.

Optionally, selecting at least one target from the aforementioned application list may specifically include: acquiring brand information of the user terminal; and selecting at least one target application corresponding to the brand information from the aforementioned application list.

Step 402: Report the feature information of at least one target application to the server.

In this embodiment, the executor of the method for generating device identification (for example, the first application running in the

terminals

101 and 102 shown in FIG. 1) can report the feature information obtained in step 401 to the server (for example, , The server 104 shown in Figure 1).

Among them, the server can be configured as:

When there is no device identity in the device identity library whose matching degree with the feature information of the at least one target application is greater than or equal to the preset threshold (that is, the device identity of the user terminal does not exist in the device identity library), based on the received in step 401 The feature information generates the device identification of the user end; and

When there is a device identity in the device identity library whose matching degree with the feature information of the at least one target application is greater than or equal to a preset threshold (that is, the device identity of the user end exists in the device identity library), the device identity of the user end and The feature information received in step 401 is associated.

The method for generating device identification provided by the embodiment of the present application obtains the characteristic information of at least one non-preinstalled application installed in the user terminal and reports it to the server terminal, so that the server terminal does not exist in the device identification library with the at least one of the above. When the matching degree of the feature information of the target application is greater than or equal to the device identification of the preset threshold, the device identification of the user is generated based on the feature information of the at least one non-preinstalled application, so that the unique hardware information of the mobile device on the user can be blocked In the case of, the unique identification of the mobile device is generated by using the application feature information without permission restriction, thereby solving the uniqueness problem of the mobile device.

Next, refer to FIG. 5, which shows a schematic structural diagram of an electronic device (for example, the terminal 101, 102 or the server 104 shown in FIG. 1) 500 suitable for implementing some embodiments of the present application. The electronic device 500 shown in FIG. 5 is only an example, and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

As shown in FIG. 5, the electronic device 500 may include a processing device (such as a central processing unit, a graphics processor, etc.) 501, which can be loaded into a random access device according to a program stored in a read-only memory (ROM) 502 or from a storage device 508. The program in the memory (RAM) 503 executes various appropriate actions and processing. In the RAM 503, various programs and data required for the operation of the electronic device 500 are also stored. The processing device 501, the ROM 502, and the RAM 503 are connected to each other through a bus 504. An input/output (I/O) interface 505 is also connected to the bus 504.

Generally, the following devices can be connected to the I/O interface 505: including input devices 506 such as touch screens, keys, etc.; output devices 507 including liquid crystal displays (LCD), speakers, vibrators, etc.; and storage devices 508 such as memory cards. ; And communication device 509. The communication device 509 may allow the electronic device 500 to perform wireless or wired communication with other devices to exchange data. Although FIG. 5 shows an electronic device 500 having various devices, it should be understood that it is not required to implement or have all of the illustrated devices. It may be implemented alternatively or provided with more or fewer devices. Each block shown in FIG. 5 may represent one device, or may represent multiple devices as needed.

In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from the network through the communication device 509, or installed from the storage device 508, or installed from the ROM 502. When the computer program is executed by the processing device 501, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed. It should be noted that the computer-readable medium described in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or a combination of any of the above. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable removable Programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above. In the embodiments of the present disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program, and the program may be used by or in combination with an instruction execution system, apparatus, or device. In the embodiments of the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as a part of a carrier wave, and a computer-readable program code is carried therein. This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. The computer-readable signal medium may also be any computer-readable medium other than the computer-readable storage medium, and the computer-readable medium may send, propagate, or transmit the program for use by or in combination with the instruction execution system, apparatus, or device . The program code contained on the computer-readable medium can be transmitted by any suitable medium, including but not limited to: wire, optical cable, RF (Radio Frequency), etc., or any suitable combination of the above.

The above-mentioned computer-readable medium may be included in the above-mentioned server or user-side mobile device; or it may exist alone without being assembled into the server or user-side mobile device. The aforementioned computer-readable medium carries one or more programs, and when the aforementioned one or more programs are executed by the server, the server: receives the characteristic information of at least one target application submitted by the user, wherein at least one target application It is a non-pre-installed application installed in the user terminal; if there is no device identification in the device identification library whose matching degree with the feature information of at least one target application is greater than or equal to the preset threshold, the user is generated based on the feature information of at least one target application Device ID of the end. When the aforementioned one or more programs are executed by the mobile device on the user side, the mobile device on the user side: obtains characteristic information of at least one target application, where at least one target application is a non-preinstalled application installed on the user side; The feature information of at least one target application is reported to the server, so that when the server does not have a device identification whose matching degree with the feature information of at least one target application is greater than or equal to a preset threshold in the device identification library, based on the feature of the at least one target application The information generates the device identification of the user terminal.

The computer program code for performing the operations of the embodiments of the present disclosure can be written in one or more programming languages or a combination thereof, the programming languages including object-oriented programming languages-such as Java, Smalltalk, C++, It also includes conventional procedural programming languages-such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partly on the user's computer, executed as an independent software package, partly on the user's computer and partly executed on a remote computer, or entirely executed on the remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (for example, through an Internet service provider). Internet connection).

The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions, and operations of the system, method, and computer program product according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagram may represent a module, program segment, or part of code, and the module, program segment, or part of code contains one or more for realizing the specified logical function Executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the block may also occur in a different order from the order noted in the drawings. For example, two blocks shown one after another can actually be executed substantially in parallel, and they can sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and/or flowchart, and the combination of the blocks in the block diagram and/or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or operations Or it can be realized by a combination of dedicated hardware and computer instructions.

The above description is only a preferred embodiment of the present disclosure and an explanation of the applied technical principles. Those skilled in the art should understand that the scope of the invention involved in this disclosure is not limited to the technical solutions formed by the specific combination of the above technical features, and should also cover the above technical features or technical solutions without departing from the above inventive concept. Other technical solutions formed by arbitrarily combining the equivalent features. For example, the above-mentioned features and the technical features disclosed in the present disclosure (but not limited to) having similar functions are replaced with each other to form a technical solution.

Claims

A method for generating device identification, applied to a server, characterized in that the method includes:

Receiving feature information of at least one target application submitted by the user terminal, where the at least one target application is a non-preinstalled application installed in the user terminal;

If there is no device identification in the device identification library whose matching degree with the feature information of the at least one target application is greater than or equal to the preset threshold, the device identification of the user terminal is generated based on the feature information of the at least one target application.
The method according to claim 1, wherein the method further comprises:

If there is a device identification in the device identification library whose matching degree with the feature information of the at least one target application is greater than or equal to the preset threshold, determine the feature information used to generate the device identification and the feature of the at least one target application Whether the information is the same;

If they are different, associate the device identifier with the feature information of the at least one target application.
The method according to claim 1, wherein the characteristic information of the at least one target application includes an installation time with a preset time accuracy of the target application.
The method according to claim 1, wherein the characteristic information of the at least one target application includes installation times of at least two target applications.
The method according to claim 1, wherein the method further comprises:

Receiving the brand information of the user terminal submitted by the user terminal;

If there is no device identification in the device identification library whose matching degree with the feature information of the at least one target application is greater than or equal to a preset threshold, the device identification of the user terminal is generated based on the feature information of the at least one target application, include:

If the device identification library corresponding to the brand information does not have a device identification whose matching degree with the feature information of the at least one target application is greater than or equal to a preset threshold, the device identification is generated based on the feature information of the at least one target application The device identification of the user end, and the generated device identification of the user end is added to the device identification library corresponding to the brand information.
A method for generating a device identification, applied to a user terminal, characterized in that the method includes:

Acquiring characteristic information of at least one target application, where the at least one target application is a non-preinstalled application installed in the user terminal;

Reporting the feature information of the at least one target application to the server, so that when the server does not have a device identifier whose matching degree with the feature information of the at least one target application is greater than or equal to a preset threshold in the device identifier library, The device identification of the user terminal is generated based on the characteristic information of the at least one target application.
The method according to claim 6, wherein said acquiring characteristic information of at least one target application comprises:

Acquiring a list of applications installed in the client;

Select at least one target application from the application list;

Read the characteristic information of the at least one target application.
The method according to claim 7, wherein the selecting at least one target application from the application list comprises:

The application list is filtered, the pre-installed applications of the system are eliminated, and at least one target application is obtained.
The method according to claim 7, wherein the selecting at least one target application from the application list comprises:

Filter the application list and exclude applications pre-installed in the system;

At least one target application whose installation amount is greater than or equal to a preset value is selected from the filtered application list.
The method according to claim 7, wherein the selecting at least one target application from the application list comprises:

Acquiring brand information of the user terminal;

At least one target application corresponding to the brand information is selected from the application list.
An electronic device including:

One or more processors;

A storage device on which one or more programs are stored,

When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1-10.
A computer-readable medium having a computer program stored thereon, wherein the program is executed by a processor to implement the method according to any one of claims 1-10.