Management methods, devices, electronic equipment and storage media for identification

Abstract

This application relates to a method, apparatus, electronic device, and storage medium for managing identifiers, and pertains to the field of Internet technology. In this application, in response to an operation at a first moment, the client sends an identifier request message to the terminal. If the time interval between the first moment and the moment the terminal last received the client's request message exceeds a preset time interval, the terminal uses a preset algorithm to encrypt the previously determined reference device identifier to obtain the reference device identifier, and sends the reference device identifier to the client. The client compares the received reference device identifier with a stored reference device identifier. If the received reference device identifier does not match the stored reference device identifier, the client uses the preset algorithm to encrypt the stored reference device identifier. If the received reference device identifier still does not match the encrypted reference device identifier, it is determined that the terminal has changed. Thus, the client can determine whether its terminal has changed from the changing identifier.

Description

Technical Field

[0001] This disclosure relates to the field of Internet technology, and in particular to a method, apparatus, electronic device and storage medium for managing identifiers. Background Technology

[0002] With the development of Internet technology, in order to ensure user data security, when a user logs into a terminal application (APP), the APP can read the device identifier (such as the mobile phone serial number) of the terminal (such as mobile phone, tablet computer, etc.) and determine whether the user has changed the terminal based on the device identifier. Then, based on whether the device has been changed, it can further determine whether there are security risks such as account theft or identity theft.

[0003] However, once the terminal's device identifier is read by the application, some problems can arise. For example, misuse of the device identifier and tracking and identification of the terminal can still lead to insecurity of user data. Therefore, how to determine whether a terminal has been altered without reading its device identifier is a pressing issue that needs to be addressed. Summary of the Invention

[0004] This disclosure provides a method, apparatus, electronic device, and storage medium for managing identifiers, used to determine whether a terminal has been changed when the terminal's device identifier is not read.

[0005] The technical solution of this disclosure is as follows:

[0006] According to a first aspect of the present disclosure, a method for managing identifiers is provided, applied to a client. The method includes: responding to an operation to call a device identifier at a first moment, sending identifier request information to a terminal where the client is located to obtain a device identifier of the terminal; receiving a target reference identifier sent by the terminal and obtaining a reference device identifier stored by the client; when the duration between the first moment and the second moment exceeds a preset duration, the target reference identifier is a second reference identifier, the second reference device identifier being a reference identifier obtained by the terminal encrypting a first reference device identifier according to a preset algorithm, the first reference device identifier being a reference identifier determined by the terminal when it last received the identifier request information sent by the client at the second moment. When the target reference identifier is inconsistent with the stored reference device identifier, the stored reference device identifier is encrypted according to a preset algorithm to obtain an encrypted reference device identifier; when the target reference identifier is inconsistent with the encrypted reference device identifier, it is determined that the terminal where the client is located has changed.

[0007] Optionally, when the duration between the first moment and the second moment does not exceed a preset duration, the target reference identifier is the first reference device identifier.

[0008] Optionally, the method further includes: determining that the terminal where the client is located has not changed when the target reference identifier is consistent with the stored reference device identifier or the target reference identifier is consistent with the encrypted reference device identifier.

[0009] Optionally, the method further includes: when it is determined that the terminal where the client is located has changed, replacing the stored reference device identifier with the target reference identifier.

[0010] Optionally, the method further includes: sending an identifier request message including the identifier of the client to the terminal for the first time; receiving and storing a third reference device identifier sent by the terminal, wherein the third reference device identifier is obtained by the terminal encrypting the identifier of the client according to a preset algorithm, and the first reference device identifier is obtained based on the third reference device identifier.

[0011] Optionally, the method further includes: receiving a first random number sent by the receiving terminal; the second reference device identifier is a reference identifier obtained by encrypting the first reference device identifier according to a preset algorithm, which means: the second reference device identifier is a reference identifier obtained by encrypting the first reference device identifier and the first random number according to a preset algorithm.

[0012] A second aspect of this disclosure provides a method for managing identifiers, applied to a terminal where a client resides. The method may include: receiving identifier request information sent by the client in response to an operation to call a device identifier at a first moment, the identifier request information being used to request the acquisition of the terminal's device identifier; determining a target reference identifier for the terminal in response to the identifier request information; when the time interval between the first moment and the second moment in which the identifier request information was last received from the client exceeds a preset time interval, the target reference identifier is a second reference device identifier; the second reference device identifier is a reference identifier obtained by encrypting a first reference device identifier according to a preset algorithm, the first reference device identifier being a reference identifier determined when the identifier request information was received from the client at the second moment; and sending the target reference identifier to the client. The target reference identifier is used to: determine that the terminal has changed when it is inconsistent with a reference device identifier stored by the client and an encrypted reference device identifier obtained by using a preset algorithm with the stored reference device identifier.

[0013] Optionally, the method further includes: when the duration between the first moment and the second moment does not exceed a preset duration, the target reference identifier is the first reference device identifier.

[0014] Optionally, the method further includes: when the client sends an identifier request information including the client's identifier for the first time, encrypting the client's identifier according to a preset algorithm to obtain a third reference device identifier, and sending a second response information including the third reference device identifier to the terminal, wherein the first reference device identifier is obtained based on the third reference device identifier.

[0015] Optionally, the identification request information includes the client's identifier, and the terminal also stores the correspondence between the client's identifier and the reference device identifier. The method further includes: after obtaining the fourth reference device identifier by encryption based on a preset algorithm, replacing the reference device identifier in the correspondence with the fourth reference device identifier.

[0016] Optionally, before determining the target reference identifier of the terminal, the method further includes: using the reference device identifier corresponding to the client in the identifier request information in the correspondence as the first reference device identifier.

[0017] Optionally, the method further includes: sending a first random number to the client; the method of "encrypting the first reference device identifier according to a preset algorithm to obtain a second reference device identifier" specifically includes: encrypting the first reference device identifier and the first random number according to a preset algorithm to obtain a second reference device identifier.

[0018] According to a third aspect of the present disclosure, an identification management device is provided for a client, the device including: a sending unit, a receiving unit, an acquisition unit, and a processing unit.

[0019] The sending unit is used to respond to the operation of calling the device identifier at the first moment by sending an identifier request information to the terminal where the client is located to obtain the device identifier of the terminal.

[0020] The receiving unit is used to receive the target reference identifier sent by the terminal. When the time interval between the first time and the second time exceeds a preset time interval, the target reference identifier becomes the second reference identifier. The second reference device identifier is a reference identifier obtained by the terminal encrypting the first reference device identifier according to a preset algorithm. The first reference device identifier is the reference identifier determined by the terminal when it last received the identifier request information sent by the client at the second time.

[0021] The acquisition unit is used to acquire the reference device identifier stored on the client.

[0022] The processing unit is used to encrypt the stored reference device identifier according to a preset algorithm to obtain the encrypted reference device identifier when the target reference identifier is inconsistent with the stored reference device identifier; and to determine that the terminal where the client is located has changed when the target reference identifier is inconsistent with the encrypted reference device identifier.

[0023] Optionally, when the duration between the first moment and the second moment does not exceed a preset duration, the target reference identifier is the first reference device identifier.

[0024] Optionally, the processing unit is also configured to determine that the terminal where the client is located has not changed when the target reference identifier is consistent with the stored reference device identifier or the target reference identifier is consistent with the encrypted reference device identifier.

[0025] Optionally, the processing unit is also configured to replace the stored reference device identifier with the target reference identifier when it is determined that the terminal where the client is located has changed.

[0026] Optionally, the sending unit is further configured to send an identification request message including the client's identifier to the terminal for the first time. The receiving unit is further configured to receive and store a third reference device identifier sent by the terminal, wherein the third reference device identifier is obtained by the terminal encrypting the client's identifier according to a preset algorithm, and the first reference device identifier is obtained based on the third reference device identifier.

[0027] Optionally, the receiving unit is also used to receive a first random number sent by the terminal. The second reference device identifier being a reference identifier obtained by encrypting the first reference device identifier according to a preset algorithm means that the second reference device identifier is a reference identifier obtained by encrypting the first reference device identifier and the first random number according to a preset algorithm.

[0028] According to a fourth aspect of the present disclosure, an identifier management device is provided, applied to a client where a client resides. The device includes a receiving unit, a determining unit, and a sending unit. The receiving unit is configured to receive identifier request information sent by the client in response to an operation to call a device identifier at a first moment. The identifier request information is used to request the acquisition of the device identifier of the terminal. The determining unit is configured to determine a target reference identifier for the terminal in response to the identifier request information. When the time interval between the first moment and the second moment in which the identifier request information was last received from the client exceeds a preset time interval, the target reference identifier is a second reference device identifier. The second reference device identifier is a reference identifier obtained by encrypting a first reference device identifier according to a preset algorithm. The first reference device identifier is a reference identifier determined when the identifier request information was received from the client at the second moment. The sending unit is configured to send the target reference identifier to the client. The target reference identifier is used to determine that the terminal has changed when it is inconsistent with a reference device identifier stored by the client and an encrypted reference device identifier obtained by using a preset algorithm with the stored reference device identifier.

[0029] Optionally, when the duration between the first moment and the second moment does not exceed a preset duration, the target reference identifier is the first reference device identifier.

[0030] Optionally, the device further includes a processing unit. The processing unit is further configured to, upon first receiving an identification request message including the client's identifier sent by the client, encrypt the client's identifier according to a preset algorithm to obtain a third reference device identifier. The sending unit is further configured to send second response information including the third reference device identifier to the terminal, wherein the first reference device identifier is obtained based on the third reference device identifier.

[0031] Optionally, the identification request information includes the client's identifier, and the terminal also stores a correspondence between the client's identifier and the reference device identifier. The processing unit is further configured to replace the reference device identifier in the correspondence with the fourth reference device identifier after obtaining the fourth reference device identifier based on a preset algorithm.

[0032] Optionally, the determining unit is further configured to, before determining the target reference identifier of the terminal, use the reference device identifier corresponding to the client in the identifier request information in the correspondence relationship as the first reference device identifier.

[0033] Optionally, the sending unit is further configured to send a first random number to the client. The processing unit is specifically configured to encrypt the first reference device identifier and the first random number according to a preset algorithm to obtain a second reference device identifier.

[0034] According to a fifth aspect of the present disclosure, an electronic device is provided, which may include: a processor and a memory for storing processor-executable instructions; wherein the processor is configured to execute the instructions to implement any of the management methods optionally identified in the first aspect above.

[0035] According to a sixth aspect of the present disclosure, an electronic device is provided, which may include: a processor and a memory for storing processor-executable instructions; wherein the processor is configured to execute the instructions to implement any of the management methods optionally identified in the second aspect above.

[0036] According to a seventh aspect of the present disclosure, a computer-readable storage medium is provided, on which instructions are stored, such that when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is able to perform any of the management methods optionally identified in the first aspect above.

[0037] According to an eighth aspect of the present disclosure, a computer-readable storage medium is provided, on which instructions are stored, such that when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is able to perform any of the management methods optionally identified in the second aspect above.

[0038] According to a ninth aspect of the present disclosure, a computer program product is provided, the computer program product including computer instructions that, when executed on an electronic device, cause the electronic device to perform an identifier management method as described in any of the optional implementations of the first aspect.

[0039] According to a tenth aspect of the present disclosure, a computer program product is provided, the computer program product including computer instructions that, when executed on an electronic device, cause the electronic device to perform an identifier management method as described in any of the optional implementations of the second aspect.

[0040] According to an eleventh aspect of the present disclosure, a communication system is provided, the communication system including a client and a terminal. The terminal can execute any of the optional implementations of the first aspect; the client can execute any of the optional implementations of the second aspect.

[0041] In this application, in response to the operation of calling the device identifier at the first moment, the client can send an identifier request message to the terminal to request the terminal's device identifier. After receiving the identifier request message, if the terminal determines that the time interval between the first moment and the moment it last received the identifier request message from the client exceeds a preset time interval, the terminal can encrypt the previously determined reference device identifier using a preset algorithm to obtain an encrypted reference device identifier. The terminal can send the encrypted reference device identifier to the client, and the client can determine whether its terminal has changed based on the encrypted reference device identifier. Since the encrypted identifier is obtained by the terminal encrypting the previously determined identifier using a preset algorithm, the encrypted identifier is unique; that is, the encrypted identifier can uniquely identify the terminal without using the terminal's device identifier.

[0042] Additionally, after receiving the reference identifier from the terminal, the client can compare the received reference identifier with the stored reference device identifier. If they do not match, the client can encrypt the stored reference device identifier using a preset algorithm, thus obtaining an encrypted reference device identifier. Since the reference device identifier stored by the client can be the reference device identifier of the client's previous terminal, if the reference device identifier received by the client does not match the stored reference device identifier or the encrypted reference device identifier, it indicates that the client's current terminal is different from its previous terminal; that is, the client's terminal has changed.

[0043] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. Attached Figure Description

[0044] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure, and are not intended to unduly limit this disclosure.

[0045] Figure 1 A schematic diagram of the structure of a communication system provided in an embodiment of this disclosure is shown;

[0046] Figure 2 A schematic diagram of the structure of another communication system provided in an embodiment of this disclosure is shown;

[0047] Figure 3 A schematic diagram of the structure of another communication system provided in an embodiment of this disclosure is shown;

[0048] Figure 4 A flowchart illustrating an identification management method provided in an embodiment of this disclosure is shown.

[0049] Figure 5 A schematic diagram of a login client provided in an embodiment of this disclosure is shown;

[0050] Figure 6 A flowchart illustrating yet another identification management method provided in this disclosure is shown.

[0051] Figure 7 A flowchart illustrating yet another identification management method provided in this disclosure is shown.

[0052] Figure 8 A flowchart illustrating yet another identification management method provided in this disclosure is shown.

[0053] Figure 9 A flowchart illustrating yet another identification management method provided in this disclosure is shown.

[0054] Figure 10 A schematic diagram of the structure of an identification management device provided in an embodiment of this disclosure is shown;

[0055] Figure 11 A schematic diagram of the structure of another identification management device provided in an embodiment of this disclosure is shown;

[0056] Figure 12 A schematic diagram of the structure of another communication system provided in an embodiment of this disclosure is shown;

[0057] Figure 13 A schematic diagram of the structure of another identification management device provided in an embodiment of this disclosure is shown. Detailed Implementation

[0058] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0059] It should be noted that the terms "first," "second," and the like in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the numbers used in this manner are interchangeable where appropriate so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure as detailed in the appended claims.

[0060] It should also be understood that the term "comprising" indicates the presence of the described feature, whole, step, operation, element and / or component, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements and / or components.

[0061] The data disclosed herein may be data authorized by the user or fully authorized by all parties.

[0062] As described in the background section, to protect user data security, client / application (APP) can obtain the device identifier of the terminal (such as a mobile phone or tablet) and determine whether the terminal has been changed based on this identifier. Furthermore, based on whether the terminal has been changed, it can determine whether there are security risks such as account theft or identity fraud. Therefore, accurate terminal identification is crucial for preventing network risks and ensuring the security of user data and funds.

[0063] The device identifier of a terminal refers to a number (such as the International Mobile Equipment Identity (IMEI)) or an immutable identifier (also known as a fixed identifier) ​​that is written into the motherboard of the terminal at the factory and cannot be erased or tampered with. The client can use this number or immutable identifier to determine whether the logged-in terminal has changed, and thus determine whether the logged-in terminal is a secure device.

[0064] In one example, the client / app can read the immutable identifier of the terminal where the client is located by calling the operating system (OS) interface, and store the immutable identifier to the background server.

[0065] like Figure 1As shown, the client / app can send a request to the terminal's operating system to request a device identifier. Upon receiving the request, the operating system can read the terminal's immutable identifier and return it to the client / app. The client / app can then store the received immutable identifier on a background server.

[0066] Subsequently, the app can obtain the immutable identifier of the terminal when responding to user login or other operations, and send this immutable identifier to the backend server. The server then compares this immutable identifier with a stored immutable identifier to determine whether the terminal on which the app is located has changed. For example, if the immutable identifier matches the stored immutable identifier, the server can determine that the terminal on which the app is located has not changed; if the immutable identifier does not match the stored immutable identifier, the server can determine that the terminal on which the app is located has changed.

[0067] However, in some cases, the client / app cannot read the terminal's immutable identifier. For example, the terminal may not allow the client / app to read its immutable identifier. In this situation, the client / app cannot determine whether the terminal has changed by using the terminal's immutable identifier.

[0068] To accurately determine whether the terminal has changed, the client / app can use a third-party component to determine whether the terminal has changed.

[0069] In this context, third-party components can refer to tools configured on the terminal. For example, this could be a software development kit (SDK). Third-party components can generate a variable identifier based on the terminal's immutable identifier and a preset algorithm.

[0070] In one example, such as Figure 2 As shown, when a client / app needs to access the terminal's device identifier, it can send a request to a third component to obtain the device identifier. The third-party component can read the terminal's immutable identifier through the terminal's operating system interface and generate a variable identifier based on it. Alternatively, the third-party component can pre-read the terminal's immutable identifier and generate a variable identifier based on it. Upon receiving the request from the client / app, the third-party component can return the variable identifier to the client / app. The client / app can then use this variable identifier to determine whether the logged-in terminal has changed. For details, please refer to the description above; further elaboration is unnecessary.

[0071] but, Figure 2The proposed solution lacks flexibility because the client / app relies on a third-party component to manage device identifiers. Furthermore, the terminal requires the third-party component to be pre-installed, limiting the application of this technology. Additionally, the variable identifier obtained through the third-party component can only change after the client / app is uninstalled and reinstalled or the terminal is reset, resulting in an excessively long identifier lifespan and poor variability. The client / app can still identify and track the terminal using this variable identifier for an extended period, potentially leading to user data leaks.

[0072] In view of this, embodiments of this application provide a method for managing identifiers. The method includes: in response to an operation to call an identifier device identifier at a first moment, a client sends an identifier request message to a terminal to request the acquisition of the terminal's device identifier. When the time interval between the first moment and the moment when the terminal last received the identifier request message from the client exceeds a preset time interval, the terminal can use a preset algorithm to encrypt a previously determined reference device identifier to obtain a first reference device identifier, and send the first reference device identifier to the client. After receiving the target reference identifier sent by the terminal, the client can compare the target reference identifier with a stored reference device identifier. When the target reference identifier and the stored reference device identifier are inconsistent, the client uses a preset algorithm to encrypt the stored reference device identifier to obtain an encrypted reference device identifier. When the target reference identifier and the encrypted reference device identifier are still inconsistent, the client can determine that the terminal it is using has changed.

[0073] and Figure 2 The solution presented in this application does not rely on third-party components, allowing the terminal to update the identifier. Furthermore, the validity period of the reference identifier in this application is highly variable. Therefore, it can prevent long-term tracking and identification, thereby improving the security of user data when determining whether a device has changed.

[0074] The method for managing identifiers provided in this disclosure is illustrated below with reference to the accompanying drawings:

[0075] Figure 3 This is a schematic diagram of a communication system provided in an embodiment of this application. The communication system may include a client 100, a server 200, and a terminal 300.

[0076] The client 100 can be an application installed on the terminal. In response to a user's operation, the client 100 can send an identification request to the terminal to obtain the terminal's device identifier. After receiving the reference device identifier sent by the terminal, the client 100 can determine whether the terminal has changed based on the received reference device identifier. For example, the client 100 can compare a pre-stored reference device with the received reference device identifier to determine whether the terminal has changed. For details, please refer to the description below, which will not be elaborated here.

[0077] The server 200 can be used to provide data to the client 100. For example, the server 200 can respond to a request from the client 100 and return corresponding data to the client 100. The server can also be used to store a reference device identifier uploaded by the client 100, which can be a reference device identifier obtained by the client 100 from the terminal. The server can also respond to a request from the client 100 and send the stored reference device identifier to the client 100.

[0078] In some embodiments, server 200 may be a single server, or it may be a server cluster consisting of multiple servers. In some embodiments, the server cluster may also be a distributed cluster.

[0079] In this embodiment, server 200 may include multiple application service platforms, each uniquely corresponding to one application installed on a terminal. Server 200 is primarily used to store business data related to the application.

[0080] In this context, terminal 300 can refer to an electronic device that has client 100 installed. Terminal 300 can also be an Internet of Things (IoT) device. For example, terminal 300 can interact with client 100 through an interface of its operating system. For instance, the operating system of terminal 300 can be Android, iOS, HarmonyOS, etc., without limitation. The operating system of terminal 300 can have one or more interfaces that can interact with client 100. For example, client 100 can send request information to terminal 300 through one or more interfaces. Terminal 300 can send response information to client 100 through one or more interfaces.

[0081] In some embodiments, the terminal 300 can be a mobile phone, platform computer, personal computer, or other terminal device, or it can be an application installed on the terminal device. This application embodiment does not impose special limitations on the specific form of the client. It can interact with the user through one or more methods such as a keyboard, touchpad, touchscreen, remote control, voice interaction, or handwriting device.

[0082] The following is combined Figure 3 The communication system shown illustrates the identification management method provided in the embodiments of this application.

[0083] like Figure 4 As shown, the identification management method provided in this application embodiment may include:

[0084] S401. In response to the operation of calling the device identifier at the first moment, the client sends an identifier request message to the terminal. Accordingly, the terminal receives the identifier request message sent by the client at the first moment.

[0085] The client can be Figure 3 Client 100 in the middle. The terminal can be... Figure 3 The terminal 300 in the terminal 300 can also be a part of the device (such as a chip) or program (such as an operating system).

[0086] The operation of retrieving the device identifier can be used to request the device identifier of the client's terminal. For example, this operation could be used for a user logging into the client or for a user making a payment using the client. Identifier request information can be used to request the device identifier of the client's terminal. For example, the identifier request information may include the client's identifier and a timestamp at the current moment. The client's identifier can be used to identify the client. For example, the client's identifier may include one or more of the client's name, type, and version information.

[0087] In one possible implementation, in response to a user's operation on the client at the first moment, the client can be triggered to generate an identification request message and send the identification request message to the client's operating system.

[0088] In one example, such as Figure 5 As shown, in response to a user entering account information (such as username and password) and clicking login through the client's login interface, the client can send an identification request to the operating system of the terminal to trigger the terminal to perform the following step S402.

[0089] S402. In response to the identification request information, the terminal determines the target reference identifier.

[0090] Specifically, when the duration between the first and second moments exceeds a preset duration, the target reference identifier is the second reference device identifier. When the duration between the first and second moments does not exceed the preset duration, the target reference identifier is the first reference device identifier. The second reference device identifier is obtained by encrypting the first reference device identifier according to a preset algorithm.

[0091] The preset algorithm can be used to encrypt the reference device identifier (also known as the tag identification code (TID)). This preset algorithm can be pre-configured on the terminal. For example, the preset algorithm can be a one-way hash function, an encryption algorithm (such as a symmetric encryption algorithm, asymmetric encryption algorithm), etc.

[0092] The first reference device identifier is a reference identifier determined by the terminal at a second time point. The second time point is the moment when the terminal last received the identifier request information sent by the client. The preset duration can be set as needed, for example, it can be 12 hours, a week, etc., without limitation. For example, the first reference device identifier can be determined based on a third reference device identifier. The third reference device identifier can be a reference device identifier determined when the terminal received the identifier request information from the client before the second time point.

[0093] In one possible implementation, the terminal may store a mapping between client identifiers and reference device identifiers. Thus, before determining the target reference identifier for the terminal, the terminal can use the reference device identifier corresponding to the client identifier in the identifier request information from this mapping as the first reference device identifier.

[0094] In one example, the client sends request information to the terminal at times T1, T2, and T3 respectively. Accordingly, the reference device identifier determined by the terminal at time T1 is reference device identifier 1. At time T2, the terminal can encrypt reference device identifier 1 using a preset algorithm to obtain the reference device identifier corresponding to time T2 (referred to as reference device identifier 2). At time T3, the terminal can encrypt reference device identifier 2 using a preset algorithm to obtain the reference device identifier corresponding to time T3 (referred to as reference device identifier 3).

[0095] It should be noted that, in this embodiment of the application, when the terminal receives the client's request information for the first time, it can use a preset algorithm to encrypt the client's identifier to obtain the corresponding reference device identifier. The client's identifier can be carried in the request information, or it can be sent by the client to the terminal's operating system during the installation process.

[0096] For example, if time T1 is the moment when the client first sends an identification request to the terminal, then reference device identifier 1 can be the reference device identifier obtained by the terminal encrypting the client's identifier using a preset algorithm. Thus, if the terminal subsequently receives another request from the client, it can use the preset algorithm to encrypt reference device identifier 1 to obtain the corresponding reference device identifier.

[0097] In one possible implementation, the terminal can determine whether the duration between two consecutive received identification request messages exceeds a preset duration based on the timestamp carried in the identification request message. For example, the timestamp carried in the identification request message sent by the client at the first moment can be t1, and the timestamp carried in the identification request message sent at the second moment can be t2. When t2-t1>the preset duration, the terminal can determine that the duration between the first moment and the second moment exceeds the preset duration. Since the preset duration can be set as needed and is variable, the period for the client to track the terminal can be shortened. In addition, the reference device identifier determined by the terminal is also variable, preventing the terminal from being tracked.

[0098] In another possible implementation, the terminal can be equipped with a timer. The terminal can determine whether the time interval between two consecutive received identification request messages exceeds a preset duration based on the timer's duration. For example, the terminal starts timing when it receives an identification request message from the client. When the terminal receives another identification request message from the client, it stops timing, and the timer records a duration of T. When T is the preset duration, the terminal can determine that the time interval between the two received identification request messages exceeds the preset duration.

[0099] Furthermore, to ensure the security of the identifier, the terminal can use a preset algorithm to encrypt the first reference device identifier and the first random number to obtain the second reference device identifier.

[0100] For example, following the above example, at time T2, the terminal can use a preset algorithm to encrypt the reference device identifier 1 and the random number 1 to obtain the reference device identifier 2. At time T3, the terminal can use the preset algorithm to encrypt the reference device identifier 2 and the random number 2 to obtain the reference device identifier 3. Thus, even if the terminal's reference device identifier 2 is obtained by other devices, those other devices cannot obtain the reference device identifier 3 from it. That is, other devices cannot identify and track the terminal based on the reference device identifier 2, thereby ensuring the security of the reference device identifier and user data.

[0101] It should be noted that the random number used by the terminal to determine the identifier each time can be the same or different. For example, random number 1 and random number 2 can be the same random number or different random numbers, without restriction.

[0102] S403. The terminal sends a target reference identifier to the client. Correspondingly, the client receives the target reference identifier from the terminal.

[0103] The target reference identifier can be used to determine that the terminal has changed when it is inconsistent with the reference device identifier stored on the client and the encrypted reference device identifier obtained by the stored reference device identifier according to a preset algorithm.

[0104] In one example, the terminal may send a first response message to the client. This first response message can be used to determine whether the client's terminal has changed. The first response message may include a target reference identifier.

[0105] In one possible implementation, the terminal can send a first response message to the client through the operating system's interface. Correspondingly, the client can receive a reference device identifier from the terminal through the operating system's interface.

[0106] Thus, each time the terminal receives an identification request from the client, it first determines the time interval between the current received identification request and the previous received identification request. If this time interval exceeds a preset interval, the terminal can encrypt the reference device identifier determined when the client last received the client's identification request using a preset algorithm to obtain the current reference device identifier, and then send this reference device identifier to the client. This allows the client to determine whether the terminal it is using has changed based on the reference device identifier determined previously. In other words, the terminal can determine the current reference device identifier based on the previously determined reference device identifier when receiving the client's identification request, achieving identifier variability. The terminal does not need to send a device identifier to the client, preventing the terminal from being tracked and identified over a long period of time.

[0107] Furthermore, when the terminal determines the reference device identifier each time by encrypting the previously determined reference device identifier and a random number according to a preset algorithm, the first response information may also include the first random number.

[0108] This allows the client to encrypt the previously acquired reference device identifier sent by the terminal and the first random number using a preset algorithm, obtaining an encrypted identifier. Then, the client can determine whether its terminal has changed based on the encrypted identifier and the identifier received from the terminal. This ensures that the number of parameters and random numbers used by the client to determine the reference device identifier are the same as those used by the terminal. It avoids misjudgments by the client when determining whether its terminal has changed due to differences in the parameters used by the client and terminal.

[0109] When the terminal uses the same random number each time it determines the reference device identifier, the first response information may not include the random number. When the first response information does not include a random number, its size can be reduced, saving energy consumption during transmission. Of course, the first response information can also include a random number. This ensures consistency between the client and terminal in determining the reference device identifier.

[0110] It should be noted that when the response information does not include a random number, to avoid discrepancies between the parameters used by the client to encrypt and determine the stored reference device identifier and the parameters used by the terminal, the terminal may send a random number to the client during the installation process. Alternatively, the client may actively obtain a random number during the installation process.

[0111] S404. The client obtains the reference device identifier for storage.

[0112] The stored reference device identifier can refer to the reference device identifier previously received from the terminal and stored by the client. That is, each time the client receives a reference device identifier sent by the terminal, it can store it. For example, the client can upload the received reference device identifier to the server, so that the server stores the reference device identifier received by the client. Thus, subsequently, when the client needs to retrieve the stored reference device identifier, it can retrieve the previously stored reference device identifier from the server.

[0113] For example, a server can store the mapping between client identifiers and reference device identifiers uploaded by the client. A client can send its identifier to the server to retrieve the previously stored reference device identifier. The server can then determine the reference device identifier previously received by the client and sent by the terminal, based on the client's identifier and the stored mapping. After determining the reference device identifier uploaded by the client, the server can send that reference device identifier back to the client. In this way, the client can obtain the stored reference device identifier.

[0114] Furthermore, when the reference device identifier received by the client from the terminal is inconsistent with the stored reference device identifier, the client can update the stored reference device identifier. That is, the client can send the reference device identifier received from the terminal to the server, so that the server can replace the previously received reference device identifier in its storage with the currently uploaded one. This ensures the validity and reliability of the stored reference device identifier.

[0115] For example, the server currently stores the device identifier as reference device identifier 1. When the client receives a reference device identifier 2 sent by the terminal that differs from reference device identifier 1, the client can send reference device identifier 2 to the server. When the server receives the reference device identifier 2 uploaded by the client, it can store reference device identifier 2. To save server memory, the server can also delete reference device identifier 1.

[0116] S405. When the target reference identifier is inconsistent with the stored reference device identifier, the client encrypts the stored device identifier according to a preset algorithm to obtain the encrypted reference device identifier.

[0117] The preset algorithm can be referred to in the description of S402 above, and will not be repeated here. When the preset algorithm is pre-configured on the terminal, the client can call the preset algorithm through the terminal's operating system. Alternatively, the preset algorithm can be negotiated between the client and the terminal through a preset protocol during the installation process. In this way, the consistency of the algorithm used by the client and the terminal in determining the reference device identifier can be guaranteed.

[0118] It should be noted that when the target reference identifier is inconsistent with the stored reference device identifier, since the target reference identifier may be the identifier obtained by the terminal using a preset algorithm to encrypt the previously determined reference device identifier, in order to verify whether the terminal where the client is located has changed, the client can use a preset algorithm to encrypt the stored reference device identifier to obtain the encrypted reference device identifier.

[0119] Furthermore, when the client receives a random number from the terminal, it can encrypt the stored reference device identifier and the random number using a preset algorithm to obtain an encrypted reference device identifier. Thus, since the target reference identifier is obtained by the terminal encrypting the previously determined reference device identifier and random number using a preset algorithm, it ensures that the terminal and client use the same random number when encrypting the reference device identifier.

[0120] When the client does not receive a random number from the terminal, the client can encrypt the stored reference device identifier and the random number obtained during installation according to a preset algorithm to obtain the encrypted reference device identifier.

[0121] S406. When the encrypted reference device identifier is inconsistent with the target reference identifier, the client determines that the terminal it is on has changed.

[0122] In this context, a change in the client's terminal can mean that the client's terminal at the first moment is different from the terminal at the second moment. When the terminal at the first moment is different from the terminal at the second moment, the client can determine that the terminal has changed.

[0123] In this way, the client can determine whether its current terminal has changed based on the reference device identifier received from the terminal and the stored reference device identifier. When the reference device identifier received from the terminal does not match the stored reference device identifier, the client can also encrypt the stored reference device identifier according to a preset algorithm and check whether the received reference device identifier matches the encrypted reference device identifier. Therefore, the client can accurately determine whether its current terminal has changed based on the consistency between the received reference device identifier and the encrypted reference device identifier.

[0124] In this embodiment, in response to the operation of calling the device identifier at the first moment, the client can send an identifier request message to the terminal to request the acquisition of the terminal's device identifier. After receiving the identifier request message, if the terminal determines that the time interval between the first moment and the moment when it last received the identifier request message from the client exceeds a preset time interval, the terminal can use a preset algorithm to encrypt the previously determined reference device identifier to obtain an encrypted reference device identifier. The terminal can send the encrypted reference device identifier to the client, and the client can determine whether its terminal has changed based on the encrypted reference device identifier. Since the encrypted identifier is obtained by the terminal encrypting the previously determined identifier using a preset algorithm, the encrypted identifier is unique; that is, the encrypted identifier can uniquely identify the terminal without using the terminal's device identifier.

[0125] Additionally, after receiving the reference device identifier from the terminal, the client can compare the received reference device identifier with the stored reference device identifier. If they do not match, the client can encrypt the stored reference device identifier using a preset algorithm, thus obtaining an encrypted identifier. Since the reference device identifier stored by the client can be the reference device identifier of the client's previous terminal, if the reference device identifier received by the client does not match the stored reference device identifier or the encrypted reference device identifier, it indicates that the client's current terminal is different from its previous terminal; that is, the client's terminal has changed.

[0126] and Figure 2 The solution presented in this application does not rely on third-party components, allowing the terminal to update the identifier. Furthermore, the validity period of the reference identifier in this application is highly variable. Therefore, it can prevent long-term tracking and identification, thereby improving the security of user data when determining whether a device has changed.

[0127] In one possible embodiment, when the duration between the first moment and the second moment does not exceed a preset duration, the target reference identifier is the first reference device identifier.

[0128] The first reference device identifier and preset duration can be referred to in the description of S402 above, and will not be repeated here.

[0129] Based on this embodiment, if the time interval between consecutive identification request messages received by the terminal from the client does not exceed a preset time interval, it indicates that the client is calling the device identification frequently. When the client is calling the terminal's device identification frequently, the terminal can send the previously determined identification to the client without needing to perform encryption again. This reduces the number of operations performed by the terminal and lowers its computational burden.

[0130] In one possible implementation, such as Figure 6 As shown, the method provided in this application embodiment may further include S601.

[0131] S601. When the target reference identifier is consistent with the stored reference device identifier, or when the target reference identifier is consistent with the encrypted reference device identifier, the client determines that the terminal it is on has not changed.

[0132] In this context, "the terminal where the client is located has not changed" can mean that the terminal the client is currently on is the same as the terminal it was on when the device identifier was last called.

[0133] It should be noted that when the reference device identifier received from the terminal is consistent with the stored reference device identifier, the client does not need to encrypt the stored reference device identifier, that is, the client does not need to execute the above S406; when the reference device identifier received from the terminal is inconsistent with the stored reference device identifier, the client can execute the above S406 to further determine whether the terminal has changed.

[0134] The technical solution provided by the above embodiments brings at least the following beneficial effects: As can be seen from the above steps, when the stored reference device identifier is consistent with the received reference device identifier, or when the received reference device identifier is consistent with the encrypted reference device identifier, the client can accurately determine that the client it is currently in has not changed.

[0135] In one possible implementation, such as Figure 7 As shown, the method provided in the embodiments of this application may further include S701 to S703.

[0136] S701, The client sends an identification request message to the terminal for the first time. Correspondingly, the terminal receives the identification request message sent by the client for the first time.

[0137] The identification request information initially sent by the client to the terminal can be used to obtain the terminal's device identifier. For example, this identification request information may include the client's identifier.

[0138] In one possible implementation, the client can send an identification request to its terminal for the first time in response to the installation operation. That is, the client can send an identification request to its terminal during the installation process.

[0139] In another possible implementation, the client can respond to the user's first login operation by sending an identification request message to the terminal it is on for the first time.

[0140] The first login operation can refer to the first time a user enters their account and password on the client's login interface.

[0141] In another possible implementation, when the client has payment functionality, the client can send an identification request to the terminal it is on for the first time in response to the user's first payment operation.

[0142] The first payment by a user can refer to the action taken when the user uses the payment function of the client. For example, it could be the action of binding a bank account for the first time, or the action of setting a preset amount for the user to pay other accounts using the client.

[0143] S702. When the client first receives the identification request information sent by the client, the terminal encrypts the client's identification according to a preset algorithm to obtain the third reference device identification.

[0144] The second reference device identifier can be obtained based on the third reference device identifier. For example, if the second moment is the moment after the client first sends the identifier request information to the terminal, the second reference device identifier can be obtained by encrypting the third reference device identifier according to a preset algorithm.

[0145] S703: The terminal sends a third reference device identifier to the client. Correspondingly, the client receives the third reference device identifier sent by the terminal.

[0146] The third reference device identifier can be used to determine whether the terminal where the client is located has changed.

[0147] In one example, the third reference device identifier may be carried in the second response information sent by the terminal to the client.

[0148] Furthermore, the terminal can also store the mapping between client identifiers and reference device identifiers. This way, when the terminal receives another identifier request from a client, it can determine the corresponding reference device identifier based on this mapping. This avoids the situation where the terminal has multiple clients installed, making it impossible to determine the reference device identifier for each client. Simultaneously, when the terminal has multiple clients installed, it only needs to store the client identifier or the reference device identifier determined based on the client identifier. Subsequently, it can determine the corresponding reference device identifier simply by using the previously stored reference device identifier, eliminating the need to store information from other clients and saving terminal memory.

[0149] In one example, after the terminal obtains the fourth reference device identifier using a preset algorithm, it can replace the reference device identifier in the stored correspondence with the fourth reference device identifier. In this way, the terminal device ensures the accuracy of the stored reference device identifier by dynamically storing it. At the same time, it can also reduce the terminal's memory usage.

[0150] like Figure 8 As shown, after the client receives the third reference device identifier sent by the terminal, it can store the third reference device identifier on the server. In this way, the client can retrieve the third reference device identifier from the server the next time to determine whether the terminal it is on has changed.

[0151] In one example, when the terminal encrypts the client's identifier and a second random number according to a preset algorithm to obtain a third reference device identifier, the second response information may also include the second random number. Thus, if the reference device identifier received by the client next time is inconsistent with the third reference device identifier, the client can encrypt its own identifier and the second random number according to the preset algorithm to obtain an encrypted reference device identifier. Furthermore, the client can accurately determine whether the terminal has changed based on this encrypted reference device identifier and the reference device identifier received from the terminal.

[0152] The technical solution provided by the above embodiments brings at least the following beneficial effects: As can be seen from the above steps, when the client sends an identification request to the terminal for the first time, the terminal can encrypt the client's identification according to a preset algorithm to obtain a reference device identifier, and then send the reference device identifier to the client. Subsequently, the client can determine whether its terminal has changed based on the reference device identifier. That is, the client can determine whether its terminal has changed without the terminal sending a device identifier to the client.

[0153] In one possible implementation, such as Figure 9As shown, when the preset algorithm is a one-way hash function, both the terminal and the client can generate a hash chain based on the previously determined TID according to the preset algorithm. For example, the hash chain of the terminal can be TID1-TID2-TID3-……-TIDn, and correspondingly, the hash chain of the client can be TID`1-TID`2-TID`3-……-TID`n.

[0154] TID2 is obtained based on TID1, and TID3 is obtained based on TID2. TID`2 is obtained based on TID`1, and TID`3 is obtained based on TID`2.

[0155] The terminal can slide along the hash chain on its own device. If the time interval between the identification request messages received by the terminal from the client does not exceed a preset time, the TID returned by the terminal to the client remains unchanged. That is, the terminal sends the uploaded and determined TID to the client. If the time interval between the identification request messages received by the terminal from the client exceeds the preset time, the terminal slides to the next TID through calculation and returns that TID to the client. The client can determine whether its terminal has changed based on this TID.

[0156] The client can also slide along the hash chain on its local machine. When the received TID sent by the terminal differs from the stored TID, the terminal can slide to the next TID and compare it again with the received TID. If the next TID still does not match the received TID, it indicates that the client's terminal has changed.

[0157] It is understood that, in actual implementation, the terminal described in the embodiments of this disclosure may include one or more hardware structures and / or software modules for implementing the management method of the aforementioned corresponding identifier, and these hardware structures and / or software modules may constitute an electronic device. Those skilled in the art should readily recognize that, in conjunction with the algorithm steps of the various examples described in the embodiments disclosed herein, this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0158] Based on this understanding, this disclosure also provides an identification management device. Figure 10 A schematic diagram of the structure of an identifier management device provided in an embodiment of this disclosure is shown. This device is applied to a client, such as… Figure 10As shown, the device may include: a transmitting unit 101, a receiving unit 102, an acquiring unit 103, and a processing unit 104.

[0159] The sending unit 101 is configured to, in response to the operation of calling the device identifier at the first moment, send identifier request information for obtaining the device identifier of the terminal to the terminal where the client is located. For example, the sending unit 101 can be used to perform... Figure 4 S401 in the middle.

[0160] The receiving unit 102 is used to receive a target reference identifier sent by the terminal. When the duration between the first time and the second time exceeds a preset duration, the target reference identifier is a second reference identifier. The second reference device identifier is a reference identifier obtained by the terminal encrypting the first reference device identifier according to a preset algorithm. The first reference device identifier is the reference identifier determined by the terminal when it last received the identifier request information sent by the client at the second time.

[0161] The acquisition unit 103 is used to acquire the reference device identifier stored by the client. For example, the acquisition unit 103 can be used to perform... Figure 4 S404.

[0162] The processing unit 104 is configured to, when the target reference identifier is inconsistent with the stored reference device identifier, encrypt the stored reference device identifier according to a preset algorithm to obtain an encrypted reference device identifier; and when the target reference identifier is inconsistent with the encrypted reference device identifier, determine that the terminal where the client is located has changed. For example, the processing unit 104 can be used to execute... Figure 4 S405 and S406 in the example.

[0163] Optionally, when the duration between the first moment and the second moment does not exceed a preset duration, the target reference identifier is the first reference device identifier.

[0164] Optionally, the processing unit 104 is further configured to determine that the terminal where the client is located has not changed when the target reference identifier matches the stored reference device identifier or the target reference identifier matches the encrypted reference device identifier. For example, the processing unit 104 may be configured to perform... Figure 6 S601 in the middle.

[0165] Optionally, the processing unit 104 is also configured to replace the stored reference device identifier with the target reference identifier when it is determined that the terminal where the client is located has changed.

[0166] Optionally, the sending unit 101 is further configured to send an identification request message including the client's identifier to the terminal for the first time. The receiving unit is further configured to receive and store a third reference device identifier sent by the terminal, wherein the third reference device identifier is obtained by the terminal encrypting the client's identifier according to a preset algorithm, and the first reference device identifier is obtained based on the third reference device identifier. For example, the sending unit 101 can be used to perform... Figure 7 S701 in the middle.

[0167] Optionally, the receiving unit 102 is further configured to receive a first random number sent by the terminal. The processing unit is specifically configured to encrypt the stored reference device identifier and the first random number according to a preset algorithm to obtain an encrypted reference device identifier.

[0168] Figure 11 A schematic diagram of the structure of an identifier management device provided in an embodiment of this disclosure is shown. This device is applied to a terminal where a client is located. The device includes a receiving unit 111, a determining unit 112, and a sending unit 113.

[0169] The receiving unit 111 is used to receive an identification request information sent by the client in response to the operation of calling the device identifier at a first moment. The identification request information is used to request to obtain the device identifier of the terminal.

[0170] The determining unit 112 is configured to determine a target reference identifier for the terminal in response to the identifier request information. When the time interval between the first moment and the second moment after which the identifier request information sent by the client was last received exceeds a preset time interval, the target reference identifier is a second reference device identifier. The second reference device identifier is obtained by encrypting the first reference device identifier according to a preset algorithm. The first reference device identifier is the reference identifier determined when the identifier request information sent by the client is received at the second moment. For example, the determining unit 112 can be used to perform... Figure 4 S402 in the middle.

[0171] The sending unit 113 is used to send a target reference identifier to the client. The target reference identifier is used to determine if the terminal has changed when it is inconsistent with a reference device identifier stored by the client and an encrypted reference device identifier obtained from the stored reference device identifier according to a preset algorithm. For example, the sending unit 113 can be used to perform... Figure 4 S403.

[0172] Optionally, when the duration between the first moment and the second moment does not exceed a preset duration, the target reference identifier is the first reference device identifier.

[0173] Optionally, such as Figure 11As shown, the device also includes a processing unit 114. The processing unit 114 is further configured to, upon first receiving an identification request message including the client's identifier sent by the client, encrypt the client's identifier according to a preset algorithm to obtain a third reference device identifier. The sending unit 113 is further configured to send second response information including the third reference device identifier to the terminal, wherein the first reference device identifier is obtained based on the third reference device identifier. For example, the sending unit 113 can be used to perform... Figure 7 S702 in the middle.

[0174] Optionally, the identification request information includes the client's identifier, and the terminal also stores the correspondence between the client's identifier and the reference device identifier. The processing unit 114 is further configured to replace the reference device identifier in the correspondence with the fourth reference device identifier after obtaining the fourth reference device identifier based on a preset algorithm.

[0175] Optionally, the determining unit 112 is further configured to, before determining the target reference identifier of the terminal, use the reference device identifier corresponding to the client in the identifier request information in the correspondence relationship as the first reference device identifier.

[0176] Optionally, the sending unit 113 is further configured to send a first random number to the client. The second reference device identifier being a reference identifier obtained by encrypting the first reference device identifier according to a preset algorithm means that the second reference device identifier is a reference identifier obtained by encrypting the first reference device identifier and the first random number according to a preset algorithm.

[0177] As described above, the embodiments of this disclosure can divide the identification management device into functional modules according to the above method examples. The integrated modules can be implemented in hardware or as software functional modules. Furthermore, it should be noted that the module division in these embodiments is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into a single processing module.

[0178] Regarding the identification management device in the above embodiments, the specific methods of operation of each module and its beneficial effects have been described in detail in the foregoing method embodiments, and will not be repeated here.

[0179] like Figure 12 As shown, this disclosure also provides a communication system, which may include a client 121 and a terminal 122. The client 121 can be used to perform the above-described... Figure 4 , Figure 6 and Figure 7The actions performed by the client in any of the accompanying drawings, for example, can be used to execute S401, S404, S405, S406, and S601. Terminal 122 can be used to execute the above. Figure 4 , Figure 6 and Figure 7 The actions performed by the terminal in any of the accompanying drawings, for example, can be used to execute S402, S403, S702, and S703.

[0180] This disclosure also provides an identification management device. Figure 13 A schematic diagram of the structure of an identifier management device provided in an embodiment of this disclosure is shown. The identifier management device may include at least one processor 131, a communication bus 132, a memory 133, and at least one communication interface 134.

[0181] Processor 131 may be a central processing unit (CPU), a microprocessor unit, an ASIC, or one or more integrated circuits for controlling the execution of programs according to the present disclosure. As an example, combined with... Figure 11 The processing unit 114 in the identification management device performs the same functions as... Figure 13 The processor 131 in the middle performs the same function.

[0182] The communication bus 132 may include a path for transmitting information between the aforementioned components.

[0183] Communication interface 134 uses any transceiver-like device for communication with other devices or communication networks, such as servers, Ethernet, radio access networks (RAN), wireless local area networks (WLAN), etc. As an example, combined with... Figure 10 The function implemented by the acquisition unit 103 in the identification management device is the same as Figure 13 The communication interface 114 in the middle performs the same function.

[0184] Memory 133 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. Memory may exist independently and be connected to the processing unit via a bus. Memory may also be integrated with the processing unit.

[0185] The memory 133 stores the application code that executes the present invention, and its execution is controlled by the processor 131. The processor 131 executes the application code stored in the memory 133 to implement the functions of the method of the present invention.

[0186] In a specific implementation, as one embodiment, the processor 131 may include one or more CPUs, for example... Figure 13 CPU0 and CPU1 in the CPU.

[0187] In a specific implementation, as one example, the terminal may include multiple processors, for example... Figure 13 Processors 131 and 135 are described herein. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor here may refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0188] In a specific implementation, as one embodiment, the identification management device may further include an input device 136 and an output device 137. The input device 136 and output device 137 communicate and can accept user input in various ways. For example, the input device 136 may be a mouse, keyboard, touchscreen device, or sensor device. The output device 137 communicates with the processor 131 and can display information in various ways. For example, the output device 131 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, etc.

[0189] Those skilled in the art will understand that Figure 13 The structure shown does not constitute a limitation on the management device for the identifier, and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0190] This disclosure also provides a computer-readable storage medium including instructions stored thereon, which, when executed by a processor of a computer device, enables the computer to perform the identification management method provided in the embodiments described above. For example, the computer-readable storage medium may be a memory 133 including instructions, which may be executed by a processor 131 of an identification management device to complete the method described above. As another example, the computer-readable storage medium may be a memory 133 including instructions, which may be executed by a processor 131 of a server to complete the method described above. Optionally, the computer-readable storage medium may be a non-transitory computer-readable storage medium, such as a ROM, RAM, CD-ROM, magnetic tape, floppy disk, or optical data storage device.

[0191] This disclosure also provides a computer program product including computer instructions that, when executed on a processor of an identification management device, cause the identification management device to perform the above-described... Figures 4-7 The management method of the markings shown in any of the attached figures.

[0192] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0193] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A method for managing identifiers, characterized in that, Applied to a client, the method includes: In response to the operation of calling the device identifier at the first moment, an identifier request information is sent to the terminal where the client is located. The identifier request information is used to request to obtain the device identifier of the terminal. The terminal receives a target reference identifier and obtains a reference device identifier stored by the client. When the duration between the first time and the second time exceeds a preset duration, the target reference identifier is a second reference device identifier. The second reference device identifier is a reference identifier obtained by the terminal encrypting the first reference device identifier according to a preset algorithm. The first reference device identifier is a reference identifier determined by the terminal when it last received the identifier request information sent by the client at the second time. Receive the first random number sent by the terminal; When the target reference identifier is inconsistent with the stored reference device identifier, the stored reference device identifier and the first random number are encrypted according to the preset algorithm to obtain the encrypted reference device identifier. When the target reference identifier is inconsistent with the encrypted reference device identifier, it is determined that the terminal where the client is located has changed; The identification request information, which includes the identifier of the client, is sent to the terminal for the first time. The terminal receives and stores a third reference device identifier sent by the terminal. The third reference device identifier is obtained by the terminal encrypting the identifier of the client according to the preset algorithm. The first reference device identifier is obtained based on the third reference device identifier.

2. The method according to claim 1, characterized in that, When the duration between the first moment and the second moment does not exceed the preset duration, the target reference identifier is the first reference device identifier.

3. The method according to claim 1, characterized in that, The method further includes: When the target reference identifier is consistent with the stored reference device identifier, or when the target reference identifier is consistent with the encrypted reference device identifier, it is determined that the terminal where the client is located has not changed.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: When it is determined that the terminal where the client is located has changed, the stored reference device identifier is replaced with the target reference identifier.

5. A method for managing identification, characterized in that, The method, applied to the terminal where the client is located, includes: The terminal receives an identification request message sent by the client in response to an operation to call the device identifier at a first moment. The identification request message is used to request the device identifier of the terminal. In response to the identification request information, a target reference identifier for the terminal is determined; when the duration between the first time and the second time exceeds a preset duration, the target reference identifier is a second reference device identifier; the second reference device identifier is a reference identifier obtained by encrypting the first reference device identifier according to a preset algorithm, and the first reference device identifier is a reference identifier determined when the identification request information sent by the client was received last time at the second time. Send the target reference identifier to the client. The target reference identifier is used to determine that the terminal has changed when it is inconsistent with the reference device identifier stored by the client and the encrypted reference device identifier obtained by the stored reference device identifier according to the preset algorithm. Send a first random number to the client; The second reference device identifier is a reference identifier obtained by encrypting the first reference device identifier according to a preset algorithm. This means that the second reference device identifier is a reference identifier obtained by encrypting the first reference device identifier and the first random number according to a preset algorithm. When the identification request information sent by the client is received for the first time, the client's identification is encrypted according to the preset algorithm to obtain the third reference device identification; The identification request information includes the identifier of the client, and the first reference device identifier is obtained based on the third reference device identifier; The third reference device identifier is sent to the client.

6. The method according to claim 5, characterized in that, When the duration between the first moment and the second moment does not exceed the preset duration, the target reference identifier is the first reference device identifier.

7. The method according to claim 5 or 6, characterized in that, The identification request information includes the client's identifier, and the terminal also stores a correspondence between the client's identifier and a reference device identifier. The method further includes: After obtaining the fourth reference device identifier based on a preset algorithm, the reference device identifier in the correspondence is replaced with the fourth reference device identifier.

8. The method according to claim 7, characterized in that, Before determining the target reference identifier of the terminal, the method further includes: The reference device identifier that corresponds to the client identifier in the identifier request information in the correspondence is taken as the first reference device identifier.

9. A device for managing identification, characterized in that, Applied to a client, the device includes a sending unit, a receiving unit, a processing unit, and a determining unit; The sending unit is configured to send an identifier request message to the terminal where the client is located in response to the operation of calling the device identifier at the first moment. The identifier request message is used to request to obtain the device identifier of the terminal. The receiving unit is configured to receive a target reference identifier sent by the terminal and obtain a reference device identifier stored by the client; when the duration between the first time and the second time exceeds a preset duration, the target reference identifier is a second reference device identifier, the second reference device identifier is a reference identifier obtained by the terminal encrypting the first reference device identifier according to a preset algorithm, and the first reference device identifier is a reference identifier determined by the terminal when it last received the identifier request information sent by the client at the second time. The receiving unit is further configured to receive a first random number sent by the terminal; The processing unit is configured to, when the target reference identifier is inconsistent with the stored reference device identifier, encrypt the stored reference device identifier and the first random number according to the preset algorithm to obtain the encrypted reference device identifier. The determining unit is used to determine that the terminal where the client is located has changed when the target reference identifier is inconsistent with the encrypted reference device identifier; The sending unit is further configured to send identification request information to the terminal for the first time, the identification request information including the identifier of the client; The receiving unit is further configured to receive and store a third reference device identifier sent by the terminal, wherein the third reference device identifier is an identifier obtained by the terminal encrypting the identifier of the client according to the preset algorithm, and the first reference device identifier is obtained based on the third reference device identifier.

10. The apparatus according to claim 9, characterized in that, When the duration between the first moment and the second moment does not exceed the preset duration, the target reference identifier is the first reference device identifier.

11. The apparatus according to claim 9, characterized in that, The processing unit is further configured to: When the target reference identifier is consistent with the stored reference device identifier, or when the target reference identifier is consistent with the encrypted reference device identifier, it is determined that the terminal where the client is located has not changed.

12. The apparatus according to claim 11, characterized in that, The processing unit is further configured to: When it is determined that the terminal where the client is located has changed, the stored reference device identifier is replaced with the target reference identifier.

13. A device for managing identification, characterized in that, The device, which is applied to the terminal where the client is located, includes: a receiving unit, a determining unit, a processing unit, and a sending unit; The receiving unit is configured to receive an identifier request information sent by the client in response to the operation of calling the device identifier at a first moment, the identifier request information being used to request the acquisition of the device identifier of the terminal; The determining unit is configured to determine the target reference identifier of the terminal in response to the identifier request information; when the duration between the first time and the second time exceeds a preset duration, the target reference identifier is a second reference device identifier; the second reference device identifier is a reference identifier obtained by encrypting the first reference device identifier according to a preset algorithm, and the first reference device identifier is a reference identifier determined when the identifier request information sent by the client was received last time at the second time. The sending unit is configured to send the target reference identifier to the client. The target reference identifier is used to determine that the terminal has changed when it is inconsistent with the reference device identifier stored by the client and the encrypted reference device identifier obtained by the stored reference device identifier according to the preset algorithm. The sending unit is further configured to send a first random number to the client; The second reference device identifier is a reference identifier obtained by encrypting the first reference device identifier according to a preset algorithm. This means that the second reference device identifier is a reference identifier obtained by encrypting the first reference device identifier and the first random number according to a preset algorithm. The processing unit is further configured to, upon first receiving the identifier request information sent by the client, encrypt the client's identifier according to the preset algorithm to obtain a third reference device identifier; The identification request information includes the identifier of the client, and the first reference device identifier is obtained based on the third reference device identifier; The sending unit is also configured to send the third reference device identifier to the client.

14. The apparatus according to claim 13, characterized in that, When the duration between the first moment and the second moment does not exceed the preset duration, the target reference identifier is the first reference device identifier.

15. The apparatus according to claim 13 or 14, characterized in that, The identification request information includes the client's identifier, and the terminal also stores a correspondence between the client's identifier and a reference device identifier. The processing unit is further configured to: After obtaining the fourth reference device identifier based on a preset algorithm, the reference device identifier in the correspondence is replaced with the fourth reference device identifier.

16. The apparatus according to claim 15, characterized in that, The processing unit is further configured to: The reference device identifier that corresponds to the client identifier in the identifier request information in the correspondence is taken as the first reference device identifier.

17. An electronic device, characterized in that, The electronic device includes: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the identification management method as described in any one of claims 1-8.

18. A computer-readable storage medium storing instructions thereon, characterized in that, When the instructions in the computer-readable storage medium are executed by the processor of the electronic device, the electronic device is able to perform the identification management method as described in any one of claims 1-8.

19. A computer program product comprising instructions, characterized in that, When the instruction is executed by the processor, the method for managing the identifier as described in any one of claims 1-8 is implemented.

Images