This invention relates to serving content to a client
Content may be served, for example, in web pages, which are adapted text and graphics documents that a user views utilizing a web browser such as Netscape Navigator® and Internet Explorer®. The documents are constructed using HyperText Markup Language (“HTML”). HTML is composed of a set of elements that define a document and guide its display.
In general, in one aspect, the invention features a method including scanning content of a web page or site in which a web component is to be inserted, inferring a profile from the scanned content and serving the web component in the web page according to the profile. This aspect may include one or more of the following features.
In implementations of the invention, the web page and the component include HyperText Markup Language (HTML). The content includes contextual material including topical, geographical, temporal and semantic characteristics. The component may include syndicated services including message boards, chat rooms, file exchanges, link exchanges, E-commerce and auctions.
The component may include syndicated content including news feeds, weather information, stock information, road maps, pictures, video, audio and text.
The profile includes a format of the scanned content and a topic of the scanned topic. The component includes embedded elements such as in-situ syndicated textual or multimedia material shown within a context of the web page.
Serving includes script insertion, inserting frames, iframes, layers, applets, active-x controls and plugins.
The embedded element may include a standalone element such as syndicated textual or multimedia material shown within its own context in a browser window, dialog window or pop-up window.
Scanning includes analyzing a site format of the content, analyzing a site content of the content and saving the site format and the site content as a profile. The profile is utilized as the profile and the profile may be utilized in real-time each time a component is displayed to a user.
Serving may include checking the web page for updates and updating the profile in response to checking, where checking can include comparing expiry information, last modified dates, cyclic redundancy codes (CRCs) or MD5s, i.e., algorithms used to verify data integrity through the creation of a 128-bit message digest from data input. Cyclic redundancy checking is a method of checking for errors in data that has been transmitted on a communications link. A sending device applies a 16- or 32-bit polynomial to a block of data that is to be transmitted and appends the resulting CRC to the block. The receiving end applies the same polynomial to the data and compares its result with the result appended by the sender. If they agree, the data has been received successfully. If not, the sender can be notified to resend the block of data.
Other features and advantages of the invention will become apparent from the following description, including the claims and drawings.
In
Computer 12 contains a processor 18 and a memory 20. Memory 20 stores an operating system (“OS”) 24 such as Windows98®, a TCP/IP protocol stack 26 for communicating over network 14, and a Web browser 28, such as Internet Explorer® or Netscape Navigator®, for accessing Web sites and pages hosted and served by devices on network 14.
First server 16 contains a processor 30 and a memory 32. Memory 32 stores machine-executable instructions 36, OS 38, TCP/IP protocol stack 40, and database 42 containing user accessible Web content, e.g., Web pages. Database 42 is described below. Instructions 36 may be part of an Internet search engine or not, and are executed by processor 30 to perform process 70 below. That is, a user at computer 12 uses Web browser 28 to access first server 16, which, in response, executes instructions 36 to perform the process described below.
Second server 17 contains a processor 44 and a memory 46. Memory 46 stores machine-executable instructions 48, OS 50, TCP/IP protocol stack 52, and database 54 containing Web components (e.g., content) accessible by the first server 16. Database 54 is described below.
Referring to
Process 70 includes a pre-processing phase 72 and a run-time phase 74. During pre-processing phase 72, process 70 requests (76), in conjunction with specific Web content residing in its database 42, subscription to one or more web components, e.g., syndicated content and/or syndicated services, resident in the database 54 of the second server 17 or externally via the network 14. In response to the request (76), the second server 17 sends (78) a web component to the first server 16. The web component is adapted to the first server 16 by the second server 17 to the specific Web content residing in database 42. In this context, “adapted” refers to a process by which at least the format and content of the specific Web content are determined and utilized to generate a profile. The profile is used by the second server 17 to format the requested web component in the database 54 for insertion into the specific web content in the database 42 for storage and/or display to a user.
During run-time phase 74, process 70 receives (80) a request for specific web content from a user. The request may be direct input of a universal resource locator (URL) by the user. Alternatively the request may be the result of the user directing their browser software to load the specific web content as part of a response to a search.
Process 70 searches (82) its database 42 for the requested specific web content. When the requested specific web content is located, the process 70 inserts (84) an additional web component from the database 54 of the second server 17 prior to serving the specific web content to the user. Process 70 displays (86) the specific web content with the additional adapted web component to the user on computer 12.
Referring to
Using HTML as an example, HTML is a language of elements that are used to define a document and guide its display. HTML documents are plain-text (also known as ASCII) files that can be composed using any text editor. An element is a fundamental component of the structure of a text document. Examples of elements are heads, tables, paragraphs, and lists. HTML uses tags to denote elements contained in the document. Some elements may include one or more attributes. An attribute is additional information that is included in a smart tag. For example, one can specify the alignment of images, e.g., top, middle, bottom, by including the appropriate image source HTML code. Other attributes may be specified. For example, background color may be specified to match a color of text font, and external images, sounds, and animations may be incorporated. Document style, colors, background, background images, table characteristics, fonts, margins, and other visual characteristic may be specified in the document.
Style Sheets allow an HTML author to separate presentation definitions from content in HTML documents. HTML was designed primarily as a content-based mark up language. Styles are defined and then applied to blocks of text (or even single characters) by referring to the definition in the available style range. An example of a simple form of style sheet could be: P {color: #800000}. This would cause any text that is classified as a paragraph to be rendered using a dark red color.
Style definitions can be applied to documents and their elements in one of four ways, i.e., using the <LINK> attribute to point to an external style sheet, using the <STYLE> element within the <HEAD> of a document, using the @import mechanism (similar to the <LINK> method above, this allows the importing of external style sheets.), and using the STYLE attribute in an element. This last way is allowed for any elements allowed within the <BODY> of a HTML document. There are various methods for denoting the style declaration and all use separate methods within HTML to determine the style to be used.
The process 100 generates (104) a profile representative of at least the format and style of the specific web content. More specifically, the profile represents the style, colors, background, background images, table characteristics, fonts, margins, and other visual characteristics that are specified in the specific web content. The profile may represent an automatically derivable description of the specific web content. For example, determining the writing style of the content and making selections in response to the determination, e.g., formal and informal presentations of embedded news stories. Further, the language in which the content is written may be determined, and subsequently selecting or translating the component into that language, or decorating it with culturally appropriate symbols may be included. Content refers to contextual material of the specific web content including topical, geographical, temporal and semantic. The profile includes style, colors, background, background images, table characteristics, fonts, margins, and other visual characteristics associated with the specific web content. The profile is stored and maintained in database 54 along with an identifier that associates the profile with the specific web content.
The process applies (106) the profile to the delivery of a component, such as syndicated services and/or syndicated content, contained in the database 54 and delivers (108) the component. Specifically, the component is modified in accordance with the profile so as to seamlessly “fit” in the specific web content as if it originated from a single source.
The component may include an embedded element and/or a standalone element. Embedded elements are in-situ syndicated textual or multimedia material shown within the context of the specified web content. Utilizing one or more methods, such as script insertion, frames, interior frames (I-frames, layers, applets, active-x controls, plugins, and so forth) may accomplish this. Standalone elements are syndicated textual or multimedia material shown within their own contexts in a browser window, dialog window, pop-up window, and so forth.
Processes 70 and 100 are not limited to use with the hardware/software configuration of
Processes 70 and 100 may be implemented using one or more computer programs executing on programmable computers that each includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and one or more output devices.
Each such program may be implemented in a high level procedural or object-oriented programming language to communicate with a computer system. Also, the programs can be implemented in assembly or machine language. The language may be a compiled or an interpreted language.
Each computer program may be stored on a storage medium or device (e.g., CD-ROM, hard disk, or magnetic diskette) that is readable by a general or special purpose programmable computer for configuring and operating the computer when the storage medium or device is read by the computer to perform processes 70 and 100.
Processes 70 and 100 may also be implemented as a computer-readable storage medium, configured with a computer program, where, upon execution, instructions in the computer program cause the computer to operate in accordance with processes 70 and 100.
The invention is not limited to the order of processing shown in
Other implementations are within the scope of the following claims.
For example, process 100 may include dynamic adaptation. Specifically, each time a component is requested by the first server, the specific web content contained in the database 42 is checked for any updates to determine if the profile associated with the specific web content is still valid. This check is accomplished in one of several ways, such as expiry 20 information, last modified dates, CRCs, MD5s, and so forth. Thus, a newly generated profile is used in real-time each time the component is requested.
In another example, process 100 stores a baseline profile and a number of deltas. The deltas contain information captured when the specific web content or the database 42 changes in any significant manner. Each delta adds more overall information about the specific web content and the first server.
Number | Name | Date | Kind |
---|---|---|---|
5530852 | Meske et al. | Jun 1996 | A |
5778363 | Light | Jul 1998 | A |
5930788 | Wical | Jul 1999 | A |
6009441 | Mathieu et al. | Dec 1999 | A |
6085220 | Courts et al. | Jul 2000 | A |
6101472 | Giangarra et al. | Aug 2000 | A |
6144991 | England | Nov 2000 | A |
6178432 | Cook et al. | Jan 2001 | B1 |
6279013 | LaMarca et al. | Aug 2001 | B1 |
6304864 | Liddy et al. | Oct 2001 | B1 |
6330592 | Makuch et al. | Dec 2001 | B1 |
6389412 | Light | May 2002 | B1 |
6470349 | Heninger et al. | Oct 2002 | B1 |
6510558 | Iinuma et al. | Jan 2003 | B1 |
6606525 | Muthuswamy et al. | Aug 2003 | B1 |
6622168 | Datta | Sep 2003 | B1 |
6625803 | Massena et al. | Sep 2003 | B1 |
6636863 | Friesen | Oct 2003 | B1 |
6691106 | Sathyanarayan | Feb 2004 | B1 |
6718313 | Lent et al. | Apr 2004 | B1 |
6769025 | Alles et al. | Jul 2004 | B1 |
6886013 | Beranek | Apr 2005 | B1 |
7127670 | Bendik | Oct 2006 | B2 |
20010020956 | Moir | Sep 2001 | A1 |
20010021914 | Jacobi et al. | Sep 2001 | A1 |
20010043364 | Messner et al. | Nov 2001 | A1 |
20010049620 | Blasko | Dec 2001 | A1 |
20010054085 | Kurganov | Dec 2001 | A1 |
20020002563 | Bendik | Jan 2002 | A1 |
20020010725 | Mo | Jan 2002 | A1 |
20020010753 | Matsuoka et al. | Jan 2002 | A1 |
20020032701 | Gao et al. | Mar 2002 | A1 |
20020059342 | Gupta et al. | May 2002 | A1 |
20020073125 | Bier | Jun 2002 | A1 |
20020083123 | Freedman et al. | Jun 2002 | A1 |
20020091725 | Skok | Jul 2002 | A1 |
20020107894 | Kent et al. | Aug 2002 | A1 |
20020111972 | Lynch et al. | Aug 2002 | A1 |
20020123334 | Borger et al. | Sep 2002 | A1 |
20020138331 | Hosea et al. | Sep 2002 | A1 |
20020138513 | Korotney et al. | Sep 2002 | A1 |
20020161803 | Shelton | Oct 2002 | A1 |
20020165881 | Shelton | Nov 2002 | A1 |
20030017440 | Bergey et al. | Jan 2003 | A1 |
20030041143 | Ronald et al. | Feb 2003 | A1 |
20030050995 | Mateos | Mar 2003 | A1 |
20030091229 | Edge et al. | May 2003 | A1 |
20030110449 | Wolfe | Jun 2003 | A1 |
20030149580 | Moores et al. | Aug 2003 | A1 |
20030196169 | Wittkotter et al. | Oct 2003 | A1 |
20030204610 | Howard et al. | Oct 2003 | A1 |
20050050460 | Bedingfield, Sr. | Mar 2005 | A1 |
20060020673 | Sorge et al. | Jan 2006 | A1 |
Number | Date | Country | |
---|---|---|---|
20020129063 A1 | Sep 2002 | US |