Patent Grant
11995656
At least some embodiments disclosed in the present application relate to the coordination of a plurality of separate computer systems connected via computer networks to set up the processing of a predetermined task at a time when a set of predetermined conditions are satisfied.
In a system having multiple computer systems connected via one or more computer networks, resources for processing a task may reside in different computer systems. The use of a predetermined communication protocol allows the computer systems to communicate with each other in a predetermined way to utilize the resources that may be distributed among the computer systems for the processing of the task. Improvements to the communication protocol can improve the performance of the system as a whole and/or improve the functionalities of the system as a whole. In some instances, improvements to the communication protocol can improve the performance of some of the individual computer systems and/or improve the functionalities of the individual computer systems.
For example, a typical electronic payment processing network has a transaction handler interconnecting a plurality of acquirer processors and a plurality of issuer processors according to an electronic communication standard. The transaction handler is generally a special purpose computer system that is substantially independent from other computer systems in the network, such as issuer processors and the acquirer processors, which are special purpose computer systems configured to control accounts from which payments are made and special purpose computer systems configured to control accounts to which the payments are made, respectively.
A typical electronic payment processing network has the capability to process certain transactions, such as credit card or debit card transactions, but may not have the capability process other transactions, such as add-on transactions (e.g., loyalty reward, benefit redemption) coupled with regular transactions.
Some recent developments provided improved electronic payment processing networks that have the improved capability to process certain add-on transactions coupled with conventional electronic payment transactions, such as those disclosed in U.S. Pat. App. Pub. No. 2014/0222533, entitled “Systems and Methods to Use Transaction Authorization Communications to Process Individualized Offers,” U.S. Pat. App. Pub. No. 2013/0282461, entitled “Systems and Methods to Use Transaction Authorization Communications to Process Offers,” U.S. Pat. App. Pub. No. 2013/0246150, entitled “Systems and Methods to Apply the Benefit of Offers via a Transaction Handler,” U.S. Pat. App. Pub. No. 2013/0091000, entitled “Systems and Methods to Provide Discount at Point of Sales Terminals,” U.S. Pat. App. Pub. No. 2013/0124287, entitled “Systems and Methods to Provide Discount at Point of Sales Terminals,” and U.S. Pat. App. Pub. No. 2011/0125565, entitled “Systems and Methods for Multi-Channel Offer Redemption,” the disclosures of which applications are hereby incorporated herein by reference.
There are challenges in implementing the additional capabilities with minimum impact to the performance of the core functionalities of the electronic payment processing network.
The disclosures of the above discussed patent documents are hereby incorporated herein by reference.
The embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.
In one embodiment disclosed herein, an identifier of a resource is propagated, using a communication portal of a processing system after the resource is allocated in the data warehouse of the processing system, to a first website, which forwards a web browser together with the identifier of the resource to a second website to perform operations with the processing system, during which operations the second web provides the identifier of the resource back to the processing system. Upon receiving the identifier of the resource back in the processing system from the second website, the processing system configures in the data warehouse the resource to be processed in connection with operations with the first website.
The use of the round trip communication of the identifier of the resource delays the configuration of the processing of the resource at a later time after the operations with the second website are performed. Thus, the processing system does not have to monitor the operations with the first website for the processing of the resource before the operations with the second website are completed. The technique at least reduces the computing workload at the processing system during the period of time between the allocation of the resource and the receiving of the identifier of the resource back from the second website, and thus improves the efficiency of the processing system.
In
During a communication session between the portal (13) and a website A (15), the portal (13) allocates (31) the resource (23) for processing during operations between the website A (15) and the processing system (11), scheduled after relevant operations between a website B (17) and the processing system (11). The availability of the resource (23) is presented to a web browser (19).
In
In one embodiment, the portal (13) provides (33) the resource ID (25) to the website A (15) during presentation of the availability of the resource (23). The website A (15) indicates the availability of the resource (23) to the web browser (19) and forwards/redirects the web browser (19) to the website B (17). In forwarding the web browser (19) to the website B (17), the website A (15) provides (35) the resource ID (25) to the website B (17) via the web browser (19).
For example, the portal (13) and/or the website A (15) is configured in one embodiment to embed the resource ID (25) in a uniform resource locator (URL) pointing to the website B (17), such that when the web browser (19) is forwarded/redirected to the website B (17), the resource ID (25) is received in the website B (17). During the subsequent communication session between the web browser (19) and the website B(17), the web browser (19) initiates (37) the operations between the website B (17) and the processing system (11), during which the website B (17) provides (39) the resource ID (25) back to the processing system (11). In response, the processing system uses (41) the resource ID (25) to update the resource status (27) and thus activate the processing of the resource during operations between the website A (15) and the processing system (11).
In one embodiment, the processing system (11) is configured to monitor the presence of a resource ID (e.g., 25) in operation communications. If the resource ID (e.g., 25) is provided in a data field of a communication, the processing system (11) updates the data warehouse (23), or instructs the portal (13) to update the data warehouse (23).
In one embodiment, after the processing of the resource at the processing system (11) is activated, the processing system (11) is further configured to process tasks to monitor operations to detect relevant operations with the website A (15) during which the resource (23) is processed, as illustrated in
In
In
In some embodiments of
For example, the method of
In
The portal (13) and/or the first website (15) provides (53) an identifier (25) of the resource (23) in a uniform resource locator (URL) used by the first website to forward or redirect a web browser (19) to a second website (17).
The web browser (19) communicates (55) with the second website (17) to initiate first operations in the processing system (11) related to the second website (17), using an account identifier (25) provided by the web browser (19), during which operations the identifier (25) of the resource (23) is transmitted to the processing system (11).
In response to the receiving of the identifier (25) of the resource (23) in the processing system (11) during the first operations, the processing system (11) and/or the portal (13) associate (57) the account identifier (25) with the resource (23) in a data warehouse (21) coupled with the processing system (11) to activate monitoring for second operations related to the first website (15) using the account identifier (25).
Subsequently, during the processing of the second operations related to the first website (15) using the account identifier (25), the processing system (11) processes (59) the allocated and activated resource (23).
In some embodiments, the first website (15) communicates with the portal (13) to process the allocated and activated resource (23) during the second operations related to the first website (15). In such embodiments, the processing system (11) does not have to monitoring general operations to detect the applicable second operations related to the first website (15).
The techniques discussed above in connection with
For example, the portal (13) may communicate with the website A (15) to provide an offer that has a benefit applicable to a payment to the website A (15), after the user of the web browser (19) is referred to the website B (17) to make a payment to the website B (17) for a purchase made in the website B (17). After an identifier of the offer is transmitted through the portal (13), to the website A (15), the web browser (19), the website B (17), and back to the processing system (11) configured in the electronic payment processing network, the offer is activated for processing in a payment transaction with the website A (15), after the web browser completes the purchase from the website B (17) and proceeds with a purchase from the website A (15). The activation of the offer allows the website A (15) or the transaction processing system (11) to apply the benefit of the offer to the payment transaction with the website A (15).
In one embodiment, for example, the processing system (11) is a transaction handler of an electronic payment processing network.
In one embodiment, a system and method is configured to active an offer of a first merchant based on a payment transaction with a second merchant. The described system and method is configured to use a round-trip transmission of an offer ID to facilitate the real time activation of such an offer. The method operates by an offer platform generating a unique ID for an offer presented to a user. When the user is referred by the first merchant to the second merchant for a purchase, the unique ID is provided to the second merchant with the referral. During the payment transaction with the second merchant, the authorization request from the second merchant is configured to include the unique offer ID. The payment processing system is configured to receive the unique ID in the authorization request and provide the unique ID to the offer platform if the payment transaction is approved. Based on the real time notification from the payment processing system, the offer platform activates the offer. As a result of the system, the merchant systems are can be simply configured to support the transmission of offer IDs for reliable processing of such offers that are activated based on the payment transactions on other merchants (e.g., advertising merchants).
For example, in one embodiment, an offer system includes a hosting merchant and an advertising merchant. The hosting merchant provides an offer to a user with a benefit applicable to a purchase from the hosting merchant. The offer is activated upon the user makes a purchase from the advertising merchant that is advertised on the hosting merchant.
For example, after the offer is presented to the user, the hosting merchant may refer the user to the advertising merchant to make the purchase required to active the offer. For example, when the user is visiting the website of the hosting merchant, the offer can be presented electronically; and the user may select the offer to follow a link to a website of the advertising merchant. The link may include an identification of the offer presented to the user and request the advertising merchant to include the identification of the offer in a payment transaction made by the user as a result of the referral.
In one embodiment, the data format of authorization requests is configured to include an optional field to host the identification of the offer. When an authorization request including such an identification of the offer is received, a payment processing apparatus in the payment processing network, such as a transaction handler, an issuer processor, or an acquirer processor, can detect the transmission of the offer identification and extract the offer identification for offer processing.
For example, the extracted offer identification can be communicated to an offer platform coupled with the payment processing apparatus to activate the offer in real time with the authorization of the payment to the advertising merchant.
The authorization request of the invention can be used to activate the offer from the hosting merchant, upon completion of the transaction with the advertising merchant.
For example, once the offer is activated, the benefit of the offer can be applied to the payment made by the user to the hosting merchant.
For example, the offer of the advertising merchant may be presented to the user at the stage of the user checking out for a purchase made by the user from the hosting merchant. If the user accepts the offer, the user is directed to the advertising merchant for a purchase. If the user makes the required purchase, the identification of the offer from the offer platform and provided to the advertising merchant is provided to the payment processing apparatus via the authorization request for the payment made to the advertising merchant, and further routed to the offer platform for activation. Thus, upon completion of the purchase with the advertising merchant, the offer is activated in real time; and the user may continue the checking out process at the hosting merchant. During checking out at the host merchant, the offer platform applies the benefit of the activated offer to reduce the amount of payment required.
In some embodiments, after the offer is activated, the payment processing apparatus may provide the benefit of the offer to the user via adjusting the transaction amount specified in an authorization request for a payment account of the user, in a way as illustrated in U.S. Pat. App. Pub. No. 2013/0124287, U.S. Pat. App. Pub. No. 2013/0091000, both entitled “Systems and Methods to Provide Discount at Point of Sales Terminals”, the entire disclosures of which applications are hereby incorporated herein by reference.
In one embodiment, when the benefit of the offer is not solely sponsored by the hosting merchant, the benefit of the offer can be provided to the user during the processing of the authorization of a payment transaction to the hosting merchant, in a way as illustrated in U.S. Pat. App. Pub. No. 2013/0246150, entitled “Systems and Methods to Apply the Benefit of Offers via a Transaction Handler”, the entire disclosure of which application is hereby incorporated herein by reference.
In one embodiment, during the activation of the offer, a trigger record is generated for the transaction handler to detect transactions that may be relevant to the offer. The trigger record specifies a portion of the requirements a payment transaction is to meet in order to be qualified for the benefit of the offer. The transaction handler uses the trigger record to filter the transactions being processed to select a subset of transactions for further processing and determining from the subset of the transactions a relevant transaction that satisfies all of the benefit redemption requirements of the offer. The generation of the trigger record upon the receiving of the identification of the offer via an authorization request for a required payment transaction with the advertising merchant improves the performance of the transaction handler, by reducing the time period the trigger record is to be operated upon for filtering operations.
In one embodiment, systems and methods are configured to transmit, in an authorization request for a payment to a first merchant, the identification of an offer of a second merchant. During the processing of the authorization request for the first merchant, the identification of the offer of the second merchant is extracted. The extracted offer identification can be used to active the offer in response to the authorization of the payment to the first merchant.
In
For example, the offer platform (185) may be integrated with an electronic shopping cart system running on the hosting merchant website (181). In response to the user (101) making a purchase from the hosting merchant via the point of interaction (107), the offer platform (185) may present an offer (186) of an advertising merchant (183) that is generally different from the hosting merchant, but may be the same as the hosting merchant in some instances.
For example, the offer platform may select the offer (186) based on the purchases made by the user (101) and/or the transaction profile (e.g., 131) of the user (101) when the identity of the user (101) is determined.
When the offer (186) presented on the hosting merchant website (181) is selected by the user (101), via the use of the point of interaction (107), such as a web browser running in a user computing device, the hosting merchant website (181) is configured to refer the user (101) to the advertising merchant website (183). The referral (197) includes the offer ID (187) of the offer (186), which uniquely identifies the offer (186) presented on the hosting merchant website (181) to the user (101), among various offers provided by the offer platform (185).
In one embodiment, the referral (197) is configured to serve as a request to transmit the offer ID (187) in an authorization request (e.g., 191) for a payment made by the user (101) as a result of the referral (197).
After the user (101) is referred to the advertising merchant website (183), the user (101) may make a required purchase (or any purchase) from the advertising merchant website (183).
For example, in one embodiment, the requirement of the purchase for activating the offer (186) can be satisfied by any purchase. Alternatively, a predetermined purchase requirement may be established based on a spending threshold, a category of items purchased, etc. In some embodiments, the requirement can be transmitted to the advertising merchant website via the referral (197). In other embodiments, the advertising merchant website (183) may look up the requirements from the offer platform using the offer ID (187). In further embodiments, the requirement is formulated based on information transmitted via the authorization request (191), such as the transaction amount (199), the date and time of the transaction, purchase details (e.g., identifications of items purchased) transmitted in the authorization request (191), etc.
In
In
The transaction handler (103) of the payment processing network (e.g., as illustrated in
In
Thus, in response to the authorization response (195) for the payment transaction requested by the authorization request (191), the transaction handler (103) and the offer platform (185) activates the offer (186), such at the use (101) can obtain the benefit of the offer (186) as soon as the payment transaction is approved.
For example, the offer platform (185) may be integrated with the electronic shopping cart system running on the hosting merchant website (181). Once the offer (186) is activated, the electronic shopping cart system automatically shows the discount provided by the offer (186), and the user (101) can verify the benefit before committing a payment to the hosting merchant website (181) and/or finalizes the purchase from the hosting merchant website (181).
In one embodiment, one or more of the components illustrated in
In one embodiment, an offer system is configured to present an online offer for qualified consumer that depends on the completion of another online purchase. The authorization request (191) containing the offer ID (187) can be used to verify accurately and immediately upon the authorization of the payment transaction for the online purchase required for the offer redemption.
For example, a consumer is shopping on Ticketmaster.com and adds 2 concert tickets to their shopping cart. On the Check-out page, the consumer is offered 25% discount (Ticketmaster gets the offer from the offer platform) on their ticket purchase if he/she spend $50 or more at Macys.com. The offer platform generates an OfferId (e.g., “1K2CGP9”) to uniquely identify the offer presented to the consumer, among similar offers presented to other consumers shopping on Ticketmaster.com. After the consumer accepts the offer by clicking on the offer, the consumer is redirected to Macys.com with an indication of “OfferId=1K2CGP9” in the referral. The consumer submits a payment made using a payment account (e.g., a credit account, a debit account, a prepaid account) for a purchase of $55 at Macys.com. Macys.com sends an authorization request with OfferId=1K2CGP9 to the transaction handler via a respective acquirer of Macys.com. Once the Transaction is authorized, the transaction handler sends the authorization details with the OfferId=1K2CGP9 to the offer platform, which Activates the 25% discount at ticketmaster.com. After the consumer returns or is redirected back to the TicketMaster.com's check-out page. Once the consumer submits the payment made using a payment account (e.g., a credit account, a debit account, a prepaid account) for the purchase of the 2 concert tickets, TicketMaster.com sends the authorization request for the payment of the concert tickets with OfferId=1K2CGP9. The transaction handler discounts the transaction amount 25% by reducing transaction amount requested from the issuer processor of the payment account of the consumer. Thus, the consumer pays the reduced amount that includes the 25% discount.
In one embodiment, the discount provided by the hosting merchant (e.g., TicketMaster.com) is sponsored at least in part by the advertising merchant (e.g., Macys.com). The transaction handler (103) is configured to charge the merchant account (148) to compensate the hosting merchant for the portion of the discount sponsored by the advertising merchant and/or the advertising fee for presenting the offer (186).
In one embodiment, the authorization request (191) containing the offer ID (187) can also be used to track the completion of purchases resulting from an offer.
For example, advertising merchants want to present offers/advertisements to online shoppers while they are browsing, or shopping on, the websites of other merchants. Merchants operating the hosting websites that present the offers are compensated (e.g., by the advertising merchants) if a presented offer has been completed.
In one embodiment, after the offer (186) of an advertising merchant is presented, via the offer platform (185), on the website (181) of a hosting merchant, the offer platform (185) stores in the data warehouse (149) the offer ID (187) in association with the hosting merchant website (181). After the user (101) is redirected, via the referral (197) that contains the offer ID (187), to the advertising merchant website (183), the advertising merchant website (183) is configured to transmit the offer ID (187) in the authorization request (191) for a payment transaction made as a result of the referral (197). In response to the authorization request (191) contains the offer ID (187), the transaction handler (103) is configured to provide the benefit of the offer to the user via the processing of the payment transaction in the consumer account (146) of the user (101), in a way as discussed above and further described in U.S. Pat. App. Pub. No. 2013/0124287, U.S. Pat. App. Pub. No. 2013/0091000, both entitled “Systems and Methods to Provide Discount at Point of Sales Terminals”, and U.S. Pat. App. Pub. No. 2013/0246150, entitled “Systems and Methods to Apply the Benefit of Offers via a Transaction Handler”, the entire disclosures of which applications are hereby incorporated herein by reference.
In one embodiment, based on the data associating the offer ID (187) with the hosting merchant website (181) in the data warehouse (149) and in response to the authorization request (191) containing the offer ID (187), the offer platform (185) and/or the transaction handler (103) is configured to compensated the hosting merchant for presenting the offer (186).
In one embodiment, the compensation provided to the hosting merchant is in response to an authorization response (193) approving the payment transaction requested by the authorization request (191). In some embodiments, the transaction handler (103) is configured to redirect a portion of the payment requested by the authorization request (191) to compensate the hosting merchant.
For example, the transaction handler (103) may generate a companion transaction to pay the hosting merchant using an account of the advertising merchant in response to the redemption of the offer (186) identified by the authorization request (191).
For example, the transaction handler (103) may split the payment from the consumer account (146) into a first payment to the merchant account (148) in response to the authorization request (191) and a second payment to an account of the hosting merchant website (181) to compensate the hosting merchant. The transaction handler (103) combines the two payments as a single payment transaction in the consumer account (146). The transaction handler (103) and/or the offer platform (185) is configured to inform the advertising merchant of the compensation provided to the hosting merchant website (181). For example, in one embodiment, the transaction handler (103) is configured to insert an indication of an advertising fee charged for the offer ID (187) in an authorization response provided to the advertising merchant website via the acquirer processor (147). For example, the authorization response (193) approving the authorization request (191) may include the offer ID (187) to indicate that a difference between the requested transaction amount (199) and the approved transaction amount has been provided to the hosting merchant website (181) as the compensation for the presentation of the offer (186) of the advertising merchant.
In some embodiments, the advertising merchant website (183) is configured to provide the benefit of the offer (186) to the user (101) (e.g., by reducing the total price, offer one or more items free of charge) and use the offer ID (187) in the authorization request (191) to report the completion of the offer (186). In response to the offer ID (187) provided in the authorization request (191), the offer platform (185) deactivates the offer (186) and/or compensates the hosting merchant website (181).
The systems discussed above in connection with
For example, based on the transaction data, an advertising network in one embodiment is provided to present personalized or targeted advertisements/offers on behalf of advertisers. A computing apparatus of, or associated with, the transaction handler uses the transaction data and/or other data, such as account data, merchant data, search data, social networking data, web data, etc., to develop intelligence information about individual customers, or certain types or groups of customers. The intelligence information can be used to select, identify, generate, adjust, prioritize, and/or personalize advertisements/offers to the customers. The transaction handler may be further automated to process the advertisement fees charged to the advertisers, using the accounts of the advertisers, in response to the advertising activities.
For example, the computing apparatus can be configured to generate trigger records for a transaction handler to identify authorization requests that satisfy the conditions specified in the trigger records, identify communication references of the users associated with the identified authorization requests, and use the communication references to target real-time messages at the users in parallel with the transaction handler providing responses to the respective authorization requests. Details in one embodiment regarding the generation and delivery of messages in real-time with the processing of transactions can be found in U.S. Pat. No. 8,359,274, the disclosure of which is hereby incorporated herein by reference.
For example, the computing apparatus can be programmable for real-time interaction with users to provide messages and/or offers, validate fulfillment conditions, and provide benefits to qualified users to fulfill the offers. In one embodiment, the computing apparatus is configured to be programmed via accepting definitions of independent events and linking the events via prerequisite requirements to specify qualification conditions. The linked events form a flow or network of events; and user progress in the flow or network of events is tracked. The operations for each event are performed in an atomic way to allow the user positions in the flow or network of events to be identified as being in between adjacent events in the network. As a result, the programming of the real-time interaction, including the offer rules and messages, can be easily modified during the execution of the programming. Details in one embodiment regarding the formulation and management of real-time interaction can be found in U.S. Pat. App. Pub. No. 2012/0078697, the disclosure of which is hereby incorporated herein by reference.
For example, the computing apparatus can be configured to allow a user to use any of a plurality of registered accounts to participate in an offer campaign, such as performing transactions in the registered accounts to fulfill requirements to obtain the benefit of the offer campaign. In one embodiment, the offer campaign is programmed by offer rules that identify the real time interactions with the user in response to the actions of the user, such as transactions made using any of the registered accounts of the user. The offer campaign for the user is driven at least in part by the actions of the user, such as the transactions made by the user. In one embodiment, transactions in the registered accounts of the user jointly advances the offer campaign for the user; and a milestone achieved in the offer campaign using one account of the user is recognized as a milestone achieved by the user with respect to the multiple registered accounts. Thus, the offer campaign for the user can be advanced by the user via different accounts, as if the registered accounts were a same account; and the user is not limited to using a particular account to participate in the offer campaign, nor using different accounts to drive the offer campaign separately, as if the accounts were assigned to different users. Details in one embodiment regarding the configuration of real time interactions using multiple accounts of a user can be found in U.S. Pat. App. Pub. No. 2014/0074575, the disclosure of which is hereby incorporated herein by reference.
In one embodiment, the computing apparatus is configured to target the same offer differently to users based on the media channels used to deliver the offer. An offer can be configured to include first qualification conditions formulated based on triggering events, such as the current location of a user, the current transaction of the user as being processed by a transaction handler, and second qualification conditions not based on such triggering events. To users reachable via a first set of media channels, the first qualification conditions are ignored in selecting candidate users for the delivery of the offer; and the candidate users are selected based on the second qualification conditions. If the offer has not be delivered to a user via the first set of media channels, the computing apparatus is configured to deliver the offer to the user via a second set of media channels, when the user satisfies both the first qualification conditions and the second qualification conditions. Details in one embodiment can be found in U.S. Pat. App. Pub. No. 2014/0074599, the disclosure of which is hereby incorporated herein by reference.
In one embodiment, a system and method is configured to allow an offer campaign to be specified based on requirements of transactions with multiple merchants. Details in one embodiment can be found in U.S. Pat. App. Pub. No. 2014/0129313, the disclosure of which is hereby incorporated herein by reference.
In one embodiment, a single entity operating the transaction handler performs various operations in the services provided based on the transaction data. For example, in the presentation of the personalized or targeted advertisements, the single entity may perform the operations such as generating the intelligence information, selecting relevant intelligence information for a given audience, selecting, identifying, adjusting, prioritizing, personalizing and/or generating advertisements based on selected relevant intelligence information, and facilitating the delivery of personalized or targeted advertisements, etc. Alternatively, the entity operating the transaction handler cooperates with one or more other entities by providing information to these entities to allow these entities to perform at least some of the operations for presentation of the personalized or targeted advertisements.
In
In one embodiment, a data warehouse (149) as illustrated in
In
In one embodiment, the transaction data (109) relates to financial transactions processed by the transaction handler (103); and the account data (111) relates to information about the account holders involved in the transactions. Further data, such as merchant data that relates to the location, business, products and/or services of the merchants that receive payments from account holders for their purchases, can be used in the generation of the transaction profiles (127).
In one embodiment, the financial transactions are made via an account identification device (141), such as financial transaction cards (e.g., credit cards, debit cards, banking cards, etc.); the financial transaction cards may be embodied in various devices, such as plastic cards, chips, radio frequency identification (RFID) devices, mobile phones, personal digital assistants (PDAs), etc.; and the financial transaction cards may be represented by account identifiers (e.g., account numbers or aliases). In one embodiment, the financial transactions are made via directly using the account information (142), without physically presenting the account identification device (141).
Centralized Data Warehouse
In one embodiment, the transaction handler (103) couples with a centralized data warehouse (149) organized around the transaction data (109). For example, the centralized data warehouse (149) may include, and/or support the determination of, spend band distribution, transaction count and amount, merchant categories, merchant by state, cardholder segmentation by velocity scores, and spending within merchant target, competitive set and cross-section. For example, the centralized data warehouse (149) may include the advertisement data (135) and/or offers of benefits such as discount, reward, points, cashback, etc. The offers can be communicated to the users (e.g., 101) via the advertisement data (135) or as part of the advertisement data (135).
In one embodiment, the centralized data warehouse (149) provides centralized management but allows decentralized execution. For example, a third party strategic marketing analyst, statistician, marketer, promoter, business leader, etc., may access the centralized data warehouse (149) to analyze customer and shopper data, to provide follow-up analyses of customer contributions, to develop propensity models for increased conversion of marketing campaigns, to develop segmentation models for marketing, etc. The centralized data warehouse (149) can be used to manage advertisement campaigns and analyze response profitability.
In one embodiment, the centralized data warehouse (149) includes merchant data (e.g., data about sellers), customer/business data (e.g., data about buyers), and transaction records between sellers and buyers over time. The centralized data warehouse (149) can be used to support corporate sales forecasting, fraud analysis reporting, sales/customer relationship management (CRM) business intelligence, credit risk prediction and analysis, advanced authorization reporting, merchant benchmarking, business intelligence for small business, rewards, etc.
In one embodiment, the transaction data (109) is combined with external data, such as surveys, benchmarks, search engine statistics, demographics, competition information, emails, etc., to flag key events and data values, to set customer, merchant, data or event triggers, and to drive new transactions and new customer contacts.
Transaction Profile Based Operations
In
In one embodiment, the transaction profiles (127) provide intelligence information on the behavior, pattern, preference, propensity, tendency, frequency, trend, and budget of the user (101) in making purchases. In one embodiment, the transaction profiles (127) include information about what the user (101) owns, such as points, miles, or other rewards currency, available credit, and received offers, such as coupons loaded into the accounts of the user (101). In one embodiment, the transaction profiles (127) include information based on past offer/coupon redemption patterns. In one embodiment, the transaction profiles (127) include information on shopping patterns in retail stores as well as online, including frequency of shopping, amount spent in each shopping trip, distance of merchant location (retail) from the address of the account holder(s), etc.
In one embodiment, the transaction handler (103) (and/or the portal (143)) is configured to provide at least part of the intelligence for the prioritization, generation, selection, customization and/or adjustment of the advertisement for delivery within a transaction process involving the transaction handler (103). For example, the advertisement may be presented to a customer in response to the customer making a payment via the transaction handler (103).
Some of the transaction profiles (127) are specific to the user (101), or to an account of the user (101), or to a group of users of which the user (101) is a member, such as a household, family, company, neighborhood, city, or group identified by certain characteristics related to online activities, offline purchase activities, merchant propensity, etc.
The profile generator (121) may generate and update the transaction profiles (127) in batch mode periodically, or generates the transaction profiles (127) in real time, or just in time, in response to a request received in the portal (143) for such profiles.
The transaction profiles (127) of one embodiment include the values for a set of parameters. Computing the values of the parameters may involve counting transactions that meet one or more criteria, and/or building a statistically-based model in which one or more calculated values or transformed values are put into a statistical algorithm that weights each value to optimize its collective predictiveness for various predetermined purposes.
In
In one embodiment, the user data (125) includes the characterization of the context at the point of interaction (107). Thus, the use of the user specific profile (131), selected using the user data (125), includes the consideration of the context at the point of interaction (107) in selecting the user specific advertisement data (119).
In one embodiment, in selecting the user specific advertisement data (119), the advertisement selector (133) uses not only the user specific profile (131), but also information regarding the context at the point of interaction (107). For example, in one embodiment, the user data (125) includes information regarding the context at the point of interaction (107); and the advertisement selector (133) explicitly uses the context information in the generation or selection of the user specific advertisement data (119).
In one embodiment, the advertisement selector (133) may query for specific information regarding the user (101) before providing the user specific advertisement data (119). The queries may be communicated to the operator of the transaction handler (103) and, in particular, to the transaction handler (103) or the profile generator (121). For example, the queries from the advertisement selector (133) may be transmitted and received in accordance with an application programming interface or other query interface of the transaction handler (103), the profile generator (121) or the portal (143) of the transaction handler (103).
In one embodiment, the queries communicated from the advertisement selector (133) may request intelligence information regarding the user (101) at any level of specificity (e.g., segment level, individual level). For example, the queries may include a request for a certain field or type of information in a cardholder's aggregate spending profile. As another example, the queries may include a request for the spending level of the user (101) in a certain merchant category over a prior time period (e.g., six months).
In one embodiment, the advertisement selector (133) is operated by an entity that is separate from the entity that operates the transaction handler (103). For example, the advertisement selector (133) may be operated by a search engine, a publisher, an advertiser, an ad network, or an online merchant. The user specific profile (131) is provided to the advertisement selector (133) to assist the customization of the user specific advertisement data (119).
In one embodiment, advertising is targeted based on shopping patterns in a merchant category (e.g., as represented by a Merchant Category Code (MCC)) that has high correlation of spending propensity with other merchant categories (e.g., other MCCs). For example, in the context of a first MCC for a targeted audience, a profile identifying second MCCs that have high correlation of spending propensity with the first MCC can be used to select advertisements for the targeted audience.
In one embodiment, the aggregated spending profile is used to provide intelligence information about the spending patterns, preferences, and/or trends of the user (101). For example, a predictive model can be established based on the aggregated spending profile to estimate the needs of the user (101). For example, the factor values and/or the cluster ID in the aggregated spending profile can be used to determine the spending preferences of the user (101). For example, the channel distribution in the aggregated spending profile can be used to provide a customized offer targeted for a particular channel, based on the spending patterns of the user (101). Further details about aggregated spending profile can be found in U.S. Pat. App. Pub. Nos. 2010/0306029 and 2010/0306032, the disclosures of which applications are here by incorporated herein by reference.
In one embodiment, mobile advertisements, such as offers and coupons, are generated and disseminated based on aspects of prior purchases, such as timing, location, and nature of the purchases, etc. In one embodiment, the size of the benefit of the offer or coupon is based on purchase volume or spending amount of the prior purchase and/or the subsequent purchase that may qualify for the redemption of the offer. Further details and examples of one embodiment are provided in U.S. Pat. App. Pub. No. 2008/0201226, entitled “Mobile Coupon Method and Portable Consumer Device for Utilizing Same,” the disclosure of which is hereby incorporated herein by reference.
In one embodiment, conditional rewards are provided to the user (101); and the transaction handler (103) monitors the transactions of the user (101) to identify redeemable rewards that have satisfied the respective conditions. In one embodiment, the conditional rewards are selected based on transaction data (109). Further details and examples of one embodiment are provided in U.S. Pat. App. Pub. No. 2008/0082418, entitled “Consumer Specific Conditional Rewards,” the disclosure of which is hereby incorporated herein by reference. The techniques to detect the satisfied conditions of conditional rewards can also be used to detect the transactions that satisfy the conditions specified to locate the transactions that result from online activities, such as online advertisements, searches, etc., to correlate the transactions with the respective online activities.
Further details about targeted offer delivery in one embodiment are provided in U.S. Pat. App. Pub. No. 2010/0030644, entitled “Targeted Advertising by Payment Processor History of Cashless Acquired Merchant Transaction on Issued Consumer Account,” and in U.S. Pat. App. Pub. No. 2011/0035280, entitled “Systems and Methods for Targeted Advertisement Delivery,” the disclosures of which applications are hereby incorporated herein by reference.
Transaction Processing and Data
In
In
The accumulated transaction data (109) and the corresponding account data (111) are used to generate intelligence information about the purchase behavior, pattern, preference, tendency, frequency, trend, amount and/or propensity of the users (e.g., 101), as individuals or as a member of a group. The intelligence information can then be used to generate, identify and/or select targeted advertisements for presentation to the user (101) on the point of interaction (107), during a transaction, after a transaction, or when other opportunities arise.
In
The account identification device (141) of one embodiment is a plastic card having a magnetic strip storing account information (142) identifying the consumer account (146) and/or the issuer processor (145). Alternatively, the account identification device (141) is a smartcard having an integrated circuit chip storing at least the account information (142). The account identification device (141) may optionally include a mobile phone having an integrated smartcard.
The account information (142) may be printed or embossed on the account identification device (141). The account information (142) may be printed as a bar code to allow the transaction terminal (105) to read the information via an optical scanner. The account information (142) may be stored in a memory of the account identification device (141) and configured to be read via wireless, contactless communications, such as near field communications via magnetic field coupling, infrared communications, or radio frequency communications. Alternatively, the transaction terminal (105) may require contact with the account identification device (141) to read the account information (142) (e.g., by reading the magnetic strip of a card with a magnetic strip reader).
The transaction terminal (105) is configured to transmit an authorization request message to the acquirer processor (147). The authorization request includes the account information (142), an amount of payment, and information about the merchant (e.g., an indication of the merchant account (148)). The acquirer processor (147) requests the transaction handler (103) to process the authorization request, based on the account information (142) received in the transaction terminal (105). The transaction handler (103) routes the authorization request to the issuer processor (145) and may process and respond to the authorization request when the issuer processor (145) is not available. The issuer processor (145) determines whether to authorize the transaction based at least in part on a balance of the consumer account (146).
The transaction handler (103), the issuer processor (145), and the acquirer processor (147) may each include a subsystem to identify the risk in the transaction and may reject the transaction based on the risk assessment.
The account identification device (141) may include security features to prevent unauthorized uses of the consumer account (146), such as a logo to show the authenticity of the account identification device (141), encryption to protect the account information (142), etc.
The transaction terminal (105) of one embodiment is configured to interact with the account identification device (141) to obtain the account information (142) that identifies the consumer account (146) and/or the issuer processor (145). The transaction terminal (105) communicates with the acquirer processor (147) that controls the merchant account (148) of a merchant. The transaction terminal (105) may communicate with the acquirer processor (147) via a data communication connection, such as a telephone connection, an Internet connection, etc. The acquirer processor (147) is to collect payments into the merchant account (148) on behalf of the merchant.
In one embodiment, the transaction terminal (105) is a POS terminal at a traditional, offline, “brick and mortar” retail store. In another embodiment, the transaction terminal (105) is an online server that receives account information (142) of the consumer account (146) from the user (101) through a web connection. In one embodiment, the user (101) may provide account information (142) through a telephone call, via verbal communications with a representative of the merchant; and the representative enters the account information (142) into the transaction terminal (105) to initiate the transaction.
In one embodiment, the account information (142) can be entered directly into the transaction terminal (105) to make payment from the consumer account (146), without having to physically present the account identification device (141). When a transaction is initiated without physically presenting an account identification device (141), the transaction is classified as a “card-not-present” (CNP) transaction.
In general, the issuer processor (145) may control more than one consumer account (146); the acquirer processor (147) may control more than one merchant account (148); and the transaction handler (103) is connected between a plurality of issuer processors (e.g., 145) and a plurality of acquirer processors (e.g., 147). An entity (e.g., bank) may operate both an issuer processor (145) and an acquirer processor (147).
In one embodiment, the transaction handler (103), the issuer processor (145), the acquirer processor (147), the transaction terminal (105), the portal (143), and other devices and/or services accessing the portal (143) are connected via communications networks, such as local area networks, cellular telecommunications networks, wireless wide area networks, wireless local area networks, an intranet, and Internet. Dedicated communication channels may be used between the transaction handler (103) and the issuer processor (145), between the transaction handler (103) and the acquirer processor (147), and/or between the portal (143) and the transaction handler (103).
In
Typically, the transaction handler (103) is implemented using a powerful computer, or cluster of computers functioning as a unit, controlled by instructions stored on a computer readable medium. The transaction handler (103) is configured to support and deliver authorization services, exception file services, and clearing and settlement services. The transaction handler (103) has a subsystem to process authorization requests and another subsystem to perform clearing and settlement services. The transaction handler (103) is configured to process different types of transactions, such credit card transactions, debit card transactions, prepaid card transactions, and other types of commercial transactions. The transaction handler (103) interconnects the issuer processors (e.g., 145) and the acquirer processor (e.g., 147) to facilitate payment communications.
In
In
The transaction terminal (105) may submit a transaction directly for settlement, without having to separately submit an authorization request.
In one embodiment, the portal (143) provides a user interface to allow the user (101) to organize the transactions in one or more consumer accounts (146) of the user with one or more issuers. The user (101) may organize the transactions using information and/or categories identified in the transaction records, such as merchant category, transaction date, amount, etc. Examples and techniques in one embodiment are provided in U.S. Pat. App. Pub. No. 2007/0055597, entitled “Method and System for Manipulating Purchase Information,” the disclosure of which is hereby incorporated herein by reference.
In one embodiment, the portal (143) provides transaction based statistics, such as indicators for retail spending monitoring, indicators for merchant benchmarking, industry/market segmentation, indicators of spending patterns, etc. Further examples can be found in U.S. Pat. App. Pub. No. 2009/0048884, entitled “Merchant Benchmarking Tool,” U.S. patent application Ser. No. 12/940,562, filed Nov. 5, 2010, and U.S. patent application Ser. No. 12/940,664, filed Nov. 5, 2010, the disclosures of which applications are hereby incorporated herein by reference.
Transaction Terminal
In one embodiment, the transaction terminal (105) includes a memory (167) coupled to the processor (151), which controls the operations of a reader (163), an input device (153), an output device (165) and a network interface (161). The memory (167) may store instructions for the processor (151) and/or data, such as an identification that is associated with the merchant account (148).
In one embodiment, the reader (163) includes a magnetic strip reader. In another embodiment, the reader (163) includes a contactless reader, such as a radio frequency identification (RFID) reader, a near field communications (NFC) device configured to read data via magnetic field coupling (in accordance with ISO standard 14443/NFC), a Bluetooth transceiver, a WiFi transceiver, an infrared transceiver, a laser scanner, etc.
In one embodiment, the input device (153) includes key buttons that can be used to enter the account information (142) directly into the transaction terminal (105) without the physical presence of the account identification device (141). The input device (153) can be configured to provide further information to initiate a transaction, such as a personal identification number (PIN), password, zip code, etc. that may be used to access the account identification device (141), or in combination with the account information (142) obtained from the account identification device (141).
In one embodiment, the output device (165) may include a display, a speaker, and/or a printer to present information, such as the result of an authorization request, a receipt for the transaction, an advertisement, etc.
In one embodiment, the network interface (161) is configured to communicate with the acquirer processor (147) via a telephone connection, an Internet connection, or a dedicated data communication channel.
In one embodiment, the instructions stored in the memory (167) are configured at least to cause the transaction terminal (105) to send an authorization request message to the acquirer processor (147) to initiate a transaction. The transaction terminal (105) may or may not send a separate request for the clearing and settling of the transaction. The instructions stored in the memory (167) are also configured to cause the transaction terminal (105) to perform other types of functions discussed in this description.
In one embodiment, a transaction terminal (105) may have fewer components than those illustrated in
In one embodiment, a transaction terminal (105) may have more components than those illustrated in
Account Identification Device
In one embodiment, the account identification device (141) includes a memory (167) coupled to the processor (151), which controls the operations of a communication device (159), an input device (153), an audio device (157) and a display device (155). The memory (167) may store instructions for the processor (151) and/or data, such as the account information (142) associated with the consumer account (146).
In one embodiment, the account information (142) includes an identifier identifying the issuer (and thus the issuer processor (145)) among a plurality of issuers, and an identifier identifying the consumer account among a plurality of consumer accounts controlled by the issuer processor (145). The account information (142) may include an expiration date of the account identification device (141), the name of the consumer holding the consumer account (146), and/or an identifier identifying the account identification device (141) among a plurality of account identification devices associated with the consumer account (146).
In one embodiment, the account information (142) may further include a loyalty program account number, accumulated rewards of the consumer in the loyalty program, an address of the consumer, a balance of the consumer account (146), transit information (e.g., a subway or train pass), access information (e.g., access badges), and/or consumer information (e.g., name, date of birth), etc.
In one embodiment, the memory includes a nonvolatile memory, such as magnetic strip, a memory chip, a flash memory, a Read Only Memory (ROM), etc. to store the account information (142).
In one embodiment, the information stored in the memory (167) of the account identification device (141) may also be in the form of data tracks that are traditionally associated with credits cards. Such tracks include Track 1 and Track 2. Track 1 (“International Air Transport Association”) stores more information than Track 2, and contains the cardholder's name as well as the account number and other discretionary data. Track 1 is sometimes used by airlines when securing reservations with a credit card. Track 2 (“American Banking Association”) is currently most commonly used and is read by ATMs and credit card checkers. The ABA (American Banking Association) designed the specifications of Track 1 and banks abide by it. It contains the cardholder's account number, encrypted PIN, and other discretionary data.
In one embodiment, the communication device (159) includes a semiconductor chip to implement a transceiver for communication with the reader (163) and an antenna to provide and/or receive wireless signals.
In one embodiment, the communication device (159) is configured to communicate with the reader (163). The communication device (159) may include a transmitter to transmit the account information (142) via wireless transmissions, such as radio frequency signals, magnetic coupling, or infrared, Bluetooth or WiFi signals, etc.
In one embodiment, the account identification device (141) is in the form of a mobile phone, personal digital assistant (PDA), etc. The input device (153) can be used to provide input to the processor (151) to control the operation of the account identification device (141); and the audio device (157) and the display device (155) may present status information and/or other information, such as advertisements or offers. The account identification device (141) may include further components that are not shown in
In one embodiment, the communication device (159) may access the account information (142) stored on the memory (167) without going through the processor (151).
In one embodiment, the account identification device (141) has fewer components than those illustrated in
For example, in one embodiment, an account identification device (141) is in the form of a debit card, a credit card, a smartcard, or a consumer device that has optional features such as magnetic strips, or smartcards.
An example of an account identification device (141) is a magnetic strip attached to a plastic substrate in the form of a card. The magnetic strip is used as the memory (167) of the account identification device (141) to provide the account information (142). Consumer information, such as account number, expiration date, and consumer name may be printed or embossed on the card. A semiconductor chip implementing the memory (167) and the communication device (159) may also be embedded in the plastic card to provide account information (142) in one embodiment. In one embodiment, the account identification device (141) has the semiconductor chip but not the magnetic strip.
In one embodiment, the account identification device (141) is integrated with a security device, such as an access card, a radio frequency identification (RFID) tag, a security card, a transponder, etc.
In one embodiment, the account identification device (141) is a handheld and compact device. In one embodiment, the account identification device (141) has a size suitable to be placed in a wallet or pocket of the consumer.
Some examples of an account identification device (141) include a credit card, a debit card, a stored value device, a payment card, a gift card, a smartcard, a smart media card, a payroll card, a health care card, a wrist band, a keychain device, a supermarket discount card, a transponder, and a machine readable medium containing account information (142).
Point of Interaction
In one embodiment, the point of interaction (107) is to provide an advertisement to the user (101), or to provide information derived from the transaction data (109) to the user (101).
In one embodiment, an advertisement is a marketing interaction which may include an announcement and/or an offer of a benefit, such as a discount, incentive, reward, coupon, gift, cash back, or opportunity (e.g., special ticket/admission). An advertisement may include an offer of a product or service, an announcement of a product or service, or a presentation of a brand of products or services, or a notice of events, facts, opinions, etc. The advertisements can be presented in text, graphics, audio, video, or animation, and as printed matter, web content, interactive media, etc. An advertisement may be presented in response to the presence of a financial transaction card, or in response to a financial transaction card being used to make a financial transaction, or in response to other user activities, such as browsing a web page, submitting a search request, communicating online, entering a wireless communication zone, etc. In one embodiment, the presentation of advertisements may be not a result of a user action.
In one embodiment, the point of interaction (107) can be one of various endpoints of the transaction network, such as point of sale (POS) terminals, automated teller machines (ATMs), electronic kiosks (or computer kiosks or interactive kiosks), self-assist checkout terminals, vending machines, gas pumps, websites of banks (e.g., issuer banks or acquirer banks of credit cards), bank statements (e.g., credit card statements), websites of the transaction handler (103), websites of merchants, checkout websites or web pages for online purchases, etc.
In one embodiment, the point of interaction (107) may be the same as the transaction terminal (105), such as a point of sale (POS) terminal, an automated teller machine (ATM), a mobile phone, a computer of the user for an online transaction, etc. In one embodiment, the point of interaction (107) may be co-located with, or near, the transaction terminal (105) (e.g., a video monitor or display, a digital sign), or produced by the transaction terminal (e.g., a receipt produced by the transaction terminal (105)). In one embodiment, the point of interaction (107) may be separate from and not co-located with the transaction terminal (105), such as a mobile phone, a personal digital assistant, a personal computer of the user, a voice mail box of the user, an email inbox of the user, a digital sign, etc.
For example, the advertisements can be presented on a portion of media for a transaction with the customer, which portion might otherwise be unused and thus referred to as a “white space” herein. A white space can be on a printed matter (e.g., a receipt printed for the transaction, or a printed credit card statement), on a video display (e.g., a display monitor of a POS terminal for a retail transaction, an ATM for cash withdrawal or money transfer, a personal computer of the customer for online purchases), or on an audio channel (e.g., an interactive voice response (IVR) system for a transaction over a telephonic device).
In one embodiment, the white space is part of a media channel available to present a message from the transaction handler (103) in connection with the processing of a transaction of the user (101). In one embodiment, the white space is in a media channel that is used to report information about a transaction of the user (101), such as an authorization status, a confirmation message, a verification message, a user interface to verify a password for the online use of the account information (142), a monthly statement, an alert or a report, or a web page provided by the portal (143) to access a loyalty program associated with the consumer account (146) or a registration program.
In other embodiments, the advertisements can also be presented via other media channels which may not involve a transaction processed by the transaction handler (103). For example, the advertisements can be presented on publications or announcements (e.g., newspapers, magazines, books, directories, radio broadcasts, television, digital signage, etc., which may be in an electronic form, or in a printed or painted form). The advertisements may be presented on paper, on websites, on billboards, on digital signs, or on audio portals.
In one embodiment, the transaction handler (103) purchases the rights to use the media channels from the owner or operators of the media channels and uses the media channels as advertisement spaces. For example, white spaces at a point of interaction (e.g., 107) with customers for transactions processed by the transaction handler (103) can be used to deliver advertisements relevant to the customers conducting the transactions; and the advertisement can be selected based at least in part on the intelligence information derived from the accumulated transaction data (109) and/or the context at the point of interaction (107) and/or the transaction terminal (105).
In general, a point of interaction (e.g., 107) may or may not be capable of receiving inputs from the customers, and may or may not co-located with a transaction terminal (e.g., 105) that initiates the transactions. The white spaces for presenting the advertisement on the point of interaction (107) may be on a portion of a geographical display space (e.g., on a screen), or on a temporal space (e.g., in an audio stream).
In one embodiment, the point of interaction (107) may be used to primarily to access services not provided by the transaction handler (103), such as services provided by a search engine, a social networking website, an online marketplace, a blog, a news site, a television program provider, a radio station, a satellite, a publisher, etc.
In one embodiment, a consumer device is used as the point of interaction (107), which may be a non-portable consumer device or a portable computing device. The consumer device is to provide media content to the user (101) and may receive input from the user (101).
Examples of non-portable consumer devices include a computer terminal, a television set, a personal computer, a set-top box, or the like. Examples of portable consumer devices include a portable computer, a cellular phone, a personal digital assistant (PDA), a pager, a security card, a wireless terminal, or the like. The consumer device may be implemented as a data processing system as illustrated in
In one embodiment, the consumer device includes an account identification device (141). For example, a smart card used as an account identification device (141) is integrated with a mobile phone, or a personal digital assistant (PDA).
In one embodiment, the point of interaction (107) is integrated with a transaction terminal (105). For example, a self-service checkout terminal includes a touch pad to interact with the user (101); and an ATM machine includes a user interface subsystem to interact with the user (101).
Hardware
In one embodiment, a computing apparatus is configured to include some of the components of systems illustrated in various figures, such as the transaction handler (103), the profile generator (121), the media controller (115), the portal (143), the profile selector (129), the advertisement selector (133), the user tracker (113), the correlator, and their associated storage devices, such as the data warehouse (149).
In one embodiment, at least some of the components such as the transaction handler (103), the transaction terminal (105), the point of interaction (107), the user tracker (113), the media controller (115), the correlator (117), the profile generator (121), the profile selector (129), the advertisement selector (133), the portal (143), the issuer processor (145), the acquirer processor (147), and the account identification device (141), can be implemented as a computer system, such as a data processing system (170) illustrated in
Further, the data illustrated in the figures, such as transaction data (109), account data (111), transaction profiles (127), and advertisement data (135), can be stored in storage devices of one or more computers accessible to the corresponding components. For example, the transaction data (109) can be stored in the data warehouse (149) that can be implemented as a data processing system illustrated in
In one embodiment, the transaction handler (103) is a payment processing system, or a payment card processor, such as a card processor for credit cards, debit cards, etc.
In
In one embodiment, the inter-connect (171) interconnects the microprocessor(s) (173) and the memory (167) together and also interconnects them to input/output (I/O) device(s) (175) via I/O controller(s) (177). I/O devices (175) may include a display device and/or peripheral devices, such as mice, keyboards, modems, network interfaces, printers, scanners, video cameras and other devices known in the art. In one embodiment, when the data processing system is a server system, some of the I/O devices (175), such as printers, scanners, mice, and/or keyboards, are optional.
In one embodiment, the inter-connect (171) includes one or more buses connected to one another through various bridges, controllers and/or adapters. In one embodiment the I/O controllers (177) include a USB (Universal Serial Bus) adapter for controlling USB peripherals, and/or an IEEE-1394 bus adapter for controlling IEEE-1394 peripherals.
In one embodiment, the memory (167) includes one or more of: ROM (Read Only Memory), volatile RAM (Random Access Memory), and non-volatile memory, such as hard drive, flash memory, etc.
Volatile RAM is typically implemented as dynamic RAM (DRAM) which requires power continually in order to refresh or maintain the data in the memory. Non-volatile memory is typically a magnetic hard drive, a magnetic optical drive, an optical drive (e.g., a DVD RAM), or other type of memory system which maintains data even after power is removed from the system. The non-volatile memory may also be a random access memory.
The non-volatile memory can be a local device coupled directly to the rest of the components in the data processing system. A non-volatile memory that is remote from the system, such as a network storage device coupled to the data processing system through a network interface such as a modem or Ethernet interface, can also be used.
In this description, some functions and operations are described as being performed by or caused by software code to simplify description. However, such expressions are also used to specify that the functions result from execution of the code/instructions by a processor, such as a microprocessor.
Alternatively, or in combination, the functions and operations as described here can be implemented using special purpose circuitry, with or without software instructions, such as using Application-Specific Integrated Circuit (ASIC) or Field-Programmable Gate Array (FPGA). Embodiments can be implemented using hardwired circuitry without software instructions, or in combination with software instructions. Thus, the techniques are limited neither to any specific combination of hardware circuitry and software, nor to any particular source for the instructions executed by the data processing system.
While one embodiment can be implemented in fully functioning computers and computer systems, various embodiments are capable of being distributed as a computing product in a variety of forms and are capable of being applied regardless of the particular type of machine or computer-readable media used to actually effect the distribution.
At least some aspects disclosed can be embodied, at least in part, in software. That is, the techniques may be carried out in a computer system or other data processing system in response to its processor, such as a microprocessor, executing sequences of instructions contained in a memory, such as ROM, volatile RAM, non-volatile memory, cache or a remote storage device.
Routines executed to implement the embodiments may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically include one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processors in a computer, cause the computer to perform operations necessary to execute elements involving the various aspects.
A machine readable medium can be used to store software and data which when executed by a data processing system causes the system to perform various methods. The executable software and data may be stored in various places including for example ROM, volatile RAM, non-volatile memory and/or cache. Portions of this software and/or data may be stored in any one of these storage devices. Further, the data and instructions can be obtained from centralized servers or peer to peer networks. Different portions of the data and instructions can be obtained from different centralized servers and/or peer to peer networks at different times and in different communication sessions or in a same communication session. The data and instructions can be obtained in entirety prior to the execution of the applications. Alternatively, portions of the data and instructions can be obtained dynamically, just in time, when needed for execution. Thus, it is not required that the data and instructions be on a machine readable medium in entirety at a particular instance of time.
Examples of computer-readable media include but are not limited to recordable and non-recordable type media such as volatile and non-volatile memory devices, read only memory (ROM), random access memory (RAM), flash memory devices, floppy and other removable disks, magnetic disk storage media, optical storage media (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks (DVDs), etc.), among others. The computer-readable media may store the instructions.
The instructions may also be embodied in digital and analog communication links for electrical, optical, acoustical or other forms of propagated signals, such as carrier waves, infrared signals, digital signals, etc. However, propagated signals, such as carrier waves, infrared signals, digital signals, etc. are not tangible machine readable medium and are not configured to store instructions.
In general, a machine readable medium includes any mechanism that provides (i.e., stores and/or transmits) information in a form accessible by a machine (e.g., a computer, network device, personal digital assistant, manufacturing tool, any device with a set of one or more processors, etc.).
In various embodiments, hardwired circuitry may be used in combination with software instructions to implement the techniques. Thus, the techniques are neither limited to any specific combination of hardware circuitry and software nor to any particular source for the instructions executed by the data processing system.
Other Aspects
The description and drawings are illustrative and are not to be construed as limiting. The present disclosure is illustrative of inventive features to enable a person skilled in the art to make and use the techniques. Various features, as described herein, should be used in compliance with all current and future rules, laws and regulations related to privacy, security, permission, consent, authorization, and others. Numerous specific details are described to provide a thorough understanding. However, in certain instances, well known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure are not necessarily references to the same embodiment; and, such references mean at least one.
The use of headings herein is merely provided for ease of reference, and shall not be interpreted in any way to limit this disclosure or the following claims.
Reference to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, and are not necessarily all referring to separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by one embodiment and not by others. Similarly, various requirements are described which may be requirements for one embodiment but not other embodiments. Unless excluded by explicit description and/or apparent incompatibility, any combination of various features described in this description is also included here. For example, the features described above in connection with “in one embodiment” or “in some embodiments” can be all optionally included in one implementation, except where the dependency of certain features on other features, as apparent from the description, may limit the options of excluding selected features from the implementation, and incompatibility of certain features with other features, as apparent from the description, may limit the options of including selected features together in the implementation.
The disclosures of the above discussed patent documents are hereby incorporated herein by reference.
In the foregoing specification, the disclosure has been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.
This application is a continuation of U.S. patent application Ser. No. 14/877,126, filed Oct. 7, 2015, which claims the benefit of U.S. Provisional Patent Application No. 62/068,230, filed Oct. 24, 2014, the disclosures of which are hereby incorporated by reference in their entirety. The present application relates to U.S. Pat. App. Pub. No. 2014/0129313, entitled “Systems and Methods to Facilitate an Offer Campaign based on Transactions with Different Merchants”, U.S. Pat. App. Pub. No. 2012/0078697, entitled “Systems and Methods to Program Operations for Interaction with Users,” U.S. Pat. App. Pub. No. 2012/0072997, entitled “Systems and Methods to Modify Interaction Rules during Run Time,” U.S. Pat. App. Pub. No. 2012/0066064, entitled “Systems and Methods to Provide Real-Time Offers via a Cooperative Database,” the entire disclosures of which applications are hereby incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4613904 | Lurie | Sep 1986 | A |
| 5401946 | Neinblatt | Mar 1995 | A |
| 5473143 | Vak et al. | Dec 1995 | A |
| 5592560 | Deaton et al. | Jan 1997 | A |
| 5604921 | Alanara | Feb 1997 | A |
| 5621812 | Deaton et al. | Apr 1997 | A |
| 5638457 | Deaton et al. | Jun 1997 | A |
| 5684990 | Boothby | Nov 1997 | A |
| 5687322 | Deaton et al. | Nov 1997 | A |
| 5710886 | Christensen et al. | Jan 1998 | A |
| 5745036 | Clare | Apr 1998 | A |
| 5870030 | DeLuca et al. | Feb 1999 | A |
| 5923016 | Fredregill et al. | Jul 1999 | A |
| 5924080 | Johnson | Jul 1999 | A |
| 5974396 | Anderson et al. | Oct 1999 | A |
| 6014635 | Harris et al. | Jan 2000 | A |
| 6035280 | Christensen | Mar 2000 | A |
| 6067529 | Ray et al. | May 2000 | A |
| 6070147 | Harms et al. | May 2000 | A |
| 6119101 | Peckover | Sep 2000 | A |
| 6216129 | Eldering | Apr 2001 | B1 |
| 6222914 | McMullin | Apr 2001 | B1 |
| 6282522 | Davis et al. | Aug 2001 | B1 |
| 6285983 | Jenkins | Sep 2001 | B1 |
| 6292786 | Deaton et al. | Sep 2001 | B1 |
| 6298330 | Gardenswartz et al. | Oct 2001 | B1 |
| 6307958 | Deaton et al. | Oct 2001 | B1 |
| 6313732 | DeLuca et al. | Nov 2001 | B1 |
| 6318631 | Halperin | Nov 2001 | B1 |
| 6318911 | Kitahara | Nov 2001 | B1 |
| 6321201 | Dahl | Nov 2001 | B1 |
| 6332126 | Peirce et al. | Dec 2001 | B1 |
| 6334108 | Deaton et al. | Dec 2001 | B1 |
| 6334110 | Walter et al. | Dec 2001 | B1 |
| 6377935 | Deaton et al. | Apr 2002 | B1 |
| 6405174 | Walker | Jun 2002 | B1 |
| 6505046 | Baker | Jan 2003 | B1 |
| 6505168 | Rothman et al. | Jan 2003 | B1 |
| 6519571 | Guheen et al. | Feb 2003 | B1 |
| 6578006 | Saito et al. | Jun 2003 | B1 |
| 6606745 | Maggio | Aug 2003 | B2 |
| 6647257 | Owensby | Nov 2003 | B2 |
| 6647269 | Hendrey et al. | Nov 2003 | B2 |
| 6685093 | Challa et al. | Feb 2004 | B2 |
| 6736322 | Gobburu et al. | May 2004 | B2 |
| 6749120 | Hung et al. | Jun 2004 | B2 |
| 6775539 | Deshpande | Aug 2004 | B2 |
| 6856992 | Britton et al. | Feb 2005 | B2 |
| 6877665 | Challa et al. | Apr 2005 | B2 |
| 6901406 | Nabe et al. | May 2005 | B2 |
| 6912398 | Domnitz | Jun 2005 | B1 |
| 6922686 | Okamoto et al. | Jul 2005 | B2 |
| 6938022 | Singhal | Aug 2005 | B1 |
| 6941376 | Mitchell et al. | Sep 2005 | B2 |
| 6996560 | Choi et al. | Feb 2006 | B1 |
| 7003476 | Samra et al. | Feb 2006 | B1 |
| 7013286 | Aggarwal et al. | Mar 2006 | B1 |
| 7024374 | Day et al. | Apr 2006 | B1 |
| 7024409 | Iyengar | Apr 2006 | B2 |
| 7028906 | Challa et al. | Apr 2006 | B2 |
| 7035855 | Kilger et al. | Apr 2006 | B1 |
| 7039599 | Merriman et al. | May 2006 | B2 |
| 7039600 | Meek et al. | May 2006 | B1 |
| 7062510 | Eldering | Jun 2006 | B1 |
| 7072847 | Ulenas et al. | Jul 2006 | B2 |
| 7107249 | Dively et al. | Sep 2006 | B2 |
| 7120590 | Eisen et al. | Oct 2006 | B1 |
| 7158943 | van der Riet | Jan 2007 | B2 |
| 7158955 | Diveley et al. | Jan 2007 | B2 |
| 7165037 | Lazarus et al. | Jan 2007 | B2 |
| 7177822 | Mahmood et al. | Feb 2007 | B2 |
| 7181412 | Fulgoni et al. | Feb 2007 | B1 |
| 7194422 | St. John Killick | Mar 2007 | B1 |
| 7225142 | Apte et al. | May 2007 | B1 |
| 7257545 | Hung | Aug 2007 | B1 |
| 7260837 | Abraham et al. | Aug 2007 | B2 |
| 7264152 | Tsuei et al. | Sep 2007 | B2 |
| 7269578 | Sweeney | Sep 2007 | B2 |
| 7299194 | Manganaris et al. | Nov 2007 | B1 |
| 7308254 | Rissanen | Dec 2007 | B1 |
| 7328169 | Temares et al. | Feb 2008 | B2 |
| 7330110 | Heintzman et al. | Feb 2008 | B1 |
| 7337127 | Smith et al. | Feb 2008 | B1 |
| 7340438 | Nordman et al. | Mar 2008 | B2 |
| 7360251 | Spalink et al. | Apr 2008 | B2 |
| 7373311 | Lambert et al. | May 2008 | B2 |
| 7395212 | Juneau et al. | Jul 2008 | B2 |
| 7424439 | Fayyad et al. | Sep 2008 | B1 |
| 7424441 | George et al. | Sep 2008 | B2 |
| 7444658 | Matz et al. | Oct 2008 | B1 |
| 7467106 | Evine et al. | Dec 2008 | B1 |
| 7490052 | Kilger et al. | Feb 2009 | B2 |
| 7493655 | Brown | Feb 2009 | B2 |
| 7526485 | Hagan et al. | Apr 2009 | B2 |
| 7529687 | Phan | May 2009 | B1 |
| 7533038 | Blume et al. | May 2009 | B2 |
| 7536360 | Stolfo et al. | May 2009 | B2 |
| 7552069 | Kepecs | Jun 2009 | B2 |
| 7562030 | Shapira et al. | Jul 2009 | B1 |
| 7578435 | Suk | Aug 2009 | B2 |
| 7613628 | Ariff et al. | Nov 2009 | B2 |
| 7668785 | Hammad | Feb 2010 | B1 |
| 7729977 | Xiao et al. | Jun 2010 | B2 |
| 7779160 | Symonds et al. | Aug 2010 | B1 |
| 7792518 | Trioano et al. | Sep 2010 | B2 |
| 7831470 | Walker | Nov 2010 | B1 |
| 7844512 | Richards et al. | Nov 2010 | B2 |
| 7937291 | Carlson et al. | May 2011 | B2 |
| 7970705 | Patterson | Jun 2011 | B2 |
| 8019685 | Patterson | Sep 2011 | B2 |
| 8099318 | Moukas et al. | Jan 2012 | B2 |
| 8103588 | Patterson | Jan 2012 | B2 |
| 8229819 | Ransom et al. | Jul 2012 | B2 |
| 8311845 | Vengroff et al. | Nov 2012 | B2 |
| 8341038 | Rolf et al. | Dec 2012 | B1 |
| 8478692 | Carlson et al. | Jul 2013 | B2 |
| 8504692 | Henderson | Aug 2013 | B1 |
| 8556169 | Maw | Oct 2013 | B2 |
| 20010027413 | Bhutta | Oct 2001 | A1 |
| 20010049620 | Blasko | Dec 2001 | A1 |
| 20010054003 | Chien et al. | Dec 2001 | A1 |
| 20020002597 | Morrell, Jr. | Jan 2002 | A1 |
| 20020004733 | Addante | Jan 2002 | A1 |
| 20020004754 | Garedenswartz et al. | Jan 2002 | A1 |
| 20020026348 | Fowler et al. | Feb 2002 | A1 |
| 20020042738 | Srinivasan et al. | Apr 2002 | A1 |
| 20020046187 | Vargas et al. | Apr 2002 | A1 |
| 20020053076 | Landesmann | May 2002 | A1 |
| 20020055933 | Feathers | May 2002 | A1 |
| 20020059100 | Shore | May 2002 | A1 |
| 20020060246 | Gobburu et al. | May 2002 | A1 |
| 20020065713 | Awada et al. | May 2002 | A1 |
| 20020065723 | Anderson et al. | May 2002 | A1 |
| 20020070278 | Hung et al. | Jun 2002 | A1 |
| 20020077871 | Udelhoven et al. | Jun 2002 | A1 |
| 20020082918 | Warwick | Jun 2002 | A1 |
| 20020091569 | Kitaura et al. | Jul 2002 | A1 |
| 20020099649 | Lee et al. | Jul 2002 | A1 |
| 20020102993 | Hendrey et al. | Aug 2002 | A1 |
| 20020103703 | Spetalnick | Aug 2002 | A1 |
| 20020112159 | Platt | Aug 2002 | A1 |
| 20020123928 | Eldering et al. | Sep 2002 | A1 |
| 20020128916 | Beinecke | Sep 2002 | A1 |
| 20020138346 | Kodaka et al. | Sep 2002 | A1 |
| 20020174013 | Freeman et al. | Nov 2002 | A1 |
| 20030046153 | Robibero | Mar 2003 | A1 |
| 20030047602 | Tida et al. | Mar 2003 | A1 |
| 20030058261 | Challa et al. | Mar 2003 | A1 |
| 20030093314 | Leung et al. | May 2003 | A1 |
| 20030191832 | Satyavolu et al. | Oct 2003 | A1 |
| 20030212595 | Antonucci | Nov 2003 | A1 |
| 20030225618 | Hessburg et al. | Dec 2003 | A1 |
| 20030230630 | Whipple et al. | Dec 2003 | A1 |
| 20030233251 | Haskell et al. | Dec 2003 | A1 |
| 20040019518 | Abraham et al. | Jan 2004 | A1 |
| 20040054575 | Marshall | Mar 2004 | A1 |
| 20040054581 | Redford et al. | Mar 2004 | A1 |
| 20040054591 | Spaeth et al. | Mar 2004 | A1 |
| 20040093512 | Sample | May 2004 | A1 |
| 20040122735 | Meshkin | Jun 2004 | A1 |
| 20040144839 | Warwick | Jul 2004 | A1 |
| 20040148224 | Gauthier et al. | Jul 2004 | A1 |
| 20040167815 | DeLaHunt | Aug 2004 | A1 |
| 20040193685 | Proehl | Sep 2004 | A1 |
| 20040225509 | Andre | Nov 2004 | A1 |
| 20040225603 | Allen et al. | Nov 2004 | A1 |
| 20040267611 | Hoerenz | Dec 2004 | A1 |
| 20050055275 | Newman et al. | Mar 2005 | A1 |
| 20050071225 | Bortolin et al. | Mar 2005 | A1 |
| 20050071227 | Hammad et al. | Mar 2005 | A1 |
| 20050071235 | Nguyen et al. | Mar 2005 | A1 |
| 20050075932 | Mankoff | Apr 2005 | A1 |
| 20050125342 | Schiff | Jun 2005 | A1 |
| 20050131761 | Trika et al. | Jun 2005 | A1 |
| 20050133590 | Rettenmyer et al. | Jun 2005 | A1 |
| 20050144074 | Fredregill et al. | Jun 2005 | A1 |
| 20050160002 | Roetter et al. | Jul 2005 | A1 |
| 20050210240 | Barron | Sep 2005 | A1 |
| 20050210387 | Alagappan et al. | Sep 2005 | A1 |
| 20050216334 | Mehrabani-Farsi | Sep 2005 | A1 |
| 20050216823 | Petersen et al. | Sep 2005 | A1 |
| 20050240474 | Li | Oct 2005 | A1 |
| 20050242179 | Warwick | Nov 2005 | A1 |
| 20050267812 | Jensen et al. | Dec 2005 | A1 |
| 20060002189 | Berkman | Jan 2006 | A1 |
| 20060004613 | Roller et al. | Jan 2006 | A1 |
| 20060053056 | Alspach-Goss et al. | Mar 2006 | A1 |
| 20060085260 | Yamagishi | Apr 2006 | A1 |
| 20060085263 | Greer et al. | Apr 2006 | A1 |
| 20060111967 | Forbes | May 2006 | A1 |
| 20060122921 | Comerford et al. | Jun 2006 | A1 |
| 20060131390 | Kim | Jun 2006 | A1 |
| 20060143071 | Hofmann | Jun 2006 | A1 |
| 20060143075 | Carr et al. | Jun 2006 | A1 |
| 20060161527 | Dwork et al. | Jul 2006 | A1 |
| 20060167818 | Wentker et al. | Jul 2006 | A1 |
| 20060178957 | LeClaire | Aug 2006 | A1 |
| 20060190337 | Ayers et al. | Aug 2006 | A1 |
| 20060212900 | Ismail et al. | Sep 2006 | A1 |
| 20060235746 | Hammond et al. | Oct 2006 | A1 |
| 20060289631 | Stretch et al. | Dec 2006 | A1 |
| 20060293948 | Weinblatt | Dec 2006 | A1 |
| 20060293959 | Hogan | Dec 2006 | A1 |
| 20070022048 | Kingsborough et al. | Jan 2007 | A1 |
| 20070038516 | Apple et al. | Feb 2007 | A1 |
| 20070045405 | Rothschild | Mar 2007 | A1 |
| 20070055597 | Patel et al. | Mar 2007 | A1 |
| 20070067267 | Ives | Mar 2007 | A1 |
| 20070067297 | Kublickis | Mar 2007 | A1 |
| 20070084917 | Fajkowski | Apr 2007 | A1 |
| 20070100691 | Patterson | May 2007 | A1 |
| 20070106556 | Edwards et al. | May 2007 | A1 |
| 20070124201 | Hu et al. | May 2007 | A1 |
| 20070136131 | Mankoff | Jun 2007 | A1 |
| 20070156470 | Granucci et al. | Jul 2007 | A1 |
| 20070162377 | Williams | Jul 2007 | A1 |
| 20070174295 | Abraham et al. | Jul 2007 | A1 |
| 20070192121 | Routson | Aug 2007 | A1 |
| 20070192122 | Routson et al. | Aug 2007 | A1 |
| 20070208671 | Brown et al. | Sep 2007 | A1 |
| 20070219865 | Leining | Sep 2007 | A1 |
| 20070219866 | Wolf et al. | Sep 2007 | A1 |
| 20070226056 | Belanger et al. | Sep 2007 | A1 |
| 20070226061 | Chen et al. | Sep 2007 | A1 |
| 20070239521 | Khadpe et al. | Oct 2007 | A1 |
| 20070239532 | Benson et al. | Oct 2007 | A1 |
| 20070241189 | Slavin et al. | Oct 2007 | A1 |
| 20070244741 | Blume et al. | Oct 2007 | A1 |
| 20070260736 | Miller | Nov 2007 | A1 |
| 20070265920 | Bistriceanu et al. | Nov 2007 | A1 |
| 20070265921 | Rempe et al. | Nov 2007 | A1 |
| 20070265923 | Krassner et al. | Nov 2007 | A1 |
| 20070282681 | Shubert et al. | Dec 2007 | A1 |
| 20080004884 | Flake et al. | Jan 2008 | A1 |
| 20080021784 | Hessburg et al. | Jan 2008 | A1 |
| 20080021785 | Hessburg et al. | Jan 2008 | A1 |
| 20080027810 | Lemer et al. | Jan 2008 | A1 |
| 20080040229 | Gholston | Feb 2008 | A1 |
| 20080040270 | Buchheit et al. | Feb 2008 | A1 |
| 20080059302 | Fordyce III et al. | Mar 2008 | A1 |
| 20080059303 | Fordyce | Mar 2008 | A1 |
| 20080059306 | Fordyce et al. | Mar 2008 | A1 |
| 20080059307 | Fordyce III et al. | Mar 2008 | A1 |
| 20080071587 | Granucci et al. | Mar 2008 | A1 |
| 20080071680 | Sheets | Mar 2008 | A1 |
| 20080077487 | Davis et al. | Mar 2008 | A1 |
| 20080082393 | Ozzie et al. | Apr 2008 | A1 |
| 20080082418 | Fordyce et al. | Apr 2008 | A1 |
| 20080097801 | MacLellan et al. | Apr 2008 | A1 |
| 20080103887 | Oldham et al. | May 2008 | A1 |
| 20080103968 | Bies et al. | May 2008 | A1 |
| 20080109335 | Keohane et al. | May 2008 | A1 |
| 20080120182 | Arnold et al. | May 2008 | A1 |
| 20080120214 | Steele et al. | May 2008 | A1 |
| 20080120218 | Reid et al. | May 2008 | A1 |
| 20080133345 | Cordery et al. | Jun 2008 | A1 |
| 20080133351 | White | Jun 2008 | A1 |
| 20080133366 | Evans et al. | Jun 2008 | A1 |
| 20080134228 | Dion et al. | Jun 2008 | A1 |
| 20080147496 | Bal et al. | Jun 2008 | A1 |
| 20080150678 | Giobbi et al. | Jun 2008 | A1 |
| 20080154654 | Niessen et al. | Jun 2008 | A1 |
| 20080154703 | Flake et al. | Jun 2008 | A1 |
| 20080154704 | Flake et al. | Jun 2008 | A1 |
| 20080154727 | Carlson | Jun 2008 | A1 |
| 20080162258 | Kala et al. | Jul 2008 | A1 |
| 20080162269 | Gilbert | Jul 2008 | A1 |
| 20080163257 | Carlson et al. | Jul 2008 | A1 |
| 20080167000 | Wentker et al. | Jul 2008 | A1 |
| 20080167961 | Wentker et al. | Jul 2008 | A1 |
| 20080167991 | Carlson et al. | Jul 2008 | A1 |
| 20080167992 | Kokernak et al. | Jul 2008 | A1 |
| 20080177602 | Sopher et al. | Jul 2008 | A1 |
| 20080183480 | Carlson et al. | Jul 2008 | A1 |
| 20080184117 | Alsbury et al. | Jul 2008 | A1 |
| 20080195465 | Redmond et al. | Aug 2008 | A1 |
| 20080195466 | Wright | Aug 2008 | A1 |
| 20080195473 | Laramy et al. | Aug 2008 | A1 |
| 20080201226 | Carlson et al. | Aug 2008 | A1 |
| 20080201472 | Bistriceanu et al. | Aug 2008 | A1 |
| 20080215429 | Ramer et al. | Sep 2008 | A1 |
| 20080215436 | Roberts | Sep 2008 | A1 |
| 20080217397 | Degliantoni et al. | Sep 2008 | A1 |
| 20080221972 | Megdal et al. | Sep 2008 | A1 |
| 20080222038 | Eden et al. | Sep 2008 | A1 |
| 20080228563 | Zellner et al. | Sep 2008 | A1 |
| 20080228582 | Fordyce et al. | Sep 2008 | A1 |
| 20080235091 | Holliday | Sep 2008 | A1 |
| 20080235243 | Lee et al. | Sep 2008 | A1 |
| 20080242317 | Abhyanker | Oct 2008 | A1 |
| 20080248815 | Busch | Oct 2008 | A1 |
| 20080262915 | Gojkovic et al. | Oct 2008 | A1 |
| 20080262935 | Baumgartner et al. | Oct 2008 | A1 |
| 20080300973 | DeWitt et al. | Dec 2008 | A1 |
| 20080313011 | Rose et al. | Dec 2008 | A1 |
| 20080318559 | Porco | Dec 2008 | A1 |
| 20080319843 | Moser et al. | Dec 2008 | A1 |
| 20080319847 | Shepard | Dec 2008 | A1 |
| 20080319889 | Hammad | Dec 2008 | A1 |
| 20080320512 | Knight | Dec 2008 | A1 |
| 20090006183 | Paintin et al. | Jan 2009 | A1 |
| 20090006203 | Fordyce et al. | Jan 2009 | A1 |
| 20090006363 | Canny et al. | Jan 2009 | A1 |
| 20090018895 | Weinblatt et al. | Jan 2009 | A1 |
| 20090030793 | Fordyce, III | Jan 2009 | A1 |
| 20090043593 | Herbrich et al. | Feb 2009 | A1 |
| 20090070207 | Engel et al. | Mar 2009 | A1 |
| 20090070219 | D'Angelo et al. | Mar 2009 | A1 |
| 20090070225 | Matz et al. | Mar 2009 | A1 |
| 20090076896 | DeWitt et al. | Mar 2009 | A1 |
| 20090076925 | DeWitt et al. | Mar 2009 | A1 |
| 20090081990 | Granucci et al. | Mar 2009 | A1 |
| 20090112703 | Brown | Apr 2009 | A1 |
| 20090112721 | Hammad et al. | Apr 2009 | A1 |
| 20090119160 | Woda et al. | May 2009 | A1 |
| 20090119167 | Kendall et al. | May 2009 | A1 |
| 20090119170 | Hammad et al. | May 2009 | A1 |
| 20090132347 | Anderson et al. | May 2009 | A1 |
| 20090132365 | Gruenhagen et al. | May 2009 | A1 |
| 20090132366 | Lam et al. | May 2009 | A1 |
| 20090144201 | Gierkink et al. | Jun 2009 | A1 |
| 20090150211 | Bayne | Jun 2009 | A1 |
| 20090157511 | Spinnell et al. | Jun 2009 | A1 |
| 20090171747 | Lanning et al. | Jul 2009 | A1 |
| 20090172551 | Kane et al. | Jul 2009 | A1 |
| 20090172728 | Shkedi et al. | Jul 2009 | A1 |
| 20090182634 | Park et al. | Jul 2009 | A1 |
| 20090192882 | Narahashi et al. | Jul 2009 | A1 |
| 20090203387 | Wold et al. | Aug 2009 | A1 |
| 20090216579 | Zen et al. | Aug 2009 | A1 |
| 20090216616 | Wang et al. | Aug 2009 | A1 |
| 20090222323 | Kelly et al. | Sep 2009 | A1 |
| 20090222348 | Ransom et al. | Sep 2009 | A1 |
| 20090234708 | Heiser et al. | Sep 2009 | A1 |
| 20090234711 | Ramer et al. | Sep 2009 | A1 |
| 20090234737 | Sarelson et al. | Sep 2009 | A1 |
| 20090248496 | Hueter et al. | Oct 2009 | A1 |
| 20090248497 | Hueter | Oct 2009 | A1 |
| 20090248511 | Mehta et al. | Oct 2009 | A1 |
| 20090249384 | Fang et al. | Oct 2009 | A1 |
| 20090254414 | Schwarz et al. | Oct 2009 | A1 |
| 20090259518 | Harvey et al. | Oct 2009 | A1 |
| 20090271262 | Hammad | Oct 2009 | A1 |
| 20090271275 | Regmi et al. | Oct 2009 | A1 |
| 20090271305 | Lal et al. | Oct 2009 | A1 |
| 20090271327 | Lal et al. | Oct 2009 | A1 |
| 20090276304 | Dorr | Nov 2009 | A1 |
| 20090276305 | Clopp | Nov 2009 | A1 |
| 20090299941 | McColgan et al. | Dec 2009 | A1 |
| 20090327151 | Carlson et al. | Dec 2009 | A1 |
| 20100017275 | Carlson et al. | Jan 2010 | A1 |
| 20100030688 | Patterson | Feb 2010 | A1 |
| 20100049588 | Debow | Feb 2010 | A1 |
| 20100049620 | Debow | Feb 2010 | A1 |
| 20100057549 | Boal | Mar 2010 | A1 |
| 20100057553 | Ameiss et al. | Mar 2010 | A1 |
| 20100082420 | Trifiletti et al. | Apr 2010 | A1 |
| 20100106568 | Grimes | Apr 2010 | A1 |
| 20100106569 | Grimes | Apr 2010 | A1 |
| 20100106570 | Radu et al. | Apr 2010 | A1 |
| 20100114677 | Carlson et al. | May 2010 | A1 |
| 20100114683 | Wessels et al. | May 2010 | A1 |
| 20100114686 | Carlson et al. | May 2010 | A1 |
| 20100125490 | Kiciman et al. | May 2010 | A1 |
| 20100125737 | Kang | May 2010 | A1 |
| 20100138838 | Lin et al. | Jun 2010 | A1 |
| 20100145786 | Fordyce III et al. | Jun 2010 | A1 |
| 20100161404 | Taylor et al. | Jun 2010 | A1 |
| 20100174596 | Gilman et al. | Jul 2010 | A1 |
| 20100174623 | McPhie et al. | Jul 2010 | A1 |
| 20100176193 | Maw | Jul 2010 | A1 |
| 20100211694 | Razmov et al. | Aug 2010 | A1 |
| 20100268588 | Lal et al. | Oct 2010 | A1 |
| 20100274566 | Carlson | Oct 2010 | A1 |
| 20100274625 | Carlson | Oct 2010 | A1 |
| 20100274627 | Carlson | Oct 2010 | A1 |
| 20100274653 | Hammad | Oct 2010 | A1 |
| 20100274691 | Hammad et al. | Oct 2010 | A1 |
| 20100274853 | Carlson et al. | Oct 2010 | A1 |
| 20100280880 | Faith et al. | Nov 2010 | A1 |
| 20100280881 | Faith et al. | Nov 2010 | A1 |
| 20100280882 | Faith et al. | Nov 2010 | A1 |
| 20100280914 | Carlson | Nov 2010 | A1 |
| 20100280927 | Faith et al. | Nov 2010 | A1 |
| 20100280950 | Faith et al. | Nov 2010 | A1 |
| 20100306029 | Jolley | Dec 2010 | A1 |
| 20100306032 | Jolley | Dec 2010 | A1 |
| 20100312692 | Teicher | Dec 2010 | A1 |
| 20100325047 | Carlson et al. | Dec 2010 | A1 |
| 20100325048 | Carlson et al. | Dec 2010 | A1 |
| 20110016050 | Evans | Jan 2011 | A1 |
| 20110022448 | Strock et al. | Jan 2011 | A1 |
| 20110029363 | Gillenson et al. | Feb 2011 | A1 |
| 20110029440 | Motoyama et al. | Feb 2011 | A1 |
| 20110029595 | Thayer et al. | Feb 2011 | A1 |
| 20110054981 | Faith et al. | Mar 2011 | A1 |
| 20110066483 | Salmon et al. | Mar 2011 | A1 |
| 20110087531 | Winters et al. | Apr 2011 | A1 |
| 20110125509 | Lidstrom et al. | May 2011 | A1 |
| 20110125565 | MacIlwaine et al. | May 2011 | A1 |
| 20110153438 | Dragt | Jun 2011 | A1 |
| 20110161150 | Steffens et al. | Jun 2011 | A1 |
| 20110202402 | Fowler et al. | Aug 2011 | A1 |
| 20110208575 | Bansal et al. | Aug 2011 | A1 |
| 20110231235 | MacIlwaine et al. | Sep 2011 | A1 |
| 20110231258 | Winters | Sep 2011 | A1 |
| 20110238483 | Yoo et al. | Sep 2011 | A1 |
| 20110270719 | Hollars et al. | Nov 2011 | A1 |
| 20110288906 | Thomas et al. | Nov 2011 | A1 |
| 20110288918 | Cervenka et al. | Nov 2011 | A1 |
| 20110288922 | Thomas et al. | Nov 2011 | A1 |
| 20110288924 | Thomas et al. | Nov 2011 | A1 |
| 20110288925 | Thomas et al. | Nov 2011 | A1 |
| 20110295670 | Thomas et al. | Dec 2011 | A1 |
| 20110295671 | Thomas et al. | Dec 2011 | A1 |
| 20110302011 | Yoder et al. | Dec 2011 | A1 |
| 20110307318 | LaPorte et al. | Dec 2011 | A1 |
| 20120030066 | Stringfellow et al. | Feb 2012 | A1 |
| 20120059702 | Yoder et al. | Mar 2012 | A1 |
| 20120066062 | Yoder et al. | Mar 2012 | A1 |
| 20120066064 | Yoder et al. | Mar 2012 | A1 |
| 20120072997 | Carlson et al. | Mar 2012 | A1 |
| 20120078697 | Carlson et al. | Mar 2012 | A1 |
| 20120078699 | Carlson et al. | Mar 2012 | A1 |
| 20120089461 | Greenspan | Apr 2012 | A1 |
| 20120109730 | Yoder et al. | May 2012 | A1 |
| 20120109734 | Fordyce, III et al. | May 2012 | A1 |
| 20120130859 | Wolfe et al. | May 2012 | A1 |
| 20120136704 | Carlson et al. | May 2012 | A1 |
| 20120150609 | Walker et al. | Jun 2012 | A1 |
| 20120185315 | VonDerheide et al. | Jul 2012 | A1 |
| 20120191525 | Singh et al. | Jul 2012 | A1 |
| 20120215637 | Hermann | Aug 2012 | A1 |
| 20120239498 | Ramer et al. | Sep 2012 | A1 |
| 20120244948 | Dhillon et al. | Sep 2012 | A1 |
| 20120259695 | Glassman et al. | Oct 2012 | A1 |
| 20120259842 | Oman et al. | Oct 2012 | A1 |
| 20120271689 | Etheredge et al. | Oct 2012 | A1 |
| 20120271691 | Hammad et al. | Oct 2012 | A1 |
| 20120271697 | Gilman et al. | Oct 2012 | A1 |
| 20120271706 | Ransom et al. | Oct 2012 | A1 |
| 20120278173 | Vaidyanathan et al. | Nov 2012 | A1 |
| 20120290909 | Speirs et al. | Nov 2012 | A1 |
| 20120290950 | Rapaport et al. | Nov 2012 | A1 |
| 20120303425 | Katzin et al. | Nov 2012 | A1 |
| 20120310838 | Harris et al. | Dec 2012 | A1 |
| 20120323664 | Klems | Dec 2012 | A1 |
| 20130006709 | Kosta | Jan 2013 | A1 |
| 20130132205 | Harris | May 2013 | A1 |
| 20130221093 | Patel et al. | Aug 2013 | A1 |
| 20130282461 | Ovick et al. | Oct 2013 | A1 |
| 20140101095 | Van Riel | Apr 2014 | A1 |
| 20140129313 | Rappoport et al. | May 2014 | A1 |
| 20140214671 | DeSilva et al. | Jul 2014 | A1 |
| 20140222533 | Ovick et al. | Aug 2014 | A1 |
| 20140236672 | Yoder et al. | Aug 2014 | A1 |
| 20140324696 | Browne et al. | Oct 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 2821951 | Jan 2015 | EP |
| 2000357204 | Dec 2000 | JP |
| 2001501328 | Jan 2001 | JP |
| 2009501891 | Jan 2009 | JP |
| 5346930 | Nov 2013 | JP |
| 20010096672 | Nov 2001 | KR |
| 20030008894 | Jan 2003 | KR |
| 20040045622 | Jun 2004 | KR |
| 20040107715 | Dec 2004 | KR |
| 20050113156 | Dec 2005 | KR |
| 20070030415 | Mar 2007 | KR |
| 20080002731 | Jan 2008 | KR |
| 20080104398 | Dec 2008 | KR |
| 101024810 | Mar 2011 | KR |
| 20110019887 | Mar 2011 | KR |
| 122505 | Nov 2012 | RU |
| 1999022328 | Dec 1899 | WO |
| 1999050775 | Oct 1999 | WO |
| 2000003328 | Jan 2000 | WO |
| 2000060435 | Oct 2000 | WO |
| 2000062231 | Oct 2000 | WO |
| 2001037183 | May 2001 | WO |
| 2001039023 | May 2001 | WO |
| 2001057758 | Aug 2001 | WO |
| 2001093161 | Dec 2001 | WO |
| 2002005116 | Jan 2002 | WO |
| 2002014985 | Feb 2002 | WO |
| 2002019229 | Mar 2002 | WO |
| 2002042970 | May 2002 | WO |
| 2002071187 | Sep 2002 | WO |
| 2003025695 | Mar 2003 | WO |
| 2003081376 | Oct 2003 | WO |
| 2005001631 | Jan 2005 | WO |
| 2005072382 | Aug 2005 | WO |
| 2005076181 | Aug 2005 | WO |
| 2006028739 | Mar 2006 | WO |
| 2006052444 | May 2006 | WO |
| 2006126205 | Nov 2006 | WO |
| 2007131258 | Nov 2007 | WO |
| 2007136221 | Nov 2007 | WO |
| 2008013945 | Jan 2008 | WO |
| 2008023912 | Feb 2008 | WO |
| 2008055217 | May 2008 | WO |
| 2008064343 | May 2008 | WO |
| 2008067543 | Jun 2008 | WO |
| 2008098004 | Aug 2008 | WO |
| 2008144643 | Nov 2008 | WO |
| 2009144010 | Dec 2009 | WO |
| 2010036915 | Apr 2010 | WO |
| 2010141270 | Dec 2010 | WO |
| 2012040270 | Mar 2012 | WO |
| 2012061758 | May 2012 | WO |
| 2012069803 | May 2012 | WO |
| 2013158861 | Oct 2013 | WO |
| Entry |
|---|
| Griffis, Linking Order Fulfillment Performance to Referrals in Online Retailing: An Empirical Analysis, Journal of business logistics, 2012, vol. 33 (4), p. 279-294. |
| Cashmore, Pete, “YouTube Ads: YouHate Em,” available at http://mashable.com/2009/04/05/youtube-ads-youhate-em/#, Apr. 5, 2009. |
| Credit Card Finder: “Airline Miles Reward Credit Cards”; http://www.plasticrewards.com/airline-miles-reward/, 2009, 2 pages. |
| Credit Card Finder: “Cash Back Reward Credit Cards”; http://www.plasticrewards.com/creditcard/cash-back-reward/, 2009, 3 pages. |
| Credit Card Finder: “Compare Cash Back Credit Cards and Credit Card Offers”; http://www.plasticrewards.com/, 2009, 1 page. |
| Credit Card Finder: “Gas Reward Credit Cards”; http://www.plasticrewards.com/creditcard/gas-reward/, 2009, 3 pages. |
| Credit Card Finder: “Hotel Reward Credit Cards”; http://www.plasticrewards.com/credit-card/hotel-reward/, 2009, 2 pages. |
| Credit Card Finder: “Reward Credit Cards”; http://www.plasticrewards.com/credit-card/reward/, 2009, 3 pages. |
| Credit Card Finder: “Travel Reward Credit Cards”; http://www.plasticrewards.com/credit-card/travel-reward, 2009, 3 pages. |
| CreditCardGuide.com: “Car rebate credit cards”; http://www.creditcardguide.com/car-rebate.html/, 2009, 2 page. |
| CreditCardGuide.com: “Cash Back Credit Cards”; http://www.creditcardguide.com/cashback2.htmll, 2009, 2 pages. |
| CreditCardGuide.com: “Dining and entertainment credit cards”; http://www.creditcardguide.com/dining-entertainment.html/, 2009, 3 pages. |
| CreditCardGuide.com: “Financial reward credit cards”; http://www.creditcardguide.com/financial-reward-credit-cards.html/, 2009, 2 pages. |
| CreditCardGuide.com: “Foundation and charity credit cards”; http://www.creditcardguide.com/foundations-charities.html/, 2009, 3 pages. |
| CreditCardGuide.com: “Gas Rebate Credit Cards”; http://www.creditcardguide.com/gascards.html/, 2009, 2 pages. |
| CreditCardGuide.com: “Sports and outdoor enthusiast credit cards”; http://www.creditcardguide.com/sports-outdoors.html/, 2009, 2 pages. |
| CreditCardGuide.com: “Use Cash Back Credit Cards”; http://www.creditcardguide.com/cashback.html/, 2009, 3 pages. |
| CreditCardGuide.com: “Use home improvement reward credit cards”; http://www.creditcardguide.com/home-improvement-credit-cards.html/, 2009, 2 pages. |
| CreditCardGuide.com: “Use hotel reward credit cards and travel reward credit cards”; http://www.creditcardguide.com/hotel-reward-credit-cards.html/, 2009, 2 pages. |
| CreditCardGuide.com: “Use retail reward credit cards and brand name reward credit cards”; http//www.creditcardguide.com/retail-brand-credit-cards.html/, 2009, 2 pages. |
| CreditCardGuide.com: “Use Reward Credit Cards”; http://www.creditcardguide.com/reward-point-credit-cards.html/, 2009, 3 pages. |
| CreditCardGuide.com: “With Airline Credit Cards, Frequent Flyer credit cards, and Travel Reward Credit Cards”; http://www.creditcardguide.com/airline-frequent-flyer-cards.html/, 2009,4 pages. |
| Li, Wen-Syan, “Knowledge Gathering and Matching in Heterogeneous Databases,” Working Notes of the AAAI Spring Symposium on Information Gathering, pp. 116-1216, Mar. 27, 1995. |
| Mielikäinen, Taneli, “Privacy Problems with Anonymized Transaction Databases,” 7th International Conference on Discovery Science, pp. 219-229, Oct. 2, 2004. |
| Punj, Girish et al. “Cluster Analysis in Marketing Research: Review and Suggestions for Application,” Journal of Marketing Research, vol. 20, pp. 134-148, May 1983. |
| Stubblebine, Unlinkable serial transactions: protocols and applications, 1999, ACM Transactions on Information and System Security vol. 2 Issue Nov. 4, 1999 pp. 354-389. |
| Van Grove, Jennifer, “Are Your Online Video Ads Driving Actual Offline Purchases?”, available at http://mashable.com/2009/05/18/video-impact/#, May 18, 2009. |
| Number | Date | Country | |
|---|---|---|---|
| 20220076257 A1 | Mar 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62068230 | Oct 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14877126 | Oct 2015 | US |
| Child | 17529336 | US |
