Technique for implementing browser-initiated user-transparent network-distributed advertising and for interstitially displaying an advertisement, so distributed, through a web browser in response to a user click-stream

• US 7,155,663 B2
• Filed: 05/31/2002
• Issued: 12/26/2006
• Est. Priority Date: 05/15/1998
• Status: Expired due to Term

• Current Assignee: Andreas Acquisitions, LLC
• Original Assignee: Unicast Communications Corporation (Extreme Reach, Inc.)
• Inventors: Lee, Wei-Yeh, Landsman, Rick W.
• Primary Examiner(s): BASHORE, WILLIAM L
• Application Number:
  US10/162,625
• Publication Number:
  US 20030005000A1
• Time in Patent Office: 1,670 Days
• Field of Search: 715/500, 715/500.1, 715/501.1, 709/219, 705 1- 19, 705/27
• US Class Current: 715/200
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0241 Advertisements
• CPC Class Codes: G06Q 30/0247 Calculate past, present or future revenues
• CPC Class Codes: G06Q 30/0251 Targeted advertisements
• CPC Class Codes: G06Q 30/0255 based on user history
• CPC Class Codes: G06Q 30/0262 during computer stand-by mode
• CPC Class Codes: G06Q 30/0268 at point-of-sale [POS]
• CPC Class Codes: G06Q 30/0273 Determination of fees for advertising
• CPC Class Codes: G06Q 30/0277 Online advertisement
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation

Abstract

A technique for implementing in a networked client-server environment, e.g., the Internet, network-distributed advertising in which advertisements are downloaded, from an advertising server to a browser executing at a client computer, in a manner transparent to a user situated at the browser, and subsequently displayed, by that browser and on an interstitial basis, in response to a click-stream generated by the user to move from one web page to the next. Specifically, an HTML advertising tag is embedded into a referring web page. This tag contains two components. One component effectively downloads, from an distribution web server and to an extent necessary, and then persistently instantiates an agent at the client browser. This agent “politely” and transparently downloads advertising files (media and where necessary player files), originating from an ad management system residing on a third-party advertising web server, for a given advertisement into browser cache and subsequently plays those media files through the browser on an interstitial basis and in response to a user click-stream. The other component is a reference, in terms of a web address, of the advertising management system. This latter reference totally “decouples” advertising content from a web page such that a web page, rather than embedding actual advertising content within the page itself, merely includes an advertising tag that refers, via a URL, to a specific ad management system rather than to a particular advertisement or its content. The ad management system selects the given advertisement that is to be downloaded, rather than having that selection or its content being embedded in the web content page.

Claims

1. Apparatus for use in rendering an information object in response to a first web page containing an embedded code, the apparatus comprising:

a processor;

a memory connected to the processor and storing both computer executable instructions and the first web page, the first web page having a plurality of computer readable instructions representing page content and the embedded code; and

an output device operative in conjunction with the processor;

wherein the processor, in response to the executable instructions and as a result of executing the code through a web browser, downloads an agent, from a first server, into the memory and subsequently executes the agent under control of the browser, wherein the agent, once executing;

downloads, from a second server and while the computer renders the first web page to a user through the output device, at least one file which is to be subsequently employed, by the processor, to render an information object, the information object being distinct from the first web page and selected by the second server;

monitors a click-stream produced by the user to detect a user navigation event signifying a user action to transition from the first web page to a next successive web page and which signifies a start of a next interstitial interval; and

in response to the user navigation event, processes the one file so as to render the information object through the output device to the user during the interval; and

wherein neither the code nor the first web page references the information object or said one file, specifies a location of the object itself or said one file or contains any content from the object or said one file such that use of the code eliminates a need to include content for the information object or said one file or an address of the object or said one file within the first web page, when the first web page is stored or rendered, thereby substantially decoupling the object and said one file from the first web page itself.

2. The apparatus in claim 1 wherein the information object comprises a web advertisement, the code comprises advertising code and the one file comprises an advertisement file.

3. The apparatus in claim 2 wherein the user navigation event comprises an affirmative action taken by the user, through the browser, to navigate from the first web page to the next successive web page, wherein the action comprises a mouse click, a key depression or a user-invoked state change in a stored history of web pages previously visited by the user.

4. The apparatus in claim 3 wherein the advertisement file comprises an Ad Descriptor file or at least one advertising file specified in the Ad Descriptor file, the advertising file being either a media file or a player file.

5. The apparatus in claim 4 wherein the processor, in response to execution of the agent, overrides default life cycle methods defined in the browser with corresponding substitute methods such that the agent persistently remains in browser storage as the browser transitions across successive web pages and different web sites.

6. The apparatus in claim 5 wherein the life cycle methods comprise at least one of start, run, stop, initialize and destroy methods.

7. The apparatus in claim 6 wherein the agent comprises a Transition Sensor applet and an Ad Controller applet, and the processor, during execution of the Transition Sensor:

instantiates and starts execution of the Ad Controller applet; and

monitors the click-stream so as to detect the user-initiated event such that the processor;

instructs the Ad Controller applet to download the Ad Descriptor file for the web advertisement from the second server into the browser storage on the computer; and

in response to an occurrence of the event, instructs the Ad Controller applet to cease any download of a further advertisement file specified in the Ad Descriptor file, to the extent any downloading of said further advertisement file is then occurring, and initiates processing through the browser, of files for an advertisement that has been previously downloaded and is currently ready to be rendered so as to render the previously downloaded advertisement during the next interstitial interval to the user.

8. The apparatus in claim 7 wherein the processor in response to executing the advertising code:

determines, through the agent, whether a new version of either the Transition Sensor applet or the Ad Controller applet then resides on a distribution server relative to a corresponding version, if any, of the Transition Sensor and Ad Controller applets, respectively, then residing in the browser storage; and

if said new version exists on the distribution server, downloads the new version from the distribution server into the browser storage and executes the new version in lieu of the corresponding version.

9. The apparatus in claim 8 wherein the Ad Controller applet comprises a play queue, wherein, the processor during execution of the Ad Controller applet:

once all the advertising files specified in an associated Ad Descriptor file for a corresponding advertisement reside in the browser storage on the computer, inserts the associated Ad Descriptor file into an end of the play queue; and

in response to the user navigation event and during the ensuing interstitial interval, processes advertising files specified in a specific Ad Descriptor file then situated at a head of the play queue so as to render, through the output device, an advertisement, corresponding to the specific Ad Descriptor file, to the user.

10. The apparatus in claim 9 wherein the agent, in response to the occurrence of the user navigation event, generates a stop event which, when processed by the agent, suspends the downloading of further advertisement files and initiates processing of files specified in the Ad Descriptor file, then situated at the head of the play queue, so as to render the web advertisement associated therewith during the ensuing interstitial interval.

11. The apparatus in claim 10 wherein the Transition Sensor applet monitors user click stream so as to detect the user navigation event and, in response thereto, produce the stop event, and wherein Ad Controller applet processes the stop event to suspend said downloading of further advertisement files and to render the advertisement associated with the Ad Descriptor file then situated at the head of the play queue.

12. The apparatus in claim 11 wherein the output device is a display.

13. The apparatus in claim 11 wherein the first and second servers are the distribution server and an advertising file server, respectively.

14. The apparatus in claim 13 wherein the advertising code further comprises a component specifying the advertising file server.

15. The apparatus in claim 14 wherein the processor, during execution of the Ad Controller applet and in response to the component contained in the code, downloads the Ad Descriptor file originating from the advertising file server specified in the second component.

16. The apparatus in claim 9 wherein, if the Ad Controller applet is not executing at the occurrence of the user navigation event, the processor, in response to the stored instructions, processes the one advertisement file, so as to render the web advertisement, only after both the Ad Controller applet has started execution and a next successive user navigation event has occurred.

17. The apparatus in claim 9 wherein the output device is a display.

18. The apparatus in claim 9 wherein the first and second servers are the distribution server and an advertising file server, respectively.

19. The apparatus in claim 18 wherein the advertising code further comprises a component specifying the advertising file server.

20. The apparatus in claim 19 wherein the processor, during execution of the Ad Controller applet and in response to the second component contained in the tag, downloads the Ad Descriptor file originating from the advertising file server specified in the second component.

21. The apparatus in claim 4 wherein the Ad Descriptor file comprises a manifest of names of a plurality of predefined advertising files and associated configuration information necessary to properly play the downloaded advertisement through the browser.

22. The apparatus in claim 21 wherein the Ad Descriptor file comprises a list having:

a name of each player and media file that constitutes the downloaded advertisement, a corresponding network address at which said each file can be accessed, configuration information for at least one of the player files for properly configuring the corresponding player to render an associated media file.

23. The apparatus in claim 3 wherein the advertising code comprises an advertising tag and the processor, in response to execution of the tag:

dynamically writes a plurality of predefined applet tags that collectively implement a script into the first web page; and

downloads, in response to subsequent execution of the script, the agent from the first server into the memory and thereafter instantiates and executes the agent.

24. The apparatus in claim 23 wherein the advertisement file comprises an Ad Descriptor file or at least one advertising file specified in the Ad Descriptor file, the advertising file being either a media file or a player file.

25. The apparatus in claim 23 wherein the processor, in response to execution of the agent, overrides default life cycle methods defined in the browser with corresponding substitute methods such that the agent persistently remains in browser storage as the browser transitions across successive web pages and different web sites.

26. The apparatus in claim 25 wherein the life cycle methods comprise at least one of start, run, stop, initialize and destroy methods.

27. The apparatus in claim 26 wherein the agent comprises a Transition Sensor applet and an Ad Controller applet, and the processor, during execution of the Transition Sensor:

instantiates and starts execution of the Ad Controller applet; and

monitors the click-stream so as to detect the user-initiated event such that the processor;

instructs the Ad Controller applet to download the Ad Descriptor file for the web advertisement from the second server into the browser storage on the computer; and

in response to an occurrence of the event, instructs the Ad Controller applet to cease any download of a further advertisement file specified in the Ad Descriptor file, to the extent any downloading of said further advertisement file is then occurring, and initiates processing through the browser, of files for an advertisement that has been previously downloaded and is currently ready to be rendered so as to render the previously downloaded advertisement during the next interstitial interval to the user.

28. The apparatus in claim 27 wherein the processor in response to executing the tag:

determines, through the agent, whether a new version of either the Transition Sensor applet or the Ad Controller applet then resides on a distribution server relative to a corresponding version, if any, of the Transition Sensor and Ad Controller applets, respectively, then residing in the browser storage; and

if said new version exists on the distribution server, downloads the new version from the distribution server into the browser storage and executes the new version in lieu of the corresponding version.

29. The apparatus in claim 28 wherein the Ad Controller applet comprises a play queue, wherein, the processor during execution of the Ad Controller applet:

once all the advertising files specified in an associated Ad Descriptor file for a corresponding advertisement reside in the browser storage on the computer, inserts the associated Ad Descriptor file into an end of the play queue; and

in response to the user navigation event and during the ensuing interstitial interval, processes advertising files specified in a specific Ad Descriptor file then situated at a head of the play queue so as to render, through the output device, an advertisement, corresponding to the specific Ad Descriptor file, to the user.

30. The apparatus in claim 29 wherein the agent, in response to the occurrence of the user navigation event, generates a stop event which, when processed by the agent, suspends the downloading of further advertisement files and initiates processing of files specified in the Ad Descriptor file, then situated at the head of the play queue, so as to render the web advertisement associated therewith during the ensuing interstitial interval.

31. The apparatus in claim 30 wherein the Transition Sensor applet monitors user click stream so as to detect the user navigation event and, in response thereto, produce the stop event, and wherein Ad Controller applet processes the stop event to suspend said downloading of further advertisement files and to render the advertisement associated with the Ad Descriptor file then situated at the head of the play queue.

32. The apparatus in claim 31 wherein the output device is a display.

33. The apparatus in claim 31 wherein the first and second servers are the distribution server and an advertising file server, respectively.

34. The apparatus in claim 27 wherein, if the Ad Controller applet is not executing at the occurrence of the user navigation event, the processor, in response to the stored instructions, processes the one advertisement file, so as to render the web advertisement, only after both the Ad Controller applet has started execution and a next successive user navigation event has occurred.

35. The apparatus in claim 27 wherein the output device is a display.

36. The apparatus in claim 27 wherein the first and second servers are a distribution server and an advertising file server, respectively.

37. The apparatus in claim 23 wherein the Ad Descriptor file comprises a manifest of names of a plurality of predefined advertising files and associated configuration information necessary to properly play the downloaded advertisement through the browser.

38. The apparatus in claim 37 wherein the Ad Descriptor file comprises a list having:

a name of each player and media file that constitutes the downloaded advertisement, a corresponding network address at which said each file can be accessed, configuration information for at least one of the player files for properly configuring the corresponding player to render an associated media file.

39. A method for use in rendering, through a computer, an information object in response to a first web page containing embedded code, the computer having a processor, a memory connected to the processor and storing both computer executable instructions and the first web page, the first web page having a plurality of computer readable instructions representing page content and the embedded code, and an output device operative in conjunction with the processor, wherein the method comprises the steps, performed by the processor and in response to the executable instructions and as a result of executing the code through a web browser, of:

downloading an agent, from a first server, into the memory and subsequently executing the agent under control of the browser, wherein the method further comprises the steps, performed by the agent, of;

downloading, from a second server and while the computer renders the first web page to a user through the output device, at least one file which is to be subsequently employed, by the processor, to render an information object, the information object being distinct from the first web page and selected by the second server;

monitoring a click-stream produced by the user to detect a user navigation event signifying a user action to transition from the first web page to a next successive web page and which signifies a start of a next interstitial interval; and

in response to the user navigation event, processing the one file so as to render the information object through the output device to the user during the interval; and

wherein neither the code nor the first web page references the information object or said one file, specifies a location of the object itself or said one file or contains any content from the object or said one file such that use of the code eliminates a need to include content for the information object or said one file or an address of the object or said one file within the first web page, when the first web page is stored or rendered, thereby substantially decoupling the object and said one file from the first web page itself.

40. The method in claim 39 wherein the information object comprises a web advertisement, the code comprises advertising code and the one file comprises an advertisement file.

41. The method in claim 40 wherein the user navigation event comprises an affirmative action taken by the user, through the browser, to navigate from the first web page to the next successive web page, wherein the action comprises a mouse click, a key depression or a user-invoked state change in a stored history of web pages previously visited by the user.

42. The method in claim 41 wherein the advertisement file comprises an Ad Descriptor file or at least one advertising file specified in the Ad Descriptor file, the advertising file being either a media file or a player file.

43. The method in claim 42 further comprising the step, performed by the processor in response to executing the agent, of over-riding default life cycle methods defined in the browser with corresponding substitute methods such that the agent persistently remains in browser storage as the browser transitions across successive web pages and different web sites.

44. The method in claim 43 wherein the life cycle methods comprise at least one of start, run, stop, initialize and destroy methods.

45. The method in claim 44 wherein the agent comprises a Transition Sensor applet and an Ad Controller applet, and the method comprises the steps, performed by the processor during execution of the Transition Sensor, of:

instantiating and starting execution of the Ad Controller applet; and

monitoring the click-stream so as to detect the user-initiated event, the monitoring step comprising the steps of;

instructing the Ad Controller applet to download the Ad Descriptor file for the web advertisement from the second server into the browser storage on the computer; and

in response to an occurrence of the event, instructing the Ad Controller applet to cease any download of a further advertisement file specified in the Ad Descriptor file, to the extent any downloading of said further advertisement file is then occurring, and initiating processing through the browser, of files for an advertisement that has been previously downloaded and is currently ready to be rendered so as to render the previously downloaded advertisement during the next interstitial interval to the user.

46. The method in claim 45 further comprising the steps, performed in response to executing the advertising code, of:

determining, through the agent, whether a new version of either the Transition Sensor applet or the Ad Controller applet then resides on a distribution server relative to a corresponding version, if any, of a Transition Sensor and Ad Controller applets, respectively, then residing in the browser storage; and

if said new version exists on the distribution server, downloading the new version from the distribution server into the browser storage and executing the new version in lieu of the corresponding version.

47. The method in claim 46 wherein the Ad Controller applet comprises a play queue, wherein the method comprises the steps performed by the processor during execution of the Ad Controller applet, of:

once all the advertising files specified in an associated Ad Descriptor file for a corresponding advertisement reside in the browser storage on the computer, inserting the associated Ad Descriptor file into an end of the play queue; and

in response to the user navigation event and during the ensuing interstitial interval, processing advertising files specified in a specific Ad Descriptor file then situated at a head of the play queue so as to render, through the output device, an advertisement, corresponding to the specific Ad Descriptor file, to the user.

48. The method in claim 47 further comprising the step, performed by the agent, in response to the occurrence of the user navigation event, of generating a stop event which, when processed by the agent, suspends the downloading of further advertisement files and initiates processing of files specified in the Ad Descriptor file, then situated at the head of the play queue, so as to render the web advertisement associated therewith during the ensuing interstitial interval.

49. The method in claim 48 further comprising the step, performed by the Transition Sensor applet, of monitoring user click stream so as to detect the user navigation event and, in response thereto, produce the stop event, and processing, by the Ad Controller applet, the stop event to suspend said downloading of further advertisement files and to render the advertisement associated with the Ad Descriptor file then situated at the head of the play queue.

50. The method in claim 49 wherein the first and second servers are the distribution server and an advertising file server, respectively.

51. The method in claim 50 wherein the advertising code further comprises a component specifying the advertising file server.

52. The method in claim 51 comprising the step performed by the processor, during execution of the Ad Controller applet and in response to the component contained in the code, of downloading the Ad Descriptor file originating from the advertising file server specified in the second component.

53. The method in claim 47 further comprising the step, performed, by the processor, of processing, in response to the stored instructions and if the Ad Controller applet is not executing at the occurrence of the user navigation event, the one advertisement file, so as to render the web advertisement, only after both the Ad Controller applet has started execution and a next successive user navigation event has occurred.

54. The method in claim 47 wherein the first and second servers are the distribution server and an advertising file server, respectively.

55. The method in claim 42 wherein the Ad Descriptor file comprises a manifest of names of a plurality of predefined advertising files and associated configuration information necessary to properly play the downloaded advertisement through the browser.

56. The method in claim 55 wherein the Ad Descriptor file comprises a list having:

a name of each player and media file that constitutes the downloaded advertisement, a corresponding network address at which said each file can be accessed, configuration information for at least one of the player files for properly configuring the corresponding player to render an associated media file.

57. The method in claim 41, wherein the advertising code comprises an advertising tag, further comprising the steps, performed by the processor, in response to execution of the tag, of:

dynamically writing a plurality of predefined applet tags that collectively implement a script into the first web page; and

downloading, in response to subsequent execution of the script, the agent from the first server into the memory and thereafter instantiates and executes the agent.

58. The method in claim 57 wherein the advertisement file comprises an Ad Descriptor file or at least one advertising file specified in the Ad Descriptor file, the advertising file being either a media file or a player file.

59. The method in claim 58 further comprising the step, performed by the processor, in response to the executing applet, of over-riding default life cycle methods defined in the browser with corresponding substitute methods such that the agent persistently remains in browser storage as the browser transitions across successive web pages and different web sites.

60. The method in claim 59 wherein the life cycle methods comprise at least one of start, run, stop, initialize and destroy methods.

61. The method in claim 60 wherein the agent comprises a Transition Sensor applet and an Ad Controller applet, and the method comprises the steps, performed by the processor, during execution of the Transition Sensor, of:

instantiating and starting execution of the Ad Controller applet; and

monitoring the click-stream so as to detect the user-initiated event such that the processor, wherein the monitoring step comprises the steps of;

instructing the Ad Controller applet to download the Ad Descriptor file for the web advertisement from the second server into the browser storage on the computer; and

in response to an occurrence of the event, instructing the Ad Controller applet to cease any download of a further advertisement file specified in the Ad Descriptor file, to the extent any downloading of said further advertisement file is then occurring, and initiating processing through the browser, of files for an advertisement that has been previously downloaded and is currently ready to be rendered so as to render the previously downloaded advertisement during the next interstitial interval to the user.

62. The method in claim 61 further comprising the steps, performed in the processor, in response to executing the tag, of:

determining, through the agent, whether a new version of either the Transition Sensor applet or the Ad Controller applet then resides on a distribution server relative to a corresponding version, if any, of the Transition Sensor and Ad Controller applets, respectively, then residing in the browser storage; and

if said new version exists on the distribution server, downloading the new version from the distribution server into the browser storage and executes the new version in lieu of the corresponding version.

63. The method in claim 62 wherein the Ad Controller applet comprises a play queue, wherein, the method comprises the steps, performed by the processor during execution of the Ad Controller applet, of:

once all the advertising files specified in an associated Ad Descriptor file for a corresponding advertisement reside in the browser storage on the computer, inserting the associated Ad Descriptor file into an end of the play queue; and

in response to the user navigation event and during the ensuing interstitial interval, processing advertising files specified in a specific Ad Descriptor file then situated at a head of the play queue so as to render, through the output device, an advertisement, corresponding to the specific Ad Descriptor file, to the user.

64. The method in claim 63 further comprising the step, performed by the agent, in response to the occurrence of the user navigation event, of generating a stop event which, when processed by the agent, suspends the downloading of further advertisement files and initiates processing of files specified in the Ad Descriptor file, then situated at the head of the play queue, so as to render the web advertisement associated therewith during the ensuing interstitial interval.

65. The method in claim 64 further comprising the step, performed by the Transition Sensor applet, of monitoring user click stream so as to detect the user navigation event and, in response thereto, produce the stop event, and the step of processing, by the Ad Controller applet, the stop event to suspend said downloading of further advertisement files and to render the advertisement associated with the Ad Descriptor file then situated at the head of the play queue.

66. The method in claim 65 wherein the first and second servers are the distribution server and an advertising file server, respectively.

67. The method in claim 61 further comprising the step performed, by the processor, of processing, in response to the stored instructions and if the Ad Controller applet is not executing at the occurrence of the user navigation event, the one advertisement file, so as to render the web advertisement, only after both the Ad Controller applet has started execution and a next successive user navigation event has occurred.

68. The method in claim 61 wherein the first and second servers are a distribution server and an advertising file server, respectively.

69. The method in claim 57 wherein the advertising tag further comprises first and second components, the first and second components specifying the distribution server and the advertising file server, respectively.

70. The method in claim 69 comprising the step performed by the processor, during execution of the Ad Controller applet and in response to the second component contained in the tag, of downloading the Ad Descriptor file originating from the advertising file server specified in the second component.

71. The method in claim 70 wherein the Ad Descriptor file comprises a manifest of names of a plurality of predefined advertising files and associated configuration information necessary to properly play the downloaded advertisement through the browser.

72. The method in claim 71 wherein the Ad Descriptor file comprises a list having:

a name of each player and media file that constitutes the downloaded advertisement, a corresponding network address at which said each file can be accessed, configuration information for at least one of the player files for properly configuring the corresponding player to render an associated media file.