1. Technical Field
The present disclosure relates to electronic content delivery and more specifically to intelligent targeting of invitational content based on enhanced knowledge of the context related to the primary content.
2. Introduction
Electronic content publishers commonly provide a description of their content. In some instances, the description is as simple as a contextual tag. For example, a news website or application might include the description “news.” In other instances, a content provider might attempt to provide a more detailed description of the content in the way of collection of tags identified by the content publisher, for example, a cloud tag, which is commonly seen on websites on the Internet.
However, such content descriptions, if available, are often overly broad or inaccurate. While such descriptions might be suitable for their intended purpose of aiding search engines in finding the content, they are not sufficient for distribution of secondary content to be displayed along with the publisher's content.
Additional features and advantages of the disclosure will be set forth in the description which follows, and in part, will be obvious from the description, or can be learned by practice of the herein disclosed principles. The features and advantages of the disclosure can be realized and obtained by means of the instruments and combinations particularly pointed out in the appended claims. These and other features of the disclosure will become more fully apparent from the following description and appended claims, or can be learned by the practice of the principles set forth herein.
The present technology provides mechanisms for delivering optimally targeted invitational content to a user by a content delivery system. One aspect of providing optimally targeted content includes providing the content delivery system with detailed and accurate information regarding the context in which the content is being requested and to be displayed.
To better understand the present technology, the following hypothetical example is useful. A primary content developer hosts a website, which the primary content developer tags as a news website. However, a user browsing content on the website is reviewing a webpage that contains sports content. When the user's device requests an item of secondary content to be displayed along with the sports content, the system will send secondary content that fits the news context, which is not ideal for sports content. Accordingly, the present technology remedies this problem by analyzing the individual web pages to gain more detailed and accurate contextual information regarding the primary content. This, in turn, results in the distribution of secondary content that is more appropriate for the context of the primary content.
In some embodiments, a device displaying an item of primary content (e.g. a website or application, etc.) will request targeted-secondary content from the content delivery system for display along with the primary content. In such embodiments, the content delivery system can take into account many different factors in determining which item of secondary content is most likely to be of interest to the user of the device. Such factors include known characteristics of the user, the device, the context in which the secondary content will be displayed, etc.
With respect to the context in which the secondary content will be displayed, the content delivery system can look up contextual tags provided by the content publisher such as html tags or tag clouds. However, such tags are often too vague and inaccurate. Accordingly, the content delivery system analyzes primary content to determine additional and more accurate contextual information regarding the primary content. The enhanced knowledge of the primary content is used to associate secondary content therewith.
In some embodiments, the analysis of the primary content comprises a text analysis of the primary content. The textual terms can be thereafter be used to correlate the primary content to an index maintained by the content delivery system. In some embodiments, only the most relevant textual terms are used to correlate the primary content to the index. The relevance of terms can be determined by a variety of mathematical techniques. However, in at least some embodiments, the relevance is determined by a frequency distribution of similar terms.
The secondary content is also correlated to the index. In some embodiments, this can be done manually when the content is loaded into the content delivery system, or it can also be analyzed in a similar fashion as described for the primary content above.
By correlating both the primary content and the secondary content to the index, the content delivery system can be ensured of delivering secondary content that fits the context of the primary content.
Toward that end, in one aspect, the disclosure concerns a computer-implemented method for improving the conversion rate of secondary content that is provided to the user of an interactive, content-receiving-and-displaying device. According to this aspect, the content of a multiplicity of primary-content sources is analyzed and keyword and/or other context-providing information is extracted from the primary-content sources. The keyword and/or other context-providing information is used to index the primary-content sources into an index according to a hierarchical taxonomy; the hierarchical taxonometric index is used to identify primary-content sources with which a given item of invitational content correlates; and the given item of invitational content is delivered to a user in response to the user accessing a primary-content source with which the given item of invitational content correlates.
In another aspect, the disclosure concerns a server, and/or a system, which implements the method described above. In yet another aspect, the disclosure concerns a software product with instructions for implementing the method described above.
In order to describe the manner in which the above-recited and other advantages and features of the disclosure can be obtained, a more particular description of the principles briefly described above will be rendered by reference to specific embodiments thereof, which are illustrated in the appended drawings. Understanding that these drawings depict only exemplary embodiments of the disclosure, and are not therefore to be considered to be limiting of its scope, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:
a is an excerpt from
Various embodiments of the disclosure are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components and configurations may be used without parting from the spirit and scope of the disclosure. The present disclosure addresses the need in the art for improved methods of selecting targeted content presented to a user based on characteristics descriptive of the user and/or the user's interaction with one or more items of targeted content.
The presently disclosed system and method is particularly useful for delivering targeted invitational content to a user in a manner that leads to a higher probability of conversion. An exemplary system configuration 100 is illustrated in
In system 100, secondary content is delivered to user terminals 1021 . . . 102n (collectively “102”) connected to a network 104 by direct and/or indirect communications with a content delivery system 106. In particular, the content delivery system 106 receives a request for an item of electronic content, such as a web page, an application, or media, etc., from one of user terminals 102. Thereafter, the content delivery system 106 assembles the secondary content into a content package in response to the request and transmits the assembled content package to the requesting one of user terminals 102. In some cases, the server will have preselected the content package before the request is received. The assembled content package can include text, graphics, audio, video, executable code, or any combination thereof.
Further, the assembled content packages can include invitational content designed to inform or elicit a pre-defined response from the user and content that can vary over time. In the various embodiments, one or more types of invitational content can be combined in a content package. The invitational content can include text, graphics, audio, video, executable code or any combination thereof. In some embodiments, the invitational content can be associated with a product or can directly or indirectly advertise a product. In some embodiments, the content package can be configured to replace or update invitational content in a content package already delivered to the user terminal.
Further, the invitational content can be active invitational content in that it is designed to primarily elicit a pre-defined response from the user. For example, active invitational content can include one or more types of advertisements configured to be clicked upon, solicit information, or be converted by the user into a further action, such as a purchase or download of the advertised item. However, invitational content can also include passive invitational content that is designed to primarily inform the user. In some cases, passive invitational content can include information that can lead or direct users to active invitational content. Additionally, the invitational content can be dynamic invitational content, i.e., invitational content that varies over time or that varies based on user interaction with the invitational content. Alternatively, the invitational content can be static invitational content that does not vary over time and does not vary based on user interaction. In the various embodiments, an item of invitational content in a content package can be static or dynamic and active or passive. Further, various types of invitational content can be combined in a same content package.
As noted above, having the content that is available to be delivered to the user well organized, e.g., by appropriate tagging and indexing, is also valuable in matching and delivering content to a given user in a manner that optimizes the likelihood of conversion of the content. In this regard, it is known that content providers and publishers often generate their own tags and metadata that are associated with the information they provide. However, in order to improve the “match” between the user and the invitational content delivered to the user thereby intended to increase the likelihood of conversion of the invitational content, the present disclosure contemplates that an independent (i.e., non-publisher-based, non-provider-based) analysis of available content can be conducted.
Thus, for every source of primary content to be analyzed, e.g., a website—that is, a general place on the Internet one might visit as a “gateway” destination, such as CNN.com or ESPN.com, to which the user will go as a starting point for further information—or a specific webpage (i.e., the specific page associated with a specific URL), according to the method 200, the system 100 will obtain the source's URL 202 and “crawl” the source 204 to extract the necessary information/data from it in order to index the source. More particularly, the system will analyze (e.g., text-process) the primary-content source and look for extraneous material to be ignored or discarded 206; words and/or strings 208 containing tags that have already been provided by the content publisher/provider; and metadata 210 associated with the primary-content source. (Extraneous material includes terms that appear frequently (e.g., “the,” “a”/“an,” “to,” “and,” etc.) and that carry no meaningful substantive or contextual information with them.) Furthermore, the system 100 can “stem” the various terms, that is, convert them into the base forms of the words by eliminating suffixes (e.g., “s” or “es,” “ed,” “ing,” etc.). Additionally, the system 100 can “normalize” the terms, e.g., by converting them all to lowercase letters, etc. In some embodiments, the delivery system 106 can use the individual terms to infer/derive additional terms and/or use the terms to identify other terms known to the delivery system 106.
Where the primary-content source already contains word tags and/or string tags that have been prepared and provided by the content provider (208), the system 100 can extract the various tags directly and index the source by processing the HTML tags (212), as described more fully below. Web pages are a commonly encountered example of content that are frequently annotated to improve search results for the purpose of providing contextual information to a content delivery system, such as system 106.
Alternatively, if the primary-content source has metatags associated with it (210), two “avenues” of processing, which are not mutually exclusive, are available. According to one avenue, the primary-content source will be mapped to its pre-existing descriptive snippets (sometimes referred to as “tag bags”) using an offline retrieval method such as GOOGLE searching and/or DMOZ searching (214) to obtain the source's site class and/or a descriptive snippet, and that information is processed (216) to generate textual tags that can be indexed, as described more fully below. On the other hand, the metadata itself often contains textual information that can be retrieved (218) and processed (220) to extract and generate textual tags that can be indexed. Exemplary textual information that can be found directly in the metadata is illustrated in
In some cases, the primary content may be annotation/tag free. To associate contextual information or textual tags with such primary content, the delivery system 106 can analyze the content. More particularly, the system can parse the primary-content source into individual terms. The granularity of the individual terms can vary with the configuration of the delivery system 106. For example, in some configurations, the delivery system can parse the content so that each word in the content is mapped to an individual term. Alternatively, an individual term can represent a phrase, idea, etc. In some configurations, the delivery system 106 can analyze sub-content, such as figures or images, to identify individual terms.
In some embodiments, the delivery system 106 can determine the contextual information from the tags/metadata provided by the content provider and independently analyze the content. The analysis can be used to verify the information provided by the content provider. The independent analysis can also be used to assign a confidence score to the contextual information provided by the content provider. For example, the delivery system 106 may assign a low confidence score to the contextual information provided by the content provider. However, a higher confidence score could be assigned to tags in the content that are a close match to the independently discovered information.
Once the various textual tags for a given source of primary content have been determined, the page is indexed by mapping those tags according to a pre-established hierarchical taxonometric index. For example, an exemplary list of textual tags that might be extracted from a given source of primary content is shown in
By way of example, the methodology used in determining the relevancy score may be either term frequency-inverse document frequency or any clustering method such as k-means, nearest-neighbor, fuzzy clustering, latent-semantic indexing (see, for example, http://www.activemath.org/amwiki/index.php/Latent-Semantic-Algorithms), SVD (singular value decomposition), LDA (latent Dirichlet Allocation), etc. (More information on this topic can be found, for example, at http://en.wikipedia.org/wiki/Cluster_analysis.)
Additionally, invitational content can have metadata and/or text associated with it, and the same process is performed for it, too. In other words, the invitational content can also be analyzed to determine its context just as described for the primary content above. In some embodiments, this might not be required to analyze the invitational content, such as instances in which the invitational content is assigned to the proper context(s) when uploaded to the content delivery system.
Once the tags have been extracted and analyzed, and the primary-content source has been indexed, the top, say, five or ten (or some other predetermined number) most contextually relevant tags are passed on to a targeting module. Additionally, in some embodiments, tags, which the content publisher has provided, can be used in the process. The targeting module uses those tags to identify primary-content sources to which invitational content to be delivered to a user optimally correlates or corresponds. In that way, when a user accesses a primary-content source with which a given item of invitational content correlates, the system 106 delivers the invitational content to the user, along with the primary content to be displayed along with it.
The content delivery system can determine that the primary content corresponds with the secondary invitational content because both the primary and the secondary content are assigned to the correlated item in the hierarchical taxonometric index of content contexts, such as the exemplary hierarchical taxonometric index illustrated in
Contexts of content can be said to be correlated when their contexts are associated so that placing secondary content having one context does not seem out of place to a user when placed with primary content having another context. One method of correlating contexts is to perform a cluster analysis of the available contexts. Any contexts that are grouped into the same or related cluster can be correlated.
Referring back to
The content delivery system 106 includes a content management module 108 that facilitates generation of the assembled content package, which can include invitational content. Specifically, the content management module can combine content from one or more primary content providers 1091 . . . 109n (collectively “109”) and content from one or more secondary content providers 1101 . . . 110n (collectively “110”) to generate the assembled content package for the user terminals 102. For example, in the case of a web page being delivered to a requesting one of user terminals 102, the content management module 108 can assemble a content package by using the contextual data for the web page to match the web page with secondary content that fits the context of the web page.
In some embodiments, the primary content and the secondary content are sent to the user device in separate communications and combined at the device. Such a scenario is possible when the device accesses primary content directly from the primary content provider and subsequently/simultaneously requests secondary content from the content delivery network to be displayed with the primary content on the device.
Although primary and secondary providers 109 and 110 are presented herein as separate entities, this is for illustrative purposes only. In some cases, the primary and secondary providers 109 and 110 can be the same entity. Thus, a single entity can define and provide both the primary and the secondary content.
Although the content management module 108 can be configured to request that content be sent directly from content providers 109 and 110, a cached arrangement can also be used to improve performance of the content delivery system 106, and improve overall user experience. That is, the content delivery system 106 can include a content database 112 for locally storing/caching content maintained by content providers 109 and 110. The data in the content database 112 can be refreshed or updated on a regular basis to ensure that the content in the database 112 is up to date at the time of a request from a user terminal. However, in some cases, the content management module 108 can be configured to retrieve content directly from content providers 109 and 110 if the metadata associated with the data in content database 112 appears to be outdated or corrupted.
In the various embodiments, the content delivery system 106 can also include a unique user identifier (UUID) database 116 that can be used for managing sessions with the various user terminal devices 102. The UUID database 116 can be used with a variety of session management techniques. For example, the content delivery system 106 can implement an HTTP cookie or any other conventional session management method (e.g., IP address tracking, URL query strings, hidden form fields, window name tracking, authentication methods, and local shared objects) for user terminals 102 connected to content delivery system 106 via a substantially persistent network session. However, other methods can be used as well. For example, in the case of handheld communications devices, e.g. mobile phones, smart phones, tablets, or other types of user terminals connecting using multiple or non-persistent network sessions, multiple requests for content from such devices may be assigned to a same entry in the UUID database 116. The delivery system 106 can analyze the attributes of requesting devices to determine whether such requests can be attributed to the same device. Such attributes can include device or group-specific attributes.
As described above, content maintained by the content providers 109 and 110 can be combined according to a predefined arrangement between the two content providers, which can be embodied as a set of rules. In an arrangement where the content delivery system assembles the content package from multiple content providers, these rules can be stored in a rules database 118 in content delivery system 106. The content management module 108 can be configured to assemble the content package for user terminals 102 based on these rules. The rules specify how to select content from secondary content providers 110 and primary content providers 109 in response to a request from one of user terminals 102. For example, in the case of a web page maintained by one of primary content providers 109 and including variable advertisement portions, the rules database 118 can specify rules for selecting one of the secondary providers 110. The rules can also specify how to select specific content from the selected one of secondary providers 110 to be combined with the content provided by one of primary providers 109. Once assembled, the assembled content package can be sent to a requesting one of user terminals 102. However, the content package is not limited to the content from content providers 109 and 110. Rather, the content package can include other data generated at the content delivery systems 106.
One concern with the arrangement typically entered into by secondary content providers 110 is that they can result in invitational content of little or no interest being presented to users. As a result, even though a desired number of impressions can be achieved, the rate of response to such invitational content may be low and/or the resulting targeted audience may be incorrect or suboptimal.
As used herein, the term “user characteristics” refers inclusively to the characteristics of a particular user associated with one or more of user terminals 102. User characteristics can include channel characteristics, demographic characteristics, behavioral characteristics, and spatial-temporal characteristics. Channel characteristics can define the specific delivery channel being used to deliver a content package to a user. For example, channel characteristics can include a type of electronic content, a type of device or user terminal, a carrier or network provider, or any other characteristic that defines a specific delivery channel for the content package. Spatial-temporal characteristics can define a location, a date, a time, or any other characteristic that defines a geographic location and/or a time for delivery of the content package. Demographic characteristics can define characteristics of the users targeted by the content or associated with the content. For example, demographic characteristics can include age, income, ethnicity, gender, occupation, or any other user characteristics. Behavioral characteristics can define user behaviors for one or more different types of content, separately or in combination with any other user characteristics. That is, different behavioral characteristics may be associated with different channel, demographic, or spatial-temporal characteristics. User characteristics can also include characteristics descriptive of a user's state of mind, including characteristics indicative of how likely a user is to click on or convert an item of invitational content if it were displayed to the user.
Furthermore, in some embodiments, the content delivery system 106 can include a user-profile database 120. The user-profile database 120 can, at least in part, be constructed based on recorded user characteristics related to one or more users. In some cases, the user-profile database may contain uncertain or incomplete user characteristic values.
The user-profile database 120 can be updated using a user-profile-updater module 122. In some embodiments, the user-profile-updater module 122 can be configured to add additional profile data, update profile data, fill in missing profile data, or derive uncertain user characteristic values from trusted data.
The updater module 122 can also be configured to maintain the profile database 120 to include only more recently acquired data, or to re-derive any uncertain characteristics in order to ensure that the user profile is an accurate reflection of the current state of the user (location, state of mind, behaviors, demographics, etc. can change rapidly). For example, the updater module 122 can be configured to maintain the profile database 120 to include only data from the last two to three months. However, the updater module 122 can be configured to adjust the data in profile database 120 to cover any span of time. In some instances, the updater module 122 can update the profile database 120 in real-time. In some instances, the updater module 122 can update the profile database 120 at least every week, or every day. In some cases, the delivery system 106 can receive a direct request to update one or more user profiles. The update request can come directly from the user's device or any other device capable of communicating with the delivery system 106, such as other content delivery networks or websites. In some cases, the delivery system 106 can receive an indirect request to update one or more user profiles. An indirect request can be the result of receiving new user characteristic values. An update request can occur at any time.
In some embodiments, the content delivery system 106 can include a segment database 114 that is used to aid in selecting invitational content to target to users. The segment database 114 stores defined segments and associations between the segments and users and/or invitational content that should be targeted to users associated with the segments. As described above, a targeted segment can be defined based on one or more user characteristics or derivatives thereof, and can be associated with one or more items of invitational content. Additionally, a targeted segment can be associated with one or more users. In some embodiments, by associating a targeted segment with both a user and an item of invitational content, the delivery system can match invitational content with users. In some embodiments, the delivery system 106 can update the segment database 114 to add newly defined targeted segments or to delete targeted segments.
In some embodiments, the delivery system 106 can include a custom segment creator module 126. A content provider 109 and 110 can interact either directly or indirectly with the creator module 126 to define a custom targeted segment. A custom segment can be defined based on one or more user characteristics known to the delivery system 106. In some cases, a custom targeted segment can be saved to the segment database 114 to use later in selecting invitational content. Alternatively, the custom targeted segment can be used immediately to identify invitational content with or without saving the segment to the segment database 114.
In some embodiments, the content delivery system 106 can provide a segment assigner module 124. The segment assigner module 124 can apply a set of user characteristics associated with a user (including segments to which a user has been previously assigned) to assign the user to one or more targeted segments. The assigner module 124 can obtain the set of user characteristic values from the user profile database 120 and/or from the user's activities during the current session. The segment assigner module 124 can assign a user to one or more defined targeted segments in the segment database 114, or alternatively, a user can be assigned to a custom targeted segment defined to meet specific goals of a content provider.
Based on the assigned segments, the user profile database 120 can be updated to reflect the segment assignments. Additionally, the delivery system 106 can use the segment assignments to select targeted content. In some cases, the user profile data in the user profile database 120 can change over time, so the segment assigner module 124 can be configured to periodically update the segment assignments in the user profile database 120. The segment assignment update can be triggered at specified intervals, upon detection of a change in the user profile database 120, and/or upon detection of a specified activity in the delivery system 106.
In some embodiments, the content delivery system 106 can provide a segment-prioritizing module 128 for ordering the targeted segments assigned to a user. The prioritization can be influenced by a number of factors, which include the user's context (state of mind of a user with respect to interest in certain types of content, subject matter of content, progress along a conversion continuum, etc.), a content provider's campaign goals, and/or content that is currently available for display to the user. A request to prioritize the targeted segments can be made explicitly or implicitly by any component in the system 100. For example, a secondary content provider 110 can explicitly request that the content delivery system 106 prioritize the targeted segments or the request can be implicit as part of a request for an assembled content package. The resulting prioritized list can be provided, for example, to the content management module 108, which can then use the information to assemble and deliver a content package. Additionally, the prioritized list can be stored, for example in the user profile, for later use. A method of prioritizing targeted segments is described in greater detail.
In the various embodiments, the one or more databases described herein can be implemented using any type of data structures. Such data structures include, but are not limited to, data structures for relational databases, key/value stores, graph databases, hierarchical databases, and distributed or columnar stores. Accordingly, although the various embodiments described herein may refer to specific data structures, in other embodiments, such data structures can be substituted for any other type of data structure.
As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve the delivery of advertisements or any other content that may be of interest to users. The present disclosure contemplates that, in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, social media ID's such as TWITTER ID's, home addresses, or any other identifying information.
The present disclosure recognizes that the use of such personal information data in the present technology can be used to the benefit of users. For example, the personal information data can be used to better understand user behavior, facilitate and measure the effectiveness of advertisements, applications, and delivered content. Accordingly, use of such personal information data enables calculated control of the delivered content. For example, the system can reduce the number of times a user receives a given ad or other content, and can thereby select and deliver content that is more meaningful to users. Such changes in system behavior improve the user experience. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure.
The present disclosure further contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data should implement and consistently use privacy policies and practices that that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. For example, personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection should occur only after the informed consent of the users. Additionally, such entities would take any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy and security policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices.
Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of advertisement delivery services, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services. In another example, users can select not to provide location information for advertisement delivery services. In yet another example, users can configure their devices or user terminals to prevent storage or use of cookies and other mechanisms from which personal information data can be discerned. The present disclosure also contemplates that other methods or technologies may exist for blocking access to their personal information data.
Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, content can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the content delivery services, or publically available information.
In some embodiments, the delivery system 106 is configured to assign users to a targeted segment of the user population. Accordingly, a segment assigner module 124 can be provided for performing the assignments. The delivery system 106 can also include a segment database 114 that stores previously defined targeted segments. The previously defined targeted segments can be based on channel, demographic, behavioral, and/or spatial-temporal characteristics. The definition of a targeted segment can include one or more user characteristics. For example, a targeted segment can be defined to target a segment of the population shaped by gender and age. Additionally, a user characteristic value for a characteristic can be a single value, multiple values, a range of values, multiple ranges of values, or any combination thereof. For example, for the age characteristic, acceptable values include 19; 19-24; 25-29; etc. In some embodiments, a user characteristic value can be a wildcard value, which indicates that any value is an acceptable match for the user characteristic.
Having defined segments to work with, the assigner module 124 can analyze one or more user characteristic values and one or more targeted segment definitions to determine if the user fits within a population segment defined by a targeted segment. The delivery system 106 can then use the segment assignments to select invitational content targeted at the assigned segment to send to the user.
As shown in
The system bus 510 may be any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. A basic input/output (BIOS) stored in ROM 540 or the like, may provide the basic routine that helps to transfer information between elements within the computing device 500, such as during start-up. The computing device 500 further includes storage devices 560, such as a hard disk drive, a magnetic disk drive, an optical disk drive, tape drive or the like. The storage device 560 can include software modules 562, 564, 566 for controlling the processor 520. Other hardware or software modules are contemplated. The storage device 560 is connected to the system bus 510 by a drive interface. The drives and the associated computer readable storage media provide nonvolatile storage of computer readable instructions, data structures, program modules and other data for the computing device 500. In one aspect, a hardware module that performs a particular function includes the software component stored in a non-transitory computer-readable medium in connection with the necessary hardware components, such as the processor 520, bus 510, output device 570, and so forth, to carry out the function. The basic components are known to those of skill in the art and appropriate variations are contemplated depending on the type of device, such as whether the device 500 is a small, handheld computing device, a desktop computer, or a computer server.
Although the exemplary embodiment described herein employs the hard disk 560, it should be appreciated by those skilled in the art that other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, digital versatile disks, cartridges, random access memories (RAMs) 550, read only memory (ROM) 540, a cable or wireless signal containing a bit stream and the like, may also be used in the exemplary operating environment. Non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.
To enable user interaction with the computing device 500, an input device 590 represents any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth. An output device 570 can also be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems enable a user to provide multiple types of input to communicate with the computing device 500. The communications interface 580 generally governs and manages the user input and system output. There is no restriction on operating on any particular hardware arrangement and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.
For clarity of explanation, the illustrative system embodiment is presented as including individual functional blocks including functional blocks labeled as a “processor” or processor 520. The functions these blocks represent may be provided through the use of either shared or dedicated hardware, including, but not limited to, hardware capable of executing software and hardware, such as a processor 520, that is purpose-built to operate as an equivalent to software executing on a general purpose processor. For example, the functions of one or more processors presented in
The logical operations of the various embodiments are implemented as: (1) a sequence of computer implemented steps, operations, or procedures running on a programmable circuit within a general use computer, (2) a sequence of computer implemented steps, operations, or procedures running on a specific-use programmable circuit; and/or (3) interconnected machine modules or program engines within the programmable circuits. The system 500 shown in
Embodiments within the scope of the present disclosure may also include tangible and/or non-transitory computer-readable storage media for carrying or having computer-executable instructions or data structures stored thereon. Such non-transitory computer-readable storage media can be any available media that can be accessed by a general purpose or special purpose computer, including the functional design of any special purpose processor as discussed above. By way of example, and not limitation, such non-transitory computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code means in the form of computer-executable instructions, data structures, or processor chip design. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or combination thereof) to a computer, the computer properly views the connection as a computer-readable medium. Thus, any such connection is properly termed a computer-readable medium. Combinations of the above should also be included within the scope of the computer-readable media.
Computer-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Computer-executable instructions also include program modules that are executed by computers in stand-alone or network environments. Generally, program modules include routines, programs, components, data structures, objects, and the functions inherent in the design of special-purpose processors, etc. that perform particular tasks or implement particular abstract data types. Computer-executable instructions, associated data structures, and program modules represent examples of the program code means for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps.
Those of skill in the art will appreciate that other embodiments of the disclosure may be practiced in network computing environments with many types of computer system configurations, including personal computers, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. Embodiments may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination thereof) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
The various embodiments described above are provided by way of illustration only and should not be construed to limit the scope of the disclosure. Those skilled in the art will readily recognize various modifications and changes that may be made to the principles described herein, without following the example embodiments and applications illustrated and described herein, and without departing from the spirit and scope of the disclosure.
Number | Name | Date | Kind |
---|---|---|---|
4829423 | Tennant et al. | May 1989 | A |
4879648 | Cochran et al. | Nov 1989 | A |
5062074 | Kleinberger | Oct 1991 | A |
5270689 | Hermann | Dec 1993 | A |
5408519 | Pierce et al. | Apr 1995 | A |
5544360 | Lewak et al. | Aug 1996 | A |
5613213 | Naddell et al. | Mar 1997 | A |
5708825 | Sotomayor | Jan 1998 | A |
5867164 | Bornstein et al. | Feb 1999 | A |
5907841 | Sumita et al. | May 1999 | A |
5943657 | Freestone et al. | Aug 1999 | A |
5978775 | Chen | Nov 1999 | A |
5978833 | Pashley et al. | Nov 1999 | A |
5978841 | Berger | Nov 1999 | A |
5991713 | Unger et al. | Nov 1999 | A |
6023700 | Owens et al. | Feb 2000 | A |
6023701 | Malik et al. | Feb 2000 | A |
6055512 | Dean et al. | Apr 2000 | A |
6073143 | Nishikawa et al. | Jun 2000 | A |
6078914 | Redfern | Jun 2000 | A |
6097942 | Laiho | Aug 2000 | A |
6138113 | Dean et al. | Oct 2000 | A |
6148334 | Imai et al. | Nov 2000 | A |
6178460 | Maddalozzo, Jr. et al. | Jan 2001 | B1 |
6182065 | Yeomans | Jan 2001 | B1 |
6256648 | Hill et al. | Jul 2001 | B1 |
6334145 | Adams et al. | Dec 2001 | B1 |
6345279 | Li et al. | Feb 2002 | B1 |
6381465 | Chern et al. | Apr 2002 | B1 |
6405243 | Nielsen | Jun 2002 | B1 |
6658464 | Reisman | Dec 2003 | B2 |
6684249 | Frerichs et al. | Jan 2004 | B1 |
6690394 | Harui | Feb 2004 | B1 |
6754470 | Hendrickson et al. | Jun 2004 | B2 |
6850530 | Waclawsky et al. | Feb 2005 | B1 |
6920326 | Agarwal et al. | Jul 2005 | B2 |
7058695 | Takagi et al. | Jun 2006 | B2 |
7072947 | Knox et al. | Jul 2006 | B1 |
7149537 | Kupsh et al. | Dec 2006 | B1 |
7194552 | Schneider | Mar 2007 | B1 |
7490045 | Flores et al. | Feb 2009 | B1 |
7558559 | Alston | Jul 2009 | B2 |
7613691 | Finch | Nov 2009 | B2 |
20010047272 | Frietas et al. | Nov 2001 | A1 |
20020016736 | Cannon et al. | Feb 2002 | A1 |
20020077130 | Owensby | Jun 2002 | A1 |
20020078147 | Bouthors et al. | Jun 2002 | A1 |
20020083411 | Bouthors et al. | Jun 2002 | A1 |
20020120565 | Yu et al. | Aug 2002 | A1 |
20020120682 | Funaki | Aug 2002 | A1 |
20020137507 | Winkler | Sep 2002 | A1 |
20020138291 | Vaidyanathan et al. | Sep 2002 | A1 |
20020175935 | Wang et al. | Nov 2002 | A1 |
20030003935 | Vesikivi et al. | Jan 2003 | A1 |
20030013483 | Ausems et al. | Jan 2003 | A1 |
20030028896 | Swart et al. | Feb 2003 | A1 |
20030040297 | Pecen et al. | Feb 2003 | A1 |
20030040300 | Bodic et al. | Feb 2003 | A1 |
20030080986 | Baird | May 2003 | A1 |
20030154300 | Mostafa | Aug 2003 | A1 |
20030188017 | Nomura | Oct 2003 | A1 |
20030191689 | Bosarge et al. | Oct 2003 | A1 |
20030197719 | Lincke et al. | Oct 2003 | A1 |
20030208472 | Pham | Nov 2003 | A1 |
20040010592 | Carver et al. | Jan 2004 | A1 |
20040034647 | Paxton et al. | Feb 2004 | A1 |
20040043777 | Brouwer et al. | Mar 2004 | A1 |
20040054576 | Kanerva et al. | Mar 2004 | A1 |
20040068527 | Smith, III | Apr 2004 | A1 |
20040122926 | Moore et al. | Jun 2004 | A1 |
20040136358 | Hind et al. | Jul 2004 | A1 |
20040185883 | Rukman | Sep 2004 | A1 |
20040192359 | McRaild et al. | Sep 2004 | A1 |
20040203761 | Baba et al. | Oct 2004 | A1 |
20040203851 | Vetro et al. | Oct 2004 | A1 |
20040204133 | Andrew et al. | Oct 2004 | A1 |
20040209649 | Lord | Oct 2004 | A1 |
20040240649 | Goel | Dec 2004 | A1 |
20040259526 | Goris et al. | Dec 2004 | A1 |
20050010641 | Staack | Jan 2005 | A1 |
20050044280 | Reisman | Feb 2005 | A1 |
20050060425 | Yeh et al. | Mar 2005 | A1 |
20050114229 | Ackley et al. | May 2005 | A1 |
20050125397 | Gross et al. | Jun 2005 | A1 |
20050138140 | Wen et al. | Jun 2005 | A1 |
20050191989 | Plush et al. | Sep 2005 | A1 |
20050249216 | Jones | Nov 2005 | A1 |
20050289113 | Bookstaff | Dec 2005 | A1 |
20060029097 | McGee et al. | Feb 2006 | A1 |
20060031327 | Kredo | Feb 2006 | A1 |
20060045245 | Aaron et al. | Mar 2006 | A1 |
20060059133 | Moritani | Mar 2006 | A1 |
20060073810 | Pyhalammi et al. | Apr 2006 | A1 |
20060095511 | Munarriz et al. | May 2006 | A1 |
20060123014 | Ng | Jun 2006 | A1 |
20060129455 | Shah | Jun 2006 | A1 |
20060141923 | Goss | Jun 2006 | A1 |
20060143027 | Jagannathan et al. | Jun 2006 | A1 |
20060161520 | Brewer et al. | Jul 2006 | A1 |
20060194595 | Myllynen et al. | Aug 2006 | A1 |
20060200460 | Meyerzon et al. | Sep 2006 | A1 |
20060200461 | Lucas et al. | Sep 2006 | A1 |
20060200541 | Wikman et al. | Sep 2006 | A1 |
20060206586 | Ling et al. | Sep 2006 | A1 |
20060223495 | Cassett et al. | Oct 2006 | A1 |
20060276170 | Radhakrishnan et al. | Dec 2006 | A1 |
20060276213 | Gottschalk et al. | Dec 2006 | A1 |
20060286963 | Koskinen et al. | Dec 2006 | A1 |
20060286964 | Polanski et al. | Dec 2006 | A1 |
20060288124 | Kraft et al. | Dec 2006 | A1 |
20070004333 | Kavanti | Jan 2007 | A1 |
20070030824 | Ribaudo et al. | Feb 2007 | A1 |
20070047523 | Jiang | Mar 2007 | A1 |
20070072631 | Mock et al. | Mar 2007 | A1 |
20070073624 | Ishibashi et al. | Mar 2007 | A1 |
20070074262 | Kikkoji et al. | Mar 2007 | A1 |
20070083602 | Heggenhougen et al. | Apr 2007 | A1 |
20070088687 | Bromm et al. | Apr 2007 | A1 |
20070088801 | Levkovitz et al. | Apr 2007 | A1 |
20070088851 | Levkovitz et al. | Apr 2007 | A1 |
20070100805 | Ramer et al. | May 2007 | A1 |
20070105536 | Tingo, Jr. | May 2007 | A1 |
20070117571 | Musial | May 2007 | A1 |
20070149208 | Syrbe et al. | Jun 2007 | A1 |
20070150483 | Goldman et al. | Jun 2007 | A1 |
20070168336 | Ransil et al. | Jul 2007 | A1 |
20070179841 | Agassi et al. | Aug 2007 | A1 |
20070180147 | Leigh | Aug 2007 | A1 |
20070214048 | Chan et al. | Sep 2007 | A1 |
20070214132 | Grubb et al. | Sep 2007 | A1 |
20070220040 | Do | Sep 2007 | A1 |
20070244750 | Grannan et al. | Oct 2007 | A1 |
20070287474 | Jenkins et al. | Dec 2007 | A1 |
20070290787 | Fiatal et al. | Dec 2007 | A1 |
20070300160 | Ferrel et al. | Dec 2007 | A1 |
20080004046 | Mumick et al. | Jan 2008 | A1 |
20080013537 | Dewey et al. | Jan 2008 | A1 |
20080032703 | Krumm et al. | Feb 2008 | A1 |
20080032717 | Sawada et al. | Feb 2008 | A1 |
20080070579 | Kankar et al. | Mar 2008 | A1 |
20080071875 | Koff et al. | Mar 2008 | A1 |
20080082686 | Schmidt et al. | Apr 2008 | A1 |
20080091796 | Story et al. | Apr 2008 | A1 |
20080109285 | Reuther et al. | May 2008 | A1 |
20080155588 | Roberts et al. | Jun 2008 | A1 |
20080201731 | Howcroft | Aug 2008 | A1 |
20080243619 | Sharman et al. | Oct 2008 | A1 |
20080270151 | Mahoney et al. | Oct 2008 | A1 |
20080281696 | Whitehead | Nov 2008 | A1 |
20080288476 | Kim et al. | Nov 2008 | A1 |
20090063279 | Ives et al. | Mar 2009 | A1 |
20090113468 | Steelberg et al. | Apr 2009 | A1 |
20090144124 | Surendran et al. | Jun 2009 | A1 |
20090164299 | Gupta et al. | Jun 2009 | A1 |
20090164300 | Gupta et al. | Jun 2009 | A1 |
20090222440 | Hantke et al. | Sep 2009 | A1 |
20090275315 | Alston | Nov 2009 | A1 |
20100005488 | Rakib et al. | Jan 2010 | A1 |
20100138452 | Henkin et al. | Jun 2010 | A1 |
20100293058 | Maher et al. | Nov 2010 | A1 |
20100312572 | Ramer et al. | Dec 2010 | A1 |
20110238495 | Kang | Sep 2011 | A1 |
20110239246 | Woodward et al. | Sep 2011 | A1 |
Number | Date | Country |
---|---|---|
19941461 | Mar 2001 | DE |
10061984 | Jun 2002 | DE |
0597630 | May 1994 | EP |
1061465 | Dec 2000 | EP |
1073293 | Jan 2001 | EP |
1109371 | Jun 2001 | EP |
1220132 | Jul 2002 | EP |
1239392 | Sep 2002 | EP |
1365604 | Nov 2003 | EP |
1408705 | Apr 2004 | EP |
1455511 | Sep 2004 | EP |
1542482 | Jun 2005 | EP |
1587332 | Oct 2005 | EP |
1615455 | Jan 2006 | EP |
1633100 | Mar 2006 | EP |
1677475 | Jul 2006 | EP |
2369218 | May 2002 | GB |
2406996 | Apr 2005 | GB |
2414621 | Nov 2005 | GB |
2002-14272 | May 2002 | JP |
2007-087138 | Apr 2007 | JP |
2007-199821 | Aug 2007 | JP |
9624213 | Aug 1996 | WO |
0030002 | May 2000 | WO |
0044151 | Jul 2000 | WO |
0122748 | Mar 2001 | WO |
0131497 | May 2001 | WO |
0152161 | Jul 2001 | WO |
0157705 | Aug 2001 | WO |
0158178 | Aug 2001 | WO |
0165411 | Sep 2001 | WO |
0169406 | Sep 2001 | WO |
0171949 | Sep 2001 | WO |
0172063 | Sep 2001 | WO |
0191400 | Nov 2001 | WO |
0193551 | Dec 2001 | WO |
0197539 | Dec 2001 | WO |
0231624 | Apr 2002 | WO |
02054803 | Jul 2002 | WO |
02069585 | Sep 2002 | WO |
02069651 | Sep 2002 | WO |
02075574 | Sep 2002 | WO |
02084895 | Oct 2002 | WO |
03015430 | Feb 2003 | WO |
03019845 | Mar 2003 | WO |
03024136 | Mar 2003 | WO |
03049461 | Jun 2003 | WO |
03088690 | Oct 2003 | WO |
2004084532 | Sep 2004 | WO |
2004086791 | Oct 2004 | WO |
200400470 | Nov 2004 | WO |
2004100521 | Nov 2004 | WO |
2004102993 | Nov 2004 | WO |
2004104867 | Dec 2004 | WO |
2005029769 | Mar 2005 | WO |
2005076650 | Aug 2005 | WO |
2006002869 | Jan 2006 | WO |
2006005001 | Jan 2006 | WO |
2006016189 | Feb 2006 | WO |
2006027407 | Mar 2006 | WO |
2006040749 | Apr 2006 | WO |
2006093284 | Sep 2006 | WO |
2006119481 | Nov 2006 | WO |
2008013437 | Jan 2008 | WO |
2008045867 | Apr 2008 | WO |
2008147919 | Dec 2008 | WO |
Entry |
---|
“Communication Pursuant to Article 94(3) EPC”, issued in connection with related European Patent Application No. 07824933.1 and mailed Oct. 13, 2009. |
“Communication Pursuant to Article 94(3) EPC”, issued in connection with related European Patent Application No. 08153658.3 and mailed Sep. 21, 2009. |
“Communication Pursuant to Article 94(3) EPC”, issued in connection with related European Patent Application No. 08153656.7 dated Sep. 23, 2009. |
“Communication Pursuant to Article 94(3) EPC dated Feb. 12, 2009”, issued by the European Patent Office in related European Patent Application No. 07824933.1. |
“European Search Report dated Aug. 1, 2008 issued by the European Patent Office”, in related EPO Application No. EP 08153651.8, Aug. 1, 2008. |
“European Search Report dated Aug. 1, 2008 issued by the European Patent Office”, in related EPO Application No. EP 08153654.2, Aug. 1, 2008. |
“European Search Report dated Jul. 18, 2008 issued by the European Patent Office”, in related EPO Application No. EP 08153656, Jul. 18, 2008. |
“European Search Report dated Jul. 18, 2008 issued by the European Patent Office”, in related EPO Application No. EP 08153658, Jul. 18, 2008. |
“International Search Report and Written Opinion of International Searching Authority dated Sep. 19, 2008”, in related International Application PCT/GB 2007/050723, Sep. 19, 2008. |
“Invitation to Pay Additional Fees and Communication Relating to the Results of the Partial International Search dated Apr. 28, 2008”, in corresponding International Application PCT/GB 2007/050723, Apr. 28, 2008. |
“Notice of Allowability issued Dec. 15, 2009”, in a related U.S. Appl. No. 12/075,986 , Dec. 15, 2009. |
“Office Action dated Apr. 28, 2009”, issued in related U.S. Appl. No. 12/075,986 (16 pages), Apr. 28, 2009. |
“Office Action dated May 28, 2009”, issued in related U.S. Appl. No. 12/075,998 (10 pages), May 28, 2009. |
“Office Action dated Mar. 10, 2009”, issued in related U.S. Appl. No. 12/075,999 (14 pages), Mar. 10, 2009. |
“Office Action dated May 7, 2009”, issued in related U.S. Appl. No. 12/156,598 (12 pages), May 7, 2009. |
“Office Action Issued Apr. 15, 2011”, in related U.S. Appl. No. 11/888,880 (12 pages). |
“Office Action issued from the USPTO dated Jul. 10, 2009”, issued in related U.S. Appl. No. 12/156,598 (9 pages), Jul. 10, 2009. |
“Office Action issued from the USPTO dated Jul. 2, 2009”, issued in related U.S. Appl. No. 12/075,986 (17 pages), Jul. 2, 2009. |
“Office Action Issued Jan. 5, 2011”, in related U.S. Appl. No. 11/888,880 (11 pages). |
“Search Report under Section 17 dated Mar. 2, 2008”, issued in related U.K. Patent Application GB 0802196.6, Mar. 2, 2008. |
“U.K. Search Report under Section 17 dated Mar. 18, 2008”, in connection with U.K. Application No. GB 0802366.5 (1 page), Mar. 18, 2008. |
“United Kingdom Search Report under Section 17 dated Sep. 15, 2007”, in connection with GB 0709604.3, Sep. 15, 2007. |
“International Preliminary Report on Patentability and Written Opinion of the International Searching Authority issued Nov. 24, 2009”, in International Application PCT/EP 2008/056084, Nov. 24, 2009. |
Gerard Salton, J. Allan, and Christopher Buckley, “Approaches to Passage Retrieval in Full Text Information Systems,” Proceedings of SIGIR ''93, pp. 49-58 (Jun. 1993). |
Danilo Fum, Giovanni Guida, and Carlo Tasso, “Forward and Backward Reasoning in Automatic Abstracting,” Coling 82: Proc. 9th Int. Joint Conf. on Computational Linguistics, Amsterdam: North-Holland, pp. 83-88 (1982). |
Klaus Zechner, “Automatic Text Abstracting by Selecting Relevant Passages,” M.Sc. Dissertation, Centre for Cognitive Science, University of Edinburgh, UK (1995). |
Kavi Mahesh, “Hypertext Summary Extraction for Fast Document Browsing,” AAAI Technical Report SS-97-02, pp. 95-103 (1997). |
Davies, N.J., Weeks R., Revett, M.C. “Jasper: Communication Information Agents for WWW.” Proc. Int. Conf. On WorldWideWeb, Boston, USA (1995). |
Keith Preston and Sandra Williams, “Managing the Information Overload,” Physics in Business, p. 2 (1994). |
Seji Miike, Etsuo Itoh, Kenji Ono, and Kazuo Sumita, “A Full-Text Retrieval System with a Dynamic Abstract Generation Function,” In W. Bruce Croft and C.J. van Rijsbergen, editors, Proceedings of Seventeenth Annual International ACM SIGIR Conference on Research and Development in Information Retrieval, pp. 152-161 (Jul. 1994). |
Gerard Salton and Christopher Buckley, “Term-Weighting Approaches in Automatic Text Retrieval,” Information Processing & Management, vol. 24, No. 5, pp. 513-523 (1988). |
John Davies, Scott Stewart, and Richard Weeks, “Knowledge Sharing Agents Over the World Wide Web,” British Telecom Tech., J., vol. 16, Nr. 3, pp. 104-109 (1988). |
S.J. Soltysiak, and I.B. Crabtree, “Automatic Learning of User Profiles-Towards the Personalization of Agent Services,” British Telecom Tech. J., vol. 16, Nr. 3, pp. 110-117 (1998). |
http://www2.hawaii.edu/˜rpeterso/engine—.htm. |
http://www.monash.com/spidap3.html. |
http://www.asis.org/annual-96/ElectronicProceedings/chu.html (Oct. 1996). |
http:///www.yale.edu/engineering/eng-info/msg00038.html. |
Robert Godin et al. “Design of a Browsing Interface for Information Retrieval”, 12th Annual Int'l ACM SIGIR Conference on Research and Dev. in Info. Retrieval,(1989). |
Number | Date | Country | |
---|---|---|---|
20120054209 A1 | Mar 2012 | US |