Patent Grant
10043196
Field
The present disclosure generally relates to targeting marketing, and more particularly, to methods, systems, and articles of manufacture for targeting ad impressions to customers and consumers based upon spend. The methods, systems, and articles described herein are further directed to the measurement of the effectiveness and relevance of those ad impressions.
Related Art
Businesses frequently store a variety of information relating to the interests and activities of their customers. For example, transaction account companies (e.g., American Express, Visa, Discover, etc.) typically maintain information about the purchasing habits and/or product affinities of their customers. Transaction account issuing companies and payment processors may use this information to target advertisements, promotional offers, discounts, and the like to their customers. Thus, the information that transaction account companies collect about their customers enables a more relevant provision of services to customers.
Although transaction account companies and payment processors often have access to a variety of purchasing information, this information is typically unavailable to merchants. Thus, merchants are unable to incorporate into their marketing efforts data associated with the actual shopping activities of transaction account customers. Merchants are therefore limited, due to an incomplete understanding of the interests of these customers, in their efforts to provide relevant and useful offers and services.
Accordingly, an improved system for understanding the interests and needs of transaction account customers is needed. This system should permit merchants to target marketing and other promotional offers to transaction account customers based on the purchasing activities of those customers. The system should further permit transaction account companies to measure the success and value of the system, particularly from a customer's standpoint. In other words, the system should incorporate an ability to evaluate the actual relevance of advertisements, offers, promotions, and discounts that are served or delivered to customers.
Finally, the system should seek to preserve the privacy of the customers it aims to serve. To this end, the system should incorporate one or more methods for maintaining the anonymity of customers.
The present disclosure includes a system, method, and article of manufacture for targeting ad impressions. In various embodiments, a list of customer records may be transmitted to a service provider system that identifies a matched customer and installs a cookie on a web client associated with the matched customer. The system may further receive a campaign request from a merchant and transmit the campaign request to the service provider system which may add a flag to the cookie based on the campaign request as well as instruct a media buyer system to bid on an ad impression for the matched customer based on the flag. The system may further receive an expenditure associated with the matched customer who received the ad impression and compare the expenditure to an expenditure associated with a customer who did not receive targeted ad impression but fits parameters associated with the campaign request.
In various embodiments, a report showing the results of this comparison may be generated and provided to a merchant associated with the campaign request. A report showing a click through associated with matched customers who received targeted ad impressions may also be generated. A click through may be shown in comparison to a click through associated with customers who did not receive targeted ad impressions
In various embodiments, the system, method, and/or article of manufacture may further permit, via the web client, the matched customer who received the targeted ad impression to select a type of ad impression in which the matched customer is interested. The matched customer may be further permitted to remove a flag from the cookie in response to a selection by the customer of a type of ad impression in which the matched customer is not interested. The system, method, and/or article may further comprise receiving an updated campaign request from the merchant in response to at least one of: a report showing the results of the comparing and a click through associated with customers who received targeted ad impressions.
The features and advantages of the present disclosure will become more apparent from the detailed description set forth below when taken in conjunction with the drawings. The left-most digit of a reference number identifies the drawing in which the reference number first appears.
The detailed description of exemplary embodiments herein makes reference to the accompanying drawings, which show the exemplary embodiments by way of illustration and their best mode. While these exemplary embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, it should be understood that other embodiments may be realized and that logical and mechanical changes may be made without departing from the spirit and scope of the disclosure. Thus, the detailed description herein is presented for purposes of illustration only and not of limitation. For example, the steps recited in any of the method or process descriptions may be executed in any order and are not limited to the order presented. Moreover, any of the functions or steps may be outsourced to or performed by one or more third parties. Furthermore, any reference to singular includes plural embodiments, and any reference to more than one component may include a singular embodiment.
Phrases and terms similar to “transaction account” or “credit account” may include any account that may be used to facilitate a financial transaction.
Phrases and terms similar to “financial institution” or “transaction account issuer” may include any entity that offers transaction account services. Although often referred to as a “financial institution,” the financial institution may represent any type of bank, lender or other type of account issuing institution, such as credit card companies, card sponsoring companies, or third party issuers under contract with financial institutions. It is further noted that other participants may be involved in some phases of the transaction, such as an intermediary settlement institution.
The terms “payment vehicle,” “financial transaction instrument,” “transaction instrument” and/or the plural form of these terms may be used interchangeably throughout to refer to a financial instrument.
Phrases and terms similar to “item” may include any good, service, information, experience, data, content, access, rental, lease, contribution, account, credit, debit, benefit, right, reward, points, coupons, credits, monetary equivalent, anything of value, something of minimal or no value, monetary value, non-monetary value and/or the like.
Phrases and terms similar to “merchant,” “supplier” or “seller” may include any entity that receives payment or other consideration. For example, a merchant may request payment for items sold to a customer or consumer who holds an account with a transaction account issuer.
Phrases and terms similar to “customer,” or “transaction account customer” may include any entity that purchases items using a transaction account. Thus, for example, a transaction account customer may purchase, lease, rent, barter or otherwise obtain items from a supplier and pay the supplier using a transaction account.
As used herein, a “consumer” may include any entity that provides payment or other consideration in exchange for the sale of one or more items.
As used herein, “personally identifying information,” or “PII,” may comprise any information that may be used to identify an individual (e.g., a consumer, a customer, etc.) For instance, in various embodiments, PII may comprise an individual's name, address, telephone number, email address, gender, birth date, social security number, a unique identifier associated with the individual, one or more transaction accounts, demographic data, and the like.
As used herein, “internal data” may include any data a transaction account issuer possesses or acquires pertaining to a particular customer or consumer. Internal data may be gathered before, during, or after a relationship between the transaction account issuer and the transaction account holder (e.g., the consumer or buyer). Such data may include customer or consumer PII, which may include demographic data. Demographic data may include any data pertaining to a customer or consumer. Demographic data may include name, address, telephone number, email address, employer and social security number. Transactional data is any data pertaining to the particular transactions in which a customer or consumer engages during any given time period. Transactional data may include, for example, transaction amount, transaction time, transaction vendor/merchant, and transaction vendor/merchant location. Transaction vendor/merchant location may contain a high degree of specificity to a vendor/merchant. For example, transaction vendor/merchant location may include a particular gasoline filing station in a particular postal code located at a particular cross section or address. Also, for example, transaction vendor/merchant location may include a particular web address, such as a Uniform Resource Locator (“URL”), an email address and/or an Internet Protocol (“IP”) address for a vendor/merchant. Transaction vendor/merchant, and transaction vendor/merchant location may be associated with a particular consumer and further associated with sets of consumers. Payment data includes any data pertaining to a customer's or consumer's history of paying debt obligations. Payment data may include payment dates, payment amounts, balance amount, and credit limit. Internal data may further comprise records of customer or consumer service calls, complaints, requests for credit line increases, questions, and comments. A record of a customer or consumer service call includes, for example, date of call, reason for call, and any transcript or summary of the actual call.
As used herein, an “ad impression” or “advertisement impression” may comprise an appearance of an advertisement on a web page. An ad impression may be based upon a “creative,” which may comprise a template or file which forms the basis for an ad impression. That is, for example, a plurality of ad impressions may be served based upon a single creative.
Phrases and terms similar to “cookie,” “HTTP cookie,” “web cookie,” “browser cookie” and the like include one or more files and/or compilations of data transmitted by a website or web-server to a destination machine (e.g., a web client). Cookies may comprise a variety of data, including state data, session data, shopping cart data, customer preference data, and the like. A cookie may be stored by a web client and returned later to the website or web-server with which the cookie originated (i.e., the website or web-server that set the cookie). A cookie may also be transmitted to a non-originating website or web-server (i.e., a website or web server that did not set the cookie).
Further, as used herein, a cookie may contain a “cookie ID.” A cookie ID may comprise any data that uniquely identifies a consumer, customer, and/or web client. Thus, a cookie ID may comprise a number, an alphanumeric string, a purely alphabetical string, a single character, and/or any other data element or compilation that may be used to uniquely identify consumer, customer, and/or web client. A cookie ID may further serve to anonymously identify a consumer, customer, and/or web client, in which case the cookie ID may not contain any PII associated with the consumer, customer, and/or web client.
A system for targeting ad impressions is disclosed. In various embodiments, a system for targeting ad impressions to customers based upon actual spend data is disclosed. Referring to
A web client 102 may comprise any device (e.g., personal computer) which communicates via any network, for example such as those discussed herein. Such browser applications comprise Internet browsing software installed within a computing unit or a system to conduct online transactions and/or communications. These computing units or systems may take the form of a computer or set of computers, although other types of computing units or systems may be used, including laptops, notebooks, hand held computers, personal digital assistants, set-top boxes, workstations, computer-servers, main frame computers, mini-computers, PC servers, pervasive computers, network sets of computers, personal computers, such as iPads, iMACs, and MacBooks, kiosks, terminals, point of sale (POS) devices and/or terminals, televisions, or any other device capable of receiving data over a network. A web client may run Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Apple Safari, or any other of the myriad software packages available for browsing the internet.
In various embodiments, a web client 102 may or may not be in direct contact with an application server. For example, a web client 102 may access the services of an application server through another server and/or hardware component, which may have a direct or indirect connection to an Internet server. For example, a web client 102 may communicate with an application server via a load balancer. In various embodiments, access is through a network or the Internet through a commercially available web browser software package.
A web client 102 may include an operating system (e.g., Windows NT, 95/98/2000/CE/Mobile, OS2, UNIX, Linux, Solaris, MacOS, PalmOS, etc.) as well as various conventional support software and drivers typically associated with computers. A web client 102 may include any suitable personal computer, network computer, workstation, personal digital assistant, cellular phone, smart phone, minicomputer, mainframe or the like. A web client 102 can be in a home or business environment with access to a network. In various embodiments, access is through a network or the Internet through a commercially available web-browser software package. A web client 102 may implement security protocols such as Secure Sockets Layer (SSL) and Transport Layer Security (TLS). A web client 102 may implement several application layer protocols including http, https, ftp, and sftp.
Web client 102, transaction account issuer system 106, service provider system 108, media buyer system 110, advertising exchange (“ad exchange”) 112, and/or merchant system 114, may communicate via a network 104. As used herein, the term “network” may include any cloud, cloud computing system or electronic communications system or method which incorporates hardware and/or software components. Communication among the parties may be accomplished through any suitable communication channels, such as, for example, a telephone network, an extranet, an intranet, Internet, point of interaction device (point of sale device, personal digital assistant (e.g., iPhone®, Palm Pilot®, Blackberry®), cellular phone, kiosk, etc.), online communications, satellite communications, off-line communications, wireless communications, transponder communications, local area network (LAN), wide area network (WAN), virtual private network (VPN), networked or linked devices, keyboard, mouse and/or any suitable communication or data input modality. Moreover, although the system is frequently described herein as being implemented with TCP/IP communications protocols, the system may also be implemented using IPX, Appletalk, IP-6, NetBIOS, OSI, any tunneling protocol (e.g. IPsec, SSH), or any number of existing or future protocols. If the network 104 is in the nature of a public network, such as the Internet, it may be advantageous to presume the network to be insecure and open to eavesdroppers. Specific information related to the protocols, standards, and application software utilized in connection with the Internet is generally known to those skilled in the art and, as such, need not be detailed herein. See, for example, D
The various system components may be independently, separately or collectively suitably coupled to the network 104 via data links which includes, for example, a connection to an Internet Service Provider (ISP) over the local loop as is typically used in connection with standard modem communication, cable modem, Dish networks, ISDN, Digital Subscriber Line (DSL), or various wireless communication methods, see, e.g., G
“Cloud” or “Cloud computing” includes a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. Cloud computing may include location-independent computing, whereby shared servers provide resources, software, and data to computers and other devices on demand. For more information regarding cloud computing, see the NIST's (National Institute of Standards and Technology) definition of cloud computing at http://csrc.nist.gov/groups/SNS/cloud-computing/cloud-def-v15.doc (last visited Feb. 4, 2011), which is hereby incorporated by reference in its entirety.
Transaction account issuer system 106 may comprise a computer-based system owned and/or operated by a transaction account issuer (e.g., American Express). A transaction account issuer system 106 may comprise one or more databases, one or more web servers, one or more application servers, and the like. A transaction account issuer system 106 may comprise internal data, as described elsewhere herein. For instance, a transaction account issuer system 106 may comprise a database that stores data associated with one or more transaction account customers.
Service provider system 108 may comprise a computer-based system owned and/or operated by a service provider (e.g., a provider of consumer data). A service provider system 108 may comprise one or more databases, one or more web servers, one or more application servers, and the like. In various embodiments, a service provider system 108 may comprise data associated with one or more online consumers. For example, a service provider system 108 may comprise PII associated with one or more consumers, one or more cookie and/or cookie data associated with one or more consumers, and the like. In various embodiments, a service provider system 108 may communicate with a transaction account issuer system 106 and/or a media buyer system 110.
Media buyer system 110 may comprise a computer-based system owned and/or operated by a media buyer (e.g., a purchaser of advertisements or ad impressions, as described elsewhere herein). A media buyer system 110 may comprise one or more databases, one or more web servers, one or more application servers, and the like. In various embodiments, a media buyer system 110 may communicate with an advertisement exchange 112 (or, “ad exchange”), a service provider system 108, and/or a transaction account issuer system 106 for the purchase and delivery of one or more ad impressions to a web client 102.
An ad exchange 112 may comprise a computer-based system that facilitates online purchases and sales of ad impressions. In various embodiments, media buyer system 110 may communicate with ad exchange 112, which may itself communicate with a variety of advertising networks (or “ad networks”), to purchase one or more ad impressions, as described elsewhere herein. For example, in various embodiments, media buyer system 110 may communicate with a plurality of ad exchanges 112 (e.g., AdECN®, Right Media®, DoubleClick®, and/or Zinc Exchange®) to purchase one or more ad impressions. Further, in various embodiments, an ad exchange 112 may communicate with a media buyer system 110, a service provider system 108, and/or a transaction account issuer system 106 for the purchase and delivery of one or more ad impressions to a web client 102.
Merchant system 114 may comprise a system owned and/or operated by a merchant. In various embodiments, merchant system 114 may comprise one or more databases, one or more web servers, one or more application servers, and the like. A merchant system 114 may communicate with a transaction account issuer system 106, a service provider system 108, a media buyer system 110, and/or an ad exchange 112 to request an ad campaign, or to make an ad campaign request, as described elsewhere herein.
Referring now to
With reference to
Service provider system 108 and/or transaction account issuer system 106 may install a cookie on a web client 102 associated with a matched customer (step 204). This installation may occur in response to generation of a matched list, and the cookie may not include any PII associated with the matched customer. That is, a cookie, or an “anonymized cookie,” may be stripped of any PII that may be associated with a matched customer (e.g., PII that was used to match a transaction account customer to an individual whose PII is known to service provider system 108). A cookie, or an anonymized cookie, may be installed on a matched customer's web client 102. In addition, transaction account issuer system 106 and/or service provider system 108 may maintain an anonymized list of matched customers. For example, a list of matched customers may comprise a list of cookie data associated with each matched customer. The anonymized list may exclude PII. Thus, customer privacy may be safeguarded by systems 106 and/or 108.
A transaction account issuer system 106 and/or a service provider system 108 may receive a campaign request from a merchant (step 206). A campaign request may comprise a request by a merchant to target marketing (e.g., ad impressions associated with the merchant) to a particular group of customers. This group of customers may be associated with, or identified by, one or more attributes (e.g., shopping attributes, purchasing attributes, PII, transaction history information, demographic information, etc.) For example, a campaign request may comprise a request by a merchant who sells electronics to target transaction account customers who are associated with greater than a threshold number of records of charge (“ROCs”) in the electronics industry and who live in a particular geographic region.
Similarly, in various embodiments, a campaign request may comprise a request by a merchant to target marketing to a group of customers based upon any code or identifier. For example, the code may include a universal product code (“U PC”) and/or a stock keeping unit (“SKU”). A UPC may comprise a machine-readable bar code coupled with a human-readable UPC number, either of which may be printed on a label or tag which is placed on an item of merchandise for purchase. A manufacturer may assign and mark each product that it sells with a UPC. Further, once an item reaches a retailer, the retailer may further identify the item with a SKU number or code and/or a variety of other information for identifying a specific item or style of merchandise. A retailer's SKU number may be either an entirely different number used to identify each item (e.g., by style) or a modified version of the manufacturer's UPC number, derived, for example, by adding a SKU number to the UPC number. Thus, in various embodiments, a merchant may request that marketing be targeted based upon one or more UPCs and/or SKUs associated with a customer's transaction history.
In response to receiving a campaign request, a transaction account issuer system 106 may locate a customer record associated with a customer whose transaction history and/or attribute information fits within the parameters associated with the campaign request (step 208). For example, transaction account issuer system 106 may locate a customer record associated with a customer who has greater than a threshold number of ROCs in a particular industry (e.g., the electronic industry) and who resides in a particular geographic area (e.g., New York, N.Y.).
Transaction account issuer system 106 may add, or request that service provider system 108 add, campaign request data to a matched customer's cookie and/or the cookie data associated with the customer in a matched list (step 210). This may occur in response to locating a customer record associated with a customer who fits within the parameters associated with the campaign request. Campaign request data may be added to a cookie and/or to cookie data as a flag and/or an identifier (e.g., a numeric or alphanumeric identifier). An identifier and/or a flag may identify a campaign request and/or the attributes comprising a particular campaign request. For example, a flag may identify a campaign request targeted to customers who have greater than a threshold number of ROCs and who reside in a particular geographic area.
In various embodiments, a customer may navigate or surf to a particular website, whereupon the customer's web client 102 (or a browser installed on the customer's web client 102) may transmit the cookie installed on the web client 102 to service provider system 108 and/or transaction account issuer system 106. A web client 102 may transmit a cookie to a service provider system 108 and/or a transaction issuer system 106, for example, in the event that system 106 and/or system 108 has established a relationship (e.g., a partnership, or an agreement to transmit a cookie in response to navigation to the website) with the website. Thus, for example, where system 108 has a relationship with a particular website, and a customer navigates to that website, the customer's web client 102 may transmit the customer's cookie to system 108.
A cookie and/or a variety of cookie data (e.g., a cookie id and a flag associated with one or more campaign requests) may be transmitted to a media buyer system 110 (step 212). This may occur in response to receipt of a cookie by a system 108 and/or 106 of a customer's cookie from a website with which the system 108 and/or 106 has a relationship (because, receipt of the cookie indicates that the customer is online). Thus, and in various embodiments, cookie data may be transmitted to a media buyer system 110 in response to a campaign request and when the customer is online. A media buyer system 110 may compare a flag associated with a particular cookie id to a list of flags (which list the media buyer system 110 may receive from a transaction account issuer system 106). A media buyer system 110 may, based upon the comparison, determine that a particular flag is associated with a particular campaign request. For example, a media buyer system 110 may determine that a flag is associated with a campaign request made by a particular merchant (e.g., a purveyor of electronics). A media buyer system 110 may thus communicate with an ad exchange 112 to purchase, or bid on, one or more ad impressions for the cookie id based upon the flag (step 214). For example, a media buyer system 110 may purchase an ad impression associated with a merchant (e.g., the purveyor of electronics) who purchased or requested a particular campaign. A media buyer system 110 may further serve a purchased ad impression to a web client 102 associated with the cookie id for which the ad impression was purchased (step 214). That is, for example, media buyer system 110 may serve an ad impression to a web client 102 associated with a customer who fits a particular campaign request.
Thus, system 100 may facilitate the targeted marketing of ad impressions to transaction account customers based upon a variety of attributes (e.g., transaction history, demographics, and the like). Each ad impression may be served to a customer irrespective of a uniform resource locator (“URL”) or address entered in a browser associated with the customer's web client 102. That is, system 100 may facilitate the delivery of targeted ad impressions to customers irrespective of a website to which each customer has surfed. Thus, system 100 may permit the targeted delivery of ad impressions across the web.
In various embodiments, transaction account issuer system 106 may measure the success of a campaign request. For example, transaction account issuer system 106 may compare an actual spend by targeted customers to an actual spend by non-targeted customers who nevertheless fit the campaign request (step 218). That is, transaction account issuer system 106 may compare expenditures associated with customers who received targeted ad impressions as a result of a campaign request to customers who, although they did not receive targeted ad impressions, nevertheless fit the parameters of the campaign request. The difference between the expenditures of targeted and non-targeted customers may illustrate an increase in value or sales arising as a result of a campaign request. In addition, click through rates (i.e., the number of targeted advertisements transmitted to web clients 102 compared to the number of transmitted targeted advertisements actually clicked on or selected by customers) may be gathered or calculated. Transaction account issuer system 106 may, in various embodiments, generate a report that illustrates this increase in value or sales (or a decrease, if this should occur) and/or click through rates. This report and/or the data comprising the report may be transmitted to one or more merchants, e.g., a merchant associated with the particular campaign request (step 220).
A merchant may utilize a report showing click through rates and/or the increase or decrease in value or sales arising as a result of a campaign request to optimize future campaign requests. For example, a merchant may optimize or update a first request to target customers with a ROC higher than a threshold of three ROCs/month in a particular industry to a second request to target customers with a ROC higher than a threshold of five ROCs/month in the industry. A merchant may, for example, choose to optimize a campaign request in this way based upon a narrow or small increase in sales to targeted customers over sales to customers who fit the campaign request but were not served ad impressions.
In various embodiments, system 100 may perform look alike modeling. For instance, in a variety of embodiments, a service provider system 108 may receive or generate a matched list, as described elsewhere herein. Service provider system 108 may, as further described elsewhere herein, update cookies comprising the matched list with campaign request data (e.g., a flag). However, in addition to targeting ad impressions to customers associated with the matched list, in a variety of embodiments, system 108 may compare attributes of matched customers to attributes associated with other, non-matched, consumers. These non-matched consumers may not hold transaction accounts issued by transaction account issuer system 106. Where system 108 locates consumers with attributes that are similar, or look like, attributes associated with matched customers, system 108 may request that media buyer system 110 purchase ad impressions for these consumers as well. That is, system 108 may add a flag associated with a campaign request to the cookies of consumers who are not associated with the matched list. Media buyer system 110 may purchase, or bid on, ad impressions for these consumers as described elsewhere herein.
Thus, system 100 may not only target ad impressions to customers based upon a merchant campaign request; it may target ad impressions to consumers who look like those customers selected by transaction account issuer system 106 for participation in a campaign request. In other words, system 100 may serve ad impressions to any consumer whose PII is known to or stored by with service provider system 108.
With reference now to
With reference to
In various embodiments, whether a customer or a consumer chooses to opt into or out of a category or type of ad impressions or a particular ad impression, a transaction account issuer system 106 and/or a service provider system 108 may modify a cookie associated with the customer or consumer to associate or dissociate the customer or consumer with the category, type, or particular ad impression. For instance, system 106 and/or 108 may add a flag associated with a particular type or category of ad impression (which may be the same as a flag associated with a campaign request) to a customer's or consumer's cookie. This flag may be used, as described elsewhere herein, to purchase and deliver ad impressions to a customer or consumer. Likewise, system 106 and/or system 108 may remove a flag associated with a particular type or category of ad impression, or with a particular ad impression, from a customer's or consumer's cookie. Where a flag is removed, a media buyer system may not bid on the type, category, or particular ad impression associated with that flag. Thus, a customer or consumer may selectively opt into and out of ad impressions based upon the user's preferences.
Systems, methods and computer program products are provided. In the detailed description herein, references to “various embodiments”, “one embodiment”, “an embodiment”, “an example embodiment”, etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. After reading the description, it will be apparent to one skilled in the relevant art(s) how to implement the disclosure in alternative embodiments.
In various embodiments, the methods described herein are implemented using the various particular machines described herein. The methods described herein may be implemented using the below particular machines, and those hereinafter developed, in any suitable combination, as would be appreciated immediately by one skilled in the art. Further, as is unambiguous from this disclosure, the methods described herein may result in various transformations of certain articles.
For the sake of brevity, conventional data networking, application development and other functional aspects of the systems (and components of the individual operating components of the systems) may not be described in detail herein. Furthermore, the connecting lines shown in the various figures contained herein are intended to represent exemplary functional relationships and/or physical couplings between the various elements. It should be noted that many alternative or additional functional relationships or physical connections may be present in a practical system.
The various system components discussed herein may include one or more of the following: a host server or other computing systems including a processor for processing digital data; a memory coupled to the processor for storing digital data; an input digitizer coupled to the processor for inputting digital data; an application program stored in the memory and accessible by the processor for directing processing of digital data by the processor; a display device coupled to the processor and memory for displaying information derived from digital data processed by the processor; and a plurality of databases. Various databases used herein may include: client data; merchant data; financial institution data; and/or like data useful in the operation of the system. As those skilled in the art will appreciate, user computer may include an operating system (e.g., Windows NT, Windows 95/98/2000, Windows XP, Windows Vista, Windows 7, OS2, UNIX, Linux, Solaris, MacOS, etc.) as well as various conventional support software and drivers typically associated with computers. A user may include any individual, business, entity, government organization, software and/or hardware that interact with a system.
In an embodiment, various components, modules, and/or engines of system 100 may be implemented as micro-applications or micro-apps. Micro-apps are typically deployed in the context of a mobile operating system, including for example, a Palm mobile operating system, a Windows mobile operating system, an Android Operating System, Apple iOS, a Blackberry operating system and the like. The micro-app may be configured to leverage the resources of the larger operating system and associated hardware via a set of predetermined rules which govern the operations of various operating systems and hardware resources. For example, where a micro-app desires to communicate with a device or network other than the mobile device or mobile operating system, the micro-app may leverage the communication protocol of the operating system and associated device hardware under the predetermined rules of the mobile operating system. Moreover, where the micro-app desires an input from a user, the micro-app may be configured to request a response from the operating system which monitors various hardware components and then communicates a detected input from the hardware to the micro-app.
As used herein, “transmit” may include sending electronic data from one system component to another over a network connection. Additionally, as used herein, “data” may include encompassing information such as commands, queries, files, data for storage, and the like in digital or any other form.
The system contemplates uses in association with web services, utility computing, pervasive and individualized computing, security and identity solutions, autonomic computing, cloud computing, commodity computing, mobility and wireless solutions, open source, biometrics, grid computing and/or mesh computing.
Any databases discussed herein may include relational, hierarchical, graphical, or object-oriented structure and/or any other database configurations. Common database products that may be used to implement the databases include DB2 by IBM (Armonk, N.Y.), various database products available from Oracle Corporation (Redwood Shores, Calif.), Microsoft Access or Microsoft SQL Server by Microsoft Corporation (Redmond, Wash.), MySQL by MySQL AB (Uppsala, Sweden), or any other suitable database product. Moreover, the databases may be organized in any suitable manner, for example, as data tables or lookup tables. Each record may be a single file, a series of files, a linked series of data fields or any other data structure. Association of certain data may be accomplished through any desired data association technique such as those known or practiced in the art. For example, the association may be accomplished either manually or automatically. Automatic association techniques may include, for example, a database search, a database merge, GREP, AGREP, SQL, using a key field in the tables to speed searches, sequential searches through all the tables and files, sorting records in the file according to a known order to simplify lookup, and/or the like. The association step may be accomplished by a database merge function, for example, using a “key field” in pre-selected databases or data sectors. Various database tuning steps are contemplated to optimize database performance. For example, frequently used files such as indexes may be placed on separate file systems to reduce In/Out (“I/O”) bottlenecks.
More particularly, a “key field” partitions the database according to the high-level class of objects defined by the key field. For example, certain types of data may be designated as a key field in a plurality of related data tables and the data tables may then be linked on the basis of the type of data in the key field. The data corresponding to the key field in each of the linked data tables is preferably the same or of the same type. However, data tables having similar, though not identical, data in the key fields may also be linked by using AGREP, for example. In accordance with one embodiment, any suitable data storage technique may be utilized to store data without a standard format. Data sets may be stored using any suitable technique, including, for example, storing individual files using an ISO/IEC 7816-4 file structure; implementing a domain whereby a dedicated file is selected that exposes one or more elementary files containing one or more data sets; using data sets stored in individual files using a hierarchical filing system; data sets stored as records in a single file (including compression, SQL accessible, hashed via one or more keys, numeric, alphabetical by first tuple, etc.); Binary Large Object (BLOB); stored as ungrouped data elements encoded using ISO/IEC 7816-6 data elements; stored as ungrouped data elements encoded using ISO/IEC Abstract Syntax Notation (ASN.1) as in ISO/IEC 8824 and 8825; and/or other proprietary techniques that may include fractal compression methods, image compression methods, etc.
In one exemplary embodiment, the ability to store a wide variety of information in different formats is facilitated by storing the information as a BLOB. Thus, any binary information can be stored in a storage space associated with a data set. As discussed above, the binary information may be stored on the financial transaction instrument or external to but affiliated with the financial transaction instrument. The BLOB method may store data sets as ungrouped data elements formatted as a block of binary via a fixed memory offset using either fixed storage allocation, circular queue techniques, or best practices with respect to memory management (e.g., paged memory, least recently used, etc.). By using BLOB methods, the ability to store various data sets that have different formats facilitates the storage of data associated with the financial transaction instrument by multiple and unrelated owners of the data sets. For example, a first data set which may be stored may be provided by a first party, a second data set which may be stored may be provided by an unrelated second party, and yet a third data set which may be stored, may be provided by an third party unrelated to the first and second party. Each of these three exemplary data sets may contain different information that is stored using different data storage formats and/or techniques. Further, each data set may contain subsets of data that also may be distinct from other subsets.
As stated above, in various embodiments, the data can be stored without regard to a common format. However, in one exemplary embodiment, the data set (e.g., BLOB) may be annotated in a standard manner when provided for manipulating the data onto the financial transaction instrument. The annotation may comprise a short header, trailer, or other appropriate indicator related to each data set that is configured to convey information useful in managing the various data sets. For example, the annotation may be called a “condition header”, “header”, “trailer”, or “status”, herein, and may comprise an indication of the status of the data set or may include an identifier correlated to a specific issuer or owner of the data. In one example, the first three bytes of each data set BLOB may be configured or configurable to indicate the status of that particular data set; e.g., LOADED, INITIALIZED, READY, BLOCKED, REMOVABLE, or DELETED. Subsequent bytes of data may be used to indicate for example, the identity of the issuer, user, transaction/membership account identifier or the like. Each of these condition annotations are further discussed herein.
The data set annotation may also be used for other types of status information as well as various other purposes. For example, the data set annotation may include security information establishing access levels. The access levels may, for example, be configured to permit only certain individuals, levels of employees, companies, or other entities to access data sets, or to permit access to specific data sets based on the transaction, merchant, issuer, user or the like. Furthermore, the security information may restrict/permit only certain actions such as accessing, modifying, and/or deleting data sets. In one example, the data set annotation indicates that only the data set owner or the user are permitted to delete a data set, various identified users may be permitted to access the data set for reading, and others are altogether excluded from accessing the data set. However, other access restriction parameters may also be used allowing various entities to access a data set with various permission levels as appropriate.
The data, including the header or trailer may be received by a stand alone interaction device configured to add, delete, modify, or augment the data in accordance with the header or trailer. As such, in one embodiment, the header or trailer is not stored on the transaction device along with the associated issuer-owned data but instead the appropriate action may be taken by providing to the transaction instrument user at the stand alone device, the appropriate option for the action to be taken. The system may contemplate a data storage arrangement wherein the header or trailer, or header or trailer history, of the data is stored on the transaction instrument in relation to the appropriate data.
One skilled in the art will also appreciate that, for security reasons, any databases, systems, devices, servers or other components of the system may consist of any combination thereof at a single location or at multiple locations, wherein each database or system includes any of various suitable security features, such as firewalls, access codes, encryption, decryption, compression, decompression, and/or the like.
Encryption may be performed by way of any of the techniques now available in the art or which may become available—e.g., Twofish, RSA, El Gamal, Schorr signature, DSA, PGP, PKI, and symmetric and asymmetric cryptosystems.
The computing unit of the web client may be further equipped with an Internet browser connected to the Internet or an intranet using standard dial-up, cable, DSL or any other Internet protocol known in the art. Transactions originating at a web client may pass through a firewall in order to prevent unauthorized access from users of other networks. Further, additional firewalls may be deployed between the varying components of CMS to further enhance security.
Firewall may include any hardware and/or software suitably configured to protect CMS components and/or enterprise computing resources from users of other networks. Further, a firewall may be configured to limit or restrict access to various systems and components behind the firewall for web clients connecting through a web server. Firewall may reside in varying configurations including Stateful Inspection, Proxy based, access control lists, and Packet Filtering among others. Firewall may be integrated within an web server or any other CMS components or may further reside as a separate entity. A firewall may implement network address translation (“NAT”) and/or network address port translation (“NAPT”). A firewall may accommodate various tunneling protocols to facilitate secure communications, such as those used in virtual private networking. A firewall may implement a demilitarized zone (“DMZ”) to facilitate communications with a public network such as the Internet. A firewall may be integrated as software within an Internet server, any other application server components or may reside within another computing device or may take the form of a standalone hardware component.
The computers discussed herein may provide a suitable website or other Internet-based graphical user interface which is accessible by users. In one embodiment, the Microsoft Internet Information Server (IIS), Microsoft Transaction Server (MTS), and Microsoft SQL Server, are used in conjunction with the Microsoft operating system, Microsoft NT web server software, a Microsoft SQL Server database system, and a Microsoft Commerce Server. Additionally, components such as Access or Microsoft SQL Server, Oracle, Sybase, Informix MySQL, Interbase, etc., may be used to provide an Active Data Object (ADO) compliant database management system. In one embodiment, the Apache web server is used in conjunction with a Linux operating system, a MySQL database, and the Perl, PHP, and/or Python programming languages.
Any of the communications, inputs, storage, databases or displays discussed herein may be facilitated through a website having web pages. The term “web page” as it is used herein is not meant to limit the type of documents and applications that might be used to interact with the user. For example, a typical website might include, in addition to standard HTML documents, various forms, Java applets, JavaScript, active server pages (ASP), common gateway interface scripts (CGI), extensible markup language (XML), dynamic HTML, cascading style sheets (CSS), AJAX (Asynchronous Javascript And XML), helper applications, plug-ins, and the like. A server may include a web service that receives a request from a web server, the request including a URL (http://yahoo.com/stockquotes/ge) and an IP address (123.56.789.234). The web server retrieves the appropriate web pages and sends the data or applications for the web pages to the IP address. Web services are applications that are capable of interacting with other applications over a communications means, such as the internet. Web services are typically based on standards or protocols such as XML, SOAP, AJAX, WSDL and UDDI. Web services methods are well known in the art, and are covered in many standard texts. See, e.g., A
Middleware may include any hardware and/or software suitably configured to facilitate communications and/or process transactions between disparate computing systems. Middleware components are commercially available and known in the art. Middleware may be implemented through commercially available hardware and/or software, through custom hardware and/or software components, or through a combination thereof. Middleware may reside in a variety of configurations and may exist as a standalone system or may be a software component residing on the Internet server. Middleware may be configured to process transactions between the various components of an application server and any number of internal or external systems for any of the purposes disclosed herein. WebSphere MQ™ (formerly MQSeries) by IBM, Inc. (Armonk, N.Y.) is an example of a commercially available middleware product. An Enterprise Service Bus (“ESB”) application is another example of middleware.
Practitioners will also appreciate that there are a number of methods for displaying data within a browser-based document. Data may be represented as standard text or within a fixed list, scrollable list, drop-down list, editable text field, fixed text field, pop-up window, and the like. Likewise, there are a number of methods available for modifying data in a web page such as, for example, free text entry using a keyboard, selection of menu items, check boxes, option boxes, and the like.
The system and method may be described herein in terms of functional block components, screen shots, optional selections and various processing steps. It should be appreciated that such functional blocks may be realized by any number of hardware and/or software components configured to perform the specified functions. For example, the system may employ various integrated circuit components, e.g., memory elements, processing elements, logic elements, look-up tables, and the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. Similarly, the software elements of the system may be implemented with any programming or scripting language such as C, C++, C#, Java, JavaScript, VBScript, Macromedia Cold Fusion, COBOL, Microsoft Active Server Pages, assembly, PERL, PHP, awk, Python, Visual Basic, SQL Stored Procedures, PL/SQL, any UNIX shell script, and extensible markup language (XML) with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. Further, it should be noted that the system may employ any number of conventional techniques for data transmission, signaling, data processing, network control, and the like. Still further, the system could be used to detect or prevent security issues with a client-side scripting language, such as JavaScript, VBScript or the like. For a basic introduction of cryptography and network security, see any of the following references: (1) “Applied Cryptography: Protocols, Algorithms, And Source Code In C,” by Bruce Schneier, published by John Wiley & Sons (second edition, 1995); (2) “Java Cryptography” by Jonathan Knudson, published by O'Reilly & Associates (1998); (3) “Cryptography & Network Security: Principles & Practice” by William Stallings, published by Prentice Hall; all of which are hereby incorporated by reference.
As used herein, the term “end user”, “consumer”, “customer”, “cardmember”, “business” or “merchant” may be used interchangeably with each other, and each may mean any person, entity, machine, hardware, software or business. A bank may be part of the system, but the bank may represent other types of card issuing institutions, such as credit card companies, card sponsoring companies, or third party issuers under contract with financial institutions. It is further noted that other participants may be involved in some phases of the transaction, such as an intermediary settlement institution, but these participants are not shown.
Each participant is equipped with a computing device in order to interact with the system and facilitate online commerce transactions. The customer has a computing unit in the form of a personal computer, although other types of computing units may be used including laptops, notebooks, hand held computers, set-top boxes, cellular telephones, touch-tone telephones and the like. The merchant has a computing unit implemented in the form of a computer-server, although other implementations are contemplated by the system. The bank has a computing center shown as a main frame computer. However, the bank computing center may be implemented in other forms, such as a mini-computer, a PC server, a network of computers located in the same of different geographic locations, or the like. Moreover, the system contemplates the use, sale or distribution of any goods, services or information over any network having similar functionality described herein.
The merchant computer and the bank computer may be interconnected via a second network, referred to as a payment network. The payment network which may be part of certain transactions represents existing proprietary networks that presently accommodate transactions for credit cards, debit cards, and other types of financial/banking cards. The payment network is a closed network that is assumed to be secure from eavesdroppers. Exemplary transaction networks may include the American Express®, VisaNet® and the Veriphone® networks.
The electronic commerce system may be implemented at the customer and issuing bank. In an exemplary implementation, the electronic commerce system is implemented as computer software modules loaded onto the customer computer and the banking computing center. The merchant computer does not require any additional software to participate in the online commerce transactions supported by the online commerce system.
As will be appreciated by one of ordinary skill in the art, the system may be embodied as a customization of an existing system, an add-on product, upgraded software, a stand alone system, a distributed system, a method, a data processing system, a device for data processing, and/or a computer program product. Accordingly, the system may take the form of an entirely software embodiment, an entirely hardware embodiment, or an embodiment combining aspects of both software and hardware. Furthermore, the system may take the form of a computer program product on a computer-readable storage medium having computer-readable program code means embodied in the storage medium. Any suitable computer-readable storage medium may be utilized, including hard disks, CD-ROM, optical storage devices, magnetic storage devices, and/or the like.
The system and method is described herein with reference to screen shots, block diagrams and flowchart illustrations of methods, apparatus (e.g., systems), and computer program products according to various embodiments. It will be understood that each functional block of the block diagrams and the flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by computer program instructions.
These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions that execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.
Accordingly, functional blocks of the block diagrams and flowchart illustrations support combinations of means for performing the specified functions, combinations of steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each functional block of the block diagrams and flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, can be implemented by either special purpose hardware-based computer systems which perform the specified functions or steps, or suitable combinations of special purpose hardware and computer instructions. Further, illustrations of the process flows and the descriptions thereof may make reference to user windows, webpages, websites, web forms, prompts, etc. Practitioners will appreciate that the illustrated steps described herein may comprise in any number of configurations including the use of windows, webpages, web forms, popup windows, prompts and the like. It should be further appreciated that the multiple steps as illustrated and described may be combined into single webpages and/or windows but have been expanded for the sake of simplicity. In other cases, steps illustrated and described as single process steps may be separated into multiple webpages and/or windows but have been combined for simplicity.
Benefits, other advantages, and solutions to problems have been described herein with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any elements that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as critical, required, or essential features or elements of the disclosure. The scope of the disclosure is accordingly to be limited by nothing other than the appended claims, in which reference to an element in the singular is not intended to mean “one and only one” unless explicitly so stated, but rather “one or more.” Moreover, where a phrase similar to ‘at least one of A, B, and C’ or ‘at least one of A, B, or C’ is used in the claims or specification, it is intended that the phrase be interpreted to mean that A alone may be present in an embodiment, B alone may be present in an embodiment, C alone may be present in an embodiment, or that any combination of the elements A, B and C may be present in a single embodiment; for example, A and B, A and C, B and C, or A and B and C. Although the disclosure includes a method, it is contemplated that it may be embodied as computer program instructions on a tangible computer-readable carrier, such as a magnetic or optical memory or a magnetic or optical disk. All structural, chemical, and functional equivalents to the elements of the above-described exemplary embodiments that are known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the present claims. Moreover, it is not necessary for a device or method to address each and every problem sought to be solved by the present disclosure, for it to be encompassed by the present claims. Furthermore, no element, component, or method step in the present disclosure is intended to be dedicated to the public regardless of whether the element, component, or method step is explicitly recited in the claims. No claim element herein is to be construed under the provisions of 35 U.S.C. 112, sixth paragraph, unless the element is expressly recited using the phrase “means for.” As used herein, the terms “comprises”, “comprising”, or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
In yet another embodiment, the transponder, transponder-reader, and/or transponder-reader system are configured with a biometric security system that may be used for providing biometrics as a secondary form of identification. The biometric security system may include a transponder and a reader communicating with the system. The biometric security system also may include a biometric sensor that detects biometric samples and a device for verifying biometric samples. The biometric security system may be configured with one or more biometric scanners, processors and/or systems. A biometric system may include one or more technologies, or any portion thereof, such as, for example, recognition of a biometric. As used herein, a biometric may include a user's voice, fingerprint, facial, ear, signature, vascular patterns, DNA sampling, hand geometry, sound, olfactory, keystroke/typing, iris, retinal or any other biometric relating to recognition based upon any body part, function, system, attribute and/or other characteristic, or any portion thereof.
Phrases and terms similar to “account”, “account number”, “account code,” “consumer account,” or “transaction account” as used herein, may include any device, code (e.g., one or more of an authorization/access code, personal identification number (“PIN”), Internet code, other identification code, and/or the like), number, letter, symbol, digital certificate, smart chip, digital signal, analog signal, biometric or other identifier/indicia suitably configured to allow the consumer to access, interact with or communicate with the system. The account number may optionally be located on or associated with a rewards account, charge account, credit account, debit account, prepaid account, telephone card, embossed card, smart card, magnetic stripe card, bar code card, transponder, radio frequency card or an associated account.
The system may include or interface with any of the foregoing accounts or devices, a transponder and reader in RF communication with the transponder (which may include a fob), or communications between an initiator and a target enabled by near field communications (NFC). Typical devices may include, for example, a key ring, tag, card, cell phone, wristwatch or any such form capable of being presented for interrogation. Moreover, the system, computing unit or device discussed herein may include a “pervasive computing device,” which may include a traditionally non-computerized device that is embedded with a computing unit. Examples may include watches, Internet enabled kitchen appliances, restaurant tables embedded with RF readers, wallets or purses with imbedded transponders, etc. Furthermore, a device or financial transaction instrument may have electronic and communications functionality enabled, for example, by: a network of electronic circuitry that is printed or otherwise incorporated onto or within the transaction instrument (and typically referred to as a “smart card”); a fob having a transponder and an RFID reader; and/or near field communication (NFC) technologies. For more information regarding NFC, refer to the following specifications all of which are incorporated by reference herein: ISO/IEC 18092 /ECMA-340, Near Field Communication Interface and Protocol-1 (NFCIP-1); ISO/IEC 21481 /ECMA-352, Near Field Communication Interface and Protocol-2 (NFCIP-2); and EMV 4.2 available at http://www.emvco.com/default.aspx.
The account number may be distributed and stored in any form of plastic, electronic, magnetic, radio frequency, wireless, audio and/or optical device capable of transmitting or downloading data from itself to a second device. A consumer account number may be, for example, a sixteen-digit account number, although each credit provider has its own numbering system, such as the fifteen-digit numbering system used by American Express. Each company's account numbers comply with that company's standardized format such that the company using a fifteen-digit format will generally use three-spaced sets of numbers, as represented by the number “0000 000000 00000”. The first five to seven digits are reserved for processing purposes and identify the issuing bank, account type, etc. In this example, the last (fifteenth) digit is used as a sum check for the fifteen digit number. The intermediary eight-to-eleven digits are used to uniquely identify the consumer. A merchant account number may be, for example, any number or alpha-numeric characters that identify a particular merchant for purposes of account acceptance, account reconciliation, reporting, or the like.
Phrases similar to a “payment processor” may include a company (e.g., a third party) appointed (e.g., by a merchant) to handle transactions for merchant banks. Payment processors may be broken down into two types: front-end and back-end. Front-end payment processors have connections to various transaction accounts and supply authorization and settlement services to the merchant banks' merchants. Back-end payment processors accept settlements from front-end payment processors and, via The Federal Reserve Bank, move money from an issuing bank to the merchant bank. In an operation that will usually take a few seconds, the payment processor will both check the details received by forwarding the details to the respective account's issuing bank or card association for verification, and may carry out a series of anti-fraud measures against the transaction. Additional parameters, including the account's country of issue and its previous payment history, may be used to gauge the probability of the transaction being approved. In response to the payment processor receiving confirmation that the transaction account details have been verified, the information may be relayed back to the merchant, who will then complete the payment transaction. In response to the verification being denied, the payment processor relays the information to the merchant, who may then decline the transaction. Phrases similar to a “payment gateway” or “gateway” may include an application service provider service that authorizes payments for e-businesses, online retailers, and/or traditional brick and mortar merchants. The gateway may be the equivalent of a physical point of sale terminal located in most retail outlets. A payment gateway may protect transaction account details by encrypting sensitive information, such as transaction account numbers, to ensure that information passes securely between the customer and the merchant and also between merchant and payment processor.
The term “non-transitory” is to be understood to remove only propagating transitory signals per se from the claim scope and does not relinquish rights to all standard computer-readable media that are not only propagating transitory signals per se. Stated another way, the meaning of the term “non-transitory computer-readable medium” should be construed to exclude only those types of transitory computer-readable media which were found in In Re Nuijten to fall outside the scope of patentable subject matter under 35 U.S.C. § 101.
This application is a continuation of, claims priority to and the benefit of, U.S. Ser. No. 14/464,474 filed Aug. 20, 2014 and entitled “Systems and Methods for Targeting Ad Impressions.” The '474 application claims the benefit of, priority to and is a continuation of, U.S. Ser. No. 13/245,636 filed Sep. 26, 2011 and entitled “Systems and Methods for Targeting Ad Impressions,” which issued on Sep. 30, 2014 as U.S. Pat. No. 8,849,699. All of above-referenced applications are incorporated herein by reference in their entirety for any purpose.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4833308 | Humble | May 1989 | A |
| 4882675 | Nichtberger et al. | Nov 1989 | A |
| 5025372 | Burton et al. | Jun 1991 | A |
| 5467269 | Flaten | Nov 1995 | A |
| 5471669 | Lidman | Nov 1995 | A |
| 5729693 | Holda-Fleck | Mar 1998 | A |
| 5918211 | Sloane | Jun 1999 | A |
| 5923016 | Fredregill et al. | Jul 1999 | A |
| 5948040 | DeLorme et al. | Sep 1999 | A |
| 5953706 | Patel | Sep 1999 | A |
| 6009411 | Kepecs | Dec 1999 | A |
| 6018718 | Walker et al. | Jan 2000 | A |
| 6035280 | Christensen | Mar 2000 | A |
| 6039244 | Finsterwald | Mar 2000 | A |
| 6222914 | McMullin | Apr 2001 | B1 |
| 6266649 | Linden et al. | Jul 2001 | B1 |
| 6298330 | Gardenswartz | Oct 2001 | B1 |
| 6321208 | Barnett et al. | Nov 2001 | B1 |
| 6330543 | Kepecs | Dec 2001 | B1 |
| 6332126 | Peirce et al. | Dec 2001 | B1 |
| 6336099 | Barnett et al. | Jan 2002 | B1 |
| 6343317 | Glorikian | Jan 2002 | B1 |
| 6360167 | Millington et al. | Mar 2002 | B1 |
| 6370514 | Messner | Apr 2002 | B1 |
| 6381603 | Chan et al. | Apr 2002 | B1 |
| 6414635 | Stewart et al. | Jul 2002 | B1 |
| 6430539 | Lazarus et al. | Aug 2002 | B1 |
| 6434534 | Walker et al. | Aug 2002 | B1 |
| 6542814 | Polidi et al. | Apr 2003 | B2 |
| 6584448 | Laor | Jun 2003 | B1 |
| 6587835 | Treyz et al. | Jul 2003 | B1 |
| 6606619 | Ortega et al. | Aug 2003 | B2 |
| 6691915 | Thaxton et al. | Feb 2004 | B1 |
| 6738711 | Ohmura et al. | May 2004 | B2 |
| 6748365 | Quinlan et al. | Jun 2004 | B1 |
| 6882290 | French et al. | Apr 2005 | B2 |
| 6883708 | Fiedler et al. | Apr 2005 | B1 |
| 6904408 | McCarthy et al. | Jun 2005 | B1 |
| 6915265 | Johnson | Jul 2005 | B1 |
| 6937995 | Kepecs | Aug 2005 | B1 |
| 7003476 | Samra et al. | Feb 2006 | B1 |
| 7010497 | Nyhan | Mar 2006 | B1 |
| 7016856 | Wiggins | Mar 2006 | B1 |
| 7016860 | Modani et al. | Mar 2006 | B2 |
| 7054830 | Eggleston et al. | May 2006 | B1 |
| 7072851 | Wilcox et al. | Jul 2006 | B1 |
| 7107238 | Hatakama et al. | Sep 2006 | B2 |
| 7120591 | Solomon et al. | Oct 2006 | B1 |
| 7139793 | Lala et al. | Nov 2006 | B2 |
| 7146328 | Solomon et al. | Dec 2006 | B1 |
| 7165037 | Lazarus et al. | Jan 2007 | B2 |
| 7302429 | Wanker | Nov 2007 | B1 |
| 7392224 | Bauer et al. | Jun 2008 | B1 |
| 7428505 | Levy et al. | Sep 2008 | B1 |
| 7430521 | Walker et al. | Sep 2008 | B2 |
| 7455226 | Hammond et al. | Nov 2008 | B1 |
| 7472073 | Masi | Dec 2008 | B1 |
| 7493268 | Kepros et al. | Feb 2009 | B2 |
| 7496520 | Handel et al. | Feb 2009 | B1 |
| 7499889 | Golan et al. | Mar 2009 | B2 |
| 7506805 | Chakravarthy | Mar 2009 | B1 |
| 7512551 | Postrel | Mar 2009 | B2 |
| 7596566 | Patwardhan | Sep 2009 | B1 |
| 7599858 | Grady et al. | Oct 2009 | B1 |
| 7618318 | Ciancio et al. | Nov 2009 | B2 |
| 7630935 | Loeger et al. | Dec 2009 | B2 |
| 7647278 | Foth et al. | Jan 2010 | B1 |
| 7653572 | Thompson | Jan 2010 | B1 |
| 7660743 | Messa et al. | Feb 2010 | B1 |
| 7665660 | Degliantoni et al. | Feb 2010 | B2 |
| 7668749 | Kepros et al. | Feb 2010 | B2 |
| 7676467 | Kozyrczak et al. | Mar 2010 | B1 |
| 7681786 | Chakravarthy | Mar 2010 | B1 |
| 7702540 | Woolston | Apr 2010 | B1 |
| 7706808 | Aggarwal et al. | Apr 2010 | B1 |
| 7711586 | Aggarwal et al. | May 2010 | B2 |
| 7734486 | Mortimore, Jr. | Jun 2010 | B2 |
| 7739134 | Mortimore, Jr. | Jun 2010 | B2 |
| 7742954 | Handel et al. | Jun 2010 | B1 |
| 7743002 | Hernandez | Jun 2010 | B2 |
| 7747524 | Brown | Jun 2010 | B2 |
| 7765119 | Messa et al. | Jun 2010 | B2 |
| 7752328 | Mortimore, Jr. et al. | Jul 2010 | B2 |
| 7788141 | Sim | Aug 2010 | B1 |
| 7797199 | Forshaw et al. | Sep 2010 | B2 |
| 7801760 | Handel et al. | Sep 2010 | B2 |
| 7806328 | Chakravarthy | Oct 2010 | B2 |
| 7814029 | Siegel | Oct 2010 | B1 |
| 7844488 | Merriman et al. | Nov 2010 | B2 |
| 7844490 | Patterson | Nov 2010 | B2 |
| 7865513 | Welch et al. | Jan 2011 | B2 |
| 7870022 | Bous et al. | Jan 2011 | B2 |
| 7899704 | Thompson | Mar 2011 | B1 |
| 7925540 | Orttung et al. | Apr 2011 | B1 |
| 7933810 | Morgenstern | Apr 2011 | B2 |
| 7937330 | Handel et al. | May 2011 | B2 |
| 7941374 | Orttung et al. | May 2011 | B2 |
| 7958017 | Rempe et al. | Jun 2011 | B1 |
| 7962381 | Handel et al. | Jun 2011 | B2 |
| 7966213 | Messa et al. | Jun 2011 | B2 |
| 7970666 | Handel | Jun 2011 | B1 |
| 7991664 | Stone | Aug 2011 | B1 |
| 8070056 | Feldman et al. | Dec 2011 | B2 |
| 8073719 | Orttung et al. | Dec 2011 | B2 |
| 8078496 | Postrel | Dec 2011 | B2 |
| 8082270 | Goyal | Dec 2011 | B2 |
| 8090707 | Orttung et al. | Jan 2012 | B1 |
| 8095402 | Orttung et al. | Jan 2012 | B2 |
| 8108304 | Loeger et al. | Jan 2012 | B2 |
| 8117073 | Orttung et al. | Feb 2012 | B1 |
| 8121953 | Orttung et al. | Feb 2012 | B1 |
| 8126771 | Walker et al. | Feb 2012 | B2 |
| 8126776 | Messa et al. | Feb 2012 | B2 |
| 8131588 | Walker et al. | Mar 2012 | B2 |
| 8140387 | Heywood | Mar 2012 | B2 |
| 8145522 | Warren et al. | Mar 2012 | B2 |
| 8160922 | Postrel | Apr 2012 | B2 |
| 8170916 | Dicker et al. | May 2012 | B1 |
| 8175926 | Handel et al. | May 2012 | B1 |
| 8180682 | Narayanaswami et al. | May 2012 | B2 |
| 8180796 | Mah et al. | May 2012 | B1 |
| 8213423 | Breau | Jul 2012 | B1 |
| 8249934 | Agarwal et al. | Aug 2012 | B2 |
| 8438061 | Grimes | May 2013 | B2 |
| 8459551 | Lee et al. | Jun 2013 | B2 |
| 8463643 | Bennett | Jun 2013 | B2 |
| 8463706 | Cervenka et al. | Jun 2013 | B2 |
| 8463851 | Bennett et al. | Jun 2013 | B2 |
| 8468053 | Bennett | Jun 2013 | B2 |
| 8473334 | Gibbs | Jun 2013 | B2 |
| 8484088 | Orttung et al. | Jul 2013 | B1 |
| 8484093 | Bennett et al. | Jul 2013 | B2 |
| 8489452 | Warner et al. | Jul 2013 | B1 |
| 8489456 | Burgess et al. | Jul 2013 | B2 |
| 8494901 | Magadi et al. | Jul 2013 | B2 |
| 8494914 | Mesaros | Jul 2013 | B2 |
| 8504411 | Subasic | Aug 2013 | B1 |
| 8504423 | Rotbard et al. | Aug 2013 | B2 |
| 8515810 | Grimes | Aug 2013 | B2 |
| 8517258 | Taylor et al. | Aug 2013 | B2 |
| 8543470 | Grady et al. | Sep 2013 | B2 |
| 8554670 | Blank | Oct 2013 | B1 |
| 8560389 | Burgess et al. | Oct 2013 | B2 |
| 8573477 | Bennett et al. | Nov 2013 | B2 |
| 8573491 | Bennett et al. | Nov 2013 | B2 |
| 8606630 | Fordyce, III et al. | Dec 2013 | B2 |
| 8615426 | Carlson | Dec 2013 | B2 |
| 8621068 | Zohar | Dec 2013 | B2 |
| 8621215 | Iyer | Dec 2013 | B1 |
| 8626579 | Fordyce, III et al. | Jan 2014 | B2 |
| 8639567 | Winters | Jan 2014 | B2 |
| 8650071 | Pointer et al. | Feb 2014 | B2 |
| 8655695 | Qu | Feb 2014 | B1 |
| 8725635 | Klein et al. | May 2014 | B2 |
| 8874674 | Allison et al. | Oct 2014 | B2 |
| 9009082 | Marshall et al. | Apr 2015 | B1 |
| 9031866 | Ng et al. | May 2015 | B1 |
| 9430773 | Aloni et al. | Aug 2016 | B2 |
| 9443262 | Mamgain | Sep 2016 | B1 |
| 20010014868 | Herz et al. | Aug 2001 | A1 |
| 20010020242 | Gupta | Sep 2001 | A1 |
| 20010037254 | Glikman | Nov 2001 | A1 |
| 20010054003 | Chien et al. | Dec 2001 | A1 |
| 20020052841 | Guthrie | May 2002 | A1 |
| 20020069079 | Vega | Jun 2002 | A1 |
| 20020069312 | Jones | Jun 2002 | A1 |
| 20020082920 | Austin et al. | Jun 2002 | A1 |
| 20020095357 | Hunter et al. | Jul 2002 | A1 |
| 20020099824 | Bender | Jul 2002 | A1 |
| 20020138343 | Weatherford et al. | Sep 2002 | A1 |
| 20020178056 | Lim | Nov 2002 | A1 |
| 20030004802 | Callegari | Jan 2003 | A1 |
| 20030027630 | Kelly et al. | Feb 2003 | A1 |
| 20030028426 | Banerjee | Feb 2003 | A1 |
| 20030028518 | Mankoff | Feb 2003 | A1 |
| 20030033211 | Haines et al. | Feb 2003 | A1 |
| 20030061093 | Todd | Mar 2003 | A1 |
| 20030078832 | Alvarez et al. | Apr 2003 | A1 |
| 20030208442 | Cockrill et al. | Nov 2003 | A1 |
| 20030233278 | Marshall | Dec 2003 | A1 |
| 20040006509 | Mannik et al. | Jan 2004 | A1 |
| 20040039686 | Klebenoff | Feb 2004 | A1 |
| 20040098326 | James | May 2004 | A1 |
| 20040098332 | Dvir | May 2004 | A1 |
| 20040122736 | Stock et al. | Jun 2004 | A1 |
| 20040153389 | Lortscher | Aug 2004 | A1 |
| 20040215517 | Chen | Oct 2004 | A1 |
| 20040225509 | Andre et al. | Nov 2004 | A1 |
| 20040225573 | Ling | Nov 2004 | A1 |
| 20040243468 | Cohagan et al. | Dec 2004 | A1 |
| 20050010394 | Bergeron | Jan 2005 | A1 |
| 20050010428 | Bergeron | Jan 2005 | A1 |
| 20050010472 | Quatse et al. | Jan 2005 | A1 |
| 20050021401 | Postrel | Jan 2005 | A1 |
| 20050033583 | Bergeron | Feb 2005 | A1 |
| 20050033605 | Bergeron | Feb 2005 | A1 |
| 20050065848 | Mitchell et al. | Mar 2005 | A1 |
| 20050071225 | Bortolin et al. | Mar 2005 | A1 |
| 20050071227 | Hammad et al. | Mar 2005 | A1 |
| 20050071228 | Bortolin et al. | Mar 2005 | A1 |
| 20050071230 | Mankoff | Mar 2005 | A1 |
| 20050075932 | Mankoff | Apr 2005 | A1 |
| 20050096976 | Nelms | May 2005 | A1 |
| 20050149394 | Postrel | Jul 2005 | A1 |
| 20050159996 | Lazarus | Jul 2005 | A1 |
| 20050165684 | Jensen | Jul 2005 | A1 |
| 20050192863 | Mohan | Sep 2005 | A1 |
| 20050234753 | Pinto | Oct 2005 | A1 |
| 20050240477 | Friday et al. | Oct 2005 | A1 |
| 20050246272 | Kitada et al. | Nov 2005 | A1 |
| 20050273388 | Roetter | Dec 2005 | A1 |
| 20060004633 | Ashbaugh | Jan 2006 | A1 |
| 20060026067 | Nicholas et al. | Feb 2006 | A1 |
| 20060041480 | Briggs | Feb 2006 | A1 |
| 20060053056 | Alspach-Goss et al. | Mar 2006 | A1 |
| 20060064372 | Gupta | Mar 2006 | A1 |
| 20060074749 | Kline | Apr 2006 | A1 |
| 20060076400 | Fletcher | Apr 2006 | A1 |
| 20060085240 | Salehi-sedeh et al. | Apr 2006 | A1 |
| 20060095434 | McCullough et al. | May 2006 | A1 |
| 20060111930 | Ayer et al. | May 2006 | A1 |
| 20060116800 | Obradovich et al. | Jun 2006 | A1 |
| 20060122874 | Postrel | Jun 2006 | A1 |
| 20060129426 | Pearson | Jun 2006 | A1 |
| 20060136299 | Ruhmkorf | Jun 2006 | A1 |
| 20060155603 | Abendroth et al. | Jul 2006 | A1 |
| 20060155641 | Postrel | Jul 2006 | A1 |
| 20060167753 | Teague et al. | Jul 2006 | A1 |
| 20060173672 | Bergeron | Aug 2006 | A1 |
| 20060178932 | Lang | Aug 2006 | A1 |
| 20060195359 | Robinson et al. | Aug 2006 | A1 |
| 20060212355 | Teague et al. | Sep 2006 | A1 |
| 20060224449 | Byerley et al. | Oct 2006 | A1 |
| 20060241859 | Kimchi et al. | Oct 2006 | A1 |
| 20060242011 | Bell et al. | Oct 2006 | A1 |
| 20060253321 | Heywood | Nov 2006 | A1 |
| 20060258397 | Kaplan et al. | Nov 2006 | A1 |
| 20060259364 | Strock et al. | Nov 2006 | A1 |
| 20060271552 | McChesney et al. | Nov 2006 | A1 |
| 20060293957 | Petersen | Dec 2006 | A1 |
| 20070000997 | Lambert et al. | Jan 2007 | A1 |
| 20070010942 | Bill | Jan 2007 | A1 |
| 20070022019 | Sherwin et al. | Jan 2007 | A1 |
| 20070033104 | Collins | Feb 2007 | A1 |
| 20070038515 | Postrel | Feb 2007 | A1 |
| 20070038516 | Apple et al. | Feb 2007 | A1 |
| 20070050258 | Dohse | Mar 2007 | A1 |
| 20070061216 | Jain et al. | Mar 2007 | A1 |
| 20070061223 | Rodriguez et al. | Mar 2007 | A1 |
| 20070073599 | Perry et al. | Mar 2007 | A1 |
| 20070083428 | Goldstein | Apr 2007 | A1 |
| 20070094114 | Bulford et al. | Apr 2007 | A1 |
| 20070129995 | Brandow | Jun 2007 | A1 |
| 20070130000 | Assanassios | Jun 2007 | A1 |
| 20070136135 | Loeger et al. | Jun 2007 | A1 |
| 20070146812 | Lawton | Jun 2007 | A1 |
| 20070150349 | Handel et al. | Jun 2007 | A1 |
| 20070157237 | Cordray | Jul 2007 | A1 |
| 20070192178 | Fung et al. | Aug 2007 | A1 |
| 20070192192 | Haberman et al. | Aug 2007 | A1 |
| 20070198354 | Senghore et al. | Aug 2007 | A1 |
| 20070198432 | Pitroda et al. | Aug 2007 | A1 |
| 20070198937 | Paris | Aug 2007 | A1 |
| 20070208879 | Liu | Sep 2007 | A1 |
| 20070210152 | Read | Sep 2007 | A1 |
| 20070214040 | Patel et al. | Sep 2007 | A1 |
| 20070233517 | Dayal | Oct 2007 | A1 |
| 20070244741 | Blume | Oct 2007 | A1 |
| 20070244811 | Tumminaro | Oct 2007 | A1 |
| 20070260513 | Pavlov | Nov 2007 | A1 |
| 20070260523 | Schadt et al. | Nov 2007 | A1 |
| 20070288312 | Wang | Dec 2007 | A1 |
| 20070288372 | Behar et al. | Dec 2007 | A1 |
| 20080004917 | Mortimore, Jr. | Jan 2008 | A1 |
| 20080004919 | Stubbs | Jan 2008 | A1 |
| 20080004980 | Hernandez | Jan 2008 | A1 |
| 20080005148 | Welch et al. | Jan 2008 | A1 |
| 20080021772 | Aloni et al. | Jan 2008 | A1 |
| 20080032720 | Mamdani et al. | Feb 2008 | A1 |
| 20080033857 | Moses | Feb 2008 | A1 |
| 20080040211 | Walker et al. | Feb 2008 | A1 |
| 20080040288 | Mortimore, Jr. et al. | Feb 2008 | A1 |
| 20080052140 | Neal | Feb 2008 | A1 |
| 20080052151 | Xie et al. | Feb 2008 | A1 |
| 20080059220 | Roth et al. | Mar 2008 | A1 |
| 20080065491 | Bakman | Mar 2008 | A1 |
| 20080082418 | Fordyce et al. | Apr 2008 | A1 |
| 20080091445 | Mihic | Apr 2008 | A1 |
| 20080091528 | Rampell et al. | Apr 2008 | A1 |
| 20080091537 | Miller et al. | Apr 2008 | A1 |
| 20080091549 | Chang et al. | Apr 2008 | A1 |
| 20080091828 | Mortimore, Jr. | Apr 2008 | A1 |
| 20080092162 | Lundy | Apr 2008 | A1 |
| 20080109317 | Singh et al. | May 2008 | A1 |
| 20080109489 | Sherwood | May 2008 | A1 |
| 20080120155 | Pliha | May 2008 | A1 |
| 20080126515 | Chambers | May 2008 | A1 |
| 20080133488 | Bandaru | Jun 2008 | A1 |
| 20080147450 | Mortimore, Jr. | Jun 2008 | A1 |
| 20080147514 | Shuster et al. | Jun 2008 | A1 |
| 20080147773 | Aaron | Jun 2008 | A1 |
| 20080154664 | Kuo et al. | Jun 2008 | A1 |
| 20080162206 | Mak et al. | Jul 2008 | A1 |
| 20080167991 | Carlson et al. | Jul 2008 | A1 |
| 20080189169 | Turpin et al. | Aug 2008 | A1 |
| 20080195475 | Lambert et al. | Aug 2008 | A1 |
| 20080195609 | Paris | Aug 2008 | A1 |
| 20080196060 | Varghese | Aug 2008 | A1 |
| 20080201197 | Orttung et al. | Aug 2008 | A1 |
| 20080201224 | Owens et al. | Aug 2008 | A1 |
| 20080201432 | Orttung et al. | Aug 2008 | A1 |
| 20080210753 | Plozay et al. | Sep 2008 | A1 |
| 20080255940 | Perreault et al. | Oct 2008 | A1 |
| 20080262925 | Kim | Oct 2008 | A1 |
| 20080263135 | Olliphant | Oct 2008 | A1 |
| 20080270223 | Collins et al. | Oct 2008 | A1 |
| 20080270251 | Coelho et al. | Oct 2008 | A1 |
| 20080276270 | Kotaru et al. | Nov 2008 | A1 |
| 20080281699 | Whitehead | Nov 2008 | A1 |
| 20080281710 | Hoal | Nov 2008 | A1 |
| 20080294624 | Kanigsberg et al. | Nov 2008 | A1 |
| 20080300894 | John | Dec 2008 | A1 |
| 20080300979 | Abhyanker | Dec 2008 | A1 |
| 20090006142 | Orttung et al. | Jan 2009 | A1 |
| 20090006143 | Orttung et al. | Jan 2009 | A1 |
| 20090006188 | Guo et al. | Jan 2009 | A1 |
| 20090006194 | Sridharan et al. | Jan 2009 | A1 |
| 20090012839 | Fusillo et al. | Jan 2009 | A1 |
| 20090018916 | Seven et al. | Jan 2009 | A1 |
| 20090030609 | Orttung et al. | Jan 2009 | A1 |
| 20090030742 | Orttung et al. | Jan 2009 | A1 |
| 20090030769 | Orttung et al. | Jan 2009 | A1 |
| 20090030779 | Tollinger et al. | Jan 2009 | A1 |
| 20090037264 | Del Favero et al. | Feb 2009 | A1 |
| 20090055292 | Chong et al. | Feb 2009 | A1 |
| 20090063268 | Burgess et al. | Mar 2009 | A1 |
| 20090063351 | Schmeyer et al. | Mar 2009 | A1 |
| 20090076912 | Rajan et al. | Mar 2009 | A1 |
| 20090094048 | Wallace et al. | Apr 2009 | A1 |
| 20090125719 | Cochran | May 2009 | A1 |
| 20090132347 | Anderson et al. | May 2009 | A1 |
| 20090140799 | Kasperkovitz | Jun 2009 | A1 |
| 20090150272 | Blythe | Jun 2009 | A1 |
| 20090156310 | Fargo | Jun 2009 | A1 |
| 20090163227 | Collins | Jun 2009 | A1 |
| 20090164314 | Blythe | Jun 2009 | A1 |
| 20090171842 | Blythe | Jul 2009 | A1 |
| 20090171853 | Georgiou et al. | Jul 2009 | A1 |
| 20090182718 | Waclawik et al. | Jul 2009 | A1 |
| 20090210261 | Mortimore, Jr. et al. | Aug 2009 | A1 |
| 20090228365 | Tomchek et al. | Sep 2009 | A1 |
| 20090247193 | Kalavade | Oct 2009 | A1 |
| 20090247282 | Cheng | Oct 2009 | A1 |
| 20090248457 | Munter et al. | Oct 2009 | A1 |
| 20090248543 | Nihalani et al. | Oct 2009 | A1 |
| 20090259499 | Bhojwani et al. | Oct 2009 | A1 |
| 20090265236 | Schultz et al. | Oct 2009 | A1 |
| 20090271263 | Regmi et al. | Oct 2009 | A1 |
| 20090276306 | Hicks | Nov 2009 | A1 |
| 20090287562 | Bosch et al. | Nov 2009 | A1 |
| 20090288012 | Hertel et al. | Nov 2009 | A1 |
| 20090288140 | Huber | Nov 2009 | A1 |
| 20090289111 | Motycka et al. | Nov 2009 | A1 |
| 20090313109 | Bous et al. | Dec 2009 | A1 |
| 20090319353 | Palmeri | Dec 2009 | A1 |
| 20090327062 | Botes | Dec 2009 | A1 |
| 20090327129 | Collas | Dec 2009 | A1 |
| 20090327174 | Honkala | Dec 2009 | A1 |
| 20100002722 | Porat | Jan 2010 | A1 |
| 20100057565 | Au-Yeung et al. | Mar 2010 | A1 |
| 20100076777 | Paretti et al. | Mar 2010 | A1 |
| 20100079336 | Skibiski et al. | Apr 2010 | A1 |
| 20100082418 | Loeger et al. | Apr 2010 | A1 |
| 20100082446 | Hjelm et al. | Apr 2010 | A1 |
| 20100088174 | Cohagan et al. | Apr 2010 | A1 |
| 20100094697 | Cananaugh | Apr 2010 | A1 |
| 20100094698 | Cawley | Apr 2010 | A1 |
| 20100094699 | Beal | Apr 2010 | A1 |
| 20100106568 | Grimes | Apr 2010 | A1 |
| 20100106569 | Grimes | Apr 2010 | A1 |
| 20100106578 | Allio et al. | Apr 2010 | A1 |
| 20100106596 | Grimes | Apr 2010 | A1 |
| 20100114661 | Alderfer | May 2010 | A1 |
| 20100114686 | Carlson et al. | May 2010 | A1 |
| 20100131342 | Thibedeau | May 2010 | A1 |
| 20100131840 | Walker et al. | May 2010 | A1 |
| 20100138299 | Preston et al. | Jun 2010 | A1 |
| 20100145744 | Beck et al. | Jun 2010 | A1 |
| 20100145762 | Coladonato et al. | Jun 2010 | A1 |
| 20100145778 | Fordyce et al. | Jun 2010 | A1 |
| 20100145786 | Fordyce, III et al. | Jun 2010 | A1 |
| 20100145860 | Pelegero | Jun 2010 | A1 |
| 20100153194 | Oram | Jun 2010 | A1 |
| 20100179879 | Cunningham et al. | Jul 2010 | A1 |
| 20100191572 | Newman et al. | Jul 2010 | A1 |
| 20100203963 | Allen | Aug 2010 | A1 |
| 20100211419 | Nickolayev et al. | Aug 2010 | A1 |
| 20100228613 | Anderson et al. | Sep 2010 | A1 |
| 20100241502 | Walker et al. | Sep 2010 | A1 |
| 20100241559 | O'Connor et al. | Sep 2010 | A1 |
| 20100250351 | Gillenson et al. | Sep 2010 | A1 |
| 20100250356 | Gillenson et al. | Sep 2010 | A1 |
| 20100257047 | Foodman et al. | Oct 2010 | A1 |
| 20100262456 | Feng et al. | Oct 2010 | A1 |
| 20100312629 | Wolf et al. | Dec 2010 | A1 |
| 20100324990 | D'Angelo et al. | Dec 2010 | A1 |
| 20100332307 | Parento | Dec 2010 | A1 |
| 20110004497 | Mortimore, Jr. et al. | Jan 2011 | A1 |
| 20110022448 | Strock et al. | Jan 2011 | A1 |
| 20110022455 | Wolf et al. | Jan 2011 | A1 |
| 20110029363 | Gillenson et al. | Feb 2011 | A1 |
| 20110029364 | Roeding et al. | Feb 2011 | A1 |
| 20110029367 | Olson et al. | Feb 2011 | A1 |
| 20110035266 | Patterson | Feb 2011 | A1 |
| 20110040539 | Szymczyk et al. | Feb 2011 | A1 |
| 20110047023 | Lieblang et al. | Feb 2011 | A1 |
| 20110055880 | Archer | Mar 2011 | A1 |
| 20110066483 | Salmon et al. | Mar 2011 | A1 |
| 20110066548 | Rodin | Mar 2011 | A1 |
| 20110078030 | Borst et al. | Mar 2011 | A1 |
| 20110078055 | Faribault et al. | Mar 2011 | A1 |
| 20110083101 | Sharon et al. | Apr 2011 | A1 |
| 20110087530 | Fordyce et al. | Apr 2011 | A1 |
| 20110087531 | Winters et al. | Apr 2011 | A1 |
| 20110093327 | Fordyce et al. | Apr 2011 | A1 |
| 20110093335 | Fordyce et al. | Apr 2011 | A1 |
| 20110093361 | Morales | Apr 2011 | A1 |
| 20110106607 | Alfonso et al. | May 2011 | A1 |
| 20110119133 | Igelman et al. | May 2011 | A1 |
| 20110125561 | Marcus | May 2011 | A1 |
| 20110125565 | MacIlwaine et al. | May 2011 | A1 |
| 20110131077 | Tan | Jun 2011 | A1 |
| 20110137716 | Reuthe et al. | Jun 2011 | A1 |
| 20110137717 | Reuthe et al. | Jun 2011 | A1 |
| 20110137721 | Bansal | Jun 2011 | A1 |
| 20110145047 | Chetty et al. | Jun 2011 | A1 |
| 20110145149 | Valdes et al. | Jun 2011 | A1 |
| 20110161149 | Kaplan | Jun 2011 | A1 |
| 20110161154 | McLaughlin et al. | Jun 2011 | A1 |
| 20110161172 | Lee | Jun 2011 | A1 |
| 20110167440 | Greenfield | Jul 2011 | A1 |
| 20110178928 | Carmichael et al. | Jul 2011 | A1 |
| 20110184792 | Butcher et al. | Jul 2011 | A1 |
| 20110191150 | Blackhurst et al. | Aug 2011 | A1 |
| 20110023124 | Bhatia et al. | Sep 2011 | A1 |
| 20110213670 | Strutton | Sep 2011 | A1 |
| 20110218031 | Bryant et al. | Sep 2011 | A1 |
| 20110225033 | Schmeyer et al. | Sep 2011 | A1 |
| 20110231224 | Winters | Sep 2011 | A1 |
| 20110231235 | MacIlwaine et al. | Sep 2011 | A1 |
| 20110231246 | Bhatia | Sep 2011 | A1 |
| 20110238469 | Gershman et al. | Sep 2011 | A1 |
| 20110246219 | Smith | Oct 2011 | A1 |
| 20110246280 | Satyavolu et al. | Oct 2011 | A1 |
| 20110246281 | Satyavolu et al. | Oct 2011 | A1 |
| 20110246287 | Wright et al. | Oct 2011 | A1 |
| 20110246299 | Satyavolu et al. | Oct 2011 | A1 |
| 20110251883 | Satyavolu et al. | Oct 2011 | A1 |
| 20110251891 | Satyavolu et al. | Oct 2011 | A1 |
| 20110251934 | Satyavolu et al. | Oct 2011 | A1 |
| 20110258011 | Burns | Oct 2011 | A1 |
| 20110264490 | Durvasula et al. | Oct 2011 | A1 |
| 20110270617 | Pacheco E Murta et al. | Nov 2011 | A1 |
| 20110270666 | Welsh et al. | Nov 2011 | A1 |
| 20110276373 | Juszczak et al. | Nov 2011 | A1 |
| 20110276377 | Kim et al. | Nov 2011 | A1 |
| 20110282702 | Mortimore, Jr. | Nov 2011 | A1 |
| 20110288918 | Cervenka et al. | Nov 2011 | A1 |
| 20110295689 | Brady | Dec 2011 | A1 |
| 20110295749 | Scalisi | Dec 2011 | A1 |
| 20110302011 | Yoder et al. | Dec 2011 | A1 |
| 20110307509 | Hsiao | Dec 2011 | A1 |
| 20110313840 | Mason et al. | Dec 2011 | A1 |
| 20110313874 | Hardie et al. | Dec 2011 | A1 |
| 20110320250 | Gemmell et al. | Dec 2011 | A1 |
| 20120004964 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004965 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004966 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004967 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004968 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004969 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004970 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004975 | Satyavolu et al. | Jan 2012 | A1 |
| 20120010932 | Satyavolu et al. | Jan 2012 | A1 |
| 20120010933 | Satyavolu et al. | Jan 2012 | A1 |
| 20120010934 | Walker et al. | Jan 2012 | A1 |
| 20120010936 | Satyavolu et al. | Jan 2012 | A1 |
| 20120010937 | Hanson et al. | Jan 2012 | A1 |
| 20120022923 | Walker et al. | Jan 2012 | A1 |
| 20120023122 | Gregov et al. | Jan 2012 | A1 |
| 20120029990 | Fisher | Feb 2012 | A1 |
| 20120029996 | Lang et al. | Feb 2012 | A1 |
| 20120030048 | Manley et al. | Feb 2012 | A1 |
| 20120035965 | Maguire | Feb 2012 | A1 |
| 20120035997 | Burgess et al. | Feb 2012 | A1 |
| 20120036079 | Sushil et al. | Feb 2012 | A1 |
| 20120036178 | Gavini | Feb 2012 | A1 |
| 20120046958 | Pynadath | Feb 2012 | A1 |
| 20120047008 | Alhadeff et al. | Feb 2012 | A1 |
| 20120053987 | Satyavolu et al. | Mar 2012 | A1 |
| 20120059701 | Van der Veen et al. | Mar 2012 | A1 |
| 20120066037 | Glen | Mar 2012 | A1 |
| 20120066046 | Satyavolu et al. | Mar 2012 | A1 |
| 20120066050 | Satyavolu et al. | Mar 2012 | A1 |
| 20120066051 | Black et al. | Mar 2012 | A1 |
| 20120066062 | Yoder et al. | Mar 2012 | A1 |
| 20120072270 | Waylonis et al. | Mar 2012 | A1 |
| 20120078689 | Rothschild | Mar 2012 | A1 |
| 20120101881 | Taylor et al. | Apr 2012 | A1 |
| 20120109751 | Binenstock et al. | May 2012 | A1 |
| 20120130737 | Finizio | May 2012 | A1 |
| 20120150641 | Dobbs | Jun 2012 | A1 |
| 20120150740 | Isaacson et al. | Jun 2012 | A1 |
| 20120196568 | Bakshi | Aug 2012 | A1 |
| 20120197707 | Cohagan | Aug 2012 | A1 |
| 20120203604 | Brown et al. | Aug 2012 | A1 |
| 20120203846 | Hull et al. | Aug 2012 | A1 |
| 20120209672 | Winner et al. | Aug 2012 | A1 |
| 20120209695 | Winner et al. | Aug 2012 | A1 |
| 20120209696 | Winner et al. | Aug 2012 | A1 |
| 20120209771 | Winner et al. | Aug 2012 | A1 |
| 20120220308 | Ledlie | Aug 2012 | A1 |
| 20120221437 | Yoo | Aug 2012 | A1 |
| 20120221479 | Schneck et al. | Aug 2012 | A1 |
| 20120226530 | Gebb et al. | Sep 2012 | A1 |
| 20120239417 | Pourfallah | Sep 2012 | A1 |
| 20120239479 | Amaro et al. | Sep 2012 | A1 |
| 20120246004 | Book | Sep 2012 | A1 |
| 20120253852 | Pourfallah | Oct 2012 | A1 |
| 20120253957 | Bakshi | Oct 2012 | A1 |
| 20120278127 | Kirakosyan et al. | Nov 2012 | A1 |
| 20120296724 | Faro et al. | Nov 2012 | A1 |
| 20120303425 | Katzin et al. | Nov 2012 | A1 |
| 20120303430 | Tiku et al. | Nov 2012 | A1 |
| 20130006737 | Goldberg | Jan 2013 | A1 |
| 20130006766 | Dedeoglu | Jan 2013 | A1 |
| 20130013396 | Vinson | Jan 2013 | A1 |
| 20130024256 | Wolf et al. | Jan 2013 | A1 |
| 20130040654 | Parish | Feb 2013 | A1 |
| 20130041902 | Swann et al. | Feb 2013 | A1 |
| 20130060623 | Walker et al. | Mar 2013 | A1 |
| 20130060644 | Le Ouay | Mar 2013 | A1 |
| 20130073336 | Heath | Mar 2013 | A1 |
| 20130073361 | Silver | Mar 2013 | A1 |
| 20130073366 | Heath | Mar 2013 | A1 |
| 20130073371 | Bosworth et al. | Mar 2013 | A1 |
| 20130073374 | Heath | Mar 2013 | A1 |
| 20130073376 | Heath | Mar 2013 | A1 |
| 20130073377 | Heath | Mar 2013 | A1 |
| 20130073387 | Heath | Mar 2013 | A1 |
| 20130073388 | Heath | Mar 2013 | A1 |
| 20130073389 | Heath | Mar 2013 | A1 |
| 20130073400 | Heath | Mar 2013 | A1 |
| 20130073473 | Heath | Mar 2013 | A1 |
| 20130073568 | Federov et al. | Mar 2013 | A1 |
| 20130080259 | Durvasula | Mar 2013 | A1 |
| 20130091000 | Hagey et al. | Apr 2013 | A1 |
| 20130103472 | Burgess et al. | Apr 2013 | A1 |
| 20130110555 | Dunham | May 2013 | A1 |
| 20130110604 | Rooke et al. | May 2013 | A1 |
| 20130124283 | Kaulbach | May 2013 | A1 |
| 20130132175 | Claessen et al. | May 2013 | A1 |
| 20130132183 | Klein et al. | May 2013 | A1 |
| 20130145016 | Vantalon | Jun 2013 | A1 |
| 20130151602 | McClelland et al. | Jun 2013 | A1 |
| 20130173320 | Bank et al. | Jul 2013 | A1 |
| 20130173478 | Farhi | Jul 2013 | A1 |
| 20130178280 | Ganz | Jul 2013 | A1 |
| 20130179246 | Ross et al. | Jul 2013 | A1 |
| 20130191195 | Carlson et al. | Jul 2013 | A1 |
| 20130212177 | Friedman | Aug 2013 | A1 |
| 20130218653 | Rooke et al. | Aug 2013 | A1 |
| 20130227636 | Bettini | Aug 2013 | A1 |
| 20130238412 | Boncyk et al. | Sep 2013 | A1 |
| 20130246146 | Fischer et al. | Sep 2013 | A1 |
| 20130246185 | Hardman et al. | Sep 2013 | A1 |
| 20130260727 | Knudson et al. | Oct 2013 | A1 |
| 20130262209 | Boyer | Oct 2013 | A1 |
| 20130268333 | Ovick et al. | Oct 2013 | A1 |
| 20130275192 | Aissa | Oct 2013 | A1 |
| 20130304563 | Haupt et al. | Nov 2013 | A1 |
| 20130325946 | Allison, Jr. et al. | Dec 2013 | A1 |
| 20130346170 | Epstein et al. | Dec 2013 | A1 |
| 20140006129 | Heath | Jan 2014 | A1 |
| 20140006132 | Barker | Jan 2014 | A1 |
| 20140025451 | Knowles et al. | Jan 2014 | A1 |
| 20140025452 | Knowles et al. | Jan 2014 | A1 |
| 20140025453 | Knowles et al. | Jan 2014 | A1 |
| 20140025460 | Knowles et al. | Jan 2014 | A1 |
| 20140046675 | Harwood | Feb 2014 | A1 |
| 20140046744 | Hagey | Feb 2014 | A1 |
| 20140046748 | Nagarajan et al. | Feb 2014 | A1 |
| 20140046794 | Vallery | Feb 2014 | A1 |
| 20140108108 | Artman et al. | Apr 2014 | A1 |
| 20140108521 | Marquess | Apr 2014 | A1 |
| 20140164199 | Wilkes | Jun 2014 | A1 |
| 20150039393 | Jain | Feb 2015 | A1 |
| 20150073925 | Renfroe | Mar 2015 | A1 |
| 20150073980 | Griffin | Mar 2015 | A1 |
| 20150100433 | Choy | Apr 2015 | A1 |
| 20150170256 | Pettyjohn | Jun 2015 | A1 |
| 20150248702 | Chatterton | Sep 2015 | A1 |
| 20160021152 | Maguire | Jan 2016 | A1 |
| 20160364790 | Lanpher | Dec 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 2001086378 | Nov 2001 | WO |
| 2012024109 | Feb 2012 | WO |
| 2012106114 | Aug 2012 | WO |
| 2012170088 | Dec 2012 | WO |
| 2013015846 | Jan 2013 | WO |
| 2014106207 | Jul 2014 | WO |
| 2015102889 | Jul 2015 | WO |
| 2015134947 | Sep 2015 | WO |
| Entry |
|---|
| USPTO; Advisory Action dated Jun. 10, 2015 in U.S. Appl. No. 13/477,806. |
| USPTO; Advisory Action dated Jun. 11, 2015 in U.S. Appl. No. 13/926,789. |
| USPTO; Advisory Action dated Jun. 15, 2015 in U.S. Appl. No. 13/715,770. |
| USPTO; Office Action dated Jun. 19, 2015 in U.S. Appl. No. 13/794,301. |
| USPTO; Office Action dated Jun. 25, 2015 in U.S. Appl. No. 13/889,307. |
| USPTO; Advisory Action dated Jun. 25, 2015 in U.S. Appl. No. 13/734,693. |
| USPTO; Advisory Action dated Jun. 26, 2015 in U.S. Appl. No. 13/794,145. |
| USPTO; Advisory Action dated Jun. 29, 2015 in U.S. Appl. No. 13/715,792. |
| USPTO; Office Action dated Jul. 10, 2015 in U.S. Appl. No. 13/794,374. |
| USPTO; Advisory Action dated Jul. 10, 2015 in U.S. Appl. No. 12/857,424. |
| USPTO; Office Action dated Jul. 10, 2015 in U.S. Appl. No. 13/411,281. |
| USPTO; Final Office Action dated Jul. 17, 2015 in U.S. Appl. No. 13/188,693. |
| USPTO; Final Office Action dated Jul. 20, 2015 in U.S. Appl. No. 13/686,608. |
| USPTO; Advisory Action dated Jul. 21, 2015 in U.S. Appl. No. 11/779,734. |
| USPTO; Final Office Action dated Jul. 23, 2015 in U.S. Appl. No. 13/466,445. |
| USPTO; Office Action dated Aug. 4, 2015 in U.S. Appl. No. 13/794,334. |
| USPTO; Office Action dated Aug. 5, 2015 in U.S. Appl. No. 13/926,789. |
| USPTO; Final Office Action dated Aug. 5, 2015 in U.S. Appl. No. 13/021,237. |
| USPTO; Final Office Action dated Aug. 7, 2015 in U.S. Appl. No. 13/889,299. |
| USPTO; Office Action dated Aug. 11, 2015 in U.S. Appl. No. 13/926,895. |
| USPTO; Final Office Action dated Aug. 12, 2015 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Aug. 17, 2015 in U.S. Appl. No. 14/065,883. |
| USPTO; Office Action dated Aug. 17, 2015 in U.S. Appl. No. 13/439,768. |
| USPTO; Office Action dated Aug. 19, 2015 in U.S. Appl. No. 13/926,884. |
| USPTO; Office Action dated Aug. 28, 2015 in U.S. Appl. No. 13/794,272. |
| Burke, “Hybrid Recommender Systems: Survey and Experiments,” User modeling and user-adapted interaction, 2002, Kluwer Academic Publishers, pp. 331-370. |
| Aimeur et al., “Alambic: a privacy-preserving recommender system for electronic commerce,” Feb. 27, 2008, Springer-Verlag, pp. 307-334. |
| Tang, “Approac to detection of community's consensus and interest,” Institute of Systems Science, 2008, Springer-Verlag, pp. 17-29. |
| Lee et al., “iJADE eMiner—A Web Based Mining Agent Based on Intelligent Java Agent Development Environment (iJADE) on Internet Shopping,” Advances in Knowledge Discovery and Data Mining, 2001, Springer-Verlag, pp. 28-40. |
| Written Opinion dated Aug. 5, 2015 in Singapore Application No. 11201400788P. |
| USPTO; Advisory Action dated Sep. 29, 2015 in U.S. Appl. No. 13/686,608. |
| USPTO; Notice of Allowance dated Sep. 29, 2015 in U.S. Appl. No. 13/715,792. |
| USPTO; Office Action dated Oct. 8, 2015 in U.S. Appl. No. 13/941,306. |
| USPTO; Advisory Action dated Oct. 13, 2015 in U.S. Appl. No. 13/021,237. |
| USPTO; Advisory Action dated Oct. 16, 2015 in U.S. Appl. No. 13/466,445. |
| USPTO; Final Office Action dated Oct. 16, 2015 in U.S. Appl. No. 13/443,100. |
| USPTO; Advisory Action dated Oct. 22, 2015 in U.S. Appl. No. 13/188,693. |
| USPTO; Final Office Action dated Oct. 26, 2015 in U.S. Appl. No. 13/476,910. |
| USPTO; Final Office Action dated Oct. 26, 2015 in U.S. Appl. No. 13/467,503. |
| USPTO; Advisory Action dated Nov. 17, 2015 in U.S. Appl. No. 13/889,299. |
| USPTO; Advisory Action dated Nov. 17, 2015 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Dec. 4, 2015 in U.S. Appl. No. 13/794,145. |
| USPTO; Office Action dated Dec. 17, 2015 in U.S. Appl. No. 13/715,770. |
| USPTO; Office Action dated Dec. 31, 2015 in U.S. Appl. No. 13/734,693. |
| USPTO; Final Office Action dated Dec. 30, 2015 in U.S. Appl. No. 14/065,883. |
| USPTO; Advisory Action dated Jan. 6, 2016 in U.S. Appl. No. 13/443,100. |
| USPTO; Final Office Action dated Jan. 11, 2016 in U.S. Appl. No. 13/411,281. |
| USPTO; Advisory Action dated Jan. 11, 2016 in U.S. Appl. No. 13/467,503. |
| USPTO; Office Action dated Jan. 14, 2016 in U.S. Appl. No. 13/889,272. |
| USPTO; Final Office Action dated Jan. 14, 2016 in U.S. Appl. No. 13/794,301. |
| USPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 13/467,503. |
| USPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 12/857,389. |
| USPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 13/466,412. |
| USPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 13/021,237. |
| USPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 13/466,445. |
| USPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 13/889,305. |
| USPTO; Office Action dated Mar. 7, 2014 in U.S. Appl. No. 13/889,285. |
| USPTO; Office Action dated Mar. 11, 2014 in U.S. Appl. No. 13/153,890. |
| USPTO; Final Office Action dated Mar. 13, 2014 in U.S. Appl. No. 13/889,272. |
| USPTO; Final Office Action dated Apr. 25, 2014 in U.S. Appl. No. 13/889,299. |
| USPTO; Final Office Action dated Apr. 28, 2014 in U.S. Appl. No. 13/889,288. |
| USPTO; Notice of Allowance dated May 22, 2014 in U.S. Appl. No. 13/245,636. |
| International Preliminary Report on Patentability dated Aug. 22, 2013 in PCT/US2012/056231. |
| USPTO; Office Action dated May 7, 2014 in U.S. Appl. No. 13/477,806. |
| USPTO; Final Office Action dated May 13, 2014 in U.S. Appl. No. 13/476,910. |
| USPTO; Final Office Action dated May 20, 2014 in U.S. Appl. No. 13/593,204. |
| USPTO; Advisory Action dated Jul. 8, 2014 in U.S. Appl. No. 13/889,299. |
| USPTO; Final Office Action dated May 29, 2014 in U.S. Appl. No. 13/468,931. |
| USPTO; Advisory Action dated Jun. 2, 2014 in U.S. Appl. No. 13/889,272. |
| USPTO; Office Action dated Jun. 5, 2014 in U.S. Appl. No. 11/779,734. |
| USPTO; Office Action dated Jun. 11, 2014 in U.S. Appl. No. 13/188,693. |
| USPTO; Final Office Action dated Jun. 16, 2014 in U.S. Appl. No. 13/467,503. |
| USPTO; Final Office Action dated Jun. 16, 2014 in U.S. Appl. No. 12/857,389. |
| USPTO; Final Office Action dated Jun. 16, 2014 in U.S. Appl. No. 13/466,412. |
| USPTO; Final Office Action dated Jun. 16, 2014 in U.S. Appl. No. 13/466,445. |
| USPTO; Office Action dated Jun. 24, 2014 in U.S. Appl. No. 13/468,880. |
| USPTO; Final Office Action dated Jun. 30, 2014 in U.S. Appl. No. 13/021,237. |
| USPTO; Final Office Action dated Jun. 30, 2014 in U.S. Appl. No. 13/889,305. |
| USPTO; Notice of Allowance dated Jul. 2, 2014 in U.S. Appl. No. 13/889,285. |
| USPTO; Advisory Action dated Jul. 2, 2014 in U.S. Appl. No. 13/889,288. |
| USPTO; Office Action dated Jul. 3, 2014 in U.S. Appl. No. 13/889,307. |
| International Preliminary Report on Patentability dated Sep. 19, 2012 in Application No. PCT/US2011/047012. |
| USPTO; Final Office Action dated Jan. 28, 2015 in U.S. Appl. No. 13/889,307. |
| USPTO; Office Action dated Oct. 11, 2013 in U.S. Appl. No. 13/245,636. |
| USPTO; Office Action dated Feb. 5, 2014 in U.S. Appl. No. 13/245,636. |
| USPTO; Office Action dated Jul. 30, 2014 in U.S. Appl. No. 13/794,301. |
| USPTO; Advisory Action dated Jul. 30, 2014 in U.S. Appl. No. 13/411,281. |
| USPTO; Advisory Action dated Jul. 30, 2014 in U.S. Appl. No. 13/593,204. |
| USPTO; Advisory Action dated Jul. 31, 2014 in U.S. Appl. No. 13/476,910. |
| USPTO; Advisory Action dated Aug. 7, 2014 in U.S. Appl. No. 13/468,931. |
| Examination Report dated Aug. 11, 2014 in New Zealand Application No. 623019. |
| USPTO; Final Office Action dated Aug. 13, 2014 in U.S. Appl. No. 13/153,890. |
| USPTO; Office Action dated Aug. 14, 2014 in U.S. Appl. No. 13/794,145. |
| USPTO; Office Action dated Aug. 14, 2014 in U.S. Appl. No. 13/794,334. |
| USPTO; Office Action dated Aug. 15, 2014 in U.S. Appl. No. 13/794,374. |
| USPTO; Advisory Action dated Sep. 3, 2014 in U.S. Appl. No. 13/466,412. |
| USPTO; Advisory Action dated Sep. 3, 2014 in U.S. Appl. No. 13/467,503. |
| USPTO; Advisory Action dated Sep. 3, 2014 in U.S. Appl. No. 13/021,237. |
| USPTO; Advisory Action dated Sep. 3, 2014 in U.S. Appl. No. 12/857,389. |
| USPTO; Advisory Action dated Sep. 2, 2014 in U.S. Appl. No. 13/466,445. |
| USPTO; Final Office Action dated Mar. 1, 2013 in U.S. Appl. No. 13/439,768. |
| USPTO; Final Office Action dated Mar. 4, 2013 in U.S. Appl. No. 13/594,528. |
| USPTO; Final Office Action dated Mar. 6, 2013 in U.S. Appl. No. 13/188,693. |
| USPTO; Final Office Action dated Jan. 10, 2013 in U.S. Appl. No. 13/468,931. |
| USPTO; Final Office Action dated Jan. 31, 2013 in U.S. Appl. No. 13/411,281. |
| USPTO; Final Office Action dated Jan. 31, 2013 in U.S. Appl. No. 13/467,910. |
| USPTO; Final Office Action dated Feb. 14, 2013 in U.S. Appl. No. 13/021,237. |
| USPTO; Final Office Action dated Feb. 25, 2013 in U.S. Appl. No. 13/477,806. |
| USPTO; Office Action dated May 2, 2013 in U.S. Appl. No. 13/468,880. |
| International Preliminary Report on Patentability dated on May 7, 2013 in Application No. PCT/US2012/021648. |
| USPTO; Advisory Action dated May 9, 2013 in U.S. Appl. No. 13/477,806. |
| USPTO; Advisory Action dated May 22, 2013 in U.S. Appl. No. 13/188,693. |
| USPTO; Office Action dated May 23, 2013 in U.S. Appl. No. 13/734,693. |
| International Preliminary Report on Patentability dated on May 23, 2013 in Application No. PCT/US2012/027810. |
| International Preliminary Report on Patentability dated on Jun. 28, 2013 in Application No. PCT/US2012/027664. |
| USPTO; Advisory Action dated Jun. 6, 2013 in U.S. Appl. No. 13/466,445. |
| USPTO; Office Action dated Jul. 19, 2013 in U.S. Appl. No. 13/715,423. |
| USPTO; Office Action dated Aug. 14, 2013 in U.S. Appl. No. 11/779,734. |
| USPTO; Final Office Action dated Aug. 14, 2013 in U.S. Appl. No. 12/857,424. |
| USPTO; Office Action dated Aug. 26, 2013 in U.S. Appl. No. 13/889,305. |
| USPTO; Office Action dated Aug. 27, 2013 in U.S. Appl. No. 13/889,285. |
| USPTO; Final Office Action dated Aug. 28, 2013 in U.S. Appl. No. 13/443,100. |
| USPTO; Office Action dated Sep. 23, 2013 in U.S. Appl. No. 13/889,307. |
| USPTO; Advisory Action dated Oct. 7, 2013 in U.S. Appl. No. 12/857,424. |
| USPTO; Advisory Action dated Oct. 4, 2013 in U.S. Appl. No. 13/468,880. |
| USPTO; Final Office Action dated Oct. 30, 2013 in U.S. Appl. No. 11/779,734. |
| USPTO; Restriction Requirement dated Oct. 30, 2013 in U.S. Appl. No. 13/889,288. |
| USPTO; Final Office Action dated Oct. 31, 2013 in U.S. Appl. No. 13/889,305. |
| USPTO; Advisory Action dated Nov. 5, 2013 in U.S. Appl. No. 13/443,100. |
| USPTO; Final Office Action dated Nov. 5, 2013 in U.S. Appl. No. 13/889,285. |
| USPTO; Office Action dated Nov. 6, 2013 in U.S. Appl. No. 13/889,272. |
| USPTO; Office Action dated Nov. 22, 2013 in U.S. Appl. No. 13/889,299. |
| USPTO; Final Office Action dated Nov. 26, 2013 in U.S. Appl. No. 13/734,693. |
| USPTO; Notice of Allowance dated Dec. 17, 2013 in U.S. Appl. No. 13/594,528. |
| USPTO; Office Action dated Jan. 3, 2014 in U.S. Appl. No. 13/889,288. |
| USPTO; Advisory Action dated Jan. 14, 2014 in U.S. Appl. No. 13/889,285. |
| USPTO; Office Action dated Jan. 15, 2014 in U.S. Appl. No. 13/411,281. |
| USPTO; Final Office Action dated Jan. 29, 2014 in U.S. Appl. No. 13/889,307. |
| USPTO; Office Action dated Jan. 30, 2014 in U.S. Appl. No. 13/476,910. |
| USPTO; Office Action dated Feb. 3, 2014 in U.S. Appl. No. 13/593,204. |
| International Preliminary Report on Patentability dated Feb. 3, 2014 in Application No. PCT/US2013/028209. |
| USPTO; Advisory Action dated Feb. 5, 2014 in U.S. Appl. No. 13/734,693. |
| USPTO; Final Office Action dated Feb. 11, 2014 in U.S. Appl. No. 13/715,423. |
| USPTO; Office Action dated Feb. 12, 2014 in U.S. Appl. No. 13/468,931. |
| Golson, “Major League Baseball Rolling out Thousands of iBeacons for Opening Day,” Jan. 30, 2014, pp. 2-3, retrieved from http://www.macrumors.com/2014/01/30/mlb-ibeacon-rollout/ on Feb. 12, 2014. |
| D Arthur, S Vassilvitskii , “k-means++: The advantages of careful seeding”, Proceedings of the eighteenth annual ACM-SIAM symposium on Discrete algorithms, pp. 1027-1035, 2007, dl.acm.org. |
| AK Jain, “Data clustering: 50 years beyond K-means”, Pattern Recognition Letters, 2010, pp. 1-33, Elsevier. |
| K-means++ Wikipedia Page, pp. 1-4, page last modified on Nov. 18, 2013, http://en.wikipedia.org/wiki/K-means++retrieved from the web Nov. 21, 2013. |
| USPTO; Advisory Action dated Apr. 30, 2014 in U.S. Appl. No. 13/715,423. |
| USPTO; Final Office Action dated May 5, 2014 in U.S. Appl. No. 13/411,281. |
| USPTO; Advisory Action dated Jun. 2, 2017 in U.S. Appl. No. 13/941,306. |
| USPTO; Notice of Allowance dated Jun. 9, 2017 in U.S. Appl. No. 14/464,439. |
| USPTO; Notice of Allowance dated Jun. 13, 2017 in U.S. Appl. No. 13/889,305. |
| USPTO; Notice of Allowance dated Jun. 13, 2017 in U.S. Appl. No. 14/464,474. |
| USPTO; Office Action dated Jun. 15, 2017 in U.S. Appl. No. 13/715,770. |
| Notice of Acceptance dated Jun. 21, 2017 in Australian Application No. 2016201509. |
| USPTO; Office Action dated Jun. 21, 2017 in U.S. Appl. No. 13/466,412. |
| USPTO; Notice of Allowance dated Jun. 29, 2017 in U.S. Appl. No. 13/889,299. |
| USPTO; Advisory Action dated Jul. 14, 2017 in U.S. Appl. No. 13/794,301. |
| USPTO; Notice of Allowance dated Jul. 25, 2017 in U.S. Appl. No. 13/411,281. |
| USPTO; Final Office Action dated Apr. 11, 2011 in U.S. Appl. No. 12/857,389. |
| USPTO; Final Office Action dated Apr. 5, 2011 in U.S. Appl. No. 12/857,424. |
| Todorova, Aleksandra, “The Best Rewards Programs,” www.smartmoney.com, Sep. 2005, pp. 1-2. |
| Todorova, Aleksandra, “Capital One Tests a New Type of Debit Card,” www.smartmoney.com, Jun. 2007, pp. 1-2. |
| Nickel, “Citi Thank You Redemptions: No Thanks,” www.fivecentnickel.com, Sep. 2005. |
| American Express Website, Frequenty Asked Questions regarding American Express GiftCards, www.americanexpress.com/gift/faq from Feb. 25, 2005, 2 pages. |
| USPTO; Office Action dated Nov. 26, 2010 in U.S. Appl. No. 12/857,424. |
| USPTO; Office Action dated Nov. 26, 2010 in U.S. Appl. No. 12/857,389. |
| USPTO; Office Action dated Apr. 30, 2010 in U.S. Appl. No. 11/779,734. |
| USPTO; Advisory Action dated Jan. 6, 2011 in U.S. Appl. No. 11/779,734. |
| USPTO; Final Office Action dated Oct. 15, 2010 in U.S. Appl. No. 11/779,734. |
| USPTO; Advisory Action dated Jul. 11, 2011 in U.S. Appl. No. 12/857,389. |
| USPTO; Advisory Action dated Jul. 11, 2011 in U.S. Appl. No. 12/857,424. |
| PCT; International Search Report and Written Opinion dated Nov. 17, 2011 in Application No. PCT/US2011/047012. |
| USPTO; Office Action dated Nov. 10, 2011 in U.S. Appl. No. 13/153,890. |
| USPTO; Final Office Action dated Apr. 5, 2012 in U.S. Appl. No. 13/153,890. |
| PCT; International Search Report and Written Opinion dated May 7, 2012 in Application No. PCT/US2012/021648. |
| PCT; International Search Report and Written Opinion dated Jun. 19, 2012 in Application No. PCT/US2012/027810. |
| PCT; International Search Report and Written Opinion dated Jul. 6, 2012 in Application No. PCT/US2012/027664. |
| USPTO; Office Action dated Aug. 3, 2012 in U.S. Appl. No. 13/466,412. |
| USPTO; Office Action dated Aug. 17, 2012 in U.S. Appl. No. 13/466,445. |
| USPTO; Office Action dated Aug. 30, 2012 in U.S. Appl. No. 13/188,693. |
| USPTO; Office Action dated Aug. 30, 2012 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Sep. 6, 2012 in U.S. Appl. No. 13/467,503. |
| USPTO; Office Action dated Sep. 14, 2012 in U.S. Appl. No. 13/476,910. |
| USPTO; Office Action dated Sep. 17, 2012 in U.S. Appl. No. 13/021,237. |
| USPTO; Office Action dated Oct. 9, 2012 in U.S. Appl. No. 13/468,931. |
| USPTO; Office Action dated Oct. 9, 2012 in U.S. Appl. No. 13/477,806. |
| USPTO; Office Action dated Oct. 12, 2012 in U.S. Appl. No. 13/439,768. |
| USPTO; Final Office Action dated Oct. 12, 2012 in U.S. Appl. No. 13/466,412. |
| USPTO; Office Action dated Oct. 15, 2012 in U.S. Appl. No. 13/594,528. |
| USPTO; Office Action dated Oct. 18, 2012 in U.S. Appl. No. 13/593,204. |
| USPTO; Office Action dated Oct. 19, 2012 in U.S. Appl. No. 13/411,281. |
| Dan Oshinsky, “Jet Blue's $1 Million Twitter Hashtag,” Aug. 18, 2010, 4 pages, retrieved from: http://danoshinsky.com/2010/08/18/a-social-media-case-study-jetblue-vs-sun-country/. |
| USPTO; Office Action dated Nov. 15, 2012 in U.S. Appl. No. 13/443,100. |
| USPTO; Advisory Action dated Nov. 23, 2012 in U.S. Appl. No. 13/466,412. |
| International Preliminary Report on Patentability dated Dec. 7, 2012 in Application No. PCT/US2011/047012. |
| MG Seigler, “Want Everyone to See your Credit Card Transactions? of Course you do. Meet Blippy.”, techcrunch.com, Dec. 11, 2009, 3 pages. |
| Tsotsis, Alexia, “The End of Blippy as We Know it.” techcrunch.com, May 19, 2011, 3 pages. |
| USPTO; Office Action dated Jan. 4, 2013 in U.S. Appl. No. 13/593,204. |
| USPTO; Office Action dated Jan. 7, 2013 in U.S. Appl. No. 13/467,503. |
| USPTO; Office Action dated Jan. 7, 2013 in U.S. Appl. No. 13/466,445. |
| USPTO; Advisory Action dated Mar. 15, 2013 in U.S. Appl. No. 13/593,204. |
| USPTO; Advisory Action dated Mar. 18, 2013 in U.S. Appl. No. 13/467,503. |
| USPTO; Advisory Action dated Mar. 19, 2013 in U.S. Appl. No. 13/021,237. |
| USPTO; Advisory Action dated Mar. 19, 2013 in U.S. Appl. No. 13/468,931. |
| International Search Report and Written Opinion dated Mar. 22, 2013 in Application No. PCT/2013/028209. |
| USPTO; Advisory Action dated Mar. 28, 2013 in U.S. Appl. No. 13/411,281. |
| USPTO; Office Action dated Apr. 11, 2013 in U.S. Appl. No. 12/857,424. |
| USPTO; Office Action dated Apr. 12, 2013 in U.S. Appl. No. 13/467,910. |
| USPTO; Office Action dated Oct. 23, 2014 in U.S. Appl. No. 13/715,770. |
| USPTO; Advisory Action dated Oct. 24, 2014 in U.S. Appl. No. 13/153,890. |
| USPTO; Office Action dated Oct. 29, 2014 in U.S. Appl. No. 13/926,884. |
| USPTO; Office Action dated Oct. 29, 2014 in U.S. Appl. No. 13/926,895. |
| USPTO; Office Action dated Nov. 7, 2014 in U.S. Appl. No. 13/715,792. |
| USPTO; Office Action dated Nov. 7, 2014 in U.S. Appl. No. 13/715,423. |
| USPTO; Office Action dated Dec. 29, 2014 in U.S. Appl. No. 13/188,693. |
| USPTO; Office Action dated Jan. 9, 2015 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Jan. 16, 2015 in U.S. Appl. No. 13/889,299. |
| USPTO; Advisory Action dated Sep. 5, 2014 in U.S. Appl. No. 13/889,305. |
| USPTO; Office Action dated Sep. 17, 2014 in U.S. Appl. No. 13/794,226. |
| USPTO; Office Action dated Sep. 26, 2014 in U.S. Appl. No. 13/477,806. |
| USPTO; Office Action dated Oct. 17, 2014 in U.S. Appl. No. 14/065,883. |
| USPTO; Office Action dated Oct. 17, 2014 in U.S. Appl. No. 11/779,734. |
| USPTO; Office Action dated Oct. 20, 2014 in U.S. Appl. No. 13/941,306. |
| USPTO; Office Action dated Oct. 3, 2014 in U.S. Appl. No. 12/857,424. |
| USPTO; Office Action dated Oct. 8, 2014 in U.S. Appl. No. 13/734,693. |
| USPTO; Office Action dated Oct. 9, 2014 in U.S. Appl. No. 13/926,789. |
| USPTO; Final Office Action dated Jan. 30, 2015 in U.S. Appl. No. 13/794,301. |
| USPTO; Final Office Action dated Feb. 11, 2015 in U.S. Appl. No. 14/065,883. |
| USPTO; Final Office Action dated Feb. 13, 2015 in U.S. Appl. No. 13/794,334. |
| Search Report and Written Opinion dated Feb. 16, 2015 in Singapore Application No. 11201400788P. |
| USPTO; Final Office Action dated Feb. 26, 2015 in U.S. Appl. No. 13/941,306. |
| USPTO; Office Action dated Feb. 27, 2015 in U.S. Appl. No. 13/443,100. |
| USPTO; Office Action dated Mar. 2, 2015 in U.S. Appl. No. 13/686,608. |
| USPTO; Final Office Action dated Mar. 13, 2015 in U.S. Appl. No. 13/794,374. |
| USPTO; Final Office Action dated Mar. 23, 2015 in U.S. Appl. No. 13/926,789. |
| Examination Report dated Mar. 24, 2015 in Australian Application No. 2012316453. |
| USPTO; Final Office Action dated Mar. 25, 2015 in U.S. Appl. No. 13/477,806. |
| USPTO; Final Office Action dated Mar. 25, 2015 in U.S. Appl. No. 13/794,226. |
| USPTO; Office Action dated Mar. 27, 2015 in U.S. Appl. No. 13/466,445. |
| USPTO; Final Office Action dated Apr. 3, 2015 in U.S. Appl. No. 13/926,884. |
| USPTO; Final Office Action dated Apr. 3, 2015 in U.S. Appl. No. 13/715,770. |
| USPTO; Final Office Action dated Apr. 7, 2015 in U.S. Appl. No. 13/926,895. |
| USPTO; Advisory Action dated Apr. 8, 2015 in U.S. Appl. No. 13/794,301. |
| USPTO; Office Action dated Apr. 8, 2015 in U.S. Appl. No. 13/021,237. |
| USPTO; Final Office Action dated Apr. 8, 2015 in U.S. Appl. No. 13/794,145. |
| USPTO; Final Office Action dated Apr. 13, 2015 in U.S. Appl. No. 13/734,693. |
| USPTO; Advisory Action dated Apr. 17, 2015 in U.S. Appl. No. 13/889,307. |
| USPTO; Final Office Action dated Apr. 17, 2015 in U.S. Appl. No. 13/715,792. |
| USPTO; Advisory Action dated Apr. 23, 2015 in U.S. Appl. No. 13/794,334. |
| USPTO; Advisory Action dated Apr. 23, 2015 in U.S. Appl. No. 14/065,883. |
| USPTO; Final Office Action dated Apr. 30, 2015 in U.S. Appl. No. 12/857,424. |
| Notice of Acceptance dated May 8, 2015 in New Zealand Application No. 623019. |
| USPTO; Advisory Action dated May 8, 2015 in U.S. Appl. No. 13/941,306. |
| USPTO; Final Office Action dated May 13, 2015 in U.S. Appl. No. 11/779,734. |
| USPTO; Office Action dated May 19, 2015 in U.S. Appl. No. 13/476,910. |
| USPTO; Office Action dated May 28, 2015 in U.S. Appl. No. 13/467,503. |
| USPTO; Advisory Action dated Jun. 3, 2015 in U.S. Appl. No. 13/794,226. |
| USPTO; Advisory Action dated Jun. 3, 2015 in U.S. Appl. No. 13/794,374. |
| USPTO; Office Action dated Jan. 15, 2016 in U.S. Appl. No. 13/889,299. |
| USPTO; Advisory Action dated Jan. 15, 2016 in U.S. Appl. No. 13/476,910. |
| USPTO; Office Action dated Jan. 20, 2016 in U.S. Appl. No. 13/889,307. |
| Pashtan, et al., “Personal Service Areas for Mobile Web Applications,” IEEE Internet Computing, 2004, ieeexplore.ieee.org, 7 pages. |
| Pandey, et al., “Exploiting User Profiles to Support Differentiated Services in Next-Generation Wireless Networks,” Network, IEEE, 2004, ieeexplore.ieee.org, 23 pages. |
| Liapis, et al., Implementing a Low-Cost, Personalized and Location Based Service for Delivering Advertisements to Mobile Users, Athens Information Technology, Oct. 2008, ieeexplore.ieee.org, 49 pages. |
| Park, et al., “Location-Based Recommendation System using Bayesian User's Preference Model in Mobile Devices,” Ubiquitous Intelligence and Computing, 2007, Springer-Verlag Berlin Heidelberg, 10 pages. |
| Office Action dated Oct. 26, 2015 in Canadian Application No. 2,863,576. |
| Notice of Acceptance dated Nov. 30, 2015 in Australian Application No. 2012316453. |
| Office Action dated Dec. 10, 2015 in Canadian Application No. 2,849,271. |
| USPTO; Office Action dated Feb. 1, 2016 in U.S. Appl. No. 13/443,100. |
| USPTO; Final Office Action dated Feb. 2, 2016 in U.S. Appl. No. 13/926,789. |
| USPTO; Final Office Action dated Feb. 2, 2016 in U.S. Appl. No. 13/941,306. |
| USPTO; Final Office Action dated Feb. 9, 2016 in U.S. Appl. No. 13/794,374. |
| USPTO; Final Office Action dated Feb. 9, 2016 in U.S. Appl. No. 13/794,272. |
| USPTO; Final Office Action dated Feb. 11, 2016 in U.S. Appl. No. 13/794,334. |
| USPTO; Final Office Action dated Feb. 11, 2016 in U.S. Appl. No. 13/926,884. |
| USPTO; Final Office Action dated Feb. 12, 2016 in U.S. Appl. No. 13/926,895. |
| USPTO; Office Action dated Feb. 12, 2016 in U.S. Appl. No. 13/593,204. |
| USPTO; Office Action dated Feb. 19, 2016 in U.S. Appl. No. 13/468,931. |
| Office Action dated Feb. 29, 2016 in Canadian Application No. 2,874,582. |
| USPTO; Office Action dated Feb. 29, 2016 in U.S. Appl. No. 13/686,608. |
| USPTO; Office Action dated Mar. 4, 2016 in U.S. Appl. No. 13/466,412. |
| USPTO; Office Action dated Mar. 4, 2016 in U.S. Appl. No. 13/794,226. |
| USPTO; Office Action dated Mar. 7, 2016 in U.S. Appl. No. 12/857,389. |
| USPTO; Office Action dated Mar. 17, 2016 in U.S. Appl. No. 13/889,305. |
| USPTO; Advisory Action dated Mar. 18, 2016 in U.S. Appl. No. 13/439,768. |
| USPTO; Advisory Action dated Mar. 18, 2016 in U.S. Appl. No. 13/411,281. |
| USPTO; Advisory Action dated Mar. 25, 2016 in U.S. Appl. No. 13/794,301. |
| USPTO; Advisory Action dated Mar. 28, 2016 in U.S. Appl. No. 14/065,883. |
| White, “Deals as Debit Rewards? Bank of America Brings Back Debit Card Rewards With a Twist,” Jan. 25, 2012, 2 pages, retrieved from http://moneyland.time.com/2012/01/25/deals-as-debit-rewards-bank-of-america-brings-back-debit-card-rewards-with-a-twist/. |
| Owen, et al., “Improving the Value and Performance of Online Offers,” A First Data White Paper, First Data Corporation, 2012, 10 pages. |
| Noyes, “Card-Linked Offers Update,” Transaction World Magazine, Jul. 2012, 2 pages. |
| Examination Report dated Feb. 26, 2016 in Australian Application No. 2015201925. |
| USPTO; Office Action dated Mar. 31, 2016 in U.S. Appl. No. 13/889,288. |
| USPTO; Final Office Action dated Apr. 14, 2016 in U.S. Appl. No. 13/715,770. |
| USPTO; Office Action dated Apr. 15, 2016 in U.S. Appl. No. 13/188,693. |
| USPTO; Advisory Action dated Apr. 15, 2016 in U.S. Appl. No. 13/926,789. |
| USPTO; Notice of Allowance dated Apr. 18, 2016 in U.S. Appl. No. 13/734,693. |
| USPTO; Advisory Action dated Apr. 21, 2016 in U.S. Appl. No. 13/794,272. |
| USPTO; Advisory Action dated Apr. 22, 2016 in U.S. Appl. No. 13/794,374. |
| Office Action dated Apr. 25, 2016 in Canadian Application No. 2,888,085. |
| USPTO; Advisory Action dated May 2, 2016 in U.S. Appl. No. 13/926,884. |
| USPTO; Advisory Action dated May 2, 2016 in U.S. Appl. No. 13/794,334. |
| USPTO; Office Action dated May 16, 2016 in U.S. Appl. No. 13/153,890. |
| USPTO; Office Action dated May 19, 2016 in U.S. Appl. No. 13/926,895. |
| Ghose, et al., “Opinion Mining using Econometrics: A case study on Reputation Systems”, Department of Information, Operations, and Management Sciences, Annual Meeting, 2007. |
| Pang, et al., “Opinion mining and sentiment analysis”, Foundations and trends in information retrieval, vol. 2, No. 1-2 (2008) 1-135. |
| Pavlovic, “Dynamics, robustness and fragility of trust”, Formal Aspects in Secruity and Trust, 2009—Springer. |
| Pocket-lint, Apple's iBeacons explained: What it is and why it matters, retrieved from internet on Feb. 21, 2017, http://web.archive.org/web/20130925141212/http://www.pocket-lint.com/news/123730-apple-sibeacons-explained-what-it-is-and-why-it-matters> published on Sep. 25, 2013 as per Wayback Machine, 10 pages. |
| Office Action dated Feb. 1, 2017 in U.S. Appl. No. 15/334,490. |
| Final Office Action dated Mar. 22, 2017 in U.S. Appl. No. 15/334,490. |
| Office Action dated Jan. 11, 2017 in Canadian Application No. 2,849,271. |
| Office Action dated Feb. 15, 2017 in Canadian Application No. 2,874,582. |
| USPTO; Notice of Allowance dated Mar. 10, 2017 in U.S. Appl. No. 13/467,503. |
| USPTO; Advisory Action dated Mar. 10, 2017 in U.S. Appl. No. 13/466,445. |
| USPTO; Advisory Action dated Mar. 13, 2017 in U.S. Appl. No. 13/466,412. |
| Aloni, U.S. Appl. No. 15/495,428, filed Apr. 24, 2017 and entitled Offers Selected During Authorization. |
| USPTO; Notice of Allowance dated Mar. 15, 2017 in U.S. Appl. No. 13/476,910. |
| USPTO; Advisory Action dated Mar. 23, 2017 in U.S. Appl. No. 13/443,100. |
| Examination Report dated Mar. 23, 2017 in Australian Application No. 2016201509. |
| USPTO; Notice of Allowance dated Mar. 24, 2017 in U.S. Appl. No. 13/794,334. |
| USPTO; Final Office Action dated Mar. 27, 2017 in U.S. Appl. No. 13/794,374. |
| Notice of Allowance dated Mar. 29, 2017 in Canadian Application No. 2,888,085. |
| USPTO; Advisory Action dated Mar. 29, 2017 in U.S. Appl. No. 13/715,770. |
| USPTO; Office Action dated Apr. 7, 2017 in U.S. Appl. No. 13/889,272. |
| USPTO; Office Action dated Apr. 10, 2017 in U.S. Appl. No. 13/443,100. |
| USPTO; Office Action dated Apr. 12, 2017 in U.S. Appl. No. 13/794,272. |
| USPTO; Office Action dated Apr. 13, 2017 in U.S. Appl. No. 13/466,412. |
| USPTO; Notice of Allowance dated Apr. 17, 2017 in U.S. Appl. No. 13/466,445. |
| USPTO; Notice of Allowance dated Apr. 20, 2017 in U.S. Appl. No. 13/889,288. |
| USPTO; Final Office Action dated Apr. 20, 2017 in U.S. Appl. No. 14/065,883. |
| USPTO; Final Office Action dated Apr. 20, 2017 in U.S. Appl. No. 13/941,306. |
| USPTO; Notice of Allowance dated Apr. 24, 2017 in U.S. Appl. No. 13/926,895. |
| USPTO; Final Office Action dated May 17, 2017 in U.S. Appl. No. 14/464,474. |
| Morris, U.S. Appl. No. 15/456,777, filed Mar. 13, 2017 and entitled Purchase Instructions Complying With Reservation Instructions. |
| USPTO; Final Office Action dated Apr. 28, 2017 in U.S. Appl. No. 13/153,890. |
| USPTO; Final Office Action dated Apr. 28, 2017 in U.S. Appl. No. 13/889,305. |
| USPTO; Final Office Action dated May 4, 2017 in U.S. Appl. No. 13/794,301. |
| USPTO; Final Office Action dated May 17, 2017 in U.S. Appl. No. 13/411,281. |
| USPTO; Advisory Action dated May 17, 2017 U.S. Appl. No. 13/794,374. |
| USPTO; Final Office Action dated May 17, 2017 in U.S. Appl. No. 14/464,439. |
| USPTO; Office Action dated Oct. 11, 2016 in U.S. Appl. No. 13/794,226. |
| USPTO; Office Action dated Oct. 11, 2016 in U.S. Appl. No. 13/794,301. |
| USPTO; Advisory Action dated Oct. 20, 2016 in U.S. Appl. No. 13/889,307. |
| USPTO; Advisory Action dated Oct. 27, 2016 in U.S. Appl. No. 12/857,424. |
| Supplementary Examination Report dated Oct. 17, 2016 in New Zealand Application No. 11201400788P. |
| USPTO; Advisory Action dated Oct. 31, 2016 in U.S. Appl. No. 13/889,288. |
| USPTO; Advisory Action dated Nov. 1, 2016 in U.S. Appl. No. 13/153,890. |
| USPTO; Final Office Action dated Nov. 1, 2016 in U.S. Appl. No. 13/926,895. |
| Notice of Eligibility for Grant dated Nov. 1, 2016 in Singapore Application No. 11201400788P. |
| USPTO; Notice of Allowance dated Nov. 2, 2016 in U.S. Appl. No. 13/477,806. |
| USPTO; Advisory Action dated Nov. 3, 2016 in U.S. Appl. No. 14/065,883. |
| USPTO; Advisory Action dated Nov. 4, 2016 in U.S. Appl. No. 13/443,100. |
| USPTO; Final Office Action dated Nov. 4, 2016 in U.S. Appl. No. 13/794,334. |
| USPTO; Office Action dated Nov. 10, 2016 in U.S. Appl. No. 13/476,910. |
| USPTO; Final Office Action dated Nov. 10, 2016 in U.S. Appl. No. 14/284,817. |
| USPTO; Advisory Action dated Nov. 15, 2016 in U.S. Appl. No. 13/889,299. |
| USPTO; Advisory Action dated Nov. 16, 2016 in U.S. Appl. No. 13/941,306. |
| USPTO; Notice of Allowance dated Nov. 17, 2016 in U.S. Appl. No. 12/857,424. |
| USPTO; Final Office Action dated Nov. 17, 2016 in U.S. Appl. No. 13/188,693. |
| USPTO; Notice of Allowance dated Nov. 18, 2016 in U.S. Appl. No. 13/468,931. |
| USPTO; Office Action dated Nov. 18, 2016 in U.S. Appl. No. 13/443,100. |
| Examination Report dated Nov. 22, 016 in Australian Application No. 2015201925. |
| USPTO; Office Action dated Nov. 28, 2016 in U.S. Appl. No. 14/065,883. |
| USPTO; Office Action dated Dec. 2, 2016 in U.S. Appl. No. 13/153,890. |
| USPTO; Office Action dated Dec. 14, 2016 in U.S. Appl. No. 13/941,306. |
| USPTO; Advisory Action dated Dec. 14, 2016 in U.S. Appl. No. 13/794,334. |
| USPTO; Final Office Action dated Dec. 15, 2016 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Dec. 15, 2016 in U.S. Appl. No. 13/411,281. |
| USPTO; Office Action dated Dec. 20, 2016 in U.S. Appl. No. 13/889,305. |
| USPTO; Office Action dated Jan. 4, 2017 in U.S. Appl. No. 13/794,334. |
| USPTO; Office Action dated Jan. 13, 2017 in U.S. Appl. No. 13/794,374. |
| USPTO; Advisory Action dated Dec. 8, 2016 in U.S. Appl. No. 13/926,895. |
| Examination Report dated Jan. 11, 2017 in Australian Application No. 2016201509. |
| USPTO; Final Office Action dated Jan. 19, 2017 in U.S. Appl. No. 13/466,445. |
| USPTO; Final Office Action dated Jan. 20, 2017 in U.S. Appl. No. 13/467,503. |
| Examination Report dated Jan. 23, 2017 in Australian Application No. 2015201925. |
| USPTO; Office Action dated Jan. 23, 2017 in U.S. Appl. No. 14/464,439. |
| USPTO; Advisory Action dated Jan. 25, 2017 in U.S. Appl. No. 14/284,817. |
| USPTO; Office Action dated Jan. 30, 2017 in U.S. Appl. No. 14/464,474. |
| USPTO; Notice of Allowance dated Feb. 2, 2017 in U.S. Appl. No. 12/857,389. |
| USPTO; Advisory Action dated Feb. 7, 2017 in U.S. Appl. No. 13/188,693. |
| USPTO; Final Office Action dated Feb. 8, 2017 in U.S. Appl. No. 13/715,770. |
| USPTO; Final Office Action dated Feb. 9, 2017 in U.S. Appl. No. 13/443,100. |
| USPTO; Final Office Action dated Feb. 14, 2017 in U.S. Appl. No. 13/466,412. |
| USPTO; Notice of Allowance dated Feb. 14, 2017 in U.S. Appl. No. 13/794,226. |
| USPTO; Notice of Allowance dated Feb. 15, 2017 in U.S. Appl. No. 13/794,145. |
| USPTO; Notice of Allowance dated Feb. 16, 2017 in U.S. Appl. No. 13/889,307. |
| Examination Report dated Feb. 24, 2017 in Australian Application No. 2015201925. |
| USPTO; Advisory Action dated Feb. 27, 2017 in U.S. Appl. No. 13/468,880. |
| USPTO; Final Office Action dated Feb. 27, 2017 in U.S. Appl. No. 13/926,895. |
| Resnick, et al., “Recommender Systems”, Mar. 1997, Commuincations of the ACM, vol. 40,No. 3, pp. 56-58. |
| Ricci, et al.; “Recommendation and Personalization in eCommerce”, Proceedings of the AH'2002 Workshop on Recommendation and Personalization in eCommerce, Malaga, Spain, May 28, 2002, pp. 1-160. |
| USPTO; Office Action dated Jun. 3, 2016 in U.S. Appl. No. 14/065,883. |
| USPTO; Office Action dated Jun. 3, 2016 in U.S. Appl. No. 12/857,424. |
| USPTO; Notice of Allowance dated Jun. 3, 2016 in U.S. Appl. No. 13/593,204. |
| USPTO; Final Office Action dated Jun. 8, 2016 in U.S. Appl. No. 12/857,389. |
| USPTO; Office Action dated Jun. 9, 2016 in U.S. Appl. No. 13/926,895. |
| USPTO; Final Office Action dated Jun. 10, 2016 in U.S. Appl. No. 13/466,412. |
| USPTO; Final Office Action dated Jun. 13, 2016 in U.S. Appl. No. 13/468,931. |
| USPTO; Final Office Action dated Jun. 15, 2016 in U.S. Appl. No. 13/686,608. |
| USPTO; Office Action dated Jun. 17, 2016 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Jun. 17, 2016 in U.S. Appl. No. 13/941,306. |
| USPTO; Final Office Action dated Jun. 17, 2016 in U.S. Appl. No. 13/794,145. |
| USPTO; Advisory Action dated Jun. 24, 2016 in U.S. Appl. No. 13/715,770. |
| USPTO; Final Office Action dated Jul. 1, 2016 in U.S. Appl. No. 13/794,226. |
| USPTO; Final Office Action dated Jul. 5, 2016 in U.S. Appl. No. 13/889,305. |
| USPTO; Advisory Action dated Jul. 6, 2016 in U.S. Appl. No. 13/468,931. |
| USPTO; Office Action dated Jul. 7, 2016 in U.S. Appl. No. 14/284,817. |
| USPTO; Notice of Allowance dated Jul. 13, 2016 in U.S. Appl. No. 11/779,734. |
| USPTO; Final Office Action dated Jul. 28, 2016 in U.S. Appl. No. 13/889,272. |
| USPTO; Final Office Action dated Aug. 12, 2016 in U.S. Appl. No. 13/889,299. |
| “What is a token in programming?” Quora, pp. 1-3, retrieved from https://www.quora.com/What-is-a-token-in-programming on May 31, 2016. |
| USPTO; Notice of Allowance dated May 25, 2016 in U.S. Appl. No. 13/439,768. |
| USPTO; Office Action dated May 26, 2016 in U.S. Appl. No. 13/477,806. |
| IP Australia; Examination Report dated Aug. 3, 2016 in Australian Application No. 2015201925. |
| USPTO; Advisory Action dated Aug. 17, 2016 in U.S. Appl. No. 12/857,389. |
| CIPO; Notice of Allowance dated Aug. 18, 2016 in Canadian Application No. 2,863,576. |
| SPTO; Advisory Action dated Aug. 18, 2016 in U.S. Appl. No. 13/466,412. |
| USPTO; Notice of Allowance dated Aug. 24, 2016 in U.S. Appl. No. 13/021,237. |
| USPTO; Advisory Action dated Aug. 24, 2016 in U.S. Appl. No. 13/686,608. |
| USPTO; Office Action dated Aug. 24, 2016 in U.S. Appl. No. 13/794,334. |
| USPTO; Final Office Action dated Aug. 25, 2016 in U.S. Appl. No. 13/466,445. |
| USPTO; Advisory Action dated Aug. 25, 2016 in U.S. Appl. No. 13/794,145. |
| USPTO; Final Office Action dated Aug. 26, 2016 in U.S. Appl. No. 13/443,100. |
| USPTO; Final Office Action dated Aug. 30, 2016 in U.S. Appl. No. 13/889,307. |
| USPTO; Office Action dated Sep. 2, 2016 in U.S. Appl. No. 13/467,503. |
| USPTO; Final Office Action dated Sep. 2, 2016 in U.S. Appl. No. 12/857,424. |
| USPTO; Final Office Action dated Sep. 7, 2016 in U.S. Appl. No. 13/153,890. |
| USPTO; Notice of Allowance dated Sep. 9, 2016 in U.S. Appl. No. 13/926,789. |
| USPTO; Advisory Action dated Sep. 12, 2016 in U.S. Appl. No. 13/889,305. |
| USPTO; Final Office Action dated Sep. 14, 2016 in U.S. Appl. No. 13/477,806. |
| USPTO; Advisory Action dated Sep. 21, 2016 in U.S. Appl. No. 13/889,272. |
| USPTO; Final Office Action dated Sep. 22, 2016 in U.S. Appl. No. 13/889,288. |
| USPTO; Advisory Action dated Sep. 22, 2016 in U.S. Appl. No. 13/794,226. |
| USPTO; Final Office Action dated Sep. 23, 2016 in U.S. Appl. No. 14/065,883. |
| USPTO; Office Action dated Sep. 29, 2016 in U.S. Appl. No. 12/857,389. |
| USPTO; Office Action dated Sep. 29, 2016 in U.S. Appl. No. 13/466,412. |
| USPTO; Office Action dated Oct. 7, 2016 in U.S. Appl. No. 13/715,770. |
| USPTO; Notice of Allowance dated Oct. 11, 2016 in U.S. Appl. No. 13/926,884. |
| USPTO; Office Action dated Oct. 11, 2016 in U.S. Appl. No. 13/794,145. |
| USPTO; Advisory Action dated Oct. 3, 2017 in U.S. Appl. No. 13/794,272. |
| USPTO; Notice of Allowance dated Dec. 13, 2017 in U.S. Appl. No. 13/941,306. |
| Lispto; Non-Final Office Action dated Oct. 6, 2017 in U.S. Appl. No. 13/188,693. |
| USPTO; Non-Final Office Action dated Oct. 6, 2017 in U.S. Appl. No. 13/468,880. |
| USPTO; Final Office Action dated Oct. 25, 2017 in U.S. Appl. No. 13/889,272. |
| USPTO; Notice of Allowance dated Oct. 30, 2017 in U.S. Appl. No. 13/794,374. |
| USPTO; Advisory Action dated Nov. 9, 2017 in U.S. Appl. No. 13/466,412. |
| USPTO; Non-Final Office Action dated Nov. 14, 2017 in U.S. Appl. No. 14/284,817. |
| USPTO; Advisory Action dated Nov. 28, 2017 in U.S. Appl. No. 13/889,272. |
| USPTO; Final Office Action dated Dec. 11, 2017 in U.S. Appl. No. 13/715,423. |
| USPTO; Final Office Action dated Aug. 11, 2017 in U.S. Appl. No. 13/443,100. |
| USPTO; Final Office Action dated Aug. 18, 2017 in U.S. Appl. No. 13/794,272. |
| USPTO; Non-Final Office Action dated Aug. 30, 2017 in U.S. Appl. No. 13/941,306. |
| USPTO; Final Office Action dated Sep. 20, 2017 in U.S. Appl. No. 13/466,412. |
| USPTO; Non-Final Office Action dated Dec. 22, 2017 in U.S. Appl. No. 15/139,176. |
| USPTO; Non-Final Office Action dated Jan. 11, 2018 in U.S. Appl. No. 15/195,781. |
| USPTO; Final Office Action dated Jan. 18, 2018 in U.S. Appl. No. 13/715,770. |
| Australian Examination Report dated Jan. 19, 2018 in Australian Application No. 2017201307. |
| USPTO; Non-Final Office Action dated Jan. 23, 2018 in U.S. Appl. No. 15/166,086. |
| USPTO; Non-Final Office Action dated Feb. 2, 2018 in U.S. Appl. No. 14/928,680. |
| USPTO; Advisory Action dated Feb. 28, 2018 in U.S. Appl. No. 13/715,770. |
| USPTO; Non-Final Action dated Mar. 9, 2018 in U.S. Appl. No. 13/794,301. |
| USPTO; Advisory Action dated Mar. 22, 2018 in U.S. Appl. No. 13/715,423. |
| USPTO; Non-Final Office Action dated Apr. 5, 2018 in U.S. Appl. No. 15/216,264. |
| USPTO; Final Office Action dated Apr. 6, 2018 in U.S. Appl. No. 13/468,880. |
| USPTO; Final Office Action dated Apr. 25, 2018 in U.S. Appl. No. 15/195,781. |
| Ying Cai et al., Design, Analysis, and Implentation of a Large-scale Real-time Location-based Information Sharing System, pp. 106-117, Proceedings of the 6th International Conference on . . . , 2008, dl.acm.org. |
| Moon-Hee Parket et al., Location-Based Recommendation System Using Bayesian User's Preference Model in Mobile Devices, International Conference on Ubiquitous, pp. 1130-1139, 2007, Spring-Verlag Berlin Heidelberg. |
| Rashid, O. et. Al., “Providing Location based information/ advertising for existing mobile phone users”, Personal and Ubiquitous Computing, 2008, pp. 3-10, Springer. |
| Singhal, M., et al., “Implementation of Location based servcies in Android Using GPS and Web Servies”, IJCSI International Journal of Computer Science Issues, vol. 9, Issue 1, No. 2, Jan. 2012, pp. 237-242, pdfs.semanticscholar.org. |
| “Standard Score”, Wikipedia.org entry, retrieved on Nov. 30, 2017 from http://en.wikipedia.org/wiki/Standard_score, pp. 1-4. |
| Mahmoud, Q., “Provisioning Context-Aware Advertisements to Wireless Mobile Users”, pp. 669-672, Multimedia and Expo, 2006 IEEE International, 2006. |
| Dhar, S. et al., “Challenges and Business Models for Mobile Location-Based Servies and Advertising”, Communications of the ACM, May 2011, vol. 54, No. 5, pp. 121-129. |
| Lynn, Michael et al., “Gratitude and Fratuity: A Meta-Analysis of Research on the Service-tipping Relationship”, Cornel University of Hotel Administraiton, 2000, Journal of Socio-Economics 29, pp. 1-18. |
| Canadian Intellectual Property Office, Canadian Examination Search Report dated Jan. 31, 2018 in Application No. 2,849,271. |
| USPTO; Final Office Action dated May 9, 2018 in U.S. Appl. No. 15/139,176. |
| USPTO; Non-Finai Office action dated May 18, 2018 in U.S. Appl. No. 15/018,623. |
| USPTO; Final Office Action dated May 23, 2018 in U.S. Appl. No. 15/166,086. |
| Uspto; Non-Final Office action dated May 24, 2018 in U.S. Appl. No. 14/928,905. |
| Number | Date | Country | |
|---|---|---|---|
| 20170286996 A1 | Oct 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14464474 | Aug 2014 | US |
| Child | 15626598 | US | |
| Parent | 13245636 | Sep 2011 | US |
| Child | 14464474 | US |
