Messenger client and method for updating messages in messenger client

• US 9,009,245 B2
• Filed: 01/09/2013
• Issued: 04/14/2015
• Est. Priority Date: 08/24/2010
• Status: Active Grant

• Current Assignee: Tencent Technology Shenzhen Company Limited (Tencent Holdings Limited)
• Original Assignee: Tencent Technology Shenzhen Company Limited (Tencent Holdings Limited)
• Inventors: Lao, Ning
• Primary Examiner(s): Vostal, O. C.
• Application Number:
  US13/737,320
• Publication Number:
  US 20130124660A1
• Time in Patent Office: 825 Days
• Field of Search: 709/206, 709/227
• 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 the messenger client is to pull a new message or a new message notification from a messenger server according to a state of the messenger client;

deciding, by the messenger client, not to pull a new message notification or a new message in response to a determination that the state of the messenger client indicates a first user interface of the messenger client is invisible;

pulling, by the messenger client, a new message notification which indicates a total number of new messages from the messenger server in response to a determination that the state of the messenger client indicates the first user interface is visible but a second user interface for displaying messages is invisible; and

pulling, by the messenger client, the new messages from the messenger server in response to a determination that the state of the messenger client indicates both the first user interface and the second user interface are visible; and

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.

2. The method of claim 1, 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.

3. 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 before pulling the new messages, pulling, by the messenger client, the 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 before pulling a new message notification, pulling, by the messenger client, 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.

4. The method of claim 3, 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.

5. The method of claim 3, 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;

pulling, by the messenger client, the 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.

6. The method of claim 1, further comprising:

judging, by the messenger client, whether the number of the new messages to be pulled exceeds a pre-defined threshold before pulling the 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.

7. The method of claim 6, 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.

8. The method of claim 7, 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.

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

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

deciding, by the messenger client, not to pull a new message notification or a new message in response to a determination that the state of the messenger client indicates a first user interface of the messenger client is invisible;

pulling, by the messenger client, a new message notification which indicates a total number of new messages from the messenger server in response to a determination that the state of the messenger client indicates the first user interface is visible but a second user interface for displaying messages is invisible; and

pulling, by the messenger client, the new messages from the messenger server in response to a determination that the state of the messenger client indicates both the first user interface and the second user interface are visible; and

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

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

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

deciding, by the messenger client, not to pull a new message notification or a new message in response to a determination that the state of the messenger client indicates a first user interface of the messenger client is invisible;

pulling, by the messenger client, a new message notification which indicates a total number of new messages from the messenger server in response to a determination that the state of the messenger client indicates the first user interface is visible but a second user interface for displaying messages is invisible; and

pulling, by the messenger client, the new messages from the messenger server in response to a determination that the state of the messenger client indicates both the first user interface and the second user interface are visible;

wherein the first user interface of the messenger client is a home interface of the messenger client, the second user interface is a user interface displaying messages.

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

judging, by a messenger client, whether the messenger client is 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 the messenger client is 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 the messenger client is to pull a new message;

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;

judging whether a current pulling frequency is within a first automatic pulling frequency limit set by the messenger server after determining the messenger client is 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 the messenger client is 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;

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; and

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.

12. A messenger client, comprising:

a state judging module, configured to judge using a processor whether the messenger client is 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 decide using a processor not to pull a new message notification or a new message in response to a determination of the state judging module that the state of the messenger client indicates a first user interface of the messenger client is invisible, to pull a new message notification which indicates a total number of new messages from the messenger server in response to a determination of the state judging module that the state of the messenger client indicates the first user interface is visible but a second user interface for displaying messages is invisible, and to pull the new messages from the messenger server in response to a determination of the state judging module that the state of the messenger client indicates both the first user interface and the second user interface are visible;

wherein the messenger client further comprises;

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

a new message displaying module, configured to display using a processor 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 pulled the new messages from the micro blog server.

13. The messenger client of claim 12, wherein

the pulling module is further configured to judge using a processor 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.

14. The messenger client of claim 13, wherein

the new message displaying module is further configured to display using a processor 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.

15. The messenger client of claim 14, wherein

the pulling module is further configured to pull using a processor 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 using a processor the new messages pulled currently on the messenger interface.

16. The messenger client of claim 12, 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 using a processor whether the current pulling frequency is within a first automatic pulling frequency limit before the pulling module pulls the new messages; and

the second automatic pulling frequency judging module is configured to judge using a processor whether the current pulling frequency is within a second automatic pulling frequency limit before the pulling module pulls the new message notification.

17. The messenger client of claim 16, further comprising:

a manual pulling frequency judging module, configured to judge using a processor 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 pull the 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.

18. A messenger client, comprising:

a state judging module, configured to judge using a processor whether the messenger client is 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 decide using a processor not to pull a new message notification or a new message in response to a determination of the state judging module that the state of the messenger client indicates a first user interface of the messenger client is invisible, to pull a new message notification which indicates a total number of new messages from the messenger server in response to a determination of the state judging module that the state of the messenger client indicates the first user interface is visible but a second user interface for displaying messages is invisible, and to pull the new messages from the messenger server in response to a determination of the state judging module that the state of the messenger client indicates both the first user interface and the second user interface are visible;

wherein first user interface of the messenger client is a home interface of the messenger client, the second user interface is a user interface displaying messages.

19. A messenger client, comprising:

a state judging module, configured to judge using a processor whether the messenger client is 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 using a processor when the state judging module determines the messenger client is to pull a new message from the messenger server, and to perform an action of pulling a new message notification from the messenger server using a processor when the state judging module determines the messenger client is to pull a new message notification;

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 using a processor 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 using a processor 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;

wherein the messenger client 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 using a processor whether the current pulling frequency is within a first automatic pulling frequency limit when the state judging module determines the messenger client is to pull a new message; and

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

wherein the first automatic pulling frequency judging module is further configured to pull the first automatic pulling frequency limit from the messenger server using a processor 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 using a processor when a user logs on the micro blog client.

20. A messenger client, comprising:

a state judging module, configured to judge using a processor whether the messenger client is 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 using a processor when the state judging module determines the messenger client is to pull a new message from the messenger server, and to perform an action of pulling a new message notification from the messenger server using a processor when the state judging module determines the messenger client is to pull a new message notification;

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 using a processor 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 using a processor 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;

wherein the messenger client 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 using a processor whether the current pulling frequency is within a first automatic pulling frequency limit when the state judging module determines the messenger client is to pull a new message; and

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

wherein the first automatic pulling frequency judging module is further configured to pull a first update frequency using a processor 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 using a processor 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.