Patent Grant
10594870
The present invention is generally related to an in-statement rewards platform.
While consumer comparison shopping for products is known, an unbiased way of comparison shopping for competing services is unavailable. Often a consumer may only be aware of some of the information related to a service provider's services, options, terms, conditions, costs, and the like. Also, the consumer may not be aware of how the service options change based on their particular usage characteristics. Thus, there remains a need for a consumer comparison shopping method that obtains actual or predicted service usage data from the consumer and service provider information in order to present the consumer with relevant alternative service offering options.
In embodiments, methods and systems may comprise gathering transaction data from a user's financial account, analyzing the transaction data for a savings opportunity indication, matching a savings opportunity from a database of savings opportunities to the user based on the savings opportunity indication, and displaying the savings opportunity in association with a statement of a user's financial account. Further, a past response may be gathered to a savings opportunity indication and analyzing it, wherein the savings opportunity is based on both the analyzed transaction data and past response data. The statement may be an online statement, an online graphical user interface associated with the user's financial account, an online bill pay area, a dialog box associated with the user's financial account, an ATM receipt, a teller receipt, a mobile statement, a paper statement, and the like. The step of analyzing may comprise extracting at least one of a merchant name, a merchant category, a merchant location, a store number, a transaction amount, a transaction frequency, a zip code, a store category, a transaction description, and a total spending amount. The step of analyzing may comprise analyzing the transaction data for a savings opportunity indication relating to a merchant. The step of analyzing may comprise analyzing the transaction data for a savings opportunity indication relating to a market segment. The step of displaying the savings opportunity may comprise displaying the savings opportunity within a field of the statement where prior transaction data may be presented. The savings opportunity may be presented interweaved within the presented prior transaction data. The step of displaying the savings opportunity may comprise displaying the savings opportunity within a field of the statement not where prior transaction data may be presented. The user's financial account may be a credit card account, a bank account, a checking account, a savings account, a personal finance program account, a loan account, and the like. The step of analyzing may comprise anonymizing the transaction data. The savings opportunity may comprise an offer to perform a bill analysis. Further, generating and displaying a link may be provided in a graphical user interface to the user's financial account, to a transaction assessment user interface to compare the transaction to a plurality of alternative offers. The savings opportunity may be a coupon. The coupon may be a barcode presented on a mobile device. The coupon may be a printed coupon presented in a statement. The coupon may be an online redemption coupon code. The savings opportunity may be an automatic discount on a subsequent transaction. The savings opportunity may be a credit on a subsequent transaction. When the user makes the subsequent transaction, the user may receive the credit. The savings opportunity may be a pre-paid offer. The pre-paid offer may be charged immediately to the user's financial account. The pre-paid offer may be redeemed via an online coupon code, an in-store coupon, a mobile phone coupon, and the like. The savings opportunity may be a merchant loyalty program. The merchant loyalty program may be implemented through the use of a transaction card associated with the financial account. The merchant loyalty program may be implemented by providing the user with a printed coupon, a bar code coupon presented on a mobile device, a credit on a merchant loyalty card, and the like. Wherein analyzing the transaction data may comprise analyzing market segment information. The step of matching may be limited to savings opportunities near a user's identified location. The user's location may be identified manually by the user. The user's location may be identified automatically from a mobile device implementing the method.
In embodiments, methods and systems may comprise following a secure user login procedure, presenting a graphical user interface where a user's financial transaction data are presented, wherein the financial transaction data were obtained from a financial institution that maintains a financial account on behalf of the user, and presenting a savings opportunity, in proximity to the financial transaction data, wherein the savings opportunity relates to the financial transaction data. The sales offer may be presented in an interweaved fashion amongst more than one financial transaction of the financial transaction data. The financial account may be a credit card account, a bank account, a checking account, a savings account, a personal finance program account, a loan account, and the like. A past response may be gathered to a savings opportunity and analyzing it, wherein the current savings opportunity may be based on both the financial transaction data and past response data. The savings opportunity may relate to an aspect of the financial transaction data chosen from a merchant name, a merchant category, a merchant location, a store number, a transaction amount, a transaction frequency, a zip code, a store category, a transaction description, a total spending amount, and the like. Further, the financial transaction data may be anonymized. The step of presenting may be limited to savings opportunities near a user's identified location. The user's location may be identified manually by the user. The user's location may be identified automatically from a mobile device implementing the method. The savings opportunity may comprise an offer to perform a bill analysis. Further, generating and displaying a link may be provided in a graphical user interface to the user's financial account, to a transaction assessment user interface to compare the transaction to a plurality of alternative offers. The savings opportunity may be a coupon. The coupon may be a barcode presented on a mobile device. The coupon may be a printed coupon presented in a statement. The coupon may be an online redemption coupon code. The savings opportunity may be an automatic discount on a subsequent transaction. The savings opportunity may be a credit on a subsequent transaction. When the user makes the subsequent transaction, the user may receive the credit. The savings opportunity may be a pre-paid offer. The pre-paid offer may be charged immediately to the user's financial account. The pre-paid offer may be redeemed via an online coupon code, an in-store coupon, a mobile phone coupon, and the like. The savings opportunity may be a merchant loyalty program.
In embodiments, methods and systems may comprise presenting an opportunity to assess alternative offerings related to a financial transaction from a user's financial account, wherein the financial transaction is related to a presently selected offering, in response to the selection of the opportunity, gathering transaction data relating to the presented selected offering and analyzing the transaction data, wherein the step of analyzing involves normalizing the transaction data such that a comparison to other offers can be assessed, collecting offer data relating to an alternative offering and normalizing the offer data such that a comparison with the normalized transaction data can be assessed, comparing the normalized transaction data with the normalized offer data to assess if the alternative offering presents an improvement to the user in comparison to the presently selected offering, and presenting the alternative offering to the user if the alternative offering presents an improvement. Presenting may be done in a statement. The statement may be an online statement, an online graphical user interface associated with the user's financial account, an online bill pay area, a dialog box associated with the user's financial account, an ATM receipt, a teller receipt, a mobile statement, a paper statement, and the like. The financial transaction may be presented in a bill for payment in an online bill pay area. The improvement may be related to at least one of a cost, a coverage, a quality, and a rating. The user financial account is may be a credit card account, a bank account, a checking account, a savings account, a personal finance program account, a loan account, and the like. Analyzing the transaction data may involve extracting a merchant name, a merchant category, a merchant location, a transaction amount, a transaction frequency, a zip code, a store name, a store category, a store number a transaction description, a purchase frequency, a total spending amount, and the like. Further, the transaction data may be anonymized.
In embodiments, methods and systems may comprise presenting, in a user financial account graphical user interface, an opportunity to assess alternative offerings related to a transaction that is presented within the account graphical user interface, wherein the transaction is related to a presently selected offering, and in response to the selection of the opportunity, redirecting the user to an alternative offering graphical user interface adapted to present the user with alternative offerings. The bill's details may be analyzed and normalized for comparison with an alternative offering that has been normalized, and if the alternative offering presents an improvement in comparison to the presently selected offering, the alternative offering may be presented in the alternative offering graphical user interface. The bill details may include a merchant name, a merchant category, a merchant location, a transaction amount, a transaction frequency, a zip code, a store name, a store category, a store number a transaction description, a purchase frequency, a total spending amount, and the like. The improvement may be related to a cost, a coverage, a quality, a rating, and the like. The financial account may be a credit card account, a bank account, a checking account, a savings account, a personal finance program account, a loan account, and the like. Further, the transaction may be anonymized. The opportunity to assess alternative offerings may relate to a plurality of transactions.
In embodiments, methods and systems may comprise gathering transaction data relating to a user's bill wherein the bill is related to a presently selected offering, analyzing the transaction data, wherein the step of analyzing involves normalizing the transaction data such that a comparison to other offers can be assessed, collecting offer usage data relating to an alternative offering and normalizing the offer usage data such that a comparison with the transaction data can be assessed, comparing the normalized transaction data with the normalized offer usage data to assess if the alternative offering presents an advantage to the user in comparison to the presently selected offering, and in response to an assessment indicating that the alternative offering presents an improvement to the user, presenting, in a user financial account statement, an indication that an alternative offering related to the bill is available. The statement may be an online statement, an online graphical user interface associated with the user's financial account, an online bill pay area, a dialog box associated with the user's financial account, an ATM receipt, a teller receipt, a mobile statement, a paper statement, and the like. The improvement may be related to a cost, a coverage, a quality, a rating, and the like. The financial account may be a credit card account, a bank account, a checking account, a savings account, a personal finance program account, a loan account, and the like. Analyzing the transaction data may comprise anonymizing the transaction data.
In embodiments, methods and systems may comprise presenting a statement of a user's financial transaction data, where the financial transaction data were obtained from a financial institution that maintains a financial account on behalf of the user, and presenting a map of a geographic area and indicating where, within the geographic area, a savings opportunity is presented, wherein the savings opportunity relates to the financial transaction data. The map may be presented in proximity to the financial transaction data. The map may be presented in a separate window from the financial transaction data. The statement may be an online statement, an online graphical user interface associated with the user's financial account, an online bill pay area, a dialog box associated with the user's financial account, an ATM receipt, a teller receipt, a mobile statement, a paper statement, and the like. The financial account may be a credit card account, a bank account, a checking account, a savings account, a personal finance program account, a loan account, and the like. Further, the financial transaction data may be anonymized. The geographic area may relate to a user's identified location. The user's location may be identified manually by the user. The user's location may be identified automatically from a mobile device implementing the method. The savings opportunity may comprise an offer to perform a bill analysis. Further, generating and displaying a link may be provided in a graphical user interface to the user's financial account, to a transaction assessment user interface to compare the transaction to a plurality of alternative offers. The savings opportunity may be a coupon. The coupon may be a barcode presented on a mobile device. The coupon may be a printed coupon presented in a statement. The coupon may be an online redemption coupon code. The savings opportunity may be an automatic discount on a subsequent transaction. The savings opportunity may be a credit on a subsequent transaction. When the user makes the subsequent transaction, the user may receive the credit. The savings opportunity may be a pre-paid offer. The pre-paid offer may be charged immediately to the user's financial account. The pre-paid offer may be redeemed via an online coupon code, an in-store coupon, a mobile phone coupon, and the like. The savings opportunity may be a merchant loyalty program.
In embodiments, methods and systems may comprise gathering transaction data from a user for a merchant from a user's financial account, where the user's financial account is a financial institution account that is maintained on behalf of the user; analyzing the transaction data to determine if an aspect of the transaction data meet a criteria set by the merchant; if the transaction data meet the criteria, matching a savings opportunity from the merchant to the user based on the analyzed transaction data; and enabling the user to redeem the savings opportunity during a subsequent transaction with the merchant. The criteria may comprise a total spending amount with the merchant, a number of transactions with the merchant, a number of transactions within a category, total spending during a period of time, a particular transaction, a particular set of transactions, a transaction at a particular merchant location, and the like. The financial account may be a bank account, a checking account, a savings account, a credit account, a personal finance program account, a loan account, and the like. Enabling may comprise automatic redemption upon presentation of a transaction card associated with the user's financial account. Enabling may comprise providing the user with a printed coupon, a bar code coupon presented on a mobile device, a credit on a merchant loyalty card, and the like. Analyzing may comprise anonymizing the financial transaction data. Analyzing may comprise extracting a merchant name, a merchant category, a merchant location, a transaction amount, a transaction frequency, a zip code, a store name, a store category, a store number, a transaction description, a purchase frequency, a total spending amount, and the like.
In embodiments, methods and systems may comprise gathering transaction data from a user for a merchant from a user's financial account, wherein the user's financial account is a financial institution account that is maintained on behalf of the user; analyzing the transaction data; matching a savings opportunity from the merchant to the user based on the analyzed transaction data; and enabling the user to redeem the savings opportunity during a subsequent transaction with the merchant. The financial account may be a bank account, a checking account, a savings account, a credit account, a personal finance program account, a loan account, and the like. Enabling may comprise automatic redemption upon presentation of a transaction card associated with the user's financial account. Enabling may comprise providing the user with at least one of a printed coupon, a bar code coupon presented on a mobile device, and a credit on a merchant loyalty card. Analyzing may comprise anonymizing the financial transaction data. Analyzing may comprise extracting a merchant name, a merchant category, a merchant location, a transaction amount, a transaction frequency, a zip code, a store name, a store category, a store number, a transaction description, a purchase frequency, a total spending amount, and the like.
In embodiments, methods and systems may comprise presenting a merchant bill assessment graphical user interface where an indication of a savings opportunity is presented, and in response to a placement of a savings opportunity in a graphical user interface associated with a user's financial account, wherein the savings opportunity was related to one or more transactions processed through the user's financial account, tracking interaction with the savings opportunity and reporting the tracking to a merchant through the merchant bill assessment graphical user interface. The reporting may comprise reporting on a total spending amount with the merchant, a number of transactions with the merchant, a number of transactions within a category, total spending during a period of time, a particular transaction, a particular set of transactions, a transaction at a particular merchant location, and the like.
In embodiments, methods and systems may comprise an executable script such that when embedded in a graphical user interface of a user's financial account will automatically provide the user, through the graphical user interface, a savings opportunity interface, wherein savings opportunities relating to user financial transactions will be presented. The executable program may be implemented in the JavaScript programming language.
In embodiments, methods and systems may comprise embedding an executable script in a graphical user interface of a user's financial account, executing the executable script when the user accesses the user financial account; and using the executable script to: (1) gather transaction data from the user financial account and anonymize the transaction data before transmitting the anonymized transaction data to a server for analysis; (2) instruct a decision engine in communication with the server to select a savings opportunity to match to the user based on the anonymized transaction data analyzed by the server; (3) receive an indication of the matched savings opportunity from the decision engine; and (4) display the savings opportunity in the user financial account graphical user interface. Analyzing may comprise extracting a merchant name, a merchant category, a merchant location, a transaction amount, a transaction frequency, a zip code, a store name, a store category, a store number, a transaction description, a purchase frequency, a total spending amount, and the like. Further, the executable script may be used to instruct the decision engine to consult a rules database in making the match. The rules database may comprise criteria that the transaction data should meet before a match is made. The criteria may comprise a total spending amount with the merchant, a number of transactions with the merchant, a number of transactions within a category, total spending during a period of time, a particular transaction, a particular set of transactions, a transaction at a particular merchant location, and the like. The financial account may be a bank account, a checking account, a savings account, a credit account, a personal finance program account, a loan account, and the like.
In embodiments, methods and systems may comprise: providing an executable script such that when embedded in a graphical user interface of a user's financial account will automatically provide a merchant with anonymized information relating to transactions made by the user from the user's financial account; and in response to receipt of the anonymized information, enabling the merchant to present a savings opportunity to the user, which will appear in the graphical user interface. The executable program may be implemented in the JavaScript programming language. The user may select to which merchants the executable program can transmit the anonymized information. A user financial account host may select to which merchants the executable program can transmit the anonymized information.
In embodiments, methods and systems may comprise embedding a first executable script in a graphical user interface of a user's financial account, executing the first executable script when the user accesses the user financial account, and using the first executable script to: (1) gather transaction data from the user financial account and anonymize the transaction data before transmitting the anonymized transaction data to a first server for analysis and (2) specify the address of a second executable script, wherein the second executable script accesses the analyzed transaction data and performs a function with the analyzed transaction data. The executable script may be implemented in the JavaScript programming language.
In embodiments, methods and systems may comprise embedding an executable script in a graphical user interface of a user's financial account, executing the executable script when the user accesses the user financial account, and using the executable script to: (1) gather transaction data from the user financial account and anonymize the transaction data before transmitting the anonymized transaction data to a server for analysis; and (2) transmit the transaction data to a third party application to be leveraged. The third party application may be a fraud detection application. The third party application may be a transaction analytics application. The third party application may be a marketing application. The third party application may be a social networking application. The executable script may be implemented in the JavaScript programming language.
In an aspect of the invention, a method for a conditional purchase may include receiving a conditional purchase offer for a good or service, wherein the conditional purchase offer specifies at least one of a desired discount and an offer price, comparing the conditional purchase offer with at least one of an inventory and a pricing information to determine if the conditional purchase offer is acceptable, if the conditional purchase offer is acceptable, optionally binding the customer to purchase the good or service, wherein binding comprises automatically charging a financial account of the user for the good or service, and if the conditional purchase offer is not acceptable, allowing the user to modify at least one of the discount and offer price.
A system and method for platform-driven savings opportunity matching includes gathering transaction data from a user's financial account, wherein the user's financial account is a financial institution account that is maintained on behalf of the user and analyzing the transaction data for a psychographic inference. A savings opportunity from a database of savings opportunities is matched to the user based on the psychographic inference. The savings opportunity is displayed in association with a statement of the user's financial account. The psychographic inference may relate to at least one of a credit rating, a gender, an age group, a life event, an income level, and a demographic.
A system and method for financial institution- and merchant-driven savings opportunity matching includes gathering transaction data from a user's financial account, wherein the user's financial account is a financial institution account that is maintained on behalf of the user and analyzing the transaction data for a savings opportunity indication. A filter may be applied to a database of savings opportunities prior to matching one to the user based on the savings opportunity indication. The savings opportunity may be displayed in association with a statement of a user's financial account. The filter may relate to a host of the user's financial account. The filter may be a blacklist of at least one of a merchant, a merchant type, a transaction type, a time period, and a savings opportunity type. The filter may relate to a merchant offering a savings opportunity. The filter may relate to a past spend with the merchant, a past spend in a category, a past purchase frequency, a transaction, and a change in purchase pattern.
A system and method for user-driven savings opportunity matching includes gathering transaction data from a user's financial account, wherein the user's financial account is a financial institution account that is maintained on behalf of the user and analyzing the transaction data for a savings opportunity indication. A savings opportunity from a database of savings opportunities may be matched to the user based on the savings opportunity indication. The savings opportunity may be displayed in association with a statement of a user's financial account, and the user is allowed to interact with the savings opportunity. The interaction data may be used to drive a subsequent match of a savings opportunity. The interaction data may be a past response to a savings opportunity. The system and method may further include decreasing the number of matches made if the response is negative. The system and method may further include increasing the number of matches made if the response is positive. The system and method may further include changing the type of savings opportunity matched if the response is negative. The interaction data may be a like or dislike of the savings opportunity. The interaction data may be an expansion of a savings opportunity headline to reveal additional details. The interaction data may be a sharing of the savings opportunity with at least one of a second user and a social network.
A system and method for providing rewards through a user financial instrument includes gathering transaction data from a user's financial account, wherein the user's financial account is a financial institution account that is maintained on behalf of the user and analyzing the transaction data to determine a reward level. The savings opportunity from the merchant may be matched to the user based on the reward level. The user is enabled to redeem the savings opportunity during a subsequent transaction with the merchant. The system and method may further include allowing the merchant to set a criterion for determining the reward level. The criterion may relate to an amount spent with the merchant. The criterion may relate to a number of visits to the merchant. As the reward level improves, the matched savings opportunity may improve.
A system and method for providing a future reward through a user financial instrument includes gathering transaction data from a user's financial account, wherein the user's financial account is a financial institution account that is maintained on behalf of the user and analyzing the transaction data to determine a future savings opportunity accessible to the user after completion of a goal. Systems and methods track progress towards completing the goal. The user is enabled to obtain the future savings opportunity when the goal is completed. The system and method may further include allowing the merchant to set the goal. The goal may relate to an amount spent with the merchant. The goal may relate to a number of visits to the merchant.
A system and method for providing socially enabled rewards through a user financial instrument includes gathering transaction data from a user's financial account and analyzing the transaction data for a savings opportunity indication. A savings opportunity from a database of savings opportunities is matched to the user based on the savings opportunity indication, wherein the savings opportunity can be shared with other users or a social network. The savings opportunity is displayed in association with a statement of a user's financial account and the user is allowed to share the savings opportunity, wherein sharing causes a shared savings opportunity to be generated. A second user, one who received the shared savings opportunity, can redeem the shared savings opportunity. The sharing and redemption of the shared savings opportunity is tracked, such as to improve targeting users who are influential based on the number of redemptions of the shared savings opportunity. The system and method may further include allowing a merchant to modify the savings opportunity priori to generating the shared savings opportunity.
A system and method for providing a geo-enhanced savings opportunity in association with a financial account includes gathering transaction data from a user's financial account and analyzing the transaction data for a savings opportunity indication. A savings opportunity from a database of savings opportunities is matched to the user based on the savings opportunity indication. The savings opportunity is displayed in association with a statement of a user's financial account. A response to the savings opportunity is tracked in order to receive an indication of whether or not the savings opportunity has been accepted. If it was not accepted, an additional incentive to accept the savings opportunity may be made when the user is in a geographic location set by a merchant offering the savings opportunity. The incentive may be at least one of an additional % discount, an additional monetary discount, an additional savings opportunity, the opportunity to share the savings opportunity, and a related opportunity.
A system and method for providing a savings opportunity matched to a spend pattern in association with a financial account includes gathering transaction data from a user's financial account and analyzing the transaction data for a spend pattern. A savings opportunity from a database of savings opportunities is matched to the user based on the spend pattern. The savings opportunity is displayed in association with a statement of a user's financial account. The system and method may further include gathering a past response to a savings opportunity and analyzing it, wherein the savings opportunity is based on both the spend pattern and past response data.
Methods and systems for a conditional purchase may include gathering transaction data from a user's financial account, wherein the user's financial account is a financial institution account that is maintained on behalf of the user and analyzing the transaction data for a savings opportunity indication. A savings opportunity is matched from a database of savings opportunities to the user based on the savings opportunity indication. The user may provide a conditional purchase offer for a good or service identified by the savings opportunity, wherein the conditional purchase offer specifies at least one of a desired discount and an offer price. The conditional purchase offer is compared with at least one of an inventory and a pricing information to determine if the conditional purchase offer is acceptable. If the conditional purchase offer is acceptable, the customer may be bound to purchase the good or service, wherein binding comprises automatically charging a financial account of the user for the good or service. If the conditional purchase offer is not acceptable, the user may modify at least one of the discount and offer price of the conditional purchase offer to try to gain acceptance again.
A system and method for matching a savings opportunity using census data includes gathering transaction data from a user's financial account and analyzing the transaction data for a savings opportunity indication. Third party census data related to a geographic location of the user may be used in addition to the savings opportunity indication to match a savings opportunity from a database of savings opportunities to the user. The savings opportunity is displayed in association with a statement of the user's financial account. The system and method may further include gathering a past response to a savings opportunity indication and analyzing it, wherein the savings opportunity is based on both the analyzed transaction data and past response data.
A system and method for matching a savings opportunity using third party data includes gathering transaction data from a user's financial account and analyzing the transaction data for a savings opportunity indication. Third party data regarding the savings opportunity may be used in addition to the savings opportunity indication to match a savings opportunity from a database of savings opportunities to the user. The savings opportunity is displayed in association with a statement of the user's financial account. The third party data may relate to an aspect of the merchant. The third party data may relate to an aspect of a product or service offered by the merchant.
These and other systems, methods, objects, features, and advantages of the present invention will be apparent to those skilled in the art from the following detailed description of the preferred embodiment and the drawings.
All documents mentioned herein are hereby incorporated in their entirety by reference. References to items in the singular should be understood to include items in the plural, and vice versa, unless explicitly stated otherwise or clear from the text. Grammatical conjunctions are intended to express any and all disjunctive and conjunctive combinations of conjoined clauses, sentences, words, and the like, unless otherwise stated or clear from the context.
The invention and the following detailed description of certain embodiments thereof may be understood by reference to the following figures:
Referring to
Referring now to
In an embodiment, collecting service usage data for a user's current service using a computer implemented facility 202 may comprise the service usage data being input manually by the user to the computer implemented facility. For example, using the user interface 102, a wireless service user may indicate their service usage data, such as how much they spend a month, how many anytime minutes they use, how many wireless lines they have, if they send text, video, or MMS messages, how frequently they message, their geographic locations of use, and the like. The service usage data may be for a current use, past use, or a predicted future use. The service usage data may relate to more than one service plan. In an embodiment, the service usage data may relate to a single service usage parameter. In an alternative embodiment, the service usage data may be obtained automatically, such as with a secure retrieval application. For example, the user may give permission for the data engine 120 to log into the user's service account and obtain the service usage data. In an embodiment, the service usage data are obtained from usage records or billing records, either current or historical. In some embodiments, the data engine 120 obtains a copy of a bill and processes it to obtain the service usage data. The service usage data may relate to more than one service plan. In an alternative embodiment, the service usage data are obtained from an application. For example, the application may be an online banking application, personal financial management software, a bill payment application, a check writing application, a logging application, a mobile phone usage logging application, a computer usage logging application, a browsing application, a search application, and the like. The service usage data may consist of average usage data over a specified period of time in the past. The service usage data may be obtained independent of a user's billing data.
In an embodiment, analyzing the service usage data to obtain a normalized service usage dataset 204 may comprise processing historical usage data to obtain an average normalized usage dataset. Alternatively, processing a single time period's usage data may be done to obtain a normalized usage dataset for that time period. Normalizing usage data may be done by sorting the data according to service-related data types used to define a data model. In an embodiment, the data are sorted according the same data types used in the normalized alternative service offering model to facilitate applying the normalized alternative service offering model to the usage data
In an embodiment, normalizing data related to a plurality of alternative service offerings may be done according to a normalized alternative service offering model. The data engine 120 is programmed to extract data related to alternative service offerings from multiple sources, some of which may be human-generated. For example, the data engine 120 may be programmed to know the location of rate plan data on a wireless carrier's website. The data related to the plurality of alternative service offerings may be obtained from a data vendor, a human-assisted normalization system, public information sources, direct connections to service providers, and the like. The data then are normalized according to an alternative service offering model. Normalizing data related to the plurality of alternative service offerings may include defining a plurality of service usage-related data types, such as number of peak minutes available, number of nights and weekend minutes available, and the like, collecting parameters related to a service usage using the computer implemented facility, such as how many minutes were used during a particular time period, and normalizing the service parameters according to the defined service usage-related data types to generate a normalized alternative service offering model. The data engine 120 may sort all of the data it collects for each plan and its potential add-on's according to the normalized alternative service offering model. As the data are collected from various sources, it is integrated according to the normalized alternative service offering model. Normalization occurs via at least one of two methods, semantic normalization, syntactic normalization, and the like. In semantic normalization, a string of characters or set of words, phrases, number, and the like may be determined to mean something specific in the data model. Semantic normalization may be done by human encoding, where humans decide the semantic meaning, or may be done in an automated fashion. For example, the normalized alternative service offering model may have only a field for afternoon rates, but a provider's rate plan segments the day according to chunks of hours, such as from 1 pm-4 pm, and the like. The data normalization platform 118 may examine the data from the service provider and determine that the 1 pm-4 pm time period rate should be described as an afternoon rate in the normalized alternative service offering model. The assignment of the provider's rate time period to a particular field of the normalized alternative service offering model may only need to be done once in order for the data normalization platform 118 to know how to interpret the data every time it pulls data automatically, such as for updating, from the service provider. In syntactic normalization, the data normalization platform 118 possesses certain information to convert certain patterns to others. For example, the data normalization platform 118 can extract the 1 pm to 2 pm time period and assign it to Hour A, extract the 2 pm to 3 pm time period and assign it to Hour B, extract the 3 pm to 4 pm time period and assign it to Hour C, and so on. In an embodiment, the data may be enhanced or validated prior to normalization.
In an embodiment, a canonical model for the user data may be defined manually. Then, an agent, or data engine, may be defined or taught so it knows how to map data from a given source into the canonical model. The data engine may be automated from then on. The data engine is taught by a human how to read the data, then convert that into a global concept, such as a model of a cell phone bill. Then the data engine may be instructed to run on a specific item, such as a bill from VERIZON, to pull data and map the data to a canonical model.
Referring to
In an embodiment, the business rules server 122 may enhance and/or validate the normalized data, either the normalized service usage dataset or the normalized alternative service offering dataset, and/or the normalized alternative service offering model. Rules may be applied to the datasets or model, such as rules regarding a given vertical, rules based on facts about a rate plan, add-on's, phones or devices, their relative importance in determining the best plan or an aggregate score, information about the user, information about similar users, and the like. The business rules server 122 may verify that the datasets and/or model fit known facts and heuristics stored in the business rules server 122.
In an embodiment, producing a plurality of alternative service offering normalized datasets may comprise applying the normalized alternative service offering model to the normalized service usage dataset. In some embodiments, the alternative service offering normalized datasets comprise at least the cost for the alternative service offering. The normalized alternative service offering model is applied to the normalized service usage dataset in order to determine what the cost of a particular alternative service offering would be given the user's service usage. For example, the normalized alternative service offering model may be envisioned as a matrix 300. For example, in
In an embodiment, determining if an alternative service offering is better than the user's current service may comprise comparing the alternative service offering normalized datasets to the normalized usage dataset. Applying the model to the usage data may comprise the decision engine 108 multiplying the number of minutes or messages used during the time period by the rate during the time period. If the data normalization platform 118 determined that 100 calls were made during the Weekday 7 am-8 am time period and the user sent and/or received 100 text messages, the cost for the Current Provider A, if only these two data types were considered, would be $20 while Provider D would be $12. The decision engine 108 may determine that given the user's service usage, the service offering from Provider D may be a better fit to the user given the lower cost. In an alternative embodiment, the data engine 120 may have pulled additional information, such as the opportunity to purchase an unlimited message plan, and placed it in the matrix 300. Therefore, when the model is applied to the service usage data, the decision engine 108 may perform an optimization with respect to messaging, calculating if it is cheaper to go with the pay-as-you-go plan or getting unlimited messaging. Continuing with the above example, if Current Provider A offered a flat rate for messaging of $5 per month while Provider D only offered the pay-per-message rate structure, the decision engine 108 optimization may result in Current Provider A offering the service offering with the better fit to the user given the lower cost of Current Provider A's service ($10) versus Provider D's service ($12). In this case, the user may be advised to not change their service provider but perhaps ask the provider to add on the flat message rate feature.
Cost may be only one component in determining if an alternative service offering is better than the user's current service. User preference, signal strength, terms and conditions, and the like may all be components of determining if an alternative service offering is better than the user's current service. In an embodiment, the decision engine 108 may perform a personalized impact analysis. The decision engine 108 may compute an aggregate score for each alternative service offering normalized dataset. For example, when the service offering is a wireless service, the aggregate score may include a normalization of the alternative service offering savings and signal strength. In an example, the data engine 120 may extract usage information then map the usage onto a wireless plan. In embodiments, the wireless plan may also have optional add-on's and Term's & Condition's added into the calculation for aggregate score. For any given service, the decision engine 108 may be able to select the best possible option from a range of service plans. Then, the decision engine 108 may be able to select optimal add-on's to achieve the lowest impact, or the best aggregate score. In embodiments, the user may be able to specify what criteria to include in the aggregate score calculation. In the case of wireless plans, wireless coverage or signal strength may also be a component of the aggregate score. Individual scores attributed to components of the service may be added together, often in a non-trivial formula, to weight them and come up with an aggregate score. For example, a score may be assigned to term's and condition's, a score may be assigned to signal strength, a score may be assigned to savings over a current service plan, and the like. Users may be able to set the weighting, such as with a slider or manually. Alternatively, certain assumptions may be made in providing an automatic weighting. Assumptions may be provided and stored on the business rules server 122.
The aggregate score may include cost and at least one other element. The other element may be selected from the group consisting of total cost, per unit cost, savings, and service quality. The instruction may further include collecting data points about the service offering and calculating the aggregate score based on those data points. The data points may be identified in the terms and conditions of the service offering. The data points may be in declarations related to the service offering.
In an embodiment, once an aggregate score is calculated, the alternative service plans may be ranked, such as according to aggregate score, according to savings, according to signal strength, according to a combination of the above, and the like, in order to compare the various alternative service plans. In some embodiments, the aggregate score may be plotted according to the overall cost of the service plan. In some embodiments, comparing service plans includes ranking the alternative service offerings according to total costs, per unit costs, and service quality or signal strength.
In an embodiment, after comparing service plans, the user may have the option to purchase a service plan or contact a current service provider in order to modify their current service.
In an embodiment, at any point during the process of collecting 202, analyzing 204, normalizing 208, applying 210 and comparing 212, an advertisement may be presented to the user, wherein the advertisement is selected based on an alternative service offering.
In an embodiment, the system 100 may repeat 214 the steps of collecting 202, analyzing 204, normalizing 208, applying 210 and comparing 212 periodically to determine on an updated basis which alternative service offering is better than the user's current service. The user may be alerted when an alternative service offering that is better than the user's current service is available, such as by email, phone, SMS, MMS, and the like. The repetition interval may be set by the user or may be a pre-determined system 100 interval. The user may also be alerted that the repetition 214 is occurring.
In an embodiment, the user may be a business entity.
In an embodiment, when the service offering is a wireless service offering, the service usage data and data related to the alternative service offering may relate to at least one of plan definitions, add-on's, carrier coverage networks, cost, included minutes, plan capacity, additional line cost, anytime minutes, mobile-to-mobile minutes, minutes overage, nights & weekends minutes, nights start, nights end, roaming minutes, peak/off-peak minutes, data/downloads/applications charges, data overages, data megabytes used/unused, most frequently called numbers, most frequently called locations, networks/carriers called, calls per day, time of day usage, day of week usage, day of month usage, overages, unused services, carrier charges, messaging, messaging overage, activation fees, early termination fees, payment preferences, carrier, current hardware, compatible hardware, hardware availability, coverage area, signal strength, included services, caller ID block, call waiting, call forwarding, caller ID, voicemail, visual voicemail, 3-way calling, insurance, at least one wireless service related item. and the like. Any of the aforementioned service usage data types may be used to calculate an aggregate score, in comparing service offerings, in ranking service offerings, and the like.
In an embodiment, when the service offering is a credit card service, the service usage data and data related to the alternative service offering may relate to at least one of monthly spending, spending categories, credit rating, current credit card, years of use of credit card, current balance, monthly pay-off amount, current APR, pay off every month, carry a balance, sign-up bonus, bonus rewards, base earning rate, maximum earning rate, earning limit, total value of rewards, earned program promotions, spend program promotions, net asset promotions, annual fee, late fee, balance transfer fee, cash advance fee, purchases APR, introductory APR, regular APR, penalty APR, balance transfer APR, cash advance APR, typical redemptions, redemption options, rewards type, credit card network, credit card issuer, features and benefits, at least one credit card related item and the like. For example, typical redemptions may include domestic airfare, international airfare, car rentals, cash rebates, charitable donations, consumer electronics, cruises, hotel stays, restaurants, shopping, and the like. The redemption may relate to an item of value, a service, and a class of services. The class of services may be one of first class, business class, coach class, and premium class.
A user may weight the availability of domestic airfare redemption options higher than the option of receiving a cash rebate, and the weighting may be used to rank credit card offerings accordingly. In another example, the rewards type may be at least one of cash, points, certificates, vouchers, discounts, and miles. In another example, the features and benefits may include at least one of instant approval, no annual fee, secured card, no fraud liability, 24 hr. customer service, airport lounge access, auto rental insurance, concierge service, emergency replacement, extended warranty, online account management, photo security, price protection, purchase protection, return protection, roadside assistance, travel insurance, and the like. Any of the aforementioned credit card data types may be used to calculate an aggregate score, in comparing credit card offerings, in ranking credit card offerings, and the like.
Referring now to
In an embodiment, at any point during the process of performing 402, associating 404, collecting 408, analyzing 410, normalizing 412, applying 414 and comparing 418, an advertisement may be presented to the user, wherein the advertisement is selected based on an alternative service offering.
In an embodiment, the system 100 may repeat the steps of performing 402, associating 404, collecting 408, analyzing 410, normalizing 412, applying 414 and comparing 418 periodically to determine on an updated basis which alternative service offering is better than the user's current service. The user may be alerted when an alternative service offering that is better than the user's current service is available, such as by email, phone, SMS, MMS, and the like. The repetition interval may be set by the user or may be a pre-determined system 100 interval. The user may also be alerted that the repetition is occurring.
In an embodiment, the user may be a business entity.
In an embodiment, the credit card usage data and data related to the alternative credit card may relate to at least one of monthly spending, spending categories, credit rating, current credit card, years of use of credit card, current balance, monthly pay-off amount, current APR, pay off every month, carry a balance, sign-up bonus, bonus rewards, base earning rate, maximum earning rate, earning limit, total value of rewards, earned program promotions, spend program promotions, net asset promotions, annual fee, late fee, balance transfer fee, cash advance fee, purchases APR, introductory APR, regular APR, penalty APR, balance transfer APR, cash advance APR, typical redemptions, redemption options, rewards type, credit card network, credit card issuer, features and benefits, and the like. For example, typical redemptions may be for domestic airfare, international airfare, car rentals, cash, charitable donations, consumer electronics, cruises, hotel stays, restaurants, and shopping. The rewards type may be one of cash, points, and/or miles. The features and benefits may include at least one of instant approval, no annual fee, secured card, no fraud liability, 24 hr. customer service, airport lounge access, auto rental insurance, concierge service, emergency replacement, extended warranty, online account management, photo security, price protection, purchase protection, return protection, roadside assistance, travel insurance, and the like.
In an alternative embodiment, credit card usage data may be analyzed to obtain a value of rewards. For example, credit card usage data for a user's current credit card may be collected 502, such as by using a computer implemented facility. Then the data may be analyzed to obtain a value of rewards 504. An indication of a rewards redemption may be received 508. A user-specific value of rewards may be calculated by multiplying a user-specific exchange rate by the normalized value of rewards 510. In addition to the rewards program data described herein, information related to calculating a value of rewards may also be collected 502. Analyzing 504 may include processing historical usage data to obtain an average value of rewards, processing a single time period's usage data to obtain a value of rewards for that time period, and the like. The exchange rate may relate to the currency system of the user's country or a different country. The system 1000 may automatically compare the value of rewards in different currencies because the system 100 may be able to convert the value of a reward point to a dollar in a personalized way. The personalized exchange rate for you may depend on what the user wants to redeem the points for. For example, redemption outside the user's country might have much more value than redemption inside the user's country. In the example, a user might get as much as 4 cents per point as compared to 0.5 cents per point depending on what, and where, the user redeems the points. Certain currencies, for example, may be more valuable to one user when compared to another user.
In an embodiment, the system 100 may repeat the steps of collecting 502, analyzing 504, receiving 508, and calculating 510 periodically to determine on an updated basis a user-specific value of rewards. The user may be alerted when a reward of a different or particular value is available, such as by email, phone, SMS, MMS, and the like. The repetition interval may be set by the user or may be a pre-determined system 100 interval. The user may also be alerted that the repetition is occurring.
Referring to
In an embodiment, a data normalization platform 118 for generating a normalized service usage model may include a business rules server 122 for storing the definitions of a plurality of service usage-related data types, a data engine 120 for collecting service parameters related to a service usage using a computer implemented facility, and a data normalization engine 124 for normalizing the service parameters according to the defined service usage-related data types to generate a normalized service usage model. In
In an embodiment, estimating the cost of an alternative service may include a decision engine 108 for applying a normalized alternative service offering model to a normalized service usage dataset to produce a plurality of alternative service offering normalized datasets, and a ranking facility 128 for comparing the alternative service offering normalized datasets to the normalized usage dataset to determine if an alternative service offering is better than the user's current service. In embodiments, the ranking facility 128 may be an integral part of the decision engine 108. The ranking facility 128 may optionally consider weights of certain dataset factors in comparing datasets. The ranking facility 128 may compare datasets based on cost. The cost may be the cost of the service offering. The cost may be a monthly savings over an existing service. The cost may be an annual savings over an existing service. The ranking facility 128 may compare datasets based on cost plus another factor. The factors may be weighted by a user. The factors may be assigned a score. The score may be based on relevance to personal usage. The ranking facility 128 may compare datasets based on a calculated score. The score may be based on relevance to personal usage. The ranking facility 128 may compare datasets based on rewards associated with a credit card offering.
In an embodiment, the system may include a user-interface 102 for performing a comparison of services, receiving input from a user regarding a user's current service usage, wherein the service usage data may be analyzed to obtain a normalized usage dataset, and enabling the user to review a plurality of alternative service offering normalized datasets generated by application of a normalized alternative service offering model to a normalized service usage dataset. The input may be a usage history provided by a user manually. The input may be login information required to automatically acquire a billing record from a service provider or third-party billing agent.
In an embodiment, comparing service offerings may include a business rules server 122 for storing the definitions of a plurality of service usage-related data types, a data engine 120 for collecting service parameters related to a service usage using a computer implemented facility, a data normalization engine 124 for normalizing the service parameters according to the defined service usage-related data types to generate a normalized service usage model for alternative service offerings and a normalized service usage dataset for a user's current service, a decision engine 108 for applying a normalized service usage model to the normalized service usage dataset to produce a plurality of alternative service offering normalized datasets, and a ranking facility 128 for comparing the alternative service offering normalized datasets to the normalized usage dataset to determine if an alternative service offering is better than the user's current service. A monitoring engine 104 may cause the system 100 to periodically compare service offerings to determine on an updated basis which alternative service offering is better than the user's current service. The normalized service usage model may be stored in a product database 110. The normalized service usage dataset may be stored in a user profile database 112. The results from comparing may be stored in a tracking database 114.
In an embodiment, referring to
Referring to
Referring now to
Referring now to
Referring now to
In an embodiment, the system may be a search engine that may compare a plurality of product and service options according to the needs of the users. On the basis of past and predicted service usage of the user, the system may suggest a service plan to the user that may be appropriate for the user's requirements. In an example, the system may suggest a service plan by comparing the costs of the service plans. The costs may be the cost of the service offering. The costs may be a monthly savings over an existing service. The costs may be an annual savings over an existing service. Also, the system may periodically compare service offerings to determine on an updated basis which alternative service offering is better than the user's current service.
A user reviewing their online financial account presents an opportunity for delivery of offers, sales opportunities, and various other opportunities based on the platform 100 of this disclosure or third party applications. An executable script running on a client used to view a user financial account may enable analysis of transaction data, including bill pay entries, from the user financial account in order to provide offers or sales opportunities based on the transaction data. The executable program may be called via a single line of JavaScript embedded in the user financial account webpage. The single line of JavaScript may also be used to call, or integrate, 3rd party or other related applications. For example, a mapping interface may leverage the capability of the executable program to analyze transaction data, match offers from an offer database, and present the locations of the offers on a map. Analyzing the transaction data may include automatically extracting merchant data, such as merchant name, merchant category, transaction category, store name, zip code, spending amounts, purchase frequency, product category, or the like. Transaction entries may be analyzed and matched against a database of offers and sales opportunities to interweave a related offer or sales opportunity. For example, in the case of a transaction description, matching to an offer may be done using natural language processing (NLP). If the transaction entry relates to a service, the analysis may indicate that an alternative offering may be available upon a more detailed analysis. A link to an alternative offering assessment interface may be provided. Alternatively, the executable program may integrate the functionality of the alternative offering assessment interface and provide an indication of an improved offering interweaved with the transaction. Analysis of the transaction data may be limited to individual transactions or may encompass all transactions on a statement, transactions from a particular period of time, transactions from a particular merchant or merchant(s), transactions of a particular nature, and the like. By analyzing transactions from a particular merchant, for example, that merchant may be able to provide offers to the user during a subsequent transaction based on past transactions. In effect, merchants can provide a merchant loyalty program implemented through the use of a transaction card associated with the financial account. Merchants may be able to track various indicia associated with this new kind of loyalty program, as well as make, update track or fulfill offers and sales opportunities through use of a merchant dashboard.
In embodiments, the platform 100 may be enabled to specifically target current customers or competitor customers as they review their recent transactions via an online or paper account statement. The account statement may be a bank statement, a credit card statement, a debit card statement, a stored value card statement, a bill payment system, and any other system for managing transactions on an account like a personal financial management system. Referring to
In an embodiment, the account statements may facilitate the system to identify various merchants listed in the account statements. Thereafter, the identified merchants may be matched with their appropriate business type or category. For example, the merchant may be automatically categorized as a telephone service provider, gas station owner, a coffeehouse owner, and the like. In an embodiment, the system may notify the user of a potential savings with an alternative service plan or item. For example, the system may recommend alternative services such as wireless plans, oil and gas services, and the like to the users as per their past and predicted usage. In the statement, the user may be invited to interact with the consumer service comparison shopping system 100 to investigate whether there are indeed savings to be had with an alternative service plan or item.
In an embodiment, the system may provide offers/recommendations based on analysis and identification of transactions made in a single account. Again referring to
Further,
The system may match an offer based on identification and analysis of the transactions made across multiple accounts. The offer shown to the customer may be driven by a combination of three different rules: what the merchant wants to show the customer, what the financial institutions want to show the customer, and what the customer chooses to see. These rules may be stored in a rules database of the system.
Further, the system may provide an account aggregation and other online financial services. Account aggregation may include compilation of information from different accounts, which may include bank accounts, credit card accounts, investment accounts, and other user or business accounts, into a single place. The account aggregation may be provided by online banking solution providers. The account aggregators may analyze the transaction summary of a user and may categorize merchants from it. The merchants may be categorized such as Oil & Gas, Grocery, Retail, and the like. In few cases, the merchants may not fall under any of the pre-defined categories. In such cases, the account aggregators may assign codes to such merchants.
Further, the account statements of the different accounts may be analyzed by the system. The account aggregators may analyze the transactions across all the accounts. For example, a user may charge their Starbucks purchases to a plurality of banks such as Citibank, Bank of America, and the like. The activity at Starbucks across all accounts held by the user may be identified by the account aggregator. Therefore, if a user makes a payment through any of the banks associated with the account aggregator, the user may get loyalty-based offers from Starbucks through the system. In an embodiment, the system may include a natural language processing (NLP) technology. The NLP technology is a form of human-to-computer interaction where the elements of human language, spoken or written, may be formalized so that a computer may perform value-adding tasks based on that interaction. The NLP technology may match offers with relevant and targeted transactions. For example, if a transaction statement is not clear, the system may get details about the purchases using the NLP technology. The details may include, but are not limited to, merchant, location of the store, and amount spent.
In an embodiment, the system may provide anonymity of the users. The identity of the user may not be provided to the system and the merchant. The bank may be the only one that may know the identity, however, the bank may not be provided with the information of the various offers that may be provided/redeemed to the users.
Once the users access the system, the users may enter their service usage data and preference data through the user interface. The data may include a current service provider, a current service cost, a current service usage, and the like. In an alternative embodiment, the data may be gathered automatically from the user's service provider by a transaction engine when the user logs into the user's service account. Either a core transaction engine or one of a plurality of transaction engines, such as one per merchant, may be used to gather a user's data. The service usage data provided by the user may be compared with other service usage plans that may be stored in a database of the system. Thereafter, a decision engine may suggest the service usage plan to the user that may fit as per the preferences of the user.
The service usage plan may be suggested to the user by an alert engine by sending an e-mail, a text message, an alert, and the like. Further, a dashboard of the system may also include information about the present and suggested service plans of the user. In an embodiment, if the user changes his/her preferences about the service usage plan, the system may reflect those changes and may suggest other plans as per the new preferences of the user. The system may analyze the transactions carried out by a user and may verify the details of the transactions.
The system may include an API interface. This API interface may enable users to interact with the raw and analyzed data stored in the system through any number of applications.
Further, the description splitter may include a merchant tokenizer that may generate a sequence of tokens that may relate to a merchant. The sequence of tokens may be generated by a merchant learning engine that may suggest similar merchant names. The merchant may be searched in a merchant database of the system. Thereafter, a merchant parser of the system may parse through the merchant database. If the merchant is already stored in the merchant database, the system may match the merchant in the transaction. However, if the merchant is new, the merchant database may store that merchant for future reference. Further, the system may include architecture for offering rewards to the users.
The system of the present invention may provide automatic offer redemption to the users. The users may be informed about the various offers that may be applicable as per their account statements. Once the users have subscribed to the services offered by the system, the system may automatically provide various saving offers to the users. Further, the system may provide various offers to the users through multiple channels such as through short message service (SMS), e-mails, and the like. The banks may offer some rewards for the users for using their transaction cards while shopping. Therefore, when a user purchases some items using a transaction card, rewards may be automatically applied to the account associated with the transaction card.
In an embodiment, an offer may be redeemed by clicking on a link that takes the user to a special page that includes a discount for an online purchase. In another embodiment of redemption, a user may use a coupon code, either one-time or multiple use, at an online or offline location to gain discount. In another embodiment of redemption, a user may receive a prepaid instrument of some kind, such as a prepaid debit card, prepaid credit card, gift card, and the like, that can be used to redeem the discount. In another embodiment of redemption, the user may receive a credit on the statement automatically post purchase. In this embodiment, the user may receive an automated discount when a purchase is made or a discount that is applied off of a prior pre-purchased amount.
In an exemplary embodiment, the offers may be included in the account statements of the users. For example, if a user receives the account summary of a bank as a paper statement, the paper statement may include offers that may be printed below the expenses mentioned in the bank statement. In this example, if a user has spent some amount for paying internet bills, the system may provide information about other internet plans as per the requirement of the user.
Further, the system may provide offers/suggestions integrated in an electronic account statement of the user. The system may include a bookmarklet that enables displaying offers/rewards in-line with the transaction history of the user. The bookmarklet may be an applet that may be integrated with the browser to show in-line offers when a bank website, that may have the user's account, may be accessed. The applet may be a uniform resource locator (URL) of a bookmark in a web browser or the applet may be a hyperlink on a web page. The bookmarklet may enable the system to provide real-time analysis of the expenses incurred by the user. In an example, a user may wish to compare other product and service options against the analysis of the user's expenses. The real-time analysis may enable the user to find whether the user is over spending on various expenses or not.
In an embodiment, the services offered by the system of the present invention may be accessed through a JavaScript code. The financial institutions that may be associated with the system may include a single line of the JavaScript that may be added as per their requirement into the account statement page of the user's account. For example, the system may allow advertiser's to create targeted offers that may be delivered through the user's online account statements. The advertiser's may target the users based on many criteria such as zip code, store name, store category, transaction description, purchase frequency, spending amount, and the like.
In embodiments, there may be multiple possibilities for delivery of the rewards. For example, as mentioned herein, JavaScript integration may occur via a financial institution, aka partner, adding JavaScript to online account pages targeted for display of rewards. The system or the partner may host the JavaScript. In another example, push API integration may be used. Here, the system exposes its API to a partner that pushes transaction data to the system, keyed to specific user IDs. This allows the option to push transactions at fixed intervals (batch mode) or preferably upon event (real-time mode). In another example, pull API integration may be used. In pull API integration, a partner may expose its API to the system. The system may request transaction data associated with specific user IDs. The frequency of requests per-user may be done at agreed-upon intervals. In another example, batch transfer, where a partner pushes transaction files to a secure FTP area (hosted by the partner or the system) may be used. The frequency of updates may occur at agreed-upon intervals, such as hourly, daily, and the like. In yet another example, processor integration may be used, where the system integrates directly via an issuer processor to get real-time transactions via authorizations at the merchant processor. In any of the integration methods, integration may provide just the user interface, just the transaction data, or a combination thereof.
In embodiments, there may be categories based on which the advertisers target the users, in accordance with an embodiment of the present invention. In an example, the advertiser's may send selected offers that may target users who may spend around $500 on internet and cell phone bills. The advertiser's may send offers that may provide more features within the limited budget. In another example, the system may enable the advertiser's to track the users based on the category of stores frequently visited by the users. The stores may be categorized as grocery, retail, oil & gas, and the like. The advertiser's may give offers to existing users of a store to increase loyalty and spending of the user. The users may click on the offers made by the advertisers to activate the offers. In an embodiment, the system may enable the advertiser's to track both online and in-store purchases for measuring the results and optimizing the offers. The system tracks online and offline redemptions and may report them to advertisers. The system may also send offers through e-mails to various users. In an embodiment, in addition to the online account statement, the system may include mobile abilities and may facilitate SMS notifications to the users. For example, the system may be embodied as a mobile application, such as in
Further, the system may offer a “deal-of-the-day”, such as a discount on a single type of product for 24 hours, wherein the product is chosen based on a user's past transactions. In an embodiment, the various offers/suggestions provided by the system may be available in the form of printed coupons that may be used at a retail point of sale (POS) terminal. The offers may be delivered to the users through mails, e-mails, gift vouchers, and the like. The users may take a print of the offers sent through e-mails and may show at the POS terminal for redeeming the offer.
Referring to
Referring to
There is an indication of reward level 5314 in the savings opportunity. Actions, such as sharing the opportunity, liking the savings opportunity, accepting the savings opportunity and the like may improve the reward level 5314. The savings opportunity may improve with reward level.
The reward levels may be tiered. A merchant or the financial institution may set the reward level tiers. For example, one merchant may set reward levels based on number of visits, another may set them on total spend, while yet another may set levels based on a combination of the two. Via auditing and analyzing transactions, the system 2700 can keep track of reward level status.
In some embodiments, in order for a user to share the savings opportunity, such as by using the share button 5310, the savings opportunity must first be social-enabled by the merchant. When the merchant social-enables a savings opportunity, a shared savings opportunity is created. The shared savings opportunity is designed for the user to share, and may not be subject to the same criteria that may have triggered the offering of the original savings opportunity to the user. The system may track redemption of the shared savings opportunity by individual user or in aggregate. The system may track redemption of various shared savings opportunities to determine which user might have broad influence. The system may then target the influencer with improved, more frequent, or more exclusive savings opportunities.
Referring to
Using a user dashboard, the user may be able to view all of their reward level statuses with each merchant, view all current rewards, view all future rewards, and the like. Referring to
Referring to
The system of the present invention may include dashboards, such as a merchant dashboard, financial institution dashboard, user dashboard, and the like. Each dashboard may show the appropriate audience how users are doing with all the offers being shown to them, such as opens, clicks, and purchases, as well as enable them to edit and manage the rules governing offer presentation by interfacing to the rules database.
In an embodiment, a user dashboard that may be used for hosting various mini-applications. Users may click on a dashboard icon to activate the dashboard. The dashboard may enable the users to edit the various mini-applications of the dashboard. For example, the users may move the mini-application icons, rearrange the icons on the dashboard, delete some of the mini-applications, recreate the mini-applications so that more than one of the same mini-application is open at the same time, and the like.
In an embodiment, the system may include a merchant dashboard, a financial institution dashboard, and a user dashboard. The merchant dashboard may be used by the various merchants and advertisers for displaying various offers that are being made by them. The various offers may be listed under a tab on the dashboard. The users may click on the tab to view all the offers provided to them. Further, the merchant dashboard may enable a merchant to display the offers in different categories. For example, few offers may be in the form of discount coupons that may be redeemed if a user spends a pre-defined amount. The system may track the activities of the users and may inform the merchants about the user activities. For example, the dashboard may provide information about the number of users who have viewed the offers listed by the merchants. The merchants may also get information about the offers that may be redeemed by the users, and the like. Further, the merchant dashboard may include a merchant re-categorization tool that may facilitate the merchants to categorize themselves as per their business. For example, some merchants may categorize themselves as a retail merchant, oil and gas merchants, and the like.
In an embodiment, the financial institution dashboard may allow the financial institution to connect with the system for providing various offers to the users. The financial institution dashboard may facilitate the financial institutions that may be associated with the system to track the users. The financial institution dashboard may allow the financial institutions to track the opted-in accounts by the users. The opted-in accounts may be the accounts that may be majorly used by a user and the account on which the user may wish to receive offers. Further, the financial institution dashboard may accumulate preferences of the user for receiving the offers. For example, the financial institutions may get information about the offers which the user may wish to receive as a part of their account statement, and the like. Further, the financial institution dashboard may enable the associated financial institutions to re-categorize the merchants as per their convenience. The financial institutions may change the categories in which the merchants may have classified themselves; the financial institution dashboard may enable the financial institutions in doing so.
In an embodiment, the user dashboard may include information about all the offers that were redeemed by the users. The user dashboard may also enable the users to view various transactions done by the users over a specific period such as over a week, over a month, and the like. Further, the user dashboard may include information about the various rewards that may be received by the user. For example, the information may include the minimum amount that the user may need to spend in a day for being eligible for a reward, the number of the times the user may need to shop in a specific category of stores for being eligible for the reward, and the like. Further the user dashboard may also include a merchant re-categorization tool that may enable the users to categorize the merchants as per their convenience.
As mentioned earlier, the users may be provided offers through their account statements and may also get rewarded on using the transaction cards such as a credit card, a debit card, and a pre-paid card. In an embodiment of the present invention, the financial institutions associated with the system may get paid when a user redeems an offer provided by the financial institution. For example, if the account statement of the user suggests a cheaper cell phone plan, the user may compare his/her present plan and the suggested plan. If the user activates the suggested plan, the financial institution may get revenues from the redemption. However, if the user decides to continue with the earlier plan, the financial institution may not get any revenue. In a similar scenario, the system may also generate revenues if a user redeems an offer suggested by the system. The offer suggested by the system may be sent to the user in the form of a text message, an e-mail, and the like.
The decision engine 108 may apply factors in matching a savings opportunity to the user. For example, a financial institution may blacklist certain merchants, merchant types, transactions, transaction types, and the like from being used to match a purchase reward to the user. In another example, the financial institution or the merchant may use a spend pattern to match an offer to the user. In some embodiments, the offer may be made in conjunction with a display of spend pattern metrics. The spend pattern may be used to send alerts to the user regarding spend with a merchant, in a category, of a total amount, in a time period, and the like. In another example, a merchant may use past spend, past spend in a category, past purchase frequency, and the like to match a purchase reward to the user. In another example, the user's likes/dislikes, expand/collapse behavior regarding obtaining more information about an offer after seeing the offer headline, past purchase behavior, and the like may be used to match a purchase reward to the user. In yet another example, the system may use geographic proximity, location, inferences, seasonal adjustments, and the like to match a purchase reward to the user. For example, with respect to inferences, consumer traits may be identified by inference via transactional data, such as merchants, transactions, transaction types, merchant types, spend total, spend at a particular merchant, and the like. For example, based on transactional data, any of gender, credit rating, age group, life events, income level, psychographic state, demographics, and the like may be inferred. For example, a user suddenly spending more during multiple transactions at a high-end baby store may be inferred to be a high income, pregnant woman.
Transaction data may be augmented with third party data in order to improve the matches. In an embodiment, census data may be used in addition to the transaction data to make a match of a savings opportunity. Since the system works with anonymized transaction data, the system knows only what it can infer about the user or what is provided by the user. Based on the user's location, possibly inferred by the system or manually input by the user, census data for the location, such as ethnic makeup, population educational level, income levels, and the like, may be used to provide a substitute demographic profile for the user. One or more of the substitute demographic profile, transaction data, and inferred traits may be used to match a savings opportunity to the user. In another embodiment, merchant data may be accessed using a third party data source and used to improve targeting to the user. For example, a restaurant may be searched on YELP.COM to obtain information about the type of cuisine offered, type of atmosphere, price range and the like. These data may be used as factors in the system's match of a savings opportunity to a user. The 3rd party data may or may not be displayed to the user along with the savings opportunity. Continuing with the example, if the restaurant was determined to be a family-friendly place, a savings opportunity at the restaurant may not be matched to a person who has been inferred to be single/dating based on transactions for flowers and higher-end restaurants. In yet another embodiment, the savings opportunity may be analyzed and 3rd party data may be obtained to improve matching it. For example, 3rd party information about a product that is the subject of the savings opportunity may be used to improve the match.
In an embodiment, the system of the present disclosure may facilitate a conditional purchase by a user from a merchant of a good or service, wherein the purchase may be conditioned on receiving a discount wherein the discount may be provided based on various bidding offers that may be received from the user. For example, the user may place a bid for a purchase amount and a discount amount that they may wish to get. For example, a user interested in buying merchandise worth $100 from a retail store may ask for a discount of 40% on that merchandise as a pre-condition. In such cases, the merchant may decide whether or not to accept the bid offer from the user. The merchant decision may be based on one or more of an inventory, a production plan, a pricing strategy, and the like. The user may have the opportunity to modify their bid offer. For example, if the merchant does not accept the user's offer to purchase a $100 item at a 40% discount, after being notified of the decline, the user may decrease the discount requested, increase the quantity of items chosen, add additional items, modify the items, and the like and re-submit the offer for consideration by the merchant. This cycle may continue until the bid is accepted or the user stops bidding.
In another embodiment, the bid offer may be automatically incremented up until an amount indicated by the user or according to a rule. For example, the user may offer to purchase a $100 item at a 40% discount but indicate when they set their offer that if it may be declined by the merchant, it may automatically be incremented to a next bid offer. The next bid offer may be explicitly indicated by the user or may be determined by consulting one or more rules. For example, the user may indicate that the offer should be decreased by 5% each time the merchant declines the offer until reaching 20% where no further offers may be made.
In another example, a user may commit to purchasing an item of a particular value if a merchant is willing to sell that item at a lower cost. The merchant may decide whether or not to accept the commitment from the user.
In an exemplary embodiment, the merchant may accept or decline the bid offer through preset rules. These preset rules may include types of bid offers, types of discounts that the user may seek, and the like. These preset rules may be defined by the merchant. Further, the preset rules may facilitate a merchant to select bid offers to be accepted from the total bid offers received by the merchant. The preset rule may also enable the merchant to decide on the volume and kind of users from which the merchant may accept bid offers. In another embodiment, the merchant may accept bid offers dynamically. In this embodiment, the merchant may need to manually approve certain bid offers from a user from among the total bid offers received by the merchant. It will be evident to a person skilled in the art that merchants may accept bid offers through a combination of the preset rules and the dynamic fashion.
In an embodiment, once the user has placed a bid offer for a good or service, an acceptance message of the bid offer may be delivered to the user through one or more of an email, a text message, a message in their account statement, or the like. The account statement may facilitate the system to identify various merchants for which the user has placed a bid offer. Further, the account statement may also provide information about the merchant who may have accepted the bid offer placed by the user. In another embodiment, the user may be approached directly by the merchant who may have accepted the bid offer of the user. In such cases, the merchant may send an e-mail, text message, or the like to the user to inform them about the acceptance of their bid offer.
In an embodiment, when reviewing an account statement, a user may have the opportunity to present an offer for a future purchase to a merchant. The merchant may be identified on the current statement or may be identified by the system as an alternative good or service supplier. In any event, the statement may include an integrated application to make the offer or may include a link to an application for presenting offers. For example, as the user reviews their credit card statement transactions, the application may be integrated to put an instance of an offer window at each transaction line, somewhere on the statement, somewhere on the web page, and the like.
In an embodiment, the application may be a browser plug-in that is active as the user is visiting various websites. For example, as the user visits WALMART.COM and navigates various pages, the browser plug-in may deploy the application in a banner, frame, or the like for the website. When the user sees an item they would like to purchase, they can interact with the application to present an offer to WALMART for the item.
The methods and systems described herein may be deployed in part or in whole through a machine that executes computer software, program codes, and/or instructions on a processor. The processor may be part of a server, cloud server, client, network infrastructure, mobile computing platform, stationary computing platform, or other computing platform. A processor may be any kind of computational or processing device capable of executing program instructions, codes, binary instructions and the like. The processor may be or include a signal processor, digital processor, embedded processor, microprocessor or any variant such as a co-processor (math co-processor, graphic co-processor, communication co-processor and the like) and the like that may directly or indirectly facilitate execution of program code or program instructions stored thereon. In addition, the processor may enable execution of multiple programs, threads, and codes. The threads may be executed simultaneously to enhance the performance of the processor and to facilitate simultaneous operations of the application. By way of implementation, methods, program codes, program instructions and the like described herein may be implemented in one or more thread. The thread may spawn other threads that may have assigned priorities associated with them; the processor may execute these threads based on priority or any other order based on instructions provided in the program code. The processor may include memory that stores methods, codes, instructions and programs as described herein and elsewhere. The processor may access a storage medium through an interface that may store methods, codes, and instructions as described herein and elsewhere. The storage medium associated with the processor for storing methods, programs, codes, program instructions or other type of instructions capable of being executed by the computing or processing device may include but may not be limited to one or more of a CD-ROM, DVD, memory, hard disk, flash drive, RAM, ROM, cache and the like.
A processor may include one or more cores that may enhance speed and performance of a multiprocessor. In embodiments, the process may be a dual core processor, quad core processors, other chip-level multiprocessor and the like that combine two or more independent cores (called a die).
The methods and systems described herein may be deployed in part or in whole through a machine that executes computer software on a server, cloud server, client, firewall, gateway, hub, router, or other such computer and/or networking hardware. The software program may be associated with a server that may include a file server, print server, domain server, internet server, intranet server and other variants such as secondary server, host server, distributed server and the like. The server may include one or more of memories, processors, computer readable media, storage media, ports (physical and virtual), communication devices, and interfaces capable of accessing other servers, clients, machines, and devices through a wired or a wireless medium, and the like. The methods, programs or codes as described herein and elsewhere may be executed by the server. In addition, other devices required for execution of methods as described in this application may be considered as a part of the infrastructure associated with the server.
The server may provide an interface to other devices including, without limitation, clients, other servers, printers, database servers, print servers, file servers, communication servers, distributed servers and the like. Additionally, this coupling and/or connection may facilitate remote execution of program across the network. The networking of some or all of these devices may facilitate parallel processing of a program or method at one or more location without deviating from the scope of the invention. In addition, any of the devices attached to the server through an interface may include at least one storage medium capable of storing methods, programs, code and/or instructions. A central repository may provide program instructions to be executed on different devices. In this implementation, the remote repository may act as a storage medium for program code, instructions, and programs.
The software program may be associated with a client that may include a file client, print client, domain client, internet client, intranet client and other variants such as secondary client, host client, distributed client and the like. The client may include one or more of memories, processors, computer readable media, storage media, ports (physical and virtual), communication devices, and interfaces capable of accessing other clients, servers, machines, and devices through a wired or a wireless medium, and the like. The methods, programs or codes as described herein and elsewhere may be executed by the client. In addition, other devices required for execution of methods as described in this application may be considered as a part of the infrastructure associated with the client.
The client may provide an interface to other devices including, without limitation, servers, other clients, printers, database servers, print servers, file servers, communication servers, distributed servers and the like. Additionally, this coupling and/or connection may facilitate remote execution of program across the network. The networking of some or all of these devices may facilitate parallel processing of a program or method at one or more location without deviating from the scope of the invention. In addition, any of the devices attached to the client through an interface may include at least one storage medium capable of storing methods, programs, applications, code and/or instructions. A central repository may provide program instructions to be executed on different devices. In this implementation, the remote repository may act as a storage medium for program code, instructions, and programs.
The methods and systems described herein may be deployed in part or in whole through network infrastructures. The network infrastructure may include elements such as computing devices, servers, routers, hubs, firewalls, clients, personal computers, communication devices, routing devices and other active and passive devices, modules and/or components as known in the art. The computing and/or non-computing device(s) associated with the network infrastructure may include, apart from other components, a storage medium such as flash memory, buffer, stack, RAM, ROM and the like. The processes, methods, program codes, instructions described herein and elsewhere may be executed by one or more of the network infrastructural elements.
The methods, program codes, and instructions described herein and elsewhere may be implemented on a cellular network having multiple cells. The cellular network may either be frequency division multiple access (FDMA) network or code division multiple access (CDMA) network. The cellular network may include mobile devices, cell sites, base stations, repeaters, antennas, towers, and the like. The cell network may be a GSM, GPRS, 3G, EVDO, mesh, or other networks types.
The methods, programs codes, and instructions described herein and elsewhere may be implemented on or through mobile devices. The mobile devices may include navigation devices, cell phones, mobile phones, mobile personal digital assistants, laptops, palmtops, netbooks, pagers, electronic books readers, music players and the like. These devices may include, apart from other components, a storage medium such as a flash memory, buffer, RAM, ROM and one or more computing devices. The computing devices associated with mobile devices may be enabled to execute program codes, methods, and instructions stored thereon. Alternatively, the mobile devices may be configured to execute instructions in collaboration with other devices. The mobile devices may communicate with base stations interfaced with servers and configured to execute program codes. The mobile devices may communicate on a peer to peer network, mesh network, or other communications network. The program code may be stored on the storage medium associated with the server and executed by a computing device embedded within the server. The base station may include a computing device and a storage medium. The storage device may store program codes and instructions executed by the computing devices associated with the base station.
The computer software, program codes, and/or instructions may be stored and/or accessed on machine readable media that may include: computer components, devices, and recording media that retain digital data used for computing for some interval of time; semiconductor storage known as random access memory (RAM); mass storage typically for more permanent storage, such as optical discs, forms of magnetic storage like hard disks, tapes, drums, cards and other types; processor registers, cache memory, volatile memory, non-volatile memory; optical storage such as CD, DVD; removable media such as flash memory (e.g. USB sticks or keys), floppy disks, magnetic tape, paper tape, punch cards, standalone RAM disks, Zip drives, removable mass storage, off-line, and the like; other computer memory such as dynamic memory, static memory, read/write storage, mutable storage, read only, random access, sequential access, location addressable, file addressable, content addressable, network attached storage, storage area network, bar codes, magnetic ink, and the like.
The methods and systems described herein may transform physical and/or or intangible items from one state to another. The methods and systems described herein may also transform data representing physical and/or intangible items from one state to another, such as from usage data to a normalized usage dataset.
The elements described and depicted herein, including in flow charts and block diagrams throughout the figures, imply logical boundaries between the elements. However, according to software or hardware engineering practices, the depicted elements and the functions thereof may be implemented on machines through computer executable media having a processor capable of executing program instructions stored thereon as a monolithic software structure, as standalone software modules, or as modules that employ external routines, code, services, and so forth, or any combination of these, and all such implementations may be within the scope of the present disclosure. Examples of such machines may include, but may not be limited to, personal digital assistants, laptops, personal computers, mobile phones, other handheld computing devices, medical equipment, wired or wireless communication devices, transducers, chips, calculators, satellites, tablet PCs, electronic books, gadgets, electronic devices, devices having artificial intelligence, computing devices, networking equipments, servers, routers and the like. Furthermore, the elements depicted in the flow chart and block diagrams or any other logical component may be implemented on a machine capable of executing program instructions. Thus, while the foregoing drawings and descriptions set forth functional aspects of the disclosed systems, no particular arrangement of software for implementing these functional aspects should be inferred from these descriptions unless explicitly stated or otherwise clear from the context. Similarly, it will be appreciated that the various steps identified and described above may be varied, and that the order of steps may be adapted to particular applications of the techniques disclosed herein. All such variations and modifications are intended to fall within the scope of this disclosure. As such, the depiction and/or description of an order for various steps should not be understood to require a particular order of execution for those steps, unless required by a particular application, or explicitly stated or otherwise clear from the context.
The methods and/or processes described above, and steps thereof, may be realized in hardware, software or any combination of hardware and software suitable for a particular application. The hardware may include a general purpose computer and/or dedicated computing device or specific computing device or particular aspect or component of a specific computing device. The processes may be realized in one or more microprocessors, microcontrollers, embedded microcontrollers, programmable digital signal processors or other programmable device, along with internal and/or external memory. The processes may also, or instead, be embodied in an application specific integrated circuit, a programmable gate array, programmable array logic, or any other device or combination of devices that may be configured to process electronic signals. It will further be appreciated that one or more of the processes may be realized as a computer executable code capable of being executed on a machine readable medium.
The computer executable code may be created using a structured programming language such as C, an object oriented programming language such as C++, or any other high-level or low-level programming language (including assembly languages, hardware description languages, and database programming languages and technologies) that may be stored, compiled or interpreted to run on one of the above devices, as well as heterogeneous combinations of processors, processor architectures, or combinations of different hardware and software, or any other machine capable of executing program instructions.
Thus, in one aspect, each method described above and combinations thereof may be embodied in computer executable code that, when executing on one or more computing devices, performs the steps thereof. In another aspect, the methods may be embodied in systems that perform the steps thereof, and may be distributed across devices in a number of ways, or all of the functionality may be integrated into a dedicated, standalone device or other hardware. In another aspect, the means for performing the steps associated with the processes described above may include any of the hardware and/or software described above. All such permutations and combinations are intended to fall within the scope of the present disclosure.
While the invention has been disclosed in connection with the preferred embodiments shown and described in detail, various modifications and improvements thereon will become readily apparent to those skilled in the art. Accordingly, the spirit and scope of the present invention is not to be limited by the foregoing examples, but is to be understood in the broadest sense allowable by law.
All documents referenced herein are hereby incorporated by reference.
This application is a non-provisional of and claims the benefit of the filing date of Provisional Application 61/427,138, filed on Dec. 24, 2010, which is hereby incorporated by reference in its entirety. This application is a continuation-in-part of, and claims the benefit of the filing date of U.S. patent application Ser. No. 13/082,591, filed on Apr. 8, 2011, which claims the benefit of the filing date of Provisional Appl. 61/388,680, filed on Oct. 1, 2010; this application is also a continuation-in-part of, and claims the benefit of the filing date of U.S. patent application Ser. No. 12/501,572, filed on Jul. 13, 2009, which claims the benefit of the filing date of Provisional Appl. 61/146,120, filed on Jan. 21, 2009. Each of these applications is incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4965763 | Zamora | Oct 1990 | A |
| 5027388 | Bradshaw et al. | Jun 1991 | A |
| 5155763 | Bigus et al. | Oct 1992 | A |
| 5159625 | Zicker | Oct 1992 | A |
| 5187787 | Skeen et al. | Feb 1993 | A |
| 5257369 | Skeen et al. | Oct 1993 | A |
| 5339392 | Risberg et al. | Aug 1994 | A |
| 5384449 | Peirce | Jan 1995 | A |
| 5513102 | Auriemma | Apr 1996 | A |
| 5657072 | Aristides et al. | Aug 1997 | A |
| 5659601 | Cheslog | Aug 1997 | A |
| 5680607 | Brueckheimer | Oct 1997 | A |
| 5761650 | Munsil et al. | Jun 1998 | A |
| 5774870 | Storey | Jun 1998 | A |
| 5794207 | Walker et al. | Aug 1998 | A |
| 5832457 | O'brien et al. | Nov 1998 | A |
| 5905246 | Fajkowski | May 1999 | A |
| 5915214 | Reece et al. | Jun 1999 | A |
| 5945653 | Walker et al. | Aug 1999 | A |
| 6018718 | Walker et al. | Jan 2000 | A |
| 6021415 | Cannon et al. | Feb 2000 | A |
| 6049599 | McCausland et al. | Apr 2000 | A |
| 6070149 | Tavor et al. | May 2000 | A |
| 6070150 | Remington et al. | May 2000 | A |
| 6085169 | Walker et al. | Jul 2000 | A |
| 6101181 | Passint et al. | Aug 2000 | A |
| 6125173 | Jagadish et al. | Sep 2000 | A |
| 6282520 | Schirripa | Aug 2001 | B1 |
| 6285991 | Powar | Sep 2001 | B1 |
| 6327573 | Walker et al. | Dec 2001 | B1 |
| 6327574 | Kramer et al. | Dec 2001 | B1 |
| 6332126 | Peirce | Dec 2001 | B1 |
| 6351735 | Deaton et al. | Feb 2002 | B1 |
| 6356878 | Walker et al. | Mar 2002 | B1 |
| 6398646 | Wei et al. | Jun 2002 | B1 |
| 6430558 | Delano | Aug 2002 | B1 |
| 6466919 | Walker et al. | Oct 2002 | B1 |
| 6493685 | Ensel et al. | Dec 2002 | B1 |
| 6510418 | Case et al. | Jan 2003 | B1 |
| 6571279 | Herz et al. | May 2003 | B1 |
| 6587995 | Duboc et al. | Jul 2003 | B1 |
| 6601761 | Katis | Aug 2003 | B1 |
| 6631007 | Buis et al. | Oct 2003 | B1 |
| 6631185 | Fleming, III | Oct 2003 | B1 |
| 6697998 | Damerau et al. | Feb 2004 | B1 |
| 6710815 | Billmaier et al. | Mar 2004 | B1 |
| 6763226 | McZeal, Jr. | Jul 2004 | B1 |
| 6785592 | Smith et al. | Aug 2004 | B1 |
| 6792422 | Stride et al. | Sep 2004 | B1 |
| D501281 | Kole | Jan 2005 | S |
| 6839682 | Blume et al. | Jan 2005 | B1 |
| D501957 | Jagger | Feb 2005 | S |
| 6848542 | Gailey et al. | Feb 2005 | B2 |
| 6885997 | Roberts | Apr 2005 | B1 |
| 6898762 | Ellis et al. | May 2005 | B2 |
| 6904336 | Raines et al. | Jun 2005 | B2 |
| 6915254 | Heinze et al. | Jul 2005 | B1 |
| 6920611 | Spaeth et al. | Jul 2005 | B1 |
| 6932268 | McCoy et al. | Aug 2005 | B1 |
| 6970871 | Rayburn | Nov 2005 | B1 |
| 6990635 | Kurapati et al. | Jan 2006 | B2 |
| 7039221 | Tumey et al. | May 2006 | B1 |
| 7039600 | Meek et al. | May 2006 | B1 |
| 7043457 | Hansen | May 2006 | B1 |
| 7051925 | Schwarz | May 2006 | B2 |
| 7021531 | Myttenaere | Jun 2006 | B2 |
| 7072858 | Litzow et al. | Jul 2006 | B1 |
| 7072864 | Brake et al. | Jul 2006 | B2 |
| 7085731 | Powell et al. | Aug 2006 | B1 |
| 7086586 | Sullivan | Aug 2006 | B1 |
| 7130828 | Phillips et al. | Oct 2006 | B2 |
| 7130901 | Roach | Oct 2006 | B2 |
| 7136467 | Brockman et al. | Nov 2006 | B2 |
| 7165049 | Slater | Jan 2007 | B2 |
| 7180887 | Schwaderer et al. | Feb 2007 | B1 |
| 7187947 | White et al. | Mar 2007 | B1 |
| 7195157 | Swartz et al. | Mar 2007 | B2 |
| 7213256 | Kikinis et al. | May 2007 | B1 |
| 7227475 | Provenzano et al. | Jun 2007 | B1 |
| 7254367 | Helden et al. | Aug 2007 | B2 |
| 7283803 | Karaoguz et al. | Oct 2007 | B2 |
| 7343317 | Jokinen et al. | Mar 2008 | B2 |
| 7343334 | Adduci et al. | Mar 2008 | B1 |
| 7349557 | Tibor | Mar 2008 | B2 |
| 7366493 | Marsh et al. | Apr 2008 | B2 |
| 7386487 | Leggett et al. | Jun 2008 | B2 |
| 7389355 | Brown et al. | Jun 2008 | B2 |
| 7392224 | Bauer et al. | Jun 2008 | B1 |
| 7398253 | Pinnell | Jul 2008 | B1 |
| 7430531 | Snyder | Sep 2008 | B1 |
| 7455226 | Hammond et al. | Nov 2008 | B1 |
| 7467106 | Levine et al. | Dec 2008 | B1 |
| 7482925 | Hammad et al. | Jan 2009 | B2 |
| 7486944 | Carpenter et al. | Feb 2009 | B2 |
| 7505924 | Whitehead | Mar 2009 | B1 |
| 7512558 | Elad et al. | Mar 2009 | B1 |
| 7512626 | Chitgupakar et al. | Mar 2009 | B2 |
| 7516103 | Peitrucha, Jr. et al. | Apr 2009 | B1 |
| 7640200 | Gardner et al. | Dec 2009 | B2 |
| 7644019 | Woda et al. | Jan 2010 | B2 |
| 7647252 | Rampell et al. | Jan 2010 | B2 |
| D611200 | Packard | Mar 2010 | S |
| 7680899 | Barnes et al. | Mar 2010 | B1 |
| 7698170 | Darr et al. | Apr 2010 | B1 |
| 7702543 | Mackay et al. | Apr 2010 | B2 |
| 7702575 | Lofton et al. | Apr 2010 | B1 |
| 7707059 | Reed et al. | Apr 2010 | B2 |
| 7707090 | Snyder | Apr 2010 | B2 |
| 7711606 | Snyder | May 2010 | B2 |
| 7720720 | Sharma et al. | May 2010 | B1 |
| 7742966 | Erlanger | Jun 2010 | B2 |
| 7752077 | Holden et al. | Jul 2010 | B2 |
| 7760861 | Croak et al. | Jul 2010 | B1 |
| 7778907 | Haskins et al. | Aug 2010 | B1 |
| 7797453 | Meijer et al. | Sep 2010 | B2 |
| 7801783 | Kende et al. | Sep 2010 | B2 |
| 7827086 | Ellenberg et al. | Nov 2010 | B1 |
| 7848940 | Harniman et al. | Dec 2010 | B1 |
| 7857212 | Matthews | Dec 2010 | B1 |
| 7870021 | Mankoff | Jan 2011 | B2 |
| 7870025 | English | Jan 2011 | B2 |
| 7885870 | Nam et al. | Feb 2011 | B2 |
| 7890089 | Fujisaki | Feb 2011 | B1 |
| 7904327 | Phelan et al. | Mar 2011 | B2 |
| 7904332 | Merkley, Jr. et al. | Mar 2011 | B1 |
| 7904354 | Pepe et al. | Mar 2011 | B2 |
| 7904358 | Brittingham et al. | Mar 2011 | B2 |
| 7930204 | Sharma et al. | Apr 2011 | B1 |
| 7933895 | Amjadi | Apr 2011 | B2 |
| 7941353 | King et al. | May 2011 | B2 |
| 7986935 | D'Souza | Jul 2011 | B1 |
| 7996310 | Edwards et al. | Aug 2011 | B1 |
| 8005726 | Bao | Aug 2011 | B1 |
| 8033456 | Drummond et al. | Oct 2011 | B2 |
| 8069407 | Armandpour et al. | Nov 2011 | B1 |
| 8108406 | Kenedy et al. | Jan 2012 | B2 |
| 8112287 | Paul et al. | Feb 2012 | B1 |
| 8156045 | Rebenack et al. | Apr 2012 | B2 |
| 8160938 | Allen et al. | Apr 2012 | B2 |
| 8160957 | Egnatios et al. | Apr 2012 | B2 |
| 8177121 | Zimmerman et al. | May 2012 | B2 |
| 8185417 | Brown et al. | May 2012 | B1 |
| 8195507 | Postrel | Jun 2012 | B2 |
| 8209198 | Harkensee et al. | Jun 2012 | B2 |
| 8249961 | Hopkins | Aug 2012 | B1 |
| 8265952 | Smith | Sep 2012 | B1 |
| 8364521 | Ramer et al. | Jan 2013 | B2 |
| 8387858 | Bohn | Mar 2013 | B2 |
| 8489452 | Warner et al. | Jul 2013 | B1 |
| 8560398 | Gregov et al. | Oct 2013 | B1 |
| 8566197 | Satyavolu et al. | Oct 2013 | B2 |
| 8577856 | Mizrahi | Nov 2013 | B2 |
| 8600857 | Satyavolu et al. | Dec 2013 | B2 |
| 8615719 | Ramer et al. | Dec 2013 | B2 |
| 8639629 | Hoffman et al. | Jan 2014 | B1 |
| 8650105 | Satyavolu et al. | Feb 2014 | B2 |
| 8660891 | Ramer et al. | Feb 2014 | B2 |
| 8660893 | Fordyce, III | Feb 2014 | B2 |
| 8666376 | Ramer et al. | Mar 2014 | B2 |
| 8688517 | Lutnick | Apr 2014 | B2 |
| 8688671 | Ramer et al. | Apr 2014 | B2 |
| 8738486 | McGeehan et al. | May 2014 | B2 |
| 8768802 | Engle et al. | Jul 2014 | B2 |
| 8812351 | Zollino et al. | Aug 2014 | B2 |
| 8930265 | Blackhurst | Jan 2015 | B2 |
| 20010007978 | Marsh et al. | Jul 2001 | A1 |
| 20010014868 | Herz et al. | Aug 2001 | A1 |
| 20010032207 | Hartley et al. | Oct 2001 | A1 |
| 20010034704 | Farhat et al. | Oct 2001 | A1 |
| 20010037236 | Dixon et al. | Nov 2001 | A1 |
| 20010038624 | Greenberg et al. | Nov 2001 | A1 |
| 20010044762 | Nault | Nov 2001 | A1 |
| 20010049636 | Hudda | Dec 2001 | A1 |
| 20010051907 | Kumar et al. | Dec 2001 | A1 |
| 20010051920 | Joao et al. | Dec 2001 | A1 |
| 20020008626 | Waters et al. | Jan 2002 | A1 |
| 20020010598 | Johnson et al. | Jan 2002 | A1 |
| 20020013728 | Wilkman | Jan 2002 | A1 |
| 20020023051 | Kunzle et al. | Feb 2002 | A1 |
| 20020026348 | Fowler et al. | Feb 2002 | A1 |
| 20020040359 | Green et al. | Apr 2002 | A1 |
| 20020052776 | Rothman et al. | May 2002 | A1 |
| 20020052782 | Landesmann | May 2002 | A1 |
| 20020055835 | Carcoba Olivares et al. | May 2002 | A1 |
| 20020055924 | Liming | May 2002 | A1 |
| 20020065713 | Awada et al. | May 2002 | A1 |
| 20020065772 | Saliba et al. | May 2002 | A1 |
| 20020082920 | Austin et al. | Jun 2002 | A1 |
| 20020086660 | Sullivan et al. | Jul 2002 | A1 |
| 20020087682 | Roach | Jul 2002 | A1 |
| 20020091650 | Ellis | Jul 2002 | A1 |
| 20020104087 | Schaffer et al. | Aug 2002 | A1 |
| 20020120540 | Kende et al. | Aug 2002 | A1 |
| 20020123919 | Brockman et al. | Sep 2002 | A1 |
| 20020138284 | DeCotiis et al. | Sep 2002 | A1 |
| 20020138848 | Alao et al. | Sep 2002 | A1 |
| 20020154751 | Thompson et al. | Oct 2002 | A1 |
| 20020169658 | Adler | Nov 2002 | A1 |
| 20020169664 | Walker et al. | Nov 2002 | A1 |
| 20020169668 | Bank et al. | Nov 2002 | A1 |
| 20020174061 | Srinivasan et al. | Nov 2002 | A1 |
| 20020198775 | Ryan | Dec 2002 | A1 |
| 20020198803 | Rowe | Dec 2002 | A1 |
| 20030009393 | Norris | Jan 2003 | A1 |
| 20030009401 | Ellis | Jan 2003 | A1 |
| 20030014307 | Heng | Jan 2003 | A1 |
| 20030028415 | Herschap, III et al. | Feb 2003 | A1 |
| 20030032409 | Hutcheson et al. | Feb 2003 | A1 |
| 20030040964 | Lacek | Feb 2003 | A1 |
| 20030045266 | Staskal et al. | Mar 2003 | A1 |
| 20030046155 | Himmel et al. | Mar 2003 | A1 |
| 20030055723 | English | Mar 2003 | A1 |
| 20030056092 | Edgett et al. | Mar 2003 | A1 |
| 20030061132 | Yu et al. | Mar 2003 | A1 |
| 20030078800 | Salle et al. | Apr 2003 | A1 |
| 20030088463 | Kanevsky et al. | May 2003 | A1 |
| 20030093414 | Litzow et al. | May 2003 | A1 |
| 20030097270 | Musselwhite et al. | May 2003 | A1 |
| 20030130878 | Kruk et al. | Jul 2003 | A1 |
| 20030134648 | Reed et al. | Jul 2003 | A1 |
| 20030149596 | Bost | Aug 2003 | A1 |
| 20030154123 | Subbloie et al. | Aug 2003 | A1 |
| 20030158800 | Pisello et al. | Aug 2003 | A1 |
| 20030158818 | George et al. | Aug 2003 | A1 |
| 20030158844 | Kramer et al. | Aug 2003 | A1 |
| 20030191832 | Satyavolu et al. | Oct 2003 | A1 |
| 20030208754 | Sridhar et al. | Nov 2003 | A1 |
| 20030212598 | Raman | Nov 2003 | A1 |
| 20030216971 | Sick et al. | Nov 2003 | A1 |
| 20030229572 | Raines et al. | Dec 2003 | A1 |
| 20030233276 | Pearlman et al. | Dec 2003 | A1 |
| 20030233278 | Marshall | Dec 2003 | A1 |
| 20040002924 | Boone et al. | Jan 2004 | A1 |
| 20040005900 | Zilliacus | Jan 2004 | A1 |
| 20040006608 | Swarna et al. | Jan 2004 | A1 |
| 20040043770 | Amit et al. | Mar 2004 | A1 |
| 20040054572 | Oldale et al. | Mar 2004 | A1 |
| 20040054610 | Amstutz et al. | Mar 2004 | A1 |
| 20040067747 | Carpenter et al. | Apr 2004 | A1 |
| 20040083146 | Goodwin et al. | Apr 2004 | A1 |
| 20040083183 | Hardesty et al. | Apr 2004 | A1 |
| 20040090458 | Yu et al. | May 2004 | A1 |
| 20040093324 | Marappan | May 2004 | A1 |
| 20040102980 | Reed et al. | May 2004 | A1 |
| 20040103017 | Reed et al. | May 2004 | A1 |
| 20040111370 | Saylors et al. | Jun 2004 | A1 |
| 20040117300 | Jones et al. | Jun 2004 | A1 |
| 20040122736 | Strock et al. | Jun 2004 | A1 |
| 20040123314 | Bova | Jun 2004 | A1 |
| 20040143546 | Wood et al. | Jul 2004 | A1 |
| 20040162778 | Kramer et al. | Aug 2004 | A1 |
| 20040209595 | Bekanich | Oct 2004 | A1 |
| 20040210524 | Benenati et al. | Oct 2004 | A1 |
| 20040217585 | Mitchell | Nov 2004 | A1 |
| 20040225609 | Greene | Nov 2004 | A1 |
| 20040243468 | Cohagan et al. | Dec 2004 | A1 |
| 20040267611 | Hoerenz | Dec 2004 | A1 |
| 20040267665 | Nam et al. | Dec 2004 | A1 |
| 20050010472 | Quatse et al. | Jan 2005 | A1 |
| 20050021420 | Michelitsch et al. | Jan 2005 | A1 |
| 20050026117 | Judson et al. | Feb 2005 | A1 |
| 20050030291 | Yanagisawa | Feb 2005 | A1 |
| 20050037755 | Hind et al. | Feb 2005 | A1 |
| 20050038893 | Graham | Feb 2005 | A1 |
| 20050055275 | Newman et al. | Mar 2005 | A1 |
| 20050059397 | Zhao | Mar 2005 | A1 |
| 20050065855 | Geller | Mar 2005 | A1 |
| 20050065981 | Blinn et al. | Mar 2005 | A1 |
| 20050080665 | Bowman-Amuah | Apr 2005 | A1 |
| 20050096976 | Nelms et al. | May 2005 | A1 |
| 20050120389 | Boss et al. | Jun 2005 | A1 |
| 20050125343 | Mendelovich | Jun 2005 | A1 |
| 20050131761 | Trika et al. | Jun 2005 | A1 |
| 20050131792 | Rowe | Jun 2005 | A1 |
| 20050160003 | Berardi | Jul 2005 | A1 |
| 20050165646 | Tedesco et al. | Jul 2005 | A1 |
| 20050183002 | Chapus | Aug 2005 | A1 |
| 20050189414 | Fano et al. | Sep 2005 | A1 |
| 20050192897 | Rogers et al. | Sep 2005 | A1 |
| 20050209921 | Roberts et al. | Sep 2005 | A1 |
| 20050213511 | Reece et al. | Sep 2005 | A1 |
| 20050220280 | Steinberg | Oct 2005 | A1 |
| 20050278716 | Koppen et al. | Dec 2005 | A1 |
| 20060004825 | Barda | Jan 2006 | A1 |
| 20060016875 | Bonalle et al. | Jan 2006 | A1 |
| 20060022048 | Johnson | Feb 2006 | A1 |
| 20060044307 | Song | Mar 2006 | A1 |
| 20060053056 | Alspach-Goss | Mar 2006 | A1 |
| 20060053060 | Wyker | Mar 2006 | A1 |
| 20060111967 | Forbes | May 2006 | A1 |
| 20060123462 | Lunt et al. | Jun 2006 | A1 |
| 20060143027 | Jagnnathan et al. | Jun 2006 | A1 |
| 20060143072 | Herman et al. | Jun 2006 | A1 |
| 20060149648 | Brown | Jul 2006 | A1 |
| 20060151598 | Chen et al. | Jul 2006 | A1 |
| 20060161599 | Rosen | Jul 2006 | A1 |
| 20060165060 | Dua | Jul 2006 | A1 |
| 20060173767 | Hansen | Aug 2006 | A1 |
| 20060173772 | Hayes et al. | Aug 2006 | A1 |
| 20060173974 | Tang | Aug 2006 | A1 |
| 20060178868 | Billerey-Mosier | Aug 2006 | A1 |
| 20060195359 | Robinson et al. | Aug 2006 | A1 |
| 20060206376 | Gibbs et al. | Sep 2006 | A1 |
| 20060208060 | Mendelovich et al. | Sep 2006 | A1 |
| 20060208064 | Mendelovich et al. | Sep 2006 | A1 |
| 20060208065 | Mendelovich et al. | Sep 2006 | A1 |
| 20060229996 | Keithly et al. | Oct 2006 | A1 |
| 20060242050 | Haggerty et al. | Oct 2006 | A1 |
| 20060247978 | Davis | Nov 2006 | A1 |
| 20060253321 | Heywood | Nov 2006 | A1 |
| 20060259364 | Strock et al. | Nov 2006 | A1 |
| 20060259390 | Rosenberger et al. | Nov 2006 | A1 |
| 20060271997 | Jacoby et al. | Nov 2006 | A1 |
| 20060277465 | Pandit et al. | Dec 2006 | A1 |
| 20060287950 | Steinberg et al. | Dec 2006 | A1 |
| 20070011044 | Hansen | Jan 2007 | A1 |
| 20070043608 | May et al. | Feb 2007 | A1 |
| 20070061487 | Moore et al. | Mar 2007 | A1 |
| 20070067208 | Haggerty et al. | Mar 2007 | A1 |
| 20070078719 | Schmitt et al. | Apr 2007 | A1 |
| 20070084917 | Fajkowski | Apr 2007 | A1 |
| 20070094114 | Bufford et al. | Apr 2007 | A1 |
| 20070129955 | Dalmia et al. | Jun 2007 | A1 |
| 20070150352 | Kelly-frank et al. | Jun 2007 | A1 |
| 20070156530 | Schmitt | Jul 2007 | A1 |
| 20070156533 | Hammond et al. | Jul 2007 | A1 |
| 20070168267 | Zimmerman et al. | Jul 2007 | A1 |
| 20070181674 | Taylor et al. | Aug 2007 | A1 |
| 20070185756 | Ahn | Aug 2007 | A1 |
| 20070201376 | Marshall-Wilson | Aug 2007 | A1 |
| 20070203880 | Kumar et al. | Aug 2007 | A1 |
| 20070260520 | Jha et al. | Nov 2007 | A1 |
| 20070263069 | Jendbro | Nov 2007 | A1 |
| 20070294271 | Bammi et al. | Dec 2007 | A1 |
| 20070298766 | Fan et al. | Dec 2007 | A1 |
| 20080010099 | Walker et al. | Jan 2008 | A1 |
| 20080010132 | Aaron et al. | Jan 2008 | A1 |
| 20080071634 | Rampell et al. | Mar 2008 | A1 |
| 20080077487 | Davis et al. | Mar 2008 | A1 |
| 20080078831 | Johnson et al. | Apr 2008 | A1 |
| 20080082373 | Durocher et al. | Apr 2008 | A1 |
| 20080085707 | Fadell | Apr 2008 | A1 |
| 20080086356 | Glassman et al. | Apr 2008 | A1 |
| 20080086361 | Eliezerov et al. | Apr 2008 | A1 |
| 20080086365 | Zollino et al. | Apr 2008 | A1 |
| 20080086474 | Haycraft et al. | Apr 2008 | A1 |
| 20080091528 | Rampell et al. | Apr 2008 | A1 |
| 20080091539 | Ruckart | Apr 2008 | A1 |
| 20080091593 | Egnatios et al. | Apr 2008 | A1 |
| 20080103883 | Szybalski et al. | May 2008 | A1 |
| 20080103968 | Bies et al. | May 2008 | A1 |
| 20080108308 | Ullah | May 2008 | A1 |
| 20080109304 | Sarelson et al. | May 2008 | A1 |
| 20080109888 | Ullah | May 2008 | A1 |
| 20080120292 | Sundaresan et al. | May 2008 | A1 |
| 20080133327 | Ullah | Jun 2008 | A1 |
| 20080133336 | Altman | Jun 2008 | A1 |
| 20080133351 | White et al. | Jun 2008 | A1 |
| 20080140484 | Akerman | Jun 2008 | A1 |
| 20080140505 | Romano et al. | Jun 2008 | A1 |
| 20080141281 | Ramsey et al. | Jun 2008 | A1 |
| 20080155453 | Othmer | Jun 2008 | A1 |
| 20080162258 | Kala et al. | Jul 2008 | A1 |
| 20080187118 | Short | Aug 2008 | A1 |
| 20080201143 | Olligschlaeger et al. | Aug 2008 | A1 |
| 20080201206 | Pokorney et al. | Aug 2008 | A1 |
| 20080208649 | Ficery et al. | Aug 2008 | A1 |
| 20080220760 | Ullah | Sep 2008 | A1 |
| 20080221972 | Megdal et al. | Sep 2008 | A1 |
| 20080221984 | Abhyanker | Sep 2008 | A1 |
| 20080222015 | Megdal et al. | Sep 2008 | A1 |
| 20080228566 | Williams et al. | Sep 2008 | A1 |
| 20080243587 | Chang et al. | Oct 2008 | A1 |
| 20080268868 | Maitland et al. | Oct 2008 | A1 |
| 20080270240 | Chu | Oct 2008 | A1 |
| 20080275774 | Pepe et al. | Nov 2008 | A1 |
| 20080277465 | Pletz et al. | Nov 2008 | A1 |
| 20080288405 | John | Nov 2008 | A1 |
| 20080294513 | Buse, Jr. | Nov 2008 | A1 |
| 20080300973 | DeWitt et al. | Dec 2008 | A1 |
| 20080304638 | Jackowitz et al. | Dec 2008 | A1 |
| 20080306985 | Murray et al. | Dec 2008 | A1 |
| 20080313256 | Kanazawa et al. | Dec 2008 | A1 |
| 20090006212 | Krajicek et al. | Jan 2009 | A1 |
| 20090006525 | Moore | Jan 2009 | A1 |
| 20090012844 | Ohlsen et al. | Jan 2009 | A1 |
| 20090015211 | Ribellino et al. | Jan 2009 | A1 |
| 20090027223 | Hill | Jan 2009 | A1 |
| 20090037268 | Zaid et al. | Feb 2009 | A1 |
| 20090037332 | Cheung et al. | Feb 2009 | A1 |
| 20090037735 | O'Farrell et al. | Feb 2009 | A1 |
| 20090048884 | Olives et al. | Feb 2009 | A1 |
| 20090074300 | Hull et al. | Mar 2009 | A1 |
| 20090076887 | Spivack et al. | Mar 2009 | A1 |
| 20090076896 | DeWitt et al. | Mar 2009 | A1 |
| 20090076925 | DeWitt et al. | Mar 2009 | A1 |
| 20090077163 | Ertugrul et al. | Mar 2009 | A1 |
| 20090089176 | McCabe | Apr 2009 | A1 |
| 20090091650 | Kodama et al. | Apr 2009 | A1 |
| 20090106202 | Mizrahi | Apr 2009 | A1 |
| 20090112639 | Robinson Beaver | Apr 2009 | A1 |
| 20090132347 | Anderson et al. | May 2009 | A1 |
| 20090132395 | Lam et al. | May 2009 | A1 |
| 20090138386 | Wilson, Jr. et al. | May 2009 | A1 |
| 20090144201 | Gierkink et al. | Jun 2009 | A1 |
| 20090150211 | Bayne | Jun 2009 | A1 |
| 20090156190 | Fisher | Jun 2009 | A1 |
| 20090164274 | Narayanaswamy et al. | Jun 2009 | A1 |
| 20090170483 | Barnett | Jul 2009 | A1 |
| 20090171779 | Shrivathsan | Jul 2009 | A1 |
| 20090182597 | Bull et al. | Jul 2009 | A1 |
| 20090192876 | De et al. | Jul 2009 | A1 |
| 20090193046 | Desai et al. | Jul 2009 | A1 |
| 20090234710 | Belgaied Hassine et al. | Sep 2009 | A1 |
| 20090234742 | Hart | Sep 2009 | A1 |
| 20090234826 | Bidlack | Sep 2009 | A1 |
| 20090254412 | Braswell | Oct 2009 | A1 |
| 20090259518 | Harvey et al. | Oct 2009 | A1 |
| 20090265233 | Sendo et al. | Oct 2009 | A1 |
| 20090271275 | Regmi et al. | Oct 2009 | A1 |
| 20090282036 | Fedtke | Nov 2009 | A1 |
| 20090287562 | Bosch et al. | Nov 2009 | A1 |
| 20090292599 | Rampell et al. | Nov 2009 | A1 |
| 20090292608 | Polachek et al. | Nov 2009 | A1 |
| 20090293018 | Wilson et al. | Nov 2009 | A1 |
| 20090299857 | Brubaker | Dec 2009 | A1 |
| 20090313106 | Taylor et al. | Dec 2009 | A1 |
| 20090327111 | Bulawa et al. | Dec 2009 | A1 |
| 20100003967 | Datta et al. | Jan 2010 | A1 |
| 20100005048 | Bodapati et al. | Jan 2010 | A1 |
| 20100010836 | Rosen et al. | Jan 2010 | A1 |
| 20100010887 | Karlin et al. | Jan 2010 | A1 |
| 20100017325 | Scherpa | Jan 2010 | A1 |
| 20100042471 | Chang et al. | Feb 2010 | A1 |
| 20100063891 | Townsend et al. | Mar 2010 | A1 |
| 20100064001 | Daily et al. | Mar 2010 | A1 |
| 20100070334 | Monteverde | Mar 2010 | A1 |
| 20100070448 | Omoigui et al. | Mar 2010 | A1 |
| 20100076835 | Silverman | Mar 2010 | A1 |
| 20100100470 | Buchanan et al. | Apr 2010 | A1 |
| 20100100478 | Hansen et al. | Apr 2010 | A1 |
| 20100106568 | Grimes et al. | Apr 2010 | A1 |
| 20100106577 | Grimes | Apr 2010 | A1 |
| 20100106580 | Etheredge et al. | Apr 2010 | A1 |
| 20100106598 | Grimes | Apr 2010 | A1 |
| 20100112990 | Dingler et al. | May 2010 | A1 |
| 20100114654 | Lukose et al. | May 2010 | A1 |
| 20100114713 | Anderson et al. | May 2010 | A1 |
| 20100138344 | Wong et al. | Jun 2010 | A1 |
| 20100146263 | Das et al. | Jun 2010 | A1 |
| 20100153242 | Preston et al. | Jun 2010 | A1 |
| 20100161379 | Bene et al. | Jun 2010 | A1 |
| 20100161446 | Alfred et al. | Jun 2010 | A1 |
| 20100169234 | Metzger et al. | Jul 2010 | A1 |
| 20100183132 | Satyavolu et al. | Jul 2010 | A1 |
| 20100185452 | Satyavolu et al. | Jul 2010 | A1 |
| 20100185453 | Satyavolu et al. | Jul 2010 | A1 |
| 20100185454 | Satyavolu et al. | Jul 2010 | A1 |
| 20100185489 | Satyavolu et al. | Jul 2010 | A1 |
| 20100185490 | Satyavolu et al. | Jul 2010 | A1 |
| 20100185491 | Satyavolu et al. | Jul 2010 | A1 |
| 20100185492 | Satyavolu et al. | Jul 2010 | A1 |
| 20100185534 | Satyavolu et al. | Jul 2010 | A1 |
| 20100223641 | Hubbard | Sep 2010 | A1 |
| 20100250534 | Lee et al. | Sep 2010 | A1 |
| 20100257612 | McGuire et al. | Oct 2010 | A1 |
| 20100262487 | Edwards et al. | Oct 2010 | A1 |
| 20100274627 | Carlson | Oct 2010 | A1 |
| 20100287115 | Lo et al. | Nov 2010 | A1 |
| 20100331016 | Dutton et al. | Dec 2010 | A1 |
| 20110022540 | Stern et al. | Jan 2011 | A1 |
| 20110035288 | Clyne | Feb 2011 | A1 |
| 20110047016 | Cook | Feb 2011 | A1 |
| 20110054981 | Faith et al. | Mar 2011 | A1 |
| 20110087546 | Fordyce, III et al. | Apr 2011 | A1 |
| 20110087550 | Fordyce et al. | Apr 2011 | A1 |
| 20110093886 | Reddy et al. | Apr 2011 | A1 |
| 20110106698 | Isaacson et al. | May 2011 | A1 |
| 20110106840 | Barrett et al. | May 2011 | A1 |
| 20110119185 | Drummond et al. | May 2011 | A1 |
| 20110125565 | MacIlwaine et al. | May 2011 | A1 |
| 20110137928 | Engle et al. | Jun 2011 | A1 |
| 20110153402 | Craig | Jun 2011 | A1 |
| 20110208588 | Joa et al. | Aug 2011 | A1 |
| 20110216292 | LaFarre et al. | Sep 2011 | A1 |
| 20110225033 | Schmeyer | Sep 2011 | A1 |
| 20110238476 | Carr et al. | Sep 2011 | A1 |
| 20110238499 | Blackhurst et al. | Sep 2011 | A1 |
| 20110246268 | Satyavolu et al. | Oct 2011 | A1 |
| 20110246280 | Satyavolu et al. | Oct 2011 | A1 |
| 20110246281 | Satyavolu et al. | Oct 2011 | A1 |
| 20110246284 | Chaikin et al. | Oct 2011 | A1 |
| 20110246292 | Satyavolu et al. | Oct 2011 | A1 |
| 20110246299 | Satyavolu et al. | Oct 2011 | A1 |
| 20110246346 | 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 |
| 20110257985 | Goldstein | Oct 2011 | A1 |
| 20110258028 | Satyavolu et al. | Oct 2011 | A1 |
| 20110258049 | Ramer et al. | Oct 2011 | A1 |
| 20110270618 | Banerjee | Nov 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 |
| 20120010933 | Satyavolu et al. | Jan 2012 | A1 |
| 20120010936 | Satyavolu et al. | Jan 2012 | A1 |
| 20120053987 | Satyavolu et al. | Mar 2012 | A1 |
| 20120066046 | Satyavolu et al. | Mar 2012 | A1 |
| 20120066050 | Satyavolu et al. | Mar 2012 | A1 |
| 20120078682 | Pinsley et al. | Mar 2012 | A1 |
| 20120101896 | Veeneman et al. | Apr 2012 | A1 |
| 20120102036 | Parker, III et al. | Apr 2012 | A1 |
| 20120123924 | Rose et al. | May 2012 | A1 |
| 20120189186 | Csulits et al. | Jul 2012 | A1 |
| 20120265587 | Kinkead et al. | Oct 2012 | A1 |
| 20120303430 | Tiku et al. | Nov 2012 | A1 |
| 20130073389 | Heath | Mar 2013 | A1 |
| 20130132410 | Rineer | May 2013 | A1 |
| 20130254008 | Ovick et al. | Sep 2013 | A1 |
| 20130275190 | Rossi et al. | Oct 2013 | A1 |
| 20130290096 | Lizotte, III | Oct 2013 | A1 |
| 20130325548 | Kulkarni et al. | Dec 2013 | A1 |
| 20130325587 | Kothari et al. | Dec 2013 | A1 |
| 20130325608 | Kulkarni et al. | Dec 2013 | A1 |
| 20130325667 | Satyavolu et al. | Dec 2013 | A1 |
| 20130325680 | Satyavolu et al. | Dec 2013 | A1 |
| 20130325681 | Somashekar et al. | Dec 2013 | A1 |
| 20130346170 | Epstein et al. | Dec 2013 | A1 |
| 20140025461 | Knowles et al. | Jan 2014 | A1 |
| 20140025492 | Donlan et al. | Jan 2014 | A1 |
| 20140051501 | Boyles | Feb 2014 | A1 |
| 20140095364 | Satyavolu et al. | Apr 2014 | A1 |
| 20140129357 | Goodwin | May 2014 | A1 |
| 20140136410 | Akin et al. | May 2014 | A1 |
| 20140143109 | Satyavolu et al. | May 2014 | A1 |
| 20140172560 | Satyavolu et al. | Jun 2014 | A1 |
| 20140180783 | Satyavolu et al. | Jun 2014 | A1 |
| 20140195398 | Rose et al. | Jul 2014 | A1 |
| 20140297392 | Moffitt | Oct 2014 | A1 |
| 20150170175 | Zhang et al. | Jun 2015 | A1 |
| 20150220951 | Kurapati et al. | Aug 2015 | A1 |
| 20150220961 | Jenkins et al. | Aug 2015 | A1 |
| 20150220999 | Thornton et al. | Aug 2015 | A1 |
| 20150348083 | Brill et al. | Dec 2015 | A1 |
| 20160086222 | Kurapati | Mar 2016 | A1 |
| 20160189213 | Gopalan et al. | Jun 2016 | A1 |
| 20170098234 | Carlson et al. | Apr 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 10055682 | May 2002 | DE |
| 2034712 | Mar 2009 | EP |
| 1020030080797 | Oct 2003 | KR |
| 10-2009-0003416 | Jan 2009 | KR |
| 10-2010-0052896 | May 2010 | KR |
| 1020120047461 | May 2012 | KR |
| 0241556 | May 2002 | WO |
| 2008035044 | Mar 2008 | WO |
| WO 2008035044 | Mar 2008 | WO |
| WO 2009001394 | Dec 2008 | WO |
| 2010085445 | Jul 2010 | WO |
| 2011058581 | May 2011 | WO |
| 2012044692 | Apr 2012 | WO |
| 2012044692 | Jun 2012 | WO |
| 2012044692 | Nov 2012 | WO |
| 2013181258 | Dec 2013 | WO |
| 2016025291 | Feb 2016 | WO |
| Entry |
|---|
| Written Opinion and Int'l Search Report for PCT/US11/53696, dated May 4, 2012 (10 pages). |
| CheckFree and Netonomy Sign Strategic Reseller Agreement PR Newswire (US) Dec. 15, 2004, 3 pages. |
| Int. Appl. PCT/US10/21371, Int. Search Report dated May 3, 2010, 2 pages. |
| Int. Appl. PCT/US10/21371, Written Opinion dated May 3, 2010, 5 pages. |
| OneSimCard, “Mobile Miles Reward Program,” Jan. 2007, published at <http://web.archive.org/web/2007101706928/http://www.onesimcard.com/?idmenu=22> 1 page. |
| WhiteFence “Purchase your Bundles and Save,” May 2008, 2 pages http://web.archive.org/web/20080505084851/www.whitefence.com/bundled-services.html. |
| BundleMyServices.“Bundle Your Internet, Phone and TV to Save.” Jul. 2008, 3 pages http://web.archive.org/web/20080711052327/http://www.bundlemyservices.com/. |
| U.S. Appl. No. 12/533,447, Non-Final Office Action dated Oct. 27, 2010, 7 pages. |
| U.S. Appl. No. 12/533,517, Non-Final Office Action dated Mar. 17, 2010, 3 pages. |
| U.S. Appl. No. 12/533,517, Final Office Action dated Oct. 13, 2010, 9 pages. |
| Balasubramanian, Dushyanth, “QoS in Cellular Networks”, http://www.cse.wustl.edu/-jain/cse574-06/ftp/cellular_qos.pdf, Washington University in Saint Louis, May 2006, 24 pages. |
| Chakrabarty, Gargi, “Rochester, N.Y.-Based Firm Lures Big Indiana Customers from Telecom Giants”, Knight Ridder Tribune Business News [Washington], Apr. 19, 2002, 2 pages. |
| city-data.com, “Best savings account rate?”, http://www.city-data.com/forum/personal-finance/533408-best-savings-account-rate.html (accessed online Apr. 12, 2012), Jan. 9, 2009, 6 pages. |
| Cotter et al, “The Limits of Reverse Auction Pricing Strategy and Priceline.Com”, Journal of Business and Entrepreneurship, suppl. Special, vol. 13, Oct. 2001, 5 pages. |
| Lieber, Ron, “Your Money, Where's It All Going? Find Out Online”, http://www.nytimes.com/2008/10/04/business/yourmoney/04money.html?_r=1&pagewanted=all, (accessed online Sep. 10, 2012), Oct. 3, 2008, 4 pages. |
| mint.com, “Mint Refreshing Money Management”, Mint Software, Inc., http://web.archive.org/web/20071029162033/http://www.mint.com/features.html., (accessed online Jun. 2, 2012), 2007, 2 pages. |
| mint.com, “MintLife Blog Track Spending Online and Compare”, Mint.com , http://www.mint.com/blog/updates/trackspending-online-compare-your-spending, (accessed online Sep. 10, 2012), Jan. 16, 2008, 2 pages. |
| mint.com, “Mint™ refreshing money management”, Mint.com , http://web.archive.org/web/20080701 042934/http://www.mint.com/features.html, (accessed online Sep. 10, 2012), Jun. 1, 2008, 3 pages. |
| money-rates.com, “Highest Rates and Yields on bank savings accounts updated daily”, http://web.archive.org/web/20071226132433/http:www.money-rats.com/savings.html (accessed online Apr. 12, 2012), Dec. 19, 2007, 3 pages. |
| International Application Serial No. PCT/US2007/018960, International Search Report and Written Opinion dated May 3, 2010, 11 pages. |
| Strupp, Joe, “Gifts that keep on giving . . . ad dollars”, Editor & Publisher, vol. 141, issue 8, http://search.proquest.com/printviewfile?accountid=14753 (accessed online Oct. 17, 2012), Aug. 2008, pp. 9-10 (4 pages online). |
| Vestal, Shawn, “It's never too late to trim dollars off your energy bill”, Powering Down, Spokesman Review [Spokane, Wash], Jan. 12, 2009, 3 pages. |
| “Answers to FAQs”, Verizon Wireless, http://support.vzw.com/faqs/Account%20Management/faq_billing.html, Feb. 11, 2008, 5 Pages. |
| “Approximate string matching”, **URL:https:jjen.wikipedia.org/w/index.php?title=Approximate string matching&oldid=491554584**, May 9, 2012, 4 Pages. |
| “Are you spending too much for wireless?”, http://www.myvalidas.com, Oct. 2008, 1 Page. |
| “Cellular Resources—Night and Weekend Minutes”, http://web.archive.org/web/20060319163017/http://www.myrateplan.com/wireless/knowledge/nightsandweekends.php, MyRatePian.com, Mar. 19, 2006, 2 Pages. |
| “Everything about Loyalty Marketing and Technology”, Jan. 2011 (Loyalty)., 10 Pages. |
| “Free Money Management, Manage Your Finances, Expense Management, Budget and Money Software”, Mint.com, http://web.archive.org/web/20080315110811/http://www.mint.com/features.html, Mar. 15, 2008, 2 Pages. |
| “Free Personal Finance Software, Money Management, Budget Planner and Tools, Online Financial Planning”, http://web.archive.org/web/20080425073230/http://www.mint.com/features.html, Mint.com, Apr. 25, 2008. |
| “G. VDSL: A universal frequency plan for VDSL: the quest for the holy grail?”, Internatonal Telecommunication Union, Geneva, CH, Aug. 6, 1999, 18 Pages. |
| “Lucene”, **URL:https:jjen.wikipedia.orgjwjindex.php?title=Time complexity&oldid=492506715**, May 6, 2012, 3 Pages. |
| “Macy's Launches Rewards Program—Star Rewards”, Jan. 20, 2005; p. 1, 1 Page. |
| “Personal Finance Software from Mint-Personal Finance Management and Financial Calculator Online”, Mint.com, http://web.archive.org/web/20080604065549/http://www.mint.com/personal-finance.html, Jun. 4, 2008, 1 Page. |
| Press Release; “Macy's Launches Star Rewards Loyalty Program”, Jan. 20, 2005; pp. 1-2, 2 Pages. |
| “Radix tree”, **URL:https:;;en.wikipedia.org/w/index.php?title=Radix tree&oldid=493867529**, May 22, 2012, 6 Pages. |
| “Time complexity”, XP055230138, Retrieved from the Internet: URL:https:jjen.wikipedia.orgjwjindex.php?title=Time complexity&oldid=492506715 [retrieved on Nov. 20, 2015] * the whole document *, May 14, 2012, 12 pages. |
| “www.flagstar.com, FinanceWorks (Progress Statement)”, https://www.flagstar.com/...1/bank:ing/online-banking-login/online-banking/jcr_content/tabs/tabitem_l/image.img.jpg/13 79434197099 .jpg, 1 Page. |
| 10733783.4, “European Application Serial No. 10733783.4, European Extended Search Report dated Oct. 15, 2014”, Billshrink Inc., 11 Pages. |
| 11829829.8, “European Application Serial No. 11829829.8, European Search Report dated Apr. 4, 2016”, Truaxis, Inc., 8 Pages. |
| 13797304.6, “European Application Serial No. 13797304.6, European Search Report dated Dec. 17, 2015”, Truaxis, Inc., 9 Pages. |
| AT&T Community Forums, “Do MMS pictures messages incur DATA charges?”, http://forums.att.com/t5/Data-Messaging-Features-Internet/Do-MMS-pictures-messages-incurr-DATA-charges/td-p/1856555, 2009, 7 pages. |
| Chakrabarty, Gargi , “Rochester, N.Y. Based Firm Lures Big Indiana Customers from Telecom Giants”, The Indianapolis Star (Indianapolis, IN), www.highbeam.com/doc/1G1-120488613.html, Apr. 19, 2002, 1 page. |
| Daniel, Domenech , “Geographical Information Resolution and its Application to the Question Answering Systems”, Universitat Polifecnica de Catalunya, 147 Pages. |
| Lai, Eric , “BillShrink exec responds to problems with its money-saving service”, Computer World blogs http://blogs.computerworld.com/billshrink_exec_responds_to_problems_with_itsmaney_saving_service, Nov. 27, 2008, 5 Pages. |
| mint.com, “Free Money Management, Manage Your Finances, Expense Management, Budget and Money Software—Mint.com”, http://web.archive.org/web/20080315110811/http://www.mint.com/features.html, Mar. 15, 2008, 2 pages. |
| mint.com, “Personal Finance Software from Mint-Personal Finance Management and Financial Calculator Online—Mint.com,”, http://web.archive.org/web/20080604065549/http://www.mint.com/personal-finance.html, Jun. 4, 2008, 2 pages. |
| PCT/US2011/053696, “International Application Serial No. PCT/US2011/053696, International Preliminary Report on Patentability dated Apr. 11, 2013”, Truaxis, Inc. et al, 7 pages. |
| PCT/US2013/043125, “International Application Serial No. PCT/US2013/043125, International Search Report and Written Opinion dated Oct. 28, 2013”, Truaxis, Inc., 15 pages. |
| PCT/US2015/044000, “International Application Serial No. PCT/US2015/044000, International Search Report and Written Opinion dated Nov. 19, 2015”, Truaxis, Inc., 11 Pages. |
| Strupp, Joe , “Gifts that keep on giving . . . ad dollars”, Editor & Publisher 141. Aug. 8, 2008, 2 pages. |
| European Application Serial No. 11829829.8, European Search Report dated Apr. 4, 2016. |
| United States Patent Office Action for U.S. Appl. No. 14/631,091 dated Jul. 2, 2018 (15 pages). |
| United States Patent Office Action for U.S. Appl. No. 14/637,150 dated Jun. 13, 2018 (25 pages). |
| Canadian Patent Office Action for Application No. 2,812,945 dated Feb. 12, 2018 (4 pages). |
| United States Patent Office Action for U.S. Appl. No. 14/955,862 dated May 3, 2018 (11 pages). |
| Office Action corresponding to Canadian Patent Application No. 2812945, dated Mar. 30, 2017, 6 pgs. |
| Office Action corresponding to Canadian Patent Application No. 2956453, dated Nov. 9, 2017, 8 pgs. |
| Office Action corresponding to U.S. Appl. No. 14/789,700, dated Nov. 29, 2017, 18 pgs. |
| Office Action corresponding to U.S. Appl. No. 14/637,150, dated Oct. 6, 2017, 16 pgs. |
| U.S. Appl. No. 12/501,572, filed Jul. 13, 2009, 20100185489, Jul. 22, 2010. |
| U.S. Appl. No. 12/533,120, filed Jul. 31, 2009, 20100183132, Jul. 22, 2010. |
| U.S. Appl. No. 12/533,162, filed Jul. 31, 2009, 20100185452, Jul. 22, 2010. |
| U.S. Appl. No. 12/533,303, filed Jul. 31, 2009, 20100185453, Jul. 22, 2010. |
| U.S. Appl. No. 12/533,386, filed Jul. 31, 2009, 20100185454, Jul. 22, 2010. |
| U.S. Appl. No. 12/533,447, filed Jul. 31, 2009, 20100185534, Jul. 22, 2010. |
| U.S. Appl. No. 12/533,517, filed Jul. 31, 2009, 20100185490, Jul. 22, 2010. |
| U.S. Appl. No. 12/533,618, filed Jul. 31, 2009, 20100185491, Jul. 22, 2010. |
| U.S. Appl. No. 12/533,678, filed Jul. 31, 2009, 20100185492, Jul. 22, 2010. |
| U.S. Appl. No. 13/082,591, filed Apr. 8, 2011, 20110246280, Oct. 6, 2011, U.S. Pat. No. 8,600,857, Dec. 3, 2013. |
| U.S. Appl. No. 13/082,606, filed Apr. 8, 2011, 20110246281, Oct. 6, 2011. |
| U.S. Appl. No. 13/082,622, filed Apr. 8, 2011, 20110246268, Oct. 6, 2011. |
| U.S. Appl. No. 13/082,634, filed Apr. 8, 2011, 20110246346, Oct. 6, 2011. |
| U.S. Appl. No. 13/082,644, filed Apr. 8, 2011, 20110246292, Oct. 6, 2011. |
| U.S. Appl. No. 13/082,655, filed Apr. 8, 2011, 20110258028, Oct. 20, 2011. |
| U.S. Appl. No. 13/082,751, filed Apr. 8, 2011, 20110251883, Oct. 13, 2011. |
| U.S. Appl. No. 13/082,762, filed Apr. 8, 2011, 20110251934, Oct. 13, 2011. |
| U.S. Appl. No. 13/082,784, filed Apr. 8, 2011, 20110251891, Oct. 13, 2011. |
| U.S. Appl. No. 13/082,801, filed Apr. 8, 2011, 20110246299, Oct. 6, 2011. |
| U.S. Appl. No. 13/180,511, filed Jul. 11, 2011, 20120004975, Jan. 5, 2012. |
| U.S. Appl. No. 13/180,513, filed Jul. 11, 2011, 20120004964, Jan. 5, 2012. |
| U.S. Appl. No. 13/180,519, filed Jul. 11, 2011, 20120004965, Jan. 5, 2012. |
| U.S. Appl. No. 13/180,521, filed Jul. 11, 2011, 20120004966, Jan. 5, 2012. |
| U.S. Appl. No. 13/180,524, filed Jul. 11, 2011, 20120004967, Jan. 5, 2012. |
| U.S. Appl. No. 13/180,526, filed Jul. 11, 2011, 20120004968, Jan. 5, 2012, U.S. Pat. No. 8,566,197, Oct. 22, 2013. |
| U.S. Appl. No. 13/180,528, filed Jul. 11, 2011, 20120004969, Jan. 5, 2012. |
| U.S. Appl. No. 13/180,530, filed Jul. 11, 2011, 20120004970, Jan. 5, 2012. |
| U.S. Appl. No. 13/180,531, filed Jul. 11, 2011, 20120010936, Jan. 12, 2012. |
| U.S. Appl. No. 13/180,533, filed Jul. 11, 2011, 20120010932, Jan. 12, 2012. |
| U.S. Appl. No. 13/180,535, filed Jul. 11, 2011, 20120010933, Jan. 12, 2012. |
| U.S. Appl. No. 13/247,657, filed Sep. 28, 2011, 20120053987, Mar. 1, 2012. |
| U.S. Appl. No. 13/300,090, filed Nov. 28, 2011, 20120066046, Mar. 15, 2012, U.S. Pat. No. 8,650,105, Feb. 11, 2014. |
| U.S. Appl. No. 13/300,121, filed Nov. 28, 2011, 20120066050, Mar. 15, 2012. |
| U.S. Appl. No. 13/904,529, filed May 29, 2013, 20130325680, Dec. 5, 2013. |
| U.S. Appl. No. 13/904,548, filed May 29, 2013, 20130325608, Dec. 5, 2013. |
| U.S. Appl. No. 13/904,558, filed May 29, 2013, 20130325667, Dec. 5, 2013. |
| U.S. Appl. No. 13/904,573, filed May 29, 2013, 20140172560, Jun. 19, 2014. |
| U.S. Appl. No. 13/904,593, filed May 29, 2013, 20130325681, Dec. 5, 2013. |
| U.S. Appl. No. 13/904,624, filed May 29, 2013, 20130325548, Dec. 5, 2013. |
| U.S. Appl. No. 13/904,650, filed May 29, 2013, 20130325587, Dec. 5, 2013. |
| U.S. Appl. No. 14/058,654, filed Oct. 21, 2013, 20140180783, Jun. 26, 2014. |
| U.S. Appl. No. 14/080,135, filed Nov. 14, 2013, 20140095364, Apr. 3, 2014. |
| U.S. Appl. No. 14/166,525, filed Jan. 28, 2014, 20140143109, May 22, 2014. |
| U.S. Appl. No. 14/631,091, filed Feb. 25, 2015, 20150170175, Jun. 18, 2015. |
| U.S. Appl. No. 14/631,130, filed Feb. 25, 2015, 20150220951, Aug. 6, 2015. |
| U.S. Appl. No. 14/637,150, filed Mar. 3, 2015, 20150220999, Aug. 6, 2015. |
| U.S. Appl. No. 14/789,700, filed Jul. 1, 2015, 20150348083, Dec. 3, 2015. |
| U.S. Appl. No. 14/955,862, filed Dec. 1, 2015, 20160086222, Mar. 24, 2016. |
| Office Action corresponding to Australian Patent Application No. 2013267530, dated Jan. 19, 2018, 3 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,624, dated Jan. 16, 2018, 26 pgs. |
| Office Action corresponding to U.S. Appl. No. 14/631,130, dated Jan. 22, 2018, 53 pgs. |
| United States Patent Office Action for U.S. Appl. No. 14/631,091 dated Apr. 16, 2019 (20 pages). |
| United States Patent Office Action for U.S. Appl. No. 14/631,130 dated Mar. 22, 2019 (27 pages). |
| Canadian Patent Office Action for Application No. 2,812,945 dated Jan. 4, 2019 (5 pages). |
| United States Patent Office Action for U.S. Appl. No. 13/904,624 dated Mar. 21, 2019 (21 pages). |
| United States Patent Office Notice of Allowance for U.S. Appl. No. 13/904,624 dated Aug. 14, 2019 (7 pages). |
| United States Patent Office Action for U.S. Appl. No. 14/631,130 dated Sep. 19, 2019 (28 pages). |
| Advisory Action corresponding to U.S. Appl. No. 12/501,572, dated Aug. 13, 2015, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/501,572, dated Nov. 4, 2016, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/501,572, dated Sep. 12, 2012, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,120, dated Apr. 12, 2013, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,162, dated Apr. 24, 2013, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,162, dated Mar. 22, 2012, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,303, dated Jul. 16, 2015, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,303, dated Mar. 13, 2014, pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,303, dated Oct. 1, 2012, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,386, dated Apr. 24, 2013, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,386, dated Aug. 10, 2011, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,447, dated Aug. 23, 2011, 2 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,447, dated Aug. 28, 2013, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,447, dated Aug. 4, 2015, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,517, dated Mar. 10, 2011, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,517, dated Mar. 12, 2014, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,517, dated Oct. 3, 2012, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,618, dated Sep. 11, 2012, 5 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,678, dated Apr. 18, 2013, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,678, dated Aug. 23, 2011, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 12/533,678, dated Mar. 30, 2015, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/082,606, dated Jun. 14, 2013, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/082,622, dated May 28, 2013, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/082,644, dated May 9, 2013, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/082,655, dated Jul. 31, 2013, 4 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/082,751, dated Dec. 18, 2012, 2 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/082,762, dated Aug. 30, 2012, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/082,784, dated Mar. 19, 2013, 19 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/180,511, dated Sep. 11, 2013, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/180,513, dated Feb. 21, 2014, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/180,521, dated Feb. 6, 2014, 2 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/180,524, dated Jul. 22, 2014, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/180,524, dated Nov. 19, 2013, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/180,526, dated Jul. 15, 2013, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/180,528, dated Jun. 23, 2015, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/180,528, dated Nov. 22, 2013, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/180,530, dated Jun. 19, 2013, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/180,531, dated Apr. 10, 2013, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/180,531, dated May 3, 2013, 5 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/180,535, dated Jun. 19, 2013, 6 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/247,657, dated Mar. 11, 2014, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/247,657, dated Mar. 28, 2016, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/300,090, dated Sep. 26, 2012, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/300,121, dated Sep. 21, 2012, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 13/904,593, dated Aug. 11, 2016, 4 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 14/058,654, dated Nov. 16, 2016, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 14/080,135, dated Jul. 17, 2015, 2 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 14/080,135, dated Oct. 27, 2016, 3 pgs. |
| Advisory Action corresponding to U.S. Appl. No. 14/166,525, dated Jul. 17, 2015, 2 pgs. |
| Examiner's Answer to Appeal Brief corresponding to U.S. Appl. No. 12/533,447, mailed Jun. 23, 2016, 11 pgs. |
| Examiner's Answer to Appeal Brief corresponding to U.S. Appl. No. 12/533,618, mailed Dec. 13, 2012, 23 pgs. |
| Examiner's Answer to Appeal Brief corresponding to U.S. Appl. No. 13/082,751, mailed Jun. 6, 2013, 5 pgs. |
| Examiner's Answer to Appeal Brief corresponding to U.S. Appl. No. 13/082,762, mailed Dec. 20, 2012, 11 pgs. |
| Examiner's Answer to Appeal Brief corresponding to U.S. Appl. No. 13/180,511, mailed Feb. 7, 2014, 21 pgs. |
| Examiner's Answer to Appeal Brief corresponding to U.S. Appl. No. 13/180,531, mailed Dec. 20, 2013, 10 pgs. |
| Examiner's Answer to Appeal Brief corresponding to U.S. Appl. No. 13/247,657, mailed Dec. 15, 2016, 44 pgs. |
| Examiner's Answer to Appeal Brief corresponding to U.S. Appl. No. 13/904,624, mailed Jul. 24, 2017, 12 pgs. |
| Examiner's Answer to Appeal Brief corresponding to U.S. Appl. No. 14/058,654, mailed Jun. 6, 2017, 9 pgs. |
| Examiner's Answer to Appeal Brief corresponding to U.S. Appl. No. 14/166,525, mailed Apr. 21, 2017, 9 pgs. |
| International Search Report with Written Opinion corresponding to International Patent Application No. PCT/US2011/053696, dated May 4, 2012, 8 pgs. |
| International Search Report with Written Opinion corresponding to International Patent Application No. PCT/US2015/049999, dated Dec. 14, 2015, 14 pgs. |
| Notice of Allowance corresponding to U.S. Appl. No. 13/082,591, dated Feb. 20, 2013, 11 pgs. |
| Notice of Allowance corresponding to U.S. Appl. No. 13/180,526, dated Aug. 26, 2013, 10 pgs. |
| Notice of Allowance corresponding to U.S. Appl. No. 13/300,090, dated Oct. 4, 2013, 13 pgs. |
| Office Action corresponding to Australian Patent Application No. 2011308914, dated Apr. 22, 2016, 7 pgs. |
| Office Action corresponding to Australian Patent Application No. 2011308914, dated Jul. 16, 2015, 6 pgs. |
| Office Action corresponding to Australian Patent Application No. 2011308914, dated Jul. 31, 2014, 5 pgs. |
| Office Action corresponding to Australian Patent Application No. 2011308914, dated Mar. 27, 2015, 6 pgs. |
| Office Action corresponding to Australian Patent Application No. 2016202766, dated Jun. 8, 207, 4 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/501,572, dated Aug. 29, 2016, 11 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/501,572, dated Dec. 11, 2014, 10 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/501,572, dated Feb. 25, 2016, 11 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/501,572, dated Jul. 5, 2012, 28 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/501,572, dated May 29, 2015, 10 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/501,572, dated May 8, 2014, 25 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/501,572, dated Oct. 3, 2011, 26 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,120, dated Aug. 1, 2014, 35 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,120, dated Jan. 4, 2013, 31 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,120, dated Mar. 9, 2012, 10 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,162, dated Apr. 25, 2014, 24 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,162, dated Jan. 7, 2013, 22 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,162, dated Jul. 13, 2015, 8 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,162, dated Jun. 5, 2012, 21 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,162, dated Mar. 22, 2011, 8 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,162, dated Nov. 28, 2014, 10 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,162, dated Oct. 5, 2011, 17 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,303, dated Jan. 15, 2014, 31 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,303, dated Jun. 22, 2012, 26 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,303, dated Jun. 27, 2013, 38 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,303, dated May 7, 2015, 17 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,303, dated Nov. 18, 2014, 26 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,303, dated Oct. 14, 2011, 9 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,386, dated Aug. 14, 2014, 25 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,386, dated Dec. 22, 2010, 7 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,386, dated Jan. 17, 2013, 23 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,386, dated May 25, 2012, 22 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,386, dated May 27, 2011, 17 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,447, dated Apr. 13, 2015, 10 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,447, dated Apr. 24, 2014, 15 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,447, dated Mar. 20, 2012, 13 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,447, dated Mar. 29, 2013, 15 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,447, dated May 6, 2011, 10 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,447, dated Nov. 28, 2014, 8 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,517, dated Jan. 27, 2014, 36 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,517, dated Jul. 30, 2014, 41 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,517, dated Jun. 20, 2013, 29 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,517, dated Jun. 22, 2012, 32 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,517, dated Sep. 22, 2011, 11 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,618, dated Apr. 26, 2012, 31 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,618, dated Nov. 3, 2011, 15 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,678, dated Dec. 20, 2010, 9 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,678, dated Feb. 4, 2013, 28 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,678, dated Jun. 11, 2012, 26 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,678, dated Jun. 25, 2015, 10 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,678, dated Mar. 1, 2016, 10 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,678, dated Mar. 28, 2014, 33 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,678, dated May 26, 2011, 18 pgs. |
| Office Action corresponding to U.S. Appl. No. 12/533,678, dated Nov. 18, 2014, 9 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,591, dated Jan. 2, 2013, 10 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,591, dated Mar. 1, 2012, 6 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,591, dated Oct. 23, 2012, 18 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,606, dated Dec. 18, 2015, 30 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,606, dated Mar. 1, 2013, 17 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,606, dated May 16, 2014, 22 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,606, dated May 7, 2015, 27 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,606, dated Oct. 23, 2014, 17 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,606, dated Sep. 17, 2012, 14 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,622, dated Feb. 15, 2013, 14 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,622, dated May 30, 3014, 19 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,622, dated May 8, 2015, 29 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,622, dated Oct. 23, 2014, 17 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,622, dated Sep. 19, 2012, 10 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,634, dated Jun. 25, 2015, 29 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,634, dated Mar. 1, 2013, 11 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,634, dated Mar. 1, 2016, 35 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,634, dated May 15, 2014, 14 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,634, dated Oct. 23, 2014, 18 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,634, dated Sep. 26, 2012, 13 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,644, dated Feb. 27, 2014, 17 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,644, dated Jan. 17, 2013, 17 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,644, dated Jun. 11, 2015, 19 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,644, dated Jun. 19, 2012, 14 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,644, dated Sep. 12, 2014, 17 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,655, dated Dec. 21, 2012, 26 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,655, dated Jun. 3, 3013, 35 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,655, dated Jun. 4, 2012, 18 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,751, dated Jul. 9, 2012, 9 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,751, dated Nov. 2, 2012, 9 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,762, dated Aug. 26, 2011, 6 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,762, dated Mar. 22, 2012, 9 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,784, dated Dec. 12, 2012, 46 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,784, dated Jan. 7, 2016, 23 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,784, dated Jun. 1, 2012, 22 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,784, dated Sep. 12, 2014, 48 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,801, dated Feb. 9, 2015, 18 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/082,801, dated Jul. 8, 2015, 19 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,511, dated Aug. 10, 2016, 12 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,511, dated Jan. 31, 2017, 16 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,511, dated May 29, 2013, 16 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,511, dated Nov. 29, 2012, 14 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,513, dated Dec. 2, 2013, 25 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,513, dated Dec. 5, 2014, 29 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,513, dated Feb. 19, 2016, 36 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,513, dated Mar. 1, 2013, 24 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,519, dated Dec. 5, 2013, 13 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,519, dated Jul. 21, 2015, 25 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,519, dated May 15, 2014, 17 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,519, dated May 24, 2013, 13 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,519, dated Sep. 18, 2014, 14 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,521, dated Dec. 10, 2014, 24 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,521, dated Dec. 24, 2013, 22 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,521, dated Mar. 29, 2013, 20 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,521, dated Mar. 30, 2016, 30 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,524, dated Apr. 8, 2014, 34 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,524, dated Dec. 26, 2012, 23 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,524, dated Feb. 13, 2015, 37 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,524, dated Jun. 12, 2012, 27 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,524, dated Jun. 30, 2015, 40 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,524, dated Jun. 5, 2014, 31 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,524, dated Sep. 20, 2013, 30 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,526, dated Mar. 11, 2013, 23 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,526, dated Nov. 7, 2012, 19 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,528, dated Apr. 9, 2014, 29 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,528, dated Dec. 28, 2012, 23 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,528, dated Mar. 11, 2015, 29 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,528, dated May 24, 2012, 24 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,528, dated Sep. 20, 2013, 23 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,528, dated Sep. 29, 2014, 28 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,530, dated Aug. 21, 2014, 32 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,530, dated Mar. 11, 2013, 18 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,530, dated May 5, 2015, 33 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,530, dated Nov. 8, 2012, 18 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,531, dated Feb. 17, 2012, 13 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,531, dated Jan. 22, 2013, 15 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,535, dated Apr. 22, 2016, 14 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,535, dated Aug. 21, 2014, 31 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,535, dated Mar. 14, 2013, 20 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,535, dated May 5, 2015, 34 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,535, dated Nov. 23, 2012, 18 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/180,535, dated Nov. 7, 2016, 13 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/247,657, dated Apr. 26, 2013, 31 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/247,657, dated Aug. 1, 2013, 29 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/247,657, dated Jan. 13, 2016, 44 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/247,657, dated Jan. 6, 2014, 39 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/247,657, dated Jun. 15, 2015, 40 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/247,657, dated Nov. 13, 2014, 39 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/247,657, dated Sep. 14, 2012, 26 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/300,090, dated Apr. 11, 2012, 14 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/300,090, dated Aug. 6, 2012, 9 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/300,121, dated Apr. 16, 2012, 13 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/300,121, dated Dec. 2, 2015, 42 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/300,121, dated Feb. 15, 2012, 12 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/300,121, dated Jul. 20, 2016, 28 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/300,121, dated Jul. 27, 2012, 22 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/300,121, dated May 1, 2014, 32 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/300,121, dated Oct. 23, 2014, 51 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,529, dated Feb. 2, 2016, 13 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,529, dated May 22, 2015, 13 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,548, dated Apr. 10, 2015, 16 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,548, dated Jul. 24, 2015, 20 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,548, dated Mar. 9, 2016, 35 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,558, dated Apr. 3, 2015, 12 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,558, dated Mar. 31, 2016, 31 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,558, dated Nov. 9, 2015, 21 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,558, dated Oct. 28, 2016, 45 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,573, dated Feb. 23, 2015, 20 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,573, dated Nov. 6, 2015, 27 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,593, dated Jul. 1, 2015, 20 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,593, dated Mar. 24, 2016, 41 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,624, dated Jan. 13, 2017, 16 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,624, dated Jun. 3, 2016, 16 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,624, dated May 22, 2015, 11 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,650, dated Jul. 15, 2015, 25 pgs. |
| Office Action corresponding to U.S. Appl. No. 13/904,650, dated Mar. 9, 2016, 32 pgs. |
| Office Action corresponding to U.S. Appl. No. 14/058,654, dated Aug. 25, 2016, 10 pgs. |
| Office Action corresponding to U.S. Appl. No. 14/058,654, dated Dec. 14, 2015, 9 pgs. |
| Office Action corresponding to U.S. Appl. No. 14/080,135, dated Apr. 2, 2015, 12 pgs. |
| Office Action corresponding to U.S. Appl. No. 14/080,135, dated Apr. 27, 2016, 8 pgs. |
| Office Action corresponding to U.S. Appl. No. 14/080,135, dated Aug. 18, 2016, 9 pgs. |
| Office Action corresponding to U.S. Appl. No. 14/080,135, dated Sep. 24, 2014, 8 pgs. |
| Office Action corresponding to U.S. Appl. No. 14/166,525, dated Apr. 27, 2016, 6 pgs. |
| Office Action corresponding to U.S. Appl. No. 14/166,525, dated Apr. 3, 2015, 11 pgs. |
| Office Action corresponding to U.S. Appl. No. 14/166,525, dated Aug. 18, 2016, 8 pgs. |
| Office Action corresponding to U.S. Appl. No. 14/166,525, dated Nov. 23, 2016, 8 pgs. |
| Office Action corresponding to U.S. Appl. No. 14/166,525, dated Nov. 6, 2014, 8 pgs. |
| Office Action corresponding to U.S. Appl. No. 14/631,130, dated Feb. 10, 2017, 37 pgs. |
| Office Action corresponding to U.S. Appl. No. 14/631,130, dated Jul. 6, 2017, 41 pgs. |
| Patent Board Decision regarding the Appeal Proceedings corresponding to U.S. Appl. No. 12/533,618, mailed May 22, 2015, 8 pgs. |
| Patent Board Decision regarding the Appeal Proceedings corresponding to U.S. Appl. No. 13/082,751, mailed May 26, 2016, 7 pgs. |
| Patent Board Decision regarding the Appeal Proceedings corresponding to U.S. Appl. No. 13/082,762, mailed May 21, 2015, 12 pgs. |
| Patent Board Decision regarding the Appeal Proceedings corresponding to U.S. Appl. No. 13/180,511, mailed Jul. 12, 2016, 7 pgs. |
| Patent Board Decision regarding the Appeal Proceedings corresponding to U.S. Appl. No. 13/180,531, mailed Aug. 5, 2016, 9 pgs. |
| Australian Patent Office Examination Report No. 2 for Application No. 2013267530 dated Oct. 23, 2018 (3 pages). |
| European Patent Office Action for Application No. 11829829.8 dated Nov. 23, 2018 (10 pages). |
| United States Patent Office Action for U.S. Appl. No. 14/955,862 dated Nov. 5, 2018 (8 pages). |
| Canadian Patent Office Action for Application No. 2,956,453 dated Jul. 23, 2018 (8 pages). |
| Canadian Patent Office Action for Application No. 2,874,981 dated Aug. 16, 2018 (3 pages). |
| United States Patent Office Action for U.S. Appl. No. 13/904,624 dated Sep. 13, 2018 (29 pages). |
| United States Patent Office Action for U.S. Appl. No. 14/631,130 dated Sep. 19, 2018 (26 pages). |
| United States Patent Office Action for U.S. Appl. No. 14/789,700 dated Sep. 6, 2018 (29 pages). |
| Canadian Patent Office Action for Application No. 2,874,981 dated Sep. 30, 2019 (4 pages). |
| Number | Date | Country | |
|---|---|---|---|
| 20120010932 A1 | Jan 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61427138 | Dec 2010 | US | |
| 61388680 | Oct 2010 | US | |
| 61146120 | Jan 2009 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13082591 | Apr 2011 | US |
| Child | 13180533 | US | |
| Parent | 12501572 | Jul 2009 | US |
| Child | 13082591 | US |
