A method, device and medium for generating a device identifier

Abstract

The present application provides a method, apparatus, and medium for generating a device identifier. The method for generating a device identifier includes: the server obtains an activation event containing a temporary identifier sent by a client and stores the temporary identifier; the server controls the client to pop up a privacy policy page, and after the server obtains the client's consent to the privacy policy event, it parses the event reported by the client to determine whether the event contains a temporary identifier and a device code. If the event includes a device code, a formal identification identifier is generated based on the device code. Since the device code of the terminal device remains unchanged and is unique, generating a formal identification identifier based on the device code of the terminal device can ensure that the device's formal identification identifier remains unchanged after the terminal device reinstalls the application client, making it convenient for the server to monitor the behavior of the application and optimize the application, thereby improving the user experience.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a method, apparatus, and medium for generating a device identifier. Background Art

[0002] With the popularity of mobile phones and other terminal devices in people's lives, more and more applications are appearing on terminal devices, such as map applications and game applications. When users use applications on terminal devices, the applications will upload more important user events to the server. The server monitors the running effect of the application based on the uploaded information, thereby optimizing the application and improving the user experience. Events are composed of event attributes and event names. Events include device identifiers, which enable the server to determine the terminal device on which the application is running. In order to accurately identify the terminal device on which the application is running, the device identifier of each terminal device should be unique and unchanged.

[0003] The existing method of generating device identifiers requires obtaining permission from the user. If the permission fails, a device identification code is randomly generated. When the user uninstalls the application, the local data will be deleted. When the application is reinstalled, a new device identifier will be generated, which will change the device identifier of the terminal device, which is not conducive to server monitoring and optimization of the application.

[0004] Therefore, how to keep the device identifier of the terminal device unchanged after reinstalling the application is a problem that those skilled in the art need to solve urgently. Summary of the invention

[0005] The purpose of the present application is to provide a method, apparatus, and medium for generating a device identifier, so as to ensure that the device identifier of a terminal device remains unchanged after an application is reinstalled.

[0006] In order to solve the above technical problems, the present application proposes a method for generating a device identifier, which is applied to a server. The method includes:

[0007] Get the activation event containing the temporary identifier;

[0008] After obtaining the privacy policy consent event returned by the client, determining whether the event reported by the client contains the temporary identifier and device code;

[0009] If so, a formal identification identifier is generated based on the device code.

[0010] Preferably, after the step of determining whether the event reported by the client contains the temporary identifier and the device code, the method further includes:

[0011] If the event only includes the temporary identifier, a cache queue is created according to the temporary identifier, and the event corresponding to the temporary identifier is stored in the cache queue.

[0012] Preferably, after the step of generating a formal identification identifier according to the device code, the step further includes:

[0013] According to the correspondence between the temporary identifier, the device code and the formal identification identifier, the event corresponding to the temporary identifier and the formal identification identifier are stored in a log database, and the event in the cache queue is cleared.

[0014] Preferably, after the step of generating a formal identification identifier according to the device code, the step further includes:

[0015] When it is detected that the events of multiple accounts are from the same client, the events of the multiple accounts are merged and stored.

[0016] Preferably, the temporary identifier is a set of data generated by the client, and the temporary identifier is unique.

[0017] Preferably, after the step of obtaining the activation event including the temporary identifier, the method further comprises:

[0018] A notification of successful receipt of the activation event is sent to the client.

[0019] In order to solve the above technical problems, the present application also proposes another method for generating a device identifier, which is applied to a client, and the method includes:

[0020] Sending an activation event including a temporary identifier to the server;

[0021] After the user agrees to the privacy policy event, obtain the device code;

[0022] The device code and the temporary identifier are added to the event to be uploaded, and the event is uploaded to the server so that the server generates a formal identification identifier according to the device code.

[0023] In order to solve the above technical problems, the present application also proposes a device for generating a device identifier, comprising:

[0024] An acquisition module, used for acquiring an activation event including a temporary identifier;

[0025] A judgment module, configured to, after obtaining the privacy policy consent event returned by the client, determine whether the event reported by the client contains the temporary identifier and the device code, and if so, trigger the generation module;

[0026] The generating module is used to generate a formal identification identifier according to the device code.

[0027] To solve the above technical problems, the present application also proposes a device for generating a device identifier, comprising a memory for storing a computer program;

[0028] A processor is used to implement the step of generating a device identifier when executing the computer program.

[0029] In order to solve the above technical problem, the present application also proposes a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the step of generating a device identifier is implemented.

[0030] The present application provides a method for generating a device identifier, including: the server obtains an activation event containing a temporary identifier sent by the client, and stores the temporary identifier; controls the client to pop up a privacy policy page, and after the server obtains the client's consent to the privacy policy event, parses the event reported by the client to determine whether the event contains a temporary identifier and a device code. If the event includes a device code, a formal identification identifier is generated based on the device code. Since the device code of the terminal device remains unchanged and unique, generating a formal identification identifier based on the device code of the terminal device can ensure that the device's formal identification identifier remains unchanged after the terminal device reinstalls the application client, making it easier for the server to monitor the behavior of the application and optimize the application, thereby improving the user experience.

[0031] In addition, the present application also provides an apparatus and medium for generating a device identifier corresponding to the above-mentioned method for generating a device identifier, and the effect is the same as above. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0033] Figure 1 A flowchart of a method for generating a device identifier provided in an embodiment of the present application;

[0034] Figure 2 A schematic diagram of an application scenario of a method for generating a device identifier provided in an embodiment of the present application;

[0035] Figure 3 A structural diagram of an apparatus for generating a device identifier provided in an embodiment of the present application;

[0036] Figure 4 A structural diagram of an apparatus for generating a device identifier provided in another embodiment of the present application. DETAILED DESCRIPTION

[0037] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0038] The purpose of this application is to provide a method, apparatus, and medium for generating a device identifier, which can ensure that the device's official identification identifier remains unchanged after the terminal device reinstalls the application client, making it convenient for the server to monitor the behavior of the application and optimize the application, thereby improving the user experience.

[0039] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below in conjunction with the accompanying drawings and specific implementation methods.

[0040] It should be noted that the terminal devices mentioned in this application include but are not limited to smart phones, computers, etc. The terminal device can run applications, such as game applications, shopping applications, map applications, etc., and the terminal device can access the Internet so that the client of the application can interact with the server. When the user uses the application on the terminal device, the application will send corresponding events to the server according to the user's operation, such as when the user starts the application, an activation event is sent to the server; when the user agrees to the privacy policy, an agreement to the privacy policy event is sent to the server; when the user logs in to the account, a character login event is sent to the server, etc. It is understandable that other information sent by the client of the application to the server can also be written into the event and sent. It should be noted that when the user does not agree to the privacy policy agreement, the application cannot collect the user's personal information.

[0041] In the specific implementation, the application server and the application client will establish a transmission link. When the terminal device with the application installed is connected to the network, information exchange between the client and the server can be realized. It can be understood that the terminal device can be any electronic device such as a smart phone, a computer, etc.

[0042] Figure 1 A flowchart of a method for generating a device identifier provided in an embodiment of the present application, such as Figure 1 As shown, the method is applied to a server, comprising:

[0043] S10: Acquire an activation event including a temporary identifier;

[0044] It should be noted that this embodiment describes the application file from the server side of the application. The temporary identifier is a set of data generated by a specific algorithm. The server obtains the temporary identifier sent by the client. After the client generates the temporary identifier, it can send the temporary operator to the server alone, or write the temporary operator into other events and then send the event to the server. In order to reduce the frequency of events sent by the client and improve the security of communication, this application adopts the solution of writing the temporary operator into other events and sending them.

[0045] It is understandable that a server of an application needs to process information sent by multiple clients at the same time, and the server is always in working state regardless of whether the application is running or not. Therefore, when the server is running normally, no matter when the client sends an event carrying a temporary operator to the server, the server can receive and process it normally. For example: the client can send an event carrying a temporary operator to the server at startup, or send the event to the server when the user logs in. After the server obtains the event carrying the temporary operator, it parses the event, obtains the temporary identifier from it and stores it for subsequent use. It should be noted that the temporary identifier can be stored in the cache, and the event corresponding to the temporary identifier can also be stored in the database.

[0046] When the server needs to process a large number of events and requests at the same time, the processing speed of the server will drop significantly, and it may not be possible to parse the temporary identifier in time, affecting subsequent use. For example, when the user creates an account on the client, the server obtains the event carrying the temporary identifier. If the temporary identifier cannot be obtained in time, it will affect the user's account registration and use of the application, affecting the user's experience. It can be seen that the earlier the server obtains the event carrying the temporary identifier, the more beneficial it is to improve the user's experience. Therefore, this embodiment chooses to write the temporary identification code into the activation event. It can be understood that the activation event refers to the event obtained by the server when the user starts the application. Writing the temporary identification code into the activation event can reserve enough time for subsequent processing work, so that users can get a better experience.

[0047] S11: After obtaining the privacy policy consent event returned by the client, determine whether the event reported by the client contains a temporary identifier and a device code. If yes, proceed to S12;

[0048] S12: Generate a formal identification identifier according to the device code.

[0049] In the specific implementation, after receiving the above activation event uploaded by the client and obtaining the temporary identifier from it, the server is ready to receive subsequent events, such as: allocating memory space for storing events, allocating computing resources, etc. According to relevant policy regulations, the application can only use the user's personal information after the user agrees to the privacy policy. Therefore, when the user agrees to the privacy policy and the server obtains the privacy policy agreement event returned by the client, the client can write the device code of the current terminal device into the event and send it to the server. After receiving the privacy policy agreement event uploaded by the client, the server detects all subsequent events uploaded by the same client to determine whether the event contains a temporary identifier and a device code, and stores the events separately. If the event contains a device code, the corresponding formal identification identifier is generated according to the device code, and other previously stored events, such as activation events, are found according to the temporary identifier in the event, and these events are merged and stored with the formal identification identifier.

[0050] It is understandable that there are many types of device codes for terminal devices, and applications can choose the appropriate device code according to their own functions. For example, applications applied to the Android system can use the International Mobile Equipment Identity (IMEI). IMEI is an international mobile equipment identification code that only Android phones have. It is an "electronic serial number" composed of 15 digits. It corresponds to each mobile phone one by one, and the code is unique in the world. IMEI is stored on the motherboard of the terminal device. After reinstalling the application, IMEI will not change; the device code can also be ANDROID_ID, which is a string of 64-bit hexadecimal numbers randomly generated by the system when the device is first started. For iOS phones, applications can obtain the advertising identifier of the phone. The advertising identifier is specially set by Apple for various advertising providers to track users, and it can also ensure that the user's device is not tracked by the application. The advertising identifier can only be modified by the user, and will not change due to reinstalling the application, and the advertising identifier obtained by the application on the same device is the same.

[0051] It should be noted that there are many ways for the server to generate a formal identification identifier based on the device code. The device code can be directly used as the formal identification identifier of the current device, or the device code can be encrypted and the encrypted data can be used as the formal identification identifier of the current device. The formal identification identifier can also be generated by combining the current time, the network address of the device and other information. There is no limitation on the algorithm for generating the formal device identifier, and it only needs to ensure that the formal identification identifier of the same device is unique and unchanged.

[0052] In specific implementations, some applications allow users to register multiple accounts on the same device. The server may detect multiple events with the same formal identification identifier, and these events can be stored together or separately according to different accounts. It is understandable that in order to ensure the normal operation of the application, after obtaining the event, the server sends a successful acquisition message to the client that uploaded the event; after the server obtains an event, if it does not obtain the next event within a preset time, for example, after the server receives the privacy policy agreement event, if it does not obtain the time containing the temporary identifier and device code within 5 seconds from the time of receipt, it will promptly send a confirmation message to the client.

[0053] The present embodiment provides a method for generating a device identifier, which is applied to a server, and includes: the server obtains an activation event containing a temporary identifier sent by a client, and stores the temporary identifier; controls the client to pop up a privacy policy page, and after the server obtains the client's consent to the privacy policy event, it parses the event reported by the client to determine whether the event contains a temporary identifier and a device code. If the event includes a device code, a formal identification identifier is generated based on the device code. Since the device code of the terminal device remains unchanged and is unique, generating a formal identification identifier based on the device code of the terminal device can ensure that the formal identification identifier of the device remains unchanged after the terminal device reinstalls the application client, which facilitates the server to monitor the behavior of the application and optimize the application, thereby improving the user experience.

[0054] In specific implementations, the server needs to process a large number of event requests from multiple clients at the same time. If these events and other data are stored in the memory space, the server storage space may be insufficient. If the server memory is increased for this purpose, the server cost will increase. Moreover, some of the data in these events only needs to be stored temporarily, such as temporary identifiers. After use, the data needs to be cleared, which requires frequent read, write and delete operations. Therefore, these temporary events are more suitable for storage in the cache queue.

[0055] On the basis of the above embodiment, when generating a device identifier, after the step of determining whether the event reported by the client contains a temporary identifier and a device code, the following steps are further included:

[0056] If the event only contains a temporary identifier, a cache queue is created according to the temporary identifier, and the event corresponding to the temporary identifier is stored in the cache queue.

[0057] It is understandable that application server resources are limited, and the number of requests that the database can accept per second is also limited (or the reading and writing of files is also limited). After the introduction of cache, the request can directly obtain the target data from the cache and return it, thereby reducing the amount of calculation and effectively improving the response speed.

[0058] In this embodiment, a cache queue is created based on a temporary identifier, and events corresponding to the temporary identifier are stored in the cache queue, thereby improving the computing speed of the server and enabling the server to effectively utilize limited resources to provide the largest possible processing capacity, allowing limited resources to serve more users, thereby reducing server costs and improving user experience.

[0059] The above embodiment improves the server operation speed and processing capacity by introducing cache technology. However, after storing the temporary identifier and other events in the cache queue, it is necessary to release the cache queue at an appropriate time and store the valid information therein in the database.

[0060] Based on the above embodiment, after the step of generating a formal identification identifier according to the device code, the method further includes:

[0061] According to the correspondence between the temporary identifier, the device code and the formal identification identifier, the events corresponding to the temporary identifier and the formal identification identifier are stored in the log database, and the events in the cache queue are cleared.

[0062] When the server generates a formal identifier based on the device code, since the device carrying the device code also carries a temporary identifier, and the temporary identifier has a unique corresponding relationship with the terminal device in a short period of time, the server can find the corresponding time stored in the cache queue based on the formal identification identifier and the temporary identifier, and store these events in the log database, which is convenient for the server to subsequently monitor and optimize the operation of the application on the terminal device, and release the events in the cache queue at the same time.

[0063] In this embodiment, the events and formal identification identifiers stored in the cache queue are stored in the log database, and the events in the corresponding cache queue are cleared to release cache resources and improve the processing speed of the server. At the same time, the corresponding events and formal identification identifiers are merged and stored in the log database, which facilitates the server to monitor and optimize the operation of the application on the terminal device and improve the user experience.

[0064] In specific implementations, some applications allow users to register multiple accounts on the same terminal device. In this case, the server will detect many events from the same terminal device but different accounts. These events can all reflect the operation of the application on the same terminal device.

[0065] Based on the above embodiment, after the step of generating a formal identification identifier according to the device code, the method further includes:

[0066] When it is detected that events of multiple accounts come from the same client, the events of the multiple accounts are merged and stored.

[0067] The application allows the user to register multiple accounts on the same client. For example, for game applications, the user can select different accounts on the same device, and the events of these accounts can be stored separately or merged. In this embodiment, different events from different accounts of the same device are merged and stored according to the formal identification identifier. It can be understood that the same account can be logged in on different devices. Since the main purpose of monitoring the operation of the application on the terminal device is to provide reference data for the subsequent optimization of the application, and the operation of the application is only related to the terminal device and has nothing to do with the account, therefore, in order to facilitate the collection and processing of the operation data of the application, the storage of events has nothing to do with the account, and all are stored according to the formal identification identifier.

[0068] In this embodiment, events sent by different accounts on the same device and events sent by the same account on different devices are classified and stored according to the same standard - the official identification identifier of the terminal device, so that the server can better monitor the operation of the application on different terminal devices, thereby making better optimization and improving the user experience.

[0069] In the process of obtaining the device code and generating a formal identification identifier based on the device code, the server needs to use the temporary identifier to mark the terminal device and process the corresponding events, for example, release the events in the cache queue and store the events in the log database. Therefore, in this process, it is necessary to ensure a one-to-one correspondence between the temporary identifier and the client.

[0070] Based on the above embodiment, the temporary identifier is a set of data generated by the client, and the temporary identifier is unique.

[0071] Since the temporary identifier is completely generated by the client and does not exchange information with the server or other clients, in order to ensure the uniqueness of the temporary identifier, the generated temporary identifier may include: the version number and download platform of the application, the number of downloads, the timestamp generated based on the current time, the gateway of the current device, etc. The method for generating the temporary identifier is not limited here, it only needs to ensure that the temporary identifier is unique.

[0072] In this embodiment, the client is marked with a unique temporary identifier to determine the correspondence between events in the server cache and the client, which facilitates the server to process events without losing events obtained before the server generates a positive identification identifier, thereby helping the server to monitor and optimize the operation of the application.

[0073] Since the server and the client transmit data through the network, when the network fluctuates, reception failure may occur, resulting in data loss. After the step of obtaining the activation event containing the temporary identifier based on the above embodiment, the method further includes:

[0074] Sends a notification to the client of the successful receipt of an activation event.

[0075] When the server obtains the activation event, it allocates memory and computing resources to the client and sends a notification of successful event reception to the client, indicating that the two have established a connection and the server is ready to receive subsequent events uploaded by the client at any time. In order to make full use of server resources, after the server sends a notification of successful event reception, if no subsequent events are obtained within the preset events, a confirmation message is sent to the client. If it is confirmed that the client has not sent an event, the computing resources allocated to the client are released.

[0076] In this embodiment, after acquiring the activation event including the temporary identifier, a notification of successful reception of the activation event is sent to the client, thereby preventing data loss due to network fluctuations, enabling the server to better monitor the operation of the application, and improving the user experience.

[0077] Based on the above embodiment, this embodiment further provides a method for generating a device identifier applied to a client, including:

[0078] S20: Sending an activation event including a temporary identifier to the server;

[0079] S21: After the user agrees to the privacy policy event, obtain the device code;

[0080] S22: Add the device code and the temporary identifier to the event to be uploaded, and upload the event to the server so that the server can generate a formal identification identifier based on the device code.

[0081] Since the method for generating a device identifier applied to the client and the method for generating a device identifier applied to the server correspond to each other, for the embodiment of the method for generating a device identifier applied to the client, please refer to the description of the embodiment of the method for generating a device identifier applied to the server, which will not be repeated here.

[0082] This embodiment provides a method for generating a device identifier, which is applied to the client of an application program, and the method includes: sending an activation event including a temporary identifier to a server; obtaining a device code after the user agrees to the privacy policy event; adding the device code and the temporary identifier to the event to be uploaded, and uploading the event to the server, so that the server can generate a formal identification identifier based on the device code. Since the device code of the terminal device remains unchanged and is unique, after the server generates a formal identification identifier based on the device code of the terminal device, it can ensure that the formal identification identifier of the device remains unchanged after the terminal device reinstalls the application client, which facilitates the server to monitor the behavior of the application program and optimize the application program, thereby improving the user experience.

[0083] Based on the above embodiments, the present application further provides an embodiment of an application scenario. This embodiment takes a game application as an example to illustrate a method for generating a device identifier. Figure 2 A schematic diagram of an application scenario of a method for generating a device identifier, such as Figure 2 As shown, the method of generating a device identifier includes:

[0084] S30: After the user installs the game client on the terminal device, the game client is started;

[0085] S31: The client loads game resources, generates a temporary identifier, and reports an activation event including the temporary identifier;

[0086] S32: The server puts the activation event into a cache queue;

[0087] S33: The server sends a report success message to the client;

[0088] S34: The client displays the privacy policy page to the user;

[0089] S35: The user obtains the device code after agreeing to the privacy policy;

[0090] S36: Sending the event carrying the device code and the temporary identifier to the server;

[0091] S37: The server generates a formal identification identifier according to the device code, and clears the event corresponding to the temporary identifier in the cache queue;

[0092] S38: storing the event and the formal identification identifier in a log database;

[0093] S39: The server sends a report success message to the client;

[0094] S40: The client displays the game interface and the user enters the game.

[0095] It can be understood that the formal identification identifier can be generated on the client side. After the client generates the formal identification identifier, it writes the formal identification identifier and the temporary identifier into the event and uploads the event to the server. The client can also write the device code and the temporary identifier into the event and upload the event to the server, and then the server generates the formal identification identifier. The present application scheme chooses the latter method. Generating the formal identification identifier on the server is more secure and not easily affected by external interference.

[0096] This embodiment provides an application scenario for generating a device identifier. The device code of the terminal device remains unchanged and is unique. By generating a formal identification identifier based on the device code of the terminal device, it can be ensured that after the terminal device reinstalls the application client, the formal identification identifier of the device remains unchanged, making it convenient for the server to monitor the behavior of the application and optimize the application, thereby improving the user experience.

[0097] In the above embodiments, the method for generating a device identifier is described in detail, and the present application also provides an embodiment corresponding to the device for generating a device identifier. It should be noted that the present application describes the embodiments of the device part from two perspectives, one is based on the functional module perspective, and the other is based on the hardware perspective.

[0098] The above describes various embodiments corresponding to the method for generating a device identifier. On this basis, the present invention also discloses an apparatus for generating a device identifier corresponding to the above method. Figure 3 This is a structural diagram of a device for generating a device identifier provided by this embodiment.

[0099] like Figure 3 As shown, a device for generating a device identifier, characterized by comprising:

[0100] An acquisition module 10, used to acquire an activation event including a temporary identifier;

[0101] The judgment module 11 is used to determine whether the event reported by the client contains a temporary identifier and a device code after obtaining the privacy policy consent event returned by the client, and if so, trigger the generation module 12;

[0102] The generating module 12 is used to generate a formal identification identifier according to the device code.

[0103] Since the embodiments of the apparatus part correspond to the embodiments of the method part, please refer to the description of the embodiments of the method part for the embodiments of the apparatus part, which will not be repeated here.

[0104] In this embodiment, a device for generating a device identifier is provided, and the device includes: a server obtains an activation event including a temporary identifier sent by a client, and stores the temporary identifier; controls the client to pop up a privacy policy page, and after the server obtains the client's consent to the privacy policy event, parses the event reported by the client to determine whether the event contains a temporary identifier and a device code. If the event includes a device code, a formal identification identifier is generated based on the device code. Since the device code of the terminal device remains unchanged and is unique, generating a formal identification identifier based on the device code of the terminal device can ensure that the device's formal identification identifier remains unchanged after the terminal device reinstalls the application client, which facilitates the server to monitor the behavior of the application and optimize the application, thereby improving the user experience.

[0105] Figure 4 A structural diagram of an apparatus for generating a device identifier provided in another embodiment of the present application, such as Figure 4 As shown, the apparatus for generating a device identifier includes: a memory 20 for storing a computer program;

[0106] The processor 21 is configured to implement the steps of the method for generating a device identifier in the above embodiment when executing a computer program.

[0107] The terminal device provided in this embodiment including the processor 21 and the memory 20 may include but is not limited to a smart phone, a tablet computer, a laptop computer or a desktop computer.

[0108] Among them, the processor 21 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 21 can be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 21 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 21 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 21 may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.

[0109] The memory 20 may include one or more computer-readable storage media, which may be non-transitory. The memory 20 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In this embodiment, the memory 20 is at least used to store the following computer program 201, wherein, after the computer program is loaded and executed by the processor 21, it can implement the relevant steps of the device for generating a device identifier disclosed in any of the aforementioned embodiments. In addition, the resources stored in the memory 20 may also include an operating system 202 and data 203, etc., and the storage method may be temporary storage or permanent storage. Among them, the operating system 202 may include Windows, Unix, Linux, etc. Data 203 may include, but is not limited to, a temporary identifier of a terminal device, etc.

[0110] In some embodiments, the apparatus for generating a device identifier may further include a display screen 22 , an input and output interface 23 , a communication interface 24 , a power supply 25 , and a communication bus 26 .

[0111] Those skilled in the art will understand that Figure 4 The structure shown in the figure does not constitute a limitation on the apparatus for generating a device identifier, and may include more or less components than those shown in the figure.

[0112] The apparatus for generating a device identifier provided in an embodiment of the present application includes a memory and a processor. When the processor executes a program stored in the memory, the processor can implement the following method: generating a device identifier.

[0113] Finally, the present application also provides an embodiment corresponding to a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps recorded in the above method embodiment are implemented.

[0114] It is understandable that if the method in the above embodiment is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0115] The above is a detailed introduction to the method, apparatus, and medium for generating a device identifier provided by the present application. The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referenced to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the claims of the present application.

[0116] It should also be noted that, in this specification, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.

Claims

1. A method for generating a device identifier, characterized in that: Applicable to servers, including: Obtaining an activation event including a temporary identifier sent by the client; the parameters for generating the temporary identifier include: the version number and download platform of the application, the number of downloads, the timestamp generated at the current time, and the gateway of the current device; the temporary identifier is generated by the client; After obtaining the privacy policy consent event returned by the client, determine whether the event reported by the client contains the temporary identifier and device code; wherein the device code is an international mobile equipment identity code or ANDROID_ID or an advertising identifier; If so, a formal identification identifier is generated according to the device code, and other previously stored events are found according to the temporary identifier in the event.

2. The method for generating a device identifier according to claim 1, characterized in that: After the step of determining whether the event reported by the client contains the temporary identifier and the device code, the method further includes: If the event only includes the temporary identifier, a cache queue is created according to the temporary identifier, and the event corresponding to the temporary identifier is stored in the cache queue.

3. The method for generating a device identifier according to claim 2, characterized in that: After the step of generating a formal identification identifier according to the device code, the method further includes: According to the correspondence between the temporary identifier, the device code and the formal identification identifier, the event corresponding to the temporary identifier and the formal identification identifier are stored in a log database, and the event in the cache queue is cleared.

4. The method for generating a device identifier according to claim 3, characterized in that: After the step of generating a formal identification identifier according to the device code, the method further includes: When it is detected that the events of multiple accounts are from the same client, the events of the multiple accounts are merged and stored.

5. The method for generating a device identifier according to claim 4, characterized in that: The temporary identifier is a set of data generated by the client, and the temporary identifier is unique.

6. The method for generating a device identifier according to claim 5, characterized in that: After the step of obtaining the activation event including the temporary identifier, the method further includes: A notification of successful receipt of the activation event is sent to the client.

7. A method for generating a device identifier, characterized in that: Applied to the client, including: Sending an activation event including a temporary identifier to the server; the parameters for generating the temporary identifier include: the version number and download platform of the application, the number of downloads, the timestamp generated at the current time, and the gateway of the current device; the temporary identifier is generated by the client; After the user agrees to the privacy policy event, obtain the device code; the device code is the International Mobile Equipment Identity code or ANDROID_ID or advertising identifier; The device code and the temporary identifier are added to the event to be uploaded, and the event is uploaded to the server, so that the server generates a formal identification identifier according to the device code and finds other previously stored events according to the temporary identifier in the event.

8. A device for generating a device identifier, characterized in that: include: An acquisition module, used for acquiring an activation event including a temporary identifier sent by a client; The parameters for generating the temporary identifier include: the version number and download platform of the application, the number of downloads, the timestamp generated at the current time, and the gateway of the current device; the temporary identifier is generated by the client; A judgment module, configured to, after obtaining the privacy policy consent event returned by the client, determine whether the event reported by the client contains the temporary identifier and the device code, and if so, trigger the generation module; wherein the device code is an international mobile equipment identity code or ANDROID_ID or an advertising identifier; The generating module is used to generate a formal identification identifier according to the device code, and find other previously stored events according to the temporary identifier in the event.

9. A device for generating a device identifier, characterized in that: comprising a memory for storing a computer program; A processor, configured to implement the step of generating a device identifier as claimed in any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the step of generating a device identifier according to any one of claims 1 to 7 is implemented.

Images