Electronic badges, electronic badge payment systems and payment methods
By physically isolating the display component and payment security component in the electronic badge, and combining the SCP03 secure channel and NFC power emergency mode, the problems of two-way payment, security and battery life of existing devices are solved, realizing instant transaction feedback and low power consumption and long battery life, meeting the diverse payment needs of users.
Patent Information
- Application Number
- CN202611160588.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-03
- Publication Date
- 2026-11-10
AI Technical Summary
Existing electronic badge devices have shortcomings in terms of form integration, security, transaction feedback, and battery life. They cannot achieve two-way payment, financial-grade security, instant transaction feedback, and low power consumption with long battery life. Furthermore, the payment function may fail in extreme cases.
It adopts a design that physically isolates the display component and the payment security component, communicates through the SCP03 secure channel, and combines NFC power-harvesting emergency mode and tri-state machine management to achieve bidirectional payment capability, financial-grade security, instant transaction feedback and low power consumption and long battery life.
It enables two-way payment capabilities within the same badge, providing financial-grade security, instant transaction feedback, and low power consumption with long battery life, ensuring payment functionality is available even in extreme situations, and enhancing user experience and device reliability.
Smart Images

Figure CN123070950A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of digital currency technology, and in particular to an electronic badge, an electronic badge payment system, and a payment method. Background Technology
[0002] With the promotion of digital currencies (such as the digital yuan) and the rise of ACG (Anime, Comics, and Games) culture and the IP-related economy, there is a growing demand for wearable devices that combine emotional collectible attributes with payment functions in scenarios such as anime conventions, concerts, IP-themed stores, and campuses. However, existing technical solutions have the following technical problems in terms of form factor integration, security, transaction feedback, and battery life:
[0003] First, existing electronic badges typically consist of a small display screen (low-power LCD / OLED, approximately 1.5 to 2.4 inches), a main control MCU, a battery, and a Bluetooth module. They only have functions such as image display, animation carousel, and Bluetooth image changing, and do not have any payment capabilities. While wearing the electronic badge, users still need to carry a separate mobile phone or physical bank card to complete the payment, resulting in a fragmented operation and an inconsistent user experience.
[0004] Secondly, existing digital RMB hardware wallets are mostly in the form of standard cards (IC cards), visual cards (with a small digital display screen that only shows the balance), or embedded mobile phone SIM cards / wristbands. Their shortcomings are: no screen or only a segment code screen, unable to display QR code payment codes, transaction details, or personalized content; a single form, lacking emotional and collectible attributes, resulting in low user willingness to carry them; and after completing dual offline payments, users lack immediate and intuitive feedback on transaction results.
[0005] Third, although existing payment wristbands integrate NFC payment, they have significant drawbacks: the display and payment share the same main control and operating system; the processing path for payment-sensitive data (keys, PINs, transaction messages) is not physically isolated from ordinary display services, resulting in limited security levels and difficulty in meeting financial-grade security certification requirements; they typically only support a single payment application (such as a single UnionPay application) and do not support the coexistence and automatic routing of digital currency hard wallets and international card organization EMV applications within the same security unit; the payment function completely fails after the main battery is depleted, making it unable to meet emergency payment needs.
[0006] Fourth, existing visual hardware wallets suffer from passive triggering and delayed feedback in their information acquisition methods. Users need to actively press a button or query through an app to obtain transaction results, resulting in a time lag between payment completion and screen display. This is particularly noticeable in dual offline payment scenarios, where users cannot immediately confirm the deducted amount and balance after payment, impacting the trust experience. Furthermore, display triggering relies on external commands; the device itself lacks the ability to proactively sense transaction status and provide immediate feedback.
[0007] Fifth, existing devices lack security protection for board-level data transmission. If communication between the main control unit and the security unit is transmitted in plaintext, sensitive information such as transaction summaries and balances may be stolen by physical probes or man-in-the-middle attacks. In addition, the NFC modules of existing devices continuously listen at full power in standby mode, resulting in high power consumption and significantly shortening battery life; moreover, the interactive experience is limited, typically only supporting payments or only supporting receiving payments, and cannot achieve two-way payment capabilities on the same device.
[0008] In summary, existing technologies urgently need a comprehensive solution that integrates a digital currency hard wallet into a small wearable badge, enables two-way payment capabilities, ensures financial-grade security, provides instant transaction feedback, and supports low power consumption, long battery life, and passive emergency payments. Summary of the Invention
[0009] The technical objective of this disclosure is to provide an electronic badge, an electronic badge payment system, and a payment method.
[0010] According to a first aspect of this disclosure, an electronic badge is provided, comprising: a display component and a payment security component; the display component includes a display screen, a display control unit, and a Bluetooth module; the payment security component includes a security unit, an NFC front-end chip, and an NFC antenna, wherein the security unit internally loads a digital currency hard wallet application, and the security unit is directly connected to the NFC front-end chip; the display control unit and the security unit communicate through a secure channel.
[0011] In the payment process, the display control unit receives the payment code token from the application terminal through the Bluetooth module, and renders the payment code on the display screen according to the payment code token, so that external payment devices can scan the code to pay.
[0012] During the payment process, after the electronic badge is brought close to the acceptance terminal, the NFC front-end chip receives payment information from the acceptance terminal through the NFC antenna and sends the payment information directly to the security unit. The security unit uses the digital currency hard wallet application to complete the offline or online transaction and sends the transaction summary to the display master control unit through the security channel. The display master control unit then displays the transaction result on the display screen based on the transaction summary.
[0013] Furthermore, after the display control unit detects that the user has performed a set action, it enables the payment window and notifies the security unit to start the payment function, so that the security unit switches the digital currency hard wallet application from a disabled state to a responsive state; after the payment window times out or the transaction is completed, the display control unit notifies the security unit that the payment is complete, so that the security unit restores the digital currency hard wallet application to a disabled state.
[0014] Furthermore, the secure channel unit uses an I2C or SPI serial interface superimposed with the SCP03 secure channel protocol. The SCP03 secure channel protocol establishes a secure channel through bidirectional authentication and session key derivation. Subsequent communication through the established secure channel uses AES-128-CBC encryption and AES-CMAC integrity verification.
[0015] Furthermore, the secure channel allows the transmission of two types of data: signed transaction digests from the secure unit to the display control unit; and cloud-signed management instructions from the display control unit to the secure unit.
[0016] Furthermore, the secure channel is established as follows: after the main control unit initializes the session context and security level and generates host challenge information, it sends an initialization update command carrying the host challenge information to the security unit;
[0017] The security unit extracts the host challenge information from the initialization update instruction and generates security unit challenge information;
[0018] The security unit also calculates a security unit encryption token based on the host challenge information and the security unit challenge information using a pre-shared static key set, and returns a response message containing the security unit challenge information and the security unit encryption token to the display control unit.
[0019] The display control unit extracts the security unit challenge information and the security unit encryption token from the response message, and verifies the security unit encryption token based on a pre-shared static key set;
[0020] After successful verification, the display control unit also uses the static key set to calculate the host encryption token based on the host challenge information and the security unit challenge information, and returns the host encryption token to the security unit.
[0021] The security unit uses the static key set to verify the host encryption token;
[0022] After both the host encryption token and the security unit encryption token are verified, the display control unit and the security unit derive a session encryption key, an integrity verification key, and a response integrity verification key for the current session based on the host challenge information, the security unit challenge information, and the static key set, respectively.
[0023] Furthermore, after the secure channel is established, all transaction summaries and management instructions are encapsulated in TLV format, encrypted using the AES-128-CBC encryption algorithm and the session encryption key, and transmitted with an AES-CMAC checksum generated based on the integrity verification password.
[0024] Furthermore, it also includes a power management unit, which includes an NFC power emergency mode; in the NFC power emergency mode, when the main battery voltage is lower than a set voltage threshold, the NFC front-end chip collects energy from the external card reader's radio frequency field, and after rectification and voltage regulation, distributes it to the security unit, the display screen and the display main control unit according to a set priority; the set priority is the security unit highest, the display screen second, and the display main control unit lowest, and the display screen is in a partial refresh state.
[0025] Furthermore, the NFC front-end chip is managed by a three-state machine of sleep mode, listening mode, and active mode. In sleep mode, the NFC front-end chip and NFC antenna are turned off, and the chip enters listening mode after being periodically woken up by a timer. In listening mode, the NFC front-end chip passively detects the radio frequency field, and enters active mode after detection. In active mode, the transaction is completed, and the chip returns to sleep mode after the transaction is completed or after a timeout period without operation.
[0026] According to a second aspect of this disclosure, an electronic badge payment system is provided, comprising: an electronic badge, an application terminal, a cloud management platform, and a digital currency payment operation institution system; wherein, the electronic badge terminal is as described in the first aspect; the application terminal remotely operates the electronic badge using Bluetooth communication; the cloud management platform is responsible for device lifecycle management, issuance of payment code tokens, and firmware OTA distribution; the firmware OTA package received by the electronic badge is signed and verified by the cloud management platform, and the digital currency hard wallet application of the secure channel is updated through the trusted service management channel of the digital currency payment operation institution system.
[0027] According to a third aspect of this disclosure, a payment method is provided, said method being performed by the electronic badge described in the first aspect; comprising:
[0028] After detecting a preset action performed by the user on the electronic badge, the display control unit enables the payment window and sends a request to the security unit to enable the payment function.
[0029] Upon receiving the activation request, the security unit switches the digital currency hard wallet application from a disabled state to a responsive state.
[0030] After the electronic badge is placed close to the acceptance terminal, the NFC front-end chip receives transaction information from the acceptance terminal through the NFC antenna and sends the transaction information directly to the digital currency hard wallet application in the secure unit for transaction.
[0031] After the transaction is completed, the security unit generates a transaction digest and signs it with the session key within the security unit;
[0032] The signed transaction summary is sent to the main control unit via a secure channel;
[0033] After verifying the signature, the main control unit partially refreshes the display screen to show the transaction result.
[0034] The security unit automatically switches back to the disabled state after the payment window times out or the transaction is completed.
[0035] After connecting to the application terminal, the transaction log of the main control unit is displayed.
[0036] Furthermore, the electronic badge includes a power management unit; the method further includes:
[0037] When the remaining power of the main battery is less than a set power threshold, the power management unit enters the NFC power emergency mode.
[0038] In the NFC power emergency mode, the NFC front-end chip collects energy from the radio frequency field of the external card reader through the NFC antenna, and allocates energy to the security unit, the display screen, and the display main control unit according to the set priority. In the NFC power emergency mode, the display screen adopts a partial refresh method.
[0039] Furthermore, the method also includes the following process for establishing a secure channel:
[0040] After the main control unit initializes the session context and security level and generates host challenge information, it sends an initialization update command carrying the host challenge information to the security unit.
[0041] The security unit extracts the host challenge information from the initialization update instruction and generates security unit challenge information;
[0042] The security unit also calculates a security unit encryption token based on the host challenge information and the security unit challenge information using a pre-shared static key set, and returns a response message containing the security unit challenge information and the security unit encryption token to the display control unit.
[0043] The display control unit extracts the security unit challenge information and the security unit encryption token from the response message, and verifies the security unit encryption token based on a pre-shared static key set;
[0044] After successful verification, the display control unit also uses the static key set to calculate the host encryption token based on the host challenge information and the security unit challenge information, and returns the host encryption token to the security unit.
[0045] The security unit uses the static key set to verify the host encryption token;
[0046] After both the host encryption token and the security unit encryption token are verified, the display control unit and the security unit derive a session encryption key, an integrity verification key, and a response integrity verification key for the current session based on the host challenge information, the security unit challenge information, and the static key set, respectively.
[0047] According to a fourth aspect of this disclosure, a payment method is provided, said method being executed by the electronic badge payment system described in the second aspect; comprising:
[0048] In response to the user's action, the application terminal initiates a request to generate a payment code;
[0049] After receiving the payment code request, the cloud management platform verifies the device status of the electronic badge and the user identity of the application terminal, generates a time-limited payment code token, and returns it to the application terminal.
[0050] After receiving the payment code token, the application terminal sends the payment code token to the electronic badge via Bluetooth communication;
[0051] After receiving the payment code token via Bluetooth, the main control unit of the electronic badge verifies the signature and validity of the payment code token, renders the payment code, and refreshes the display screen to display the payment code.
[0052] After the payment code token expires or a payment completion message is received, the main control unit automatically refreshes the display screen to clear the payment code.
[0053] Other features and advantages of this disclosure will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the disclosure. The objects and other advantages of this disclosure may be realized and obtained by means of the structures particularly pointed out in the description, claims and drawings. Attached Figure Description
[0054] The accompanying drawings are provided to further illustrate the present disclosure and form part of the specification. They are used in conjunction with the embodiments of the present disclosure to explain the disclosure and do not constitute a limitation thereof. In the drawings:
[0055] Figure 1 This is a schematic diagram of the overall architecture of the electronic badge payment system described in this embodiment of the disclosure;
[0056] Figure 2 This is a schematic diagram of the hardware architecture of the electronic badge terminal described in an embodiment of this disclosure;
[0057] Figure 3 This is a schematic diagram illustrating the process of establishing an SCP03 secure channel between the display component and the payment security component as described in this embodiment of the disclosure.
[0058] Figure 4 This is a schematic diagram of the payment direction and result display process described in the embodiments of this disclosure;
[0059] Figure 5 This is a schematic diagram of the process for generating and displaying the payment code in the payment direction as described in the embodiments of this disclosure. Detailed Implementation
[0060] To make the purpose, technical solution and advantages of this disclosure clearer, the following detailed description is provided in conjunction with the accompanying drawings.
[0061] This disclosure aims to solve the following technical problems: (1) How to realize the bidirectional payment capability of displaying the QR code and NFC hard wallet tap-to-pay simultaneously in a small electronic badge, so that users can complete the receiving and payment operations while wearing the badge; (2) How to establish a physical isolation and controlled security channel between the display main control unit and the payment security component, so that payment sensitive data does not pass through the display main control unit and meets financial-grade security requirements; (3) How to realize the reliable and real-time feedback of dual offline transaction results on a low-power small screen device, so that users can know the deducted amount and balance immediately after payment; (4) How to use NFC radio frequency field energy to complete emergency payment and result display when the main battery is exhausted, so as to ensure payment availability in extreme cases; (5) How to extend the device's battery life through a low-power NFC listening strategy, so that the small badge can achieve a standby time of several weeks to several months with limited battery capacity; (6) How to realize the secure separation of firmware OTA and payment application updates, so as to ensure the security and maintainability of the device throughout its life cycle.
[0062] This disclosure presents a displayable electronic badge payment system and its payment method integrating a digital currency hard wallet. The system includes an electronic badge terminal, an application terminal, a cloud platform, and an operating institution system. The electronic badge terminal comprises a display component and a payment security component, which are physically isolated. The display component's screen displays an IP image, a QR code for payment, and the transaction result. The security unit of the payment security component is directly connected to the NFC front-end chip, and payment messages do not pass through the display control unit, achieving physical isolation. The display control unit and the security unit communicate via an SCP03 secure channel, establishing a session using a bidirectional challenge-response authentication mechanism based on a static key set, transmitting only signed transaction digests and management instructions. The power management unit supports an NFC-powered emergency mode. This disclosure achieves bidirectional payment capabilities—displaying a payment code and NFC tap-to-pay—within a small badge. Physical isolation and SCP03 encryption ensure financial-grade security. It supports instant display of offline transaction results, low power consumption and long battery life, and passive emergency payment, combining emotional collectible attributes with payment functionality.
[0063] According to one embodiment of this disclosure, an electronic badge is provided, including a display component and a payment security component. The display component includes a display screen, a display control unit, and a Bluetooth module; the payment security component includes a security unit, an NFC front-end chip, and an NFC antenna. The security unit internally loads a digital currency hard wallet application and is directly connected to the NFC front-end chip, enabling payment messages to be transmitted directly between the security unit and the NFC front-end chip without passing through the display control unit, thus achieving physical isolation between the display domain and the payment security domain; the display control unit and the security unit communicate via a secure channel.
[0064] During the payment process, the display control unit receives a payment code token from the application terminal via the Bluetooth module, and renders the payment code on the display screen according to the payment code token, so that external payment devices can scan the code to make payments.
[0065] During the payment process, after the electronic badge is brought close to the acceptance terminal, the NFC front-end chip receives payment information from the acceptance terminal through the NFC antenna and sends the payment information directly to the security unit. The security unit uses the digital currency hard wallet application to complete the offline or online transaction and sends the transaction summary to the display master control unit through the security channel. The display master control unit then displays the transaction result on the display screen based on the transaction summary.
[0066] Through the aforementioned two-way payment design, the same electronic badge can both display a payment code as a recipient and perform NFC tap-to-pay as a payer, meeting the diverse needs of users in scenarios such as comic conventions and IP-themed stores who need to receive payments (such as vendors) and make payments (such as consumers).
[0067] In some optional implementations, the display control unit enables the payment window after detecting a user's set action and notifies the security unit to activate the payment function, causing the security unit to switch the digital currency hardware wallet application from a disabled state to a responsive state. After the payment window times out or the transaction is completed, the display control unit notifies the security unit that the payment is complete, causing the security unit to restore the digital currency hardware wallet application to a disabled state. The set action includes, but is not limited to, double-clicking the badge surface, long-pressing a button, or using specific gestures to flip the device. Through the payment window mechanism, the digital currency hardware wallet application (applet) is in a disabled state during non-payment periods and cannot be woken up by an external card reader, effectively preventing unauthorized NFC scanning and fraudulent transactions, and improving payment security.
[0068] In some optional implementations, the secure channel employs an I2C or SPI serial interface overlaid with the SCP03 secure channel protocol. The SCP03 secure channel protocol establishes the secure channel through bidirectional authentication and session key derivation. Subsequent communication through this established secure channel uses AES-128-CBC encryption and AES-CMAC integrity verification. The secure channel allows the transmission of two types of data: the first is a signed transaction digest from the secure unit to the display control unit, used for transaction result display; the second is a cloud-signed management command from the display control unit to the secure unit, used for remote management of the secure unit. By limiting the secure channel to transmitting only transaction digests and management commands—two types of non-sensitive data—rather than complete payment messages, the impact of a compromised display domain on the payment security domain is further reduced.
[0069] In some optional implementations, the establishment process of the secure channel is as follows: After the display master unit initializes the session context and security level and generates host challenge information, it sends an initialization update instruction carrying the host challenge information to the security unit; the security unit extracts the host challenge information from the initialization update instruction and generates security unit challenge information; the security unit also calculates a security unit encryption token based on a pre-shared static key set for the host challenge information and the security unit challenge information, and returns a response message containing the security unit challenge information and the security unit encryption token to the display master unit; the display master unit extracts the security unit challenge from the response message. The system processes information and a security unit encryption token, and verifies the security unit encryption token based on a pre-shared static key set. Upon successful verification, the display control unit calculates a host encryption token using the static key set against the host challenge information and security unit challenge information, and returns the host encryption token to the security unit. The security unit then verifies the host encryption token using the static key set. After both the host encryption token and the security unit encryption token are verified, the display control unit and the security unit derive session encryption keys, integrity verification keys, and response integrity verification keys specific to the current session based on the host challenge information, security unit challenge information, and the static key set, respectively. Initializing the session context and security level includes clearing the SCP03 session context structure and setting the security level to 0x03, enabling dual protection of encryption (ENC) and message authentication (MAC). This authentication mechanism based on a static key set and a two-way challenge-response approach is suitable for resource-constrained MCU and SE environments, while ensuring the legitimacy of both communicating parties and the freshness of the session through two-way token verification.
[0070] In some optional implementations, after the secure channel is established, all transaction summaries and management instructions are encapsulated in TLV format, encrypted using AES-128-CBC and the session encryption key, and transmitted with an AES-CMAC checksum generated based on the integrity verification key. The TLV encapsulation includes a tag field, a length field, and a value field, where the tag field identifies the data type, the length field identifies the length of the value field, and the value field carries the actual data content. This combination of TLV encapsulation, AES-128-CBC encryption, and AES-CMAC verification ensures the confidentiality and integrity of data during board-level transmission, preventing physical probing and tampering attacks.
[0071] In some optional implementations, the electronic badge further includes a power management unit, which includes an NFC power-charging emergency mode. When the main battery voltage falls below a set voltage threshold, the power management unit enters the NFC power-charging emergency mode. In this mode, the NFC front-end chip collects energy from the external reader's radio frequency field, and after rectification and voltage regulation, distributes it to the security unit, display screen, and display control unit according to a set priority. The set priority is: security unit highest, display screen second, and display control unit lowest, with the display screen in a partial refresh state. Through the NFC power-charging emergency mode, even if the main battery is completely depleted, the electronic badge can still use radio frequency field energy to complete emergency payment and transaction result display when it is close to the payment terminal, ensuring payment availability in extreme situations.
[0072] In some optional implementations, the NFC front-end chip employs a three-state machine management system encompassing sleep mode, listening mode, and active mode. In sleep mode, the NFC front-end chip and NFC antenna are turned off, and the chip enters listening mode after periodic wake-ups by a timer. In listening mode, the NFC front-end chip passively detects radio frequency fields, and enters active mode upon detection. In active mode, a transaction is completed, and the chip returns to sleep mode after the transaction is completed or after a timeout period of inactivity. Through this three-state machine management, the NFC operates in a very low-power sleep mode during non-transaction periods, passively detecting radio frequency fields only during brief periodic listening windows, significantly reducing standby power consumption and extending battery life.
[0073] According to another embodiment of this disclosure, an electronic badge payment system is provided, including an electronic badge, an application terminal, a cloud management platform, and a digital currency payment operation institution system. The electronic badge is as described above in this disclosure; the application terminal uses Bluetooth communication to remotely operate the electronic badge, including issuing payment code tokens, synchronizing transaction records, and pushing personalized content; the cloud management platform is responsible for device lifecycle management, payment code token issuance, and firmware OTA distribution; the firmware OTA package received by the electronic badge is signed and verified by the cloud management platform to ensure the trustworthiness and integrity of the firmware source; the digital currency hard wallet application of the security unit is updated through the Trusted Service Management (TSM) channel of the digital currency payment operation institution system to achieve secure over-the-air card issuance and lifecycle management of the payment application. Through the separation design of the cloud management platform and the TSM channel, firmware updates and payment application updates each use independent secure channels, without interference, improving the overall security and maintainability of the system.
[0074] According to another embodiment of this disclosure, a payment method (payment direction) based on the above-mentioned electronic badge is provided, including the following steps: after detecting a preset action performed by a user on the electronic badge, the display control unit enables the payment window and sends a payment function activation request to the security unit; after receiving the activation request, the security unit switches the digital currency hard wallet application from a disabled state to a responsive state; after the electronic badge is brought close to the acceptance terminal, the NFC front-end chip receives transaction information from the acceptance terminal through the NFC antenna and sends the transaction information directly to the digital currency hard wallet application in the security unit for transaction; after the transaction is completed, the security unit generates a transaction digest and signs it with the session key in the security unit; the signed transaction digest is sent to the display control unit through a secure channel; after verifying the signature, the display control unit partially refreshes the display screen to display the transaction result; when the payment window times out or the transaction is completed, the security unit automatically switches back to the disabled state; after connecting to the application terminal, the display control unit synchronizes the transaction flow. Through the above process, the user only needs to double-click the badge to enable the payment window and bring it close to the acceptance terminal to complete the payment, and immediately see the transaction result on the badge screen after the payment is completed, without having to open a mobile app to check.
[0075] According to another embodiment of this disclosure, a payment method (receiving direction) based on the above-mentioned electronic badge payment system is provided, including the following steps: In response to a user's operation, an application terminal initiates a request to generate a payment code; after receiving the payment code request, the cloud management platform verifies the device status of the electronic badge and the user identity of the application terminal, generates a time-limited payment code token, and returns it to the application terminal; after receiving the payment code token, the application terminal sends the payment code token to the electronic badge via Bluetooth communication; after receiving the payment code token through the Bluetooth module, the display control unit of the electronic badge verifies the signature and validity of the payment code token, renders the payment code, and refreshes the display screen to display the payment code; after the payment code token expires or a payment completion message is received, the display control unit automatically refreshes the display screen to clear the payment code. Through the time-limited control and signature verification of the payment code token, it is ensured that the payment code cannot be tampered with or replayed, and the automatic clearing upon expiration prevents expired codes from being mistakenly scanned.
[0076] The embodiments provided in this disclosure can achieve the following technical effects:
[0077] First, it integrates two-way payment capabilities and form factor. This invention integrates a display screen and NFC hard wallet payment within a single electronic badge, supporting both QR code display (for receiving payments) and NFC tap-to-pay (for sending payments). Users can complete two-way payment operations simply by wearing a badge. Simultaneously, the display screen can show personalized content such as IP images and animations, combining emotional collectible attributes with payment functionality, meeting the needs of users in scenarios such as comic conventions and IP-themed stores for emotional wearable payment devices.
[0078] Second, physical isolation and financial-grade security. This disclosure physically isolates the display component from the payment security component. The security unit is directly connected to the NFC front-end chip, and payment messages do not pass through the display control unit, cutting off the exposure path of sensitive payment data at the hardware level. The display control unit and the security unit communicate through the SCP03 secure channel, using a two-way challenge-response authentication mechanism based on a static key set to establish a session. Subsequent communication uses AES-128-CBC encryption and AES-CMAC integrity verification to ensure the confidentiality and integrity of board-level data transmission. The secure channel only transmits two types of non-sensitive data: transaction summaries and management instructions, further reducing security risks.
[0079] Third, instant transaction feedback and dual offline support. Upon completion of a transaction, the security unit immediately generates a transaction digest signed with the session key and sends it to the display control unit via a secure channel. The display control unit verifies the signature and then partially refreshes the display screen to show the transaction result. Even in dual offline payment scenarios (where neither the electronic badge nor the payment terminal is connected to the internet), users can still immediately confirm the deducted amount and balance on the badge screen after payment, eliminating the time lag between payment completion and result feedback and enhancing the trust experience.
[0080] Fourth, passive emergency payment. The power management unit disclosed herein supports an NFC-powered emergency mode. When the main battery voltage is lower than a set threshold, the NFC front-end chip collects energy from the external reader's radio frequency field. After rectification and voltage regulation, energy is allocated according to the priority order: highest for the security unit, second for the display screen, and lowest for the display control unit. The display screen uses a partial refresh method to reduce power consumption. Even if the main battery is completely depleted, the electronic badge can still complete emergency payments and display transaction results, ensuring payment availability in extreme situations.
[0081] Fifth, low power consumption and long battery life. The NFC front-end chip disclosed herein employs a three-state machine management system consisting of sleep mode, listening mode, and active mode. During non-transaction periods, it is in a very low-power sleep mode, only periodically woken up by a timer to enter listening mode for passive detection of radio frequency fields. Only after detecting a radio frequency field does it enter active mode to complete the transaction. This mechanism reduces the standby power consumption of the NFC module by more than an order of magnitude. Combined with the zero-power retention characteristic of the display, this allows small badges to achieve standby times of several weeks to several months with limited battery capacity.
[0082] Sixth, a secure and maintainable system architecture. The disclosed electronic badge payment system uses a cloud management platform for firmware OTA distribution (with signature verification) and a TSM channel within the digital currency payment operator's system for updating the digital currency hardware wallet application. These two update channels are independent and each performs its own function. Firmware updates ensure device function iteration and vulnerability patching, while the TSM channel ensures secure over-the-air card issuance and lifecycle management of the payment application. This separation avoids single points of failure and security coupling, improving the overall maintainability and security of the system.
[0083] The present disclosure will now be described in further detail with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the present disclosure. In the description of the present disclosure, it should be understood that the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features.
[0084] Example 1: System Overall Architecture
[0085] like Figure 1As shown, this embodiment provides an electronic badge payment system, comprising four parts: an electronic badge terminal (also known as an electronic badge), an application terminal (running the electronic badge's accompanying APP, not shown in the figure), a cloud management platform, and a digital currency payment operation institution system. These parts are interconnected via Bluetooth Low Energy (BLE), the Internet, and a dedicated digital currency network to collaboratively perform functions such as device management, QR code issuance, firmware OTA distribution, payment application updates, and transaction processing.
[0086] The electronic badge terminal is a wearable device worn by the user, shaped like a round or square badge (stick), approximately 55 to 75 mm in diameter and 8 to 12 mm thick. The front features a display screen, while the back houses the NFC antenna area. Internally, the electronic badge terminal integrates display and payment security components, supporting two-way payment capabilities including QR code display and NFC tap-to-pay with a hard wallet. The electronic badge terminal communicates with application terminals via BLE, receiving QR code tokens, synchronizing transaction records, and pushing personalized content.
[0087] The application terminal is deployed on the user's smartphone, serving as the remote operation entry point for the electronic badge terminal. The application terminal establishes a connection with the electronic badge terminal via BLE, providing functions such as initiating payment code requests, viewing transaction records, personalized image push notifications, device status queries, and triggering firmware OTA updates. The application terminal also communicates with the cloud management platform, forwarding user requests to the cloud and receiving data such as payment code tokens and firmware packages returned from the cloud.
[0088] The cloud-based management platform is the core management backend of the system, responsible for the full lifecycle management of the electronic badge terminals. Specific functions include: device registration and activation, device status monitoring (online / offline, battery level, firmware version, etc.), payment code token issuance (generating time-limited payment code tokens after verifying device status and user identity), firmware OTA distribution (pushing signed new firmware packages to application terminals, which then distribute them to the electronic badge terminals via BLE), user account management, and transaction data statistics and analysis. The cloud-based management platform connects to the digital currency payment operator's system to obtain authorization for card issuance and updates for digital currency hardware wallet applications.
[0089] The digital currency payment operator system is the official operating system for digital currencies (such as the digital yuan), responsible for the issuance, circulation, and management of digital currencies. Within this system, the digital currency payment operator system communicates with the secure unit of the electronic badge terminal through a Trusted Service Management (TSM) channel to achieve secure over-the-air card issuance, application updates, key rotation, and other lifecycle management operations for digital currency hard wallet applications. The TSM channel and the firmware OTA channel of the cloud management platform are independent, handling payment application updates and device firmware updates respectively, avoiding secure coupling.
[0090] During system operation, the firmware OTA packages received by the electronic badge terminal are signed and verified by the cloud management platform, ensuring the trustworthiness and integrity of the firmware source. The digital currency hardware wallet application in the security unit is updated through the TSM channel of the digital currency payment operator system, ensuring secure over-the-air card issuance and lifecycle management of the payment application. Through the above architectural design, the system achieves secure separation and collaboration of functions such as device management, payment application management, and transaction processing.
[0091] Example 2: Electronic Badge Terminal Hardware Architecture
[0092] like Figure 2 As shown, this embodiment provides the hardware architecture of an electronic badge terminal. The electronic badge terminal includes two main parts: a display component and a payment security component. These two parts are physically isolated from each other and exchange limited data only through a controlled secure channel.
[0093] The display components include a display screen, a display control unit (MCU), and a Bluetooth module (not shown in the diagram). The display screen can be, for example, a 1.54-inch or 2.13-inch E-Ink display with a resolution of 152×152 or 250×122, supporting black and white or tri-color (black, white, and red) display, and featuring zero-power retention (the image remains unchanged after power loss). The display control unit can be, for example, a low-power ARM Cortex-M0+ or M4 core MCU (such as Nordic nRF52840, STM32L4 series), with a clock frequency of 64MHz to 128MHz, built-in Flash and SRAM, and running firmware such as display drivers, Bluetooth protocol stack, secure channel client, and state machine management. The Bluetooth module can be, for example, using the BLE 5.0 or 5.2 protocol, operating in the 2.4GHz band, communicating with the application terminal, and supporting low-power retention during connection and automatic reconnection after disconnection.
[0094] The payment security components include a security element (SE), an NFC front-end chip, and an NFC antenna (not shown in the diagram). The security element can be, for example, a financial-grade security certified SE chip (such as the NXP NCJ38D or Infineon SLC series), supporting Java Card OS and GlobalPlatform specifications. It internally loads a digital currency hard wallet application (such as a digital RMB hard wallet applet) and stores sensitive data such as payment keys, certificates, and transaction logs. The security element is directly connected to the NFC front-end chip, communicating via an ISO 7816 or SWP interface. Payment messages are transmitted directly between the security element and the NFC front-end chip, bypassing the display control unit, thus achieving physical isolation between the display domain and the payment security domain. The NFC front-end chip can be, for example, an NXP PN5180 or ST25R3916, supporting the ISO 14443 Type A / B protocol, operating in the 13.56MHz frequency band, and communicating contactlessly with external acceptance terminals via the NFC antenna. The NFC antenna is a loop PCB antenna or FPC antenna, integrated on the back of the badge.
[0095] The main control unit and the secure unit are connected via an I2C or SPI serial interface, with the SCP03 secure channel protocol superimposed on the serial interface. Once the secure channel is established, only two types of data are transmitted between the main control unit and the secure unit: a signed transaction digest from the secure unit to the main control unit (used for transaction result display), and a cloud-signed management command from the main control unit to the secure unit (used for remote management of the secure unit). Payment messages (such as transaction requests, responses, keys, etc.) are always transmitted directly between the secure unit and the NFC front-end chip, without passing through the secure channel, ensuring that sensitive payment data is not exposed to the display field.
[0096] The electronic badge terminal also includes a power management unit, comprising a main battery (such as a lithium polymer battery with a capacity of 150 to 300 mAh), a charging management chip (such as TP4056), a low-dropout linear regulator (LDO), and an NFC power harvesting circuit. The power management unit supports an NFC power harvesting emergency mode. When the main battery voltage is lower than a set voltage threshold (such as 3.3V), the NFC front-end chip collects energy from the external reader's radio frequency field. After rectification and voltage regulation, energy is allocated according to a priority order: highest for the security unit, second for the display screen, and lowest for the display main control unit. The display screen uses a partial refresh method to reduce power consumption. Detailed implementation of the power management unit is shown in Embodiment Seven.
[0097] In the payment collection process, the main control unit receives the payment code token from the application terminal via Bluetooth. After verifying the token's signature and validity, it renders the payment code (such as a digital RMB payment code or an aggregated payment code) on the display screen based on the token's content, allowing external payment devices to scan and make payments. In the payment process, after the electronic badge terminal is brought close to the acceptance terminal (such as a merchant's POS terminal), the NFC front-end chip receives payment information from the acceptance terminal via the NFC antenna and sends the payment information directly to the security unit. The security unit uses a digital currency hardware wallet application to complete the offline or online transaction, generates a transaction summary, and sends it to the main control unit via a secure channel. The main control unit then displays the transaction result (such as the deduction amount, balance, and transaction time) on the display screen.
[0098] Example 3: Implementation of the SCP03 Protocol for Inter-Domain Secure Channels
[0099] like Figure 3 As shown, this embodiment provides the establishment and data transmission process of the SCP03 secure channel between the display control unit (MCU) of the display component and the security unit (SE) of the payment security component. This embodiment adopts an authentication mechanism based on a pre-shared static key set and a two-way challenge-response mechanism, which does not require certificate chains and public key operations, making it suitable for resource-constrained MCU and SE environments.
[0100] Before a secure channel is established, the MCU and SE share a set of static keys during the factory initialization phase. This static key set includes a static encryption key SK-ENC, a static integrity verification key SK-MAC, and a static key encryption key SK-KEK, all of which are stored in the MCU's secure storage area and the SE's protected storage area. The static key set is bound to the SE's unique identifier (such as SEID), and each SE corresponds to a unique static key set.
[0101] The process of establishing a secure passage includes the following steps:
[0102] Step S301: The MCU initializes the session context and security level, and generates host challenge information. The host challenge information is an 8-byte random number generated by the MCU using a hardware random number generator to ensure session freshness. The MCU sends an initialization update command (INITIALIZE UPDATE) to the SE, which carries the host challenge information and the security level requested by the MCU (such as the SCP03 protocol version, key suite identifier, etc.).
[0103] Step S302: After receiving the initialization update command, the SE extracts the host challenge information and generates a Secure Element Challenge (SE Challenge) using its own hardware random number generator, which is also an 8-byte random number. The SE also calculates a Secure Element Cryptographic Token (SECryptogram) based on the pre-shared static key set, using the host challenge information, the Secure Element Challenge information, and the SE's counter value (such as the serial number) as input, and calculates the Secure Element Cryptographic Token using the AES-CMAC algorithm. Subsequently, the SE returns a response message to the MCU, which includes the Secure Element Challenge information, the Secure Element Cryptographic Token, and information such as the SE's key version number and protocol parameters.
[0104] Step S303: The MCU extracts the security element challenge information and the security element encryption token from the response message. Based on its own stored pre-shared static key set, the MCU calculates the desired security element encryption token in the same way as the SE, and compares the calculation result with the security element encryption token in the response message for verification. If the verification passes, the MCU confirms that the SE's identity is legitimate and the session is fresh; if the verification fails, the MCU aborts the secure channel establishment process and records the security event.
[0105] Step S304: After successful verification, the MCU calculates the Host Cryptogram using the static key set based on the Host Challenge Information and the Security Unit Challenge Information. For example, the MCU uses SK-MAC as the key, taking the Security Unit Challenge Information, the Host Challenge Information, and the MCU's counter value as input, and calculates the Host Cryptogram using the AES-CMAC algorithm. The MCU then sends the Host Cryptogram to the SE via an External Authenticator command.
[0106] Step S305: After receiving the host encryption token, the SE uses its stored static key set to calculate the desired host encryption token in the same way as the MCU, and compares the calculation result with the received host encryption token for verification. If the verification passes, the SE confirms the MCU's legitimate identity; if the verification fails, the SE aborts the secure channel establishment process and locks the session.
[0107] Step S306: After both the host encryption token and the security element encryption token have been successfully verified, the MCU and SE derive the session encryption key (S-ENC), integrity verification key (S-MAC), and response integrity verification key (S-RMAC) for the current session based on the host challenge information, security element challenge information, and static key set, respectively. Specifically, both parties use SK-KEK as the key for key derivation, taking the concatenation of the host challenge information and security element challenge information as input, and derive the three sets of session keys, S-ENC, S-MAC, and S-RMAC, respectively, through the key derivation function (KDF). These three sets of session keys are only used for the current session and are destroyed after the session ends.
[0108] Step S307: After the secure channel is established, all subsequent communication between the MCU and SE is protected using a session key. In some embodiments, all transaction summaries and management instructions are encapsulated in TLV (Tag-Length-Value) format: the tag field identifies the data type (such as transaction summary, management instruction, status query, etc.), the length field identifies the length of the value field, and the value field carries the actual data content. The encapsulated TLV data is encrypted using S-ENC as the key and the AES-128-CBC algorithm to ensure data confidentiality; at the same time, an AES-CMAC checksum generated based on S-MAC is attached to ensure data integrity and tamper-proof.
[0109] Step S308: In the transaction result display scenario, after completing the transaction, the SE generates a transaction digest (including transaction amount, balance, transaction time, transaction type, etc.), calculates an AES-CMAC signature on the transaction digest using S-MAC, encapsulates the signed transaction digest in TLV format, encrypts it, attaches a checksum, and sends it to the MCU via a secure channel. Upon receiving the data, the MCU first verifies the AES-CMAC checksum to confirm data integrity, then uses S-ENC to decrypt and obtain the plaintext of the transaction digest, and finally verifies the signature of the transaction digest to confirm the trustworthiness of the data source. After successful verification, the MCU partially refreshes the transaction digest content onto the display screen.
[0110] Step S309: In the management command issuance scenario, the cloud management platform generates management commands (such as application lock / unlock, parameter configuration update, etc.), digitally signs the management commands using the cloud private key, and issues them to the MCU via BLE through the application terminal. After verifying the cloud signature, the MCU encapsulates the management commands in TLV format, encrypts them, attaches a verification code, and sends them to the SE through a secure channel. After verifying the verification code and signature, the SE executes the management commands and returns the execution result to the MCU through a secure channel.
[0111] Through the aforementioned two-way challenge-response authentication mechanism based on a static key set, the MCU and SE do not need to perform certificate chain verification and public key calculations during the establishment of a secure channel, significantly reducing computational overhead and storage requirements, making it suitable for resource-constrained embedded environments. Simultaneously, two-way token verification (Secure Element Encryption Token and Host Encryption Token) ensures the legitimacy and session freshness of both communicating parties, preventing man-in-the-middle and replay attacks. The dynamic derivation mechanism of session keys ensures that each session uses an independent encryption key, so even if a session key is leaked, it does not affect the security of other sessions.
[0112] Example 4: Payment Direction and Result Display
[0113] like Figure 4 As shown, this embodiment provides an electronic badge terminal for real-time display of payment process and transaction results in the payment direction.
[0114] Step S401: The user performs a preset action to trigger the payment window. By default, the digital currency hard wallet application on the electronic badge terminal is disabled and cannot be activated by an external card reader. When the user needs to make a payment, they perform a preset action (such as double-clicking the badge surface, long-pressing the side button, or using a specific gesture to flip it). The display control unit (MCU) detects this preset action and enables the payment window. The payment window is a time-limited function, such as 30 or 60 seconds, after which it automatically closes.
[0115] Step S402: The MCU notifies the security unit to enable the payment function. The MCU sends an enable request for the payment function to the security unit (SE) via a secure channel. This request is encapsulated in TLV format and transmitted encrypted via the SCP03 secure channel. After receiving the enable request, the SE switches the digital currency hard wallet application from a disabled state to a responsive state. In the responsive state, the SE can respond to transaction requests from the NFC front-end chip.
[0116] Step S403: The electronic badge is brought close to the acceptance terminal for NFC communication. The user brings the NFC antenna area of the electronic badge terminal close to the acceptance terminal (such as a POS machine, cash register, etc.). The NFC front-end chip receives transaction information (such as transaction amount, merchant information, transaction random number, etc.) from the acceptance terminal through the NFC antenna. The NFC front-end chip sends the transaction information directly to the SE, without going through the MCU, ensuring that the payment message is not exposed to the display field.
[0117] Step S404: SE executes transaction processing. The digital currency hardware wallet application within the SE executes transaction processing based on the received transaction information. In a dual offline scenario, the SE uses its locally stored digital currency hardware wallet for offline deductions, updating the local balance and transaction logs. In an online scenario, the SE interacts with the acceptance terminal via NFC, connecting to the digital currency payment operator's system through the acceptance terminal to complete the online transaction. During transaction processing, the SE generates a transaction summary, including information such as transaction amount, post-deduction balance, transaction time, transaction type, and transaction serial number.
[0118] Step S405: The SE generates a transaction digest and signs it with the session key. The SE uses the session key (S-MAC) of the current secure channel to calculate an AES-CMAC signature on the transaction digest, ensuring the integrity and unforgeability of the transaction digest. The signed transaction digest is encapsulated in TLV format, encrypted with S-ENC, and an AES-CMAC checksum is appended before being sent to the MCU through the secure channel.
[0119] Step S406: The MCU verifies the signature and displays the transaction result. After receiving the encrypted data, the MCU first verifies the AES-CMAC checksum to confirm data integrity, then uses S-ENC to decrypt and obtain the plaintext transaction digest, and finally verifies the signature of the transaction digest to confirm the data source is trustworthy. After successful verification, the MCU performs a partial refresh on the display screen to show the transaction result, including the deduction amount, balance, transaction time, and transaction status (success / failure). The partial refresh only updates the content of the transaction result area on the screen, without refreshing the entire screen. The refresh time is approximately 0.5 to 1 second, and the power consumption is much lower than that of a full-screen refresh.
[0120] Step S407: Payment window closed and hard wallet application disabled. Upon payment window timeout or transaction completion, the MCU notifies the SE that payment is complete. The SE then automatically switches the digital currency hard wallet application back to a disabled state, restoring it to an unresponsive state to prevent unauthorized NFC scanning and fraudulent transactions.
[0121] Step S408: Transaction Transaction Synchronization. After the electronic badge terminal connects to the application terminal, the MCU synchronizes the locally stored transaction transaction data to the application terminal via BLE. The application terminal then uploads the transaction transaction data to the cloud management platform for persistent storage and data analysis. After synchronization is complete, the MCU can clear the locally synchronized transaction transaction data to free up storage space.
[0122] Through the above process, users only need to double-click the badge to enable the payment window and then hold it close to the payment terminal to complete the payment. The transaction result will be immediately displayed on the badge screen after payment, without needing to open a mobile app to check. Even in offline payment scenarios, users can instantly confirm the deducted amount and balance, eliminating the time lag between payment completion and result feedback.
[0123] Example 5: Generation and Display of Payment Code for Recipient Direction
[0124] like Figure 5 As shown, this embodiment provides a process for generating and displaying a payment code in the payment direction of an electronic badge terminal.
[0125] Step S501: The user initiates a payment code request on the application terminal. The user opens the application terminal, selects the "Payment Code" function, enters or confirms the payment amount (or selects a general payment code without specifying an amount), and clicks the "Generate Payment Code" button. In response to the user's action, the application terminal sends a request to the cloud management platform to generate a payment code. The request includes the device identifier of the electronic badge terminal, the user's identity information, and the payment amount (if any).
[0126] Step S502: The cloud management platform verifies and issues a payment code token. Upon receiving the payment code request, the cloud management platform verifies the device status of the electronic badge terminal (e.g., whether the device is online, activated, or reported lost) and the user identity of the application terminal (e.g., whether the user is real-name authenticated and has payment collection permissions). After successful verification, the cloud management platform generates a time-limited payment code token. This token contains the payee's account information, the payment amount (if any), the validity period (e.g., 5 minutes), and a random number of anti-replay parameters. The platform then digitally signs the token using its cloud private key. The cloud management platform returns the signed payment code token to the application terminal.
[0127] Step S503: The application terminal sends the payment code token to the electronic badge. After receiving the payment code token, the application terminal sends it to the electronic badge terminal via BLE communication. During the sending process, the BLE link uses the encryption mechanism built into the Bluetooth protocol to protect the data transmission security.
[0128] Step S504: Electronic Badge Verifies Token and Renders Payment Code. After receiving the payment code token via Bluetooth, the display control unit (MCU) of the electronic badge terminal verifies the token's signature and validity. Specifically, the MCU uses a pre-set cloud public key to verify the token signature, confirming the token's source is trustworthy and has not been tampered with; it also checks the token's validity period to confirm it has not expired. Upon successful verification, the MCU generates a payment code image (such as a digital RMB payment code or a combined payment code's QR code image) based on the token content and refreshes the display screen to show the payment code.
[0129] Step S505: Automatic clearing of the payment code upon expiration or completion of payment. After the payment code token expires (e.g., after 5 minutes) or the MCU receives a payment completion message (e.g., the application terminal notifies that payment has been received), the MCU automatically refreshes the display to clear the payment code and restores the default display content (e.g., IP image, time, etc.). This automatic clearing mechanism prevents expired payment codes from being accidentally scanned and restores the badge's decorative display function.
[0130] By controlling the validity period of the payment code token and verifying its signature, the system ensures that the payment code cannot be tampered with or replayed. Simultaneously, the payment code is displayed on the screen, eliminating the need for the phone screen to be constantly on. Users can place the badge on their desktop for payment recipients to scan, making it convenient to use. For payment scenarios such as comic convention vendors, wearing the badge allows vendors to simultaneously display their personal brand image and payment code, serving both decorative and payment collection functions.
[0131] Example 6: NFC Power Supply Emergency Mode
[0132] This embodiment provides an NFC-powered emergency mode for the power management unit of the electronic badge terminal.
[0133] The power management unit of the electronic badge terminal includes a main battery, a charging management chip, a low-dropout linear regulator (LDO), and an NFC power extraction circuit. The main battery is typically a lithium polymer battery with a capacity of 150 to 300 mAh, providing power for normal device operation. The power management unit continuously monitors the main battery voltage. When the main battery voltage falls below a set voltage threshold (e.g., 3.3V, corresponding to approximately 5% remaining charge), the power management unit enters an NFC power extraction emergency mode.
[0134] In NFC power-up emergency mode, the NFC front-end chip harvests energy from the radio frequency field of an external reader (such as a payment terminal). Specifically, when the electronic badge terminal is brought close to the payment terminal, the NFC antenna senses the alternating magnetic field of the payment terminal's radio frequency field, generating an induced AC voltage. This induced AC voltage is converted into a DC voltage by a rectifier circuit (such as a bridge rectifier), and then regulated by a voltage regulator circuit (such as an LDO or DC-DC converter) to the operating voltage (such as 3.0V or 1.8V) required by the SE, display, and MCU.
[0135] The collected energy is allocated to the security unit, display screen, and display control unit according to a set priority. The priority is set as follows: the security unit has the highest priority, followed by the display screen, and then the display control unit has the lowest priority. The specific allocation strategy is as follows: First, ensure the energy supply to the security unit to ensure that the SE can complete transaction processing (including transaction message parsing, key calculation, transaction digest generation, etc.); second, only drive the display screen to perform a minimal partial refresh when there is sufficient collected energy; otherwise, only the security unit completes the transaction to reduce power consumption; finally, only when there is sufficient energy will the display control unit be powered, and the MCU is responsible for receiving the transaction digest sent by the SE and driving the display screen to display it.
[0136] Because the NFC radio frequency field energy is limited (typically tens of milliwatts), in the NFC power emergency mode, all modules of the system operate at the lowest power consumption. The SE operates at the lowest clock frequency, performing only necessary transaction processing functions; the display uses a partial refresh method, updating only the pixels in the transaction result area without refreshing the entire screen, reducing refresh power consumption to less than one-tenth of that of a full-screen refresh; the MCU enters sleep mode during non-data processing periods and is woken up by an interrupt to perform data processing.
[0137] With its NFC-powered emergency mode, even if the main battery is completely depleted, the electronic badge terminal can still use radio frequency energy to complete emergency payments and display transaction results when brought close to the payment terminal. This feature is especially important in scenarios where users forget to charge their devices or are away for extended periods, ensuring payment availability even in extreme situations.
[0138] Example 7: Low-power NFC listening state machine
[0139] This embodiment provides a low-power tri-state state machine management mechanism for the NFC front-end chip of the electronic badge terminal.
[0140] The NFC front-end chip employs a three-state machine for management: sleep mode, listening mode, and active mode. State transitions between these three modes are triggered by a timer, radio frequency field detection circuitry, and transaction status, enabling the NFC module to achieve extremely low power standby during non-transaction periods.
[0141] Sleep mode is the default standby state for the NFC front-end chip. In sleep mode, the NFC front-end chip and NFC antenna are turned off, the RF front-end circuitry is inactive, and only an ultra-low-power timer (such as an RTC) runs. The timer periodically wakes the NFC front-end chip at set intervals (such as every 500 milliseconds or 1 second), causing it to enter listen mode from sleep mode. The NFC module consumes extremely low power in sleep mode, typically in the microamplitude range.
[0142] Listen Mode is a brief operating state of the NFC front-end chip after it is woken up by a timer. In Listen Mode, the NFC antenna passively detects external radio frequency fields; that is, the NFC front-end chip does not actively emit radio frequency signals, but only passively senses the radio frequency field of the external card reader. The duration of Listen Mode is very short (e.g., 5 to 10 milliseconds). If a radio frequency field is detected within the listening window, the NFC front-end chip enters active mode; if no radio frequency field is detected, it returns to sleep mode, waiting for the next timer wake-up. The power consumption of the NFC module in Listen Mode is in the milliampere range, but due to its extremely short duration, it has a minimal impact on overall standby power consumption.
[0143] Active Mode is the full-function operating state of the NFC front-end chip after detecting a radio frequency field. In Active Mode, the NFC front-end chip establishes a complete ISO 14443 communication link with the external receiving terminal to send and receive transaction messages. The SE interacts with the receiving terminal through the NFC front-end chip to complete the transaction processing. After the transaction is completed, or after a timeout period of no operation (e.g., no transaction message exchange within 5 seconds), the NFC front-end chip returns to sleep mode. The NFC module consumes more power (tens of milliamps) in Active Mode, but only operates briefly during the transaction period.
[0144] Through tri-state machine management, the NFC module remains in sleep mode for most of the non-transaction period, passively detecting radio frequency fields only during brief periodic listening windows, significantly reducing standby power consumption. Compared to the continuous full-power listening scheme of the NFC module, the tri-state machine in this embodiment can reduce the standby power consumption of the NFC module by more than an order of magnitude. Combined with the zero-power retention characteristic of the display, this allows small badges to achieve standby time of several weeks to several months with limited battery capacity (e.g., 200mAh).
[0145] Example 8: Application Terminal and Cloud Management Platform
[0146] This embodiment provides the functional modules and security update mechanism for the application terminal and cloud management platform.
[0147] The application terminal is deployed on the user's smartphone (supporting iOS and Android platforms) and serves as the remote operation entry point for the electronic badge terminal. The application terminal's functional modules include: a device management module (device registration, binding, unbinding, and status query), a payment code module (payment code request initiation, payment code token reception and distribution), a transaction log module (transaction log synchronization, viewing, and export), a personalized content module (IP image push, animation settings, and screensaver settings), a firmware update module (firmware OTA package reception and distribution), and a settings module (payment window duration settings, preset action settings, security settings, etc.).
[0148] The application terminal communicates with the electronic badge terminal via BLE, and the communication link uses the encryption mechanisms built into the Bluetooth protocol (such as LE Secure Connections) to protect data transmission security. The application terminal also communicates with the cloud management platform via HTTPS, and all API requests are encrypted with TLS and authenticated with tokens.
[0149] The cloud management platform is the core management backend of the system, deployed on a cloud server and employing a microservice architecture. The functional modules of the cloud management platform include: a device lifecycle management module (device registration, activation, status monitoring, loss reporting, and deregistration); a payment code token issuance module (verifying device status and user identity, generating and signing time-limited payment code tokens); a firmware OTA distribution module (firmware version management, firmware package signing, canary rollout, and full rollout); a user account management module (user registration, real-name authentication, and permission management); a transaction data module (transaction data reception, storage, statistics, and analysis); and a TSM integration module (integrating with the TSM platform of digital currency payment operators to forward payment application card issuance and update requests).
[0150] The security mechanism for firmware OTA updates is as follows: When releasing a new firmware version, the cloud management platform digitally signs the firmware package using a cloud private key. Upon receiving the firmware OTA package, the application terminal first verifies the signature to confirm the firmware's trustworthy origin and integrity, and then distributes the firmware package to the electronic badge terminal via BLE. After receiving the firmware package, the MCU of the electronic badge terminal verifies the cloud signature again. If the verification is successful, the firmware upgrade is executed. Through dual signature verification (application terminal verification + electronic badge terminal verification), it is ensured that the firmware OTA package has not been tampered with during transmission, and the firmware's origin is trustworthy.
[0151] The security update mechanism for digital currency hard wallet applications is as follows: Card issuance, updates, and key rotation operations for digital currency hard wallet applications are completed through the Trusted Service Management (TSM) channel of the digital currency payment operator's system. The TSM channel is a secure communication channel between the digital currency payment operator's system and the SE (Security Provider), using a dedicated digital currency network for transmission and end-to-end encryption with the SE's root key. The cloud management platform forwards payment application management requests to the digital currency payment operator's system through the TSM interface module. The digital currency payment operator's system then communicates directly with the SE via the TSM channel to complete over-the-air card issuance and updates for the payment application. Throughout this process, the payment application's keys and sensitive data are transmitted only between the digital currency payment operator's system and the SE, without passing through the cloud management platform or the application terminal, ensuring the security of payment application updates.
[0152] The system employs a separate design, where a cloud-based management platform handles firmware OTA distribution (with signature verification) and the TSM channel of the digital currency payment operator's system handles payment application updates. Firmware updates and payment application updates each utilize independent secure channels, ensuring they do not interfere with each other. Firmware updates ensure device functionality iteration and vulnerability patching, while the TSM channel ensures secure over-the-air card issuance and lifecycle management for the payment application. This separation avoids single points of failure and security coupling, improving the overall maintainability and security of the system.
[0153] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.
Claims
1. An electronic badge, characterized in that, include: Display components and payment security components; the display components include a display screen, a display main control unit, and a Bluetooth module; the payment security components include a security unit, an NFC front-end chip, and an NFC antenna, the security unit internally loads a digital currency hard wallet application, and the security unit is directly connected to the NFC front-end chip; The display control unit and the security unit communicate via a secure channel. In the payment process, the display control unit receives the payment code token from the application terminal through the Bluetooth module, and renders the payment code on the display screen according to the payment code token, so that external payment devices can scan the code to pay. During the payment process, after the electronic badge is brought close to the acceptance terminal, the NFC front-end chip receives payment information from the acceptance terminal through the NFC antenna and sends the payment information directly into the security unit. The security unit completes offline or online transactions using the digital currency hardware wallet application and sends the transaction summary to the display control unit through the security channel. The display control unit then displays the transaction results on the display screen based on the transaction summary.
2. The electronic badge according to claim 1, characterized in that, After the display control unit detects that the user has performed a set action, it enables the payment window and notifies the security unit to start the payment function, so that the security unit switches the digital currency hard wallet application from a disabled state to a responsive state; after the payment window times out or the transaction is completed, the display control unit notifies the security unit that the payment is completed, so that the security unit restores the digital currency hard wallet application to a disabled state.
3. The electronic badge according to claim 1, characterized in that, The secure channel unit uses an I2C or SPI serial interface superimposed with the SCP03 secure channel protocol. The SCP03 secure channel protocol establishes a secure channel through bidirectional authentication and session key derivation. Subsequent communication through the established secure channel uses AES-128-CBC encryption and AES-CMAC integrity verification.
4. The electronic badge according to claim 3, characterized in that, The secure channel allows the transmission of two types of data: signed transaction summaries from the secure unit to the display control unit; and cloud-signed management instructions from the display control unit to the secure unit.
5. The electronic badge according to any one of claims 1-4, characterized in that, The secure channel is established as follows: after the main control unit initializes the session context and security level and generates host challenge information, it sends an initialization update command carrying the host challenge information to the security unit; The security unit extracts the host challenge information from the initialization update instruction and generates security unit challenge information; The security unit also calculates a security unit encryption token based on the host challenge information and the security unit challenge information using a pre-shared static key set, and returns a response message containing the security unit challenge information and the security unit encryption token to the display control unit. The display control unit extracts the security unit challenge information and the security unit encryption token from the response message, and verifies the security unit encryption token based on a pre-shared static key set; After successful verification, the display control unit also uses the static key set to calculate the host encryption token based on the host challenge information and the security unit challenge information, and returns the host encryption token to the security unit. The security unit uses the static key set to verify the host encryption token; After both the host encryption token and the security unit encryption token are verified, the display control unit and the security unit derive a session encryption key, an integrity verification key, and a response integrity verification key for the current session based on the host challenge information, the security unit challenge information, and the static key set, respectively.
6. The electronic badge according to any one of claims 1-4, characterized in that, After the secure channel is established, all transaction summaries and management instructions are encapsulated in TLV format, encrypted using the AES-128-CBC encryption algorithm and the session encryption key, and transmitted with an AES-CMAC checksum generated based on the integrity verification password.
7. The electronic badge according to any one of claims 1-4, characterized in that, Also includes: The power management unit includes an NFC power emergency mode. In the NFC power emergency mode, when the main battery voltage is lower than a set voltage threshold, the NFC front-end chip collects energy from the radio frequency field of an external card reader, and after rectification and voltage regulation, distributes it to the security unit, the display screen, and the display main control unit according to a set priority. The set priority is that the security unit is the highest, the display screen is the second highest, and the display main control unit is the lowest, and the display screen is in a partial refresh state.
8. An electronic badge payment system, characterized in that, include: The system comprises an electronic badge, an application terminal, a cloud management platform, and a digital currency payment operation institution system; wherein the electronic badge terminal is as described in any one of claims 1-7; the application terminal uses Bluetooth communication to remotely operate the electronic badge; the cloud management platform is responsible for device lifecycle management, issuance of payment code tokens, and firmware OTA distribution; the firmware OTA package received by the electronic badge is signed and verified by the cloud management platform; and the digital currency hard wallet application of the secure channel is updated through the trusted service management channel of the digital currency payment operation institution system.
9. A payment method, characterized in that, The method is performed by the electronic badge as described in claims 1-7; comprising: After detecting a preset action performed by the user on the electronic badge, the display control unit enables the payment window and sends a request to the security unit to enable the payment function. Upon receiving the activation request, the security unit switches the digital currency hard wallet application from a disabled state to a responsive state. After the electronic badge is placed close to the acceptance terminal, the NFC front-end chip receives transaction information from the acceptance terminal through the NFC antenna and sends the transaction information directly to the digital currency hard wallet application in the secure unit for transaction. After the transaction is completed, the security unit generates a transaction digest and signs it with the session key within the security unit; The signed transaction summary is sent to the main control unit via a secure channel; After verifying the signature, the main control unit partially refreshes the display screen to show the transaction result. The security unit automatically switches back to the disabled state after the payment window times out or the transaction is completed. After connecting to the application terminal, the transaction log of the main control unit is displayed.
10. A payment method, characterized in that, The method is performed by the electronic badge payment system of claim 9; comprising: In response to the user's action, the application terminal initiates a request to generate a payment code; After receiving the payment code request, the cloud management platform verifies the device status of the electronic badge and the user identity of the application terminal, generates a time-limited payment code token, and returns it to the application terminal. After receiving the payment code token, the application terminal sends the payment code token to the electronic badge via Bluetooth communication; After receiving the payment code token via Bluetooth, the main control unit of the electronic badge verifies the signature and validity of the payment code token, renders the payment code, and refreshes the display screen to display the payment code. After the payment code token expires or a payment completion message is received, the main control unit automatically refreshes the display screen to clear the payment code.
