This specification relates to wireless communication between devices.
Fixed radio receivers can also be used to triangulate a location of a mobile device. Mobile device locations can also be determined using Global Positioning System (GPS) signals.
Like reference numbers and designations in the various drawings indicate like elements.
Wireless beacons installed in a physical store location can help a user to obtain information about products in the store and to maintain a shopping list using a mobile user device. Each wireless beacon can be installed in a particular section of a store. A user device can receive signals emitted by the wireless beacon to present information about the items in a virtual shopping list that are located in the particular section of the store.
For example, a user application installed on the user device can determine that a user has entered a particular section of a physical store location using information communicated by a wireless beacon assigned to that section of the store. The user application can then present items on the user's shopping list that are located in that particular section. The user application can also arrange the items on the shopping list in an order according to distance from the user's current location and can provide directions to items on the shopping list that have not yet been purchased. The user application can also use past purchases by the user to guide the user to those items in the physical store environment and suggest new items for purchase by the user. The user application can also use past purchase history and the user's location in the store to present manufacturer offers in real-time, e.g., a coupon to switch detergent brands.
In this specification, wireless beacons refer to devices that use direct radio signal communication to directly communicate information wirelessly to other devices using mid-range to short-range radio signal protocols. In other words, the wireless beacons can directly communicate using radio signals without interaction with any intermediary devices between the communicating devices. Furthermore, a device can communicate information using radio signals, e.g. a user identifier, to another device without the devices engaging in a pairing process that requires user input and without requiring explicit user authorization to communicate with another device. The direct radio signal communication functionality can be performed by any appropriate computing device, e.g. wristwatch, a mobile phone, a portable music player, a tablet computer, a laptop computer, a personal digital assistant, a smartphone, a keychain beacon, or another handheld or wearable mobile device to name a few examples. The radio signals emitted by the devices for such wireless communication can be part of any appropriate standard for mid-range to short-range radio communications having an operable range of at least 1 meter and up to about 50 meters, e.g., Bluetooth 4.0 and Bluetooth Low Energy (BLE). The radio signals described in this specification can be any appropriate type of signal, e.g., a broadcast or advertiser signal that indicates presence of the device to nearby devices, or a connection signal that transmits data to a connected nearby device, to name a few examples. In this specification, a device can be said to be “nearby” if the device is within the operable range for performing direct radio signal communication with another user device.
The wireless beacon 122 is installed, e.g., on the shelf 120, and emits a signal 124 that encodes information about a particular store section. For example, the signal 124 can encode the section-specific information, e.g., “Meats,” to indicate that the wireless beacon 122 is installed in a section that includes meats. Nearby user devices, e.g., the user device 102, can use the information encoded in the signal 124 to present information about products sold in that section or about products on a user shopping list that are located in that section. The signal 124 can also encode product-specific information, e.g., “Laundry detergent” or brand specific information, e.g., “A1 brand laundry detergent” about products that are nearby.
The wireless beacon 112 is installed, e.g., on the shelf 110, in a different section of the store. Similarly, the wireless beacon 112 emits a signal 114 that can encode information about the different store section or nearby products or brands. The user device 102 may measure signal strength from nearby wireless beacons, and use the measurement to determine which wireless beacon is closest. The user device 102 may present information only for a closest wireless beacon or may blend or otherwise combine information relevant to information received multiple wireless beacons.
Because the user device 102 can receive the signals 114 and 124 using direct radio signal communication, an otherwise “offline” user device 102, e.g., a user device that has deactivated its WiFi and cellular data transceiver, can still obtain such information from the wireless beacons.
The interface 202 presents a shopping list 210 of items on a display device of a mobile user device. The shopping list 210 is organized into rows, with each row including a name 212 of the item, e.g., “Pizza,” an image 214 of the item, a price 216 of the item, e.g., “$6.99,” and a store section 218 of the item. A row can also include an input field 217 to enter a quantity of an item purchased, e.g., a weight or a number.
The interface 202 includes icons that help a user manage the shopping list. A blank icon 220 indicates that a particular item has not yet been selected by the user. For example, the user can select the blank icon 220, e.g., after the user places the item in a physical shopping cart, which can change the blank icon 220 into a checked icon 250. Alternatively or in addition, the user application may automatically change a blank icon to a checked icon if certain criteria are met. For example, the user application can change a blank icon for a particular item to a checked icon if the user application detects that the user lingers for at least a threshold period of time at a particular section containing the particular item. Detection that the user has lingered at a particular section can be accomplished by detecting that the signal strength of the wireless beacon for that section has remained above a certain threshold for the threshold period of time. Other information, e.g., signal strength of other beacons or data from motion sensors in the user device can be used.
The user application can display an add icon 230 for an item in the shopping list when the user is near the item in question. The add icon 230 can serve as a suggestion to the user to look for the item in question and to add it to the physical shopping cart. Each row can also include a navigation icon 240 that the user can select to receive indoor navigation directions to the location of the item within the store.
The interface 202 also includes a current total 260 of items that have been added, e.g., as indicated by items having the checked icon 220. The interface 202 also includes a projected total 270 for all items in the shopping list.
A user can assemble the shopping list 210 before arriving at the store using a mobile device or another computing device, e.g., a desktop computer. The user can also assemble the shopping list as the user selects items in the store, in which case the user application may only present the current total 260 and not the projected total 270.
The user device can obtain one or more of the items of information in the example interface 202 directly from wireless beacons installed in the store. For example, price and other information can be obtained from a product-specific wireless beacon that is installed proximate to particular items within the store.
The user device can also use section-specific wireless beacons to arrange items in the shopping list. For example, if the user device receives a signal from a wireless beacon in the “Produce” section, the user device can order the shopping list so that produce items appear near the top of the list and remaining items appear in descending order. For example, if the meat section is further away than the frozen food section, the user device presents information about the fish item on the list above the pizza item on the list. For each of the items located in a closest section, the user application may present an add icon 230 to suggest to the user that the items be added to the physical shopping cart while the user is in that section.
The user interface 302 can also present offer information 340 about a real-time for nearby items. For example, the offer information 340 indicates that the user can save $1 if the user purchases Bargain Brand Detergent. The offer information 340 can be triggered by the user having a particular item listed in a shopping list, e.g., A1 Detergent 320. The offer information 340 can also be triggered by the user being a particular section of the store, e.g., the detergent section, as determined by a signal received from a wireless beacon. The user can accept the offer by selecting an add icon 330 presented with the item information.
The merchant device 430 can install a merchant application received from the serving system 450 that can be used to configure the wireless beacon 420. In some implementations, the serving system 450 issues item and product-specific identifiers for specific items or products sold by the merchant, and which will be broadcast by the wireless beacon 420.
The user device 410 can install user application received from the serving system 450. The user application can be used to receive signals 422 from the wireless beacon 420 and to present, on a display device of the user device 410, a user interface that includes item information received from the wireless beacon 420.
The user device obtains shopping list data identifying one or more items selected by a user (510). A user can create a virtual shopping list on the user device, using a desktop computer, or using another computing device. The shopping list stores item identifiers and other associated information for each item, e.g., a picture, a description, a price, a manufacturer, a website URL, to name a few examples. The item identifiers can be maintained by the serving system, the item manufacturers, a merchant, or another party.
The shopping list can be stored on the user device or can be stored at a serving system in an account associated with the user. The user device can then access the shopping list for display to the user through an application installed on the user device. The user device can access the shopping list from local storage of the user device, or the user device can access the shopping list at a serving system over a network.
The user device receives a signal from a wireless beacon located in a particular section of a store (520). The wireless beacon can be part of a number of wireless beacons installed throughout a physical store location. For example, a merchant can divide the store into a number of sections and install a wireless beacon in each section. The merchant can use a merchant device to program each wireless beacon to broadcast a section identifier for the appropriate section.
The merchant can obtain section identifiers from a serving system that uses a global categorization of store sections across merchants. For example, the section identifiers can correspond to different grocery store sections, e.g., meat, dairy, produce, to different clothing store sections, e.g., men, women, boys, girls, or to any other appropriate store division or categorization. The merchant can communicate with a serving system to obtain the global section identifiers. The merchant can then use a merchant device to program wireless beacons in each section to broadcast the appropriate section identifier.
The user device determines a section identifier from the signal (530). The user device may first engage in an automatic pairing process with the wireless beacon in which one or more packets are exchanged between the devices in order to set up direct radio signal communication between the devices. The user device can then obtain a section identifier encoded in the signal emitted by the wireless beacon.
If the user device receives signals from multiple wireless beacons, the user device can choose a closest wireless beacon, e.g., by comparing the strength of the signal received from each wireless beacon. In some implementations, the user device can select sections identifiers corresponding to multiple wireless beacons.
The user device obtains an association between the items in the shopping list and respective store sections (540). The association provides information about in which sections particular items in the shopping list are located within the store. The association can be defined by a serving system, the merchant, or another party.
For example, the merchant can use a merchant device to upload, to a serving system, an association between items for sale in the store and associated store sections. The user device can then access the association uploaded by the merchant. For example, if apples are an item on the shopping list, the user device can obtain an association between apples and an identifier for the produce section of the store.
The user device determines one or more items in the shopping list that are located in the section (550). The user device can use the association between the items in the shopping list and respective store sections to identify items that are located in the section of the store determined by the wireless beacon.
The user device displays information related to the one or more items (560). The user device can present a variety of information about items located in the section. For example, the user device can present only a list of items that are located in the section, along with information about the items, e.g., a description, a price, and whether the item has already been selected for purchase by the user. The user device can display a suggestion icon, e.g., an “Add” icon, for items that are in the section but have not yet been selected by the user. If the user device is receiving signals from multiple wireless beacons from different store sections, the user device can generate a blended list of items from the multiple sections.
The user device can also present items in the shopping list in an order, with items determined to be in the section first in a list. In addition, unselected items within the determined section can be presented above items that the user has indicated as being selected. The user device may also arrange items in other sections in an increasing order by distance to the current section, as measured from the current section or a location of the user device. The user device can also present an option to obtain a map of the store or navigation directions to other items in the shopping list.
The user device can also automatically determine that the user has selected one or more items for purchase, e.g., by placing the items in a physical shopping cart. For example, if the user device has remained near a particular section for a threshold period of time, e.g., at least 1 minute, the user device can automatically determine that the user has selected the items in that section for purchase.
The user device can also automatically determine that the user has selected an item for purchase from a wireless device installed in a physical shopping cart. For example, the shopping cart can have installed on it a device that communicates with item-specific wireless beacons embedded in or coupled to the items themselves. The shopping cart beacon can then communicate with the user device to provide item identifiers of the items that are determined to be in the shopping cart. The shopping cart device can determine that items are in the shopping cart by computing a measurement of signal strength emitted by the item-specific wireless beacons embedded in the items.
The user device can also obtain information about current offers for one or more items in the section and present the offers when the user is determined to be in the section. The user can redeem the offer by selecting the item mentioned in the offer and carrying through with the purchase of the item.
The offers can be identified by a serving system based on various criteria, in addition to the user being located in a particular section of the store. For example, the offers can be identified based on items in the shopping list of the user. The serving system can identify offers for the items currently in the user's shopping list, or the serving system can identify offers for products that are competing with or otherwise related to the products in the shopping list.
The serving system can also identify offers based on the purchase history of the user. For example, if the user has purchased a particular brand in the past, the serving system can identify offers for products based on that particular brand or on a competing brand. The serving system can also identify offers for products that other people have purchased with products in the user's shopping list.
The serving system can also identify offers based on regularity of a particular purchase by the user. For example, if the user typically buys milk once per week, the serving system can identify offers for milk if the user is in the milk section and about a week has passed since the user last purchased milk. The serving system can also use pattern matching to determine items that users typically purchase when in particular store sections. For example, the serving system may determine that users that buy milk also typically buy diapers when in the diaper section of the store. Thus, if the user has milk in the shopping list, the serving system can present an offer for diapers when the user is in the diaper section of the store.
Embodiments of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, in tangibly-embodied computer software or firmware, in computer hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a tangible non-transitory program carrier for execution by, or to control the operation of, data processing apparatus. Alternatively or in addition, the program instructions can be encoded on an artificially-generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. The computer storage medium can be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them. The computer storage medium is not, however, a propagated signal.
The term “data processing apparatus” encompasses all kinds of apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). The apparatus can also include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.
A computer program (which may also be referred to or described as a program, software, a software application, a module, a software module, a script, or code) can be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data, e.g., one or more scripts stored in a markup language document, in a single file dedicated to the program in question, or in multiple coordinated files, e.g., files that store one or more modules, sub-programs, or portions of code. A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
As used in this specification, an “engine,” or “software engine,” refers to a software implemented input/output system that provides an output that is different from the input. An engine can be an encoded block of functionality, such as a library, a platform, a software development kit (“SDK”), or an object. Each engine can be implemented on any appropriate type of computing device, e.g., servers, mobile phones, tablet computers, notebook computers, music players, e-book readers, laptop or desktop computers, PDAs, smart phones, or other stationary or portable devices, that includes one or more processors and computer readable media. Additionally, two or more of the engines may be implemented on the same computing device, or on different computing devices.
The processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
Computers suitable for the execution of a computer program include, by way of example, can be based on general or special purpose microprocessors or both, or any other kind of central processing unit. Generally, a central processing unit will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a central processing unit for performing or executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device, e.g., a universal serial bus (USB) flash drive, to name just a few.
Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
To provide for interaction with a user, embodiments of the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) monitor, an LCD (liquid crystal display) monitor, or an OLED display, for displaying information to the user, as well as input devices for providing input to the computer, e.g., a keyboard, a mouse, or a presence sensitive display or other surface. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending resources to and receiving resources from a device that is used by the user; for example, by sending web pages to a web browser on a user's client device in response to requests received from the web browser.
Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.
The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
For a system of one or more computers to be configured to perform particular operations or actions means that the system has installed on it software, firmware, hardware, or a combination of them that in operation cause the system to perform the operations or actions. For one or more computer programs to be configured to perform particular operations or actions means that the one or more programs include instructions that, when executed by data processing apparatus, cause the apparatus to perform the operations or actions.
While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system modules and components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
Particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results. As one example, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous.
This application claims priority to and is a continuation of U.S. patent application Ser. No. 14/079,320, filed on Nov. 13, 2013, entitled “WIRELESS BEACON SHOPPING EXPERIENCE,” the entirety of which is herein incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4035614 | Frattarola et al. | Jul 1977 | A |
| 4254441 | Fisher | Mar 1981 | A |
| 4591937 | Nakarai et al. | May 1986 | A |
| 4845740 | Tokuyama et al. | Jul 1989 | A |
| 5266789 | Anglin et al. | Nov 1993 | A |
| 5434400 | Scherzer | Jul 1995 | A |
| 5463678 | Kepley, III et al. | Oct 1995 | A |
| 5589855 | Blumstein et al. | Dec 1996 | A |
| 5764742 | Howard et al. | Jun 1998 | A |
| 5850599 | Seiderman | Dec 1998 | A |
| 5945654 | Huang | Aug 1999 | A |
| 6006109 | Shin | Dec 1999 | A |
| 6021944 | Arakaki | Feb 2000 | A |
| 6026375 | Hall et al. | Feb 2000 | A |
| 6032859 | Muehlberger et al. | Mar 2000 | A |
| 6061666 | Do et al. | May 2000 | A |
| 6129277 | Grant et al. | Oct 2000 | A |
| 6234389 | Valliani et al. | May 2001 | B1 |
| 6341353 | Herman et al. | Jan 2002 | B1 |
| 6363139 | Zurek et al. | Mar 2002 | B1 |
| 6374176 | Schmier et al. | Apr 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 |
| 6526275 | Calvert | Feb 2003 | B1 |
| 6536670 | Postman et al. | Mar 2003 | B1 |
| 6579728 | Grant et al. | Jun 2003 | B2 |
| 6612488 | Suzuki | Sep 2003 | B2 |
| 6659344 | Otto et al. | Dec 2003 | B2 |
| 6820062 | Gupta et al. | Nov 2004 | B1 |
| 6832721 | Fujii | Dec 2004 | B2 |
| 6850147 | Prokoski et al. | Feb 2005 | B2 |
| 6868391 | Hultgren | Mar 2005 | B1 |
| 6888443 | Ritter | May 2005 | B2 |
| 6896182 | Sakaguchi | May 2005 | B2 |
| 6898598 | Himmel et al. | May 2005 | B2 |
| 6944782 | von Mueller et al. | Sep 2005 | B2 |
| 6957334 | Goldstein et al. | Oct 2005 | B1 |
| 7003316 | Elias et al. | Feb 2006 | B1 |
| 7149296 | Brown et al. | Dec 2006 | B2 |
| 7207480 | Geddes | Apr 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 |
| 7376431 | Niedermeyer | May 2008 | B2 |
| 7376433 | Hose | May 2008 | B1 |
| 7376583 | Rolf | May 2008 | B1 |
| 7403762 | Morgan et al. | Jul 2008 | B2 |
| 7409234 | Glezerman | Aug 2008 | B2 |
| 7433452 | Taylor et al. | Oct 2008 | B2 |
| 7506812 | von Mueller et al. | Mar 2009 | B2 |
| 7520430 | Stewart et al. | Apr 2009 | B1 |
| 7581678 | Narendra et al. | Sep 2009 | B2 |
| 7600673 | Stoutenburg et al. | Oct 2009 | B2 |
| 7620404 | Chesnais et al. | Nov 2009 | B2 |
| 7684809 | Niedermeyer | Mar 2010 | B2 |
| 7708189 | Cipriano | May 2010 | B1 |
| 7711100 | Dennis | May 2010 | B2 |
| 7793834 | Hachey et al. | Sep 2010 | B2 |
| 7810729 | Morley | Oct 2010 | B2 |
| 7848765 | Phillips et al. | Dec 2010 | B2 |
| 7869591 | Nagel et al. | Jan 2011 | B1 |
| 7896248 | Morley | Mar 2011 | B2 |
| 7918394 | Morley, Jr. | Apr 2011 | B1 |
| 7945494 | Williams | May 2011 | B2 |
| 8050984 | Bonner et al. | Nov 2011 | B2 |
| 8090351 | Klein | Jan 2012 | B2 |
| 8135624 | Ramalingam et al. | Mar 2012 | B1 |
| 8231055 | Wen | Jul 2012 | B2 |
| 8376239 | Humphrey | Feb 2013 | B1 |
| 8413901 | Wen | Apr 2013 | B2 |
| 8438066 | Yuen et al. | May 2013 | B1 |
| 8509734 | Gupta et al. | Aug 2013 | B1 |
| 8554670 | Blank et al. | Oct 2013 | B1 |
| 8684261 | Burdett et al. | Apr 2014 | B2 |
| 8707319 | Nguyen et al. | Apr 2014 | B2 |
| 8750901 | Gupta et al. | Jun 2014 | B1 |
| 8766791 | Koen et al. | Jul 2014 | B2 |
| 9055400 | Lee | Jun 2015 | B1 |
| 9113344 | Lee | Aug 2015 | B1 |
| 9204257 | Mendelson | Dec 2015 | B1 |
| 9264850 | Lee | Feb 2016 | B1 |
| 9373112 | Henderson et al. | Jun 2016 | B1 |
| 9407689 | Casares et al. | Aug 2016 | B1 |
| 9451397 | Lee | Sep 2016 | B1 |
| 9576289 | Henderson et al. | Feb 2017 | B2 |
| 9633352 | Henderson et al. | Apr 2017 | B2 |
| 9652791 | Brock | May 2017 | B1 |
| 9665858 | Kumar | May 2017 | B1 |
| 9730015 | Lee | Aug 2017 | B1 |
| 9767474 | Ramalingam et al. | Sep 2017 | B1 |
| 9805370 | Quigley et al. | Oct 2017 | B1 |
| 9838840 | Lee | Dec 2017 | B1 |
| 9875471 | Myrick et al. | Jan 2018 | B1 |
| 9924322 | Post et al. | Mar 2018 | B2 |
| 9959529 | Varma et al. | May 2018 | B1 |
| 10026083 | Varma et al. | Jul 2018 | B1 |
| 10163148 | Chatterjee et al. | Dec 2018 | B1 |
| 10332162 | Brock et al. | Jun 2019 | B1 |
| 10373151 | Lee | Aug 2019 | B1 |
| 10885522 | Brock | Jan 2021 | B1 |
| 20010001856 | Gould et al. | May 2001 | A1 |
| 20010011250 | Paltenghe et al. | Aug 2001 | A1 |
| 20020002507 | Hatakeyama | Jan 2002 | A1 |
| 20020013815 | Obradovich et al. | Jan 2002 | A1 |
| 20020030871 | Anderson et al. | Mar 2002 | A1 |
| 20020049644 | Kargman | Apr 2002 | A1 |
| 20020077974 | Ortiz | Jun 2002 | A1 |
| 20020099648 | DeVoe et al. | Jul 2002 | A1 |
| 20020108062 | nakajima et al. | Aug 2002 | A1 |
| 20020128967 | Meyer et al. | Sep 2002 | A1 |
| 20020169541 | Bouve et al. | Nov 2002 | A1 |
| 20020198818 | Scott et al. | Dec 2002 | A1 |
| 20030004842 | Williams et al. | Jan 2003 | A1 |
| 20030089772 | Chien | May 2003 | A1 |
| 20030132300 | Dilday et al. | Jul 2003 | A1 |
| 20030135463 | Brown et al. | Jul 2003 | A1 |
| 20030144040 | Liu et al. | Jul 2003 | A1 |
| 20030194071 | Ramian | Oct 2003 | A1 |
| 20030200179 | Kwan | Oct 2003 | A1 |
| 20030200180 | Phelan et al. | Oct 2003 | A1 |
| 20040002897 | Vishik | Jan 2004 | A1 |
| 20040002903 | Stolfo et al. | Jan 2004 | A1 |
| 20040006510 | Lertzman et al. | Jan 2004 | A1 |
| 20040012875 | Wood | Jan 2004 | A1 |
| 20040015475 | Scheepsma | Jan 2004 | A1 |
| 20040041911 | Odagiri et al. | Mar 2004 | A1 |
| 20040049451 | Berardi et al. | Mar 2004 | A1 |
| 20040064378 | Yoshida | Apr 2004 | A1 |
| 20040093274 | Vanska et al. | May 2004 | A1 |
| 20040093496 | Colnot | May 2004 | A1 |
| 20040104268 | Bailey | Jun 2004 | A1 |
| 20040107170 | Labrou et al. | Jun 2004 | A1 |
| 20040127256 | Goldthwaite et al. | Jul 2004 | A1 |
| 20040128256 | Krouse et al. | Jul 2004 | A1 |
| 20040193553 | Lloyd et al. | Sep 2004 | A1 |
| 20040204074 | Desai | Oct 2004 | A1 |
| 20050004757 | Neeman et al. | Jan 2005 | A1 |
| 20050048961 | Ribaudo et al. | Mar 2005 | A1 |
| 20050077870 | Ha et al. | Apr 2005 | A1 |
| 20050159133 | Hasan et al. | Jul 2005 | A1 |
| 20050242173 | Suzuki | Nov 2005 | A1 |
| 20050251440 | Bednarek | Nov 2005 | A1 |
| 20050256782 | Sands et al. | Nov 2005 | A1 |
| 20050266798 | Moloney et al. | Dec 2005 | A1 |
| 20060089909 | Mcleod et al. | Apr 2006 | A1 |
| 20060094481 | Gullickson | May 2006 | A1 |
| 20060122902 | Petrov et al. | Jun 2006 | A1 |
| 20060200378 | Sorensen | Sep 2006 | A1 |
| 20060208066 | Finn et al. | Sep 2006 | A1 |
| 20060223580 | Antonio et al. | Oct 2006 | A1 |
| 20060234771 | Shavrov | Oct 2006 | A1 |
| 20060282864 | Gupte | Dec 2006 | A1 |
| 20060293968 | Brice et al. | Dec 2006 | A1 |
| 20070030824 | Ribaudo et al. | Feb 2007 | A1 |
| 20070067833 | Colnot | Mar 2007 | A1 |
| 20070072678 | Dagres | Mar 2007 | A1 |
| 20070100651 | Ramer et al. | May 2007 | A1 |
| 20070118429 | Subotovsky | May 2007 | A1 |
| 20070124211 | Smith | May 2007 | A1 |
| 20070138268 | Tuchman | Jun 2007 | A1 |
| 20070150369 | Zivin | Jun 2007 | A1 |
| 20070150414 | Templeton | Jun 2007 | A1 |
| 20070155430 | Cheon et al. | Jul 2007 | A1 |
| 20070221728 | Ferro et al. | Sep 2007 | A1 |
| 20070244778 | Bailard | Oct 2007 | A1 |
| 20070244811 | Tumminaro | Oct 2007 | A1 |
| 20070250623 | Hickey et al. | Oct 2007 | A1 |
| 20070255653 | Tumminaro et al. | Nov 2007 | A1 |
| 20070282700 | Masse | Dec 2007 | A1 |
| 20070299722 | Stoffelsma et al. | Dec 2007 | A1 |
| 20080027815 | Johnson et al. | Jan 2008 | A1 |
| 20080040219 | Kim et al. | Feb 2008 | A1 |
| 20080040274 | Uzo | Feb 2008 | A1 |
| 20080054072 | Katragadda et al. | Mar 2008 | A1 |
| 20080059297 | Vallier et al. | Mar 2008 | A1 |
| 20080059370 | Sada et al. | Mar 2008 | A1 |
| 20080059375 | Abifaker | Mar 2008 | A1 |
| 20080061150 | Phillips | Mar 2008 | A1 |
| 20080084977 | Nayak et al. | Apr 2008 | A1 |
| 20080147507 | Langhammer | Jun 2008 | A1 |
| 20080147564 | Singhal | Jun 2008 | A1 |
| 20080177662 | Smith et al. | Jul 2008 | A1 |
| 20080189170 | Ramachandra et al. | Aug 2008 | A1 |
| 20080195428 | O'Sullivan | Aug 2008 | A1 |
| 20080215380 | Graeber | Sep 2008 | A1 |
| 20080238610 | Rosenberg | Oct 2008 | A1 |
| 20080242278 | Rekimoto | Oct 2008 | A1 |
| 20080249865 | Angell et al. | Oct 2008 | A1 |
| 20080249882 | Spolar | Oct 2008 | A1 |
| 20080249939 | Veenstra | Oct 2008 | A1 |
| 20080277183 | Huang et al. | Nov 2008 | A1 |
| 20080306678 | Miyawaki | Dec 2008 | A1 |
| 20090024533 | Fernandes et al. | Jan 2009 | A1 |
| 20090030885 | DePasquale et al. | Jan 2009 | A1 |
| 20090043696 | Ornce 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 |
| 20090132413 | Engelbrecht | May 2009 | A1 |
| 20090159681 | Mullen et al. | Jun 2009 | A1 |
| 20090166422 | Biskupski | Jul 2009 | A1 |
| 20090171844 | Olliphant et al. | Jul 2009 | A1 |
| 20090210334 | Russell | Aug 2009 | A1 |
| 20090216676 | Mathur et al. | Aug 2009 | A1 |
| 20090287408 | Gerdes et al. | Nov 2009 | A1 |
| 20090298514 | Ullah | Dec 2009 | A1 |
| 20090328052 | Nguyen et al. | Dec 2009 | A1 |
| 20100057503 | Katz | Mar 2010 | A1 |
| 20100063893 | Townsend | Mar 2010 | A1 |
| 20100087144 | Korenshtein | Apr 2010 | A1 |
| 20100125495 | Smith et al. | May 2010 | A1 |
| 20100131764 | Goh | May 2010 | A1 |
| 20100135178 | Aggarwal et al. | Jun 2010 | A1 |
| 20100144375 | Pfister et al. | Jun 2010 | A1 |
| 20100145868 | Niedermeyer | Jun 2010 | A1 |
| 20100184479 | Griffin | Jul 2010 | A1 |
| 20100191653 | Johnson et al. | Jul 2010 | A1 |
| 20100197325 | Dredge | Aug 2010 | A1 |
| 20100243732 | Wallner | Sep 2010 | A1 |
| 20100287250 | Carlson et al. | Nov 2010 | A1 |
| 20100306080 | Trandal et al. | Dec 2010 | A1 |
| 20100328029 | Kolek | Dec 2010 | A1 |
| 20110045840 | Alizadeh-Shabdiz et al. | Feb 2011 | A1 |
| 20110047037 | Wu | Feb 2011 | A1 |
| 20110060600 | Fox et al. | Mar 2011 | A1 |
| 20110063138 | Berkobin et al. | Mar 2011 | A1 |
| 20110084131 | McKelvey | Apr 2011 | A1 |
| 20110084139 | McKelvey et al. | Apr 2011 | A1 |
| 20110084147 | Wilson et al. | Apr 2011 | A1 |
| 20110090124 | Liu et al. | Apr 2011 | A1 |
| 20110137773 | Davis, III et al. | Jun 2011 | A1 |
| 20110137803 | Willins | Jun 2011 | A1 |
| 20110153495 | Dixon et al. | Jun 2011 | A1 |
| 20110161235 | Beenau et al. | Jun 2011 | A1 |
| 20110180601 | Morley | Jul 2011 | A1 |
| 20110198395 | Chen | Aug 2011 | A1 |
| 20110202393 | DeWakar et al. | Aug 2011 | A1 |
| 20110202463 | Powell | Aug 2011 | A1 |
| 20110208612 | Shader et al. | Aug 2011 | A1 |
| 20110213652 | Gillen et al. | Sep 2011 | A1 |
| 20110238476 | Carr et al. | Sep 2011 | A1 |
| 20110238517 | Ramalingam et al. | Sep 2011 | A1 |
| 20110249668 | Van Milligan et al. | Oct 2011 | A1 |
| 20110258120 | Weiss | Oct 2011 | A1 |
| 20120005096 | Dorsey et al. | Jan 2012 | A1 |
| 20120008851 | Pennock et al. | Jan 2012 | A1 |
| 20120012653 | Johnson et al. | Jan 2012 | A1 |
| 20120052874 | Kumar | Mar 2012 | A1 |
| 20120052910 | Mu et al. | Mar 2012 | A1 |
| 20120101942 | Park | Apr 2012 | A1 |
| 20120109781 | Felt et al. | May 2012 | A1 |
| 20120115512 | Grainger et al. | May 2012 | A1 |
| 20120116861 | Dobyns | May 2012 | A1 |
| 20120128089 | Tsutsui | May 2012 | A1 |
| 20120130895 | Granbery et al. | May 2012 | A1 |
| 20120149390 | Gravely et al. | Jun 2012 | A1 |
| 20120158500 | Hochstatter et al. | Jun 2012 | A1 |
| 20120166267 | Beatty et al. | Jun 2012 | A1 |
| 20120195295 | Elmaleh | Aug 2012 | A1 |
| 20120209686 | Horowitz et al. | Aug 2012 | A1 |
| 20120209773 | Ranganathan | Aug 2012 | A1 |
| 20120235812 | Maia et al. | Sep 2012 | A1 |
| 20120252500 | Mitsuya et al. | Oct 2012 | A1 |
| 20120278150 | Chen | Nov 2012 | A1 |
| 20120278172 | Mercuri et al. | Nov 2012 | A1 |
| 20120296724 | Faro et al. | Nov 2012 | A1 |
| 20120303425 | Katzin et al. | Nov 2012 | A1 |
| 20120310760 | Phillips et al. | Dec 2012 | A1 |
| 20130002840 | Toney et al. | Jan 2013 | A1 |
| 20130024018 | Chang et al. | Jan 2013 | A1 |
| 20130027227 | Nordstrom | Jan 2013 | A1 |
| 20130030931 | Moshfeghi | Jan 2013 | A1 |
| 20130054281 | Thakkar et al. | Feb 2013 | A1 |
| 20130073365 | McCarthy | Mar 2013 | A1 |
| 20130079037 | Dobyns | Mar 2013 | A1 |
| 20130080289 | Roy | Mar 2013 | A1 |
| 20130110659 | Phillips et al. | May 2013 | A1 |
| 20130132274 | Henderson et al. | May 2013 | A1 |
| 20130144715 | Kranzley et al. | Jun 2013 | A1 |
| 20130157685 | Young | Jun 2013 | A1 |
| 20130185123 | Krivopaltsev et al. | Jul 2013 | A1 |
| 20130191195 | Carlson et al. | Jul 2013 | A1 |
| 20130217332 | Altman et al. | Aug 2013 | A1 |
| 20130217333 | Sprigg et al. | Aug 2013 | A1 |
| 20130226800 | Patel et al. | Aug 2013 | A1 |
| 20130238540 | O'Donoghue et al. | Sep 2013 | A1 |
| 20130268378 | Yovin | Oct 2013 | A1 |
| 20130282438 | Hunter et al. | Oct 2013 | A1 |
| 20130297422 | Hunter et al. | Nov 2013 | A1 |
| 20130304898 | Aggarwal et al. | Nov 2013 | A1 |
| 20140028440 | Takeuchi et al. | Jan 2014 | A1 |
| 20140052615 | Andersen | Feb 2014 | A1 |
| 20140068719 | Kiukkonen et al. | Mar 2014 | A1 |
| 20140123043 | Schmidt et al. | May 2014 | A1 |
| 20140149282 | Philliou et al. | May 2014 | A1 |
| 20140179340 | Do et al. | Jun 2014 | A1 |
| 20140187257 | Emadzadeh et al. | Jul 2014 | A1 |
| 20140370879 | Redding et al. | Dec 2014 | A1 |
| 20150006308 | Lin | Jan 2015 | A1 |
| 20150031388 | Chatterjee et al. | Jan 2015 | A1 |
| 20150079942 | Kostka et al. | Mar 2015 | A1 |
| 20150126119 | Schulz et al. | May 2015 | A1 |
| 20150178698 | Schulz et al. | Jun 2015 | A1 |
| 20160019531 | Gormley | Jan 2016 | A1 |
| 20160210606 | Henderson et al. | Jul 2016 | A1 |
| 20160259616 | Hosein et al. | Sep 2016 | A1 |
| 20180227712 | Post et al. | Aug 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 2017208387 | Aug 2017 | AU |
| 2 919 238 | Jan 2015 | CA |
| 2 506 642 | Oct 2012 | EP |
| 2004-078662 | Mar 2004 | JP |
| 2005-269172 | Sep 2005 | JP |
| 10-0452161 | Oct 2004 | KR |
| 10-2005-0077659 | Aug 2005 | KR |
| 10-2008-0039330 | May 2008 | KR |
| 0165827 | Sep 2001 | WO |
| 2010097711 | Sep 2010 | WO |
| 2010135174 | Nov 2010 | WO |
| 2013009891 | Jan 2013 | WO |
| 2015013170 | Jan 2015 | WO |
| Entry |
|---|
| Non-Final Office Action dated Dec. 13, 2018, for U.S. Appl. No. 15/909,005, of Post, J.D., et al., filed Mar. 1, 2018. |
| Final Office Action dated Dec. 13, 2018, for U.S. Appl. No. 15/084,390, of Henderson, W., et al., filed Mar. 29, 2016. |
| Examiner Requisition for Canadian Patent Application No. 2,919,238, mailed Dec. 20, 2018. |
| Non-Final Office Action dated Dec. 31, 2018, for U.S. Appl. No. 15/445,380, of Brock, Z., filed Feb. 28, 2017. |
| Notice of Allowance dated Feb. 4, 2019, for U.S. Appl. No. 14/042,366, of Brock, Z., filed Sep. 30, 2013. |
| Advisory Action dated Feb. 8, 2019, for U.S. Appl. No. 14/941,020, of Lee, B., filed Nov. 13, 2015. |
| Examination Report No. 3 for Australian Patent Application No. 2017208387, dated Feb. 11, 2019. |
| Notice Of Allowance dated Mar. 15, 2019, for U.S. Appl. No. 14/941,020 of Lee, B., filed Nov. 13, 2015. |
| Advisory Action dated Mar. 29, 2019, for U.S. Appl. No. 15/084,390, of Henderson, W., et al., filed Mar. 29, 2016. |
| International Search Report and Written Opinion for International Application No. PCT/US2012/046282, dated Oct. 4, 2012. |
| International Search Report and Written Opinion for International Application No. PCT/US2014/047381 dated Nov. 25, 2014. |
| “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. |
| “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. |
| “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. |
| “Arduino magnetic stripe decoder,” Instructables, Retrieved from the Internet URL: http://www.instructables.com/id/Arduino-magneticstripe-decorder/, on Feb. 8, 2011, pp. 1-5. |
| “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. |
| “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. |
| “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. |
| “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. |
| “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 (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. |
| “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. |
| “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. |
| “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. |
| “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. |
| “Pay@PC,” Retrieved from the Internet URL: http://www.merchantanywhere.com/PAY_AT_PCT@PC.htm, on Feb. 11, 2011, pp. 1-2. |
| “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. |
| “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. |
| “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. |
| “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. |
| “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. |
| “Uber—Android Apps on Google Play,” dated Nov. 10, 2014, Retrieved from the internet URL: https://play.google.com/store/apps/details?id=com.ubercab&hl=en, on Nov. 12, 2014, pp. 2. |
| “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. |
| 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. |
| 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. |
| Bourdeauducq, S., “Reading magnetic cards (almost) for free” (“Lekernel”), Jan. 26, 2009, Retrieved from the Internet URL: http://lekernel.net/blog/?p=12, on May 5, 2011, pp. 1-2. |
| Burke, R.R., “The Third Wave of Marketing Intelligence,” Retailing in the 21st Century: Current and Future Trends, pp. 103-115 (2010). |
| 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. |
| Chediak, M., “Retail technology; Grocers get taste of future; Store owners who want to stand out in the crowd these days are embracing cutting-edge services,” The Orlando Sentinel, pp. 1-2 (Jan. 21, 2006). |
| Finzgar et al.; “Use of NFC and QR code identification in an electronic ticket system for public transport”; Published in SoftCOM 2011, 19th International Conference on Software, Telecommunications and Computer networks; Published Nov. 1, 2011 (Year: 2011). |
| Goode, L., “Paying With Square's New Mobile-Payments App,” All Things D., published on Apr. 30, 2012, Retrieved from the Internet URL: http://allthingsd.com/20120430/paying-with-squares-new-mobile-payments-app/, on Nov. 7, 2014, pp. 1-3. |
| Grandison, K., “vTerminal Credit Card Processing App for Authorize Net and PayPal Payflow Pro for Curve 8350 3500 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. |
| Hachman, M., “MobilePay: Your Phone Is Your Credit Card,” dated Sep. 28, 2010, Retrieved from the Internet URL: http://www.pcmag.com/article2/0,2817,2369877,00.asp, on Sep. 25, 2013, p. 1. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| Padilla, L., “Magnetic stripe reader circuit,” Jan. 28, 1997, Retrieved from the Internet URL: http://www.gae.ucm.es/˜padilla/extraworkImagamp.html, on May 5, 2011, pp. 1-7. |
| 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. |
| Shekar, S., et al., “iGrocer—A Ubiquitous and Pervasive Smart Grocery Shopping System,” Proceedings of the 2003 ACM Symposium on Applied Computing, pp. 645-652 (Mar. 9, 2003). |
| Siegler, MG., “MobilePay May Be the Death of the Wallet. Yes, for Real This Time,” TechCrunch, dated Sep. 28, 2010, Retrieved from the internet URL: http://techcrunch.com/2010/09/28/mobilepayusa/, on Sep. 22, 2013, pp. 12. |
| 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. |
| Website: www.alexwinston.com, Aug. 31, 2009, pp. 1-5. |
| Non-Final Office Action dated Aug. 7, 2009, for U.S. Appl. No. 12/050,752, of Niedermeyer, B.J., filed Mar. 18, 2008. |
| Notice of Allowance dated Dec. 16, 2009, for U.S. Appl. No. 12/050,752, of Niedermeyer, B.J., filed Mar. 18, 2008. |
| Von-Final Office Action dated Sep. 10, 2010, for U.S. Appl. No. 12/707,228, of Niedermeyer, B.J., filed Feb. 17, 2010. |
| Final Office Action dated Mar. 31, 2011, for U.S. Appl. No. 12/707,228, of Niedermeyer, B.J., filed Feb. 17, 2010. |
| Non-Final Office Action dated Oct. 10, 2012, for U.S. Appl. No. 13/179,832, of Dorsey, J., et al., filed Jul. 11, 2011. |
| Final Office Action dated Jun. 27, 2013, for U.S. Appl. No. 13/179,832, of Dorsey, J., et al., filed Jul. 11, 2011. |
| Advisory Action dated Oct. 24, 2013, for U.S. Appl. No. 13/179,832, of Dorsey, J., et al., filed Jul. 11, 2011. |
| Non-Final Office Action dated Jan. 8, 2014, for U.S. Appl. No. 13/179,832, of Dorsey, J., et al., filed Jul. 11, 2011. |
| Non Final Office Action dated Dec. 1, 2014, for U.S. Appl. No. 13/802,064, of Lee, B., filed Mar. 13, 2013. |
| Notice of Allowance dated Feb. 6, 2015, for U.S. Appl. No. 13/802,290, of Lee, B., filed Mar. 13, 2013. |
| Final Office Action dated Mar. 20, 2015, for U.S. Appl. No. 13/802,064, of Lee, B., filed Mar. 13, 2013. |
| Notice of Allowance dated Apr. 13, 2015, for U.S. Appl. No. 13/801,340, of Lee, B., filed Mar. 13, 2013. |
| Non Final Office Action dated Oct. 1, 2015, for U.S. Appl. No. 14/803,850, of Lee, B., filed Jul. 20, 2015. |
| Notice of Allowance dated Oct. 13, 2015, for U.S. Appl. No. 13/802,064, of Lee, B., filed Mar. 13, 2013. |
| Non-Final Office action dated Oct. 19, 2015, for U.S. Appl. No. 13/948,871, of Post, J.D., et al., filed Jul. 23, 2013. |
| Non Final Office Action dated Jan. 13, 2016, for U.S. Appl. No. 14/726,165, of Lee, B., filed May 29, 2015. |
| Non-Final Office Action dated Mar. 10, 2016, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., fied Oct. 29, 2013. |
| Notice of Allowance dated May 12, 2016, for U.S. Appl. No. 14/726,165, of Lee, B., filed May 29, 2015. |
| Final Office action dated May 17, 2016, for U.S. Appl. No. 13/948,871, of Post, J.D., et al., filed Jul. 23, 2013. |
| Final Office Action dated Jul. 6, 2016, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
| Final Office Action dated Jul. 22, 2016, for U.S. Appl. No. 14/803,850, of Lee, B., filed Jul. 20, 2015. |
| Non-Final Office Action dated Jul. 29, 2016, for U.S. Appl. No. 14/079,320, of Chatterjee, S., et al., filed Nov. 13, 2013. |
| Examination Report No. 1 for Australian Patent Application No. 2014293388, dated Aug. 2, 2016. |
| Advisory Action dated Sep. 1, 2016, for U.S. Appl. No. 13/948,871, of Post, J.D., et al., filed Jul. 23, 2013. |
| Non-Final Office Action dated Sep. 28, 2016, for U.S. Appl. No. 14/042,366, of Brock, Z., et al., filed Sep. 30, 2013. |
| Non-Final Office action dated Dec. 16, 2016, for U.S. Appl. No. 13/948,871, of Post, J.D., et al., filed Jul. 23, 2013. |
| Examiner Requisition for Canadian Patent Application No. 2,919,238, mailed Feb. 6, 2017. |
| Non Final Office Action dated Mar. 1, 2017, for U.S. Appl. No. 14/941,020, of Lee, B., filed Nov. 13, 2015. |
| Non-Final Office Action dated Apr. 4, 2017, for U.S. Appl. No. 15/269,865, of Lee, B., filed Sep. 19, 2016. |
| Non-Final Office Action dated Apr. 6, 2017, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
| Notice of Allowance dated Apr. 7, 2017, for U.S. Appl. No. 14/803,850, of Lee, B., filed Jul. 20, 2015. |
| Final Office Action dated Apr. 11, 2017, for U.S. Appl. No. 14/079,320, of Chatterjee, S., et al., filed Nov. 13, 2013. |
| Non-Final Office Action dated May 4, 2017, for U.S. Appl. No. 15/084,390, of Henderson, W., et al., filed Mar. 29, 2016. |
| Advisory Action dated Jul. 20, 2017, for U.S. Appl. No. 14/079,320, of Chatterjee, S., et al., filed Nov. 13, 2013. |
| Final Office action dated Jul. 20, 2017, for U.S. Appl. No. 13/948,871, of Post, J.D., et al., filed Jul. 23, 2013. |
| Notice of Allowance dated Jul. 25, 2017, for U.S. Appl. No. 15/269,865, of Lee, B., filed Sep. 19, 2016. |
| Final Office Action dated Sep. 27, 2017, for U.S. Appl. No. 14/941,020, of Lee, B., filed Nov. 13, 2015. |
| Advisory Action dated Oct. 5, 2017, for U.S. Appl. No. 13/948,871, of Post, J.D., et al., filed Jul. 23, 2013. |
| Non-Final Office Action dated Oct. 6, 2017, for U.S. Appl. No. 14/079,320, of Chatterjee, S., et al., filed Nov. 13, 2013. |
| Final Office Action dated Oct. 18, 2017, for U.S. Appl. No. 15/084,390, of Henderson, W., et al., filed Mar. 29, 2016. |
| Final Office Action dated Nov. 1, 2017, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
| Notice of Allowance dated Nov. 6, 2017, for U.S. Appl. No. 13/948,871, of Post, J.D., et al., filed Jul. 23, 2013. |
| Advisory Action dated Jan. 4, 2018, for U.S. Appl. No. 14/941,020, of Lee, B., filed Nov. 13, 2015. |
| Final Office Action dated Jan. 8, 2018, for U.S. Appl. No. 14/042,366, of Brock, Z., et al., filed Sep. 30, 2013. |
| Examiner Requisition for Canadian Patent Application No. 2,919,238, mailed Feb. 9, 2018. |
| Final Office Action dated Feb. 22, 2018, for U.S. Appl. No. 14/079,320, of Chatterjee, S., et al., filed Nov. 13, 2013. |
| Examination Report No. 1 for Australian Patent Application No. 2017208387, dated Feb. 26, 2018. |
| Advisory Action dated Feb. 28, 2018, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
| Non-Final Office Action dated Mar. 22, 2018, for U.S. Appl. No. 14/941,020, of Lee, B., filed Nov. 13, 2015. |
| Advisory Action dated May 15, 2018, for U.S. Appl. No. 14/042,366, of Brock, Z., et al., filed Sep. 30, 2013. |
| Non-Final Office Action dated May 16, 2018, for U.S. Appl. No. 15/084,390, of Henderson, W., et al., filed Mar. 29, 2016. |
| Non-Final Office Action dated Jun. 25, 2018, for U.S. Appl. No. 14/042,366, of Brock, Z., et al., filed Sep. 30, 2013. |
| Non-Final Office Action dated Aug. 6, 2018, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
| Notice of Allowance dated Aug. 8, 2018, for U.S. Appl. No. 14/079,320, of Chatterjee, S., et al., filed Nov. 13, 2013. |
| Final Office Action dated Oct. 30, 2018, for U.S. Appl. No. 14/941,020, of Lee, B., filed Nov. 13, 2015. |
| Examination Report No. 2 for Australian Patent Application No. 2017208387, dated Nov. 9, 2018. |
| Final Office Action dated Apr. 17, 2020, for U.S. Appl. No. 15/445,380, of Brock, Z., filed Feb. 28, 2017. |
| Notice of Allowance dated May 14, 2020, for U.S. Appl. No. 15/084,390, of Henderson, W., et al., filed Mar. 29, 2016. |
| Advisory Action dated Jul. 8, 2019, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
| Final Office Action dated Jul. 8, 2019, for U.S. Appl. No. 15/445,380, of Brock, Z., filed Feb. 28, 2017. |
| Notice of Allowance dated Sep. 25, 2019, for U.S. Appl. No. 15/909,005, of Post, D. J., et al., filed Jan. 3, 2018. |
| Advisory Action dated Sep. 26, 2019, for U.S. Appl. No. 15/445,380, of Brock, Z., filed Feb. 28, 2017. |
| Advisory Action dated Jul. 2, 2020, for U.S. Appl. No. 15/445,380, of Brock, Z., filed Feb. 28, 2017. |
| Non-Final Office Action dated Aug. 17, 2021, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
| Notice of Allowance for Canadian Patent Application No. 2,919,238, dated Jun. 15, 2021. |
| Final Office Action dated Apr. 4, 2019, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
| Final Office Action dated Apr. 4, 2019, for U.S. Appl. No. 15/909,005, of Post, D. J., et al., filed Jan. 3, 2018. |
| Advisory Action dated Jun. 17, 2019, for U.S. Appl. No. 15/909,005, of Post, D. J., et al., filed Jan. 3, 2018. |
| Final Office Action dated Feb. 22, 2022, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
| Notice of Acceptance for Australian Patent Application No. 2019201310, dated Jul. 21, 2020. |
| Notice of Allowance dated Sep. 2, 2020, for U.S. Appl. No. 15/445,380, of Brock, Z., filed Feb. 28, 2017. |
| Notice of Allowance dated May 12, 2022, for U.S. Appl. No. 14/065,760, of Henderson, W., et al., filed Oct. 29, 2013. |
| Notice of Grant for Australian Patent Application No. 2019201310, dated Nov. 12, 2020. |
| Non-Final Office Action dated Oct. 30, 2019, for U.S. Appl. No. 15/084,390, of Henderson, W., et al., filed Mar. 29, 2016. |
| Non-Final Office Action dated Oct. 31, 2019, for U.S. Appl. No. 15/445,380, of Brock, Z., filed Feb. 28, 2017. |
| Examiner Requisition for Canadian Patent Application No. 2,919,238, mailed Nov. 5, 2019. |
| Examination report for Australian Patent Application No. 2019201310, dated Nov. 25, 2019. |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14079320 | Nov 2013 | US |
| Child | 16220094 | US |