Patent Grant
10417635
Consumers today use many types of payment cards and other payment mechanisms to make purchases, for example, using a credit card or automated teller machine (ATM) card to buy a coffee at a coffee shop. In a typical transaction, a consumer takes a payment card out of her wallet or purse and the payment card is slid through a card reader by the consumer or a sales clerk. In the case of a purchase using a credit card, the consumer may have to provide a signature. The consumer typically provides a signature that is captured electronically, such as by signing on a touch sensitive pad or screen provided by the seller, the touch sensitive pad or screen capturing the signature electronically. In the case of a purchase using an ATM card, the consumer may need to provide her personal identification number (PIN) for her card. The consumer typically enters her PIN using a keypad provided by the seller.
Some consumers are concerned with certain aspects of such purchase transactions. For example, a consumer may be concerned with touching items previously touched by other people, due to their concern or, in some cases, even fear of catching germs left on the items by other people. When providing her signature for a credit card transaction, a consumer may be concerned with germs left on the stylus or touch-sensitive pad or screen by a previous consumer when the previous consumer provides his signature.
When providing her PIN number, a consumer may be concerned with catching germs left on the keypad or touch screen when a previous consumer uses the keypad or touch screen to provide his PIN.
Consumers may also be concerned with others obtaining information the consumer prefers to keep private during the transaction. For example, a consumer may be concerned about using the seller's keypad to enter the consumer's PIN, as the consumer may feel that she cannot adequately hide from others the PIN that she enters using that keypad.
Embodiments of the present invention will be described and explained through the use of the accompanying drawings in which:
The drawings are not necessarily drawn to scale. For example, the dimensions of some of the elements in the figures may be expanded or reduced to help improve the understanding of the embodiments of the present invention. Similarly, some components and/or operations may be separated into different blocks or combined into a single block for the purposes of discussion of some of the embodiments of the present invention. Moreover, while the invention is amenable to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and are described in detail below. The intention, however, is not to limit the invention to the particular embodiments described. On the contrary, the invention is intended to cover all modifications, equivalents, and alternatives falling within the scope of the invention as defined by the appended claims.
This application discloses technology related to processing a purchase transaction wherein a consumer can use a mobile device related to the purchase, for example, to authorize the purchase transaction, to review items associated with the purchase transaction, or to select a payment account to use for a payment. As one example, a consumer can pay for a purchase using a credit card, automated teller machine (ATM) card, or proxy card, and the card can be swiped through a card reader that is part of the seller's point of sale system, a common example of a point of sale system being sales systems typically used by businesses like Walmart® and Target®. The term “swipe” here refers to any manner of triggering a physical card reader to read a physical card, such as passing a card through a magnetic stripe reader, smartcard reader, optical code reader, radio frequency identification (RFID) reader, etc. The term “sale”, as in point-of-sale (POS) or sales system, refers to any type of payment-oriented transaction, including a lease or rental for example, and is not limited to an actual purchase. After a successful swipe, the process of authorizing the transaction begins. A consumer can use, for example, a smartphone instead of the seller's keypad or signature pad to electronically capture a signature or personal identification number (PIN) as part of the consumer's authorization of the purchase transaction. A consumer can use a mobile device, for example, to review line items of a purchase transaction. At a business where tips are appropriate, such as a restaurant, a consumer can, for example, use a mobile device such as a smartphone to add a tip amount to the purchase transaction. In an embodiment, a proxy card is a payment card that is associated with multiple electronic accounts via an association maintained at a server. When the consumer uses a proxy card to pay for the purchase, the consumer can use a mobile device to select an electronic account to use to pay for the purchase.
Some consumers are concerned with several aspects of making a purchase using a payment card such as a credit card or an ATM card. For example, when providing a signature for a credit card transaction, some consumers are concerned about catching germs left on the stylus or the touch-sensitive pad or screen by a previous consumer when the previous consumer provides a signature. Such consumers would appreciate being able to provide a signature without having to worry about catching germs from others. Some consumers are similarly concerned about catching germs left on the seller's keypad used by other consumer's when entering their PINs. Such consumers would similarly appreciate being able to provide their PIN without having to worry about catching germs from others. Further, some customers are concerned with security, for example, concerned that someone may see their PIN when they enter it using the seller's keypad.
As discussed above, this application discloses technology related to processing a purchase transaction wherein a consumer can use a mobile device related to the purchase, for example, to authorize the purchase transaction, to review items associated with the purchase transaction, or to select a payment account to use for a payment. A consumer can use a mobile device, such as a smartphone or tablet, to electronically capture the consumer's signature or PIN. This enables the consumer to avoid having to touch the seller's equipment. For example, the consumer does not have to touch the seller's stylus or touch-sensitive pad or screen to provide a signature, nor does the consumer have to touch the seller's keypad to enter her PIN. Further, the consumer can use her mobile device for other parts of the purchase transaction. For example, a bill for a meal at a restaurant can be displayed on the mobile device of a consumer, and the consumer can enter the amount she desires to leave as a tip using her mobile device with this amount being added to her bill. As another example, the bill for the meal can also be displayed at the line item level, and the consumer can check each line item of the bill to ensure that the bill is correct before using her mobile device to authorize the purchase transaction, for example, by providing her signature or PIN using her mobile device. As another example, the consumer can pay for the meal using a proxy card. The card is swiped through a card reader coupled to a point-of-sale (POS) system, and a listing of the payment account associated with the proxy card appears on the consumer's mobile device. The consumer uses the mobile device to select a payment card to use to pay for the meal.
Further, using a mobile device as part of authorizing a purchase transaction can increase the security of the transaction. For example, to use a mobile device as part of a purchase transaction authorization, the mobile device may need to be associated with a payment card such as a credit card. A transaction that involves both a credit card and a mobile phone, both of which are associated with a consumer, can be more secure than a purchase transaction involving only one item, such as only the credit card or only the mobile device.
Some restaurant owners may also appreciate certain aspects of the disclosed technology. For example, the process of collecting payment for a meal can be streamlined. A waiter can take a consumer's order using a restaurant mobile device, for example an iPad©, and can also read the consumer's payment card using, for example, a card reader coupled to the iPad©. The bill for the meal can be automatically generated and transmitted to the consumer's mobile device where the bill for the meal can be displayed on the screen. The consumer, at her leisure and even while at her table, can use her mobile device to review the bill at the line item level, can use her mobile device to add a tip, can use her mobile device to provide her signature or PIN number, and can conclude the payment transaction without any need to walk to a station where a cashier is working at a sales register. The consumer can further obtain a copy of the purchase transaction receipt on her mobile device.
Walking through a simple example may be helpful in understanding the disclosed technology. A consumer can enter a store, such as Target® or Walmart®, and can select a number of items to purchase. She can take the items to a sales register, where she can provide a payment card such as a credit card, an ATM card, or a proxy card to a cashier. After ringing up the consumer's items, the cashier can take the consumer's payment card and can swipe the card through a card reader coupled to the sales register. The sales register can transmit the transaction information, such as the amount of the purchase, to a financial system, an example of a financial system being the system used by Target® or Walmart® to process credit card and ATM card purchase transactions. The sales register can further transmit the payment card information read from the consumer's payment card to the financial system. The financial system can transmit this purchase information and payment card information to a payment processing computer system. In some embodiments, the sales register can transmit the transaction information to the payment processing computer system, which can transmit the purchase information and the payment card information to a financial system.
The payment processing computer system can use the payment card information to determine a mobile device, such as a smartphone associated with the payment card. The payment processing computer system can transmit information to be displayed on the consumer's mobile device, such as the amount of the purchase transaction, line items of the purchase transaction, or a listing of payment accounts associated with a proxy card. The consumer can review the purchase transaction and determine whether to authorize the transaction. When the payment card is a proxy card, authorizing the transaction can include selecting a payment account associated with the proxy card to use for the payment. As part of the consumer authorizing the purchase transaction, the payment processing computer system can transmit a request to authorize the purchase transaction to the consumer's mobile device, where the request can be displayed. The consumer can use her mobile device review the purchase transaction and to electronically capture her signature or PIN to satisfy the authorization request. The consumer's mobile device can transmit the consumer's signature or ATM number to the payment processing computer system to indicate that the consumer authorizes the purchase transaction.
After receiving the customer's transaction authorization from the consumer's mobile device, the payment processing computer system can transmit a message to the financial system indicating the customer's authorization of the transaction. The financial system, after authorizing the purchase transaction, can transmit an authorization for the purchase transaction to the seller's sales register, thereby successfully completing the purchase transaction. The financial system authorization can indicate that the payment account being used to initiate the payment has access to adequate funds for the payment. Once the purchase transaction is successfully completed, the consumer is free to leave the store with the items that are part of the purchase transaction.
Brief definitions of terms, abbreviations, and phrases used throughout this application are given below.
The terms “connected” or “coupled” and related terms are used in an operational sense and are not necessarily limited to a direct physical connection or coupling. Thus, for example, two devices may be coupled directly, or via one or more intermediary media or devices. As another example, devices may be coupled in such a way that information can be passed there between, while not sharing any physical connection with one another. Based on the disclosure provided herein, one of ordinary skill in the art will appreciate a variety of ways in which connection or coupling exists in accordance with the aforementioned definition.
The phrases “in some embodiments,” “according to various embodiments,” “in the embodiments shown,” “in one embodiment,” “in other embodiments,” “various embodiments,” “some embodiments,” and the like generally mean the particular feature, structure, or characteristic following the phrase is included in at least one embodiment of the present invention, and may be included in more than one embodiment of the present invention. In addition, such phrases do not necessarily refer to the same embodiments or to different embodiments.
If the specification states a component or feature “may”, “can”, “could”, or “might” be included or have a characteristic, that particular component or feature is not required to be included or have the characteristic. The terms “purchase transaction” and “transaction” are used interchangeably in this document and both have the same meaning.
The term “module” refers broadly to software, hardware, or firmware (or any combination thereof) components. Modules are typically functional components that can generate useful data or other output using specified input(s). A module may or may not be self-contained. An application program (also called an “application”) may include one or more modules, or a module can include one or more application programs.
General Description
After the cashier finishes ringing up consumer 105's items and determines the total bill, and consumer 105 uses payment card 140, which can be for example a credit card, an automated teller machine (ATM) card, or a proxy card, to pay for the purchase. Payment card 140 is swiped through card reader 155, which reads the payment card information from the magnetic stripe of payment card 140. The payment card information can include, for example, identity information of the payment card, or meta data. Card reader 150 transmits the payment card information to the sales register (i.e., sales device 110), card reader 155 being coupled to sales device 110. The sales register, which can be for example a point of sale (POS) system, initiates a transaction authorization. The transaction authorization can be to ensure that the credit or bank account associated with payment card 140 has access to adequate funds to pay the total bill.
The sales register transmits the transaction information, such as the total amount of the purchase transaction, and the payment card information to financial system 160A to have the purchase transaction authorized. Financial system 160A, after determining that payment card 140 is associated with computer system 150 based on, for example, the payment card identity information or meta data, transmits the transaction information and the payment card information to computer system 150. The meta data can include, for example, an internet protocol (IP) address of computer system 150, or a phone number associated with computer system 150, or some other data or commands that indicate to the financial system to send the transaction information and the payment card information to computer system 150. Computer system 150, having access to a database that associates the payment card information with consumer 105's smartphone (i.e., mobile device 165), transmits a message that causes the transaction information to be displayed on consumer 105's smartphone. Consumer 105 can use the smartphone (i.e., mobile device 165) to review the transaction information, for example consumer 105 can make sure that the total amount is correct. When consumer 105 makes a purchase at a business, such as a restaurant, where tips are accepted, the transaction information can include a display enabling consumer 105 to enter or select a tip amount.
Mobile device 165, after electronically capturing, as part of consumer 105's authorization of the transaction, consumer 105's signature or PIN number, or consumer 105's selection of the payment account to authorize using the selected payment account to initiate the payment, can transmit this consumer authorization information to computer system 150. When the transaction information includes a display enabling or in some other way enables consumer 105 to enter a tip amount, the consumer information can include a tip amount that is authorized by consumer 105. Computer system 150, upon receipt of this consumer authorization information, can transmit the consumer authorization information to financial system 160A. Financial system 160A can use the consumer authorization information, along with other information, to determine to authorize the purchase transaction. Financial system 160A, having determined to authorize the purchase transaction, can transmit a transaction authorization to the cashier's sales register (i.e., sales device 110), and the cashier can complete the purchase transaction. In some embodiments, computer system 150 authorizes the purchase transaction and sends the transaction authorization to the cashier's sales register. At this point, consumer 105 is free to leave the store with the items that are part of the purchase transaction.
The purchase process as illustrated in
Once consumer 105's items have been rung up by the sales clerk using sales device 110 and scanner 108, a card swipe 250 phase is initiated. At step 205, consumer 105 uses payment card 140 to pay for the purchase, and card reader 155 reads information from the magnetic strip of payment card 140. At step 210, card reader 155 transmits the information obtained from payment card 140 to sales device 110 completing the card swipe phase of the purchase transaction. Sales device 110, scanner 108, and card reader 155 can comprise a sales system, as illustrated in the embodiment of
Transaction authorization 245, where consumer 105's purchase transaction is authorized, starts at step 215. At step 215, sales device 110 transmits part or all of the payment card information, obtained by card reader 155 from payment card 140, to financial system 160. Sales device 110 can further transmit transaction information related to the purchase that consumer 105 desires to make to financial system 160. For example, sales device 110 can transmit the total amount of the purchase, or the line items of the purchase, to financial system 160.
Financial system 160 can be, for example, the system used by Target® or Walmart® to process credit card and ATM card purchase transactions. As will be appreciated, financial system 160 can take on any one of a variety of suitable embodiments. For example, financial system 160 can be financial system 160A of
As will be appreciated, data transmitted or received by a component of a system is also transmitted or received by the system of which the component is a part. For example, in
At step 220, financial system 160, having determined that payment card 140 is associated with computer system 150 based on, for example, the identity information or meta data of payment card 140, transmits at least part of the transaction information and the payment card information to computer system 150. In some embodiments, such as in
Computer system 150, having access to a database that associates the payment card information with mobile device 165, for example a smartphone owned by consumer 105, at step 225 transmits a message that causes the transaction information to be displayed on consumer 105's smartphone, starting consumer authorization 255, a sub-part of transaction authorization 245.
The message transmitted at step 225 further contains a consumer authorization request. As part of an authorization of the transaction, and to satisfy the consumer authorization request, consumer 105 can use mobile device 165 to electronically capture consumer 105's signature or personal identification number (PIN), or can select the payment account. When consumer 105 makes a purchase at a business, such as a restaurant, where tips are accepted, the consumer authorization request can include a display enabling consumer 105 to enter or select a tip amount.
At step 230, mobile device 165 (i.e., consumer 105's smartphone in the example of
At this point, assuming that the purchase transaction was authorized (i.e., the result of transaction authorization 245 is that the purchase transaction was authorized), the purchase transaction is complete and the consumer is free to walk out of the store with the items that are part of the purchase transaction.
As illustrated in
Sales system 480 can include any component associated with processing a purchase transaction. A component can be associated with processing a purchase transaction when the component assists in identifying purchase transaction items, or assists in identifying the payment mechanism associated with the purchase transaction, or assists in receiving the payment, or assists in processing cash or other proxies for money, such as checks, money orders, travelers checks, and the like associated with the purchase transaction, or assists in calculations associated with the purchase transaction, or assists in tracking inventory effects of purchase transactions, or provides any other assistance related to the purchase transaction.
Examples of sales systems and components of sales systems include point of sale (POS) systems, cash registers, computer systems running sales applications including mobile devices running sales applications, cloud based POS systems, checkout registers, computer systems running internet based applications such as a web browser, mobile devices running sales applications, fixed function devices (i.e., hardware devices without a general purpose operating system) configured to function as sales devices, card readers, scanners, automated money acceptance devices, automated change devices, self-serve point of sales systems (i.e., systems where a consumer can scan or enter the items to be purchased, can provide a payment card, and can complete a purchase transaction without the assistance of a store employee), and the like.
Sales system 480 can obtain information associated with payment object 740 of
Financial system 160A (as well as financial system 160 of
Some components of
It is noteworthy that, in some embodiments, including the embodiments of
Step 610 includes swiping a payment card through a card reader. Step 610 can occur after step 605, or can be the event that triggers step 605. The term “swipe” here refers to any manner of triggering a physical card reader to read or obtain information from a physical card, such as passing a card through a magnetic stripe reader, smartcard reader, optical code reader, radio frequency identification (RFID) reader, etc. Step 610 can involve a payment card, such as payment card 140, being swiped though a card reader, such as card reader 155, as is depicted in
Step 615 includes receiving transaction information associated with a purchase transaction. A computer system, such as computer system 150, can receive the transaction information, which can be sent by a sales system, such as sales system 480. Using the example of
As discussed above related to
Step 620 includes receiving identity information of the payment card. The identity information can have been obtained from the payment card using the card reader, and includes information that enables the identification of the payment card or an account associated with the payment card. Using the example of
At step 210, card reader 155 transmits the payment card information to sales device 110, which at step 215 transmits the payment card information to financial system 160. Financial system 160 transmits the payment card information to computer system 150 at step 220. The payment card information received by computer system 150 is from card reader 155 via both sales device 110 and financial system 160. As discussed related to step 615, any data transmitted or received by sales device 110 is also transmitted or received by the sales system of which sales device 110 is a part. Accordingly, computer system 150 receives, from a sales system of which sales device 110 is a part, payment card information including identity information, the payment card information having been obtained using card reader 155 from payment card 140, a payment card associated with consumer 105, as per step 620.
Step 625 includes determining information related to a mobile device associated with a customer. Computer system 150 can have access to a database that associates the payment card, such as payment card 140, with a mobile device, such as mobile device 165. Computer system 150 can access the database to obtain, for example, contact information for the mobile device, such as the internet protocol (IP) address or phone number of the mobile device, or an email address associated with the mobile device, such as consumer 105's email address.
Step 630 includes sending or causing to be sent an authorization request. Using the example of
Step 635 includes receiving a response to the authorization request. Using the example of
Step 640 includes sending the response information to a financial system. Using the example of
After the cashier finishes ringing up consumer 105's items and determines the total bill, consumer 105 presents payment object 740, which can be, for example, a credit card, an automated teller machine (ATM) card, a proxy card, or a mobile device, to the seller. Payment object 740 is compatible with sales system 750 and with financial system 160A. Because payment object 740 is compatible with sales system 480, sales system 480 can obtain information associated with payment object 740 sufficient to enable initiation of a transaction authorization, such as transaction authorization 245 of
Using the method diagrammed in
As another example, payment object 740 can be a mobile device, such as mobile device 165. In embodiments where payment object 740 is a mobile device, sales system 480 can obtain identity information and other information for the mobile device or a digital wallet associated with the mobile device. Sales system 480 can obtain the identity and other information from mobile device 165 via, in various embodiments, WiFi, 3G, 4G, Near Field Communication (NFC), or Bluetooth, or can obtain the identity and other information via a QR code or a bar code or any machine readable code from the mobile device, for example, by scanning a QR code or bar code displayed by the mobile device.
Sales system 480 can obtain information from payment object 740 (i.e., the payment object information) sufficient to enable initiation of a transaction authorization, such as transaction authorization 245 of
Sales system 480 and financial system 160A can establish a communication channel between themselves. Once established, sales system 480 can transmit the transaction information and the payment object information to financial system 160A to have the purchase transaction authorized. The transaction information can include an amount of the purchase transaction and line items from the purchase transaction, and the payment object information can include identity information for payment object 740 (i.e., payment object identity information). Financial system 160A, after determining that payment object 740 is associated with computer system 150 based on, for example, the payment object identity information, transmits the transaction information and the payment object information to computer system 150. Computer system 150, having access to a database that associates the payment object information with mobile device 165, transmits a message that causes the transaction information to be displayed on mobile device 165. Consumer 105 can use mobile device 165 to review the transaction information, for example consumer 105 can make sure that the line items and the total amount are correct. As part of consumer 105's authorization of the transaction, consumer 105 can use mobile device 165 to electronically capture consumer 105's signature or PIN, or to select the payment account to use to initiate the payment.
Mobile device 165, after electronically capturing consumer 105's signature or PIN number or payment account selection as part of consumer 105's authorization of the transaction, can transmit this consumer authorization information to computer system 150. Computer system 150, upon receipt of this consumer authorization information, can transmit the consumer authorization information to financial system 160A. Financial system 160A can use the consumer authorization information, along with other information, to determine whether to authorize the purchase transaction. Financial system 160A, upon determining to authorize the purchase transaction, can transmit a transaction authorization to sales system 480, and the cashier can complete the purchase transaction. At this point, consumer 105 is free to leave the store with the items that are part of the purchase transaction.
Payment object 740 can be compatible with financial system 160A, as well as financial system 160 of
Further, payment object 740 can be associated with loyalty programs, wherein the loyalty programs are another type of payment mechanism which can be used to make the purchase. In some embodiments, payment object 740 can be a mobile device. Examples of mobile devices include smartphones such as an iPhone, tablets such as an iPad©, portable media devices such as an iPod©, wearable devices such as Google Glass© or Samsung Smartwatch©, or a laptop or other portable computer.
When payment object 740 is a proxy card or proxy object, computer system 150B can access a database containing association information representing an association between the proxy card or proxy object and multiple payment accounts or other types of electronic accounts. Computer system 150B can determine a payment account to use to initiate the payment in several ways. In one example, computer system 150B causes one or more of the payment accounts associated with the proxy card or proxy object to be displayed on mobile device 165, and consumer 105 indicates a selection of the payment account to use to initiate the payment. In another example, computer system 150B determines a payment account associated with the proxy card or proxy object to use to initiate the payment. The determination can be based on consumer 105 having previously indicated a payment account to use for this transaction, or based on the payment account used for previous purchases at that merchant, or that day, or based on the user's location, or based on only one payment account being linked to the proxy card or proxy object.
Further, payment object 740 is compatible with financial system 160C, in that financial system 160C can determine a payment mechanism that is associated with payment object 740, and can determine whether to approve a purchase transaction made using payment object 740. For example, the credit card (i.e., payment object 740) is compatible with financial system 160C, in that financial system 160C can determine a credit account that is associated with the credit card from which to obtain funds to pay for the current purchase transaction. In some embodiments, financial system 160C can determine a credit account associated with the credit card by performing a database operation to determine a credit account associated with the credit card. In some embodiments, financial system 160C can determine a credit account associated with the credit card by receiving a message from computer system 150B wherein the message identifies a credit account that is associated with the credit card. In some embodiments, sales system 480 can obtain credit account information from payment object 740 and can transmit a message containing the credit account information to computer system 150B, which can transmit the message to financial system 160C. Financial system 160C can determine a credit account associated with the credit card by receiving the message and obtaining the credit account information obtained from payment object 740 from the received message.
In some embodiments where payment object 740 is a mobile device, sales system 480 can obtain digital wallet information associated with payment object 740 (i.e., the mobile device), and can initiate a transaction authorization by transmitting information associated with the digital wallet (i.e., the digital wallet information) and the purchase transaction information to computer system 150B. The purchase transaction information can include, for example, an amount of the purchase. The transaction information can further include a display enabling consumer 105 to enter or select a tip amount.
In some embodiments, computer system 150B can determine a payment mechanism, such as a credit card or a credit account that is associated with payment object 740, or a digital wallet that is associated with payment object 740. Computer system 150B can transmit the payment mechanism information and the purchase transaction information to financial system 160C. Financial system 160C can determine the payment mechanism information by receiving the transmitted data from computer system 150B and obtaining the payment mechanism information from the transmitted data. Financial system 160C can further determine whether to approve the purchase transaction, and when approved, can transmit an authorization for the purchase transaction to computer system 150B.
In some embodiments, computer system 150B, having access to a database that associates payment object 740 with mobile device 165, transmits a message that causes the purchase transaction information to be displayed on mobile device 165. Consumer 105 can use mobile device 165 to review the transaction information, for example consumer 105 can make sure that the total amount is correct or can review line items of the purchase transaction. The transaction information can also include a display enabling consumer 105 to enter or select a tip amount, or some other way of enabling consumer 105 to enter of select a tip amount.
As part of an authorization of the transaction, consumer 105 can use mobile device 165 to electronically capture consumer 105's signature or PIN. In some embodiments, computer system 150B transmits the message that causes the purchase transaction information to be displayed on mobile device 165 before obtaining a transaction authorization for the current purchase transaction from financial system 160C. In some embodiments, computer system 150B transmits the message that causes the purchase transaction information to be displayed on mobile device 165 after obtaining a transaction authorization for the current purchase transaction from financial system 160C.
In some embodiments, financial system 160C will not provide a transaction authorization for the current purchase transaction until financial system 160C receives consumer authorization information, such as the data transmitted from mobile device 165 to computer system 150 during consumer authorization 255 of
After computer system 150B transmits the message that causes the purchase transaction information to be displayed on mobile device 165, mobile device 165 can electronically capturing consumer 105's signature or PIN number. Consumer 105's signature or PIN can indicate consumer 105's authorization of the purchase transaction. For some purchase transactions, neither a signature nor a PIN is required. When neither a signature or PIN is required, consumer 105 can indicate an authorization of the purchase transaction in any other compatible way. One example of such a way is by selecting a virtual button on mobile device 165, the virtual button indicating consumer 105's authorization of the purchase transaction.
For example, mobile device 165 can display the text “Do you authorize this purchase transaction,” and consumer 105 can either select a virtual “Yes” button to indicate that consumer 105 authorizes the purchase transaction, or can select a virtual “No” button to indicate that consumer 105 declines the purchase transaction. Mobile device 165 can transmit consumer 105's response to the authorization request (i.e., the consumer authorization information), such as the electronically captured signature or the PIN number of the virtual button selection, to computer system 150B.
When payment object 740 is a proxy card or proxy object, computer system 150B can cause a display containing, for example, a listing of one or more of the payment accounts associated with the proxy card or proxy object. Display 1300 of
In some embodiments, computer system 150B, upon receipt of the consumer authorization information, can transmit the consumer authorization information to financial system 160C. Financial system 160C can use the consumer authorization information, along with other information, to determine whether to authorize the purchase transaction. Financial system 160C, when it determines to authorize the purchase transaction, can transmit a transaction authorization to computer system 150B, and computer system 150B can transmit a similar transaction authorization to sales system 480 thereby completing the purchase transaction. At this point, consumer 105 is free to leave the restaurant, as consumer 105 has paid the bill.
In some embodiments, computer system 150B has already obtained an authorization for the purchase transaction from financial system 160B prior to receipt of the consumer authorization information. Upon receipt of the consumer authorization information, and having already obtained the authorization for the purchase transaction from financial system 160C, computer system 150B can transmit a purchase transaction authorization to sales system 480 thereby completing the purchase transaction. At this point, consumer 105 is free to leave the restaurant, as consumer 105 has paid the bill. In some embodiments, computer system 150B authorizes the purchase transaction, and sends the purchase transaction authorization to sales system 480 thereby completing the purchase transaction.
Payment mechanisms which can be associated with payment object 740 include a credit card, a charge card, an automated teller machine (ATM) card, a debit card, a pre-paid credit card, a pre-paid debit card, a gift card, a stored value card, a fleet card, and a loyalty program, among others.
A loyalty program can be associated with payment object 740, and a loyalty program can be a payment mechanism. For example, a mobile device or the digital wallet of a mobile device or a proxy card or proxy object can be associated with a loyalty program, and the loyalty program can be used to pay for a purchase transaction. A seller may be motivated to incentivize certain behaviors in customers. For example, the seller may want the consumer to return to the seller's store, or to purchase a certain item, or to return to the store at a certain time or during a certain time window and make a purchase. To incentivize behaviors such as these, a seller can participate in or offer a loyalty program. The seller can provide loyalty points or some equivalent for each purchase made by a consumer. By coming back to the seller's store and making additional purchases, the consumer can grow the consumer's loyalty points. The loyalty points can be redeemed for purchases made at the seller's store or another of the seller's stores or with other businesses that participate in the loyalty program.
In addition to incentivizing loyalty to a store or a brand by providing loyalty points for purchases made at the store or for brand products, a seller can use the loyalty program to incentivize other behaviors. For example, if the store has a slow period, such as a coffee shop is slow between 3 pm and 4 pm, the store owner can, in order to incentivize consumers to make purchases at the store during this slow time, offer increased loyalty points for purchases made between 3 pm and 4 pm at the store. The store owner can also offer increased redemption value for a consumer's loyalty points, or can lower the cost of products or services in terms of loyalty points, during this time window. For example, the store owner could offer to redeem 100 loyalty points and provide 150 points of value, or could reduce an item that normally costs 150 loyalty points to 100 loyalty points, for purchases made between 3 pm and 4 pm. As another example, if a business owner wants to incentivize consumers to purchase a new item the business owner is introducing, the business owner can offer increased loyalty points to consumers for purchasing this new item. The business owner can also offer increased loyalty point redemption value or reduced loyalty point costs to a consumer for purchasing this new item using loyalty program points. For example, if the new item can be normally purchased with 150 loyalty points, the business owner can offer 150 points of loyalty program value for 100 redeemed loyalty points to a consumer for purchasing this new item, or the business owner can reduce the cost of the new item to 100 loyalty points.
Step 905 includes establishing a communications channel with a sales system. Using the example of
Where the communications channel is via an intermediary computer system, the intermediary computer system can forward messages/data transmitted by sales system 480 to computer system 150 and can forward messages/data transmitted by computer system 150 to sales system 480. Further, the intermediary computer system, while transmitting messages/data as part of the communications channel, can process the message/data transmitted by sales system 480 and computer system 150, and can change, transform, or replace the message/data before transmitting the message/data. Messages/data transmitted by sales system 480 do not need to be addressed to computer system 150. For example, sales system 480 can send a message or data addressed to financial system 160A. Financial system 160A can determine that the message/data should be transmitted to computer system 150, and can forward that message/data to computer system 150. Further, financial system 160A can process the message/data, changing, transforming, or replacing the message/data, and can transmit the processed message/data to computer system 150 as part of the communications channel. The communications channel can work similarly in the opposite direction (i.e., from computer system 150 to sales system 480).
The communications channel can be established using any communication medium or mediums supported by sales system 480 and computer system 150. For example, the communications channel can be established using an internet protocol network (i.e., a network that supports the TCP/IP protocol), a network that includes third generation telecommunications (i.e., 3G), a network that includes fourth generation telecommunications (i.e., 4G), a network that includes WiFi (i.e., IEEE 802.11b), and a network that includes Bluetooth, among others. Once the communications channel is established, messages/data transmitted by sales system 480 can be received by computer system 150, and messages/data transmitted by computer system 150 can be received by sales system 480. As previously discussed, the received messages/data can be processed by an intermediary computer system or systems.
Step 910 includes receiving transaction information associated with a purchase transaction. Using the example of
Step 915 includes receiving identity information associated with a payment object. The payment object was used to pay for the purchase transaction. Using the example of
Step 920 includes determining information for a mobile device associated with the payment object. Using the example of
Step 925 includes causing an authorization request to be transmitted to the mobile device. Using the example of
When the payment object is a proxy card or proxy object, computer system 150 can cause a display containing, for example, a listing of one or more of the payment accounts associated with the proxy card or proxy object. Display 1300 of
Further, the authorization request can include a display or some other mechanism enabling consumer 105 to select or enter a tip amount. For example, the display or other mechanism can present several tip options to consumer 105, and consumer 105 can select a tip amount from amongst these tip options. As a second example, the display may have a tip amount field, and the consumer can enter any monetary amount in this field. The tip amount can be added to the purchase transaction, and the total amount of the purchase transaction can include the tip amount. Additionally, the authorization request can include other information related to the purchase transaction. For example, the authorization request can include a listing of line items of the purchase transaction. One example of a display that includes a listing of line items of a purchase transaction is the illustration of
Step 930 includes causing a listing of the line items of the purchase transaction to be displayed at the mobile device. Using the example of
In some embodiments, computer system 150 can transmit a message to an alternative computer system, and the alternative computer system can transmit a machine readable code to mobile device 165. The machine readable code, when received by mobile device 165, can cause line items of the purchase transaction to be displayed on mobile device 165. For example, computer system 150 can transmit a message to sales system 480, and sales system 480 can transmit a message to mobile device 165. The message, when received by mobile device 165, can cause a listing of line items of the purchase transaction to be displayed on mobile device 165. The transmission from sales system 480 to mobile device 165 can be via any medium supported by both devices. For example, the transmission can be via Bluetooth, WiFi, 3G, 4G, or any other available medium.
Step 935 includes receiving a response to the authorization request including response information. Using the example of
Step 940 includes sending the response information to a financial system. Using the example of
First proxy card 1130 is associated with first card association information 1103, which includes user A 1105, mobile device data 1110, first account 1120, second account 1121, and user address 1125. User A is a representation of first consumer 1140 and can be the consumer's account, the name of the consumer, an identifying indicator of the consumer such as a social security number, a driver's license number, or a number or character string that is unique and is associated with the consumer, among other things. Mobile device data 1110 is a representation of data associated with a mobile device of the consumer, in this case mobile device 1141 of first consumer 1140. Mobile device data 1110 includes contact information 1115, which is information as to how to contact mobile device 1141.
A mobile device can be contacted, for example, by an internet protocol (IP) message, a text message, an email message, among other methods of contact. Contact information 1115 includes IP address 1116 and phone number 1117. When an IP message is sent, IP address 1116 can be used to send the message to mobile device 1141. When a text message is sent, phone number 1117 can be used to send the text message to mobile device 1141. When an email message is sent, an email address (not shown), which can be associated with contact information 1115, can be used to send the email message to mobile device 1141. First account 1120 and second account 1121 are electronic accounts that are associated with first proxy card 1130. User address 1125 is the mailing address of first consumer 1140.
Second proxy card 1180 is associated with second card association information 1153, which includes user B 1155, mobile device data 1160, first account 1170, second account 1171, and user address 1175. User B is a representation of second consumer 1190 and can be the consumer's account, the name of the consumer, an identifying indicator of the consumer such as a social security number, a driver's license number, or a number or character string that is unique and is associated with the consumer, among other things. Mobile device data 1160 is a representation of data associated with a mobile device of the consumer, in this case mobile device 1191 of second consumer 1190. Mobile device data 1160 includes contact information 1165, which is information as to how to contact mobile device 1191.
A mobile device can be contacted, for example, by an internet protocol (IP) message, a text message, an email message, among other methods of contact. Contact information 1165 includes IP address 1166 and phone number 1167. When an IP message is sent, IP address 1166 can be used to send the message to mobile device 1191. When a text message is sent, phone number 1167 can be used to send the text message to mobile device 1191. When an email message is sent, an email address (not shown), which can be associated with contact information 1165, can be used to send the email message to mobile device 1191. First account 1170 and second account 1171 are electronic accounts that are associated with second proxy card 1180. User address 1175 is the mailing address of second consumer 1190.
In various embodiments, the association information is generated in various ways. To generate first card association information 1103, first consumer 1140 can use a website to create a login account, information for which can be at user A 1105. First consumer 1140 can enter various information related to mobile device 1141 using the website, and that information can comprise mobile device data 1110. First consumer 1140 can enter information for various electronic accounts using the website, and the electronic accounts can be added to first card association information 1103, such as at first account 1120 and second account 1121. First consumer 1140 can enter his mailing address using the website, and this information can be added to first card association information 1103, such as at user address 1125. Alternately, first consumer 1140 can send a text message or an email to cause first card association information 1103 to be generated, or any portion of first card association information 1103 to be generated. For example, first consumer 1140 can create a login account using the website. First consumer 1140 can send a text message to create mobile device data 1110, or can run an application on mobile device 1141, which can send information obtained from mobile device 1141 to cause part or all of first card association information 1103 to be generated. A person of ordinary skill will appreciate that there are many ways to cause the association information to be generated.
In various embodiments, the electronic accounts associated with a proxy card are electronic accounts associated with credit cards, debit cards, charge cards, automated teller machine (ATM) cards, pre-paid credit cards, pre-paid debit cards, pre-paid gift cards, stored value cards, fleet cards, gift cards, library cards, loyalty cards, identification cards, among others. In various embodiments, a proxy card can be a magnetic stripe card, a smart card, a proximity card, a re-programmable magnetic stripe card, a card or device containing a quick response (QR) code, or a card containing a bar code. In some embodiments, a proxy object can be used in place of a proxy card. The proxy object can be, among other objects, a mobile device, such as a tablet computer, a smartphone, a laptop computer, a wearable device, or a portable media device, or can be a biometrically identifiable object, such as a finger, a hand, an iris, a retina, or a face.
In various embodiments, association information 1101 can contain other information, such as additional electronic accounts, data for additional mobile devices, data for additional users of a proxy card, such as the spouse or other relative of a consumer who had a proxy card, or business associates of a consumer who has a proxy card. In various embodiments, association information 1101 can include less information. In various embodiments association information 1101 is stored in a database, a data structure, a file, or any combination of one or more of a database, a data structure, or a file. In various embodiments, the association information can be organized hierarchically, including multiple levels of hierarchy, or can have a flat organization. A person of ordinary skill in the art will appreciate that the association information can be stored in various ways using various mechanisms and organizations.
Step 1210 includes receiving an indication of initiation of a payment transaction. Step 1210 can occur after step 1205. A computer system, such as computer system 150 of
Step 1215 includes receiving transaction information associated with a financial transaction. Step 1215 can occur after step 1205 or before or after step 1210. The merchant's payment terminal system sends transaction information, such as the amount of the payment, a listing of items associated with the payment, or identifying information for the merchant, to a financial system, such as financial system 160A of
Step 1220 includes receiving payment card information. Step 1220 can occur after steps 1205 or 1210, or before or after step 1215. The merchant's payment terminal system sends identifying information for the proxy card, such as the information obtained during the swipe of the proxy card, to a financial system, such as financial system 160A. The identifying information is sent partly to obtain authorization for a payment made in association with a financial transaction. Financial system 160A relays the identifying information to a computer system, such as computer system 150, where it is accordingly received.
Step 1222 includes accessing a database that includes stored association information representing an association between the payment card and at least one payment account. Step 1222 can occur after steps 1205-1220. A computer system, such as computer system 150, can access the database. The association information can be, for example, association information 1101 of
Step 1224 includes accessing a database that includes stored association information representing an association between the payment card and contact information for a mobile device. Step 1224 can occur after steps 1205-1220, and before or after step 1222. A computer system, such as computer system 150, can access the database. The association information can be, for example, association information 1101 of
Step 1226 includes determining one or more payment accounts associated with the payment card. Step 1222 can occur after steps 1205-1222. A computer system, such as computer system 150, can determine one or more payment accounts associated with the proxy card. When the payment card is a credit card, the computer system can determine the payment account associated with the credit card. The computer system can make this determination based on the database access of step 1222, or based on identifying information obtained from the payment card during the card swipe, or in other ways. For example, the computer system can determine the payment accounts by communicating with a remote computer that is part of a different computer system. The remote computer can, for example, perform a database access to determine one or more payment account associated with the proxy card, and send information related to the payment account(s) to the computer system. When the computer system receives information related to the payment account(s), the computer system has determined the one or more payment accounts associated with the payment card.
Step 1228 includes determining contact information for a mobile device associated with the payment card. Step 1228 can occur after steps 1205-1220 or 1224, and before or after steps 1222 or 1226. A computer system, such as computer system 150, can determine contact information for a mobile device associated with the proxy card. The computer system can make this determination based on the database access of step 1222. For example, when the payment card is a credit card, the computer system can access a database, such as the database of step 1222, that associates identifying information from the credit card and contact information for a mobile device.
Step 1230 includes causing a portion of the association information, such as one or more payment accounts associated with the proxy card, to be displayed. Step 1230 can be after steps 1226 or 1222, and before or after steps 1228 or 1224. A computer system, such as computer system 150, can cause a portion of the association information to be displayed. The computer system causes information related to the one or more payment accounts associated with the proxy card to be displayed on a mobile device, such as mobile device 1141.
Step 1235 includes sending or causing to be sent a transaction event associated with the payment transaction. Step 1235 can be after 1228 or 1224, or before or after 1230. A computer system, such as computer system 150, can send the transaction event or cause the transaction event to be sent to a mobile device, such as mobile device 1141. In an embodiment, the transaction event is to cause the consumer to indicate, using the mobile device, a selection of a payment account of the payment accounts to use in processing the payment transaction. The transaction event can be the sending of a signal/message/text/email/etc. that causes the display of an image related to the transaction at the mobile device. For example, the transaction event can be the sending of a signal/message/text/email/etc. that causes a listing of one or more of the payment accounts associated with the proxy card to be displayed on the mobile device. The listing is associated with the payment transaction in that the consumer can indicate a selection of one of the payment accounts to use to obtain funds for the payment transaction.
In an embodiment, the transaction event is to cause the consumer to indicate, using the mobile device, a tip amount associated with the payment transaction. The transaction event can be the sending of a signal/message/text/email/etc. that causes the display of an tipping interface, such as the interface of
In an embodiment, the transaction event is to cause the consumer to provide, using the mobile device, at least one of a personal identification number (PIN) of the consumer, a password of the consumer, or a pass phrase of the consumer. The transaction event can be the sending of a signal/message/text/email/etc. that causes the display of an interface to capture the PIN, password, or passphrase. The transaction event is associated with the payment transaction in that the captured PIN, password, or passphrase indicate acceptance of the payment transaction by the consumer.
Step 1240 includes receiving response information. Step 1240 can be after step 1230 or before or after step 1235. A mobile device, such as mobile device 1141, can send the response information, which can be received by a computer system, such as computer system 150. As examples, the response information can include: an indication of a response made by the consumer in response to the transaction event; an indication of a selection of a payment account of the payment accounts to use in processing the payment transaction; an indication of a tip amount associated with the payment transaction; an electronic signature, in some embodiments to indicate that the consumer agrees to the terms of the payment transaction; a PIN; a password; or a passphrase, among others.
Step 1245 includes causing the payment transaction to be processed in accordance with the response information. A computer system, such as computer system 150, causes the payment transaction to be processed in accordance with the response information received at step 1240. When the response information indicates a selection of a payment account of the payment accounts to use in processing the payment transaction, the computer system causes the payment transaction to be processed using the selected payment account. When the response information indicates a tip amount associated with the payment transaction, the computer system causes the processing of the payment transaction to include the tip amount. When the response information includes an electronic signature indicating acceptance of the terms of the purchase transaction, the computer system causes the purchase transaction to be processed in accordance with the acceptance. When the response information includes a PIN, password, or passphrase, the computer system causes the payment transaction to be obtained from the payment account associated with the PIN, password, or passphrase.
Step 1245 includes causing funds to be transferred from a payment account to an account associated with the payee. A computer system, such as computer system 150, causes the funds to be transferred. When the payment card is a proxy card, and one of the associated payment accounts is selected, the computer system causes funds to be transferred from the selected payment account to an account associated with the merchant (i.e., the payee). When the payment card is associated with only one payment account, the computer system causes funds to be transferred from the one payment account to an account associated with the merchant (i.e., the payee).
This disclosure contemplates the computer system 1400 taking any suitable physical form. As example and not by way of limitation, computer system 1400 may be an embedded computer system, a system-on-chip (SOC), a single-board computer system (SBC) (such as, for example, a computer-on-module (COM) or system-on-module (SOM)), a desktop computer system, a laptop or notebook computer system, an interactive kiosk, a mainframe, a mesh of computer systems, a mobile telephone, a personal digital assistant (PDA), a server, or a combination of two or more of these. Where appropriate, computer system 1400 may include one or more computer systems 1400; be unitary or distributed; span multiple locations; span multiple machines; or reside in a cloud, which may include one or more cloud components in one or more networks. Where appropriate, one or more computer systems 1400 may perform without substantial spatial or temporal limitation one or more steps of one or more methods described or illustrated herein. As an example and not by way of limitation, one or more computer systems 1400 may perform in real time or in batch mode one or more steps of one or more methods described or illustrated herein. One or more computer systems 1400 may perform at different times or at different locations one or more steps of one or more methods described or illustrated herein, where appropriate.
The processor may be, for example, a conventional microprocessor such as an Intel Core microprocessor or an Intel Itanium microprocessor or a Motorola power PC microprocessor or a SPARC architecture processor. One of skill in the relevant art will recognize that the terms “machine-readable (storage) medium” or “computer-readable (storage) medium” include any type of device that is accessible by the processor.
The memory is coupled to the processor by, for example, a bus. The memory can include, by way of example but not limitation, random access memory (RAM), such as dynamic RAM (DRAM) or static RAM (SRAM). The memory can be local, remote, or distributed.
The bus also couples the processor to the non-volatile memory and drive unit. The non-volatile memory cane be a magnetic floppy or hard disk, a magnetic-optical disk, an optical disk, a flash memory such as NAND flash memory or NOR flash memory, a read-only memory (ROM) such as a CD-ROM, a programmable read-only memory such as EPROM or EEPROM, a magnetic or optical card, or another form of storage for large amounts of data. Some of this data is often written, by a direct memory access process, into memory during execution of software in the computer 1400. The non-volatile storage can be local, remote, or distributed. The non-volatile memory is optional because systems can be created with all applicable data available in memory. A typical computer system will usually include at least a processor, memory, and a device (e.g., a bus) coupling the memory to the processor.
Software is typically stored in the non-volatile memory and/or the drive unit. Indeed, for large programs, storing the entire program in memory may not even be possible. Nevertheless, one should understand that for software to run, if necessary, the software is moved to a computer readable location appropriate for processing, and for illustrative purposes, that location is referred to as the memory in this paper. Even when software is moved to the memory for execution, the processor will typically make use of hardware registers to store values associated with the software, and local cache that, ideally, serves to speed up execution. As used herein, a software program is assumed to be stored at any known or convenient location (from non-volatile storage to hardware registers) when the software program is referred to as “implemented in a computer-readable medium.” A processor is considered to be “configured to execute a program” when at least one value associated with the program is stored in a register readable by the processor.
The bus also couples the processor to the network interface device. The interface can include one or more of a modem or network interface. A person of ordinary skill will appreciate that a modem or network interface can be considered to be part of the computer system 1400. The interface can include an analog modem, ISDN modem, cable modem, token ring interface, satellite transmission interface (e.g., “direct PC”), Wi-Fi interface, or other interfaces for coupling a computer system to other computer systems. The interface can include one or more input and/or output devices. The I/O devices can include, by way of example but not limitation, a keyboard, a mouse or other pointing device, disk drives, printers, a scanner, and other input and/or output devices, including a display device. The display device can include, by way of example but not limitation, a cathode ray tube (CRT), liquid crystal display (LCD), or some other applicable known or convenient display device. For simplicity, this disclosure assumes that controllers of any devices not depicted in the example of
The computer system can have one Bus or multiple Buses. A bus can include for example, a system bus, a Peripheral Component Interconnect (PCI) bus or PCI-Express bus, a HyperTransport or industry standard architecture (ISA) bus, a small computer system interface (SCSI) bus, a universal serial bus (USB, USB 2.0, USB 3.0), IIC (I2C) bus, an Institute of Electrical and Electronics Engineers (IEEE) standard 1394 bus, also called “Firewire,” a QuickPath Interconnect bus, a ThunderBolt interconnect bus, a DisplayPort interconnect bus or its companion standards Mini DisplayPort (mDP), Direct Drive Monitor (DDM), Embedded DisplayPort (eDP), Internal DisplayPort (iDP), Portable Digital Media Interface (PDMI), Wireless DisplayPort (wDP), and Mobility DisplayPort (MyDP), an HDMI interconnect bus, a DVI bus.
In operation, the computer system 1400 can be controlled by operating system software that includes a file management system, such as a disk operating system. One example of operating system software with associated file management system software is the family of operating systems known as Windows® from Microsoft Corporation of Redmond, Wash., and their associated file management systems. Another example of operating system software with its associated file management system software is the Linux™ operating system and its associated file management system. The file management system is typically stored in the non-volatile memory and/or drive unit and causes the processor to execute the various acts required by the operating system to input and output data and to store data in the memory, including storing files on the non-volatile memory and/or drive unit.
Some portions of the detailed description may be presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. Referring to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like has proven convenient at times, principally for reasons of common usage.
One should bear in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, one should appreciate that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or “generating” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within registers and memories of the computer system into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used with programs in accordance with the teachings herein, or constructing more specialized apparatus to perform the methods of some embodiments may prove more convenient. The required structure for a variety of these systems will appear from the description below. In addition, the techniques are not described with reference to any particular programming language, and various embodiments may thus be implemented using a variety of programming languages.
In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.
The machine may be a server computer, a client computer, a personal computer (PC), a laptop computer, a tablet, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, a Blackberry, a smartphone, a processor, a telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
While the machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies or modules of the presently disclosed technique and innovation.
In general, the routines executed to implement the embodiments of the disclosure, may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure.
Moreover, while embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that the disclosure applies equally regardless of the particular type of machine or computer-readable media used to actually effect the distribution.
Further examples of machine-readable storage media, machine-readable media, or computer-readable (storage) media include but are not limited to recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), Blu-ray disks, among others, and transmission type media such as digital and analog communication links.
In some circumstances, operation of a memory device, such as a change in state from a binary one to a binary zero or vice-versa, for example, may comprise a transformation, such as a physical transformation. With particular types of memory devices, such a physical transformation may comprise a physical transformation of an article to a different state or thing. For example, but without limitation, for some types of memory devices, a change in state may involve an accumulation and storage of charge or a release of stored charge. Likewise, in other memory devices, a change of state may comprise a physical change or transformation in magnetic orientation or a physical change or transformation in molecular structure, such as from crystalline to amorphous or vice versa. The foregoing is not intended to be an exhaustive list of all examples in which a change in state for a binary one to a binary zero or vice-versa in a memory device may comprise a transformation, such as a physical transformation. Rather, the foregoing is intended as illustrative examples.
A storage medium typically may be non-transitory or comprise a non-transitory device. In this context, a non-transitory storage medium may include a device that is tangible, meaning that the device has a concrete physical form, although the device may change its physical state. Thus, for example, non-transitory refers to a device remaining tangible despite this change in state.
A person having ordinary skill in the art will appreciate that there are various other ways to implement the described functionality. The scope of this disclosure also includes embodiments implementing the described functionality in these various other ways. Accordingly, the scope of the present disclosure is intended to embrace all such alternatives, modifications, and variations as fall within the scope of the claims, together with all equivalents thereof.
Numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present invention. One skilled in the art will appreciate that embodiments of the present invention may be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form.
Embodiments of the present invention include various steps. The steps may be performed by hardware components or may be embodied in machine-executable instructions, which may be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the steps. Alternatively, the steps may be performed by a combination of hardware, software and/or firmware.
This application claims the benefit of U.S. Provisional Patent Application No. 61/894,322, filed Oct. 22, 2013, which is incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5590038 | Pitroda | Dec 1996 | A |
| 5652421 | Veeneman et al. | Jul 1997 | A |
| 5878337 | Joao et al. | Mar 1999 | A |
| 5960411 | Hartman et al. | Sep 1999 | A |
| 6154738 | Call | Nov 2000 | A |
| 6175922 | Wang | Jan 2001 | B1 |
| 6193155 | Walker et al. | Feb 2001 | B1 |
| 6263352 | Cohen | Jul 2001 | B1 |
| 6330544 | Walker et al. | Dec 2001 | B1 |
| 6341353 | Herman et al. | Jan 2002 | B1 |
| 6422462 | Cohen | Jul 2002 | B1 |
| 7085812 | Sherwood | Aug 2006 | B1 |
| 7155411 | Blinn et al. | Dec 2006 | B1 |
| 7233843 | Budhraja et al. | Jun 2007 | B2 |
| 7475024 | Phan | Jan 2009 | B1 |
| 7478054 | Adams et al. | Jan 2009 | B1 |
| 7493390 | Bobde et al. | Feb 2009 | B2 |
| 7552087 | Schultz et al. | Jun 2009 | B2 |
| 7575166 | McNamara | Aug 2009 | B2 |
| 7580873 | Silver et al. | Aug 2009 | B1 |
| 7603382 | Halt, Jr. | Oct 2009 | B2 |
| 7764185 | Manz et al. | Jul 2010 | B1 |
| 7805378 | Berardi et al. | Sep 2010 | B2 |
| 7810729 | Morley, Jr. | Oct 2010 | B2 |
| 7818809 | Sobel et al. | Oct 2010 | B1 |
| 8060259 | Budhraja et al. | Nov 2011 | B2 |
| 8112066 | Ben Ayed | Feb 2012 | B2 |
| 8190514 | Bishop et al. | May 2012 | B2 |
| 8266551 | Boldyrev et al. | Sep 2012 | B2 |
| 8401710 | Budhraja et al. | Mar 2013 | B2 |
| 8423459 | Green et al. | Apr 2013 | B1 |
| 8434682 | Argue et al. | May 2013 | B1 |
| 8459544 | Casey et al. | Jun 2013 | B2 |
| 8498888 | Raff et al. | Jul 2013 | B1 |
| 8498900 | Spirin et al. | Jul 2013 | B1 |
| 8577803 | Chatterjee et al. | Nov 2013 | B2 |
| 8577810 | Dalit et al. | Nov 2013 | B1 |
| 8579203 | Lambeth et al. | Nov 2013 | B1 |
| 8602296 | Velline et al. | Dec 2013 | B1 |
| 8630586 | Dvortsov et al. | Jan 2014 | B2 |
| 8676119 | Cohen et al. | Mar 2014 | B2 |
| 8712854 | Rafferty et al. | Apr 2014 | B1 |
| 8788418 | Spodak et al. | Jul 2014 | B2 |
| 8855312 | Hodgman et al. | Oct 2014 | B1 |
| 8859337 | Gaul et al. | Oct 2014 | B2 |
| 8892462 | Borovsky et al. | Nov 2014 | B1 |
| 8939357 | Perry | Jan 2015 | B1 |
| 8972298 | Kunz | Mar 2015 | B2 |
| 9010644 | Workley | Apr 2015 | B1 |
| 9064249 | Borovsky et al. | Jun 2015 | B1 |
| 9092767 | Andrews et al. | Jul 2015 | B1 |
| 9092776 | Dessert | Jul 2015 | B2 |
| 9092828 | Hosp | Jul 2015 | B2 |
| 9195985 | Domenica et al. | Nov 2015 | B2 |
| 9721251 | Jen et al. | Aug 2017 | B1 |
| 9836739 | Borovsky et al. | Dec 2017 | B1 |
| 9881305 | Lewis et al. | Jan 2018 | B1 |
| 20020091646 | Lake et al. | Jul 2002 | A1 |
| 20030014317 | Siegel et al. | Jan 2003 | A1 |
| 20030061157 | Hirka et al. | Mar 2003 | A1 |
| 20030065805 | Barnes, Jr. | Apr 2003 | A1 |
| 20030115126 | Pitroda | Jun 2003 | A1 |
| 20030115285 | Lee et al. | Jun 2003 | A1 |
| 20030204447 | Dalzell et al. | Oct 2003 | A1 |
| 20040030601 | Pond et al. | Feb 2004 | A1 |
| 20040138999 | Friedman et al. | Jul 2004 | A1 |
| 20040193489 | Boyd et al. | Sep 2004 | A1 |
| 20040204990 | Lee et al. | Oct 2004 | A1 |
| 20040215520 | Butler et al. | Oct 2004 | A1 |
| 20040219971 | Ciancio et al. | Nov 2004 | A1 |
| 20050055582 | Bazakos et al. | Mar 2005 | A1 |
| 20050246245 | Satchell | Nov 2005 | A1 |
| 20060064373 | Kelley | Mar 2006 | A1 |
| 20060085333 | Wah et al. | Apr 2006 | A1 |
| 20060131385 | Kim | Jun 2006 | A1 |
| 20060146839 | Hurwitz et al. | Jul 2006 | A1 |
| 20060261149 | Raghavendra Tulluri | Nov 2006 | A1 |
| 20070069013 | Seifert et al. | Mar 2007 | A1 |
| 20070073619 | Smith | Mar 2007 | A1 |
| 20070150387 | Seubert et al. | Jun 2007 | A1 |
| 20070208930 | Blank et al. | Sep 2007 | A1 |
| 20070255653 | Tumminaro et al. | Nov 2007 | A1 |
| 20070255662 | Tumminaro | Nov 2007 | A1 |
| 20080035725 | Jambunathan et al. | Feb 2008 | A1 |
| 20080037442 | Bill | Feb 2008 | A1 |
| 20080040265 | Rackley, III et al. | Feb 2008 | A1 |
| 20080052176 | Buchheit | Feb 2008 | A1 |
| 20080078831 | Johnson et al. | Apr 2008 | A1 |
| 20080133351 | White et al. | Jun 2008 | A1 |
| 20080177624 | Dohse | Jul 2008 | A9 |
| 20080177826 | Pitroda | Jul 2008 | A1 |
| 20080197188 | Jagatic et al. | Aug 2008 | A1 |
| 20080262925 | Kim et al. | Oct 2008 | A1 |
| 20080270246 | Chen | Oct 2008 | A1 |
| 20080277465 | Pletz et al. | Nov 2008 | A1 |
| 20080296978 | Finkenzeller et al. | Dec 2008 | A1 |
| 20090070228 | Ronen | Mar 2009 | A1 |
| 20090094126 | Killian et al. | Apr 2009 | A1 |
| 20090099961 | Ogilvy | Apr 2009 | A1 |
| 20090106138 | Smith et al. | Apr 2009 | A1 |
| 20090112766 | Hammad et al. | Apr 2009 | A1 |
| 20090119190 | Realini | May 2009 | A1 |
| 20090159663 | Mullen et al. | Jun 2009 | A1 |
| 20090192904 | Patterson et al. | Jul 2009 | A1 |
| 20090266884 | Killian et al. | Oct 2009 | A1 |
| 20090271265 | Lay et al. | Oct 2009 | A1 |
| 20090288012 | Hertel et al. | Nov 2009 | A1 |
| 20090313132 | McKenna et al. | Dec 2009 | A1 |
| 20090319421 | Mathis et al. | Dec 2009 | A1 |
| 20090319638 | Faith et al. | Dec 2009 | A1 |
| 20100010906 | Grecia | Jan 2010 | A1 |
| 20100076777 | Paretti et al. | Mar 2010 | A1 |
| 20100082420 | Trifiletti et al. | Apr 2010 | A1 |
| 20100102125 | Gatto | Apr 2010 | A1 |
| 20100174596 | Gilman et al. | Jul 2010 | A1 |
| 20100217674 | Kean | Aug 2010 | A1 |
| 20100217699 | Bookstaff | Aug 2010 | A1 |
| 20100223145 | Dragt | Sep 2010 | A1 |
| 20100269059 | Othmer et al. | Oct 2010 | A1 |
| 20100306099 | Hirson et al. | Dec 2010 | A1 |
| 20110029416 | Greenspan | Feb 2011 | A1 |
| 20110035319 | Brand et al. | Feb 2011 | A1 |
| 20110047013 | McKenzie, III | Feb 2011 | A1 |
| 20110055084 | Singh | Mar 2011 | A1 |
| 20110071892 | Dickelman | Mar 2011 | A1 |
| 20110087550 | Fordyce, III et al. | Apr 2011 | A1 |
| 20110125633 | Aaltonen et al. | May 2011 | A1 |
| 20110131128 | Vaananen | Jun 2011 | A1 |
| 20110145049 | Hertel et al. | Jun 2011 | A1 |
| 20110145052 | Lin et al. | Jun 2011 | A1 |
| 20110153438 | Dragt | Jun 2011 | A1 |
| 20110178883 | Granbery | Jul 2011 | A1 |
| 20110180598 | Morgan | Jul 2011 | A1 |
| 20110218871 | Singh | Sep 2011 | A1 |
| 20110246284 | Chaikin et al. | Oct 2011 | A1 |
| 20110251892 | Laracey | Oct 2011 | A1 |
| 20110251962 | Hruska | Oct 2011 | A1 |
| 20110258014 | Evangelist et al. | Oct 2011 | A1 |
| 20110258689 | Cohen et al. | Oct 2011 | A1 |
| 20110270747 | Xu | Nov 2011 | A1 |
| 20110276418 | Velani | Nov 2011 | A1 |
| 20110295750 | Rammal | Dec 2011 | A1 |
| 20110302019 | Proctor, Jr. et al. | Dec 2011 | A1 |
| 20110302080 | White et al. | Dec 2011 | A1 |
| 20110313840 | Mason et al. | Dec 2011 | A1 |
| 20110313867 | Silver | Dec 2011 | A9 |
| 20110313871 | Greenwood | Dec 2011 | A1 |
| 20110320345 | Taveau et al. | Dec 2011 | A1 |
| 20120011072 | Lodolo | Jan 2012 | A1 |
| 20120016731 | Smith et al. | Jan 2012 | A1 |
| 20120029990 | Fisher | Feb 2012 | A1 |
| 20120030044 | Hurst | Feb 2012 | A1 |
| 20120059701 | van der Veen et al. | Mar 2012 | A1 |
| 20120059718 | Ramer et al. | Mar 2012 | A1 |
| 20120059758 | Carlson | Mar 2012 | A1 |
| 20120084210 | Farahmand | Apr 2012 | A1 |
| 20120089418 | Kamath et al. | Apr 2012 | A1 |
| 20120095867 | McKelvey | Apr 2012 | A1 |
| 20120095871 | Dorsey et al. | Apr 2012 | A1 |
| 20120110568 | Abel et al. | May 2012 | A1 |
| 20120143772 | Abadir | Jun 2012 | A1 |
| 20120150611 | Isaacson et al. | Jun 2012 | A1 |
| 20120150643 | Wolfe et al. | Jun 2012 | A1 |
| 20120150742 | Poon et al. | Jun 2012 | A1 |
| 20120166311 | Dwight et al. | Jun 2012 | A1 |
| 20120166331 | Varsaysky Waisman-Diamond | Jun 2012 | A1 |
| 20120185306 | Cheng | Jul 2012 | A1 |
| 20120185355 | Kilroy | Jul 2012 | A1 |
| 20120197740 | Grigg et al. | Aug 2012 | A1 |
| 20120197743 | Grigg et al. | Aug 2012 | A1 |
| 20120197794 | Grigg et al. | Aug 2012 | A1 |
| 20120209749 | Hammad et al. | Aug 2012 | A1 |
| 20120209773 | Ranganathan | Aug 2012 | A1 |
| 20120214416 | Kent et al. | Aug 2012 | A1 |
| 20120244885 | Hefetz | Sep 2012 | A1 |
| 20120253852 | Pourfallah et al. | Oct 2012 | A1 |
| 20120254031 | Walker | Oct 2012 | A1 |
| 20120271707 | Harrison et al. | Oct 2012 | A1 |
| 20120271725 | Cheng | Oct 2012 | A1 |
| 20120278727 | Ananthakrishnan et al. | Nov 2012 | A1 |
| 20120284036 | Evans | Nov 2012 | A1 |
| 20120290422 | Bhinder | Nov 2012 | A1 |
| 20120290609 | Britt | Nov 2012 | A1 |
| 20120296679 | Im | Nov 2012 | A1 |
| 20120296726 | Dessert et al. | Nov 2012 | A1 |
| 20120323685 | Ullah | Dec 2012 | A1 |
| 20130006773 | Lutnick et al. | Jan 2013 | A1 |
| 20130019284 | Pacyga et al. | Jan 2013 | A1 |
| 20130024341 | Jeon et al. | Jan 2013 | A1 |
| 20130024364 | Shrtvastava et al. | Jan 2013 | A1 |
| 20130024371 | Hariramani et al. | Jan 2013 | A1 |
| 20130030889 | Davich et al. | Jan 2013 | A1 |
| 20130041824 | Gupta | Feb 2013 | A1 |
| 20130048719 | Bennett | Feb 2013 | A1 |
| 20130050080 | Dahl et al. | Feb 2013 | A1 |
| 20130054320 | Dorso | Feb 2013 | A1 |
| 20130065672 | Gelman et al. | Mar 2013 | A1 |
| 20130066783 | Wolff | Mar 2013 | A1 |
| 20130073363 | Boal | Mar 2013 | A1 |
| 20130103574 | Conrad et al. | Apr 2013 | A1 |
| 20130103946 | Binenstock | Apr 2013 | A1 |
| 20130117329 | Bank et al. | May 2013 | A1 |
| 20130124333 | Doughty et al. | May 2013 | A1 |
| 20130132140 | Amin et al. | May 2013 | A1 |
| 20130132246 | Amin et al. | May 2013 | A1 |
| 20130132274 | Henderson et al. | May 2013 | A1 |
| 20130132887 | Amin et al. | May 2013 | A1 |
| 20130134962 | Kamel et al. | May 2013 | A1 |
| 20130138563 | Gilder et al. | May 2013 | A1 |
| 20130144707 | Issacson et al. | Jun 2013 | A1 |
| 20130151613 | Dhawan et al. | Jun 2013 | A1 |
| 20130159081 | Shastry et al. | Jun 2013 | A1 |
| 20130159172 | Kim | Jun 2013 | A1 |
| 20130159173 | Sivaraman et al. | Jun 2013 | A1 |
| 20130159446 | Carlson et al. | Jun 2013 | A1 |
| 20130166402 | Parento | Jun 2013 | A1 |
| 20130166445 | Issacson et al. | Jun 2013 | A1 |
| 20130173407 | Killian et al. | Jul 2013 | A1 |
| 20130179227 | Booth et al. | Jul 2013 | A1 |
| 20130181045 | Dessert et al. | Jul 2013 | A1 |
| 20130198018 | Baig | Aug 2013 | A1 |
| 20130204727 | Rothschild | Aug 2013 | A1 |
| 20130204777 | Irwin, Jr. et al. | Aug 2013 | A1 |
| 20130204793 | Kerridge et al. | Aug 2013 | A1 |
| 20130218697 | Kingston et al. | Aug 2013 | A1 |
| 20130218721 | Borhan et al. | Aug 2013 | A1 |
| 20130225081 | Doss et al. | Aug 2013 | A1 |
| 20130228616 | Bhosle et al. | Sep 2013 | A1 |
| 20130236109 | Madden et al. | Sep 2013 | A1 |
| 20130246203 | Laracey | Sep 2013 | A1 |
| 20130246207 | Novak et al. | Sep 2013 | A1 |
| 20130246280 | Kirsch | Sep 2013 | A1 |
| 20130246301 | Radhakrishnan et al. | Sep 2013 | A1 |
| 20130248591 | Look et al. | Sep 2013 | A1 |
| 20130268431 | Mohsenzadeh | Oct 2013 | A1 |
| 20130290173 | Nemeroff | Oct 2013 | A1 |
| 20130290522 | Behm, Jr. | Oct 2013 | A1 |
| 20130291018 | Billings et al. | Oct 2013 | A1 |
| 20130297933 | Fiducia et al. | Nov 2013 | A1 |
| 20130317835 | Mathew | Nov 2013 | A1 |
| 20130317950 | Abraham et al. | Nov 2013 | A1 |
| 20130332354 | Rhee et al. | Dec 2013 | A1 |
| 20130332385 | Kilroy et al. | Dec 2013 | A1 |
| 20130339253 | Sincai | Dec 2013 | A1 |
| 20130346223 | Prabhu | Dec 2013 | A1 |
| 20140006205 | Berry et al. | Jan 2014 | A1 |
| 20140012754 | Hanson | Jan 2014 | A1 |
| 20140019236 | Argue et al. | Jan 2014 | A1 |
| 20140025446 | Nagarajan et al. | Jan 2014 | A1 |
| 20140032297 | Germann et al. | Jan 2014 | A1 |
| 20140052617 | Chawla et al. | Feb 2014 | A1 |
| 20140057667 | Blankenship et al. | Feb 2014 | A1 |
| 20140058861 | Argue et al. | Feb 2014 | A1 |
| 20140067557 | van Niekerk et al. | Mar 2014 | A1 |
| 20140074569 | Francis et al. | Mar 2014 | A1 |
| 20140074655 | Lim et al. | Mar 2014 | A1 |
| 20140074658 | Sanchez | Mar 2014 | A1 |
| 20140074691 | Bank et al. | Mar 2014 | A1 |
| 20140074716 | Ni | Mar 2014 | A1 |
| 20140081783 | Paranjape et al. | Mar 2014 | A1 |
| 20140081853 | Sanchez | Mar 2014 | A1 |
| 20140081854 | Sanchez et al. | Mar 2014 | A1 |
| 20140084059 | Sierchio et al. | Mar 2014 | A1 |
| 20140089073 | Jacobs et al. | Mar 2014 | A1 |
| 20140089078 | Dessert et al. | Mar 2014 | A1 |
| 20140096179 | Ben-Shalom et al. | Apr 2014 | A1 |
| 20140099888 | Flanagan et al. | Apr 2014 | A1 |
| 20140100931 | Sanchez et al. | Apr 2014 | A1 |
| 20140100973 | Brown et al. | Apr 2014 | A1 |
| 20140101737 | Rhee | Apr 2014 | A1 |
| 20140108245 | Drummond et al. | Apr 2014 | A1 |
| 20140114775 | Cloin et al. | Apr 2014 | A1 |
| 20140114781 | Watanabe | Apr 2014 | A1 |
| 20140122345 | Argue et al. | May 2014 | A1 |
| 20140129135 | Holden et al. | May 2014 | A1 |
| 20140129302 | Amin et al. | May 2014 | A1 |
| 20140129357 | Goodwin | May 2014 | A1 |
| 20140129942 | Rathod | May 2014 | A1 |
| 20140129951 | Amin et al. | May 2014 | A1 |
| 20140136318 | Alberth, Jr. et al. | May 2014 | A1 |
| 20140136349 | Dave et al. | May 2014 | A1 |
| 20140149282 | Philliou et al. | May 2014 | A1 |
| 20140156508 | Argue et al. | Jun 2014 | A1 |
| 20140156517 | Argue et al. | Jun 2014 | A1 |
| 20140164234 | Coffman et al. | Jun 2014 | A1 |
| 20140180805 | Argue et al. | Jun 2014 | A1 |
| 20140184505 | Fullerton et al. | Jul 2014 | A1 |
| 20140201067 | Lai et al. | Jul 2014 | A1 |
| 20140207669 | Rosenberg | Jul 2014 | A1 |
| 20140214567 | Llach et al. | Jul 2014 | A1 |
| 20140214652 | Zheng et al. | Jul 2014 | A1 |
| 20140236762 | Gerber et al. | Aug 2014 | A1 |
| 20140249947 | Hicks | Sep 2014 | A1 |
| 20140250002 | Issacson et al. | Sep 2014 | A1 |
| 20140254820 | Gardenfors et al. | Sep 2014 | A1 |
| 20140257958 | Andrews | Sep 2014 | A1 |
| 20140278589 | Rados et al. | Sep 2014 | A1 |
| 20140279098 | Ham | Sep 2014 | A1 |
| 20140279184 | Lai et al. | Sep 2014 | A1 |
| 20140379497 | Varma et al. | Dec 2014 | A1 |
| 20140379536 | Varma et al. | Dec 2014 | A1 |
| 20140379580 | Varma et al. | Dec 2014 | A1 |
| 20150012426 | Purves et al. | Jan 2015 | A1 |
| 20150025983 | Cicerchi | Jan 2015 | A1 |
| 20150032567 | Bhatia | Jan 2015 | A1 |
| 20150058146 | Gaddam et al. | Feb 2015 | A1 |
| 20150066765 | Banks et al. | Mar 2015 | A1 |
| 20150073907 | Purves et al. | Mar 2015 | A1 |
| 20150095228 | Su et al. | Apr 2015 | A1 |
| 20150100481 | Ghosh et al. | Apr 2015 | A1 |
| 20150112838 | Li et al. | Apr 2015 | A1 |
| 20150120418 | Cervenka et al. | Apr 2015 | A1 |
| 20150134513 | Olson et al. | May 2015 | A1 |
| 20150134528 | Fineman et al. | May 2015 | A1 |
| 20150178755 | Olson et al. | May 2015 | A1 |
| 20150194023 | Brackenridge et al. | Jul 2015 | A1 |
| 20150294312 | Kendrick et al. | Oct 2015 | A1 |
| 20160086166 | Pomeroy et al. | Mar 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 2017235924 | Oct 2017 | AU |
| 2 916 603 | Dec 2014 | CA |
| 2 930 186 | May 2015 | CA |
| 1107198 | Oct 2007 | EP |
| 2530451 | Mar 2016 | GB |
| 10-2006-0103089 | Sep 2006 | KR |
| WO 2009111857 | Sep 2009 | WO |
| 2014210020 | Dec 2014 | WO |
| 2015061005 | Apr 2015 | WO |
| 2015069389 | May 2015 | WO |
| 2015100378 | Jul 2015 | WO |
| 2015179316 | Nov 2015 | WO |
| Entry |
|---|
| Berger, McFaddin, Chandra Narayanaswami and Mandayam Raghunath, “Web services on mobile devices-implementation and experience,” 2003 Proceedings Fifth IEEE Workshop on Mobile Computing Systems and Applications, Monterey, CA, USA, 2003, pp. 100-109. |
| N. Delic and A. Vukasinovic, “Mobile Payment Solution—Symbiosis Between Banks, Application Service Providers and Mobile NetworkOperators,” Third International Conference on Information Technology: New Generations (ITNG'06), Las Vegas, NV, 2006, pp. 346-350. |
| Non-Final Office Action dated May 29, 2014, U.S. Appl. No. 13/837,562 of Chin, H.C.A. et al., filed Mar. 15, 2013. |
| Co-Pending U.S. Appl. No. 13/830,350 by Morgan, T.B. et al., filed Mar. 14, 2013. |
| Co-Pending U.S. Appl. No. 13/837,562 by Chin, H.C.A. et al., filed Mar. 15, 2013. |
| Co-Pending U.S. Appl. No. 14/088,113 by Maxwell, D.W. et al., filed Nov. 22, 2013. |
| Co-Pending U.S. Appl. No. 14/088,141 by Maxwell, D., filed Nov. 22, 2013. |
| Co-Pending U.S. Appl. No. 14/145.895 by Aaron, P., filed Dec. 31, 2013. |
| Co-Pending U.S. Appl. No. 14/149,754 by Spindel, N., et al. filed Jan. 7. 2014. |
| Co-Pending U.S. Appl. No. 14/160,490 by Morig, D., et al., filed Jan. 21, 2014. |
| Co-Pending U.S. Appl. No. 14/168,274 by Odawa, A. et al., filed Jan. 30. 2014. |
| Co-Pending U.S. Appl. No. 14/172,842 by Borovsky, A. et al., filed Feb. 25, 2014. |
| Co-Pending U.S. Appl. No. 14/182,655 by Spindel, N., filed Feb. 18, 2014. |
| Co-Pending U.S. Appl. No. 14/184,503 by Borovsky, A., filed Feb. 19, 2014. |
| Co-Pending U.S. Appl. No. 14/189,869 by Lamba, K. et al., filed Feb. 25, 2014. |
| Co-Pending U.S. Appl. No. 14/189,880 by Aaron, P. et al., filed Feb. 25, 2014. |
| U.S. Appl. No. 14/208,800 of Thome, J.P. et al., filed Mar. 13, 2014. |
| U.S. Appl. No. 14/225,338 of Aaron, P. et al., filed Mar. 25, 2014. |
| Non-Final Office Action dated Apr. 10, 2014, U.S. Appl. No. 14/160,490 of Morig, D., et al., filed Jan. 21, 2014. |
| Non-Final Office Action dated Apr. 9, 2014, U.S. Appl. No. 14/172,842 of Borovsky, A. et al., filed Feb. 4, 2014. |
| Final Office Action dated Aug. 28, 2014, U.S. Appl. No. 14/160,490 of Morig, D., et al., filed Jan. 21, 2014. |
| Notice of Allowance dated Aug. 1, 2014, U.S. Appl. No. 14/172,842 of Borovsky, A. et al., filed Feb. 4, 2014. |
| U.S. Appl. No. 14/513,076 of Borovsky, A., et al., filed Oct. 13, 2014. |
| U.S. Appl. No. 14/526,361 of White, M.W., et al., filed Oct. 28, 2014. |
| Advisory Action dated Nov. 18, 2014, U.S. Appl. No. 14/160,490 of Moring, D., et al., filed Jan. 21, 2014. |
| International search report and written opinion for PCT Application No. PCT/US2014/058398 dated Dec. 24, 2014. |
| Non-Final Office Action dated Jan. 9, 2015, U.S. Appl. No. 14/145,895 of Aaron, P., et al., filed Dec. 31, 2013. |
| International search report and written opinion for PCT Application No. PCT/US2014/058447 dated Jan. 15, 2015. |
| Final Office Action dated Jan. 26, 2015, U.S. Appl. No. 13/837,562 of Chin, H.C.A., et al., filed Mar. 15, 2013. |
| Notice of Allowance dated Feb. 20, 2015, U.S. Appl. No. 14/513,076 of Borovsky, A., et al., filed Oct. 13, 2014. |
| International search report and written opinion for PCT Application No. PCT/US2014/072269 dated Mar. 31, 2015. |
| Restriction Requirement dated Apr. 9, 2015, U.S. Appl. No. 14/225,338 of Aaron, P., et al., filed Mar. 25, 2014. |
| U.S. Appl. No. 14/692,655 of Borovsky, A., et al., filed Apr. 21, 2015. |
| Non-Final Office Action dated Apr. 27, 2015, U.S. Appl. No. 14/184,503 of Borovsky, A., et al., filed Feb. 19, 2014. |
| Non-Final Office Action dated May 12, 2015, U.S. Appl. No. 14/189,869 of Lamba, K., et al., filed Feb. 25, 2014. |
| “Another EBay Band-Aid Fails to Fix the New Pricing Structure Flaws,” dated Oct. 18, 2008, Retrieved from the Internet URL: https://thebrewsnews.wordpress.com/2008/10/18/another-ebay-band-aid-fails-to-fix-the-new-pricing-structure-flaws/, pp. 1-5. |
| “Online Shopping,” dated Nov. 2, 2014, Retrieved from the Internet URL: http://en.wikipedia.org/wiki/Online_shopping, on Nov. 10, 2014, pp. 1-12. |
| Goode, L., “Paying With Square's New Mobile-Payments App,” All Things D, dated Apr. 30, 2012, Retrieved from the Internet URL: http://allthingsd.com/20120430/paying-with-squares-new-mobile-payments-app/, on Nov. 7, 2014, pp. 1-3. |
| Myres, L., “What is Multi-Factor Authentication, and How Will It Change in the Future?,” Intego, dated Aug. 17, 2012, Retrieved from the Internet URL: http://www.intego.com/mac-security-blog/what-is-multi-factor-authentication-and-how-will-it-change-in-the-future/, on Nov. 11, 2014, pp. 1-4. |
| Wallen, J., “Five Top Apps for Managing Inventory,” Tech Republic, dated Aug. 15, 2012, Retrieved from the Internet URL: http://www.techrepublic.com/blog/five-apps/five-top-apps-for-managing-inventory/, on Nov. 10, 2014, pp. 1-7. |
| U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| U.S. Appl. No. 13/829,658, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| U.S. Appl. No. 14/197,704, of Lamba, K., et al., filed Mar. 5, 2014. |
| U.S. Appl. No. 14/329,638, of Aaron, P., et al. filed Jul. 11, 2014. |
| U.S. Appl. No. 14/329,658, of Aaron, P., et al. filed Jul. 11, 2014. |
| U.S. Appl. No. 14/730,860, of Sasmaz, Y., et al. filed Jun. 4, 2015. |
| Non-Final Office Action dated Mar. 19, 2015, for U.S. Appl. No. 14/329,638, of Aaron, P., et al. filed Jul. 11, 2014. |
| Non-Final Office Action dated May 20, 2015, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Non-Final Office Action dated May 26, 2015, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2014. |
| Non-Final Office Action dated May 27, 2015, for U.S. Appl. No. 14/197,704, of Lamba, K., et al., filed Mar. 5, 2014. |
| Non-Final Office Action dated Jun. 11, 2015, for U.S. Appl. No. 14/692,655, of Borovsky, A., et al., filed Apr. 21, 2015. |
| Restriction Requirement dated Jun. 19, 2015, for U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014. |
| Non-Final Office Action dated Jul. 10, 2015, for U.S. Appl. No. 14/526,361, of White, M.W., et al., filed Oct. 28, 2014. |
| Restriction Requirement dated Jul. 24, 2015, for U.S. Appl. No. 14/182,655, of Spindel, N., et al., filed Feb. 18, 2014. |
| Final Office Action dated Aug. 18, 2015, for U.S. Appl. No. 14/145,895, of Aaron, P., et al., filed Dec. 31, 2013. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2015/031423 dated Aug. 13, 2015. |
| “Tracking Inventory,” PayPal, dated Jan. 4, 2010, Retrieved from the Internet URL: https://www.paypal-community.com/t5/How-to-use-PayPal-Archive/Tracking-inventory/td-p/19392, pp. 1-3. |
| Final Office Action dated Sep. 17, 2015, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Notice of Allowance dated Sep. 18, 2015, for U.S. Appl. No. 14/197,704, of Lamba, K., et al., filed Mar. 5, 2014. |
| Non-Final Office Action dated Sep. 30, 2015, for U.S. Appl. No. 14/189,880, of Aaron, P., filed Feb. 25, 2014. |
| Final Office Action dated Oct. 2, 2015, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2014. |
| Final Office Action dated Oct. 5, 2015, for U.S. Appl. No. 14/526,361, of White, M.W., et al., filed Oct. 28, 2014. |
| Non-Final Office Action dated Oct. 5, 2015, for U.S. Appl. No. 13/829,658, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Non-Final Office Action dated Oct. 6, 2015, for U.S. Appl. No. 14/329,658, of Aaron, P., et al. filed Jul. 11, 2014. |
| Final Office Action dated Oct. 16, 2015, for U.S. Appl. No. 14/692,655, of Borovsky, A., et al., filed Apr. 21, 2015. |
| Final Rejection dated Oct. 21, 2015, for U.S. Appl. No. 14/329,638, of Aaron, P., et al. filed Jul. 11, 2014. |
| Non-Final Office Action dated Nov. 18, 2015, for U.S. Appl. No. 14/182,655, of Spindel, N., et al., filed Feb. 18, 2014. |
| Advisory Action dated Nov. 24, 2015, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Final Office Action dated Aug. 10, 2017, for U.S. Appl. No. 14/160,490, of Moring, D., et al., filed Jan. 21, 2014. |
| Final Office Action dated Sep. 15, 2017, for U.S. Appl. No. 14/182,655, of Spindel, N., et al., filed Feb. 18, 2014. |
| Examination Report No. 2 for Australian Patent Application No. 2014302661, dated Sep. 26, 2017. |
| Advisory Action dated Oct. 31, 2017, for U.S. Appl. No. 14/160,490, of Moring, D., et al., filed Jan. 21, 2014. |
| “Card Not Present Transaction,” Wikipedia, published Mar. 4, 2014, Retrieved from the Internet URL: http://en.wikipedia.org/wiki/Card_not_present_transaction, on Jun. 6, 2014, pp. 1-2. |
| “Payment Gateway,” Wikipedia, published May 30, 2014, Retrieved from the Internet URL: http://en.wikipedia.org/wik/Pavment gateways, on Jun. 6, 2014, pp. 1-3. |
| “ProPay JAK Mobile Card Reader,” Propay, published Dec. 27, 2011, Retrieved from the Internet URL: https://web.archive.org/web/20111227055421/https://www.propay.com/products-services/accept-payments/jak-card-reader, pp. 1-2. |
| “Verified by Visa Acquirer and Merchant Implementation Guide,” U.S. Region, Visa Public, May 2011, pp. 1-114. |
| “Uber—Android Apps on Google Play,” Published on Nov. 10, 2014, Retrieved from the Internet URL: https://play.google.com/store/apps/details?id=com.ubercab&hl=en, on Nov. 12, 2014, pp. 1-2. |
| Punch, L., “E-commerce: Just what does card-present mean these days,” dated Oct. 1, 2012, Retrieved from the Internet URL: http://digitaltransactions.net/news/ story/ E-Commerce_-Just-What-Does-Card-Present-Mean-These-Days, on Feb. 17, 2015, pp. 1-4. |
| Non-Final Office Action dated Dec. 1, 2014, for U.S. Appl. No. 14/062,617, of Templeton, T., et al., filed Oct. 24, 2013. |
| Non Final Office Action dated Dec. 15, 2014, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014. |
| Final Office Action dated Apr. 16, 2015, for U.S. Appl. No. 14/062,617, of Templeton, T., et al., filed Oct. 24, 2013. |
| Final Office Action dated Aug. 31, 2015, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014. |
| Non-Final Office Action dated Jan. 14, 2016, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014. |
| Non-Final Office Action dated Feb. 23, 2016, for U.S. Appl. No. 14/062,617, of Templeton, T., et al., filed Oct. 24, 2013. |
| Non-Final Office Action dated May 5, 2016, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014. |
| Non-Final Office Action dated Aug. 10, 2016, for U.S. Appl. No. 14/312,433, of Varma, A.K., et al., filed Jun. 23, 2014. |
| Final Office Action dated Sep. 1, 2016, for U.S. Appl. No. 14/062,617, of Templeton, T., et al., filed Oct. 24, 2013. |
| Non-Final Office Action dated Sep. 8, 2016, for U.S. Appl. No. 14/312,371, of Varma, A.K., et al., filed Jun. 23, 2014. |
| Examination Report No. 1 for Australian Patent Application No. 2014302661, dated Sep. 27, 2016. |
| Non-Final Office Action dated Nov. 17, 2016, for U.S. Appl. No. 14/701,571, of Jen, M., et al., filed May 1, 2015. |
| Advisory Action dated Nov. 28, 2016, for U.S. Appl. No. 14/062,617, of Templeton, T., et al., filed Oct. 24, 2013. |
| Final Office Action dated Nov. 28, 2016, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014. |
| Examiner's Requisition for Canadian Patent Application No. 2,916,603, dated Feb. 9, 2017. |
| Notice of Allowance dated Mar. 23, 2017, for U.S. Appl. No. 14/701,571, of Jen, M., et al., filed May 1, 2015. |
| Advisory Action dated Apr. 10, 2017, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014. |
| Non-Final Office Action dated Apr. 18, 2017, for U.S. Appl. No. 14/160,490, of Moring, D., et al., filed Jan. 21, 2014. |
| Final Office Action dated Apr. 19, 2017, for U.S. Appl. No. 14/312,433, of Varma, A.K., et al., filed Jun. 23, 2014. |
| Final Office Action dated Apr. 27, 2017, for U.S. Appl. No. 14/312,371, of Varma, A.K., et al., filed Jun. 23, 2014. |
| Non-Final Office Action dated Jun. 19, 2017, for U.S. Appl. No. 14/730,860, of Sasmaz, Y., et al., filed Jun. 4, 2015. |
| Advisory Action dated Jun. 30, 2017, for U.S. Appl. No. 14/312,433, of Varma, A.K., et al., filed Jun. 23, 2014. |
| Non-Final Office Action dated Jul. 10, 2017, for U.S. Appl. No. 13/830,350, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Advisory Action dated Jul. 11, 2017, for U.S. Appl. No. 14/312,371, of Varma, A.K., et al., filed Jun. 23, 2014. |
| Examination Report No. 1 for Australian Patent Application No. 2015264426, dated Jul. 11, 2017. |
| International Search Report and Written Opinion for International Application No. PCT/US2014/043891, dated Dec. 10, 2014. |
| Munson, J., and Gupta, V.K., “Location-Based Notification as a General-Purpose Service,” dated Sep. 28, 2002, Retrieved from the Internet URL—https://ai2-s2-pdfs.s3.amazonaws.com/1bb5/6ae0a70b030e2f2376ed246834bddcabd27b.pdf, pp. 40-44. |
| Examiner Requisition for Canadian Patent Application No. 2,930,186, dated Jan. 30, 2017. |
| Notice of Acceptance for Australian Patent Application No. 2014347192, dated Feb. 16, 2017. |
| Advisory Action dated Feb. 24, 2017, for U.S. Appl. No. 14/526,361, of White, M.W., et al., filed Oct. 28, 2014. |
| Corrected Notice of Allowance dated Feb. 27, 2017, for U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014. |
| Notice of Allowance dated Mar. 2, 2017, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Non-Final Office Action dated Mar. 13, 2017, for U.S. Appl. No. 14/189,869, of Lamba, K., et al., filed Feb. 25, 2014. |
| Non-Final Office Action dated Mar. 15, 2017, for U.S. Appl. No. 13/829,658, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Non-Final Office Action dated Jul. 6, 2018, for U.S. Appl. No. 14/526,337, of Wolter, J.A., filed Oct. 28, 2014. |
| Non-Final Office Action dated Jan. 2, 2015, for U.S. Appl. No. 14/271,379, of Lewis, J., et al., filed May 6, 2014. |
| Non-Final Office Action dated Apr. 27, 2015, for U.S. Appl. No. 14/184,503 of Borovsky, A., et al., filed Feb. 19, 2014. |
| Final Office Action dated Jun. 26, 2015, for U.S. Appl. No. 14/271,379, of Lewis, J., et al., filed May 6, 2014. |
| Non-Final Office Action dated Jul. 2, 2015, for U.S. Appl. No. 14/208,800, of Thome, J.P., et al., filed Mar. 13, 2014. |
| Final Office Action dated Sep. 21, 2015, for U.S. Appl. No. 14/184,503, of Borovsky, A., et al., filed Feb. 19, 2014. |
| Non-Final Office Action dated Sep. 30, 2015, for U.S. Appl. No. 14/189,880, of Aaron, P., et al., filed Feb. 25, 2014. |
| Non-Final Office Action dated Oct. 8, 2015, for U.S. Appl. No. 14/149,754, of Spindel, N., et al., filed Jan. 7, 2014. |
| Advisory Action dated Dec. 4, 2015, for U.S. Appl. No. 14/184,503, of Borovsky, A., et al., filed Feb. 19, 2014. |
| Non-Final Office Action dated Mar. 31, 2016, for U.S. Appl. No. 14/271,379, of Lewis, J., et al., filed May 6, 2014. |
| Non-Final Office Action dated Sep. 21, 2016, for U.S. Appl. No. 14/189,880, of Aaron, P., et al., filed Feb. 25, 2014. |
| Final Office Action dated Oct. 6, 2016, for U.S. Appl. No. 14/271,379, of Lewis, J., et al., filed May 6, 2014. |
| Advisory Action dated Dec. 29, 2016, for U.S. Appl. No. 14/271,379, of Lewis, J., et al., filed May 6, 2014. |
| Non-Final Office Action dated Jan. 20, 2017, for U.S. Appl. No. 14/168,274, of Odawa, A.W., et al., filed Jan. 30, 2014. |
| Final Office Action dated Mar. 2, 2017, for U.S. Appl. No. 14/189,880, of Aaron, P., et al., filed Feb. 25, 2014. |
| Advisory Action dated Mar. 9, 2017, for U.S. Appl. No. 14/184,503, of Borovsky, A., et al., filed Feb. 19, 2014. |
| Non-Final Office Action dated Apr. 21, 2017, for U.S. Appl. No. 14/149,754, of Spindel, N., et al., filed Jan. 7, 2014. |
| Final Office Action dated May 19, 2017, for U.S. Appl. No. 14/168,274, of Odawa, A.W., et al., filed Jan. 30, 2014. |
| Notice of Allowance dated Jul. 6, 2017, for U.S. Appl. No. 14/184,503, of Borovsky, A., et al., filed Feb. 19, 2014. |
| Non-Final Office Action dated Aug. 4, 2017, for U.S. Appl. No. 14/526,337, of Wolter, J.A., filed Oct. 28, 2014. |
| Notice of Allowance dated Sep. 18, 2017, for U.S. Appl. No. 14/271,379, of Lewis, J., et al., filed May 6, 2014. |
| Final Office Action dated Dec. 1, 2017, for U.S. Appl. No. 14/149,754, of Spindel, N., et al., filed Jan. 7, 2014. |
| Final Office Action dated Mar. 14, 2018, for U.S. Appl. No. 14/526,337, of Wolter, J.A., filed Oct. 28, 2014. |
| Advisory Action dated Mar. 16, 2018, for U.S. Appl. No. 14/149,754, of Spindel, N., et al., filed Jan. 7, 2014. |
| Non-Final Office Action dated May 17, 2018, for U.S. Appl. No. 14/149,754, of Spindel, N., et al., filed Jan. 7, 2014. |
| “Merchantindustry.com—Best Merchant Services,” retrieved from Internet URL: https://web.archive.org/web/20121020212419/http://www.merchantindustry.com/, on Dec. 30, 2015, pp. 1-7. |
| Advisory Action dated Dec. 30, 2015, for U.S. Appl. No. 14/692,655, of Borovsky, A., et al., filed Apr. 21, 2015. |
| Final Office Action dated Dec. 31, 2015, for U.S. Appl. No. 14/208,800, of Thome, J. P., et al., filed Mar. 13, 2014. |
| Advisory Action dated Dec. 31, 2015, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2014. |
| Advisory Action dated Jan. 21, 2016, for U.S. Appl. No. 14/526,361, of White, M. W., et al., filed Oct. 28, 2014. |
| Non-Final Office Action dated Jan. 22, 2016, for U.S. Appl. No. 14/189,869, of Lamba, K., et al., filed Feb. 25, 2014. |
| Non-Final Office Action dated Feb. 2, 2016, for U.S. Appl. No. 13/829,080, of Morgan, T, B., et al., filed Mar. 14, 2013. |
| Restriction Requirement dated Feb. 29, 2016, for U.S. Appl. No. 14/088,141, of Maxwell, D. W., et al., filed Nov. 22, 2013. |
| Non-Final Office Action dated Mar. 14, 2016, for U.S. Appl. No. 14/692,655, of Borovsky, A., et al., filed Apr. 21, 2015. |
| Restriction Requirement dated Mar. 16, 2016, for U.S. Appl. No. 14/088,113, of Maxwell, D. W., et al., filed Nov. 22, 2013. |
| Non-Final Office Action dated Mar. 24, 2016, for U.S. Appl. No. 14/145,895, of Aaron, P., et al., filed Dec. 31, 2013. |
| Shalmanese, “The Straight Dope Message Board,” message dated Oct. 5, 2013, Retrieved from the Internet URL: http://boards.straightdope.com/sdmb/showthread.php?t=703989%BB, on Jul. 18, 2016, pp. 1-10. |
| Non-Final Office Action dated Apr. 8, 2016, for U.S. Appl. No. 14/526,361, of White, M. W., et al., filed Oct. 28, 2014. |
| Final Office Action dated Apr. 27, 2016, for U.S. Appl. No. 14/182,655, of Spindel, N., et al., filed Feb. 18, 2014. |
| Final Office Action dated Apr. 28, 2016, for U.S. Appl. No. 14/189,880, of Aaron, P., et al., filed Feb. 25, 2014. |
| Non-Final Office Action dated May 3, 2016, for U.S. Appl. No. 13/830,350, of Morgan, T. B., et al., filed Mar. 14, 2013. |
| Non-Final Office Action dated May 9, 2016, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2013. |
| Final Office Action dated May 20, 2016, for U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014. |
| Non-Final Office Action dated Jun. 7, 2016, for U.S. Appl. No. 14/088,113, of Maxwell, D. W., et al., filed Nov. 22, 2013. |
| Non-Final Office Action dated Jun. 7, 2016, for U.S. Appl. No. 14/208,800, of Thome, J. P., et al., filed Mar. 13, 2014. |
| Non-Final Office Action dated Jun. 8, 2016, for U.S. Appl. No. 14/088,141, of Maxwell, D. W., et al., filed Nov. 22, 2013. |
| Non-Final Office Action dated Jun. 17, 2016, for U.S. Appl. No. 14/184,503, of Borovsky, A., et al., filed Feb. 19, 2014. |
| Final Office Action dated Jun. 17, 2016, for U.S. Appl. No. 14/149,754, of Spindel, N., et al., filed Jan. 7, 2014. |
| Final Office Action dated Jun. 20, 2016, for U.S. Appl. No. 13/829,658, of Morgan, T. B., et al., filed Mar. 14, 2013. |
| Non-Final Office Action dated Jul. 14, 2016, for U.S. Appl. No. 14/160,490, of Moring, D., et al., filed Jan. 21, 2014. |
| Final Office Action dated Jul. 18, 2016, for U.S. Appl. No. 14/189,869, of Lamba, K., et al., filed Feb. 25, 2014. |
| Non-Final Office Action dated Jul. 21, 2016, for U.S. Appl. No. 14/329,638, of Aaron, P., et al., filed Jul. 11, 2014. |
| Final Office Action dated Sep. 1, 2016, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2014. |
| Notice of Allowance dated Sep. 13, 2016, for U.S. Appl. No. 14/692,655, of Borovsky, A., et al., filed Apr. 21, 2015. |
| Advisory Action dated Sep. 21, 2016, for U.S. Appl. No. 13/829,658, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Advisory Action dated Sep. 21, 2016, for U.S. Appl. No. 14/149,754, of Spindel, N., et al., filed Jan. 7, 2014. |
| Non-Final Office Action dated Sep. 21, 2016, for U.S. Appl. No. 14/189,880, of Aaron, P., filed Feb. 25, 2014. |
| Non-Final Office Action dated Sep. 22, 2016, for U.S. Appl. No. 14/182,655, of Spindel, N., et al., filed Feb. 18, 2014. |
| Advisory Action dated Sep. 29, 2016, for U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014. |
| Final Office Action dated Oct. 11, 2016, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Advisory Action dated Oct. 11, 2016, for U.S. Appl. No. 14/189,869, of Lamba, K., et al., filed Feb. 25, 2014. |
| Final Office Action dated Oct. 12, 2016, for U.S. Appl. No. 14/145,895, of Aaron, P., et al., filed Dec. 31, 2013. |
| Final Office Action dated Nov. 1, 2016, for U.S. Appl. No. 14/160,490, of Moring, D., et al., filed Jan. 21, 2014. |
| Notice of Allowance dated Nov. 8, 2016, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2014. |
| Final Office Action dated Nov. 10, 2016, for U.S. Appl. No. 13/830,350, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Final Office Action dated Nov. 14, 2016, for U.S. Appl. No. 14/526,361, of White, M.W., et al., filed Oct. 28, 2014. |
| Final Office Action dated Nov. 29, 2016, for U.S. Appl. No. 14/088,113, of Maxwell, D.W., et al., filed Nov. 22, 2013. |
| Final Office Action dated Nov. 30, 2016, for U.S. Appl. No. 14/208,800, of Thome, J.P., et al., filed Mar. 13, 2014. |
| Final Office Action dated Dec. 12, 2016, for U.S. Appl. No. 14/088,141, of Maxwell, D.W., et al., filed Nov. 22, 2013. |
| Advisory Action dated Dec. 22, 2016, for U.S. Appl. No. 14/145,895, of Aaron, P., et al., filed Dec. 31, 2013. |
| Final Office Action dated Dec. 27, 2016, for U.S. Appl. No. 14/184,503, of Borovsky, A., et al., filed Feb. 19, 2014. |
| Notice of Allowance dated Jan. 13, 2017, for U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014. |
| Final Office Action dated Jan. 27, 2017, for U.S. Appl. No. 14/329,638, of Aaron, P., et al., filed Jul. 11, 2014. |
| Examination Report No. 1 for Australian Patent Application No. 2014347192, dated Dec. 15, 2016. |
| Final Office Action dated Nov. 17, 2017, for U.S. Appl. No. 14/730,860, of Sasmaz, Y., et al., filed Jun. 4, 2015. |
| Notice of Allowance dated Nov. 24, 2017, for U.S. Appl. No. 13/829,658, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Non-Final Office Action dated Dec. 13, 2017, for U.S. Appl. No. 14/312,397, of Varma, A.K., et al., filed Jun. 23, 2014. |
| Final Office Action dated Jan. 22, 2018, for U.S. Appl. No. 13/830,350, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Examiner's Requisition for Canadian Patent Application No. 2,930,186, dated Jan. 11, 2018. |
| Examiner's Requisition for Canadian Patent Application No. 2,916,603, dated Feb. 15, 2018. |
| Number | Date | Country | |
|---|---|---|---|
| 61894322 | Oct 2013 | US |
