Unidirectional NFC Communication for Secure Mobile Payments

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Unidirectional communication protocols, such as NFC P2P mode, are inadequate for secure and bidirectional transactions, limiting their use in secure payment systems.

Innovation Solution

Implementing a method that utilizes multiple unidirectional communication sessions with a pause to simulate bidirectional communication, allowing a mobile device to process responses and send encrypted payment credentials, thereby enabling secure transactions using existing unidirectional protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If unidirectional communication protocols (NFC P2P mode) are used for mobile payments, then device compatibility and simplicity are improved, but secure bidirectional challenge-response communication cannot be achieved

Engineering Contradiction:
Improvecompatibility with existing NFC protocolsVSAvoidsecurity of transaction
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent divides the communication process into multiple separate unidirectional sessions rather than attempting a single bidirectional session. The first session transmits challenge data from terminal to mobile device, and the second session transmits the response from mobile device to terminal. This segmentation allows the system to work within the constraints of unidirectional protocols while achieving the security requirements of bidirectional challenge-response communication.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The terminal performs preliminary actions by sending the challenge data in advance during the first communication session, before the mobile device needs to generate its response. This allows the mobile device sufficient time to process the challenge and generate the cryptographic response without requiring simultaneous bidirectional communication. The pause between sessions ensures the response is ready before the second session begins.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If bidirectional communication is implemented for secure transactions, then transaction security is improved, but protocol complexity and device requirements increase

Engineering Contradiction:
Improvesecurity of transactionVSAvoidcommunication protocol requirements
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Instead of attempting to implement true bidirectional communication which would require both devices to support it, the patent inverts the approach by using two sequential unidirectional sessions. The terminal initiates both sessions, effectively controlling the communication flow in a way that simulates bidirectional interaction while actually using only unidirectional capabilities. This inversion allows secure challenge-response communication without requiring the mobile device to support bidirectional protocols.

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

Solution Approach 2:

The patent introduces a pause period as an intermediary element between the two communication sessions. This pause acts as a mediator that allows the mobile device to process the challenge data and generate the response without requiring simultaneous two-way communication. The pause bridges the gap between receiving the challenge and sending the response, enabling secure authentication through unidirectional protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9524499B2Systems, methods, and computer program products providing electronic communication during transactions
Publication Date: 2016.12.20 PAYPAL INC
  • US9524499B2 patent drawing
  • US9524499B2 patent drawing
  • US9524499B2 patent drawing

AI summary

An electronic device includes one or more processors configured to execute the instructions to: during a first communication session, sending first information regarding a transaction to a user device that is participating in the first transaction, interrupting the first communication session, pausing for a time to allow the user device to process the first information and to generate second information in furtherance of the transaction, establishing a second communication session with the user device, receiving the second information from the user device during the second communication session, and further processing the transaction using the second information.