Systems and Methods for Sending Messages

• US 20150127757A1
• Filed: 01/08/2015
• Published: 05/07/2015
• Est. Priority Date: 08/16/2013
• Status: Abandoned Application

• Current Assignee: Tencent Technology Company Limited (Tencent Holdings Limited)
• Original Assignee: Tencent Technology Company Limited (Tencent Holdings Limited)
• Inventors: Liu, Li, Shu, Jun, Tian, Ming, Wang, Yao, Wang, Hui
• Application Number:
  US14/592,314
• Publication Number:
  US 20150127757A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads
• CPC Class Codes: H04L 51/234 for tracking messages

Abstract

Devices and methods are provided for sending messages. For example, a receiving user list corresponding to a specific message to be sent is acquired; a first timeline refresh request associated with a first receiving user in the receiving user list is received; and upon the capture of the first timeline refresh request, the specific message is sent to a client associated with the first receiving user that refreshes a timeline.

Claims

1. A method for sending messages, the method comprising:

acquiring a receiving user list corresponding to a specific message to be sent;

capturing a first timeline refresh request associated with a first receiving user in the receiving user list; and

upon the capture of the first timeline refresh request, sending the specific message to a client associated with the first receiving user that refreshes a timeline.

2. The method of claim 1, wherein the acquiring a receiving user list corresponding to a specific message to be sent includes:

acquiring a sending user identification associated with the specific message;

searching for a listening user list associated with a sending user based on at least information associated with the sending user identification; and

adopting the listening user list as the receiving user list corresponding to the specific message, wherein one or more receiving user identifications are included in the receiving user list.

3. The method of claim 2, wherein the upon the capture of the first timeline refresh request, sending the specific message to a client associated with the first receiving user that refreshes a timeline includes:

upon the capture of the first timeline refresh request, acquiring a first user identification associated with the first receiving user;

matching the first user identification with the receiving user list;

in response to the first user identification existing in the receiving user list,

determining that the first timeline refresh request associated with the first receiving user is captured; and

sending the specific message to the client.

4. The method of claim 3, further comprising:

in response to the specific message being sent to the client, deleting the first user identification from the receiving user list.

5. The method of claim 1, further comprising:

presetting one or more time points or one or more time periods for capturing the first timeline refresh request;

wherein the capturing a first timeline refresh request associated with a first receiving user in the receiving user list includes;

capturing the first timeline refresh request associated with the first receiving user at the preset time points;

or

capturing the first timeline refresh request associated with the first receiving user according to the preset time periods.

6. The method of claim 5, further comprising:

in response to the specific message being sent to all receiving users in the receiving user list,

stopping capturing one or more second timeline refresh requests associated with one or more second receiving users in the receiving user list; and

stopping sending the specific message.

7. The method of claim 5, further comprising:

in response to a preset termination time being reached,

stopping capturing one or more second timeline refresh requests associated with one or more second receiving users in the receiving user list; and

stopping sending the specific message.

8. A method for receiving messages, the method comprising:

sending a timeline refresh request to a server; and

displaying a specific message received from the server according to a first time associated with the specific message in a timeline of a receiving user.

9. The method of claim 8, wherein the first time corresponds to a time when the specific message is received.

10. A server comprising:

a capturing module configured to acquire a receiving user list corresponding to a specific message to be sent and capture a first timeline refresh request associated with a first receiving user in the receiving user list; and

a message sending module configured to, upon the capture of the first timeline refresh request, send the specific message to a client associated with the first receiving user that refreshes a timeline.

11. The server of claim 10, wherein the capturing module is further configured to acquire a sending user identification associated with the specific message, search for a listening user list associated with a sending user based on at least information associated with the sending user identification, and adopt the listening user list as the receiving user list corresponding to the specific message, wherein one or more receiving user identifications are included in the receiving user list.

12. The server of claim 10, wherein the message sending module is further configured to:

upon the capture of the first timeline refresh request, acquire a first user identification associated with the first timeline refresh request;

match the first user identification with the receiving user list;

in response to the first user identification existing in the receiving user list, determine that the first timeline refresh request associated with the first receiving user is captured; and

send the specific message to the clients.

13. The server of claim 11, further comprising:

a deleting module configured to, in response to the specific message being sent to the client, delete the receiving user identification from the receiving user list.

14. The server of claim 10, further comprising:

a setting module configured to preset one or more time points or one or more time periods for capturing the first timeline refresh request;

wherein the message sending module is further configured to capture the first timeline refresh request associated with the first receiving user at the preset time points or capture the first timeline refresh request associated with the first receiving user according to the preset time periods.

15. The server of claim 14, wherein the message sending module is further configured to, in response to the specific message being sent to all receiving users in the receiving user list, stop capturing one or more second timeline refresh requests associated with one or more second receiving users in the receiving user list and stop sending the specific message.

16. The server of claim 14, wherein:

the setting module is further configured to preset a termination time; and

the message sending module is further configured to, in response to the preset termination time being reached,

stop capturing one or more second timeline refresh requests associated with one or more second receiving users in the receiving user list; and

stop sending the specific message.

17. The server of claim 10, further comprising:

one or more data processors; and

a computer-readable storage medium;

wherein one or more of the capturing module, and the message sending module are stored in the storage medium and configured to be executed by the one or more data processors.

18. A client comprising:

a sending module configured to send a timeline refresh request to a server; and

a display module configured to display a specific message received from the server according to a first time associated with the specific message in a timeline of a receiving user.

19. The client of claim 18, wherein the first time corresponds to a time when the specific message is received.

20. The client of claim 18, further comprising:

one or more data processors; and

a computer-readable storage medium;

wherein one or more of the sending module, and the display module are stored in the storage medium and configured to be executed by the one or more data processors.

21. A message sending system comprising:

a server; and

a client;

wherein the server includes;

a capturing module configured to acquire a receiving user list corresponding to a specific message to be sent and capture a timeline refresh request associated with a receiving user in the receiving user list; and

a message sending module configured to, upon the capture of the timeline refresh request, send the specific message to the client associated with the receiving user that refreshes a timeline;

wherein the client includes;

a sending module configured to send the timeline refresh request to the server; and

a display module configured to display the specific message received from the server according to a first time associated with the specific message in a timeline of the receiving user.

22. A non-transitory computer readable storage medium comprising programming instructions for sending messages, the programming instructions configured to cause one or more data processors to execute operations comprising:

acquiring a receiving user list corresponding to a specific message to be sent;

capturing a timeline refresh request associated with a first receiving user in the receiving user list; and

upon the capture of the timeline refresh request, sending the specific message to a client associated with the first receiving user that refreshes a timeline.

23. A non-transitory computer readable storage medium comprising programming instructions for receiving messages, the programming instructions configured to cause one or more data processors to execute operations comprising:

sending a timeline refresh request to a server; and

displaying a specific message received from the server according to a first time associated with the specific message in a timeline of a receiving user.