A method for managing an anonymous device identifier, a terminal, and a storage medium

Abstract

This invention discloses a method, terminal, and storage medium for managing anonymous device identifiers, comprising: acquiring anonymous device identifiers from a device system and configuring an identifier mapping table based on the anonymous device identifiers; determining a unique device identifier and preset instruction rules based on the configured identifier mapping table, and sending an update operation instruction for the anonymous device identifiers to the device system; acquiring the updated anonymous device identifiers from the device system, and updating and storing the identifier mapping table based on the updated anonymous device identifiers; wherein the updated anonymous device identifiers are either the device system's updated anonymous device identifier on / off state or the identifiers after the update. This invention establishes an anonymous device identifier management mechanism to control anonymous device identifiers in the background, effectively preventing the malicious collection of personal information without the user's awareness, and effectively protecting the security of user personal information.

Description

Technical Field

[0001] This invention relates to the field of mobile devices, and more particularly to a method, terminal, and storage medium for managing anonymous device identifiers. Background Technology

[0002] Currently, personal information includes descriptions of a person's frequently used devices, such as hardware serial numbers, device MAC addresses, software lists, and unique device identifiers (e.g., IMEI / Android ID / IDFA / OpenUDID / GUID / SIM card / IMSI information). This type of information requires authorization before it can be obtained. In accordance with relevant regulations, the OTT (Over-The-Top) industry has established a supplementary device identifier mechanism. UDIDs (Unique Device Identifiers) are only obtained from authorized applications, while OAIDs (Anonymous Device Identifiers) require user authorization before use, and users can reset their OAIDs.

[0003] However, although the OTT industry has established a supplementary device identifier mechanism, existing technologies do not control the device identifiers that users have enabled, nor do they have a corresponding server-side control mechanism for device identifiers. Even when users enable device identifiers without their knowledge, personal information can still be maliciously collected.

[0004] Therefore, existing technologies still need improvement. Summary of the Invention

[0005] The technical problem to be solved by the present invention is to provide a method, terminal and storage medium for managing anonymous device identifiers, in order to solve the problem of malicious collection of users' personal information due to the lack of a server-side management mechanism for anonymous device identifiers.

[0006] The technical solution adopted by this invention to solve the technical problem is as follows:

[0007] In a first aspect, the present invention provides a method for controlling anonymous device identifiers, comprising:

[0008] Obtain the anonymous device identifier of the device system, and configure the identifier mapping table according to the anonymous device identifier;

[0009] Based on the configuration identifier mapping table, a unique device identifier code and preset instruction rules are determined, and an update operation instruction for the anonymous device identifier is sent to the device system.

[0010] Obtain the updated anonymous device identifier of the device system, and update and store the identifier mapping table according to the updated anonymous device identifier; wherein, the updated anonymous device identifier is the identifier after the device system updates the anonymous device identifier switch state or the identifier after updating the anonymous device identifier.

[0011] In one implementation of the present invention, obtaining the anonymous device identifier of the device system and configuring the identifier mapping table according to the anonymous device identifier includes:

[0012] Configure an identifier mapping table based on the unique device identifier of the device system;

[0013] The mapping relationship between the unique device identifier of the device system and the corresponding anonymous device identifier is stored in the identifier mapping table.

[0014] In one implementation of the present invention, configuring the identifier mapping table based on the unique device identifier code of the device system includes:

[0015] Record the matching relationship between the unique device identifier and the anonymous device identifier in the device system, and configure an identifier mapping table; the matching relationship includes the matching relationship between a unique device identifier and an anonymous device identifier in the device system;

[0016] In one implementation of the present invention, the configuration identifier mapping table includes:

[0017] If the anonymous device identifier in the identifier mapping table is updated or reset, the identifier mapping table becomes invalid.

[0018] In one implementation of the present invention, the step of determining a unique device identifier code and a preset instruction rule based on the configuration identifier mapping table, and sending an update instruction for the anonymous device identifier to the device system, includes:

[0019] Obtain the current anonymous device identifier, search the identifier mapping table, and determine whether the current anonymous device identifier matches the anonymous device identifier in the identifier mapping table;

[0020] If a matching relationship exists, it is determined whether the matching relationship has expired according to preset rules;

[0021] If no matching relationship exists, a shutdown command or a reset command is issued to the device system.

[0022] In one implementation of the present invention, determining whether the matching relationship has expired according to a preset rule includes:

[0023] If the matching relationship expires, the matching relationship will be added to the timeout list, and an update suggestion message will be sent to the device system.

[0024] In one implementation of the present invention, issuing a shutdown command or reset command to the device system includes:

[0025] Determine whether a matching relationship exists in the timeout list;

[0026] If a matching relationship exists in the timeout list, a shutdown command is issued to the device system;

[0027] If no matching relationship exists in the timeout list, a reset command is issued to the device system.

[0028] In one implementation of the present invention, the update suggestion information includes:

[0029] Set the current anonymous device identifier status to off; and / or replace the current anonymous device identifier with a new anonymous device identifier.

[0030] In a second aspect, the present invention also provides a terminal, comprising: a processor and a memory, the memory storing an execution program for the management of anonymous device identifiers, the execution program for the management of anonymous device identifiers being executed by the processor for implementing the steps of the anonymous device identifier management method as described in the first aspect.

[0031] Thirdly, the present invention also provides a storage medium, which is a computer-readable storage medium, storing an execution program for the management of anonymous device identifiers, wherein the execution program for the management of anonymous device identifiers, when executed by a processor, is used to implement the steps of the method for managing anonymous device identifiers as described in the first aspect.

[0032] The present invention, by employing the above technical solution, has the following effects:

[0033] This invention discloses a method, terminal, and storage medium for managing anonymous device identifiers, comprising: acquiring anonymous device identifiers from a device system and configuring an identifier mapping table based on the anonymous device identifiers; determining a unique device identifier and preset instruction rules based on the configured identifier mapping table, and sending an update operation instruction for the anonymous device identifiers to the device system; acquiring the updated anonymous device identifiers from the device system, and updating and storing the identifier mapping table based on the updated anonymous device identifiers; wherein the updated anonymous device identifiers are either the device system's updated anonymous device identifier on / off state or the identifiers after the update. This invention establishes a server-side management mechanism for anonymous device identifiers, enabling background control of anonymous device identifiers, effectively preventing the malicious collection of personal information without the user's awareness, and effectively protecting the security of user personal information. Attached Figure Description

[0034] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the structures shown in these drawings without creative effort.

[0035] Figure 1 This is a flowchart of a method for managing anonymous device identifiers in one implementation of the present invention.

[0036] Figure 2 This is a functional schematic diagram of the terminal in one implementation of the present invention.

[0037] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0038] To facilitate understanding of this application, a more complete description will be provided below with reference to the accompanying drawings. Preferred embodiments of this application are shown in the drawings. However, this application can be implemented in many different forms and is not limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the disclosure of this application.

[0039] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein in the specification of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application.

[0040] Exemplary methods

[0041] Currently, personal information includes descriptions of a person's frequently used devices, such as hardware serial numbers, device MAC addresses, software lists, and unique device identifiers (e.g., IMEI / Android ID / IDFA / OpenUDID / GUID / SIM card / IMSI information). This type of information requires authorization and consent to be obtained. In accordance with relevant regulations, the OTT sector has established a supplementary device identifier mechanism, obtaining UDID only from authorized applications. OAID requires user authorization before use, and users can reset their OAID.

[0042] However, although the OTT industry has established a supplementary device identifier mechanism, existing technologies do not control the device identifiers that users have enabled, nor do they have a corresponding server-side control mechanism for device identifiers. Even when users enable device identifiers without their knowledge, personal information can still be maliciously collected.

[0043] To address the aforementioned technical issues, this invention provides a method for managing anonymous device identifiers. By establishing a server-side management mechanism for anonymous device identifiers, the method enables background control of anonymous device identifiers, effectively preventing the malicious collection of personal information without the user's knowledge and effectively protecting the security of the user's personal information.

[0044] like Figure 1 As shown, this embodiment of the invention provides a method for controlling anonymous device identifiers, including the following steps:

[0045] Step S100: Obtain the anonymous device identifier of the device system, and configure the identifier mapping table according to the anonymous device identifier.

[0046] A unique device identifier is a unique hardware identifier for a device, generated during device manufacturing based on specific hardware information. It can be used for verifying the device's production environment and legitimacy. An anonymous device identifier is an identifier that can be linked to all application data; it is generated immediately upon the first startup of the mobile smart terminal system. In this embodiment, an identifier mapping table is configured to manage anonymous device identifiers. The unique device identifier is used as the primary key to establish a matching relationship with all associated anonymous device identifiers, thereby achieving the goal of managing the anonymous device identifier server.

[0047] Specifically, in one implementation of this embodiment, step S100 includes the following steps:

[0048] Step S101: Configure the identifier mapping table based on the unique device identifier code of the device system.

[0049] Specifically, in one implementation of this embodiment, step S101 includes the following steps:

[0050] Step S101a: Record the matching relationship between the unique device identifier code of the device system and the anonymous device identifier, and configure the identifier mapping table; the matching relationship includes the matching relationship between a unique device identifier code of the device system and an anonymous device identifier.

[0051] For a given device, its unique device identifier is immutable, but its anonymous device identifier can be updated or reset. Therefore, in this embodiment, there is a one-to-one matching relationship between the device system's unique device identifier and the anonymous device identifier, which needs to be stored on the server and configured in an identifier mapping table.

[0052] Although anonymous device identifiers can be updated or reset, such changes are not frequent in general. Therefore, in this embodiment, on the server side, in addition to recording the matching relationship between the device system's unique device identifier and the anonymous device identifier, it is also necessary to record the number of times and duration of use of a certain anonymous device identifier. Users can set the number of times or the duration of use as the judgment criteria for the use of anonymous device identifiers, or they can set the weight of the number of times and the duration of use parameters to comprehensively determine whether to use the current anonymous device identifier.

[0053] In this embodiment, if the user does not actively update or reset the anonymous device identifier, the server also sets rules for automatically updating the anonymous device identifier. The server pre-sets the conversion duration, number of conversions, and monitoring period, monitors all newly generated anonymous device identifiers, and sets the newly generated anonymous device identifiers to a monitoring state. If the usage duration of the current anonymous device identifier within the monitoring period exceeds the conversion duration or the number of uses within the monitoring period exceeds the number of conversions, then the current anonymous device identifier is determined as the anonymous device identifier to be used, and the monitoring state is removed. Otherwise, the server continues to maintain the monitoring state for this anonymous device identifier. For example, if the conversion duration is set to 3 days, the number of conversions is set to 10, and the observation period is set to 5 days, then within 5 days, as long as the usage duration of the anonymous device identifier reaches 3 days or the number of uses reaches 10, the monitoring state of the current anonymous device identifier is removed.

[0054] Specifically, in one implementation of this embodiment, step S101a includes the following steps:

[0055] Step S101a1: If the anonymous device identifier in the identifier mapping table is updated or reset, then the identifier mapping table becomes invalid.

[0056] The identifier mapping table records the mapping relationship between the unique identifier of a device and the anonymous device identifier. Once the anonymous device identifier is updated or reset, the corresponding identifier mapping table becomes invalid.

[0057] Step S102: Store the mapping relationship between the unique device identifier of the device system and the corresponding anonymous device identifier in the identifier mapping table.

[0058] The server stores the mapping relationship between the unique device identifier of the device system and the corresponding anonymous device identifier in the identifier mapping table, and monitors the usage status of the anonymous device identifier of the device system to prepare for sending relevant operation instructions in the future.

[0059] Step S200: Determine the unique device identifier code and preset instruction rules according to the configuration identifier mapping table, and send an update operation instruction for the anonymous device identifier to the device system.

[0060] Specifically, in one implementation of this embodiment, step S200 includes the following steps:

[0061] Step S201: Obtain the current anonymous device identifier, search the identifier mapping table, and determine whether the current anonymous device identifier matches the anonymous device identifier in the identifier mapping table.

[0062] In this embodiment, whenever the current anonymous device identifier is obtained, the identifier mapping table needs to be searched. If no matching relationship can be found, it means that the anonymous device identifier is not the anonymous device identifier that the user usually uses, and there is a risk of personal information leakage. If a matching relationship can be found, corresponding operations need to be performed according to the status of the anonymous device identifier.

[0063] Step S202: If a matching relationship exists, determine whether the matching relationship has expired according to preset rules.

[0064] Specifically, in one implementation of this embodiment, step S202 includes the following steps:

[0065] In step S202a, if the matching relationship expires, the matching relationship is added to the timeout list, and an update suggestion message is sent to the device system.

[0066] In actual use, users may not use the device system for a long time, but the anonymous device identifier is still stored in the identifier mapping table. The anonymous device identifier has not expired. Long-term inactivity may lead to the risk of personal information leakage. Therefore, when the server obtains the anonymous device identifier that has not been used for a long time, it will send a reminder message to the user.

[0067] In this embodiment, a timeout period is preset. If the user does not use the anonymous device identifier within the timeout period, the anonymous device identifier is added to the timeout list, and an update suggestion message is sent to the device system, suggesting that the user update the anonymous device identifier.

[0068] Step S202b: Set the current anonymous device identifier status to off; and / or replace the current anonymous device identifier with a new anonymous device identifier.

[0069] In this embodiment, the server can send various types of update suggestion messages based on the status of the anonymous device identifier. If the anonymous device identifier has not been used for a long time but has a high number of recorded uses, an update suggestion message can be sent to replace it and remove it from the timeout list. The new anonymous device identifier to be replaced can be a new anonymous device identifier selected by the user or another anonymous device identifier that already exists in the identifier mapping table. If the anonymous device identifier has not been used for a long time and has a low number of recorded uses, an update suggestion message can be sent to disable the current anonymous device identifier.

[0070] In step S203, if no matching relationship exists, a shutdown command or a reset command is issued to the device system.

[0071] Specifically, in one implementation of this embodiment, step S203 includes the following steps:

[0072] Step S203a: Determine whether a matching relationship exists in the timeout list.

[0073] If no match is found in the identifier mapping table, it means that the anonymous device identifier is not the one the user usually uses, posing a risk of personal information leakage. Therefore, it needs to be closed or reset. There may also be cases where there is no match in the identifier mapping table but a match exists in the timeout list. This indicates that the anonymous device identifier was deleted by the server because the user chose to delete it or it was automatically cleaned up after being listed in the timeout list for too long, suggesting that the user had previously used this type of anonymous device identifier.

[0074] Step S203b: If a matching relationship exists in the timeout list, a shutdown command is issued to the device system.

[0075] If a match is found in the timeout list, a shutdown command is issued to the device system.

[0076] If the anonymous device identifier is deleted by the server because the user chose to delete it or it was automatically cleaned up due to being in the timeout list for too long, you only need to issue a shutdown command to the device system. When the shutdown command is issued, the server will automatically generate a new anonymous device identifier as a replacement.

[0077] Step S203c: If there is no matching relationship in the timeout list, a reset command is issued to the device system.

[0078] In this case, it indicates that the anonymous device identifier is appearing for the first time, and the risk of information leakage is greatest. The server will issue a reset command to the device system and directly generate a new anonymous device identifier to replace it, in order to ensure the security of the user's personal information.

[0079] Step S300: Obtain the updated anonymous device identifier of the device system, and update and store the identifier mapping table according to the updated anonymous device identifier; wherein, the updated anonymous device identifier is the identifier after the device system updates the anonymous device identifier switch state or the identifier after updating the anonymous device identifier.

[0080] In this embodiment, when the device receives an update suggestion or update instruction from the server, it will perform a corresponding update operation. After updating the anonymous device identifier of the device system, the device system will automatically report the updated anonymous device identifier to the server, and the server will update and save the identifier mapping table.

[0081] This embodiment achieves the following technical effects through the above technical solution:

[0082] This invention discloses a method, terminal, and storage medium for managing anonymous device identifiers, comprising: acquiring anonymous device identifiers from a device system and configuring an identifier mapping table based on the anonymous device identifiers; determining a unique device identifier and preset instruction rules based on the configured identifier mapping table, and sending an update operation instruction for the anonymous device identifiers to the device system; acquiring the updated anonymous device identifiers from the device system, and updating and storing the identifier mapping table based on the updated anonymous device identifiers; wherein the updated anonymous device identifiers are either the device system's updated anonymous device identifier on / off state or the identifiers after the update. This invention establishes a server-side management mechanism for anonymous device identifiers, enabling background control of anonymous device identifiers, effectively preventing the malicious collection of personal information without the user's awareness, and effectively protecting the security of user personal information.

[0083] Exemplary device

[0084] Based on the above embodiments, the present invention also provides a terminal, comprising: a processor, a memory, an interface, a display screen, and a communication module connected via a system bus; wherein, the processor is used to provide computing and control capabilities; the memory includes a storage medium and internal memory; the storage medium stores an operating system and computer programs; the internal memory provides an environment for the operation of the operating system and computer programs in the storage medium; the interface is used to connect to external devices, such as mobile terminals and computers; the display screen is used to display corresponding information; and the communication module is used to communicate with a cloud server or a mobile terminal.

[0085] When the computer program is executed by the processor, it implements the steps of a method for managing anonymous device identifiers.

[0086] It will be understood by those skilled in the art that Figure 2 The schematic diagram shown is merely a partial structural diagram related to the present invention and does not constitute a limitation on the terminal to which the present invention is applied. A specific terminal may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0087] In one embodiment, a terminal is provided, comprising: a processor and a memory, the memory storing an executable program for the management of anonymous device identifiers, the executable program for the management of anonymous device identifiers being executed by the processor to implement the steps of the anonymous device identifier management method as described above.

[0088] In one embodiment, a storage medium is provided, wherein the storage medium stores an executable program for the management of anonymous device identifiers, the executable program for the management of anonymous device identifiers being executed by the processor to implement the steps of the anonymous device identifier management method as described above.

[0089] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile storage medium, and when executed, it can include the processes of the embodiments of the methods described above. Any references to memory, storage, databases, or other media used in the embodiments provided by this invention can include non-volatile and / or volatile memory.

[0090] In summary, this invention discloses a method, terminal, and storage medium for managing anonymous device identifiers, comprising: acquiring anonymous device identifiers from a device system and configuring an identifier mapping table based on the anonymous device identifiers; determining a unique device identifier and preset instruction rules based on the configured identifier mapping table, and sending an update operation instruction for the anonymous device identifiers to the device system; acquiring the updated anonymous device identifiers from the device system, and updating and storing the identifier mapping table based on the updated anonymous device identifiers; wherein the updated anonymous device identifiers are either the device system's updated anonymous device identifier on / off state or the identifiers after the update. This invention establishes a server-side management mechanism for anonymous device identifiers, enabling background control of anonymous device identifiers, effectively preventing the malicious collection of personal information without the user's awareness, and effectively protecting the security of user personal information.

[0091] It should be understood that the application of the present invention is not limited to the examples above. Those skilled in the art can make improvements or modifications based on the above description, and all such improvements and modifications should fall within the protection scope of the appended claims.

Claims

1. A method for controlling anonymous device identifiers, characterized in that, include: Obtain the anonymous device identifier of the device system, and configure the identifier mapping table according to the anonymous device identifier; Based on the configuration identifier mapping table, a unique device identifier code and preset instruction rules are determined, and an update operation instruction for the anonymous device identifier is sent to the device system. Obtain the updated anonymous device identifier of the device system, and update and store the identifier mapping table according to the updated anonymous device identifier; wherein, the updated anonymous device identifier is the device system's updated anonymous device identifier switch state or the identifier after updating the anonymous device identifier; The step of determining a unique device identifier and a preset instruction rule based on the configuration identifier mapping table, and sending an update instruction for the anonymous device identifier to the device system, includes: Obtain the current anonymous device identifier, search the identifier mapping table, and determine whether the current anonymous device identifier matches the anonymous device identifier in the identifier mapping table; If a matching relationship exists, it is determined whether the matching relationship has expired according to preset rules; If no matching relationship exists, a shutdown command or a reset command is issued to the device system, and a new anonymous device identifier is generated to replace the original anonymous device identifier after the reset command is issued.

2. The method for controlling anonymous device identifiers according to claim 1, characterized in that, The step of obtaining the anonymous device identifier of the device system and configuring the identifier mapping table according to the anonymous device identifier includes: Configure an identifier mapping table based on the unique device identifier of the device system; The mapping relationship between the unique device identifier of the device system and the corresponding anonymous device identifier is stored in the identifier mapping table.

3. The method for controlling anonymous device identifiers according to claim 2, characterized in that, The step of configuring an identifier mapping table based on the unique device identifier code of the device system includes: Record the matching relationship between the unique device identifier and the anonymous device identifier in the device system, and configure an identifier mapping table; the matching relationship includes the matching relationship between a unique device identifier and an anonymous device identifier in the device system.

4. The method for controlling anonymous device identifiers according to claim 3, characterized in that, The configuration identifier mapping table includes: If the anonymous device identifier in the identifier mapping table is updated or reset, the identifier mapping table becomes invalid.

5. The method for controlling anonymous device identifiers according to claim 1, characterized in that, The step of determining whether the matching relationship has expired according to preset rules includes: If the matching relationship expires, the matching relationship will be added to the timeout list, and an update suggestion message will be sent to the device system.

6. The method for controlling anonymous device identifiers according to claim 5, characterized in that, The step of issuing a shutdown or reset command to the device system includes: Determine whether a matching relationship exists in the timeout list; If a matching relationship exists in the timeout list, a shutdown command is issued to the device system; If no matching relationship exists in the timeout list, a reset command is issued to the device system.

7. The method for controlling anonymous device identifiers according to claim 5, characterized in that, The update suggestion information includes: Set the current anonymous device identifier status to off; and / or replace the current anonymous device identifier with a new anonymous device identifier.

8. A terminal, characterized in that, include: The processor and memory, the memory storing an executable program for the management of anonymous device identifiers, the executable program for the management of anonymous device identifiers being executed by the processor to implement the steps of the method for managing anonymous device identifiers as described in any one of claims 1-7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores an executable program for the management of anonymous device identifiers, which, when executed by a processor, is used to implement the steps of the anonymous device identifier management method as described in any one of claims 1-7.

Images