NFC Type 4 Tag Interface for Complex Card Protocols

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Smartphones restrict communication protocols with NFC-enabled payment cards to simple NFC data exchange format (NDEF), blocking complex applications and preventing interactions such as financial transactions.

Innovation Solution

Implementing a system where a smart phone communicates with an NFC chip using simple memory-read and memory-write commands, employing sequence numbers or nonces to simulate higher-level protocols by checking for changes in designated memory locations, allowing complex applications to function.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If NFC readers restrict communication to NDEF format, then device compatibility and simplicity are improved, but complex application functionality is blocked

Engineering Contradiction:
Improvecommunication simplicityVSAvoidapplication complexity
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent introduces an intermediary simulation layer that mediates between the simple NDEF communication interface and the complex application protocols. The terminal application simulates card reader behavior and the card applet simulates terminal behavior, creating a virtual communication channel that allows complex protocols to operate over the simple NDEF interface.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates virtual copies of the actual communication interfaces. The terminal application copies card reader functionality, and the card applet copies terminal functionality. These copies operate over the restricted NDEF interface while reproducing the behavior of full protocol support, enabling complex applications without requiring actual protocol capabilities.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If full communication protocol support is implemented, then complex applications can operate, but device compatibility and simplicity are reduced

Engineering Contradiction:
Improveprotocol supportVSAvoidcommunication implementation
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Instead of implementing full protocol support in the hardware/OS layer, the patent inverts the approach by implementing protocol simulation in the application layer. The terminal application and card applet exchange roles and simulate each other's behavior, allowing complex protocols to function through software simulation rather than hardware implementation.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The patent changes the operational parameters of the communication system by operating over NDEF format while simulating different protocol behaviors. The terminal application and card applet dynamically adjust their communication parameters to match the expected protocol behavior, enabling multiple protocol types over a single unified interface.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12488331B2Type 4 NFC tags as protocol interface
Publication Date: 2025.12.02 VISA INTERNATIONAL SERVICE ASSOCIATION
  • US12488331B2 patent drawing
  • US12488331B2 patent drawing
  • US12488331B2 patent drawing

AI summary

NFC terminal devices and corresponding integrated circuit cards (ICCs) use NFC Type 4 tags as a protocol interface for complex or encrypted communication protocols that are not natively supported by the NFC terminal devices. A smartphone acting as an NFC terminal may block applications and/or protocols other than NFC data exchange formatted (NDEF) messages. An ICC applet supporting an advanced function uses designated memory locations for the transfer of commands normally supported at an application level. Both the terminal side and the ICC applet may check the designated memory locations for updated data in the absence of protocol-level message controls.