A method, medium, apparatus, and computing device for processing harmful information.

Abstract

This disclosure provides a method, medium, apparatus, and computing device for processing harmful information. The method includes: upon detecting that a user has logged into a client on a target device, acquiring harmful information data of the user, and acquiring an unprocessed harmful information identifier corresponding to the target device based on the harmful information data; generating a cleanup instruction based on the unprocessed harmful information identifier; and sending the cleanup instruction to the target device, causing the target device to delete the harmful information indicated by the cleanup instruction. By acquiring the unprocessed harmful information identifier corresponding to the target device when a user logs into the client through the target device, unprocessed harmful information on the user's target device can be tracked, thereby enabling more thorough deletion of harmful information on various devices of the user.

Description

Technical Field

[0001] The embodiments of this disclosure relate to the field of data processing, and more specifically, the embodiments of this disclosure relate to a method, medium, apparatus, and computing device for processing harmful information. Background Technology

[0002] Harmful information typically refers to chat logs containing content that violates relevant regulations or that negatively impacts a user's mental or physical health. To prevent the spread of harmful information, the server notifies the client to delete it once it is identified as such. However, users can switch between multiple devices and log into the same account, and each device can cache and synchronize information records from other devices. If the cached or synchronized records contain harmful information, the deletion may not be complete when the user switches devices, thus increasing the risk of harmful information spreading.

[0003] This section is intended to provide background or context for the embodiments of this disclosure as set forth in the claims. The description herein is not intended to be a prior art simply because it is included in this section. Summary of the Invention

[0004] In this context, embodiments of the present disclosure aim to provide a method, medium, apparatus, and computing device for processing harmful information, so as to more thoroughly delete harmful information and prevent its spread.

[0005] In a first aspect of this disclosure, a method for processing harmful information is provided, applied to a server, the method comprising:

[0006] In response to detecting that a user has logged into the client on the target device, harmful information data of the user is obtained;

[0007] Based on the harmful information data, obtain the unprocessed harmful information identifier corresponding to the target device;

[0008] Based on the unprocessed harmful information identifier, a cleanup command is generated;

[0009] The cleaning command is sent to the target device, causing the target device to delete the harmful information indicated by the cleaning command.

[0010] In one embodiment of this disclosure, the method further includes:

[0011] The information records of the user stored in the server are detected to identify harmful information in the information records;

[0012] Delete the stored harmful information and record the deletion time of the harmful information.

[0013] In one embodiment of this disclosure, the harmful information data includes all harmful information identifiers of the user, and the deletion time of the harmful information;

[0014] The step of obtaining the unprocessed harmful information identifier corresponding to the target device based on the harmful information data includes:

[0015] Obtain the cleaning progress record corresponding to the target device, and the cleaning progress record is used to record the processed harmful information identifiers corresponding to the target device;

[0016] Based on the cleanup progress record, the unprocessed harmful information identifier corresponding to the target device is obtained from all harmful information identifiers of the user.

[0017] In one embodiment of this disclosure, the cleanup progress record includes an identifier corresponding to the last piece of harmful information deleted by the target device;

[0018] The step of obtaining the unprocessed harmful information identifier corresponding to the target device from all harmful information identifiers of the user based on the cleanup progress record includes:

[0019] Obtain the deletion time corresponding to the identifier of the last harmful message from all of the user's harmful information;

[0020] Among all the user's harmful information, all harmful information that occurred after the deletion time is identified as unprocessed harmful information identifiers corresponding to the target device.

[0021] In one embodiment of this disclosure, the harmful information data includes all harmful information identifiers of the user;

[0022] The step of obtaining the unprocessed harmful information identifier corresponding to the target device based on the harmful information data includes:

[0023] If no cleanup progress record is obtained for the target device, then all harmful information identifiers of the user are identified as unprocessed harmful information identifiers for the target device.

[0024] In one embodiment of this disclosure, the method further includes:

[0025] When the target device is logged in, in response to the detection of a newly added harmful information identifier, a cleanup command is generated based on the newly added harmful information identifier;

[0026] The cleaning command is sent to the target device, causing the target device to delete the harmful information indicated by the cleaning command.

[0027] In one embodiment of this disclosure, the method further includes:

[0028] Receive a cleanup response command from the target device, the cleanup response command being used to indicate the deleted harmful information identifiers;

[0029] Update the cleanup progress record corresponding to the target device according to the cleanup response command.

[0030] In one embodiment of this disclosure, the cleanup instruction is used to instruct the target device to delete the harmful information corresponding to the unprocessed harmful information identifier in the cleanup instruction from the message list and cache file, and to hide the harmful information on the message list interface when deleting the harmful information in the message list.

[0031] In a second aspect of this disclosure, a harmful information processing apparatus is provided, applied to a server, the apparatus comprising:

[0032] The acquisition unit is used to acquire harmful information data of the user when it is detected that the user has logged into the client on the target device, and to acquire the unprocessed harmful information identifier corresponding to the target device based on the harmful information data;

[0033] The generation unit is used to generate a cleanup instruction based on the unprocessed harmful information identifier;

[0034] The sending unit is used to send the cleaning instruction to the target device, so that the target device deletes the harmful information indicated by the cleaning instruction.

[0035] In a third aspect of this disclosure, a computer-readable storage medium is provided that stores computer program instructions thereon, which, when executed by a processor, implement the method described in any embodiment.

[0036] In a fourth aspect of the present disclosure, a computing device is provided, including: a memory and a processor;

[0037] The memory is used to store computer instructions that can run on a processor, which is used to implement the method described in any of the above embodiments when executing the computer instructions.

[0038] According to the harmful information processing method of this disclosure, when a user is detected logging into a client on a target device, harmful information data of the user is obtained, and an unprocessed harmful information identifier corresponding to the target device is obtained based on the harmful information data; a cleanup instruction is generated based on the unprocessed harmful information identifier; the cleanup instruction is sent to the target device, causing the target device to delete the harmful information indicated by the cleanup instruction. When a user logs into the client through a target device, by obtaining the unprocessed harmful information identifier corresponding to the target device, unprocessed harmful information on the user's target device can be tracked, thereby enabling more thorough deletion of harmful information on the user's various devices. Attached Figure Description

[0039] The above and other objects, features, and advantages of this disclosure will become readily apparent from the following detailed description of exemplary embodiments, taken in conjunction with the accompanying drawings. Several embodiments of this disclosure are illustrated in the drawings by way of example and not limitation, in which:

[0040] Figure 1 An exemplary flowchart is provided for a method of processing harmful information;

[0041] Figure 2A An exemplary flowchart provides a method for handling harmful information when obtaining cleanup progress records;

[0042] Figure 2B An exemplary flowchart provides a method for handling harmful information when no cleanup progress record is obtained;

[0043] Figure 3 An exemplary structural diagram of a harmful information processing device is provided;

[0044] Figure 4 This is a schematic diagram of a computer-readable storage medium provided in this disclosure;

[0045] Figure 5 This is a schematic diagram of the structure of a computing device provided in this disclosure.

[0046] In the accompanying drawings, the same or corresponding reference numerals indicate the same or corresponding parts. Detailed Implementation

[0047] The principles and spirit of this disclosure will now be described with reference to several exemplary embodiments. It should be understood that these embodiments are given merely to enable those skilled in the art to better understand and implement this disclosure, and are not intended to limit the scope of this disclosure in any way. Rather, these embodiments are provided to make this disclosure more thorough and complete, and to fully convey the scope of this disclosure to those skilled in the art.

[0048] Those skilled in the art will recognize that embodiments of this disclosure can be implemented as a system, apparatus, device, method, or computer program product. Therefore, this disclosure can be specifically implemented in the following forms: entirely hardware, entirely software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0049] According to embodiments of this disclosure, a method, medium, apparatus, and computing device for processing harmful information are proposed.

[0050] The principles and spirit of this disclosure will be explained in detail below with reference to several representative embodiments.

[0051] Users can typically spread harmful information through chat software. To prevent the spread of harmful information, the server will notify the client to delete the harmful information from the message list when it detects harmful information in the chat history. However, the criteria for determining harmful information may change. Information that was not initially identified as harmful may later be identified as harmful. For ease of description, information that was not initially identified as harmful but was later identified as harmful is called potentially harmful information. In the case of potentially harmful information in the chat history, a user logs into the client on device A to chat and caches the chat history. Then, the user switches to device B, logs into the same account, and synchronizes the cached chat history from device A. After the server identifies the potentially harmful information as harmful, it will notify the client on device B to delete the harmful information. However, the harmful information cached on device A is not deleted, resulting in incomplete deletion of the harmful information.

[0052] In other words, the currently logged-in client can synchronize chat history from other clients. If the synchronized chat history contains potentially harmful information, the deletion of harmful information may not be thorough if the user changes the login device.

[0053] In view of this, this disclosure provides a method for processing harmful information. The method is applied to a server, which can be the server of a target application. For example, if the target application is a chat application, the server is the server corresponding to the chat application. The method records the processing status of harmful information on various devices of the user through harmful information data. When it detects that a user has logged into the client on one of their devices, it tracks unprocessed harmful information on that device using pre-recorded processing information and notifies that device to delete the unprocessed harmful information. This more thoroughly removes harmful information from multiple devices of the user, reducing the spread of harmful information and its interference with the user.

[0054] The following describes a method for processing harmful information according to exemplary embodiments of the present disclosure, with reference to the accompanying drawings.

[0055] Figure 1 An exemplary flowchart of a method for processing harmful information is provided, such as... Figure 1 As shown, the harmful information processing method provided in this disclosure includes the following steps S101 to S104.

[0056] In step S101, in response to detecting that a user has logged into the client on the target device, harmful information data of the user is obtained.

[0057] In this embodiment, a single user can have multiple devices, and a user can switch between devices that log in to the same account. In this embodiment, the device used to log in to the account is referred to as the target device. For example, if user 1 has device A and device B, when user 1 logs in to the account through the client on device A, device A is the target device. However, when the user switches to log in to the account through the client on device B, device B becomes the target device.

[0058] The server can pre-store harmful information data for multiple users. When it detects that a user has logged into the client on the target device, it retrieves the harmful information data corresponding to that user from the pre-stored harmful information data.

[0059] In some possible implementations, the harmful information data includes harmful information data from the user's various devices, and the harmful information data includes status indicators indicating whether the harmful information has been processed. For example, the harmful information data is shown in Table 1.

[0060] Table 1

[0061]

[0062] Those skilled in the art will understand that, in order to prevent the spread of harmful information, the server may store identifiers of harmful information in this embodiment. In addition to the storage structure shown in Table 1, other structures may also be used to store harmful information data, and this disclosure does not limit this.

[0063] In step S102, the unprocessed harmful information identifier corresponding to the target device is obtained based on the harmful information data.

[0064] When a user is detected logging into the client on a target device, the user identifier and the target device identifier can be obtained. Based on the user identifier and the target device identifier, the unprocessed harmful information identifier corresponding to the target device can be obtained from the harmful information data.

[0065] Suppose the server detects that user 1 has logged into the client on device A, then the server can obtain the unprocessed harmful information identifier corresponding to device A from user 1's harmful information data, such as the harmful message bbb.

[0066] In step S103, a cleanup command is generated based on the unprocessed harmful information identifier.

[0067] If an unprocessed harmful information identifier is found on the target device, a cleanup command can be generated based on the unprocessed harmful information identifier.

[0068] In step S104, the cleaning command is sent to the target device, causing the target device to delete the harmful information indicated by the cleaning command.

[0069] The cleanup command is sent to the client on the target device, causing the client on the target device to delete the harmful information indicated by the cleanup command.

[0070] This embodiment of the disclosure, upon detecting that a user has logged into the client on a target device, acquires the user's harmful information data and obtains an unprocessed harmful information identifier corresponding to the target device based on the harmful information data; generates a cleanup command based on the unprocessed harmful information identifier; and sends the cleanup command to the target device, causing the target device to delete the harmful information indicated by the cleanup command. By acquiring the unprocessed harmful information identifier corresponding to the target device when a user logs into the client through the target device, the unprocessed harmful information on the user's target device can be tracked, thereby enabling a more thorough deletion of harmful information on the user's various devices.

[0071] In some embodiments, the information records of the user stored in the server can be detected to identify harmful information in the information records; the stored harmful information can be deleted, and the deletion time of the harmful information can be recorded.

[0072] In other words, the server can inspect (or audit) user information records according to pre-set rules. If the information does not conform to the rules, it is determined to be harmful. If the information is determined to be harmful, it is deleted from the server's storage, rendering subsequent access to the resource invalid and thus preventing the spread of harmful information to some extent.

[0073] For example, if the server is the server of a chat application, the server can detect the user's chat information according to preset rules. If harmful information is detected, the server will delete the harmful information stored on the server and record the deletion time of the harmful information.

[0074] It's important to note that harmful information includes, but is not limited to, text, video, audio, images, emoticons, and external links. Different types have different detection rules and methods, resulting in varying processing times for each type. Therefore, in practice, harmful information is not deleted first; rather, it is deleted based on the time it was identified as harmful. Furthermore, the rules for detecting harmful information can be continuously updated. After an update, information that was previously not considered harmful may now be classified as harmful.

[0075] In the above circumstances, this disclosure can also be used to track unprocessed harmful information on the target device, so as to more thoroughly delete the harmful information on the target device.

[0076] Those skilled in the art should understand that the rules for determining whether information is harmful can be specifically set according to actual needs, and this disclosure does not limit them.

[0077] In some embodiments, the harmful information data may include all harmful information identifiers of the user and the deletion time of the harmful information; in this case, obtaining the unprocessed harmful information identifier corresponding to the target device based on the harmful information data may include: obtaining the cleanup progress record corresponding to the target device, the cleanup progress record being used to record the processed harmful information identifier corresponding to the target device; and obtaining the unprocessed harmful information identifier corresponding to the target device from all harmful information identifiers of the user based on the cleanup progress record.

[0078] In this embodiment, the harmful information data may include a user identifier, a harmful information identifier, and the time the harmful information was deleted. Compared to recording the user identifier, the user's various device identifiers, and the status indicators of whether harmful information on each device has been processed in the harmful information data, data redundancy can be reduced and storage space can be saved.

[0079] When the harmful information data includes user identifier, harmful information identifier, and the deletion time of the harmful information, a cleanup progress record for each user's device can be stored. Upon detecting that a user has logged into the client on a target device, the cleanup progress record corresponding to that target device can be retrieved. Based on the cleanup progress record, the unprocessed harmful information identifier corresponding to the target device is retrieved from the user's total harmful information identifiers.

[0080] To better understand this solution, this embodiment uses the harmful information data shown in Table 2 as an example for illustration. The deletion time in Table 2 is based on the same day.

[0081] Table 2

[0082]

[0083] As shown in Table 2, in some possible implementations, the harmful information data may include a user identifier, a harmful information identifier, and the time of deletion of the harmful information. Those skilled in the art should understand that the data in Table 2 is for better understanding of this solution, but does not constitute a limitation on the scope of this solution.

[0084] In some possible implementations, the harmful information data is stored in a harmful information list. The server can add harmful information to the harmful information list sequentially according to the time when it is detected as harmful information. The server can also delete harmful information according to the time when it is detected. Subsequently, each device corresponding to the user deletes harmful information according to the order of the harmful information list.

[0085] In some embodiments, the server can store the cleanup progress records for different devices corresponding to multiple users using a data structure of user identifier-device identifier-harmful information identifier. Furthermore, to further save storage space, the cleanup progress record for each device can record the identifier of the last piece of harmful information deleted by that device. That is, one cleanup progress record is kept for each device, and by default, all harmful information before the deletion time corresponding to the harmful information identifier recorded in the cleanup progress record has been processed.

[0086] For example, the cleanup progress records for each user's different devices stored on the server can be shown in Table 3.

[0087] Table 3

[0088] User ID Equipment identification Harmful information label User 1 Equipment A Harmful news aaa User 1 Equipment B Harmful information CCC User 2 Equipment C Harmful news aaa User 2 Device D Harmful news ddd

[0089] As shown in Table 3, the cleaning progress record for each device records the identifier of the last piece of harmful information deleted from the device.

[0090] If the cleanup progress record includes the identifier corresponding to the last harmful information deleted from the target device; obtaining the unprocessed harmful information identifier corresponding to the target device from all harmful information identifiers of the user based on the cleanup progress record may include: obtaining the deletion time corresponding to the identifier of the last harmful information from all harmful information of the user; and determining all harmful information after the deletion time from all harmful information of the user as the unprocessed harmful information identifier corresponding to the target device.

[0091] Since the harmful information data includes all harmful information identifiers of the user and the deletion time of the harmful information, the deletion time corresponding to the identifier of the last harmful information in the cleanup progress record can be obtained from all the harmful information of the user. All harmful information after the deletion time is identified as the unprocessed harmful information identifier corresponding to the target device.

[0092] Take the cleanup progress record of User 1 - Device A in Table 3 as an example.

[0093] User 1 Equipment A Harmful news aaa

[0094] For device A corresponding to user 1, the deletion time for harmful information "aaa" is 9:45. This means that device A has already cleaned up harmful information deleted before 9:45, such as harmful message "bbb". Conversely, device A has not cleaned up harmful information deleted after 9:45, such as harmful messages "ccc" and "ddd".

[0095] Let's take the cleanup progress record of User 1 - Device B in Table 3 as an example.

[0096] User 1 Equipment B Harmful information CCC

[0097] For device B corresponding to user 1, the deletion time for the harmful message "ccc" is 10:00. This means that device B has already cleaned up harmful messages deleted before 10:00, such as harmful messages "aaa" and "bbb". Conversely, device B has not cleaned up harmful messages deleted after 10:00, such as harmful message "ddd".

[0098] Therefore, the server can retrieve the cleanup progress record corresponding to the target device from the pre-stored cleanup progress records based on the user identifier and the target device identifier. Based on the cleanup progress record corresponding to the target device, the server can retrieve the unprocessed harmful information identifier corresponding to the target device from the user's total harmful information identifiers.

[0099] In some embodiments, if the cleanup progress record corresponding to the target device is not obtained, then all harmful information identifiers of the user are determined as unprocessed harmful information identifiers corresponding to the target device.

[0100] If no cleanup progress record is obtained for the target device, it indicates that the device may be new to the user, or that the user has not logged into the client on the device for a long time, resulting in the server not having a cleanup progress record for that device. After logging into the client on the device, the user can synchronize information records from other clients. If the synchronized information records include potentially harmful information, there is a risk of the spread of harmful information. Therefore, in the absence of a cleanup progress record for the target device, all harmful information identifiers of the user are identified as unprocessed harmful information identifiers for the target device. For the target device, if there is no harmful information corresponding to the unprocessed harmful information identifier on the target device, it is assumed that the target device has completed the processing of the harmful information.

[0101] In the absence of a cleanup progress record for the target device, identifying all harmful information of the user as unprocessed harmful information for the target device can further reduce the risk of harmful information spreading.

[0102] As can be seen from the above embodiments, different devices of the same user can sequentially delete harmful information based on the deletion time corresponding to the harmful information.

[0103] In some possible implementations, when harmful information data is stored in a harmful information list, the unprocessed harmful information identifier corresponding to the target device can be determined based on the position of the harmful information identifier in the harmful information list. For example, all harmful information following the identifier of the last harmful information in the cleanup progress record among all harmful information identifiers corresponding to the user in the harmful information list can be determined as the unprocessed harmful information identifier corresponding to the target device.

[0104] In some embodiments, when the target device is logged in, in response to the detection of a newly added harmful information identifier, a cleanup command is generated based on the newly added harmful information identifier; the cleanup command is sent to the target device, causing the target device to delete the harmful information indicated by the cleanup command.

[0105] It is understandable that, while a user continuously logs into the client through the target device (i.e., while the target device is logged in), if a new harmful information identifier is detected in the user's harmful information data, a cleanup command is generated based on the new harmful information identifier. The cleanup command is then sent to the target device, causing it to delete the harmful information indicated by the cleanup command. This ensures that even when the target device is logged in, it can delete harmful information detected by the server.

[0106] In some possible implementations, the cleanup command can be used to instruct the target device to delete the harmful information corresponding to the unprocessed harmful information identifier in the cleanup command from the message list and cache file, and to hide the harmful information on the message list interface when deleting the harmful information in the message list.

[0107] For the target device, upon receiving a cleanup command from the server, the target device deletes the harmful information corresponding to the unprocessed harmful information identifier in the cleanup command from the message list and cache files according to the instructions. Furthermore, the harmful information can be hidden from the message list interface when it is being deleted.

[0108] Compared to related technologies where the server notifies the client to remove harmful information from the message list, this embodiment can also delete harmful information already downloaded to the user's client, i.e., the cached file, which can further reduce the spread of harmful information.

[0109] In some embodiments, the server may also receive a cleanup response instruction from the target device, the cleanup response instruction being used to indicate the deleted harmful information identifier; and update the cleanup progress record corresponding to the target device according to the cleanup response instruction.

[0110] In this embodiment, by updating the cleaning progress record corresponding to the target device, the harmful information identifiers that have already been processed by the target device will not be re-sent to the target device.

[0111] In this embodiment, storing the cleanup progress records of the devices in a structure of "user identifier-device identifier-harmful message identifier" enables tracking of the deletion of harmful messages on multiple devices belonging to the same user. Furthermore, storing corresponding cleanup progress records for each device ensures that no harmful information is missed during deletion.

[0112] The following embodiments of this disclosure will illustrate the method for processing harmful information through specific examples in conjunction with the accompanying drawings. Figure 2A and 2B This demonstrates how the server handles harmful information when the same user logs into the client on different devices. Figure 2A The diagram illustrates how the server handles harmful information when it stores the cleanup progress record corresponding to user 1's device A; Figure 2B The example illustrates how the server handles harmful information when it does not store the cleanup progress record for user 1's device B.

[0113] like Figure 2A As shown, the harmful information processing process performed by the server after a user logs in on device A includes the following steps S201A to S203A.

[0114] In step S201A, it is detected that a user has logged into the client on device A.

[0115] In step S202A, the cleanup progress record corresponding to device A is obtained according to "user id + device Aid", and the unprocessed harmful information identifier corresponding to device A is obtained from all harmful information identifiers of the user according to the cleanup progress record. A cleanup instruction is generated according to the unprocessed harmful information identifier.

[0116] In step S203A, a cleanup response instruction from device A is received, and the cleanup progress record corresponding to device A is updated according to the cleanup response instruction.

[0117] In other words, harmful message IDs that have already been processed under the same device will not be subject to repeated cleanup commands.

[0118] like Figure 2B As shown, the harmful information processing process performed by the server after the user logs in on device B includes the following steps S201B to S203B.

[0119] In step S201B, it is detected that a user has logged into the client on device B.

[0120] In step S202B, if the cleanup progress record corresponding to device B is not obtained based on "user id + device Bid", then all harmful information identifiers of the user are determined as unprocessed harmful information identifiers corresponding to device B, and a cleanup instruction is generated based on the unprocessed harmful information identifiers.

[0121] In step S203B, a cleanup response instruction from device B is received, and the cleanup progress record corresponding to device B is updated according to the cleanup response instruction.

[0122] It should be noted that the above application scenarios are shown only to facilitate understanding of the spirit and principles of this disclosure, and the implementation of this disclosure is not limited in any way. On the contrary, the implementation of this disclosure can be applied to any applicable scenario.

[0123] Figure 3 An exemplary structural diagram of a harmful information processing device is provided, wherein the harmful information processing device is applied to a server, such as... Figure 3 As shown, this disclosure provides a harmful information processing device, comprising:

[0124] The acquisition unit 301 is used to acquire harmful information data of the user when it is detected that the user has logged into the client on the target device, and to acquire the unprocessed harmful information identifier corresponding to the target device based on the harmful information data.

[0125] The generation unit 302 is used to generate a cleanup command based on the unprocessed harmful information identifier;

[0126] The sending unit 303 is used to send the cleaning instruction to the target device, so that the target device deletes the harmful information indicated by the cleaning instruction.

[0127] In some embodiments, the harmful information data includes all harmful information identifiers of the user and the deletion time of the harmful information; the acquisition unit 301 is specifically used for:

[0128] Obtain the cleaning progress record corresponding to the target device, and the cleaning progress record is used to record the processed harmful information identifiers corresponding to the target device;

[0129] Based on the cleanup progress record, the unprocessed harmful information identifier corresponding to the target device is obtained from all harmful information identifiers of the user.

[0130] In some embodiments, the cleanup progress record includes an identifier corresponding to the last harmful message deleted by the target device; the acquisition unit 301 is specifically used for:

[0131] Obtain the deletion time corresponding to the identifier of the last harmful message from all of the user's harmful information;

[0132] Among all the user's harmful information, all harmful information that occurred after the deletion time is identified as unprocessed harmful information identifiers corresponding to the target device.

[0133] In some embodiments, the acquisition unit 301 is specifically used to: if the cleaning progress record corresponding to the target device is not acquired, then determine all the harmful information identifiers of the user as the unprocessed harmful information identifiers corresponding to the target device.

[0134] In some embodiments, the generation unit 302 is further configured to: when the target device is logged in, in response to detecting a newly added harmful information identifier, generate a cleanup instruction based on the newly added harmful information identifier;

[0135] The cleaning command is sent to the target device, causing the target device to delete the harmful information indicated by the cleaning command.

[0136] In some embodiments, the apparatus further includes an update unit for receiving a cleanup response instruction from the target device, the cleanup response instruction indicating the deleted harmful information identifiers, and updating the cleanup progress record corresponding to the target device according to the cleanup response instruction.

[0137] In some embodiments, the cleanup instruction is used to instruct the target device to delete the harmful information corresponding to the unprocessed harmful information identifier in the cleanup instruction from the message list and cache file, and to hide the harmful information on the message list interface when deleting the harmful information in the message list.

[0138] It should be noted that although several units / modules or sub-units / modules of the apparatus have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided and embodied by multiple units / modules.

[0139] Figure 4 This is a schematic diagram of a computer-readable storage medium 400 provided in this disclosure, on which a computer program is stored, which, when executed by a processor, implements the method of any embodiment of this disclosure.

[0140] This disclosure also provides a computing device, including a memory and a processor; the memory is used to store computer instructions that can be executed on the processor, and the processor is used to implement the methods of any embodiment of this disclosure when executing the computer instructions.

[0141] Figure 5 This is a schematic diagram of the structure of a computing device provided in this disclosure. The computing device 500 may include, but is not limited to, a processor 501, a memory 502, and a bus 503 connecting different system components (including the memory 502 and the processor 501).

[0142] The memory 502 stores computer instructions that can be executed by the processor 501, enabling the processor 501 to perform the methods of any embodiment of this disclosure. The memory 502 may include a random access memory (RAM) 5021, a cache memory 5022, and / or a read-only memory (ROM) 5023. The memory 502 may also include a program tool 5025 having a set of program modules 5024, including but not limited to: an operating system, one or more application programs, other program modules, and program data. One or more combinations of these program modules may include an implementation of a network environment.

[0143] Bus 503 may include, for example, a data bus, an address bus, and a control bus. The computing device 500 can also communicate with external devices 505 via I / O interface 504, such as a keyboard or a Bluetooth device. The computing device 500 can also communicate with one or more networks via network adapter 506, such as a local area network (LAN), a wide area network (WAN), or a public network. The network adapter 506 can also communicate with other modules of the computing device 500 via bus 503.

[0144] Furthermore, although the operations of the methods disclosed herein are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all of the operations shown must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0145] While the spirit and principles of this disclosure have been described with reference to several specific embodiments, it should be understood that this disclosure is not limited to the disclosed specific embodiments, and the division of aspects does not imply that features in these aspects cannot be combined for benefit; such division is merely for convenience of expression. This disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A harmful information processing method characterized by comprising: The application is applied to a server, the server pre-stores harmful information data of each device bound by each user, the harmful information data includes harmful information, harmful information identifier and state identifier indicating whether the harmful information has been processed; the method comprises: In each case where the same user is detected to log in the client on a target device, obtaining the harmful information data of the user from the pre-stored harmful information data; wherein the target device is one of the devices bound by the user and currently used to log in the client; Obtaining the harmful information identifier of the harmful information not processed in the harmful information data of the target device from the harmful information data of the user; Generating a cleaning instruction according to the harmful information identifier not processed; Sending the cleaning instruction to the target device, so that the target device deletes the harmful information indicated by the harmful information identifier not processed.

2. The method of claim 1, wherein, The method further comprises: Detecting the information record of the user stored in the server to determine the harmful information in the information record; Deleting the stored harmful information and recording the deletion time of the harmful information.

3. The method of claim 2, wherein, The harmful information data includes all harmful information identifiers of the user and the deletion time of the harmful information; The method of obtaining the harmful information identifier not processed corresponding to the target device from the harmful information data comprises: Obtaining the cleaning progress record corresponding to the target device, the cleaning progress record is used to record the harmful information identifier processed corresponding to the target device; Obtaining the harmful information identifier not processed corresponding to the target device from all harmful information identifiers of the user according to the cleaning progress record.

4. The method of claim 3, wherein, The cleaning progress record includes the identifier corresponding to the last harmful information deleted by the target device; The method of obtaining the harmful information identifier not processed corresponding to the target device from all harmful information identifiers of the user according to the cleaning progress record comprises: Obtaining the deletion time corresponding to the identifier of the last harmful information from all harmful information of the user; In all harmful information of the user, all harmful information after the deletion time is determined as the harmful information identifier not processed corresponding to the target device.

5. The method of claim 2, wherein, The harmful information data includes all harmful information identifiers of the user; The method of obtaining the harmful information identifier not processed corresponding to the target device from the harmful information data comprises: In response to not obtaining the cleaning progress record corresponding to the target device, all harmful information identifiers of the user are determined as the harmful information identifier not processed corresponding to the target device.

6. The method according to any one of claims 1 to 5, characterized in that, The method further comprises: In the case where the target device is in a login state, in response to detecting a new harmful information identifier, generating a cleaning instruction according to the new harmful information identifier; Sending the cleaning instruction to the target device, so that the target device deletes the harmful information indicated by the cleaning instruction.

7. The method of claim 6, wherein, The method further comprises: Receiving the cleaning reply instruction of the target device, the cleaning reply instruction is used to indicate the harmful information identifier deleted; According to the cleaning reply instruction, the cleaning progress record corresponding to the target device is updated.

8. The method of claim 1, wherein, The cleaning instruction is used to instruct the target device to delete harmful information corresponding to the harmful information identifier that is not processed in the cleaning instruction from the message list and the cache file, and hide the harmful information on the interface of the message list when the harmful information in the message list is deleted.

9. A harmful information processing apparatus characterized by comprising: The server pre-stores harmful information data of each device bound by each user, and the harmful information data includes harmful information, harmful information identifier, and state identifier indicating whether the harmful information has been processed. The acquisition unit is configured to, in each case where the same user logs in the client on a target device, acquire harmful information data of the user from the pre-stored harmful information data, and acquire harmful information identifiers that are not processed in harmful information data of the target device from the harmful information data of the user, wherein the target device is one of the devices bound by the user and currently used to log in the client. The generation unit is configured to generate a cleaning instruction according to the harmful information identifiers that are not processed. The sending unit is configured to send the cleaning instruction to the target device, so that the target device deletes harmful information indicated by the harmful information identifiers that are not processed.

10. A computer readable storage medium having stored thereon computer program instructions, wherein, The computer program instructions are executed by the processor to implement the method of any one of claims 1-8.

11. A computing device, comprising: The computer program instructions are executed by the processor to implement the method of any one of claims 1-8. The computer program instructions are executed by the processor to implement the method of any one of claims 1-8. The computer program instructions are executed by the processor to implement the method of any one of claims 1-8.

Images