Patent Application
20180034752
A discussion group is a synchronized conversation using a messaging application such as Twitter™. For example, there currently are discussion groups related to health issues (diabetes, lupus, weight loss, postpartum depression, etc.), hobbies (movies, wine, skiing, photography, food, sports, cars, etc.), and education (elementary school teachers, college professors, thesis writing, etc.). Typically, participants in a discussion group agree on a topic identifier for the discussion group to use (e.g., a hashtag). The participants may then participate in the discussion group by following the topic identifier, and/or generating messages that include the topic identifier.
Discussion group may further include any set of messages related to a common topic. Examples of such groups may include a set of user generated online reviews related to a particular restaurant or product. In another example, a discussion group may be a thread or chain of comments related to a topic on an online message board, or comments associated with a particular article or blog posting.
While these discussion groups are useful for their participants, they may also be relevant or useful to users who have an interest in the topic that is discussed in the group. For example, a user who is researching a health issue may find the messages from a discussion group related to the health issue useful, or may wish to participate in the next scheduled discussion group. In another example, a restaurant may be interested in what users are saying about the restaurant in a discussion group related to local restaurants, or in comments associated with the restaurant on a website for providing restaurant reviews. However, there is no way to easily search for and identify relevant discussion groups for a particular topic or query, making it difficult for interested parties to be made aware of such groups or to make use of information provided in the discussion groups.
Messages are collected and processed to determine topic identifiers that correspond to discussion groups. A query is received and multiple discussion groups that are relevant to the query are determined based on the messages that are associated with the discussion groups and the topic identifiers associated with the discussion groups. The relevant discussion groups are ranked using a group preference model that simulates the behavior of a hypothetical seeker that considers discussion groups by selecting a message author who is an authority in a particular group, and exploring the discussion groups that are preferred by the selected author. The behavior of the seeker is simulated using a stationary Markov process and is used to generate a probability distribution that is used to rank the relevant discussion groups. The ranked relevant discussion groups are provided in response to the query.
In an implementation, a query is received by a computing device. A plurality of discussion groups that are relevant to the query is determined by the computing device. Each discussion group is associated with a plurality of messages and each message is associated with an author. For each discussion group of the plurality of discussion groups, an authority score for each author associated with a message in the discussion group is determined by the computing device. For each author associated with a message, a preference score for the author for each discussion group of the plurality of discussion groups is determined by the computing device. The discussion groups of the plurality of discussion groups are ranked using the preference scores and the authority scores by the computing device.
In an implementation, a plurality of messages is received at a computing device. Each message includes a topic identifier and is associated with an author. Topic identifiers of the plurality of messages that represent discussion groups are determined by the computing device. A query is received at the computing device. Topic identifiers of the determined topic identifiers that are relevant to the received query are determined by the computing device. The determined topic identifiers are ranked based on the messages that include the determined topic identifiers by the computing device. The ranked determined topic identifiers are provided in response to the query by the computing device.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
The foregoing summary, as well as the following detailed description of illustrative embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the embodiments, there is shown in the drawings example constructions of the embodiments; however, the embodiments are not limited to the specific methods and instrumentalities disclosed. In the drawings:
In some implementations, the client 110 may include a desktop personal computer, workstation, laptop, personal digital assistant (PDA), smart phone, cell phone, or any WAP-enabled device or any other computing device capable of interfacing directly or indirectly with the network 120. The client 110 may be implemented using one or more computing devices such as the computing device 800 illustrated in
The message service 170 may be configured to provide a messaging application that allows users to generate messages 173 using a client 110. Typically each user of the message service 170 is assigned a user account identifier such as a word, phrase, or number. The user may then use the message service 170 to send messages 173 to specific user accounts, or may use the message service 170 to more broadly publish their messages 173 where other users can chose to view them. The messages 173 generated by the message service 170 may be stored and/or published as message data 175. The user account or user that generates a message 173 is referred to herein as the author of the message 173.
For example, a user may use the message service 170 to “follow” a particular user account, and may receive some or all of the messages 173 that are generated by the followed user account. In some implementations, users of the message service 170 may be able to search the messages 173 generated by users that include specific key words, or that were generated using specific user accounts. An example message service 170 may include Twitter™ and the messages 173 may include tweets™. Other message services 170 and/or message 173 types may be supported. Another example of a message service 170 may be a source for online reviews such as Amazon.com™ or Yelp™, or a commenting system such as Disqus™. The messages 173 may include text messages, audio messages, video messages, and combinations thereof.
Each message 173 may include some amount of text or characters. Depending on the implementation, the number of characters in each message 173 may be limited or may be effectively unlimited. For example, in some implementations each message 173 may be limited to 140 or fewer characters. In addition, each message 173 may be associated with a date. The date may be the approximate date and time on which the associated message 173 was generated or sent. Other types of data may be associated with, or part of a message 173. For example, messages 173 may include URLs, images, videos, and other media types.
Each message 173 may further include what is referred to herein as a topic identifier. A topic identifier may identify a topic, theme, or subject associated with the message 173 it appears in. Examples of topic identifiers include hashtags. Other types of topic identifiers may be used. A hashtag is a string of characters that begins with the pound sign (“#”). Authors may add a topic hashtag to a message 173 to indicate that it belongs to, or is associated with, the topic or subject associated with the hashtag. Thus, for example, in a message 173 about their dog's health, an author may add hashtags such as #dog, #pet, #veterinarian, etc.
Where the messages 173 are online reviews, the topic identifier may be an identifier of the thing (e.g., restaurant, product, or service) being reviewed. Where the messages 173 are part of an online discussion or message board, the topic identifier may be the subject of the particular thread, or an identifier of the article or post that is being discussed.
The message service 170 may allow users to search the message data 175 using the topic identifiers. For example, a user may query the message service 170 for all messages 173 that include the topic identifier #dog. The message service 170 may then return all messages 173 that include the topic identifier #dog. In addition, the message service 170 may also allow users to follow a particular topic identifier. Continuing the example above, a user may select to follow the topic identifier #dog. When a message 173 that includes the topic identifier #dog is generated by another user of the message service 170, the message 173 is provided to every user that follows the topic identifier #dog.
The use of topic identifiers in messages 173 may allow users to organize their messages 173 into what is referred to herein as a discussion group. In some implementations, during a discussion group, participants in the discussion group may send and receive messages 173 that include an agreed upon topic identifier at or around an agreed upon time. Each participant in the discussion group may then receive each message 173 that includes the agreed upon topic identifier during the discussion group, and may respond to one or more of the messages 173 creating a discussion. Typically, the discussion groups are held at a regular agreed upon time (e.g., once a week) and last for an agreed upon duration of time (e.g., one hour). In some instances, a discussion group may include an agreed upon user to act as a moderator and to highlight particular messages 173 that include the agreed upon topic identifier for the users of the discussion group to discuss. Alternatively, a discussion group may not have an agreed upon time or duration, but may be participated in merely by generating messages 173 for a particular website or in particular thread or comment chain. Discussion groups exist on a variety of topics including entertainment, health, finances, and sports, for example.
Depending on the implementation, a topic identifier may be associated with a discussion group if it is one or more of periodic, synchronous, and cohesive. Alternatively, any topic identifier may be associated with a discussion group regardless of whether or not it is periodic, synchronous, or cohesive.
A topic identifier may be periodic if the messages 173 associated with the topic identifier are generated or sent by authors according to a periodic schedule (e.g., every predetermined number of seconds, minutes, hours, etc.). The period may be hourly, daily, weekly, biweekly, monthly, etc. Other periods may be used.
A topic identifier may be synchronous if the messages 173 associated with the topic identifier are generated or sent by authors during a duration of time. This duration may be an hour, two hours, three hours, etc. Other durations may be used. For example, for a discussion group that has a period of one week and lasts an hour, the duration is one hour.
A topic identifier may be cohesive if some predetermined number or fraction of the messages 173 associated with the topic identifier represent communications between user accounts. For example, the topic identifier may be determined to be cohesive if at least about 20% of the messages 173 associated with the topic identifier are communications between user accounts. Other percentages may be used. In another example, the topic identifier may be cohesive if a threshold number of user account pairs that use the topic identifier communicated with each other using the topic identifier.
In order to allow users to search for and identify relevant discussion groups, and topic identifiers associated with the relevant discussion groups, the environment 100 may further include a discussion group engine 180. The discussion group engine 180 may receive message data 175 from the message service 170, and may identify topic identifiers that correspond to discussion groups. The identified topic identifiers that correspond to discussion groups, and the messages 173 that include the identified topic identifiers, may be stored by the discussion group engine 180 as the discussion group data 185.
In addition, the discussion group engine 180 may further receive one or more queries 112 from clients 110, and may identify discussion groups that are relevant to the queries 112. For example, the discussion group engine 180 may search for topic identifiers that include one or more terms of the query 112, or that include one or more terms that are known to be related to the query 112. Alternatively or additionally, the discussion group engine 180 may search for messages 173 that include one or more terms, or related terms, of the query 112, and may determine the topic identifiers associated with any matching messages 173 to be discussion groups that are related to the query 112. The relevant discussion groups may be identified and provided as results 130. Information such as when the identified discussion groups occur, and their duration may also be provided.
In some implementations, the discussion group engine 180 may also rank the relevant discussion groups according to what is referred to as the group preference model. The group preference model attempts to model how a hypothetical user (referred to as the seeker) would select relevant discussion groups from a set of discussion groups that are relevant to a query 112.
According to the group preference model, the seeker initially choses a discussion group from the set of relevant discussion groups. The seeker then reviews some of the messages 173 associated with the discussion group and determines an author that appears to have some authority among the participants of the discussion group. Authority may be determined by the seeker based on the number of messages generated by the author or by the number of direct replies that the author receives. Other methods for determining or measuring authority may be used.
After selecting an author with high authority, the seeker may then determine other discussion groups that the selected author participates in or has a preference for. These groups may be other discussion groups from the set of relevant discussion groups. The discussion groups that the author participates in may be determined from a profile page associated with the author, or based on the messages 173 associated with the author. For example, an author may generate more messages 173 for discussion groups that the author has a high preference for than discussion groups that the author has a low preference for.
According to the group preference model, the seeker may then continuously alternate between authors and discussion groups as described above until the seeker ultimately selects a discussion group that they are satisfied with. After multiple iterations of the group reference model, the seeker may ultimately select multiple discussion groups of the relevant discussion groups forming a distribution. As described further with respect to
The discussion group identifier 210 may receive message data 175 and may determine one or more topic identifiers that are likely to be associated with a discussion group. As described above, one of the characteristics of a discussion group is that it is periodic. In some implementations, the discussion group identifier 210 may extract the topic identifiers from the messages 173 that are included in the message data 175, and may consider whether each extracted topic identifier is periodic. Alternatively, the discussion group identifier 210 may receive a set of topic identifiers to consider. For example, a user or administrator may preselect a set of topic identifiers that may be associated with discussion groups, or the set of topic identifiers may be collectively identified.
The discussion group engine 180 may, for each topic identifier in the message data 175, determine if the topic identifier is periodic. The discussion group engine 180 may determine if a topic identifier is periodic by retrieving each message 173 associated with the topic identifier, and may determine if the topic identifier is periodic based on the times associated with each message 173. For example, the discussion group identifier 210 may look for times where the messages 173 are clustered or particularly dense, and may determine if the clusters repeat according to any discernable period. Any method for determining a period for a time ordered group of samples may be used.
The discussion group engine 180 may further determine whether the topic identifiers associated with the message data 175 are synchronous. As described above, another characteristic of discussion groups is that they are synchronous. A topic identifier is synchronous if most of the associated messages 173 occur during a fixed duration at some offset of the determined period. Thus, for example, a topic identifier is synchronous if most of the messages 173 occur during a one hour duration starting at 7 pm every week.
The discussion group engine 180 may determine whether the topic identifiers that have already been determined to be periodic are synchronous. The discussion group engine 180 may determine if a topic identifier is synchronous using the determined period for the topic identifier and the time associated with each message 173 that uses the topic identifier.
In some implementations, the discussion group engine 180 may determine if there is duration of time that includes most of the messages 173 with respect to the determined period. The discussion group engine 180 may consider several possible candidate durations (e.g., one hour, two hours, three hours, etc.) until a duration is determined that includes most of the generated messages 173. If a suitable duration is determined by the discussion group engine 180, the duration may be stored by the discussion group engine 180 with the topic identifier in the discussion group data 185.
The discussion group engine 180 may further determine whether the topic identifiers associated with the message data 175 are cohesive. As described above, another characteristic of discussion groups is that they are cohesive. A topic identifier is cohesive if some number or percentage of the messages 173 that include the topic identifier are messages 173 that are sent between user accounts. A distinguishing feature of discussion groups is that they are used to facilitate discussion among users. Therefore, a greater number of the messages 173 that are associated with a discussion group are likely to be addressed to particular user accounts associated with the discussion group (such as a moderator or other user accounts) than for messages 173 that are not associated with a discussion group.
The discussion group identifier 210 may determine whether the topic identifiers that have already been determined to be periodic and synchronous are cohesive. In some implementations, the discussion group identifier 210 may determine a topic identifier is cohesive based on a number of user account pairs that exchange messages 173 associated with the topic identifier. The number of user account pairs may be compared with a threshold number to determine if the topic identifier is cohesive. The threshold number may be set by a user or administrator, and may be based on the number of messages 173 associated with the topic identifier and/or the number of user accounts that use the topic identifier. Other methods for determining whether a topic identifier is cohesive may be used.
If the discussion group identifier 210 determines that topic identifier is cohesive, then the topic identifier may be stored in the discussion group data 185. The topic identifiers that were determined to be one or more of periodic, synchronous, and cohesive may be identified as discussion groups in the discussion group data 185.
In other implementations, any topic identifier may be considered a discussion group by the discussion group identifier 210 regardless of whether or not it is determined to be one or more of periodic, synchronous, and cohesive. For example, a topic identifier may be considered a discussion group when it is recommended by a user to the discussion group identifier 210, or has been used in a message 173 more than a threshold number of times. Thus, if a particular thing (e.g., item, service, product, topic, restaurant, movie, television show, etc.) that is being reviewed or discussed online has more than a threshold number of associated messages 173, then a topic identifier associated with the thing may be considered a discussion group by the discussion group identifier 210.
The discussion group engine 180 may receive a query 112 for a discussion group. The query 112 may include one or more terms that indicate a topic that a user is interested in finding one or more discussion groups to discuss or learn about. For example, a user may be interested in discussion groups related to toddlers, and may generate a query 112 that includes the term toddlers.
The discussion group engine 180 may search the discussion group data 185 for one or more discussion groups that are relevant to the query 112. Depending on the implementation, a discussion group may be relevant to the query 112 if its associated topic identifier includes a term of the query 112, or includes a known variation, synonym, or misspelling of a term of the query 112. Alternatively or additionally, a discussion group may be relevant to the query 112 if any of the messages 173 associated with the discussion group includes a term of the query 112, or includes a known variation, synonym, or misspelling of a term of the query 112. A message 173 may be associated with a discussion group if it includes the topic identifier (e.g., hashtag) associated with the discussion group.
After identifying a set of relevant discussion groups, the discussion group engine 180 may rank the relevant discussion groups, and may provide some or all of the relevant discussion groups according to the ranking as the results 130. As described above, in some implementations, the discussion group engine 180 may rank the relevant discussion groups using the group preference model. The discussion group engine 180 may apply the group preference model using some or all of authority scores, preference scores, and teleport scores computed for some of all of the relevant discussion groups.
The authority score engine 220 may compute an authority score for each author of a message 173 associated with a discussion group of the relevant discussion groups. Alternatively or additionally, the authority scores may be computed for each participant in a discussion group. Each author or participant may receive an authority score for each relevant discussion group that they are associated with. Thus, for example, an author who participates in a discussion group with a topic of #depression and a discussion group with a topic identifier of #therapy may receive a separate authority score by the authority score engine 220 for each discussion group.
How the authority score is calculated by the authority score engine 220 may depend on the implementation, and how much weight the concept of authority is given in the group preference model. In some implementations, the authority score for an author may be based on the number of followers that are associated with the author, and may be determined by the authority score engine 220 based on a profile associated with the author. The profile may be provided by the message service 170.
In other implementations, the authority score for an author may be based on the total number of messages 173 generated by the author in the particular discussion group, or may be based on the number of replies that the author receives in the discussion group. For example, the authority score engine 220 may count the number of times that the author's user name appears in a message 173 that also include the topic identifier associated with the discussion group.
In implementations where the authority score is given little weight, the authority score engine 220 may assign the same authority score to each author in a discussion group regardless of the number of messages 173 associated with the author, or the number of followers that the author has. Other techniques for scoring the authority of an author or participant based on messages 173 may be used.
In another implementation, the authority score for an author with respect to a topic identifier may be determined using what is referred to herein as “noun-frequency.” In such an implementation, the authority score for an author may be based on a count of how many messages 173 associated with the author include both a received query 112 and the topic identifier.
In another implementation, the authority score for an author with respect to a topic identifier may be determined using what is referred to herein as “mention weights.” In such an implementation, the authority score for an author may be based on a count of how many times that the author is mentioned in a message 173 that includes both a received query 112 and the topic identifier.
The computed authority scores for each author or participant may be stored by the authority score engine 220 as the authority data 225. The authority data 225 for a discussion group may form a distribution of authority scores across all authors and participants of the discussion group.
The preference score engine 230 may compute a preference score for each author or participant associated with a discussion group of the relevant discussion groups. The preference score for a participant or author for a discussion group may represent how much the author or participant likes or prefers the particular discussion group. Each author or participant may receive a preference score for each discussion group of the relevant discussion groups.
In some implementations, the preference score for an author or participant for a discussion group may be proportional to the total number of times the participant or author participated in the discussion group. For example, if the participant participated in #therapy one hundred times and #depression thirty times, the preference score for #therapy may be larger than the preference score for #depression. The data used to determine which discussion groups that a user participated in may be part of the message data 175, for example.
Alternatively or additionally, the preference score may be based on the number of messages 173 that the author created or generated. Regardless of the method used to generate preference scores, the sum of the preference scores generated for an individual author or participant by the preference score engine 230 across all discussion groups of the relevant discussion groups may equal one.
In some implementations, the group preference scores may be computed using a transition probability matrix. A transition probability matrix for (query 112, author) pairs are calculated. The matrix includes transition edge probabilities for each author and query 112 and each pair of topic identifiers (e.g., h1 and h2). The transition edge probability represents the author's preference for the topic identifier h1 over h2 for the query 112. When computing the author's preference between h1 and h2, only messages 173 associated with a time-period when the author was “aware” of both of the topic identifiers may be considered. For this time-period, a number of meetings of h1 and h2 attended by the author that are responsive to the given query 112 are determined. The transition probability may then be determined based on the relative differences between the numbers of each group discussion attended by the author.
The computed preference scores for each author or participant may be stored by the preference score engine 230 as the preference data 235. Similar to the authority scores, the preference data 235 for the discussion groups may form a probability distribution of preference scores across all authors and participants of the discussion groups.
With respect to the group preference model described above, the computed authority scores may be used by the discussion group engine 180 to determine which author to follow from a selected discussion group of the relevant discussion groups, and the determined preference scores may be used by the discussion group engine to select the discussion group that is preferred by the followed author. In particular, the discussion group engine 180 may use the probability distributions from the authority data 225 and the preference data 235 to determine the probability that each discussion group of the relevant discussion groups will be ultimately selected by a hypothetical seeker after applying the group preference model. The relevant discussion groups may then be ranked based on the probabilities associated with each discussion group.
In some implementations, the group preference model used by the discussion group engine 180 may further consider what is referred to herein as a teleport score for each of the relevant discussion groups. The teleport score represents the observation that when a hypothetical seeker as described above is exploring the relevant discussion groups by repeatedly selecting participants and discussion groups according to the authority and preference scores, at some point the seeker may abandon their exploration and may start over by selecting a new discussion group from the relevant discussion groups. The teleport score for a discussion group represents the likelihood that the discussion group will be the selected new discussion group. The seeker may then continue to consider authors and discussion groups as described above starting from the newly selected discussion group.
In such implementations, the discussion group engine 180 may further include a teleport score engine 240. The teleport score for a discussion group may represent the probability that the hypothetical seeker randomly decides to abandon their current exploration and selects the discussion group. In some implementations, the teleport score may be equal for all of the discussion groups in the set of relevant discussion groups, and may be calculated by the teleport score engine 240 based on the total number of discussion groups that are in the set of relevant discussion groups. For example, the teleport score engine 240 may calculate the teleport score for a discussion group as one divided by the total number of discussion groups in the set of discussion groups.
In other implementations, the teleport score engine 240 may calculate the teleport scores for the discussion groups based on how relevant each discussion group is to the query 112. For example, the teleport score engine 240 may calculate the teleport score for a discussion group based on the percentage of messages 173 that are associated with the discussion group that are also relevant to the query 112. Other methods for scoring based on relativity may be used. The computed teleport scores for each discussion group may be stored by the teleport score engine 240 as the teleport data 245.
The discussion group engine 180 may then implement the group preference model using the computed authority data 225, preference data 235, and teleport data 245 using the following process where λ is a stopping probability. At a first step, the discussion group engine 180 may randomly or arbitrarily select a starting discussion group g from the set of discussion groups that are relevant to the query 112. The starting discussion group g may be randomly selected or may be selected based on the teleport score Dq computed for the discussion group g for the query 112 q by the teleport score engine 240.
At a second step, the discussion group engine 180 may select an author or participant p associated with the discussion group g according to the probability distribution of the authority scores Aq,g(p) computed by the authority score engine 220.
At a third step, the discussion group engine 180 may select a new discussion group g′ from the set of discussion groups preferred by the selected author or participant p according to the probability distribution of the preference scores Pq,g(g′) computed for the relevant discussion groups by the preference score engine 230.
At a fourth step, the discussion group engine 180 may, with a probability λ, sample a discussion group g from the set of relevant discussion groups according to the probability distribution of the teleport scores Dq, and may return to the second step. Otherwise, the discussion group engine 180 may set g′ to g, and may return to the second step.
Depending on the implementations, the discussion group engine 180 may execute the group preference model over many iterations, and may record the discussion group that is ultimately selected from the set of relevant discussion groups for each iteration. The records of which discussion groups are selected may be used by the discussion group engine 180 to rank the relevant discussion groups. For example, the discussion group that is most often selected may receive a highest rank, and the discussion group that is selected the least may receive a lowest rank.
In some implementations, the discussion group engine 180 may apply the group preference model described above using a stationary Markov process. The group preference model may be represented by a Markov process over the set of relevant discussion groups with transition probabilities Mg
M
g
,g
(q)=λDg(g2)+(1−λ)Σp∈UAq,g
In formula (1), each transition probability Mg
The discussion group engine 180 may calculate the stationary distribution of the Markov process defined in the above formula 1 for a query 112 and a set of relevant discussion groups using the authority data 225, the preference data 235, and the teleport data 245. The discussion group engine 180 may then rank the discussion groups in the set of relevant discussion groups using the calculated stationary distribution.
A plurality of messages are received at 301. The plurality of messages 173 may be received by the discussion group engine 180 from the message service 170. Each message 173 may include a topic identifier, such as a hashtag, for example. Each message 173 may further be associated with an author and a date that the message was generated.
Topic identifiers that represent discussion groups are identified at 303. The topic identifiers that represent discussion groups may be identified by the discussion group identifier 210 of the discussion group engine 180.
A query is received at 305. The query 112 may be received by the discussion group engine 180 from a client 110. The query 112 may include one or more terms. The query 112 may be a request to identify topic identifiers associated with discussion groups that are relevant to the query 112.
Topic identifiers that are relevant to the received query are determined at 307. The topic identifiers may be determined by the discussion group engine 180 by determining topic identifiers that include one or more terms of the query 112. Alternatively or additionally, the discussion group engine 180 may determine that a topic identifier is relevant if some number of its associated messages 173 include one or more terms of the query 112. Other methods for determining relevant topic identifiers may be used.
The determined topic identifiers are ranked based on the messages that include the determined topic identifiers at 309. The determined topic identifiers may be ranked by the discussion group engine 180 using the group reference model using one or more of authority scores, preference scores and teleport scores computed based on the messages 173 associated with the topic identifiers.
The determined topic identifiers are provided at 311. The determined topic identifiers may be provided by the discussion group engine 180 according to the ranking by the discussion group engine 180 as the results 130.
A plurality of discussion groups that are relevant to the query is determined at 403. The relevant discussion groups may be determined by the discussion group engine 180 using one or both of the messages or topic identifiers associated with the discussion groups.
For each discussion group, an authority score is determined for each author at 405. The authority score for each author associated with a relevant discussion group may be determined by the authority score engine 220. Depending on the implementation, the authority score for an author may be determined using some or all of the number of followers that the author has, the number of messages that the author generated in the discussion group, or the number of replies that are associated with the author. Other methods may be used. The determined authority scores may be stored by the authority score engine 220 as the authority data 225, for example.
For each author, a preference score for the author with respect to each relevant discussion group is determined at 407. The preference score for each relevant discussion group for an author may be determined by the preference score engine 230. Depending on the implementation, the preference score for each relevant discussion group may be determined based on the attendance of the author with respect to each of the relevant discussion groups. Alternatively, or additionally the preference scores for the relevant discussion groups may be determined based on how many messages 173 that the author generates for each of the relevant discussion groups. Other methods may be used. The determined preference scores may be stored by the preference score engine 230 as the preference data 235, for example.
For each relevant discussion group, a teleport score is determined at 409. The teleport score for each relevant discussion group may be determined by the teleport score engine 240. Depending on the implementations, the teleport score for a relevant discussion group may be determined based on a number of messages 173 associated with the relevant discussion group that are relevant to the query 112. For example, the teleport score may be a ratio of the relevant messages 173 associated with the discussion group to a total number of messages 173 associated with the discussion group. Other methods may be used. The determined teleport scores may be stored by the teleport score engine 240 as the teleport data 245, for example.
The relevant discussion groups are ranked using the authority scores, the preference scores, and the teleport scores at 411. The relevant discussion groups may be ranked by the discussion group engine 180 using a Markov process to generate a stationary distribution using the authority scores, the preference scores, and the teleport scores, and ranking the relevant discussion groups using the generated stationary distribution.
Messages associated with a discussion group are determined at 501. The messages may be determined by the authority score engine 220 by determining messages 173 that include a topic identifier associated with the discussion group. The topic identifier may be a hashtag, for example. Other topic identifiers may be used.
Authors associated with the messages are determined at 503. The authors may be determined by the authority score engine 220 using the messages 173 associated with the discussion group. Each message 173 may have an associated author, and the authority score engine 220 may compile a list of authors from the determined messages 173 that are associated with the discussion group.
For each author, a number of followers associated with the author or a number of replies to messages associated with the author are determined at 505. The number of followers and/or the number of replies may be determined by the authority score engine 220. With respect to the number of followers, the authority score engine 220 may determine the number based on a profile page or other account information associated with the author in the message service 170. With respect to the number of replies associated with the author, the authority score engine 220 may determine the number of replies based on information provided by the messaging service 170, or by parsing the messages 173 associated with the discussion group for a sequence of one or more characters followed by the user name of the author. In some implementations, the sequence of one or more character is “@” followed by the user name of the author.
For each author, an authority score is determined based on the determined number of followers or the determined number of replies at 507. The authority score may be determined by the authority score engine 220.
For each author, a number of discussion groups that the author participated in is determined based on the dates associated with the messages at 603. The number may be determined by the preference score engine 230. Depending on the implementation, the number of discussion groups may be determined from information provided by the message service 170, or may be determined based on the messages 173 associated with the author in the discussion group. For example, a date associated with each occurrence of the discussion group may be compared with dates associated with messages 173 generated by the author to determine how many of the discussion groups that the author participated in.
For each author, a preference score is determined based on the determined number at 605. The preference score for each author for the discussion group may be proportional to the number of occurrences of the discussion group that the author participated in. Across all relevant discussion groups, the combined preference scores generated for an author may be equal to one.
A total number of messages associated the discussion group is determined at 701. The total number of messages 173 associated with the discussion group may be determined by the teleport score engine 240 using the topic identifier associated with the discussion group. For example, the teleport score engine 240 may count each message 173 that includes the topic identifier associated with the discussion group.
A number of messages associated with the discussion group that are relevant to a received query is determined at 703. The number of messages 173 that are relevant to the query 112 may be determined by the teleport score engine 240. The number of messages 173 that are relevant to the query 112 may be determined by searching for one or more terms of the query 112 in the messages 173 that also include the topic identifier associated with the discussion group.
A teleport score is determined for the discussion group based on a ratio of the messages that are relevant to the query to the total number of messages at 705. The ratio may be determined by the teleport score engine 240. Other methods for determining a teleport score may be used.
Numerous other general purpose or special purpose computing devices environments or configurations may be used. Examples of well-known computing devices, environments, and/or configurations that may be suitable for use include, but are not limited to, personal computers, server computers, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, network personal computers (PCs), minicomputers, mainframe computers, embedded systems, distributed computing environments that include any of the above systems or devices, and the like.
Computer-executable instructions, such as program modules, being executed by a computer may be used. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Distributed computing environments may be used where tasks are performed by remote processing devices that are linked through a communications network or other data transmission medium. In a distributed computing environment, program modules and other data may be located in both local and remote computer storage media including memory storage devices.
With reference to
Computing device 800 may have additional features/functionality. For example, computing device 800 may include additional storage (removable and/or non-removable) including, but not limited to, magnetic or optical disks or tape. Such additional storage is illustrated in
Computing device 800 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by the device 800 and includes both volatile and non-volatile media, removable and non-removable media.
Computer storage media include volatile and non-volatile, and removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Memory 804, removable storage 808, and non-removable storage 810 are all examples of computer storage media. Computer storage media include, but are not limited to, RAM, ROM, electrically erasable program read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computing device 800. Any such computer storage media may be part of computing device 800.
Computing device 800 may contain communication connection(s) 812 that allow the device to communicate with other devices. Computing device 800 may also have input device(s) 814 such as a keyboard, mouse, pen, voice input device, touch input device, etc. Output device(s) 816 such as a display, speakers, printer, etc. may also be included. All these devices are well known in the art and need not be discussed at length here.
It should be understood that the various techniques described herein may be implemented in connection with hardware or software or, where appropriate, with a combination of both. Thus, the methods and apparatus of the presently disclosed subject matter, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other machine-readable storage medium where, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the presently disclosed subject matter.
Although exemplary implementations may refer to utilizing aspects of the presently disclosed subject matter in the context of one or more stand-alone computer systems, the subject matter is not so limited, but rather may be implemented in connection with any computing environment, such as a network or distributed computing environment. Still further, aspects of the presently disclosed subject matter may be implemented in or across a plurality of processing chips or devices, and storage may similarly be effected across a plurality of devices. Such devices might include personal computers, network servers, and handheld devices, for example.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
This application is a continuation of U.S. application Ser. No. 14/307,912, filed on Jun. 18, 2014, the disclosure of which is hereby incorporated in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14307912 | Jun 2014 | US |
| Child | 15782731 | US |
