NFC无线射频取电技术研究及应用探索Research on NFC Radio Frequency Power Supply Technology and Its Application Exploration深圳市每开创新科技有限公司欧阳红军摘要：由于传统供电方式无法满足社会可持续发展需求，以及物联网应用灵活且低成本部署的需求，NFC无线射频取电技术成为一种有效的解决方案。
介绍了NFC无线射频取电技术，分析其天线设计、输入功率和输出电压、能量转换效率、灵敏度及兼客性等技术指标，阐述其在NFC智能锁及电子纸显示的两种典型应用场景，对其在电子纸应用方面从技术和市场两方面做了展望，为业界在NFC无线射频取电技术及其应用领域的研究提供参考。
关键词:RFID，NFC，无线射频取电技术, 电子纸, 智能锁Abstract:Because the traditional power supply mode can't meet the needs of social sustainable development, as well as the need for flexible and low-cost deployment of IoT applications, NFC radio frequency power supply technology has become an effective solution and is highly expected. This paper introduces the NFC radio frequency power supply technology, analyzes its technical indicators, including antenna design, input power and output voltage, energy conversion efficiency, sensitivity and compatibility. Besides that, this paper also expounds its two typical application scenarios in NFC smart lock and e-Paper display, and looks forward to its application in e-Paper from both technical and market aspects, providing reference for the industry's research in NFC radio frequency power acquisition technology and its application fields.Keywords:radio frequency identification; near field communication: radio frequency power supply technology; e-Papersmart lock.1. 引言在全社会营造节能低碳浓厚的氛围下，环境取能与碳达峰碳中和的政策、理念不谋而合。
手机nfc功能怎么打开手机NFC（Near Field Communication）功能是一种近距离无线通信技术，用于在手机与其他支持NFC的设备之间进行数据传输。
下面是关于手机NFC功能如何打开的一个简单教程。
第一步是确保您的手机支持NFC功能。
几乎所有现代智能手机，尤其是Android手机，都已经配备了NFC芯片。
您可以通过设置菜单或在手机规格中查看是否支持NFC功能。
第二步是打开手机的设置菜单。
找到“连接”或“无线和网络”选项，通常可以在主屏幕上滑动通知栏中找到快捷方式。
选择“NFC和支付”。
第三步是打开NFC功能。
在NFC和支付设置菜单中，通常会显示一个“NFC”选项，可能默认处于关闭状态。
点击该选项，即可打开NFC功能。
第四步是设置NFC的使用方式。
在NFC和支付设置菜单中，您可能会看到其他与NFC相关的选项，例如“Android Beam”、“NFC标签读取器模式”等。
您可以按照自己的需求打开或关闭这些选项。
第五步是进行NFC传输。
一旦打开了NFC功能，您就可以使用NFC进行数据传输了。
例如，您可以将两台支持NFC的手机靠近，然后在屏幕上显示的提示下，点击确认进行数据传输。
您还可以将支持NFC的手机靠近一个NFC标签，以读取其中的信息。
具体的传输方法可能因手机型号而有所不同，请根据手机的使用说明进行操作。
总结起来，打开手机的NFC功能可以通过进入手机的设置菜单，在“连接”或“无线和网络”选项中找到“NFC和支付”设置，然后打开NFC功能。
根据需要设置其他相关的NFC选项，然后就可以开始使用NFC进行数据传输了。
多种⾮接触卡ATQA字节说明13.56 MHz RFIDSoftwareAn Open Source implementation of an NFC stack, and various related utilities is available from the project.The author of this page has released a number of small utilities, and enhancements to third-party ones in a on BitBucket.A link to a tool for examining data stored on Atmel CryptoRF tokens, and errata is available in .The project supply a package of tools for manipulating the contents of various types of RFID tokens, and examining Machine-Readable Travel Documents and EMV cards.A driver that supposedly allows for use of LibNFC with generic PCSC-enabled applications is available from the project onSourceForge.This doesn't seem to build against the latest version of LibNFC:ifd-nfc.c: In function ‘IFDHTransmitToICC’:ifd-nfc.c:355:17: error: too few arguments to function ‘nfc_initiator_transceive_bytes’/usr/local/include/nfc/nfc.h:80:19: note: declared hereDatasheetsA is available for the STMicroElectronics SRI512 ISO/IEC 14443-B chipset.A is available from ACS for the InnoVision/Broadcom Topaz family of ISO/IEC 14443-A chipsets.A is available for Maxim's ISO/IEC 14443-B chipset.A (MF0ICU1) is available for the ISO/IEC 14443-A chipset.A is available for FuDan's FM11RF08 chipset (which is supposedly compatible with existing MiFare Classic implementations).The for the NXP PN532 chipset is available.A for a variant of the ACS ACR122U card reader is available.HardwareFeliCa tokensSony FeliCa Lite RC-S701LibNFC's nfc-list -v command reports:1 Felica (212 kbps) passive target(s) found:ID (NFCID2): 01 27 00 5d 1a 05 88 cdParameter (PAD): 00 f0 00 00 02 06 03 00System Code (SC): 88 b41 Felica (424 kbps) passive target(s) found:ID (NFCID2): 01 27 00 5d 1a 05 88 cdParameter (PAD): 00 f0 00 00 02 06 03 00System Code (SC): 88 b4LibNFC's nfc-read-forum-tag3 command reports:Place your NFC Forum Tag Type 3 in the field...NDEF Mapping version: 1.0NFC Forum Tag Type 3 capacity: 208 bytesNDEF data lenght: 60 byteslibnfc.chip.pn53x - InListPassiveTarget libnfc.driver.acr122 - TX: ff 00 00 00 09 d4 4a 01 01 00 ff ff 01 00 libnfc.driver.acr122 - RX: d5 4b 0101 14 01 01 27 00 5d 1a 05 88 cd 00 f0 00 00 02 06 03 00 88 b4 90 00libnfc.chip.pn53x - InListPassiveTarget libnfc.driver.acr122 - TX: ff 00 00 00 09 d4 4a 01 02 00 ff ff 01 00 libnfc.driver.acr122 - RX: d5 4b 01 01 14 01 | 01 27 00 5d 1a 05 88 cd | 00 f0 00 00 02 06 03 00 | 88 b4 | 90 00ISO/IEC 14443-A tokensNXP MiFare Classic 4KBLibNFC's nfc-list -v command reports:1 ISO14443A passive target(s) found:ATQA (SENS_RES): 00 02* UID size: single* bit frame anticollision supportedUID (NFCID1): 7c 52 49 e4SAK (SEL_RES): 18* Not compliant with ISO/IEC 14443-4* Not compliant with ISO/IEC 18092Fingerprinting based on ATQA & SAK values:* Mifare Classic 4K* SmartMX with Mifare 4K emulationUsing the under Linux, it is possible to derive the sector keys for a genuine MiFare Classic card, whilst dumping and decrypting its entire contents in a reasonable timeframe (several minutes) on a moderately powerful PC.It appears that this tool does not work properly under VirtualBox, due to latency induced by its USB passthrough implementation. NXP MiFare DESFire EV1LibNFC's nfc-list -v command reports:1 ISO14443A passive target(s) found:ATQA (SENS_RES): 03 44* UID size: double* bit frame anticollision supportedUID (NFCID1): 04 8b 1f f1 ad 26 80SAK (SEL_RES): 20* Compliant with ISO/IEC 14443-4* Not compliant with ISO/IEC 18092ATS: 75 77 81 02 80* Max Frame Size accepted by PICC: 64 bytes* Bit Rate Capability:* PICC to PCD, DS=2, bitrate 212 kbits/s supported* PICC to PCD, DS=4, bitrate 424 kbits/s supported* PICC to PCD, DS=8, bitrate 847 kbits/s supported* PCD to PICC, DR=2, bitrate 212 kbits/s supported* PCD to PICC, DR=4, bitrate 424 kbits/s supported* PCD to PICC, DR=8, bitrate 847 kbits/s supported* Frame Waiting Time: 77.33 ms* Start-up Frame Guard Time: 0.6041 ms* Node ADdress not supported* Card IDentifier supported* Historical bytes Tk: 80* No COMPACT-TLV objects found, no status foundFingerprinting based on ATQA & SAK values:* Mifare DESFire / Desfire EV1DESFire EV1 OysterThe mifare-desfire-info utility reports:===> 0000 90 60 00 00 00 |.`... |<=== 0000 04 01 01 01 00 16 05 91 af |......... |===> 0000 90 af 00 00 00 |..... |<=== 0000 04 01 01 01 03 16 05 91 af |......... |===> 0000 90 af 00 00 00 |..... |<=== 0000 04 8b 1f f1 ad 26 80 00 00 00 00 00 42 08 91 00 |.....&......B...|===> Version information for tag 048b1ff1ad2680:UID: 0x048b1ff1ad2680Batch number: 0x0000000000Production date: week 42, 2008Hardware Information:Vendor ID: 0x04Type: 0x01Subtype: 0x01Version: 1.0Storage size: 0x16 (=2048 bytes)Protocol: 0x05Software Information:Vendor ID: 0x04Type: 0x01Subtype: 0x01Version: 1.3Storage size: 0x16 (=2048 bytes)Protocol: 0x05===> 0000 90 45 00 00 00 |.E... |<=== 0000 0b 01 91 00 |.... |Master Key settings (0x0b):0x08 configuration changeable;0x00 PICC Master Key not required for create / delete;0x02 Free directory list access without PICC Master Key;0x01 Allow changing the Master Key;===> 0000 90 64 00 00 01 00 00 |.d..... |<=== 0000 31 91 00 |1.. |Master Key version: 49 (0x31)===> 0000 90 6e 00 00 00 |.n... |<=== 0000 e0 04 00 91 00 |..... |Free memory: 1248 bytesUse random UID: noNXP MiFare UltraLightLibNFC's nfc-list -v command reports:1 ISO14443A passive target(s) found:ATQA (SENS_RES): 00 44* UID size: double* bit frame anticollision supportedUID (NFCID1): 04 45 57 ba 34 23 80SAK (SEL_RES): 00* Not compliant with ISO/IEC 14443-4* Not compliant with ISO/IEC 18092Fingerprinting based on ATQA & SAK values:* Mifare Ultralight* Mifare UltralightCOrange Cash PayPass CardLibNFC's nfc-list -v command reports:1 ISO14443A passive target(s) found:ATQA (SENS_RES): 00 04* UID size: single* bit frame anticollision supportedUID (NFCID1): 29 8b cf 51SAK (SEL_RES): 28* Compliant with ISO/IEC 14443-4* Not compliant with ISO/IEC 18092ATS: 78 80 82 02 80 31 80 66 b0 84 12 01 6e 01 83 00 90 00 * Max Frame Size accepted by PICC: 256 bytes* Bit Rate Capability:* Same bitrate in both directions mandatory* Frame Waiting Time: 77.33 ms* Start-up Frame Guard Time: 1.208 ms* Node ADdress not supported* Card IDentifier supported* Historical bytes Tk: 80 31 80 66 b0 84 12 01 6e 01 83 00 90 00* Tk after 0x80 consist of optional consecutive COMPACT-TLV data objects;the last data object may carry a status indicator of one, two or three bytes.See ISO/IEC 7816-4 8.1.1.3 for more infoFingerprinting based on ATQA & SAK values:* JCOP31 v2.3.1* SmartMX with Mifare 1K emulationUsing the following TAMA script, it is possible to access the EMV Payment System Environment, and obtain the name of the first application:02; // Get firmware version4A 01 00; // 1 target requested// Select the payment system environment40 01 00 A4 04 00 0E 31 50 41 59 2E 53 59 53 2E 44 44 46 30 31;40 01 80 A8 00 00 02 83 00;40 01 00 c0 00 00 26;40 01 00 b2 00 0c 00;40 01 00 b2 01 0c 00;40 01 00 b2 01 0c 21;ISO/IEC 14443-B tokenson the LibNFC project's issues list contains some details pertinent to the proprietary "14443-B'" technology used by some Calypso transport cards.Maxim MAX66040E-000AA+LibNFC's nfc-list -v command reports:1 ISO14443B passive target(s) found:PUPI: a2 a6 02 00Application Data: 30 00 2b e0Protocol Info: 77 21 71* Bit Rate Capability:* PICC to PCD, 1etu=64/fc, bitrate 212 kbits/s supported* PICC to PCD, 1etu=32/fc, bitrate 424 kbits/s supported* PICC to PCD, 1etu=16/fc, bitrate 847 kbits/s supported* PCD to PICC, 1etu=64/fc, bitrate 212 kbits/s supported* PCD to PICC, 1etu=32/fc, bitrate 424 kbits/s supported* PCD to PICC, 1etu=16/fc, bitrate 847 kbits/s supported* Maximum frame sizes: 32 bytes* Protocol types supported: ISO/IEC 14443-4* Frame Waiting Time: 38.66 ms* Frame options supported: NADThese cards are advertised as having a 64-bit UID, consisting of data in the PUPI field (e.g. a2 a6 02 00 or 34 ab 02 00), and data in the Application Data field (e.g. 77 21 71).The Application Data field supposedly contains the "upper 32 bits of the UID" (which appears to be consistent between new cards); and the (variable) PUPI corresponds to the "lower 32 bits of the UID".It is possible to run the Get System Information (0x2B) command using this PN532 TAMA shell script on a TouchATag reader:02; // Get firmware version//4A 01 00; // 1 target requested4a 01 03 00;40 01 2B;The TAMA commands are wrapped in an InDataExchange (0x40) packet that looks like d4 40 01 2bThe Get System Information command returns a result similar to 00 00 0f a2 a6 02 00 30 00 2b e0 00 00 13 07 b2PN532 Pseudo-APDUsISO/IEC 14443-B0000 d5 4b 01 01 50 34 ab 02 00 30 00 2b e0 77 21 710010 01 01 90 000000 d5 4b 01 01 50 a2 a6 02 00 30 00 2b e0 77 21 710010 01 01 90 00DESFire EV10000 d5 4b 01 01 03 44 20 07 04 8b 1f f1 ad 26 80 060010 75 77 81 02 80 90 00MiFare UltraLight0000 d5 4b 01 01 00 44 00 07 04 2b 6e ba 34 23 80 900010 00Sony FeliCa Lite RC-S7010000 d5 4b 01 01 14 01 01 27 00 5d 1a 05 8a cd 00 f00010 00 00 02 06 03 00 88 b4 90 00Hardware SuppliersAtmel of the USA have a .Although the order process appears to be successful (since I receive an e-mail in my university account), I have had limited success with using the confirmation URL provided in said e-mail, and have not seen any evidence of a product delivery, or further confirmation to date.of Japan supply Sony FeliCa (RC-S701) tags on an international basis, and fulfil orders promptly. They are also quick to provide refunds, should buyers accidentally make multiple payments for an order. As of writing, the grand total cost of shipping 2 tags to the UK was JPY2,168 (£19.19 according to PayPal).The Identive Group of the USA appear to be supplying on an international basis - although the author cannot vouch for thecompany's service, due to having never utilised it.Maxim supply a number of RFID-related products through a - although shipments are slightly delayed due to requiring internal Business Manager authorisation; and a commercial or academic e-mail address is required for successful order approval.Samples ordered within the UK are usually despatched from a UK-based warehouse, if memory serves correctly.Other InformationThe has a fairly exhaustive on Radio Frequency Identification-related content.。
nfc功能怎么打开
NFC（Near Field Communication）近场通信是一种无线通信技术，它通过近距离的无线电波来实现设备之间的交互和数据传输。
如果你想使用NFC功能，首先需要确保你的设备支持NFC功能。
以下是在手机中打开NFC功能的步骤：
1. 打开手机设置：在主屏幕上找到“设置”图标，点击打开手机的设置界面。
2. 进入无线和网络设置：在设置界面中找到“无线和网络”或“连接”选项，点击进入该选项的设置页面。
3. 打开NFC功能：在无线和网络设置页面中，找到“NFC”选项，可能需要向下滚动屏幕才能找到。
点击打开NFC开关，确认打开NFC功能。
4. 配置NFC偏好设置（可选）：一些设备可能还提供了一些额外的NFC偏好设置，例如默认支付应用、将来文件传输目录等。
根据个人需求进行设置。
5. 设置其他NFC功能（可选）：一些设备还提供了一些额外的NFC功能，例如NFC标签读取、NFC数据交换等。
根据个人需求，设置这些NFC功能。
6. 确认NFC功能已打开：在设置完以上步骤后，返回到手机主屏幕。
在状态栏上可能会出现一个NFC的图标，表示NFC 功能已打开。
虽然每个手机的设置界面可能略有不同，但大致的步骤应该是相似的。
如果你遇到了问题，可以参考手机的用户手册或在互联网上搜索相关的指导。
需要注意的是，NFC功能在不同的设备上可能会有一些不同的用途和限制，例如NFC标签的支持和应用的兼容性等。
在使用NFC功能时，建议阅读相关的使用说明，以了解更多关于NFC功能的信息。
