US 7,200,801 B2Grant
Rich media information portals
Issue Date:2007-04-03
•51 Claims
•15 Drawing Sheets
Abstract
Methods and systems for providing personalized information in a variety of formats is disclosed. Articles may be disseminated to users according to the users' preferences. Each article may contain a plurality of content segments, each content segment being contained within a corresponding content block that is labeled as being renderable using one or more rendering media, such as audio, video, image, or text. In this way, users may receive personalized information in a variety of ways; for example, a user can receive customized presentations about particular articles of interest via radio, cell phone, voicemail, television, MPEG player, web browser, or virtually any other type of media player.
Metadata
Assignee
- SAP Aktiengesellschaft
Inventors
- Shai Agassi
- Brian Willis
Application Information
Application Number:US 10/231,459
Filing Date:2002-08-30
Priority Date:2002-05-17
Art Unit:2176
Classifications
IPC:
G06F17/24
Patent Drawings (15 sheets)
Description
Cross-Reference to Related Applications
[0001] This application claims priority from U.S. Provisional Application No. 60/380,863, titled “Enhancing Information Portals with Supplemental Contextual Content,” filed May 17, 2002, and from U.S. Provisional Application No. 60/380,834, titled “Personalizing Portal Content Dynamically,” filed May 17, 2002, and from U.S. Provisional Application No. 60/380,864, titled “Rich Media Information Portals,” filed May 17, 2002, which are hereby incorporated by reference in their entirety for all purposes.
Technical Field
[0002] Certain disclosed implementations relate generally to information displays, and more particularly to dynamic, customized displays.
Background
[0003] Technologies exist which allow users to designate categories of information in which desired content may be presented. For example, web sites may allow users to select categories from a variety of different sources and content providers. Such sites are generally known as “portals,” and provide a central gateway through which users can be presented with options and links to various information sources. In this way, users can check, for example, their stocks, mail, local weather, sports scores, and movie listings.
[0004] Other techniques exist that attempt to provide users with content that will be of particular interest to each user. For example, web sites may track items such as books and Digital Video Disks (“DVDs”) based on attributes of such items, such as title, author, performer, and genre. By tracking previously-purchased books and DVDs, registered users may be presented with a web page offering items with similar attributes.
[0005] Finally, video recording systems may allow users to voice opinions about specific shows. Coupled with a programming guide, these video recording systems can later record concurrent episodes of the show or shows starring the same actor or shows of similar interest. Other techniques may exist for providing users with content having some degree of personalization for each user.
[0006] In another example, portals are capable of providing categorized content in disparate pieces (sometimes referred to as “iViews”), where each iView and its associated content can be aggregated into a single delivery package (for example, a web page). Users may select a category of content to be included within each iView, and may generally choose which iView(s) to see and exercise some control over how it is positioned inside the aggregated result.
[0007] In practical implementations of portals utilizing iViews, however, most users set up their portal once, if at all, and will thereafter simply keep these initial preferences. As a result, such users may miss out on viewing new content and categories of content that may be more interesting than the iViews originally selected. Similarly, content which is most interesting to the user at a particular time will not be properly emphasized within the aggregated result, such that the user does not give it the attention it is due.
[0008] Even if users update their iView configuration very frequently, each configuration is still static. That is, the set of iViews shown, and the order in which they are shown, is constant. Moreover, although the content of each iView may change over time (e.g. actual news headlines), its overall subject is static (for example, company news).
[0009] Finally, conventional portals often concentrate on the computer screen as the main output device thru which the user will receive the delivered content. The scope may be further limited if the portal is rendered in Hypertext Mark-up Language (“HTML”) and runs in a web browser. Even when mobile devices like personal digital assistants (“PDAs”) and smart cellular phones are used to access conventional portals, the portals are often still rendered in a type of browser.
[0010] Such a browser-limited approach may have emerged from an impression that browsers are ubiquitous on many client machines and that portals leave no-footprint on those clients by rendering to them. However, by heading in that direction the portal vendors have limited the capabilities of the portal and the distribution of the content. Moreover, to the extent that delivered content is typically text or image-based in a browser, users may have come to expect only those formats.
[0011] The browser-centric approach is usually used for the average business user who comes in to the office in the morning, and logs-in to his computer. However, there are many scenarios that prohibit access to computers. For example, many blue-collar employees do not have computers at their place of work. Also, many people are simply not computer savvy, and/or find computers intimidating. Even the savvy computer user has situations where using a laptop is difficult or impossible (the drive to the office, for example).
Summary
[0012] In contrast with the above, one implementation of a content presentation system described below enables dynamic selection of the shown set of iViews, based on an individual relevance of each iView to the user at any given time. That is, this implementation allows the user to personalize content based not only on its expected result (that is, the type of iView), but also on its actual result (that is, actual content of the iView).
[0013] In another implementation, a system incrementally learns the user's preferences regarding previously-shown items and categories, and uses that information to decide what content should be shown to the user in the future. Time may also be of significance, for example, by playing a part in deciding a level of relevance for each iView with respect to a specific user.
[0014] In another implementation, a system combines the concepts of the portal and personalized content with other delivery channels, such as, for example, telephone, radio, and television. The synergy opens up many new opportunities, such as “Enterprise TV,” wherein a television is placed in a lobby of a company, the company cafeteria, or other high-traffic areas, or “Enterprise radio,” wherein news (particularly company news) is broadcast to all employees over the airwaves. Yet another example is voice mail, wherein messages are left on the employee's voice mail. In this last example, participants of a meeting can easily be notified when a meeting is postponed.
[0015] In one general aspect, content may be aggregated for a user. A plurality of media assets may be accessed, each media asset comprising content blocks, each of the content blocks comprising content of the media asset associated with one of a plurality of content types. A subset of the plurality of media assets may be selected, based on a preference of a user. One of a plurality of rendering media may be chosen for each media asset within the subset and associated with a content type of content within a content block of the media asset. Content of each media asset within the subset may be aggregated into a cohesive presentation, the content of each media asset being expressed in the rendering medium chosen for that media asset.
[0016] Each media asset may include a content discussion object characterizing the content within the media asset. The subset of the plurality of media assets may be selected, wherein preference discussion objects received from the user may be input, and the content discussion object included within each of the plurality of media assets may be compared against the preference discussion objects. The content discussion objects may each characterize individual elements of information within the content.
[0017] The plurality of content types may include hyper-text markup language (“HTML”), text, text to be rendered as video, or text to be rendered as audio. The plurality of rendering media may include an HTML-based web-page, video, audio, or text.
[0018] One of the plurality of content types may be chosen from among the content types based on a characteristic of a client system of the user, or based on a preference of the user.
[0019] A delivery request may be received from the user, and may include information about a client system of the user.
[0020] Aggregating content of each media asset within the subset may include determining that at least one of the chosen content types is narrative data, and generating a graphic, video, or audio presentation of the narrative data. Aggregating content of each media asset within the subset may alternately include determining that at least one of the chosen content types is graphical data, and generating a video representation of the graphical data. Aggregating content of each media asset within the subset into a cohesive presentation may alternately include determining an order of content of each media asset within the cohesive presentation based on a preference of the user.
[0021] Each media asset in the subset may include metadata characterizing the content thereof. An order of content within each media asset within the cohesive presentation may be determined based on a consideration of the metadata with respect to a characteristic of a client system of the user or a preference of the user.
[0022] The cohesive presentation may be delivered to a machine accessible by the user, and may be delivered electronically.
[0023] Accessing a plurality of media assets, selecting a subset of the plurality of media assets, choosing one of the plurality of presentation formats, and aggregating content of each media asset within the subset into a cohesive presentation may be performed electronically.
[0024] The cohesive presentation may be delivered via a private or public network.
[0025] In selecting a subset of the plurality of media assets, the plurality of media assets may be filtered based on the preference of the user, to thereby obtain a filtered subset. The filtered subset may be prioritized based on the preference of the user.
[0026] The preference of the user may include a preferred rendering media.
[0027] In another general aspect, a system for delivering content to a user at a client system may include an article reader operable to access a plurality of media assets, each media asset including content blocks, each content block labeled as one of a plurality of content types and containing a segment of the content. The system may further include a sorting engine operable to select a subset of the plurality of media assets, based on a preference of a user, and a content-type selector operable to select a content block for each media asset within the subset. The system may also include an aggregation engine operable to combine content segments of the subset, each content segment corresponding to the content block selected for each media asset within the subset.
[0028] The content-type selector may be operable to select the content block based on a characteristic of a client system of the user. The article reader may be further operable to publish content metadata associated with each media asset, the content metadata characterizing the content segment of the media asset.
[0029] The sorting engine may be further operable to select the subset based on the content metadata. The content-type selector may be operable to select one of the plurality of content types based on a preference of the user, or may be operable to select one of the plurality of content types based on receipt of a delivery request from the user, the request including information about a client system of the user.
[0030] The aggregation engine may be operable to determine that at least one of the plurality of content types is narrative data, and to generate a graphic, video or audio presentation of the narrative data.
[0031] The aggregation engine also may be operable to determine that at least one of the plurality of content types is narrative data, and generate a video representation of the narrative data. The video representation may be a computer-generated image of an animated head made to resemble a person reading the narrative data.
[0032] The rendering engine may be further operable to render the combined content segments based on prioritization information contained in the preference of the user.
[0033] In another general aspect, a storage medium may have instructions stored thereon, the instructions including a first code segment for selecting a first media asset and a second media asset, the first and second media assets including a first and a second content segment, respectively, the first and second content segments each associated with at least two rendering media, a second code segment for selecting, for each of the first and second content segments, at least one of the rendering media for delivering each of the first and second content segments, to a client system, and a third code segment for combining the first and second content segments into a cohesive presentation.
[0034] A fourth code segment for delivering the cohesive presentation to the client system also may be included in the instructions. Also, the second code segment may be for selecting at least one of the rendering media based on a characteristic of the client system. The first code segment also may be for selecting narrative text, and the third code segment may be for generating a video or an audio presentation from the narrative text.
[0035] In another general aspect, delivering content may include selecting a first media asset and a second media asset, the first and second media assets including a first and a second content segment, respectively, the first and second content segments each associated with at least two rendering media. For each of the first and second content segments, at least one of the rendering media for delivering each of the first and second content segments to a client system may be selected. The first and second content segments may then be combined into a cohesive presentation and delivered to the client system.
[0036] In another general aspect, a system for delivering content may include a selection subsystem operable to select a first and second article from among a pool of articles, the first and second article containing a first and second content segment, respectively. The system may further include a pagination engine operable to aggregate the first and second content segments, and further operable to render the content segments for delivery to a client system based on data contained within the first and second articles indicating a first and second rendering medium for rendering the first and second content segments, respectively.
[0037] The pagination engine may be further operable to render the first and second content segments based on a characteristic of the client system.
[0038] The first and second content segments may include a first and a second content type, respectively, of the first and second content segments. The first content type may be text, audio, video, text to be rendered as audio, or text to be rendered as video.
[0039] The selection subsystem may be further operable to determine an order of the first content segment with respect to the second content segment, based on a preference of a user of the client system.
[0040] In another general aspect, a system for delivering content may include means for selecting a subset of a plurality of articles, each article in the subset including a first content segment and a second content segment, the first content segment and the second content segment associated with a first content type and a second content type, respectively, means for selecting at least one of the first content type and the second content type for each content segment, and means for combining the content segments and selected content type into a cohesive presentation. The system may also include means for delivering the cohesive presentation.
[0041] The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features will be apparent from the description, the drawings, and the claims.
Description of Drawings
[0042] FIG. 1 is an architectural block diagram of one implementation of a content presentation system.
[0043] FIG. 2 is an example of a first portion of a process flow used by the system of FIG. 1 .
[0044] FIG. 3 is an example of a second portion of a process flow used by the system of FIG. 1 .
[0045] FIG. 4 is an example of a third portion of a process flow used by the system of FIG. 1 .
[0046] FIG. 5 demonstrates a first example of page generation.
[0047] FIG. 6 demonstrates a second example of page generation.
[0048] FIG. 7 is an example of an article.
[0049] FIG. 8 is an example of a hypertext markup language (“HTML”) result page.
[0050] FIG. 9 is a first example of a context menu designed to allow users to input preference information.
[0051] FIG. 10 is a second example of a context menu designed to allow users to input preference information.
[0052] FIG. 11 is an example of a floating toolbar designed to allow users to input preference information.
[0053] FIG. 12 is a page that reflects user-expressed opinions with respect to the page of FIG. 8 .
[0054] FIG. 13 is an architectural block diagram of an example of a content presentation system designed primarily for generating personalized audio and video.
[0055] FIG. 14 is an example of an article used in one implementation of the system of FIG. 13 .
[0056] FIG. 15 is an example of a rendering of an article using the system of FIG. 13 .
Detailed Description
[0057] FIG. 1 is an example of a content presentation system including a system 100. In FIG. 1 , external information from an external information source 105 is received by a content generator 110, which generates a corresponding article. Many types of external information sources 105 may be used, as will be discussed in more detail with respect to FIG. 2 . Also, content generator 110 may utilize various techniques for gathering and publishing the information as discrete articles. For example, content generator 110 may utilize software agents to gather appropriate information (agents are generally defined as automatons running on a scheduled basis and querying a data source for information and either producing or not producing content based in part on the result of that query). Moreover, in other implementations, content generator 110 may be included within system 100.
[0058] The use of the term “article” in this context, as is discussed in more detail below, generally refers to a discrete collection of information that may include content and information about the content. Information about the content may include high-level attributes of the article, such as its author or general subject heading (for example, sports or weather). The information about the article may also include portions of the actual content itself used to articulate content metadata, perhaps in the form of “discussion objects.”
[0059] In general, discussion objects are considered to be conceptual or tangible objects that are mentioned (discussed) as part of an article. Similarly, “discussion classes” are the types, or categories, of discussion objects. For example, an article about a discussion class of “computer manufacturers” may mention discussion objects “International Business Machines” (“IBM”) many times, while only mentioning “Dell” infrequently. By determining at least some information directly from such specific discussion objects within the content of the article, this implementation is capable of accurately sorting articles against a user's interests.
[0060] Articles may be, for example, text, video, audio, HTML, or another available rendering medium, or a combination of two or more of these media. Articles may contain the same piece of content in multiple forms, and may permit generation of one type of content from another, as discussed below. Therefore, articles may also be referred to as “media assets,” or other similar terminology describing such information to be passed on to a user. Content of an article may be a publicly-available web page (or portion thereof), an internal electronic mail, an individual's personal contact information, weather information, or a set of stock quotes. Content may also be obtained from specific applications, such as a profit and loss report of a company, an online analytical processing (“OLAP”) report, a “print-out” of a sales order, or many other examples of discrete pieces of content to be made available to the user(s).
[0061] In FIG. 1 , then, an article reader 115 accesses articles from content generator 110. Some articles may already include attribute and content metadata information. If a particular article has no associated metadata, a metadata enhancer 120 may be used to examine the content of the article and generate metadata accordingly. Even if some information, such as attribute information, is included with an article, metadata enhancer 120 may be used to further enhance the article.
[0062] In one implementation, system 100 may be provided to an enterprise as a resource for its employees and/or customers. The enterprise may have its own object model (that is, definition of permissible discussion objects) describing how the content metadata should be generated, characterized, and interpreted. These object models may differ from one enterprise to the next; for example, IBM might be a “customer” to one enterprise and a “supplier” to another. Individual enterprise object models can therefore be implemented instead of, or in conjunction with, a standardized, centralized object model.
[0063] In particular, articles generated within an enterprise may require very little metadata enhancement, whereas articles obtained from publicly-available web pages may require a substantial amount of metadata enhancement.
[0064] Accessed articles are stored in a database 125, and information referencing the articles is passed on to a content-based router 130. Although entire articles could be passed through the system 100, other techniques may be used. For example, only links to corresponding articles need be circulated through system 100, with the articles themselves remaining stored in database 125. As another example, such links may be circulated with the associated attribute and/or content metadata, but without the content itself; in this way, the article may processed (as discussed below), without actually having to circulate the article in its entirety.
[0065] Content-based router 130 examines each article with respect to its content and associated attributes and content metadata, for example, discussion objects, and compares this information to information stored for individual users. For example, an Access Control List (“ACL”) database 135 contains a security clearance for each user with respect to various subjects, so that a user who is not cleared to receive certain information within an article will not receive that article. A user preference database 140 contains information about each user, for example, the extent to which a user likes or dislikes a particular subject, or the type of device(s) the user may be receiving the articles on.
[0066] Any type of router capable of routing articles based on content as described herein may be built and/or utilized to implement system 100. One type of router that is capable of performing the functionality of content-based router 130 is known as Elvin and is produced by the Distributed Systems Technology Centre (DSTC). Other types of content-based services include Gryphon, produced by International Business Machines (IBM), and Keryx, a Java-notification service by Hewlett Packard.
[0067] User preferences for populating user preference database 140 can be obtained by a number of techniques. For example, the preferences could be gained by asking users to fill out a preference form before gaining access to system 100. As another example, the preferences can be modified over time by obtaining feedback from the users, examples of which are discussed in more detail below.
[0068] By accessing databases 135 and 140, content-based router 130 is able to filter articles which are restricted or are of no interest with respect to a particular user. The action of content-based router 130 thus eases the burden on a personalized article processor (“PAP”) 145, which has the job of individually prioritizing the remaining articles, based on a comparison of contents of the user preference database 140 to the content and to the content metadata/attributes of each article. Accordingly, individually-sorted articles may be stored in a sorted articles database 150, where articles for a User A and a User B are stored with their corresponding priority information for each user in database portions 155 and 160, respectively.
[0069] A pagination engine 165 thus gains access to a set of articles associated with, and prioritized with respect to, individual users. Pagination engine 165 will typically have access to characteristics of the client system being used by each user. This information may be stored in user preference database 140, or (as explained in more detail below) it may be determined from the user request at the time of the request.
[0070] In either case, pagination engine 165 determines a layout of the canvas being used by each user, using a canvas layout subsystem 170. In this context, the term “canvas” includes any rendering media in which articles may be presented. Canvas examples include web pages (on desktop computers, laptops, Personal Digital Assistants (“PDAs”), web-enabled cell phones, etc.), audio (for example, cell phone or radio), video (for example, television or Motion Picture Expert Group (“MPEG”) player), or another type of device capable of receiving content within an article and presenting it to the user.
[0071] Since, as a practical matter, a canvas will typically have capacity limitations, one of the services of the canvas layout subsystem 170 within pagination engine 165 is to determine how much “space” is available to the user for displaying articles. For example, a web browser on a PDA will be able to display a smaller number of articles than a browser on a desktop computer. As another example, a user who receives audio articles via cell phone or radio may only have twenty minutes during a car ride during which to listen to articles. In short, canvas layout subsystem 170 determines any user-specific capacity constraints when deciding which articles to provide to a given user.
[0072] A content-type selector 175 determines which rendering media are available to the user for the selected canvas, and which articles are consistent, or can be made to be consistent, with that media. For example, content-type selector 175 may determine that a canvas has video and HTML capabilities, but not audio.
[0073] Finally within pagination engine 165, a media-type enabler 180 is available to enable a rendering media that would not ordinarily be available to the user (based on the content type(s) of the articles), when feasible and desired. One example of this feature is the capability of reading aloud to the user an email that is included as an article. Another example is the generation of an animation of a newscaster, complete with moving lips, to read aloud a print story to the user. These and other examples are discussed in more detail below.
[0074] During a final portion of the pagination process, pagination engine 165 aggregates the selected articles, in their selected formats, and delivers a personalized “page” of information to each user, so that each user receives articles for rendering that are of the most interest to him or her at a given point in time (or that the system determines the user should/must see, even if the user has expressed non-interest in such an article, such as a direction from the user's boss, or an article about a “hot” topic of the day). User systems 185 and 190 thus receive information suitable for rendering a page of information consistently with their respective system capabilities and requirements.
[0075] System 100 may also receive feedback from the users to be recorded in user preference database 140, so that the pages increasingly become better-personalized to each user as time goes by. The use of user preference feedback, as well as various formats in which pages may be rendered, are discussed below.
[0076] System 100 may be implemented in an enterprise environment, as discussed above, for the convenience of employees and/or customers of the enterprise. Implementations may be utilized via various other private networks, such as a university or other school network. On the other hand, implementations may be provided to members of the public at large, via the Internet.
[0077] FIGS. 2–4 demonstrate a process flow that might be used by the system of FIG. 1 . FIG. 2 demonstrates a technique for gathering a pool of articles to be later filtered, sorted, and rendered to a user. In FIG. 2 , sources of information for articles might include an application's application program interface (“API”) 205, an on-line analytical processing (“OLAP”) server 210, a database 215, and the world-wide web 220 (perhaps queried through the hypertext transfer protocol (“HTTP”), simple object access protocol (“SOAP”) or other common protocols of the Internet).
[0078] Content generation occurs in a process 225, during which articles are generated. Some articles, such as articles 230x and 235x, might be generated without attribute information or content metadata. In this case, meta-data enhancer 255 may be used to examine such articles and generate content metadata to thereby produce articles 230 and 235. Other articles, such as articles 240, 245, and 250, may already be generated with attribute data (describing general features of the articles such as author and date of publication) and content metadata (characterizing actual content of the articles). It should be noted that, in FIGS. 2–4 , articles including content metadata are illustrated with a dotted background, whereas articles having no content metadata (such as articles 230x and 235x) are shown with a plain background.
[0079] It should be understood that various techniques may be used for gathering article content. For example, software agents may operate in an agent execution environment which may serve as a host for the runtime execution of agents and administer execution of the agents (for example, scheduling of the agents). The agents may be used to query various databases, such as those shown in FIG. 2 . On the other hand, the content could also be generated within system 100, as referred to above with respect to FIG. 1 , or could be obtained by a variety of other means.
[0080] Examples of content that might be obtained according to FIG. 2 include a querying of the OLAP database 210 for a list of the top twenty customers in a particular region of an enterprise implementing system 100. For each one of these customers, an agent may access the API 205 of a customer relationship management (“CRM”) application, and then report the list of top customers that have pending complaints with customer service. This list may be used as an article, as discussed below.
[0081] Another example of content for articles might be current levels of the financial markets, gleaned from the web 220. Many other types of content, whether internal to an enterprise or simply drawn from the public domain, may form the basis for an article.
[0082] In FIG. 2 and continuing into FIG. 3 , articles 230, 235, 240, 245, and 250 thus represent a pool of articles, from which a subset for each user will be drawn. Once a pool of articles is established at a given point in time, a content-based security analysis 305 may be performed, the analysis being personalized for each user. Analysis 305 may be performed within content-based router 130 by accessing ACL database 135, both of FIG. 1 . In this way, articles which a particular user does not have security rights to access will be removed prior to actual content-based sorting, in order to make the sorting process more efficient.
[0083] After security analysis 305 is complete, a “bucket” 310 of articles exists for a user A, and a separate bucket 315 of articles exists for user B. At this point, content-based filtration analysis 320 occurs, wherein the content-based router 130 interacts with user-preference database 140 in FIG. 1 to determine which of the articles in buckets 310 and 315 match the interests of users A and B, respectively. This process results in refined buckets 325 and 330, as shown in FIG. 3 and continuing into FIG. 4 .
[0084] FIG. 4 demonstrates a prioritization process 405 that occurs within PAP 145, using data from within user preference database 140 in FIG. 1 . As a result of process 405, articles within buckets 325 and 330 are prioritized and stored in final buckets 410 and 415, in accordance with the preferences of users A and B, respectively. Although FIG. 4 shows only a few articles in buckets 410 and 415 for the sake of clarity, the number of articles that can be assigned to a given user as a result of the operations of FIGS. 1–4 can be significantly higher and is limited only by system performance considerations.
[0085] Once the articles have been filtered, sorted, and prioritized, system 100 may begin the pagination process. FIG. 5 demonstrates a first example of page generation. In FIG. 5 , articles 240 and 230, which were stored in bucket 410, are shown to contain content in various formats suitable for rendering in various media. For example, article 240 contains content blocks in the form of a readable text block 505, a narrative text block 510 (that is, text to be read as audio), and an image block 515. Similarly, article 230 contains content blocks in the form of a readable text block 520, a narrative text block 525, a video block 530, and an HTML block 535.
[0086] Based on knowledge of a user system onto which the page will be rendered, a page 540 is then created by pagination engine 165. In the example of FIG. 5 , the user system capabilities and/or user preferences indicate that the article should be rendered as HTML and therefore only readable text and associated images are to be utilized.
[0087] Accordingly, page 540 includes article 240 rendered as a section 545, as well as article 230 rendered as a section 560. Section 545 includes readable text content block 505 rendered as a portion 550 in HTML form, as well as image information content block 515 rendered as an image 555 as part of the HTML. Article 230 includes only readable text content block 520 rendered as a portion 565, again in HTML form.
[0088] It should be understood from FIGS. 4 and 5 that article 240 was given a higher priority for display than article 230, and was therefore shown on page 540 prior to article 230. In general, relatively more important articles might be shown in a more prominent location on the page, while the less important ones, space permitting, might only be shown as headlines with reference (for example, hyperlinks) to the full article.
[0089] FIG. 6 shows an alternate pagination process for rendering articles 240 and 230 within bucket 410. In FIG. 6 , pagination engine 165 determines that user A should receive the content of articles 230 and 240 as audio. This might be the case for a user wishing to receive articles 240 and 230 via radio and/or cell phone. Accordingly, a page 605 includes a portion of narrative text content block 525 rendered as audio portion 610, as well as narrative text content block 510 rendered as an audio portion 615. In page 605, article 230 is still prioritized lower than article 240, and might therefore generally be rendered subsequent to article 240. However, in page 605, a slightly different format is shown, in which a portion of lower priority article is shown as a “top story” to be discussed later in the page 605, whereas the higher priority article 240 is provided in its entirety as the day's “main story.” Alternatively, a “teaser” for the main story could be given first, and then returned to after the less-important articles were read. Such alternate formats mirror popular formats of conventional news programs, and may be preferred by some users.
[0090] It should be understood from FIGS. 5 and 6 that an article may contain several content blocks or content segments, which might each represent a subset of the total amount of content within the article (or might include all of the content). Together, these portions represent the entirety of the article content, however, the content need not be shown in its entirety. For example, image 515 is not included in page 605, because the articles were to be rendered only as audio. Thus, the provision of at least a portion of an article's content, in a format most suitable for a particular user, allows maximum flexibility in providing the user with information in a personalized, convenient format.
[0091] FIG. 7 shows an example of an article used in one implementation. In FIG. 7 , the article is expressed in one possible extensible markup language (“XML”) form, however, other implementations of an article may take other forms. In a section 705, the article contains some general attributes like the time it was created, the importance of the story, and the author who created it.
[0092] Article 700 also contains several content blocks for one or more possible rendering scenarios. For example, a section 710 includes a “text/narrative” content block for cases where an audio description of the content is necessary (for example, if the content is to be broadcast on radio or read by a TV spokesman). This content block is analogous to narrative text content blocks 510 and 525, and includes a headline section 715, as well as a detailed content section 720.
[0093] A “text/html” content block is shown in a section 725, which is useful for cases where the content will be shown in a web browser. Section 725 also contains a headline in a section 730, as well as a body of information (in this case, a table) in section a 735.
[0094] Finally, article 700 includes a list of discussion objects in a section 740. As discussed above, these discussion objects can be included when the article is first generated, and/or can be added with metadata enhancer 120 after generation is otherwise complete. Section 740 includes relevant discussion objects that were part of the article content. In this example, four business partners were discussed in the content; therefore, the discussion objects block contains four objects of class “BizPartner.” The article also relates to, and mentions in the content, the Eastern region and thus an additional object block is included to represent that object.
[0095] The discussion objects also include information about what is shown for the purpose of enforcing a security policy. In this example, article 700 shows sales numbers of customers and therefore a security realm is defined for that article stating that fact. Thus, in a filtering process such as process 305 in FIG. 3 , users who are not allowed to see articles of this security realm will be denied access to the article.
[0096] Defining classes and determining what classes are available may be done in many ways. For example, classes could be rigidly defined and coupled to the system 100, or classes could be defined in a distributed manner based on the incoming messages. In the latter case, system 100 assumes that an object and class exist if and when such object or class are read in an incoming article. It does not try to enforce validity based on a pre-defined object model; in this case, the full list of discussion classes is the object model referred to above with respect to metadata enhancer 120.
[0097] FIG. 8 demonstrates an example of an HTML result page 800 that includes article 700. Page 800 is generally organized like a newspaper front page, having a headline 805 (which in this case indicates the enterprise sponsoring the page). A main story 810, corresponding to article 700, is shown in the upper middle portion of the page. A section 815 shows current levels of the Dow Jones, NASDAQ, and S&P 500. The rest of page 800 includes additional hypothetical articles not previously described.
[0098] The filtering, sorting, prioritizing, and paginating processes already described determine whether an article is displayed in full size (for example, article 700 in section 810), simply as a link (for example, links within sections 820, 825, 830, 835, 840, and 850, which are shown grouped together with similar articles), with a “more” link (not shown) that does not include any details but allows access to additional articles, or not at all (in case there is no room on the screen). The rules under which the articles are rendered generally take into account both subjective (that is, according to user preferences) and objective (that is, according to the author) levels of importance assigned to each article and its content.
[0099] In FIG. 8 , the highest-ranking article occupies a central location. If two or more articles are categorized as highest ranking, then a number of options are available for deciding how and whether to display them. Examples include: (i) one article could be selected, at random or otherwise, (ii) all, or some, of the articles could be rotated in and out of the page (which uses time slicing as well as real estate allocation), (iii) if there is enough space, then all of the articles could be displayed, or at least part of each of them, for example, by giving each article the same amount of space or allocating space based on priority, and (iv) one article could be selected for full, or primary display, and the others could be identified with links indicating the title of the article or with a “more” link.
[0100] The concept of using time as a variable (T), as well as space (which can be considered as a single variable of area or as two variables—X and Y), can be applied in many ways to render prioritized data on a page or other format. For example, articles or other data could be displayed at particular locations for specified times, scrolled, formed into a collage, zoomed in and out with a fixed or variable size space, etc.
[0101] It should be noted that articles within page 800 may take many various forms besides the form of a general news articles. For example, section 840 includes an email that can be read by, or read to, the user. Section 840 also includes internal documents to be approved by the user. As a final example, section 850 is devoted to a personal scheduling issue of the user.
[0102] In any case, page 800 is generally arranged such that more important articles, as determined by system 100, are assigned a more prominent position and/or size, whereas less important articles are assigned a less prominent position and/or size (and/or are shown only partially or in summary form). Such prioritized assignment of “real estate” on page 800 is generally without respect to a given category into which an article of page 800 might fall, but rather, as explained above, is determined based on the actual content of the article(s).
[0103] Some implementations may group together articles of similar type or content, and in essence “categorize” the page view. For example, all email articles might be shown together. Such categorization may be done dynamically, based on the available content. In some of these implementations, categories such as “emails” may be used due to the presence of a large number of articles within that category for a particular user; in these cases, a combined priority weighting may be used to determine their (collective) prominence on page 800. In others of these implementations, a location for a specific subset may be determined in advance; such fixed positioning may be used for all or part of page 800
[0104] Page 800 may allow the user to express his preferences regarding what is shown in several different ways. In this implementation of the user interface (“UI”), every identified discussion object in the page is highlighted and also an icon (for example, “smiley face” 860) is located next to some articles or groups of articles. By clicking on any of these icons and/or discussion objects, the user is provided with a dialog that allows him to express his opinion on the object or article associated with the point where he clicked.
[0105] For example, user A may have previously indicated that articles about the customer Wacky Foods (the company's most important customer) are to be upgraded. Article 700's importance is shown as Normal within section 705 of FIG. 7 , but since it discusses Wacky Foods, its importance level is upgraded to Important for user A. Article 700 may thus be shown in a more prominent location in the result page for user A.
[0106] A future article about Wacky Foods may come in as already being designated as Important. In such a case, user A's upgrade will make that article Critical, emphasizing it in the result page 800. This later article will then show more prominently than article 700.
[0107] Further illustrating techniques by which a user may indicate preferences as to which articles should be shown and how they should be shown, FIG. 9 demonstrates a context menu 905 designed to allow users to input preference information. Context menu 905 may be accessed by a user by clicking on a highlighted discussion object within an article.
[0108] For example, a user may click on the words “Krafti Cheese” within one-of the links contained in section 820. In context menu 905, the user is then able to indicate one of five possible opinions on Krafti Cheese: never to be shown articles about Krafti Cheese (but note that in cases where articles contain both Krafti Cheese and a discussion object that the user has expressed explicit interest in, the article may still be shown); always to be shown articles dealing with Krafti Cheese; upgrade (or promote) the importance of articles containing Krafti Cheese; downgrade (or demote) the importance of articles containing Krafti Cheese (if the user downgrades a discussion object some predetermined number of times, that discussion object may be thereafter blocked completely); and postpone articles about Krafti Cheese for a specified period of time (this option is useful if the user has more important tasks at the moment but wants to be informed of such articles at a more convenient time). In the last example, context menu 910 illustrates time periods which may be selected to set a length of a postponement.
[0109] Finally, context menu 905 includes an advanced opinion dialog, provided for cases where the user wishes to express, for example, complex conditional opinions on the discussion object. One such condition might be to block all articles about Krafti Cheese unless they are marked as important. Another example might be to block Krafti Cheese articles that originated from publicly-available sources. The “Krafti Cheese” article within section 820 referred to above, about a CEO resignation, is an example of such an article. The fact that it is publicly accessible may be indicated as an attribute of the article, for example, as a security realm, as a custom attribute, or by an author of the article.
[0110] It is also possible, though not shown in FIG. 9 , to allow the user to express an opinion about the class of the discussion object. This option would allow the user to no longer receive articles concerning any business partners, not just Krafti Cheese.
[0111] In a similar fashion, the user may express an opinion about an article as a whole. For example, if the user is no longer interested in receiving a stock market update in section 815, the user may click on the “smiley face” icon 860 next to the market article in section 815.
[0112] FIG. 10 demonstrates an opinion dialog 1005 that enables the user to express his opinion about an article such as the market report article within section 815. Similarly to context menu 905, context menu 1005 allows the user to characterize the article in question. For the postpone operation, a box 1010 is available to provide similar options to those discussed with respect to context menu 910.
[0113] An additional option shown in context menu 1005 is the ability to Acknowledge an article, allowing the user to express the fact that he or she does not want to be informed of this particular instance of the article anymore. Future versions of the same article, however, would still be considered interesting to that user.
[0114] It is also possible to let the user provide more information. For example, the user may give a reason why he or she is no longer interested in this article, the reason being, for example, one of the discussion objects contained within the article. This feature may be useful in cases where the full article is not fully displayed on screen, and therefore its discussion objects are not visible. For example, the first article in section 840 talks about six documents, but names and authors are not shown as part of the link because of lack of space. The user may specify that he no longer wants to be notified about documents from John Doe (a hypothetical author of one of the documents), for example.
[0115] In many cases, the user would like to indicate his preferences regarding objects that are not currently displayed on the screen. Such objects may have been read in a story in a newspaper, or seen on TV, or heard in a rumor. For those cases, the system 100 provides a Tell Me input box or similar UI in section 855 that enables the user to enter the name of what he or she is looking for.
[0116] As an example, if the user heard from the sales manager that sales of Pizza Zitti are down 5% this quarter, the user can type in Pizza Zitti in the Tell Me box and press enter. The system 100 will look up the object that matches the text, possibly presenting several options for the user to choose from. In this case, Pizza Zitti is a product, so every article containing a reference to this product will be prioritized based on the user's preferences regarding Pizza Zitti.
[0117] FIG. 11 demonstrates a different technique by which the user may express his or her opinions about a discussion object. In FIG. 11 , clicking on a highlighted discussion object results in a pop-up box that allows the user to rate the discussion object. In FIG. 11 , the discussion object “Wacky Foods” has been given one out of a possible five stars in pop-up box 1105, whereas the discussion object “Have Your Cake, Inc.” has been given four out of five stars in a pop-up box 1110. Pop-up boxes 1105 and 1110 also include an “x” and a “check” box, by which a user may choose to “block” the given object or select to “always see” it in the future, respectively, as described above. Pop-up boxes like boxes 1105 and 1110 may be used with respect to individual discussion objects, classes of discussion objects, or may be used with respect to articles as a whole.
[0118] FIG. 12 demonstrates a page 1200 that reflects user-expressed opinions with respect to page 800 of FIG. 8 . Specifically, page 1200 illustrates the situation in which the user (1) clicked on the Market Report 815 opinion icon 860 and indicated “no interest” in Market Reports, and (2) clicked on the words “Krafti Cheese” in section 820 and indicated “no interest” in Krafti Cheese.
[0119] Page 1200 reflects the resulting new set of preferences. Specifically, articles about Krafti Cheese in sections 820 and 825 are removed, and a new article entitled “Milky Way Milk files Chapter 11” is included instead. Also, the Market Report in section 815 is gone, and the weather article in section 835 has taken its place. Finally, additional space created by the above changes, particularly movement of the weather article in section 835, permits the addition of two new articles in section 840.
[0120] In some implementations, system 100 may learn automatically by observing the user's behavior. For example, if a user clicks on a particular article, the implementation may increment the priority of one or more of the various discussion objects represented by that article. Two possibilities, for example, are that (1) all of the discussion objects or object classes in that article are incremented in priority, or that (2) only a primary discussion object in that article is incremented. A primary discussion object could be determined in a variety of ways, such as, for example, by counting occurrences of search strings in the article. Priority may be a numerical scale or otherwise, allowing easy incrementing and decrementing.
[0121] Various operations depicted in FIGS. 2–6 may be combined. For example, operations of agents in gathering information for articles may be combined with the filtering, sorting, prioritizing, and/or pagination operations. In one implementation, each user may have an individual “agent” that performs all of the filtering, sorting, prioritizing, and/or pagination operations when a page is requested by the user.
[0122] Also, articles may be pushed straight from a source, rather than being collected by an agent. In one implementation, articles are broadcast and are filtered at the time of broadcast, by the broadcaster, to place them in one or more buckets. In another implementation, a user's system performs the filtering operations on articles as the articles are broadcast. In either of these implementations, the function of the agent has been moved to the broadcaster and the user, respectively, and the agent execution environment has been removed.
[0123] One implementation may process articles as they come in, filtering them into the buckets of each user at that time. The articles wait in that bucket until such time as a user requests a page. At that time the prioritization and pagination processes kick in, and the page is created. This may provide improved performance over filtering at the time a user requests a page, particularly in cases where the user logs into the system 100 relatively rarely.
[0124] Various implementations allow: (i) filtering articles or other data based on content of the delivered or available data, (ii) adjusting display of data based on content, (iii) filtering articles dynamically, upon viewing, or otherwise, (iv) adjusting display of data dynamically, and/or (v) separating producers of articles or other data from consumers of the data.
[0125] Implementations discussed above contemplate the use of audio and video presentations as part of a personalized delivery of content. In some implementations, these and other features can be utilized outside of the context of system 100 and the associated discussions above, and can be implemented similarly to portal-based techniques.
[0126] FIG. 13 demonstrates an implementation of a content personalization system designed primarily for generating personalized audio and video-based information systems.
[0127] In FIG. 13 , article reader 1305 obtains articles from content generator 110. An article reader 1305 need not include a metadata enhancer, and need not store the articles separately (although the articles could be cached for possible later use, as is known). An article processor may then associate articles with particular users, using a user preference database 1315. This association may occur by virtue of content metadata such as discussion objects contained within the articles, as discussed above, or may occur only by virtue of a comparison of general article attributes to user preferences.
[0128] A pagination engine 1320 communicates with both article processor 1310 and user systems 1340 and/or 1345. Pagination engine 1320, as with pagination engine 165 of FIG. 1 , will typically have access to characteristics of the client system being used by each user, either from user preference database 1315, or determined from the user request at the time of the request.
[0129] In this way, pagination engine 1320 determines a layout of the canvas being used by each user, using a canvas layout subsystem 1325 that is similar to canvas layout subsystem 170 of FIG. 1 . As with canvas layout subsystem 170, one of the services of the canvas layout subsystem 1325 is to determine how much “space” is available to the user for displaying articles, as well as any other user-specific capacity constraints relevant to deciding which articles to provide to the user(s).
[0130] Content-type selector 1330 may then determine which rendering media are available to the user for the selected canvas, and which articles are consistent, or can be made to be consistent, with that media. Media-type enabler 1335 is available to utilize a type of media that would not normally be available to the user, as discussed above with respect to media-type enabler 180.
[0131] As referred to above, in the implementation of FIG. 13 , article selection and layout may be determined essentially as is done in the context of traditional portal technology, or may incorporate any or all of the advantageous features of system 100. In any case, as discussed in more detail below, system 1300 serves to provide personalized audio and/or video presentations above and beyond the context of traditional browser-based technologies.
[0132] FIG. 14 demonstrates an article 1400 used in one implementation of the system. Article 1400 is similar to article 700 in many respects, and is also written in XML. In article 1400, a section 1405 contains general attributes of the article, such as its author, time of creation, and level of importance. A section 1410 labels a first content portion as being narrative text in proper grammar for reading and having a headline portion 1415 and a details portion 1420. A section 1425 labels a second content portion as being HTML-based, with a headline in section 1430 and a table 1435, as its detailed content.
[0133] A section 1440 labels the next content block as containing a viewable image in a standard format such as “.gif.” The image has an associated headline in section 1445, and is itself located in section 1450. Finally, a section 1455 labels a last content block as containing music, which may be, for example, background music having no words, in a standard format such as “midi.” The actual midi file is in a section 1460.
[0134] Although not explicitly shown, it should be understood that video (for example, MPEG) and other formats may also be used. Also, as should be understood from FIG. 6 , articles such as article 1400 may include summaries of the articles, or of article portions. Also, content blocks may be labeled as mutually exclusive or not, for example, typically an article summary would not be included in the same page as the article itself, as that would be redundant.
[0135] FIG. 15 shows one implementation of a rendering of article 1400. In FIG. 15 , a computer 1505 displays in a section 1510 the HTML table from sections 1430/1435 of article 1400. A section 1515 depicts an anchorwoman “reading” the story of section 1415/1420; that is, a computer-generated image of a woman with animated lips and eyes moving to simulate talking, generates audio represented by a section 1520. Headline 1425 may be read by the generated anchorwoman image, and/or may be shown as an image 1535 (note that, since narrative text can be treated as readable text, it does not always have to be read).
[0136] A section 1525 displays the gif image from sections 1445/1450 of article 1400, and though not explicitly shown in FIG. 15 , the midi music file from section 1460 may be played in the background, or may be ignored. Finally, a section 1530 displays additional headlines from other articles, which may be aggregated for inclusion in the display of computer 1505 by pagination engine 1325. These articles may be, for example, articles designated as “headlines of the day” by article processor 1415 or articles related to the currently-displayed article. These articles may be non-specific to users A and B, or may be specific to a group of users.
[0137] In FIG. 15 , the layout places the sensory input types into appropriate positions. For example, the anchorwoman cannot “read” an image; she can only read narrative text. The system 1300 has chosen, using canvas layout subsystem 1325, to display the two viewable images contained in the article 1400; two are shown because there is enough real estate on the screen of computer 1505. Other implementations may show one at a time, flicking between them, or not show some of them at all.
[0138] The following examples demonstrate various utilizations of content presentation systems. Many people today spend a lot of their time commuting to work. They sit in a car usually listening to the radio without the ability to access corporate data, or perhaps they have a conference call with several colleagues. Content presentation systems as described herein may allow this time to be better used by generating an audio track summarizing the day's news. The track's time length can be set so as to cover the time it takes the employee to commute. Then, the employee can simply call a phone number to access the information needed to start the day. Alternatively, the audio track may be delivered to a capable audio player like an MPEG Layer 3 (“MP3”) player or a PDA. Delivery may be made, for example, by downloading from a cellular network.
[0139] In a company building, there are several places of high-traffic where people congregate. Those places are often characterized by not having access to computers. Two examples of these places are the lobby and the cafeteria. Implementations of content presentation systems may be used to generate a video track that will run in a loop and be shown on a television screen. People can then watch that video while they wait in the lobby (for example, public company data shown to a guest of the company) or eat lunch (for example, internal company news for its employees).
[0140] Another example of a location where people wait, often with little or nothing to do, is an airport. In many airports, next to the boarding gate, there are TV sets tuned to a news station, such as the Cable News Network (“CNN”). In some cases, the channel is even customized for airport use. However, there is only one channel for all airports, so the channel is not personalized to a particular airport or even a gate. Various implementations allow for such personalization. For example, depending on a destination of a flight leaving a near-by gate, as well as connecting flights out of that location, the video may show relevant weather reports, flight delays, security alerts, or terminal maps.
[0141] Various implementations allow a content editor to personalize an information system for a group of users, such as by personalizing a TV station for passengers at a particular gate in a specific airport. Various implementations allow an individual user to personalize an information system for himself, such as by personalizing a voicemail recording of particular news items so that the user can listen to it during the morning commute. The acquisition, rendering, and delivery of such personalized information can be automated and no human involvement is necessary. Mediums such as, for example, TV, telephone, computer, and radio can be used.
[0142] Moreover, the personalization process itself can be automated. For example, using the example of the airport gate TV, the destination of a flight can be input as “user preferences” in database 1315 (here the “user” is, for example, an airport administrator, and system 1340 is the gate TV) by accessing a flight schedule database.
[0143] As already mentioned, acquiring, rendering, and editing data, as well as various other operations, can be performed in whole or in part using elements of system 100. Additional editing may be used to control the content for a specified period of time. For example, a user may personalize the rendering format to provide ten minutes of different content in an audio format. Articles or other data could be prioritized based on content, with entire articles narrated in order of priority. Such narration could be used in an audio format, and also in a video format with additional information being visible.
[0144] A number of implementations of methods and systems for presenting personalized content have been described. Nevertheless, it will be understood that various modifications may be made. For example, the system 100 can be used without the personalized security and/or preference-based filtering performed in content-based router 130; that is, all articles in database 125 may be prioritized by PAP 145. Also, prioritization in PAP 145 may occur before security/preference-based filtering. Security-based filtering may occur without preference-based filtering, and vice-versa. As a final example, content-based router 130 could be implemented in two separate subsystems, one subsystem being responsible for security-based filtering, while the other subsystem is responsible for preference-based filtering. Accordingly, other implementations are within the scope of the following claims.
Claims
What is claimed is:
1. A computer-implemented method for aggregating content for a user, the method comprising:
accessing a plurality of media assets stored in a computer-readable medium, wherein:
at least one media asset is associated with a discrete piece of content and includes content blocks,
each content block that is included in the at least one media asset includes at least a portion of the discrete piece of content associated with the at least one media asset,
each content block that is included in the at least one media asset is associated with one of a plurality of content types,
each of the content types represent a format capable of being rendered in a particular rendering medium, and
one content block included in the at least one media asset is associated with a content type that is different from a content type associated with another content block included in the at least one media asset;
selecting a subset of the plurality of media assets based on a content preference of a user; determining a rendering medium that is available;
using the determined rendering medium to choose, for each media asset within the subset, a content block of the media asset, a chosen content block being associated with a content type having a format capable of being rendered in the determined rendering medium;
aggregating, for each media asset within the subset, the at least a portion of the discrete piece of content included in each of the chosen content blocks into a cohesive presentation, the at least a portion of the discrete piece of content included in each of the chosen content blocks being expressed in the determined rendering medium; and
storing the cohesive presentation for later display.
2. The method of claim 1, wherein each media asset includes a content discussion object characterizing the discrete piece of content associated with the media asset, and selecting the subset of the plurality of media assets comprises:
inputting content preference discussion objects received from the user; and
comparing the content discussion object included within each of the plurality of media assets against the content preference discussion objects.
3. The method of claim 2, wherein the content discussion objects each characterize individual elements of information within the discrete piece of content.
4. The method of claim 1, wherein the plurality of content types includes hyper-text markup language (“HTML”), text, text to be rendered as video, or text to be rendered as audio.
5. The method of claim 1, wherein the determined rendering medium includes at least one of an HTML-based web-page, video, audio, or text.
6. The method of claim 1, wherein a rendering medium is available if the rendering medium is associated with a characteristic of a client system of the user.
7. The method of claim 1, wherein a rendering medium is available if the rendering medium is associated with a preference of the user.
8. The method of claim 1, wherein a rendering medium is available if the rendering medium is associated with a delivery request from the user, the request including information about a client system of the user.
9. The method of claim 1, wherein aggregating the at least a portion of the discrete pieces of content included in the chosen content blocks comprises:
determining that at least one of the chosen content blocks is associated with a content type of narrative data; and
generating a graphic, video, or audio presentation of the narrative data.
10. The method of claim 1, wherein aggregating the at least a portion of the discrete piece of content included in the chosen content blocks comprises:
determining that at least one of the chosen content blocks is associated with a content type of graphical data; and
generating a video representation of the graphical data.
11. The method of claim 1, wherein aggregating the at least a portion of the discrete piece of content included in the chosen content block for each media asset within the subset into a cohesive presentation comprises determining an order of the discrete piece of content of each media asset within the cohesive presentation based on a preference of the user.
12. The method of claim 1, wherein each media asset in the subset includes metadata characterizing the discrete piece of content thereof and aggregating the at least a portion of the discrete piece of content included in the chosen content blocks into a cohesive presentation comprises determining an order of the at least a portion of the discrete piece of content included in the chosen content blocks within the cohesive presentation based on a consideration of the metadata with respect to a characteristic of a client system of the user or a preference of the user.
13. The method of claim 1, further comprising delivering the cohesive presentation to a machine accessible by the user.
14. The method of claim 13, wherein delivering the cohesive presentation comprises delivering the cohesive presentation electronically.
15. The method of claim 13, wherein delivering the cohesive presentation comprises delivering the cohesive presentation via a private network.
16. The method of claim 13, wherein delivering the cohesive presentation comprises delivering the cohesive presentation via a public network.
17. The method of claim 1, wherein accessing a plurality of media assets, selecting a subset of the plurality of media assets, and aggregating the at least a portion of the discrete piece of content included in the chosen content blocks into a cohesive presentation are performed electronically.
18. The method of claim 1, wherein selecting a subset of the plurality of media assets comprises:
filtering the plurality of media assets based on the content preference of the user, to thereby obtain a filtered subset; and
prioritizing the filtered subset based on the content preference of the user.
19. The method of claim 1, wherein the discrete piece of content of the media asset includes a profit and loss report of a company, an online analytical processing report, or a print-out of a sales order.
20. The method of claim 1, wherein the cohesive presentation is stored in persistent memory.
21. The method of claim 1, wherein the cohesive presentation is stored in transient memory.
22. A computer-based system tangibly embodied on a computer-readable medium for aggregating content for a user, the system comprising:
an article reader operable to access a plurality of media assets stored in a computer storage medium, wherein:
at least one media asset is associated with a discrete piece of content and includes content blocks,
each content block that is included in the at least one media asset is labeled as one of a plurality of content types,
each content block that is included in the at least one media asset includes a segment of the discrete piece of content of the at least one media asset,
each content type represents a format capable of being rendered in a particular rendering medium;
one content block included in the at least one media asset is labeled with a content type that is different from a content type label applied to another content block included in the at least one media asset;
a sorting engine operable to select a subset of the plurality of media assets based on a content preference of a user;
a rendering medium determination engine operable to determine a rendering medium that is available;
a content-type selector operable to use the determined rendering medium to select a content block for each media asset within the subset, a selected content block being associated with a content type having a format capable of being rendered in the determined rendering medium;
an aggregation engine operable to combine, for each media asset within the subset, the at least a portion of the discrete piece of content included in each of the selected content blocks; and
a storage facility operable to store the combined content for later display.
23. The system of claim 22, wherein the content-type selector is operable to select the content block based on a characteristic of a client system of the user.
24. The system of claim 22, wherein the article reader is further operable to publish content metadata associated with each media asset, the content metadata characterizing the segment of the discrete piece of content associated with at least one media asset.
25. The system of claim 24, wherein the sorting engine is further operable to select the subset based on the content metadata.
26. The system of claim 22, wherein the content-type selector is operable to select a content block based on a preference of the user.
27. The system of claim 22, wherein the content-type selector is operable to select the content block based on receipt of a delivery request from the user, the request including information about a client system of the user.
28. The system of claim 22, wherein the aggregation engine is further operable to determine that at least one of the plurality of content types is narrative data, and to generate a graphic, video or audio presentation of the narrative data.
29. The system of claim 22 wherein the aggregation engine is further operable to determine that at least one of the plurality of content types is narrative data, and generate a video representation of the narrative data.
30. The system of claim 29, wherein the video representation is a computer-generated image of an animated head made to resemble a person reading the narrative data.
31. The system of claim 22, further comprising a rendering engine is operable to render the combined and stored content based on prioritization information related to a preference of the user.
32. The system of claim 22, wherein the storage facility is further operable to store the aggregated content in persistent memory.
33. The system of claim 22, wherein the storage facility is further operable to store the aggregated content in transient memory.
34. A computer program product for aggregating content for a user, the computer program product embodied in a computer-readable medium including instructions, that when executed by a processor, cause the processor to:
access a first media asset and a second media asset from a computer storage medium, wherein:
the first and second media assets are each associated with a discrete piece of content,
the first media asset includes a first content segment,
the second media asset includes a second content segment,
each of the first and second content segments includes at least a portion of the discrete piece of content associated with the first and second media assets,
each of the first and second content segments is associated with a rendering medium, and
the first content segment is associated with a rendering medium that is different from the rendering medium associated with the second content segment;
select a the rendering medium associated with the first content segment for delivery of the at least a portion of the discrete piece of content included in the first content segment to a client system;
select the rendering medium associated with the second content segment for delivery of the at least a portion of the discrete piece of content included in the second content segment to the client system;
aggregate the at least a portion of the discrete piece of content included in the first content segment and the at least a portion of the discrete piece of content included in the second content segment into a cohesive presentation; and
store the cohesive presentation for later display.
35. The computer program product of claim 34 wherein the instructions, when executed, further cause the processor to deliver the cohesive presentation to the client system.
36. The computer program product of claim 34 wherein the instructions, when executed, further cause the processor to select f the rendering medium associated with each of the first and second content segments based on a characteristic of the client system.
37. The computer program product of claim 34, wherein accessing a first media asset and second media asset includes accessing the discrete piece of content associated with each of the first and second media assets, wherein the discrete pieces of content each include narrative text, and combining the first and second content segments includes generating a video or an audio presentation from the narrative text.
38. The computer program product of claim 34 wherein the instructions, when executed, further cause the processor to store the cohesive presentation in persistent memory.
39. The computer program product of claim 34 wherein the instructions, when executed, further cause the processor to store the cohesive presentation in transient memory.
40. A computer-implemented method for delivering content, the method comprising:
selecting a first media asset and a second media asset from a computer storage medium, wherein:
the first and second media assets are each associated with a discrete piece of content,
the first media asset includes a first content segment,
the second media asset includes a second content segment,
each of the first and second content segments include at least a portion of the discrete piece of content of the first and second media assets,
each of the first and second content segments is associated with a rendering medium,
the first content segment is associated with a rendering medium that is different from the rendering medium associated with the second content segment;
selecting the rendering medium associated with the first content segment for delivery of the at least a portion of the discrete piece of content included in the first content segment to a client system;
selecting the rendering medium associated with the second content segment for delivery of the at least a portion of the discrete piece of content included in the second content segment to the client system;
combining the at least a portion of the discrete piece of content included in the first content segment and the at least a portion of the discrete piece of content included in the second content segment into a cohesive presentation;
storing the cohesive presentation; and
delivering the stored cohesive presentation to the client system for display.
41. The method of claim 40, wherein the cohesive presentation is stored in persistent memory.
42. The method of claim 40, wherein the cohesive presentation is stored in transient memory.
43. A computer-based system tangibly embodied on a computer-readable medium for delivering content, the system comprising:
a selection subsystem operable to select a first and second article from among a pool of articles stored in a computer storage medium, wherein:
the first and second article are each associated with a discrete piece of content,
the first article includes a first content segment,
the second article includes a second content segment,
each of the first and second content segments include at least a portion of the discrete piece of content of the first and second articles,
each of the first and second content segments is associated with one of a plurality of rendering media,
the first content segment is associated with a rendering medium that is different from the rendering medium associated with the second content segment, and
the rendering media associated with each of the first and second content segments is determined based on data included within the first and second articles; and
a pagination engine operable to aggregate the at least a portion of the discrete piece of content included in the first and second content segments;
a delivery engine operable to deliver the aggregated content to a client system; and
a rendering engine operable to render the aggregated content at the client system using the rendering media associated with each of the first and second content segments.
44. The system of claim 43, wherein the data included within the first and second articles relates to a characteristic of the client system.
45. The system of claim 43, wherein the first and second content segments include a first and a second content type, and the first and second content types are related to the rendering media associated with the first and second content segments, respectively.
46. The system of claim 45, wherein the first content type is text, audio, video, text to be rendered as audio, or text to be rendered as video.
47. The system of claim 43, wherein the selection subsystem is further operable to determine an order of the first content segment with respect to the second content segment, based on a content preference of a user of the client system.
48. A computer-based system tangibly embodied on a computer-readable medium for delivering content, the system comprising:
means for selecting a subset of a plurality of articles stored in a computer storage medium, wherein:
at least one article in the subset is associated with a discrete piece of content and includes a first content segment and a second content segment,
each of the first and second content segments include at least a portion of the discrete piece of content of the at least one article,
each of the first and second content segments is associated with a content type,
each of the content types represents a format capable of being rendered in a specific rendering medium;
the first content segment is associated with a content type that is different from the content type associated with the second content segment,
means for determining a rendering medium that is available;
means for choosing, for each article within the subset, a content segment of the article based on the determined rendering medium, a chosen content segment being associated with the content type having a format capable of being rendered in the determined rendering medium;
means for combining, for each article within the subset, the at least a portion of the discrete piece of content included in each of the chosen content segments into a cohesive presentation, the at least a portion of the discrete piece of content included in each of the chosen content segments being expressed in the determined rendering medium; and
means for storing the cohesive presentation for later display.
49. The system of claim 48, further comprising means for delivering the cohesive presentation.
50. The system of claim 48 wherein the means for storing the cohesive presentation stores the cohesive presentation in persistent memory.
51. The system of claim 48 wherein the means for storing the cohesive presentation stores the cohesive presentation in transient memory.
Patent Citations (50)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5442740(A) | 1995-08-01 | Parikh | Applicant |
| US5848424(A) | 1998-12-01 | Scheinkman et al. | Applicant |
| US5995943(A) | 1999-11-01 | Bull et al. | Applicant |
| US6041331(A) | 2000-03-01 | Weiner et al. | Applicant |
| US6058277(A) | 2000-05-01 | Streefkerk et al. | Applicant |
| US6064980(A) | 2000-05-01 | Jacobi et al. | Applicant |
| US6085229(A) | 2000-07-01 | Newman et al. | Applicant |
| US6094648(A) | 2000-07-01 | Aalbersberg | Applicant |
| US6154764(A) | 2000-11-01 | Nitta et al. | Applicant |
| US6181342(B1) | 2001-01-01 | Niblack | Applicant |
| US6209100(B1) | 2001-03-01 | Robertson et al. | Applicant |
| US6236395(B1) | 2001-05-01 | Sezan et al. | Applicant |
| US6266649(B1) | 2001-07-01 | Linden et al. | Applicant |
| US6271840(B1) | 2001-08-01 | Finseth et al. | Applicant |
| US6300947(B1) | 2001-10-01 | Kanevsky | Applicant |
| US6317722(B1) | 2001-11-01 | Jacobi et al. | Applicant |
| US6327628(B1) | 2001-12-01 | Anuff et al. | Applicant |
| US6356908(B1) | 2002-03-01 | Brown et al. | Applicant |
| US6356922(B1) | 2002-03-01 | Schilit et al. | Applicant |
| US6457026(B1) | 2002-09-01 | Graham et al. | Applicant |
| US6646549(B2) | 2003-11-01 | Dawson | Applicant |
| US6918090(B2) | 2005-07-01 | Hesmer et al. | Examiner |
| US2002/0018078(A1) | 2002-02-01 | Khan et al. | Examiner |
| US2002/0049833(A1) | 2002-04-01 | Kikinis | Applicant |
| US2002/0053078(A1) | 2002-05-01 | Holtz et al. | Applicant |
| US2002/0059584(A1) | 2002-05-01 | Ferman et al. | Applicant |
| US2002/0122063(A1) | 2002-09-01 | Weinberg et al. | Applicant |
| US2002/0138844(A1) | 2002-09-01 | Otenasek et al. | Examiner |
| US2002/0178007(A1) | 2002-11-01 | Slotznick et al. | Examiner |
| US2002/0198973(A1) | 2002-12-01 | Besaw | Examiner |
| US2003/0093790(A1) | 2003-05-01 | Logan et al. | Applicant |
| US2003/0101412(A1) | 2003-05-01 | Eid | Examiner |
| US2003/0110297(A1) | 2003-06-01 | Tabatabai et al. | Examiner |
| US2003/0126136(A1) | 2003-07-01 | Omoigui | Examiner |
| US2003/0152904(A1) | 2003-08-01 | Doty, Jr. | Examiner |
| US2003/0217061(A1) | 2003-11-01 | Agassi et al. | Applicant |
| US2003/0229900(A1) | 2003-12-01 | Reisman | Applicant |
| US2004/0205473(A1) | 2004-10-01 | Fisher et al. | Examiner |
| US2004/0220926(A1) | 2004-11-01 | Lamkin et al. | Examiner |
| US2005/0193335(A1) | 2005-09-01 | Dorai et al. | Applicant |
| EP1143679(A2) | 2001-10-01 | Applicant | |
| EP1176520(A2) | 2002-01-01 | Applicant | |
| EP1367513(A2) | 2003-12-01 | Applicant | |
| WO99/62011 | 1999-12-01 | Applicant | |
| WO/65773 | 2000-11-01 | Applicant | |
| WO1/09737(A1) | 2001-02-01 | Applicant | |
| WO1/13287(A) | 2001-02-01 | Applicant | |
| WO1/18688(A2) | 2001-03-01 | Applicant | |
| WO1/77903(A1) | 2001-10-01 | Applicant | |
| WO1/81829(A1) | 2001-11-01 | Applicant |
Non-Patent Literature (26)
- SAP Design Guild—Generic Portal Pages—What Do Most Portal Need?, published at www.sapdesignguild.org/editions/edition3/print—generic—pages.asp on May 21, 2001.Examiner
- SAP Design Guild—Building Blocks of Portals, published at www.sapdesignguild.org/editions/edition1/print—cooper2.asp on Aug. 1, 2000.Examiner
- SAP Design Guild—Portals—A Step Beyond the Desktop, published at www.sapdesignguild.org/editions/edition1/print—walo2.asp on Aug. 1, 2000.Examiner
- SAP Design Guild—Generic MiniApps (iViews), published at www.sapdesignguild.org/editions/edition3/print—gen—iview.asp on May 21, 2001.Examiner
- SAP Design Guild—The Web—A Short Introduction, published at www.sapdesignguild.org/communicty/design/print—web.asp on Dec. 22, 2000.Examiner
- SAP Design Guild—Budget Manager Portal, published at www.sapdesignguild.org/editions/edition2/print—budget—m.asp on Dec. 22, 2000.Examiner
- SAP Design Guild—Brand Manager Portal, published at www.sapdesignguild.org/editions/edition2/print—brand—m.asp on Dec. 22, 2000.Examiner
- SAP Design Guild—Line Manager Portal, published at www.sapdesignguild.org/editions/edition2/print—line—m.asp on Dec. 22, 2000.Examiner
- SAP Aktiengesellschaft, “mySAP Technology: Portal Infrastructure: People-Centric Collaboration,” undated materials, copyright 2001, 28 pgs.Applicant
- Bhatia, S. K., “Selection of Search Terms Based on User Profile,” Proceedings of the 1992 ACM/SIGAPP Symposium on Applied Computing: Technological Challenges of the 1990's, Kansas City, MO, 1992, pp. 224-233.Applicant
- Kamba, T. et al., “The Krakatoa Chronicle—An Interactive, Personalized, Newspaper on the Web,” Proceedings of the International Conference on World Wide Web, Dec. 11, 1995, pp. 1-12.Applicant
- Salembier, P. et al., “Description Schemes for Video Programs, Users and Devices,” Signal Processing: Image Communication, Sep. 2000, vol. 16, pp. 211-234.Applicant
- Seo, Y. W. et al., “Learning User's Preferences by Analyzing Web-Browsing Behaviors,” Proceedings of the Fourth International Conference on Autonomous Agents, Barcelona, Spain, Jun. 3-7, 2000, pp. 381-387.Applicant
- Sugiura, A. et al., “Internet Scrapbook: Automating Web Browsing Tasks by Demonstration,” UIST '98, ACM Symposium on User Interface Software and Technology, San Francisco, CA, Nov. 1-4, 1998, pp. 9-18.Applicant
- Bulterman, D. C. A., et al., “GriNS: A Graphical Interface for Creating and Playing SMIL Documents,” Computer Networks and ISDN Systems, North Holland Publishing, Amsterdam, NL, vol. 30, No. 1-7, pp. 519-529, XP004121396, © 1998.Applicant
- Google News (BETA), “Top Stories,” http://news.google.com, printed from the Internet Oct. 1, 2002, 5 pgs.Applicant
- Google News (BETA), “A Novel Approach to News,” http://news.google.com/help/about—news—search.html, printed from the Internet Oct. 1, 2002, 3 pgs.Applicant
- IBM, “IBM Websphere Portal Server Product Architecture V2.1,” Nov. 19, 2001, pp. 1-31, XP002268018.Applicant
- Li, Chung-Sheng, et al., “Multimedia Content Description in the Infopyramid,” Acoustics, Speech and Signal Processing, Proceedings of the 1998 IEEE International Conference, May 12, 1998, pp. 3789-3792, XP010279595.Applicant
- Boguraev, Branimir, et al., “Dynamic Presentation of Document Content for Rapid On-Line Skimming,” AAAI Symposium on Intelligent Text Summarization, Mar. 23, 1998, XP002096508, 10 pgs.Applicant
- Graham, Jamey, “The Reader's Helper: A Personalized Document Reading Environment,” CHI '99 Conference Proceedings Human Factors in Computing Systems, Pittsburgh, PA, May 15, 1999, XP000894254, pp. 481-488.Applicant
- Amazon.com, “Recommendations,” http://www.amazon.com/exec/obidos/tg/browse/-/508506/ref=br—bx—c—2—1/002-7851280-4410446, published 1996, 2 pgs.Applicant
- Amazon.com, “Why Was I Recommended This?” http://www.amazon.com/exec/obidos/tg/browse/-/764534/ref%3Dbr%5Fbx%5Fc%5F2%5F2/002-/002-7851280-4410446, published 1996, 2 pgs.Applicant
- Amazon.com, “Your Favorites,” http://www.amazon.com/exec/obidos/tg/browse/-/560726/ref=br—bx—c—2—0/002-7851280-4410446, published 1996, 2 pgs.Applicant
- Netflix, “About Netflix,” http://www.netflix.com/PressRoom?id=1005, published Apr. 28, 2003, 1 pg.Applicant
- Netflix, “Fact Sheet,” http://www.netflix.com/PressRoom?id=5206, published Oct. 2, 2003 , 3 pgs.Applicant