CN108023806B - Method and device for marking event invalidation - Google Patents
Method and device for marking event invalidation Download PDFInfo
- Publication number
- CN108023806B CN108023806B CN201610943195.2A CN201610943195A CN108023806B CN 108023806 B CN108023806 B CN 108023806B CN 201610943195 A CN201610943195 A CN 201610943195A CN 108023806 B CN108023806 B CN 108023806B
- Authority
- CN
- China
- Prior art keywords
- marking
- target
- client
- invalid
- invalidation
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
- H04L51/18—Commands or executable codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/42—Mailbox-related aspects, e.g. synchronisation of mailboxes
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The present disclosure relates to a method and apparatus for marking event invalidity. The method for marking the event invalidity comprises the following steps: receiving an invalid marker request for a target event from an initiating client; generating an invalid marking command according to the invalid marking request; sending the invalidation marking command to a responding client of the target event, wherein the invalidation marking command is used for marking the target event as an invalid state on the responding client. In the embodiment of the present disclosure, after receiving an invalid marker request for a target event from an initiating client, an invalid marker command generated according to the invalid marker request may be sent to a responding client of the target event, so that the target event is marked as an invalid state on the responding client of the target event, interference to the responding client of the target event is reduced, unnecessary responses of the responding client are reduced, and time of both the transmitting and receiving parties is saved.
Description
Technical Field
The present disclosure relates to the field of internet technologies, and in particular, to a method and an apparatus for marking an event invalid.
Background
In the related art, some applications provide revocation functionality. For example, Outlook provides the function of revoking mail. The WeChat provides the function of withdrawing information.
Wherein the message withdrawal in the WeChat must be within 2 minutes. Even if the mail or message can be withdrawn in Outlook and WeChat, the mail or message content may be visible to the recipient and cause confusion.
Disclosure of Invention
To overcome the problems in the related art, the present disclosure provides a method and apparatus for invalidating a marker event.
According to a first aspect of embodiments of the present disclosure, there is provided a method for marking event invalidity, including:
receiving an invalid marker request for a target event from an initiating client;
generating an invalid marking command according to the invalid marking request;
sending the invalidation marking command to a responding client of the target event, wherein the invalidation marking command is used for marking the target event as an invalid state on the responding client.
For the above method, in one possible implementation, the target event is a mail,
receiving an invalidation marking request for a target event from an initiating client, comprising: receiving a mail invalidation marking request aiming at a target mail from an initiating client of a mail application;
sending the invalidation marking command to a responding client of the target event, the invalidation marking command being used to mark the target event as invalid on the responding client, comprising: and sending the mail invalidation marking command to the response client of each receiver of the target mail, wherein the mail invalidation marking command is used for marking the target mail in an invalid state on the response client of each receiver of the target mail.
For the above method, in one possible implementation, the target event is a message,
receiving an invalidation marking request for a target event from an initiating client, comprising: receiving a message invalidation marking request aiming at a target message from an initiating client of a chat tool;
sending the invalidation marking command to a responding client of the target event, the invalidation marking command being used to mark the target event as invalid on the responding client, comprising: and sending the message invalidation marking command to the response client of each receiver of the target message, wherein the message invalidation marking command is used for marking the target message as an invalid state on the client of each receiver of the target message.
With respect to the above method, in one possible implementation, the target event is a call,
receiving an invalidation marking request for a target event from an initiating client, comprising: receiving a call invalid marking request aiming at a target call from an initiating client of a call application;
sending the invalidation marking command to a responding client of the target event, the invalidation marking command being used to mark the target event as invalid on the responding client, comprising: and sending the call invalidation marking command to a response client of the contact person of the target call, wherein the call invalidation marking command is used for marking the target call in an invalid state on the client of the contact person of the target call.
According to a second aspect of the embodiments of the present disclosure, there is provided a method for marking event invalidity, including:
receiving an invalid marking command aiming at a target event sent by a server, wherein the invalid marking command is generated according to an invalid marking request aiming at the target event of an initiating client;
the target event is marked as invalid on the responding client.
For the above method, in one possible implementation, the target event is a mail,
receiving an invalidation marking command for a target event sent by a server, wherein the invalidation marking command is generated according to an invalidation marking request for the target event of an initiating client, and the invalidation marking command comprises the following steps: receiving a mail invalidation marking command aiming at a target mail sent by a server of a mail application, wherein the mail invalidation marking command is generated according to a mail invalidation marking request aiming at the target mail of an initiating client;
marking the target event as invalid on a responding client, comprising: and marking the target mail as an invalid state on a response client of each receiver of the target mail.
For the above method, in one possible implementation, the target event is a message,
receiving an invalidation marking command for a target event sent by a server, wherein the invalidation marking command is generated according to an invalidation marking request for the target event of an initiating client, and the invalidation marking command comprises the following steps: receiving a message invalidation marking command aiming at a target message and sent by a server of a chat tool, wherein the message invalidation marking command is generated according to a message invalidation marking request aiming at the target message of an initiating client;
marking the target event as invalid on a responding client, comprising: the targeted message is marked as invalid on the respective recipient's response client for the targeted message.
With respect to the above method, in one possible implementation, the target event is a call,
receiving an invalidation marking command for a target event sent by a server, wherein the invalidation marking command is generated according to an invalidation marking request for the target event of an initiating client, and the invalidation marking command comprises the following steps: a server receiving call application sends a call invalid marking command aiming at a target call, wherein the call invalid marking command is generated according to a call invalid marking request aiming at the target call of an initiating client;
marking the target event as invalid on a responding client, comprising: and marking the target call as an invalid state on a response client of the contact of the target call.
For the above method, in a possible implementation manner, marking the target event as an invalid state includes at least one of the following manners:
marking the target event as belonging to an invalid state on an interactive interface corresponding to the target event;
sending out an invalid prompt under the condition that a response operation to the target event is detected;
setting the target event as a disable response.
According to a third aspect of the embodiments of the present disclosure, there is provided an apparatus for marking event invalidation, including:
a first receiving module, configured to receive an invalid flag request for a target event from an initiating client;
the first generation module is used for generating an invalid mark command according to the invalid mark request;
a first sending module, configured to send the invalidation marking command to a response client of the target event, where the invalidation marking command is used to mark the target event as an invalid state on the response client.
For the above apparatus, in one possible implementation, the target event is a mail,
the first receiving module includes: the first receiving submodule is used for receiving a mail invalidation marking request aiming at a target mail from an initiating client of a mail application;
the first transmitting module includes: and the first sending submodule is used for sending the mail invalidation marking command to the response client of each receiver of the target mail, and the mail invalidation marking command is used for marking the target mail in an invalid state on the response client of each receiver of the target mail.
For the above apparatus, in one possible implementation, the target event is a message,
the first receiving module includes: a second receiving submodule, configured to receive a message invalidation marking request for the target message from an originating client of the chat tool;
the first transmitting module includes: and the second sending submodule is used for sending the message invalidation marking command to the response client of each receiver of the target message, and the message invalidation marking command is used for marking the target message in an invalid state on the client of each receiver of the target message.
For the above apparatus, in one possible implementation, the target event is a call,
the first receiving module includes: the third receiving submodule is used for receiving a call invalid marking request aiming at the target call from an initiating client of the call application;
the first transmitting module includes: and the third sending submodule is used for sending the call invalidation marking command to a response client of the contact person of the target call, and the call invalidation marking command is used for marking the target call in an invalid state on the client of the contact person of the target call.
According to a fourth aspect of the embodiments of the present disclosure, there is provided an apparatus for marking event invalidity, including:
a second receiving module, configured to receive an invalidation marking command for a target event sent by a server, where the invalidation marking command is generated according to an invalidation marking request for the target event of an initiating client;
a marking module for marking the target event as invalid state on the response client.
For the above apparatus, in one possible implementation, the target event is a mail,
the second receiving module includes: a fourth receiving submodule, configured to receive a mail invalidation marking command for a target mail, sent by a server of a mail application, where the mail invalidation marking command is generated according to a mail invalidation marking request for the target mail of an originating client;
the marking module includes: and the first marking submodule is used for marking the target mail as an invalid state on a response client of each receiver of the target mail.
For the above apparatus, in one possible implementation, the target event is a message,
the second receiving module includes: a fifth receiving submodule, configured to receive a message invalidation marking command for a target message sent by a server of a chat tool, where the message invalidation marking command is generated according to a message invalidation marking request for the target message of an originating client;
the marking module includes: a second tagging submodule for tagging said targeted message as invalid on a response client of each recipient of said targeted message.
For the above apparatus, in one possible implementation, the target event is a call,
the second receiving module includes: a sixth receiving submodule, configured to receive a call invalidation marking command sent by a server of a call application for a target call, where the call invalidation marking command is generated according to a call invalidation marking request of an originating client for the target call;
the marking module includes: and the third marking submodule is used for marking the target call as an invalid state on a response client of the contact of the target call.
For the above apparatus, in one possible implementation, the marking module further includes at least one of the following sub-modules:
the fourth marking submodule is used for marking that the target event belongs to an invalid state on the interactive interface corresponding to the target event;
the reminding submodule is used for sending out invalid reminding under the condition that response operation to the target event is detected;
and the response inhibition submodule is used for setting the target event as an inhibition response.
According to a fifth aspect of the embodiments of the present disclosure, there is provided an apparatus for marking event invalidity, including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
receiving an invalid marker request for a target event from an initiating client;
generating an invalid marking command according to the invalid marking request;
sending the invalidation marking command to a responding client of the target event, wherein the invalidation marking command is used for marking the target event as an invalid state on the responding client.
According to a sixth aspect of the embodiments of the present disclosure, there is provided an apparatus for marking event invalidity, including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
receiving an invalid marking command aiming at a target event sent by a server, wherein the invalid marking command is generated according to an invalid marking request aiming at the target event of an initiating client;
the target event is marked as invalid on the responding client.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: after receiving the invalid mark of the client aiming at the target event, the invalid mark can be sent to the client of the related contact person of the target event, so that the target event is marked to be in an invalid state on the client of the related contact person of the target event, the interference on the related contact person of the target event is reduced, the unnecessary response of the related contact person is reduced, and the time of the receiving side and the sending side is saved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a flow diagram illustrating a method of flagging event invalidations in accordance with an exemplary embodiment.
FIG. 2 is a flow diagram illustrating a method of flagging event invalidation according to another example embodiment.
FIG. 3 is a flow diagram illustrating a method of flagging event invalidation according to another example embodiment.
FIG. 4 is a block diagram illustrating an apparatus for flagging event invalidations in accordance with an exemplary embodiment.
FIG. 5 is a block diagram illustrating an apparatus for flagging event invalidation according to another example embodiment.
FIG. 6 is a block diagram illustrating an apparatus for flagging event invalidation according to another example embodiment.
FIG. 7 is a block diagram illustrating an apparatus for flagging event invalidation according to another example embodiment.
FIG. 8 is a block diagram illustrating an apparatus for flagging event invalidation according to another example embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Fig. 1 is a flowchart illustrating a method of flagging event invalidation, which may be used in a server as shown in fig. 1, and may include the following steps, according to an example embodiment.
In step 101, an invalidation flag request for a target event is received from an initiating client.
In step 102, an invalidation marking command is generated according to the invalidation marking request.
In step 103, the invalidation marking command is sent to the responding client of the target event, and the invalidation marking command is used for marking the target event as an invalid state on the responding client.
In the disclosed embodiment, the target event may include various types, for example: mail, message, conversation, etc. The mail can be transmitted and received by a client of the mail application installed on the terminal device of the user and a server of the mail application. The client of the chat tool installed on the terminal equipment of the user and the server of the chat tool can realize the receiving and sending of the messages. The call connection can be realized through a client of the call application installed on the terminal device of the user and a server of the call application. Among other things, chat tools may include, but are not limited to, short messages, rice chat, QQ, WeChat, Federation, and the like. Telephony applications include, but are not limited to, cell phone calls, network calls, and the like.
Wherein, if the user wants to mark the target event which is already sent out as an invalid state, an invalid mark request for the target event can be sent to the server through the client (initiating client) of the user. And generating an invalid marking command by the server according to the invalid marking request, and sending the invalid marking command to the client (response client) of the related contact related to the target event. The server may employ different processing for different target events, see the example below.
Example one, the target event is a mail.
Receiving an invalidation marking request for a target event from an initiating client (step 101), which may include: receiving a mail invalidation marking request aiming at a target mail from an initiating client of a mail application;
sending the invalidation marking command to the responding client of the target event, the invalidation marking command being used for marking the target event as invalid state on the responding client (step 103), which may include: and sending the mail invalidation marking command to the response client of each receiver of the target mail, wherein the mail invalidation marking command is used for marking the target mail in an invalid state on the response client of each receiver of the target mail.
Example two, the target event is a message.
Receiving an invalidation marking request for a target event from an initiating client (step 101), which may include: receiving a message invalidation marking request aiming at a target message from an initiating client of a chat tool;
sending the invalidation marking command to the responding client of the target event, the invalidation marking command being used for marking the target event as invalid state on the responding client (step 103), which may include: and sending the message invalidation marking command to the response client of each receiver of the target message, wherein the message invalidation marking command is used for marking the target message as an invalid state on the client of each receiver of the target message.
Example three, the target event is a call.
Receiving an invalidation marking request for a target event from an initiating client (step 101), which may include: receiving a call invalid marking request aiming at a target call from an initiating client of a call application;
sending the invalidation marking command to the responding client of the target event, the invalidation marking command being used for marking the target event as invalid state on the responding client (step 103), which may include: and sending the call invalidation marking command to a response client of the contact person of the target call, wherein the call invalidation marking command is used for marking the target call in an invalid state on the client of the contact person of the target call.
In one possible implementation, marking the target event as invalid on the clients of the related contacts of the target event may include at least one of the following:
in a first mode, the target event is marked to belong to an invalid state on an interactive interface corresponding to the target event.
For example, on the client of each recipient of the target email, the target email is marked as invalid.
As another example, the targeted message is marked as invalid on each recipient's client of the targeted message.
As another example, the target call is marked as invalid on the client of the contact of the target call.
Wherein, on the interactive interface, the invalid state can be marked by adopting the characters such as 'no reply is needed', 'invalid' and the like; the invalid state may also be marked by color, symbols, voice, etc. The marking means may include various kinds, not limited to the above examples.
And secondly, sending out an invalid prompt under the condition that the response operation to the target event is detected.
For example, a detection instruction may be set in advance on the response client of each recipient of the target email, and when it is detected that the user performs response operations such as "reply," "all reply," and the like on the target email, the response client of each recipient may issue an email invalidity reminder to the recipient.
For another example, a detection instruction may be set in advance on the response client of each recipient of the target message, and when it is detected that the user performs a response operation such as "reply" to the target message, the response client of each recipient may issue a message invalidity reminder to the recipient.
For another example, a detection instruction may be set in advance on a response client of a contact of the target call, and when it is detected that the user performs a response operation such as "call back" on the target call, the response client of the contact may send a call invalidation prompt to the contact.
Wherein, on the interactive interface, the words such as "marked no longer needs to reply, whether to continue replying? "issue invalid reminder; and the invalid reminding can be sent out by adopting a color, a symbol, a voice and the like. The reminding manner may be various and is not limited to the above examples.
And thirdly, setting the target event as a forbidden response.
For example, the target mail may be set to "prohibit reply" or other prohibited response on the response client of each recipient of the target mail in advance. When detecting that the user performs response operations such as 'reply', 'all reply' and the like, the response client of each receiver can send a reminder for prohibiting the response of the mail to the receiver.
For another example, the target message may be set to "prohibit reply" or other prohibited response on the response client of each recipient of the target message in advance. When detecting that the user performs response operation such as 'reply' to the target message, the response client of each receiver can send a reminder for prohibiting responding to the message to the receiver.
For another example, the target call may be set to "call back prohibition" or other prohibition responses on the response client of the contact of the target call in advance. When detecting that the user performs response operations such as call back on the target call, the response client of the contact person may send a prompt to the contact person to prohibit the response to the call.
Wherein, on the interactive interface, the response prohibition prompt can be sent out by adopting a text mode such as 'reply prohibition' and the like; the response prohibition prompt can also be sent out by adopting a color, a symbol, a voice and the like. The reminding manner may be various and is not limited to the above examples.
In this embodiment, after receiving an invalid marker request for a target event from an initiating client, an invalid marker command generated according to the invalid marker request may be sent to a responding client of the target event, so that the target event is marked as an invalid state on the responding client of the target event, interference to the responding client of the target event is reduced, unnecessary responses of the responding client are reduced, and time of both the transmitting and receiving parties is saved.
Fig. 2 is a flowchart illustrating a method of flagging event invalidation, which may be used in a terminal as illustrated in fig. 2, according to another exemplary embodiment, and may include the following steps.
In step 201, an invalidation marking command for a target event sent by a server is received, and the invalidation marking command is generated according to an invalidation marking request for the target event of an initiating client.
In step 202, the target event is marked as invalid on the responding client.
Wherein, if the user wants to mark the target event which is already sent out as an invalid state, an invalid mark request for the target event can be sent to the server through the client (initiating client) of the user. After the server generates an invalidation marking command according to the invalidation marking request, the invalidation marking command can be sent to the client (response client) of the relevant contact related to the target event. The responding client may employ different processing for different target events, see the example below.
Example one, the target event is a mail.
Receiving an invalidation marking command for a target event sent by a server, the invalidation marking command being generated according to an invalidation marking request for the target event of an initiating client (step 201), which may include: receiving a mail invalidation marking command aiming at a target mail sent by a server of a mail application, wherein the mail invalidation marking command is generated according to a mail invalidation marking request aiming at the target mail of an initiating client;
marking the target event as invalid on the responding client (step 202), which may include: and marking the target mail as an invalid state on a response client of each receiver of the target mail.
Example two, the target event is a message.
Receiving an invalidation marking command for a target event sent by a server, the invalidation marking command being generated according to an invalidation marking request for the target event of an initiating client (step 201), which may include: receiving a message invalidation marking command aiming at a target message and sent by a server of a chat tool, wherein the message invalidation marking command is generated according to a message invalidation marking request aiming at the target message of an initiating client;
marking the target event as invalid on the responding client (step 202), which may include: the targeted message is marked as invalid on the respective recipient's response client for the targeted message.
Example three, the target event is a call.
Receiving an invalidation marking command for a target event sent by a server, the invalidation marking command being generated according to an invalidation marking request for the target event of an initiating client (step 201), which may include: a server receiving call application sends a call invalid marking command aiming at a target call, wherein the call invalid marking command is generated according to a call invalid marking request aiming at the target call of an initiating client;
marking the target event as invalid on the responding client (step 202), which may include: and marking the target call as an invalid state on a response client of the contact of the target call.
In one possible implementation, marking the target event as invalid on the clients of the related contacts of the target event may include a variety of ways. For example, refer to the description of the first to third modes in the above embodiments, which are not repeated herein.
In this embodiment, if the target event needs to be marked as the invalid state, an invalid marking request for the target event may be sent to the server, so that the server sends an invalid marking command generated according to the invalid marking request to the response client of the target event, so that the target event is marked as the invalid state on the response client of the target event, interference to the response client of the target event is reduced, unnecessary responses of the response client are reduced, and time of both the transmitter and the receiver is saved.
Fig. 3 is a flowchart illustrating a method of flagging event invalidation according to another exemplary embodiment, which may include the following steps, as shown in fig. 3.
In step 301, a user issues various events to a server through an initiating client. Such as mail, messages, conversations, and the like.
In step 302, the server sends these events to the responding clients of the relevant contacts.
In step 303, the user may have received a reply to some event or the user no longer wishes to receive a reply to some event. At this time, the User may regard these events as target events and mark these target events as invalid on their own initiating client by some UI (User Interface) manner. For example, clicking the "invalid button" of the target event on the display interface of the client computer, right-clicking the invalid option, and the like. For another example, a corresponding gesture is performed on the target event on the display interface of the client touch screen. As another example, the target event is marked as invalid using speech.
In step 304, the user sends an invalidation flag request for the target event to the server through its own initiating client.
In step 305, after receiving the invalidation marking request for the target event, the server may generate an invalidation marking command according to the invalidation marking request.
In step 306, the server may send the invalidate mark command to the responding client for the relevant contact of the target event.
In step 307, the response client of the relevant contact of the target event may mark the target event as invalid when receiving an invalid mark command for the target event. Wherein different types of responding clients mark events as invalid states in different forms.
With the present disclosure, events in the following examples can be marked as invalid to reduce duplicate replies.
Example one, a user U made several calls to a colleague a in the morning to solve a problem, but for some reason a did not answer the user U's phone. U calls another colleague B and gets the help of B to solve the problem. After a few hours, a finds an unanswered call made by U, and asks U what happened by dialing back the call? U has to spend time explaining to a why the call is made, which is a waste of time for both U and a.
Example two, user U urgently needs an electronic file or some information, but U is less aware of which people can help him. So U sends information to many people in the chat tool or sends mail in a group in the mailbox. When the U receives the needed information or the file, the U does not want to receive the repeated file or the information, and does not want to waste time of other people to help the U to solve the solved problem.
The following application scenarios are distinguished for the above example, and the method for invalidating the tagged event of the present disclosure is exemplarily described below.
The application scene one: and E-mail.
A user has sent a mass mail through a mail application (originating client) that wishes to obtain a file. When the user receives at least one mail reply and obtains the expected file, if the user does not want to occupy the time of other recipients to search for the file and reply the user, the user does not want to be occupied by the reply of other recipients.
The mail application (originating client) may provide the user with an option to mark whether the sent mail is "no longer in need of reply" or "still in need of reply". The user may tag the sent mail by some UI means of the originating client and pass the tag to the mail server (e.g., by an invalid tag request). When the server receives the user's token, the token may be distributed (e.g., by an invalidate token command) to all recipients in the sent mail (responding clients). And displays the indicia in the mail application using some UI means at the responding client of each recipient to notify all recipients. If the user's flag is "no more reply needed", then if a certain recipient selects "reply" or "reply all", the mail application (response client) of each recipient may prompt "is the sender marked that the mail no longer needs to reply, continue to reply? ". The mail application (responding client) may then enter the mail editing interface or return to the previous interface, depending on the user's selection.
Application scenario two: a chat tool.
A user has sent a message to a group of people via a chat facility (originating client) that he wishes to get an answer to a question. When the user receives a valid reply, the user does not want to occupy the time of other contacts to search for the answer and reply to the user, and does not want to be occupied by the replies of other contacts to occupy the screen.
The chat facility (originating client) may provide the user with an option to flag whether the sent message "no longer needs to reply" or "still needs to reply". The user may tag the sent message by some UI means of the originating client and pass the tag to the chat facility server (e.g., by an invalid tag request). When the server receives the user's token, it can distribute the token (e.g., via an invalidate token command) to the group (the responding clients of each recipient) where the sent message exists. And displays the tag in the chat tool to notify all contacts in the group (the recipient's responding clients) using some UI means. If the user's flag is "no more reply needed", then if a contact attempts to reply to the message, the chat facility (responding client) of each recipient may prompt "does the messenger flag that the message no more replies to, continue replying? ". The chat tool (responding client) can then enter the text editing interface or return to the previous interface, depending on the user's selection.
Application scenario three: a telephone.
The user places a number of calls to contact a for assistance. The phone is not answered by the A, such as the ring tone of the mobile phone is set to be silent, the A keeps the mobile phone at home, and the like. The user gets a valid answer through other contacts such as B. The user does not want to take the time of contact a to reply to the user.
The conversation application (originating client) may provide the user with an option to mark whether the sent message "no longer needs to reply" or "still needs to reply". The user may tag the sent message by some UI means of the originating client and pass the tag and the corresponding phone number of contact a to the server (e.g., by an invalid tag request). When the server receives the user's token, it may distribute the token to the contact a's handset (responding client), e.g., via an invalidate token command, and display the token in a call-related application, such as a call log, missed call prompt, etc., using some UI means to notify the contact a. If the user's flag is "no more needed to reply," then if contact a attempts to dial back the user's phone, contact a's call application (response client) may prompt "does the phone originator flag that the call no more needs to reply, continue to dial the call? ". The telephony application (responding client) can then enter the dialing interface or return to the previous interface, depending on the user's selection.
In this embodiment, after the e-mail, the social message, or the phone of the user is no longer valid, the user may mark the e-mail, the social message, or the phone as "no reply needed", and distribute the e-mail, the social message, or the phone to the response clients of all the related recipients or contacts through the server, thereby eliminating the trouble of the related recipients or contacts, avoiding the related recipients from continuing to reply, and saving time of both parties.
In this embodiment, if the user needs to mark the target event in the invalid state, the user may send an invalid marking request for the target event to the server through the originating client of the user, and the server sends an invalid marking command generated according to the invalid marking request to the responding client of the target event, so that the target event is marked in the invalid state on the responding client of the target event, interference to the responding client of the target event is reduced, unnecessary responses of the responding client are reduced, and time of both the transmitting and receiving parties is saved.
FIG. 4 is a block diagram illustrating an apparatus for flagging event invalidations in accordance with an exemplary embodiment. Referring to fig. 4, the apparatus may include a first receiving module 41, a first generating module 42, and a first transmitting module 43.
Wherein, the first receiving module 41 is configured to receive an invalidation marking request for the target event from the initiating client. And the first generation module is used for generating an invalid marking command according to the invalid marking request. A first sending module 43, configured to send the invalidation marking command to the responding client of the target event, where the invalidation marking command is used to mark the target event as invalid state on the responding client.
In this embodiment, after receiving an invalid marker request for a target event from an initiating client, an invalid marker command generated according to the invalid marker request may be sent to a responding client of the target event, so that the target event is marked as an invalid state on the responding client of the target event, interference to the responding client of the target event is reduced, unnecessary responses of the responding client are reduced, and time of both the transmitting and receiving parties is saved.
FIG. 5 is a block diagram illustrating an apparatus for flagging event invalidation according to another example embodiment. The components in fig. 5 having the same reference numerals as those in fig. 4 have the same meanings, and are not described herein again.
Referring to fig. 5, the difference from the previous embodiment is that the target event referring to the above-described method embodiment is an example of a mail.
The first receiving module 41 may include: a first receiving submodule 411, configured to receive a mail invalidation marking request for a target mail from an initiating client of a mail application;
the first sending module 43 may include: the first sending submodule 431 is configured to send the mail invalidation marking command to the response client of each recipient of the target mail, where the mail invalidation marking command is used to mark the target mail as an invalid state on the response client of each recipient of the target mail.
In one possible implementation, the target event referred to above in the method embodiments is an example of a message.
The first receiving module 41 may include: a second receiving submodule 412, configured to receive a message invalidation marking request for the target message from the originating client of the chat tool;
the first sending module 43 may include: a second sending submodule 432, configured to send the message invalidation marking command to the responding client of each recipient of the target message, where the message invalidation marking command is used to mark the target message as invalid state on the client of each recipient of the target message.
In one possible implementation, the target event in the above method embodiment is an example of a call.
The first receiving module 41 may include: a third receiving submodule 413, configured to receive a call invalidation marking request for the target call from the originating client of the call application;
the first sending module 43 may include: a third sending submodule 433, configured to send the call invalidation marking command to a response client of the contact of the target call, where the call invalidation marking command is used to mark the target call as an invalid state on the client of the contact of the target call.
In this embodiment, after receiving an invalid marker request for a target event, such as a mail, a message, a call, etc., from an initiating client, an invalid marker command generated according to the invalid marker request may be sent to a responding client of the target event, so that the target event is marked as an invalid state on the responding client of the target event, interference to the responding client of the target event is reduced, unnecessary responses of the responding client are reduced, and time of both the transmitting and receiving parties is saved.
FIG. 6 is a block diagram illustrating an apparatus for flagging event invalidation according to another example embodiment. Referring to fig. 6, the apparatus may include a second receiving module 61 and a marking module 63.
The second receiving module 61 is configured to receive an invalidation marking command for the target event sent by the server, where the invalidation marking command is generated according to an invalidation marking request for the target event of the initiating client. A marking module 63 for marking the target event as invalid on the responding client.
In this embodiment, if the target event needs to be marked as the invalid state, an invalid marking request for the target event may be sent to the server, so that the server sends an invalid marking command generated according to the invalid marking request to the response client of the target event, so that the target event is marked as the invalid state on the response client of the target event, interference to the response client of the target event is reduced, unnecessary responses of the response client are reduced, and time of both the transmitter and the receiver is saved.
FIG. 7 is a block diagram illustrating an apparatus for flagging event invalidation according to another example embodiment. The components in fig. 7 having the same reference numerals as those in fig. 6 have the same meanings, and are not described again here.
Referring to fig. 7, the difference from the previous embodiment is that the target event referring to the above-described method embodiment is an example of a mail.
The second receiving module 61 may include: a fourth receiving submodule 611, configured to receive a mail invalidation marking command for a target mail sent by a server of a mail application, where the mail invalidation marking command is generated according to a mail invalidation marking request for the target mail of an originating client;
the marking module 63 may include: a first marking sub-module 631, configured to mark the target email as invalid on the response client of each recipient of the target email.
In one possible implementation, the target event referred to above in the method embodiments is an example of a message.
The second receiving module 61 may include: a fifth receiving submodule 612, configured to receive a message invalidation marking command for a target message sent by a server of the chat tool, where the message invalidation marking command is generated according to a message invalidation marking request for the target message of an originating client;
the marking module 63 may include: a second tagging submodule 632 is configured to tag the targeted message as invalid on the respective recipient's response client for the targeted message.
In one possible implementation, the target event in the above method embodiment is an example of a call.
The second receiving module 61 may include: a sixth receiving submodule 613, configured to receive a call invalidation marking command for a target call sent by a server of a call application, where the call invalidation marking command is generated according to a call invalidation marking request for the target call of an originating client;
the marking module 63 may include: a third tagging submodule 633 for tagging the target call as an invalid state on a responding client of a contact of the target call.
In one possible implementation, the marking module 63 further includes at least one of the following sub-modules:
the fourth marking sub-module 634, configured to mark that the target event belongs to an invalid state on the interactive interface corresponding to the target event;
the reminding submodule 635 is configured to send an invalid reminder when a response operation to the target event is detected;
and a disable response submodule 636, configured to set the target event as a disable response.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
In this embodiment, if a target event, such as a mail, a message, a call, etc., needs to be marked as an invalid state, an invalid marking request for the target event may be sent to the server, so that an invalid marking command generated according to the invalid marking request is sent to a responding client of the target event through the server, thereby marking the target event as an invalid state on the responding client of the target event, reducing interference to the responding client of the target event, reducing unnecessary responses of the responding client, and saving time of both the transmitting and receiving parties.
Fig. 8 is a block diagram illustrating an apparatus 800 for flagging event invalidation according to another example embodiment. For example, the apparatus 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.
Referring to fig. 8, the apparatus 800 may include one or more of the following components: processing component 802, memory 804, power component 806, multimedia component 808, audio component 810, input/output (I/O) interface 812, sensor component 814, and communication component 816.
The processing component 802 generally controls overall operation of the device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing components 802 may include one or more processors 820 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interaction between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.
The memory 804 is configured to store various types of data to support operations at the apparatus 800. Examples of such data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 804 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
The multimedia component 808 includes a screen that provides an output interface between the device 800 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the device 800 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the apparatus 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.
The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
The sensor assembly 814 includes one or more sensors for providing various aspects of state assessment for the device 800. For example, the sensor assembly 814 may detect the open/closed status of the device 800, the relative positioning of components, such as a display and keypad of the device 800, the sensor assembly 814 may also detect a change in the position of the device 800 or a component of the device 800, the presence or absence of user contact with the device 800, the orientation or acceleration/deceleration of the device 800, and a change in the temperature of the device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 816 is configured to facilitate communications between the apparatus 800 and other devices in a wired or wireless manner. The device 800 may access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the apparatus 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described methods.
In an exemplary embodiment, a non-transitory computer-readable storage medium comprising instructions, such as the memory 804 comprising instructions, executable by the processor 820 of the device 800 to perform the above-described method is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
Claims (20)
1. A method of flagging event invalidity, comprising:
receiving an invalid marker request for a target event from an initiating client;
generating an invalid marking command according to the invalid marking request;
sending the invalidation marking command to a responding client of the target event, wherein the invalidation marking command is used for marking the target event as an invalid state on the responding client;
the marking the target event as an invalid state comprises: and sending out an invalid prompt when the response operation to the target event is detected.
2. The method of claim 1, wherein the target event is a mail,
receiving an invalidation marking request for a target event from an initiating client, comprising: receiving a mail invalidation marking request aiming at a target mail from an initiating client of a mail application;
sending the invalidation marking command to a responding client of the target event, the invalidation marking command being used to mark the target event as invalid on the responding client, comprising: and sending the mail invalidation marking command to the response client of each receiver of the target mail, wherein the mail invalidation marking command is used for marking the target mail in an invalid state on the response client of each receiver of the target mail.
3. The method of claim 1, wherein the target event is a message,
receiving an invalidation marking request for a target event from an initiating client, comprising: receiving a message invalidation marking request aiming at a target message from an initiating client of a chat tool;
sending the invalidation marking command to a responding client of the target event, the invalidation marking command being used to mark the target event as invalid on the responding client, comprising: and sending the message invalidation marking command to the response client of each receiver of the target message, wherein the message invalidation marking command is used for marking the target message as an invalid state on the client of each receiver of the target message.
4. The method of claim 1, wherein the target event is a call,
receiving an invalidation marking request for a target event from an initiating client, comprising: receiving a call invalid marking request aiming at a target call from an initiating client of a call application;
sending the invalidation marking command to a responding client of the target event, the invalidation marking command being used to mark the target event as invalid on the responding client, comprising: and sending the call invalidation marking command to a response client of the contact person of the target call, wherein the call invalidation marking command is used for marking the target call in an invalid state on the client of the contact person of the target call.
5. A method of flagging event invalidity, comprising:
receiving an invalid marking command aiming at a target event sent by a server, wherein the invalid marking command is generated according to an invalid marking request aiming at the target event of an initiating client;
marking the target event as invalid on a responding client;
the marking the target event as an invalid state comprises: and sending out an invalid prompt when the response operation to the target event is detected.
6. The method of claim 5, wherein the target event is a mail,
receiving an invalidation marking command for a target event sent by a server, wherein the invalidation marking command is generated according to an invalidation marking request for the target event of an initiating client, and the invalidation marking command comprises the following steps: receiving a mail invalidation marking command aiming at a target mail sent by a server of a mail application, wherein the mail invalidation marking command is generated according to a mail invalidation marking request aiming at the target mail of an initiating client;
marking the target event as invalid on a responding client, comprising: and marking the target mail as an invalid state on a response client of each receiver of the target mail.
7. The method of claim 5, wherein the target event is a message,
receiving an invalidation marking command for a target event sent by a server, wherein the invalidation marking command is generated according to an invalidation marking request for the target event of an initiating client, and the invalidation marking command comprises the following steps: receiving a message invalidation marking command aiming at a target message and sent by a server of a chat tool, wherein the message invalidation marking command is generated according to a message invalidation marking request aiming at the target message of an initiating client;
marking the target event as invalid on a responding client, comprising: the targeted message is marked as invalid on the respective recipient's response client for the targeted message.
8. The method of claim 5, wherein the target event is a call,
receiving an invalidation marking command for a target event sent by a server, wherein the invalidation marking command is generated according to an invalidation marking request for the target event of an initiating client, and the invalidation marking command comprises the following steps: a server receiving call application sends a call invalid marking command aiming at a target call, wherein the call invalid marking command is generated according to a call invalid marking request aiming at the target call of an initiating client;
marking the target event as invalid on a responding client, comprising: and marking the target call as an invalid state on a response client of the contact of the target call.
9. The method according to any one of claims 1 to 8, wherein marking the target event as invalid further comprises at least one of:
marking the target event as belonging to an invalid state on an interactive interface corresponding to the target event;
setting the target event as a disable response.
10. An apparatus for flagging event invalidity, comprising:
a first receiving module, configured to receive an invalid flag request for a target event from an initiating client;
the first generation module is used for generating an invalid mark command according to the invalid mark request;
a first sending module, configured to send the invalidation marking command to a responding client of the target event, where the invalidation marking command is used to mark the target event as an invalid state on the responding client; the marking the target event as an invalid state comprises: and sending out an invalid prompt when the response operation to the target event is detected.
11. The apparatus of claim 10, wherein the target event is a mail,
the first receiving module includes: the first receiving submodule is used for receiving a mail invalidation marking request aiming at a target mail from an initiating client of a mail application;
the first transmitting module includes: and the first sending submodule is used for sending the mail invalidation marking command to the response client of each receiver of the target mail, and the mail invalidation marking command is used for marking the target mail in an invalid state on the response client of each receiver of the target mail.
12. The apparatus of claim 10, wherein the target event is a message,
the first receiving module includes: a second receiving submodule, configured to receive a message invalidation marking request for the target message from an originating client of the chat tool;
the first transmitting module includes: and the second sending submodule is used for sending the message invalidation marking command to the response client of each receiver of the target message, and the message invalidation marking command is used for marking the target message in an invalid state on the client of each receiver of the target message.
13. The apparatus of claim 10, wherein the target event is a call,
the first receiving module includes: the third receiving submodule is used for receiving a call invalid marking request aiming at the target call from an initiating client of the call application;
the first transmitting module includes: and the third sending submodule is used for sending the call invalidation marking command to a response client of the contact person of the target call, and the call invalidation marking command is used for marking the target call in an invalid state on the client of the contact person of the target call.
14. An apparatus for flagging event invalidity, comprising:
a second receiving module, configured to receive an invalidation marking command for a target event sent by a server, where the invalidation marking command is generated according to an invalidation marking request for the target event of an initiating client;
a marking module for marking the target event as an invalid state on a response client;
and the reminding submodule is used for sending out invalid reminding under the condition that the response operation to the target event is detected.
15. The apparatus of claim 14, wherein the target event is a mail,
the second receiving module includes: a fourth receiving submodule, configured to receive a mail invalidation marking command for a target mail, sent by a server of a mail application, where the mail invalidation marking command is generated according to a mail invalidation marking request for the target mail of an originating client;
the marking module includes: and the first marking submodule is used for marking the target mail as an invalid state on a response client of each receiver of the target mail.
16. The apparatus of claim 14, wherein the target event is a message,
the second receiving module includes: a fifth receiving submodule, configured to receive a message invalidation marking command for a target message sent by a server of a chat tool, where the message invalidation marking command is generated according to a message invalidation marking request for the target message of an originating client;
the marking module includes: a second tagging submodule for tagging said targeted message as invalid on a response client of each recipient of said targeted message.
17. The apparatus of claim 14, wherein the target event is a call,
the second receiving module includes: a sixth receiving submodule, configured to receive a call invalidation marking command sent by a server of a call application for a target call, where the call invalidation marking command is generated according to a call invalidation marking request of an originating client for the target call;
the marking module includes: and the third marking submodule is used for marking the target call as an invalid state on a response client of the contact of the target call.
18. The apparatus of any one of claims 14 to 17, wherein the tagging module further comprises at least one of the following sub-modules:
the fourth marking submodule is used for marking that the target event belongs to an invalid state on the interactive interface corresponding to the target event;
and the response inhibition submodule is used for setting the target event as an inhibition response.
19. An apparatus for flagging event invalidity, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
receiving an invalid marker request for a target event from an initiating client;
generating an invalid marking command according to the invalid marking request;
sending the invalidation marking command to a responding client of the target event, wherein the invalidation marking command is used for marking the target event as an invalid state on the responding client; the marking the target event as an invalid state comprises: and sending out an invalid prompt when the response operation to the target event is detected.
20. An apparatus for flagging event invalidity, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
receiving an invalid marking command aiming at a target event sent by a server, wherein the invalid marking command is generated according to an invalid marking request aiming at the target event of an initiating client;
marking the target event as invalid on a responding client;
the marking the target event as an invalid state comprises: and sending out an invalid prompt when the response operation to the target event is detected.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610943195.2A CN108023806B (en) | 2016-10-31 | 2016-10-31 | Method and device for marking event invalidation |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610943195.2A CN108023806B (en) | 2016-10-31 | 2016-10-31 | Method and device for marking event invalidation |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108023806A CN108023806A (en) | 2018-05-11 |
| CN108023806B true CN108023806B (en) | 2020-10-30 |
Family
ID=62070015
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610943195.2A Active CN108023806B (en) | 2016-10-31 | 2016-10-31 | Method and device for marking event invalidation |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108023806B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101931916A (en) * | 2010-09-03 | 2010-12-29 | 中兴通讯股份有限公司 | Method and system for controlling sending of electronic mail (E-mail) of wireless communication terminal |
| CN102223392A (en) * | 2010-04-16 | 2011-10-19 | 佳能株式会社 | Print server and printing apparatus, network printing system, and printing method |
| CN104869051A (en) * | 2015-03-18 | 2015-08-26 | 广东时代互联科技有限公司 | Method and system for revoking e-mail |
| CN106027788A (en) * | 2016-06-21 | 2016-10-12 | 珠海市魅族科技有限公司 | Method and device for processing popup message |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9083667B2 (en) * | 2008-01-16 | 2015-07-14 | International Business Machines Corporation | System and method for follow-on message processing |
-
2016
- 2016-10-31 CN CN201610943195.2A patent/CN108023806B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102223392A (en) * | 2010-04-16 | 2011-10-19 | 佳能株式会社 | Print server and printing apparatus, network printing system, and printing method |
| CN101931916A (en) * | 2010-09-03 | 2010-12-29 | 中兴通讯股份有限公司 | Method and system for controlling sending of electronic mail (E-mail) of wireless communication terminal |
| CN104869051A (en) * | 2015-03-18 | 2015-08-26 | 广东时代互联科技有限公司 | Method and system for revoking e-mail |
| CN106027788A (en) * | 2016-06-21 | 2016-10-12 | 珠海市魅族科技有限公司 | Method and device for processing popup message |
Non-Patent Citations (1)
| Title |
|---|
| 基于kano模型的顺风车服务设计研究;丁鼎;《中国优秀硕士学位论文全文数据库（信息科技辑）》;20160715;正文3.3、4.2章节，附图3-8、3-9、3-13、3-22 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108023806A (en) | 2018-05-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101884543B1 (en) | Method and device for warning | |
| US20130035054A1 (en) | Phone with multi-portal access for display during incoming and outgoing call | |
| CN104683568A (en) | Information reminding method and information reminding device | |
| CN104506410A (en) | Instant communication method and device | |
| CN108173744B (en) | Information processing method and device | |
| CN104113646A (en) | Method and apparatus for calling forwarding | |
| CN112632418A (en) | Password sharing method and device, electronic equipment and storage medium | |
| EP2991326B1 (en) | Method, apparatus and computer program product for processing communication identification | |
| CN112202582B (en) | Group establishing method and device, electronic equipment and storage medium | |
| CN107171938B (en) | Method and device for shielding social friends | |
| CN108011990B (en) | Contact management method and device | |
| CN106231137A (en) | Processing method and processing device based on electricity | |
| US10263925B2 (en) | Method, device and medium for sending message | |
| CN105939424B (en) | Application switching method and device | |
| CN105245705A (en) | Telephone prompting method and device | |
| CN111181844A (en) | Message processing method, device and medium | |
| CN105101121B (en) | A kind of method and device that information is sent | |
| CN104363166B (en) | Instant communicating method, device and intelligent terminal | |
| CN107295167B (en) | Information display method and device | |
| CN105100352A (en) | Method and device for acquiring contact information | |
| CN108023806B (en) | Method and device for marking event invalidation | |
| CN107026941B (en) | Method and device for processing reply of unread message | |
| CN107846481B (en) | Account management method and device | |
| CN107104878B (en) | User state changing method and device | |
| CN107181850B (en) | Number marking method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |