Patent Grant
9785973
Field of the Invention
This invention relates generally to systems and methods associated with portable devices, and more particularly to systems and methods associated with portable devices to deliver target advertising:
Description of the Related Art
Currently general advertising on portable devices is delivered only as SMS or text messages. These messages can only contain plain text and are delivered to the SMS inbox provided by most portable devices. They go into the general inbox that contains all messages received by that device from any source. There is no ability to track which advertisements or coupons are read or deleted or, in fact, any confirmation that the user even looked in the SMS inbox.
Advertising is also delivered as part of streaming video (ie. TV) on some mobile devices, however it acts like current TV adverting, where it interrupts the content with the advertisement and there is no ability to target different ads to different demographics nor any way to interact with the advertising.
Accordingly, an object of the present invention is to provide improved methods for delivering advertising items to a client at the client's portable device.
Another object of the present invention is to provide improved methods for delivering coupons to a client's portable device.
Yet another object of the present invention is to provide improved methods for making coupon recommendations to a client using client demographic and client historical data.
A further object of the present invention is to provide improved methods for displaying layouts with advertising item data at a client's portable device.
Another object of the present invention is to provide improved methods for allowing customers to manage their advertising campaigns.
Yet another object of the present invention is to provide improved methods for downloading advertising items to a portable device of a client.
These and other objects of the present invention are achieved in a method for loading a layout with advertising item data. Layout header data is parsed. A layout item object is then built. Global layout variables are replaced with values. Local layout variables are replaced with data from content objects. Displayed data is then created.
In another embodiment of the present invention, a method is provided for allowing customers to manage their advertising campaigns. A client delivered advertising item is delivered relative to a product or service of a customer. A new demographic profile is created for client targeting. A new advertising campaign is created that links content deliverables and demographic profiles relative to the advertising item. The new advertising campaign is launched. The advertising campaign results are then viewed by the customer.
In another embodiment of the present invention, a method is provided of downloading advertising items from a host server to a portable device of a client. A client's device information, relative to the client's portable device, is received at the host server. A determination is made, from the client's device information, the model or version of the client's portable device. In response to the step of determining, a client ID is embedded in the client's portable device. Client software is delivered from the host server to the client's portable device. The client software is used for downloaded advertising items relative to a product or service from the host server to the client's portable device.
In one embodiment of the present invention, illustrated in
A client ID is sent to a host server. A downloaded advertising item is produced relative to a product or service from the host server, as illustrated in
The displayed advertising item includes at least one of, a list of merchants, special event data, a coupon, an ad, a contest, a loyalty card (
When the client first starts an application, a network connection with the host server begins in the background. This network connection reaches the host server both to upload and download data. All logged information is uploaded, including but not limited to each advertising item, such as a coupon, used, deleted and viewed by the client and how often. The amount of free space available on the client's portable device is also uploaded. Addition data can be attached including but not limited to the current GPS coordinates of the client's portable device. Client requests are uploaded. By way of illustration, and without limitation, these client request can include, requests to install the client on a different portable device, specifically requested advertising items, personal data entered, and the like. Advertising items can be requested by entering a short code, waving a Bluetooth enabled device over a transmitter, taking a picture of a code, such as a barcode or other machine readable picture, with the client's portable device's built in camera. This can then be translated into a code to be uploaded, received as an IR signal via an IR receiver or any other reasonable input method into the client's portable device.
As shown in
A portable device application is downloaded from the host computer and installed on the client's portable device. An application can be run by the client that is prompted for the client's personalized information. Such personal information can include, but it not limited to the client's, zip code, age, gender, address, contact information, preferences, and the like. One instance of how the initial flow can work can be see in
In producing the downloaded advertising item, data of the client's actions and the client's non-actions is processed at the server from previous client activity. The client's actions and non-actions for the advertising item are then updated and storing it at the host server. In response to the updating, the new advertising item is sent to the client.
During parsing, the host server can pre-format the advertising item for easier client use. By way of illustration, and without limitation, the host server can place the content to be delivered in a specific fixed order, delimited by a special character. The client can then easily iterate across this list, parsing and placing each element into an array in the same order. The client can use the same previous knowledge about the order to index into that array, to load any specific element. The data in the same form can be stored for later retrieval using the same method.
The data can be transmitted in an extremely compact form. By way of illustration, and without limitation, one method is to have a list of values, delimited by a special character, with each addition position representing a different element of data. By way of illustration, a coupon can be represented as follows:
In addition, a string of suitable length can be first compressed. Many other characters can also be a delimiter. Some delimiters could also be removed by fixed the length of ids, so that the first part above could be transmitted as “434101”. If the amount of data transmitted can not be as constrained, the XML given above can also be transmitted as is.
In a case where a string (for instance the small print string with type_id 6 above) is already on the client, instead of transmitting the string again, a code number can be transmitted representing the coupon for which the string already exists that should be used for this coupon.
Following parsing, the client tokenizes the advertising item, exams each of a header of a token to determine it's type, and then process according to type, see
The client's portable device sorts through the layout and replaces any variables in the layout with data from the content. Layout constants are adjusted based on specific settings of the client's portable device. The layout is then passed with the adjusted values to a controller of the portable device. The controller follows instructions in the layout, and the instructions then paint the data onto the screen of the client's portable device. Client input is accepted by the controller, and instructions or commands are applied in the layout to decided what to do next. The layout maps each possible client input to a command string. When the client receives the command, the client loads and parses that command string which can consist of one or more commands. Each command is executed in order, effecting either the current screen, flow to another screen, causing the storing of data or causing a network operation to occur. These steps are then repeated for each screen that the client sees at its portable device.
An iteration is made over all of the elements in the layout. The type of each layout element is determined, and specific parsing code is used to properly expand the layout data into the element later to be displayed. Variables or constants found in the layout are then replaced with data from the content of a configuration file of the portable device. Equations found to calculate final values of specific elements in the layout are then executed. Equations can consist of constant numerical values, variable specific to the content, constants specific to the client portable device or variable specific to the current state of the layout. The calculations produce a final numerical value that is used in the display of an object. Looping objects are duplicated based on the number of content objects that exist, each of a sub-loop element value being loaded from a specific sub-content object.
In response to client input to the portable device, the portable device loads an appropriate set of commands from the active layout and then executes those commands. A variety of commands can be utilized including but not limited to those that can, cause storage operation, network operations, screen operations flow control operations, and the like. One embodiment of a possible flow for loading, viewing and use of a coupon can be seen in
In one embodiment, the commands are executed by specific portable device phone threads. The threads can include but are not limited to, timer threads that cause a command to executed after a specific amount of time has passed, a network status thread, causing a command to be executed at various stages of network operation, a save storage status thread, the also causes a command to be executed at various stages of network operation, and other interrupt or restore threads.
In one embodiment, the host server functionality is broken down into several sections, including but not limited to, user management, advertising item distributor, campaign manager, client distribution, display management, and the like. The functionality needed can be divided other ways, this keeps the cleanest separation by enforcing the separation of clients from content, content management and other client details. This allows expansion or modification of one area while minimizing change in the others. In addition a controller exists for managing the network connection and sending incoming request data to the appropriate system, and appending its response to the set of responses due to be returned to the client. The controller is responsible for passing data between the separate sections, enforcing their separation by allowing communication via one known channel. In one embodiment of the present invention, Java is used with Java Servlet technology and a SQL database for data storage. The host server can be written in other languages, including but not limited to in C/C++, Perl or several other languages. In addition, all changes to the database can be stored with timestamps and old data need not be deleted. Therefore, when a field needs to be updated, a new entry is created with a timestamp indicating the new data value. The old value is marked as no longer valid. In this way, a complete history of all data changes can be examined.
A user management system (“UMS”) is provided and is responsible for registering and verifying clients, tracking client information, including but not limited to, client location via GPS, device and software version, personal details, connection information, billing information and billing records, and also provides for the administration of the same. One embodiment can be see in
In one embodiment, the UMS has two sets of access points, one used by the client and one used via a web browser to view and edit the client data. When contacted from the client, there are two major actions that can be performed. The first is the one time registration of a new client with the hose server. The client uploads to the UMS, the client's portable device identifier along with all information on model, type, free memory plus any data already gathered from the client, including but not limited to, gender, age or zip code. The UMS creates a new database entry for this client and assigns a unique client ID (uid). It also checks the client distribution system (“CDS”) to see if there is any data about who referred this client and if they are seeking some specific coupon, and stores this information. It then returns to the device this UID which is stored for future communication.
The second type of action is a standard communication from a device processed through the controller. The UMS is responsible for verifying that a valid was sent, storing any data uploaded by the client that is related to the client and returning any commands to ask the client to request additional client information. After checking that the UID exists in the database and is currently active and valid (not marked as locked) the UMS parses the data passed in for personal client information. If it finds keys for values it is interested in, such as date of birth, gender, age, income, zip code, address, billing or credit card information, reward card information or other personal information the UMS adds it to the client record and removes it from the incoming information flow.
The UMS looks for location based information, including but not limited to GPS coordinates, received data from Bluetooth transmitters, an ip address assigned from a wireless or wired internet connection, where the location can be calculated or other data. This is then converted into a street address and stored along with the an accuracy range (where the GPS coordinates might give a three meter range, a Bluetooth message a 3 foot range and an ip lookup might allow for a 1 mile radius or more) for access by other systems. In the case of the GSP coordinates, a map lookup will give a street address. For the Bluetooth transmitted the location of the transmitter must already be known. For wired connections, by tracking the path that packets take, the closest router or server can be determined and based on the location of that server and the delay packets take to get from the client to that server, a location can be calculated. Finally for wireless, the location of the base station that the client is connecting to can be looked up.
The UMS then checks to see if the current rules suggest that it ask the client for additional personal information. For instance if the client has used the system for two weeks, several times a day, the internal rule set might suggest that this is a good time to ask them for the client's zip code. In addition the client might have performed an action that required more data. For instance, the client may have attempted to buy a prepaid purchase code that could be loaded on the client's portable device and the system need to request their credit card number. If any of these are true, the system adds to its outgoing command list a request to the client to ask the client for this information and if the information is optional or not.
The UMS processes any incoming requests that require a billing or debit action such as directly buying something via an ad, prepaying for a series of items, buying a discount of some type or other action. The UMS charges the client's credit card, paypal account, bank account or internal balance if it is a dollar charge, or debits internal reward balances if the client is using a reward points gained for use of coupons, viewing ads, sharing ads or other reasons. The UMS records this and adds the note of the successfully or unsuccessfully charge to the outgoing data. All of the results are then returned to the controller for future actions.
The ad distribution system (“ADS”) is in charge of managing and delivering all item data to the client, including but not limited to ads, coupons, discount cards, prepaid charge numbers, and the like. The ADS receives the UID from the controller and the log data from the client. It first processes the log data, possessing records of advertising items deletions, such as coupon, from memory, marking those advertising items as removed from the client. Second it records views, uses and deletes of advertised items. All used and expired advertising items are marked to be deleted from the client memory and commands to do so are added to the outgoing command queue.
The ADS checks incoming data for any requests from the client for specific requested advertising items such as coupons, for instance if the client entered a code or otherwise indicated it wanted a coupon for a specific item or set of items either via the client or the web, or purchased items that need to be delivered, and adds them to the outgoing queue. The ADS checks if any advertising items have been explicitly sent to the client by another client and adds them to the queue in order.
Finally the ADS checks the database of available advertising items not yet delivered or planned to be delivered and selects a subset that best match the client's profile. This is a two step processes. First, available advertising items are filtered on client information such as age, gender, location (either zip code or location information processed by the client manager) and all advertising items whose distribution demographics requirements do not include the client are excluded. Advertising item data can include explicit restrictions or targets for one or more of these demographics that mean the advertising item would not be valid to be delivered under any normal circumstance to this client. Second, all remaining advertising items are given a score on a scale of 0.0-100.0 on how good a fit they are for the client. This includes filtering based on the same demographics as before except now using the suggested range information included in a coupon data.
By way of illustration, and without limitation, a coupon might only be allowed to be delivered to people age 18-45 of either gender but would prefer to reach age males 24-35 years old. In addition, the categories this coupon falls into are compared with ones this client has already used or not used (e.g., expired or deleted) and values are added or subtracted from the total score accordingly. The ADS then checks what other clients have used this coupon and if their coupon usage patterns and demographics match this client. For instance, if this coupon, perhaps one for diapers, was used by others who also used a coupon for baby formula, and this current client used the baby formula coupon, the score for this coupon for diapers would be increased. The greater the similarity between two clients, the more coupons in common they either used or did not use, the higher the score is increased for a coupon used by one but not by the other. This in turn is done for all clients who have a similarity, producing a final score.
Finally for any coupon that uses random values to provide rewards, a random number is chosen and the final values of the coupon are generated and a use code is assigned. In some cases this use code will be the same across all coupons, for example, a generic discount coupon that have the same UPC, and in other cases each have an a unique code. This allows one time use coupons, coupons that acted as cash or cash equivalents or any other situation where either individual tracking of coupon use at Point-of-Sale was critical or enforcing a one-time use policy was desired. The list of possible advertising items, such as coupons, is then sorted by score is returned to the controller.
In one embodiment of the present invention, the display manager has three primary functions. The three functions are, keeping track of what kind of list viewer the client has and how many advertising items it can handle, determining what display's and images are already installed on the client and how much free space is available for more and finally delivering any additional display's or images necessary to view new advertising items being delivered.
The display manager receives the UID and log information from client and advertising item information just generated by the ADS from the controller. The display manager first processes the log data, noting all deleted advertising items, images and display's and updates its understanding of how much space remains on the client for addition images, displays and ads. Second the display manger considers the current list view display installed on the client and if any new updated ones are available and, if so, adds them to the outgoing queue.
The display manager considers the list of advertising items from the ADS, first trimming the list by removing those with the lowest score until the list is of a size that the list display that is or will be installed can handle based on technical and HCl requirements. The display manger then proceeds through the list from highest score to lowest, determining what additional display's or images are necessary for that advertising item. It continues until the total size of the additional data hits the maximum for the client. The display manger then adds the display's images and advertising items selected to the outgoing queue.
The display manager examines the list of deleted advertising items and current advertising items and decides which images and display's are no longer necessary for the client and appends to the queue commands to the client to delete the unnecessary ones. This data is then returned to the controller. At this point the controller sends the complete set of commands and data to the client and closes the network connection.
In addition to client access some of the systems or parts of the host server systems are accessed via a web browser for clients to view or edit data or request. These include the CDS, UMS and the ADS.
The CDS is a system for making the client available for download. One method for distributing the client is via SMS where a SMS is sent with a download link to the client hardware. When the link is followed the client is installed. The CDS has two parts, one getting this SMS message to a client and second hosting the link to download the client, as illustrated in
In various embodiments of the present invention, an SMS is sent with the client download link in numerous methods. One is to request it via another client application already installed. The client enters a phone number of the portable device that should receive the SMS and the client transmits it to the CDS along with the UID of the requesting client for tracking purposes. The CDS logs this information and sends a SMS with a link to a servlet on the CDS server. The link has an unique ID embedded in it to track how many people use this link, if this SMS if forwarded to others.
The client download link can also be requested by sending a empty SMS message from the portable device in question to a specific number or short code which the CDS monitors and responds as above sending the SMS to the same device that sent the original SMS. Finally the phone number, email address or other contact information, and the like, can be entered in a web form. In addition the UID or phone number of the referred can be entered. Again an SMS, as described above, can be sent to the phone number in question. In all of these cases, a code could also be included either in the SMS message or on the website to indicate the client is signing up for a specific advertising item to start.
When a link in a SMS is followed, the CDS server receives the request, logs the ID in the download link and checks the header information passed with the browser request. Based on this information the CDS server decides which version of the application to deliver to the portable device in question, and sends a redirect request to the browser that points at the actual download URL for this version of the client.
When a new client connects for the first time, the CDS can be checked to see who or what should receive credit for getting the client to the host server. If it is another client, it might receive some kind of credit or special advertising item while someone paid to sign up clients could be tracked to see how well they do their job. Additionally, the host server is checked for any special code to indicate that certain advertising items or data should be delivered as soon as possible. One embodiment of this flow. A client can also access its personal information and profile via the web. The UMS provides both authentication for web site login and the ability to view and edit certain information.
If a client desires access via the web site, the client enters the client's portable device ID on the site. The site then sends to the client a random password for the first login. This, combined with the client's portable device ID, allows the client access to the UMS and all other web based systems. The UMS acts as a universal authentication system for all the web systems. The UMS is responsible for providing basic authentication tools, the ability to change passwords, recover a lost password, and the like. Additionally, the client can view its personal profile, edit demographic data, provide addition demographic data, view billing information, update billing data and perform other tasks on their personal data.
The ADS can be partly accessible online. The client can see what advertising items it currently has, search the advertising item database for addition advertising items it wants to have downloaded, view previously used advertising item data and access other data. Additionally, the ADS is responsible for allowing advertising items to be sent to a specific client. As discussed before from within a client the present invention provides that a specific advertising item can be sent to another client.
There are two ways the ADS can be used. The first is where one client to sends an advertising item or set of advertising items to another client. By entering some unique information about the client, for instance an email address, device id, phone number or the like, and selecting the subset of advertising items it wants to send, the ADS records the fact that these advertising items were specifically requested by others, giving them a high score the next time that client's client connects to receive new data. Second, a client can follow an outside link from a website, email or other source that contains an advertising item ID. This takes the them to this ADS website where, by entering their client ID, can alert the system that the next time the client connects it wants the advertising item indicated by the ID in the link it followed. This link can be provided several ways including, by another client or by a corporation advertising its advertising items via email, a website, flyer or in another manner.
Referring to
Client demographic and client historical data is loaded to the host server. Coupons are loaded from customers to the host server, as shown in
The client can be presented with a view of the coupons it currently has. At the same time, a network operation starts in the background, connecting to the host server and checking for new display's and new coupons. The host server can upload any information gained in response to client actions, including but not limited to, coupons viewed, used, deleted, the scrolling that took place, how often the application was started, exited, when a network conductivity failed, how long a client spent looking at any once screen, the interactions selected by the client, and any other client action performed on the display.
Selected coupon results are delivered from the scored coupons to a mobile device of the client in response to the scoring and sorting.
Demographic scoring criteria of the client are applied to the coupons. Customer request criteria can also be applied to the coupons. The application of the customer request criteria can be achieved by loading customer contract information to the host server. A coupon score is then increased or decreased based on the amount the customer pays for each coupon redemption an/or deliver. Coupon scores are then adjusted in response to preferences provided by customers to the host server. These preferences include, placement of coupons in a ranked ordering, preferred coupon display location on a screen of the mobile device, size and quantity of graphics used, fonts, client alerts, and the like.
In one embodiment, the step of applying client preferences includes utilizing client preferences to the scores of the coupons. In another embodiment, client category preferences are used to adjust coupon scores. Data sources can be used that are external to the host server to assist in the scoring of the coupons. By way of illustration, and without limitation, an external data source can be the purchasing history stored by a merchant on a specific client, historical and or geographic data on purchasing trends, real time data on current purchases, and the like. Customer data relative a client can be used to assist in scoring the customer's coupons for that client.
In one embodiment, the host server formats coupon data by compacts into a custom client language to provide for efficient parsing of data, as discussed above.
In another embodiment of the present invention, a method is provided for loading a layout with advertising item data. Layout header data is parsed. A layout item object is then built. Global layout variables are replaced with values. Each unresolved global variable in the created object containing data structures is replaced with a global value from a settings file.
Local layout variables are replaced with data from content objects. Each local variable in the created object containing data structures is located. A look up is perform for variables in an associated content object. Variables are replaced from created object that contain data structures with a value from the content object. Calculations associated with the variables are completed. At least a portion of the variable string representations are converted into another type of data.
Displayed data is then created. A determination is made for each layout item object to see if it is a loop layout item. The parsing layout header data includes, parsing out ID numbers that represent the layout. Global settings associated with the layout are also parsed out. In building a layout item object, layout component strings are parsed in a layout. Object containing data structures are created for each component string.
At least a portion of converted and non-converted data is painted onto the screen of a client's portable device. Each display set consists of a unique display ID and a set of one or more screens each with an ID unique within this set. In turn, each screen consists of a set of items that consist of but are not limited to, strings to display including font size, color and location; shape to draw, including which shape, location, color and fill if any; Image, including a unique image ID, location and if it is animated or not. In addition each item can be interactive or not and include one or more response's to an interaction, including reading or storing data, replacing itself with another item or other response. Also any value for a field can instead of a value have a id which can later be filled in by the coupon. Each screen can include a list of initial items to display. Instead of an absolute layout a relative layout can be used, either to other objects to the edge of the screen, such as by example using a layout manager, and the like.
By way of illustration, and without limitation, a simple display with one screen can be described as shown in Table 1 and a coupon driving it in Table 2.
It will be appreciated that the method set forth in Tables 1 and 2 is given by way of illustration, and other methods can also be utilized.
A display can be transmitted in a much more compact form, and in one embodiment, XML is used.
In other embodiments, the coupons are broken down by categories, allowing the client to search coupons, to sort by discount or expiration date, grouping by brand or store, showing only a logo with a discount to allow more to be shown, giving more detail with a second line of small text below each line above, showing only those that could be used within a certain radius of the clients current location, and the like.
From this illustrated screen, the client can either delete or select a coupon. If the coupon is deleted, it is removed from the list. If the client views the coupon, the client is taken to the detail view that is defined by the display information associated with that coupon.
The display view then controls what is seen and responds to client actions until the client indicates it is done viewing that coupon. At that point log information is updated, the list of coupons used is updated, and the client is returned to the list view. The display can support all advertising items. This includes any number of screens, each with any item or area on the screen being an interactor and allowing for animated images. The screen can support interactive coupons or ads including but not limited to, quiz's where right answers can lead to higher discounts, scratch off games, coupons with randomness, for example spinning a wheel to get a discount, or mini-games of any type with high scores leading to discounts, GPS based games where a client needs to reach certain coordinates to receive a discount, coupons or loyalty cards that require the client to reach the range, and the like.
In one embodiment of the present invention, a campaign management system (CMS) is provided for creating, managing and reviewing the results of advertising and advertising item campaigns, sales of discount cards or other digital items, sales of actual items and any other data that is presented to the client via the portable devices and the clients response to it. The CMS can be used by internal sales engineers or customers to detail what kind of campaign they want to run. In one embodiment, there are three parts to designing a campaign, the contents of the advertising item or ads, the target demographics and the number of advertising items or ads delivered and how often they should be delivered. Each of the parts can be combined in multiple ways to create a campaign. The results can be viewed either at this campaign level or for any piece. For instance, one can look across a series of campaigns to see how well a specific advertising item did.
The first step in the process of using CMS is creating an account for a customer. This is done once for each contract established and along with basic customer information it includes details on the length of the contract, negotiated base CPM (cost per thousand of advertising items delivered) and other details. Once done, accounts are also created for customers who need access to this system. Accounts type include but are not limited to, view results only, create campaigns and authorize campaigns with each later one including all the access of the previous account type.
The final task of the CMS is to provide real time results of a campaign status to clients. At any point a client can access the CMS and view how many advertising items have been delivered in relation to a specific campaign, how the distribution is spread across any of the demographic areas and again broken down by demographic who viewed, used or delete the advertising item. Finally they can see this information on a campaign level or a advertising item level. The data can be exported as comma delimited output for import into statistical packages or they can view charts and graphs generated by the CMS. Depending on the contact in place, only some part of this data might be accessible to the client, with extra fees required for a more detailed breakdown.
In addition to the CMS, certain embodiments of the present invention provide administration systems for managing clients, advertising items, display's, reports produced based on these results and the like. These are designed for use by the staff only and provide complete access to most of the data fields storied in the database. Via a web interface, these values can be updated and modified. With the exception of the display upload tool, these tools would only be used infrequently for modifications to fix errors.
The customer does not have to create every discount. The CMS can tie into the customer's inventory and sales tracking system. Based on current inventory needs, current selling patterns, under stocked or over stocked items and the like, discount coupons or other targeted ads can be delivered or not delivered to their appropriate clients to help balance the customer's inventory.
In another embodiment of the present invention, generally illustrated in
A new demographic profile is created for client targeting. Customers are provided with an opportunity to select client demographic parameters. Customers are also provided with an opportunity to select scores for preferred client demographic data. An estimated delivery count of content of the advertising item is displayed. Customers can then repeat the first two steps in this paragraph. Optional boosters can be selected to increase delivery probabilities of the advertising item. The boosters are selected from at least one of, placement of coupons in a ranked ordering, preferred coupon display location on a screen of the portable device, size and quantity of graphics used, fonts, client alerts, and the like. A demographic profile is saved and named by the customer.
A new advertising campaign is created that links content deliverables and demographic profiles relative to the advertising item. Saved and named entered data and uploaded images are selected. Saved and named demographic profile are also selected. Start and end dates are established for the advertising campaign. Maximum costs or impressions of clients relative to the advertising item for the advertising campaign are indicated. The customer then approves a final advertising campaign.
Final advertising campaign data is sent to the host server. The new advertising campaign is launched. The advertising campaign results are then viewed by the customer. Customer's are provided with access to advertising campaign results. The customer can then view at least one of, number of discounts redeemed, number of discounts viewed, demographic breakdown of users who redeemed or viewed; geographic breakdown of the above, temporal breakdown of the above, total costs of the advertising campaign, and the like.
The first step to creating an advertising campaign is defining the actual advertising item such as a coupon or ad. This is done first by selecting the base display that will be used. The display comes up on the screen with blank spaces where text, images or other dynamic data will go. At this time the host server provides a base CPM based on the complexity of the display selected and the current contract. The client names the advertising item and then fills in, uploads and otherwise provides all the necessary data for blank spaces. In interactive advertising items, for instance ones with random rewards, percentages are also given for the probabilities of any one reward coming up. This finished advertising item is then saved.
The second step is creating a demographic description of the target group. This is not linked to the advertising item in any way at this point. The client names their demographic group and then can add criteria in two ways. First, they can absolutely restrict their distribution by indicating ranges or choices in demographics, for instance that a advertising item should only be delivered to people ages 22-48. In addition, however, they can also indicate preference, for instance delivering the advertising item to people age 28-38 should take priority. As they make changes the system checks the data with the host server and reports how many clients match the criteria chosen so far.
In another embodiment of the present invention, a method is provided of downloading advertising items from a host server to a portable device of a client. A client's device information, relative to the client's portable device, is received at the host server. A determination is made, from the client's device information, the model or version of the client's portable device. In response to the step of determining, a client ID is embedded in the client's portable device. Client software is delivered from the host server to the client's portable device. The client software is used for downloaded advertising items relative to a product or service from the host server to the client's portable device. By way of illustration, and without limitation, the client software can be written in J2ME (Java2 Portable Edition), be ported to Symbian, BREW, Palm OS and .NET for windows CE, and the like. In addition as new portable device OS's and development languages evolve the client software can be easily ported to them as well. By way of illustration, and without limitation, the J2ME application can installed onto a cell phone by sending an SMS message to the phone with a download link. The client selects the link and then automatically install the software. However, the url can also be entered by hand in the devices web browser or the software could be transferred over a download cable.
In one embodiment of the present invention, a display upload tool (“GUT”) is provided. For advertising items the GUT takes the XML file (like the type above) and uploads it into the CMS, making it available as a choice when designing a advertising item. However, for display's to replace the list view, while an XML file is again uploaded, additional data has to be provided. A display controller is told how to distribute the new list view. For instance, it might only be to certain demographics (for example people under 18), or to a certain random percentage of the client base (for testing) or only if more then a certain number of advertising items are kept on the portable device.
The foregoing description of embodiments of the present invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Obviously, many modifications and variations will be apparent to practitioners skilled in this art. It is intended that the scope of the invention be defined by the following claims and their equivalents.
This application claims the benefit of U.S. Ser. No. 60/650,363 filed Feb. 4, 2005, which application is fully incorporated herein by reference
| Number | Name | Date | Kind |
|---|---|---|---|
| 5353218 | De Lapa | Oct 1994 | A |
| 5710886 | Christensen | Jan 1998 | A |
| 5754176 | Crawford | May 1998 | A |
| 5822735 | De Lapa | Oct 1998 | A |
| 5857175 | Day | Jan 1999 | A |
| 5970469 | Scroggie | Oct 1999 | A |
| 6026370 | Jermyn | Feb 2000 | A |
| 6035280 | Christensen | Mar 2000 | A |
| 6041309 | Laor | Mar 2000 | A |
| 6041311 | Chislenko et al. | Mar 2000 | A |
| 6055573 | Gardenswartz | Apr 2000 | A |
| 6061060 | Berry et al. | May 2000 | A |
| 6076069 | Laor | Jun 2000 | A |
| 6185541 | Scroggie | Feb 2001 | B1 |
| 6278979 | Williams | Aug 2001 | B1 |
| 6298330 | Gardenswartz | Oct 2001 | B1 |
| 6321208 | Barnett | Nov 2001 | B1 |
| 6336099 | Barnett | Jan 2002 | B1 |
| 6385591 | Mankoff et al. | May 2002 | B1 |
| 6467686 | Guthrie et al. | Oct 2002 | B1 |
| 6484146 | Day | Nov 2002 | B2 |
| 6487538 | Gupta et al. | Nov 2002 | B1 |
| 6493110 | Roberts | Dec 2002 | B1 |
| 6584448 | Laor | Jun 2003 | B1 |
| 6647269 | Hendry et al. | Nov 2003 | B2 |
| 6670687 | Satoh | Dec 2003 | B2 |
| 6671732 | Weiner | Dec 2003 | B1 |
| 6679421 | Shin et al. | Jan 2004 | B2 |
| 6736322 | Gobburu et al. | May 2004 | B2 |
| 6753887 | Carolan et al. | Jun 2004 | B2 |
| 6882442 | Roberts | Apr 2005 | B2 |
| 6885994 | Scroggie | Apr 2005 | B1 |
| 6954732 | De Lapa | Oct 2005 | B1 |
| 6968513 | Rinebold et al. | Nov 2005 | B1 |
| 6996579 | Leung et al. | Feb 2006 | B2 |
| 7003734 | Gardner et al. | Feb 2006 | B1 |
| 7047502 | Petropoulos et al. | May 2006 | B2 |
| 7089530 | Dardinski et al. | Aug 2006 | B1 |
| 7184972 | Flaherty | Feb 2007 | B2 |
| 7228285 | Hull | Jun 2007 | B2 |
| 7233913 | Scroggie | Jun 2007 | B2 |
| 7236942 | Walker et al. | Jun 2007 | B1 |
| 7346606 | Bharat | Mar 2008 | B2 |
| 7346615 | Bem | Mar 2008 | B2 |
| 7370002 | Heckerman et al. | May 2008 | B2 |
| 7398248 | Phillips | Jul 2008 | B2 |
| 7415426 | Williams | Aug 2008 | B2 |
| 7421504 | Imaida et al. | Sep 2008 | B2 |
| 7499948 | Smith et al. | Mar 2009 | B2 |
| 7552458 | Finseth et al. | Jun 2009 | B1 |
| 7599850 | Laor | Oct 2009 | B1 |
| 7653594 | Davis | Jan 2010 | B2 |
| 7711834 | Gormish | May 2010 | B2 |
| 8595056 | Sohya et al. | Nov 2013 | B2 |
| 9298677 | Tollinger et al. | Mar 2016 | B2 |
| 20010051911 | Marks et al. | Dec 2001 | A1 |
| 20020040316 | Shin et al. | Apr 2002 | A1 |
| 20020040341 | Shin et al. | Apr 2002 | A1 |
| 20020049635 | Mai et al. | Apr 2002 | A1 |
| 20020065713 | Awanda et al. | May 2002 | A1 |
| 20020091569 | Kitaura et al. | Jul 2002 | A1 |
| 20020111172 | DeWolf et al. | Aug 2002 | A1 |
| 20020120505 | Henkin et al. | Aug 2002 | A1 |
| 20020161646 | Gailey et al. | Oct 2002 | A1 |
| 20030004802 | Callegari | Jan 2003 | A1 |
| 20030032409 | Hutcheson et al. | Feb 2003 | A1 |
| 20030033292 | Meisel et al. | Feb 2003 | A1 |
| 20030046156 | Cromer et al. | Mar 2003 | A1 |
| 20030046161 | Kamangar et al. | Mar 2003 | A1 |
| 20030058261 | Challa et al. | Mar 2003 | A1 |
| 20030064713 | Deshpande | Apr 2003 | A1 |
| 20030078966 | Kinjo | Apr 2003 | A1 |
| 20030088525 | Velez | May 2003 | A1 |
| 20030093314 | Leung et al. | May 2003 | A1 |
| 20030115152 | Flaherty | Jun 2003 | A1 |
| 20030144035 | Weinblatt et al. | Jul 2003 | A1 |
| 20030146939 | Petropoulos et al. | Aug 2003 | A1 |
| 20030233276 | Pearlman et al. | Dec 2003 | A1 |
| 20040137886 | Ross et al. | Jul 2004 | A1 |
| 20040141011 | Smethers et al. | Jul 2004 | A1 |
| 20040181555 | Ratner et al. | Sep 2004 | A1 |
| 20040254836 | Emoke Barabas et al. | Dec 2004 | A1 |
| 20040260577 | Dahlin et al. | Dec 2004 | A1 |
| 20040260911 | Chauvel et al. | Dec 2004 | A1 |
| 20050071224 | Fikes et al. | Mar 2005 | A1 |
| 20050086104 | McFadden | Apr 2005 | A1 |
| 20050092839 | Oram | May 2005 | A1 |
| 20050119949 | Campagna | Jun 2005 | A1 |
| 20050131761 | Trika et al. | Jun 2005 | A1 |
| 20050165642 | Brouze et al. | Jul 2005 | A1 |
| 20050222905 | Wills | Oct 2005 | A1 |
| 20050222906 | Chen | Oct 2005 | A1 |
| 20060004628 | Axe et al. | Jan 2006 | A1 |
| 20060036491 | Leung et al. | Feb 2006 | A1 |
| 20060041638 | Whittaker et al. | Feb 2006 | A1 |
| 20060095424 | Petropoulos et al. | May 2006 | A1 |
| 20060143067 | Calabria | Jun 2006 | A1 |
| 20060149622 | Baluja et al. | Jul 2006 | A1 |
| 20060156283 | Landau et al. | Jul 2006 | A1 |
| 20060190331 | Tollinger et al. | Aug 2006 | A1 |
| 20060259360 | Flinn | Nov 2006 | A1 |
| 20060294084 | Patel et al. | Dec 2006 | A1 |
| 20070038509 | Jain | Feb 2007 | A1 |
| 20070061197 | Ramer | Mar 2007 | A1 |
| 20070061242 | Ramer et al. | Mar 2007 | A1 |
| 20070249330 | Cortegiano | Oct 2007 | A1 |
| 20070250383 | Tollinger et al. | Oct 2007 | A1 |
| 20090030779 | Tollinger et al. | Jan 2009 | A1 |
| 20090070207 | Engel et al. | Mar 2009 | A1 |
| 20100088166 | Tollinger et al. | Apr 2010 | A1 |
| 20100138299 | Preston et al. | Jun 2010 | A1 |
| 20100138303 | Preston et al. | Jun 2010 | A1 |
| 20160034954 | Tollinger et al. | Feb 2016 | A1 |
| 20160321701 | Tollinger et al. | Nov 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 2002-288506 | Oct 2002 | JP |
| 10-2005-0092682 | Sep 2005 | KR |
| WO 0171949 | Sep 2001 | WO |
| WO 2008021382 | Feb 2008 | WO |
| Entry |
|---|
| Non-Final Office Action of related U.S. Appl. No. 11/349,050 (mailed Oct. 13, 2009). |
| Non-Final Office Action of related U.S. Appl. No. 11/349,050 (mailed Aug. 19, 2009). |
| Interview Summary of related U.S. Appl. No. 11/349,050 (mailed Jan. 12, 2010). |
| Non-Final Office Action of related U.S. Appl. No. 12/212,530 (mailed Dec. 21, 2009). |
| Office Action mailed on Jul. 20, 2010 issued against U.S. Appl. No. 11/898,197. |
| Office Action mailed on May 26, 2010 issued against U.S. Appl. No. 11/408,599. |
| Office Action mailed on Feb. 25, 2010 issued against U.S. Appl. No. 11/349,050. |
| International Search Report dated Apr. 20, 2010 against Application No. PCT/US2009/055653. |
| Written Opinion of the International Searching Authority dated Apr. 20, 2010 against Application No. PCT/US2009/055653. |
| DeBolt, Virginia, “Integrated HTML and CSS: A Smarter, Faster Way to Learn”, Jan. 2005, Sybex, pp. 15-29. |
| “IEEE 100 The Authoritative Dictionary of IEEE Standards Terms Seventh Edition”, Date of Publication: 2000, p. 1176. |
| Number | Date | Country | |
|---|---|---|---|
| 20060190330 A1 | Aug 2006 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60650363 | Feb 2005 | US |
