Dynamically Providing Relevant Browser Content

• US 20090313536A1
• Filed: 06/11/2008
• Published: 12/17/2009
• Est. Priority Date: 06/11/2008
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Yariv, Eran, Elyada, Oded, Ramote, Omer, Varshavsky, Roy, Karidi, Ron, Sitton, Daniel, Amit, Noga
• Application Number:
  US12/136,889
• Publication Number:
  US 20090313536A1
• Time in Patent Office: Days
• US Class Current: 715/209
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation

Abstract

A requested content page is provided with additional relevant content that is dynamically generated. A page originally requested by a browser application is generated and examined to determine key words, address information, and other information for which relevant content may be retrieved. The other information may not be part of the original page content, but it can be the relation between the content page and other pages. The relevant content is determined based on the results of the content page examination. After retrieving the relevant content, the retrieved content is embedded into the requested content page and provided to the requesting user. The retrieved relevant content may be provided with the requested content page in a designated portion within the requested content page, near related content in the page, and/or displayed in response to user input as a pop-up window or in a preview pane. Relevant content can be determined, retrieved and embedded in a content page by a relevant content engine implemented as a server application, client application or browser application plug-in.

Claims

1. A method for providing a content page, comprising:

receiving a request for content page data;

generating content page information in response to the request;

parsing the received content page information to generate parse results;

retrieving relevant content associated with selected portions of the parse results;

embedding data associated with the relevant content in the received content page information; and

providing the content page with the embedded relevant content data to a client device.

2. The method of claim 1, wherein the request for the content page data is received from a remote client by a server

3. The method of claim 1, wherein the received content page information is parsed for one or more keywords.

4. The method of claim 1, wherein the received content page information is parsed for at least one of stock symbols, address information or music files.

5. The method of claim 1, wherein said step of retrieving relevant content includes:

retrieving relevant content from a remote server by a content engine residing on an application server.

6. The method of claim 1, wherein said step of embedding data includes:

embedding the retrieved relevant content in a position in the content page designated for relevant content.

7. The method of claim 1, wherein said step of embedding data includes:

embedding the retrieved relevant content in a position in the content page near content related to the relevant content.

8. The method of claim 7, wherein relevant content comprising a map image is positioned in the content page near related content comprising an address, the map image illustrating a location for the address.

9. The method of claim 1, wherein said step of embedding data includes:

embedding the retrieved relevant content in the content page code such that the relevant content is provided in response to receiving mouse-over input by a browser application providing the content page.

10. One or more processor readable storage devices having processor readable code embodied on said processor readable storage devices, said processor readable code for programming one or more processors to perform a method comprising:

accessing a content page provided by a first server over a network;

parsing the accessed content page to detect keyword information;

retrieving content relevant to the detected keyword information, the relevant content retrieved from a second server, the first server and second server provided by different application providers;

embedding the retrieved content in the accessed content page; and

providing the content page with the embedded retrieved keyword content.

11. The one or more processor readable storage devices of claim 10, wherein said step of accessing includes:

requesting the content page from the first server by a browser application on a client device.

12. The one or more processor readable storage devices of claim 10, wherein said step of parsing the accessed content page includes:

parsing the content page to detect at least one of address data and stock symbols.

13. The one or more processor readable storage devices of claim 10, wherein said step of retrieving content includes:

retrieving content from a remote server by a client application on the client device.

14. The one or more processor readable storage devices of claim 10, wherein said step of retrieving content includes:

retrieving content from a remote server by a browser application plug-in on the client device.

15. The one or more processor readable storage devices of claim 10, wherein said step of embedding includes:

embedding the retrieved relevant content in the content page to be displayed automatically by a browser application.

16. The one or more processor readable storage devices of claim 10, wherein said step of embedding includes:

embedding the retrieved relevant content in the content page to be displayed in response to receiving user input into the content page.

17. A system for providing a content page, comprising:

a relevant content engine,

the relevant content engine accessing a network browser content page, parsing the content page, retrieving content relevant to the content page and embedding the retrieved relevant content in the content page; and

one or more relevant content servers,

the one or more relevant content servers providing relevant content in response to a request received from the relevant content engine, each of the one or more relevant content servers located remote from the relevant content engine.

18. The system of claim 17, wherein said relevant content engine is implemented as an application on an application server, the application server processing a request for the content page from a client device.

19. The system of claim 17, wherein said relevant content engine is implemented as an client application on a client device, the client including a browser application which requests the content page from a remote server.

20. The system of claim 17, wherein said relevant content engine is implemented as an network browser plug-in on a client device, the plug-in communicating with a browser application which requests the content page from a remote server.