METHOD AND SYSTEM FOR SUBSCRIBING LONG TAIL INFORMATION

• US 20150134762A1
• Filed: 01/20/2015
• Published: 05/14/2015
• Est. Priority Date: 07/18/2013
• Status: Active Grant

• Current Assignee: Tencent Technology Company Limited (Tencent Holdings Limited)
• Original Assignee: Tencent Technology Company Limited (Tencent Holdings Limited)
• Inventors: HUANG, SHUICHENG
• Granted Patent: US 10,212,106 B2
• Time in Patent Office: Days
• US Class Current: 709/207
• CPC Class Codes: H04L 51/046 Interoperability with other network applications or services
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

A long tail information subscribing method is provided. The method includes receiving a to-be-subscribed long tail information type from a client-side, and determining whether an information content matches the long tail information type. The method also includes, when it is determined that an information content matches the long tail information type, sending a long tail information alert message to the client-side to cause the client-side to update an alert display based on the long tail information alert message. Further, the method includes receiving a trigger request message corresponding to the alert display from the client-side, and sending long tail information content corresponding to the trigger request message to the client-side. The information distribution efficiency is thus substantially improved.

Claims

1. A long tail information subscribing method, comprising:

receiving, by a server, a to-be-subscribed long tail information type from a client-side;

determining, by the server, whether an information content matches the long tail information type;

when it is determined that an information content matches the long tail information type, sending, by the server, a long tail information alert message to the client-side to cause the client-side to update an alert display based on the long tail information alert message;

receiving, by the server, a trigger request message corresponding to the alert display from the client-side; and

sending, by the server, long tail information content corresponding to the trigger request message to the client-side.

2. The method according to claim 1, wherein:

the method further comprises;

storing a type identifier of the to-be-subscribed long tail information type in a type identifier table; and

determining whether the information content matches the long tail information type further includes;

determining whether the information content contains a type identifier that matches the long tail information type identifier stored in the type identifier table;

when it is determined that the information content contains the type identifier that matches the long tail information type identifier stored in the type identifier table, determining that the information content matches the long tail information type.

3. The method according to claim 2, further comprising:

updating, by the client-side, the alert display based on the long tail information alert message; and

determining a number of information contents matching the long tail information type, wherein updating further includes;

displaying the number of information contents on the alert display.

4. The method according to claim 2, further comprising:

updating, by the client-side, the alert display based on the long tail information alert message,

wherein receiving the to-be-subscribed long tail information type from the client-side includes;

receiving the to-be-subscribed long tail information type from a client-side browser on the client-side; and

wherein updating further includes;

updating, by the client-side browser, the alert display based on the long tail information alert message.

5. The method according to claim 4, wherein receiving the to-be-subscribed long tail information type from the client-side browser includes:

providing, by the server, the client-side browser with long tail information subscription option data;

based on the long tail information subscription option data, the client-side browser displaying, by the client-side browser, a subscription option list of the long tail information;

receiving, by the client-side browser, a select operation performed by a user on the long tail information subscription option list;

determining, by the client-side browser, the to-be-subscribed long tail information type based on the select operation; and

receiving, by the server, the to-be-subscribed long tail information type from the client-side browser.

6. A long tail information subscribing apparatus, comprising:

an information type receiving unit configured to receive a to-be-subscribed long tail information type from a client-side;

a push unit configured to determine whether an information content matches the long tail information type and, when it is determined that an information content matches the long tail information type, to send a long tail information alert message to the client-side to cause the client-side to update an alert display based on the long tail information alert message; and

an information transmitting unit configured to receive a trigger request message corresponding to the alert display from the client-side and to send long tail information content corresponding to the trigger request message to the client-side.

7. The apparatus according to claim 6, wherein the push unit is further configured to:

store a type identifier of the to-be-subscribed long tail information type in a type identifier table;

determine whether the information content contains a type identifier that matches the long tail information type identifier stored in the type identifier table; and

when it is determined that the information content contains the type identifier that matches the long tail information type identifier stored in the type identifier table, determine that the information content matches the long tail information type.

8. The apparatus according to claim 7, wherein:

the push unit is configured to determine a number of information contents matching the long tail information type, to push an long tail information alert message to the client-side, wherein the long tail information alert message contains the number of information contents matching the long tail information type, to cause the client-side to display the number of the information contents on the alert display.

9. The apparatus according to claim 7, wherein:

the information type receiving unit is configured to receive the to-be-subscribed long tail information type from a client-side browser;

the push unit is configured to push the long tail information alert message to the client-side browser to cause the client-side browser to update the alert display according to the long tail information alert message.

10. The apparatus according to claim 9, wherein:

the information type receiving unit is configured to provide long tail information subscription option data to the client-side browser to cause the client-side browser to display a subscription options list of the long tail information, to receive a select operation performed by a user on the long tail information subscription option list, and to determine the to-be-subscribed long tail information type based on the select operation; and

the information type receiving unit is further configured to receive the to-be-subscribed long tail information type from the client-side browser.

11. An long tail information subscribing system, comprising:

a client-side configured to send out a to-be-subscribed long tail information type;

a content management server configured to receive the to-be-subscribed long tail information type from the client-side;

a push server; and

a content server configured to edit information contents and to send the edited information contents to the content management server,

wherein;

the content management server is further configured to determine whether an information content matches the long tail information type and, when it is determined that an information content matches the long tail information type, to send a push request to the push server;

the push server is further configured to push a long tail information alert message to the client-side; and

the client-side is further configured to update an alert display based on the long tail information alert message and to send a trigger request message corresponding to the alert display to the content server; and

the content server is further configured to send long tail information content corresponding to the trigger request message to the client-side.

12. The system according to claim 11, wherein the content management server is configured to:

store a type identifier of the to-be-subscribed long tail information type in a type identifier table;

determine whether the information content contains a type identifier that matches the long tail information type identifier stored in the type identifier table; and

when it is determined that the information content contains the type identifier that matches the long tail information type identifier stored in the type identifier table, determine that the information content matches the long tail information type.

13. The system according to claim 12, wherein:

the content management server is configured to receive the to-be-subscribed long tail information type from a client-side browser on the client-side; and

the client-side browser is configured to update the alert display based on the long tail information alert message.

14. The system according to claim 13, wherein:

the content management server is further configured to provide long tail information subscription option data to the client-side browser;

the client-side browser is configured to display a subscription option list of the long tail information based on the long tail information subscription option data, to receive a select operation performed by a user on the long tail information subscription option list, and to determine the to-be-subscribed long tail information type based on the select operation; and

the content management server is further configured to receive the to-be-subscribed long tail information type from the client-side browser.