CN103379019B - Information push method and device in microblogging, system - Google Patents
Information push method and device in microblogging, system Download PDFInfo
- Publication number
- CN103379019B CN103379019B CN201210118969.XA CN201210118969A CN103379019B CN 103379019 B CN103379019 B CN 103379019B CN 201210118969 A CN201210118969 A CN 201210118969A CN 103379019 B CN103379019 B CN 103379019B
- Authority
- CN
- China
- Prior art keywords
- message
- messages
- microblog
- comment
- message group
- 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
- 238000000034 method Methods 0.000 title claims abstract description 30
- 238000012216 screening Methods 0.000 claims description 2
- 239000000284 extract Substances 0.000 abstract description 4
- 238000013507 mapping Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses the information push method in a kind of microblogging, methods described includes：Receive relays messages and/or comment message；Extract the relays messages and/or comment message, generation and/or the message groups for updating the correspondence same Twitter message of the same Twitter message of association；The relevant information of the message groups is pushed to client.Accordingly, it is used for the micro blog server that message is pushed in microblogging the invention also discloses a kind of, targetedly carry out relays messages and/or comment on the push of message, improve the accuracy of message push, message is prevented effectively to spread unchecked, save user to check relays messages and/or comment on the manpower spent by message and time, improve the efficiency of Twitter message push.
Description
Technical Field
The invention relates to a network communication technology, in particular to a method, a device and a system for pushing messages in a microblog.
Background
With the continuous development of internet applications, microblogs are widely and rapidly applied as a new product of an Instant Messaging (IM) message propagation mechanism.
In the microblog application, after the microblog message sent by the client is rebroadcast or commented, the microblog server pushes the rebroadcast message or the comment message of the microblog message to the client for displaying so as to prompt a user and achieve the purpose of instant messaging. However, in the existing push mode, the micro-blog server pushes the rebroadcast messages or comment messages according to a time sequence, and the client displays the rebroadcast messages or comment messages according to the time sequence, so that the rebroadcast messages or comment messages aiming at different micro-blog messages are mixed together, and a user needs to read and screen the messages one by one to find the messages of interest, which not only wastes time and labor, but also has low efficiency. This is especially true when the number of rebroadcast or comment messages is large (e.g., hundreds or thousands).
Disclosure of Invention
In view of the above, the main object of the present invention is to provide a method, an apparatus, and a system for pushing a message in a microblog, which can push a rebroadcast message and/or a comment message in a targeted manner, and improve the reading efficiency of the rebroadcast message and/or the comment message.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
the invention provides a method for pushing a message in a microblog, which comprises the following steps:
receiving rebroadcast messages and/or comment messages;
extracting rebroadcasting messages and/or comment messages related to the same microblog message, and generating and/or updating a message group corresponding to the same microblog message;
and pushing the related information of the message group to a client.
In the foregoing solution, the generating a message group corresponding to the same microblog message includes: generating a message group containing all rebroadcast messages and/or comment messages related to the same microblog message; and/or generating at least one message group containing rebroadcast messages and/or comment messages which are related to the same microblog message and have the same zone bit attribute.
In the above scheme, the updating the message group corresponding to the same microblog message includes: adding the rebroadcasting messages and/or the comment messages related to the same microblog message to a message group containing all the rebroadcasting messages and/or the comment messages related to the same microblog message; and/or adding the rebroadcast messages and/or the comment messages which are related to the same microblog message and have the corresponding mark bit attributes to a message group containing the rebroadcast messages and/or the comment messages which are related to the same microblog message and have the same mark bit attributes.
In the above scheme, before the pushing the related information of the message group to the client, the method further includes: counting the messages in each message group; the related information of the message group includes an ID of the message group and the number of messages in the message group.
In the above aspect, the method further includes: and the client receives the related information of the message group and displays the related information on the microblog page.
In the above scheme, the client displays the ID of the message group and the number of messages in the message group on a microblog page.
In the above scheme, after the pushing the relevant information of the message group to the client, the method further includes: receiving a request sent by a client for acquiring the content of a message group, inquiring the corresponding message group and pushing the rebroadcast message and/or the comment message in the corresponding message group to the client; and the client receives the rebroadcast message and/or the comment message in the corresponding message group and displays the rebroadcast message and/or the comment message on the microblog page.
In the above solution, before pushing the rebroadcast message and/or the comment message in the corresponding message group to the client, the method further includes: and screening the rebroadcast messages and/or the comment messages in the corresponding message groups according to preset pushing conditions.
The invention also provides a microblog server for pushing messages in a microblog, and the microblog server comprises: the system comprises a receiving module, a message group module and a pushing module; wherein,
the receiving module is used for receiving the rebroadcasting message and/or the comment message;
the message group module is used for extracting rebroadcast messages and/or comment messages related to the same microblog message from the rebroadcast messages and/or comment messages received by the receiving module, and generating and/or updating a message group corresponding to the same microblog message;
and the pushing module is used for pushing the related information of the message group generated and/or updated by the message group module to the client.
In the above scheme, the message group module is specifically configured to generate a message group including all rebroadcast messages and/or comment messages related to the same microblog message; and/or generating at least one message group containing rebroadcast messages and/or comment messages which are related to the same microblog message and have the same zone bit attribute.
In the above scheme, the message group module is specifically configured to add the rebroadcast message and/or the comment message associated with the same microblog message to a message group including all the rebroadcast messages and/or comment messages associated with the same microblog message; and/or adding the rebroadcast messages and/or the comment messages which are related to the same microblog message and have the corresponding mark bit attributes to a message group containing the rebroadcast messages and/or the comment messages which are related to the same microblog message and have the same mark bit attributes.
In the above scheme, the message group module is further configured to count messages in each message group; the related information of the message group includes an ID of the message group and the number of messages in the message group.
In the above scheme, the receiving module is further configured to receive a request sent by a client for obtaining the content of the message group, and send the request to the pushing module; the pushing module is further configured to query a message group corresponding to the request and push rebroadcast messages and/or comment messages in the message group to the client.
In the above scheme, the pushing module is further configured to filter the rebroadcast messages and/or comment messages in the message group according to a preset pushing condition and then push the filtered rebroadcast messages and/or comment messages to the client.
The invention also provides a system for pushing messages in the microblog, which comprises a microblog server and a client; wherein, the microblog server includes: the system comprises a receiving module, a message group module and a pushing module; wherein,
the receiving module is used for receiving the rebroadcasting message and/or the comment message;
the message group module is used for extracting rebroadcast messages and/or comment messages related to the same microblog message from the rebroadcast messages and/or comment messages received by the receiving module, and generating and/or updating a message group corresponding to the same microblog message;
the pushing module is used for pushing the related information of the message group generated and/or updated by the message group module to the client;
and the client is used for receiving the related information of the message group and displaying the related information on a microblog page.
In the above scheme, the client is configured to display the ID of the message group and the number of messages in the message group on a microblog page.
In the above scheme, the receiving module is further configured to receive a request sent by a client for obtaining the content of the message group, and send the request to the pushing module; the pushing module is further configured to query a message group corresponding to the request and push rebroadcast messages and/or comment messages in the message group to the client; the client is further used for receiving the rebroadcasting message and/or the comment message in the corresponding message group and displaying the rebroadcasting message and/or the comment message on the microblog page.
According to the method and the device for pushing the messages in the microblog, the rebroadcast messages and/or the comment messages related to the same microblog message are aggregated into the message group, and the related information of the message group is pushed to the user, so that the rebroadcast messages and/or the comment messages are pushed in a targeted manner, the rebroadcast messages and/or the comment messages are not pushed according to the time sequence, the accuracy of message pushing is improved, the message flooding is effectively avoided, the labor and time consumed for the user to check the rebroadcast messages and/or the comment messages are saved, and the efficiency of microblog message pushing is improved.
Drawings
FIG. 1 is a flowchart illustrating an implementation of a method for pushing messages in a microblog according to the present invention;
FIG. 2 is a schematic diagram of a composition structure of a microblog server for pushing messages in a microblog according to the present invention;
fig. 3 is a schematic flow chart of message pushing according to an embodiment of the present invention.
Detailed Description
According to the invention, the rebroadcast messages and/or comment messages related to the same microblog message are aggregated and then pushed to the client side for display, so that a user can conveniently look up interested rebroadcast messages and/or comment messages based on own requirements.
As shown in fig. 1, the method for pushing a message in a microblog of the present invention mainly includes the following steps:
step 101: receiving rebroadcast messages and/or comment messages;
step 102: extracting rebroadcasting messages and/or comment messages related to the same microblog message, and generating and/or updating a message group corresponding to the same microblog message;
here, the message group includes all or part of rebroadcast messages and/or comment messages associated with the respective microblog messages. At least one message group may be generated for the same microblog message.
Specifically, the microblog server generates a message group containing all rebroadcasting messages and/or comment messages related to the same microblog message; and/or generating at least one message group containing rebroadcast messages and/or comment messages which are related to the same microblog message and have the same zone bit attribute.
The microblog server adds the rebroadcasting message and/or the comment message related to the same microblog message to a message group containing all the rebroadcasting messages and/or comment messages related to the same microblog message; and/or adding the rebroadcast messages and/or the comment messages which are related to the same microblog message and have the corresponding mark bit attributes to a message group containing the rebroadcast messages and/or the comment messages which are related to the same microblog message and have the same mark bit attributes.
Here, the flag attribute may be an attribute of a client that transmits the rebroadcast message or the comment message, or may be an attribute of the rebroadcast message or the comment message itself. For example, whether the information is from an authenticated client, whether the information is from a related client of a client issuing the same microblog message, whether the information is from a preset VIP client, whether a preset content condition is met, and the like.
Step 103: and pushing the related information of the message group to a client.
Wherein, the related information of the message group may include an ID, a number of messages, and the like of the message group. Before the related information of the message groups is pushed to the client, the microblog server also counts the messages in each message group in real time so as to push the counting result, namely the number of the messages in each message group, to the client.
Wherein, after step 103, further comprising: and the client receives the related information of the message group and displays the related information on the microblog page. Specifically, the client displays the ID of the message group and the number of messages in the message group on a microblog page.
After step 103, the method further comprises: receiving a request sent by a client for acquiring the content of a message group, inquiring the corresponding message group and pushing the rebroadcast message and/or the comment message in the corresponding message group to the client; and the client receives the rebroadcast message and/or the comment message in the corresponding message group and displays the rebroadcast message and/or the comment message on the microblog page. Here, the microblog server may further filter and then push the rebroadcast messages and/or comment messages in the corresponding message group according to a preset push condition. The push condition may be customized by a user, for example, "block all relay messages that do not contain substantive content", or the like.
Correspondingly, the present invention further provides a microblog server for pushing messages in a microblog, as shown in fig. 2, the microblog server may include: the system comprises a receiving module, a message group module and a pushing module; the receiving module is used for receiving the rebroadcasting message and/or the comment message; the message group module is used for extracting rebroadcast messages and/or comment messages related to the same microblog message from the rebroadcast messages and/or comment messages received by the receiving module, and generating and/or updating a message group corresponding to the same microblog message; and the pushing module is used for pushing the related information of the message group generated and/or updated by the message group module to the client.
Specifically, the message group module may generate a message group including all rebroadcast messages and/or comment messages related to the same microblog message; and/or generating at least one message group containing rebroadcast messages and/or comment messages which are related to the same microblog message and have the same zone bit attribute.
The message group module can also add the rebroadcast message and/or the comment message related to the same microblog message to a message group containing all the rebroadcast messages and/or comment messages related to the same microblog message; and/or adding the rebroadcast messages and/or the comment messages which are related to the same microblog message and have the corresponding mark bit attributes to a message group containing the rebroadcast messages and/or the comment messages which are related to the same microblog message and have the same mark bit attributes.
The message group module can also be used for counting the messages in each message group; the related information of the message group may include an ID, a number of messages, etc. of the message group.
The receiving module can be further configured to receive a request sent by a client for obtaining the content of the message group, and send the request to the pushing module; the pushing module may be further configured to query a message group corresponding to the request and push a rebroadcast message and/or a comment message in the message group to the client.
Here, the push module may be further configured to filter the rebroadcast messages and/or comment messages in the message group according to a preset push condition and then push the filtered rebroadcast messages and/or comment messages to the client.
Correspondingly, the invention also provides a system for pushing messages in the microblog, and the system comprises the microblog server and the client; and the client is used for receiving the related information of the message group and displaying the related information on a microblog page. Specifically, the client is configured to display the ID of the message group and the number of messages in the message group on a microblog page.
Here, the receiving module is further configured to receive a request sent by a client for obtaining the content of the message group, and send the request to the pushing module; the pushing module is further configured to query a message group corresponding to the request and push rebroadcast messages and/or comment messages in the message group to the client; the client is further used for receiving the rebroadcasting message and/or the comment message in the corresponding message group and displaying the rebroadcasting message and/or the comment message on the microblog page.
Specifically, as shown in fig. 3, the process of pushing the rebroadcast message and/or the comment message in the microblog may include the following steps:
step 301: the current client A issues a microblog message a;
step 302: the microblog server receives rebroadcasting messages and/or comment messages related to the microblog message a;
specifically, other microblog users rebroadcast or comment a microblog message a issued by a current client A on a microblog page of the other microblog users, the clients send corresponding rebroadcast messages and/or comment messages to a microblog server, and the microblog server receives the rebroadcast messages and/or comment messages; here, when the client sends the rebroadcast message and/or the comment message to the microblog server, the client may also carry the microblog message a and/or the related information (such as information of a user ID, a Uniform Resource Locator (URL), and the like) of the client a.
Step 303: the microblog server extracts rebroadcasting messages and/or comment messages related to the microblog messages a, and generates and/or updates a message group corresponding to the microblog messages a;
the microblog server extracts rebroadcasting messages and/or comment messages associated with the microblog messages a from the received messages, and generates or updates message groups corresponding to the microblog messages a; and/or the microblog server extracts rebroadcast messages and/or comment messages associated with the microblog message a, classifies and screens the rebroadcast messages and/or comment messages based on the flag bit attributes of the rebroadcast messages and/or comment messages, and generates and/or updates different message groups corresponding to the microblog message a. Here, the message group corresponding to the microblog message a may include all or part of rebroadcast messages and/or comment messages of the microblog message a issued by the client a. Here, the flag may be a characteristic of a client that transmits the rebroadcast message or the comment message or a content characteristic of the rebroadcast message or the comment message, and may be set in advance. For example, whether the associated client from the current client, whether the associated client from the authenticated client, whether the predetermined VIP client is satisfied, whether the predetermined content condition is satisfied, or the like may be used as a flag of the rebroadcast message or the comment message, and accordingly, the flag attribute may be that the associated client from the current client or not is the associated client from the current client, is the authenticated client or not, is the VIP client or not, satisfies the predetermined content condition, or does not satisfy the predetermined content condition.
For example, the microblog server may generate three message groups for microblog message a: the method comprises a first message group, a second message group and a third message group, wherein the first message group comprises all rebroadcast messages and/or comment messages associated with a microblog message a published by a client A, and the ID of the message group can be set to be 'all'; the second message group is a rebroadcast message and/or a comment message which are associated with the microblog message a issued by the client A and come from an associated client of the client A, and the ID of the second message group can be set as 'listener'; the third message group is a rebroadcast message and/or a comment message from an authenticated client, which is associated with the microblog message a issued by the client a, and the ID of the third message group can be set as "authenticated user".
For another example, the microblog server may generate four message groups for the microblog message a, including the first message group, the second message group, the third message group, and a fourth message group, where the fourth message group includes a rebroadcast message and/or a comment message that are associated with the microblog message a and whose content satisfies a preset content condition (e.g., the number of characters exceeds a preset character threshold, etc.), and an ID of the message group may be set to "essence".
Step 304: the microblog server pushes the related information of each message group corresponding to the microblog message a to the client A and the associated client of the client A; here, the related information of the message group may include information such as an ID of the message group and the number of included messages.
In practical application, each time the microblog server receives a rebroadcasting message and/or a comment message aiming at a microblog message a issued by the client A, the microblog server updates the content and the related information of the corresponding message group in real time and pushes the related information of the corresponding message group to the client A in real time. Specifically, the microblog server adds the received rebroadcast message and/or comment message to the corresponding message group, counts the messages in the corresponding message group again, and pushes the counting result to the client a in real time.
For example, the microblog server receives a rebroadcast message for a microblog message a issued by the client a, judges that the rebroadcast message is from the associated client of the client a based on the issuing information of the rebroadcast message (including the client information issuing the rebroadcast message, etc.), adds the rebroadcast message to an 'all' message group and a 'listener' message group for the microblog message a issued by the client a, respectively, counts the number of messages in the 'all' message group and the 'listener' message group again, updates the number of messages in the 'all' message group and the 'listener' message group, and pushes the updated message group information to the client a in real time.
Step 305: after the client A or a related client of the client A is on line, receiving and displaying message group information of a microblog message a on a microblog page;
step 306: a user clicks message group information (such as a message group ID) of a microblog message a issued by a client A on a microblog page of the user, and a client B of the user generates a request for acquiring corresponding message group content and sends the request to a microblog server;
here, the request for acquiring the content of the message group may contain information such as an ID of the message group.
For example, if a user clicks an "authenticated user" message group of the microblog message a issued by the client a on a self microblog page, the client B of the user generates a request for acquiring the content of the "authenticated user" message group of the microblog message a issued by the client a and sends the request to the microblog server. Here, the request may include information such as the issue information of the microblog message a (e.g., information related to the client a issuing the microblog message a, information related to the microblog message a, and the like), and the ID of the "authenticated user" message group. The user may be a user of the client a, or a user of an associated client of the client a. Client B may be client a or an associated client of client a.
Step 307: the microblog server receives the request sent by the client B and pushes rebroadcast messages and/or comment messages contained in the corresponding message group to the client B;
for example, the microblog server receives a request sent by the client B for acquiring the content of an "authenticated user" message group for the microblog message a issued by the client a, locally queries the "authenticated user" message group for the microblog message a issued by the client a, reads the rebroadcast message and/or the comment message contained in the message group, and sends the rebroadcast message and/or the comment message to the client B. In practical application, the microblog server can send the read rebroadcast messages and/or comment messages to the client B in batches, or can send the messages to the client B at one time or one by one.
Step 308: and the client B receives and displays the rebroadcast message and/or the comment message contained in the corresponding message group on the microblog page.
For example, the client B receives a rebroadcast message and/or a comment message sent by the microblog server, displays the rebroadcast message and/or the comment message on a microblog page, and displays the message to the user. In practical applications, the client B may display the rebroadcast messages and/or the comment messages in batches (for example, display 5 rebroadcast messages and/or comment messages at a time, where the number of displayed messages may be preset or customized by a user), or display all the rebroadcast messages and/or comment messages one by one or at a time.
In the pushing process, the user can also set the pushing conditions of the rebroadcast message and/or the comment message according to needs. If the user sets the push condition, in the process of pushing the rebroadcast message and/or the comment message in step 307, the microblog server also filters the rebroadcast message and/or the comment message in the corresponding message group according to the push condition set by the user and then sends the rebroadcast message and/or the comment message to the client B. For example, if the user sets "block all rebroadcast messages not containing substantial content" in advance, in step 307, the microblog server reads the rebroadcast messages and/or comment messages of the corresponding message group, deletes the "rebroadcast messages not containing substantial content" and then sends the remaining rebroadcast messages and/or comment messages to the client B.
In the pushing process, the microblog server stores the rebroadcast messages and/or comment messages in each message group in the following ways: the microblog server stores rebroadcast messages and/or comment messages through 2 Key-List data chains (a first Key-List data chain and a second Key-List data chain), wherein the first Key-List data chain is a mapping relation between microblog messages and relevant information of clients thereof and relevant information of corresponding message groups, and the length threshold of the first Key-List data chain can be set, for example, 1500, so that the microblog server can eliminate data in the first Key-List data chain at regular time, keep the length of the first Key-List data chain not exceeding the preset length threshold, and ensure that the storage pressure is not too large; the second Key-List data chain is a mapping relationship between the related information of the message group and each rebroadcast message and/or comment message, the related information of the message group and the rebroadcast message and/or comment message contained in the message group are correspondingly stored, and a length threshold of the second Key-List data chain can also be set, for example, 1000, so that the microblog server can eliminate data in the second Key-List data chain at regular time, and keep the length of the second Key-List data chain not exceeding the preset length threshold, thereby ensuring that the storage pressure is not too large, ensuring that the stored message is latest, realizing efficient data reading and writing, and saving storage space.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (12)
1. A method for pushing a message in a microblog is characterized by comprising the following steps:
receiving rebroadcast messages and/or comment messages;
extracting rebroadcasting messages and/or comment messages related to the same microblog message, and generating and/or updating a message group corresponding to the same microblog message;
pushing the related information of the message group to a client;
before the pushing the related information of the message group to the client, the method further includes: counting the messages in each message group;
the related information of the message group includes an ID of the message group and the number of messages in the message group,
wherein the generating of the message group corresponding to the same microblog message comprises: generating at least one message group containing rebroadcast messages and/or comment messages which are related to the same microblog message and have the same zone bit attribute; the flag bit attribute is an attribute of a client that sends the rebroadcast message or the comment message.
2. The method according to claim 1, wherein the updating of the message group corresponding to the same microblog message comprises: and adding the rebroadcast messages and/or the comment messages which are related to the same microblog message and have the corresponding mark bit attributes to a message group containing the rebroadcast messages and/or the comment messages which are related to the same microblog message and have the same mark bit attributes.
3. The method for pushing the message in the microblog according to claim 1, wherein the method further comprises the following steps: and the client receives the related information of the message group and displays the related information on the microblog page.
4. The method for pushing messages in the microblog according to claim 3, wherein the client displays the ID of the message group and the number of messages in the message group on a microblog page.
5. The method for pushing messages in microblogs according to claim 1, wherein after the pushing the information related to the message group to the client, the method further comprises:
receiving a request sent by a client for acquiring the content of a message group, inquiring the corresponding message group and pushing the rebroadcast message and/or the comment message in the corresponding message group to the client;
and the client receives the rebroadcast message and/or the comment message in the corresponding message group and displays the rebroadcast message and/or the comment message on the microblog page.
6. The method for pushing messages in microblogs according to claim 1, wherein before the pushing the information related to the message group to the client, the method further comprises:
and screening the rebroadcast messages and/or the comment messages in the corresponding message groups according to preset pushing conditions.
7. A microblog server for pushing messages in a microblog, the microblog server comprising: the system comprises a receiving module, a message group module and a pushing module; wherein,
the receiving module is used for receiving the rebroadcasting message and/or the comment message;
the message group module is used for extracting rebroadcast messages and/or comment messages related to the same microblog message from the rebroadcast messages and/or comment messages received by the receiving module, and generating and/or updating a message group corresponding to the same microblog message;
the pushing module is used for pushing the related information of the message group generated and/or updated by the message group module to the client;
the message group module is also used for counting the messages in each message group;
the related information of the message group comprises the ID of the message group and the number of messages in the message group; the message group module is specifically used for generating a message group containing all rebroadcast messages and/or comment messages related to the same microblog message; and/or generating at least one message group containing rebroadcast messages and/or comment messages which are related to the same microblog message and have the same zone bit attribute, wherein the zone bit attribute is the attribute of a client side sending the rebroadcast messages or the comment messages.
8. The microblog server according to claim 7, wherein the message group module is specifically configured to add the rebroadcast message and/or the comment message associated with the same microblog message and having the corresponding flag bit attribute to a message group including the rebroadcast message and/or the comment message associated with the same microblog message and having the same flag bit attribute.
9. The microblog server according to claim 7, wherein the receiving module is further configured to receive a request sent by a client for obtaining content of a message group, and send the request to the pushing module;
the pushing module is further configured to query a message group corresponding to the request and push rebroadcast messages and/or comment messages in the message group to the client.
10. The microblog server according to claim 7, wherein the pushing module is further configured to filter the rebroadcast messages and/or comment messages in the message group according to a preset pushing condition and then push the filtered rebroadcast messages and/or comment messages to the client.
11. The system for pushing the message in the microblog is characterized by comprising a microblog server and a client; wherein, the microblog server includes: the system comprises a receiving module, a message group module and a pushing module; wherein,
the receiving module is used for receiving the rebroadcasting message and/or the comment message;
the message group module is used for extracting rebroadcast messages and/or comment messages related to the same microblog message from the rebroadcast messages and/or comment messages received by the receiving module, and generating and/or updating a message group corresponding to the same microblog message;
the pushing module is used for pushing the related information of the message group generated and/or updated by the message group module to the client;
the client is used for receiving the related information of the message group and displaying the related information on a microblog page;
the client is used for displaying the ID of the message group and the number of messages in the message group on a microblog page;
the message group module is specifically used for generating at least one message group containing rebroadcast messages and/or comment messages which are related to the same microblog message and have the same zone bit attribute; the flag bit attribute is an attribute of a client that sends the rebroadcast message or the comment message.
12. The system for pushing messages in microblogs according to claim 11, wherein the receiving module is further configured to receive a request sent by a client for obtaining content of a message group, and send the request to the pushing module;
the pushing module is further configured to query a message group corresponding to the request and push rebroadcast messages and/or comment messages in the message group to the client;
the client is further used for receiving the rebroadcasting message and/or the comment message in the corresponding message group and displaying the rebroadcasting message and/or the comment message on the microblog page.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210118969.XA CN103379019B (en) | 2012-04-20 | 2012-04-20 | Information push method and device in microblogging, system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210118969.XA CN103379019B (en) | 2012-04-20 | 2012-04-20 | Information push method and device in microblogging, system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103379019A CN103379019A (en) | 2013-10-30 |
| CN103379019B true CN103379019B (en) | 2017-10-24 |
Family
ID=49463594
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210118969.XA Active CN103379019B (en) | 2012-04-20 | 2012-04-20 | Information push method and device in microblogging, system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103379019B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104618216B (en) * | 2013-11-05 | 2019-05-17 | 腾讯科技（北京）有限公司 | Information management method, equipment and system |
| CN105099866B (en) * | 2014-05-23 | 2019-04-12 | 腾讯科技（北京）有限公司 | The control method and device that data are shown |
| CN105227425B (en) * | 2014-05-26 | 2019-11-15 | 腾讯科技（北京）有限公司 | Method, equipment and the network social intercourse system of syndication message |
| CN107222381B (en) * | 2016-03-21 | 2020-03-06 | 北大方正集团有限公司 | Microblog data propagation path determining method and device |
| CN106656736B (en) * | 2016-09-14 | 2019-10-18 | Oppo广东移动通信有限公司 | Message sink control method and terminal device |
| CN107180095A (en) * | 2017-05-16 | 2017-09-19 | 百度在线网络技术（北京）有限公司 | Method and apparatus for exhibition information |
| CN107612966B (en) * | 2017-08-11 | 2021-01-26 | 百度在线网络技术（北京）有限公司 | Feed information feedback processing method and system |
| CN107786884B (en) * | 2017-10-23 | 2021-03-05 | 咪咕视讯科技有限公司 | Barrage data processing method, server, first terminal and storage medium |
| CN108111397B (en) * | 2017-12-15 | 2020-08-04 | 北京小米移动软件有限公司 | Method and device for processing forwarding notification message |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102375866A (en) * | 2010-08-24 | 2012-03-14 | 腾讯科技（深圳）有限公司 | Rebroadcasting message presenting method and system |
| CN102387126A (en) * | 2010-09-01 | 2012-03-21 | 腾讯科技（深圳）有限公司 | Method, server, client and system for converging single microblog message |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1917463B (en) * | 2006-08-30 | 2011-02-23 | 中国移动通信集团公司 | Method for associating user information based on user's operating characters |
| CN101916274A (en) * | 2010-08-11 | 2010-12-15 | 魏新成 | Method and system for polymerization display of LinkUGC (User Generated Content) |
| CN102387090B (en) * | 2010-08-31 | 2015-05-20 | 腾讯科技（深圳）有限公司 | Device, system and method for realizing change of multi-user relationship chain |
| CN102402378B (en) * | 2010-09-17 | 2013-08-21 | 腾讯科技（深圳）有限公司 | Method and device for displaying message |
-
2012
- 2012-04-20 CN CN201210118969.XA patent/CN103379019B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102375866A (en) * | 2010-08-24 | 2012-03-14 | 腾讯科技（深圳）有限公司 | Rebroadcasting message presenting method and system |
| CN102387126A (en) * | 2010-09-01 | 2012-03-21 | 腾讯科技（深圳）有限公司 | Method, server, client and system for converging single microblog message |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103379019A (en) | 2013-10-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103379019B (en) | Information push method and device in microblogging, system | |
| CN102402378B (en) | Method and device for displaying message | |
| KR101764286B1 (en) | Providing link to portion of media object in real time in social networking update | |
| EP2574004B1 (en) | Method, apparatus and system for improving synchronization efficiency of really simple syndication service | |
| CN100544268C (en) | A kind of reminding demand service of telecommunication method and device | |
| CN102984049B (en) | Customer group is carried out according to theme and divides client and method with information transmission | |
| CN105323147A (en) | Group message reading feedback method, and server and client side device thereof | |
| CN103095746A (en) | Method and device capable of sending information to group users through microblog | |
| CN104022938A (en) | Message synchronization method, system, server and client end | |
| CN103095737B (en) | A kind for the treatment of method and apparatus of network browsing information | |
| CN101043348A (en) | Method, system and equipment for realizing advertisement service | |
| CN103001855B (en) | A kind of client and customer group divide and the method for information transmission | |
| CN102447647A (en) | Notification method, device and system based on new message | |
| CN103903124B (en) | A kind of E-mail processing method and device | |
| CN103838814A (en) | Method for dynamically displaying contacts diagram relationship | |
| CN106789598A (en) | Public number information push method, apparatus and system based on social networks chain | |
| CN101835107A (en) | Method, device and system for reporting spam | |
| JP2011191911A (en) | Advertisement distribution device, advertisement distribution system, advertisement distribution method and program | |
| CN103220343B (en) | Big data multi-system retransmission method | |
| CN103327050B (en) | application content sharing method, system and device | |
| CN104320330A (en) | Message issuing method of electronic forum | |
| CN105245437A (en) | Method for recording and preserving communication messages of webpage version instant communication platform | |
| CN103297471B (en) | A kind of method mentioning many people in microblogging and device | |
| CN102647366A (en) | Method for realizing propagation of microblog list, terminal and system | |
| US20140229534A1 (en) | Method and system for accessing micro-blog album and micro-blog client |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |