This disclosure relates generally to network-enabled appliances and other apparatus, and, more particularly, to systems and methods for activating network-enabled apparatus using web-based near field communication (NFC) protocols.
Many home appliances, vehicles, and IT systems now have virtually immediate network connectivity upon installation in the home. Typical activation procedures, however, require the homeowner to connect the new appliance or other apparatus to their home network, then download an installation application to their home computer or mobile device. The application then walks the homeowner through the process of activating and provisioning the new apparatus according to the homeowner's use preferences. Typically, this requires the user to locate and enter identification information for the new device. The application may also require that the homeowner provide account information required for management or use of the device.
An illustrative aspect of the invention provides network-enabled apparatus comprising an apparatus data processing system, at least one operational system in communication with the apparatus data processing system and configured for carrying out a mechanical or electrical operation, a first network communication interface configured for establishing communication over a wide area network, a second network communication interface configured for establishing communication over a local network, and a memory. The memory has stored therein apparatus identification information, at least one service application comprising instructions for the apparatus data processing system to implement a service operation using the at least one operational system, and an activation application. The activation application comprises instructions for the apparatus data processing system to establish an internet connection via the first network communication interface and create an NFC-enabled web page. The application further comprises instructions to transmit, to a user device via the second communication interface, an instruction to navigate to the NFC-enabled web page and instructions to transmit to the user device via the NFC-enabled web page an instruction for a user of the user device to tap an NFC-enabled smart transaction card to the user device. The activation application also comprises instructions to read, via the NFC-enabled web page, NFC information transmitted to the user device by the smart transaction card. The NFC information includes card identification information unique to the smart transaction card. The activation application still further comprises instructions to transmit the NFC information and the apparatus identification information to a service administration server, and receive, from the service administration server, a service activation command. Responsive to the service activation command, the application will cause activation of at least one of the at least one service application.
Another aspect of the invention provides a method for activating a network-enabled apparatus using an NFC-enabled user device and an NFC-enabled smart transaction card associated with a card account. The method comprises establishing an internet connection by the network-enabled apparatus, creating an NFC-enabled web page by the network-enabled apparatus, and transmitting, by the network-enabled apparatus to the user device, an instruction to navigate to the NFC-enabled web page. The method further comprises transmitting, by the network-enabled apparatus to the user device via the NFC-enabled web page, an instruction for the user to tap the smart transaction card to the user device, and reading, by the network-enabled apparatus via the NFC-enabled web page, NFC information transmitted to the user device by the smart transaction card. The NFC information includes card identification information unique to the smart transaction card. The method still further comprises transmitting, by the network-enabled apparatus to a service administration server of a service administrator, the NFC information and apparatus identification information, identifying, by the service administration server using the apparatus identification information, the network-enabled apparatus, and transmitting the NFC information by the service administration server to a card administration server. The method also comprises receiving, by the service administration server from the card administration server, card account information associated with the card account, identifying an account holder by the service administration server using the card account information, and associating, by the service administration server, the network-enabled apparatus with the card account and an apparatus service account with the service administrator. The method further comprises transmitting, by the service administration server to the network-enabled apparatus, a service activation command.
Another aspect of the invention provides a method for activating a network-enabled apparatus using an NFC-enabled user device and an NFC-enabled smart transaction card associated with a card account. The method comprises establishing communication between the network-enabled apparatus and the user device, creating an NFC-enabled web page by the network-enabled apparatus, and navigating to the NFC-enabled webpage by a web browser on the user device. The method further comprises establishing NFC communication between the smart transaction card and the user device and reading, by the network-enabled apparatus via the NFC-enabled web page, NFC information transmitted to the user device by the smart transaction card. The NFC information includes card identification information unique to the smart transaction card. The method still further comprises transmitting, by the network-enabled apparatus to a service administration server, the NFC information and apparatus identification information and transmitting the NFC information by the service administration server to a card administration server. The method also comprises identifying, by the card administration server using the NFC information, a card account associated with the smart transaction card and transmitting, by the card administration server to the service administration server, card account information associated with the card account. The method yet further comprises identifying an account holder by the service administration server using the card account information, associating, by the service administration server, the network-enabled apparatus with the card account and an apparatus service account with the service administrator, and transmitting, by the service administration server to the network-enabled apparatus from the service administration server, a service activation command.
The invention can be more fully understood by reading the following detailed description together with the accompanying drawings, in which like reference indicators are used to designate like elements, and in which:
While the invention will be described in connection with particular embodiments and manufacturing environments, it will be understood that the invention is not limited to these embodiments and environments. On the contrary, it is contemplated that various alternatives, modifications and equivalents are included within the spirit and scope of the invention as described.
The present invention provides systems and methods for activating and provisioning various network-connected smart appliances and other apparatus. As homes become integrated via the “Internet of things”, homeowners are finding that every time they purchase a new appliance, they must go through an elaborate process to add the appliance to their home network, establish service, and configure the appliance to fit their needs. This process may be required for any uniquely identifiable smart appliance or device (i.e. any device having a network-enabled processing system). In a typical prior art scenario, a user purchases a device such as a Wi-Fi router for use in conjunction with an Internet service provider (ISP). The user must establish an account with the ISP and then may be asked to download an application for use in initializing the router and establishing Internet service. The app may require the user to log on to the user's account, then scan a barcode on the bottom of the router. The ISP then associates the router with the user account and steps the user through a series of queries that can be used to establish service and configure the router.
In the methods of the present invention, the appliance or other apparatus may be provided with the capability of establishing its own web page which can be used to obtain information from an NFC-capable transaction card via the user's mobile or other device. This can be accomplished without the need for an application on the mobile device with API calls configured for reading and interpreting the NFC information from the transaction card. The transaction card information may be read directly by the smart device and then passed to the ISP or other service provider, which may use the card information to identify the user and establish service. This provides for enhanced efficiency and security of the service initialization process as well as simplifying the process for the user.
NFC works using magnetic induction. The powered NFC reader creates a magnetic field in which a transmitter (typically unpowered) may be immersed. Immersion in the magnetic field produces a current within the transmitter that can be used to power transmission of data to the receiver. NFC capability may be incorporated into transaction processing devices (e.g., merchant check-out devices) or into mobile and other user devices. The NFC transmitter may be a passive tag or, as will be discussed in more detail below, may be incorporated into a smart transaction card.
While NFC capability may be built into a user device, the ability to interpret NFC-transmitted information from a tag or other transmitter requires the use of an application on-board the user device. For example, if a mobile device is to read and interpret a tag's unique identifier, the user must open the application before establishing NFC communication with the tag. The tag may then be brought into NFC range of the user device, whereupon the device reads and interprets the tag's identifier. Absent the application, the NFC information can be “read” but the information is unusable.
To avoid the need for an NFC application to be loaded on the user device, embodiments of the invention make use of browser-based NFC (referred to herein as “Web NFC”). Web NFC is a simplified API for using NFC via web page JavaScript. Web NFC uses a high level approach instead of a powerful low level API that requires special privileges. In short, Web NFC allows the reading of NFC tags through a browser on the user device. This means that no additional application needs to be downloaded to the user device. The NFC-transmitted information is simply passed through the user device to the server or apparatus operating through the web page.
As will be discussed in more detail below, the methods of the invention may be used in conjunction with a typical home network and appliance control system having one or more network-enabled smart apparatus connected to a user device via a local network. (See
An exemplary scenario for a method of the invention may follow a sequence of operations for initializing and provisioning a network-enabled smart apparatus as shown in
The NFC information may be or include a unique identifier for the transaction card that is associated with a card account of the user. At 1300, the smart apparatus may transmit some or all of the NFC information, including the card identifier, to the service administration server associated with the apparatus or a service to be provided by the apparatus. The apparatus may also transmit its own unique identifier. The service administration server may then use the NFC information to identify the administrator of the account associated with the card. At 1400, the service administration server transmits some or all of the NFC information, including the card identifier, to a server of the card account administrator. The card account administrator uses the NFC information to determine the account associated with the transaction card and transmits, at 1500, account information back to the service administration server. This account information may include information about the account holder that the service administration server can use to determine whether the user has an existing service account with the service administrator or to establish a new service account for the user. The service administration server may then associate the account information with the apparatus and transmit a service activation command to the apparatus at 1600. The service activation command may include default provisioning instructions or provisioning instructions determined based on existing service account preferences. In some embodiments, the service administration server may contact the user to prompt for and receive provisioning preferences.
From the user perspective, the above scenario provides a highly simplified activation/provisioning experience in which the user does no more than connect the apparatus, establish communication between the apparatus and the user device, open the web page identified by the apparatus, and tap the transaction card to the user device.
The systems and methods of the invention will now be discussed in more detail.
With reference to
The data processing system 191 comprises the elements for communicating with the apparatus 190 and for controlling its operation. These may include a control data processor 192 configured for monitoring and controlling one or more operational parameters of the operational system 197. Such parameters may be as simple as “on or off” or more complex such as the parameters associated with a wash cycle in a washer (e.g., control and timing of water filling and draining, water temperature, agitation cycling, etc.). Operational instructions for the control processor 192 may be stored in a memory module 195. These instructions may be a combination of permanently stored instructions and temporary, user-supplied instructions. In many instances, the memory 195 may have stored therein predetermined operational modes. The memory 195 may also have stored therein operational restrictions that prevent operation of the operational system 197 under predetermined circumstances (e.g., an over-heating condition or excessive current draw). These could require, for example, the control processor 192 to alter the operational mode of the operational system 197 or even shut it down completely.
The memory module 195 may also have stored therein one or more service applications comprising instructions for the apparatus data processing system to implement a service operation. These service applications may include instructions for the control processor 192 to implement operational instructions received from the user or from a service administrator associated with the apparatus 190 or with services provided by or through the apparatus 190. For example, in a case where the apparatus 190 is a router for use in connecting other devices to the Internet, the service administrator could be an ISP and one or more of the service applications may be established and/or controlled by the ISP.
The memory module 195 may have stored therein software for configuring a web page for facilitating initialization of apparatus 190 operation. The web page coding may include Web NFC JavaScript configured for reading transaction card-transmitted NFC information via the browser of a user device.
User input to the data processing system 191 may be received through the use of a user interface 194, which may be or include any device for entering information, control input, and instructions into the system 191. In many cases, the user interface 194 may be a combination of buttons and/or dials having preset control functions. In some apparatus, the user interface 194 may include more complex devices such as a touch-screen, keyboard, mouse, cursor-control device, microphone, stylus, or digital camera.
The data processing system 191 also includes a local area communication interface 193 in communication with the control processor 192 and configured for communication over one or more networks such as the local network 105 of
In some embodiments, the data processing system 191 may include a wireless hotspot module 199 in communication with the WAN communication interface 198. The hotspot module 199, in combination with software stored in the memory module 195, is configured for operation as a limited range wireless access point that may be accessed by the user device 110 for communication therewith.
The smart apparatus 190 may include a sensor arrangement 196 in communication with the control processor 192. The sensor arrangement 196 may be configured for monitoring one or more operational parameters of the operational system 197 and/or a measurable parameter of the environment in which the apparatus 190 is operating. In the case of a refrigerator, for example, the sensor arrangement 196 could include temperature sensors for monitoring the temperature in various compartments of refrigerator. In a home heating system, the sensor arrangement 196 could include a room air temperature sensor. The sensor arrangement 196 may also include sensors for monitoring a condition or operating characteristic of the operational system 197. This could include, for example, a sensor for measuring an internal machine temperature that could, if it exceeds a certain level, result in damage to the apparatus. Sensor measurement information is transferred from the sensor arrangement 196 to the control processor 192, which uses it to control operation of the operational system 197.
The memory 195 may also have stored therein an apparatus activation application that may be configured for execution upon the apparatus first being powered up and connected to the Internet. The activation application may include instructions for the control processor 192 to receive, via the local network communication interface 193 or via the wireless hotspot module 199, a service initiation communication from a user device 110. The application may further include instructions to establish Internet communication via the wide area network communication interface 198 and to create a Web NFC-enabled web page. The application may then cause the control processor 192 to transmit to the user device via the local communication interface 193 or the wireless hotspot module 199, a communication that includes the address for the web page and instructs the user to navigate to the web page, which instructs the user to tap an NFC-enabled smart transaction card to the user device. The application then uses the Web NFC methodology to read NFC information transmitted to the user device by the smart transaction card, the NFC information including card identification information unique to the smart transaction card. The application then causes the processor 192 to transmit the NFC information and to a service administration server along with an apparatus identifier stored in the memory 195. The application is configured to receive an activation command back from the service administration server. The service command may include initial operation instructions and/or initial provisioning options for configuring the apparatus for operation. In response, the application may activate apparatus operation and/or one or more service applications.
In some embodiments, the smart apparatus 190 may be a service apparatus configured for facilitating the delivery or monitoring of a utility (e.g., electricity, water, or gas service), a telecommunications link, or data delivery system (e.g., cable or satellite). In such embodiments, the service administrator may be the supplier of the utility, telecommunications service, or data delivery service. For example, if the smart apparatus is or is part of an electrical distribution system, the service administrator would be the power company supplying the electricity.
With reference to
The user interface 115 includes a user input mechanism, which can be any device for entering information and instructions into the account holder device 110, such as a touch-screen, keyboard, mouse, cursor-control device, microphone, stylus, or digital camera. The user interface 115 may also include a display, which can be any type of device for presenting visual information such as a computer monitor, a flat panel display, and a mobile device screen, including liquid crystal displays, light-emitting diode displays, plasma panels, and cathode ray tube displays.
The communication interface 117 is configured to establish and support wired or wireless data communication capability for connecting the device 110 to a broad network (e.g., network 230 of
The user device 110 may further include an NFC interface 119 that includes an NFC receiver configured for selectively activating a magnetic field for use in establishing near field communication with an NFC transmitter. The NFC interface 119 is configured for establishing NFC communication when a passive NFC tag or other NFC-enabled device is brought into the magnetic field and within NFC communication range of the user device 110. The NFC interface 119 is configured, in particular, for communication with an NFC-enabled smart transaction card 102 when the card 102 is tapped to the user device 110.
In embodiments of the invention, the memory 113 may have stored therein one or more applications usable by the data processor 111 to conduct and/or monitor transactions on a transaction account between the account holder device 110 and a merchant device or other device. These applications may include instructions usable by the data processor 111 to identify transaction events, store event data in the memory 113, and communicate event data to a transaction processing server and/or an account management server. Some applications may also include instructions relating to receiving and interpreting notifications and/or instructions from the transaction processor or account administration server (e.g., card account administration server 260 of
In particular embodiments, the memory 113 may have stored therein a financial monitoring application configured for receiving account information from an account management server. The account information may include information on any account parameter including, but not limited to, a current account balance, average account balance, project account balance, expenditures over a time interval or since a beginning date of a time interval (e.g., the first day of the month). The account information may also include information such as a previous account balance, information on recent transactions, information on projected or scheduled transactions (e.g., automatic deposits or withdrawals), and payments to particular merchants.
The user device memory 113 may also have stored therein a smart apparatus control application configured with instructions for the data processor 111 to construct and transmit control instructions to one or more of the smart apparatus 120, 130, 140, 150, 160, 170, 190 via the local network 105. The application may be configured to tailor these instructions according to information stored in the memory 113 for the apparatus being controlled. The instructions associated with a generic apparatus 190 may include instructions for displaying prompts to the account holder for and receiving from the account holder via the user interface 115 control input information for the apparatus 190. The control input information may include an operation mode selection, specification of one or more operational parameters, and/or one or more desired apparatus output parameter. The control application may be configured to instruct the data processor to receive the control input information and construct apparatus control instructions and transmit them to the data processing system 191 of the apparatus 190 via the local network 105. The apparatus control instructions may include an instruction to set or change an operational parameter of the apparatus 190.
The control application may be further configured with instructions for receiving operation information from the data processing system 191 of the apparatus 190. The application may be configured to review this information and determine whether to display some or all of the information to the account holder via the user interface 115. In some embodiments, the control application may be configured to prompt for and receive additional control input information in response to the operation information received from the apparatus 190.
The user device memory 113 may also have stored therein an apparatus operation monitoring application having instructions configured for receiving information on the operation of an apparatus to determine if automated changes to its operation may be having a negative or unintended effect on the apparatus. This may include instructions to receive and evaluate operation information from any or all of the apparatus 120, 130, 140, 150, 160, 170, 190. Such operation information may include information on one or more measured operational parameters for the apparatus and/or measured environment parameters.
In some embodiments, the control application may include instructions for the data processor 111 to use financial parameter information and operational parameter information along with empirical life expectancy and/or cost information for an apparatus 190 to determine an optimized set of operational parameters for that apparatus 190. The optimized set of operational parameters can then be included in change control instructions transmitted by the data processor 111 to the control processor 192 of the apparatus 190.
With reference now to
The various components of the system 200 may include various network-enabled computer systems configured for processing information and transactions involving a plurality of service accounts administered by an apparatus service administrator and/or a plurality of transaction card accounts administered by a financial institution, merchant or other card account administrator. As referred to herein, a network-enabled computer system and/or device may include, but is not limited to any computer device, or communications device including, a server, a microprocessor or system of microprocessors, a network appliance, a personal computer (PC), a workstation, and a mobile processing device such as a smart phone, smart pad, handheld PC, or personal digital assistant (PDA). In some examples, the computer device may use instructions stored on a computer-accessible medium (e.g., a storage device such as a hard disk, floppy disk, memory stick, CD-ROM, RAM, ROM, etc., or a collection thereof). The computer-accessible medium can contain executable instructions thereon. In addition or alternatively, a storage arrangement can be provided separately from the computer-accessible medium, which can provide the instructions to the processing arrangement so as to configure the processing arrangement to execute certain exemplary procedures, processes, and methods, as described herein.
The network-enabled computer systems used to carry out the actions contemplated by the invention may execute one or more software applications to, for example, receive data as input from an entity accessing the network-enabled computer system, process received data, transmit data over a network, and receive data over a network. The one or more network-enabled computer systems may also include one or more software applications to notify an account holder based on transaction information.
It will be understood that the depiction in
The network 230 may be any form of communication network capable of enabling communication between the subsystems of the system 200. For example, the network 230 may be one or more of a wireless network, a wired network or any combination of wireless network and wired network. The network 230 may be or include one or more of a fiber optics network, a passive optical network, a cable network, an Internet network, a satellite network, a wireless LAN, a Global System for Mobile Communication (“GSM”), a Personal Communication Service (“PCS”), a Personal Area Network (“PAN”), Wireless Application Protocol (WAP), Multimedia Messaging Service (MMS), Enhanced Messaging Service (EMS), Short Message Service (SMS), Time Division Multiplexing (TDM) based systems, Code Division Multiple Access (CDMA) based systems, D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b, 802.15.1, 802.11n and 802.11g or any other wired or wireless network for transmitting and receiving a data signal. The network 230 may utilize one or more protocols of one or more network elements to which it is communicatively coupled. The network 230 may translate to or from other protocols to one or more protocols of network devices. Although the network 230 is depicted as a single network, it will be appreciated that it may comprise a plurality of interconnected networks, such as, for example, the Internet, a service provider's network, a cable television network, corporate networks, and home networks.
In the example embodiments presented herein, an account holder may be any individual or entity permitted to conduct a transaction (which may be, but is not limited to a financial transaction) using a transaction card account. An account may be held by any place, location, object, entity, or other mechanism for holding money or performing transactions in any form, including, without limitation, electronic form. An account may be, for example, a credit card account, a prepaid card account, stored value card account, debit card account, check card account, payroll card account, gift card account, prepaid credit card account, charge card account, checking account, rewards account, line of credit account, credit account, mobile device account, or mobile commerce account. An account holder may be a transaction processing entity such as a financial institution, credit card provider, or other entity that offers accounts to customers.
A transaction account may be associated with one or more smart transaction cards 220 (e.g., debit cards, credit cards, or prepaid account cards). Alternatively or in addition, the transaction account may be associated with one or more account holder processing devices or simply associated with a unique identifier enterable by an account holder to facilitate a transaction. The processing devices may be configured to act as a method of payment at a POS location using, for example, NFC or any other mobile payment technology. In some embodiments, separate cards or user devices may be associated with individual account co-holders.
The transaction card 220 may be any chip-carrying transaction card (“smart” card) having electrical and/or near field or other short range communication capabilities. As illustrated in
The transaction card 220 is configured for communication with transaction terminals and other device via a first communication interface 224. The interface 224 and the microprocessor 222 may, in particular, be configured for establishing communication with merchant transaction processing devices for carrying out purchase and other transactions. The communication interface 224 may be configured to provide for contact-based communication, in which case the interface 224 may have electrical circuitry and contact pads on the surface of the card 220 for establishing direct electrical communication between the microprocessor 222 and the processing circuitry of a transaction terminal. Alternatively or in addition, the first communication interface 224 may be configured for contactless communication with a transaction terminal or other wireless device. In such embodiments, the communication interface 224 may be or include an NFC communication interface configured for communication with other NFC communication devices when the card 220 is within a predetermined NFC range. The communication interface 224 and the microprocessor 222 may, in particular, be configured for establishing NFC communication with the user device 210. In some embodiments, the microprocessor chip 221 may include a second communication interface 228 configured for establishing short range communication with the user device 210 via Bluetooth, or other short range communication methodology. In such embodiments, the transaction card 220 may have a short range communication antenna 229 that is included in or connected to the short range communication interface 228. The microprocessor chip 221 may also include a power management system 225 for use in managing the distribution of power during an NFC transaction.
In particular embodiments, the transaction card 220 may be Bluetooth enabled using the microprocessor chip 221, the second communication interface 228 and the antenna 229. A Bluetooth-enabled transaction card may support Bluetooth Low Energy (BLE) and may be paired to the user device 210. In some embodiments, pairing and communications may be established between the transaction card 220 and other interfacing devices, such as a terminal (not shown), a merchant transaction processor 140, and the like. A Bluetooth-enabled device may include the capabilities to establish a link between a card and the device (or pair the devices) using device settings (e.g., iOS or Android settings that manage Bluetooth connections) and/or mobile application(s) associated with the card issuer that can cooperate with the device controls to manage a Bluetooth connection with the card 220.
The memory 226 may be a read-only memory, write-once read-multiple memory or read/write memory, e.g., RAM, ROM, and EEPROM, and the chip 221 may include one or more of these memories. The memory 226 may have stored therein information associated with a transaction card account. In some embodiments, the memory 226 may have permanently stored therein a unique alphanumeric identifier associated with the account. It may also have stored public and private card encryption keys. In some embodiments, the private and public encryption keys may be permanently hard-wired into the card memory.
The memory 226 may be configured to store one or more software applications for execution by the microprocessor 222. In various embodiments, the memory 226 may have stored therein instructions for generating encrypted information and transmitting it to a receiving device (e.g., the user device 210) via the first communication interface 224 (e.g., via NFC) or the short-range communication interface 228. Such encrypted information may be or include an encrypted verification block or signature that may be used to authenticate and verify the presence of the transaction card 220 during transaction processing. In some embodiments, encrypted information be unique to a particular communication (e.g., a particular NFC transmission by the transaction card).
The apparatus service administration server 250 may be associated with and/or managed by the manufacturer or the seller (or lessor) of the smart apparatus 290. Alternatively, the service administration server 250 may be associated with a provider of a service administered through the apparatus 290. With reference to
The service account management processor 256 in communication with account information database 251 is configured to receive card account holder information from the apparatus initialization processor 254. The service account management processor 256 may then use the card account holder information to identify the card user and determine whether the user has a service account with the service provider. This may be accomplished by comparing the card account information with account information stored in a service account information database 251. If the user has an account, the processor 256 may associate the apparatus identifier of the apparatus 290 with the existing service account of the user. If the user does not have an existing account, the processor 256 may create a new service account using the card account information for the user. In some embodiments, the service account management processor 256 may contact the user (e.g., via a transmission to the user device 210 over the network 230) to verify that the user wishes to open a new service account or to obtain user preferences in establishing the account and/or operational parameters of the smart apparatus 290. The service account management processor 256 may then associate the smart apparatus 290 with the new account and store the service account information in the account information database 251.
Upon associating the apparatus 290 with either an existing account or a new account, the account management processor 256 may then send the service account information back to the initialization processor 254, which constructs and transmits an initialization command to the smart apparatus 290. This command may include initial provisioning information as well as an instruction to initiate apparatus operation.
In some embodiments, the service administration server 250 may also include an apparatus operation management processor 258, which is configured to communicate with the apparatus 290 for monitoring and management of apparatus operation. In some cases, the operation management processor 258 may communicate with the user regarding the user's operational preferences or instructions. The apparatus operation management processor 258 may also be configured to provide system updates to the data processing system of the smart apparatus 290. In some embodiments, the operation management processor 258 may also be configured to determine time or use-based service fees associated with the use of the apparatus or for services accessed or used via the apparatus. The operation management processor 258 may also be configured to automatically charge some or all of such service fees to the transaction card account associated with the transaction card 220 or to another financial account of the service account holder.
The card account administration server 260 is a system of one or more network-enabled processing servers configured to monitor and/or process transactions involving the transaction card 220 and to process information requests relating to a card account associated with the transaction card 220. With reference to
The card account administration server 260 has a transaction processor 264 and a card account information server 266, both of which are configured for communication over the network 230 via the transaction communication interface 262. The card account information server 266 may be configured for maintaining a transaction card account database (not shown) in which is stored identification information for each of the plurality of transferable cards along with associated account information. Such account information may include identification, contact, and other information relating to the account holder.
The card account information server 266 may be further configured for assigning private and public personal encryption keys to an account of an account holder to whom a transaction card 220 has been issued or is to be issued. Once assigned, the card management server may transmit, via the network 230, the personal encryption keys to a user device 210 associated with the account holder. The card processing system may be further configured to receive a request from the user device 210, via the network 230 and the transaction communication interface 262, to activate the transaction card 220. The activation request includes a software signature encrypted by the user device 210 using the public and private personal encryption keys and a hardware signature encrypted by of the card's microprocessor chip 221 using the public and private card encryption keys stored therein. The card account information server 266 is further configured to, upon receiving the activation request, decrypt the software and hardware signatures to verify their association with the account, and, upon positive verification, activate the transaction card 220 by associating one or more authorized account functions with the transaction card 220. The server 266 may then store information reflecting the activation in the card database. An authorized account function could be any typical transaction card functionality such as, for example, interaction with a merchant transaction processing device to carry out a purchase transaction or use in an automatic teller machine. In particular embodiments, the authorized account functions may include the use of the transaction card 220 to initiate service and/or create a service account associated with the smart apparatus 290.
The card account information server 266 may also be configured to receive account information requests from a merchant or service account administrator to whom the transaction card 220 has been presented. In particular, the server 266 may be configured to receive an account information request from the service account management processor 256. The request may include NFC information transmitted by the transaction card 220 and read by the smart apparatus 290. In embodiments where a portion of the NFC information is encrypted using keys stored on the transaction card, the server 266 may be configured to retrieve the encryption keys associated with the transaction card 220 and decrypt the encrypted information to authenticate the and verify the presence of the transaction card 220.
At S140, the apparatus data processing system transmits an instruction to the user device to tap the transaction card to the user device. This instruction may be presented via the web page or by a separate transmission via the local network or apparatus-generated hotspot. Upon the user tapping the transaction card to the user device, the apparatus data processing system reads, via Web NFC code, NFC information transmitted to the user device by the transaction card at S150. The NFC information includes, at least, sufficient information to identify the transaction card administrator and information usable by the transaction card administrator to identify the card and its associated transaction account. At S160, the apparatus data processing system transmits an activation request to the service administration server via the apparatus's network connection. The activation request may include a unique identifier for the apparatus and some or all of the NFC information read from the transaction card. At S170, the apparatus data processing system receives a service activation command from the service administration server. This command may include an instruction to initiate operation and/or initial operation and provisioning instructions. In some embodiments, the apparatus may also receive service account information. At S180, the apparatus initiates operation or, in some cases, established operational readiness. In the latter cases, the apparatus may require additional instruction or manipulation by the user before actually “turning on”. In some embodiments, the apparatus may optionally send a service initiation notification to the user device at S190. This may be transmitted via the local network, the apparatus's self-generated hotspot, or through the wide area or other communications network.
At S220, the service administration server uses the NFC information to identify a card account administrator associated with the transaction card transmits a card account information request to a card account administration server of that administrator. This request may include some or all of the NFC information, including card identification information, some or all of which may be encrypted. At S230, the service administration server receives card account information back from the card account administration server. This information may include identification, contact, and other information relating to the account holder/user. At S240, the server uses the account information to identify the account holder/user wishing to activate the smart apparatus. At S250, the server associates the apparatus identification information with a service account associated with the account holder. The account and apparatus ID information may be stored by the server in a service account information database. At S260, the service administration server may optionally determine user preferences for apparatus service or operating parameters. If the account holder already had an existing account, this may include importing previously established preferences for the account holder. Alternatively or in addition, the account holder may be contacted to provide or confirm the account holder's preferences. At S270, the server constructs a service activation command. This command may include an instruction to initiate operation and/or initial operation and provisioning instructions, which may be based on user preferences. In some embodiments, the command may also include service account and/or account holder information. At S280, the service administration server transmits the service activation command to the smart apparatus via the network.
At S320, the service administration server uses the NFC information to identify a card account administrator associated with the transaction card and, at S330, transmits a card account information request to a card account administration server of that administrator. This request may include some or all of the NFC information, including card identification information, some or all of which may be encrypted. At S340, the service administration server receives card account information back from the card account administration server. This information may include identification, contact, and other information relating to the account holder/user. At S350, the server uses the account information to identify the card account holder wishing to activate the smart apparatus and determines whether that card account holder has a service account with the service administrator. This may include comparing the card account information with account information stored in a service account information database. If the user has an account, the processor sets the current service account to be the existing account at S351. If the user does not have an existing account, the server may create a new service account at S352 using the card account information. In some embodiments, the service administration server may contact the card account holder (e.g., via a transmission to the account holder's user device over the network) to verify that the user wishes to open a new service account or to obtain user preferences in establishing the account and/or operational parameters of the smart apparatus. After opening the new account, the service administration server may then set the current account to be the new service account at S354. At S360, the server may associate the smart apparatus with the existing or new account as appropriate and store the service account information in the account information database.
At S370, the service administration server may optionally determine user preferences for apparatus service or operating parameters. If the account holder already had an existing account, this may include importing previously established preferences for the account holder. Alternatively or in addition, the account holder may be contacted to provide or confirm the account holder's preferences. At S380, the server constructs a service activation command. This command may include an instruction to initiate operation and/or initial operation and provisioning instructions, which may be based on user preferences. In some embodiments, the command may also include service account and/or account holder information. At S390, the service administration server transmits the service activation command to the smart apparatus via the network.
The present invention provides a significant improvement in the security and efficiency of systems initiating operation of smart appliances, vehicles, and other apparatus by eliminating the need to download a specialized application to a user device. The method also enhances security by providing direct pass-through of transaction card identification information without interpretation or decryption by the user device being used to activate the apparatus.
It will be readily understood by those persons skilled in the art that the present invention is susceptible to broad utility and application. Many embodiments and adaptations of the present invention other than those herein described, as well as many variations, modifications and equivalent arrangements, will be apparent from or reasonably suggested by the present invention and foregoing description thereof, without departing from the substance or scope of the invention.
This application is a continuation of U.S. application Ser. No. 17/213,943, filed Mar. 26, 2021, the complete disclosure of which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4683553 | Mollier | Jul 1987 | A |
4827113 | Rikuna | May 1989 | A |
4910773 | Hazard et al. | Mar 1990 | A |
5036461 | Elliott et al. | Jul 1991 | A |
5363448 | Koopman, Jr. et al. | Nov 1994 | A |
5377270 | Koopman, Jr. et al. | Dec 1994 | A |
5533126 | Hazard | Jul 1996 | A |
5537314 | Kanter | Jul 1996 | A |
5592553 | Guski et al. | Jan 1997 | A |
5616901 | Crandall | Apr 1997 | A |
5666415 | Kaufman | Sep 1997 | A |
5764789 | Pare, Jr. et al. | Jun 1998 | A |
5768373 | Lohstroh et al. | Jun 1998 | A |
5778072 | Samar | Jul 1998 | A |
5796827 | Coppersmith et al. | Aug 1998 | A |
5832090 | Raspotnik | Nov 1998 | A |
5883810 | Franklin et al. | Mar 1999 | A |
5901874 | Deters | May 1999 | A |
5929413 | Gardner | Jul 1999 | A |
5960411 | Hartman et al. | Sep 1999 | A |
6021203 | Doucem et al. | Feb 2000 | A |
6049328 | Vanderheiden | Apr 2000 | A |
6058373 | Blinn et al. | May 2000 | A |
6061666 | Do et al. | May 2000 | A |
6105013 | Curry et al. | Aug 2000 | A |
6199114 | White et al. | Mar 2001 | B1 |
6199762 | Hohle | Mar 2001 | B1 |
6216227 | Goldstein et al. | Apr 2001 | B1 |
6227447 | Campisano | May 2001 | B1 |
6282522 | Davis et al. | Aug 2001 | B1 |
6324271 | Sawyer et al. | Nov 2001 | B1 |
6342844 | Rozin | Jan 2002 | B1 |
6367011 | Lee et al. | Apr 2002 | B1 |
6402028 | Graham, Jr. et al. | Jun 2002 | B1 |
6438550 | Doyle et al. | Aug 2002 | B1 |
6501847 | Helot et al. | Dec 2002 | B2 |
6631197 | Taenzer | Oct 2003 | B1 |
6641050 | Kelley et al. | Nov 2003 | B2 |
6655585 | Shinn | Dec 2003 | B2 |
6662020 | Aaro et al. | Dec 2003 | B1 |
6721706 | Strubbe et al. | Apr 2004 | B1 |
6731778 | Oda et al. | May 2004 | B1 |
6779115 | Naim | Aug 2004 | B1 |
6792533 | Jablon | Sep 2004 | B2 |
6829711 | Kwok et al. | Dec 2004 | B1 |
6834271 | Hodgson et al. | Dec 2004 | B1 |
6834795 | Rasmussen et al. | Dec 2004 | B1 |
6852031 | Rowe | Feb 2005 | B1 |
6865547 | Brake, Jr. et al. | Mar 2005 | B1 |
6873260 | Lancos et al. | Mar 2005 | B2 |
6877656 | Jaros et al. | Apr 2005 | B1 |
6889198 | Kawan | May 2005 | B2 |
6905411 | Nguyen et al. | Jun 2005 | B2 |
6910627 | Simpson-Young et al. | Jun 2005 | B1 |
6971031 | Haala | Nov 2005 | B2 |
6990588 | Yasukura | Jan 2006 | B1 |
7006986 | Sines et al. | Feb 2006 | B1 |
7085931 | Smith et al. | Aug 2006 | B1 |
7127605 | Montgomery et al. | Oct 2006 | B1 |
7128274 | Kelley et al. | Oct 2006 | B2 |
7140550 | Ramachandran | Nov 2006 | B2 |
7152045 | Hoffman | Dec 2006 | B2 |
7165727 | de Jong | Jan 2007 | B2 |
7175076 | Block et al. | Feb 2007 | B1 |
7202773 | Oba et al. | Apr 2007 | B1 |
7206806 | Pineau | Apr 2007 | B2 |
7232073 | de Jong | Jun 2007 | B1 |
7246752 | Brown | Jul 2007 | B2 |
7254569 | Goodman et al. | Aug 2007 | B2 |
7263507 | Brake, Jr. et al. | Aug 2007 | B1 |
7270276 | Vayssiere | Sep 2007 | B2 |
7278025 | Saito et al. | Oct 2007 | B2 |
7287692 | Patel et al. | Oct 2007 | B1 |
7290709 | Tsai et al. | Nov 2007 | B2 |
7306143 | Bonneau, Jr. et al. | Dec 2007 | B2 |
7319986 | Praisner et al. | Jan 2008 | B2 |
7325132 | Takayama et al. | Jan 2008 | B2 |
7373515 | Owen et al. | May 2008 | B2 |
7374099 | de Jong | May 2008 | B2 |
7375616 | Rowse et al. | May 2008 | B2 |
7380710 | Brown | Jun 2008 | B2 |
7424977 | Smets et al. | Sep 2008 | B2 |
7453439 | Kushler et al. | Nov 2008 | B1 |
7472829 | Brown | Jan 2009 | B2 |
7487357 | Smith et al. | Feb 2009 | B2 |
7568631 | Gibbs et al. | Aug 2009 | B2 |
7584153 | Brown et al. | Sep 2009 | B2 |
7597250 | Finn | Oct 2009 | B2 |
7628322 | Holtmanns et al. | Dec 2009 | B2 |
7652578 | Braun et al. | Jan 2010 | B2 |
7689832 | Talmor et al. | Mar 2010 | B2 |
7703142 | Wilson et al. | Apr 2010 | B1 |
7748609 | Sachdeva et al. | Jul 2010 | B2 |
7748617 | Gray | Jul 2010 | B2 |
7748636 | Finn | Jul 2010 | B2 |
7762457 | Bonalle et al. | Jul 2010 | B2 |
7789302 | Tame | Sep 2010 | B2 |
7793851 | Mullen | Sep 2010 | B2 |
7796013 | Murakami et al. | Sep 2010 | B2 |
7801799 | Brake, Jr. et al. | Sep 2010 | B1 |
7801829 | Gray et al. | Sep 2010 | B2 |
7805755 | Brown et al. | Sep 2010 | B2 |
7809643 | Phillips et al. | Oct 2010 | B2 |
7827115 | Weller et al. | Nov 2010 | B2 |
7828214 | Narendra et al. | Nov 2010 | B2 |
7848746 | Juels | Dec 2010 | B2 |
7882553 | Tuliani | Feb 2011 | B2 |
7900048 | Andersson | Mar 2011 | B2 |
7908216 | Davis et al. | Mar 2011 | B1 |
7922082 | Muscato | Apr 2011 | B2 |
7933589 | Mamdani et al. | Apr 2011 | B1 |
7949559 | Freiberg | May 2011 | B2 |
7954716 | Narendra et al. | Jun 2011 | B2 |
7954723 | Charrat | Jun 2011 | B2 |
7962369 | Rosenberg | Jun 2011 | B2 |
7993197 | Mamdani et al. | Aug 2011 | B2 |
8005426 | Huomo et al. | Aug 2011 | B2 |
8010405 | Bortolin et al. | Aug 2011 | B1 |
RE42762 | Shin | Sep 2011 | E |
8041954 | Plesman | Oct 2011 | B2 |
8060012 | Sklovsky et al. | Nov 2011 | B2 |
8074877 | Mullen et al. | Dec 2011 | B2 |
8082450 | Frey et al. | Dec 2011 | B2 |
8095113 | Kean et al. | Jan 2012 | B2 |
8099332 | Lemay et al. | Jan 2012 | B2 |
8103249 | Markison | Jan 2012 | B2 |
8108687 | Ellis et al. | Jan 2012 | B2 |
8127143 | Abdallah et al. | Feb 2012 | B2 |
8135648 | Oram et al. | Mar 2012 | B2 |
8140010 | Symons et al. | Mar 2012 | B2 |
8141136 | Lee et al. | Mar 2012 | B2 |
8150321 | Winter et al. | Apr 2012 | B2 |
8150767 | Wankmueller | Apr 2012 | B2 |
8186602 | Itay et al. | May 2012 | B2 |
8196131 | von Behren et al. | Jun 2012 | B1 |
8215563 | Levy et al. | Jul 2012 | B2 |
8224753 | Atef et al. | Jul 2012 | B2 |
8232879 | Davis | Jul 2012 | B2 |
8233841 | Griffin et al. | Jul 2012 | B2 |
8245292 | Buer | Aug 2012 | B2 |
8249654 | Zhu | Aug 2012 | B1 |
8266451 | Leydier et al. | Sep 2012 | B2 |
8285329 | Zhu | Oct 2012 | B1 |
8302872 | Mullen | Nov 2012 | B2 |
8312519 | Bailey et al. | Nov 2012 | B1 |
8316237 | Felsher et al. | Nov 2012 | B1 |
8332272 | Fisher | Dec 2012 | B2 |
8365988 | Medina, III et al. | Feb 2013 | B1 |
8369960 | Tran et al. | Feb 2013 | B2 |
8371501 | Hopkins | Feb 2013 | B1 |
8381307 | Cimino | Feb 2013 | B2 |
8391719 | Alameh et al. | Mar 2013 | B2 |
8417231 | Sanding et al. | Apr 2013 | B2 |
8439271 | Smets et al. | May 2013 | B2 |
8475367 | Yuen et al. | Jul 2013 | B1 |
8489112 | Roeding et al. | Jul 2013 | B2 |
8511542 | Pan | Aug 2013 | B2 |
8559872 | Butler | Oct 2013 | B2 |
8566916 | Vernon et al. | Oct 2013 | B1 |
8567670 | Stanfield et al. | Oct 2013 | B2 |
8572386 | Takekawa et al. | Oct 2013 | B2 |
8577810 | Dalit et al. | Nov 2013 | B1 |
8583454 | Beraja et al. | Nov 2013 | B2 |
8589335 | Smith et al. | Nov 2013 | B2 |
8594730 | Bona et al. | Nov 2013 | B2 |
8615468 | Varadarajan | Dec 2013 | B2 |
8620218 | Awad | Dec 2013 | B2 |
8667285 | Coulier et al. | Mar 2014 | B2 |
8723941 | Shirbabadi et al. | May 2014 | B1 |
8726405 | Bailey et al. | May 2014 | B1 |
8740073 | Vijayshankar et al. | Jun 2014 | B2 |
8750514 | Gallo et al. | Jun 2014 | B2 |
8752189 | De Jong | Jun 2014 | B2 |
8794509 | Bishop et al. | Aug 2014 | B2 |
8799668 | Cheng | Aug 2014 | B2 |
8806592 | Ganesan | Aug 2014 | B2 |
8807440 | Von Behren et al. | Aug 2014 | B1 |
8811892 | Khan et al. | Aug 2014 | B2 |
8814039 | Bishop et al. | Aug 2014 | B2 |
8814052 | Bona et al. | Aug 2014 | B2 |
8818867 | Baldwin et al. | Aug 2014 | B2 |
8850538 | Vernon et al. | Sep 2014 | B1 |
8861733 | Benteo et al. | Oct 2014 | B2 |
8880027 | Darringer | Nov 2014 | B1 |
8888002 | Chesney et al. | Nov 2014 | B2 |
8898088 | Springer et al. | Nov 2014 | B2 |
8934837 | Zhu et al. | Jan 2015 | B2 |
8977569 | Rao | Mar 2015 | B2 |
8994498 | Agrafioti et al. | Mar 2015 | B2 |
9004365 | Bona et al. | Apr 2015 | B2 |
9038894 | Khalid | May 2015 | B2 |
9042814 | Royston et al. | May 2015 | B2 |
9047531 | Showering et al. | Jun 2015 | B2 |
9069976 | Toole et al. | Jun 2015 | B2 |
9081948 | Magne | Jul 2015 | B2 |
9104853 | Venkataramani et al. | Aug 2015 | B2 |
9118663 | Bailey et al. | Aug 2015 | B1 |
9122964 | Krawczewicz | Sep 2015 | B2 |
9129280 | Bona et al. | Sep 2015 | B2 |
9152832 | Royston et al. | Oct 2015 | B2 |
9203800 | Izu et al. | Dec 2015 | B2 |
9209867 | Royston | Dec 2015 | B2 |
9251330 | Boivie et al. | Feb 2016 | B2 |
9251518 | Levin et al. | Feb 2016 | B2 |
9258715 | Borghei | Feb 2016 | B2 |
9270337 | Zhu et al. | Feb 2016 | B2 |
9306626 | Hall et al. | Apr 2016 | B2 |
9306942 | Bailey et al. | Apr 2016 | B1 |
9324066 | Archer et al. | Apr 2016 | B2 |
9324067 | Van OS et al. | Apr 2016 | B2 |
9332587 | Salahshoor | May 2016 | B2 |
9338622 | Bjontegard | May 2016 | B2 |
9373141 | Shakkarwar | Jun 2016 | B1 |
9379841 | Fine et al. | Jun 2016 | B2 |
9413430 | Royston et al. | Aug 2016 | B2 |
9413768 | Gregg et al. | Aug 2016 | B1 |
9420496 | Indurkar | Aug 2016 | B1 |
9426132 | Alikhani | Aug 2016 | B1 |
9432339 | Bowness | Aug 2016 | B1 |
9455968 | Machani et al. | Sep 2016 | B1 |
9473509 | Arsanjani et al. | Oct 2016 | B2 |
9491626 | Sharma et al. | Nov 2016 | B2 |
9553637 | Yang et al. | Jan 2017 | B2 |
9619952 | Zhao et al. | Apr 2017 | B1 |
9635000 | Muftic | Apr 2017 | B1 |
9665858 | Kumar | May 2017 | B1 |
9674705 | Rose et al. | Jun 2017 | B2 |
9679286 | Colnot et al. | Jun 2017 | B2 |
9680942 | Dimmick | Jun 2017 | B2 |
9710804 | Zhou et al. | Jul 2017 | B2 |
9740342 | Paulsen et al. | Aug 2017 | B2 |
9740988 | Levin et al. | Aug 2017 | B1 |
9763097 | Robinson et al. | Sep 2017 | B2 |
9767329 | Forster | Sep 2017 | B2 |
9769662 | Queru | Sep 2017 | B1 |
9773151 | Mil'shtein et al. | Sep 2017 | B2 |
9780953 | Gaddam et al. | Oct 2017 | B2 |
9891823 | Feng et al. | Feb 2018 | B2 |
9940571 | Herrington | Apr 2018 | B1 |
9953323 | Candelore et al. | Apr 2018 | B2 |
9961194 | Wiechman et al. | May 2018 | B1 |
9965756 | Davis et al. | May 2018 | B2 |
9965911 | Wishne | May 2018 | B2 |
9978058 | Wurmfeld et al. | May 2018 | B2 |
10043164 | Dogin et al. | Aug 2018 | B2 |
10075437 | Costigan et al. | Sep 2018 | B1 |
10129648 | Hernandez et al. | Nov 2018 | B1 |
10133979 | Eidam et al. | Nov 2018 | B1 |
10217105 | Sangi et al. | Feb 2019 | B1 |
10506642 | Henrique Minatel et al. | Dec 2019 | B2 |
10949842 | Lee et al. | Mar 2021 | B1 |
11245438 | Osborn | Feb 2022 | B1 |
20010010723 | Pinkas | Aug 2001 | A1 |
20010029485 | Brody et al. | Oct 2001 | A1 |
20010034702 | Mockett et al. | Oct 2001 | A1 |
20010054003 | Chien et al. | Dec 2001 | A1 |
20020078345 | Sandhu et al. | Jun 2002 | A1 |
20020093530 | Krothapalli et al. | Jul 2002 | A1 |
20020100808 | Norwood et al. | Aug 2002 | A1 |
20020120583 | Keresman, III et al. | Aug 2002 | A1 |
20020152116 | Yan et al. | Oct 2002 | A1 |
20020153424 | Li | Oct 2002 | A1 |
20020165827 | Gien et al. | Nov 2002 | A1 |
20030023554 | Yap et al. | Jan 2003 | A1 |
20030034873 | Chase et al. | Feb 2003 | A1 |
20030055727 | Walker et al. | Mar 2003 | A1 |
20030078882 | Sukeda et al. | Apr 2003 | A1 |
20030167350 | Davis et al. | Sep 2003 | A1 |
20030208449 | Diao | Nov 2003 | A1 |
20040015958 | Veil et al. | Jan 2004 | A1 |
20040039919 | Takayama et al. | Feb 2004 | A1 |
20040127256 | Goldthwaite et al. | Jul 2004 | A1 |
20040215674 | Odinak et al. | Oct 2004 | A1 |
20040230799 | Davis | Nov 2004 | A1 |
20050044367 | Gasparini et al. | Feb 2005 | A1 |
20050075985 | Cartmell | Apr 2005 | A1 |
20050081038 | Arditti Modiano et al. | Apr 2005 | A1 |
20050138387 | Lam et al. | Jun 2005 | A1 |
20050156026 | Ghosh et al. | Jul 2005 | A1 |
20050160049 | Lundholm | Jul 2005 | A1 |
20050195975 | Kawakita | Sep 2005 | A1 |
20050247797 | Ramachandran | Nov 2005 | A1 |
20060006230 | Bear et al. | Jan 2006 | A1 |
20060040726 | Szrek et al. | Feb 2006 | A1 |
20060041402 | Baker | Feb 2006 | A1 |
20060044153 | Dawidowsky | Mar 2006 | A1 |
20060047954 | Sachdeva et al. | Mar 2006 | A1 |
20060085848 | Aissi et al. | Apr 2006 | A1 |
20060136334 | Atkinson et al. | Jun 2006 | A1 |
20060173985 | Moore | Aug 2006 | A1 |
20060174331 | Schuetz | Aug 2006 | A1 |
20060242698 | Inskeep et al. | Oct 2006 | A1 |
20060280338 | Rabb | Dec 2006 | A1 |
20070033642 | Ganesan et al. | Feb 2007 | A1 |
20070055630 | Gauthier et al. | Mar 2007 | A1 |
20070061266 | Moore et al. | Mar 2007 | A1 |
20070061487 | Moore et al. | Mar 2007 | A1 |
20070116292 | Kurita et al. | May 2007 | A1 |
20070118745 | Buer | May 2007 | A1 |
20070197261 | Humbel | Aug 2007 | A1 |
20070224969 | Rao | Sep 2007 | A1 |
20070241182 | Buer | Oct 2007 | A1 |
20070256134 | Lehtonen et al. | Nov 2007 | A1 |
20070258594 | Sandhu et al. | Nov 2007 | A1 |
20070278291 | Rans et al. | Dec 2007 | A1 |
20080008315 | Fontana et al. | Jan 2008 | A1 |
20080011831 | Bonalle et al. | Jan 2008 | A1 |
20080014867 | Finn | Jan 2008 | A1 |
20080035738 | Mullen | Feb 2008 | A1 |
20080071681 | Khalid | Mar 2008 | A1 |
20080072303 | Syed | Mar 2008 | A1 |
20080086767 | Kulkarni et al. | Apr 2008 | A1 |
20080103968 | Bies et al. | May 2008 | A1 |
20080109309 | Landau et al. | May 2008 | A1 |
20080110983 | Ashfield | May 2008 | A1 |
20080120711 | Dispensa | May 2008 | A1 |
20080156873 | Wilhelm et al. | Jul 2008 | A1 |
20080162312 | Sklovsky et al. | Jul 2008 | A1 |
20080164308 | Aaron et al. | Jul 2008 | A1 |
20080207307 | Cunningham, II et al. | Aug 2008 | A1 |
20080209543 | Aaron | Aug 2008 | A1 |
20080223918 | Williams et al. | Sep 2008 | A1 |
20080285746 | Landrock et al. | Nov 2008 | A1 |
20080308641 | Finn | Dec 2008 | A1 |
20090037275 | Pollio | Feb 2009 | A1 |
20090048026 | French | Feb 2009 | A1 |
20090132417 | Scipioni et al. | May 2009 | A1 |
20090143104 | Loh et al. | Jun 2009 | A1 |
20090171682 | Dixon et al. | Jul 2009 | A1 |
20090210308 | Toomer et al. | Aug 2009 | A1 |
20090235339 | Mennes et al. | Sep 2009 | A1 |
20090249077 | Gargaro et al. | Oct 2009 | A1 |
20090282264 | Amiel et al. | Nov 2009 | A1 |
20100023449 | Skowronek et al. | Jan 2010 | A1 |
20100023455 | Dispensa et al. | Jan 2010 | A1 |
20100029202 | Jolivet et al. | Feb 2010 | A1 |
20100033310 | Narendra et al. | Feb 2010 | A1 |
20100036769 | Winters et al. | Feb 2010 | A1 |
20100078471 | Lin et al. | Apr 2010 | A1 |
20100082491 | Rosenblatt et al. | Apr 2010 | A1 |
20100094754 | Bertran et al. | Apr 2010 | A1 |
20100095130 | Bertran et al. | Apr 2010 | A1 |
20100100480 | Altman et al. | Apr 2010 | A1 |
20100114731 | Kingston et al. | May 2010 | A1 |
20100192230 | Steeves et al. | Jul 2010 | A1 |
20100207742 | Buhot et al. | Aug 2010 | A1 |
20100211797 | Westerveld et al. | Aug 2010 | A1 |
20100240413 | He et al. | Sep 2010 | A1 |
20100257357 | McClain | Oct 2010 | A1 |
20100312634 | Cervenka | Dec 2010 | A1 |
20100312635 | Cervenka | Dec 2010 | A1 |
20100330904 | Stougaard | Dec 2010 | A1 |
20110028160 | Roeding et al. | Feb 2011 | A1 |
20110035604 | Habraken | Feb 2011 | A1 |
20110060631 | Grossman et al. | Mar 2011 | A1 |
20110068170 | Lehman | Mar 2011 | A1 |
20110084132 | Tofighbakhsh | Apr 2011 | A1 |
20110101093 | Ehrensvard | May 2011 | A1 |
20110113245 | Varadrajan | May 2011 | A1 |
20110125638 | Davis et al. | May 2011 | A1 |
20110131415 | Schneider | Jun 2011 | A1 |
20110153437 | Archer et al. | Jun 2011 | A1 |
20110153496 | Royyuru | Jun 2011 | A1 |
20110208658 | Makhotin | Aug 2011 | A1 |
20110208965 | Machani | Aug 2011 | A1 |
20110211219 | Bradley | Sep 2011 | A1 |
20110218911 | Spodak | Sep 2011 | A1 |
20110238564 | Lim et al. | Sep 2011 | A1 |
20110246780 | Yeap et al. | Oct 2011 | A1 |
20110258452 | Coulier et al. | Oct 2011 | A1 |
20110280406 | Ma et al. | Nov 2011 | A1 |
20110282785 | Chin | Nov 2011 | A1 |
20110294418 | Chen | Dec 2011 | A1 |
20110312271 | Ma et al. | Dec 2011 | A1 |
20120024947 | Naelon | Feb 2012 | A1 |
20120030047 | Fuentes et al. | Feb 2012 | A1 |
20120030121 | Grellier | Feb 2012 | A1 |
20120047071 | Mullen et al. | Feb 2012 | A1 |
20120079281 | Lowenstein et al. | Mar 2012 | A1 |
20120109735 | Krawczewicz et al. | May 2012 | A1 |
20120109764 | Martin et al. | May 2012 | A1 |
20120143754 | Patel | Jun 2012 | A1 |
20120150737 | Rottink | Jun 2012 | A1 |
20120178366 | Levy et al. | Jul 2012 | A1 |
20120196583 | Kindo | Aug 2012 | A1 |
20120207305 | Gallo et al. | Aug 2012 | A1 |
20120209773 | Ranganathan | Aug 2012 | A1 |
20120238206 | Singh et al. | Sep 2012 | A1 |
20120239560 | Pourfallah et al. | Sep 2012 | A1 |
20120252350 | Steinmetz et al. | Oct 2012 | A1 |
20120254394 | Barras | Oct 2012 | A1 |
20120284194 | Liu et al. | Nov 2012 | A1 |
20120290472 | Mullen et al. | Nov 2012 | A1 |
20120296818 | Nuzzi et al. | Nov 2012 | A1 |
20120316992 | Oborne | Dec 2012 | A1 |
20120317035 | Royyuru et al. | Dec 2012 | A1 |
20120317628 | Yeager | Dec 2012 | A1 |
20130005245 | Royston | Jan 2013 | A1 |
20130008956 | Ashfield | Jan 2013 | A1 |
20130026229 | Jarman et al. | Jan 2013 | A1 |
20130048713 | Pan | Feb 2013 | A1 |
20130054474 | Yeager | Feb 2013 | A1 |
20130065564 | Conner et al. | Mar 2013 | A1 |
20130080228 | Fisher | Mar 2013 | A1 |
20130080229 | Fisher | Mar 2013 | A1 |
20130099587 | Lou | Apr 2013 | A1 |
20130104251 | Moore et al. | Apr 2013 | A1 |
20130106576 | Hinman et al. | May 2013 | A1 |
20130119130 | Braams | May 2013 | A1 |
20130130614 | Busch-Sorensen | May 2013 | A1 |
20130144793 | Royston | Jun 2013 | A1 |
20130171929 | Adams et al. | Jul 2013 | A1 |
20130179351 | Wallner | Jul 2013 | A1 |
20130185772 | Jaudon et al. | Jul 2013 | A1 |
20130191279 | Calman et al. | Jul 2013 | A1 |
20130200999 | Spodak et al. | Aug 2013 | A1 |
20130216108 | Hwang et al. | Aug 2013 | A1 |
20130226791 | Springer et al. | Aug 2013 | A1 |
20130226796 | Jiang et al. | Aug 2013 | A1 |
20130232082 | Krawczewicz et al. | Sep 2013 | A1 |
20130238894 | Ferg et al. | Sep 2013 | A1 |
20130282360 | Shimota et al. | Oct 2013 | A1 |
20130303085 | Boucher et al. | Nov 2013 | A1 |
20130304651 | Smith | Nov 2013 | A1 |
20130312082 | Izu et al. | Nov 2013 | A1 |
20130314593 | Reznik et al. | Nov 2013 | A1 |
20130344857 | Berionne et al. | Dec 2013 | A1 |
20140002238 | Taveau et al. | Jan 2014 | A1 |
20140019352 | Shrivastava | Jan 2014 | A1 |
20140027506 | Heo et al. | Jan 2014 | A1 |
20140032409 | Rosano | Jan 2014 | A1 |
20140032410 | Georgiev et al. | Jan 2014 | A1 |
20140040120 | Cho et al. | Feb 2014 | A1 |
20140040139 | Brudnicki et al. | Feb 2014 | A1 |
20140040147 | Varadarakan et al. | Feb 2014 | A1 |
20140047235 | Lessiak et al. | Feb 2014 | A1 |
20140067690 | Pitroda et al. | Mar 2014 | A1 |
20140074637 | Hammad | Mar 2014 | A1 |
20140074655 | Lim et al. | Mar 2014 | A1 |
20140081720 | Wu | Mar 2014 | A1 |
20140138435 | Khalid | May 2014 | A1 |
20140171034 | Aleksin et al. | Jun 2014 | A1 |
20140171039 | Bjontegard | Jun 2014 | A1 |
20140172700 | Teuwen et al. | Jun 2014 | A1 |
20140180851 | Fisher | Jun 2014 | A1 |
20140208112 | McDonald et al. | Jul 2014 | A1 |
20140214674 | Narula | Jul 2014 | A1 |
20140229375 | Zaytzsev et al. | Aug 2014 | A1 |
20140245391 | Adenuga | Aug 2014 | A1 |
20140256251 | Caceres et al. | Sep 2014 | A1 |
20140258099 | Rosano | Sep 2014 | A1 |
20140258113 | Gauthier et al. | Sep 2014 | A1 |
20140258125 | Gerber et al. | Sep 2014 | A1 |
20140274179 | Zhu et al. | Sep 2014 | A1 |
20140279479 | Maniar et al. | Sep 2014 | A1 |
20140337235 | Van Heerden et al. | Nov 2014 | A1 |
20140339315 | Ko | Nov 2014 | A1 |
20140346860 | Aubry et al. | Nov 2014 | A1 |
20140365780 | Movassaghi | Dec 2014 | A1 |
20140379361 | Mahadkar et al. | Dec 2014 | A1 |
20150012444 | Brown et al. | Jan 2015 | A1 |
20150032635 | Guise | Jan 2015 | A1 |
20150071486 | Rhoads et al. | Mar 2015 | A1 |
20150088757 | Zhou et al. | Mar 2015 | A1 |
20150089586 | Ballesteros | Mar 2015 | A1 |
20150134452 | Williams | May 2015 | A1 |
20150140960 | Powell et al. | May 2015 | A1 |
20150154595 | Collinge et al. | Jun 2015 | A1 |
20150170138 | Rao | Jun 2015 | A1 |
20150178724 | Ngo et al. | Jun 2015 | A1 |
20150186871 | Laracey | Jul 2015 | A1 |
20150205379 | Mag et al. | Jul 2015 | A1 |
20150302409 | Malek | Oct 2015 | A1 |
20150317626 | Ran et al. | Nov 2015 | A1 |
20150332266 | Friedlander et al. | Nov 2015 | A1 |
20150339474 | Paz et al. | Nov 2015 | A1 |
20150371234 | Huang et al. | Dec 2015 | A1 |
20160012465 | Sharp | Jan 2016 | A1 |
20160026997 | Tsui et al. | Jan 2016 | A1 |
20160048913 | Rausaria et al. | Feb 2016 | A1 |
20160055480 | Shah | Feb 2016 | A1 |
20160057619 | Lopez | Feb 2016 | A1 |
20160065370 | Le Saint et al. | Mar 2016 | A1 |
20160087957 | Shah et al. | Mar 2016 | A1 |
20160092696 | Guglani et al. | Mar 2016 | A1 |
20160148193 | Kelley et al. | May 2016 | A1 |
20160232523 | Venot et al. | Aug 2016 | A1 |
20160239672 | Khan et al. | Aug 2016 | A1 |
20160253651 | Park et al. | Sep 2016 | A1 |
20160255072 | Liu | Sep 2016 | A1 |
20160267486 | Mitra et al. | Sep 2016 | A1 |
20160277383 | Guyomarc'h et al. | Sep 2016 | A1 |
20160277388 | Lowe et al. | Sep 2016 | A1 |
20160307187 | Guo et al. | Oct 2016 | A1 |
20160307189 | Zarakas et al. | Oct 2016 | A1 |
20160314472 | Ashfield | Oct 2016 | A1 |
20160330027 | Ebrahimi | Nov 2016 | A1 |
20160335531 | Mullen et al. | Nov 2016 | A1 |
20160379217 | Hammad | Dec 2016 | A1 |
20170004502 | Quentin et al. | Jan 2017 | A1 |
20170011395 | Pillai et al. | Jan 2017 | A1 |
20170011406 | Tunnell et al. | Jan 2017 | A1 |
20170017957 | Radu | Jan 2017 | A1 |
20170017964 | Janefalkar et al. | Jan 2017 | A1 |
20170024716 | Jiam et al. | Jan 2017 | A1 |
20170039566 | Schipperheijn | Feb 2017 | A1 |
20170041759 | Gantert et al. | Feb 2017 | A1 |
20170068950 | Kwon | Mar 2017 | A1 |
20170103388 | Pillai et al. | Apr 2017 | A1 |
20170104739 | Lansler et al. | Apr 2017 | A1 |
20170109509 | Baghdasaryan | Apr 2017 | A1 |
20170109730 | Locke et al. | Apr 2017 | A1 |
20170116447 | Cimino et al. | Apr 2017 | A1 |
20170124568 | Moghadam | May 2017 | A1 |
20170140379 | Deck | May 2017 | A1 |
20170154328 | Zarakas et al. | Jun 2017 | A1 |
20170154333 | Gleeson et al. | Jun 2017 | A1 |
20170180134 | King | Jun 2017 | A1 |
20170230189 | Toll et al. | Aug 2017 | A1 |
20170237301 | Elad et al. | Aug 2017 | A1 |
20170289127 | Hendrick | Oct 2017 | A1 |
20170295013 | Claes | Oct 2017 | A1 |
20170316696 | Bartel | Nov 2017 | A1 |
20170317834 | Smith et al. | Nov 2017 | A1 |
20170330173 | Woo et al. | Nov 2017 | A1 |
20170374070 | Shah et al. | Dec 2017 | A1 |
20180034507 | Wobak et al. | Feb 2018 | A1 |
20180039986 | Essebag et al. | Feb 2018 | A1 |
20180068316 | Essebag et al. | Mar 2018 | A1 |
20180129945 | Saxena et al. | May 2018 | A1 |
20180160255 | Park | Jun 2018 | A1 |
20180191501 | Lindemann | Jul 2018 | A1 |
20180205712 | Versteeg et al. | Jul 2018 | A1 |
20180240106 | Garrett et al. | Aug 2018 | A1 |
20180254909 | Hancock | Sep 2018 | A1 |
20180268132 | Buer et al. | Sep 2018 | A1 |
20180270214 | Caterino et al. | Sep 2018 | A1 |
20180294959 | Traynor et al. | Oct 2018 | A1 |
20180300716 | Carlson | Oct 2018 | A1 |
20180302396 | Camenisch et al. | Oct 2018 | A1 |
20180315050 | Hammad | Nov 2018 | A1 |
20180316666 | Koved et al. | Nov 2018 | A1 |
20180322486 | Deliwala et al. | Nov 2018 | A1 |
20180359100 | Gaddam et al. | Dec 2018 | A1 |
20190014107 | George | Jan 2019 | A1 |
20190019375 | Foley | Jan 2019 | A1 |
20190036678 | Ahmed | Jan 2019 | A1 |
20190172055 | Hale et al. | Jun 2019 | A1 |
20190238517 | D'Agostino et al. | Aug 2019 | A1 |
Number | Date | Country |
---|---|---|
3010336 | Jul 2017 | CA |
101192295 | Jun 2008 | CN |
103023643 | Apr 2013 | CN |
103417202 | Dec 2013 | CN |
1 085 424 | Mar 2001 | EP |
1 223 565 | Jul 2002 | EP |
1 265 186 | Dec 2002 | EP |
1 783 919 | May 2007 | EP |
2 852 070 | Jan 2009 | EP |
2 139 196 | Dec 2009 | EP |
2 457 221 | Aug 2009 | GB |
2 516 861 | Feb 2015 | GB |
2 551 907 | Jan 2018 | GB |
101508320 | Apr 2015 | KR |
WO 0049586 | Aug 2000 | WO |
WO 2006070189 | Jul 2006 | WO |
WO 2008055170 | May 2008 | WO |
WO 2009025605 | Feb 2009 | WO |
WO 2010049252 | May 2010 | WO |
WO 2011112158 | Sep 2011 | WO |
WO 2012001624 | Jan 2012 | WO |
1 469 419 | Feb 2012 | WO |
WO 2013039395 | Mar 2013 | WO |
WO 2013155562 | Oct 2013 | WO |
WO 2013192358 | Dec 2013 | WO |
WO 2014043278 | Mar 2014 | WO |
WO 2014170741 | Oct 2014 | WO |
WO 2015179649 | Nov 2015 | WO |
WO 2015183818 | Dec 2015 | WO |
WO 2016097718 | Jun 2016 | WO |
WO 2016160816 | Oct 2016 | WO |
WO 2016168394 | Oct 2016 | WO |
WO 2017042375 | Mar 2017 | WO |
WO 2017042400 | Mar 2017 | WO |
WO 2017157859 | Sep 2017 | WO |
WO 2017208063 | Dec 2017 | WO |
WO 2018063809 | Apr 2018 | WO |
WO 2018137888 | Aug 2018 | WO |
Entry |
---|
Haykin M. and Warnar, R., “Smart Card Technology: New Methods for Computer Access Control,” Computer Science and Technology NIST Special Publication 500-157:1-60 (1988). |
Lehpamer, Harvey, “Component of the RFID System,” RFID Design Principles, 2nd edition pp. 133-201 (2012). |
Pourghomi, Pardis et al., “A Proposed NFC Payment Application,” International Journal of Advanced Computer Science and Applications, vol. 4, No. 8 (2013). |
Author Unknown, “CardrefresherSM from American Express®,” [online] 2019 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://merchant-channel.americanexpress.com/merchant/en_US/cardrefresher, 2 pages. |
Author Unknown, “Add Account Updater to your recurring payment tool,” [online] 2018-19 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://www.authorize.net/our-features/account-updater/, 5 pages. |
Author Unknown, “Visa® Account Updater for Merchants,” [online] 2019 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://usa.visa.com/dam/VCOM/download/merchants/visa-account-updater-product-information-fact-sheet-for-merchants.pdf, 2 pages. |
Author Unknown, “Manage the cards that you use with Apple Pay,” Apple Support [online] 2019 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://support.apple.com/en-us/HT205583, 5 pages. |
Author Unknown, “Contactless Specifications for Payment Systems,” EMV Book B—Entry Point Specification [online] 2016 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://www.emvco.com/wp-content/uploads/2017/05/BookB_Entry_Point_Specification_v2_6_20160809023257319.pdf, 52 pages. |
Author Unknown, “EMV Integrated Circuit Card Specifications for Payment Systems, Book 2, Security and Key Management,” Version 3.4, [online] 2011 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://www.emvco.com/wp-content/uploads/2017/05/EMV_v4.3_Book_2_Security_and_Key_Management_20120607061923900.pdf, 174 pages. |
Author unknown, “NFC Guide: All You Need to Know About Near Field Communication” Square Guide [online] 2018[retrieved on Nov. 13, 2018]. Retrieved from Internet URL: https://squareup.com/guides/nfc, 8 pages. |
Profis, S., “Everything you need to know about NFC and mobile payments” CNET Directory [online], 2014 [retrieved on Mar. 25, 2019]. Retrieved from the Internet URL: https://www.cnet.com/how-to/how-nfc-works-and-mobile-payments/, 6 pages. |
Cozma, N., “Copy data from other devices in Android 5.0 Lollipop setup” CNET Directory [online] 2014 [retrieved on Mar. 25, 2019]. Retrieved from the Internet URL: https://www.cnet.com/how-to/copy-data-from-other-devices-in-android-5-0-lollipop-setup/, 5 pages. |
Kevin, Android Enthusiast, “How to copy text string from nfc tag” StackExchange [online] 2013 [retrieved on Mar. 25, 2019]. Retrieved from the Internet URL: https://android.stackexchange.com/questions/55689/how-to-copy-text-string-from-nfc-tag, 11 pages. |
Author unknown, “Tap & Go Device Setup” Samsung [online] date unknown [retrieved on Mar. 25, 2019]. Retrieved from the Internet URL: https://www.samsung.com/us/switch-me/switch-to-the-galaxy-s-5/app/partial/setup-device/tap-go.html, 1 page. |
Author Unknown, “Multiple encryption”, Wikipedia [online] 2019 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://en.wikipedia.org/wiki/Multiple_encryption, 4 pages. |
Krawczyk, et al., “HMAC: Keyed-Hashing for Message Authentication”, Network Working Group RFC:2104 memo [online] 1997 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://tools.ietf.org/html/rfc2104, 12 pages. |
Song, et al., “The AES-CMAC Algorithm”, Network Working Group RFC: 4493 memo [online] 2006 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://tools.ietf.org/html/rfc4493, 21 pages. |
Katz, J., and Lindell, Y., “Aggregate Message Authentication Codes”, Topics in Cryptology [online] 2008 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://www.cs.umd.edu/˜jkatz/papers/aggregateMAC.pdf, 11 pages. |
Adams, D., and Maier, A-K, “Goldbug Big Seven open source crypto-messengers to be compared -: or Comprehensive Confidentiality Review & Audit of GoldBug Encrypting E-Mail-Client & Secure Instant Messenger”, Big Seven Study 2016 [online] [retrieved on Mar. 25, 2018]. Retrieved from Internet URL: https://sf.net/projects/goldbug/files/bigseven-crypto-audit.pdf, 309 pages. |
Author Unknown, “Triple DES”, Wikipedia [online] 2018 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://simple.wikipedia.org/wiki/Triple_DES, 2 pages. |
Song, F., and Yun, A.l, “Quantum Security of NMAC and Related Constructions—PRF domain extension against quantum attacks”, IACR Cryptology ePrint Archive [online] 2017 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://eprint.iacr.org/2017/509.pdf, 41 pages. |
Saxena, N., “Lecture 10: NMAC, HMAC and Number Theory”, CS 6903 Modern Cryptography [online] 2008 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: http://isis.poly.edu/courses/cs6903/Lectures/lecture10.pdf, 8 pages. |
Berg, Guy, “Fundamentals of EMV” Smart Card Alliance [online] date unknown [retrieved on Mar. 27, 2019]. Retrieved from Internet URL: https://www.securetechalliance.org/resources/media/scap13_preconference/02.pdf, 37 pages. |
Pierce, Kevin, “Is the amazon echo NFC compatible,?” Amazon.com Customer Q&A [online] 2016 [retrieved on Mar. 26, 2019]. Retrieved from Internet URL: https://www.amazon.com/ask/questions/Tx1RJXYSPE6XLJD?_encodi . . . , 2 pages. |
Author Unknown, “Multi-Factor Authentication”, idaptive [online] 2019 [retrieved on Mar. 25, 2019], Retrieved from Internet URL: https://www.centrify.com/products/application-services/adaptive-multi-factor-authentication/risk-based-mfa/, 10 pages. |
Author Unknown, “Adaptive Authentication”, SecureAuth [online] 2019 [retrieved on Mar. 25, 2019}. Retrieved from Internet URL: https://www.secureauth.com/products/access-management/adaptive-authentication, 7 pages. |
van den Breekel, J., et al., “EMV in a nutshell”, Technical Report, 2016 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://www.es.ru.nl/E.Poll/papers/EMVtechreport.pdf, 37 pages. |
Author Unknown, “Autofill”, Computer Hope [online] 2018 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://www.computerhope.eom/jargon/a/autofill.htm, 2 pages. |
Author Unknown, “Fill out forms automatically”, Google Chrome Help [online] 2019 [retrieved on Mar. 25, 2019], Retrieved from Internet URL: https://support.google.com/chrome/answer/142893?co=GENIE.Platform%3DDesktop&hl=en, 3 pages. |
Author unknown, “Autofill credit cards, contacts, and passwords in Safari on Mac”, Apple Safari User Guide [online] 2019 [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://support.apple.com/guide/safari/use-autofill-ibrw1103/mac, 3 pages. |
Menghin, M.J., “Power Optimization Techniques for Near Field Communication Systems” 2014 Dissertation at Technical University of Graz [online]. Retrieved from Internet URL: https://diglib.tugraz.at/download.php?id=576a7b910d2d6&location=browse, 135 pages. |
Mareli, M., et al., “Experimental evaluation of NFC reliability between an RFID tag and a smartphone” Conference paper (2013) IEEE AFRICON at Mauritius [online] [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://core.ac.uk/download/pdf/54204839.pdf, 5 pages. |
Davison, A., et al., “MonoSLAM: Real-Time Single Camera SLAM”, IEEE Transactions on Pattern Analysis and Machine Intelligence 29(6): 1052-1067 (2007). |
Barba, R., “Sharing your location with your bank sounds creepy, but it's also useful”, Bankrate, LLC [online] 2017 [retrieved on Mar. 25, 2019], Retrieved from Internet URL: https://www.bankrate.com/banking/banking-app-location-sharing/, 6 pages. |
Author unknown: “onetappayment™”, [online] Jan. 24, 2019, [retrieved on Mar. 25, 2019]. Retrieved from Internet URL: https://www.payubiz.in/onetap, 4 pages. |
Vu et al., (2012). “Distinguishing users with capacitive touch communication” Proceedings of the Annual International Conference on Mobile Computing and Networking, MOBICOM. 10.1145/2348543.2348569. |
EMVCo, EMV Card Personalization Specification, version 1.0 (Jun. 2003), 81 pages. |
Ullmann et al., (2012). “On-Card” User Authentication for Contactless Smart Cards based on Gesture Recognition, LNI, 223-234, 12 pages. |
Faraj et al. (2008). “Investigation of Java Smart Card Technology for Multi-Task Applications” J. of Al-Anbar University for Pure Science, vol. 2: No. 1: 2008, 11 pages. |
Dhamdhere (2017) “Key Benefits of a Unified Platform for Loyalty, Referral Marketing, and UGC” Annex Cloud [retrieved on Jul. 3, 2019]. Retrieved from Internet URL: https://www.annexcloude.com/blog/benefits-unified-platform/, 13 pages. |
Number | Date | Country | |
---|---|---|---|
20220311475 A1 | Sep 2022 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17213943 | Mar 2021 | US |
Child | 17560391 | US |