WO2009092214A1

WO2009092214A1 - Method, client, server and system for processing the published information

Info

Publication number: WO2009092214A1
Application number: PCT/CN2008/072849
Authority: WO
Inventors: Qian Sun
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2008-01-23
Filing date: 2008-10-27
Publication date: 2009-07-30
Also published as: CN101262494A

Abstract

A method for processing the user-published information is disclosed, which includes the following steps: receiving the information sent by user; searching the information record in information Database matched to the information, publishing the information, and recording it in the information Database; returning and presenting the prompt information of successful release and the matching information together. Other several methods for processing the user-published information combining the searching technology, and server, client etc are also disclosed.

Description

Method, client, server and system for processing published information

Embodiments of the present invention relate to the field of Internet, and in particular, to a method, a client, a server, and a system for processing published information. Background technique

Micro-blogging is a form of blog that allows users to update short texts and publish them in a timely manner, allowing anyone to read or only select groups by users, etc., also known as mini-blogs or instant blogs. Through microblogging, users can share information. At present, some of the main microblogs are Twitter, Fan No, and Yu.

Users can post information to microblogs via web pages, mobile Internet access, instant messaging tools, short messages or multimedia messages. However, usually after the user posts the information, the information is flooded with huge amounts of information. Even if there are other users who are interested in this information, it is difficult to find and reply to this information. In addition, if the user browses the micro-blog website through the webpage, the information that has already been published is generally displayed on the webpage, and a text input box can be provided on the webpage for the user to post the information, but now the user posts the information on the webpage. In addition to increasing the information that has just been published, the information records that have been displayed before the user posts the information are usually displayed. The information may have been viewed by the user and has nothing to do with the information posted by the user.

Search engine technology has been a mature technology that has been developed for many years, especially for the search for text information. The general search engine consists of four parts: the searcher, the indexer, the retriever, and the user interface. The searcher is used to roam, discover and collect information on the Internet. It is often a computer program that runs around the clock, also known as a web spider. The indexer is used to understand the information searched by the searcher, extracting index items from it, representing the document and generating an index table of the document library. The function of the retriever is to quickly check the document in the index library according to the user's query, evaluate the relevance of the document and the query, and sort the results to be output. The user interface is used to input user queries, display query results, and the like. Search The application of engine's indexing and retrieval technology to the microblogging business can help the discovery and sharing of massive information in microblogs.

In carrying out the process of the present invention, the inventors have found that the prior art has at least the following problems:

At present, the user knows what the friend is currently doing through microblogging or instant messaging service, such as the media information such as the music video being played, and cannot enable the user to obtain and synchronously play the media that the friend is playing, and cannot obtain and simultaneously display the played by the friend. Music lyrics, video subtitles, etc. Summary of the invention

The embodiment of the invention provides a method for processing information published by a user, so as to enable the user to obtain similar information that has been released while publishing the information.

The embodiment of the present invention further provides a method for processing information sent by a user, and assigns a corresponding location attribute to the information distributed by the user, and can provide the user with information matching the location.

The embodiment of the invention also proposes a method for processing information published by a user, which can directly search for information published by the user by one click operation.

The embodiment of the invention also provides a method for sharing media information, so that users can synchronously play media or synchronously display lyrics, subtitle texts and the like of corresponding media.

The embodiment of the invention also proposes a method for processing instant communication signature information, which can search for the signature information issued by the user in the instant communication tool by one click operation.

The embodiment of the present invention further provides a method for providing presence information, which can simultaneously publish information published by a user on a microblog in a presence service.

The embodiment of the present invention further provides a server, which enables a user to obtain similar information that has been released while publishing information.

The embodiment of the invention also proposes a client, which can share application information, especially media information, between users. The embodiment of the invention also proposes a micro-blog browser interface, which can display information records on corresponding sub-pages according to information types.

The embodiment of the present invention also provides a system, which enables a user to obtain similar information that has been released while publishing information. The technical solution proposed by the embodiment of the present invention is as follows:

A method for processing information published by a user, the method comprising the steps of: receiving information sent by a user;

Searching in the information base for information records matching the information, publishing the information, and recording the information into the information base;

The prompt message that is successfully posted is returned and presented together with the matched information.

A method for processing information sent by a user, the method comprising the steps of: receiving information sent by a user;

Obtaining location information of the user, generating a location attribute according to the location information; and saving the location attribute together with the information.

A method for processing information published by a user, the method comprising the steps of: simultaneously displaying a corresponding search button when displaying the information record;

When the search button is clicked, the search engine is called to query the corresponding information record content.

A method for media information sharing, the method comprising the steps of:

Collecting and publishing media information of the media being played, wherein the media information includes time information of the broadcast;

Obtain the media information subscribed to;

The corresponding media is played synchronously according to the time information, or the lyrics or subtitle text of the corresponding media is synchronously displayed.

A method for processing instant messaging signature information, the method comprising the steps of: displaying a corresponding query button simultaneously when displaying the signature information of the friend; and using the corresponding signature information as the search keyword when the query button is clicked Call the search engine to query; Receive the query results and display them.

A method of providing presence information, the method comprising the steps of:

The microblog server records the presence service user identifier of the microblog user; the microblog server receives the information sent by the user terminal;

The microblog server converts the information into a presence information element;

The microblog server issues the presence information element as the corresponding user according to the presented service user identifier.

A server, comprising:

An information receiving unit, configured to receive information sent by the user client, and record the information to the information storage unit, and notify the search matching unit to perform search matching on the information record in the information storage unit;

The information storage unit is configured to record the information received by the information receiving unit, and the search matching unit is configured to search for the matched information record in the information storage unit for the information received by the information receiving unit, and return the matched information to the client.

A client that includes:

An information collecting unit, configured to collect information of an application running in the user terminal; and an information publishing unit, configured to publish the application information collected by the information collecting unit;

The information receiving unit is configured to receive the published application information of the other user; and the application starting unit is configured to start the corresponding application according to the application information received by the information receiving unit.

A micro-blog browser interface displays information records on corresponding sub-pages according to information types, and the sub-pages include at least one of the following:

A sub-page for displaying information records of the type of the report;

Question sub-page, an information record for displaying the type of question;

A wish subpage, a record of information used to display the type of wish.

A system comprising: a microblog server, the microblog server comprising an information receiving unit, an information storage unit and a search matching unit,

The information receiving unit is configured to receive the information sent by the user client and record it to An information storage unit that notifies the search matching unit to perform search matching on the information record in the information storage unit,

The information storage unit is configured to record information received by the information receiving unit,

The search matching unit is configured to search the information storage unit for the information received by the information receiving unit to match the information record, and return the matched information.

Compared with the prior art, the embodiment of the invention has at least the following advantages:

After receiving the information posted by the user, the embodiment of the present invention immediately searches the information base for the information record that matches the content of the published information, so that the user can obtain other information similar to the self-published information immediately after the information is published. recording. By subtly using the information published by the user as the input condition of the search, the other information records that have been published are retrieved, and the information matching function is provided at the same time as the completion of the information release, which is especially suitable for micro-blogs. Less situation. With the present invention, users can more easily find people who have "common language" with themselves in a social networking (SNS) such as a microblog. Moreover, the user can see different information records before the release of the information, and the information records are related to the information published by the user, which improves the utilization efficiency of the user interface, so that the user can see more and more relevant information.

It also captures application information and publishes it after structuring, using search technology to enable users to discover other users who use similar applications, and to enter the same or similar application scenarios based on structured application information. In addition, by transmitting media information including playback time information, and preferably using the system time on the server side, synchronization processing of media playback can be performed accurately between different clients. Search resources can also be queried and downloaded using search technology.

It also enables users to obtain information about their location matching by generating and saving location attributes for the information record.

By providing a corresponding search button on the web page or instant messaging client interface, the user can perform a corresponding search directly by one click operation. DRAWINGS

FIG. 1 is a basic flowchart of processing information published by a user according to an embodiment of the present invention; Figure 2 is a flow chart of the first embodiment of the present invention;

Figure 3 is a flow chart of a second embodiment of the present invention;

Figure 4 is a flow chart of a third embodiment of the present invention;

Figure 5 is a flow chart of a fourth embodiment of the present invention;

Figure 6 is a flow chart of a fifth embodiment of the present invention;

7 is a flowchart of sending a search request to an external server according to a sixth embodiment of the present invention; FIG. 8 is a flowchart of releasing information to an external server according to a sixth embodiment of the present invention; FIG. 9 is a flowchart of a seventh embodiment of the present invention;

10 is a schematic diagram of a communication state interface when an instant messaging client communicates with a friend according to a seventh embodiment of the present invention;

11 is a schematic diagram showing display of signature information and corresponding search and play buttons in an instant messaging client according to a seventh embodiment of the present invention;

12 is a schematic diagram showing display information records and corresponding search hyperlinks in a browser according to an eighth embodiment of the present invention;

Figure 13 is a flow chart of an eighth embodiment of the present invention;

FIG. 14 is a schematic diagram of calculating a time difference according to a ninth embodiment of the present invention; FIG.

Figure 15 is a flowchart of a ninth embodiment of the present invention;

Figure 16 is a flowchart of a tenth embodiment of the present invention;

Figure 17 is a schematic view showing a sub-area displayed in a browser according to an eleventh embodiment of the present invention;

Figure 18 is a diagram showing the display of a material page in a browser according to an eleventh embodiment of the present invention;

Figure 19 is a flow chart showing an eleventh embodiment of the present invention;

20 is a schematic diagram of a basic structure of a server according to an embodiment of the present invention;

21 is a schematic structural diagram of a server including an automatic labeling and a virtual robot unit according to an embodiment of the present invention;

FIG. 22 is a schematic structural diagram of an application information sharing tool according to an embodiment of the present invention; FIG. 23 is a schematic structural diagram of an application information sharing tool including a query, download, and synchronization playing unit according to an embodiment of the present invention. detailed description

Referring to FIG. 1 , which is a basic flowchart of processing information published by a user according to an embodiment of the present invention, the method includes the following steps: Step 101: Receive information sent by a user. A user terminal such as a computer or a mobile phone can send a message to the server through a protocol such as HTTP (HyperText Transfer Protocol), WAP (Wireless Application Protocol), instant message, short message, or multimedia message. The server parses the received message according to the corresponding protocol, and obtains the content information and the user identifier therein. Step 102: Search an information record in the information base that matches the information, publish the information, and record the information in the information base. The server searches the repository for similar information that matches the information posted by the user. The matching may be that the content of the information is related, the labels of the information are the same, or the location attributes of the information are the same or similar. For the matching processing of the information content, the current single search engine technology can be used to index the content of the saved information record, and the information content published by the user is searched as an input of the search, and then the matching result can be correlated. Sort by degree and chronological order. When searching, it is also possible to exclude the information records previously sent by the user and search only the information records sent by other users. The server records the received information, and generally records the current time, the transmission path information (such as through an instant message or a short message, etc.); and then publishes the original information together with the time and route information. The post-release information is stored in the information base. Usually, the server also builds an index library for the information base for retrieval by keywords. In this step, the matching information may be searched for and then the posting information may be recorded, or the posting information may be recorded first and then the matching information may be searched. The results of the search do not affect the recording and publishing, such as successfully publishing the information even if no matching information is found. Step 103: Return and present the prompt information that is successfully posted together with the matched information. The content of the information to be matched, as well as the sender's identity, release time, etc. Return to the user. For example, if the user sends the information through the webpage, after the information is sent, the content presented in the returned webpage may include information matching the information sent by the webpage. In addition, the return information, such as the returned webpage, also includes a prompt for the user to successfully post the information, and the prompt may be a prompt text such as "the information you sent has been released", or may directly present the user just released in the form of a published message. The piece of information serves as a reminder that the publication is successful, and according to this form (such as the presentation time at which the information is presented), the user can be made aware that the information has been successfully published. If the user sends the information through the instant messaging tool, the matched information can also be returned to the user's instant messaging client through the instant message. It can be seen from the above steps that while the user publishes the information, the search is performed with the information published by the user as the input search condition, and the target of the search is also the information that has been published by other users. This method is just right for the short message content in the microblog. The publication of traditional general blog posts with more content is not suitable for the above methods. A method of processing information posted by a user through a web page is described in detail in the first embodiment. First, the user must first log in to the microblogging website. If the user has not logged in when sending the message, the user should be prompted to log in first. The message sent by the user through the webpage may include a picture, a voice, a video, and the like in addition to the text information. In this embodiment, the processing of the text information is mainly considered. In this embodiment, a tag technology may also be adopted to enhance search capabilities, such as improving the accuracy of matching information. The implementation of the label technology includes a manual labeling method and an automatic labeling method. When the user sends a message through a webpage, the user assigns a label to the information and transmits it to the server along with the information. Tags are usually one or more keyword texts, such as "games", "work", "food", "music", "movie", "sports" and "mood". In micro-blogs, you can provide categories based on the activities of people's daily lives, each of which corresponds to a label. Considering that the information sent by the user can be used as the presence information, or vice versa, the presence information is used as the information sent by the user to the blog website, and the IETF (Internet) can be used. Engineering Task Force) The SIMPLE group presents classifications in the Activity Activities element of the business specification RFC 4480 (RIPD) as labels, such as appointment appointments, breakfast breaks, dinner dinners, vacation holidays, meeting meetings, travel travel, etc. In addition, the mood mood defined in the specification can also be used as a label. The text information content corresponds to the content of the note element in the activity Activities and mood mood elements. Thus, when the user posts an activity Activity or mood mood presentation information, the presence server can also publish the presence information to the user's blog website. Or after the user posts the information with the activity Activities and mood mood tags to the blog site, the server can distribute the information as presence information to the user's presence information subscriber. The server may also automatically generate a corresponding label for the information after receiving the information sent by the user. Proactively generate tags by analyzing keywords in text messages sent by users. The keyword is selected from the body of the text information and is a vocabulary that has substantial meaning for expressing the central content of the text information. When determining keywords, semantic-based topic analysis is performed, and a number of words (usually clear and stable nouns and verbs) are selected as the keyword set of the text information according to the result. The automatic annotation method based on keyword analysis combines the advantages of traditional classification method and manual labeling, and labels in the context of text information content itself. At the same time, it provides the contribution of each keyword to the content as a reference, and standardizes the labeling. Standards, thus ensuring quality. The correspondence table of keywords and classification labels can be established, and keywords such as "breakfast", "mung bean soup" and "steak" can correspond to the "diet" label, and the information sent by the user includes "steak". When the keyword is used, the server automatically labels the corresponding label such as "diet". An information record can be labeled with one or more tags. It is also possible to adopt a method for labeling text information, and automatically extract the portion before the first space in the text information as a label. This method of labeling is very suitable for the use of short messages to post information, such as the user to send a short message on the mobile phone "Dance Competition Friday finals to see." The server will receive the text message first by removing the leading and trailing spaces and the carriage return line feed, etc., and then the first in the text content. The text portion before the space is taken out as a label. If the intercepted text portion is too long and exceeds a preset upper limit, such as more than 5 characters, it will not be used as a label. In addition, the text content may not contain spaces. In these cases, it may not be a text. The information is automatically generated by the tag, or the keyword method is still used to generate the tag. There is also a text before the first space, if it is a function identifier character such as "!", "*", etc., or the text before the first space is a function text, which is used to indicate that the information is a specific type of information, such as The "report" indicates that the information is the report information, and the text before the first space cannot be used as the keyword. The server uses the tag to search for an information record that matches the content of the information. The information records containing the same label can be determined to be similar, for example, if both information records have a "diet" label, it can be determined to be similar information. In order to improve the accuracy of the matching, the matching degree of the keywords in the information can be further compared. The higher the matching frequency of the keywords, the higher the matching degree is. In addition, there are more than 4 mature technologies for calculating the similarity of text information, which can be applied to this embodiment, and will not be described here. Unlike search engines, considering that the user's purpose is not to search, there is no need to provide too many matching results here. You can set a limit on the number of returns for a matching result, such as 5 or 10, which can be displayed in one screen. When the matching result is returned, only the information record of the preset upper limit number is returned, and all are displayed in the returned page. The server can sort all the matching results to be returned in the order of publication time, so that the latest published information is displayed first, and the older information is displayed later. In addition, in order to improve the search speed, it is possible to match only the information records within a certain period of time such as the day or the last hour. In fact, users are often only interested in newer information, and if the matching information is similar to the time the user sends the information, the two publishers can have a greater chance of chatting. In addition, the user can also filter the matching message sender attribute in advance. For example, by filtering the sender's area, gender and other attributes, the user can only see similar information sent by other users in the same area. Server saves this Some filtering settings, when searching for information records that match the content of the information, apply filtering settings to the sender of the information record. This way, even if the text information is matched, the information may be filtered according to the sender's attributes, and the server will not return it to the user. In addition, whether the user friend (or contact) in the sender attribute can also be used as a filtering setting, for example, if the user can only search for a record similar to the one published by himself in the information sent by the friend, it can be a friend attribute. Filter settings are made, and the server filters the settings to search for matching information records only in the information sent by their friends. Before the search, if the server detects that the user posting the message is bound to a channel or column, then the matching information record can be searched only within that channel or column. The so-called binding, that is, the information sent by the user will be automatically divided into a fixed channel or column classification set by the server. For example, the user who is the identity of the reporter can be bound to the news channel column, and the information published by the user is classified by default. Go to the news channel column. Other users can browse the news channel column to see the information posted by the user. In addition, binding the user to the label can also achieve the same effect, that is, the information sent by the user is automatically assigned a corresponding preset label. For example, an information server published to a user can assign a "smile" tag to the user based on the settings. Some information records may be user replies to other users posting information, and the server records the replies between such information. If a matching message is a reply message, the server also returns a link corresponding to the original information, or directly returns the content of the original information. When displaying the returned information, the original information can be displayed in the adjacent area below the matching reply information, and clearly indicates that it is the original information corresponding to the reply information. Some users who post information can be service providers that provide information services.

(SP), such as jokes, weather conditions, stock market quotes, etc. Ordinary users can add these SP users as contacts to obtain the consultation information provided by these SP users. For this type of special SP user, no search match can be made. Specifically, the corresponding search setting can be saved for each user, and the server determines whether it is necessary to search according to the setting. Cable matching. The server can generate an index on the fly when the information posted by the user is recorded; it can also generate an index on the information record at a specific time. When searching for matching information, the server may retrieve a matching information record in the index library according to the extracted keywords. The specific indexing and retrieval techniques have many mature existing technologies, which will not be described here. The label of the information may not exist in the content of the information, such as the label "diet" does not exist in the information "in the McDonald's licking chicken". The generated tags are also indexed to make the search smarter. When the server records the information to the information base, the index item is generated for the index, and the index item is saved to the index library, and the index item generated for the corresponding relationship between the label and the information is also included. When searching for an information record that matches the content of the information, extracting keywords in the information, using the keywords and the tags to search and match index entries in the index library, and in the information base Get the information record corresponding to the matching index item. After receiving the information posted by the user, the server may match the appropriate advertisement content information according to the information registered by the user, such as age, gender, hobbies, regions, etc. The advertisement information may be text, picture or video. The corresponding advertisement information can also be obtained by combining the information published by the user. If the information published by the user includes the "meal" keyword, a restaurant advertisement information can be selected. After the server selects the advertisement information, the advertisement information is returned and presented together with the matched information. The advertisement information can be presented in the same way as the matching information, and the advertisement information can also be used as a matching information. The server may first query the matching information in the user information database, and then query the matching advertisement information from the advertisement information database, and then mix the advertisement information and the matching information, for example, the advertisement information may be arranged in front of the first matching information or The position behind. In the advertisement information database, each piece of advertisement information may be set with one or more matching keywords. If the server detects that there is a corresponding keyword in the information posted by the user, the corresponding advertisement information may be provided to the advertisement information. In addition, each ad message can also Set the corresponding user information matching conditions, such as age, regional conditions, etc., and the server only provides corresponding advertising information to users who meet the corresponding condition settings. Referring to FIG. 2, an example is described below with reference to a flowchart: Step 201: Receive text information sent by a user through a webpage. Step 202: Analyze keywords in the text information sent by the user to generate a label. Step 203: Acquire an information record having the same label as the text information, and apply a filtering setting of the user to the message sender attribute.

Step 204: Select matching information that is less than the preset number upper limit. Step 205: Acquire corresponding advertisement information according to user information and/or information posted by the user and/or the matched information. For example, the corresponding advertisement is selected according to the user's interest information, or the information posted by the user and the keyword in the matched information.

Step 206: Return and present the matched information together with the advertisement information. The second embodiment mainly describes the combination of a microblog and a chat room. The microblogging website can simultaneously provide a chat system. When the user enters a chat room, the server can obtain the information record that the user has recently posted on the microblog, and then display it in the chat room, such as the public speech of the user in the chat room. Display. After the user posts the information in the first embodiment, after obtaining the information matched by other users, the user may also initiate a chat. In the initiated chat, the server may first display a similar message sent by two people in the established temporary chat room as an opening or topic of the chat room. The server can assign an identifier to the established temporary chat room, as indicated by a unique random string. In the first embodiment, when the server returns and presents the matched information, the address link of the chat room where the sender of the matched information is located may also be returned and presented together, and the address link of the chat room includes the identifier. When the user clicks on the address link of the chat room, the server can add the user to the chat room according to the corresponding request. Referring to FIG. 3, an example will be described below with reference to a flowchart: Step 301: A user is detected to enter a chat state. If it is detected that a user joins the chat room, or detects that one user invites another user to chat. Step 302: Obtain a record of information that the user has recently posted on the microblog. Step 303: Display the acquired information record in the chat room. The posting of information by means of a WAP webpage is similar to that of the first embodiment, and the third embodiment mainly describes a situation in which information is distributed by an instant messaging tool. The virtual robot technology of instant messaging can be used to publish information. Specifically, a service processing server is set up and corresponding to an instant messaging account, and the user can add the instant messaging account corresponding to the service processing server as a friend, and the service processing server can Like the user's regular friends, you can send and receive instant messages and presence information. Therefore, the friend or contact of such a non-natural person is called a virtual robot, and is actually a program entity that performs business processing. The business processing server corresponding to the virtual robot can be independent of the microblog server or the microblog server.

There are two ways to publish information through instant messaging tools. One is to send instant messages directly to the virtual robot corresponding to the microblog service through instant messaging, and the virtual robot records and publishes the information in the received instant messages. And searching for an information record that matches the content of the information, and then returning and presenting the matched information through an instant message. The user's experience is like a conversation with an instant message with a robot. In addition to the matching information itself, it is better to have some prompt information indicating that the returned information is automatically matched information, such as "a similarly released similar information:". If the sender of the matching information is also bound with an instant message account, the account number can also be returned together with the information, so that the user can directly use the account information to directly chat with the corresponding other users, or add them as friends. . Another way to post information is by presenting information. Typical Presence is the current state of users such as online, offline, busy, etc. In addition, the signature in the instant messaging tool can also be used as a kind of presentation information. Virtual robot through subscription The user's presence information can obtain information such as the user's latest status and signature, and the virtual robot can post the information to the microblog. The user can preset which presentation information can be published to the blog, and the virtual robot selectively issues information according to the user's settings. The RFC 4480 mentioned in the first embodiment is based on some extended presentation information of the IETF's SIMPLE specification. When the user publishes the presence information in the instant messaging system, the virtual robot can be used to publish it to his microblog website. . Referring to FIG. 4, an example is described below with reference to a flowchart: Step 401: Receive an instant message and/or presence information of a user and publish it. Step 402: Search for an information record that matches the content of the information. In step 403, the matched information record is returned and presented through the instant message. All retrieved matching information records can be returned in an instant message, or can be returned in multiple instant messages, each containing a matching information record. The information posted by the user can be self-written content, and can also include application information. The fourth embodiment describes a case where the information posted by the user contains the application information. The application information is mainly used to describe the situation in which the user terminal is currently running the application, including the name and parameters of the application. Specifically, such as the browser (Internet Explorer) and the website address parameter currently being browsed, or the map client (Google Earth) and the center point coordinate parameter of the current map. The release of application information is usually not manually published by the user, but can be automatically collected by the application information sharing tool and then controlled to be published. Users can pre-set which application information is allowed to be published to control privacy protection. You can collect information about the running application by monitoring the process information of the terminal. For some complex and specific application information (such as the level of user characters in the online game, location coordinates, etc.), the process may not be obtained from the operating system. Obtained in the information, this can define the corresponding application interface, so that the application can transfer some specific information to the application information sharing tool through the interface. Can apply Program information sharing tools are directly integrated into instant messaging tools, which are essentially present information. You can also use a separate application information sharing tool to collect, publish, and share application information.

The application information sharing tool can automatically generate information such as text or images based on the collected application information and publish it to the server. The automatically generated information allows the user to make modifications and supplements. For example, if the information is released: "The game is being played, the hands are numb", the first half is automatically generated by the tool, and the second half is supplemented by the user.

The application information sharing tool preferably provides structured application information to the server, such as application information described in the Extensible Markup Language (XML) format, as follows:

<?xml version="1.0" encoding="UTF-8"?>

<application-info>

<name>Google Earth</name>

<OS>Microsoft Windows XP Professional</OS>

</application-info>

Structured application information <application-info> can include application name <name>, version number <version>, running operating system <OS>, and parameter <paral>. There can be one or more parameter elements, in this case there is only one parameter <paral> , which includes the coordinates of the center position of the satellite map in the current Google Earth application. The application information can also include a comment <11 (^> element that allows the user to supplement the text content information. For example:

<note>The price here will rise to 30,000 in 2008 </note>

Application information sharing tool via HTTP or SIP (Session Initiation Protocols and other protocols send structured application information to the server, and the server saves the received application information. The server can automatically generate readable natural language text information based on the structured application information. For example, according to the application information in the above example, text information can be generated: "Google Earth is being used, and the price here will rise to 30,000 in 2008" The server will publish the generated text information. The server can also provide a link to the structured application information, so that other users can obtain the original structured application information corresponding to the text information, and further reproduce the application scene according to the same, such as obtaining a satellite map viewing the same coordinate position. Wait.

After receiving the structured application information, the server can search for information records that match the application information. If the application name is the same, the matching can be determined. In order to reduce the number of matching results and improve the matching accuracy, the parameters or the contents of the memo elements can be further matched. The keyword matches in the text message of the note. For application parameter matching, which is often related to a specific application, the application may be different, and the method of parameter matching determination may be different. The server selects a corresponding matching determination program according to the application name. For example, for the coordinate parameter in the map application, the proximity degree of the position coordinate can be determined to determine the matching degree; and for the user team gang parameter in the network game application, it can be determined whether the same , only the same is judged as a match. The server returns the matched structured application information to the application information sharing tool, and the application information sharing tool can start the corresponding application according to the user request, and reproduce the corresponding application scenario. If the application information sharing tool cannot find the corresponding application on the local terminal, you can prompt that the corresponding application cannot be started. Referring to FIG. 5, an example is described below in conjunction with the flowchart: Step 501: The application information sharing tool automatically collects application information according to user settings. Step 502: Convert the collected application information into an XML format and publish it. Step 503: After receiving the application information, the server searches for an information record that matches the application information. Step 504: The server returns the matched structured application information to the application information sharing tool. Step 505: The application information sharing tool starts the corresponding application according to the user request, and reproduces the application scenario corresponding to the matched application information. Microblogs can also be used as private personal diaries or memos. The fifth embodiment describes the processing of the memo information. When posting a message, the user can set the message to be a private personal journal, or a memo. A method of ordering a tube can be identified by a special character at the beginning of publishing the information content. For example, when the server receives the text content in a piece of information starting with a "*" character, it determines that the piece of information is a memo information. Or when publishing through a webpage, use a single information field other than the information content input field to indicate whether the information is a memo information. After the memo information is published, it can only be viewed by the publisher himself, that is, the server only provides his own memo information to the memo information publisher. After the server receives the memo information released by the user, the server may search for the memo information record that the user has posted, and match similar memo information to the user. This allows users to easily discover similar information that they have previously published, and enhances the memo function. More generally, the server can determine the scope of the search according to the manner in which the user posts the information, and search for the matching information record within the determined range. The way users post information can be determined by the way of posting (such as SMS, MMS) or the type of web page where the information is posted. For example, when posting information in a multimedia message, search matching can be performed within the information recording range including the image content. For example, when the information is posted on the memo page, the server searches only within the user's own memo; and when the information is published while browsing the information posted by the friend, the server only performs within the information record of the user's friend. search for. Usually microblogging sites are very The function area of the published information provided by multiple pages, the corresponding processing procedure is different when different pages are published, or the corresponding publishing mode parameters are transmitted when the information is published, so that the server identifies and performs corresponding processing on different publishing modes.

Referring to Figure 6, the following is an example of a flow chart:

Step 601: Detecting that the information posted by the user is the memo information, or detecting that the user is the information posted on the memo information browsing page.

Step 602: Search for a record of the memo information that the user has posted. Step 603: Match similar memo information to the user client.

The sixth embodiment mainly describes the interconnection between microblogs. At present, there are already many microblogs in operation, which are independent of each other, which is very inconvenient for users, such as the inability to add users of another microblogging website as friends. First, let's take a look at the process of adding a friend: UserA of the microblogging website A selects the name of the microblogging website where the friend is located, such as B, on the add friend page provided by the microblog website A, and then enters the friend's identification name such as UserB. After clicking the add friend button, the browser sends a request to add a friend to the server A of the microblog website A, and the server A sends a message to the server B of the micro blog website B, the message includes the identification names of the users UserA and UserB, and the server B detects Whether UserB exists or not, if it exists, it can further detect the security settings of UserB, and verify whether UserA can add UserB as a friend according to the security settings. When the addition is successful, Server B adds a UserB's buddy record, which contains the ID name of UserA and the ID name of the microblogging website A. Server B then returns a successful response message to server A. Server A also adds a UserA friend record containing the identity name of UserB and the identification name of microblogging website B. So the two microblogging websites have established the friend relationship records of UserA and UserB respectively. If the server B is not successfully added, the response message of adding the failure is returned to the server A, and the addition may fail. The reason, such as including the absence of UserB, or UserB is not allowed to add a reason description. On the other hand, when the UserB of the UserA is deleted, the server A sends a deletion notification to the server B in addition to the corresponding friend relationship record in the local area, and the server B also deletes the corresponding friend relationship record. The server can only save information published by users of this website, so that when accessing information records of other external websites, the external server is accessed. For example, if the scope of the search is limited to the information record published by the friend, when some of the friends of the user belong to other microblog websites, the server needs to submit a corresponding search request to the servers of other microblog websites. The search request includes information posted by the user, the name of the website identifier of the user, and the name of the user identifier. The server receiving the search request determines the website according to the website identification name and the user identification name of the user in the search request. The user's buddy list, and then search for the records matching the information posted by the user in the information records published by the buddies, and return them to the server that sends the search request, and the server that sends the search request returns the information returned by the other server. The records are merged with the locally retrieved information records and returned to the client. The combination of the bills can be displayed on the front of the page by the information records matched by the website, and the information records matched by other websites in the 4th bar are displayed in the back. Of course, in order to sort all the information records according to the matching degree, one server can calculate the matching degree for the information records returned by other servers, and sort them according to the matching degree together with the locally matched information records. If the matching degree is returned when the information record is returned by another server, the calculation method of the matching degree may be inconsistent and cannot be reasonably sorted. Here, the unified calculation is performed by the server that sends the search request, and the consistency of the matching degree calculation can be ensured. If the order is sorted by time, it can be sorted according to the time information in the information records returned by other servers. It can be considered that the system time of each server is accurate and consistent, and of course the time difference factor is also considered. Generally, it is also possible to limit the search request to return the maximum number of matching records or the time range, etc., and these limits can be used in the search request. The microblogging website can also open the search request interface, which can be based on

The interface of the HTTP protocol, which can be provided not only to other microblogging websites, but also to other Internet services. The search request interface includes search condition parameters, such as text content or keyword parameters, and may also include time parameters, user identifiers, and the like. The server queries according to the parameters provided in the search request interface, and returns the matching information record to the sending search requester. The specific interface can use the HTTP GET or HTTP POST method, where the HTTP GET method puts the search condition parameter in the request line of the message, and the HTTP POST method can put the search condition parameter into the message body. In addition, the HTTP-based SOAP protocol can also be used to implement the search request interface, which will not be described here. An example of an interface based on the HTTP GET method: 3⁄4 port:

GET http:〃 www.example.com/search ?uid=123456&txt=hello HTTP/1.1 where the parameters "uid" and "txt" are the user ID and release information respectively. The HTTP GET request message is sent to the external server, and after the external server retrieves the parameter according to the parameter, the matched information record is returned through the HTTP OK response message body of the HTTP protocol. Referring to FIG. 7, an example is described below with reference to a flowchart: Step 701: The client issues information to the server. Step 702: The server acquires a friend relationship record of the user. Step 703: The server sends a search request to an external server. A search request may be sent to one or more external servers. Step 704: Receive a search result returned by an external server. Step 705: Combine the information record returned in the search result with the locally retrieved information record. Step 706, returning the merged information record to the client. After receiving the information published by the users of the website, the server may also publish the information to an external server interconnected with the information. Conversely, the server can also receive the published information forwarded by the external server. After a user of an external website posts information to an external server, the external server stores the information of the user in addition to storing the information locally, and the website of the user belongs to the website to which the user's friend belongs, and the user's friend may be distributed in multiple Different websites. The external server sends the published information and the user's identifier to the server corresponding to the website to which the friend belongs through the publishing request. The server corresponding to the friend stores the user identifier in the publishing request together with the published information, the website identifier corresponding to the external server, and the like in a local information base.

When the server is in the subsequent matching process, if there is matching information from the external server, the website identifier or name corresponding to the external server is returned and presented together with the information record. The above-mentioned publishing request can be implemented by using the SOAP (Simple Object Access Protocol) protocol bound to the HTTP (Hypertext Transfer Protocol) protocol. Specific examples are as follows:

POST /publish HTTP/1.1

Content- Type: text/xml; charset="utf-8"

Content-Length: nnnn

SOAPAction: "http://www.example.com/publish/"

Host: www.example.com

<?xml version="1.0" encoding="UTF-8" ?>

<env: Envelope

Xmlns:env="http:〃 www.w3.org/2001/06/soap-envelope">

<env:Body>

<publish_blog xmlns="http:〃 www.example.com/schema/"> <domain>example</domain>

<domain_name>www.example.net</domain_name>

<uid>xyz@example.net</uid>

<txt>Hello World</txt>

</publish_blog>

</env:Body>

</env:Envelope>

The above SOAP protocol is bound to the HTTP POST method, and the message body includes the user identifier "uid" and the release information "txt". In addition, the ID "domain_name" and the name "domain" of the external server to which the user belongs are also directly included in the message body.

Referring to FIG. 8, the following is described in conjunction with the flowchart: Step 801: The server receives and saves the information published by the user of the website. Step 802: Query the user relationship record of the user, and determine an external server where the user friend is located. Step 803, the information is simultaneously published to the external server.

The seventh embodiment describes a method of media information sharing, such as music, video, and the like. The instant messaging client can collect media information of the media being played, such as music or movie information being played. The media information generally includes the name of the media, and may also include information such as album name, artist, etc. The media information is actually an application information. , generally can get media information from the media player. The client can also obtain the time information of the media playing, such as the start time. Specifically, if the instant messaging client is started after the media playing starts, the start time of the playing can be determined according to the playing time of the current media, and the instant communication is started when the media playing starts. Once the client has been started, the client can directly record the start time of the playback. The client can then publish the media information containing the playback start time; generally posted to the instant messaging service The server, which is distributed by the instant messaging server to the subscriber, is actually distributed to the user's friends. In addition, in order to avoid inaccurate time of the client, the following method may be used: When the client publishes the media information, the current playback progress information is posted to the server as the time information, and the progress information is the length of time that the current media has been played, if the media plays After the start, the instant messaging client starts, the progress time information is a positive number, which can be calculated in seconds; if the instant messaging client has started when the media playback starts, the corresponding media information can be immediately released, which is the corresponding progress. The time information is 0 seconds. After receiving the playback progress information, the server calculates the start time of the media play according to its own system time, and then replaces the play progress time in the media information with the play start time based on the server system time, and distributes it to the subscriber. The subscriber's instant messaging client can calculate the actual playback progress based on the difference between the recorded time and the server time. Since the time difference between the real-time request and response when the client communicates with the server is generally within a few seconds, it is possible to approximate the time when the client sends the real-time request to the server and the server time in the corresponding server response obtained. The difference is used as the system time difference between the client and the server. Considering the delay between the request and the response, it is also possible to increase the compensation amount by one or two seconds. Specifically, the system time difference value may be calculated according to a time in the SIP NOTIFY message sent by the server or a time in the 200 OK response message, such as Date or Timestamp header field information. The reason the server does not directly distribute the published playback progress is because the server may not be able to immediately distribute the playback progress. When the server receives the broadcast progress of the release, a friend has not yet been online. When the friend is online, since it has been a while, it is obvious that the original playback progress cannot be directly sent to him. Another solution is: if the server records the released play progress information and the current release time, when the server sends the play progress information, it needs to calculate the difference between the time of sending and the release time, and increase the difference to the play progress. Send it. Of course, if the server immediately distributes the received playback progress information, then It is necessary to calculate the difference and directly distribute the received playback progress information. When receiving the playback progress information distributed by the server, the client records its own system time, and the subsequent client can use the received playback progress information and the recorded system time of the current time to calculate the current actual playback progress. Thereby the synchronization process is performed. The friend's client obtains the subscribed media information, including the time information of the play. Usually, the client does not perform synchronization processing immediately after receiving the media information, but may be subsequently detected when the media information is detected, or when it is detected that the media information is selected. The synchronization process is performed. At this time, the client synchronously plays the corresponding media according to the played time information, or synchronously displays the lyrics or subtitle text of the corresponding media. The client can query the corresponding lyrics or subtitle files according to the music or video information in the media information, such as the title and the name of the artist. For example, the lyrics (Lyric) file is usually in the LRC format. The specific format is as follows:

[ti:Hello Goodbye]

[ar: Cheyenne Kimball]

[al:The Day Has Come]

[00:00.00]07. Hello Goodbye

[00:02.47]Am I speaking Japanese

[00:04.46]I told you 20 times when neat

[00:07. ll]but you still don't get it. It includes information such as the title, and each time the lyrics have time information, such as [00:02.47], the general format is "[mm:ss.fff]", that is, "minutes: seconds". The subtitle file format, such as SRT, is similar to the lyrics file and will not be described here. The client calculates the actual progress of the play according to the time information of the play, and then adjusts the displayed subtitle or lyrics locally to the corresponding time point. In addition, after obtaining the subscribed media information, the client can automatically invoke the search engine to query and download the corresponding media resource file, or the lyrics, subtitle text, and the like. If the media information includes the name of a song and the name of the singer, the media information is used as a search keyword to invoke the search engine to query, and the address of the media resource file or the lyrics, subtitle text, etc. can be further taken out from the query result. Then download it to the client. Of course, you can first search the corresponding media resource file locally on the client. If the local one already exists, you do not need to download it. Before the query or download, the user can also be prompted to confirm, and the query or download operation is performed after the user confirms. In addition, when the media information is published, the total duration information of the media may also be included, so that it can be determined whether the media has been played. After the client finishes playing a media, the client can play other media or repeatedly play the media. When detecting that any media starts playing, the client can release the media information. Referring to FIG. 9, an example is described below in conjunction with the flowchart: Step 901: The instant messaging client collects and publishes media information of the media being played, including time information of the media playing. In step 902, the server receives and distributes the media information. Step 903: The friend of the friend obtains the subscribed media information. Step 904, the search engine is invoked to query and download the media resource file corresponding to the media information. Step 905: Perform synchronization processing when it is detected that the person who is posting the media information is in a communication state, or when it is detected that the media information is selected. Referring to FIG. 10, a communication status interface for an instant messaging client to communicate with a friend mainly includes a chat text display area B1, a lyrics synchronization display area B2, a text input area B3, and a send button B4. The user inputs the text information in the text input area B3, and then clicks the send button B4 to send the text, the text information is displayed in the chat text display area B1, and the lyrics corresponding to the music being played by the friend are displayed in the The lyrics synchronization display area B2 can be scrolled from top to bottom. Many instant messaging clients provide the function of setting and displaying signature information. The signature information may be a piece of text input by the user or automatically obtained by the client. When a friend's signature information is displayed, a corresponding query button may be displayed at the same time; when the query button is clicked, the search engine is invoked to query by using the corresponding signature information as a search key. The results of the query can be displayed in an instant messaging client or browser. In this way, the user can conveniently query the information related to the signature of the friend on the Internet, and in particular, the related media resource file can be queried according to the media information. Of course, the relevant media resource file can also be queried locally on the client. There is no need for the user to copy the signature information or manually input it into the search engine, which saves the operation steps. If the signature information is the media information, the client downloads the corresponding media resource file according to the resource link provided by the query result when receiving the query result. The client can play while downloading, or it can be played after the download is complete. After the download is completed, a play button or a synchronous play button may be displayed next to the signature information. When the play button is clicked, the corresponding media can be played from the beginning, and when the synchronized play button is clicked, the synchronization information can be synchronized according to the time information in the media information. Play processing. Referring to FIG. 11, for the instant messaging client interface, a contact list, that is, a buddy list is generally displayed, and each buddy item display has an icon, a friend's name, and a signature. When the mouse is stuck to an item such as friend 1, the corresponding query button A1 is displayed after the signature information. If the signature information contains media information, after the media is downloaded or obtained the address of the media resource, a corresponding play button A2 is displayed after the signature information.

The eighth embodiment describes a method of querying a user's posting information using a search engine external to the microblog. Taking the webpage as an example, when a user visits a microblogging website, when displaying each information record in the webpage, a corresponding search button is simultaneously displayed; when the search button is clicked, the search engine is called to perform corresponding information recording content. Inquire. Specifically, you can display a "search" under each displayed information record. The "button" or the hyperlink. The code in the webpage source file corresponding to each "search" button or hyperlink is generated by the microblog server according to the content of each information record. For example, if the text content of a piece of information record is "Hello", then the corresponding "search" hyperlink source code generated by the server for this information record can be:

<a href = ' ' http ://www. example . com/s ?txt=Hello " target="_blank">Search</a> From the above, you can directly pass the text content of the information record to a search engine such as " Http://www.example.com/s" o

If there is more text in the information record, such as more than 30 Chinese characters, it is best not to pass all the text content directly to the search engine. The server may preset an upper limit of the number of characters, for example, 30. When the server detects that the text content of the information record is more than the preset text limit, the server extracts keywords in the text content of the information record, and transmits the extracted keywords to the search engine. For use by queries. In this way, the amount of information transmitted to the search engine is reduced, and the microblogging website knows more about the user. For example, when the user registers with the microblogging website, the user provides information such as hobbies, occupations, regions, etc., and the microblogging website can extract more suitable based on the characteristics of the user. Key words.

For example, if the keywords extracted by the server from an information record are "weekend" and "overtime", the server generates a corresponding "search" hyperlink for the information record. The source code can be:

<a href=''http://www.example.cn/search?q=weekend+overtime''> Search </a>

When the user clicks on the corresponding "search" hyperlink displayed under the information record in the browser, the browser sends an HTTP GET request to the search engine server, and the search result is returned to the browser in the response message. There are many types of information published by users. In addition to ordinary plain text information, image information can also be included. It can also include media information such as the name of the music being listened to, or the name of the movie being watched. The server can first judge the information record The content type, then call the appropriate search engine based on the content type. If it is detected that an information record only contains ordinary plain text information, it can be called by an ordinary general search engine, and if an information record is detected, in addition to the text information, the image search engine can be called. The text message and/or picture in the information record can be passed to the image search engine. If the server detects that the information record includes media information, the media information may include a media name, an artist name, a media type, and the like. The virtual blog of the microblog can publish the media information to the microblog server after obtaining the media name, artist name and media type information on the instant messaging client. The server transmits the media name and the like to the vertical search engine corresponding to the media type for query. The vertical search engine is specific to a general search engine, and is used for searching in a certain domain, such as an image search engine, a music search engine, or Video search engine, etc. For example, a virtual robot publishes an information record: "Listening to music: Blue and White Porcelain Jay Chou", the server determines the "listening music" as the music type media according to the content type in the message, corresponding to a music search engine, and the media name, artist The name is passed to the music search engine. The correspondence between the information type and the search engine can be pre-stored in the server. The "search" hyperlink source code generated by the server for this information record can be:

<a

Href="http://music.example.cn/m?w=%C7%E0%BB%A8%B4%C9+ %D6%DC%BD%DC%C2%D7">Search </a>

In addition, a button or hyperlink for "in-site search" can be provided for each information record displayed. When it is clicked, the server will query the information database in the station for information related to the information record. Referring to FIG. 12, for the interface for displaying information records in the browser, each information record displayed mainly includes a user name such as “User A” and a user's icon, and a text information content A13. If there is a picture content, it may also be The picture is displayed on the right. Below the information record you can display some hyperlinks such as "Comments" and "Search" All, "Site Search for "A12, etc." When clicking the "Search" All hyperlink, the search engine is called to retrieve the text information in the information record, and then the search result is displayed to the user in a new web page. Referring to Figure 13, the following is combined The flow chart is described by way of example: Step 1301: When the server detects that the text content of the information record is more than the preset text limit, the server extracts keywords in the text content of the information record.

Step 1302: Determine the content type of the information record, and invoke the corresponding search engine according to the content type.

Step 1303: Generate a search hyperlink that inquires the corresponding search engine to query the extracted keywords.

In step 1304, when each piece of information is displayed, a corresponding search hyperlink is simultaneously displayed.

In the seventh and eighth embodiments described above, the corresponding search button is provided on the webpage or the instant messaging client interface, so that the user can perform the corresponding search directly by one click operation. It is also possible to call the corresponding search engine to search according to the type of information, and download the searched media resource file, and then play it synchronously. The ninth embodiment describes synchronization of an application (such as media playback) based on an event initiation and notification mechanism of the Session Initiation Protocol (SIP). Here, media playback is taken as an example. The information required to simultaneously play media between different clients mainly includes the media name and playback progress. The key issue of synchronization is how to accurately deliver the actual playback progress information, because different clients The system time between them is likely to be inconsistent, and the user can arbitrarily set the system time of his or her computer or mobile phone for some purposes. Other applications such as map programs for synchronization (ie, synchronous application interface scenarios) may require current map coordinates, etc., to enable different clients to simultaneously display substantially the same map scene. The client first obtains the system time of the server, which may be based on some time sent by the server, such as a SIP NOTIFY message or a 200 OK response message. Date or Timestamp header field information. This allows you to calculate the system time difference between the client and the server. The first client uses the SIP PUBLISH publishing method to publish the media information event package to the server. The event package includes media information, and the media information includes the start time of the media playback. The start time is based on the system time of the server, not the client system. time. Specific examples are as follows:

PUBLISH sip:usera@example.com SIP/2.0

Event: mediainfo

Content- Type: application/mediainfo+xml

<?xml version="1.0" encodings "UTF- 8 "?>

<tune>

<title>example music</title>

<server_start_time>2008-01-09Tl 1 :10: 00Z</server_start_time>

<total_time>242</total_time>

</tune>

</mediainfo> In the PUBLISH message, the name of the event package is "mediainfo", and the content type of the event package is "application/mediainfo+xml". Other SIP fields are omitted for clarity. The contents of the event package include some information of the current music "tune", such as the music title name "title", and the total duration of the music "totaUime", etc., and the system time "server_start_time" of the server at the start of the music. If the music resource can be obtained from a specific address, it may also include a corresponding resource The address is "uri". If the played music is a local media file, you can provide some file information at the same time, so that the other client can download the same file, such as the file size "size", the file name "name", and the file name should include the file suffix, so that Identify the file type. The file can also include the hash value "shal" of the file data.

The second client subscribes to the media information event package corresponding to the friend by using the SIP SUBSCRIBE subscription method, and the server distributes the media information event package published by the first client to the subscriber, such as the second client, by using the SIP NOTIFY notification method. After receiving the media information event package, the second client may calculate the playback start time, that is, the actual playback progress, according to the difference between the system time and the server system time, thereby performing synchronization processing. A method for calculating the system time difference between the client and the server is to record the client local time T1 when the client sends a real-time request message (such as SIP INFO), and the server local system after receiving the request. Time T2 is placed in the response message (such as 200 OK), and the client obtains the current client system time T3 when receiving the response message, and the system time difference between the client and the server can be approximated as: (T1+T3) /2 -T3, which is the difference between the time when the client sends the request and the time when the response is received and the time the server returns in the response. Referring to FIG. 14, the client sends a real-time request to the server at the first time T1, and the request takes X in the network, and the server returns its own system time, that is, the second time T2, to the client in response, which takes time Y. The client receives the response at the third time T3. If X and Y are similar or have small values, the calculated system time difference between the client and the server will be more accurate. Note that the selected request and response messages preferably have a good real-time performance, that is, the server can return the response in near real time, and does not need to spend more time processing, such as the processing time of the server is preferably no more than 1 second. If the server needs a certain amount of time to process, it is better not to receive the request message or to send the response message. The accuracy of the difference is determined by the request message from the client to the server. The difference in the time that the server-to-client response message is transmitted over the network is actually very short, and the network that travels back and forth is basically the same, so the difference is small. This not only fully considers the transmission time of the message in the network, but also considers the processing time of the server, so that the difference is more accurate, and the synchronization effect is better. Alternatively, the client can obtain the system time of the server by the time protocol defined by RFC 868. Referring to FIG. 15, an example is described below with reference to the flowchart: Step 1501: The first client uses the SIP PUBLISH publishing method to issue a media information event packet to the server, where the media information includes a media playback start time based on the system time of the server.

Step 1502: The server sends the media information event package published by the first client to the second client by using a SIP NOTIFY notification method. Step 1503: After receiving the media information event package, the second client calculates an actual playback progress according to the difference between the system time and the server system time. Step 1504: The second client performs synchronization processing according to the actual playback progress. The tenth embodiment describes the interworking of a microblogging website with a presence service or an instant communication service. The micro-blog information published by the user through the mobile phone, the computer, and the like can also be used as the presentation information at the same time, and can be implemented as follows: The micro-blog server receives the information posted by the user, including text information and picture information. Then put this information into the corresponding rendering information element, such as:

<text>very yellow, very violent</text>

</microblog> The microblogging element "microblog" may include text information such as "text", and may also include sub-elements such as picture information such as "picture". The microblog server includes the presence information element in the presence information event package, and passes it through the SIP PUBLISH method. Or the XCAP (XML Configuration Access Protocol) protocol is published to the presence server or instant messaging server. In addition, the micro-blog server records the SIP identifier set by the user, that is, the user identifier of the service or instant communication service, such as ''sip:usera@example.com'), and may also be a logo such as a number or a phone number. When the presence information is published, the identifier of the user is included in the presence information document. After receiving the microblog presence information, the presence server or the instant communication server may merge the presentation information with the other presentation information of the user according to the user identifier. Then, the subscribers who distribute the information to the user are distributed. Thus, the user can publish the micro-blog information as the presentation information at the same time, which saves time and operation steps. Referring to FIG. 16, the following description will be described with reference to the flowchart. Step 1601: The microblog server receives the information posted by the user. Step 1602: Convert the information into a corresponding presentation information element. Step 1603: Publish information to the presence server or the instant communication server by using the SIP PUBLISH method or the XCAP protocol. The embodiment mainly describes the bit The information record of the attribute. In fact, the micro-blog can also serve as a platform for the general public to publish news messages, and the user can post news events to the micro-blog website through short messages, multimedia messages or web pages. The method makes the news dissemination more timely and direct. In order to distinguish the material information released by the user from other common information, the notification function identifier can be added in the posting information. For example, as follows, the information published by the user through the short message is "reporting". If Merlin closes the traffic jam, the server will detect the message and report the "report" of the message, and then save the information content part of the message function after the follow-up space "Merlin shut traffic jam". And marking the saved information record as the report information. If the user posts the report information through the webpage, the default initial content is set to the report function identifier such as "report" in the text box provided to the user for inputting the report information. This The user does not have to enter it again. Other special information input can also be used in this way, such as input of memo information, setting the default initial content in the text box provided to the user to input the memo information as a memo function identifier such as "*" or "ready" Wait.

Many news events are related to location, especially for ordinary users to report, but the location information provided by the user may not provide location information or the location information provided is inaccurate. In addition, the user sometimes wants to record the location of the information he posted, and can only view the location attribute of the published information for himself or some friends. Therefore, how to add location attribute information to the information posted by users is a problem worth solving. After receiving the information sent by the user, the microblog server may send a location query request to the positioning system according to the mobile phone number registered by the sender on the website registration, and the location query request includes the mobile phone number of the user. Then, the current location information corresponding to the mobile phone number returned by the positioning system is received, and the location attribute is determined according to the current location information. Since the location information relates to the privacy of the user, the user generally sets an authorized microblogging website in the positioning system to obtain his own location information, and can also set the accuracy of the provided location information. The microblog server sends a location query request to the location system to carry the service provider SP identifier of the microblog. The location system determines whether the server has the right to obtain the user location information according to the SP identifier, and if so, provides the location information of the corresponding precision. The positioning system can also return location information of multiple precisions at the same time, and the microblog server provides location information of corresponding precision to different information viewers according to the user's settings, such as providing city information to non-friend users, and providing more accurate areas to friends. Information, and you can view accurate coordinate information and so on.

In addition, after receiving the sent information, the short message center or the multimedia message center initiates a location query request to the home location register HLR corresponding to the mobile phone number of the sent information, and inserts the obtained location query result into the information, and then forwards the information. To the microblog server, the microblog server queries according to the location in the information The result determines the location attribute. If the original text message sent by the user terminal through the short message or the multimedia message is "reporting five cars collided together", the short message center or the multimedia message center requests from the mobile application part MAP (Mobile Application Part) protocol such as MAP_Any_Time_Interrogate The HLR queries the location information, ie, the cell identifier (Cell-ID), and then translates it into latitude and longitude data or location name information that can be directly applied, and inserts the latitude and longitude or location name into the original text information, such as "·3⁄4 five cars collided Together!! Shenzhen Nanshan." Here, the location information is inserted at the end of the original information, and the location identifier "/!" is added before the location information to distinguish it from the ordinary text information content. The short message center or the multimedia message center sends the information of the location information to the microblog server, from which the microblog server parses the included location information, and then saves the information content part "five cars collided together" with the location information. . Note that depending on the user's location permission settings, even if you can query the content of a message, you may not be able to view the corresponding location information. Of course, for some less accurate location information, the user can not limit the viewing rights. It is also possible to determine the location attribute based on the IP address of the sender of the message. If the user client posts information to the server through the webpage, the server obtains the IP address of the client. The WHOIS service of the Internet can generally obtain the city to which the IP address belongs, and the city name can be used as the location attribute of the information. Similarly, the location attribute is determined based on the attribution of the telephone number of the sender. For example, if the number of the mobile phone number in China or the area code of the telephone number has a fixed correspondence with the city, the name of the home city of the telephone number can be used as the location attribute of the information. If you want to publish information and simultaneously search for information records that match the location attribute of the published information, you can retrieve information records with the same or similar location attributes in the repository at the time of publication. For example, the same city or administrative district name, or the distance calculated from the latitude and longitude coordinates of the location is within the preset range. In addition, when an information viewer obtains information from the server, the server may first obtain the location information of the information viewer, and then retrieve information records having the same or similar location attributes in the information repository, and return the matched information records to the information browsing. Client's client. Users generally fill in the city or region where they live when registering, but this may not be the city or region where the user posted the message. The microblogging website can provide browsing information by location information, such as providing location hyperlinks of various provinces or regions on the webpage, corresponding to information records published by users in different provinces or regions. When the user clicks on a hyperlink in a province or region such as "Guangdong", the server returns to the browser an information record whose location attribute matches "Guangdong". And it can further display the city hyperlinks in the province or region, such as the "Shenzhen" location hyperlink, corresponding to the information records published by the users located in the city, and so on can be accurate to the "administrative area" and the like. The server can calculate the total number of information records published on the current day of each location, and display the total number of corresponding information records after each generated location name in the generated page provided to the browser, if the number of information records corresponding to a certain location is Zero, the location name is not displayed. Referring to FIG. 17, the left side is the information record display area D1, and the information record matching the selected position is displayed, and the right side displays the sub-area hyperlink included in the current position, such as "Futian District (56), D2, where the number indicates The total number of information records corresponding to the location area. The user's report information can be displayed together, such as adding a "report" subpage. Referring to Figure 18, the browser is displayed to observe a user such as "User A". The page, in which the user A related messages are divided into several categories, such as "message" C1, "and friends'messages" C2, and "reports" C3, etc. When clicking "report" C3, in the information record In the display area C4, the information of the information sent by the user is displayed, and the information records can be sorted in the order of the publishing time. Referring to FIG. 19, the following describes the location attribute matching of the information viewer by using the flowchart: Step 1901 The information viewer requests the server to obtain the information record. Step 1902: The server acquires the location information of the information viewer. Step 1903: Search the information library to have the same or similar location attribute information record. Step 1904, and returning the matched information record to the client of the information viewer. It can be seen that this embodiment enables the user to obtain information related to the matching of his own location by generating and saving the location attribute for the information record. More generally, in fact, for speech or self-speaking without certain objects, it is suitable for posting in microblogs, such as newspapers, etc., and users can also post their wishes on microblogs and express what they want. Wait. Referring to FIG. 18, the specific implementation may add a "wish" sub-page C6 similar to "report", and centrally display the "wish" information published by the user. The information published by the user includes the function identifier corresponding to the "wish", and the server This identifies the type of information and stores the type of information along with the content of the information in the repository. This "wish" information is more valuable than other information because it generally reveals the user's needs and can be used to match the appropriate advertising information to the user. In addition to identifying the type of information with a clear function identifier, it is also possible to determine whether it is a "wish" type of information through semantic analysis, such as a user posting a message "want to change a mobile phone", a "thinking" keyword through which to express a will, and a follow-up The verbs and nouns that follow, can determine that the information is of the "wish" type of information, and the server stores the information while storing the identified "wish" types together. After the information is released, the server can return the advertisement information related to the "mobile phone" and present it on the page after the information is published. Similarly, a "problem" sub-page C5 can be added, the user can post his own question information, and other users can answer the question by replying to the question information. One of ordinary skill in the art can understand that all or part of the steps of implementing the foregoing embodiments may be performed by a program to instruct related hardware, and the program may be stored in a computer readable storage medium. , performing all or part of the steps in the above embodiment methods. The above-mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like. As shown in FIG. 20, the microblog server may include: an information receiving unit E1, configured to receive information sent by the user client, and record the information to the information storage unit Ε3, and notify the search matching unit Ε2 to the information storage unit Ε3. Information recording The information matching unit E3 is configured to record the information received by the information receiving unit E1, and corresponds to the information base in the above embodiment, and uses the database to store the information record; the search matching unit E2 is used to receive the information received by the information receiving unit. A matching information record is searched in the information storage unit E3, and the matched information is returned to the client. As shown in FIG. 21, the server may further include an automatic labeling unit E4 for automatically labeling the information received by the information receiving unit E1, and then saving the information together with the automatically generated label to the information storage unit E3. The virtual robot unit E5 may be further configured to receive an instant message and/or presence information sent by the user to the virtual robot by using an instant message tool, and save the content to the information storage unit E3, and notify the search matching unit E2 to the information storage unit E3. The information record in the search matches, and the matching information is returned to the client through an instant message. As shown in FIG. 22, the application information sharing tool, that is, the client, may include: an information collecting unit F1, configured to collect information of an application running in the user terminal; and an information publishing unit F2, configured to collect the information collected by the information collecting unit F1. The application information is released; the information receiving unit F3 is configured to receive the published application information of other users; and the application starting unit F4 starts the corresponding application according to the application information received by the information receiving unit F3.

As shown in FIG. 23, the application information sharing tool may further include a query unit F5 for searching the application information received by the information receiving unit F3. The application information may be media information, and may further include a downloading unit F6 for downloading a corresponding media resource file according to the search result obtained by the query unit F5. The synchronous play unit F7 is further configured to perform synchronous play processing according to the play time information in the media information and the media resource file acquired by the download unit F6. By collecting application information and sharing it after structuring, search technology allows users to discover other users who use similar applications and can enter the same or similar application scenarios based on structured application information. In addition, by transmitting the media information including the playing time information, and preferably using the system time on the server side, the media can be accurately played between different clients. Step processing. Search technology can also be used to query and download the corresponding media resource file. For some specific processing details in the microblog server and the application information sharing client, reference may be made to the above several embodiments, and details are not described herein again. The UI server can be an instant messaging server, and the application information sharing client can be an instant messaging client. Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by hardware, or can be implemented by means of software plus necessary general hardware platform, and the technical solution of the present invention. It can be embodied in the form of a software product that can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), including a number of instructions for making a computer device (may It is a personal computer, a server, or a network device, etc.) that performs the methods described in various embodiments of the present invention.

In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Rights request

2. The method according to claim 1, wherein after receiving the information sent by the user, generating a corresponding label for the information;

When the information is recorded, the corresponding label is simultaneously recorded;

The tag is used to search for an information record that matches the content of the information.

3. The method according to claim 2, wherein the step of using the tag to search for an information record that matches the content of the information is specifically: when searching for information records that match the information Obtaining an information record having the same label as the information, and recording the information having the same label as matching information.

The method according to claim 2, wherein when the information is recorded to the information base, an index entry is generated for the information record, and the index item is saved to the index library, which is also included An index entry generated by the correspondence between the label and the information;

When searching for an information record that matches the content of the information, extracting keywords in the information, using the keywords and the tags to search and match index entries in the index library, and in the information base Obtaining an information record corresponding to the matched index item, and recording the corresponding information as matching information.

The method according to any one of claims 1 to 4, wherein the filtering setting of the matching message sender attribute by the user is saved in advance;

When searching for an information record that matches the content of the information, the filtering settings are applied to the sender of the information record at the same time.

6. The method according to claim 5, wherein the matched information is sorted by matching degree and/or publishing time, and returned and presented.

7. The method according to claim 1, wherein after the user enters the chat room, an information record that the user has recently transmitted is displayed in the chat room.

8. The method according to claim 7, wherein the matching information is returned and presented, and the identifier of the chat room where the sender of the matched information is located is also returned and presented together.

9. The method according to claim 1, wherein the information sent by the user includes application information;

The information recording of the information matching the content of the information is specifically performed by searching for an information record that matches the application information in the information.

The method according to claim 9, wherein the information sent by the user is acquired by the client and the application information is released on the terminal;

The client receives and presents the returned matching information;

The corresponding application is launched based on the application information in the matching information.

11. The method according to claim 1, wherein only the matching information that does not exceed the preset upper limit is sorted by the posting time, returned, and all presented in one page.

12. The method according to claim 1, wherein if a matched information is reply information, the corresponding link or content of the original information is also returned.

13. The method according to claim 1, wherein if the information posted by the user is the memo information, the matching information record is searched only in the memo information that has been published before the user releases the self.

14. The method according to claim 1, wherein if a user who detects the posting of information is bound to a channel or a column, only the matching information record is searched within the channel or column.

15. The method according to claim 1, wherein the corresponding advertisement information is obtained according to the user information and/or the information published by the user and/or the matched information, and the advertisement information is matched with the matched information. Return and render.

16. The method according to claim 1, wherein the range of the search is determined according to a manner in which the user issues the information, and the matched information is searched for within the determined range. Recorded.

17. The method according to claim 1, wherein after receiving the information sent by the user, the search request is further sent to the external server, and after the matching external information record is obtained, the matching degree of the external information record is calculated. All information records including the external information record are then sorted by matching degree and returned and presented.

The method according to claim 17, wherein the search request is a GET or POST request method of an HTTP protocol, and the search request includes a user identifier of the published information and the posted information;

After receiving the search request, the external server queries the friend relationship record corresponding to the user identifier, and retrieves an external information record that matches the release information in the search request in the information published by the friend, and then The external information record is returned.

19. The method according to claim 1, wherein the publishing request sent by the external server is further received, and the content in the publishing request is stored in a local information base.

The method according to claim 19, wherein the publishing request is an HTTP-based SOAP protocol method, and the message body of the publishing request includes a user identifier and the published information;

After receiving the publishing request sent by the external server, the user identifier in the publishing request is stored in the local information repository together with the published information and the website identifier corresponding to the external server.

21. The method according to claim 19, wherein if the matching information is from an external server, the website identification name and the information record corresponding to the external server are returned and presented together.

22. The method according to claim 1, wherein after receiving the information sent by the user, generating a location attribute for the information;

An information record matching the location attribute of the information is searched in the information base, the information is published, and the information and its corresponding location attributes are recorded together in the information base.

The method according to claim 22, wherein the method for generating a location attribute is one of the following methods: Sending a location query request to the positioning system according to the mobile phone number bound by the sender, and determining the current location information corresponding to the mobile phone number returned by the positioning system, and determining the location attribute according to the current location information;

Alternatively, after receiving the sent information, the short message center or the multimedia message center initiates a location query to the home location register corresponding to the mobile phone number of the sent information, and inserts the location query result into the information, and then forwards the message to the microblog. a server, the microblog server determines a location attribute according to the location query result in the information;

Or determining a location attribute according to an IP address of the sender;

Alternatively, the location attribute is determined according to the attribution of the telephone number of the sender; or the location information is inserted into the transmitted information by the client of the sender, and the server determines the location attribute based on the location information.

24. A method of processing information sent by a user, the method comprising the steps of: receiving information sent by a user;

25. The method according to claim 24, wherein the request for the information viewer to obtain the information record is received;

Obtain location information of the information viewer;

An information record having a location attribute matching the location information is retrieved in the information repository, and the matched information record is returned to the client of the information viewer.

The method according to claim 24, wherein the method for generating a location attribute is one of the following methods:

Sending a location query request to the positioning system according to the mobile phone number bound by the sender, determining the current location information corresponding to the mobile phone number returned by the positioning system, and determining the location attribute according to the current location information;

Alternatively, after receiving the sent information, the short message center or the multimedia message center initiates a location query to the home location register corresponding to the mobile phone number of the sent information, and inserts the location query result into the information, and then forwards the message to the microblog. a server, the microblog server determines a location attribute according to the location query result in the information; Or determining the location attribute according to the IP address of the sender; or determining the location attribute according to the attribution of the sender's phone number; or inserting the location information into the sent information by the client of the sender, the server according to The location information determines a location attribute.

27. A method of processing information published by a user, the method comprising the steps of: simultaneously displaying a corresponding search button when displaying the information record;

The method according to claim 27, wherein if it is detected that the text content of the information record is less than the preset text limit, the text content of the information record is directly transmitted to the search engine for query.

The method according to claim 27 or 28, wherein if it is detected that the text content of the information record is more than a preset text limit, the keyword in the text content of the information record is extracted, and The extracted keywords are transmitted to the search engine for query.

The method according to claim 27, wherein, if the media information is included in the information record, the media information includes a media name and a media type, and the media name is transmitted to a vertical corresponding to the media type. The search engine makes a query.

31. A method for media information sharing, the method comprising the steps of:

Obtain the media information subscribed to;

32. The method according to claim 31, wherein when it is detected that the person who is posting the media information is in a communication state, or when the person who publishes the media information is detected to be selected, the corresponding time information is synchronously played according to the time information. Media, or synchronously display the lyrics or subtitle text of the corresponding media.

33. The method of claim 31, wherein obtaining the subscribed After the media information, the search engine is automatically invoked to query and download the corresponding media resource file and/or the lyrics subtitle text.

The method according to claim 31, 32 or 33, wherein the time information is playback progress information, and the server records the released play progress information and the release time at that time;

When the server sends the play progress information, the difference between the time of sending and the release time is calculated, and the difference is added to the play progress and then sent;

When obtaining the subscribed media information, the client receives the playback progress information sent by the server, and records the current system time of the user;

When the client performs the synchronization process, the current actual playback progress is calculated according to the received playback progress information and the corresponding system time.

35. The method according to claim 31, 32 or 33, wherein the event package containing the media information is issued by the publishing method of the session initiation protocol, and the time information of the play included in the media information is the server system at the start of the play. Time

After obtaining the subscribed media information, the actual playback progress is determined by the difference between the local system time and the server system time, and then the synchronization process is performed.

36. The method according to claim 35, wherein the difference between the local system time and the server system time is obtained by the following method:

The first time when the client records the request message;

The second time the server returns in the response message;

The client uses the third time when the response message is received and the mean of the first time to subtract from the second time to obtain a difference.

37. A method for processing instant messaging signature information, the method comprising the steps of: displaying a corresponding query button simultaneously when displaying the signature information of the friend; and searching for the corresponding signature information when the query button is clicked The keyword calls the search engine to query;

Receive the query results and display them.

The method according to claim 37, wherein the signature information is media information, and when the query result is received, the resource chain is provided according to the query result. Then download the corresponding media resource file.

39. The method according to claim 38, wherein the media information includes time information of media playback;

After the corresponding media resource file is downloaded, a synchronous play button corresponding to the signature information is displayed;

When the synchronous play button is clicked, the actual play progress is determined according to the time information of the media play, and the synchronous play process is performed.

40. A method of providing presence information, the method comprising the steps of:

41. A server, comprising:

The server according to claim 41, wherein the server further comprises at least one of the following units:

The automatic labeling unit is configured to automatically mark the information received by the information receiving unit, and then save the information together with the automatically generated label to the information storage unit; the virtual robot unit is configured to receive the user sending the virtual robot to the virtual robot by using an instant message tool. The instant message and/or the presence information is saved to the information storage unit, and the search matching unit is notified to perform search matching on the information record in the information storage unit, and the matching information is returned to the client through the instant message.

43. A client, characterized in that: An information collecting unit, configured to collect information of an application running in the user terminal; and an information publishing unit, configured to publish the application information collected by the information collecting unit;

44. The client according to claim 43, wherein the application information is media information, and the client further comprises at least one of the following units:

a query unit, configured to search for media information received by the information receiving unit; and a downloading unit, configured to download a corresponding media resource file according to the search result obtained by the query unit;

The synchronous play unit is configured to perform synchronous play processing according to the play time information in the media information and the media resource file obtained by the download unit.

45. A microblog browser interface, wherein the information record is displayed on a corresponding subpage according to a type of information, and the subpage includes at least one of the following:

A sub-page for displaying information records of the type of the report;

Question sub-page, an information record for displaying the type of question;

A wish subpage, a record of information used to display the type of wish.

46. The microblog browser interface of claim 45, wherein a search hyperlink is displayed correspondingly below each of the information records.

47. A system, comprising: a microblog server, the microblog server including an information receiving unit, an information storage unit, and a search matching unit,

The information receiving unit is configured to receive information sent by the user client, and record the information to the information storage unit, and notify the search matching unit to perform search matching on the information record in the information storage unit.