Transaction object reading devices are devices that read information from transaction objects, such as credit cards or wireless near field communication (NFC) devices. Transaction object reading devices typically include circuitry that reads, stores, and conveys sensitive information such as a customer's credit card number or personal identification number (“PIN”). If such circuitry of the transaction object reader is left unprotected, a malicious party could potentially retrieve a customer's sensitive information by accessing the circuitry of the transaction object reader that reads, stores, or conveys the sensitive information.
Some transaction object reading devices include security precautions to prevent malicious parties from retrieving a customer's sensitive information, for example by encrypting the customer's sensitive information as quickly as possible upon receiving it. However, encryption takes some time, particularly with smaller low-power processors intended for portable devices, and any processor performing encryption or memory storing a cryptographic key both need to be protected against malicious parties as well, further slowing down this path.
Transactions using NFC-based readers and NFC-capable devices such as smartphones are still uncommon in many countries. Users who are relatively unfamiliar with the process or with the reader hardware are sometimes unsure where to tap or place their NFC-capable device. Typical NFC-based readers will only notify the user once a payment is complete, which can take a while given the various security precautions built into many transaction object reading devices. In the meantime, users must often resort to tapping their NFC-capable devices on different areas of the NFC-based reader hoping that one of the areas will work, often not stopping at any one areas long enough for the NFC-based reader to actually successfully read the transaction information and conduct the transaction.
An output device is a component that produces an output that may be visual, audio, or tactile. Examples of output devices include display screens, light bulbs, speakers, and vibration actuators.
There is a need in the art for bypassing security transaction object reading device.
A transaction object reader receives a signal from a user's transaction object when the user's transaction object is in proximity with the transaction object reader. This signal is conveyed from the transaction object reader to a secure processor that reads transaction information from the signal, generates a processed dataset by encrypting or otherwise processing the transaction information, and outputs the processed dataset to a main processor, which uses the processed dataset to conduct a transaction. The signal from the transaction object reader is also conveyed along a second path that bypasses the secure processor, instead going to a filter that filters the signal to attenuate the transaction information and then going to the main processor, which uses the filtered signal to provide feedback to the user identifying how close the transaction object is to the transaction object reader.
The POS device 100A of
The terms “main processor 105” and “secure processor 110” as used herein each include a set of one or more of any type of processor(s), controller(s), microcontroller(s), application specific integrated circuit(s) (ASIC), field-programmable gate array(s) (FPGA), or combinations thereof. The “main processor 105” and “secure processor 110” may include any circuit board component illustrated or discussed with respect to the “processor(s)/controller(s) 810” or any of the rest of the circuit board components 800 illustrated or discussed with respect to
The secure processor 110 of
The transaction object reader interfaces of
In addition to outputting transaction information, IC chip contact block 120 may also output a IC chip proximity detection signal 122 that goes directly to the main processor 105 in
The IC proximity detection signal 122 is generally received by the main processor 105 before the main processor 105 receives from the secure processor 110 the processed dataset corresponding to the IC transaction information. The IC proximity detection signal 122 effectively allows the main processor 105 to perform a few tasks before they are needed to speed up operation of the POS system 100 during a transaction. For example, the main processor 105 can, in response to receipt of the IC proximity detection signal 122, wake itself up from a low-power or “sleep” state into a higher-power state, turn on or wake up a receipt printer, turn on or wake up the network interfaces 197, cache subroutines or information necessary to conduct an IC chip transaction in memory, or a combination thereof. The IC proximity detect signal 122 can wake up the main processor 105 itself if it feeds into one or more general purpose input/output (GPIO) pins, for example including an inter-integrated circuit (I2C) pin. Generation and sending of the IC proximity detection signal 122 directly to the main processor 105 and bypassing the secure processor 110 ultimately produces the technical benefit and effect of speeding up operation of the POS system 100 and making transaction processing more efficient while maintaining security.
The IC proximity detection signal 122 can also be used by the main processor 105 to give useful feedback to the user. For instance, if the main processor 105 has received the IC proximity detection signal 122 but does not receive the corresponding processed dataset from the secure processor 110 after a predetermined threshold amount of time has passed, the main processor 105 can assume that the IC chip transaction card was inserted upside-down, the IC chip transaction card was inserted backwards, the IC chip transaction card was not fully inserted into the slot, the IC chip transaction card was inserted too far past the slot and contacts, the IC chip of the IC chip transaction card is malfunctioning or broken, the transaction card is missing an IC chip and is therefore not an IC chip transaction card, the IC chip reader interface is malfunctioning or broken, or a combination thereof. The main processor 105 can then indicate to the user via an output device 185 that the user should check their card and try again, or, if the IC chip reader interface has failed over a predetermine threshold number of times in a row, that the IC chip reader interface is likely broken and to switch to another payment method. In this situation, the main processor 105 can also send repair, replacement, or debugging requests via the network interface 197 to a vendor, distributor, or repair service for POS systems 100. Examples of feedback 910A and 910B given by the POS device 100 to the user is illustrated in
The transaction object reader interfaces of
Traditional magstripe read heads 130 have no clear analogue to the IC proximity detection signal 122 output by the IC chip contact block 120. Including some card detection mechanism in the magstripe card slot of the POS device 100 to send a card proximity detection signal in response to detection of a card within the magstripe card slot would, however, confer some of the same benefits. Like in the IC chip contact block 120, a proximity detection of a magstripe transaction card in the magstripe card slot of the POS device 100 may be achieved with a physical switch or button within the slot that is opened or closed by the pressure of the transaction card moving into or through the slot.
A different approach is illustrated
The filter/buffer 140 are illustrated in
As with the IC proximity detection signal 122 discussed above, the filtered magstripe signal is generally received by the main processor 105 before the main processor 105 receives from the secure processor 110 the processed dataset corresponding to the magstripe transaction information. The filtered magstripe signal effectively allows the main processor 105 to perform a few tasks before they are needed to speed up operation of the POS system 100 during a transaction. For example, the main processor 105 can, in response to receipt of the filtered magstripe signal, wake itself up from a low-power or “sleep” state into a higher-power state, turn on or wake up a receipt printer, turn on or wake up the network interfaces 197, cache subroutines or information necessary to conduct a magstripe transaction in memory, or a combination thereof. The filtered magstripe signal can wake up the main processor 105 itself if it feeds into one or more general purpose input/output (GPIO) pins, for example including an inter-integrated circuit (I2C) pin. Generation and sending of the filtered magstripe signal directly to the main processor 105 and bypassing the secure processor 110 ultimately produces the technical benefit and effect of speeding up operation of the POS system 100 and making transaction processing more efficient while maintaining security.
Because the transaction information is encoded along multiple parallel “tracks” of the magnetic stripe, the filtered magstripe signal need not be Boolean like the IC proximity detection signal 122. While the filter ensures that none of the information from each track is accessible once it reaches the main processor, the filtered magstripe signal may convey if all three tracks have been “found” and thereby the magstripe transaction card is likely positioned correctly. If the filtered magstripe signal indicates that only two out of the three tracks, or one out of the three tracks, have been “found,” the main processor 105 can infer that the transaction card is being swiped in a crooked fashion, the magnetic stripe of the transaction card is malfunctioning or damaged, or the magstripe read head 130 is malfunctioning or damaged. The main processor 105 can provide feedback to the user indicating that the tracks aren't all coming through and to try swiping again as illustrated in
In some cases, the magstripe read head 130 and IC chip contact block 120 may be located within the same transaction card slot that can read either type of card. In this case, any combination of the proximity card detection mechanisms discussed above may be used.
The near field communication (NFC) transceiver of the POS device 100 of
Like the magstripe read head 130, there is no traditional analog to the IC proximity detection signal 122 with respect to the NFC transceiver. However, like for the magstripe read interface of
The filter 170 is illustrated in
The ADC 175 can be used to convey an indicator of that an NFC-capable transaction object is in proximity to the NFC antenna 150. The ADC 175 may be optional depending on the types of inputs that the main processor 105 is configured to receive—that is, the ADC 175 is unnecessary if the main processor 105 is configured to receive analog signals.
As with the IC proximity detection signal 122 and the filtered magstripe information signal discussed above, the filtered NFC information signal is generally received by the main processor 105 before the main processor 105 receives from the secure processor 110 the processed dataset corresponding to the NFC transaction information. The filtered magstripe signal effectively allows the main processor 105 to perform a few tasks before they are needed to speed up operation of the POS system 100 during a transaction. For example, the main processor 105 can, in response to receipt of the filtered magstripe signal, wake itself up from a low-power or “sleep” state into a higher-power state, turn on or wake up a receipt printer, turn on or wake up the network interfaces 197, cache subroutines or information necessary to conduct an NFC transaction in memory, or a combination thereof. The filtered magstripe signal can wake up the main processor 105 itself if it feeds into one or more general purpose input/output (GPIO) pins, for example including an inter-integrated circuit (I2C) pin. Generation and sending of the filtered NFC signal directly to the main processor 105 and bypassing the secure processor 110 ultimately produces the technical benefit and effect of speeding up operation of the POS system 100 and making transaction processing more efficient while maintaining security.
Because the NFC transceiver can include a number of NFC antennae 150, and because differences in amplitude, frequency, and signal receipt timing can be conveyed through the filtered NFC signal to the main processor 150, the main processor 105 can efficiently provide detailed feedback to the user of the POS system 100. Differences in amplitude, frequency, and and/or signal receipt timing between multiple different NFC antennae 150 or between the same NFC antenna 150 at different times can help the main processor 105 track a location of the NFC-capable transaction object 450 relative to the NFC antennae 150 as illustrated and discussed further with respect to
The main processor 105 and/or secure processor 110 may include instructions for one or more applications that may correspond to the type of transaction object and type of transaction object information. Transaction object information may include credit card information, debit card information, automated teller machine (ATM) information, gift card account information, transit account information, identification card information, game token card information, ticket information, bank account information, credit union account information, online gaming account information, HSA/FSA account information, health insurance account information, healthcare information, or some combination thereof. The main processor 105 and/or secure processor 110 may run applications specifically concerning any of these transaction object types or transaction object information types, as well as any of the transaction object reader interfaces 120/130/150 and/or transaction object reader circuitry 870 as illustrated and discussed with respect to
While these application(s) are running, the main processor 105 receives processed dataset that includes processed transaction information from the secure processor 110, the processed transaction information having been encrypted, password-protected, or otherwise processed by the secure processor 110 before its receipt by the main processor 105. The processed dataset may also include user input information that has been encrypted, password-protected, or otherwise processed by the secure processor 110 before its receipt by the main processor 105. The user input information may correspond to information input by a user through input device circuitry 860 such as a keyboard, a number pad, touchscreen, or touch-sensitive surface. The input device circuitry 860 may be at least partially within the secure enclosure 195 to prevent these inputs from being accessible to a malicious party. The user input information may include, for example, a user's personal identification number (PIN) code, a user's signature, a user's selection in response to a charity donation request, a user's selection in response to a question asking whether or not the user desires a receipt and/or if the user would like a printed receipt or an electronic receipt sent to the user's electronic device, or identifying information about the user such as a name, physical address, e-mail address, or phone number. The application running on the main processor 105 may then send the processed dataset, either all together or piecemeal, via the network interface(s) 197, to one or more appropriate servers in order to complete the transaction. The one or more appropriate servers depend on the type of transaction object and type of transaction object information, and may include servers corresponding to any of the types of transaction objects or transaction object information listed above or with respect to the transaction object reader interfaces 120/130/150 and/or transaction object reader circuitry 870 as illustrated and discussed with respect to
The output device(s) 185 of
The secure enclosure 195 refers to an enclosure or housing that includes tamper detection circuitry 115 integrated into the enclosure or housing itself, for example along the surfaces and/or filling an interior. Circuitry that is within the secure enclosure 195 is protected or secured, while circuitry that is outside of the secure enclosure 195 is generally unprotected and unsecured relative to the circuitry inside the secure enclosure 195. The secure processor 110 of
The tamper detection circuitry 115 can include a variety of different types of sensors and sensing methods. The tamper detection circuitry 115 can use a “tamper mesh,” in which two long conductive tamper trace lines run in parallel and in a zig-zagging and/or boustrophedonic pattern that covers at least a majority of at least one surface of the secure enclosure 195. A small example of two lines in a boustrophedonic pattern is illustrated in the “tamper circuitry 115” box of
The tamper detection circuitry 115 can alternately or additionally include inductive sensors that detect nearby objects that are metal and/or have conductive properties in response to an inductive sensor measurement exceeding a predefined threshold. The tamper detection circuitry 115 can alternately or additionally include capacitive sensors that detect touches to surface(s) of the secure enclosure 195 in response to a capacitive sensor measurement exceeding a predefined threshold, where the surface(s) of the secure enclosure 195 should remain internal and should not be touched.
An attempt to open, damage, drill into, or otherwise tamper with the secure enclosure 195 can be identified by the secure processor 110 in concert with the tamper circuitry 115. In response, the secure processor can shut down one or more transaction object read interfaces, and in some cases can also convey a warning that the POS system 100 has been tampered with to a user via output device 185 and/or to a remote server via network interface(s) 197, either through main processor 105 or through a direct line (not pictured in
An additional optional filter 177 is illustrated in
One of the technical benefits to bypassing the secure processor 110 via the filter 170 or filter and/or buffer 140 and/or IC prox signal 122 and/or filter 177 is speeding up the ability of the main processor 105 to provide feedback to the customer. Sending information from the transaction object reader interfaces, through the secure processor 110, and to the main processor can take several hundred milliseconds to several thousand milliseconds. On the other hand, sending information from the transaction object reader interfaces to the main processor through the filters 140/170/177, bypassing the secure processor 110, generally takes under one hundred milliseconds, sometimes even under ten milliseconds. The result is a marked improvement in the efficiency, speed, and responsiveness of the POS device 100.
The dual-unit POS system 100B of
The reader device 210 and host device 220 of
The reader device 210 and host device 220 of
Note that while the ADC 145, ADC 175, and additional filter 180 are illustrated as being within the secure enclosure 195 of the reader device 210 in
The reader device 210 and host device 220 both include their own output devices 185 in
At step 305, the NFC transceiver receives an information signal conveying transaction information from the transaction object associated with the customer in response to physical proximity between the transaction object and the NFC transceiver. Step 305 precedes both step 310 and step 330. Step 310 and the steps that follow it represent the filter path of
At step 310, information signal from the NFC transceiver passes into the filter 170. At step 315, the filter 170 generates a filtered signal from the information signal and then outputs the filtered signal to a main processor in response to receipt of the information signal at the filter 170. The transaction information is attenuated in the filtered signal. The filter 170 may include, for example, a low-pass filter or a band-pass filter.
At step 320, the main processor 105 instructs an output device 185 to output feedback to the customer indicating a degree of proximity between the NFC transceiver and the transaction object. At step 325, the output device outputs the feedback, which may be visual feedback, audio feedback, vibration feedback, or some combination thereof. Examples of visual feedback 410/510/610 are illustrated in
At step 330, the secure processor receives the information signal and generates a processed dataset based on the transaction information. Generating the processed dataset may include encrypting, password-protecting, or otherwise processing the transaction information as discussed above, and may also include user inputs from input device circuitry 860 such as PIN numbers or signatures as discussed above.
At step 335, the secure processor 110 outputs the processed dataset to the main processor 105. The main processor 105 receives the processed dataset after the main processor receives the filtered information signal.
While the flow diagram of
In some cases, multiple NFC antennae 150 may be used in place of the one suggested in
If there are three or more NFC antennae 150, as in the three NFC antenna coils 420 of
If there are two NFC antennae 150, the NFC-capable transaction object can still be located along a single axis extending along a vector connecting the two NFC antennae 150 as pictured in
If there is only one NFC antenna 150, the NFC-capable transaction object can still be located within a radius around the NFC antenna as pictured in
An additional non-illustrated embodiment with at least four NFC antenna coils 420, for example arranged in a tetrahedron, though not illustrated, could allow the main processor 105 to locate the NFC-capable transaction object 450 relative to the NFC antenna coils 420 in three dimensions. Very detailed feedback 410, such as “move NFC object down by 8 centimeters and right by 4 cm and forward by 2 cm” can be given by the main processor 105 to the user via output device 185 as to exactly which directions in any dimension the NFC-capable transaction object 450 should be moved in.
Other types of feedback not illustrated herein can also be used. For example, the main processor can generate a heat map on a display screen 415 identifying places along the display screen 415 or along another portion of the POS device 100 where the NFC-capable transaction object 450 would be close to the NFC transceiver. This would be particularly useful if multiple NFC antenna coils 420 are spaced relatively far apart from each other.
In situations where multiple NFC antenna coils 420 are used, there may be one “main” NFC antenna coil 420 that is most powerful and used for reading and/or transmission, and one or more “secondary” or NFC antenna coils 420 that are smaller and/or weaker and used more for position determination of the NFC-capable transaction object 450.
Besides outputting feedback to the user/customer, the main processor 105 and/or secure processor 110 can perform other functions based on the filtered NFC information. For example, if the filtered NFC information consistently shows a weak signal or that the NFC-capable transaction object 450 is far away from the NFC transceiver, the main processor 105 and/or secure processor 110 could temporarily (i.e., for a predetermined period of time) or permanently increase power directed to the NFC antennae 150 and/or the related circuitry illustrated and discussed with respect to
The main processor 105 of
Because a shaking NFC-capable transaction object 450 can decrease quality and reliability of the NFC read process, the main processor 105 provides helpful feedback 410D through display screen 415 based on this determination of shaking, namely “you are shaking your NFC object too much—try pressing it to a surface of this POS.”
Another type of single-antenna NFC-based feedback 510 similar to the feedback 410C of
In place of the meter output device 185 of
The reader device 210 of
It should be understood that a POS system 100 and/or transaction object reader device 210 as discussed herein can be made with any combination of components, features, and/or elements illustrated in and/or discussed with respect to at least
The horizontal axis 710 measures time 710 moving forward from left to right. The vertical axis 720 measures NFC-capable transaction object 450's proximity to an NFC transceiver 720 as conveyed to the main processor 105 via the filtered signal, where the distance becomes closer (due to stronger/higher amplitude signal) higher along the axis.
A first line 730 is illustrated representing an ideal read, such as if the NFC-capable transaction object 450 suddenly materialized out of nowhere right on top of the NFC transceiver. A second line 740 represents an expected successful read, where the user takes a little more time to find the correct place but gets pretty close to the NFC transceiver of the POS device 100 pretty quickly. Both the first line 730 and the second line 740 should represent successful NFC reads.
A third line 750 represents a user with a shaky hand, where the NFC-capable transaction object 450 appears to “wobble” and the amplitude of the signal is weakened, likely as a result of the shaking as well as a farther distance. This third line may or may not represent a successful read. A fourth line 760 represents a failed read in which the user never moves the NFC-capable transaction object 450 close enough to the NFC transceiver of the POS device 100 and pulls away too quickly as well.
The circuit board components 800 of
The circuit board components 800 of
The circuit board components 800 of
The circuit board components 800 of
The circuit board components 800 of
The circuit board components 800 of
Transaction object reader circuitry 870 may include, for example, a magnetic read head or other type of magnetic stripe reader that is capable of reading information from a magnetic stripe of a transaction card. Transaction object reader circuitry 870 can also include an integrated circuit (IC) chip reader and/or smartcard chip reader for reading an IC chip and/or smartcard chip embedded in a transaction card. Such an IC chip/smartcard chip can follow the Europay-MasterCard-Visa (EMV) payment chip standard. The IC chip/smartcard chip reader can be contact-based, in that it can include one or more conductive prongs that contact a conductive metal contact pad of the IC chip/smartcard chip. The IC chip/smartcard chip can instead be contactless and use a contactless antenna. The contactless antenna can also double as a receiver for near-field-communication (NFC) signals, radio-frequency identification (RFID) signals, Bluetooth® wireless signals, wireless local area network (WLAN) signals, 802.xx Wi-Fi signals, or some combination thereof, which can be sent from a transaction card or from a another type of transaction object as discussed above. In some cases, a transaction object may only send these wireless signals in response to receipt of a magnetic field or other wireless signals from the transaction object reader circuitry 870. For example, if the transaction object is a passive NFC/RFID tag or functions based on similar technology, it generates energy from the magnetic field or other wireless signals from the transaction object reader circuitry 870 via induction coil(s) that is then used to transmit the wireless signals that are ultimately read by the transaction object reader circuitry 870.
The information read from the transaction object by the transaction object reader circuitry 870, regardless of the type of the transaction object, may include at least credit card information, debit card information, automated teller machine (ATM) information, gift card account information, transit account information, identification card information, game token card information, ticket information, bank account information, credit union account information, online gaming account information, HSA/FSA account information, health insurance account information, healthcare information, or some combination thereof. Certain terms discussed herein should be understood to refer to transaction objects, including but not limited to “payment object,” “transaction object,” “financial object,” “payment card,” “transaction card,” or “financial card.”
Peripheral circuitry 880 may include any type circuitry permitting connection and use of computer support devices to add additional functionality to the circuit board 100. For example, peripheral circuitry 780 may support connection of a modem or a router. The components shown in
The reader device 210 of
While various flow diagrams have been described above, it should be understood that these show a particular order of operations performed by certain embodiments of the invention, and that such order is exemplary. Alternative embodiments can perform the operations in a different order, combine certain operations, or overlap certain operations illustrated in or described with respect to each flow diagram.
The foregoing detailed description of the technology has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the technology to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described embodiments were chosen in order to best explain the principles of the technology, its practical application, and to enable others skilled in the art to utilize the technology in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the technology be defined by the claim.
This application is a continuation of U.S. application Ser. No. 17/217,873, filed Mar. 30, 2021, entitled “READER DETECTION SIGNAL BYPASSING SECURE PROCESSOR,”, which is a continuation of U.S. application Ser. No. 15/836,753, filed Dec. 8, 2017, entitled “READER DETECTION SIGNAL BYPASSING SECURE PROCESSOR,” issuing as U.S. Pat. No. 10,970,698, the full disclosures of which are expressly incorporated herein by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
3128349 | Nash | Apr 1964 | A |
4758714 | Carlson | Jul 1988 | A |
4776003 | Harris | Oct 1988 | A |
4860336 | D'Avello | Aug 1989 | A |
5221838 | Gutman | Jun 1993 | A |
5351296 | Sullivan | Sep 1994 | A |
5388155 | Smith | Feb 1995 | A |
5408513 | Busch, Jr. | Apr 1995 | A |
5714741 | Pieterse | Feb 1998 | A |
5729591 | Bailey | Mar 1998 | A |
5740232 | Pailles | Apr 1998 | A |
5752046 | Oprescu | May 1998 | A |
5838773 | Eisner | Nov 1998 | A |
5850599 | Seiderman | Dec 1998 | A |
5867795 | Novis | Feb 1999 | A |
5940510 | Curry | Aug 1999 | A |
6010067 | Elbaum | Jan 2000 | A |
6065679 | Levie | May 2000 | A |
6098881 | DeLand, Jr. | Aug 2000 | A |
6144336 | Preston | Nov 2000 | A |
6234389 | Valliani | May 2001 | B1 |
6278779 | Bryant | Aug 2001 | B1 |
6481623 | Grant | Nov 2002 | B1 |
6600823 | Hayosh | Jul 2003 | B1 |
6886742 | Stoutenburg | May 2005 | B2 |
6990683 | Itabashi | Jan 2006 | B2 |
7003316 | Elias | Feb 2006 | B1 |
7066382 | Kaplan | Jun 2006 | B2 |
7083090 | Zuili | Aug 2006 | B2 |
7124937 | Myers | Oct 2006 | B2 |
7163148 | Durbin | Jan 2007 | B2 |
7210627 | Morley, Jr. | May 2007 | B2 |
7343496 | Hsiang | Mar 2008 | B1 |
7424732 | Matsumoto | Sep 2008 | B2 |
7433452 | Taylor | Oct 2008 | B2 |
7502878 | Wright | Mar 2009 | B1 |
7506956 | Usui | Mar 2009 | B2 |
7515962 | Lyden | Apr 2009 | B2 |
7673799 | Hart | Mar 2010 | B2 |
7810729 | Morley, Jr. | Oct 2010 | B2 |
7896248 | Morley, Jr. | Mar 2011 | B2 |
8086531 | Litster | Dec 2011 | B2 |
8126734 | Dicks | Feb 2012 | B2 |
8265553 | Cheon | Sep 2012 | B2 |
8355003 | Pope | Jan 2013 | B2 |
8397988 | Zuili | Mar 2013 | B1 |
8553055 | Martell | Oct 2013 | B1 |
8702007 | Yisraelian | Apr 2014 | B2 |
9020853 | Hoffman | Apr 2015 | B2 |
9092766 | Bedier | Jul 2015 | B1 |
9223376 | Derbyshire | Dec 2015 | B2 |
9344281 | Kobres | May 2016 | B2 |
9355277 | Kobres | May 2016 | B2 |
9396368 | Lamba | Jul 2016 | B1 |
9489703 | Kauniskangas | Nov 2016 | B2 |
9529758 | Szeto | Dec 2016 | B1 |
9590747 | Thoukydides | Mar 2017 | B2 |
9607181 | Matsumoto | Mar 2017 | B2 |
9659441 | Kelly | May 2017 | B2 |
10182328 | Maibach | Jan 2019 | B1 |
10380471 | Locke | Aug 2019 | B2 |
10643200 | Dorsey et al. | May 2020 | B2 |
10679197 | Gantert | Jun 2020 | B1 |
10733589 | Douthat et al. | Aug 2020 | B2 |
10970698 | Binder et al. | Apr 2021 | B1 |
11257058 | Douthat | Feb 2022 | B1 |
20020091633 | Proctor | Jul 2002 | A1 |
20020153414 | Stoutenburg | Oct 2002 | A1 |
20030135418 | Shekhar | Jul 2003 | A1 |
20030154414 | von Mueller | Aug 2003 | A1 |
20030183691 | Lahteenmaki | Oct 2003 | A1 |
20030200108 | Malnoe | Oct 2003 | A1 |
20040012875 | Wood | Jan 2004 | A1 |
20040041911 | Odagiri | Mar 2004 | A1 |
20040059682 | Hasumi | Mar 2004 | A1 |
20040088449 | Sakaki | May 2004 | A1 |
20040167820 | Melick | Aug 2004 | A1 |
20040204082 | Abeyta | Oct 2004 | A1 |
20040251908 | Knopf | Dec 2004 | A1 |
20050097015 | Wilkes | May 2005 | A1 |
20050109841 | Ryan | May 2005 | A1 |
20050179956 | Silverbrooks | Aug 2005 | A1 |
20050236480 | Vrotsos | Oct 2005 | A1 |
20060032905 | Bear | Feb 2006 | A1 |
20060049255 | von Mueller | Mar 2006 | A1 |
20060049256 | von Mueller | Mar 2006 | A1 |
20060056401 | Bohm | Mar 2006 | A1 |
20060223580 | Antonio | Oct 2006 | A1 |
20070067833 | Colnot | Mar 2007 | A1 |
20070168300 | Quesselaire | Jul 2007 | A1 |
20070194104 | Fukuda | Aug 2007 | A1 |
20070198436 | Weiss | Aug 2007 | A1 |
20070255885 | Bohm | Nov 2007 | A1 |
20080091617 | Hazel | Apr 2008 | A1 |
20080104631 | Krock | May 2008 | A1 |
20080148394 | Poidomani | Jun 2008 | A1 |
20080238687 | Ozer | Oct 2008 | A1 |
20090112768 | Hammad | Apr 2009 | A1 |
20090164326 | Bishop | Jun 2009 | A1 |
20090271270 | Regmi | Oct 2009 | A1 |
20090317161 | Vo | Dec 2009 | A1 |
20100057620 | Li | Mar 2010 | A1 |
20100220136 | Sheahan | Sep 2010 | A1 |
20100243732 | Wallner | Sep 2010 | A1 |
20110019234 | Nakamura | Jan 2011 | A1 |
20110078034 | Hayhow | Mar 2011 | A1 |
20110080422 | Lee | Apr 2011 | A1 |
20110321173 | Weston | Dec 2011 | A1 |
20120039469 | Mueller | Feb 2012 | A1 |
20120060041 | Hashimoto | Mar 2012 | A1 |
20120203620 | Dobyns | Aug 2012 | A1 |
20130013515 | Walters | Jan 2013 | A1 |
20130079037 | Dobyns | Mar 2013 | A1 |
20130094668 | Poulsen | Apr 2013 | A1 |
20130103190 | Carapelli | Apr 2013 | A1 |
20130110678 | Vigier | May 2013 | A1 |
20130262708 | McLeod | Oct 2013 | A1 |
20140021254 | Marshall | Jan 2014 | A1 |
20140108241 | Tunnell | Apr 2014 | A1 |
20140127995 | Hendricksen | May 2014 | A1 |
20140191913 | Ge | Jul 2014 | A1 |
20140206339 | Lindoff | Jul 2014 | A1 |
20140249942 | Hicks | Sep 2014 | A1 |
20140268458 | Luciani | Sep 2014 | A1 |
20140295777 | Wang | Oct 2014 | A1 |
20140368339 | Thaker | Dec 2014 | A1 |
20150199882 | Fernando | Jul 2015 | A1 |
20150227485 | Maung | Aug 2015 | A1 |
20150254621 | Matsumoto | Sep 2015 | A1 |
20150269805 | Korala | Sep 2015 | A1 |
20150302708 | Hattori | Oct 2015 | A1 |
20160014623 | Tanner | Jan 2016 | A1 |
20160064979 | Huang | Mar 2016 | A1 |
20160098690 | Silva | Apr 2016 | A1 |
20160125376 | Beatty | May 2016 | A1 |
20160154967 | Lee | Jun 2016 | A1 |
20160174038 | Menardais | Jun 2016 | A1 |
20160211843 | Wang | Jul 2016 | A1 |
20160307010 | Ge | Oct 2016 | A1 |
20160307171 | Haga | Oct 2016 | A1 |
20160335132 | Ash | Nov 2016 | A1 |
20160342819 | Lamba | Nov 2016 | A1 |
20170004485 | Lee | Jan 2017 | A1 |
20170017943 | Bilhan | Jan 2017 | A1 |
20170076269 | Saeed | Mar 2017 | A1 |
20170160819 | Yi | Jun 2017 | A1 |
20170220822 | Kobres | Aug 2017 | A1 |
20170255927 | Dorsey | Sep 2017 | A1 |
20170300893 | Sasaki | Oct 2017 | A1 |
20170309137 | Shah | Oct 2017 | A1 |
20170337403 | Ohno | Nov 2017 | A1 |
20180026373 | Schwent | Jan 2018 | A1 |
20180314661 | Douthat | Nov 2018 | A1 |
20180316815 | Douthat | Nov 2018 | A1 |
20180366978 | Matan | Dec 2018 | A1 |
20210216988 | Binder et al. | Jul 2021 | A1 |
Number | Date | Country |
---|---|---|
WO-2014116235 | Jul 2014 | WO |
Number | Date | Country | |
---|---|---|---|
20230410077 A1 | Dec 2023 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17217873 | Mar 2021 | US |
Child | 18242837 | US | |
Parent | 15836753 | Dec 2017 | US |
Child | 17217873 | US |