Consumers can interact with merchants to conduct various financial payment transactions. For example, a consumer can conduct a transaction with a merchant at a point-of-sale system using cash, a transaction card, or other transaction instrument. Conventional systems can include expensive and bulky financial transaction electronics, as may include a card reader for payment cards (e.g., debit or credit cards), a cash drawer, monitors, keyboards, and various other electronic devices. Oftentimes, however, this equipment can be costly and large, requiring additional space and resources. Further, in retail stores where space is limited, a merchant may not require all components that come with conventional point-of-sale system or at least may find it desirable to piece together a modular or mobile system to streamline the checkout experience. Further still, merchants may find approaches to conducting a financial transaction using conventional systems burdensome, where during a transaction, if a customer pays by credit card, the merchant has to enter a transaction amount and the merchant or the customer has to swipe the credit card in the card reader. Further, many transactions require that the customer sign a physical receipt, electronically approve a transaction, e.g., by pressing an approve button on a user interface, electronically sign for the transaction, e.g., with a stylus or finger on an electronic signature capture device with a touch sensitive pad, or enter an authorizing personal identification number (PIN), many of which techniques require additional financial transaction electronics and time.
In order to describe the manner in which features of the disclosure can be obtained, a more particular description of the principles will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. Understanding that these drawings depict only exemplary embodiments of the disclosure and are not therefore to be considered to be limiting of its scope, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:
Systems and methods in accordance with various embodiments of the present disclosure overcome one or more of the above-referenced and other deficiencies in conventional approaches to conducting financial transactions. In particular, in accordance with various embodiments, approaches provide for a mobile or otherwise modular point-of-sale system configured to facilitate the transfer of funds between entities (e.g., customers and merchants).
For example, in accordance with various embodiments, a portable computing device (e.g., a mobile phone, a tablet computer, etc.) that runs a merchant application or other software can be provided, where the device and software can provide functionality for a point-of-sale system. The device can be connected through a hub to one or more peripheral components such as a financial transaction electronic device including a card reader, a signature pad, a pin entry device, a controllable cash drawer, a receipt printer, a bar code reader, or other financial transaction devices. The hub can be positioned remote from a cradle or other support structure that supports or otherwise holds the portable computing device. The hub can include, for example, a first connector and cable configured to provide power and data to the portable computing device and a second connector and cable configured to receive power from a power source. In accordance with various embodiments, the data can include data acquired from the financial peripheral components or data acquired from the computing device, such as data based on a point-of-sale transaction.
The hub can further include a portable computing device port configured to couple the hub to the portable computing device using the first connector and cable, and a plurality of client peripheral ports, each client peripheral port configured to couple to one of a plurality of peripheral components. The hub can include a host including a processor and an enclosure surrounding at least the electronics and the second connector, where the host can be configured to host at least one of the plurality of client peripheral ports and operate as a single client to the portable computing device. Advantageously, such a mobile point-of-sale system tends to be less bulky and expensive than a conventional point-of-sale system, which can include a computer, a cash drawer, a receipt printer, a display, a bar code reader, specialized keyboards, among other financial devices.
Other advantages, variations, and functions are described and suggested below as may be provided in accordance with the various embodiments.
The computing device can run a merchant application or other financial transaction software that can provide functionality to facilitate a point-of-sale such as by enabling payment transactions. For example, in accordance with various embodiments, the merchant application can be downloaded and installed on the computing device. The software can be configured to operate with a card reader, where an individual can complete a financial transaction by swiping a magnetic stripe card through the card reader connected to the computing device. In this example, the financial transaction can be any transaction that involves receiving or sending payment from one person to another. The magnetic stripe card can be, for example, a credit card, a debit card, or other types of payment authenticating pieces capable of carrying out the financial transaction. In accordance with various embodiments, the size of the card reader is miniaturized to be portable for connection with the computing device. The card reader is configured to reliably read data encoded in a magnetic strip of the card with minimum error in a single swipe and provide a signal that corresponds to the data read to the computing device, which then decodes the incoming signal from the card reader and acts as a point-of-sale device to complete the financial transaction.
In accordance with various embodiments, the financial transaction card reader device can include a housing having a slot for swiping a magnetic stripe of a financial transaction card to complete the financial transaction. A read head in the housing reads data stored on the magnetic stripe and produces a signal indicative of data stored on the magnetic stripe. An output jack is adapted to be inserted into a microphone input associated with the computing device for providing the signal indicative of data stored on the magnetic stripe to the computing device, where the signal is then decoded in the computing device.
In accordance with various embodiments, the computing device can be supported and detachably secured to a stand or cradle 205. The stand can include, for example, any structure capable of holding or otherwise supporting the computing device. In various embodiments, the stand can be part of a point-of-sale system that is prominently viewable by a customer. The hub can be positioned remote the stand, cradle, or other support structure that supports or otherwise holds the computing device.
The computing device can connect to one or more peripheral components (208, 210, 212, and 214) or other devices through the hub 204. The peripheral components can include a financial transaction electronic device including a card reader, a signature pad, a pin entry device, a controllable cash drawer, a receipt printer, a bar code reader, or other financial transaction devices. The peripheral components can couple to the hub, for example, via a plurality of client peripheral ports. In accordance with various embodiments, the plurality of client peripheral ports can include USB ports, FireWire ports, Lightning ports, etc., and a financial peripheral component can connect to the hub via an appropriate connector.
The hub can include a computing device port that connects to a first connector and cable configured to couple the hub to a computing device, where the first connector and cable can provide power and data to the computing device. In accordance with various embodiments, the data can include data from the peripheral components to the computing device or data from the computing device to the peripheral components, such as data based on a point-of-sale transaction. It should be noted that any number of cables and connectors can be used to couple the hub to the computing device. Example connectors include USB connectors, FireWire connectors, Lightning connectors, etc. The hub can connect to a power source 202 via a second connector and cable and can receive power from the power source. It should be noted that the first connector can connect to any number of devices provided by any number of manufacturers. In this way, the hub acts as a communication bridge between the computing device and the peripherals connected to the hub.
The hub can further include, for example, a host including a processor and an enclosure surrounding at least the electronics and the connectors, where the host can be configured to host at least one of the plurality of client peripheral ports and operate as a single client to the computing device. In accordance with various embodiments, operating as a single client to the computing device enables the hub to host, manage, and/or otherwise independently interact with a connected peripheral component. In this way, the hub includes the necessary software and hardware to host one or more peripheral components independent of the portable computing device. Because the hub is both the host to the multiple peripheral devices, and the single client to the computing device, the hub facilitates the use of multiple peripheral devices even with computing devices that utilize protocols or policies that prohibit the computing device acting as a host to multiple peripheral devices. Further, many computing devices, especially mobile phones and tablets, utilize proprietary communication protocols for devices communicating with the computing device via a physical data port. In such embodiments, the processor is further configured to format communications according to an acceptable format to comply with the communication protocol of the computing device.
As described, in some implementations, the hub can connect the computing device to a cash drawer. The cash drawer is a structure that includes electronics to interface with the computing device and can be controlled by the computing device via the hub. For example, the computing device can send a signal to the hub to control whether to open the cash drawer. In this example, when conducting a transaction, a merchant application running on the computing device can choose to process a payment with cash or card. If a cash payment is selected, the application can send a signal to the host which can open the cash drawer. When the cash drawer closes, the cash drawer can send a signal to the host, which can notify the application running on the computing device.
In some implementations, the hub can connect the computing device to a receipt printer. In this situation, the computing device can send data to the printer through the hub. For example, the computing device can be a merchant device that conducts payment transactions with a customer and the computing device can send receipt data to the hub. The hub, in turn, can send the receipt data to the printer. The printer can receive the receipt data and print a receipt based on the receipt data. In accordance with various embodiments, the printer can be a commercially available receipt printer with a USB connector that will plug into the hub.
In some implementations, the hub can connect the computing device to a bar code reader. The bar code reader can, for example, be a commercially available bar code reader with a USB connector that will plug into the hub. A merchant can scan a barcode with the connected bar code reader and the hub can send the signals from the bar code reader to the computing device.
In various embodiments, the hub can connect to a financial transaction card reader. As described, the financial transaction card reader can be connected to the computing device, but in various embodiments a merchant may decide to connect the card reader to the hub. In the situation where the merchant decides to connect the card reader to the hub, the card reader can include, for example, appropriate ports and cables necessary to connect to the hub. The hub can include appropriate circuitry to process a signal indicative of data stored on the magnetic stripe, such as by providing the signal to the computing device. For example, a read head of the card reader can read data stored on a magnetic stripe of a financial transaction card and can produce a signal indicative of the data stored on the magnetic stripe. The signal can be provided to the hub over an appropriate cable and connector. The hub can provide the signal indicative of data stored on the magnetic stripe, encrypted or otherwise, to the computing device for further processing. The computing device can decode the signal from the hub and acts as a point-of-sale device to complete the financial transaction.
Accordingly, in accordance with various embodiments, the computing device in communication with the hub can act as a point-of-sale system. For example, the computing device can run a merchant application to process transactions. This can include, for example, scanning items, where the merchant application causes the computing device to act as a merchant-facing device. Alternatively, the merchant application can display items for purchase on the screen of the computing device and process various user-selections on the display element of the computing device. Once item scanning or item selection is complete, the computing device can calculate a total amount due, e.g., including tax and/or tip, and display the total amount to the user. The application then can display a prompt to receive a customer's signature, customer personal identification number (PIN) or other form of authorization or authentication for the transaction. When the merchant sees the prompt, the merchant can swivel the stand to face the computing device towards the customer. After the customer approves the transaction, signs on the touchpad of the computing device, the computing device can display, to the customer, different methods of obtaining a receipt. For example, the methods include printing the receipt, emailing the receipt to an email of the customer, or allowing the customer an option to skip the receipt process.
As shown in
The hub also includes USB device component peripheral 316 for connecting with the computing device via, for example, the first connector and cable. For example, the USB device peripheral can connect with a USB host on the computing device. In various embodiments, the USB device component communicates with the USB host on the computing device through at least one interface layer. In accordance with various embodiments, the interface layer can include a set of APIs (or other such interfaces) for receiving calls or requests from across the first connector and cable. Each API can be provided to receive requests for at least one specific action to be performed with respect to the peripheral components. Upon receiving a request to one of the APIs, the hub can parse or otherwise analyze the request to determine the steps or actions needed to act on or process the request. For example, a request might be received that includes a request to print a receipt. In this example, the hub can parse the request to determine the type of hardware requested (if any), or other such aspects. Information for the request can be written to a data store, or other appropriate storage location or job queue, for subsequent processing.
In accordance with various embodiments, the USB host peripheral 320 may implement multiple host controllers and each host controller can provide one or more USB ports. In the example shown, at least three USB ports can be hosted. As described, various peripheral components can be connected to the ports and can communicate with the computing device via the hub.
In accordance with various embodiments the hub can be associated with a unique identification number and software running on the computing device can determine whether the computing device is correctly paired with the hub. For example, the computing device can access the unique identification number and can determine whether the hub is correctly paired with the software running on the computing device. In other implementations, the computing device accesses the unique identification number from the host and the unique identification number associated with the host and an identification number associated with the software can be sent to a remote server, where the remote server can determine whether the hub is paired with an authorized computing device. In the situation where the unique identification numbers do not complement each other, the computing device (or remote server) can perform at least one of notifying an external system of suspicious activity, e.g., a payment service system, or preventing at least one operation or function associated with the point-of-sale system. The at least one operation can include, for example, preventing a cash drawer from opening, voiding a transaction, requiring a password or other credentials to gain access to the merchant software, etc. Such actions can deter fraud involving, for example, the drawer, where the system can detect switching of a cash-filled drawer with an empty drawer. In the situation where the unique identification numbers do complement each other, the financial transaction can proceed.
In some embodiments, the hub can include additional components. For example, the hub can include one or more network interface elements for communicating over various networks, such as a Wi-Fi, Bluetooth, RF, wired, or wireless communication systems. The hub in many embodiments can communicate with a network, such as the Internet, and may be able to communicate with other such devices. Accordingly, in accordance with various embodiments, the peripheral components capable of being connected to the hub and controlled by the computing device can be updated. For example, configuration information can be received over the network via a service provider. The configuration information can be received at the computing device and can be communicated to the hub. The configuration information can, for example, enable the operation of additional peripheral components with the computing device through the hub. This can include, for example, updating the firmware or other software stored on the hub such that the hub can be configured to process data from at least one additional peripheral component. In certain embodiments, the configuration information can be stored to a memory component and accessed by the hub. In certain embodiments, the updating and/or providing of software to support additional and/or current devices can occur, for example, as a background process where user interaction is not required.
In various other embodiments, a plurality of networked hubs can interact with one another in completing a financial or other transaction. For example, a first hub can include a network interface element or other networking component to communicate with a second hub, where the second hub is not connected to a computing device. However, in various embodiments the second hub can be connected to a computing device. In this example, data received from at least one peripheral component connected to the second hub can be provided to the first hub and processed by the computing device connected to the first hub. For example, a bar code scanner connected to the second hub can scan a barcode. Information received from the bar code scanner can be communicated from the second hub to the first hub. The first hub can provide the information to the computing device and the computing device can process the information accordingly.
In certain embodiments, a plurality of computing devices can be connected to a single hub. In this example, the hub can include a multiplexer configured to connect the computing device to a plurality of computing devices, each of the plurality of computing devices configured to access a peripheral component connected to a respective one of the plurality of client peripheral ports. For example, a first computing device connected to the hub can operate a cash drawer connected to hub, a second computing device can operate a receipt printer connected to the hub, and a third computing device can also operate the cash drawer. In this example, the hub includes the appropriate electronics and software to select between the computing devices and process information between the computing devices and connected peripheral components.
During operation, the computing device can verify 404 that the hub and computing device are an authorized pair. For example, the hub can be associated with a unique identification number and software running on the computing device can determine whether the computing device is paired or otherwise authorized to operate with the hub by comparing the unique identification number associated with the hub to a stored identification number of the hub on the computing device. In the situation where the hub and computing device are not an authorized pair, for example, the unique identification numbers do not match, the computing device can perform 406 at least one security action. This can include, for example, contacting a security service, blocking access to the software, preventing at least one peripheral connected to the hub from operating, among other such actions.
In the situation where the hub and computing device are an authorized pair, for example, the unique identification numbers match, at least one of a plurality of client peripheral ports of the host can be hosted 408, where the plurality of client peripheral ports can be configured to couple to one of the plurality of financial transaction devices. In this way, at least one of the electronic devices can be controlled by the computing device. For example, data can be received 410 from one of the plurality of electronic devices connected to a respective client peripheral port of the host device and the data can be provided 412 to the computing device via a port configured to couple the host device to the portable computing device to perform at least one financial transaction. For example, the data received can be processed by the hub into a signal acceptable to be transmitted using the first connector and readable by the computing device. In various other embodiments, the computing device can control at least one peripheral component through the hub. For example, the computing device can send a signal to the hub to control whether to open a cash drawer. In this example, when conducting a transaction, a merchant application running on the computing device can choose to process payment with cash or card. If a cash payment is selected, the application can send a signal to the host which can open the cash drawer. When the cash drawer closes, the cash drawer can send a signal to the host, which can notify the application running on the computing device. In another example, the hub can connect the computing device to a bar code reader. In this example, a merchant can scan a barcode with the connected bar code reader and the hub can send the signals from the bar code reader to the computing device.
As described, the point-of-sale systems 510 and 511 can include the hub (e.g., hub 204) and computing device, where the computing device can be coupled to or in communication with the merchant payment system through a data communication network 508, e.g., the Internet. These devices each generally include a memory, e.g., a random access memory (RAM), for storing instructions and data, and a processor for executing stored instructions. The devices and can each include one or more components, e.g., software or hardware, that are operable to send and receive requests, messages, or other types of information over the network. Some examples of computing devices include personal computers, cellular phones, handheld messaging devices, laptop computers, personal data assistants, tablet devices, and the like.
The network 508 can include any appropriate network, including an intranet, the Internet, a cellular network, a local area network, a wide area network, or any other such network, or combination thereof. Components used for such a system can depend at least in part upon the type of network, the environment selected, or both. Protocols and components for communicating over such a network are well known and will not be discussed herein in detail. The devices and the referral system can communicate over the network using wired or wireless connections, and combinations thereof.
Each of the computing devices is configured to send to the merchant payment system respective financial data that corresponds to a financial transaction that was processed by the computing device. The financial data can include, for example, data stored in a financial payment card, e.g., Track 1 data, receipt email addresses, and information describing a card-less payment account. Other examples of financial data that can be captured includes purchase data, e.g., an itemized listing of purchases, card mix data, geolocation data indicating a geographic location of a particular transaction, online/offline card data, data describing the merchant, e.g., merchant category codes (MCCs), and any type of data that is received upon a customer's authentication into a social network.
The user device and the merchant device can each be a computer coupled to the payment system through a data communication network 650, e.g., the Internet. The user device and the merchant device each generally include a memory, e.g., a random access memory (RAM), for storing instructions and data, and a processor for executing stored instructions. The user device and the merchant device can each include one or more components, e.g., software or hardware, that are configured to respectively determine a geographic location of the user device or the merchant device, using, for example, various geolocation techniques, e.g., a global positioning system (GPS). Further, the user device and the merchant device can each be any appropriate device operable to send and receive requests, messages, or other types of information over the network. Some examples of user devices include personal computers, cellular phones, handheld messaging devices, laptop computers, personal data assistants, tablet devices, and the like.
The network can include any appropriate network, including an intranet, the Internet, a cellular network, a local area network, a wide area network, or any other such network, or combination thereof. Components used for such a system can depend at least in part upon the type of network, the environment selected, or both. Protocols and components for communicating over such a network are well known and will not be discussed herein in detail. The payment system, the merchant device, and the user device can communicate over the network using wired or wireless connections, and combinations thereof.
As used in this specification, a financial transaction is a transaction that is conducted between a customer and a merchant at a point-of-sale. When paying for a financial transaction, the customer can provide the merchant with cash, a check, or credit card for the amount that is due. The merchant can interact with a point-of-sale device, e.g., merchant device, to process the financial transaction. During financial transactions, the point-of-sale device can collect data describing the financial transaction, including, for example, the amount of payment received from customers.
In some implementations, the payment system is configured to accept card-less payment transactions from customers, e.g., the customer. As used in this specification, a card-less payment transaction is a transaction conducted between the customer and a merchant at the point-of-sale during which a financial account of the customer is charged without the customer having to physically present a financial payment card to the merchant at the point-of-sale. That is, the merchant need not receive any details about the financial account, e.g., the credit card issuer or credit card number, for the transaction to be processed.
Before conducting card-less payment transactions, the customer typically creates a user account with the payment system. The customer can create the user account, for example, by interacting with a user application that is configured to perform card-less payment transactions and that is running on the user device. When creating a user account with the payment system, the customer will provide information of the customer, data describing a financial account of the customer, e.g., credit card number, expiration date, and a billing address. This user information can be securely stored by the payment system, for example, in a user information database. To accept card-less payment transactions, the merchant typically creates a merchant account with the payment system by providing information describing the merchant including, for example, a merchant name, contact information, e.g., telephone numbers, the merchant's geographic location address, and one or more financial accounts to which funds collected from users will be deposited. This merchant information can be securely stored by the payment system, for example, in a merchant information database.
The payment system is configured to perform card-less payment transactions. The payment system can include one or more servers that are configured to securely perform electronic financial transactions, e.g., electronic payment transactions, between a customer and a merchant, for example, through data communicated between the user device and the merchant device. Generally, when a customer and a merchant enter into an electronic financial transaction, the transaction is processed by transferring funds from a financial account associated with the user account to a financial account associated with the merchant account.
The payment system is configured to send and receive data to and from the user device and the merchant device. For example, the payment system can be configured to send data describing merchants to the user device using, for example, the information stored in the merchant information database 612. For example, the payment system can communicate data describing merchants that are within a threshold geographic distance from a geographic location of the user device, as described in this specification. The data describing merchants can include, for example, a merchant name, geographic location, contact information, and an electronic catalogue, e.g., a menu, that describes items that are available for purchase from the merchant.
In some embodiments, the payment system is configured to determine whether a geographic location of the user device is within a threshold geographic distance from a geographic location of the merchant device. The payment system can determine a geographic location of the user device using, for example, geolocation data provided by the user device. Similarly, the payment system can determine a geographic location of the merchant device using, for example, geolocation data provided by the merchant device or using a geographic address, e.g., street address, provided by the merchant. Depending on the implementation, the threshold geographic distance can be specified by the payment system or by the merchant.
Determining whether the user device is within a threshold geographic distance of the merchant device can be accomplished in different ways including, for example, determining whether the user device is within a threshold geographic radius of the merchant device, determining whether the user device is within a particular geofence, or determining whether the user device can communicate with the merchant device using a specified wireless technology, e.g., Bluetooth or Bluetooth low energy (BLE). In some embodiments, the payment system restricts card-less payment transactions between the customer and the merchant to situations where the geographic location of the user device is within a threshold geographic distance from a geographic location of the merchant device.
The payment system can also be configured to communicate with a computer system 616 of a card payment network, e.g., Visa or MasterCard, over the network, or over a different network, for example, to conduct electronic financial transactions. The computer system of the card payment network can communicate with a computer system 616 of a card issuer, e.g., a bank. There may be computer systems of other entities, e.g., the card acquirer, between the payment system and the computer system of the card issuer.
The customer operating the user device that is within a threshold geographic distance of the merchant can interact with a user application running on the user device to conduct a card-less payment transaction with the merchant. While interacting with the user application, the customer can select the merchant, from a listing of merchants, with whom the customer wants to enter into a card-less payment transaction. The user can select the merchant, for example, by selecting a “check in” option associated with the merchant. The user device can communicate data to the payment system indicating that the customer has checked in with the merchant. In response, the payment system can communicate data to notify the merchant device that the user has checked in. A merchant application running on the merchant device can notify the merchant that the user has electronically checked in with the merchant through a display screen of the merchant device.
Once checked in, the customer can collect, or request, items that are available for purchase from the merchant. When the customer is ready to enter into the card-less payment transaction, the customer can, for example, approach a point-of-sale for the merchant and identify him or herself. For example, the customer can verbally notify the merchant that the customer wants to enter into a card-less payment transaction and can provide the merchant with the customer's name. The merchant can then interact with the merchant application to select the customer, from a listing of customers that have checked in with the merchant, to initiate a card-less payment transaction for the items being purchased by the customer. For example, the merchant can determine a total amount to bill the customer for the items being purchased. The customer can verbally approve the total amount to be billed and, in response, the merchant can submit a request for a card-less payment transaction for the total amount to the payment system. In response, the payment system can obtain, for example, from the user information database, data describing a financial account associated with a user account of the customer to which the total amount will be billed.
The payment system can then communicate with the computer system of a card payment network to complete an electronic financial transaction for the total amount to be billed to the customer's financial account. Once the electronic financial transaction is complete, the payment system can communicate data describing the card-less payment transaction to the user device, e.g., an electronic receipt, which can, for example, notify the customer of the total amount billed to the user for the card-less payment transaction with the particular merchant.
For clarity of explanation, in some instances the present technology may be presented as including individual functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.
In some embodiments the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.
Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.
Devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include laptops, smart phones, small form factor personal computers, personal digital assistants, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.
The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.
Although a variety of examples and other information was used to explain aspects within the scope of the appended claims, no limitation of the claims should be implied based on particular features or arrangements in such examples, as one of ordinary skill would be able to use these examples to derive a wide variety of implementations. Further and although some subject matter may have been described in language specific to examples of structural features and/or method steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or acts. For example, such functionality can be distributed differently or performed in components other than those identified herein. Rather, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
3854036 | Gupta | Dec 1974 | A |
4035614 | Frattarola et al. | Jul 1977 | A |
4254441 | Fisher | Mar 1981 | A |
4591937 | Nakarai et al. | May 1986 | A |
4609957 | Gentet et al. | Sep 1986 | A |
4727544 | Brunner et al. | Feb 1988 | A |
4788420 | Chang et al. | Nov 1988 | A |
4845740 | Tokuyama et al. | Jul 1989 | A |
5173597 | Anglin | Dec 1992 | A |
5266789 | Anglin et al. | Nov 1993 | A |
5406627 | Thompson et al. | Apr 1995 | A |
5434395 | Storck et al. | Jul 1995 | A |
5434400 | Scherzer | Jul 1995 | A |
5463678 | Kepley, III et al. | Oct 1995 | A |
5589855 | Blumstein et al. | Dec 1996 | A |
5603078 | Henderson et al. | Feb 1997 | A |
5616904 | Fernadez | Apr 1997 | A |
5679943 | Schultz et al. | Oct 1997 | A |
5729591 | Bailey | Mar 1998 | A |
5763862 | Jachimowicz et al. | Jun 1998 | A |
5764742 | Howard et al. | Jun 1998 | A |
5850599 | Seiderman | Dec 1998 | A |
5878337 | Joao et al. | Mar 1999 | A |
5907801 | Albert et al. | May 1999 | A |
5945654 | Huang | Aug 1999 | A |
5991410 | Albert et al. | Nov 1999 | A |
5991749 | Morrill, Jr. | Nov 1999 | A |
D417442 | Butts et al. | Dec 1999 | S |
6006109 | Shin | Dec 1999 | A |
6010067 | Elbaum | Jan 2000 | A |
6021944 | Arakaki | Feb 2000 | A |
6032859 | Hughes et al. | Mar 2000 | A |
6061666 | Do et al. | May 2000 | A |
6095410 | Andersen et al. | Aug 2000 | A |
6129277 | Grant et al. | Oct 2000 | A |
6234389 | Valliani et al. | May 2001 | B1 |
6308227 | Kumar et al. | Oct 2001 | B1 |
6363139 | Zurek et al. | Mar 2002 | B1 |
6400517 | Murao | Jun 2002 | B1 |
6431445 | Deland et al. | Aug 2002 | B1 |
6476743 | Brown et al. | Nov 2002 | B1 |
6481623 | Grant et al. | Nov 2002 | B1 |
6497368 | Friend et al. | Dec 2002 | B1 |
6536670 | Postman et al. | Mar 2003 | B1 |
D477321 | Baughman | Jul 2003 | S |
6612488 | Suzuki | Sep 2003 | B2 |
6813608 | Baranowski | Nov 2004 | B1 |
6832721 | Fujll | Dec 2004 | B2 |
6850147 | Prokoski et al. | Feb 2005 | B2 |
6868391 | Hultgren | Mar 2005 | B1 |
6896182 | Sakaguchi | May 2005 | B2 |
6944782 | von Mueller et al. | Sep 2005 | B2 |
6979231 | Shinohara | Dec 2005 | B2 |
7003316 | Elias et al. | Feb 2006 | B1 |
7013149 | Vetro et al. | Mar 2006 | B2 |
7149296 | Brown et al. | Dec 2006 | B2 |
7167711 | Dennis | Jan 2007 | B1 |
7252232 | Fernandes et al. | Aug 2007 | B2 |
7309012 | Von Mueller et al. | Dec 2007 | B2 |
7324836 | Steenstra et al. | Jan 2008 | B2 |
7363054 | Elias et al. | Apr 2008 | B2 |
D575056 | Tan | Aug 2008 | S |
7409234 | Glezerman | Aug 2008 | B2 |
7424732 | Matsumoto et al. | Sep 2008 | B2 |
7433452 | Taylor et al. | Oct 2008 | B2 |
7505762 | Onyon et al. | Mar 2009 | B2 |
7506812 | von Mueller et al. | Mar 2009 | B2 |
D590828 | Sherrod et al. | Apr 2009 | S |
7520430 | Stewart et al. | Apr 2009 | B1 |
7581678 | Narendra et al. | Sep 2009 | B2 |
7600673 | Stoutenburg et al. | Oct 2009 | B2 |
D607000 | Cheng et al. | Dec 2009 | S |
7668308 | Wurtz | Feb 2010 | B1 |
7703676 | Hart et al. | Apr 2010 | B2 |
7708189 | Cipriano | May 2010 | B1 |
7757953 | Hart et al. | Jul 2010 | B2 |
7793834 | Hachey et al. | Sep 2010 | B2 |
7810729 | Morley, Jr. | Oct 2010 | B2 |
7869591 | Nagel et al. | Jan 2011 | B1 |
7945494 | Williams | May 2011 | B2 |
8011587 | Johnson et al. | Sep 2011 | B2 |
8015070 | Sinha et al. | Sep 2011 | B2 |
D646264 | Dong | Oct 2011 | S |
D653664 | Turnbull et al. | Feb 2012 | S |
8132670 | Chen | Mar 2012 | B1 |
8231055 | Wen | Jul 2012 | B2 |
8297507 | Kayani | Oct 2012 | B2 |
8302860 | McKelvey | Nov 2012 | B2 |
8336771 | Tsai et al. | Dec 2012 | B2 |
D675618 | Behar et al. | Feb 2013 | S |
8376239 | Humphrey | Feb 2013 | B1 |
D677667 | Smith et al. | Mar 2013 | S |
D679714 | Smith et al. | Apr 2013 | S |
D680537 | Miller et al. | Apr 2013 | S |
8413901 | Wen | Apr 2013 | B2 |
8452004 | Lee | May 2013 | B2 |
D686208 | Miller et al. | Jul 2013 | S |
8500010 | Marcus et al. | Aug 2013 | B1 |
8500018 | McKelvey et al. | Aug 2013 | B2 |
8560823 | Aytek et al. | Oct 2013 | B1 |
8571989 | Dorsey et al. | Oct 2013 | B2 |
8573486 | McKelvey et al. | Nov 2013 | B2 |
8573487 | McKelvey | Nov 2013 | B2 |
8573489 | Dorsey et al. | Nov 2013 | B2 |
8584946 | Morley, Jr. | Nov 2013 | B2 |
8584956 | Wilson et al. | Nov 2013 | B2 |
8602305 | Dorsey et al. | Dec 2013 | B2 |
8612352 | Dorsey et al. | Dec 2013 | B2 |
8615445 | Dorsey et al. | Dec 2013 | B2 |
8640953 | Dorsey et al. | Feb 2014 | B2 |
D700606 | Lo | Mar 2014 | S |
8662389 | Dorsey et al. | Mar 2014 | B2 |
8678277 | Dorsey et al. | Mar 2014 | B2 |
D703211 | Weller et al. | Apr 2014 | S |
8701996 | Dorsey et al. | Apr 2014 | B2 |
8701997 | Dorsey et al. | Apr 2014 | B2 |
D706266 | Rotsaert | Jun 2014 | S |
8740072 | Dorogusker | Jun 2014 | B1 |
8763900 | Marcus et al. | Jul 2014 | B2 |
D711876 | McWilliam et al. | Aug 2014 | S |
8794517 | Templeton et al. | Aug 2014 | B1 |
D712892 | Hong et al. | Sep 2014 | S |
8820650 | Wilson et al. | Sep 2014 | B2 |
8840017 | Chan et al. | Sep 2014 | B2 |
8840024 | McKelvey et al. | Sep 2014 | B2 |
8870070 | McKelvey et al. | Oct 2014 | B2 |
8870071 | McKelvey | Oct 2014 | B2 |
8876003 | McKelvey | Nov 2014 | B2 |
8910868 | Wade et al. | Dec 2014 | B1 |
8931699 | Wade et al. | Jan 2015 | B1 |
D724094 | Blochinger et al. | Mar 2015 | S |
D725655 | Debaigue et al. | Mar 2015 | S |
8967465 | Wade et al. | Mar 2015 | B1 |
D726171 | Edwards | Apr 2015 | S |
9016570 | Gluck | Apr 2015 | B1 |
9016572 | Babu et al. | Apr 2015 | B2 |
D728549 | Su et al. | May 2015 | S |
D728568 | Debaigue et al. | May 2015 | S |
D731493 | Mills | Jun 2015 | S |
9063737 | Babu et al. | Jun 2015 | B2 |
D740820 | Templeton et al. | Oct 2015 | S |
9218517 | Morley, Jr. | Dec 2015 | B2 |
9237401 | Modi et al. | Jan 2016 | B2 |
9256769 | Lamfalusi et al. | Feb 2016 | B1 |
9256770 | Edwards | Feb 2016 | B1 |
9355285 | Wade et al. | May 2016 | B1 |
D762651 | Edwards et al. | Aug 2016 | S |
9576159 | Templeton et al. | Feb 2017 | B1 |
9633236 | Wade | Apr 2017 | B1 |
9760740 | Edwards | Sep 2017 | B1 |
20010001856 | Gould et al. | May 2001 | A1 |
20020002507 | Hatakeyama | Jan 2002 | A1 |
20020017568 | Grant et al. | Feb 2002 | A1 |
20020030871 | Anderson et al. | Mar 2002 | A1 |
20020073304 | Marsh et al. | Jun 2002 | A1 |
20020077974 | Ortiz | Jun 2002 | A1 |
20020099648 | DeVoe et al. | Jul 2002 | A1 |
20020108062 | Nakajima et al. | Aug 2002 | A1 |
20020165462 | Westbrook et al. | Nov 2002 | A1 |
20020169541 | Bouve et al. | Nov 2002 | A1 |
20020188535 | Chao et al. | Dec 2002 | A1 |
20030089772 | Yuan | May 2003 | A1 |
20030132300 | Dilday et al. | Jul 2003 | A1 |
20030135463 | Brown et al. | Jul 2003 | A1 |
20030144040 | Liu et al. | Jul 2003 | A1 |
20040011650 | Zenhausern et al. | Jan 2004 | A1 |
20040012875 | Wood | Jan 2004 | A1 |
20040033726 | Kao | Feb 2004 | A1 |
20040041911 | Odagiri et al. | Mar 2004 | A1 |
20040058705 | Morgan et al. | Mar 2004 | A1 |
20040087339 | Goldthwaite et al. | May 2004 | A1 |
20040093496 | Colnot | May 2004 | A1 |
20040104268 | Bailey | Jun 2004 | A1 |
20040127256 | Goldthwaite et al. | Jul 2004 | A1 |
20040128256 | Dhanjal et al. | Jul 2004 | A1 |
20040151026 | Naso et al. | Aug 2004 | A1 |
20040178326 | Hamilton et al. | Sep 2004 | A1 |
20040204074 | Desai | Oct 2004 | A1 |
20040204082 | Abeyta | Oct 2004 | A1 |
20040230489 | Goldthwaite et al. | Nov 2004 | A1 |
20040230526 | Praisner | Nov 2004 | A1 |
20040235524 | Abuhamdeh | Nov 2004 | A1 |
20050009004 | Xu et al. | Jan 2005 | A1 |
20050010702 | Saito et al. | Jan 2005 | A1 |
20050023348 | Lucas et al. | Feb 2005 | A1 |
20050077870 | Ha et al. | Apr 2005 | A1 |
20050156037 | Wurzburg | Jul 2005 | A1 |
20050156038 | Wurzburg et al. | Jul 2005 | A1 |
20050164631 | Jin | Jul 2005 | A1 |
20050167496 | Morley, Jr. et al. | Aug 2005 | A1 |
20050194452 | Nordentoft et al. | Sep 2005 | A1 |
20050209719 | Beckert et al. | Sep 2005 | A1 |
20050219728 | Durbin et al. | Oct 2005 | A1 |
20050236480 | Vrotsos et al. | Oct 2005 | A1 |
20050242173 | Suzuki | Nov 2005 | A1 |
20050247787 | Von Mueller et al. | Nov 2005 | A1 |
20050283403 | Ramirez | Dec 2005 | A1 |
20060000917 | Kim et al. | Jan 2006 | A1 |
20060049255 | Von Mueller et al. | Mar 2006 | A1 |
20060094481 | Gullickson | May 2006 | A1 |
20060122902 | Petrov et al. | Jun 2006 | A1 |
20060123138 | Perdomo et al. | Jun 2006 | A1 |
20060152276 | Barksdale | Jul 2006 | A1 |
20060208066 | Finn et al. | Sep 2006 | A1 |
20060219776 | Finn | Oct 2006 | A1 |
20060223580 | Antonio et al. | Oct 2006 | A1 |
20060234771 | Shavrov | Oct 2006 | A1 |
20060273158 | Suzuki | Dec 2006 | A1 |
20070063048 | Havens et al. | Mar 2007 | A1 |
20070067833 | Colnot | Mar 2007 | A1 |
20070100651 | Ramer et al. | May 2007 | A1 |
20070124211 | Smith | May 2007 | A1 |
20070155430 | Cheon et al. | Jul 2007 | A1 |
20070174080 | Outwater | Jul 2007 | A1 |
20070201492 | Kobayashi | Aug 2007 | A1 |
20070221728 | Ferro et al. | Sep 2007 | A1 |
20070236336 | Borcherding | Oct 2007 | A1 |
20070244811 | Tumminaro | Oct 2007 | A1 |
20070250623 | Hickey et al. | Oct 2007 | A1 |
20070255620 | Tumminaro et al. | Nov 2007 | A1 |
20070255643 | Capuano et al. | Nov 2007 | A1 |
20070255653 | Tumminaro et al. | Nov 2007 | A1 |
20070287498 | Wang et al. | Dec 2007 | A1 |
20080011850 | Henry | Jan 2008 | A1 |
20080017712 | Hart et al. | Jan 2008 | A1 |
20080027815 | Johnson et al. | Jan 2008 | A1 |
20080040265 | Rackley, III et al. | Feb 2008 | A1 |
20080040274 | Uzo | Feb 2008 | A1 |
20080059370 | Sada et al. | Mar 2008 | A1 |
20080059375 | Abifaker | Mar 2008 | A1 |
20080103972 | Lane | May 2008 | A1 |
20080147564 | Singhal | Jun 2008 | A1 |
20080172306 | Schorr et al. | Jul 2008 | A1 |
20080177662 | Alton et al. | Jul 2008 | A1 |
20080208762 | Arthur et al. | Aug 2008 | A1 |
20080238610 | Rosenberg | Oct 2008 | A1 |
20080249939 | Veenstra | Oct 2008 | A1 |
20080275779 | Lakshminarayanan | Nov 2008 | A1 |
20080294766 | Wang et al. | Nov 2008 | A1 |
20090048978 | Ginter et al. | Feb 2009 | A1 |
20090068982 | Chen et al. | Mar 2009 | A1 |
20090098908 | Silverbrook et al. | Apr 2009 | A1 |
20090100168 | Harris | Apr 2009 | A1 |
20090104920 | Moon et al. | Apr 2009 | A1 |
20090117883 | Coffing et al. | May 2009 | A1 |
20090119190 | Realini | May 2009 | A1 |
20090125429 | Takayama | May 2009 | A1 |
20090144161 | Fisher | Jun 2009 | A1 |
20090159681 | Mullen et al. | Jun 2009 | A1 |
20090166422 | Biskupski | Jul 2009 | A1 |
20090172384 | Anson | Jul 2009 | A1 |
20090180354 | Sander et al. | Jul 2009 | A1 |
20090187492 | Hammad et al. | Jul 2009 | A1 |
20090302806 | Lindlar et al. | Dec 2009 | A1 |
20100063893 | Townsend | Mar 2010 | A1 |
20100108762 | Morley, Jr. | May 2010 | A1 |
20100127857 | Kilmurray et al. | May 2010 | A1 |
20100128900 | Johnson | May 2010 | A1 |
20100184479 | Griffin, Jr. | Jul 2010 | A1 |
20100222000 | Sauer et al. | Sep 2010 | A1 |
20100241838 | Cohen et al. | Sep 2010 | A1 |
20100243732 | Wallner | Sep 2010 | A1 |
20100260341 | Sander et al. | Oct 2010 | A1 |
20100289390 | Kenney | Nov 2010 | A1 |
20100314446 | Morley, Jr. | Dec 2010 | A1 |
20110033910 | Maho et al. | Feb 2011 | A1 |
20110053560 | Jain et al. | Mar 2011 | A1 |
20110062235 | Morley, Jr. | Mar 2011 | A1 |
20110084131 | McKelvey | Apr 2011 | A1 |
20110084139 | McKelvey et al. | Apr 2011 | A1 |
20110084140 | Wen | Apr 2011 | A1 |
20110137803 | Willins | Jun 2011 | A1 |
20110161235 | Beenau et al. | Jun 2011 | A1 |
20110165896 | Stromberg et al. | Jul 2011 | A1 |
20110174879 | Morley, Jr. | Jul 2011 | A1 |
20110180601 | Morley, Jr. | Jul 2011 | A1 |
20110191196 | Orr et al. | Aug 2011 | A1 |
20110198395 | Chen | Aug 2011 | A1 |
20110202463 | Powell | Aug 2011 | A1 |
20110231272 | Englund et al. | Sep 2011 | A1 |
20110258120 | Weiss | Oct 2011 | A1 |
20110313880 | Paul et al. | Dec 2011 | A1 |
20120008851 | Pennock et al. | Jan 2012 | A1 |
20120011024 | Dorsey et al. | Jan 2012 | A1 |
20120011071 | Pennock et al. | Jan 2012 | A1 |
20120012653 | Johnson et al. | Jan 2012 | A1 |
20120016794 | Orr et al. | Jan 2012 | A1 |
20120026018 | Lin | Feb 2012 | A1 |
20120052910 | Mu et al. | Mar 2012 | A1 |
20120066079 | Falzone | Mar 2012 | A1 |
20120095869 | McKelvey | Apr 2012 | A1 |
20120095870 | McKelvey | Apr 2012 | A1 |
20120097739 | Babu et al. | Apr 2012 | A1 |
20120097740 | Lamba et al. | Apr 2012 | A1 |
20120118956 | Lamba | May 2012 | A1 |
20120118959 | Sather et al. | May 2012 | A1 |
20120118960 | Sather et al. | May 2012 | A1 |
20120126005 | Dorsey et al. | May 2012 | A1 |
20120126006 | Dorsey et al. | May 2012 | A1 |
20120126007 | Lamba | May 2012 | A1 |
20120126010 | Babu et al. | May 2012 | A1 |
20120126011 | Lamba et al. | May 2012 | A1 |
20120126012 | Lamba et al. | May 2012 | A1 |
20120126013 | Sather et al. | May 2012 | A1 |
20120126014 | Sather et al. | May 2012 | A1 |
20120130903 | Dorsey et al. | May 2012 | A1 |
20120132712 | Babu et al. | May 2012 | A1 |
20120138683 | Sather et al. | Jun 2012 | A1 |
20120154561 | Chari | Jun 2012 | A1 |
20120168505 | Sather et al. | Jul 2012 | A1 |
20120234918 | Lindsay | Sep 2012 | A1 |
20120246074 | Annamalai et al. | Sep 2012 | A1 |
20120255996 | Ahmed et al. | Oct 2012 | A1 |
20120259651 | Mallon et al. | Oct 2012 | A1 |
20120270528 | Goodman | Oct 2012 | A1 |
20130021046 | Prentice et al. | Jan 2013 | A1 |
20130031003 | Dorsey et al. | Jan 2013 | A1 |
20130031004 | Dorsey et al. | Jan 2013 | A1 |
20130087614 | Limtao et al. | Apr 2013 | A1 |
20130137367 | Fisher | May 2013 | A1 |
20130200147 | Dorsey et al. | Aug 2013 | A1 |
20130200148 | Dorsey et al. | Aug 2013 | A1 |
20130200149 | Dorsey et al. | Aug 2013 | A1 |
20130200153 | Dorsey et al. | Aug 2013 | A1 |
20130200154 | Dorsey et al. | Aug 2013 | A1 |
20130204788 | Dorsey et al. | Aug 2013 | A1 |
20130204791 | Dorsey et al. | Aug 2013 | A1 |
20130204792 | Dorsey et al. | Aug 2013 | A1 |
20130207481 | Gobburu et al. | Aug 2013 | A1 |
20130254117 | von Mueller et al. | Sep 2013 | A1 |
20130254118 | Dorsey et al. | Sep 2013 | A1 |
20130254574 | Zacchio et al. | Sep 2013 | A1 |
20130278122 | Edwards | Oct 2013 | A1 |
20130290762 | Pawar | Oct 2013 | A1 |
20130299575 | McKelvey et al. | Nov 2013 | A1 |
20130304244 | Ojanpera | Nov 2013 | A1 |
20130320089 | Marcus et al. | Dec 2013 | A1 |
20140001257 | Dorsey et al. | Jan 2014 | A1 |
20140001263 | Babu et al. | Jan 2014 | A1 |
20140017955 | Lo et al. | Jan 2014 | A1 |
20140018016 | Chang | Jan 2014 | A1 |
20140061301 | Cho et al. | Mar 2014 | A1 |
20140076964 | Morley, Jr. | Mar 2014 | A1 |
20140089205 | Kapur et al. | Mar 2014 | A1 |
20140097242 | McKelvey | Apr 2014 | A1 |
20140124576 | Zhou | May 2014 | A1 |
20140131442 | Morrow et al. | May 2014 | A1 |
20140144983 | Dorsey et al. | May 2014 | A1 |
20140203082 | Huh | Jul 2014 | A1 |
20140258132 | Swamy et al. | Sep 2014 | A1 |
20140265642 | Utley et al. | Sep 2014 | A1 |
20140295761 | Lo | Oct 2014 | A1 |
20140297539 | Swamy et al. | Oct 2014 | A1 |
20150078560 | Ilango et al. | Mar 2015 | A1 |
20150100495 | Salama et al. | Apr 2015 | A1 |
20150149992 | Wade et al. | May 2015 | A1 |
20150161419 | Wade et al. | Jun 2015 | A1 |
20150199677 | Wade et al. | Jul 2015 | A1 |
20150200590 | Tanzawa | Jul 2015 | A1 |
20160055478 | Skoog | Feb 2016 | A1 |
20160070940 | Lamba et al. | Mar 2016 | A1 |
20160132703 | Lamfalusi et al. | May 2016 | A1 |
20160188915 | Babu et al. | Jun 2016 | A1 |
20160203466 | Lamba et al. | Jul 2016 | A1 |
20160203667 | Lamba et al. | Jul 2016 | A1 |
20160239691 | Wade et al. | Aug 2016 | A1 |
20160371513 | Lamba et al. | Dec 2016 | A1 |
Number | Date | Country |
---|---|---|
2 812 251 | Apr 2012 | CA |
2 932 849 | Jun 2015 | CA |
2 920 589 | Aug 2016 | CA |
2459833 | Nov 2001 | CN |
2543289 | Apr 2003 | CN |
1682240 | Oct 2005 | CN |
1860730 | Nov 2006 | CN |
101520928 | Sep 2009 | CN |
302341093 | Mar 2013 | CN |
302526592 | Aug 2013 | CN |
1 145 766 | Oct 2001 | EP |
2 693 298 | Feb 2014 | EP |
3 091 474 | Nov 2016 | EP |
1211124 | May 2016 | HK |
2003-108777 | Apr 2003 | JP |
2004-078662 | Mar 2004 | JP |
2005-063869 | Mar 2005 | JP |
2005-242550 | Sep 2005 | JP |
2005-269172 | Sep 2005 | JP |
2009-199649 | Sep 2009 | JP |
2001-313714 | Nov 2011 | JP |
2013-518344 | May 2013 | JP |
10-0452161 | Oct 2004 | KR |
10-2005-0077659 | Aug 2005 | KR |
10-2008-0039330 | May 2008 | KR |
0137199 | May 2001 | WO |
0165827 | Sep 2001 | WO |
02084548 | Oct 2002 | WO |
2007070592 | Jun 2007 | WO |
2009128483 | Oct 2009 | WO |
2010097711 | Sep 2010 | WO |
2010111130 | Sep 2010 | WO |
2010135174 | Nov 2010 | WO |
2011047028 | Apr 2011 | WO |
2011047030 | Apr 2011 | WO |
2012051070 | Apr 2012 | WO |
2013009891 | Jan 2013 | WO |
2013074499 | May 2013 | WO |
2015081002 | Jun 2015 | WO |
2015089301 | Jun 2015 | WO |
2016028823 | Feb 2016 | WO |
Entry |
---|
Majekodunmi, Muyinat O. Utilizing automatic identification tracking systems to compile operational field and structure data. University of Maryland, College Park, ProQuest Dissertations Publishing, 2014. |
Non-Final Office Action dated Nov. 21, 2013, for U.S. Appl. No. 14/052,009, of Wilson, M., et al., filed Oct. 11, 2013. |
Non-Final Office Action dated Jul. 19, 2012, for U.S. Appl. No. 12/903,758, of Wilson, M., et al., filed Oct. 13, 2010. |
“Reading magnetic cards (almost) for free,” Lekernel's Scrapbook, (“Lekernel”), Jan. 26, 2009, Retrieved from the Internet URL: http://lekernel.net/blog/?p=12, on May 5, 2011, pp. 1-2. |
“MSR500EX (Mini123EX) Portable Magnetic Stripe Card Reader,” TYNER, Apr. 27, 2007, Retrieved from the Internet URL: http://www.tyner.com/magnetic/msr500ex.htm, on Apr. 22, 2011, pp. 1-3. |
Padilla, L., “Turning your mobile into a magnetic stripe reader,” Retrieved from the Internet URL: http://www.gae.ucm.es/˜padilla/extrawork/mobilesoundtrack.html, on Feb. 7, 2011, pp. 1-4. |
Padilla, L., “Magnetic stripe reader circuit,” Jan. 28, 1997, Retrieved from the Internet URL: http://www.gae.ucm.es/˜padilla/extraworklmagamp.html, on May 5, 2011, pp. 1-7. |
Padilla, L. “The simplest magnetic stripe reader,” Jan. 27, 2003, Retrieved from the Internet URL: www.gae.ucm.esi˜padilla/extrawork/soundtrack.html, on Dec. 21, 2009, pp. 1-5. |
“Travel industry targeted for Palm PDA card reader,” Retrieved from the Internet URL: http://www.m-travel.com/news/2001/08/travel_industry.html, on Apr. 19, 2011, pp. 1-2. |
“Semtek to target healthcare with HandEra PDAs and PDA swipe card reader,” Aug. 29, 2001, Retrieved from the Internet URL: http://www.pdacortex.com/semtek.htm, on Apr. 19, 2011, pp. 1-2. |
“Semtek 3913 Insert Magnetic Card Reader 20 Pin Serial RS232,” Product description, RecycledGoods.com, Retrieved from the Internet URL: http://www.recycledgoods.com/products/Semtek-3913-Insert-Magnetic-Card-Reader-20-Pi . . . , on Apr. 19, 2011, pp. 1-3. |
“Credit Card Swiper and Reader for iPhone, iPad, Blackberry, Android and more,” Retrieved from the Internet URL: http://hubpages.com/hub/Credit-Card-Swiper-and-Reader-for-iPhone-iPad-Blackberry-An . . . , on Apr. 20, 2011, pp. 1-2. |
Titlow, J.P., “ROAM pay is like Square for Blackberry (Plus Android, iOS and Desktops),” Dec. 1, 2010, Retrieved from the Internet URL: http://www.readwriteweb.com/biz/2010/12/roampay-is-like-square-for-bla.php, on Apr. 20, 2011, pp. 1-12. |
Veneziani, V., “Use a cellphone as a magnetic card reader,” Apr. 15, 2005, Retrieved from the Internet URL: http://hackaday.com/2005/04/15/use a-cellphone-as-a-magnetic-card . . . , on Feb. 7, 2011, pp. 1-10. |
Buttell, A.E., “Merchants eye mobile phones to transact card payments,” Feb. 3, 2010, Retrieved from the Internet URL: http://www.merchantaccountguide.com/merchant-account-news/cell-phone-credit-card-mer . . . , on Feb. 8, 2011, pp. 1-3. |
“USB Magnetic Stripe Credit/Card Track-2 Reader and Writer (75/210BPI),” Deal Extreme (dealextreme.com), Nov. 15, 2008, Retrieved from the Internet URL: http://www.dealextreme.com/p/usb-magnetic-stripe-credit-debit-card-track-2-reader-and-wr . . . , on Feb. 8, 2011, pp. 1-3. |
“Mophie Marketplace Magnetic Strip Reader/Case for iPhone 3G & 3GS—Grey,” J&R (JR.com), Retrieved from the Internet URL: http://www.jr.com/mophie/pe/MPE_MPIP3GBLK, on Feb. 8, 2011, pp. 1-1. |
“Barcode scanner and Magnetic Stripe Reader (MSR) for Pocke . . . ,” Tom's Hardware (tomshardware.com), Retrieved from the Internet URL: http://www.tomshardware.com/forum/24068-36-barcode-scanner-magnetic-stripe-reader-po . . . , on Feb. 8, 2011, pp. 1-2. |
“A Magnetic Stripe Reader—Read Credit Cards & Driver Licences!,” Articlesbase (articlesbase.com), Sep. 7, 2009, Retrieved from the Internet URL: http://www.articlesbase.com/electronics-articles/a-magnetic-stripe-reader-read-credit-cards- . . . , on Feb. 8, 2011, pp. 1-3. |
Jones, R., “U.S. Credit Cards to get a high-tech makeover,” Oct. 22, 2010, Retrieved from the Internet URL: http://lifeine.today.com/_news/2010/10/22/5334208-us-credit-cards-to-get-a-high-tech-mak . . . , on Feb. 8, 2011, pp. 1-8. |
“Arduino magnetic stripe decoder,” Instructables, Retrieved from the Internet URL: http://www.instructables.com/id/Arduino-magneticstripe-decorded, on Feb. 8, 2011, pp. 1-5. |
“Magnetic Stripe Reader (MSR) MSR7000-100R,” Motorola Solutions, Retrieved from the Internet URL: http://www.motorola.com/business/US-EN/MSR7000-100R_US-EN.do?vgnextoid=164fc3 . . . , on Feb. 8, 2011, pp. 1-1. |
“Pay@PC,” Retrieved from the Internet URL: http://www.merchantanywhere.com/PAY_AT_PCT@PC.htm, on Feb. 11, 2011, pp. 1-2. |
“Get paid on the spot from your mobile phone,” Retrieved from the Internet URL: http://payments.intuit.com/products/basic-payment-solutions/mobile-credit-card-processin . . . , on Feb. 11, 2011, pp. 1-3. |
“TOUCH-PAY Wireless Credit Card Processing,” MerchantSeek, Retrieved from the Internet URL: http://www.merchantseek.com/wireless-credit-card-processing.htm, on Feb. 11, 2011, pp. 1-5. |
“Announcement: Semtek Introduces Side Swipe II Card Reader for Wireless Devices,” Brighthand, Retrieved from the Internet URL: http://forum.brighthand.com/pdas-handhelds/173285-announcement-semtek-introduces-sid . . . , on Apr. 19, 2011, pp. 1-2. |
Grandison, K., “vTerminal Credit Card Processing App for AuthorizeNet and PayPal Payflow Pro for Curve 8350 8500 8900 and Bold 9000,” Retrieved from the Internet URL: http://www.4blackberry.net/tag/business-tools/vterminal-credit-card-processing-app-for-authorizenet-and-paypal-payflow-pro-for-curve-8350-8500-890-download-2075.html, on Mar. 30, 2015, pp. 1-4. |
Harris, A., “Magnetic Stripe Card Spoofer,” Aug. 4, 2008, Retrieved from the Internet URL: http://hackaday.com/2008/08/04/magnetic-stripe-card-spoofer/, on Apr. 25, 2011, pp. 1-11. |
“Headphone Jack (3.5mm),” Retrieved from the Internet URL: http://www.phonescoop.com/glossary/term.php?gid=440, on May 5, 2011, pp. 1-1. |
“2.5mm Headset Jack,” Retrieved from the Internet URL: http://www.phonescoop.com/glossary/term.php?gid=360, on May 5, 2011, pp. 1-1. |
“Reference Designations for Electrical and Electronics Parts and Equipment,” Engineering Drawing and Related Documentation Practices, ASME Y14.44/2008, The American Society of Mechanical Engineers, Nov. 21, 2008, pp. 1-31. |
Acidus, “Mag-stripe Interfacing—A Lost Art,” Retrieved from the Internet URL: http://www.scribd.com/doc/18236182/Magstripe-Interfacing#open_ . . . , on Feb. 7, 2011, pp. 1-4. |
“Mag-stripe readers the hunt for a homebrew mag-stripe reader that'll work with modern,” Jan. 16, 2009, Retrieved from the Internet URL: http://www.hak5.org/forums/index.php?showtopic=11563&st=20, on Apr. 25, 2011, pp. 1-6. |
Kuo, Y-S et al., “Hijacking Power and Bandwidth from the Mobile Phone's Audio Interface,” Proceedings of the First ACM Symposium on Computing for Development, (DEV'10), Dec. 17, 2010, pp. 1-10. |
Website: www.alexwinston.com, Aug. 31, 2009, pp. 1-5. |
“Magnetic Card Reader,” lekernel.net˜scrapbook, Retrieved from the Internet URL: http://lekernel.net/scrapbook/old/cardreader.html, on Apr. 25, 2011, pp. 1-4. |
“Magnetic stripe reader/writer,” Retrieved from the Internet URL: http://www.gae.ucm.es/-padilla/extrawork/stripe.html, on Dec. 21, 2009, pp. 1-2. |
Lucks, S., “Two-Pass Authenticated Encryption Faster than Generic Composition,” H. Gilbert and H. Handschuh (Eds.): FSE 2005, LNCS 3557, © International Association for Cryptologic Research 2005, pp. 284-298. |
Bauer, G.R. et al., “Comparing Block Cipher Modes of Operation on MICAz Sensor Nodes,” 17th Euromicro International Conference on Parallel, Distributed and Network-based Processing, 2009, Feb. 18-20, 2009, pp. 371-378. |
European Search Report and Opinion for European Patent Application No. 11 786 731.7, dated Mar. 28, 2014. |
Office Action for European Patent Application No. 11 786 731.7, dated Jul. 16, 2015. |
Non-Final Office Action dated Sep. 30, 2011, for U.S. Appl. No. 12/903,753, of McKelvey, J., et al., filed Oct. 13, 2010. |
Final Office Action dated Jul. 6, 2012, for U.S. Appl. No. 12/903,753, of McKelvey, J., et al., filed Oct. 13, 2010. |
Non-Final Office Action dated Jul. 8, 2013, for U.S. Appl. No. 12/903,753, of McKelvey, J., et al., filed Oct. 13, 2010. |
Notice of Allowance dated Oct. 10, 2013, for U.S. Appl. No. 12/903,753, of Mckelvey, J., filed Oct. 13, 2010. |
Final Office Action dated Apr. 24, 2013, for U.S. Appl. No. 12/903,758, of Wilson, M., et al., filed Oct. 13, 2010. |
Notice of Allowance dated Aug. 6, 2013, for U.S. Appl. No. 12/903,758, of Wilson, M., et al., filed Oct. 13, 2010. |
Notice of Allowance dated Apr. 4, 2014, for U.S. Appl. No. 14/052,009, of Wilson, M., et al., filed Oct. 11, 2013. |
Notice of Allowance dated Jul. 30, 2014, for U.S. Appl. No. 14/052,009, of Wilson, M., et al., filed Oct. 11, 2013. |
Non-Final Office Action dated Sep. 30, 2011, for U.S. Appl. No. 13/010,976, of Babu, A. R., et al., filed Jan. 21, 2011. |
Final Office Action dated Jun. 12, 2012, for U.S. Appl. No. 13/010,976, of Babu, A. R., et al., filed Jan. 21, 2011. |
Advisory Action dated Aug. 24, 2012, for U.S. Appl. No. 13/010,976, of Babu, A. R., et al., filed Jan. 21, 2011. |
Non-Final Office Action dated Aug. 15, 2014, for U.S. Appl. No. 13/010,976, of Babu, A. R., et al., filed Jan. 21, 2011. |
Notice of Allowance dated Dec. 24, 2014, for U.S. Appl. No. 13/010,976, of Babu, A. R., et al., filed Jan. 21, 2011. |
Non-Final Office Action dated Apr. 2, 2014, for U.S. Appl. No. 14/012,655, of McKelvey, J., filed Aug. 28, 2013. |
Final Office Action dated Aug. 15, 2014, for U.S. Appl. No. 14/012,655, of McKelvey, J., filed Aug. 28, 2013. |
Non-Final Office Action dated Jan. 20, 2015, for U.S. Appl. No. 14/012,655, of McKelvey, J., filed Aug. 28, 2013. |
Notice of Allowance dated Sep. 1, 2015, for U.S. Appl. No. 13/298,487, of Babu, A., et al., filed Nov. 17, 2011. |
Non-Final Office Action dated Apr. 29, 2013, for U.S. Appl. No. 13/298,487, of Babu, A., et al., filed Nov. 17, 2011. |
Final Office Action dated Aug. 22, 2013, for U.S. Appl. No. 13/298,487, of Babu, A., et al., filed Nov. 17, 2011. |
Advisory Action dated Oct. 22, 2013, for U.S. Appl. No. 13/298,487, of Babu, A., et al., filed Nov. 17, 2011. |
Non-Final Office Action dated Aug. 21, 2014, for U.S. Appl. No. 13/298,487, of Babu, A., et al., filed Nov. 17, 2011. |
Final Office Action dated Mar. 18, 2015, for U.S. Appl. No. 13/298,487, of Babu, A., et al., filed Nov. 17, 2011. |
Non-Final Office Action dated Feb. 20, 2015, for U.S. Appl. No. 14/512,104, of Templeton, T., et al., filed Oct. 10, 2014. |
International Search Report and Written Opinion for PCT Application No. PCT/US2010/052483, dated Jun. 10, 2011. |
International Search Report and Written Opinion for PCT Application No. PCT/US2011/055386, dated Feb. 22, 2012. |
European Search Report and Opinion for European Application No. 11833172.7, dated Apr. 22, 2014. |
International Search Report and Written Opinion for PCT Application No. PCT/US2014/069788, dated May 14, 2015. |
International Search Report and Written Opinion for PCT Application No. PCT/US2012/064782, dated Feb. 26, 2013. |
International Search Report and Written Opinion for PCT Application No. PCT/US2010/052481, dated Jun. 23, 2011. |
International Search Report and Written Opinion for PCT Application No. PCT/US2014/067074, dated Mar. 15, 2015. |
Examination Report for Canadian Application No. 2,812,594, dated Feb. 24, 2015. |
Examination Report No. 1 for Australian Application No. 201415781, dated Feb. 23, 2015. |
“Review: Square, Inc. Square Credit Card Reader (2013),” iLounge, Retrieved from the Internet URL: http://www.ilounge.com/index.php/reviews/entry/square-inc.-square-credit-card-reader-2013/, on Jan. 16, 2014, pp. 3. |
“TUAW The Unofficial Apple Weblog, Square credit card reader loses weight, gains accuracy”, Retrieved from the Internet URL: http://www.tuaw.com/2013/12/09/square-credit-card--reader-loses-weight-gains-accuracy/, on Dec. 9, 2013, p. 1. |
Examination Report No. 2 for Australian Application No. 201415781, dated Aug. 13, 2015 (Registration No. 359005). |
Ryan, P., “Plug and Pay: A Gallery of 26 Mobile Card Readers,” Aug. 20, 2013, Retrieved from the Internet URL: http://bankinnovation.net/2013/08/plug-and-pay-a-gallery-of-26-mobile-card-readers/, on Feb. 19, 2015, pp. 1-12. |
Notification of Registration of a Design for Australian Application No. 201415781, dated Nov. 27, 2014 (Registration No. 359005). |
First Examination Report for Indian Design Application No. 267386, dated Feb. 5, 2015. |
Non-Final Office Action dated Apr. 25, 2013, for U.S. Appl. No. 13/298,491, of Lamba, K., et al., filed Nov. 17, 2011. |
Final Office Action dated Sep. 17, 2013, for U.S. Appl. No. 13/298,491, of Lamba, K., et al., filed Nov. 17, 2011. |
Advisory Action dated Oct. 22, 2013, for U.S. Appl. No. 13/298,491, of Lamba, K., et al., filed Nov. 17, 2011. |
Non-Final Office Action dated Jul. 17, 2014, for U.S. Appl. No. 13/298,491, of Lamba, K., et al., filed Nov. 17, 2011. |
Final Office Action dated Feb. 4, 2015, for U.S. Appl. No. 13/298,491, of Lamba, K., et al., filed Nov. 17, 2011. |
Notice of Allowance dated Jun. 22, 2015, for U.S. Appl. No. 13/298,491, of Lamba, K., et al., filed Nov. 17, 2011. |
Non-Final Office Action dated Jun. 6, 2014, for U.S. Appl. No. 14/231,598, of Wade, J., et al., filed Mar. 31, 2014. |
Non-Final Office Action dated Apr. 10, 2015, for U.S. Appl. No. 14/189,997, of Lamfalusi, M., et al., filed Feb. 25, 2014. |
Notice of Allowance dated Nov. 25, 2014, for U.S. Appl. No. 14/231,598, of Claude, J.B., et al., filed Mar. 31, 2014. |
Non-Final Office Action dated Jun. 22, 2015, for U.S. Appl. No. 14/322,815, of Edwards, T., filed Jul. 2, 2014. |
Notice of Allowance dated Aug. 1, 2014, for U.S. Appl. No. 14/203,463, of Wade, J., et al., filed Mar. 10, 2014. |
Notice of Allowance dated Aug. 27, 2015, for U.S. Appl. No. 13/298,501, of Babu, A., et al., filed Nov. 17, 2011. |
Non-Final Office Action dated Sep. 11, 2014, for U.S. Appl. No. 13/298,501, of Babu, A., et al., filed Nov. 17, 2011. |
Final Office Action dated May 6, 2015, for U.S. Appl. No. 13/298,501, of Babu, A., et al., filed Nov. 17, 2011. |
Notice of Allowance dated Oct. 17, 2014, for U.S. Appl. No. 14/220,967, of Wade, J., et al., filed Mar. 20, 2014. |
Notice of Allowance dated Dec. 18, 2014, for U.S. Appl. No. 14/220,967, of Wade, J., et al., filed Mar. 20, 2014. |
Notice of Allowance dated May 19, 2015, for U.S. Appl. No. 14/620,765, of Wade, J., et al., filed Feb. 12, 2015. |
Non-Final Office Action dated May 26, 2015, for U.S. Appl. No. 14/551,681, of Wade, J., et al., filed Nov. 24, 2014. |
Notice of Allowance dated Jun. 10, 2014, for U.S. Appl. No. 29/491,147, of Templeton T., et al., filed May 16, 2014. |
Non-Final Office Action dated Sep. 11, 2014, for U.S. Appl. No. 13/298,506, of Lamba, K., et al., filed Nov. 17, 2011. |
Final Office Action dated May 6, 2015, for U.S. Appl. No. 13/298,506, of Lamba, K., et al., filed Nov. 17, 2011. |
Non-Final Office Action dated Sep. 30, 2011, for U.S. Appl. No. 13/005,822, of McKelvey, J., et al., filed Jan. 13, 2011. |
Notice of Allowance dated Aug. 28, 2015, for U.S. Appl. No. 13/298,510, of Lamba, K. et al., filed Nov. 17, 2011. |
Non-Final Office Action dated Sep. 11, 2014, for U.S. Appl. No. 13/298,510, of Lamba, K. et al., filed Nov. 17, 2011. |
Final Office Action dated May 6, 2015, for U.S. Appl. No. 13/298,510, of Lamba, K. et al., filed Nov. 17, 2011. |
Final Office Action dated Jul. 9, 2012, for U.S. Appl. No. 13/005,822, of McKelvey, J., et al., filed Jan. 13, 2011. |
Non-Final Office Action dated Jun. 18, 2013, for U.S. Appl. No. 13/005,822, of McKelvey, J., et al., filed Jan. 13, 2011. |
Non-Final Office Action dated Dec. 10, 2013, for U.S. Appl. No. 13/005,822 of McKelvey, J., et al., filed Jan. 13, 2011. |
Non-Final Office Action dated Oct. 7, 2011, for U.S. Appl. No. 13/043,258, of McKelvey, J., filed Mar. 8, 2011. |
Final Office Action dated Jul. 13, 2012, for U.S. Appl. No. 13/043,258, of McKelvey, J., filed Mar. 8, 2011. |
Non-Final Office Action dated Dec. 11, 2013, for U.S. Appl. No. 13/043,258, of McKelvey, J., filed Mar. 8, 2011. |
Notice of Allowance dated Jul. 1, 2014, for U.S. Appl. No. 13/043,258, of McKelvey, J., filed Mar. 8, 2011. |
Advisory Action dated Aug. 15, 2012, for U.S. Appl. No. 13/043,258, of McKelvey, J., filed Mar. 8, 2011. |
Advisory Action dated Aug. 17, 2012, for U.S. Appl. No. 13/005,822, of McKelvey, J.,et al., filed Jan. 13, 2011. |
Notice of Allowance dated Jun. 24, 2014, for U.S. Appl. No. 13/005,822, of McKelvey, J., et al., filed Jan. 13, 2011. |
Non-Final Office Action dated Oct. 7, 2014, for U.S. Appl. No. 13/298,534, of Lamba, K., et al., filed Nov. 17, 2011. |
Final Office Action dated Apr. 8, 2015, for U.S. Appl. No. 13/298,534, of Lamba, K., et al., filed Nov. 17, 2011. |
Final Office Action dated Sep. 6, 2013, for U.S. Appl. No. 13/298,560, of Lamba K. et al., filed Nov. 17, 2011. |
Advisory Action dated Oct. 21, 2013, for U.S. Appl. No. 13/298,560 of Lamba K. et al., filed Nov. 17, 2011. |
Final Office Action dated Aug. 15, 2013, for U.S. Appl. No. 13/043,263, of McKelvey, J., filed Mar. 8, 2011. |
Advisory Action dated Nov. 8, 2013, for U.S. Appl. No. 13/043,263, of McKelvey, J., filed Mar. 8, 2011. |
Non-Final Office Action dated Feb. 24, 2014, for U.S. Appl. No. 13/043,263, of McKelvey, J., filed Mar. 8, 2011. |
Notice of Allowance dated Jul. 15, 2014, for U.S. Appl. No. 13/043,263, of McKelvey, J., filed Mar. 8, 2011. |
Non-Final Office Action dated Jul. 22, 2014, for U.S. Appl. No. 13/298,560, of Lamba K. et al., filed Nov. 17, 2011. |
Final Office Action dated Jan. 28, 2015, for U.S. Appl. No. 13/298,560, of Lamba K. et al., filed Nov. 17, 2011. |
Non-Final Office Action dated Oct. 11, 2011, for U.S. Appl. No. 13/043,203, of McKelvey. J., et al., filed Mar. 8, 2011. |
Final Office Action dated Jul. 6, 2012, for U.S. Appl. No. 13/043,203, of McKelvey. J., et al., filed Mar. 8, 2011. |
Non-Final office Action dated Oct. 11, 2011, for U.S. Appl. No. 13/043,263, of McKelvey, J., filed Mar. 8, 2011. |
Advisory Action dated Aug. 1, 2012, for U.S. Appl. No. 13/043,203, of McKelvey, J., filed Mar. 8, 2011. |
Advisory Action dated Aug. 16, 2012, for U.S. Appl. No. 13/043,263, of McKelvey, J., filed Mar. 8,2011. |
Non-Final Office Action dated Apr. 29, 2013, for U.S. Appl. No. 13/043,263, of McKelvey, J., filed Mar. 8, 2011. |
Non-Final office Action dated Apr. 30, 2013, for U.S. Appl. No. 13/043,203, of McKelvey, J., filed Mar. 8, 2011. |
Non-Final Office Action dated May 28, 2013, for U.S. Appl. No. 13/298,560, of Lamba K. et al., filed Nov. 17, 2011. |
Notice of Allowance dated Jul. 9, 2013, for U.S. Appl. No. 13/043,203, of McKelvey, J., filed Mar. 8, 2011. |
Non-Final Office Action dated Jul. 6, 2015, for U.S. Appl. No. 13/298,534, of Lamba K. et al., filed Nov. 17, 2011. |
Advisory Action dated Apr. 9, 2015, for U.S. Appl. No. 13/298,560, of Lamba K. et al., filed Nov. 17, 2011. |
Final office Action dated Jul. 9, 2012, for U.S. Appl. No. 13/043,263, of McKelvey, J., filed Mar. 8, 2011. |
Non-Final Office Action dated Jul. 16, 2015, for U.S. Appl. No. 13/298,560, of Lamba K. et al., filed Nov. 17, 2011. |
Application for Registration of an Industrial Design Examiner's Report for Canadian Design Application No. 159528, dated Jun. 11, 2015. |
English-language translation of Notice of Reasons for Rejection for Japanese Application No. 2014-0255525, dated Mar. 31, 2015. |
Certificate of Registration of Design for Indian Design Application No. 267386 mailed Nov. 14, 2014 (Registration No. 39149). |
Non-Final Office Action dated Jul. 27, 2015, for U.S. Appl. No. 29/493,212, of Edwards, T., et al., filed Jun. 6, 2014. |
English-language translation of Decision of Final Rejection for Japanese Patent Application No. 2013-533897, dated Feb. 23, 2015. |
English-language translation of Office Action for Japanese Patent Application No. 2013-533897, dated Jun. 5, 2014. |
English-language translation of Search Report for Japanese Patent Application No. 2013-533897, dated Apr. 14, 2014. |
Certificate of Design Registration for European Patent Application No. 002578674, mailed Nov. 14, 2014 (Registration No. 002578674-0001). |
Notice of Allowance dated Sep. 2, 2015, for U.S. Appl. No. 14/578,107, of Wade, J. et al., filed Dec. 19, 2014. |
Advisory Action dated Sep. 11, 2015 for U.S. Appl. No. 13/298,506, of Lamba, K., et al., filed Nov. 17, 2011. |
Notice of Allowance dated Sep. 16, 2015 for U.S. Appl. No. 14/551,681, of Wade, J., et al., filed Nov. 24, 2014. |
Notice of Allowance dated Oct. 5, 2015 for U.S. Appl. No. 14/322,815, of Edwards, T., filed Jul. 2, 2014. |
Notice of Allowance dated Oct. 6, 2015 for U.S. Appl. No. 13/298,491, of Lamba, K., et al., filed Nov. 17, 2011. |
Notice of Allowance dated Oct. 7, 2015 for U.S. Appl. No. 13/298,510, of Lamba, K., et al., filed Nov. 17, 2011. |
Notice of Allowance dated Oct. 8, 2015 for U.S. Appl. No. 13/298,487, of Lamba, K., et al., filed Nov. 17, 2011. |
Notice of Allowance dated Oct. 13, 2015 for U.S. Appl. No. 14/578,107, of Wade, J., et al., filed Dec. 19, 2014. |
Non-Final Office Action dated Oct. 29, 2015 for U.S. Appl. No. 14/512,104, of Templeton, T., et al., filed Oct. 10, 2014. |
English-language translation of Final Rejection for Japanese Application No. 2014-025525, dated Oct. 20, 2015. |
Notice of Allowance dated Nov. 13, 2015, for U.S. Appl. No. 13/298,487, of Lamba, K., et al., filed Nov. 17, 2011. |
Corrected Notice of Allowance dated Nov. 18, 2015, for U.S. Appl. No. 14/578,107, of Wade, J., et al., filed Dec. 19, 2014. |
Notice of Allowance dated Nov. 19, 2015, for U.S. Appl. No. 13/298,491, of Lamba, K., et al., filed Nov. 17, 2011. |
Corrected Notice of Allowance dated Nov. 19, 2015, for U.S. Appl. No. 13/298,510, of Lamba, K., et al., filed Nov. 17, 2011. |
Notice of Allowance dated Nov. 20, 2015, for U.S. Appl. No. 13/298,501, of Babu, A., et al., filed Nov. 17, 2011. |
Ex parte Quayle Action dated Nov. 20, 2015, for U.S. Appl. No. 14/620,699, of Wade, J., et al., filed Feb. 12, 2015. |
Notice of Allowance dated Nov. 23, 2015, for U.S. Appl. No. 14/189,997, of Lamfalusi, M., et al., filed Feb. 25, 2014. |
Non-Final Office Action dated Dec. 14, 2015, for U.S. Appl. No. 13/298,506, of Lamba, K., et al., filed Nov. 17, 2011. |
Notice of Allowance dated Jan. 12, 2016, for U.S. Appl. No. 13/298,534, of Lamba, K., et al., filed Nov. 17, 2011. |
Final Office Action dated Jan. 15, 2016, for U.S. Appl. No. 29/493,212, of Edwards, T., et al., filed Jun. 6, 2014. |
“What is a Coupling Capacitor,” Retrieved from the Internet URL: http://www.learningaboutelectronics.com/Articles/What-is-a-coupling-capacitor, on Mar. 21, 2016, pp. 1-4. |
Examiner's Report for Canadian Industrial Design Application No. 159528, dated Dec. 1, 2015. |
Notice of Allowance dated Jan. 29, 2016, for U.S. Appl. No. 13/298,501, of Babu, A., et al., filed Nov. 17, 2011. |
Notice of Allowance dated Jan. 29, 2016, for U.S. Appl. No. 13/298,534, of Lamba, K., et al., filed Nov. 17, 2011. |
Final Office Action dated Feb. 1, 2016, for U.S. Appl. No. 13/298,560, of Lamba, K., et al., filed Nov. 17, 2011. |
Notice of Allowance dated Feb. 5, 2016, for U.S. Appl. No. 14/620,699, of Wade, J., et al., filed Feb. 12, 2015. |
Non-Final Office Action dated Feb. 25, 2016, for U.S. Appl. No. 14/979,407, of Lamfalusi, M., et al., filed Dec. 27, 2015. |
Examiner Requisition for Canadian Application No. 2,812,594, dated Feb. 26, 2016. |
Non-Final Office Action dated Mar. 1, 2016, for U.S. Appl. No. 14/942,515, of Lamba, K., et al., filed Nov. 16, 2015. |
Notice of Allowance dated Mar. 28, 2016, for U.S. Appl. No. 29/493,212, of Edwards, T., et al., filed Jun. 6, 2014. |
Non-Final Office Action dated Apr. 7, 2016, for U.S. Appl. No. 13/298,506, of Lamba, K., et al., filed Nov. 17, 2011. |
Advisory Action dated Apr. 14, 2016, for U.S. Appl. No. 13/298,560, of Lamba, K., et al., filed Nov. 17, 2011. |
Non-Final Office Action dated May 5, 2016, for U.S. Appl. No. 14/306,041, of Wade, J., et al., filed Jun. 16, 2014. |
Non-Final Office Action dated May 6, 2016, for U.S. Appl. No. 14/512,104, of Templeton, T., et al., filed Oct. 10, 2014. |
Notice of Allowance dated May 10, 2016, for U.S. Appl. No. 14/942,515, of Lamba, K., et al., filed Nov. 16, 2015. |
Non-Final Office Action dated May 19, 2016, for U.S. Appl. No. 13/298,560, of Lamba, K., et al., filed Nov. 17, 2011. |
Office Action for Canadian Patent Application No. 2,920,589, dated Mar. 11, 2016. |
Office Action for European Patent Application No. 11 833 172.7, dated May 17, 2016. |
Notice of Allowance dated Jun. 3, 2016, for U.S. Appl. No. 14/942,515, of Lamba, K., et al., filed Nov. 16, 2015. |
Notice of Allowance dated Jun. 13, 2016, for U.S. Appl. No. 14/979,407, of Lamfalusi, M., et al., filed Dec. 27, 2015. |
Notice of Allowance dated Jun. 14, 2016, for U.S. Appl. No. 14/942,515, of Lamba, K., et al., filed Nov. 16, 2015. |
Certificate of Design Registration for Japanese Design Application No. 2014-255525, mailed on Jun. 24, 2016 (Registration No. 1554745). |
Non-Final Office Action dated Jun. 30, 2016 for U.S. Appl. No. 15/066,496, of Babu, A., et al., filed Mar. 10, 2016. |
Notice of Acceptance for Australian Patent Application No. 2014362287, dated Jun. 30, 2016. |
Non-Final Office Action dated Jul. 1, 2016, for U.S. Appl. No. 15/013,937, of Lamba, K., et al., filed Feb. 2, 2016. |
Office Action for Canadian Patent Application No. 2,932,849, dated Jul. 13, 2016. |
Notice of Allowance dated Jul. 14, 2016, for U.S. Appl. No. 14/942,515, of Lamba, K., et al., filed Nov. 16, 2015. |
Office Action for Brazilian Design Application No. 3020140057308, dated Jul. 26, 2016. |
Non-Final Office Action dated Aug. 16, 2016, for U.S. Appl. No. 14/312,524, of Edwards, T., filed Jun. 23, 2014. |
Non-Final Office Action dated Aug. 17, 2016, for U.S. Appl. No. 14/985,624, of Wade, J., et al., filed Dec. 31, 2015. |
Notice of Allowance dated Aug. 26, 2016, for U.S. Appl. No. 13/298,506, of Lamba, K., et al., filed Nov. 17, 2011. |
Notice of Allowance dated Sep. 22, 2016, for U.S. Appl. No. 13/298,506, of Lamba, K., et al., filed Nov. 17, 2011. |
Notice of Allowance dated Sep. 27, 2016, for U.S. Appl. No. 14/306,041, of Wade, J., et al., filed Jun. 16, 2014. |
Notice of Allowance dated Oct. 7, 2016, for U.S. Appl. No. 14/512,104, of Templeton, T., et al., filed Oct. 10, 2014. |
Extended European Search Report for European Patent Application No. 16155374.8, dated Oct. 11, 2016. |
Notice of Allowance dated Oct. 26, 2016, for U.S. Appl. No. 15/013,937, of Lamba, K., et al., filed Feb. 2, 2016. |
Corrected Notice of Allowance dated Nov. 1, 2016, for U.S. Appl. No. 14/512,104, of Templeton, T., et al., filed Oct. 10, 2014. |
Final Office Action dated Nov. 3, 2016, for U.S. Appl. No. 13/298,560, of Lamba, K., et al., filed Nov. 17, 2011. |
International Search Report and Written Opinion, for PCT Application No. PCT/US2015/045772, dated Nov. 6, 2015. |
Notice of Allowance for Canadian Application No. 2,920,589, dated Sep. 21, 2016. |
Notice of Allowance dated Dec. 19, 2016, for U.S. Appl. No. 14/306,041, of Wade, J., filed Jun. 16, 2014. |
Notice of Allowance dated Jan. 12, 2017, for U.S. Appl. No. 14/985,624, of Wade, J., et al., filed Dec. 31, 2015. |
Non-Final Office Action dated Jan. 17, 2017, for U.S. Appl. No. 14/463,455, of Skoog, L., filed Aug. 19, 2014. |
Non-Final Office Action dated Feb. 15, 2017, for U.S. Appl. No. 15/066,496, of Babu, A., et al., filed Mar. 10, 2016. |
Advisory Action dated Feb. 21, 2017, for U.S. Appl. No. 13/298,560, of Lamba, K., et al., filed Nov. 17, 2011. |
Final Office Action dated Feb. 23, 2017, for U.S. Appl. No. 14/312,524, of Edwards, T., filed Jun. 23, 2014. |
Certificate of Industrial Design Registration for Canadian Design Application No. 166511, mailed Feb. 27, 2017. |
Certificate of Industrial Design Registration for Canadian Design Application No. 159528, mailed Feb. 27, 2017. |
Notice of Allowance for Canadian Patent Application No. 2,932,849, dated Mar. 27, 2017. |
Corrected Notice of Allowance dated Apr. 10, 2017, for U.S. Appl. No. 14/985,624, of Wade, J., et al., filed Dec. 31, 2015. |
English-language translation of First Office Action and Search for Chinese Patent Application No. 201510109013.7, dated Sep. 5, 2017. |
Office Action for European Patent Application No. 16155374.8, dated Oct. 18, 2017. |
Office Action for European Patent Application No. 11833172.7, dated Oct. 24, 2017. |
Non-Final Office Action dated Jul. 28, 2017, for U.S. Appl. No. 15/252,033, of Lamba, K., et al., filed Aug. 30, 2016. |
Ex Parte Quayle Action mailed Sep. 8, 2017, for U.S. Appl. No. 15/066,496, of Babu, A., et al., filed Mar. 10, 2016. |
Notice of Allowance dated Sep. 28, 2017, for U.S. Appl. No. 15/013,964, of Lamba, K., et al., filed Feb. 2, 2016. |
English-language translation of Office Action for Chinese Patent Application No. 201080051400.5, dated Sep. 3, 2014. |
Notice of Allowance dated May 5, 2017, for U.S. Appl. No. 14/312,524, of Edwards, T., filed Jun. 23, 2014. |
Non-Final Office Action dated May 8, 2017, for U.S. Appl. No. 15/013,964, of Lamba, K., et al., filed Feb. 2, 2016. |
Notice of Allowance dated Jun. 22, 2017, for U.S. Appl. No. 14/463,455, of Skoog, L., filed Aug. 19, 2014. |
Notice of Allowance dated Jan. 18, 2018, for U.S. Appl. No. 15/066,496, of Babu, A., et al., filed Mar. 10, 2016. |
Final Office Action dated Jan. 29, 2018, for U.S. Appl. No. 15/252,033, of Lamba, K., et al., filed Aug. 30, 2016. |
Corrected Notice of Allowance dated Feb. 9, 2018, for U.S. Appl. No. 15/066,496, of Babu, A., et al., filed Mar. 10, 2016. |