CN110752963A

CN110752963A - Event processing method and device, storage medium and electronic device

Info

Publication number: CN110752963A
Application number: CN201810820934.8A
Authority: CN
Inventors: 张志根; 林钊武; 杨朗
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2018-07-24
Filing date: 2018-07-24
Publication date: 2020-02-04
Anticipated expiration: 2038-07-24
Also published as: CN110752963B

Abstract

The invention discloses an event processing method and device, a storage medium and an electronic device. Wherein, the method comprises the following steps: detecting that a target event occurs on a target terminal where a first client logged in by using a first account is located; sending a first message to a second client logged in by using a second account, wherein the first message is used for indicating that the target event occurs on the target terminal, and the first account and the second account have an association relationship; receiving an operation instruction sent by the second client, wherein the operation instruction is used for instructing to execute a target operation corresponding to the target event on the target terminal; and responding to the operation instruction, and executing the target operation. The invention solves the technical problem of low event processing efficiency caused by failure to process the event in time.

Description

Event processing method and device, storage medium and electronic device

Technical Field

The present invention relates to the field of computers, and in particular, to an event processing method and apparatus, a storage medium, and an electronic apparatus.

Background

At present, after a client detects that a target event occurs on a terminal where the client is located, the client sends prompt information to a user through the terminal to prompt the user that the target event occurs on the terminal and prompt the user to process the target event.

However, if the user fails to receive the prompt information or timely process the target event, the event processing efficiency is low.

That is, the event processing method of the related art has a problem of low efficiency in processing an event due to failure to process the event in time.

Disclosure of Invention

Embodiments of the present invention provide an event processing method and apparatus, a storage medium, and an electronic apparatus, so as to at least solve a technical problem of low event processing efficiency caused by failure to process an event in time.

According to an aspect of an embodiment of the present invention, there is provided an event processing method, including: detecting that a target event occurs on a target terminal where a first client logged in by using a first account is located; sending a first message to a second client logged in by using a second account, wherein the first message is used for indicating that the target event occurs on the target terminal, and the first account and the second account have an association relationship; receiving an operation instruction sent by the second client, wherein the operation instruction is used for instructing to execute a target operation corresponding to the target event on the target terminal; and responding to the operation instruction, and executing the target operation.

According to another aspect of the embodiments of the present invention, there is also provided an event processing method, including: receiving a first message sent by a first client logged in by using a first account on a second client logged in by using a second account, wherein the first message is used for indicating that a target event occurs on a target terminal where the first client is located, and the first account and the second account have an association relationship; and sending an operation instruction to the first client, wherein the operation instruction is used for instructing to execute a target operation corresponding to the target event on the target terminal.

According to another aspect of the embodiments of the present invention, there is also provided an event processing apparatus, including: the system comprises a detection unit, a processing unit and a processing unit, wherein the detection unit is used for detecting that a target event occurs on a target terminal where a first client logged in by using a first account is located; a sending unit, configured to send a first message to a second client that logs in using a second account, where the first message is used to indicate that the target event occurs on the target terminal, and the first account and the second account have an association relationship; a receiving unit, configured to receive an operation instruction sent by the second client, where the operation instruction is used to instruct a target terminal to execute a target operation corresponding to the target event; and the execution unit is used for responding to the operation instruction and executing the target operation.

According to another aspect of the embodiments of the present invention, there is also provided an event processing apparatus, including: the system comprises a receiving unit, a sending unit and a processing unit, wherein the receiving unit is used for receiving a first message sent by a first client logged in by using a first account on a second client logged in by using a second account, the first message is used for indicating that a target event occurs on a target terminal where the first client is located, and the first account and the second account have an incidence relation; a sending unit, configured to send an operation instruction to the first client, where the operation instruction is used to instruct to execute a target operation corresponding to the target event on the target terminal.

According to a further aspect of the embodiments of the present invention, there is also provided a storage medium having a computer program stored therein, wherein the computer program is configured to perform the above method when executed.

According to another aspect of the embodiments of the present invention, there is also provided an electronic apparatus, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the method by the computer program.

In the embodiment of the invention, a mode that a second client is used for monitoring and processing a target event occurring on a terminal where a first client is located is adopted, and the target event occurring on the target terminal where the first client logged in by using a first account is detected; sending a first message to a second client logged in by using a second account, wherein the first message is used for indicating that a target event occurs on a target terminal, and the first account and the second account have an association relationship; receiving an operation instruction sent by a second client, wherein the operation instruction is used for indicating that target operation corresponding to a target event is executed on a target terminal; the target operation corresponding to the target event is executed on the terminal where the first client is located in response to the operation instruction sent by the second client, so that the target event occurring on the terminal where the first client is located is monitored and processed by the second client, the technical effect of improving the processing efficiency of the target event on the terminal where the first client is located is achieved, and the technical problem of low event processing efficiency caused by failure of timely processing of the event is solved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

FIG. 1 is a schematic diagram of an application environment of an event processing method according to an embodiment of the invention;

FIG. 2 is a flow diagram illustrating an alternative event processing method according to an embodiment of the present invention;

FIG. 3 is a schematic flow diagram of an alternative event processing method according to an embodiment of the invention;

FIG. 4 is a schematic flow chart diagram illustrating an alternative event processing method according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of an alternative event processing method according to an embodiment of the invention;

FIG. 6 is a schematic diagram of an alternative event processing method according to an embodiment of the invention;

FIG. 7 is a schematic diagram of yet another alternative event processing method according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of yet another alternative event processing method according to an embodiment of the present invention;

FIG. 9 is a schematic diagram of yet another alternative event processing method according to an embodiment of the present invention;

FIG. 10 is a schematic diagram of yet another alternative event processing method according to an embodiment of the present invention;

FIG. 11 is a schematic diagram of yet another alternative event processing method according to an embodiment of the present invention;

FIG. 12 is a schematic diagram of an alternative event processing device according to an embodiment of the present invention;

FIG. 13 is a schematic diagram of an alternative event processing device according to an embodiment of the present invention;

FIG. 14 is a schematic diagram of an alternative electronic device according to an embodiment of the invention;

fig. 15 is a schematic structural diagram of an alternative electronic device according to an embodiment of the invention.

Detailed Description

In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

According to an aspect of an embodiment of the present invention, there is provided an event processing method. Alternatively, the event processing method can be applied to, but not limited to, the application environment shown in fig. 1. As shown in fig. 1, a first client 110-1 is installed on a first terminal 102 (similar to a target terminal in function), the first client 110-1 logs in by using a first account, a second client 110-2 is installed on a second terminal 108, the second client 110-2 logs in by using a second account, and the first account and the second account have an association relationship (or a binding relationship). The first account and the second account may be bound by the server 106 via the network 104.

After detecting that a target event (e.g., installation of malware) occurs on the terminal, the first terminal 102 sends a first message indicating that the target event occurs on the terminal to a second client 110-2 logged in using a second account through the network 104 via the first client 110-1. The second client 110-2 receives the first message sent by the first client 110-1, and sends an operation instruction for instructing to execute a target operation corresponding to the target event on the first terminal 102 to the first client 110-1 through the network 104. After receiving the operation instruction sent by the second client 110-2, the first client 110-1 responds to the operation instruction to execute the target operation indicated by the operation instruction.

Optionally, in this embodiment, the first terminal and the second terminal may include, but are not limited to, at least one of the following: mobile phones, tablet computers, and the like. The network may include, but is not limited to, a wireless network, a wired network, wherein the wireless network includes, but is not limited to: bluetooth, WIFI and other wireless communication enabled networks, including but not limited to: local area networks, metropolitan area networks, wide area networks. The server may include, but is not limited to, at least one of: PC and other equipment for providing service, cloud server. The above is only an example, and the present embodiment is not limited to this.

Optionally, in this embodiment, as an optional implementation manner, as shown in fig. 2, the event processing method may include:

s202, detecting that a target event occurs on a target terminal where a first client logged in by using a first account is located;

s204, sending a first message to a second client logged in by using a second account, wherein the first message is used for indicating that a target event occurs on a target terminal, and the first account and the second account have an association relation;

s206, receiving an operation instruction sent by the second client, wherein the operation instruction is used for instructing to execute a target operation corresponding to a target event on the target terminal;

and S208, responding to the operation instruction, and executing the target operation.

Alternatively, the event processing method can be, but is not limited to, a scenario of remotely installing and uninstalling mobile phone software. The method is applied to a scene of remotely cleaning mobile phone rubbish or a scene of remotely unloading malicious software.

Optionally, in this embodiment, it is detected that a target event occurs on a target terminal where a first client logged in by using a first account is located.

Optionally, the first account is used to identify an account used for logging in the first client, and may include, but is not limited to: the user obtains a user name, a mobile phone number and an account number associated with an account number of the third-party application through registration on the first client.

Alternatively, the target event may be an event occurring on any target terminal that can be detected by the first client, and may include, but is not limited to: events related to software installed or needing to be installed on the target terminal, events affecting the operational performance of the target terminal, fraud-related events.

Optionally, the events related to the software installed on the target terminal may include, but are not limited to: malware is installed, the number of installed software exceeds a predetermined number, and the installed malware is not successfully uninstalled within a predetermined time.

For example, when the target event is that malware is installed, the first client periodically checks a list of software installed on the target terminal and listens for newly installed software. And when the software list contains the malicious software or the newly installed software is the malicious software, detecting that a target event occurs on the target terminal.

Optionally, the event related to the software that needs to be installed on the target terminal may include, but is not limited to: the target software is not successfully downloaded or installed within a predetermined time.

For example, when the target event is that the target software is not successfully installed within 3 days after the target software download is completed, the first client checks a software list installed on the target terminal 3 days after the target software download is completed. And when the software list does not contain the target software, detecting that a target event occurs on the target terminal.

Optionally, the event affecting the operation performance of the target terminal may include, but is not limited to: insufficient storage space, junk files exceeding a specified data or size.

For example, when the target event is that the available storage space of the target terminal is less than 3G, the first client periodically detects the available storage space of the target terminal, and when the available storage space of the target terminal is less than 3G, the target event is detected to occur on the target terminal.

Alternatively, fraud-related events may include, but are not limited to: receiving or answering the incoming call of the fraud number, dialing the fraud number, receiving or answering the incoming call of the unknown number, receiving the short message or multimedia message of the fraud number or the unknown number, and receiving the short message or multimedia message containing the target keyword.

Alternatively, the fraud number may be a number marked as fraud by the user during the course of making a call or after the call is completed, or a number marked as fraud after receiving a fraud message, and the number of marking may be at least once. The unknown number may be a number that a caller dials through some client or a number that is selected not to be displayed in a call function, resulting in the caller's number not being displayed on the callee's terminal. The target keyword may be a word belonging to a set of target keywords, and the target keyword is used for identifying a keyword (e.g., a prize) of an abnormal short message (e.g., a fraud short message, a short message including a phishing website).

For example, when the target event is that the target terminal answers the incoming call of the fraud number, the first client detects the telephone number answered by the target terminal, and when the target terminal answers the incoming call of the fraud number, the target event is detected to occur on the target terminal.

Optionally, in this embodiment, a first message is sent to a second client that logs in using a second account, where the first message is used to indicate that a target event occurs on a target terminal, and the first account and the second account have an association relationship.

Alternatively, the first client and the second client may be the same type of client. The client integrates the function of assisting event processing and the function of assisted event processing. The first client and the second client may also be different types of clients with corresponding relationships (for example, the first client and the second client may be application software with corresponding relationships under the same software product), the first client has a function of assisted event processing integrated thereon, and the second client has a function of assisting event processing integrated thereon.

For example, the first client and the second client are two types of application software under a remote assistance product developed by a software developer, the first client is the application software used by an assistor, and the second client is the application software used by the assistor.

Optionally, the first account and the second account have an association relationship. The association between the first account and the second account may be one of a plurality of associations. The plurality of associations may be: the identity relationship between the first account and the second account is, for example, a child and a parent, a grandchild (or grandchild) and a grandfather (or grandmother), or other relatives, and also, for example, a social relationship between a nurse and an employer. The first account number and the second account number may be associated in a variety of ways.

In an alternative embodiment, the first account and the second account may be associated through direct interaction. Ways of association include, but are not limited to: scanning a two-dimensional code in a second client logged in by using a second account through a first client logged in by using a first account, or scanning the two-dimensional code in the first client logged in by using the first account through the second client logged in by using the second account, and determining the incidence relation between the two clients through interaction between the two clients; inputting a second account in a first client logged in by using the first account, requesting for association, and determining to perform association by using the second client logged in by using the second account, or inputting the first account in the second client logged in by using the second account, requesting for association, determining to perform association by using the first client logged in by using the first account, and completing association. The message for requesting association may include description information of the first account and a type of the requested association relationship.

For example, an identification code (e.g., a two-dimensional code) of the first account may be called up on the first client, the identification code of the first account is scanned by using a code scanning function in the second client, and the type of association relationship are selected from a window popped up in the first client or the second client to complete the association. For another example, the second account is input in the first client, the type of association and the type of association relationship are selected, an association request is sent to the second client based on the selected information, association is determined to be performed in the second client, and association is completed.

In another optional embodiment, the first account and the second account may be associated by means of transfer of a third party application.

Optionally, a binding request sent by a third party application logged in by a second client through a fourth account may be received in a third party application logged in by using the third account (e.g., a social network platform), where the binding request is used to request binding of a first account and a second account, the first account and the third account have an association relationship, and the second account and the fourth account have an association relationship; associating the third account with the fourth account; and associating the fourth account with the second account.

Optionally, the third-party application logged in by using the third account may be application software installed on the terminal where the first client is located, and the third-party application logged in by using the fourth account may be application software installed on the terminal where the second client is located. The binding request may be sent via a sharing applet in a third party application, an H5 link, etc. The third account and the fourth account can be bound by clicking a shared applet, an H5 link, and the like in a third-party application logged in by using the third account.

Alternatively, in a third party application, each user may generate one openId for each public number, application, and applet, and a user may have multiple different openids for multiple public numbers, applications, and applets, but only one unionId for all public numbers, applications, and applets under the same open platform account. The first client, the second client, the third-party applet and the public number belong to the same open platform and account of the same developer, so that only openIds are different, and the unionIds of the same user are the same.

Optionally, the first client may have a first client account guid, log in a third party application, and the third party application may also assign a unionId and openId to the first client. Therefore, the association between the first client account (first account) and the third party application account (third account) can be performed by logging in the third party application.

In an optional implementation manner, in a case that the first client is installed and logged in the target terminal, after the fourth account and the third account are associated, the first client is skipped to, the third account and the first account are associated, and then the association between the first account and the second account is completed.

In another optional implementation manner, under the condition that the first client is not installed on the target terminal, after the fourth account is associated with the third account, before the third account is associated with the first account, the first client is downloaded and installed on the target terminal, and after the first account is used for logging in the first client, the first account is associated with the third account, so that the association between the first account and the second account is completed.

Optionally, downloading and installing the first client on the target terminal may be performed by: receiving a third message which is sent by a third party application logged in by using a third account and carries a download link pointing to the installation package of the first client; downloading the installation package of the first client by using the download link, and installing the first client; and logging in the first client by using the first account, and associating the first account with the third account after logging in the first client.

Optionally, before, after, or during sending the first message to the second client logged in by using the second account, prompt information for prompting that a target event occurs on the target terminal may be displayed on the target terminal by the first client (e.g., by performing a pop-up on the target terminal), and an operation identifier (e.g., a button) that triggers the target terminal to perform a specified operation (which may be the same as or different from the target operation) corresponding to the target event is provided. And executing the specified operation after detecting the touch operation of the operation identifier.

Optionally, the association relationship between the first account and the second account may be a one-to-one, one-to-many, many-to-one, many-to-many relationship.

For example, one assisting account may have only one assisted account, one assisting account may have a plurality of assisted accounts, one assisted account may have only one assisting account, and one assisted account may have a plurality of assisting accounts.

Optionally, when there are a plurality of second accounts associated with the first account, the priority of the second account may be set, and when there are a plurality of received operation instructions, a target operation corresponding to the operation instruction sent by the second account with the highest priority is executed.

Optionally, in this embodiment, an operation instruction sent by the second client is received, where the operation instruction is used to instruct to execute a target operation corresponding to the target event on the target terminal.

Alternatively, the operation instruction may be sent by: and after receiving the first message, the second client displays prompt information for prompting that a target event occurs on the target terminal on the terminal where the second client is located, and sends an operation instruction to the first client after detecting the touch operation of the operation identifier corresponding to the target operation.

Optionally, after receiving the operation instruction sent by the second client, the operation instruction may be parsed, the indication information for indicating the target event may be obtained, and the target operation corresponding to the indication information may be obtained.

For example, the target events occurring on the target terminal are: installing malicious software X, wherein the operation instruction is as follows: uninstall the malware X, or pop-up prompts to install the malware X and provides an operation identifier (e.g., a button) to uninstall the malware X. Then, the indication information indicating the target event may be: and the malicious software X acquires the target operation as follows: and uninstalling the malicious software X, or prompting the installation of the malicious software X by popup window to provide an operation identifier for uninstalling the malicious software X.

Optionally, in this embodiment, the target operation is executed in response to the operation instruction. The target operation to be performed may be different for different operation instructions. The target operation may include, but is not limited to: the reminding operation is used for reminding the occurrence of the target event, and the processing operation is used for processing the target event.

In an optional embodiment, in the case that the indication information indicates that the target terminal does not install the target software before the target time point, first prompt information for prompting the installation of the target software is displayed.

Alternatively, the target time point may be a time point corresponding to an end point of a predetermined time period (for example, 1 day, 3 days, a week, a half month, and the like) starting from a time point at which the target terminal finishes downloading the target software or from a time point at which instruction information for instructing the first client to download the installation package of the target software according to the software identifier is received.

Optionally, while displaying the first prompt information for prompting the target software to be installed, an operation identifier (e.g., a button) for installing the target software may be provided, so as to quickly install the target software.

Optionally, before detecting that a target event occurs on a target terminal where a first client logged in by using a first account is located, receiving a second message sent by a second client, wherein the second message carries a software identifier of target software, and the second message is used for instructing the first client to download an installation package of the target software according to the software identifier; and downloading the installation package of the target software corresponding to the software identification.

Optionally, the software identification of the target software may include at least one of: the package name of the installation package of the target software, the outer code (e.g., serial number) of the target software, and the download address of the installation package of the target software. The software identification of the target software may also include a version number of the target software. And the installation package of the target software can be downloaded through the software identification of the target software.

For example, the software identifier of the target software carried in the second message sent by the second client is the package name and version number of the installation package of the target software, and because the corresponding relationship between the package name and version number of the software installation package in the software list in the first client and the second client and the software is consistent. Therefore, the first client can locate the installation package of the target software according to the package name and the version number of the installation package of the target software, and further download the installation package.

In another alternative embodiment, in the case where the indication information indicates that malware is installed on the target terminal, at least one of the following two types of operations may be performed: uninstalling the malicious software; and displaying a second prompt message for prompting the uninstallation of the malicious software.

Optionally, an auxiliary function permission may be set at the first client, and when the auxiliary function permission is obtained, the malware may be directly uninstalled according to an instruction of the second client, and when the auxiliary function permission is not obtained, the target operation is a reminding operation, for example, prompt information for prompting existence of the malware and uninstalling of the malware is displayed, and an operation identifier (for example, a button) for uninstalling the malware may be provided, so that the malware is quickly installed.

In yet another alternative embodiment, in the case that the indication information indicates that the storage space of the target terminal is lower than the target threshold, at least one of the following two types of operations may be performed: clearing junk files on a target terminal; and displaying a third prompt message for prompting to clear the junk files on the target terminal.

Optionally, the first client may directly clear the junk file on the target terminal according to the instruction of the second client, may also display a prompt message for prompting that the storage space is insufficient and clearing the junk file on the target terminal, and may also provide an operation identifier (e.g., a button) for clearing the junk file, so as to quickly clear the junk file.

In yet another alternative embodiment, in case that the indication information indicates that the target terminal has a fraud-related event, prompt information for reminding fraud may be displayed on the target terminal.

For example, in the case where the target event is that the target terminal answers an incoming call of a fraud number, prompt information for prompting the fraud number may be displayed on the target terminal (e.g., the telephone number X is a fraud number, being carefully deceived).

Optionally, after the target operation is executed in response to the operation instruction, a response message may be sent to the second client to indicate that the execution condition of the operation instruction is: the target operation is executed and not executed.

Therefore, in the related art, after detecting that the target event occurs on the terminal where the client is located, the client sends prompt information to the user through the terminal to prompt the user that the target event occurs on the terminal and prompt the user to process the target event. With the method, if the user fails to receive the prompt message or to process the target event in time, the event processing efficiency is low. In the application, a target event is detected to occur on a target terminal where a first client logged in by using a first account is located; sending a first message to a second client logged in by using a second account, wherein the first message is used for indicating that a target event occurs on a target terminal, and the first account and the second account have an association relationship; receiving an operation instruction sent by a second client, wherein the operation instruction is used for indicating that target operation corresponding to a target event is executed on a target terminal; and responding to the operation instruction, and executing the target operation, so that the target event occurring on the terminal where the first client is located can be monitored and processed through the second client, the processing efficiency of the target event on the terminal where the first client is located is improved, and the technical problem of low event processing efficiency caused by failure of timely processing the event is solved.

As an optional scheme, after receiving the operation instruction sent by the second client, the method further includes:

s1, analyzing the operation instruction, and acquiring indication information for indicating the target event;

and S2, acquiring the target operation corresponding to the instruction information.

According to the embodiment, the operation instruction is analyzed, the target operation corresponding to the indication information for indicating the target event is obtained, and the target event corresponding to the operation information can be determined due to the fact that the obtained indication information indicates the target event, so that the accuracy of the target operation is improved.

Optionally, in response to the operation instruction, the performing the target operation includes:

s1, when the instruction information indicates that the target terminal has not installed the target software before the target time point, displays first instruction information for instructing installation of the target software.

By the embodiment, the prompt information for prompting the installation of the target software is displayed, so that the probability that the user of the target terminal knows that the target software needs to be installed can be improved, and the success rate of the installation of the target software is improved.

Optionally, before detecting that a target event occurs on a target terminal where a first client logged in by using a first account is located, the method further includes:

s1, receiving a second message sent by a second client, wherein the second message carries a software identifier of the target software, and the second message is used for instructing the first client to download the installation package of the target software according to the software identifier;

and S2, responding to the second message, and downloading the installation package of the target software corresponding to the software identification.

By the embodiment, the target terminal can be assisted to download the target software by responding to the second message and downloading the installation package of the target software corresponding to the software identifier carried in the second message, and the user of the target terminal is not required to execute additional operations (for example, clicking a download link and the like), so that the download efficiency of the target software is improved.

in the case that the indication information indicates that the target terminal is provided with the malicious software, performing at least one of the following operations:

s1, uninstalling the malicious software;

and S2, displaying a second prompt message for prompting the uninstalling of the malicious software.

According to the embodiment, at least one of direct uninstallation of the malicious software and display of the prompt message for uninstalling the malicious software is executed, so that the probability of discovering and uninstalling the malicious software by the user of the target terminal can be improved, and the probability of uninstalling the malicious software is improved.

in the case that the indication information indicates that the storage space of the target terminal is lower than the target threshold, performing at least one of the following operations:

s1, clearing the junk files on the target terminal;

and S2, displaying a third prompting message for prompting to clear the junk files on the target terminal.

According to the embodiment, at least one of clearing the junk files on the target terminal and displaying the prompt message for prompting clearing of the junk files on the target terminal is executed, so that the probability of clearing the junk files by a user of the target terminal can be improved, the running performance of a system is guaranteed, and the user experience is improved.

As an optional scheme, before detecting that a target event occurs on a target terminal where a first client logged in by using a first account is located, the method further includes:

s1, receiving a binding request sent by a third party application logged in by a second client through a fourth account in the third party application logged in by the third account, wherein the binding request is used for requesting to bind a first account and a second account, the first account and the third account have an association relationship, and the second account and the fourth account have an association relationship;

s2, associating the fourth account with the third account;

and S3, associating the third account with the first account.

Through the embodiment, the association of the first account and the second account is carried out in a third-party application transfer mode, so that the limitation of direct association on the distance of the terminal can be avoided, and the account binding efficiency is improved.

Optionally, before associating the third account with the first account, the method further includes:

receiving a third message which is sent by a third party application logged in by using a third account and carries a download link, wherein the download link points to an installation package of the first client;

downloading the installation package of the first client pointed by the download link, and installing the first client;

and logging in the first client by using the first account.

According to the embodiment, the target terminal is guided to install the first client through the third-party application, so that the binding of the first account and the second account is completed, the condition of association failure caused by the fact that the target terminal does not install the first client can be reduced, the association process can be guided, and user experience is improved.

According to another aspect of the embodiments of the present invention, there is provided an event processing method, as shown in fig. 3, the event processing method may include:

s302, receiving a first message sent by a first client logged in by using a first account on a second client logged in by using a second account, wherein the first message is used for indicating that a target event occurs on a target terminal where the first client is located, and the first account and the second account have an association relation;

s304, an operation instruction is sent to the first client, wherein the operation instruction is used for instructing to execute target operation corresponding to the target event on the target terminal.

Alternatively, the event processing method can be, but is not limited to, a scenario of remotely installing and uninstalling mobile phone software. For example, the method is applied to a scene of remotely cleaning mobile phone rubbish or a scene of remotely unloading malicious software.

Optionally, in this embodiment, a first message sent by a first client logged in by using a first account is received on a second client logged in by using a second account, where the first message is used to indicate that a target event occurs on a target terminal where the first client is located, and the first account and the second account have an association relationship.

Optionally, the second account is used to identify an account used for logging in the second client, and may include, but is not limited to: and the user obtains a user name, a mobile phone number and an account number associated with the account number of the third-party application through registration on the second client.

Alternatively, the target event may be an event occurring on any target terminal, and may include but is not limited to: events related to software installed or needing to be installed on the target terminal, events affecting the operational performance of the target terminal, fraud-related events. The first client and the second client may be the same type of client, and may be different types of clients having a correspondence relationship. The association relationship between the first account and the second account may be one of multiple association relationships, and the target event, the association relationship between the first client and the second client, and the association relationship between the first account and the second account are similar to the foregoing, and are not described herein again.

In an alternative embodiment, the first account and the second account may be associated through direct interaction. The direct interaction manner is similar to the above, and is not described herein.

Optionally, a binding request sent by a third party application logged in by using a fourth account to the third party application logged in by using the third account may be used, where the binding request is used to request binding of a first account and a second account, the first account and the third account have an association relationship, and the second account and the fourth account have an association relationship.

Optionally, a binding request sent by a first client through a third-party application logged in by using a third account may be received in the third-party application logged in by using a fourth account, where the binding request is used to request binding of a first account and a second account, the first account and the third account have an association relationship, and the second account and the fourth account have an association relationship; associating the third account with the fourth account; and associating the fourth account with the second account.

Alternatively, the binding request may be sent via sharing applets, H5 links, etc. in a third party application. The third account and the fourth account can be bound by clicking a shared applet, an H5 link, and the like in a third-party application logged in by using the fourth account.

Optionally, the second client may have a second client account guid, log in to the third party application, and the third party application may also assign a unionId and openId to the second client. Therefore, the association between the second client account (second account) and the third party application account (fourth account) can be performed by logging in the third party application.

In an optional implementation manner, when a second client is installed and logged in a terminal where a third-party application logged in by a fourth account is located, after the fourth account and the third account are associated, the second client is skipped to, the fourth account and the second account are associated, and then the association between the first account and the second account is completed.

In another optional implementation manner, in a case that a second client is not installed on a terminal where a third-party application where a fourth account logs in is located, after the fourth account and the third account are associated, before the fourth account and the second account are associated, the second client is downloaded and installed on the terminal, and after the second account logs in the second client, the fourth account and the second account are associated, so that the association between the first account and the second account is completed.

Optionally, downloading and installing the first client on the target terminal may be performed by: receiving a fourth message which is sent by a third party application logged in by using a fourth account and carries a download link pointing to an installation package of a second client; downloading the installation package of the second client by using the download link, and installing the second client; and logging in the second client by using the second account, and associating the second account with the fourth account after logging in the second client.

Optionally, the association relationship between the first account and the second account may be a one-to-one, one-to-many, many-to-one, many-to-many relationship. The second clients logged in by the second accounts can be assisted by the second clients logged in by the second accounts to perform event processing respectively.

Optionally, in this embodiment, an operation instruction is sent to the first client, where the operation instruction is used to instruct to execute a target operation corresponding to the target event on the target terminal.

Optionally, the operation instruction may be generated based on a preset correspondence between a target event and a target operation, or after receiving the first message, using a second client to prompt a terminal where the second client is located for the target event, and an operation identifier for indicating a target operation for processing the target event, and generating the operation instruction in response to the touch operation of the received operation identifier. The operation identifier may be one or more.

Optionally, before receiving a first message sent by a first client logged in by using a first account, a second message may be pushed to the first client, where the second message carries a software identifier of target software, and the second message is used to instruct the first client to download an installation package of the target software according to the software identifier.

Alternatively, the target operation may include, but is not limited to: the reminding operation is used for reminding the occurrence of the target event, and the processing operation is used for processing the target event.

In an alternative embodiment, in the case that the first message indicates that the target terminal has not installed the target software before the target time point, the target operation may be: and displaying first prompt information for prompting the installation of the target software.

Optionally, the target time point may be a time point when the target terminal finishes downloading the target software or a time point corresponding to an end point of a predetermined time period, where the time point is a time point when the first client receives instruction information for instructing the first client to download the installation package of the target software according to the software identifier.

Optionally, the target operation may also be: the method comprises the steps of providing an operation identifier for installing the target software while displaying first prompt information for prompting the target software to be installed so as to install the target software quickly.

In another alternative embodiment, in the case where the first message indicates that malware is installed on the target terminal, the target operation may be at least one of: uninstalling the malicious software; and displaying a second prompt message for prompting the uninstallation of the malicious software.

Alternatively, an auxiliary function indicating whether to allow the second client to directly perform the software uninstalling operation may be set at the first client, and in the case where the auxiliary function is set to be yes, the target operation may be: and directly uninstalling the malicious software, wherein under the condition that the auxiliary function is set to be negative, the target operation can be as follows: the reminding operation can also be as follows: an operation identification (e.g., a button) to uninstall the malware is provided to quickly install the malware.

In yet another alternative embodiment, in the case that the first message indicates that the storage space of the target terminal is lower than the target threshold, the target operation may be at least one of: clearing junk files on a target terminal; and displaying a third prompt message for prompting to clear the junk files on the target terminal.

In yet another alternative embodiment, in case that the first message indicates that a fraud-related event occurs at the target terminal, the target operation may be: and displaying prompt information for reminding fraud.

Therefore, in the related art, after detecting that the target event occurs on the terminal where the client is located, the client sends prompt information to the user through the terminal to prompt the user that the target event occurs on the terminal and prompt the user to process the target event. With the method, if the user fails to receive the prompt message or to process the target event in time, the event processing efficiency is low. In the application, a first message sent by a first client logged in by using a first account is received on a second client logged in by using a second account, wherein the first message is used for indicating that a target event occurs on a target terminal where the first client is located, and the first account and the second account have an association relationship; and sending an operation instruction to the first client, wherein the operation instruction is used for instructing a target terminal to execute target operation corresponding to the target event, so that the target event occurring on the terminal where the first client is located can be monitored and processed through the second client, the processing efficiency of the target event on the terminal where the first client is located is improved, and the technical problem of low event processing efficiency caused by failure of timely processing the event is solved.

As an alternative, the target operation is: under the condition that the first message indicates that the target terminal does not install the target software before the target time point, displaying first prompt information for prompting the installation of the target software; under the condition that the first message indicates that the target terminal is provided with the malicious software, the malicious software is uninstalled, and/or a second prompt message for prompting the uninstallation of the malicious software is displayed; or, in the case that the first message indicates that the storage space of the target terminal is lower than the target threshold, the junk file on the target terminal is cleared, and/or a third prompt message for prompting clearing of the junk file on the target terminal is displayed.

According to the embodiment, the target operation is at least one of a reminding operation for reminding the target event and a processing operation for processing the target event, so that the probability that the user of the target terminal knows the target event can be improved, and the processing efficiency of the target event can be improved.

Optionally, before receiving a first message sent by a first client logged in by using a first account, the method further includes:

s1, pushing a second message to the first client, wherein the second message carries the software identifier of the target software, and the second message is used for instructing the first client to download the installation package of the target software according to the software identifier.

By the embodiment, the second message is used for carrying the software identifier of the target software, so that the target terminal can be assisted to download the target software, and the downloading efficiency of the target software is improved.

As an optional scheme, before receiving a first message sent by a first client logged in by using a first account, the method further includes:

and sending a binding request to a third party application logged in by using a third account by using a third party application logged in by using a fourth account, wherein the binding request is used for requesting to bind a first account and a second account, the first account and the third account have an association relationship, and the second account and the fourth account have an association relationship.

The event processing method of the present invention will be described below with reference to the following examples. In this example, the assisted person is the teacher's ancestor (e.g., mom, grandpa, milk). The client A and the client B are two pieces of safety management software under the same remote assistance product. The client a (similar to the aforementioned first client function) logged in by the assisted person on the terminal a using the account a (similar to the aforementioned first account function), and the client B (similar to the aforementioned second client function) logged in by the assisted person on the terminal B using the account B (similar to the aforementioned second account function). The account a and the account B have an association relationship therebetween. The user B may remotely assist the user a in processing the service on the terminal a through the client B and the client a, for example, installing software, uninstalling software, cleaning a memory, and the like. The terminal A and the terminal B are both mobile phones.

The assisted person can use the client A to scan malicious software, check and kill viruses, clear mobile phone garbage, recognize fraud short message calls, download mobile phone software and the like, and provides safety guarantee and management assistance for the assisted person. The client B can integrate safety protection, physical examination acceleration, harassment interception and software management, and as assistance side software in a remote assistance product, an assistor can use the client B to provide remote assistance for an assisted person (such as mobile phone garbage cleaning, mobile phone card pause optimization, mobile phone software downloading and installation and the like).

The event processing method in this example can be divided into two core steps of relationship binding and remote assistance, and the relationship binding is a precondition for realizing the remote assistance. The following describes the event processing method in this example in detail, and as shown in fig. 4, the event processing method may include the following steps:

at step 402, remote assistance relationship binding of the assistor and the assisted person is performed.

The remote assistance is primarily to establish account association between the assistor and the two sides of the assisted person, that is, assistance relationship binding. The assistance relationship binding may be implemented by associating with a third party application system.

As shown in fig. 5, fig. 6, fig. 7 and fig. 8, the binding flow of the assistance relationship may be divided into a binding flow of the assistance side and a binding flow of the assisted side.

For the assistance side, as shown in fig. 5, the functions integrated on the client B include: logging in a third-party application to initiate binding, reminding by malicious software of an assisted end, remotely downloading a mobile phone application and the like. The function may be displayed by an operation identifier on the client B.

As shown in fig. 5 and fig. 6, the binding flow of the assistance side includes the following steps:

step 1, detecting that an operation identifier (for example, an operation identifier of an assisted person is added) used for logging in a third-party application to initiate assistance binding on a client B is touched.

Step 2, judging whether a third party application account (account D, similar to the fourth account in function) logs in, if so, executing step 4, and if not, executing step 3;

and 3, logging in the account D, and associating the logged-in account D with the account B.

And 4, sharing and initiating a binding request through the third-party application.

The third-party application sharing may be sharing the third-party applet carrying the guid, unionId and openId information, the public number H5 to the third-party application of the assisted person (the third-party application logging in using account C (similar to the third account) for action).

For the assisted side, as shown in fig. 5, the functions integrated on the client a include: and logging in a third-party application to determine an assistance relationship, malicious software uninstalling reminding, downloading and installing a mobile phone application and the like. The function may be displayed through an operation identifier on the client a.

The binding process of the assisted side may include binding of the account C and the account D and binding of the account a and the account C.

As shown in fig. 5 and 7, the binding process of the account C and the account D includes the following steps:

step 1, detecting that an applet or H5 connection shared by an account D is clicked in a third-party application logged in by using the account C, and popping up a window.

Step 2, detecting a touch operation of an operation identifier used for allowing the account C and the account D to be bound in the pop-up window, and determining the binding relationship of the account C and the account D for remote assistance.

And popping up a window on the terminal A, wherein the popped up window comprises the operation identification allowing binding and the operation identification not allowing binding. And allowing the helper to log in the applet or the public number by clicking the operation identifier allowing the binding, thereby obtaining the unionId and the openId of the helper, binding the account C and the account D, and further completing the association of the account C and the account D.

So far, the association between the client B related account (guid, unionId and openId) of the assisting side and the third party applet or public account (unionId and openId) of the assisted side is completed. Because the unionId in the applet or the public account of the assisted side is consistent with the unionId distributed by the third-party application in the client a, the final binding of the assistance relationship can be completed if the assisted person downloads and logs in the client a.

And 3, after the touch operation for rejecting the operation identifier for binding the account C and the account D in the pop-up window is detected, ending the process.

Optionally, if the terminal a has installed and logged in the client a by using the account a, after binding the account C and the account D, an operation identifier for binding the account C and the account a may be provided in a skipped window or page, and when a touch operation on the operation identifier is detected, the terminal a skips to the client a to complete the binding of the account C and the account a.

Optionally, if the client a is not installed on the terminal a, after the account C and the account D are bound, prompt information prompting downloading of the installation client a may be displayed on the terminal a in a pop-up window manner, so as to guide the assisted person to download the installation client a.

After the client a finishes downloading, the account a is used for logging in the client a, and the account a and the account C can be bound on the client a. As shown in fig. 5 and 7, the binding process of account a and account C includes the following steps:

step 1, after logging in a client A by using an account A, detecting a touch operation of an operation identifier used for logging in a third-party application to determine a remote assistance relationship on the client A.

The assisted person clicks the operation identifier on the client A for logging in a third-party application to confirm the remote assistance relationship.

And 2, judging whether the account C logs in, if so, executing the step 3, otherwise, executing the step 4.

And 3, logging in the account C, and associating the logged-in account C with the account A.

And 4, judging whether the account C has a binding relationship of remote assistance, finishing the operation if the judgment result is yes, and otherwise, executing the step 5.

And 5, sending binding sharing to the third-party application logged in by using the account D, and reminding an assistor to perform binding association through the third-party application.

The binding of the remote assistance relationship between the account B and the account A can be completed by associating the account B with the account D, associating the account D with the account C and associating the account C with the account A.

As shown in fig. 9, the assistor is the mother of the assistor, the assistor shares a link for binding the assistance relationship with the assistor in the third-party application, the assistor clicks the link shared by the assistor, and then pops up a window shown in the right side of fig. 9, and the assistor immediately logs in the client a by clicking a button of the client a, and jumps to the client a to complete the binding of the assistance relationship.

In step 404, the assistor remotely assists the assisted person in performing event processing.

The event processing performed by the assistor for remote assistance by the assistor may include, but is not limited to: downloading and installing mobile phone software, uninstalling the mobile phone software, cleaning mobile phone garbage and the like. The same assistor may assist multiple assisted persons to perform event processing, as shown in fig. 10, in the client a, the assistor may remotely assist the first assisted person and the second assisted person to perform event processing. When the operation identifier of "remote downloading" is clicked, the user jumps to the interface shown on the right side of fig. 10, and the first assisted person can select the mobile phone software to download and install in the interface.

For the process of remotely assisting in downloading and installing the mobile phone software, the assistor can initiate the remote downloading and installing process, remotely assist in installing the mobile phone software on the client A and remind the assisted person of downloading and installing. The process for downloading and installing the mobile phone software with remote assistance comprises the following steps:

step 1, the assisting end selects mobile phone software for the assisted person at the client B, clicks one key to assist the assisted person to download and install, and then the identification data of the selected mobile phone software is pushed to the assisted end (the client A of the assisted end) through the remote assistance product background.

And 2, the client A of the assisted end receives the push message of the background, and the client A silently downloads the installation package of the mobile phone software under the condition that WIFI exists and networking is available.

And 3, finishing downloading and reminding the assisted person to install.

After downloading is finished, the helped person can be reminded to install the mobile phone software in a popup mode.

For the process of remotely assisting in uninstalling the mobile phone software, the assistor can initiate the process of remotely uninstalling or uninstalling the mobile phone software, and remotely assist in uninstalling the mobile phone software on the client a. As shown in fig. 11, the process of remotely assisting to uninstall the mobile phone software includes the following steps:

step 1, the client A periodically checks a mobile phone installation software list and monitors newly installed applications.

The client A integrates virus checking and killing and malicious software scanning functions, when the client A runs in the background, malicious software scanning can be carried out regularly, and newly installed applications are monitored.

And 2, the client A finds the malicious software, if the client A has the auxiliary click permission, the client A pops the window to inform the assisted person after silent unloading, and otherwise, the client A reports the malicious software to the assisted person and pops the window to remind the assisted person.

If the client A detects that the malicious software is installed on the terminal A, the client A reminds the assisted person to unload the malicious software and reports the malicious software information to the assisting terminal. If the client A sets the assistant click right (allows assistance), the assistor can choose to unload the client A in a silent mode.

The process of remotely assisting in cleaning the mobile phone garbage is similar to the process of downloading the malicious software, and is not described herein again.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.

Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM) and includes instructions for enabling a terminal device (e.g., a smart phone) to execute the method according to the embodiments of the present invention.

According to another aspect of the embodiments of the present invention, there is also provided an event processing apparatus, as shown in fig. 12, including:

(1) a detecting unit 1202, configured to detect that a target event occurs on a target terminal where a first client logged in by using a first account is located;

(2) a sending unit 1204, configured to send a first message to a second client that logs in using a second account, where the first message is used to indicate that a target event occurs on a target terminal, and the first account and the second account have an association relationship;

(3) a receiving unit 1206, configured to receive an operation instruction sent by the second client, where the operation instruction is used to instruct a target terminal to execute a target operation corresponding to a target event;

(4) and an execution unit 1208, configured to execute the target operation in response to the operation instruction.

Alternatively, the event processing event can be, but is not limited to, a scenario of remotely installing and uninstalling the mobile phone software. The method is applied to a scene of remotely cleaning mobile phone rubbish or a scene of remotely unloading malicious software.

Optionally, the first account and the second account have an association relationship. The association between the first account and the second account may be one of a plurality of associations. The plurality of associations may be: an identity relationship, e.g., a relationship of relativity, a social relationship, between the first account number and the second account number. The first account number and the second account number may be associated in a variety of ways.

Optionally, the software identification of the target software may include at least one of: name of the target software, external code (e.g., serial number) of the target software, download address of the installation package of the target software. The software identification of the target software may also include a version number of the target software. And the installation package of the target software can be downloaded through the software identification of the target software.

As an optional solution, the apparatus further includes:

(1) the analysis unit is used for analyzing the operation instruction after receiving the operation instruction sent by the second client and acquiring indication information for indicating the target event;

(2) and the acquisition unit is used for acquiring the target operation corresponding to the indication information.

Optionally, the executing unit 1208 includes:

and the first display module is used for displaying first prompt information for prompting the target software to be installed under the condition that the indication information indicates that the target terminal does not install the target software before the target time point.

Optionally, the apparatus further comprises:

(1) the first receiving unit is used for receiving a second message sent by a second client before detecting that a target event occurs on a target terminal where a first client logged in by using a first account is located, wherein the second message carries a software identifier of target software, and the second message is used for indicating the first client to download an installation package of the target software according to the software identifier;

(2) and the first downloading unit is used for responding to the second message and downloading the installation package of the target software corresponding to the software identification.

Optionally, the execution unit 1208 includes at least one of:

(1) the uninstalling module is used for uninstalling the malicious software under the condition that the indication information indicates that the target terminal is provided with the malicious software;

(2) and the second display module is used for displaying a second prompt message for prompting to uninstall the malicious software under the condition that the indication information indicates that the malicious software is installed on the target terminal.

Optionally, the execution unit 1208 includes at least one of:

(1) the clearing module is used for clearing the junk files on the target terminal under the condition that the indication information indicates that the storage space of the target terminal is lower than the target threshold value;

(2) and the third display module is used for displaying a third prompt message for prompting to clear the junk files on the target terminal under the condition that the indication information indicates that the storage space of the target terminal is lower than the target threshold.

As an optional solution, the apparatus further includes:

(1) the second receiving unit is used for receiving a binding request sent by a second client through a third party application logged in by using a fourth account in the third party application logged in by using the third account before a target event is detected to occur on a target terminal where the first client logged in by using the first account is located, wherein the binding request is used for requesting to bind the first account and the second account, the first account and the third account have an association relationship, and the second account and the fourth account have an association relationship;

(2) the first association unit is used for associating the fourth account with the third account;

(3) and the first association unit associates the third account with the first account.

Optionally, the apparatus further comprises:

(1) a third receiving unit, configured to receive a third message carrying a download link sent by a third-party application logged in by using a third account before associating the third account with the first account, where the download link points to an installation package of the first client;

(2) the second downloading unit is used for downloading the installation package of the first client pointed by the downloading link and installing the first client;

(3) and the login unit is used for logging in the first client by using the first account.

According to another aspect of the embodiments of the present invention, there is provided an event processing apparatus, as shown in fig. 13, the event processing apparatus may include:

(1) a receiving unit 1302, configured to receive, on a second client logged in using a second account, a first message sent by a first client logged in using a first account, where the first message is used to indicate that a target event occurs on a target terminal where the first client is located, and the first account and the second account have an association relationship;

(2) a sending unit 1304, configured to send an operation instruction to the first client, where the operation instruction is used to instruct a target operation corresponding to the target event to be performed on the target terminal.

Alternatively, the event processing device can be, but is not limited to, a scenario of remotely installing and uninstalling mobile phone software. For example, the method is applied to a scene of remotely cleaning mobile phone rubbish or a scene of remotely unloading malicious software.

Optionally, the second account is used to identify an account used for logging in the second client, and may include, but is not limited to: the user obtains a user name, a mobile phone number and an account number associated with an account number of the third-party application through registration on the first client.

As an alternative, the target operation may be: under the condition that the first message indicates that the target terminal does not install the target software before the target time point, displaying first prompt information for prompting the installation of the target software; under the condition that the first message indicates that the target terminal is provided with the malicious software, the malicious software is uninstalled, and/or a second prompt message for prompting the uninstallation of the malicious software is displayed; or, in the case that the first message indicates that the storage space of the target terminal is lower than the target threshold, the junk file on the target terminal is cleared, and/or a third prompt message for prompting clearing of the junk file on the target terminal is displayed.

Optionally, the apparatus further comprises:

(1) the pushing unit is used for pushing a second message to the first client before receiving a first message sent by the first client logged in by using the first account, wherein the second message carries a software identifier of the target software, and the second message is used for indicating the first client to download the installation package of the target software according to the software identifier.

As an optional solution, the apparatus further includes:

(1) the device comprises a sending unit, a binding unit and a processing unit, wherein the sending unit is used for sending a binding request to a third party application logged in by a third account through the third party application logged in by a fourth account before receiving a first message sent by a first client logged in by the first account, the binding request is used for requesting to bind the first account and a second account, the first account and the third account have an association relationship, and the second account and the fourth account have an association relationship.

According to a further aspect of embodiments of the present invention, there is also provided a storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the above-mentioned method embodiments when executed.

Alternatively, in the present embodiment, the storage medium may be configured to store a computer program for executing the steps of:

s1, detecting that a target event occurs on a target terminal where a first client logged in by using a first account is located;

s2, sending a first message to a second client logged in by using a second account, wherein the first message is used for indicating that a target event occurs on a target terminal, and the first account and the second account have an association relation;

s3, receiving an operation instruction sent by the second client, wherein the operation instruction is used for instructing to execute a target operation corresponding to the target event on the target terminal;

and S4, responding to the operation instruction, and executing the target operation.

s1, after receiving the operation instruction sent by the second client, analyzing the operation instruction, and acquiring indication information for indicating the target event;

s1, before detecting that a target event occurs on a target terminal where a first client logged in by using a first account is located, receiving a second message sent by a second client, wherein the second message carries a software identifier of target software, and the second message is used for indicating the first client to download an installation package of the target software according to the software identifier;

s1, uninstalling the malicious software;

s1, clearing the junk files on the target terminal;

s1, before a target event on a target terminal where a first client logged in by using a first account is located is detected, receiving a binding request sent by a second client through a third party application logged in by using a fourth account in the third party application logged in by using the third account, wherein the binding request is used for requesting to bind the first account and the second account, the first account and the third account have an incidence relation, and the second account and the fourth account have an incidence relation;

s2, associating the fourth account with the third account;

and S3, associating the third account with the first account.

s1, before the third account and the first account are associated, receiving a third message carrying a download link, which is sent by a third party application logged in by using the third account, wherein the download link points to an installation package of the first client;

s2, downloading the installation package of the first client pointed by the download link, and installing the first client;

and S3, logging in the first client by using the first account.

and S1, when the number of the second accounts is multiple, executing the target operation corresponding to the operation instruction sent by the second account with the highest priority.

s1, receiving a first message sent by a first client logged in by using a first account on a second client logged in by using a second account, wherein the first message is used for indicating that a target event occurs on a target terminal where the first client is located, and the first account and the second account have an association relationship;

and S2, sending an operation instruction to the first client, wherein the operation instruction is used for instructing the target terminal to execute the target operation corresponding to the target event.

the target operation is: under the condition that the first message indicates that the target terminal does not install the target software before the target time point, displaying first prompt information for prompting the installation of the target software; under the condition that the first message indicates that the target terminal is provided with the malicious software, the malicious software is uninstalled, and/or a second prompt message for prompting the uninstallation of the malicious software is displayed; or, in the case that the first message indicates that the storage space of the target terminal is lower than the target threshold, the junk file on the target terminal is cleared, and/or a third prompt message for prompting clearing of the junk file on the target terminal is displayed.

s1, before receiving a first message sent by a first client logged in by using a first account, pushing a second message to the first client, wherein the second message carries a software identifier of target software, and the second message is used for indicating the first client to download an installation package of the target software according to the software identifier.

and S1, before receiving a first message sent by a first client logged in by using a first account, sending a binding request to a third party application logged in by using a third account by using a third party application logged in by using a fourth account, wherein the binding request is used for requesting to bind the first account and the second account, the first account and the third account have an association relationship, and the second account and the fourth account have an association relationship.

Alternatively, in this embodiment, a person skilled in the art may understand that all or part of the steps in the methods of the foregoing embodiments may be implemented by a program instructing hardware associated with the terminal device, where the program may be stored in a computer-readable storage medium, and the storage medium may include: Read-Only Memory (ROM).

According to still another aspect of the embodiments of the present invention, there is also provided an electronic device for implementing the event processing method, as shown in fig. 14, the electronic device including: a processor 1402, a memory 1404, a transmitting device 1406, a display 1408, and a bus 1410 connecting the various components described above, among others. The memory has stored therein a computer program, and the processor is arranged to execute the steps of any of the above method embodiments by means of the computer program.

Optionally, in this embodiment, the electronic apparatus may be located in at least one network device of a plurality of network devices of a computer network.

Optionally, in this embodiment, the processor may be configured to execute the following steps by a computer program:

Alternatively, it can be understood by those skilled in the art that the structure shown in fig. 14 is merely an illustration, and the electronic device may be a smart phone (e.g., an Android phone). Fig. 14 is a diagram illustrating a structure of the electronic device. For example, the electronic device may also include more or fewer components (e.g., network interfaces, etc.) than shown in FIG. 14, or have a different configuration than shown in FIG. 14.

The memory 1404 may be used to store software programs and modules, such as program instructions/modules corresponding to the event processing method and apparatus in the embodiment of the present invention, and the processor 1402 executes various functional applications and data processing by running the software programs and modules (the detection unit 1202, the sending unit 1204, the receiving unit 1206, and the execution unit 1208) stored in the memory 1404, so as to implement the event processing method. The memory 1404 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 1404 may further include memory located remotely from the processor 1402, which may be connected to a terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmitting device 1406 is used for receiving or sending data via a network. Examples of the network may include a wired network and a wireless network. In one example, the transmission device 1406 includes a network adapter (NIC) that can be connected to a router via a network cable and other network devices to communicate with the internet or a local area network. In one example, the transmitting device 1406 is a Radio Frequency (RF) module, which is used to communicate with the internet by wireless means. The display 1408 displays the first client, display information, and the like.

According to still another aspect of the embodiments of the present invention, there is also provided an electronic device for implementing the event processing method, as shown in fig. 15, the electronic device including: a processor 1502, a memory 1504, a transmission 1506, a display 1508, and a bus 1510 connecting the various components described above, among others. The memory has stored therein a computer program, and the processor is arranged to execute the steps of any of the above method embodiments by means of the computer program.

Alternatively, it can be understood by those skilled in the art that the structure shown in fig. 15 is merely an illustration, and the electronic device may be a smart phone (e.g., an Android phone, an ios phone, etc.). Fig. 15 is a diagram illustrating a structure of the electronic device. For example, the electronic device may also include more or fewer components than shown in FIG. 15, or have a different configuration than shown in FIG. 15.

The memory 1504 may be used for storing software programs and modules, such as program instructions/modules corresponding to the event processing method and apparatus in the embodiments of the present invention, and the processor 1502 executes various functional applications and data processing by running the software programs and modules (the receiving unit 1302 and the sending unit 1304) stored in the memory 1504, that is, implementing the event processing method. The memory 1504 may include high-speed random access memory and may also include non-volatile memory. In some examples, the memory 1504 can further include memory located remotely from the processor 1502, which can be connected to the terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device 1506 is used for receiving or transmitting data via a network. Examples of the network may include a wired network and a wireless network. In one example, the transmission device 1506 includes a network adapter NIC, which can be connected to a router via a network cable and other network devices to communicate with the internet or a local area network. In one example, the transmission device 1506 is an RF module for communicating with the internet in a wireless manner. The display 1508 displays the second client, display information, and the like.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

The integrated unit in the above embodiments, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in the above computer-readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing one or more computer devices (which may be personal computers, servers, network devices, etc.) to execute all or part of the steps of the method according to the embodiments of the present invention.

In the above embodiments of the present invention, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the several embodiments provided in the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.

Claims

1. An event processing method, comprising:

detecting that a target event occurs on a target terminal where a first client logged in by using a first account is located;

sending a first message to a second client logged in by using a second account, wherein the first message is used for indicating that the target event occurs on the target terminal, and the first account and the second account have an association relationship;

receiving an operation instruction sent by the second client, wherein the operation instruction is used for instructing to execute a target operation corresponding to the target event on the target terminal;

and responding to the operation instruction, and executing the target operation.

2. The method according to claim 1, wherein after receiving the operation instruction sent by the second client, the method further comprises:

analyzing the operation instruction to acquire indication information for indicating the target event;

and acquiring the target operation corresponding to the indication information.

3. The method of claim 2, wherein performing the target operation in response to the operation instruction comprises:

and under the condition that the indication information indicates that the target terminal does not install the target software before the target time point, displaying first prompt information for prompting the installation of the target software.

4. The method according to claim 3, wherein before detecting that the target event occurs on the target terminal where the first client logged in using the first account is located, the method further comprises:

receiving a second message sent by the second client, wherein the second message carries the software identifier of the target software, and the second message is used for instructing the first client to download the installation package of the target software according to the software identifier;

and responding to the second message, and downloading the installation package of the target software corresponding to the software identification.

5. The method of claim 2, wherein performing the target operation in response to the operation instruction comprises:

in the case that the indication information indicates that malware is installed on the target terminal, performing at least one of the following operations:

uninstalling the malware;

and displaying a second prompt message for prompting the uninstallation of the malicious software.

6. The method of claim 2, wherein performing the target operation in response to the operation instruction comprises:

in the case that the indication information indicates that the storage space of the target terminal is lower than a target threshold, performing at least one of the following operations:

clearing junk files on the target terminal;

and displaying a third prompt message for prompting to clear the junk files on the target terminal.

7. The method according to claim 1, wherein before detecting that the target event occurs on the target terminal where the first client logged in using the first account is located, the method further comprises:

receiving a binding request sent by a third party application logged in by a second client through a fourth account in a third party application logged in by the third account, wherein the binding request is used for requesting to bind the first account and the second account, the first account and the third account have an association relationship, and the second account and the fourth account have an association relationship;

associating the fourth account with the third account;

and associating the third account with the first account.

8. The method of claim 7, wherein prior to associating the third account number with the first account number, the method further comprises:

receiving a third message which is sent by a third party application logged in by using the third account and carries a download link, wherein the download link points to the installation package of the first client;

and logging in the first client by using the first account.

9. The method of any of claims 1-8, wherein performing the target operation in response to the operation instruction comprises:

and under the condition that the number of the second accounts is multiple, executing target operation corresponding to the operation instruction sent by the second account with the highest priority.

10. An event processing method, comprising:

receiving a first message sent by a first client logged in by using a first account on a second client logged in by using a second account, wherein the first message is used for indicating that a target event occurs on a target terminal where the first client is located, and the first account and the second account have an association relationship;

and sending an operation instruction to the first client, wherein the operation instruction is used for instructing to execute a target operation corresponding to the target event on the target terminal.

11. The method of claim 10, wherein the target operation is:

under the condition that the first message indicates that the target terminal does not install the target software before the target time point, displaying first prompt information for prompting the installation of the target software;

under the condition that the first message indicates that the target terminal is provided with the malicious software, the malicious software is uninstalled, and/or a second prompt message used for prompting the uninstallation of the malicious software is displayed; alternatively, the first and second electrodes may be,

and when the first message indicates that the storage space of the target terminal is lower than a target threshold value, clearing the junk files on the target terminal, and/or displaying a third prompt message for prompting clearing of the junk files on the target terminal.

12. The method of claim 11, wherein prior to receiving the first message sent by the first client logged in using the first account, the method further comprises:

and pushing a second message to the first client, wherein the second message carries the software identifier of the target software, and the second message is used for indicating the first client to download the installation package of the target software according to the software identifier.

13. The method according to any one of claims 10 to 12, wherein before receiving the first message sent by the first client logged in using the first account, the method further comprises:

sending a binding request to a third party application logged in by using a third account by using a third party application logged in by using a fourth account, wherein the binding request is used for requesting to bind the first account and the second account, the first account and the third account have an association relationship, and the second account and the fourth account have an association relationship.

14. An event processing apparatus, comprising:

the system comprises a detection unit, a processing unit and a processing unit, wherein the detection unit is used for detecting that a target event occurs on a target terminal where a first client logged in by using a first account is located;

a sending unit, configured to send a first message to a second client that logs in using a second account, where the first message is used to indicate that the target event occurs on the target terminal, and the first account and the second account have an association relationship;

a receiving unit, configured to receive an operation instruction sent by the second client, where the operation instruction is used to instruct a target terminal to execute a target operation corresponding to the target event;

and the execution unit is used for responding to the operation instruction and executing the target operation.

15. An event processing apparatus, comprising:

the system comprises a receiving unit, a sending unit and a processing unit, wherein the receiving unit is used for receiving a first message sent by a first client logged in by using a first account on a second client logged in by using a second account, the first message is used for indicating that a target event occurs on a target terminal where the first client is located, and the first account and the second account have an incidence relation;

a sending unit, configured to send an operation instruction to the first client, where the operation instruction is used to instruct to execute a target operation corresponding to the target event on the target terminal.

16. A storage medium, in which a computer program is stored, wherein the computer program is arranged to perform the method of any of claims 1 to 13 when executed.

17. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method of any of claims 1 to 13 by means of the computer program.