Importance

Loading Importance Indicators...

Abstract

A central system controller prepares a list of ads to be played, this list being prepared from an 'ad played' database maintained at the system controller. This 'to be played list' includes ad identity and an ad Internet address. This 'to be played list' is first computed and thereafter lodged in the central system controller at peripheral websevers for distribution to browsers. When a browser hits a client website, it is diverted to the system controller at one of the peripheral webservers. The system controller forwards a non-scrolling ad frame set, the 'to be played list' of ads to be shown within the non-scrolling frame set, a unique cookie identifier having intervals for recording the identity of ads played together with the day and time of play and processing logic. Once the 'to be played list' is installed at the browser, the processing logic compares the 'to be played list' at the browser against the record of ads played in the browser cookie. Ads are then played in sequence from the browser in accordance with the 'to be played list' with already played ads being eliminated from play by the browser. As each ad is played and timed out, report is made to the system controller at the peripheral webservers. The peripheral webservers batch and periodically forward to the central processor of the system controller the record of ads played. This enables periodic computation and distribution of updated 'to be played lists' as well as periodic billing for ads displayed.

Loading the Abstract Image...

First Claim