The present invention relates to a mediating server and more specifically relates to a mediating server that generates communities based on a semantic understanding of requested content.
Internet users often search for web forums or chat groups related to topics of interest to the users. However, the users must actively search for such communities. Thus, there is a need for a system and method for establishing communities of users that do not require the users to actively search for the communities.
The present invention provides a system and method for creating communities based on a semantic understanding of content requested by a number of user devices. More specifically, a mediating server located at an intermediary network node operates to interconnect a number of user devices to destination servers. In operation, the mediating server receives requests from the user devices and routes the requests to the appropriate destination servers. The mediating server examines the responses from the destination servers to gain a semantic understanding of the content requested by the user devices. In addition, the mediating server may examine the requests to gain further semantic understanding of the content requested by the user devices. Thereafter, the mediating server establishes communities of the user devices based on the semantic understanding of the content requested by the user devices. For example, the mediating server may invite users of the user devices that have requested semantically similar content to join a chat group around a common topic.
Those skilled in the art will appreciate the scope of the present invention and realize additional aspects thereof after reading the following detailed description of the preferred embodiments in association with the accompanying drawing figures.
The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the invention, and together with the description serve to explain the principles of the invention.
The embodiments set forth below represent the necessary information to enable those skilled in the art to practice the invention and illustrate the best mode of practicing the invention. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the invention and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure and the accompanying claims.
The network node 12 may be a mediating server associated with an Internet Service Provider (ISP), a corporate firewall, a Local Area Network (LAN) access point, or the like. According to the present invention, the network node 12 includes a mediating server 28 and an ontology 30. Alternatively, the ontology 30 may be hosted by a remote server. Also, the mediating server 28 may alternatively be implemented as a number of distributed mediating proxies that collaboratively operate as the mediating server 28 described herein. For example, a load balancing technique may be used where a request may be routed through a first mediating server and the corresponding response may be routed through a second mediating server. The two mediating servers may then collaboratively operate at the mediating server 28 described herein. The mediating server 28 may be implemented in software, hardware, or a combination thereof. As discussed below, the mediating server 28 gains semantic understanding of content accessed by the user devices 14-20 and facilitates the formation of communities based on semantic similarities of the content accessed by the user devices 14-20. The communities may be hosted by the mediating server 28, the network node 12, or some other network node. The ontology 30 is generally a data model that represents a domain that is used to gain a semantic understanding about the objects in that domain and the relations between them. An exemplary ontology or portion of an ontology is illustrated in
The destination server 22 then provides a response including the requested content to the mediating server 28 (step 104). In one embodiment, the response may also include semantic metadata. The semantic metadata may be, for example, metadata provided according to the Resource Description Framework (RDF) model semantically describing the requested content. Information describing the family of specifications for RDF can be found at http://www.w3.org/RDF/. An exemplary RDF semantic metadata structure describing an article about Fidel Castro is:
Other examples of semantic metadata include, but are not limited to, keywords, annotations, location information, or the like within the headers of or associated with a media file, streaming media content, or the like. In addition, the semantic metadata may include a reference to external content or information.
The mediating server 28 then examines the response from the destination server 22 to gain a semantic understanding of the requested content (step 106). In one embodiment, the response includes semantic metadata giving semantic meaning to the requested content. The mediating server 28 may gain further semantic understanding of the requested content by mapping keywords from the semantic metadata to one or more nodes in the ontology 30. In addition, the mediating server 28 may gain further semantic understanding by examining the request. For example, the mediating server 28 may examine a Uniform Resources Locator (URL) and any parameters, such as parameters for a Hypertext Transfer Protocol (HTTP) GET request, of the request to gain semantic understanding of the requested content.
In another embodiment, the mediating server 28 extracts the content from the response using a screen scraping function. Note that different screen scraping functions may be used for different types of content such as, but not limited to, Hypertext Markup Language (HTML) files, Microsoft Word documents, Adobe Acrobat PDF files, PowerPoint presentations, and the like. Further, different screen scraping functions may be included for different types of web sites. As an example, screen scraping may be used to extract the text of a web page from a corresponding HTML file. By extracting the text from the web page, the mediating server 28 ensures that HTML tags that repeatedly occur in the HTML file are not interpreted as keywords regarding the semantic meaning of the web page. Once the content is extracted from the response, the mediating server 28 uses an inference engine, such as a natural language inference engine, to gain semantic understanding of the requested content, which is referred to herein as the semantic meaning of the requested content. For example, the inference engine may determine one or more of the most commonly used keywords or phrases in the text of a web page other than common words such as, for example, “the,” “a,” “an,” and the like. As another example, screen scraping may be used to extract text from streaming video content. For example, streaming video content may include scrolling text messages, and screen scraping, or a similar technique, may be used to extract the text messages from the video.
Based on the semantic meaning of the requested content, the mediating server 28 identifies a community for the user device 14 (step 108). The community may be one of a number of existing communities previously established by the mediating server or a new community. The community may be, for example, a chat group among users of user devices 14-20 having requested semantically similar content, a peer-to-peer (P2P) file sharing community among user devices 14-20 having requested semantically similar content, an e-mail list or forum associated with a particular topic related to the semantic meaning of the request content, or the like.
In order to identify a community for the user device 14, the mediating server 28 first determines whether there is an existing community for a topic related to or equivalent to the semantic meaning of the requested content. The mediating server 28 may identify topics related to the semantic meaning of the requested content using the ontology 30. For example, the requested content may be a web page discussing Ian McKellen. By examining the response passing through the mediating server 28, the mediating server 28 determines that the semantic meaning of the requested content is “Ian McKellen.” If there are no communities around the topic “Ian McKellen,” the mediating server 28 may query the ontology 30, thereby determining that the topic “Ian McKellen” is semantically related to the topics “Lord of the Rings” and “Fantasy.” If there is an existing community around the topic “Fantasy,” the mediating server 28 may identify the community around the topic “Fantasy” as the community to which to invite the user of the user device 14.
If there are no existing communities around topics related to or equivalent to the semantic meaning of the requested content, the mediating server 28 may then determine whether there is another active request for content that is semantically similar to, or related to, the content requested by the user device 14. For example, the user device 14 may request a streaming video related to “Ian McKellen” and the user device 16 may request a web page related to “Harry Potter.” Using the ontology 30, the mediating server 28 may determine that both of these topics are related to the topic “Fantasy.” As such, the mediating server 28 may identify a new community around the topic “Fantasy” and, as discussed below, invite the users of the user devices 14 and 16 to join the community.
If there are no existing communities and no other active requests around topics related to or equivalent to the semantic meaning of the requested content, the mediating server 28 may start a new community, where the user of the user device 14 waits for additional users to join the community.
It should be noted that the mediating server 28 may also manage the size of the communities. For example, the mediating server 28 may limit the number of users for each community and create multiple communities around the same topic if desired. The mediating server 28 may additionally or alternatively create narrow or broad topics for communities based on user density around the topic. For example, if there are a large number of users requesting content related to the “Fantasy” topic, the mediating server 28 may create communities around related sub-topics such as “Lord of the Rings,” “Harry Potter,” and “Ian McKellen.” In contrast, if the number of users requesting content related to the “Fantasy” topic is small, the mediating server 28 may create a single community around the topic “Fantasy.”
Once the community is identified, the mediating server 28 forwards the response from the destination server 22 to the user device 14 (step 110) and invites the user to join the identified community (step 112). While in this example the response is not forwarded to the user device 14 until after steps 106 and 108, the response may alternatively be forwarded to the user device 14 prior to steps 106 and 108 or simultaneously therewith. The invitation to join the community may be provided, for example, by framing the content from the destination server 22 with an invitation to join the community or modifying the response to add a JavaScript pop-up message inviting the user in join the community. The invitation may alternatively be provided by an end-user agent application that receives the invitation message from the mediating server 28 and generates a user interface message that invites the user of the user device 14 to join the community.
Those skilled in the art will recognize improvements and modifications to the preferred embodiments of the present invention. All such improvements and modifications are considered within the scope of the concepts disclosed herein and the claims that follow.
Number | Name | Date | Kind |
---|---|---|---|
6721282 | Motley | Apr 2004 | B2 |
6865605 | Soderberg et al. | Mar 2005 | B1 |
6970848 | Osaka et al. | Nov 2005 | B2 |
6987985 | Purkayastha et al. | Jan 2006 | B2 |
7016668 | Vaidyanathan et al. | Mar 2006 | B2 |
7039562 | Notani et al. | May 2006 | B1 |
7149807 | Kontothanassis | Dec 2006 | B1 |
7376790 | Lango et al. | May 2008 | B2 |
7512973 | Chan et al. | Mar 2009 | B1 |
20020010759 | Hitson et al. | Jan 2002 | A1 |
20020013812 | Krueger et al. | Jan 2002 | A1 |
20020054578 | Zhang et al. | May 2002 | A1 |
20020061029 | Dillon | May 2002 | A1 |
20020104099 | Novak | Aug 2002 | A1 |
20020129367 | Devara | Sep 2002 | A1 |
20020144267 | Gutta et al. | Oct 2002 | A1 |
20020156842 | Signes et al. | Oct 2002 | A1 |
20030050055 | Ting et al. | Mar 2003 | A1 |
20030081580 | Vaidyanathan et al. | May 2003 | A1 |
20030152096 | Chapman | Aug 2003 | A1 |
20030161268 | Larsson et al. | Aug 2003 | A1 |
20040030798 | Anderson et al. | Feb 2004 | A1 |
20040042421 | Mahany | Mar 2004 | A1 |
20040117824 | Karaoguz et al. | Jun 2004 | A1 |
20040248615 | Purkayastha et al. | Dec 2004 | A1 |
20040264372 | Huang | Dec 2004 | A1 |
20040267900 | Hoekstra et al. | Dec 2004 | A1 |
20050008017 | Datta et al. | Jan 2005 | A1 |
20050034001 | Pontarelli | Feb 2005 | A1 |
20050108769 | Arnold et al. | May 2005 | A1 |
20050120127 | Bradley et al. | Jun 2005 | A1 |
20050165828 | Lango et al. | Jul 2005 | A1 |
20050169632 | Song et al. | Aug 2005 | A1 |
20050183120 | Jain et al. | Aug 2005 | A1 |
20050192987 | Marsh | Sep 2005 | A1 |
20050201340 | Wang et al. | Sep 2005 | A1 |
20050216942 | Barton | Sep 2005 | A1 |
20050239497 | Bahl et al. | Oct 2005 | A1 |
20050286438 | Rajkotia | Dec 2005 | A1 |
20060048185 | Alterman | Mar 2006 | A1 |
20060048186 | Alterman | Mar 2006 | A1 |
20060053452 | Lee et al. | Mar 2006 | A1 |
20060056349 | Nakatugawa et al. | Mar 2006 | A1 |
20060085830 | Bruck et al. | Apr 2006 | A1 |
20060129672 | Mayer | Jun 2006 | A1 |
20060206933 | Molen et al. | Sep 2006 | A1 |
20070002742 | Krishnaswamy et al. | Jan 2007 | A1 |
20070061488 | Alagappan et al. | Mar 2007 | A1 |
20070061580 | Venkatesan et al. | Mar 2007 | A1 |
Number | Date | Country |
---|---|---|
2 306 869 | Nov 1995 | GB |