Systems and methods for providing data to NFC devices

Abstract

The NFC device and the NFC reader each include NFC circuitry, an FFC antenna, and a controller. The NFC circuitry establishes an NFC connection between the NFC reader and the NFC device, and may perform an NFC function, such as NFC authentication. The NFC circuitry of the NFC device harvests energy from the NFC field received from the NFC reader. If the NFC reader has data for the NFC device, or if the NFC device has data for the NFC reader, data may be provided between the NFC reader and the NFC device via the FFC antenna.

Description

Technical Field

[0001] The present disclosure relates to the field of near field communication (NFC), and more particularly to upgrading firmware of an NFC device. Background Art

[0002] NFC technology uses radio frequency signals to enable devices to communicate with each other in close proximity. Many applications of NFC technology use NFC readers to query and receive data from NFC devices. NFC readers typically output an inquiry signal. If the NFC device is within the range of the inquiry signal, the NFC device responds by providing an identification signal that identifies the NFC device. After the NFC device identifies itself, the NFC reader and the NFC device can further exchange information.

[0003] Some NFC devices may include a controller that controls the functions of the NFC device. The controller may include firmware. The firmware corresponds to software that defines or controls the basic functions of the NFC device. In some cases, it may be beneficial to upgrade the firmware of the NFC device. However, upgrading the firmware of the NFC device may be relatively difficult.

[0004] All subject matter discussed in the background section is not necessarily prior art and should not be assumed to be prior art simply as a result of its discussion in the background section. Along these lines, any recognition of a problem in the prior art discussed in the background section or associated with such subject matter should not be considered prior art unless explicitly stated to be prior art. Instead, the discussion of any subject matter in the background section should be considered as part of the inventor's approach to solving a particular problem, which in itself may also be inventive. Summary of the invention

[0005] Embodiments of the present disclosure provide NFC devices that can provide data updates or transmit other types of large data files to controllers in a simple and effective manner. NFC devices according to the principles of the present disclosure utilize both NFC and far field communication (FFC) to effectively send or receive large data files. In particular, NFC devices according to the principles of the present disclosure include NFC antennas and FFC antennas. When large data files are to be sent or received, the NFC device utilizes the NFC antenna and other NFC circuit devices to collect energy from an external NFC field. The NFC device utilizes the collected energy to power the controller, and the controller controls the FFC antenna to send or receive update data to an external device.

[0006] In one embodiment, the NFC device is a part of an electronic device that utilizes NFC to perform certain functions of the electronic device. For example, when the NFC device is in front of an NFC reader, the NFC device can receive an identification or command from the NFC reader. Then, the NFC device can cause the electronic device to perform an action in response to the identification or command. In these situations, the NFC reader can communicate entirely through NFC. However, in some cases, the NFC reader may have update data for the NFC device. In these cases, the NFC device may provide the FFC address to the NFC reader. Then, the NFC reader may provide the update data to the NFC device via the FFC. Because the FFC can send data at a much higher data rate than NFC, the update data is quickly provided to the NFC device via the FFC.

[0007] In some embodiments, the NFC device does not include a battery or other internal power source. Advantageously, the NFC device is powered entirely by harvesting energy from the NFC field provided by the NFC reader. Thus, the NFC device actively harvests energy from the NFC reader while communicating with the NFC reader via the FFC antenna. Because the FFC antenna is powered by energy harvested from the NFC field, the NFC device can operate without an internal battery that is used to connect to another internal power source of the electronic device of which the NFC device is a part.

[0008] In one embodiment, the NFC device is part of an electronic lock. The electronic lock does not include an internal battery. The internal electronic lock includes a motor and a locking mechanism. Because the electronic lock has no internal power source, the electronic lock uses NFC to harvest energy to activate the locking mechanism. The electronic lock can receive updates using FFC while being powered by energy harvested from an external NFC field.

[0009] In one embodiment, a method includes establishing an NFC connection with an NFC reader with an NFC device, powering a controller of the NFC device by harvesting energy from an NFC field received from the NFC device, and establishing an FFC connection with the NFC reader with the NFC device. The method includes receiving update data from the NFC reader via the FFC connection while harvesting energy from the NFC field with the NFC device and updating data of the NFC device with the update data.

[0010] In one embodiment, an electronic system includes: an NFC circuit device including an NFC antenna; an FFC antenna; and a controller coupled to the NFC circuit device and the NFC antenna.

[0011] In one embodiment, an electronic lock includes: an NFC circuit device including an NFC antenna; an FFC antenna; and a controller coupled to the NFC circuit device and the NFC antenna. The electronic lock includes a motor coupled to the controller and a locking mechanism coupled to the motor.

[0012] In one embodiment, an electronic system includes an NFC reader configured to receive firmware update data. The NFC reader includes a first NFC antenna and a first FFC antenna. The system includes an NFC device. The NFC device includes an NFC circuit device. The NFC device includes a second NFC antenna, a second FFC antenna, and a controller coupled to the NFC circuit device and the second FFC antenna.

[0013] In one embodiment, an electronic device includes an NFC antenna, an FFC antenna, and a controller coupled to the NFC antenna and the FFC antenna. The controller is configured to cause the NFC antenna to output an NFC field to establish an NFC connection with an NFC device, and to establish an FFC connection with the NFC device via the FFC antenna while the NFC antenna outputs the NFC field.

[0014] In one embodiment, a method includes receiving firmware update data with an NFC reader and establishing near field communication with an NFC device by outputting an NFC field from an NFC antenna. The method includes establishing FFC communication with the NFC device via an FFC antenna of the NFC reader and providing the firmware update data to the NFC device via the FFC antenna.

[0015] In one embodiment, a method includes receiving an NFC field from an NFC reader with an NFC antenna of an NFC device and generating a voltage by harvesting energy from the NFC field. The method includes powering a controller of the NFC device with the voltage and controlling the FFC antenna of the NFC device with the controller powered by the voltage.

[0016] Embodiments of the present disclosure provide a simple and efficient NFC-based firmware update process, which avoids the use of intrusive equipment and manual access procedures to perform firmware updates for NFC devices and associated electronic devices and systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 is a block diagram of an NFC system according to one embodiment.

[0018] Figure 2 is a block diagram of an NFC system according to one embodiment.

[0019] Figure 3 is a block diagram of an NFC system according to one embodiment.

[0020] Figure 4is a schematic diagram of a portion of an NFC device according to one embodiment.

[0021] Figure 5 is a flow chart of a process for operating an NFC system according to one embodiment.

[0022] Figure 6 is a flow chart of a process for operating an NFC system according to one embodiment.

[0023] Figure 7 is a flow chart of a process for operating an NFC system according to one embodiment.

[0024] Figure 8 is a flow chart of a process for operating an NFC system according to one embodiment. DETAILED DESCRIPTION

[0025] Figure 1 1 is a block diagram of an NFC system 100 according to one embodiment. The NFC system 100 includes an NFC device 102 and an NFC reader 104. The NFC device 102 and the NFC reader 104 communicate with each other using NFC technology. As will be described in more detail below, the NFC device 102 and the NFC reader 104 cooperate to quickly and efficiently transfer large data files from the NFC device 102 to the NFC reader 104 or from the NFC reader 104 to the NFC device 102.

[0026] Before describing further details of the NFC system 100, it is beneficial to describe the operating characteristics of some NFC devices. The first operating mode of the NFC reader is the read / write mode, hereinafter referred to as the "reader mode". In the reader mode, the NFC reader outputs a carrier field corresponding to a radio frequency signal that facilitates NFC communication. The NFC reader outputs an interrogation signal by modulating the carrier field. If the NFC device is close to the NFC reader, the NFC device can receive the interrogation signal. The interrogation signal causes a response from the NFC device. Once communication is established between the NFC device and the NFC reader, the NFC reader can read data from the NFC device or can provide data to the NFC device.

[0027] As used herein, an "NFC device" is a device that includes NFC functionality. As used herein, when interacting with an NFC reader in reader mode, an "NFC device" may operate as an NFC tag or in another manner. An NFC device receives a carrier field and an interrogation signal from an NFC device, and responds by providing data to the NFC device using NFC or by receiving data from an NFC reader using NFC. An NFC device may act as a tag in some situations, and as an NFC reader in other situations.

[0028] As used herein, an "NFC reader" is a device that includes NFC functionality and can output an NFC carrier field to read or receive data from an NFC device. An NFC reader may correspond to an electronic device that has a primary function other than acting as an NFC reader. An NFC reader may act as an NFC reader in some cases and be an NFC device in other cases.

[0029] NFC device 102 includes NFC circuitry 106, controller 108, and FFC antenna 114. The components of NFC device 102 cooperate together to provide NFC communications.

[0030] As used herein, the term "FFC" may correspond to communications within a frequency range between 500MHz and 60GHz. Specifically, the term "FFC" is used herein to refer to a communication protocol or component that can communicate within a range significantly larger than a typical NFC communication range and has a frequency much higher than a conventional NFC frequency. Although NFC communications typically occur within a range of less than 15cm, FFC communications may occur within a range of up to 50m or more. Some examples of FFC communications are Wi-Fi communications and Bluetooth communications, but other communication protocols may be used for FFC without departing from the scope of this disclosure. In the example of Wi-Fi communications, FFC may be performed at 2.4GHz, 5GHz, or 6GHz, depending on the standard. In the example of Bluetooth communications, FFC may be performed at a frequency between 2.4GHz and 2.5GHz, depending on the standard.

[0031] The NFC circuit device 106 enables the NFC device 102 to send signals and receive signals. The NFC circuit device 106 may include an NFC antenna 107 for sending NFC signals and for receiving NFC signals. The NFC circuit device 106 may include additional circuit devices for enabling the NFC circuit device 106 to receive signals, including interrogation signals, carrier fields, and other types of signals. The NFC circuit device 106 may include additional circuit devices for enabling the NFC circuit device 106 to receive and process signals, including interrogation signals and other types of signals from various types of NFC readers. The NFC circuit device 106 may include circuit devices for collecting energy from an external NFC field to power the NFC circuit device. Although the controller 108 is shown as being separate from the NFC circuit device 106, in fact, the controller 108 may be part of the NFC circuit device 106.

[0032] Controller 108 includes control circuitry for controlling the functions of NFC device 102. Controller 108 controls the operation of NFC circuitry 106. Controller 108 controls the reception and transmission of signals with NFC circuitry 106. Controller 108 may include processing resources, memory resources, and data transmission resources. Controller 108 may correspond to a microcontroller, a microprocessor, or other type of controller or processor.

[0033] The controller 108 includes a memory 110. The memory 110 may include an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other types of memory. The EEPROM may include flash memory or other types of memory. The RAM may include static RAM (SRAM), dynamic RAM (DRAM), or other types of RAM.

[0034] The memory 110 stores data 111. The data 111 may include software that controls the basic functions of the controller 108, such as firmware data. In other examples, the data 111 may include other types of data in addition to the firmware data. The data may serve as an operating system for the NFC device 102. The data 111 may include instruction protocols for executing operations, processes, and methods performed by the NFC device 102, including those described herein. As will be described in more detail below, the components of the NFC system 100 cooperate to update the data 111 in the memory 110. Although some embodiments described herein relate to firmware data, other types of data 111 may be updated without departing from the scope of the present disclosure.

[0035] Although some embodiments describe updating the data of the memory 110 of the controller 108, the memory 110 may be external to the controller. In addition, the data 111 may include photos, videos, documents, software, or other types of data. Such data may be added or replaced using the update process described herein.

[0036] Although Figure 1 The embodiments described herein illustrate a controller as part of the NFC device 102, but the controller may also be part of a device or system that hosts the NFC device 102. The processes described herein for updating data may be utilized to update data of other components of the electronic device or system that hosts the NFC device 102. The data associated with these other controllers may be more complex than the data 111 associated with the NFC device 102.

[0037] From time to time, it may be beneficial to update the data 111 of the controller 108. In many situations, it may be difficult to update the data 111 of a controller associated with an NFC device. This may be particularly true when the NFC device is part of a device that is not normally connected to the Internet or does not have a ready interface that allows a user to navigate the Internet to update data. In addition, in some cases, it may be desirable to provide other types of data to the memory of the NFC device, such as images, videos, music, or other types of data.

[0038] In one example, the NFC device is part of an electronic device. The electronic device may not have any internal power source, such as a battery. In some cases, the electronic device may have a power source, but the NFC device 102 is not connected to the power source of the electronic device. In these cases, the NFC device 102 is powered entirely by collecting energy from the external NFC field output by the NFC reader 104.

[0039] It is difficult to update firmware or provide large data files to NFC devices that do not have an internal power supply or are not configured for a wired data transfer connection. One solution is to provide the update data to the NFC device from an NFC reader via NFC. However, in many cases, the firmware update may include a relatively large amount of data. Updating the firmware via NFC may take a relatively large amount of time. In addition, if the NFC device and the NFC reader move out of the NFC range during the firmware update process, the firmware update may fail and may require a restart. This is very inconvenient for the individual performing the firmware update.

[0040] NFC system 100 overcomes the disadvantages and difficulties associated with other solutions for updating the firmware of a controller. Figure 1 The NFC device 102 and NFC reader 104 provide a convenient, efficient and effective way to update data 111 of a controller 108 associated with the NFC device 102. In particular, the NFC device 102 utilizes the FFC antenna 114 to facilitate fast and reliable updating of the controller 108 or otherwise provide large data files to the NFC device 102.

[0041] The NFC reader 104 plays a role in updating the data 111 of the NFC device 102. The NFC reader 104 includes an NFC antenna 116, a controller 118, a memory 120, and an FFC antenna 123. The NFC antenna 116 includes an antenna and other circuit devices for receiving signals from the NFC device 102 and for providing signals to the NFC device 102. The NFC antenna 116 can be a part of the NFC transceiver of the NFC reader 104.

[0042] The controller 118 can control the operation of the NFC antenna 116. The controller 118 can control the output of the carrier field. The controller can control the modulation of the carrier field to output an interrogation signal, output one or more commands, output various identification signals, or provide other types of data. The controller 118 can also control the reception and processing of signals received from the NFC device 102.

[0043] The carrier field is a radio frequency signal that facilitates NFC communication. The NFC device 102 outputs an inquiry signal by modulating the carrier field. The inquiry signal is configured to cause a response from an NFC reader within the range of communication with the NFC device 102. If the NFC reader 104 is within the range of the NFC device 102, the NFC reader 104 can respond to the inquiry signal. In one embodiment, the NFC reader 104 outputs a carrier field with a standard center frequency of 13.56 MHz. However, without departing from the scope of the present disclosure, the NFC reader 104 can utilize other frequencies. As used herein, the terms "carrier field" and "NFC field" can be used interchangeably.

[0044] The memory 120 may store software instructions associated with operating the NFC reader 104. Figure 1 1 , but the memory 120 may include firmware data for the controller 118. The memory 120 may include the same type of memory described with respect to the memory 110 of the NFC device 102, or may include other types of memory.

[0045] The memory 110 may store a unique identification (UID) of the NFC tag 102. The UID is an identification code associated with the NFC tag 102. The UID may also identify the type of the NFC tag 102. As will be explained in more detail below, the UID may be read by the NFC reader 104 in order to authenticate the NFC tag 102.

[0046] The memory 110 can also store data according to the NFC data exchange format (NDEF). Such data can facilitate FFC pairing, such as Bluetooth pairing, Wi-Fi pairing or other types of FFC pairing. Some examples of NDEF records may include Bluetooth pairing data, universal resource identifier data, text data, short message service (SMS) data, smart poster data or other types of data or records. The type of NDEF record is defined in the record type definition (RTD) field located in the NDEF header. A type of NDEF record for Bluetooth switching is a multipurpose Internet mail extension (MIME) type record. Various types of NDEF data can be stored and utilized by the NFC tag 102 for data exchange to facilitate pairing, identification or other actions.

[0047] The NFC reader 104 is configured to receive update data 121. The NFC reader 104 stores the update data 121 in the memory 120. The update data 121 corresponds to data that will replace or expand the data 111 of the controller 108. Therefore, in some embodiments, the update data 121 corresponds to the replacement of the data 111 of the controller 108. In an embodiment where the data 111 is firmware data, the update data 121 is firmware update data. In some embodiments, the update data 121 includes large data files, such as image data, video data, music data, text data, software data, or other types of data. The data can be transmitted from the NFC reader 104 to the NFC device 102, or from the NFC device 102 to the NFC reader 104. For example, video data can be transmitted from the NFC reader 104 to the NFC device 102, or from the NFC device 102 to the NFC reader 104.

[0048] The NFC reader 104 may receive the update data via the Internet, via a network connection, or in other ways. In one example, the NFC reader 104 is a device that includes a user interface and an application associated with the NFC device 102. The application may prompt a user of the NFC reader 104 to download the update data 121 in preparation for executing the update process of the controller 108. The user may then accept the update data 121 or may otherwise choose to download the update 121. In another example, the application associated with the NFC reader 104 may automatically download the update data 121 without user input. There are various ways in which the NFC reader 104 may receive the update data 121.

[0049] In one embodiment, the NFC reader 104 is a smart phone. The smart phone may include an application associated with the NFC device 102. The application may download update data 121 of the controller 108. Alternatively, the user may utilize the application to accept or request the download of update data 121. The NFC reader 104 may include a smart watch, a tablet and an NFC card, an NFC tag, or other types of electronic devices including NFC capabilities.

[0050] After the NFC reader 104 has downloaded or otherwise received the update data 121, the user of the NFC reader 104 brings the NFC reader 104 near the NFC device 102. The NFC reader 104 outputs a carrier field and modulates the carrier field to generate an inquiry signal. The device 102 operating as an NFC tag or in an NFC tag emulation mode receives the inquiry signal and causes the device to respond to the inquiry signal. Initially, the NFC reader 104 reads an identification, such as a UID, from the NFC device 102. After authenticating the NFC device 102, the NFC device 102 provides the AID to the NFC reader 104 by modulating the NFC field. The AID indicates that the NFC reader 104 wishes to provide the update data 121 to the NFC device 102. Data transmission can be from the NFC reader 104 to the NFC device 102 or from the NFC device 102 to the NFC reader 104.

[0051] When the NFC device 102 receives an indication that the NFC reader 104 is ready to provide update data 121, the NFC device 102 may provide the FFC address data to the NFC reader 104. The FFC address data corresponds to the FFC address associated with the NFC device 102. The NFC device 102 may provide the address data by modulating the impedance of the NFC antenna 107. The NFC reader receives the address data by detecting the modulation of the impedance of the NFC antenna 107. Throughout the process, the NFC circuit device 106 collects energy from the NFC field provided by the NFC reader 104. The NFC circuit device 106 generates a voltage from the energy collected from the NFC field. The NFC circuit device 106 provides the voltage to the controller 108 so that the controller 108 can operate the FFC antenna 114 to receive data.

[0052] After the NFC reader 104 receives the FFC address data of the NFC device 102, the controller 118 controls the FFC antenna 123 to establish an FFC connection with the FFC antenna 114 of the NFC device 102. After the NFC reader 104 establishes the FFC connection with the NFC device 102, the NFC reader 104 proceeds to provide the update data 121 to the NFC device 102. The controller 108 of the NFC device 102 receives the update data 121 via the NFC antenna 114. Then, the controller 108 updates the data 111 with the update data 121. Alternatively, the update data may be provided from the NFC device 102 to the NFC reader 104.

[0053] Because the NFC device 102 does not include its own power supply, the controller 108 controls the FFC antenna 114 to establish an FFC connection and send or receive update data while being powered by the voltage provided by the NFC circuit device 106. The NFC circuit device 106 generates voltage by collecting energy from the carrier field provided by the NFC antenna 116 of the NFC reader 104. The update of the controller 108 can be performed very quickly. For example, the update can be performed in less than two seconds using FFC communication instead of NFC communication. This is very advantageous because the user of the NFC reader 104 can keep the NFC reader 104 in place for only a few seconds or less in order to perform the update. Once the update is completed, the NFC device 102 can output a signal indicating that the update has been successfully completed via the FFC antenna 114. Then, the NFC reader 104 can output an indication that the update process is completed to the user of the NFC reader 104.

[0054] Figure 2 2 is a block diagram of an NFC system 200 according to an embodiment. The NFC system includes an electronic device 103 and a mobile phone 105. The electronic device 103 is Figure 1 Alternatively, the electronic device 103 may be considered to include the NFC device 102. The mobile phone 105 is Figure 1 An example of an NFC reader 104 is shown. The electronic device 103 cooperates with the mobile phone 105 to update the firmware of the controller 108 or to exchange data between 103 and 105.

[0055] Figure 2 Mobile phone 105 and Figure 1 The NFC reader 104 is substantially similar. Figure 2 The mobile phone 105 is used, but other types of NFC devices may be used to provide firmware updates to the electronic device 103. Figure 1 The NFC reader 104 of the present invention is substantially similar, except that the mobile phone 105 includes a main controller 125 in addition to the NFC controller 118. In fact, the main controller 125 can be a general controller of the mobile phone 105. After the FFC communication has been established, the main controller 125 can push the firmware update data 122 to the electronic device 103.

[0056] The electronic device 103 is a device or system that hosts the NFC device 102. The electronic device 103 includes a controller 108 that controls the NFC device 102. The controller 108 may include a microprocessor, a microcontroller, or another type of controller. The controller 108 includes firmware data 112. The firmware data 112 is Figure 1 An example of data 111.

[0057] The electronic device 103 includes an NFC circuit device 106. The NFC circuit device 106 includes an NFC antenna 107, an NFC tag 126, a voltage rectifier 128, and a voltage regulator 130. The NFC tag 126 is coupled to the controller 108. The electronic device 103 also includes an FFC antenna 114 coupled to the controller 108. The controller 108 is configured to implement an FFC communication protocol with the FFC antenna 114.

[0058] When the mobile phone 105 is used to interact with the electronic device 103, the mobile phone 105 outputs an NFC field via the NFC antenna 116. As previously described, the NFC antenna 116 can modulate the NFC field to output an interrogation signal, identification data command data, application identification data, or other types of data. The NFC antenna 107 receives the carrier signal and provides the carrier signal to the voltage rectifier 128 and the NFC tag 126. The voltage rectifier 128 rectifies the carrier field to generate a rectified voltage. The rectified voltage may correspond to a DC voltage. The voltage rectifier 128 provides a rectified voltage regulator 130.

[0059] The voltage regulator 130 receives the rectified voltage and generates a regulated voltage from the rectified voltage. The regulated voltage may correspond to a standard supply voltage that may be provided to the NFC tag 126 and the controller 108. One example is a regulated voltage between two old files, but other voltages may be utilized without departing from the scope of the present disclosure.

[0060] The NFC tag 126 may include a memory that stores data, such as identification data or address data. The NFC tag is powered by a regulated voltage and receives a modulated carrier signal. The NFC tag 126 may modulate the impedance of the antenna 107 to output identification data, address data, or other types of data from the NFC antenna 107, such as for Figure 1 as described.

[0061] The NFC tag may also provide data to the controller 108. If the data indicates that a firmware update is available, the controller 108 may enter an FFC communication mode to facilitate the FFC antenna 114 to establish FFC communication with the FFC antenna 123 of the mobile phone 105, such as for Figure 1 When the mobile phone 105 receives the FFC address data via the NFC connection, the mobile phone 105 can then use the FFC address data to establish an FFC connection with the antenna 114. The mobile phone 105 can then push the firmware update data 122 from the mobile phone 105 to the electronic device 103. The controller 108 can then update the firmware data 112 with the firmware update data 122. The firmware update data 122 is Figure 1 An example of update data 121.

[0062] Although the examples herein describe providing firmware update data from mobile phone 105 to electronic device 103, other types of data may be provided. For example, other types of software update data may be provided from mobile phone 105 to electronic device 103 instead of firmware update data 122. Various types of data may be provided via FFC communications from mobile phone 105 to electronic device 103. Alternatively, data may be transmitted from electronic device 103 to mobile phone 105.

[0063] Figure 3 3 is a block diagram of an NFC system 300 according to one embodiment. The NFC system includes an electronic locker 103 and a mobile phone 105. The electronic locker 103 cooperates with the mobile phone 105 to update the firmware of the controller 108 of the electronic locker 103.

[0064] Figure 3 Mobile phones and Figure 2 The mobile phone 105 is substantially the same as the mobile phone 105. In particular, the mobile phone 103 can communicate with the electronic lock 103 via both NFC and FFC. The mobile phone can provide the firmware update data 122 to the electronic lock 103 via FFC.

[0065] Electronic lock 103 is Figure 2 An example of an electronic device 103. The electronic lock 103 includes Figure 2 The electronic locker 103 also includes a motor 132 , a locking mechanism 134 , and a motor controller 136 .

[0066] In one embodiment, the electronic striker 103 can act as a padlock or other type of lock. However, unlike traditional locks that use a key or manual combination to unlock the lock, the electronic striker 103 is unlocked only through NFC. The mobile phone 105 uses NFC as a key to unlock the electronic striker 103. In particular, as previously described, the mobile phone 105 establishes NFC communication with the electronic striker 103. When the mobile phone 105 receives an identification from the electronic striker 103, the mobile phone 105 can then provide an identification signal for unlocking the locking mechanism 134. The NFC tag 126 or the controller 108 authenticates the identification signal from the mobile phone 105. If the identification signal is valid, the controller 108 controls the motor controller 136 to start the motor 132. The motor 132 moves the locking mechanism 134 to unlock the electronic striker 103. The motor controller 136 is powered by a regulated voltage from the voltage regulator 130. Although Figure 3 A mobile phone 105 is illustrated, but the mobile phone 105 may be replaced with an NFC-enabled device other than a mobile phone.

[0067] As previously described, in some examples, the mobile phone 105 may be used to update the firmware data 112 of the controller 108 via the FFC. The firmware update may be substantially the same as for Figure 1 and Figure 2 Descriptive happening.

[0068] Figure 4 1 is a schematic diagram of an NFC circuit device 106 according to one embodiment. The NFC circuit device 106 includes a matching circuit device 140, a rectifier 128, and an NFC tag 126. The matching circuit device 140 includes an NFC antenna 107 and a plurality of capacitors C4 to C9. The antenna 107 may correspond to a primary NFC antenna through which a carrier field is received from the NFC reader 104. Capacitors C4 and C5 are connected to a first terminal of the NFC antenna 107 and are connected in parallel with each other. Capacitors C6 and C7 are connected to a second terminal of the NFC antenna 107 and are connected in parallel with each other. Capacitors C8 and C9 are connected in parallel with each other between capacitors C4 and C7. The matching network circuit device 140 can help ensure reliable power delivery from the antenna 107.

[0069] Voltage regulator 128 includes diodes D1 to D4 that perform initial rectification of the carrier field. Diodes D1 to D4 are connected in a bridge configuration. Anodes of diodes D2 and D4 are coupled to ground. The cathodes of diodes D1 and D3 provide the rectified voltage Vrect. The anode of diode D1 and the cathode of diode D2 are coupled to capacitors C4 and C5. The anode of diode D3 and the cathode of diode D4 are coupled to capacitors C6 and C7.

[0070] Diode D6 is also coupled between ground and the rectified voltage Vrect. Capacitors C1 to C3 are coupled in parallel with each other between ground and the rectified voltage Vrect. A pair of resistors R1 and R2 are coupled between ground and Vrect as a voltage divider. The divided voltage is provided to a sense terminal Vrect_SENSE that can be used to sense the rectified voltage via resistor R9. The rectified voltage also passes through resistor R3. Although Figure 4 Although not shown in FIG. 1 , the voltage regulator 130 may receive the rectified voltage Vrect and may generate a regulated voltage. The regulated voltage may be a power supply voltage VCC.

[0071] The tag 126 includes a chip 142. The chip 142 includes antenna terminals AC1 and AC0. AC1 is coupled to a first terminal of the NFC antenna 107 via a resistor R5 and a capacitor C10. AC0 is coupled to a second terminal of the NFC antenna 107 via a resistor R4 and a capacitor C11. Capacitor C12 is coupled between AC1 and ground. Capacitor C14 is coupled between AC0 and ground. Capacitor C13 is coupled between C12 and C14. Capacitor C13 is coupled between C12 and C14. Chip 142 reads data from a modulated carrier field via AC1 and AC0. Chip 142 can also output data to antenna 107 via AC1 and AC0.

[0072] The chip 142 may also include terminals V_EH, VCC, VSS, GPO, SCL, SDA, and EP. V_EH may correspond to an energy harvesting output. Terminal VCC is a power supply terminal that receives a power supply voltage VCC from the voltage regulator 130. VSS is coupled to ground. GPO is an interrupt output. SDA is a serial data input / output that may be coupled to the controller 108. SCL is a serial clock terminal that may be coupled to a clock (not shown). EP is coupled to an exposed pad that remains floating. Capacitor C15 is coupled between VCC and ground. Resistor R6 is coupled between GPO and ground. Resistor R7 is coupled between SCL and ground. Resistor R8 is coupled between SDA and ground. Chip 142 may store identification data of an NFC device and may store address data for FFC communication. Chip 142 may be controlled by controller 108. Other configurations of the NFC circuit device 106 may be utilized without departing from the scope of the present disclosure.

[0073] Figure 5 is a flow chart of a method 500 for operating an NFC system according to one embodiment. The method 500 may utilize Figures 1 to 4 The system, components, and processes described herein. At 502, method 500 includes sending an NFC field from an NFC reader. At 504, method 500 includes receiving a carrier field with an NFC device and rectifying it. At 506, method 500 includes sending FFC address data from the NFC device to the NFC reader. At 508, method 500 includes generating a regulated voltage from the rectified voltage and supplying the regulated voltage to a controller of the NFC device. At 510, method 500 includes communicating with an NFC reader via an FFC antenna of the NFC device.

[0074] Figure 6 is a flow chart of a method 600 for operating an NFC system according to one embodiment. The method 600 may utilize Figures 1 to 5The system, components and processes described herein are described herein. At 602, method 600 establishes a near field communication connection with an NFC reader with an NFC device. At 604, method 600 includes powering a controller of the NFC device by collecting energy from an NFC field received from the NFC device. At 606, method 600 includes establishing a far field communication connection with an NFC reader with the NFC device. At 608, method 600 includes receiving update data from the NFC reader via the far field communication connection while collecting energy from the NFC field with the NFC device. At 610, method 600 includes updating data of the NFC device with the update data.

[0075] Figure 7 is a flow chart of a method 700 for operating an NFC system according to one embodiment. The method 700 may utilize Figures 1 to 6 The system, components, and processes described herein. At 702, method 700 includes receiving firmware update data with an NFC reader. At 704, method 700 includes establishing near field communication with an NFC device by outputting an NFC field from an NFC antenna. At 706, method 700 includes establishing FFC communication with the NFC device via an FFC antenna of the NFC reader. At 708, method 700 includes providing the firmware update data to the NFC device via the FFC antenna.

[0076] Figure 8 is a flow chart of a method 800 for operating an NFC system according to one embodiment. The method 800 may utilize Figures 1 to 6 The method 800 includes receiving an NFC field from an NFC reader with an NFC antenna of an NFC device at 802. At 804, the method 800 includes generating a voltage by harvesting energy from the NFC field. At 806, the method 800 includes powering a controller of the NFC device with the voltage. At 808, the method 800 includes controlling an FFC antenna of the NFC device with the controller powered by the voltage.

[0077] In one embodiment, a method includes establishing a near field communication connection with an NFC reader with an NFC device, powering a controller of the NFC device by harvesting energy from an NFC field received from the NFC device, and establishing a far field communication connection with the NFC reader with the NFC device. The method includes receiving update data from the NFC reader via the far field communication connection while harvesting energy from the NFC field with the NFC device and updating data of the NFC device with the update data.

[0078] In one embodiment, an electronic system includes: an NFC circuit device including an NFC antenna; an FFC antenna; and a controller coupled to the NFC circuit device and the NFC antenna.

[0079] In one embodiment, an electronic lock includes: an NFC circuit device including an NFC antenna; an FFC antenna; and a controller coupled to the NFC circuit device and the NFC antenna. The electronic lock includes a motor coupled to the controller and a locking mechanism coupled to the motor.

[0080] In one embodiment, an electronic system includes an NFC reader configured to receive firmware update data. The NFC reader includes a first NFC antenna and a first FFC antenna. The system includes an NFC device. The NFC device includes an NFC circuit device. The NFC circuit device includes a second NFC antenna, a second FFC antenna, and a controller coupled to the NFC circuit device and the second FFC antenna.

[0081] In one embodiment, an electronic device includes an NFC antenna, an FFC antenna, and a controller coupled to the NFC antenna and the FFC antenna. The controller is configured to cause the NFC antenna to output an NFC field to establish an NFC connection with an NFC device, and to establish an FFC connection with the NFC device via the FFC antenna while the NFC antenna outputs the NFC field.

[0082] In one embodiment, a method includes receiving firmware update data with an NFC reader and establishing near field communication with an NFC device by outputting an NFC field from an NFC antenna. The method includes establishing FFC communication with the NFC device via an FFC antenna of the NFC reader and providing the firmware update data to the NFC device via the FFC antenna.

[0083] In one embodiment, a method includes receiving an NFC field from an NFC reader with an NFC antenna of an NFC device and generating a voltage by harvesting energy from the NFC field. The method includes powering a controller of the NFC device with the voltage and controlling the FFC antenna of the NFC device with the controller powered by the voltage.

[0084] The various embodiments described above may be combined to provide other embodiments. These and other changes may be made to the embodiments according to the description detailed above. In general, in the claims below, the terms used should not be understood to limit the claims to the specific embodiments disclosed in the specification and claims, but should be understood to include all possible embodiments within the entire equivalent scope of the rights granted to such claims. Accordingly, the claims are not limited by the present disclosure.

Claims

1. A method comprising: establishing a near field communication connection with a near field communication reader using a near field communication device; powering a controller of the near field communication device by harvesting energy from a near field communication field received from the near field communication device; establishing a far field communication connection with the near field communication reader using the near field communication device; receiving update data from the near field communication reader via the far field communication connection with the near field communication device while harvesting energy from the near field communication field; as well as The data of the near field communication device is updated with the update data. 2 . The method of claim 1 , wherein the far field communication connection is a Wi-Fi connection or Bluetooth. The method according to claim 1 , wherein the update data is firmware update data.

4. The method according to claim 1, comprising: receiving, with the near field communication device via the near field communication connection, an indication that an update is available; as well as In response to receiving the indication that the update is available, the near field communication device transmits, with the near field communication device, far field communication address data to the near field communication reader.

5. The method according to claim 4, comprising: receiving, with the near field communication device, from the near field communication reader, a far field communication pairing request including the far field communication address data; as well as In response to receiving the far field communication pairing request, establishing the far field communication connection. The method of claim 1 , wherein the near field communication device is part of an electronic device. The method of claim 6 , wherein the electronic device is part of an electronic lock.

8. The method of claim 1, wherein the near field communication reader is a mobile phone.

9. The method of claim 1 , wherein establishing a near field communication connection with the near field communication reader comprises: receiving, with the near field communication device, an identification of the near field communication reader; as well as The near field communication identifier is authenticated using the near field communication device.

10. The method of claim 9, wherein establishing a near field communication connection with the near field communication reader comprises: receiving, with the near field communication device, an application identifier of the near field communication reader; as well as The identification of the application identification refers to the update process.

11. The method of claim 10, comprising updating data of the controller in response to identifying that the application identification corresponds to a data update process.

12. An electronic system comprising: A near field communication circuit device, the near field communication circuit device comprising a near field communication antenna; Far field communication antenna; as well as A controller is coupled to the near field communications circuitry and the near field communications antenna.

13. The electronic system of claim 12, wherein the NFC circuitry is configured to establish a NFC connection with a NFC reader and to harvest energy from a NFC field received from the NFC reader.

14. The electronic system of claim 13, wherein the near field communication circuitry is configured to power the controller with the energy harvested from the near field communication field.

15. The electronic system of claim 14, wherein the near field communication circuit device is configured to receive an update request from the near field communication reader and indicate to the controller that the update request has been received, wherein the controller is configured to establish a far field communication connection with the near field communication reader via the far field communication antenna. 16 . The electronic system of claim 15 , wherein the controller is configured to receive update data from the near field communication reader via the far field communication antenna.

17. The electronic system of claim 16, wherein the controller is configured to update aspects of the controller with the update data, wherein the near field communication circuit device is configured to power the controller when the controller receives the update data and when the controller updates the aspects of the controller with the update data.

18. The electronic system of claim 17, wherein the update data comprises firmware update data for the controller.

19. The electronic device of claim 14, wherein the controller is configured to establish a far field communication connection with the near field communication reader via the far field communication antenna and provide update data to the near field communication reader via the far field communication antenna.

20. The electronic system of claim 12, comprising a motor coupled to the controller and the near field communication circuitry, wherein the controller is configured to activate the motor in response to receiving valid identification data from the near field communication reader via the near field communication circuitry.

21. The electronic system of claim 20, comprising a locking mechanism coupled to the motor, wherein the motor is configured to lock or unlock the locking mechanism in response to activation of the controller.

22. The electronic system of claim 12, wherein the near field communication circuit device comprises: a near field communication tag coupled to the near field communication antenna and the controller; a voltage rectifier coupled to the near field communication antenna and configured to harvest energy from the near field communication field by generating a rectified voltage from the near field communication field; as well as A voltage regulator is coupled to the rectifier and is configured to generate a regulated voltage from the rectified voltage and supply the rectified voltage to the controller and the near field communication tag.

23. The electronic device of claim 12, wherein the controller is not coupled to a battery and is powered solely by energy harvested from the near field communication field.

24. An electronic lock comprising: A near field communication circuit device, the near field communication circuit device comprising a near field communication antenna; Far field communication antenna; a controller coupled to the near field communications circuitry and the near field communications antenna; a motor coupled to the controller; as well as A locking mechanism is coupled to the motor.

25. An electronic lock according to claim 24, wherein the near-field communication circuit device is configured to: establish near-field communication with a near-field communication reader, generate a voltage by collecting energy from a near-field communication field received from the near-field communication reader, and power the controller with the voltage; wherein the controller is configured to: establish a far-field communication connection with the near-field communication reader via the far-field communication antenna while being powered by the voltage from the near-field communication circuit device.

26. The electronic lock of claim 25, wherein the controller is configured to receive firmware update data from the electronic device via the far-field communication antenna while being powered by the voltage from the near-field communication circuitry.

27. The electronic lock of claim 25, wherein the NFC circuitry is configured to provide the voltage to the motor, wherein the controller is configured to cause the motor to operate the locking mechanism in response to the NFC circuitry receiving a valid identification from the NFC reader.

28. An electronic system comprising: A near field communication reader configured to receive firmware update data and comprising: a first near field communication antenna; and a first far-field communication antenna; A near field communication device, the near field communication device comprising: a near field communication circuit device, the near field communication circuit device comprising a second near field communication antenna; a second far-field communications antenna; and A controller is coupled to the near-field communications circuitry and the second far-field communications antenna.

29. An electronic system according to claim 28, wherein the electronic device is configured to: output a near field communication field, establish a near field communication connection with the near field communication circuit device, provide an indication of update readiness to the near field communication device, establish a far field communication connection with the near field communication device using the first far field communication antenna, and provide the update data to the near field communication device via the first far field communication antenna.

30. The electronic system of claim 28, wherein the near field communication reader is a cellular telephone.

31. An electronic device comprising: Near field communication antenna; Far field communication antenna; as well as A controller is coupled to the near-field communication antenna and the far-field communication antenna and is configured to: cause the near-field communication antenna to output a near-field communication field to establish a near-field communication connection with a near-field communication device, and to establish a far-field communication connection with the near-field communication device via the far-field communication antenna while the near-field communication antenna outputs the near-field communication field.

32. An electronic device according to claim 31, wherein the controller is configured to: cause the near-field communication antenna to output an update request to the near-field communication device, and establish the far-field communication connection in response to receiving address data from the near-field communication device via the near-field communication antenna, and output update data to the near-field communication device via the far-field communication antenna.

33. The electronic device according to claim 30, wherein the update data is firmware data for the near field communication device.

34. A method comprising: receiving firmware update data using a near field communication reader; establishing near field communication with a near field communication device by outputting a near field communication field from a near field communication antenna; establishing far-field communication with the near-field communication device via a far-field communication antenna of the near-field communication reader; as well as The firmware update data is provided to the near field communication device via the far field communication antenna.

35. The method of claim 31, wherein the firmware update data is for a controller of the near field communication device.

36. A method comprising: receiving a near field communication field from a near field communication reader with a near field communication antenna of the near field communication device; generating a voltage by harvesting energy from the near field communication field; powering a controller of the near field communication device with the voltage; as well as A far field communication antenna of the near field communication device is controlled with the controller powered by the voltage.

37. The method of claim 36, comprising receiving update data from the near field communication reader via the far field communication antenna.

38. The method of claim 37, comprising updating the controller with the update data.

39. A method comprising: establishing a near field communication connection with a near field communication reader using a near field communication device; powering a controller of the near field communication device by harvesting energy from a near field communication field received from the near field communication device; establishing a far field communication connection with the near field communication reader using the near field communication device; sending update data to the near field communication reader via the far field communication connection with the near field communication device while harvesting energy from the near field communication field; as well as The data of the near field communication reader is updated with the update data.

40. The method of claim 39, wherein the far field communication connection is a Wi-Fi connection or Bluetooth.

Images