Messenger Client And Method For Updating Messages In Messenger Client

• US 20130124660A1
• Filed: 01/09/2013
• Published: 05/16/2013
• Est. Priority Date: 08/24/2010
• Status: Active Grant

• Current Assignee: Tencent Technology Company Limited (Tencent Holdings Limited)
• Original Assignee: Tencent Technology Company Limited (Tencent Holdings Limited)
• Inventors: LAO, Ning
• Granted Patent: US 9,009,245 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 12/6418 Hybrid transport
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/224 providing notification on incoming messages, e.g. pushed notifications of received messages
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements

Abstract

Updating messages in a messenger client includes a messenger client judging whether it is necessary to pull a new message or a new message notification from a messenger server according to a state of the messenger client; performing an action of pulling a new message notification from the messenger server in response to a determination that it is necessary to pull a new message notification; and performing an action of pulling new messages from the messenger server in response to a determination that it is necessary to pull a new message. The messenger client includes a state judging module and a pulling module. A new message notification is pulled when it is determined it is only necessary to pull a new message notification.

Claims

1. A method for updating messages in a messenger client, comprising:

judging, by a messenger client, whether it is necessary to pull a new message or a new message notification from a messenger server according to a state of the messenger client;

performing, by the messenger client, an action of pulling a new message notification from the messenger server in response to a determination that it is necessary to pull a new message notification; and

performing, by the messenger client, an action of pulling new messages from the messenger server in response to a determination that it is necessary to pull a new message.

2. The method of claim 1, wherein the new message notification includes a total number of new messages;

and

the method further comprises;

prompting, by the messenger client, a user that there is a new message when the total number in the new message notification pulled is larger than 0 after pulling the new message notification from the messenger server.

3. The method of claim 2, wherein the prompting by the messenger client the user that there is a new message comprises:

lightening, by the messenger client, a tag on a messenger interface, and displaying the total number of new messages on a tag on the messenger interface.

4. The method of claim 1, further comprising:

displaying, by the messenger client, the new messages on a messenger interface when the number of the new messages is larger than 0 after performing the action of pulling new messages from the messenger server.

5. The method of claim 1, wherein the state of the messenger client comprises one of the messenger client is invisible, the messenger client is visible but a messenger interface is invisible, or both the messenger client and the messenger interface are visible.

6. The method of claim 5, wherein the judging whether it is necessary to pull a new message or a new message notification from a messenger server according to a state of the messenger client comprises:

making a determination that the messenger client does not need to pull a new message or a new message notification when the state of the messenger client indicates the messenger client is invisible;

making a determination that the messenger client needs to pull a new message notification from the messenger server when the state of the messenger client indicates the messenger client is visible but the messenger interface is invisible;

making a determination that the messenger client needs to pull a new message from the messenger server when the state of the messenger client indicates both the messenger client and the messenger interface are visible.

7. The method of claim 1, further comprising:

judging whether a current pulling frequency is within a first automatic pulling frequency limit set by the messenger server after determining it is necessary to pull a new message, performing, by the messenger client, the action of pulling new messages from the messenger server in response to a determination that the current pulling frequency is within a first automatic pulling frequency limit;

or

judging whether a current pulling frequency is within a second automatic pulling frequency limit set by the messenger server after determining it is necessary to pull a new message notification, performing, by the messenger client, the action of pulling the new message notification from the messenger server in response to a determination that the current pulling frequency is within a second automatic pulling frequency limit.

8. The method of claim 7, wherein the first automatic pulling frequency limit and the second automatic pulling frequency limit is pulled by the messenger client from the messenger server when the user logs on the messenger client.

9. The method of claim 8, further comprising:

pulling, by the messenger client, a first update frequency and a second update frequency when pulling the first automatic pulling frequency limit and the second automatic pulling frequency limit;

pulling a new first automatic pulling frequency limit from the messenger server at a frequency specified by the first update frequency and updating a current first automatic pulling frequency limit by using the new first automatic pulling frequency limit;

pulling a new second automatic pulling frequency limit from the messenger server at a frequency specified by the second update frequency and updating a current second automatic pulling frequency limit by using the new second automatic pulling frequency limit.

10. The method of claim 7, further comprising:

setting, by the messenger server, a manual pulling frequency limit;

judging, by the messenger client, whether a manual refreshing process is triggered by the user after judging the current pulling frequency is beyond the first automatic pulling frequency limit;

performing, by the messenger client, the action of pulling new messages from the messenger server in response to a determination that a manual refreshing process is triggered by the user and a frequency of manual refreshing is within the manual pulling frequency limit.

11. The method of claim 1, further comprising:

judging, by the messenger client, whether the number of new messages to be pulled exceeds a pre-defined threshold before performing the action of pulling new messages from the messenger server;

pulling, by the messenger client, a pre-defined number of most recent messages from the messenger server in response to a determination that the number of new messages to be pulled exceeds the pre-defined threshold; and

pulling, by the messenger client, all of the new messages from the messenger server in response to a determination that the number of new messages to be pulled does not exceed the pre-defined threshold.

12. The method of claim 11, further comprising:

displaying, by the messenger client, the pre-defined number of most recent messages on the messenger interface when only the pre-defined number of most recent messages are pulled from the messenger server, and displaying a placeholder on the messenger interface representing new messages which have not been pulled;

displaying, by the messenger client, all of the new messages on the messenger interface when all of the new messages are pulled from the messenger server.

13. The method of claim 12, further comprising:

pulling, by the messenger client, the new messages which have not been pulled from the messenger server after a click by the user on the placeholder on the messenger interface, and displaying the new messages currently pulled on the messenger interface.

14. A messenger client, comprising:

a state judging module, configured to judge whether it is necessary to pull a new message or a new message notification from a messenger server according to a state of a messenger client;

a pulling module, configured to perform an action of pulling new messages from the messenger server when the state judging module determines it is necessary to pull a new message from the messenger server, and to perform an action of pulling a new message notification from the messenger server when the state judging module determines it is necessary to pull a new message notification.

15. The messenger client of claim 14, wherein the new message notification includes a total number of new messages, and the messenger client further comprises:

a new message notification displaying module, configured to lighten a tag on the micro blog interface if the total number of new messages in the new message notification pulled is larger than 0 after the pulling module performed the action of pulling the new message notification from the micro blog server; and

a new message displaying module, configured to display the new messages pulled on the micro blog interface if the number of the new messages pulled is larger than 0 after the pulling module performed the action of pulling the new messages from the micro blog server.

16. The messenger client of claim 15, wherein

the pulling module is further configured to judge whether the number of new messages to be pulled exceeds a pre-defined threshold before pulling the new messages from the micro blog server, pull a pre-defined number of most recent messages from the micro blog server in response to a determination that the number of new messages to be pulled exceeds a pre-defined threshold, and pull all of the new messages from the micro blog server in response to a determination that the number of new messages to be pulled does not exceed a pre-defined threshold;

wherein the pre-defined number is smaller than the pre-defined threshold.

17. The messenger client of claim 16, wherein

the new message displaying module is further configured to display the pre-defined number of most recent messages on the micro blog interface when the pulling module pulls only the pre-defined number of most recent messages from the micro blog server, and display a placeholder on the micro blog interface representing the new messages not pulled.

18. The messenger client of claim 17, wherein

the pulling module is further configured to pull new messages which have not been pulled after a click by a user on the placeholder on the messenger interface;

the new message displaying module is further configured to display the new messages pulled currently on the messenger interface.

19. The messenger client of claim 14, wherein the state of the messenger client comprises one of:

the messenger client is invisible, the messenger client is visible but a messenger interface is invisible, both the messenger client and the messenger interface are visible;

the state judging module is further configured to;

make a determination that the messenger client does not need to pull a new message or a new message notification when the state of the messenger client indicates the messenger client is invisible;

make a determination that the messenger client needs to pull a new message notification from the messenger server when the state of the messenger client indicates the messenger client is visible but the messenger interface is invisible;

make a determination that the messenger client needs to pull a new message from the messenger server when the state of the messenger client indicates both the messenger client and the messenger interface are visible.

20. The messenger client of claim 14, further comprising:

a first automatic pulling frequency judging module and a second automatic pulling frequency judging module;

wherein

the first automatic pulling frequency judging module is configured to judge whether the current pulling frequency is within a first automatic pulling frequency limit when the state judging module determines it is necessary to pull a new message; and

the second automatic pulling frequency judging module is configured to judge whether the current pulling frequency is within a second automatic pulling frequency limit when the state judging module determines it is necessary to pull a new message notification;

21. The messenger client of claim 20, wherein

the first automatic pulling frequency judging module is further configured to pull the first automatic pulling frequency limit from the messenger server when a user logs on the micro blog client;

and

the second automatic pulling frequency judging module is further configured to pull the second automatic pulling frequency limit from the messenger server when a user logs on the micro blog client.

22. The messenger client of claim 20, wherein

the first automatic pulling frequency judging module is further configured to pull a first update frequency when puling the first automatic pulling frequency limit, pull a new first automatic pulling frequency limit from the messenger server at a frequency specified by the first update frequency, and update a current first automatic pulling frequency limit by using the new first automatic pulling frequency limit;

and

the second automatic pulling frequency judging module is further configured to pull a second update frequency when puling the second automatic pulling frequency limit, pull a new second automatic pulling frequency limit from the messenger server at a frequency specified by the second update frequency, and update a current second automatic pulling frequency limit by using the new second automatic pulling frequency limit.

23. The messenger client of claim 20, further comprising:

a manual pulling frequency judging module, configured to judge whether a manual refreshing process is triggered by a user when the first automatic pulling frequency judging module determines the current pulling frequency is beyond the first automatic pulling frequency limit, and instruct the pulling module to perform the action of pulling new messages from the micro blog server in response to a determination that a manual refreshing process is triggered by a user and the frequency of the manual refreshing process is within the manual pulling frequency limit.