WO2012113265A1 - 微博名单传播的实现方法、终端及系统 - Google Patents

微博名单传播的实现方法、终端及系统 Download PDF

Info

Publication number
WO2012113265A1
WO2012113265A1 PCT/CN2012/000224 CN2012000224W WO2012113265A1 WO 2012113265 A1 WO2012113265 A1 WO 2012113265A1 CN 2012000224 W CN2012000224 W CN 2012000224W WO 2012113265 A1 WO2012113265 A1 WO 2012113265A1
Authority
WO
WIPO (PCT)
Prior art keywords
microblog
user
message
list
group
Prior art date
Application number
PCT/CN2012/000224
Other languages
English (en)
French (fr)
Inventor
张丽
李晶晶
Original Assignee
腾讯科技(深圳)有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority claimed from CN201110042017XA external-priority patent/CN102647366A/zh
Priority claimed from CN2011100434897A external-priority patent/CN102651713A/zh
Priority claimed from CN201110050116.2A external-priority patent/CN102655513B/zh
Priority claimed from CN201110072143.XA external-priority patent/CN102694741B/zh
Application filed by 腾讯科技(深圳)有限公司 filed Critical 腾讯科技(深圳)有限公司
Priority to US14/000,590 priority Critical patent/US20130339465A1/en
Publication of WO2012113265A1 publication Critical patent/WO2012113265A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21Monitoring or handling of messages
    • H04L51/216Handling conversation history, e.g. grouping of messages in sessions or threads
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/07User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/18Commands or executable codes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/52User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail for supporting social networking services

Definitions

  • the present invention relates to the field of network communication technologies, and in particular, to a method, a terminal, and a system for implementing a microblog list propagation.
  • Weibo applications similar to Twitter are also growing. This type of information dissemination through microblogs can spread and transmit information very quickly.
  • the way of transmitting information through Weibo is no longer limited to the one-to-one friend individual chat mode commonly used in IM (Instant Messaging) communication, or the one-to-many group message chat mode.
  • Weibo actually implements a user message chat mode from one-to-one, one-to-many to one-to-one infinity; it is a pair of infinite patterns that means that one person can spread the message to infinitely many people, the same one. People can also listen to Weibo information published by other users above 10,000, so there are new requirements for the application of large users.
  • a Weibo List can be regarded as a list of aggregated users created by Weibo users for a certain group of related Weibo users. Of course, if the user has a slight Interested in Bo, you can also join the Weibo List created by other users to listen to the Weibo messages published by users in the Weibo List.
  • Weibo users want to share the Weibo List that they have created or joined with other Weibo users.
  • Weibo system there is no one that can quickly and conveniently put Weibo. The way the List is propagated.
  • Embodiments of the present invention provide a method, a terminal, and a system for implementing microblog list propagation, which are used to promote rapid dissemination of a microblog list.
  • a method for implementing microblog list propagation including:
  • the terminal receives the microblog list sharing instruction provided by the user
  • the microblog list sharing message is automatically generated according to the basic information of the microblog list to be shared; and the microblog list sharing message is published.
  • a microblog terminal includes:
  • a receiving unit configured to receive a microblog list sharing instruction provided by the user
  • a generating unit configured to automatically generate a microblog list sharing message according to basic information of the microblog list to be shared
  • a publishing unit configured to publish the microblog list sharing message.
  • a microblog list distribution system comprising: a microblog terminal and a microblog server; wherein the microblog terminal is configured to receive a microblog list sharing command provided by the user, and automatically generate the basic information according to the microblog list to be shared.
  • the microblog list shares the message, and the microblog list sharing message is published through the microblog server.
  • the method, the terminal, and the system for implementing the microblog list propagation provided by the embodiment of the present invention automatically generate a microblog list that the user participates in after receiving the microblog list sharing instruction sent by the user, that is, the user creates the microblog list. Or sharing the microblog list information of the added microblog list information, and publishing the microblog list sharing message through the microblog server; since this process is simplified The user operates, so that the microblog list can be quickly and conveniently transmitted.
  • the microblog server After receiving the microblog list sharing message, the microblog server converts the web address information carried therein into a network link, thereby facilitating other After seeing the microblog list sharing message posted by the user, the microblog user can directly enter the microblog list that the user wants to share through the network link; therefore, the solution in the embodiment of the present invention can be greatly used. Promote the rapid spread of the Weibo list.
  • the embodiment of the present invention further provides a method, device and system for managing user group members, which realizes that a user recommends other users to a group, which greatly facilitates the extension creation of the user group.
  • an embodiment of the present invention provides a method for managing a user group member, including: receiving, by a server, a recommended join protocol command sent by a client to a predetermined user group, where the recommended join protocol command includes Recommended user ID and predetermined user group ID;
  • the recommended user ID is added to the member list of the predetermined user group.
  • an embodiment of the present invention further provides a method for managing a user group member, including: the client acquiring a recommended user ID that is recommended to join the predetermined user group;
  • the recommended join protocol command includes the pushed user ID and the predetermined user group.
  • an embodiment of the present invention provides a server, including:
  • a first receiving unit configured to receive a recommended joining association command sent by the recommended user to the predetermined user group, where the recommended joining protocol command includes the recommended user ID and the predetermined user group ID;
  • a first determining unit configured to determine, according to the predetermined user group ID received by the first receiving unit, a created user of the predetermined user group;
  • a first sending unit configured to send a recommended join notification message to the created user determined by the first determining unit, so that the created user determines whether to join the recommended user to the predetermined user group;
  • a first operating unit configured to add the recommended user ID to the predetermined user group when receiving a response message sent by the creating user to join the recommended user to the predetermined user group The list of members in the group.
  • an embodiment of the present invention further provides a client, including:
  • a first obtaining unit configured to acquire a recommended user ID that is recommended to join the predetermined user group
  • a first sending unit configured to send, to the server, a recommended joining protocol command that the recommended user joins the predetermined user group, where the recommended joining protocol The command contains the recommended user ID and the predetermined user group.
  • an embodiment of the present invention provides a system for managing a user group member, including: a client, configured to acquire a recommended user ID that is recommended to join a predetermined user group; and send a recommended user to the server to join the predetermined user group.
  • the recommendation of the group is added to the association command, and the recommended join protocol command includes the recommended user ID and the predetermined user group ID;
  • a server configured to receive a recommended join protocol command that the recommended user sent by the client joins the predetermined user group, where the recommended join protocol command includes the recommended user ID and the predetermined user group ID; according to the predetermined user group Determining a created user of the predetermined user group, and transmitting a recommendation join notification message to the create user, so that the create user determines whether to join the recommended user to the predetermined user group; when receiving the When the response message sent by the user agreeing to join the recommended user to the predetermined user group is created, the recommended user ID is added to the member list of the predetermined user group.
  • the method, device, and system for managing user group members are provided by the embodiment of the present invention.
  • the acquisition is used for reservation.
  • the recommended group user recommended by the user group, and sends a recommended join protocol command to the server to join the predetermined user group to the server; after receiving the recommended join protocol command, the server includes, according to the recommended join protocol command, a predetermined user group ID determines a created user of the predetermined user group, and sends a recommendation join notification message to the created user, and joins the recommended user to the predetermined user when receiving the consent sent by the created user
  • the recommended user ID is added to the member list of the predetermined user group, thereby realizing that the user recommends other users to a certain group, which greatly facilitates the user group.
  • Extended creation is used for reservation.
  • the embodiment of the invention further provides a method for publishing a microblog message, a microblog terminal, and a microblog server, which can implement a one-to-many event for the users outside the microblog list to improve the user experience. , improve product competitiveness"
  • an embodiment of the present invention provides a method for publishing a microblog message, including:
  • the first microblog terminal corresponding to the first user acquires the microblog message to be published by the first user, and transmits the microblog message to the microblog server;
  • the microblog server detects whether the specific location of the microblog message includes the microblog group nickname information, and if the detection flag is yes, the microblog server adds the microblog message to the microblog group. In a specific message queue for each member;
  • the microblog server sends the microblog message in the specific message queue of each member of the microblog group to the microblog terminal corresponding to each member in the microblog group for publishing.
  • the specific location of the microblog message is a preset location of a regular expression.
  • the microblog server detects whether the specific location of the microblog message includes the microblog group account information. If the detection result is yes, the microblog server adds the microblog message to the microblog. Specific message queues for each member of the group, including:
  • the microblog server parses the microblog message according to a regular matching principle, and determines a specific location of the microblog message that matches a location agreed by the preset regular expression;
  • the microblog server detects whether the specific location of the microblog message includes a microblog group account Information
  • the microblog server queries the member account information list of the microblog group according to the microblog group nickname information;
  • the microblog server adds the microblog message to a specific message queue of each member in the microblog group according to the member account information list.
  • the method further includes:
  • the microblog server determines whether the specific location of the microblog message includes the second User account information
  • the microblog server adds the microblog message to the specific message queue of the second user according to the second user nickname information
  • the microblog server scans the specific message queue of the second user, and pushes the microblog message in the specific message queue of the second user to the second microblog terminal corresponding to the second user;
  • the second microblog terminal displays the microblog message in the specific message queue of the second user on a specific message interface.
  • the microblog server sends the microblog message in the specific message queue of each member of the microblog group to the microblog terminal corresponding to each member in the microblog group for publishing, including:
  • the microblog server scans a specific message queue of each member in the microblog group, and pushes a microblog message in a specific message queue of each member in the microblog group to each member in the microblog group.
  • the microblog terminal corresponding to each member in the microblog group displays the microblog message in the specific message queue of each member in the microblog group.
  • the microblogging terminal corresponding to each member of the microblog group displays the microblog message in the specific message queue of each member of the microblog group, including:
  • the microblog terminal corresponding to each member in the microblog group provides the display reminder and the view link of the microblog message in the specific message queue to each member in the microblog group; When each member of the microblog group operates the viewing link, the microblog terminal corresponding to each member in the microblog group displays the specificity of each member in the microblog group on a specific message interface. A microblog message in the message queue.
  • the microblog server After the microblog server sends the microblog message in the specific message queue of each member of the microblog group to the microblog terminal corresponding to each member in the microblog group, the microblog server further includes :
  • the microblog terminal corresponding to the member obtains the content of the reply or the content of the rebroadcast. Encapsulating the microblog group account information and the replied content or the retransmitted content, generating a reply message or a rebroadcast message, and transmitting the message to the microblog server;
  • the microblog server adds the reply message or the rebroadcast message to the broadcast queue of the microblog group according to the microblog group account information in the reply message or the rebroadcast message;
  • the microblog server scans the broadcast queue of the microblog group, and pushes the microblog message in the broadcast queue of the microblog group to the first microblog terminal;
  • the first microblog terminal displays a microblog message in a broadcast queue of the microblog group in a group message page.
  • an embodiment of the present invention further provides a microblog terminal, including:
  • the microblog message management module is configured to manage the microblog message, and when the user issues the microblog message, obtain the microblog message to be published by the user, and transmit the microblog message to the microblog server;
  • the interface management module is configured to receive a microblog message in the specific message queue of the user sent by the microblog server, and display a microblog message in the specific message queue of the user on a specific message interface.
  • the microblog terminal further includes:
  • a microblog group management module configured to manage a microblog group, receive a microblog message in a broadcast queue of the microblog group sent by the microblog server, and display the micro message in the group message page a microblog message in the broadcast queue of the blog group;
  • a microblog message reminding module configured to provide the user with a microblog message in the specific message queue of the user, and/or a display reminder and a view link of the microblog message in the broadcast queue of the microblog group, And when the user operates the viewing link, notifying the specific message interface management module and/or the microblog group management module to display a corresponding microblog message.
  • the microblog message management module is further configured to: when the user replies or rebroadcasts a microblog message in a specific message queue as a member of the microblog group, acquiring the content replied by the user or rebroadcasting
  • the content is encapsulated by the microblog group account information and the replied content or the retransmitted content, and a reply message or a rebroadcast message is generated and transmitted to the microblog server.
  • an embodiment of the present invention further provides a microblog server, including:
  • the microblog group server is configured to store and manage basic information of the microblog group, where the basic information of the microblog group includes: a group account information and a member account information list;
  • a microblog message server configured to detect whether a specific location of the microblog message sent by the first microblog terminal includes the microblog group nickname information, and if the detection result is yes, add the microblog message to the microblog group In a specific message queue for each member of the group;
  • a microblog message pushing server configured to scan the microblog message server to add a specific message queue of each member in the microblog group, and to microblog in a specific message queue of each member in the microblog group The message is pushed to the microblog terminal corresponding to each member in the microblog group for publishing.
  • the microblog message server includes:
  • a parsing unit configured to parse a microblog message sent by the first microblog terminal according to a regular matching principle, and determine a specific location of the microblog message that matches a preset regular expression agreed location; and a detecting unit, configured to Determining, by the parsing unit, the specific location of the microblog message, detecting whether the specific location of the microblog message includes microblog group nickname information;
  • a first operation unit configured to: when the detection result of the detection unit is YES, query a list of member account information of the microblog group from the microblog group server, and according to the member account information list, The microblog message is added to a specific message queue of each member in the microblog group.
  • the microblog server side further includes:
  • the microblog user 3 server is configured to store and manage basic information of the microblog user, and the basic information of the microblog user includes: user account information;
  • the microblog message server further includes:
  • a determining unit configured to: when the detecting unit detects that the flag is no, determine whether the specific location of the microblog message includes the second user account information;
  • a second operation unit configured to add the microblog message to a specific message queue of the second user according to the second user account information when the judgment unit of the determining unit is yes, and notify
  • the microblog message pushing server pushes the microblog message in the specific message queue of the second user to the second microblog terminal corresponding to the second user for publishing.
  • the microblog message server is further configured to: when the member in the microblog group replies or rebroadcasts the microblog message posted by the first user corresponding to the first microblog terminal in the specific message queue of the member Receiving a reply message or a conversion message sent by the microblog terminal corresponding to the member, and adding the reply message or the rebroadcast message to the microblog according to the microblog group account information in the reply message or the rebroadcast message.
  • the microblog message pushing server is notified to push the microblog message in the broadcast queue of the microblog group to the first microblog terminal for publishing.
  • the method for distributing the microblog message, the microblog terminal and the microblog server end of the embodiment of the present invention have the following beneficial effects:
  • the user of the embodiment of the present invention may input the microblog group nickname information in the microblog message to be advertised, and the microblog server detects the microblog message to be advertised, when detecting the specificity of the microblog message.
  • the location includes the microblog group account information
  • the microblog message is added to a specific message queue (for example, @ message queue) of each member in the microblog group, and the microblog group is The microblog message in the specific message queue of each member is pushed to the microblog terminal corresponding to each member in the microblog group for publishing, and a single microblog user is realized (the user in the microblog group or the microblog group) User)
  • a specific message queue for example, @ message queue
  • Each member in the microblog group can perform the microblog message in the specific message queue of the ij ⁇ Replying or rebroadcasting, the microblogging terminal corresponding to each member encapsulates the microblog group account information and the replied content or the retransmitted content, generates a reply message or a rebroadcast message and sends it to the microblog server, which is based on the microblog server.
  • the group account information is added to each member's reply message or broadcast message to the broadcast queue of the microblog group and pushed to the sender (single microblog user), realizing the microblog group to a single microblog user (micro The many-to-one session of users in the blog group or users outside the microblog group further enhances the product competitiveness.
  • the embodiment of the invention further provides a microblog integration method, a microblog terminal, a microblog list, a microblog server and a system, which can implement microblog information aggregation and provide users with richer information.
  • the invention provides a microblog integration method, comprising the steps of:
  • the microblog terminal queries the microblogging message according to the topic content, and obtains the topic identifier of the topic; sends an establishment instruction that establishes the association relationship between the topic and the microblog list to which the microblog terminal belongs, to the microblog list server and/or micro a topic server; the content of the establishing instruction includes a topic identifier and a microblog list identifier; and the association relationship includes an archival relationship and/or a listening relationship;
  • the microblog list server searches for the data content corresponding to the microblog list identifier according to the microblog list identifier, and writes the topic identifier to the data content to establish a mapping relationship; and/or, the microblog topic server obtains The topic identifier of the topic is searched for the data content corresponding to the topic identifier, and the microblog list identifier is written to the data content to establish a listening relationship.
  • the microblog list server searches for the data content corresponding to the microblog list identifier according to the microblog list identifier, and writes the topic identifier to the data content, and after the step of establishing a mapping relationship Includes:
  • the microblog message server sends the microblog message sent by the microblog member in the microblog list to the message list of the topic having a mapping relationship with the microblog list.
  • the step of the microblog message server sending the microblog message sent by the microblog member in the microblog list to the message list of the topic having the mapping relationship with the microblog list includes:
  • the microblog message server obtains the microblog list identifier corresponding to the microblog member, and displays the topic identifier that has a mapping relationship with the microblog list identifier, and writes the microblog message to the topic identifier. List of interest.
  • the microblog topic server acquires the topic identifier of the topic, searches for the data content corresponding to the topic identifier, and writes the advertised blog list identifier to the data content, and further includes the step of establishing a listening relationship. :
  • the microblog message server parses the received microblog message, obtains the topic content, and queries whether the same topic content exists through the microblogging server;
  • the microblog message server sends an insert instruction to the microblog topic server to insert the topic content into the message list of the corresponding topic;
  • the microblogging device creates a new topic based on the topic content.
  • the invention also provides a microblog terminal, comprising:
  • An instruction sending module configured to send a setup instruction for establishing an association relationship between the topic and the microblog list to which the microblog terminal belongs, to the microblog server and/or the microblogging server;
  • the content includes a topic identifier and a microblog list identifier;
  • the association relationship includes a mapping relationship and/or a listening relationship;
  • a request writing module configured to search, according to the microblog list identifier, the data content corresponding to the microblog list identifier by using the microblog list server, and write the topic identifier to the data content to establish a mapping relationship; and / or,
  • the invention also provides a microblog list server, comprising:
  • a list instruction receiving module configured to receive, by the microblog terminal, an establishment instruction for establishing a mapping relationship between the topic and the microblog list to which the microblog terminal belongs; the content of the establishing instruction includes a topic identifier and a microblog list identifier;
  • a list search module configured to: according to the microblog list identifier, the search corresponding to the microblog list identifier Counting the content, and writing the topic identifier to the data content to establish a mapping relationship.
  • the invention also proposes a microblogging server, comprising:
  • a topic instruction receiving module configured to receive an establishment instruction sent by the microblog terminal to establish a listening relationship between the topic and the microblog list to which the microblog terminal belongs; the content of the establishing instruction includes a topic identifier and a microblog list identifier;
  • the topic search module is configured to acquire a topic identifier of the topic, find a data content corresponding to the topic identifier, and write the microblog list identifier to the data content to establish a listening relationship.
  • the present invention also provides a microblogging system, including a microblogging terminal, a microblog topic server, and a microblogging server, wherein the microblogging terminal is used to:
  • the content of the establishment instruction includes a topic identifier and a microblog list Identification
  • the association relationship includes a mapping relationship and/or a listening relationship
  • the microblog list server is used to:
  • the microblogging server is used for:
  • the microblog system further includes:
  • the microblog message server is configured to send the microblog message sent by the microblog terminal in the microblog list to the message list of the topic having a mapping relationship with the microblog list.
  • the microblog message server is specifically configured to:
  • the microblog message server is further configured to: Parsing the received microblog message, obtaining the topic content and querying whether the same topic content exists through the microblogging server; when present, sending the insertion instruction to the microblogging message, inserting the topic content into the corresponding a list of messages for the topic;
  • the microblogging server is also used to:
  • the invention can view the microblog list related to the topic through the topic display manner of the microblog, so that the microblog list related to the topic can be found from the topic to listen or audition operation; meanwhile, the creator of the microblog list
  • the microblog message published by the microblog list member automatically enters the message list related to the topic; thus, the microblog terminal listening to the topic can view the corresponding microblog.
  • the microblog message published by the list members realizes the integration between the topic of Weibo and the microblog list, thereby realizing information aggregation and providing users with richer information. Appendix B
  • FIG. 1 is a flowchart of a method for implementing microblog list propagation in an embodiment of the present invention
  • FIG. 2 is a schematic structural diagram of a microblog terminal according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of a microblog list distribution system according to an embodiment of the present invention
  • FIG. 4 is a flowchart of a method for implementing microblog list propagation in another embodiment of the present invention
  • a microblogging List page display in one embodiment
  • FIG. 6 is a page display of a microblog broadcast publishing window in another embodiment of the present invention
  • FIG. 7 is a display of a broadcast message page of another user receiving a shared microblog list according to another embodiment of the present invention
  • a schematic structural diagram of a microblog terminal in another embodiment of the invention
  • FIG. 9 is a flowchart of a method for managing a user group member on a server side according to an embodiment of the present invention
  • FIG. 10 is a flowchart of a method for managing a user group member on a client side according to an embodiment of the present invention
  • FIG. 12 is a flowchart of a method for managing a user group member according to another embodiment of the present invention.
  • FIG. 12 is a flowchart of a method for managing a user group member according to another embodiment of the present invention; Another method flow diagram for managing user group members in another embodiment;
  • FIG. 14 is a flowchart of another method for managing user group members in another embodiment of the present invention.
  • Figure 15 is a block diagram showing the composition of a server in another embodiment of the present invention.
  • 16 is a block diagram showing the composition of another server in another embodiment of the present invention.
  • Figure ⁇ is a block diagram of another server in another embodiment of the present invention.
  • FIG. 18 is a block diagram showing the composition of another server in another embodiment of the present invention.
  • Figure 19 is a block diagram showing the composition of another server in another embodiment of the present invention.
  • 20 is a block diagram showing the composition of another server in another embodiment of the present invention.
  • FIG. 2 is a block diagram showing the composition of another server in another embodiment of the present invention.
  • Figure 22 is a block diagram showing the composition of a client in another embodiment of the present invention.
  • 23 is a block diagram showing the composition of a client in another embodiment of the present invention.
  • 24 is a block diagram showing the composition of a client in another embodiment of the present invention.
  • 25 is a block diagram showing the composition of a client in another embodiment of the present invention.
  • 26 is a block diagram of a system for managing members of a user group according to another embodiment of the present invention.
  • FIG. 27 is a schematic structural diagram of a first embodiment of a microblog terminal according to the present invention.
  • FIG. 28 is a schematic structural diagram of a second embodiment of a microblog terminal according to the present invention.
  • 29 is a schematic structural diagram of a first embodiment of a microblog server end according to the present invention.
  • FIG. 30 is a schematic structural diagram of a second embodiment of a microblog server end according to the present invention.
  • 31 is a schematic structural diagram of an embodiment of a microblog message server according to the present invention. 12 000224
  • FIG. 34 is a flowchart of a third embodiment of a method for publishing a microblog message according to the present invention.
  • FIG. 35 is a schematic diagram of a step-by-step process of implementing a microblog integration method according to the present invention.
  • 36 is a schematic flow chart of another step in an embodiment of a microblogging method according to the present invention.
  • 39 is a schematic structural diagram of an embodiment of a microblog list server according to the present invention.
  • FIG. 40 is a schematic structural diagram of an embodiment of a microblog topic server according to the present invention.
  • FIG. 41 is a schematic structural diagram of an embodiment of a microblogging system according to the present invention.
  • Weibo has experienced rapid growth as a new product and new application that expands the message dissemination mechanism.
  • the relationship between users in Weibo is looser and in a state of a pan-link relationship, that is, users can follow any Weibo users and listen to their published Weibo messages according to their interests and hobbies. For example, the user can view a certain broadcast message and listen to the user who sends the broadcast message directly, so that the broadcast message can be spread more quickly and widely.
  • Weibo Li ⁇ is a management method for Weibo users to similar groups composed of Weibo users who are interested in themselves.
  • the members of Weibo List can be users who are concerned about themselves or users who are not concerned by themselves.
  • the management capability for the Weibo List is more provided, for example, for the management of materials and members, and the combination of the ubiquitous relationship chain of Weibo and the dissemination of broadcast messages is not enough.
  • an implementation scheme of microblog list propagation is provided, which is a microblog-based broadcast form pair that fully utilizes the above-mentioned microblogging pan-relationship chain and the dissemination of broadcast messages. Weibo List to share the program.
  • the method for implementing the microblog list propagation includes at least the following steps:
  • the terminal receives a microblog list sharing instruction provided by the user.
  • the microblog list sharing instruction may be input by the user through a code; preferably, the microblogging terminal may set a control button on the displayed microblogging page or the microblogging list page, and the user only needs to operate the mouse to click the button.
  • the control button can be used to send a microblog list sharing instruction to the microblog terminal.
  • the basic information of the microblog list includes: a name of the microblog list and a web address corresponding to the microblog list.
  • the terminal may send the generated microblog list sharing message to the microblog server and issue the microblog list sharing message through the microblog server.
  • the microblog terminal includes:
  • the receiving unit 21 is configured to receive a microblog list sharing instruction provided by the user;
  • the generating unit 22 is configured to automatically generate a microblog list sharing message according to the basic information of the microblog list to be shared;
  • the publishing unit 23 is configured to publish the microblog list sharing message.
  • the microblog list distribution system includes: a microblog terminal 3 and Weibo server 32; wherein
  • the microblog terminal 31 is configured to receive a microblog list sharing instruction provided by the user, automatically generate a microblog list sharing message according to the basic information of the microblog list to be shared, and pass the microblog list sharing message through the micro The blog server 32 is released.
  • the microblog terminal after receiving the microblog list sharing instruction issued by the user, the microblog terminal automatically generates a microblog list including the microblog list that the user participates in, that is, the microblog list information created or added by the user.
  • the message is shared, and the microblog list sharing message is distributed through the microblog server; since the process of user operation is completed, the microblog list can be quickly and conveniently transmitted.
  • microblog list propagation provided in the embodiment of the present invention and the corresponding microblog terminal thereof will be further explained in a more specific embodiment.
  • the method for implementing the microblog list propagation provided by another embodiment of the present invention specifically includes the following steps:
  • the user logs in to the microblog server through the microblog terminal.
  • the user enters the earning number and password belonging to the user through the microblog terminal, and the microblog terminal sends the account and password to the login server for user identity verification.
  • the connection channel between the microblog terminal and the login server is established; and the microblog terminal needs to ensure the connection between the microblog terminal and the login server by periodically transmitting the heartbeat packet.
  • the microblog terminal may be, but not limited to, an IM client; the user may perform related interface operations and information interaction through the microblog terminal.
  • the microblog terminal After the user logs in to the microblog, the microblog terminal obtains the microblog list ID list and the basic information corresponding to the at least one microblog list in the microblog list BD list and the microblog from the microblog server. Member list information in the List.
  • the microblogging list management module of the microblogging terminal sends a protocol command for obtaining the list of the microblog list IDs that the user participates to, and the data packet corresponding to the protocol command is carried in the packet user management server on the microblog server side.
  • the number identifier corresponding to the user The above-mentioned user participates in the microblogging list
  • the body can be a Weibo List created by the user or added.
  • the microblog user server After receiving the data packet corresponding to the protocol command, the microblog user server parses the data packet and obtains the number identifier of the user, and searches the database according to the number of the user to obtain the microblog that the user participates in.
  • the List ID list is returned to the Weibo terminal.
  • the microblog terminal queries the microblog list server to query the basic information of the microblog list in the microblog list and the member list information in each microblog list according to the microblog list ID list returned by the microblog user server. After obtaining the basic information of the microblog list and the member list information in each microblog list, the microblog terminal puts it in the local file.
  • the microblog list management module on the microblog terminal side is mainly used for pulling and storing the data and member list associated with the microblog list, and simultaneously creating a microblog list display interface and then the ⁇ bo to the microblog list.
  • the associated information data is displayed in the exhibition;
  • the microblog user server on the microblog server side is mainly used to store the user's basic information such as the listening relationship of the microblog user and the basic data, user type, and user tag attributes.
  • the microblog terminal may select one of the microblog lists for display according to the user needs, and create The microblogging list interface shown in FIG.
  • the microblog terminal receives a microblog list sharing instruction provided by the user.
  • the microblogging terminal may monitor the user's mouse click operation, and confirm whether the user clicks the "share” button on the microblog list interface shown in FIG. 5 to know whether the user has issued the microblog list sharing instruction; As long as the user clicks the "Share” button, the Weibo terminal will receive a list sharing command.
  • the microblog terminal extracts the basic information of the currently opened microblog list from the local, and automatically generates a microblog list sharing message according to the basic information of the microblog list.
  • the currently opened microblog list is the microblog list to be shared.
  • the basic information of the microblog list may be combined with the default information saved locally by the microblog terminal to form the content of the microblog list sharing message; thereafter, in the current microblog list page A microblog broadcast publishing window is created, and the content of the above microblog list sharing message is filled into the microblog broadcast publishing window.
  • the default message may be "just created a list of microblogs called '****," and found that there are a lot of interesting people and their broadcasts, and push them to share http: //***";
  • the * part of the default message will be replaced by the different Weibo List name and / or the URL corresponding to the Weibo List.
  • the microblog terminal monitors whether a mouse operation occurs on a “send” button of the microblog broadcast publishing window, and if the “send” button is clicked, the microblog message management module shares the content of the microblog list and the user number.
  • the identifier is assembled into the data packet and sent to the microblog message server on the microblog server side, and then the microblog list sharing message is distributed through the microblog message server.
  • the microblog message server generates a corresponding microblog message ID and puts it into the list of published message IDs corresponding to the user.
  • the microblog message management module is located on the microblog terminal side, and is mainly used for performing protocol command interaction with the microblog message server on the microblog server side, thereby implementing the pull of the microblog message ID list by «1" for each message.
  • the microblog message server is mainly used to manage the mapping relationship between the microblog message index (message ID) and the message body (message content); the microblog terminal can index to the corresponding message body according to the microblog.
  • the microblog list sharing message is displayed on a microblog page of other microblog users.
  • the microblogging terminal used by the other microblog users pulls the published message queue corresponding to the number identifier of the microblog user concerned, and the published message is sent.
  • the queues are sorted by time and returned to the home page corresponding to the Weibo terminal.
  • the message ID list is sent to the microblog message management module of the microblog terminal, and the message content corresponding to each message ID is extracted by using the microblog message management module, so that a microblog similar to that shown in FIG. 7 can be created.
  • the microblog message management module of the microblog terminal monitors a mouse click operation in each message body of the user. If the network link shown in FIG. 7 is clicked, the microblog terminal obtains the corresponding micro according to the network link.
  • the Bo List ID identifies the corresponding Weibo List display interface, and according to the Weibo List ID iW!l, the basic information of the Weibo List and its member number list.
  • the microblog user can view the latest news published by all members in the shared microblog list; through the spread of the pan-relationship chain, the microblog list can be quickly shared, and the microblogging is greatly expanded.
  • the use of the Weibo List is used.
  • the operation of joining the microblog list can be conveniently performed, thereby facilitating the rapid promotion of the microblog list.
  • the user directly triggers the microblog list sharing instruction by clicking "share” in a list page.
  • Weibo users can also glaze the Weibo list sharing instructions by directly clicking the control button "Share" set on their own Weibo page.
  • microblog terminal Since the number of microblog lists that a microblog user participates in is greater than one, after the microblog terminal receives the microblog list sharing instruction provided by the user, and automatically generates micro information according to the basic information of the microblog list to be shared. Before the blog sharing news, the microblogging terminal needs to do the following:
  • the microblog terminal displays to the user a list of all the microblog lists that the user participates in, so that the user selects at least one of the microblog lists; The user selects at least one microblog list from the displayed microblog list list as the microblog list to be shared, and then submits;
  • the microblog terminal After the user submits the selected Weibo List, the microblog terminal acquires information of at least one microblog list selected by the user;
  • the microblog terminal automatically generates a microblog list sharing message according to basic information corresponding to at least one microblog list selected by the user.
  • the levy terminal includes: a receiving unit 81, a generating unit 82, and a publishing unit 83;
  • the receiving unit 81 is configured to receive a microblog list sharing instruction provided by the user;
  • the generating unit 82 is configured to automatically generate a microblog list sharing message according to the basic information of the microblog list to be shared;
  • the publishing unit 83 is configured to publish the microblog list sharing message.
  • the microblog terminal further includes: an obtaining unit 84, configured to acquire basic information of the at least one microblog list that the user participates from the microblog server.
  • the microblog list to be shared may be the microblog list currently opened by the user; or the microblog list to be shared is at least one microblog list in all the microblog lists in which the user participates.
  • the display unit 85 needs to be set in the microblog terminal so that the user can conveniently access the microblog list from which the user participates. Select the Weibo List to be shared;
  • a display unit 85 configured to display, to the user, a list of all the microblog lists that the user participates in, so that the user selects at least one of the microblog lists;
  • the receiving unit 81 is further configured to receive information about at least one microblog list obtained by the user according to the microblog list displayed by the display unit;
  • the generating unit 82 is further configured to: according to the basic list corresponding to at least one microblog list selected by the user The information automatically generates a microblog list sharing message.
  • the user can publish the microblog list created or added by the user in the form of microblog broadcasting, and the interface link corresponding to the microblog list to be shared is attached in the message content, so that other microblog users view After the broadcast message, click on the Weibo List display interface link in the message to view the message list aggregated by all members of the Weibo List, and other users can select whether to subscribe or join the Weibo List by reading these messages.
  • the Weibo's ubiquitous relationship chain and the rapid propagation of messages can quickly spread the Weibo List, so that each Weibo List can also be quickly spread and grow.
  • the method, terminal and system for implementing the microblog list propagation provided in the embodiments of the present invention are applicable to any microblog system.
  • the topic is a list of aggregated messages of related microblog messages.
  • the microblog terminal can conveniently create a topic by inserting a topic in the broadcast publishing box, for example, as long as the broadcast message published by the microblog terminal contains the content.
  • the microblog terminal can aggregate the list of microblog messages associated with it through "topic content”; and the microblog list (List) function is to aggregate the terminal list of a certain type of related microblog terminal.
  • the microblog list is a list of the collection terminals that are aggregated according to the characteristics of the related microblogging microblogging terminal.
  • the microblogging list can be very convenient to interact with similar microblogging terminals through the microblogging list; the topic function of Weibo and Weibo
  • the list function has its own advantages, which is convenient for the microblogging terminal to use.
  • the use of the microblogging terminal will be inconvenient. Shadow ⁇ User experience.
  • the embodiment of the present invention further provides a method for managing a user group member.
  • the method is a method on the server side. As shown in FIG. 9, the method includes:
  • the server receives a recommended join protocol command that the recommended user sent by the client joins the predetermined user group, where the recommended join protocol command includes the recommended user ID.
  • the J ⁇ 1 server records the related information created by the user group, and stores the related information in the form of a data table, the related information includes the user group name, User group ID, creator, etc., when the service needs to obtain the creator of a user group, the user group related information data table only needs to be queried according to the ID of the user group, so that the first user group can be obtained.
  • the creator when determining the created user of the predetermined user group according to the predetermined user group, that is, the user group related information data may be queried through the predetermined user group ID.
  • the table determines the created user of the predetermined user group.
  • An embodiment of the present invention further provides a method for managing a user group member.
  • the method is a method on the client side. As shown in FIG. 10, the method includes:
  • the client obtains the recommended user recommended to join the predetermined user group.
  • the client may obtain the recommended user ID manually input by the user through the interface operation, or may receive the user from the displayed user through the interface operation.
  • the recommended user ID is selected in the group, but the method in the embodiment of the present invention is not limited. Any method for obtaining the recommended user ID that is recommended to join the predetermined user group belongs to the scope of protection of the embodiment of the present invention. .
  • 1002 Send, to the server, a recommended join protocol command that the recommended user joins the predetermined user group, where the push join protocol command includes the recommended user ID and the predetermined user group.
  • the recommended user ED recommended to join the predetermined user group is obtained, and the recommended user is added to the server.
  • a recommended join protocol command of the predetermined user group after receiving the recommended join protocol command, the server determines the created user of the predetermined user group according to the predetermined user group ID included in the recommended join protocol command, Sending a recommendation join notification message to the created user, and adding the recommended user ID to the response message sent by the create user to join the recommended user to the predetermined user group.
  • the predetermined group of users In the member list, the user is allowed to recommend other users to a certain user group, which greatly facilitates the extension creation of the user group.
  • the embodiment of the present invention further provides a method for managing user group members. As shown in FIG. 11, the method includes:
  • the client obtains the recommended user ID recommended to join the predetermined user group, and sends a recommended join protocol command to the server to join the predetermined user group, where the recommended join protocol includes the recommended user ID and the predetermined User group ID.
  • the server receives a recommended adding protocol command that the recommended user sent by the client joins the predetermined user group, and determines the user of the predetermined user group according to the predetermined user group ID.
  • the server determines, according to the recommended user ID, whether the created user of the predetermined user group is the recommended user. If the created user of the specified user group is the recommended user, step 1104 is performed. If the created user of the specified user group is not the recommended user, step 1105 is performed.
  • the recommended user ID is not added to the member list of the predetermined user group. in.
  • the method further includes:
  • the client in step 1101 acquires a plurality of user IDs recommended to join the predetermined user group, and when the recommended join protocol command is sent to the server, the multiple user IDs are recommended.
  • the user ⁇ ) list is included in the recommendation join protocol command; the server may perform a recommended join operation one by one according to the method described in steps 1102 to 1107 for each recommended user in the recommended user ID list.
  • the recommended user ID recommended to join the predetermined user group is obtained, and the recommended user is added to the server.
  • a recommended join protocol command of the predetermined user group after receiving the recommended join protocol command, the server determines, according to the predetermined user group included in the recommended join protocol command, the created user of the predetermined user group, and Sending a recommendation join notification message to the created user, and adding the recommended user ID to the response message when receiving the response message sent by the creation user to join the recommended user to the predetermined user group
  • the member list of the predetermined user group is implemented, thereby realizing that the user recommends other users to a group, which facilitates the extension creation of the user group.
  • the user recommends the joining user to the predetermined user group
  • multiple users can be recommended to join at one time, which avoids sending the recommendation joining protocol command to the server multiple times when joining one by one, which saves resources and is greatly convenient.
  • the extension of the user group is created.
  • the recommended user when the created user of the predetermined user group is the recommended user, the recommended user is directly added to the member list of the predetermined user group, thereby saving the reservation.
  • the confirmation of the user created by the user group speeds up the process of joining the recommended users.
  • the embodiment of the present invention may further send the recommended user that the recommended user has been subscribed to the user.
  • the notification message included in the group is convenient for recommending the user to know the status of the recommended user joining; and also sending the notification message to the recommended user that has been recommended to be included in the predetermined user group, so that the recommended user knows the user Joined user groups, improved users ⁇ .
  • the embodiment of the present invention further provides a method for managing a user group member.
  • the method mainly displays information about a user group created or added by a user. As shown in FIG. 12, the method includes:
  • the client sends an obtaining ID list protocol command to the server, where the obtaining ID list protocol command is used to obtain a user group ID list created or added by the user, where the obtaining ⁇ list association command includes the user ⁇
  • the client sends an acquisition ID list protocol command to the server to obtain a user group ED list created or added by the user, which may be automatically sent to the server when the user logs in to the client, or after the user logs in to the client. This is not limited by the embodiment of the present invention.
  • the server receives an acquisition ID list protocol command sent by the client, acquires a user group ID list created or added by the user according to the user ID, and sends the user group ID column 1 to the client. end.
  • the related information created by the server is saved in the form of a data table, and the related information may include a user group name, a user group ED, a creator, and the like; And the server of the related information of each user is also saved in the form of a data table.
  • the related data table can be queried according to the user ID, and the related information of the user, including the user, can be obtained.
  • the client receives a list of user group IDs created or joined by the user returned by the server, and obtains a basic group of each user group in the user group according to the user group ID list.
  • the information information, and the basic information information of each user group is displayed.
  • the user can also set whether the user group list can be viewed by other users through the privacy setting. Specifically, as shown in FIG. Includes:
  • the client obtains a privacy setting option set by the user, and the privacy setting option includes Show other users the user groups created or joined by the user.
  • the user may set the privacy setting option through the privacy setting interface when the user sets the privacy setting option, and the privacy setting option may be selected by the user in the form of a unit frame, but the embodiment of the present invention does not limit the .
  • the privacy setting option may be to display the user group created or added by the user to other users in the profile or the guest page, but the embodiment of the present invention does not limit this, as long as the The privacy setting option includes whether to show other users the user groups created or joined by the user.
  • the client sends a privacy setting protocol command to the server according to the privacy setting option, where the user is included in the privacy setting protocol command
  • the server receives a privacy setting protocol command sent by the client, obtains data content corresponding to the privacy setting according to the user ID, and performs privacy setting on the data content according to the privacy setting protocol command, so as to When the user queries the user's profile, it is determined according to the privacy setting whether to display the user group created or added by the user to other users.
  • the user may view the personal data of other users on the client.
  • the user obtains the privacy information according to the different user settings.
  • the personal data is different, including personal data containing a list of user groups created or joined by the user, and personal data that does not contain a list of user groups created or added by other users.
  • the specific method is as shown in FIG. 14, and the method includes:
  • the client sends a protocol command for acquiring other user profiles to the server, where the protocol command for acquiring other user profiles includes the user ID; wherein the protocol command for obtaining other user profiles is A protocol command sent to the server when the user queries the profile of a user other than himself.
  • the server receives a protocol command sent by the client to obtain other user profiles, where the protocol command for acquiring other user profiles includes the user ID, and obtains a privacy setting item corresponding to the user according to the user ⁇ ) Basic information about the users.
  • the privacy setting item is to display a user group created or added by a user to another user, obtain a user group ID list created or added by the user, and base the user The data and the user group ID column created or joined by the user; 1 ⁇ 2 is sent to the client.
  • the client receives the basic data of the user sent by the server, and a user group ID list created or added by the user, and obtains each user in the user group ID list according to the user group I list query.
  • the basic resource of the group is frf
  • the first profile interface of the user is created according to the basic profile information of the user group and the basic profile of the user, and the first profile is created.
  • the interface is displayed, and the user's personal data is obtained.
  • the server sends the basic data of the user to the client.
  • the client receives the basic data of the user sent by the server, creates a second personal data interface of the user according to the basic data of the user, and displays the second personal data interface, ending the present Acquisition of secondary user profiles.
  • the user group created or added by the user may be displayed to the user in the user profile, so that the user can view the user group included in the user profile, thereby improving the user.
  • the user after displaying the information of the user group created or added by the user to the user, the user can set whether the user group list can be viewed by other users through the privacy setting operation interface, and can satisfy the user's privacy. Protection; When the user is set to show other users the user group created or joined by the user, other users can conveniently view the user group related to the user, which greatly facilitates the user to expand and create the user group.
  • the embodiment of the present invention further provides a server.
  • the server includes: a first receiving unit 151, a first determining unit 152, a first sending unit 153, and a first operating unit 154.
  • the first receiving unit 151 is configured to receive a recommended join protocol command sent by the client to join the predetermined user group, where the recommended join protocol command includes the user ID and the predetermined user group.
  • the first determining unit 152 is configured to determine, according to the predetermined user group I received by the first receiving unit 151, a created user of the predetermined user group.
  • a first sending unit 153 configured to send a recommendation join notification message to the created user determined by the first determining unit 152, so that the creating user determines whether the recommended user is added to the In the scheduled user group.
  • the first working unit 154 is configured to add the recommended user ID to the predetermined message when receiving the response message sent by the creating user to join the recommended user to the predetermined user group. In the member list of the user group.
  • the server further includes: a second operating unit 155.
  • the second operation unit 155 is configured to not add the recommended user ID to the subscription when receiving the response message sent by the creating user to reject the recommended user to join the predetermined user group.
  • the member list of the user group In the member list of the user group,
  • the server further includes: a second determining unit 156.
  • a second determining unit 156 configured to: when the recommendation protocol command further includes a recommended user ID, after the first determining unit 152 determines the created user of the predetermined user group according to the predetermined user group ID, according to The recommended user ED determines whether the created user of the predetermined user group is the recommended user.
  • the first operation unit 154 is further configured to: when the second determining unit 56 determines that the created user of the predetermined user group is the recommended user, directly adding the recommended user ID to the pre- In the member list of the group.
  • the first sending unit 153 is further configured to: when the second determining unit 156 determines that the created user of the predetermined user group is not the recommended user, send a recommendation join notification message to the created user.
  • the server further includes: a first notification unit 157 and/or a second notification unit 158.
  • a first notification unit 157 configured to send, after the first operation unit 154, the recommended user ID to a member list of the predetermined user group, send the recommended user that the recommended user has been subscribed to the recommended user Notification message included in the group.
  • the server further includes: a second receiving unit 159, a first obtaining unit 1510, and a second sending unit 15?
  • the second receiving unit 159 is configured to receive an access ⁇ ) list protocol command sent by the client, where the acquiring the ID list protocol command is used to obtain a user group ID list created or added by the user, where the acquiring the ID list protocol command includes The user ⁇
  • the first obtaining unit 1510 is configured to obtain, according to the user ID received by the second receiving unit 159, a user group ID list created or added by the user.
  • the second sending unit 1511 is configured to send the user group ID list obtained by the first acquiring unit 1510 to the client.
  • the server further includes: a third receiving unit 1512, a second obtaining unit 1513, and a setting unit 1514.
  • a third receiving unit 1512 configured to receive a privacy setting protocol command sent by the client, where the privacy setting protocol command includes the user ID, where the privacy setting protocol command is set by the client according to a user
  • the privacy setting option sends a protocol command to the server, and the privacy setting option includes whether to display the user group created or joined by the user to other users.
  • the second obtaining unit 1513 is configured to obtain the data content corresponding to the privacy setting according to the user ID received by the third receiving unit 1512.
  • the setting unit 1514 is configured to: in the data acquired by the second obtaining unit 1513, the row privacy setting according to the privacy setting protocol.
  • the server further includes: a fourth receiving unit 1515, a third obtaining unit 1516, a fourth obtaining unit 1517, and a third sending unit 1518.
  • the fourth receiving unit 1515 is configured to receive a protocol command sent by the client to obtain other user profiles, where the protocol command for acquiring other user profiles includes user IDs of other users; wherein, the acquiring other user profiles
  • a protocol command is a protocol command sent to the server when the user queries the profile of a user other than himself.
  • the third obtaining unit 516 is configured to obtain the privacy setting item corresponding to the user and the basic data of the user according to the user ID received by the fourth receiving unit 1515.
  • the fourth obtaining unit 1517 is configured to obtain, when the privacy setting item is a user group that is created or joined by the user, to obtain a user group ID list created or added by the user.
  • the third sending unit 1518 is configured to send the basic data of the user acquired by the third obtaining unit 1516 and the user group ED created or added by the user acquired by the fourth acquiring unit Give the account to the client.
  • the third sending unit 1518 is further configured to: when the privacy setting item is not displaying the user group created or added by the user to other users, the basic information of the user acquired by the third obtaining unit 15 The data is sent to the client.
  • a client includes: a first obtaining unit 221 and a first sending unit 222.
  • the first obtaining unit 221 is configured to acquire a recommended user that is recommended to join the predetermined user group, where the first obtaining unit 221 obtains the recommended user ID recommended for joining the predetermined user group, and may receive the user input.
  • the recommended user ID is obtained by the user, and may be obtained by the user, which is selected by the user group, but is not limited by the embodiment of the present invention.
  • the first sending unit 222 is configured to send, to the server, a recommended join protocol command for the recommended user to join the predetermined user group, where the recommended join protocol command includes the recommended user ID and the predetermined user group.
  • the client further includes: a second sending unit 223, a first receiving unit 224, a second obtaining unit 225, and a display unit 226.
  • the second sending unit 223 is configured to send, to the server, an acquiring ID list protocol command, where the acquiring the ID list protocol command is used to obtain a protocol command of the user group ID list created or added by the user, where the acquiring the list protocol command Include the user ⁇
  • the first receiving unit 224 is configured to receive a list of user group IDs created or joined by the user returned by the server.
  • the second obtaining unit 225 is configured to obtain basic material information of each user group in the user group ID list according to the user group ID list received by the first receiving unit 224,
  • the display unit 226 is configured to display the basic material information of the respective user groups acquired by the second obtaining unit 225.
  • the client further includes: a third obtaining unit 227 and a third sending unit 228.
  • the third obtaining unit 227 is configured to obtain, after the displaying unit 226 displays the basic material information of each user group, a privacy setting option set by the user, where the privacy setting option includes whether to display the user creation or Joined user groups.
  • the third sending unit 228 is configured to send a privacy setting protocol command to the server according to the privacy setting option acquired by the third obtaining unit 227, where the privacy setting protocol command includes the user ⁇
  • the client further includes: a fourth sending unit 229, a second receiving unit 2210, a first operating unit 22U, a first creating display unit 2212, and a second creating display unit 2213.
  • the fourth sending unit 229 is configured to: when the user queries the personal data of the user other than the user, send a protocol command to obtain the other user's personal data to the server, where the command for obtaining the other user's personal information includes The user ⁇
  • the second receiving unit 22 "0" is configured to receive the basic data of the user returned by the server, or return the basic data of the user and the user group I list created or added by the user to the client.
  • the first operating unit 2211 is configured to: when the receiving unit 89 receives the basic information of the user and the user group created or joined by the user, the list is returned to the client, according to the user group B0 list query Obtaining basic data of each user group in the user group ID list
  • a first creation display unit 2212 configured to create a first personal resource of the user according to basic information of the user and basic material information of each user group acquired by the first operation unit 2211 Material interface, and display the first profile interface.
  • a second creation unit 2213 configured to create a second profile interface of the user according to the basic data of the user when the receiving unit 2210 receives the basic information of the user, and Two personal data interface display.
  • the embodiment of the present invention further provides a system for managing members of a user group. As shown in FIG. 26, the system includes: a client 261 and a server 262.
  • the client 261 is configured to obtain a recommended user ID that is recommended to join the predetermined user group, and send a recommended join protocol command to the server 262 to join the recommended user group, where the recommended join protocol command is recommended.
  • the server 262 is configured to receive, by the client 261, a recommended join protocol command that the recommended user joins the predetermined user group, where the recommended join protocol command includes the recommended user ID and the predetermined user group ID; according to the predetermined user group
  • the group ID determines a created user of the predetermined user group, and sends a recommendation join notification message to the created user, so that the create user determines whether to join the recommended user to the predetermined user group;
  • the recommended user ID is added to the member list of the predetermined user group.
  • the client acquires the recommended user ID recommended to join the predetermined user group, and sends the recommended user to the server.
  • a recommended join protocol command to be added to a predetermined user group; after receiving the recommended join protocol command, the server determines a created user of the predetermined user group according to a predetermined user group ID included in the recommended join protocol command, And sending a recommendation join notification message to the created user, and adding the recommended user to the office when receiving the consent sent by the create user
  • the response message in the predetermined user group is described, the recommended user is added to the member list of the predetermined user group, thereby realizing that other users recommend other users to a certain group, which facilitates the user group.
  • the extension of the group is created. Further, when the user recommends the joining user to the predetermined user group, multiple users can be recommended to join at one time, which avoids sending the recommendation joining protocol command to the server multiple times when joining one by one, which saves resources and is greatly convenient.
  • the extension of the user group is created.
  • the created user of the predetermined user group is the recommended user
  • the recommended user is added to the member list of the predetermined user group, thereby saving the predetermined user.
  • the confirmation of the creation of the group user speeds up the process of joining the recommended users.
  • the embodiment of the present invention may further send, to the recommended user, a notification message that the recommended user has been included in the predetermined user group.
  • the user is recommended to know the status of the recommended user to join; and the recommended user may also send a notification message that has been recommended to the predetermined user group, so that the recommended user knows the user group that he or she joins. Improve the user experience.
  • the user group created or added by the user may be displayed to the user in the user profile, so that the user can view which user group is included in the user profile, thereby improving the user experience.
  • the user after displaying the information of the user group created or added by the user to the user, the user can set whether the user group list can be viewed by other users through the privacy setting operation interface, and can satisfy the user's privacy. Protection;
  • the user is set to display the user group created or joined by the user in the profile or the user group created or joined by the user in the guest page, other user customers can conveniently view the user related to the user. Groups, greatly facilitate user extensions to create user groups.
  • the method, the device, and the user group in the system for managing user group members in the embodiment of the present invention may be a list of microblogs in the microblog, or may be a group in other IM software tools, which is an embodiment of the present invention. There is no limit to this.
  • Weibo Lis provides a small circle of focus, communication and communication platform for Weibo users with the same hobbies or the same label.
  • the microblog user in the microblog list can be engaged in a session.
  • Existing Weibo system only when users join After the Weibo List, the group ⁇ can be performed, and the one-to-many function of the users outside the Weibo List can not be realized, which reduces the user experience and reduces the product competitiveness.
  • the embodiment of the present invention further provides a method for publishing a microblog message, a microblog terminal, and a microblog server end.
  • the microblog terminal includes:
  • the microblog message management module 2701 is configured to manage the microblog message. When the user issues the microblog message, the microblog message to be published by the user is obtained, and the microblog message is transmitted to the microblog server.
  • the user uses the registered user account and the password to log in to the microblog server through the IM client of the microblog terminal to perform verification.
  • the microblog terminal establishes a connection channel with the microblog server.
  • the microblog terminal accesses the microblog server through the access server, and the microblog terminal ensures the connection with the microblog server by periodically sending a heartbeat packet to the microblog server.
  • the microblog terminal may display a user's microblog homepage, a popular broadcast, a broadcast hall or a broadcast message interface such as a city broadcast, a user's specific message interface (eg: @message interface), a group message interface, and a private message interface.
  • the Weibo message management module 2701 is used to manage the user's Weibo message.
  • the microblog message management module 2701 creates a broadcast window for the user in response to the mouse operation of the user; when the user inputs a microblog message in the broadcast window, The microblog message management module 2701 monitors the input button information of the user in real time, and when the mouse click release button of the user is monitored, the microblog message management module 2701 acquires the broadcast window according to the monitored input button information.
  • the microblog message to be published is sent to the microblog server. It can be understood that the microblog message management module 2701 performs a series of processing, such as encapsulation and encryption, on the obtained microblog message based on the broadcast publishing protocol, and then sends the microblog message to the microblog server.
  • the specific message queue is a queue for storing a microblog message including a specific location and the specific location includes the number information according to the embodiment of the present invention.
  • the specific message queue is a @ message queue.
  • @ ⁇ message in the message queue is: the microblog message of the package number information, Also known as: "@ ⁇ ", "about my message” or "refer to my message.”
  • the specific message queues described in the subsequent embodiments of the present invention refer to the @Message Queue.
  • the microblog message management module 270 ⁇ is further configured to: when the local user replies or rebroadcasts the microblog message in the @ message queue as a member of the microblog group, obtains the content replied by the user or rebroadcast Content: encapsulating the microblog group account information and the replied content or the retransmitted content, generating a reply message or a rebroadcast message, and transmitting the message to the microblog server.
  • the specific message interface management module 2702 is configured to receive a microblog message in the specific message queue of the user sent by the microblog server, and display a microblog message in the specific message queue of the user on a specific message interface. .
  • the specific message interface management module 2702 is preferably an @page management module of the microblog terminal, configured to manage a user's @message interface, which can receive or pull the push of the microblog server.
  • the microblog message in the @ message queue of the user displays all the microblog messages in the @ message queue of the user through the @ message interface.
  • the embodiment of the invention can realize one-to-many conversations of users outside the microblog group to each member of the microblog group, facilitate the information transmission of the microblog user, and improve the user's ⁇ experience.
  • the microblog terminal includes: a microblog message management module 2701 and a specific message interface management module 2702.
  • the microblog terminal further includes:
  • the microblog group management (2) is configured to manage the microblog group, receive the microblog message in the broadcast queue of the microblog group sent by the microblog server, and display the message in the group message page. A microblog message in the broadcast queue of the microblog group.
  • the microblog list management module 2703 mainly manages the creation of the microblog list, the basic information of the microblog list, and the message interface of the microblog list.
  • the microblog list management module 2703 receives or pulls the microblog message in the broadcast queue of the microblog list pushed by the microblog server, and displays the broadcast queue of the microblog group in the group message page. Weibo news in the middle.
  • the microblog message reminding module 2704 is configured to provide the user with a microblog message in the @ message queue of the user, and/or a display reminder and view of the microblog message in the broadcast queue of the microblog group. Linking, and when the user enters the viewing link, the notification specific message interface management module 2702 and/or the microblog group management module 2703 displays the corresponding microblog message.
  • the microblog message reminding module 2704 is mainly to remind the user to view when a new microblog message is published, for example: when there is a reply message about the user, the reply is A link to the information is provided to the user and the user is prompted to view it.
  • the microblog message reminder 2704 provides the user with a microblog message in the @ message queue of the user, and/or a display reminder of the microblog message in the broadcast queue of the microblog group. And viewing the link, and when the user operates the view link (eg, clicking the view link), notifying the specific message interface management module 2702 and/or the microblog group management module 2703 at the @message interface and / or the corresponding microblog message is displayed in the group message interface flick
  • FIG. 29 it is a schematic structural diagram of a first embodiment of a microblog server according to the present invention.
  • the microblog server side includes:
  • the microblog group server 2901 is configured to store and manage basic information of the microblog group.
  • the basic information of the spoofing group includes but is not limited to: group nickname information, member account information list, group type, and group label attribute.
  • the microblog group server 2701 interacts with the microblog list management 2703 of the microblog terminal, and provides the microblog list management module 2703 with creation management, basic information, and group message interface for the user's microblog group.
  • the various services managed are the same as the existing technologies, and will not be described here.
  • the microblog message server 2902 is configured to detect whether the specific location of the microblog message sent by the first microblog terminal includes the microblog group nickname information, and if the detection flag is yes, add the microblog message to the micro In a specific message queue for each member of the blog group.
  • the specific location of the microblog message is the location of the preset regular expression convention.
  • the microblog server and the microblog terminal pre-arrange the regular expression of the microblog message in the embodiment, such as: number information + space + message content, and the specific position of the regular expression is: the position before the message content.
  • the microblog message server 2902 After receiving the microblog message sent by the microblog terminal, the microblog message server 2902 first checks whether the microblog message is complete, that is, checks whether the microblog message has a complete message structure (message header and message body, etc.), if it is determined The Weibo message is incomplete, confirming the Weibo If the information is invalid, the microblog message server 2902 discards the microblog message; if it is determined that the microblog message is complete, it is confirmed that the microblog message is valid, and the microblog message server 29CC presets a regular expression based on the principle of regular matching.
  • the microblog message server 29CC presets a regular expression based on the principle of regular matching.
  • the microblog message server 2902 processes the microblog message according to a normal broadcast message, and the process is related to the existing microblog message.
  • the broadcasting process is the same and will not be described here.
  • the microblog message server 2902 determines the part before the message content of the microblog message as the specific location of the microblog message, and from the The specific information of the microblog message extracts the account information (the content between the "@” and the "space"), and detects whether the account information is the microblog group account information from the microblog group server 2901, and if the detection result is The microblog message server 2902 adds the microblog message to the @ message queue of each member in the microblog group. It can be understood that the above regular expression is only an example. The role of "@" and "space” in the expression is to distinguish the account information from the message content.
  • the regular expression can be determined according to actual needs. , such as: letter + nickname information + space + message content, or: message content + letter + account information + space, or: message content + @ number information + empty ⁇ message content, etc., in other cases can be similar Analysis, not to repeat here.
  • the microblog message server 2902 is further configured to receive the microblog terminal corresponding to the member when the member in the spoofing group replies or retransmits the microblog message advertised by the first user in the @ message queue of the member. Sending a reply message or a conversion message, adding the reply message or the rebroadcast message to the broadcast queue of the microblog group according to the microblog group account information in the reply message or the relay message, and notifying the microblog
  • the blog message pushing server 2903 pushes the microblog message in the broadcast queue of the microblog group to the first microblog terminal for publishing. In an actual application, the microblog message pushing server 2903 groups the microblog group.
  • the microblogging terminal corresponding to all the users who listen to the microblog group is also pushed, so that the other listens to the All users of the microblog group can also view the microblog messages in the broadcast queue of the microblog group.
  • the microblog message pushing server 2903 is configured to scan the microblog message server 2902 to add a specific message queue of each member in the processed microblog group, and set the special message of each member in the microblog group.
  • the microblog message in the message queue is pushed to the microblog terminal corresponding to each member in the microblog group for publishing.
  • the microblog message pushing server 2903 is mainly used to transfer various advertised messages or related data packets that each user forwards to other users or microblog groups through the microblogging terminal, which can scan each user in real time or periodically.
  • the message queue when a new microblog message is found in the message queue, pushes the microblog message in the message queue to each user.
  • the microblog message pushing server 2903 pushes the microblog message in the @ message queue to each microblog device corresponding to each member in the microblog group, and the microblog group
  • the microblog terminal corresponding to each member in the microblog group provides a display reminder and a view link of the microblog message in the @ message queue to each member in the microblog group; when each member in the microblog group views the view When the link is operated, the microblog terminal corresponding to each member in the microblog group displays the microblog message in the @ message queue of each member in the microblog group on the @ message interface.
  • the microblog server end and the microblog terminal of the embodiment of the present invention can implement a one-to-many relationship between the users outside the microblog list and each member in the microblog list, and can implement multiple members in the microblog Lis to a single user outside the microblog list. For a session, the user experience is improved and the product competitiveness is improved.
  • the microblog server includes: a microblog group server 2901, a microblog message server 2902, and a micro The blog message push server 2903.
  • the microblog server further includes:
  • the microblog user server 2904 is used to store and manage basic information of the microblog user.
  • the basic information of the microblog user includes but is not limited to: user nickname information, user type, user tag attribute, and authentication information.
  • the microblog group server 2901 detects that the nickname information included in the specific location of the microblog information is not the microblog group account information
  • the microblog user server 2904 further queries the microblog user server 2904. Whether the nickname information is the account information of a single user, if the query is YES, the microblog message server 2902 adds the microblog message to the @ message queue of the user according to the queried user account information, and Notifying the microblog message push server 2903 to push the microblog message in the user's @ message queue to the user's microblog end
  • the terminal performs the publishing, and the microblog terminal of the queried user displays the microblog message in the @ message queue of the user in the @ message interface. It should be noted that the process of sending a microblog message to a single microblog user is similar to the existing process of sending a private message to a single microblog user.
  • the microblog group server 2901 determines that the account information in the levy message is neither the microblog group account information nor the account information of the single user, it indicates that the specific location of the microblog message does not include The microblog group account information does not include the account information of a single user, and the multicast message is processed by the broadcast message. The process is the same as the broadcast process of the existing microblog message, and details are not described herein.
  • microblog message server 2902 of the microblog server side of the present invention will be described in detail below.
  • the microblog message server 2902 includes:
  • the parsing unit 2921 is configured to parse the microblog message sent by the microblog terminal according to the regular matching principle, and determine a specific location of the microblog message that matches the location of the preset regular expression contract.
  • the microblog server and the microblog terminal pre-arrange the regular expression of the microblog message in the embodiment, for example: @+account information+ ⁇ +message content, the specific position of the regular expression is : The location before the message content.
  • the parsing unit 2921 After receiving the microblog message sent by the microblog terminal, the parsing unit 2921 first checks whether the microblog message is complete, that is, whether the microblog message has a complete message structure (message header and message body, etc.), if it is determined If the microblog message is incomplete, it is confirmed that the microblog message is invalid, and the parsing unit 2921 discards the microblog message; if the microblog message is determined to be complete, and the microblog message is confirmed to be valid, the parsing unit 2921 is configured according to the The regular expression matches the microblog message based on the regular matching principle. If the format of the microblog message does not satisfy the regular expression, the matching fails, and the parsing unit 2921 processes the microblog message according to a normal broadcast message.
  • the broadcast process is the same as the existing broadcast message, and will not be described here. If the format of the microblog message satisfies the above regular expression, the matching is successful, and the parsing unit 2921 determines the part before the message content of the microblog message as the specific position of the microblog message.
  • the parsing unit 2921 needs to perform decapsulation, decryption, and the like on the received microblog message correspondingly before parsing.
  • the process is the same as the prior art. , I won't go into details here.
  • the detecting unit 2922 is configured to detect, according to the specific location of the microblog message determined by the parsing unit 2921, whether the specific location of the microblog message includes microblog group account information.
  • the detecting unit 2922 extracts account information (content between "@" and "space") from a specific location of the spoof message according to the specific location of the microblog message determined by the parsing unit 292 )) And detecting, by the microblog group server 2901, whether the account information is microblog group account information.
  • the first operation unit 2923 is configured to: when the detection unit 2922 determines that the result is YES, query the microblog group server to query the member account information list of the microblog group, and select the member account information list. And adding the microblog message to a specific message queue (@ message queue) of each member in the microblog group.
  • the determining unit 2924 is configured to determine, when the detection result of the detecting unit 2922 is negative, whether the specific location of the microblog message includes the second user nickname information.
  • the determining unit 2924 further queries the microblog user server 2904 whether the nickname information is account information of a single user.
  • the second operation unit 2925 is configured to add the microblog message to the specific message queue of the second user (@ message queue) according to the second user account information when the determining unit 2924 determines that the result is yes. And informing the microblog message pushing server to push the microblog message in the specific message queue of the second user to the second microblog terminal corresponding to the second user for publishing. It can be understood that if the judgment result of the judging unit 2924 is no, it indicates that the specific location of the microblog message does not include the microblog group nickname information, and the account information of the single user is not included.
  • the broadcast message processes the microblog message, and the process is the same as the broadcast process of the existing microblog message, and details are not described herein.
  • the first user is used for any microblog in the microblog system.
  • the second user is any Weibo user other than the first user.
  • the embodiment of the invention can implement a one-to-many relationship between the users outside the microblog list and each member in the microblog list, and can implement a multi-to-one session of each member in the microblog list to a single user outside the microblog list, thereby improving the use of the user.
  • a multi-to-one session of each member in the microblog list to a single user outside the microblog list, thereby improving the use of the user.
  • enhance product competitiveness enhance product competitiveness.
  • FIG. 32 it is a flowchart of a first embodiment of a method for publishing a microblog message according to the present invention. the method includes:
  • the first microblog terminal corresponding to the first user acquires the microblog message to be advertised by the first user, and transmits the microblog message to the microblog server.
  • the user uses the registered user's account and password to log in to the microblog server through the IM client of the microblog terminal to verify, and after the verification succeeds, the microblog terminal establishes a connection channel with the microblog server.
  • the microblog terminal accesses the microblog server through the access server, and the microblog terminal ensures the connection with the microblog server by periodically sending a heartbeat packet to the microblog server.
  • the microblog terminal may display a broadcast message interface of the user's microblog homepage, a hot broadcast, a broadcast hall or a city broadcast, a user's @ message interface, a group message interface, and a private message interface, etc., the microblog terminal to the user Weibo messages are managed.
  • the microblogging terminal monitors the mouse operation of the user in real time, and when the mouse clicks the broadcast button of the user, the microblog terminal responds to the mouse operation of the user, executes the S3201, and creates a broadcast window for the user.
  • the S3201 monitors the input button information of the user in real time, and when the user clicks the release button of the user, the S3201 inputs according to the monitoring ⁇ : The information is obtained, and the microblog message to be published in the broadcast window is obtained, and the microblog message is transmitted to the microblog server.
  • the microblogging terminal performs a series of processing, such as encapsulation and encryption, on the obtained microblog message according to a broadcast publishing protocol, and then sends the microblog message to the microblog server, in this embodiment.
  • the process and the sending process of the microblog message in the S3201 are similar to the prior art, and are not described here.
  • the microblog server detects whether the specific location of the microblog message includes the microblog group account information. If the detection result is yes, the microblog server adds the microblog message to the microblog.
  • a specific message queue (@Message Queue) for each member of the group.
  • the microblog server and the microblog terminal pre-arrange the regular expression of the microblog message described in this embodiment, for example: ⁇ ⁇ information + space + message content, the specific position of the regular expression is: The location before the message content.
  • the microblog server After receiving the microblog message sent by the microblog terminal, the microblog server first checks whether the microblog message is complete, that is, checks whether the microblog message has a complete message structure (message header and message body, etc.), if it is determined If the microblog message is incomplete, it is confirmed that the microblog message is invalid, and the server end discards the microblog message; if it is determined that the microblog message is complete, it is confirmed that the microblog message is valid, and the server end executes S3202, according to the pre a regular expression is set, and the microblog message is matched according to a regular matching principle.
  • the server processes the microblog message according to a normal broadcast message. This process is the same as the broadcast process of the existing microblog message, and will not be described here. If the format of the microblog message satisfies the regular expression, the matching is successful, and the S3202 determines the part before the message content of the microblog message as the specific location of the microblog message, and from the specific location of the microblog message. Extracting the account information (the content between the "@" and the "space"), detecting whether the nickname information is the microblog group account information, and if the detection result is yes, the S3202 adds the microblog message to the In the @Message Queue of each member of the Weibo group.
  • the microblog server sends the microblog message in the specific message queue of each member of the microblog group to the microblog terminal corresponding to each member in the microblog group for publishing.
  • the member in the microblog group corresponds to each member in the microblog group.
  • the microblog terminal provides the display reminder and the view link of the microblog message in the @ message queue to each member of the microblog group; when each member of the microblog group operates the view link, The microblog terminal corresponding to each member in the microblog group displays the microblog message in the @ message queue of each member in the microblog group on the @ message interface.
  • the embodiment of the invention can realize the one-to-many ⁇ of the members of the microblog list to facilitate the microblog user to transmit information, improve the user experience, and improve the product competitiveness.
  • FIG. 33 it is a flowchart of a second embodiment of a method for publishing a microblog message according to the present invention. the method includes:
  • the first microblog terminal corresponding to the first user acquires the microblog message to be posted by the first user, and transmits the microblog message to the microblog server. .
  • the S3301 is the same as the step S3201 in the previous embodiment, and details are not described herein.
  • the microblog server parses the microblog message according to a regular matching principle, and determines a specific location of the microblog message that matches a location agreed by the preset regular expression.
  • the microblog server and the microblog terminal pre-arrange the regular expression of the microblog message in the embodiment, for example: @+ account information + space + message content, and the specific position of the regular expression is: The location before the message content.
  • the microblog server After receiving the microblog message sent by the microblog terminal, the microblog server first checks whether the microblog message is complete, that is, checks whether the microblog message has a complete message structure (message header and message body, etc.), if it is determined If the microblog message is incomplete, the microblog message is invalid, and the microblog server discards the microblog message; if it is determined that the microblog message is complete, the microblog message is confirmed to be valid, and the server executes S3302.
  • the microblog message is matched according to the regular matching principle. If the format of the microblog message does not satisfy the regular expression, the matching fails, and the S3302 processes the microblog message according to a normal broadcast message. The process is the same as the broadcast process of the existing microblog message, and will not be described here. If the format of the microblog message satisfies the regular expression, the matching is successful, and the S3302 determines the part before the message content of the microblog message as the specific location of the microblog message.
  • S3303 The microblog server detects whether the specific location of the microblog message includes the microblog group account information, and if the detection result is yes, proceeds to S3304; otherwise, proceeds to S3309.
  • the specific location of the microblog message determined by S3303 in S3303 Extracting the account information (the content between "@” and "space") from the specific location of the microblog message, and detecting whether the account information is the microblog group account information from the microblog group server on the microblog server side .
  • the microblog server sends a member account information list of the microblog group according to the microblog group account information.
  • the ii server adds the microblog message to the @ message queue of each member in the microblog group according to the member account information list.
  • the microblog server scans the @ message queue of each member in the microblog group, and pushes the microblog message in the @ message queue of each member of the microblog group to the microblog group.
  • the microblog terminal corresponding to each member.
  • the microblog terminal corresponding to each member in the microblog group provides a display reminder and a view link of the microblog message in the @ message queue to each member in the microblog group.
  • the microblog terminal corresponding to each member in the microblog group displays the members in the microblog group on the @ message interface.
  • S3306 ⁇ S3308 is a specific refinement step of S3203 of the previous embodiment.
  • the microblog server determines whether the specific location of the microblog message includes the second user account information. If the determination result is yes, the process proceeds to S3310; otherwise, the process ends.
  • the microblog server performs S3309, and further queries, from the microblog user server of the microblog server, whether the account information is account information of a single user.
  • the microblog server adds the microblog message to the @ message queue of the second user according to the second user account information.
  • the microblog server scans the @ message queue of the second user, and pushes the microblog message in the @ message queue of the second user to the second microblog terminal corresponding to the second user.
  • the second microblog terminal displays a microblog message in the @ message queue of the second user on the @ message interface; and then the transfer ends.
  • the first user is any Weibo user in the Weibo system
  • the second user is any Weibo user except the first user. It can be understood that if the judgment result of the S3309 is no, it indicates that the specific location of the microblog message does not include the microblog group account information, and the account information of the single user is not included, and the normal broadcast message is processed.
  • the microblog message is the same as the broadcast process of the existing microblog message, and is not described here.
  • S3302-S3305 and S3309-S3312 are specific refinement steps of S3202 in the previous embodiment.
  • the embodiment of the present invention can implement a one-to-many relationship between the users outside the microblog list and the members in the microblog list, and can realize the use of multiple users in the microblog list for a single user outside the microblog list.
  • FIG. 34 it is a flowchart S of a third embodiment of a method for publishing a microblog message according to the present invention.
  • the method includes:
  • the first microblog terminal corresponding to the first user acquires the microblog message to be posted by the first user, and transmits the microblog message to the microblog server.
  • the microblog server detects whether the specific location of the microblog message includes the microblog group account information. If the detection result is yes, the microblog server adds the microblog message to the microblog group. In the @Message Queue of each member.
  • the microblog server sends the microblog message in the @ message queue of each member of the microblog group to the microblog terminal corresponding to each member in the microblog group for publishing.
  • S3401-S3403 is the same as the S320i ⁇ S3203 in the embodiment shown in FIG. 32, and details are not described herein.
  • the microblog terminal corresponding to the member obtains the reply content or the broadcasted content.
  • the microblog terminal corresponding to the member encapsulates the microblog group account information, the replied content, or the retransmitted content, generates a reply message or a rebroadcast message, and transmits the message to the microblog service. Server side.
  • the S3405 is similar to the process of replying or retransmitting the existing microblog message, first extracting the account information of the reply or rebroadcast message source, and then acquiring the content replied by the user or the content of the rebroadcast, and extracting the extracted nickname
  • the information is encapsulated with the content of the reply or the content of the rebroadcast to generate a final reply message or a broadcast message.
  • the microblog server adds the reply message or the rebroadcast message to the broadcast queue of the microblog group according to the microblog group account information in the reply message or the rebroadcast message.
  • the microblog server scans the broadcast queue of the microblog group, and pushes the microblog message in the broadcast queue of the microblog group to the first microblog terminal.
  • the microblog server performs the S3407, and pushes the microblog terminal corresponding to all users of the microblog group, so that all users who listen to the microblog group can View the microblog messages in the broadcast queue of the microblog group.
  • the first microblog terminal displays a microblog message in a broadcast queue of the microblog group in a group message page.
  • the members in the microblog group reply or retransmit the message in the form of a microblog group message, and realize the multi-to-one broadcast propagation of the microblog group to a single microblog user.
  • the embodiment of the invention can realize a one-to-many comparison between the users outside the microblog list and the members in the microblog list, and can realize the multiple pairs of ones in the microblog list to a single user outside the microblog list, thereby improving User experience, improve product competitiveness.
  • the user of the embodiment of the present invention may input the microblog group account information in the microblog message to be advertised, and the microblog server detects the microblog message to be advertised, when the microblog is detected.
  • the specific location of the blog message includes the microblog group nickname information
  • the microblog message is added to a specific message queue (for example: @Message Queue) of each member in the microblog group, and the The microblog message in the specific message queue of each member of the microblog group is pushed to the microblog terminal corresponding to each member in the microblog group for publishing, and a single microblog user (user in the microblog group or The user outside the microblog group) has a one-to-many ⁇ for each member of the group, which improves the user's Using the experience, the product competitiveness is improved; in addition, each member in the microblog group can reply or retransmit the microblog message in the received specific message queue, and the microblog terminal corresponding to each member to the microblog group
  • the account information is encapsul
  • the group function in the existing IM software is implemented by the following steps: The user obtains the user group information that needs to be joined, and sends a join request to the server through the client, where the join request includes the user ID. And the user group information needs to be added; the server receives the join request, and sends a join request notification to the administrator of the user group according to the user group information, and the user can join the user after the user group administrator agrees Group.
  • the group function in the IM software belongs to a closed user aggregate. Users can only apply for the user group they want to join after they know the user group information they want to join, and other users cannot give a group. The group recommends other users.
  • the embodiment of the present invention further provides a microblog integration method, a microblog terminal, a microblog list, a microblogging, and a system.
  • microblog integration method may include:
  • Step 350 The microblog terminal queries the microblogging message according to the topic content, and obtains the topic identifier of the topic;
  • Step 351 Send an establishment instruction that establishes an association relationship between the foregoing topic and the microblog list to which the microblog terminal belongs, to the microblog list server and/or the microblog topic server.
  • the content of the establishment instruction includes a topic identifier and a microblog list identifier.
  • the association relationship includes a mapping relationship and/or a listening relationship.
  • Step 352 The microblog list server searches for the data content corresponding to the microblog list identifier according to the microblog list identifier, and writes the topic identifier to the data content.
  • Step S353 The microblog topic server acquires the topic identifier of the topic, searches for the data content corresponding to the topic identifier, and writes the microblog list identifier to the data content to establish a listening relationship.
  • the microblog (system) in this embodiment may mainly include a microblog terminal and a microblog background server group; the microblog terminal mainly includes a microblog message management module, a microblog list (List) management module, and a microblog topic management module.
  • the microblog backend server group may include a microblogging server, a microblog list server, a microblog message server, and a microblog terminal server. The microblog terminal and the microblog backend server group can communicate through the server.
  • the microblog message management module can pull the message and parse the message content according to the identifier (ID) of the microblog message, and create a related message interface to display the message content; the microblog list management module can be used to create and delete the microblog list.
  • ID identifier
  • the microblog terminal server is mainly used for storing the basic information of the listening relationship, the basic data, the terminal type, the terminal tag attribute, and the authentication of the microblog terminal;
  • the microblog list server is mainly used for storing and managing the data associated with the microblog list. Content, and operation management for creating a microblog list, setting up microblog list data related signaling, etc.;
  • the microblog message server is mainly used for managing the mapping relationship between the microblog message index and the message body, so that the microblog terminal can use micro The Bo index is pulled to the corresponding message body;
  • the microblogging server is mainly used for managing the creation of topics on the terminal, the list of message identifiers corresponding to the topic, and the management of the mapping relationship between the topic identifier and the topic content.
  • the microblog terminal corresponding to the creator of the microblog list may send an instruction of querying a topic (such as a hot topic list) to the microblogging server, and the microblogging message may be based on the topic with which the current message is most associated.
  • the list is returned to the Weibo terminal.
  • the microblog terminal can set the listening relationship between the microblog list and the topic, and can select the corresponding topic to send the request to the microblogging server for listening, so that all the microblog terminals in the microblog list can listen to the topic. (Or, the microblog terminal directly sends a request to the microblog topic server to listen to the corresponding topic).
  • All the levy terminals can query the microblog topic server through the topic identifier, and obtain the protocol command of the microblog list identifier list corresponding to the topic,
  • the blog list identifier queries the microblog column, and the name of the microblog list corresponding to the topic and the information of the cartridge type are displayed.
  • the microblogging list and the topic listening relationship may be a microblogging terminal corresponding to the creator of the microblog list, and send a setting instruction for establishing a listening relationship between the topic and the microblog list to which the silver blog terminal belongs to the microblogging session.
  • the content of the foregoing establishment instruction includes a topic identifier and a microblog list identifier; the microblogging server searches for the data content corresponding to the topic identifier according to the topic identifier, and writes the microblog list identifier to The content of the data is used to establish a listening relationship.
  • the data content corresponding to the topic may include: a name, a description, a listening list of the topic, and the like.
  • the microblog terminal corresponding to the creator of the microblog list can also select the corresponding mapping relationship.
  • the microblog terminal queries the microblog topic server according to the topic content, and obtains the topic identifier of the topic; and then sends an establishment instruction that establishes the mapping relationship between the topic and the gambling list that the microblog terminal belongs to (creates) to the microblog list.
  • the f3 ⁇ 4 of the setup command includes at least a topic identifier and a microblog list identifier of the microblog list; and the microblog list server searches for the data content corresponding to the microblog list identifier according to the microblog list identifier, and the foregoing
  • the topic identifier is written to the found data content, thereby establishing a mapping relationship between the topic and the microblog list.
  • the number corresponding to the microblog list identifier may include: a name, a description, a label, a permission, a member, and an associated topic.
  • step S352 ⁇ may further include:
  • Step S3520 The microblog message server sends the microblog message sent by the microblog member of the microblog list to the message list of the topic having the radiant relationship with the microblog list.
  • the step S3520 specifically includes: the microblog message server obtains the microblog list identifier corresponding to the microblog member, and displays the topic identifier that has a mapping relationship with the microblog list identifier, and writes the microblog message to the message list of the topic identifier.
  • the microblog messages published by all the microblog terminals in the microblog list are automatically added to the message list corresponding to the topic, and the microblog is obtained in the microblog list server.
  • a list of topics having a narrow relationship with the data content corresponding to the list identifier is used.
  • the mapping relationship is operated by the microblog terminal, the data packet (microblog message) protocol is inserted into the corresponding mapping relationship list.
  • the microblog member (the microblog terminal) in the microblog list publishes the microblog message
  • the microblog message server obtains the microblog terminal that sends the microblog message
  • the query microblog list server obtains the corresponding microblog terminal.
  • the method further includes:
  • Step S3531 The microblog message server parses the received microblog message, obtains the topic content, and queries whether the same topic content is included;
  • Step Lin S3532 if present, the microblog message server sends an insert instruction to the microblog topic server, and inserts the topic content into the message list of the corresponding topic;
  • Step S3533 If not, the microblog topic server establishes a new topic according to the content of the topic.
  • the microblogging terminal can use the microblog message management module to create a related topic in the broadcast publishing window to publish the microblog message; the microblog message server can receive the microblog message published by the microblog terminal, and parse the content of the microblog message.
  • the topic regular (expression) rule the topic content in the microblog message is obtained, and the topic content query topic data table is used to confirm whether there is an exact matching topic content.
  • the spoofing message server sends an instruction to insert the message identifier to the topic message list to the microblogging server, and the microblogging server can confirm the topic identifier according to the topic content, and write the corresponding microblog message
  • the message is identified in the message (identification) list associated with the topic; if not, the microblog topic server generates a new topic identifier and inserts the corresponding topic content to create a new topic.
  • the above-mentioned microblogging terminal includes, but is not limited to, an IM (Instant Messaging) client, a webpage microblogging terminal, and a WAP (Wreless Ai3 ⁇ 4) Hcation Protocol, which is a wireless application.
  • IM Intelligent Messaging
  • WAP Wide Ai3 ⁇ 4 Hcation Protocol
  • the above IM client can provide related operations and interactive interfaces. After the IM client sends the microblog account and password corresponding to the IM client to the microblog terminal server to verify the login success, the connection channel with the microblog terminal server is established, and the form of the heartbeat packet is periodically sent and guaranteed. The connection of the microblog terminal server.
  • the IM client listens to the user's mouse click operation through the microblog message management module, creates a broadcast publishing window, and the user clicks the "insert topic” button to invoke the input control to insert the topic "#", the user can be in two # Enter the topic content (for example: #topic content#), and the user can also input other message content in other input fields.
  • the message content in the input box is extracted, combined into the data packet for encryption and sent to the microblog message server.
  • the microblog message server After receiving the content of the message, the microblog message server parses and confirms the valid data packet, generates a message index identifier corresponding to the content of the message, and sends a message identifier list corresponding to the user's published message, and simultaneously parses the message content. According to the regular rule of the topic (#), the matching analysis is performed to obtain the topic content, and the instruction for querying the topic is sent to the microblog topic server.
  • the microblog message server queries the topic data table according to the topic content through the microblog message server to confirm whether the topic content already exists. If it already exists, the microblog topic server inserts the topic content into the message list of the existing topic. If it does not exist, the microblog topic server creates a new topic based on the above topic content.
  • the microblog terminal corresponding to the creator of the microblog list sends an instruction to establish a listening relationship to the microblog topic server to listen to the topic.
  • the microblog terminal in the microblog list can display the name of the microblog list corresponding to the topic, and the information of the cartridge type.
  • the microblog terminal corresponding to the creator of the microblog list may also select a corresponding topic to establish a mapping relationship.
  • the mapping relationship is operated by using the microblog terminal in the microblog list
  • the data packet (microblog message) protocol is inserted into the corresponding mapping relationship list.
  • the microblog message sent by the microblog terminal of the microblog list is sent to the message list of the topic having a mapping relationship with the microblog list through the microblog message server.
  • the microblog list related to the topic can be viewed through the topic display manner of the microblog, so that the microblog list related to the topic can be found from the topic for listening or audition operation; meanwhile, the microblog The creator of the list can create a list of topics and microblogs
  • the mapping relationship is such that the microblog message published by the microblog list member (the microblog terminal) automatically enters the message list related to the topic; thus, the microblog terminal listening to the topic can view the corresponding microblog list member.
  • the published Weibo newsletter realized the integration between Weibo's topic and the Weibo list, enabling Weibo terminals to obtain more abundant resources and enhance the user experience.
  • the microblog terminal 380 can include:
  • the instruction sending module 383 is configured to send an establishment instruction for establishing an association relationship between the topic and the microblog list to which the microblog terminal 380 belongs to the microblog list server and/or the microblog topic server;
  • the request writing module 384 is configured to search, according to the microblog list identifier, the data content corresponding to the microblog list identifier by using the microblog server, and write the topic identifier to the data content to establish a mapping relationship; and / or,
  • the microblog terminal 380 corresponding to the creator of the microblog list may send an instruction for querying a topic (such as a hot topic list) to the microblogging server through the command sending module 383, and the microblog topic server may be associated with the current microblogging server.
  • the list of topics with the most messages is returned to the microblog terminal 380.
  • the microblog terminal 380 can set the listening relationship between the microblog list and the topic, and can select the corresponding topic to send the request to the microblogging server for listening, so that all the microblog terminals 380 in the microblog list can listen to the microblogging terminal 380.
  • the topic (or, the microblog terminal 380 directly sends a request to the microblogging device through the setup listening module 381 to listen to the corresponding topic).
  • All the microblogging terminals 380 can query the microblog topic server through the topic identifier, obtain the protocol command of the microblog list identifier list corresponding to the topic, and query the microblog list server through the microblog list identifier to display the corresponding topic.
  • the microblogging list and the topic listening relationship may be generated by the microblog terminal 380 corresponding to the creator of the microblog list, and the establishment instruction for establishing the listening relationship of the topic and the microblog list to which the microblog terminal 380 belongs is sent to the microblog topic.
  • the content of the establishing instruction includes a topic identifier and a microblog list identifier;
  • the microblogging server searches for data content corresponding to the topic identifier according to the topic identifier, and writes the microblog list identifier to the Data content, establish a listening relationship.
  • the data content corresponding to the topic may include: a name, a description, a listening list of the topic, and the like.
  • the microblog terminal 380 corresponding to the creator of the microblog list may also select a corresponding topic to establish a mapping relationship.
  • the microblog terminal 380 will query the microblogging server according to the topic content by obtaining the # ⁇ block 382, and obtain the topic identifier of the topic; then, the instruction sending module 383 is used to send and establish the above topic and the microblog terminal 380 belongs to (create)
  • the microblog list is configured to generate a command to the microblog server; the content of the setup command includes at least the topic identifier and the microblog list identifier of the microblog list; and further, the request is written by using the microblog list server.
  • the ingress module 384 searches for the data content corresponding to the microblog list identifier according to the microblog list identifier, and writes the topic identifier to the found data content, thereby establishing a mapping relationship between the topic and the microblog list.
  • the data content corresponding to the microblog list identifier may include: a name, a description, a label, a permission, a member, and an associated topic.
  • the microblog terminal 380 can view the microblog list related to the topic through the topic display manner of the microblog, so that the microblog list related to the topic can be found from the topic for listening or audition operation; meanwhile, the microblog The creator of the list can establish a microblogging message of the topic and the microblog list, so that the microblog message published by the microblog list member automatically enters the message list related to the topic; thus, the microblog terminal listening to the topic 380 can view the microblog messages published by the corresponding microblog list members, and realize the integration between the microblog topic and the microblog list, and the microblog terminal can obtain more abundant resources and improve the user experience.
  • the levy server 390 can include:
  • the list instruction receiving module 391 is configured to receive, by the microblog terminal 380, an establishment instruction for establishing a mapping relationship between the topic and the microblog list of the microblogging terminal 380; the content of the establishing instruction includes a topic identifier and a microblog list identifier;
  • the list search module 392 is configured to search for the data content corresponding to the microblog list identifier according to the microblog list identifier, and write the topic identifier to the data content.
  • the microblog terminal 380 queries the microblog topic server according to the topic content to obtain the topic identifier of the topic; and then sends an establishment instruction for establishing the mapping relationship between the topic and the microblog list to which the microblog terminal 380 belongs (created) to the microblog column.
  • the server 3 0; the content of the setup command at least the package identifier and the microblog list identifier of the microblog list, etc.; the microblog list server 390 receives the setup command through the list instruction receiving module 391, and reuses the list lookup module 392. According to the microblog list identifier, through the microblog column ⁇ !
  • the server 390 searches for the data content corresponding to the microblog list identifier, and writes the topic identifier to the found data content, thereby establishing a mapping relationship between the topic and the microblog list, and the microblog list identifier
  • Corresponding data content can include: name, description, label, permissions, members, and associated topics.
  • the microblogging server 4000 includes:
  • the topic command receiving module 4001 is configured to receive, by the microblog terminal 380, an establishment instruction for establishing a listening relationship between the topic and the microblog list to which the microblog terminal belongs; the content of the establishing instruction includes a topic identifier and a microblog list identifier;
  • the topic search module 4002 is configured to obtain a topic identifier of the topic, find a data content corresponding to the topic identifier, and write the microblog list identifier to the data content to establish a listening relationship.
  • the microblogging list and the topic listening relationship may be sent by the microblog terminal 380 corresponding to the creator of the microblog list, and the establishment instruction for establishing the listening relationship between the topic and the microblog list to which the microblog terminal belongs is sent to the microblogging message.
  • the data content corresponding to the topic may include: a name, a description, and a listening list of the topic, etc.
  • the microblogging system includes a microblog terminal 380, a microblog topic server 4000, and a microblog list server 3S), and the microblog terminal 380 Used for:
  • the microblogging engine 4000 is queried according to the content of the topic, and the topic identifier of the topic is obtained; and the establishing instruction for establishing the association relationship between the topic and the microblogging list to which the microblog terminal 380 belongs is sent to the microblog list server 390 and/or micro
  • the content of the above-mentioned establishment instruction includes a topic identifier and a microblog list identifier; the association relationship includes a mapping relationship and/or a listening relationship; the microblog server 390 is configured to:
  • the microblogging server 4000 is used to:
  • the microblog terminal 380 corresponding to the creator of the microblog list may send an instruction of querying a topic (such as a hot topic list) to the microblogging message, and the microblogging message 40 (K) may be based on the current The list of topics with the most associated messages is returned to the microblog terminal 380.
  • the microblog terminal 380 can set the listening relationship between the microblog list and the topic, and can select the corresponding topic sending request to the microblog topic server 4000 to listen, so that all the microblog terminals 380 in the microblog list can listen to the topic ( Alternatively, the microblog terminal 380 directly sends a request to the microblogging server 4 (1 ⁇ 20, listening to the corresponding topic).
  • All the microblog terminals 380 can query the microblog topic server 4000 through the topic identifier to obtain the corresponding topic.
  • the protocol command of the microblog list identification list by querying the microblog list server 390 through the microblog list identification, may display the name of the microblog list corresponding to the topic, the information of the mediation class, and the like.
  • the microblogging list and the topic listening relationship may be a microblogging terminal 380 corresponding to the creator of the microblogging list, and sending an establishment instruction to establish a listening relationship between the topic and the microblogging list to which the microblogging terminal 380 belongs to the microblogging message.
  • the server includes the topic identifier and the microblog list identifier.
  • the microblog topic server 4000 searches for the data content corresponding to the topic identifier according to the topic identifier, and writes the microblog list identifier. Enter the data content and establish a listening relationship.
  • the data content corresponding to the topic may include: a name, a description, a listening list of the topic, and the like.
  • the microblog terminal 380 corresponding to the creator of the microblog list may also select a corresponding topic to establish a mapping relationship. Department.
  • the Weibo terminal 380 will be the root! ⁇
  • the content query microblogging message 4000 obtain the topic identifier of the topic; Then, send the establishment instruction to establish the mapping relationship between the above topic and the microblog list to which the microblog terminal 380 belongs (created) to the microblog column
  • the content of the establishment instruction includes at least a topic identifier and a microblog list identifier of the microblog list, and the like; further, the microblog queue server 390 searches and identifies the microblog list identifier according to the microblog list identifier.
  • the data content corresponding to the microblog list identifier may include: a name, a description, a label, a permission, a member, and an associated topic, etc.
  • the microblog system further includes: a microblog message server 410, configured to send the microblog message sent by the microblog member in the microblog list to the message list of the topic having a mapping relationship with the microblog list.
  • a microblog message server 410 configured to send the microblog message sent by the microblog member in the microblog list to the message list of the topic having a mapping relationship with the microblog list.
  • the microblog message server 410 is specifically configured to: obtain a microblog list identifier corresponding to the microblog member, view a topic identifier that has a mapping relationship with the microblog list identifier, and write the microblog message to the message list of the topic identifier.
  • the microblog messages published by all the microblog terminals 380 in the microblog list are automatically added to the message list corresponding to the topic, and the microblog server 390 is used.
  • the topic list with the mapping relationship between the data content corresponding to the microblog list identifier is used.
  • the mapping relationship is operated by the microblog terminal 380, the data packet (microblog message) protocol is inserted into the corresponding mapping relationship list.
  • the microblog message server 410 obtains the microblog terminal 380 that sends the microblog message
  • the query microblog list server 390 obtains the corresponding message.
  • a list of the microblog list identifiers of the microblog terminal 380 and traversing the list of the loop microblog list identifiers to view a list of topic identifiers having a block relationship with the blog list; and then by traversing the list of the topic identifiers, writing the micro
  • the blog terminal 380 issues a message identifying the microblog message to the message identifier list corresponding to the topic.
  • the ⁇ &weibo terminal 380 when the ⁇ &weibo terminal 380 queries the message corresponding to the topic, it can query the message list of the microblog message published by the microblog terminal 380 in the microblog list that has been mapped to the topic, and establish The association relationship between the microblog message and the topic published by the microblog terminal 380 of the microblog list.
  • the microblog message server 410 is further configured to: parse the received microblog message, obtain the topic content, and query whether the same topic content exists through the microblog topic server 4000; when present, send the insert instruction to the microblog topic server 4000 , inserting the topic content into the message list of the corresponding topic;
  • the above microblogging message 40O is also used to: Create a new topic based on the above topic content when it does not exist.
  • the microblog terminal 380 can use the microblog message management module to create a related topic in the broadcast publishing window for publishing the microblog message; the microblog message server 410 can receive the microblog message published by the microblog terminal 380, and the microblog message is The content is parsed, and the topic content in the microblog message is obtained according to the topic regular (expression) rule, and the topic content query topic data table is used to confirm whether there is an exact matching topic content. If it already exists, the gambling message server 410 sends an instruction to insert the message identifier to the topic message list to the microblog topic service burial 4000, and the microblogging server 4000 can confirm the topic identifier according to the topic content, and write the microblog. The message corresponding to the message is identified in the message (identification) list associated with the topic; if ⁇ does not exist, the microblogging server 4000 generates a new topic identifier and interpolates the topic content to create a new topic.
  • the microblogging system can view the microblog list related to the topic through the topic display manner of the microblog, so that the microblog list related to the topic can be found from the topic for listening or audition operation; meanwhile, the microblog list is The creator can establish a mapping relationship between the topic and the Weibo list, so that the Weibo message published by the Weibo Lister will automatically be in the message list related to the topic; thus, the Weibo terminal listening to the topic 380 can view the microblog message published by the corresponding microblogging staff, realize the integration between the topic of the microblog and the microblog list, so that the microblog terminal 380 can obtain more abundant resources and improve the user experience.
  • -a- may be a personal computer, server, or network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Description

微博名单传播的实现方法、 终端及系统 本申请要求了 2011年 2月 21 日提交的、 申请号为 20in0042017X、发明 名称为 "微博名单传播的实现方法、 终端及系统", 以及 2011年 2月 23曰提 交的、 申请号为 2011100434897、 发明名称为 "管理用户群组成员的方法、 装 置及系统", 以及 2011年 3月 2日提交的、 申请号为 2011100501162、 发明名 称为 "微博消息的发布方法、 微博终端及微博服务器端", 以及 2011年 3月 24 日提交的、 申请号为 20in0072143X、 发明名称为 "微博整合方法、 微博 终端、 微博列表、 微博话 ¾J§ 务器及系统" 的中国申请的优先权, 其全部内 容通过引用结合在本申请中。 技术领域 本发明涉及网络通信技术领域, 尤其涉及一种微博名单传播的实现方法、 终端及系统。
背景技术
随着互联网应用的不断发展, 类似于 twitter (推特)的微博应用也不断发 展壮大; 这类通过微型博客进行信息发布方式可以非常快速地对信息进行传 播与传递。 现如今, 通过微博进行信息传递的方式不再局限于 IM ( Instant Messaging, 即时通讯)通信中所常用的一对一的好友单独聊天模式、 或者一 对多的群组消息聊天模式。 微博实际上实现了用户消息聊天模式从一对一、 一对多到一对无穷的一种跨越; 正是一对无穷的模式意味着一个人可以对无 穷多个人进行消息的传播, 同样一个人也可以同时收听万级以上的其他用户 所发布的微博信息, 因此这里对大用户量的应用提出了新的要求。
当某一用户所关注的用户数量较多时, 该用户可能会将他所关注的用户 按照不同的个人风格、 或者不同地域、 或者不同社交圈等进行分类并对应地 创建微博 List (微博名单)。 一个微博 List可以看作是微博用户针对某一类相 关微博用户群体所创建的聚合用户列表。 当然, 如果用户对某一类主题的微 博感兴趣, 也可以加入到其他用户创建的微博 List中以收听该微博 List中的 用户所发布的微博消息。
一般情况下, 微博用户都希望将自己创建的或者加入的微博 List与其他 微博用户进行分享; 但是在现有的微博系统中, 还没有一种能够快速地、 便 捷地将微博 List进行传播的方式。
发明内容
本发明的实施例提供一种微博名单传播的实现方法、 终端及系统, 用于 推进微博名单的快速传播。
为达到上述目的, 本发明的实施例采用如下技术方案:
一种微博名单传播的实现方法, 包括:
终端接收用户提供的微博名单分享指令;
根据待分享的微博名单的基本信息自动生成微博名单分享消息; 将所述微博名单分享消息进行发布。
一种微博终端, 包括:
接收单元, 用于接收用户提供的微博名单分享指令;
生成单元, 用于根据待分享的微博名单的基本信息自动生成微博名单分 享消息;
发布单元, 用于将所述微博名单分享消息进行发布。
一种微博名单传播系统, 包括: 微博终端和微博服务器; 其中, 所述微博终端, 用于接收用户提供的微博名单分享指令, 根据待分享的 微博名单的基本信息自动生成微博名单分享消息, 并将所述微博名单分享消 息通过所述微博服务器进行发布。
本发明实施例提供的微博名单传播的实现方法、 终端及系统, 在微博终 端接收到用户下达的微博名单分享指令后, 会自动生成包含有用户所参与的 微博名单即用户自己创建的或者加入的微博名单信息的微博名单分享消息, 并通过微博服务器对所述微博名单分享消息进行发布; 由于这一过程简化了 用户操作, 因此可以实现快速、 便捷地对微博名单进行传播; 此外, 所述微博服务器在接收到所述微博名单分享消息后会将其中携带 的网址信息转换成网络链接, 从而便于其他微博用户在看到所述用户发布的 微博名单分享消息后可以直接通过所述网络链接进入到所述用户想要分享的 微博名单中; 因此利用本发明实施例中的方案可以极大地推进微博名单的快 速传播。
本发明的实施例还提供一种管理用户群组成员的方法、 装置及系统, 实 现了用户给某个群组推荐其他用户, 极大的方便了用户群组的扩展创建。
为达到上述目的, 本发明的实施例采用如下技术方案:
一方面, 本发明的实施例提供一种管理用户群组成员的方法, 包括: 服务器接收客户端发送的推荐用户加入到预定用户群组的推荐加入协议 命令, 所述推荐加入协议命令中包含被推荐用户 ID和预定用户群纽 ID;
根据所述预定用户群组 ID确定所述预定用户群组的创建用户, 并向所述 创建用户发送推荐加入通知消息, 以便所迷创建用户确定是否将被推荐用户 加入到所述預定用户群组中;
当接收到所述创建用户发送的同意将所述推荐用户加入到所述预定用户 群组中的响应消息时,将所述被推荐用户 ID添加到所述預定用户群组的成员 列表中。
一方面, 本发明的实施例还提供一种管理用户群组成员的方法, 包括: 客户端获取向預定用户群组推荐加入的被推荐用户 ID;
向服务器发送推荐用户加入到预定用户群组的推荐加入协议命令, 所述 推荐加入协议命令中包含被推 用户 ID和预定用户群组 Π
另一方面, 本发明的实施例提供一种服务器, 包括:
第一接收单元, 用于接收客户端发送的推荐用户加入到预定用户群组的 推荐加入协 i义命令, 所述推荐加入协议命令中包含被推荐用户 ID和预定用户 群组 ID; 第一确定单元, 用于根据所述第一接收单元接收的所述预定用户群组 ID 确定所述预定用户群组的创建用户;
第一发送单元, 用于向所述第一确定单元确定的所述创建用户发送推荐 加入通知消息, 以便所迷创建用户确定是否将被推荐用户加入到所述预定用 户群组中;
第一操作单元, 用于当接收到所述创建用户发送的同意将所述推荐用户 加入到所述预定用户群组中的响应消息时, 将所述被推荐用户 ID添加到所述 预定用户群组的成员列表中。
另一方面, 本发明的实施例还提供一种客户端, 包括:
第一获取单元, 用于获取向预定用户群組推荐加入的被推荐用户 ID; 第一发送单元, 用于向服务器发送推荐用户加入到预定用户群组的推荐 加入协议命令, 所述推荐加入协议命令中包含被推荐用户 ID和预定用户群组
ΠΧ
再一方面, 本发明实施例提供一种管理用户群组成员的系统, 包括: 客户端, 用于获取向预定用户群组推荐加入的被推荐用户 ID; 向服务器 发送推荐用户加入到預定用户群组的推荐加入协 i义命令, 所述推荐加入协议 命令中包含被推荐用户 ID和预定用户群组 ID;
服务器, 用于接收客户端发送的推荐用户加入到预定用户群组的推荐加 入协议命令, 所述推荐加入协议命令中包含被推荐用户 ID和预定用户群组 ID; 根据所述预定用户群组 Π)确定所述预定用户群组的创建用户, 并向所述 创建用户发送推荐加入通知消息, 以便所述创建用户确定是否将被推荐用户 加入到所述预定用户群组中; 当接收到所述创建用户发送的同意将所述推荐 用户加入到所述预定用户群组中的响应消息时,将所述被推荐用户 ID添加到 所迷預定用户群组的成员列表中。
本发明实施例提供的管理用户群组成员的方法、 装置及系统, 当用户需 要将一个用户群组中的用户推荐加入到另一个用户群组中时, 获取向预定用 户群组推荐加入的被推荐用户 Π, 并向服务器发送推荐用户加入到预定用户 群组的推荐加入协议命令; 所述服务器接收到该推荐加入协议命令后, 根据 所述推荐加入协议命令中包含的预定用户群组 ID确定所述预定用户群組的创 建用户, 并向所述创建用户发送推荐加入通知消息, 当接收到所述创建用户 发送的同意将所述推荐用户加入到所述预定用户群组中的响应消息时, 将所 述被推荐用户 ID添加到所述预定用户群组的成员列表中,从而实现了用户给 某个群组推荐其他用户, 极大的方便了用户群组的扩展创建。
本发明实施例还提供一种微博消息的发布方法、 微博终端及微博服务器 端, 可实现微博 List外用户对微博 List内各成员的一对多会活, 提高用户的 使用体验, 提升产品竟争力》
为了解决上述技术问題, 本发明实施例提供了一种微博消息的发布方法, 包括:
当第一用户发布微博消息时, 所述第一用户对应的第一微博终端获取所 述第一用户待发布的微博消息, 并将所述微博消息传送至微博服务器端; 所述微博服务器端检测所述微博消息的特定位置是否包含微博群组怅号 信息, 若检测结杲为是, 所迷微博服务器端将所述微博消息添加至所述微博 群组中各成员的特定消息队列中;
所述微博服务器端将所述微博群组中各成员的特定消息队列中的微博消 息推送至所述微博群组中各成员对应的微博终端上进行发布。
其中, 所述微博消息的特定位置为预设的正则表达式约定的位置。
其中 , 所述微博服务器端检测所述微博消息的特定位置是否包含微博群 组帐号信息, 若检测结果为是, 所述微博服务器端将所述微博消息添加至所 述微博群组中各成员的特定消息队列中, 包括:
所述微博服务器端根据正则匹配原则解析所述微博消息, 确定与所述预 设的正则表达式约定的位置相匹配的所述微博消息的特定位置;
所述微博服务器端检测所述微博消息的特定位置是否包含微博群组帐号 信息;
若检测结果为是, 所述微博服务器端根据所述微博群组怅号信息, 查询 所述微博群组的成员帐号信息列表;
所述微博服务器端根据所述成员帐号信息列表, 将所述微博消息添加至 所述微博群组中各成员的特定消息队列中。
其中, 所述方法还包括:
当所述微博服务器端检测所述微博消息的特定位置是否包含微博群组帐 号信息的检测结果为否时 , 所述微博服务器端判断所述微博消息的特定位置 是否包含笫二用户帐号信息;
若判断结果为是, 所述微博服务器端根据所述第二用户怅号信息, 将所 述微博消息添加至所述第二用户的特定消息队列中;
所述微博服务器端扫描所述第二用户的特定消息队列, 将所述第二用户 的特定消息队列中的微博消息推送至所述第二用户对应的第二微博终端; 所述第二微博终端在特定消息界面上显示所述第二用户的特定消息队列 中的微博消息。
其中, 所述微博服务器端将所述微博群组中各成员的特定消息队列中的 微博消息推送至所迷微博群组中各成员对应的微博终端上进行发布, 包括: 所述微博服务器端扫描所述微博群组中各成员的特定消息队列, 将所述 微博群组中各成员的特定消息队列中的微博消息推送至所述微博群组中各成 员对应的微博终端;
所述微博群组中各成员对应的微博终端显示所述微博群组中各成员的特 定消息队列中的微博消息。
其中, 所述微博群组中各成员对应的微博终端显示所述微博群组中各成 员的特定消息队列中的微博消息, 包括:
所述微博群组中各成员对应的微博终端向所述微博群组中各成员提供所 述特定消息队列中的微博消息的展示提醒和查看链接; 当所述微博群組中各成员对所述查看链接进行操作时, 所述微博群组中 各成员对应的微博终端在特定消息界面上显示所述微博群组中各成员的特定 消息队列中的微博消息。
其中, 所述微博服务器端将所述微博群组中各成员的特定消息队列中的 微博消息推送至所述微博群组中各成员对应的微博终端上进行发布之后, 还 包括:
当所述微博群组中的成员回复或转播所述成员的特定消息队列中所述第 一用户发布的微博消息时, 所述成员对应的微博终端获取回复的内容或转播 的内容, 对所述微博群组帐号信息与所述回复的内容或转播的内容进行封装, 生成回复消息或转播消息并传送至所述微博服务器端;
所述微博服务器端根据所述回复消息或转播消息中的微博群组帐号信 息, 将所述回复消息或转播消息添加至所述微博群组的广播队列中;
所述微博服务器端扫描所述微博群组的广播队列, 将所述微博群组的广 播队列中的微博消息推送至所述第一微博终端;
所述第一微博终端在群组消息页面中显示所述微博群组的广播队列中的 微博消息。
相应地, 本发明实施例还提供了一种微博终端, 包括:
微博消息管理模块, 用于对微博消息进行管理, 当用户发布微博消息时, 获取所述用户待发布的微博消息, 并将所述微博消息传送至微博服务器端; 特定消息界面管理模块, 用于接收所迷微博服务器端发送的所述用户的 特定消息队列中的微博消息, 并在特定消息界面上显示所述用户的特定消息 队列中的微博消息。
其中, 所迷微博终端还包括:
微博群组管理模块, 用于对微博群组进行管理, 接收所述微博服务器端 发送的微博群組的广播队列中的微博消息, 并在群组消息页面中显示所述微 博群组的广播队列中的微博消息; 微博消息提醒模块, 用于向所述用户提供所述用户的特定消息队列中的 微博消息、 和 /或所述微博群组的广播队列中的微博消息的展示提醒和查看链 接, 并当所述用户对所述查看链接进行操作时, 通知所述特定消息界面管理 模块和 /或所述微博群組管理模块显示相应的微博消息。
其中, 所述微博消息管理模块, 还用于当所述用户作为所述微博群组中 的成员回复或转播特定消息队列中的微博消息时, 获取所述用户回复的内容 或转播的内容, 对所述微博群组帐号信息与所述回复的内容或转播的内容进 行封装, 生成回复消息或转播消息并传送至所述微博服务器端。
相应地, 本发明实施例还提供了一种微博服务器端, 包括:
微博群组服务器, 用于存储和管理微博群组的基本信息, 所述微博群组 的基本信息包括: 群组帐号信息及成员帐号信息列表;
微博消息服务器, 用于检测第一微博终端发送的微博消息的特定位置是 否包含微博群組怅号信息, 若检测结果为是, 将所述微博消息添加至所述微 博群组中各成员的特定消息队列中;
微博消息推送服务器, 用于扫描所述微博消息服务器添加处理后的所述 微博群组中各成员的特定消息队列, 将所迷微博群组中各成员的特定消息队 列中的微博消息推送至所迷微博群组中各成员对应的微博终端上进行发布。
其中, 所述微博消息服务器包括:
解析单元, 用于根据正则匹配原則解析第一微博终端发送的微博消息, 确定与预设的正則表达式约定的位置相匹配的所述微博消息的特定位置; 检测单元, 用于根据所述解析单元确定的所述微博消息的特定位置, 检 测所述微博消息的特定位置是否包含微博群组怅号信息;
第一操作单元, 用于当所述检测单元检測结果为是时, 从所述微博群组 服务器中查询所述微博群组的成员帐号信息列表, 并根据所述成员帐号信息 列表, 将所述微博消息添加至所述微博群组中各成员的特定消息队列中。
其中, 所述微博服务器端还包括: 微博用户 3艮务器, 用于存储和管理微博用户的基本信息, 所述微博用户 的基本信息包括: 用户帐号信息;
所述微博消息服务器还包括:
判断单元, 用于当所述检测单元检测结杲为否时, 判断所述微博消息的 特定位置是否包含第二用户帐号信息;
第二操作单元, 用于当所述判断单元的判断结杲为是时, 根据所述第二 用户帐号信息, 将所述微博消息添加至所述第二用户的特定消息队列中, 并 通知所述微博消息推送服务器将所述第二用户的特定消息队列中的微博消息 推送至所述第二用户对应的第二微博终端进行发布。
其中, 所述微博消息服务器, 还用于当所述微博群組中的成员回复或转 播所述成员的特定消息队列中所述第一微博终端对应的第一用户发布的微博 消息时, 接收所述成员对应的微博终端发送的回复消息或转换消息, 根据所 述回复消息或转播消息中的微博群组帐号信息, 将所述回复消息或转播消息 添加至所述微博群组的广播队列中, 并通知所述微博消息推送服务器将所述 微博群组的广播队列中的微博消息推送至所述第一微博终端进行发布。
实施本发明实施例微博消息的发布方法、 微博终端及微博服务器端, 具 有如下有益效果:
1、 本发明实施例的用户可在待发布的微博消息中输入微博群组怅号信 息, 微博服务器端对该待发布的微博消息进行检测, 当检测到该微博消息的 特定位置包含微博群组帐号信息时, 则将所述微博消息添加至所述微博群组 中各成员的特定消息队列 (比如: @消息队列) 中, 并将所述微博群组中各 成员的特定消息队列中的微博消息推送至所述微博群组中各成员对应的微博 终端上进行发布, 实现了单个微博用户 (微博群组内用户或微博群组外用户) 对微博群组内各成员的一对多^, 提高了用户的使用体验, 提升了产品竟 争力。
2、微博群組内的各成员可针对接 ij ^的特定消息队列中的微博消息进行 回复或转播, 各成员对应的微博终端对微博群组帐号信息与回复的内容或转 播的内容进行封装, 生成回复消息或转播消息并发送至微博服务器端, 由微 博服务器端根据微博群组帐号信息, 将各成员的回复消息或转播消息添加至 微博群组的广播队列中并推送至发送方(单个微博用户), 实现了微博群组对 单个微博用户 (微博群组内用户或微博群组外用户)的多对一会话, 进一步 提升了产品竟争力。
本发明实施例还提供一种微博整合方法、 微博终端、 微博列表、 微博话 务器及系统, 可实现微博信息聚合, 为用户提供更丰富的信息。
本发明提出一种微博整合方法, 包括步骤:
微博终端根据话题内容查询微博话 «务器, 获取话题的话题标识; 发送建立所述话题与所述微博终端所属的微博列表关联关系的建立指令 至微博列表服务器和 /或微博话题服务器; 所述建立指令的内容包括话題标识 以及微博列表标识; 所述关联关系包括决射关系和 /或收听关系;
微博列表服务器根据所述微博列表标识, 查找与微博列表标识对应的数 据内容, 并将所述话题标识写入至所迷数据内容, 建立映射关系; 和 /或, 微博话题服务器获取所迷话题的话題标识, 查找与话题标识对应的数据 内容, 并将所迷微博列表标识写入至所述数据内容, 建立收听关系。
优选地, 所述微博列表服务器根据所述微博列表标识, 查找与微博列表 标识对应的数据内容, 并将所述话題标识写入至所述数据内容, 建立映射关 系的步骤后还包括:
微博消息服务器将微博列表中的微博成员发送的微博消息, 发送至与微 博列表具有映射关系的话题的消息列表。
地, 所述微博消息服务器将微博列表中的微博成员发送的微博消息, 发送至与微博列表具有映射关系的话题的消息列表的步骤具体包括:
微博消息服务器获取所迷微博成员对应的微博列表标识, 查看与微博列 表标识具有映射关系的话題标识, 将所述微博消息写入至所述话题标识的消 息列表。
优选地, 所述微博话题服务器获取所述话题的话題标识, 查找与话题标 识对应的数据内容, 并将所迷徵博列表标识写入至所述数据内容, 建立收听 关系的步骤后还包括:
微博消息服务器对接收的微博消息进行解析, 获取话題内容并通过微博 话¾ ^务器查询是否存在相同的话題内容;
如存在, 微博消息服务器发送插入指令至微博话题服务器, 将话题内容 插入至相应话题的消息列表;
如不存在, 微博话 ¾1良务器根据所迷话题内容建立新的话题。
本发明还提出一种微博终端, 包括:
获 块, 用于根据话题内容查询微博话 ¾J5 务器, 获取话题的话题标 识;
指令发送模块, 用于发送建立所述话題与所述微博终端所属的微博列表 关联关系的建立指令至微博列 m务器和 /或微博话¾1良务器; 所述建立指令 的内容包括话题标识以及微博列表标识; 所述关联关系包括映射关系和 /或收 听关系;
请求写入模块, 用于通过微博列表服务器根据所述微博列表标识, 查找 与微博列表标识对应的数据内容, 并将所迷话题标识写入至所述数据内容, 建立映射关系; 和 /或,
用于通过微博话题服务器获取所述话题的话题标识, 查找与话题标识对 应的数据内容, 并将所述微博列表标识写入至所述数据内容, 建立收听关系。
本发明还提出一种微博列表服务器, 包括:
列表指令接收模块, 用于接收微博终端发送建立所述话题与所述微博终 端所属的微博列表映射关系的建立指令; 所述建立指令的内容包括话题标识 以及微博列表标识;
列表查找模块, 用于根据所迷微博列表标识, 查找与微博列表标识对应 的数椐内容, 并将所述话题标识写入至所述数据内容, 建立映射关系。
本发明还提出一种微博话 ¾艮务器, 包括:
话题指令接收模块, 用于接收微博终端发送的建立所述话题与所述微博 终端所属的微博列表收听关系的建立指令; 所述建立指令的内容包括话题标 识以及微博列表标 、;
话题查找模块, 用于获取所述话题的话题标识, 查找与话题标识对应的 数据内容, 并将所述微博列表标识写入至所述数据内容, 建立收听关系。
本发明还提出一种微博系统, 包括微博终端、 微博话题服务器以及微博 列 良务器, 所述微博终端用于:
根据话题内容查询微博话 务器, 获取话题的话題标识;
发送建立所述话题与所述微博终端所属的微博列表关联关系的建立指令 至微博列^良务器和 /或微博话题服务器; 所述建立指令的内容包括话题标识 以及微博列表标识; 所述关联关系包括映射关系和 /或收听关系;
所述微博列表服务器用于:
根据所述微博列表标识, 查找与微博列表标识对应的数据内容, 并将所 述话题标识写入至所述数据内容, 建立映射关系; 和 /或,
所述微博话 ¾m务器用于:
获取所述话题的话题标识, 查找与话题标识对应的数据内容, 并将所述 微博列表标识写入至所述数据内容, 建立收听关系。
优选地, 所述微博系统还包括:
微博消息服务器, 用于将微博列表中的微博终端发送的微博消息, 发送 至与微博列表具有映射关系的话題的消息列表。
优选地, 所述微博消息服务器具体用于:
获取所迷微博成员对应的微博列表标识, 查看与微博列表标识具有映射 关系的话题标识, 将所述微博消息写入至所述话题标识的消息列表。
优选地, 所述微博消息服务器还用于: 对接收的微博消息进行解析, 获取话题内容并通过微博话¾1艮务器查询 是否存在相同的话题内容; 在存在时, 发送插入指令至微博话«务器, 将 话题内容插入至相应的话題的消息列表;
所述微博话 ¾ ^务器还用于:
在不存在时, 根据所述话题内容建立新的话题。
本发明可以通过微博的话题展示方式查看到与该话题有关的微博列表, 从而可以从话题中查找到与话題相关的微博列表进行收听或者试听操作; 同 时, 微博列表的创建者可以通过建立一个话题与微博列表的映射关系, 使微 博列表成员发表的微博消息会自动进入与该话题相关的消息列表中; 如此, 收听该话题的微博终端就可以查看对应微博列表成员发表的微博消息, 实现 了微博的话题与微博列表之间的整合, 从而可实现信息聚合, 为用户提供更 丰富的信息。 附 B说明
为了更清楚地说明本发明实施例或现有技术中的技术方案, 下面将对实 施例描述中所需要使用的附图作筒单地介绍, 显而易见地, 下面描述中的附 图仅仅是本发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创 造性劳动的前提下, 还可以根据这些附图获得其他的附图。
图 1为本发明的一个实施例中的微博名单传播的实现方法的流程图; 图 2为本发明的一个实施例中的微博终端的结构示意图;
图 3为本发明的一个实施例中的微博名单传播系统的结构示意图; 图 4为本发明的另一个实施例中的微博名单传播的实现方法的流程图; 图 5为本发明的另一个实施例中的微博 List页面展示;
图 6为本发明的另一个实施例中的微博广播发表窗口页面展示; 图 7为本发明的另一个实施例中其他用户收到分享的微博 List的广播消 息页面展示; 图 8为本发明的另一个实施例中的微博终端的结构示意图; 图 9为本发明的一个实施例中服务器側管理用户群组成员的方法流程图; 图 10 为本发明的一个实施例中客户端側管理用户群组成员的方法流程 图;
图 n为本发明的另一个实施例中管理用户群组成员的方法流程图; 图 12为本发明的另一个实施例中一种管理用户群组成员的方法流程图; 图 13 为本发明的另一个实施例中另一种管理用户群组成员的方法流程 图;
图 14 为本发明的另一个实施例中另一种管理用户群组成员的方法流程 图;
图 15为本发明的另一个实施例中一种服务器的组成框图;
图 16为本发明的另一个实施例中另一种服务器的组成框图;
图 Π为本发明的另一个实施例中另一种服务器的组成框图;
图 18为本发明的另一个实施例中另一种服务器的组成框图;
图 19为本发明的另一个实施例中另一种服务器的组成框图;
图 20为本发明的另一个实施例中另一种服务器的组成框图;
图 2〗为本发明的另一个实施例中另一种服务器的组成框图;
图 22为本发明的另一个实施例中一种客户端的组成框图;
图 23为本发明的另一个实施例中一种客户端的组成框图;
图 24为本发明的另一个实施例中一种客户端的组成框图;
图 25为本发明的另一个实施例中一种客户端的组成框图;
图 26 为本发明的另一个实施例中一种管理用户群组成员的系统组成框 图 ·,
图 27为本发明的微博终端的第一实施例的结构示意图;
图 28为本发明的微博终端的第二实施例的结构示意图;
图 29为本发明的微博服务器端的第一实施例的结构示意图;
图 30为本发明的微博服务器端的第二实施例的结构示意图;
图 31为本发明的微博消息服务器的实施例的结构示意图; 12 000224
图 32为本发明的微博消息的发布方法的第一实施例的流程图;
图 33为本发明的微博消息的发布方法的第二实施例的流程图;
图 34为本发明的微博消息的发布方法的第三实施例的流程图;
图 35为本发明微博整合方法一实施倒中步様流程示意图;
图 36为本发明微博 方法一实施例中另一步骤流程示意图;
图 37为本发明微博 方法一实施例中是否存在相同的话题内容步骤流 程示意图;
图 38为本发明微博终端一实施例中结构示意图;
图 39为本发明微博列表服务器一实施例中结构示意图;
图 40为本发明微博话题服务器一实施例中结构示意图;
图 41为本发明微博系统一实施例中结构示意图。
实施方式
下面将结合本发明实施例中的附图, 对本发明实施例中的技术方案进行 清楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而 不是全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有做 出创造性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范围。
在网络发展的现阶段,微博作为一种扩展 消息传播机制的新产品新应 用得到了快速的增长。 在微博中用户之间的关系更加松散, 处于一种泛关系 链的状态之中, 即用户可以根据自己的兴趣与爱好去关注任何微博用户并收 听其发布的微博消息, 不需要任何的验证处理; 例如用户查看到某个广播消 息, 对发广播消息的用户感兴趣就可以直接收听, 这样可以使得广播消息的 传播更加快速与广泛。 微博 Li^是微博用户对自己感兴趣的微博用户所组成 的类似群体的一种管理方式, 微博 List成员可以是自己关注的用户也可以不 是自己关注的用户。 对于微博 List当前来说更多是提供了对于微博 List的管 理能力, 例如对于资料与成员的管理, 而与微博的泛关系链以及广播消息的 传播性结合还不够。 在本发明实施例中, 将提供了一种微博名单传播的实现方案, 该方案就 是充分利用了上述微博的泛关系链以及广播消息的传播性实现的一种基于微 博的广播形式对微博 List进行分享的方案。
下面将结合附图对本发明实施例中提供的微博名单传播的实现方法做进 一步介绍。
如图 1 所示, 本发明的一个实施例中提供的微博名单传播的实现方法, 至少包括以下步骤:
101、 终端接收用户提供的微博名单分享指令。
所述微博名单分享指令可以是由用户通过代码输入; 优选地, 可以是由 微博终端在所展示的微博页面上或者微博 List页面上设置控制按钮, 用户只 需操作鼠标点击所述控制按钮即可向微博终端下达微博名单分享指令。
102、 根据待分享的微博名单的基本信息自动生成微博名单分享消息。 其中, 所述微博名单的基本信息至少包括: 所述微博名单的名称和所述 微博名单对应的网址。
103、 将所迷微博名单分享消息进行发布。
终端在接收到用户下达的发布指令后, 即可将已生成的微博名单分享消 息发送给微博服务器并通过所述微博服务器对所述微博名单分享消息进行发 布。
对应于上述方法描述, 本实施例中还提供了一种用于实现上述微博名单 传播的微博终端。 如图 2所示, 所述微博终端, 包括:
接收单元 21, 用于接收用户提供的微博名单分享指令;
生成单元 22, 用于根据待分享的微博名单的基本信息自动生成微博名单 分享消息;
发布单元 23, 用于将所述微博名单分享消息进行发布。
将上述方法及微博终端应用到网络通信系统中即可形成一种微博名单传 播系统。 具体地, 如图 3所示, 所述微博名单传播系统包括: 微博终端 3〗和 微博服务器 32; 其中,
所述微博终端 31 , 用于接收用户提供的微博名单分享指令, 根据待分享 的微博名单的基本信息自动生成微博名单分享消息, 并将所述微博名单分享 消息通过所述微博服务器 32进行发布。
在上述实施例中, 在微博终端接收到用户下达的微博名单分享指令后, 会自动生成包含有用户所参与的微博名单即用户自己创建的或者加入的微博 名单信息的微博名单分享消息, 并通过微博服务器对所述微博名单分享消息 进行发布; 由于这一过程筒化了用户操作, 因此可以实现快速、 便捷地对微 博名单进行传播。
下面将以一更为具体的实施例来进一步阐述本发明实施例中所提供的微 博名单传播的实现方法及其对应的微博终端。
如图 4所示, 本发明的另一个实施例所提供的微博名单传播的实现方法, 具体包括以下步骤:
401、 用户通过微博终端登录到微博服务器上。
具体地, 用户通过微博终端录入属于该用户的賺号和密码, 微博终端将 所述账号和密码发送到登录服务器进行用户身份验证。 在验证通过且登录成 功后, 则建立起微博终端与登录服务器之间的连接通道; 并且, 微博终端需 要通过定时发送心跳包的形式保证其与登录服务器之间的连接。
在本实施例中, 上述微博终端可以是但不限于是 IM客户端; 用户可以通 过所述微博终端进行相关的界面操作与信息交互。
402、 用户登录微博成功后, 微博终端从微博服务器上获取该用户所参与 的微博 List ID列表以及该微博 List BD列表中的至少一个微博 List对应的基本 信息和该微博 List中的成员列表信息。
具体地, 微博终端倒的微博 List管理模块向微博服务器側的徵博用户服 务器发送获取用户所参与的微博 List ID列表的协议命令, 在该协议命令对应 的数据包中携带有所述用户对应的号码标识。 上述用户所参与的微博 List具 体可以是用户所创建的或者加入的微博 List.
所述微博用户服务器在接收到所述协议命令对应的数据包后, 解析该数 据包并从中获取到用户的号码标识, 根据所述用户的号码标识查询数据库以 获取该用户所参与的微博 List ID列表返回给微博终端。
微博终端根据所述微博用户服务器返回的微博 List ID列表到微博 List服 务器查询所述微博 List Π)列表中的微博 List的基本信息以及每个微博 List中 的成员列表信息; 在获取到所述微博 List的基本信息以及每个微博 List中的 成员列表信息后, 微博终端将其 在本地文件中。
其中, 上述微博终端侧的微博 List管理模块, 主要用于拉取和存储与该 微博 List关联的资料和成员列表, 同时创建微博 List展示界面进而对^^到 的与微博 List关联的信息数据进 f亍展示;
上述微博服务器側的微博用户服务器, 主要用于保存微博用户的收听关 系以及基本资料、 用户类型、 用户标签属性等用户基本信息。
403、 微博终端在获 微博 List ID列表以及其中至少一个微博 List对 应的基本信息和该微博 List中的成员列表信息后, 可以根据用户需要选择其 中一个微博 List进行展示, 并创建如图 5所示的微博 List界面。
404、 微博终端接收用户提供的微博 List分享指令。
具体地, 可以是微博终端监听用户的鼠标点击操作, 通过确认用户是否 点击了图 5中所示的微博 List界面上的 "分享" 按钮来获知用户是否下达了 微博 List分享指令; 即, 只要用户点击了 "分享"按钮, 則微博终端就会收 到一个徵博 List分享指令。
405、 微博终端从本地提取出当前打开的微博 List的基本信息, 根据该微 博 List的基本信息自动生成微博名单分享消息。
在本实施例中, 当前打开的微博 List即为待分享的微博 List。
具体地, 可以将所述微博 List的基本信息与微博终端本地保存的默认信 息进行组合, 以形成微博名单分享消息的内容; 之后, 在当前微博 List页面 上创建微博广播发表窗口, 并将上述微博名单分享消息的内容填充到所述微 博广播发表窗口中。
如图 6所示, 所述默认消息可以是 "剛剛创建了一个叫 '****, 的微博 名单, 发现里面有很多有趣的人和他们发的广播, 推推给大家一起分享 http://***";在实际的发布过程中,所迷默认消息中的 *号部分会由不同的微博 List名称和 /或微博 List对应的网址所代替,
406、 微博终端监听上述微博广播发表窗口的 "发送" 按钮上是否出现鼠 标操作, 如果 "发送" 按钮被点击則微博消息管理模块将所述微博名单分享 消息的内容以及用户的号码标识组装到数据包中并发送给微博服务器側的微 博消息服务器, 之后通过所述微博消息服务器进行微博名单分享消息的发布。
微博消息服务器生成对应的微博消息 ID放入到对应该用户的发表消息 ID列表中。
其中, 上述微博消息管理模块位于微博终端側, 主要用于与微博服务器 侧的微博消息服务器进行协议命令交互,进而实现微博消息 ID列表的拉取以 «1"应每个消息内容的 展示, 同时还负责微博消息广播发表窗口的创建 与管理处理;
上述微博消息服务器, 主要用于管理微博消息索引 (消息 ID )与消息体 (消息内容)之间的映射关系; 微博终端可以根据微博索引 到对应的消 息体。
407、 所述微博名单分享消息在其他微博用户的微博页面上进行显示。 在其他微博用户查看自己的微博主页消息时, 所述其他微博用户所使用 的微博终端会拉取其所关注的微博用户的号码标识对应的发表消息队列, 将 所述发表消息队列按照时间排序后返回给微博终端对应的主页。
具体地, 消息 ID列表被发送给微博终端的微博消息管理模块, 利用微博 消息管理模块拉取对应于每个消息 ID的消息内容, 则可以创建出类似于图 7 所示的微博消息展示; 其中图 7所显示的网络链接对应于所述待分享的微博 List的网址。
408、微博终端的微博消息管理模块监听用户的每个消息体内的鼠标点击 操作, 如果图 7 中所展示的网络链接被点击, 则微博终端会根据所述网络链 接获取到对应的微博 List ID标识, 创建对应的微博 List展示界面, 并根据微 博 List ID iW!l该微博 List的基本信息及其成员号码列表。
409、在其他用户使用的微博终端上显示所共享的微博 List中所有成员的 微博消息。
根据所述微博 List的基本信息创建对应的展示控件以显示对应的名称等 信息, 根据所述成员号码列表从微博消息服务器获取对应该成员号码列表的 最新发表消息 Π)列表, 并根据所迷最新发表消息 ID列表称具体的消息内 容。 这样, 微博用户就可以查看到对应所述共享的微博 List 中所有成员 发表的最新消息; 通过这种泛关系链的传播方式, 可以快速地进行微博 List 的分享, 极大地 ·Τ展微博 List 的使用 。
进一步地, 如果上述其他用户在看到所述共享的微博 List之后, 如果对 其产生兴趣也可以很方便地进行加入该微博 List的操作,因此有利于微博 List 的快速推广。
在通过上述各步骤所描述的微博名单传播的实现方法中, 是以用户直接 在一个徵博 List页面中点击 "分享" 这样一个控制按 来触发微博名单分享 指令的。 除了上述方式外, 微博用户也可以通过直接点击设置在自己微博页 面上的控制按钮 "分享" 来釉发微博名单分享指令。
由于一个微博用户所参与的微博 List的数量会大于 1个, 这样在微博终 端接收到用户提供的微博名单分享指令之后, 且在根据待分享的微博名单的 基本信息自动生成微博名单分享消息之前, 所迷微博终瑞还需要进行如下操 作:
在用户点击了 "分享"按钮之后, 微博终端向用户展示该用户所参与的 所有微博 List的列表, 以便于该用户选择其中的至少一个微博 List; 用户从显示的微博 List列表中, 选出至少一个微博 List作为待分享的微 博 List, 之后进行提交;
在用户提交了选择的微博 List之后, 微博终端获取到用户所选的至少一 个微博名单的信息;
之后, 微博终端会根据用户所选的至少一个微博 List对应的基本信息自 动生成微博名单分享消息。
对应于上述方法实施例的描述, 在本实施例中还提供了一种用于实现上 述方法的微博终端。 如图 8所示, 所述徵博终端包括: 接收单元 81、 生成单 元 82和发布单元 83; 其中,
接收单元 81, 用于接收用户提供的微博名单分享指令;
生成单元 82, 用于根据待分享的微博名单的基本信息自动生成微博名单 分享消息;
发布单元 83, 用于将所述微博名单分享消息进行发布。
此外, 在本实施例中, 所述微博终端还包括: 获取单元 84, 用于从微博 服务器上获取所述用户参与的至少一个微博名单的基本信息。
其中, 上述待分享的微博名单可以是用户当前打开的微博名单; 或者, 所迷待分享的微博名单是用户所参与的所有微博名单中的至少一个微博名 单。
在所述待分享的微博名单为用户参与的所有微博名单中的至少一个时, 在所述微博终端中还需要设置展示单元 85以便于用户能够方便地从其参与的 微博名单中选取待分享微博 List; 其中,
展示单元 85,用于向所迷用户展示该用户所参与的所有微博名单的列表, 以便于该用户选择其中的至少一个微博名单;
所迷接收单元 81, 还用于接收用户根据所述展示单元展示的微博名单进 行选择得到的至少一个微博名单的信息;
所述生成单元 82, 还用于根据用户所选的至少一个微博名单对应的基本 信息自动生成微博名单分享消息。
在本实施例中, 用户可以通过微博广播的形式对自己创建或者加入的微 博 List进行发表,在消息内容中会附带上待分享的微博 List对应的界面链接, 这样其他微博用户查看到这个广播消息之后, 点击消息中的微博 List展示界 面链接就可以去查看该微博 List所有成员聚合的消息列表, 其他用户通过阅 读这些消息可以选择是否订阅或者加入该微博 List。这样通过微博的泛关系链 以及消息的快速传播能够快速的传播微博 List,使得每个微博 List也可以得到 快速的传播与增长。
本发明实施例中提供的微博名单传播的实现方法、 终端及系统适用于任 何微博系统。
微博中, 话题是一类相关微博消息的聚合消息列表, 微博终端可以方便 地在广播发表框中以插入话题的方式建立一个话题, 比如只要微博终端发表 的广播消息中包含内容中呈现" #话题内容# "时,微博终端即可通过"话题内容" 聚合与之相关的微博消息列表; 而微博列表(List )功能是聚合某一类相关微 博终端的终端列表的功能, 微博列表是按照相关微博微博终端特点聚合在一 起的徵博终端列表, 通过微博列表微博终端可以非常方便与同类微博终端产 生互动; 微博的话题功能与微博的列表功能各有优点, 便于微博终端使用, 然而现有技术中两个功能之间缺少了关联关系, 随着微博终端需求的提升, 将给微博终端对微博的使用带来不便, 影^用户体验。
为此, 本发明实施例还提供一种管理用户群组成员的方法, 该方法为服 务器側的方法, 如图 9所示, 该方法包括:
901、服务器接收客户端发送的推荐用户加入到预定用户群组的推荐加入 协议命令, 所述推荐加入协议命令中包含被推荐用户 ID ^¾定用户群组 Π
902、 根据所述预定用户群组 ID确定所迷预定用户群组的创建用户, 并 向所述创建用户发送推荐加入通知消息, 以便所述创建用户确定是否将被推 荐用户加入到所述预定用户群纽中。 需要说明的是, 用户在创建用户群组时, J§1务器会记录用户群组创建的 相关信息, 并将所述相关信息以数据表的形式存储, 该相关信息包括用户群 組名、 用户群组 ID、 创建者等信息, 当服务需要获取一个用户群组的创建者 时, 仅需要根据所述用户群組的 ID查询用户群组相关信息数据表, 便可以获 取第一用户群组的创建者, 因此本发明实施例中在根据所述预定用户群组 Π) 确定所述预定用户群组的创建用户时, 即可以通过所述预定用户群组 ID查询 该用户群组相关信息数据表确定所迷预定用户群组的创建用户。
903、 当接收到所述创建用户发送的同意将所述推荐用户加入到所述预定 用户群组中的响应消息时, 将所述被推荐用户 Π 添加到所述预定用户群组的 成员列表中。
本发明的实施例还提供一种管理用户群组成员的方法, 该方法为客户端 側的方法, 如图 10所示, 该方法包括:
1001、 客户端获取向预定用户群组推荐加入的被推荐用户 Π
其中, 所述客户端获取向预定用户群组推荐加入的被推荐用户 ID时, 可 以通过接收用户通过界面操作手动输入的被推荐用户 ID得到, 也可以通过接 收用户通过界面操作从已显示的用户群组中选取的被推荐用户 ID得到,但本 发明实施例对此不进行限制, 任何可以获取所迷向预定用户群组推荐加入的 被推荐用户 ID的方法都属于本发明实施例保护的范围.
1002、 向服务器发送推荐用户加入到预定用户群组的推荐加入协议命令, 所述推苒加入协议命令中包^^推荐用户 ID和预定用户群组 Π
本发明实施例中, 当用户需要将一个用户群组中的用户推荐加入到另一 个用户群组中时, 获取向预定用户群組推荐加入的被推荐用户 ED, 并向服务 器发送推荐用户加入到預定用户群组的推荐加入协议命令; 所¾ ^务器接收 到该推荐加入协议命令后, 根据所迷推荐加入协议命令中包含的预定用户群 组 ID确定所述预定用户群组的创建用户, 并向所述创建用户发送推荐加入通 知消息, 当接收到所述创建用户发送的同意将所述推荐用户加入到所述预定 用户群组中的响应消息时, 将所述被推荐用户 ID添加到所述预定用户群组的 成员列表中, 从而实现了用户给某个用户群组推荐其他用户, 极大的方便了 用户群组的扩展创建。
本发明实施例还提供一种管理用户群组成员的方法, 如图 11所示, 该方 法包括:
1101、 客户端获取向预定用户群组推荐加入的被推荐用户 ID, 并向服务 器发送推荐用户加入到预定用户群组的推荐加入协议命令, 所述推荐加入协 议命令中包含被推荐用户 ID和预定用户群組 ID.
1102、 服务器接收客户端发送的推荐用户加入到预定用户群组的推荐加 入协议命令,并根据所述预定用户群组 ID确定所述预定用户群组的^建用户。
1103、 所述服务器根据所述推荐用户 ID确定所述预定用户群组的创建用 户是否为所述推苒用户; 若所述领定用户群組的创建用户为所迷推荐用户, 则执行步骤 1104; 若所述领定用户群组的创建用户为非所述推荐用户时, 则 执行步骤 1105。
1104、直接将所述被推荐用户 ID添加到所述预定用户群组的成员列表中。
1105、 向所述创建用户发送推荐加入通知消息, 以便所述创建用户确定 是否将被推荐用户加入到所述预定用户群组。
1106、 当接收到所述创建用户发送的同意将所述推荐用户加入到所述預 定用户群组中的响应消息时,将所述被推荐用户 E 添加到所述预定用户群组 的成员列表中。
1107、 当接收到所述创建用户发送的拒绝将所迷推荐用户加入到所述预 定用户群組中的响应消息时, 不将所述被推荐用户 ID添加到所述预定用户群 组的成员列表中。
进一步可选的,在将所述被 用户 ID添加到所述预定用户群组的成员 列表中之后, 还包括:
向所述推荐用户发送被推荐用户已被领定用户群组收录的通知消息, 以 便推荐用户客户端将所述通知消息创建对应提醒界面, 提示用户被推荐用户 的加入状态; 和 /或 向所述被推荐用户发送其已被推荐收录到预定用户群组的通知消息, 以 便被推荐用户客户端将所述通知消息创建对应提醒界面, 提示被推荐用户已 经加入了用户群组。
进一步可选的,用户在向预定用户群组推荐加入用户时,可以如步骤 1101 至 1107中所述的一次只推荐一个用户加入,但也可以一次推荐多个用户加入。 当推荐多个用户加入时, 步骤 1101中所述客户端获取向预定用户群组推荐加 入的多个用户 ID, 并在向服务器发送推荐加入协议命令时, 将所述多个用户 ID以被推荐用户 Π)列表的形式包含在所述推荐加入协议命令中;所述服务器 可以将所述被推荐用户 ID列表中的每个被推荐用户按照步骤 1102至 1107中 描述的方法逐一进行推荐加入操作, 具体的描述, 本发明实施倒此处将不再 资述。
本发明实施例中, 当用户需要将一个用户群组中的用户推荐加入到另一 个用户群组中时, 获取向預定用户群组推荐加入的被推荐用户 ID, 并向服务 器发送推荐用户加入到预定用户群组的推荐加入协议命令; 所述服务器接收 到该推荐加入协议命令后, 根据所述推荐加入协议命令中包含的预定用户群 组 Π)确定所述预定用户群组的创建用户, 并向所迷创建用户发送推荐加入通 知消息, 当接收到所述创建用户发送的同意将所述推荐用户加入到所述預定 用户群组中的响应消息时,将所迷被推荐用户 ID添加到所述预定用户群组的 成员列表中, 从而实现了用户给某个群组推荐其他用户, 方便了用户群组的 扩展创建。 更进一步的, 用户向预定用户群组推荐加入的用户时, 可以一次 推荐多个用户加入, 避免了一个个的加入时多次向服务器发送推荐加入协议 命令, 节省了资源, 极大的方便了用户群组的扩展创建。
并且, 本发明实施例中, 当所述预定用户群组的创建用户为所述推荐用 户时, 直接将所述被推荐用户 Π)添加到所述预定用户群组的成员列表中, 节 省了预定用户群组的创建用户的确认, 加快了被推荐用户的加入流程。
进一步的, 在将所述被推荐用户 ID添加到所述预定用户群组的成员列表 中之后, 本发明实施例还可以向所述推荐用户发送被推荐用户已被预定用户 群组收录的通知消息, 方便推荐用户得知被推荐用户加入的状态; 并且还可 以向所迷被推荐用户发送其已被推荐收录到预定用户群组的通知消息, 以便 被推荐用户得知自己加入的用户群纽, 提高了用户^^。
本发明实施例还提供一种管理用户群組成员的方法, 该方法主要阐述显 示用户创建或者加入的用户群组的信息, 如图 12所示, 该方法包括:
1201、 客户端向所述服务器发送获取 ID列表协议命令, 所述获取 ID列 表协议命令用于获取用户创建或者加入的用户群组 ID列表, 所述获取 Π 列 表协 i又命令中包含所述用户 Π
其中, 所述客户端向所述服务器发送获取用户创建或者加入的用户群组 ED列表的获取 ID列表协议命令, 可以在用户登录客户端时自动向服务器发 送, 也可以在用户登录客户端后, 由用户触发向服务器发送, 本发明实施例 对此不进行限制。
1202、 服务器接收所述客户端发送的获取 ID列表协议命令, 根据所述用 户 ID获取所述用户创建或者加入的用户群组 ID列表, 并将所述用户群组 ID 列 l送给所述客户端。
需要说明的是, 每个用户群组的创建, 其创建的相关信息所述服务器都 会以数据表的形式保存,所迷的相关信息可以包括用户群组名、用户群组 ED、 创建者等; 并且每个用户的相关信息所述服务器也会以数据表的形式保存, 当需要查询用户的相关信息时, 其可以根据用户 ID查询相关数据表, 便可以 获取该用户的相关信息, 包括该用户创建或者加入的用户群组 Π
1203、 所述客户端接收所述服务器返回的所述用户创建或者加入的用户 群组 ID列表; 根据所述用户群组 ID列表, 获取所述用户群组 Π)列表中各个 用户群组的基本资料信息, 并将所述各个用户群组的基本资料信息展示。
进一步的, 当用户获取并显示了自己创建或加入的用户群組列表后, 用 户还可以通过隐私设置设置该用户群组列表是否可以被其他用户查看, 具体 的, 如图 13所示, 该方法包括:
130 客户端获取用户设置的隐私设置选项, 所述隐私设置选项包括是 否向其他用户展示用户创建或者加入的用户群组。
其中, 用户在设置所述隐私设置选项时, 可以通过隐私设置界面设置所 述隐私设置选项, 所述隐私设置选项可以通过单元框的形式供用户选择, 但 本发明实施例对此并不进行限制。 当在微博中时, 所迷隐私设置选项可以为 是否在个人资料中或者客人页中向其他用户展示用户创建或者加入的用户群 组, 但本发明实施例对此不进行限制, 只要所述隐私设置选项为包括是否向 其他用户展示用户创建或者加入的用户群组便可。
1302、 所述客户端根据所述隐私设置选项向所述服务器发送隐私设置协 议命令, 所述隐私设置协议命令中包含所述用户 ΠΧ
1303、 服务器接收所述客户端发送的隐私设置协议命令, 根据所述用户 ID获取所述隐私设置对应的数据内容, 并根椐所迷隐私设置协议命令对所述 数据内容进行隐私设置, 以便其他用户查询该用户的个人资料时, 根据所述 隐私设置确定是否将该用户创建或者加入的用户群组显示给其他用户„
进一步可选的, 用户可以在客户端查看其他用户的个人资料, 基于上述 步骤 1301至 1303中的描述, 用户在查看其他用户的个人资料时, 根据该其 他用户设置的隐私设置的不同, 获取的个人资料不同, 包括含有其弛用户创 建或加入的用户群组列表的个人资料和不含有其他用户创建或加入的用户群 组列表的个人资料, 具体方法如图 14所示, 该方法包括:
1401、 客户端向所述服务器发送获取其他用户个人资料的协议命令, 所 述获取其他用户个人资料的协议命令中包含所述用户 ID; 其中, 所述获取其 他用户个人资料的协议命令, 为当用户查询除自己以外的其他用户的个人资 料时, 向所述服务器发送的协议命令。
1402、 服务器接收客户端发送的获取其他用户个人资料的协议命令, 所 述获取其他用户个人资料的协议命令中包含所述用户 ID,并根据所述用户 Π) 获取所迷用户对应的隐私设置项和所迷用户的基本资料。
1403、 若所述隐私设置项为向其他用户展示用户创建或者加入的用户群 组, 则获取所述用户创建或者加入的用户群组 ID列表, 并将所述用户的基本 资料和所迷用户创建或者加入的用户群组 ID列; ½送给所述客户端。
1404、 所述客户端接收所述服务器发送的所述用户的基本资料和所述用 户创建或者加入的用户群组 ID列表, 根据用户群组 I 列表查询获取所述用 户群组 ID列表中各个用户群组的基本资 frf言息, 并根据所迷^ ^用户群组的 基本资料信息和所述用户的基本资料创建所迷用户的第一个人资料界面, 并 将所述第一个人资料界面展示, 结束本次用户个人资料的获取。
1405、 若所述隐私设置项为不向其他用户展示用户创建或者加入的用户 群组, 则所述服务器将所述用户的基本资料发送给所述客户端。
1406、 所述客户端接收所述服务器发送的所述用户的基本资料, 根据所 述用户的基本资料创建所述用户的第二个人资料界面, 并将所述第二个人资 料界面展示, 结束本次用户个人资料的获取。
本发明实施例中, 可以在用户个人资料中将用户创建或者加入的用户群 组展示给用户, 方便用户查看其被邯些用户群组收录, 提高了用户 。
并且, 本发明实施例中, 在将用户创建或者加入的用户群组的信息展示 给用户后, 用户可以通过隐私设置操作界面设置该用户群组列表是否可以被 其他用户查看, 能够满足用户对于隐私的保护; 当用户设置为向其他用户展 示用户创建或者加入的用户群组时, 其他用户可以非常方便的查看到与该用 户相关的用户群组, 极大的方便了用户扩展创建用户群组。
本发明实施例还提供一种服务器, 如图 15所示, 该服务器包括: 第一接 收单元 151、 第一确定单元 152、 第一发送单元 153和第一操作单元 154。
第一接收单元 151,用于接收客户端发送的推荐用户加入到预定用户群组 的推荐加入协议命令, 所述推荐加入协议命令中包含被 ^用户 ID和预定用 户群组 ΠΧ
第一确定单元 152,用于根据所述第一接收单元 151接收的所述預定用户 群组 I 确定所迷预定用户群组的创建用户。
第一发送单元 153,用于向所述第一确定单元 152确定的所述创建用户发 送推荐加入通知消息, 以便所述创建用户确定是否将被推荐用户加入到所述 预定用户群组中。
第一搡作单元 154,用于当接收到所述创建用户发送的同意将所述推荐用 户加入到所述预定用户群组中的响应消息时, 将所述被推荐用户 ID添加到所 述预定用户群组的成员列表中。
可选的, 如图 16所示, 该服务器还包括: 第二操作单元 155。
第二操作单元 155,用于当接收到所述创建用户发送的拒绝将所述推荐用 户加入到所述预定用户群组中的响应消息时, 不将所述被推荐用户 ID添加到 所迷预定用户群组的成员列表中,
可选的, 如图 17所示, 该服务器还包括: 第二确定单元 156。
第二确定单元 156, 用于当所迷推荐协议命令中还包括推荐用户 ID时, 在所述第一确定单元 152根据所述预定用户群组 ID确定所述预定用户群组的 创建用户之后,根据所述推荐用户 ED确定所迷预定用户群组的创建用户是否 为所述推荐用户。
所述第一操作单元 154还用于, 在所述第二确定单元〗56确定所述预定 用户群组的创建用户为所述推荐用户时, 直接将所述被推荐用户 ID添加到所 述预 户群组的成员列表中。
所述第一发送单元 153还用于, 在所迷第二确定单元 156确定所述预定 用户群组的创建用户为不是所述推荐用户时, 向所述创建用户发送推荐加入 通知消息。
可选的, 如图 18所示, 该服务器还包括: 第一通知单元 157和 /或第二通 知单元 158。
第一通知单元 157, 用于在所述第一操作单元 154将所述被推荐用户 ID 添加到所述预定用户群组的成员列表中之后, 向所述推荐用户发送被推荐用 户已被预定用户群组收录的通知消息。
第二通知单元 158, 用于在所述第一操作单元 154将所述被推荐用户 ID 添加到所述预定用户群组的成员列表中之后, 向所述被推荐用户发送其已被 推荐收录到预定用户群组的通知消息。 可选的, 如图 19所示, 该服务器还包括: 第二接收单元 159、 第一获取 单元 1510和第二发送单元 15Π,
第二接收单元 159, 用于接收客户端发送的获取 Π)列表协议命令, 所述 获取 ID列表协议命令用于获取用户创建或者加入的用户群组 ID列表, 所述 获取 ID列表协议命令中包含所述用户 Π
第一获取单元 1510, 用于根据所述第二接收单元 159接收的所述用户 ID 获取所迷用户创建或者加入的用户群组 ID列表。
第二发送单元 1511 ,用于将所迷第一获取单元 1510获取的所述用户群组 ID列表发送给所述客户端。
可选的, 如图 20所示, 该服务器还包括: 第三接收单元 1512、 第二获取 单元 1513和设置单元 1514.
第三接收单元 1512, 用于接收所述客户端发送的隐私设置协议命令, 所 述隐私设置协议命令中 含所述用户 ID; 其中, 所述隐私设置协议命令为所 述客户端根据用户设置的隐私设置选项向所述服务器发送的协议命令, 所述 隐私设置选项包括是否向其他用户展示用户创建或者加入的用户群组。
第二获取单元 1513,用于根据所迷第三接收单元 1512接收的所述用户 ID 获取所述隐私设置对应的数据内容。
设置单元 1514, 用于根据所述隐私设置协议命令对所述第二获取单元 1513获取的所述数据内 «行隐私设置。
可选的, 如图 21所示, 该服务器还包括: 第四接收单元 1515、 第三获取 单元 1516、 第四获取单元 1517和第三发送单元 1518。
第四接收单元 1515, 用于接收客户端发送的获取其他用户个人资料的协 议命令, 所述获取其他用户个人资料的协议命令中包含其他用户的用户 ID; 其中, 所述获取其他用户个人资料的协议命令, 为当用户查询除自己以外的 其他用户的个人资料时, 向所述服务器发送的协议命令。
第三获取单元 Ϊ516,用于根据所述第四接收单元 1515接收的所述用户 ID 获取所述用户对应的隐私设置项和所迷用户的基本资料。 第四获取单元 1517, 用于当所述隐私设置项为向其他用户展示用户创建 或者加入的用户群组时, 获取所述用户创建或者加入的用户群组 ID列表。
第三发送单元 1518,用于将所述第三获取单元 1516获取的所述用户的基 本资料和所述第四获取单元 】5〗7 获取的所迷用户创建或者加入的用户群组 ED列 送给所 ΐ½户端。
所述第三发送单元 1518还用于, 当所述隐私设置项为不向其他用户展示 用户创建或者加入的用户群组时, 将所述第三获取单元 15〗6获取的所述用户 的基本资料发送给所述客户端。
需要说明的是, 该服务器所包含功能模块的其他描述, 可以参考上述实 施例管理用户群组成员的方法中的相应描述, 本发明实施例此处将不再赞述„ 本发明实施例还提供一种客户端, 如图 22所示, 该客户端包括: 第一获 取单元 221和笫一发送单元 222。
第一获取单元 221, 用于获取向預定用户群组推荐加入的被推荐用户 Π 其中, 所述第一获取单元 221获取向预定用户群组推荐加入的被推荐用户 ID 时, 可以通过接收用户输入的所述被推荐用户 ID获取, 也可以通过接收用户 从该用户的用户群组中选取的所述被推荐用户 I 获取, 但本发明实施例对此 不进行限制。
第一发送单元 222 ,用于向服务器发送推荐用户加入到预定用户群组的推 荐加入协议命令, 所述推荐加入协议命令中包含被推荐用户 ID和預定用户群 组 Π
可逸的, 如图 23所示, 该客户端还包括: 第二发送单元 223、 第一接收 单元 224、 第二获取单元 225和展示单元 226。
第二发送单元 223, 用于向所述服务器发送获取 ID列表协议命令, 所述 获取 ID列表协议命令用于获取用户创建或者加入的用户群组 ID列表的协议 命令, 所述获取 Π 列表协议命令中包含所述用户 Π
第一接收单元 224,用于接收所述服务器返回的所述用户创建或者加入的 用户群组 ID列表。 第二获取单元 225,用于根据所述第一接收单元 224接收的所述用户群组 ID列表, 获取所迷用户群组 ID列表中各个用户群组的基本资料信息,
展示单元 226,用于将所述第二获取单元 225获取的所述各个用户群组的 基本裔料信息展示。
可选的, 如图 24所示, 该客户端还包括: 第三获取单元 227和第三发送 单元 228。
第三获取单元 227,用于在所述展示单元 226将所迷各个用户群組的基本 资料信息展示之后, 获取用户设置的隐私设置选项, 所述隐私设置选项包括 是否向其他用户展示用户创建或者加入的用户群组。
第三发送单元 228,用于根据所述第三获取单元 227获取的所述隐私设置 选项向所 务器发送隐私设置协议命令, 所述隐私设置协议命令中包含所 迷用户 Π
可选的, 如图 25所示, 该客户端还包括: 第四发送单元 229、 第二接收 单元 2210、 第一操作单元 22U、 第一创建展示单元 2212和第二创建展示单 元 2213。
第四发送单元 229,用于用户查询除用户自己以外的其他用户的个人资料 时, 向所述服务器发送获取其他用户个人资料的协议命令, 所述获取其他用 户个人资料的协 i义命令中包含所述用户 Π
第二接收单元 22〗0, 用于接收所述服务器返回的所述用户的基本资料, 或者所述用户的基本资料和所述用户创建或者加入的用户群组 I 列表返回给 所述客户端。
第一操作单元 2211,用于当所迷第 收单元 89接 所述用户的基本 资料和所述用户创建或者加入的用户群组 Π)列表返回给所述客户端时,根据 用户群组 B0列表查询获取所述用户群组 ID列表中各个用户群组的基本资料
^息 β
第一创建展示单元 2212, 用于根据所述用户的基本 i 料和所述第一操作 单元 2211获取的各个用户群组的基本资料信息, 创建所述用户的第一个人资 料界面, 并将所述第一个人资料界面展示。
第二创^^示单元 2213,用于当所述第 收单元 2210接 所述用户 的基本资料时, 根据所述用户的基本资料创建所述用户的第二个人资料界面, 并将所述第二个人资料界面展示。
需要说明的是, 该客户端所包含功能模块的其他描述, 可以参考上述实 施例管理用户群组成员的方法中的相应描述, 本发明实施例此处将不再赘述。
本发明实施例还提供一种管理用户群组成员的系统, 如图 26所示, 该系 统包括: 客户端 261和服务器 262。
客户端 261, 用于获取向预定用户群组推荐加入的被推荐用户 ID; 向服 务器 262发送推荐用户加入到颈定用户群组的推荐加入协议命令, 所述推荐 加入协议命令中包舍被推荐用户 ID和预定用户群组 ΠΧ
服务器 262,用于接收客户端 261发送的推荐用户加入到预定用户群组的 推荐加入协议命令, 所述推荐加入协议命令中包含被推荐用户 ID和预定用户 群组 ID;根据所述预定用户群组 ID确定所述预定用户群组的创建用户,并向 所述创建用户发送推荐加入通知消息, 以便所述创建用户确定是否将被推荐 用户加入到所述预定用户群组中; 当接收到所述创建用户发送的同意将所述 推荐用户加入到所述预定用户群组中的响应消息时,将所述被推荐用户 ID添 加到所述预定用户群组的成员列表中。
需要说明的是, 该系统所包含功能模块的其他描述, 可以参考上述实施 例管理用户群组成员的方法, 以及本实施例装置本分的相应描述, 本发明实 施例此处将不再赘迷。
本发明实施例中, 当用户需要将一个用户群组中的用户推荐加入到另一 个用户群组中时, 客户端获取向预定用户群组推荐加入的被推荐用户 ID, 并 向服务器发送推荐用户加入到预定用户群组的推荐加入协议命令; 所述服务 器接收到该推荐加入协议命令后, 根据所述推荐加入协议命令中包含的预定 用户群组 ID确定所述预定用户群组的创建用户, 并向所述创建用户发送推荐 加入通知消息, 当接收到所述创建用户发送的同意将所述推荐用户加入到所 述预定用户群组中的响应消息时,将所述被推荐用户 Π)添加到所述预定用户 群组的成员列表中, 从而实现了其他用户给某个群组推荐其他用户, 方便了 用户群组的扩展创建。 更进一步的, 用户向预定用户群组推荐加入的用户时, 可以一次推荐多个用户加入, 避免了一个个的加入时多次向服务器发送推荐 加入协议命令, 节省了资源, 极大的方便了用户群组的扩展创建。
并且, 本发明实施例中, 当所述预定用户群組的创建用户为所述推荐用 户时, 直 所述被推荐用户 Π)添加到所述预定用户群组的成员列表中, 节 省了预定用户群组的创建用户的确认, 加快了被推荐用户的加入流程。
进一步的, 在将所述被推荐用户 ID添加到所迷预定用户群组的成员列表 中之后, 本发明实施例还可以向所述推荐用户发送被推荐用户已被预定用户 群组收录的通知消息, 方便推荐用户得知被推荐用户加入的状态; 并且还可 以向所述被推荐用户发送其已被推荐收录到預定用户群组的通知消息, 以便 被推荐用户得知自己加入的用户群组, 提高了用户体验。
本发明实施例中, 可以在用户个人资料中将用户创建或者加入的用户群 ^示给用户, 方便用户查看其被哪些用户群组收录, 提高了用户体验。 并且, 本发明实施例中, 在将用户创建或者加入的用户群组的信息展示 给用户后, 用户可以通过隐私设置操作界面设置该用户群组列表是否可以被 其他用户查看, 能够满足用户对于隐私的保护; 当用户设置为在个人资料中 展示用户创建或者加入的用户群组或者在客人页中展示用户创建或者加入的 用户群组时, 其他用户客户非常方便的查看到与该用户相关的用户群组, 极 大的方便了用户扩展创建用户群组。
需要说明的是, 本发明实施例管理用户群组成员的方法、 装置及系统中 的用户群组可是微博中的微博 List列表, 也可以是其他 IM软件工具中的群, 本发明实施例对此不进行限制。
微博 Lis (群组)为相同爱好或者相同标签的微博用户提供小圈子的聚焦、 沟通和交流的平台。 当用户创建微博 List或加入到某个微博 List时, 可以对 该微博 List中的多个微博用户进行会话。 现有的微博系统只有当用户加入到 微博 List中后, 才能进行群组 ^, 无法实现微博 List外用户对微博 List内 各成员的一对多^ 功能, 降低了用户的使用体验性, 降低了产品竟争力。
为此, 本发明实施例还提供一种微博消息的发布方法、 微博终端及微博 服务器端'
请参见图 27, 为本发明的微博终端的第一实施倒的结构示意图; 所述微 博终端包括:
微博消息管理模块 2701, 用于对微博消息进行管理, 当用户发布微博消 息时, 获取所迷用户待发布的微博消息, 并将所迷微博消息传送至微博服务 器端。
具体实现中, 用户使用注册的用户枨户和密码,通过微博终端的 IM客户 端登录到微博服务器端进行验证, 验证成功后, 微博终端与微博服务器端之 间建立连接通道, 所迷微博终端通过接入服务器接入到所述微博服务器端, 所述微博终端通过定时向所述微博服务器端发送心跣包的形式保证与所述微 博服务器端之间的连接。 所述微博终端可以显示用户的微博主页、 热门广播、 广播大厅或同城广播等广播消息界面、 用户的特定消息界面 (比如: @消息 界面)、 群组消息界面以及私信消息界面等, 所迷微博消息管理模块 2701 则 用于对用户的微博消息进行管理。 当所述用户的鼠标点击广播按键时, 所述 微博消息管理模块 2701响应所迷用户的鼠标操作,为所述用户创建广播窗口; 当所述用户在广播窗口中输入微博消息时, 所述微博消息管理模块 2701实时 监听所述用户的输入按键信息, 当监听到所述用户的鼠标点击发布按键时, 所述微博消息管理模块 2701根据监听的输入按键信息, 获取所迷广播窗口中 待发布的微博消息, 并将所述微博消息传送至微博服务器端。 可以理解的是, 所述微博消息管理模块 2701基于广播发表协议对所述获取的微博消息进行封 装、 加密等一系列处理后, 将其发送至微博服务器端。
需要说明的是, 所述特定消息队列是存放本发明实施例所述的包含特定 位置、 且该特定位置包含张号信息的微博消息的队列, 优选地, 所述特定消 息队列为@消息队列, @消息队列中的微博消息为:包舍 号信息的微博消息, 又称为: "@消息"、 "关于我的消息" 或 "提到我的消息"。 除特別说明外, 本发明后续实施例中所述的特定消息队列均指 @消息队列。
具体实现中, 所述微博消息管理模块 270ί还用于当本端用户作为微博群 组中的成员回复或转播 @消息队列中的微博消息时, 获取所述用户回复的内 容或转播的内容, 对所述微博群组帐号信息与所述回复的内容或转播的内容 进行封装, 生成回复消息或转播消息并传送至微博服务器端。
特定消息界面管理模块 2702, 用于接收所述微博服务器端发送的所述用 户的特定消息队列中的微博消息, 并在特定消息界面上显示所述用户的特定 消息队列中的微博消息。
具体实现中, 所述特定消息界面管理模块 2702优选为所述微博终端的@ 页管理模块, 用于对用户的@消息界面进行管理, 其可接收或拉取所述微博 服务器端推送的所述用户的@消息队列中的微博消息,通过@消息界面显示所 述用户的@消息队列中的所有微博消息。
本发明实施例可实现微博群组外用户对微博群组内各成员的一对多会 话, 方便微博用户进行信息传递, 提高了用户的^^体验。
请参见图 28, 为本发明的微博终端的第二实施例的结构示意图; 与上一 实施例相同, 所述微博终端包括: 微博消息管理模块 2701和特定消息界面管 理模块 2702。 本实施例中, 所述微博终端还包括:
微博群组 ( list )管理 2703, 用于对微博群组进行管理, 接收微博服 务器端发送的微博群组的广播队列中的微博消息, 并在群组消息页面中显示 所述微博群组的广播队列中的微博消息。
所述微博 List管理模块 2703主要对微博 List的创建、微博 List的基本信 息及微博 List的消息界面进行管理。本实施例中,所述微博 List管理模块 2703 接收或拉取微博服务器端推送的微博 List的广播队列中的微博消息, 并在群 组消息页面中显示微博群组的广播队列中的微博消息。
微博消息提醒模块 2704, 用于向所述用户提供所述用户的 @消息队列中 的微博消息、 和 /或所述微博群组的广播队列中的微博消息的展示提醒和查看 链接, 并当所迷用户对所述查看链接进 4亍操作时, 通知特定消息界面管理模 块 2702和/或所述微博群组管理模块 2703显示相应的微博消息。
具体实现中, 所述微博消息提醒模块 2704主要是当存在关于用户的新的 微博消息发布时, 提醒所述用户进行查看, 比如: 当有一条关于该用户的回 复信息时, 将该回复信息的链接提供给用户, 并提醒用户进行查看。 本实施 例中, 所述微博消息提醒 2704向所述用户提供所述用户的 @消息队列中 的微博消息、 和 /或所述微博群組的广播队列中的微博消息的展示提醒和查看 链接, 并当所述用户对所述查看链接进行操作(如: 点击该查看链接)时, 通知特定消息界面管理 4莫块 2702和 /或微博群组管理模块 2703在@消息界面 和 /或群组消息界面中显示相应的微博消息„
请参见图 29, 为本发明的微博服务器端的第一实施例的结构示意图; 所 述微博服务器端包括:
微博群組服务器 2901, 用于存储和管理微博群组的基本信息。
一般地, 所述徵博群组的基本信息包括但不限于: 群组怅号信息、 成员 帐号信息列表、 群组类型及群组标签属性。 所述微博群组服务器 2701与微博 终端的微博 List管理才 2703进行交互, 为所述微博 List管理模块 2703提 供对用户的微博群组的创建管理、基本信息和群组消息界面管理的各种服务, 该文互过程与现有技术相同, 在此不赘述。
微博消息服务器 2902, 用于检测第一微博终端发送的微博消息的特定位 置是否包含微博群组怅号信息, 若检测结杲为是, 将所述微博消息添加至所 述微博群组中各成员的特定消息队列中。
具体实现中, 所迷微博消息的特定位置为预设的正则表达式约定的位置。 微博服务器端与微博终端预先约定本实施例所述的微博消息的正则表达式, 比如: 号信息 +空格 +消息内容, 该正則表达式约定的特定位置为: 消息 内容之前的位置。 所迷微博消息服务器 2902接收到微博终端发送的微博消息 后, 首先检查该微博消息是否完整, 即检查该微博消息是否具备完整消息结 构(消息头及消息主体等结构), 如果确定该微博消息不完整, 确认该微博消 息无效, 所述微博消息服务器 2902则丢弃该微博消息; 如果确定该微博消息 完整, 确认该微博消息有效, 所述微博消息服务器 29CC 预设的正则表达 式, 基于正則匹配原則匹配该微博消息, 若该微博消息的格式不满足上述正 则表达式, 则匹配失敗, 所述微博消息服务器 2902按普通广播消息处理该微 博消息, 该处理过程与现有微博消息的广播过程相同, 在此不赘述。 若该微 博消息的格式满; L_L述正 表达式, 则匹配成功, 所述微博消息服务器 2902 将该微博消息的消息内容之前的部分确定为该微博消息的特定位置, 并从该 微博消息的特定位置提取帐号信息("@" 与 "空格" 之间的内容), 从所述 微博群组服务器 2901中检测该帐号信息是否为微博群组帐号信息, 若检测结 果为是, 所述微博消息服务器 2902将所述微博消息添加至所述微博群组中各 成员的 @消息队列中。 可以理解的是, 上述正則表达式仅为举例, 该表达式 中的 "@" 和 "空格" 的作用是为了把帐号信息与消息内容区分开来, 当然, 正则表达式可根据实际需要进行确定, 如: 字母 +怅号信息 +空格 +消息内容, 或者: 消息内容 +字母 +帐号信息 +空格, 或者: 消息内容+@ 号信息 +空^ 消息内容, 等等, 上述其他情况下可进行类似分析, 在此不赘述。
当所述徵博群组中的成员回复或转播所述成员的 @消息队列中第一用户 发布的微博消息时, 所述微博消息服务器 2902还用于接收所述成员对应的微 博终端发送的回复消息或转换消息, 根据所述回复消息或转播消息中的微博 群组帐号信息, 将所述回复消息或转播消息添加至所述微博群组的广播队列 中 , 并通知所迷微博消息推送服务器 2903将所述微博群组的广播队列中的微 博消息推送至所述第一微博终端进行发布, 实际应用中, 所述微博消息推送 服务器 2903将所述微博群组的广播队列中的微博消息推送至所述第一微博终 端进行发布的同时, 也会向其他收听所述微博群組的所有用户对应的微博终 端进行推送, 使其他收听所述微博群组的所有用户也可以查看所述微博群组 的广播队列中的微博消息。
微博消息推送服务器 2903,用于扫描所迷微博消息服务器 2902添加处理 后的所述微博群组中各成员的特定消息队列, 将所述微博群組中各成员的特 定消息队列中的微博消息推送至所述微博群组中各成员对应的微博终端上进 行发布。
具体实现中, 所述微博消息推送服务器 2903主要是中转各用户通过微博 终端转发给其他用户或微博群组的各种徵博消息或者相关数据包, 其可以实 时或定时扫描各用户的消息队列, 当发现消息队列中存在新的微博消息时, 向各用户推送所述消息队列中的微博消息。 本实施例中, 所述微博消息推送 服务器 2903将所述微博群组中各成员提供所述@消息队列中的微博消息推送 至各成员对应的微博终端后, 所迷微博群组中各成员对应的微博终端向所述 微博群组中各成员提供所述 @消息队列中的微博消息的展示提醒和查看链 接; 当所述微博群组中各成员对所述查看链接进行操作时, 所述微博群组中 各成员对应的微博终端在@消息界面上显示所述微博群组中各成员的@消息 队列中的微博消息。
利用本发明实施例的微博服务器端和微博终端可实现微博 List外用户对 微博 List内各成员的一对多 并可实现微博 Lis 内各成员对微博 List外 单个用户的多对一会话, 提高了用户的使用体验, 提升了产品竟争力。
请参见图 30, 为本发明的微博服务器端的第二实施例的结构示意图; 与 上一实施例相同, 所述微博服务器端包括: 微博群组服务器 2901、 微博消息 服务器 2902和微博消息推送服务器 2903。本实施例中, 所述微博服务器端还 包括:
微博用户服务器 2904, 用于存储和管理微博用户的基本信息。
一般地, 所述微博用户的基本信息包括但不限于: 用户怅号信息、 用户 类型、用户标签属性及认证信息。上一实施例中,若所述微博群组服务器 2901 检测到所述微博信息的特定位置包含的怅号信息并非微博群组帐号信息时, 则进一步从微博用户服务器 2904中查询该怅号信息是否为某单个用户的帐号 信息, 如果查询结杲为是, 所迷微博消息服务器 2902根据查询到的用户帐号 信息, 将所述微博消息添加至该用户的 @消息队列中, 并通知所述微博消息 推送服务器 2903将该用户的@消息队列中的微博消息推送至该用户的微博终
- 59 - 端进行发布,该查询到的用户的微博终端则在@消息界面中显示该用户的@消 息队列中的微博消息。 需要说明的是, 所述向单个微博用户发送微博消息的 过程与现有的向单个微博用户发送私信的过程类似。
可以理解的是, 若所迷微博群组服务器 2901确定徵博消息中的帐号信息 既不是微博群组帐号信息, 也不是单个用户的帐号信息, 则表明该微博消息 的特定位置既未包含微博群组帐号信息, 也未包含单个用户的帐号信息, 则 ^ 通广播消息处理该微博消息, 该处理过程与现有微博消息的广播过程相 同, 在此不赘述。
为了更清楚的说明本发明, 下面将对本发明的微博服务器端的微博消息 服务器 2902进 4于详细介绍。
请参见图 31 , 为本发明的微博消息服务器的实施例的结构示意图; 所述 微博消息服务器 2902包括:
解析单元 2921 , 用于根据正則匹配原则解析微博终端发送的微博消息, 确定与預设的正則表达式约定的位置相匹配的所述微博消息的特定位置。
具体实现中, 微博服务器端与微博终端预先约定本实施例所述的微博消 息的正則表达式, 比如: @ +帐号信息 +空福 +消息内容, 该正則表达式约定的 特定位置为: 消息内容之前的位置。 所述解析单元 2921接收到微博终端发送 的微博消息后, 首先检查该微博消息是否完整, 即检查该微博消息是否具备 完整消息结构(消息头及消息主体等结构), 如果确定该微博消息不完整, 确 认该微博消息无效, 所述解析单元 2921则丢弃该微博消息; 如杲确定该微博 消息完整,确认该微博消息有效,所述解析单元 2921根据领设的正則表达式, 基于正則匹配原則匹配该微博消息, 若该微博消息的格式不满足上述正則表 达式, 則匹配失敗, 所述解析单元 2921按普通广播消息处理该微博消息, 该 处理过程与现有徵博消息的广播过程相同, 在此不赘述。 若该微博消息的格 式满足上述正则表达式, 則匹配成功, 所述解析单元 2921将该微博消息的消 息内容之前的部分确定为该微博消息的特定位置„
可以理解的是, 由于所述微博终端基于广播发表协议对所述发送的微博 消息进行了封装、加密等一系列处理, 因此,所述解析单元 2921在解析之前, 还需要相应地对接收的微博消息进行解封装、 解密等一系列处理, 该处理过 程与现有技术相同, 在此不赘述。
检测单元 2922,用于根据所述解析单元 2921确定的所迷微博消息的特定 位置, 检测所述微博消息的特定位置是否包含微博群组帐号信息。
具体实现中, 所述检测单元 2922根据所述解析单元 292Ϊ确定的所述微 博消息的特定位置, 从该徵博消息的特定位置提取帐号信息("@"与 "空格" 之间的内容), 从所迷微博群组服务器 2901 中检测该帐号信息是否为微博群 组帐号信息。
第一操作单元 2923,用于当所述检测单元 2922 测结果为是时, 斤述 微博群组服务器中查询所述微博群组的成员帐号信息列表, 并根椐所述成员 帐号信息列表, 将所述微博消息添加至所述微博群组中各成员的特定消息队 列 (@消息队列) 中。
判断单元 2924,用于当所述检測单元 2922的检测结果为否时,判断所述 微博消息的特定位置是否包含第二用户怅号信息。
具体实现中,若所述检测单元 2922检测结果为否, 則所述判断单元 2924 进一步从微博用户服务器 2904中查询该怅号信息是否为某单个用户的帐号信 息。
第二操作单元 2925,用于当所述判断单元 2924判断结果为是时,根据所 述第二用户帐号信息, 将所迷微博消息添加至所述第二用户的特定消息队列 ( @消息队列 ) 中, 并通知所述微博消息推送服务器将所述第二用户的特定 消息队列中的微博消息推送至所述第二用户对应的第二微博终端进行发布。 可以理解的是, 若所述判断单元 2924的判断结杲为否, 則表明该微博消息的 特定位置既未包含微博群组怅号信息, 也未包含单个用户的帐号信息, 則按 普通广播消息处理该微博消息, 该处理过程与现有微博消息的广播过程相同, 在此不赘述。
需要说明的是, 本发明实施例中, 第一用户为微博系统中的任一微博用 户, 第二用户为除第一用户以外的任一微博用户。
本发明实施例可实现微博 List外用户对微博 List内各成员的一对多 , 并可实现微博 List内各成员对微博 List外单个用户的多对一会话, 提高了用 户的使用体驗, 提升了产品竟争力。
为了更清楚的说明本发明, 下面将对本发明的微博消息的发布方法进行 详细介绍。
请参见图 32, 为本发明的微博消息的发布方法的第一实施例的流程图; 所述方法包括:
S3201, 当第一用户发布微博消息时, 所述第一用户对应的第一微博终端 获取所述第一用户待发布的微博消息, 并将所述微博消息传送至微博服务器
具体实现中,用户使用注册的用户胀户和密码,通过微博终端的 IM客户 端登录到微博服务器端进行验证, 验证成功后, 微博终端与微博服务器端之 间建立连接通道, 所述微博终端通过接入服务器接入到所述微博服务器端, 所述微博终端通过定时向所述微博服务器端发送心跳包的形式保证与所述微 博服务器端之间的连接。 所述微博终端可以显示用户的微博主页、 热 Π广播、 广播大厅或同城广播等广播消息界面、 用户的 @消息界面、 群组消息界面以 及私信消息界面等, 所述微博终端对用户的微博消息进行管理。 所述微博终 端实时监听用户的鼠标操作, 当监听到所述用户的鼠标点击广播按键时, 所 述微博终端响应所述用户的鼠标操作,执行所述 S3201 ,为所述用户创建广播 窗口; 当所述用户在广播窗口中儉入微博消息时, 所述 S3201 实时监听所述 用户的输入按键信息, 当监听到所迷用户的鼠标点击发布按键时, 所述 S3201 根据监听的输入 ^:信息, 获取所述广播窗口中待发布的微博消息, 并将所 迷微博消息传送至微博服务器端。 可以理解的是, 所述 S3201 中, 所述微博 终端基于广播发表协议对所述获取的微博消息进行封装、 加密等一系列处理 后, 将其发送至微博服务器端, 本实施例中, 所述 S3201 中对所述微博消息 的处理过程和发送过程与现有技术类似, 在此不赘述。 53202, 所述微博服务器端检测所述微博消息的特定位置是否包含微博群 组帐号信息, 若检测结果为是, 所述微博服务器端将所述微博消息添加至所 述微博群組中各成员的特定消息队列 (@消息队列) 中。
具体实现中, 微博服务器端与微博终端预先约定本实施例所述的微博消 息的正则表达式, 比如: ^怅号信息 +空格 +消息内容, 该正則表达式约定的 特定位置为: 消息内容之前的位置。 所述微博服务器端接收到微博终端发送 的微博消息后, 首先检查该微博消息是否完整, 即检查该微博消息是否具备 完整消息结构(消息头及消息主体等结构), 如果确定该微博消息不完整, 确 认该微博消息无效, 所述服务器端则丢弃该微博消息; 如果确定该微博消息 完整, 确认该微博消息有效, 所述服务器端則执行 S3202,根据预设的正则表 达式, 基于正則匹配原則匹配该微博消息, 若该微博消息的格式不满足上迷 正则表达式, 則匹配失改, 所述服务器端按普通广播消息处理该微博消息, 该处理过程与现有微博消息的广播过程相同, 在此不赘述。 若该微博消息的 格式满足上述正则表达式, 则匹配成功, 所述 S3202将该微博消息的消息内 容之前的部分确定为该微博消息的特定位置, 并从该微博消息的特定位置提 取帐号信息("@" 与 "空格" 之间的内容), 检测该怅号信息是否为微博群 组帐号信息, 若检测结果为是, 所述 S3202将所述微博消息添加至所述微博 群组中各成员的@消息队列中。 可以理解的是, 上述正则表达式仅为举例, 该表达式可根据实际需要进行确定, 如: 字母 +帐号信息 +空格 +消息内容, 或 者: 消息内容 +字母 +帐号信息 +空格, 或者: 消息内容 +@+帐号信息 +空格 + 消息内容, 等等, 上述其他情况下可进行类似分析, 在此不赘述。
53203, 所述微博服务器端将所述微博群组中各成员的特定消息队列中的 微博消息推送至所述微博群组中各成员对应的微博终端上进行发布。
具体实现中, 所述 S3203将所述微博群组中各成员提供所述 @消息队列 中的微博消息推送至各成员对应的微博终端后, 所述微博群组中各成员对应 的微博终端向所述微博群组中各成员提供所述@消息队列中的微博消息的展 示提醒和查看链接; 当所述微博群组中各成员对所述查看链接进行操作时, 所述微博群组中各成员对应的微博终端在 @消息界面上显示所述微博群组中 各成员的@消息队列中的微博消息。
本发明实施例可实现微博 List外用户对微博 List内各成员的一对多^^, 方便微博用户进行信息传递, 提高了用户的 体验, 提升了产品竟争力。
请参见图 33, 为本发明的微博消息的发布方法的第二实施例的流程图; 所迷方法包括:
53301 , 当第一用户发布微博消息时, 所述第一用户对应的第一微博终端 获取所迷第一用户待发布的微博消息, 并将所述微博消息传送至微博服务器 端。
本实施例中, 所述 S3301与上一实施例的 S3201步骤相同, 在此不赘述。
53302, 所述微博服务器端根据正則匹配原则解析所述微博消息, 确定与 所述预设的正则表达式约定的位置相匹配的所述微博消息的特定位置。
具体实现中, 微博服务器端与微博终端预先约定本实施例所述的微博消 息的正則表达式, 比如: @+帐号信息 +空格 +消息内容, 该正则表达式約定的 特定位置为: 消息内容之前的位置。 所述微博服务器端接收到微博终端发送 的微博消息后, 首先检查该微博消息是否完整, 即检查该微博消息是否具备 完整消息结构(消息头及消息主体等结构), 如果确定该微博消息不完整, 确 认该微博消息无效, 所述微博服务器端则丢弃该微博消息; 如果确定该微博 消息完整,确认该微博消息有效, 所述服务器端则执行 S3302,根据预设的正 则表达式, 基于正则匹配原则匹配该微博消息, 若该微博消息的格式不满足 上述正则表达式, 则匹配失敗, 所迷 S3302按普通广播消息处理该微博消息, 该处理过程与现有微博消息的广播过程相同, 在此不赘述。 若该微博消息的 格式满足上述正则表达式, 则匹配成功, 所述 S3302将该微博消息的消息内 容之前的部分确定为该微博消息的特定位置。
S3303, 所述微博服务器端检测所述微博消息的特定位置是否包含微博群 组帐号信息, 若检测结果为是, 转入 S3304; 否则, 转入 S3309。
具体实现中, 所述 S3303所迷 S3303确定的所述微博消息的特定位置, 从该微博消息的特定位置提取帐号信息("@" 与 "空格" 之间的内容), 从 所述微博服务器端的微博群组服务器中检測该帐号信息是否为微博群组帐号 信息。
53304, 所述微博服务器端根据所述微博群組帐号信息, 询所述微博群組 的成员帐号信息列表。
53305, 所 iiJl务器端根据所述成员帐号信息列表, 将所述微博消息添加 至所述微博群组中各成员的@消息队列中。
53306, 所述微博服务器端扫描所述微博群组中各成员的 @消息队列, 将 所述微博群组中各成员的 @消息队列中的微博消息推送至所述微博群组中各 成员对应的微博终端。
53307, 所述微博群组中各成员对应的微博终端向所迷微博群组中各成员 提供所述@消息队列中的微博消息的展示提醒和查看链接。
53308, 当所述微博群组中各成员对所述查看链接进行操作时, 所述微博 群组中各成员对应的微博终端在@消息界面上显示所述微博群组中各成员的 @消息队列中的微博消息; 之后转入结束,
本实施例中, S3306^S3308为上一实施例的 S3203的具体细化步骤。
53309, 所述微博服务器端判断所述微博消息的特定位置是否包含第二用 户帐号信息, 若判断结果为是, 转入 S3310; 否则, 结束。
具体实现中, 若所述 S3303检测结果为否, 则所迷微博服务器端执行 S3309,进一步从所述微博服务器端的微博用户服务器中查询该帐号信息是否 为某单个用户的帐号信息。
53310, 所述微博服务器端根据所述第二用户帐号信息, 将所述微博消息 添加至所述第二用户的@消息队列中。
53311, 所述微博服务器端扫描所迷第二用户的 @消息队列, 将所述第二 用户的 @消息队列中的微博消息推送至所述第二用户对应的第二微博终端。
53312, 所述第二微博终端在 @消息界面上显示所述第二用户的@消息队 列中的微博消息; 之后转入结束。 需要说明的是, 本发明实旄例中, 第一用户为微博系统中的任一微博用 户,第二用户为除第一用户以外的任一微博用户。可以理解的是,若所述 S3309 的判断结果为否, 則表明该微博消息的特定位置既未包含微博群組帐号信息, 也未包含单个用户的帐号信息, 則按普通广播消息处理该微博消息, 该处理 过程与现有微博消息的广播过程相同, 在此不赘述。
本实施例中, S3302-S3305, S3309-S3312为上一实施例的 S3202的具体 细化步骤。
本发明实施例可实现微博 List外用户对微博 List内各成员的一对多 , 并可实现微博 List内各成员对微博 List外单个用户的多对一^^ 提高了用 户的使用体验, 提升了产品竟争力。
请参见图 34, 为本发明的微博消息的发布方法的第三实施例的流程 S; 所述方法包括:
53401 , 当第一用户发布微博消息时, 所述第一用户对应的第一微博终端 获取所迷第一用户待发布的微博消息, 并将所述微博消息传送至微博服务器
¾。
53402, 所述微博服务器端检测所迷微博消息的特定位置是否包含微博群 组帐号信息, 若检测结果为是, 所述微博服务器端将所迷微博消息添加至所 述微博群组中各成员的@消息队列中。
53403, 所述微博服务器端将所述微博群组中各成员的@消息队列中的微 博消息推送至所迷微博群组中各成员对应的微博终端上进行发布。
本实施例中, S3401-S3403与图 32所示实施例中的 S320i^S3203步猓相 同, 在此不赘述。
53404, 当所述微博群组中的成员回复或转播所迷成员的@消息队列中所 述第一用户发布的微博消息时, 所迷成员对应的微博终端获取回复的内容或 转播的内容。
53405, 所述成员对应的微博终端对所述微博群组帐号信息与所述回复的 内容或转播的内容进行封装, 生成回复消息或转播消息并传送至所述微博服 务器端。
具体实现中, 所述 S3405与现有微博消息的回复或转播的处理过程类似, 首先提取回复或转播的消息源的帐号信息, 然后获取用户回复的内容或转播 的内容, 将提取的怅号信息与回复的内容或转播的内容进行封装, 生成最终 的回复消息或转播消息,
53406, 所述微博服务器端根据所述回复消息或转播消息中的微博群組帐 号信息, 将所述回复消息或转播消息添加至所述微博群组的广播队列中。
53407, 所述微博服务器端扫描所述微博群组的广播队列, 将所述微博群 組的广播队列中的微博消息推送至所述第一微博终端。
实际应用中, 所述微博服务器端执行 S3407的同时, 还会向其他收听所 迷微博群组的所有用户对应的微博终端进行推送, 使其他收听所述微博群组 的所有用户均可以查看所迷微博群组的广播队列中的微博消息。
53408, 所述第一微博终端在群组消息页面中显示所述微博群組的广播队 列中的微博消息。
本实施例的 S3404~S3408 中, 微博群组中的成员以微博群组消息的形式 进行消息的回复或转播, 实现了微博群组对单个微博用户的多对一的广播传 播。
本发明实施例可实现微博 List外用户对微博 List内各成员的一对多 ^, 并可实现微博 List内各成员对微博 List外单个用户的多对一 ^¾", 提高了用 户的使用体验, 提升了产品竟争力.
通过上述实施例的描述, 本发明实施例的用户可在待发布的微博消息中 输入微博群组帐号信息, 微博服务器端对该待发布的微博消息进行检测, 当 检测到该微博消息的特定位置包含微博群组怅号信息时, 則将所述微博消息 添加至所述微博群组中各成员的特定消息队列 (比如: @消息队列) 中, 并 将所述微博群组中各成员的特定消息队列中的微博消息推送至所述微博群组 中各成员对应的微博终端上进行发布, 实现了单个微博用户 (微博群组内用 户或微博群组外用户)对徵博群组内各成员的一对多^■, 提高了用户的使 用体验, 提升了产品竟争力; 另外, 微博群组内的各成员可针对接收到的特 定消息队列中的微博消息进行回复或转播, 各成员对应的微博终端对微博群 组帐号信息与回复的内容或转播的内容进行封装, 生成回复消息或转播消息 并发送至微博服务器端, 由微博服务器端根据微博群组帐号信息, 将各成员 的回复消息或转播消息添加至微博群组的广播队列中并推送至发送方(单个 微博用户), 实现了微博群组对单个微博用户 (微博群组内用户或微博群组外 用户)的多对一会话, 进一步提升了产品竟争力。
在现有 IM软件中的群组功能, 是通过如下方式实现的, 该方式包括: 用 户获取需要加入的用户群组信息, 通过客户端向服务器发送加入请求, 所述 加入请求中包含该用户 ID和需要加入用户群组信息;服务器接收该加入请求, 根据该用户群组信息向所述用户群组的管理员发送加入请求通知, 在用户群 组的管理员同意后该用户便可以加入该用户群组。
IM软件中的群组功能属于一个封闭的用户聚合体, 用户只能在获知其要 加入的用户群组信息后, 才能申请加入其想要加入的用户群纽, 并且其他用 户无法给某个群组推荐其他用户。
为此, 本发明实施例还提供一种微博整合方法、 微博终端、 微博列表、 微博话 ¾J¾务器及系统。
参照图 35, 提出本发明一种微博整合方法的一实施例。 该微博整合方法 可包括:
步骤 350、微博终端根据话题内容查询微博话 ¾ϋ 务器, 获取话题的话题 标识;
步骤 351、发送建立上述话題与上述微博终端所属的微博列表关联关系的 建立指令至微博列表服务器和 /或微博话题服务器; 上述建立指令的内容包括 话题标识以及微博列表标识; 所迷关联关系包括映射关系和 /或收听关系; 步骤 352、微博列表服务器根据上述微博列表标识, 查找与微博列表标识 对应的数据内容, 并将上述话题标识写入至上述数据内容, 建立映射关系; 和 /或, 步猓 S353 微博话題服务器获取所述话題的话题标识, 查找与话题标识 对应的数据内容, 并将所述微博列表标识写入至所述数据内容, 建立收听关 系。
本实施例中的微博 (系统)主要可包括微博终端和微博后台服务器群; 该微博终端主要包括微博消息管理模块、 微博列表(List )管理模块以及微博 话題管理模块等; 该微博后台服务器群可包括微博话 ^良务器、 微博列表服 务器、 微博消息服务器以及微博终端服务器等。 其中, 上述微博终端与微博 后台服务器群可通过接 All务器连接通讯。
上迷微博消息管理模块可根据微博消息的标识(ID )拉取消息与解析消 息内容, 并创建相关的消息界面展示消息内容; 上述微博列表管理模块可用 于微博列表的创建、 劂除、 基本资料管理以及列表成员 (微博终端)的管理 等; 上述微博话題管理模块可主要用于话题的收听与取消, 收听话题列表的 与存储管理, 以及对应某个话題的所有消息的标识列表拉取等。
微博终鴣服务器主要用于保存微博终端的收听关系、 基本资料、 终端类 型、 终端标签属性以及是否认证等终端基本信息; 微博列表服务器主要用于 存储与管理与微博列表关联的数据内容, 以及对于创建微博列表、 设置微博 列表资料相关信令的操作管理等; 微博消息服务器主要用于管理微博消息索 引与消息体之间的映射关系, 使微博终端可以用微博索引拉取到对应的消息 体; 微博话 ¾J艮务器主要用于对终端创建话題的管理, 对话题对应的消息标 识列表以及话题标识与话题内容之间映射关系的管理等。
微博列表的创建者对应的微博终端, 可发送查询话题(比如热门话题列 表)的指令到微博话¾1艮务器, 该微博话¾1 务器可根据当前与之关联消息 最多的话题列表返回给该微博终端。 如此, 该微博终端可以设置微博列表与 话題的收听关系, 可以选择相应的话题发送请求至微博话 ¾ ^务器进行收听, 使微博列表中所有微博终端都可收听该话题(或者, 该微博终端直接发送请 求至微博话题服务器, 收听相应话题)。 所有徵博终端即可通过话题标识查询 微博话題服务器, 获取该话題对应的微博列表标识列表的协议命令, 通过微 博列表标识查询微博列^ Jil务器, 则可展示出与该话题对应的微博列表的名 称以及筒介类信息等。
上述微博列表与话題收听关系, 可以是由微博列表的创建者对应的微博 终端, 发送建立上迷话题与上述银博终端所属的微博列表收听关系的建立指 令至微博话 ¾ 务器; 上述建立指令的内容包括话题标识以及微博列表标识; 微博话 ¾ ^务器根据所述话题标识, 查找与话题标识对应的数据内容, 并将 所述微博列表标识写入至所迷数据内容, 建立收听关系。 该与话題对应的数 据内容可包括: 名称、 描述以及话題的收听列表等。
微博列表的创建者对应的微博终端也可选择相应的话 ¾ 立映射关系。 该微博终端将根据话题内容查询微博话题服务器, 获取话題的话題标识; 然 后, 发送建立上述话題与该微博终端所属(创建)的徵博列表映射关系的建 立指令至微博列表服务器; 该建立指令的 f¾容至少包括话题标识以及该微博 列表的微博列表标识等; 上述微博列表服务器根据该微博列表标识, 查找与 微博列表标识 应的数据内容, 并将上述话题标识写入至查找到的数据内容, 以此建立话題与该微博列表之间的映射关系。 该与微博列表标识对应的数椐 内容可包括: 名称、 描迷、 标签、 权限、 成员以及关联的话题等。
参照图 36' 上述步骤 S352 ^还可包括:
步骤 S3520、微博消息服务器将微博列表的微博成员发送的微博消息,发 送至与微博列表具有玦射关系的话题的消息列表。
上述步骤 S3520具体包括: 微博消息服务器获取上述微博成员对应的微 博列表标识, 查看与微博列表标识具有映射关系的话题标识, 将上述微博消 息写入至上述话题标识的消息列表。
在上述话题与微博列表之间的映射关系建立后, 微博列表中所有微博终 端发表的微博消息会自动加入到该话題对应的消息列表中, 通过在微博列表 服务器中微博列表标识对应的数据内容中建立与之有狭射关系的话題列表, 当利用微博终端操作映射关系时候, 则通过数据包(微博消息)协议插入到 对应的映射关系列表中。 当微博列表中的微博成员 (微博终端)发表微博消息的时候, 微博消息 服务器获取到发送该微博消息的微博终端, 查询微博列表服务器获取到对应 该微博终端的微博列表标识的列表, 通过遍历循环微博列表标识的列表查看 与该博列表有映射关系的话題标识的列表; 再通过遍历循环该话题标识的列 表, 写入该微博终端发表微博消息的消息标识到对应该话题的消息标识列表 之中。 如此, 当其他微博终端查询对应该话題的消息的时, 就可以查询到与 该话题已经建立映射关系的微博列表中的微博终端发表的微博消息的消息列 表, 建立了一种微博列表的微博终端发表的徵博消息与话題之间的关联关系。
参照图 37, 上述步骤 之后还包括:
步骤 S3531、微博消息服务器对接收的微博消息进行解析,获取话题内容 并查询是否存 同的话題内容;
步霖 S3532、 如存在, 微博消息服务器发送插入指令至微博话题服务器, 将话题内容插入至相应的话题的消息列表;
步骤 S3533、如不存在,微博话题服务器根据上述话题内容建立新的话题。 微博终端可利用微博消息管理模块在广播发表窗口中创建相关的话题进 行微博消息的发表; 微博消息服务器可接收微博终端发表的微博消息, 并对 微博消息的内容进行解析, 按照话题正则 (表达式)规则获取到微博消息中 的话题内容, 利用话题内容查询话题数据表确认当前是否存在完全匹配的话 题内容。 如果已经存在, 則徵博消息服务器发送插入消息标识到话题消息列 表的指令到微博话 ¾ ^务器, 该微博话 ¾m务器可根据话题内容确认话题标 识, 并写入微博消息对应的消息标识到与话题关联的消息(标识)列表中; 如果不存在, 则微博话题服务器生成新的话題标识并插入对应的话题内容, 建立新的话题。
上述微博终端包括但不限于 IM ( InstantMessaging, 即时通讯)客户端、 网頁微博终端以及 WAP ( Wreless Ai¾)Hcation Protocol, 为无线应用格议)终 端等, 以下将以 IM客户端为例说明上述微博整合方法的具体实现。 上述 IM 客户端可以提供相关的操作、 交互界面。 IM客户端将与 IM客户端对应的微博账号与密码发送到微博终端服务器 验证登录成功后, 則建立起与微博终端服务器之间的连接通道, 并且通过定 时发送心跳包的形式保证与微博终端服务器的连接。
IM客户端通过、 微博消息管理模块监听用户的鼠标点击操作, 创建广播 发表窗口,用户点击"插入话题"按钮, 即可调用输入控件插入话题的标志" #", 用户可以在两个#之间输入话题内容(比如: #话题内容 # ), 用户还可以在其 他的输入区域输入其他消息内容。
用户点击发送按叙的时候, 則提取出输入框中的消息内容, 组合到数据 包中进行加密后发送到微博消息服务器。
微博消息服务器接 消息内容后, 解析确认有效数据包后, 则生成对 应该消息内容的消息索引标识, 并^到对应该用户的发表消息的消息标识 列表之中, 同时对消息内容进行解析, 按照话题(# )的正则规则进行匹配解 析获取到话题内容, 发送查询话題的指令到微博话题服务器。
微博消息服务器通过微博话 ¾^务器根据该话题内容, 查询话題数据表 确认是否已经存在该话题内容, 如果已经存在, 微博话题服务器将话题内容 插入至已存在的话题的消息列表; 如不存在, 微博话题服务器根据上述话題 内容建立新的话题。
微博列表的创建者对应的微博终端发送建立收听关系的指令到微博话题 服务器, 对该话题进行收听。 微博列表中的微博终端, 则可展示出与该话題 对应的微博列表的名称以及筒介类信息等。
微博列表的创建者对应的微博终端也可选择相应话题建立映射关系。 当 利用微博列表中的微博终端操作映射关系时候, 則通过数据包(微博消息) 协议插入到对应的映射关系列表中。 微博列表的微博终端发送的微博消息, 通过微博消息服务器, 发送至与微博列表具有映射关系的话题的消息列表。
通过上述微博整合方法, 可以通过微博的话題展示方式查看到与该话题 有关的微博列表, 从而可以从话题中查找到与话题相关的微博列表进行收听 或者试听操作; 同时, 微博列表的创建者可以通过建立一个话題与微博列表 的映射关系, 使微博列表成员 (微博终端)发表的微博消息会自动进入与该 话題相关的消息列表中; 如此, 收听该话題的微博终端就可以查看对应微博 列表成员发表的微博消息, 实现了微博的话題与微博列表之间的整合, 使微 博终端可获取更丰富的资源, 提升了用户体验。
参照图 38, 提出本发明一种微博终端的一实施例 该微博终端 380可包 括:
获 ^块 382,用于根据话題内容查询微博话 务器,获取话题的话题 标识;
指令发送模块 383,用于发送建立上述话题与上述微博终端 380所属的微 博列表关联关系的建立指令至微博列表服务器和 /或微博话題服务器; 上迷建 立指令的内容包^ "题标识以及微博列表标识; 上述关联关系包括映射关系 和 /或收听关系;
请求写入模块 384, 用于根据上述微博列表标识,通过微博列 良务器查 找与微博列表标识对应的数据内容, 并将上述话题标识写入至上述数据内容, 建立映射关系; 和 /或,
用于通过微博话 ¾1艮务器获取所述话题的话题标识, 查找与话题标识对 应的数据内容, 并将所述微博列表标识写入至所述数据内容, 建立收听关系。
微博列表的创建者对应的微博终端 380,可通过指令发送模块 383发送查 询话题(比如热门话题列表)的指令到微博话¾1艮务器, 该微博话题服务器 可根据当前与之关联消息最多的话题列表返回给该微博终端 380。如此, 该微 博终端 380可以设置微博列表与话题的收听关系, 可以选择相应的话题发送 请求至微博话 ¾5艮务器进行收听, 使微博列表中所有微博终端 380都可收听 该话題(或者, 该微博终端 380直接通过建立收听模块 381发送请求至微博 话¾11务器, 收听相应话題)。 所有微博终端 380即可通过话题标识查询微博 话题服务器, 获取该话題对应的微博列表标识列表的协议命令, 通过微博列 表标识查询微博列表服务器, 则可展示出与该话题对应的微博列表的名称以 及简介类信息等。 上述微博列表与话題收听关系, 可以是由微博列表的创建者对应的微博 终端 380,发送建立上述话题与上述微博终端 380所属的微博列表收听关系的 建立指令至微博话题服务器; 上述建立指令的内容包括话题标识以及微博列 表标识; 微博话 ¾ΛΙ务器根据所述话题标识, 查找与话题标识对应的数据内 容, 并将所述微博列表标识写入至所述数据内容, 建立收听关系。 该与话题 对应的数据内容可包括: 名称、 描迷以及话題的收听列表等。
微博列表的创建者对应的微博终端 380也可选择相应的话题建立映射关 系。 该微博终端 380将通过获 # ^块 382根据话题内容查询微博话 ¾Λ务器, 获取话题的话題标识; 然后, 利用指令发送模块 383发送建立上述话题与该 微博终端 380所属(创建)的微博列表决射关系的建立指令至微博列 务 器; 该建立指令的内容至少包括话題标识以及该微博列表的微博列表标识等; 再是, 通过微博列表服务器使用请求写入模块 384根据该微博列表标识, 查 找与微博列表标识对应的数据内容, 并将上述话题标识写入至查找到的数据 内容, 以此建立话題与该微博列表之间的映射关系。 该与微博列表标识对应 的数据内容可包括: 名称、 描迷、 标签、 权限、 成员以及关联的话题等。
上述微博终端 380,可以通过微博的话题展示方式查看到与该话题有关的 微博列表, 从而可以从话題中查找到与话题相关的微博列表进行收听或者试 听操作; 同时, 微博列表的创建者可以通过建立一个话题与微博列表的缺射 关系, 使微博列表成员发表的微博消息会自动进入与该话题相关的消息列表 中; 如此, 收听该话題的微博终端 380就可以查看对应微博列表成员发表的 微博消息, 实现了微博的话题与微博列表之间的整合, 吏微博终端可获取更 丰富的资源, 提升了用户体验。
参照图 39, 提出本发明一种微博列^务器 390的一实施例。 该徵博列 ^J 务器 390可包括:
列表指令接收模块 391,用于接收微博终端 380发送的建立上述话题与上 述微博终瑞 380 所属的微博列表映射关系的建立指令; 上述建立指令的内容 包括话题标识以及微博列表标识; 列表查找模块 392,用于根据上述微博列表标识,查找与微博列表标识对 应的数据内容, 并将上述话题标识写入至上述数据内容。
该微博终端 380将根据话题内容查询微博话题服务器, 获取话题的话題 标识; 然后, 发送建立上述话题与该微博终端 380所属(创建)的微博列表 映射关系的建立指令至微博列^ 务器 3 0;该建立指令的内容至少包 题 标识以及该微博列表的微博列表标识等; 该微博列表服务器 390通过列表指 令接收模块 391接收该建立指令,再利用列表查找模块 392,根据该微博列表 标识, 通过微博列^!艮务器 390查找与微博列表标识对应的数据内容, 并将 上述话题标识写入至查找到的数据内容, 以此建立话题与该微博列表之间的 映射关系, 该与微博列表标识对应的数据内容可包括: 名称、 描述、 标签、 权限、 成员以及关联的话题等。
参照图 40, 提本发明一种微博话题服务器的一实施例„ 该微博话 1务 器 4000包括:
话题指令接收模块 4001, 用于接收微博终端 380发送建立所述话题与所 述微博终端所属的微博列表收听关系的建立指令; 所述建立指令的内容包括 话题标识以及微博列表标识;
话题查找模块 4002, 用于获取所迷话题的话题标识, 查找与话題标识对 应的数据内容, 并将所述微博列表标识写 ^所述数据内容, 建立收听关系。
上述微博列表与话題收听关系, 可以是由微博列表的创建者对应的微博 终端 380,发送建立上述话題与上迷微博终端所属的微博列表收听关系的建立 指令至微博话題服务器 4000; 上述建立指令的内容包括话题标识以及微博列 表标识;上述话題指令接收模块 400Ϊ接收该建立指令,利用话題查找 ·4002 根据所述话题标识, 查找与话题标识对应的数据内容, 并将所述微博列表标 识写入至所述数据内容, 建立收听关系。 该与话题对应的数据内容可包括: 名称、 描述以及话题的收听列表等,
参照图 41 , 提出本发明一种微博系统的一实施例。 该微博系统包括微博 终端 380, 微博话题服务器 4000以及微博列表服务器 3S ), 该微博终端 380 用于:
根据话题内容查询微博话舰务器 4000, 获取话題的话題标识; 发送建立上迷话题与上述微博终端 380所属的微博列表关联关系的建立 指令至微博列表服务器 390和 /或微博话¾1艮务器 4000; 上述建立指令的内容 包括话题标识以及微博列表标识;所述关联关系包括映射关系和 /或收听关系; 上述微博列 务器 390用于:
根据上述微博列表标识, 查找与微博列表标识对应的数据内容, 并将上 述话題标识写入至上述数据内容, 建立块射关系; 和 /或,
所述微博话 ¾^务器 4000用于:
获取所述话题的话題标识, 查找与话题标识对应的数据内容, 并将所述 微博列表标识写 所述数椐内容, 建立收听关系。
微博列表的创建者对应的微博终端 380,可发送查询话题(比如热门话题 列表)的指令到微博话 «I务器 4000,该微博话¾1 务器 40(K)可根据当前与 之关联消息最多的话题列表返回给该微博终端 380。如此,该微博终端 380可 以设置微博列表与话题的收听关系, 可以选择相应的话题发送请求至微博话 题服务器 4000进行收听,使微博列表中所有微博终端 380都可收听该话题(或 者, 该微博终端 380直接发送请求至微博话¾8艮务器 4(½0, 收听相应话題)。 所有微博终端 380即可通过话题标识查询微博话题服务器 4000, 获取该话题 对应的微博列表标识列表的协议命令, 通过微博列表标识查询微博列表服务 器 390, 则可展示出与该话題对应的微博列表的名称以及筒介类信息等。
上述微博列表与话題收听关系, 可以是由微博列表的创建者对应的微博 终端 380,发送建立上述话题与上述微博终端 380所属的微博列表收听关系的 建立指令至微博话 ¾良务器 4000; 上述建立指令的内容包括话题标识以及微 博列表标识; 微博话题服务器 4000根据所述话題标识, 查找与话题标识对应 的数据内容, 并将所述微博列表标识写入至所述数据内容, 建立收听关系。 该与话题对应的数据内容可包括: 名称、 描述以及话题的收听列表等。
微博列表的创建者对应的微博终端 380也可选择相应的话题建立映射关 系。 该微博终端 380将根! ^题内容查询微博话 ¾i 务器 4000, 获取话题的 话題标识; 然后, 发送建立上述话题与该微博终端 380所属(创建)的微博 列表映射关系的建立指令至微博列^良务器 390;该建立指令的内容至少包括 话题标识以及该微博列表的微博列表标识等; 再是,上述微博列^ I良务器 390 根据该微博列表标识, 查找与微博列表标识对应的数据内容, 并将上述话题 标识写入至查找到的数据内容, 以此建立话题与该微博列表之间的映射关系。 该与微博列表标识对应的数据内容可包括: 名称、 描述、 标签、 权限、 成员 以及关联的话题等„
上述微博系统还包括:微博消息服务器 410,用于将微博列表中的微博成 员发送的微博消息, 发送至与微博列表具有映射关系的话题的消息列表。
上述微博消息服务器 410具体用于: 获取上述微博成员对应的微博列表 标识, 查看与微博列表标识具有映射关系的话題标识, 将上述微博消息写入 至上述话題标识的消息列表,
在上述话题与微博列表之间的映射关系建立后, 微博列表中所有微博终 端 380发表的微博消息会自动加入到该话题对应的消息列表中, 通过在微博 列 艮务器 390 中微博列表标识对应的数据内容中建立与之有映射关系的话 题列表, 当利用微博终端 380操作映射关系时候, 则通过数据包(微博消息) 协议插入到对应的映射关系列表中。
当微博列表中的微博成员 (微博终端 380 )发表微博消息的时候,微博消 息服务器 410获取到发送该微博消息的微博终端 380, 查询微博列表服务器 390获取到对应该微博终端 380的微博列表标识的列表,通过遍历循环微博列 表标识的列表查看与该博列表有块射关系的话题标识的列表; 再通过遍历循 环该话题标识的列表, 写入该微博终端 380发表微博消息的消息标识到对应 该话题的消息标识列表之中。 如此, 当^ &微博终端 380查询对应该话题的 消息的时, 就可以查询到与该话題已经建立映射关系的微博列表中的微博终 端 380发表的微博消息的消息列表, 建立了一种微博列表的微博终端 380发 表的微博消息与话題之间的关联关系。 上述微博消息服务器 410还用于: 对接收的微博消息进行解析, 获取话 题内容并通过微博话题服务器 4000查询是否存在相同的话题内容;在存在时, 发送插入指令至微博话题服务器 4000, 将话题内容插入至相应的话题的消息 列表;
上述微博话 ¾艮务器 40O)还用于: 在不存在时, 根据上述话题内容建立 新的话题。
微博终端 380可利用微博消息管理模块在广播发表窗口中创建相关的话 題进行微博消息的发表; 微博消息服务器 410可接收微博终端 380发表的微 博消息, 并对微博消息的内容进行解析, 按照话题正则 (表达式)规则获取 到微博消息中的话題内容, 利用话題内容查询话題数据表确认当前是否存在 完全匹配的话题内容。 如果已经存在, 则徵博消息服务器 410发送插入消息 标识到话题消息列表的指令到微博话题服务葬 4000, 该微博话¾1良务器 4000 可根据话题内容确认话题标识, 并写入微博消息对应的消息标识到与话题关 联的消息(标识)列表中; 如杲不存在, 则微博话¾ ^务器 4000生成新的话 题标识并插 应的话题内容, 建立新的话题。
上述微博系统, 可以通过微博的话题展示方式查看到与该话题有关的微 博列表, 从而可以从话题中查找到与话题相关的微博列表进行收听或者试听 操作; 同时, 微博列表的创建者可以通过建立一个话题与微博列表的映射关 系, 使微博列 Μ·员发表的微博消息会自动 ¾ ^与该话題相关的消息列表中; 如此, 收听该话题的微博终端 380就可以查看对应微博列 员发表的微博 消息, 实现了微博的话题与微博列表之间的整合, 使微博终端 380 可获取更 丰富的资源, 提升了用户体验。
通过以上实施方式的描述, 本领域的技术人员可以清楚地了解到本发明 可借助软件加必需的硬件平台的方式来实现, 当然也可以全部通过硬件来实 施。 基于这样的理解, 本发明的技术方案对背景技术做出贡献的全部或者部 分可以以软件产品的形式体现出来, 该计算机软件产品可以存储在存储介质 中, 如 ROM/RAM、 磁碟、 光盘等, 包括若千指令用以使得一台计算机设备
-a- (可以是个人计算机, 服务器, 或者网络设备等)执行本发明各个实施例或 者实施例的某些部分所述的方法。
以上所述, 仅为本发明的具体实施方式, 但本发明的保护范困并不局限 于此, 任何熟悉本技术领域的技术人员在本发明揭露的技术范围内, 可轻易 想到的变化或替换, 都应涵盖在本发明的保护范围之内。 因此, 本发明的保 护范围应以权利要求的保护范围为准。

Claims

权利要求书
1、 一种微博名单传播的实现方法, 其特征在于, 包括:
终端接收用户提供的微博名单分享指令;
根据待分享的微博名单的基本信息自动生成微博名单分享消息;
将所述微博名单分享消息进行发布。
2、 根据权利要求 1所述的微博名单传播的实现方法, 其特征在于, 在所述 根据待分享的微博名单的基本信息自动生成微博名单分享消息之前, 还包括: 从微博服务裟上获取某一用户参与的至少一个微博名单的基本信息。
3、 根据权利要求 1或 2所述的微博名单传播的实现方法, 其特征在于, 所 述微博名单的基本信息至少包括: 所述微博名单的名称和所述微博名单对应的 网址。
4、 根据权利要求 1所述的微博名单传播的实现方法, 其特征在于, 所述待 分享的微博名单为用户当前打开的微博名单。
5、 根据权利要求 1所述的微博名单传播的实现方法, 其特征在于, 所述待 分享的微博名单为用户所参与的所有微博名单中的至少一个微博名单。
6、 根据权利要求 5所述的微博名单传播的实现方法, 其特征在于, 在所述 接收用户提供的微博名单分享指令之后, 且在所迷根据待分享的微博名单的基 本信息自动生成微博名单分享消息之前, 还包括:
向所述用户展示该用户所参与的所有微博名单的列表, 以便于该用户选择 其中的至少一个微博名单; 接收用户所选的至少一个微博名单的信息;
所述根据所述微博名单的基本信息自动生成微博名单分享消息为: 根据用 户所选的至少一个微博名单对应的基本信息自动生成微博名单分享消息。
7、 一种管理用户群组成员的方法, 其特扭在于, 包括:
服务器接收客户端发送的推荐用户加入到預定用户群组的推荐加入协议命 令, 所述推荐加入协议命令中包含被推荐用户标识 ID和预定用户群组 ID; 根据所述预定用户群组 Π 确定所述预定用户群组的创建用户, 并向所述创 建用户发送推荐加入通知消息, 以便所述创建用户确定是否将被推荐用户加入 到所述预定用户群组中;
当接收到所述创建用户发送的同意将所述推荐用户加入到所述预定用户群 组中的响应消息时,将所迷被推荐用户 ID添加到所述预定用户群组的成员列表 中。
8、 根据权利要求 7所述的方法, 其特征在于, 所述推荐协议命令中还包括 推荐用户 ID,在根据所述预定用户群组 ID确定所述预定用户群组的创建用户之 后, 该方法还包括:
根据所述推荐用户 Π>确定所述预定用户群組的创建用户是否为所述推荐用 户;
若所述预定用户群组的创建用户为所述推荐用户, 则直接将所述被推荐用 户 ID添加到所述顸定用户群组的成员列表中;
若所述预定用户群组的创建用户不是所迷推荐用户时, 則执行所述向所述 创建用户发送推荐加入通知消息, 以便所述创建用户确定是否将被推荐用户加 入到所述预定用户群組。
9、根据权利要求 7或 8所述的方法, 其特征在于, 在将所述被推荐用户 Π 添加到所述预定用户群组的成员列表中之后, 还包括:
向所述推荐用户发送被推荐用户已被预定用户群组收录的通知消息; 和 /或 向所述被推荐用户发送其已被推荐收录到预定用户群組的通知消息。
10、 根据权利要求 7或 8所述的方法, 其特狃在于, 所述推荐加入协议命 令中包含的被推荐用户 ID为一个被推荐用户 ID或者多个被推荐用户 Π, 所述 多个被推荐用户 ID以被推荐用户 ID列表的形式包含在所述推荐加入协议命令 中;
当所述推荐加入协议命令中包含被推荐用户 ID列表时, 将所述被推荐用户 Π 列表中的每个被推荐用户逐一进行推荐加入操作。 11、 根据权利要求 7所述的方法, 其特征在于, 还包括: 接收客户端发送的获取 ID列表协议命令, 所述获取 ID列表协议命令用于 获取所述用户创建或者加入的用户群纽 ID列表, 所述获取 ID列表协议命令中 包含所述用户 Π ;
根据所述用户 I 获取所述用户创建或者加入的用户群组 ID列表, 并将所 述用户群组 ID列 ½送给所述客户端。
12、 根据权利要求 7所述的方法, 其特征在于, 还包括:
客户端获取向预定用户群組推荐加入的被推荐用户 ID;
客户端向服务器发送推荐用户加入到预定用户群組的推荐加入协议命令, 所述推荐加入协议命令中包^ ϋ推荐用户 ID和领定用户群组 ID。
13、 根据权利要求 12所述的方法, 其特征在于, 还包括:
客户端向所述服务器发送获取 ID列表协议命令, 所述获取 ID列表协议命 令用于获取用户创建或者加入的用户群組 ID列表的协议命令, 所述获取 ID列 表协议命令中包含所述用户 ID;
客户端接收所迷 J!良务器返回的所迷用户创建或者加入的用户群组 ID列表; 客户端根据所迷用户群组 Π 列表, 获取所述用户群组 ID列表中各个用户 群组的基本资料信息, 并将所述各个用户群组的基本资料信息展示。
14、 一种徵博消息的发布方法, 其特征在于, 包括:
当第一用户发布徵博消息时, 所述第一用户对应的第一微博终端获取所述 第一用户待发布的微博消息, 并将所述微博消息传送至微博服务器端;
所述微博服务器端检测所述微博消息的特定位置是否包含微博群组帐号信 息, 若检测结果为是, 所述微博服务器端将所述微博消息添加至所述微博群组 中各成员的特定消息队列中;
所述微博服务器端将所述微博群组中各成员的特定消息队列中的微博消息 推送至所述微博群组中各成员对应的微博终端上进行发布。
15、 如权利要求 14所述的方法, 其特征在于, 所迷微博消息的特定位置为 预设的正则表达式约定的位置。
16, 如权利要求〗 5所述的方法, 其特征在于, 所述微博服务器端检测所述 微博消息的特定位置是否包含微博群组帐号信息, 若检测结果为是, 所述微博 服务器端将所述微博消息添加至所述微博群组中各成员的特定消息队列中, 包 括:
所述微博服务器端根据正则匹配原则解析所述微博消息, 确定与所述预设 的正则表达式约定的位置相匹配的所述微博消息的特定位置;
所述微博服务器端检测所述微博消息的特定位置是否包含微博群組帐号信 息;
若检測结果为是, 所述微博服务器端根据所述微博群组帐号信息, 查询所 述微博群组的成员帐号信息列表;
所述微博服务器端根据所述成员怅号信息列表, 将所述微博消息添加至所 述微博群组中各成员的特定消息队列中。
】7、 如权利要求〗 6所述的方法, 其特征在于, 还包括:
当所述微博服务器端检测所述微博消息的特定位置是否包含微博群组怅号 信息的检测结果为否时, 所迷微博服务器端判断所述微博消息的特定位置是否 包含第二用户帐号信息;
若判断结杲为是, 所述微博服务器端根据所述第二用户帐号信息, 将所述 微博消息添加至所述第二用户的特定消息队列中;
所述微博服务器端扫描所述第二用户的特定消息队列, 将所述第二用户的 特定消息队列中的微博消息推送至所述第二用户对应的第二微博终端;
所述第二微博终端在特定消息界面上显示所述第二用户的特定消息队列中 的微博消息。
18、 如权利要求 16所述的方法, 其特征在于, 所述微博服务器端将所述微 博群組中各成员的特定消息队列中的微博消息推送至所述微博群组中各成员对 应的微博终端上进行发布, 包括: 所述微博服务器端扫描所述微博群组中各成员的特定消息队列, 将所述微 博群组中各成员的特定消息队列中的微博消息推送至所述微博群组中各成员对 应的微博终端;
所迷微博群组中各成员对应的微博终端显示所述微博群组中各成员的特定 消息队列中的微博消息。
19、 如权利要求 18所述的方法, 其特征在于, 所述微博群组中各成员对应 的微博终端显示所述微博群组中各成员的特定消息队列中的微博消息, 包括: 所迷微博群组中各成员对应的微博终端向所迷微博群组中各成员提供所述 特定消息队列中的微博消息的展示提醒和查看链接;
当所迷微博群組中各成灵对所述查看链接进行操作时, 所述微博群組中各 成员对应的微博终端在特定消息界面上显示所述微博群组中各成员的特定消息 队列中的微博消息。
20、如权利要求〗 4-19任一项所迷的方法,其特征在于, 所述微博服务器端 将所述微博群组中各成员的特定消息队列中的微博消息推送至所述微博群组中 各成员对应的微博终端上进行发布之后, 还包括:
当所述微博群组中的成员回复或转播所述成员的特定消息队列中所述第一 用户发布的微博消息时, 所述成员对应的微博终端获取回复的内容或转播的内 容, 对所述微博群组帐号信息与所述回复的内容或转播的内容进行封装, 生成 回复消息或转播消息并传送至所述微博服务器端;
所述微博服务器端根据所述回复消息或转播消息中的微博群组帐号信息, 将所述回复消息或转播消息添加至所迷微博群组的广播队列中;
所述微博服务器端扫描所述微博群组的广播队列, 将所述微博群组的广播 队列中的微博消息推送至所迷第一微博终端;
所述第一微博终端在群组消息页面中显示所述微博群組的广播队列中的微 博消息。
21、 一种微博整合方法, 其特征在于, 包括步骤: 微博终端根据话题内容查询微博话题服务器, 获取话题的话题标识; 发送建立所述话題与所述微博终端所属的微博列表关联关系的建立指令至 微博列表服务器和 /或微博话题服务器; 所述建立指令的内容包括话題标识以及 微博列表标识; 所迷关联关系包括映射关系和 /或收听关系;
微博列表服务器根据所述微博列表标识, 查找与微博列表标识对应的数据 内容, 并将所述话题标识写入至所述数据内容, 建立映射关系; 和 /或,
微博话 ¾^务器获取所述话題的话題标识, 查找与话题标识对应的数据内 容, 并将所述微博列表标识写入至所述数据内容, 建立收听关系。
22、 根据权利要求 21所述的微博整合方法, 其特征在于, 所述微博列表服 务器根据所述微博列表标识, 查找与微博列表标识对应的数据内容, 并将所述 话题标识写入至所述数据内容, 建立映射关系的步驟后还包括:
微博消息服务器将微博列表中的微博成员发送的微博消息, 发送至与微博 列表具有映射关系的话題的消息列表。
23、 根据权利要求 22所述的微博整合方法, 其特征在于, 所述微博消息服 务器将微博列表中的微博成员发送的微博消息, 发送至与微博列表具有玦射关 系的话题的消息列表的步紫具体包括:
微博消息服务器获取所述微博成员对应的微博列表标识, 查看与微博列表 标识具有映射关系的话題标识, 将所迷微博消息写入至所述话题标识的消息列 表。
24、 根据权利要求 21至 23中任一项所述的微博整合方法, 其特征在于, 所述微博话 ¾ϋ务器获取所迷话题的话题标识, 查找与话题标识对应的数据内 容, 并将所述微博列表标识写入至所述数据内容, 建立收听关系的步骤后还包 括:
微博消息服务器对接收的微博消息进行解析, 获取话題内容并通过微博话 «I务器查询是否存在相同的话题内容;
如存在, 微博消息服务器发送插入指令至微博话题服务器, ^題内容插 入至相应话题的消息列表;
如不存在, 微博话题服务器根据所述话題内容建立新的话题。
PCT/CN2012/000224 2011-02-21 2012-02-21 微博名单传播的实现方法、终端及系统 WO2012113265A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/000,590 US20130339465A1 (en) 2011-02-21 2012-02-21 Method, apparatus and system for spreading a microblog list

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
CN201110042017.X 2011-02-21
CN201110042017XA CN102647366A (zh) 2011-02-21 2011-02-21 微博名单传播的实现方法、终端及系统
CN201110043489.7 2011-02-23
CN2011100434897A CN102651713A (zh) 2011-02-23 2011-02-23 管理用户群组成员的方法、装置及系统
CN201110050116.2 2011-03-02
CN201110050116.2A CN102655513B (zh) 2011-03-02 2011-03-02 微博消息的发布方法、微博终端及微博服务器端
CN201110072143.X 2011-03-24
CN201110072143.XA CN102694741B (zh) 2011-03-24 2011-03-24 微博整合方法、微博终端、微博列表、微博话题服务器及系统

Publications (1)

Publication Number Publication Date
WO2012113265A1 true WO2012113265A1 (zh) 2012-08-30

Family

ID=46720108

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/000224 WO2012113265A1 (zh) 2011-02-21 2012-02-21 微博名单传播的实现方法、终端及系统

Country Status (2)

Country Link
US (1) US20130339465A1 (zh)
WO (1) WO2012113265A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103167172A (zh) * 2013-02-08 2013-06-19 广州三星通信技术研究有限公司 将多种聊天记录整合的方法和系统
WO2015103975A1 (en) * 2014-01-10 2015-07-16 Tencent Technology (Shenzhen) Company Limited Information sharing management on an instant messaging platform

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102790726B (zh) * 2011-05-18 2015-10-28 腾讯科技(深圳)有限公司 一种基于即时通讯推送信息的方法、装置及系统
CN103379024B (zh) * 2012-04-26 2018-07-10 腾讯科技(深圳)有限公司 微博信息发布方法和服务器
CN103457962B (zh) * 2012-05-28 2018-03-23 腾讯科技(深圳)有限公司 访问微博相册的方法、微博客户端及系统
US9285981B1 (en) 2012-07-16 2016-03-15 Wickr Inc. Discouraging screen capture
US10129260B1 (en) 2013-06-25 2018-11-13 Wickr Inc. Mutual privacy management
US9830089B1 (en) 2013-06-25 2017-11-28 Wickr Inc. Digital data sanitization
US10567349B2 (en) 2013-06-25 2020-02-18 Wickr Inc. Secure time-to-live
US9698976B1 (en) 2014-02-24 2017-07-04 Wickr Inc. Key management and dynamic perfect forward secrecy
US9584530B1 (en) 2014-06-27 2017-02-28 Wickr Inc. In-band identity verification and man-in-the-middle defense
US10116600B2 (en) * 2014-08-14 2018-10-30 Excalibur Ip, Llc Expressing statements in messages with personalized expression style
US10425783B1 (en) * 2014-09-10 2019-09-24 West Corporation Providing data messaging support by intercepting and processing received short message service (SMS) messages at a customer support service
CN104317473B (zh) * 2014-09-24 2018-03-16 广州华多网络科技有限公司 一种界面显示方法及客户端
US9654288B1 (en) 2014-12-11 2017-05-16 Wickr Inc. Securing group communications
US9584493B1 (en) 2015-12-18 2017-02-28 Wickr Inc. Decentralized authoritative messaging
US10291607B1 (en) 2016-02-02 2019-05-14 Wickr Inc. Providing real-time events to applications
US9596079B1 (en) 2016-04-14 2017-03-14 Wickr Inc. Secure telecommunications
US9602477B1 (en) 2016-04-14 2017-03-21 Wickr Inc. Secure file transfer
CN111614549B (zh) * 2020-05-21 2022-05-31 腾讯科技(深圳)有限公司 交互处理方法、装置、计算机设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101039284A (zh) * 2006-03-16 2007-09-19 腾讯科技(深圳)有限公司 一种向群组发送即时消息的方法
CN101217504A (zh) * 2007-12-27 2008-07-09 腾讯科技(深圳)有限公司 一种共享通信好友的方法及网络通信系统
US20080215591A1 (en) * 2006-11-06 2008-09-04 Robert Howard Email interface for weblog entries
CN101378368A (zh) * 2008-09-28 2009-03-04 腾讯科技(深圳)有限公司 一种信息交互的方法及系统
CN101534207A (zh) * 2009-04-13 2009-09-16 腾讯科技(深圳)有限公司 群组加入系统及方法

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030163516A1 (en) * 2002-02-27 2003-08-28 Perkins Gregory Eugene Session coordination
US7895273B1 (en) * 2003-01-23 2011-02-22 Sprint Spectrum L.P. System and method for sorting instant messages
GB0602523D0 (en) * 2006-01-05 2006-03-22 Redburn Consulting Ltd Community messaging system
US7548907B2 (en) * 2006-05-11 2009-06-16 Theresa Wall Partitioning electrical data within a database
US20070290787A1 (en) * 2006-06-20 2007-12-20 Trevor Fiatal Systems and methods for group messaging
US8161052B2 (en) * 2008-01-30 2012-04-17 Hewlett-Packard Development Company, L.P. Information module recommendation
US20100088187A1 (en) * 2008-09-24 2010-04-08 Chris Courtney System and method for localized and/or topic-driven content distribution for mobile devices
US8752071B2 (en) * 2008-12-19 2014-06-10 International Business Machines Corporation Identifying subscriber data while processing publisher event in transaction
US8539359B2 (en) * 2009-02-11 2013-09-17 Jeffrey A. Rapaport Social network driven indexing system for instantly clustering people with concurrent focus on same topic into on-topic chat rooms and/or for generating on-topic search results tailored to user preferences regarding topic
US20120066303A1 (en) * 2010-03-03 2012-03-15 Waldeck Technology, Llc Synchronized group location updates
US8380799B2 (en) * 2010-04-15 2013-02-19 Ebay Inc. Topic-based messaging using consumer address and pool
US20120036085A1 (en) * 2010-08-05 2012-02-09 Accenture Global Services Gmbh Social media variable analytical system
US20120042020A1 (en) * 2010-08-16 2012-02-16 Yahoo! Inc. Micro-blog message filtering
US9418160B2 (en) * 2010-12-17 2016-08-16 Microsoft Technology Licensing, Llc Hash tag management in a microblogging infrastructure

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101039284A (zh) * 2006-03-16 2007-09-19 腾讯科技(深圳)有限公司 一种向群组发送即时消息的方法
US20080215591A1 (en) * 2006-11-06 2008-09-04 Robert Howard Email interface for weblog entries
CN101217504A (zh) * 2007-12-27 2008-07-09 腾讯科技(深圳)有限公司 一种共享通信好友的方法及网络通信系统
CN101378368A (zh) * 2008-09-28 2009-03-04 腾讯科技(深圳)有限公司 一种信息交互的方法及系统
CN101534207A (zh) * 2009-04-13 2009-09-16 腾讯科技(深圳)有限公司 群组加入系统及方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103167172A (zh) * 2013-02-08 2013-06-19 广州三星通信技术研究有限公司 将多种聊天记录整合的方法和系统
WO2015103975A1 (en) * 2014-01-10 2015-07-16 Tencent Technology (Shenzhen) Company Limited Information sharing management on an instant messaging platform
US9565145B2 (en) 2014-01-10 2017-02-07 Tencent Technology (Shenzhen) Company Limited Information sharing management on an instant messaging platform

Also Published As

Publication number Publication date
US20130339465A1 (en) 2013-12-19

Similar Documents

Publication Publication Date Title
WO2012113265A1 (zh) 微博名单传播的实现方法、终端及系统
CN110521172B (zh) 用于处理短暂内容消息的方法和系统
US9705841B2 (en) Private mobile messaging and data communications apparatus and method of managing organizational messaging
WO2012097655A1 (zh) 一种群组的实现方法、系统及客户端
CA2787763C (en) Method, system and group server for synchronizing operations of multiple groups
WO2013060143A1 (zh) 一种通过微博向群用户发送消息的方法及装置
US9602309B2 (en) Alert message portal to securely notify subscribers of events
US20140310349A1 (en) Method and apparatus for establishing relationships among devices and users
CN102655513B (zh) 微博消息的发布方法、微博终端及微博服务器端
WO2017128178A1 (zh) 一种信息交互方法、客户端和装置
WO2012155602A1 (zh) 一种推送信息的方法、装置及系统
US20200195458A1 (en) Multiplexing message distribution within group-based communication system
GB2445429A (en) Message modification on basis of group membership
KR20180118732A (ko) 비동기 메시징 시스템에서의 단일 계정에 대한 다수 프로파일의 관리
US20110307565A1 (en) Group messaging integration system, method and apparatus
CN103685004A (zh) 一种支持企业级即时通信系统互联互通的协议网关及方法
WO2008022522A1 (en) Method and system for providing mobile service and management center server therefor
WO2012171404A1 (zh) 一种分享微博消息的方法、装置和系统
US8914448B2 (en) Mobile communication system and method for the requesting of positive delivery reports from individual group members
WO2014187397A1 (zh) 多媒体消息的发布方法及装置
US20160277339A1 (en) Electronic Communication System
CN102647366A (zh) 微博名单传播的实现方法、终端及系统
CN102611635B (zh) 基于微博的消息交互方法、系统
WO2012155652A1 (zh) 跨社交网络的通信方法、网元及系统
WO2013023593A1 (zh) 一种基于群号的微博聚合方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12749125

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 14000590

Country of ref document: US

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205N DATED 29/10/2013)

122 Ep: pct application non-entry in european phase

Ref document number: 12749125

Country of ref document: EP

Kind code of ref document: A1