RRAS - a Reminder-based Ad system

The RRAS system is a real-time reminder-based ad system which allows a web server to send, and track advertising messages based on our reminder xml schema directly to a user's desktop (patent pending). The RRAS system uses the same tracking mechanism as the RCAS system; and is essentially an extension to RCAS.

RRAS - a Real-time Reminder-based Ad system

The RRAS system is developed on top of an HTTP server, which is able to send PUT requests, to a user's desktop. The user's desktop must be running an HTTP server and/or plugin, which can send and receive the reminder-based ad messages. The sending server, always expect confirmation messages, akin to the old Mail Transfer Agent (MTA) receipt confirmation exchanges, every time a link that is part of the message is clicked or accessed by the user; allowing the originating server to track every query made to desktop or internet accessible content.

The origin and content of every query is tracked, based on keywords used and content requested. The information associated with each query, which is used by RRAS, is taken from the web server, which may or not be a content-enabled one. If the web server does not provide content information; then, RRAS generates its own, based on the data provided.

RRAS uses the display attributes of the message/reminder, to summarize visually the content of the message, in this case the advertising message. When a user clicks on the visual summary, a confirmation is sent to the originating server; and the full content of the ad is then presented to the user. The full content can be a link to the sponsor's website, or embedded script, html, or animation file, such as flash or silverlight. A confirmation message is also sent to the originating server, if a link in an embedded message is clicked/accessed by the user.

A plugin which understands our reminder advertising schema
(patent pending), must be running on the user's desktop; it must also be able to send HTTP click confirmations responses to the originating server. The plugin may perform a SALT or SSL handshake with the originating server, every time a user turns-on their computer and their internet access. The handshake is required by RRAS so that advertising messages can be sent to the user's desktop. The RRAS system also regularly scans the internet/network, to initiate handshakes with subscribers who may be online. The handshake may contain additional information regarding which ports to access on the server, for downloads.

An adjunct to this patent is the use of our HTTP SALT protocol to both secure the message exchanges, and to identify the recipient of the advertising messages by RRAS. The plugin can perform the handshake through a UDP or TCP port. The server can broadcast the advertising messages to a reserved audience, which is identified by internet network masking or subdomain addressing, or by a list of subscribers or users, identified as clubs (patent pending).

An second adjunct to this patent is the use of display attributes which are used to present a visual summary of the content of the transmitted message/reminder to the user. The display attributes can be a link to an animation file, a set or sequence of icons, animated or not, seen as pictograms.

A third adjunct to this patent is the option of using another authentication protocol, instead of the SALT protocol, when sending the advertising messages. The most obvious alternatives to our SALT protocol are the OpenID protocol or HTTP Cookies and Authorization headers.

A fourth adjunct to this patent is the requirement of having a dynamic naming service alias a fully qualified domain name (FQDN) to your host computer, as it is connected to the Internet, if a static IP address is not provided.

A fifth adjunct to this patent is the derivation of  an email schema from the message schema, with the same features and attributes of the advertising schema; except, updates are seen as attachments, so that simple emails can be seen as announcements of the day, advertising messages (e.g. flyers), etc.. Club related emails can simply be typed as subscriber|emai.

Patent Pending