Secure Mobile Device Communication via Trusted Server

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional mobile card readers are often expensive, difficult to install, and do not significantly enhance the user experience, and existing secure communication methods between devices in mobile card processing systems are inefficient, particularly in environments like taxis where internet connectivity is not always reliable.

Innovation Solution

Establishing secure communication between mobile devices using a trusted server via a WiFi hotspot, allowing devices to communicate without relying on external networks, by authenticating with a server, generating and exchanging cryptographic keys, and using these keys to encrypt and decrypt transmissions, ensuring secure data exchange during transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If mobile card readers use WiFi or cellular technology to communicate with the credit card processor, then wireless communication capability is improved, but device cost and installation complexity increase

Engineering Contradiction:
Improvewireless communication capabilityVSAvoidinstallation complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a payment server as an intermediary that mediates communication between the mobile computing device and the credit card processor. The mobile device communicates transaction information to the payment server, which then communicates with the credit card processor, eliminating the need for complex direct wireless communication hardware in the mobile device.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The mobile computing device uses its existing wireless communication capabilities (WiFi, cellular) to autonomously communicate transaction information to the payment server without requiring specialized card reader hardware or complex installation procedures.

Inventive Principle:
Principle #25Self-service

2Ease of operation

If mobile card readers use WiFi or cellular technology, then wireless communication capability is improved, but system cost increases

Engineering Contradiction:
Improvewireless communication capabilityVSAvoidsystem cost
Core Design Contradiction:
Ease of operationVSEase of manufacture

Solution Approach 1:

The payment server performs multiple functions: receiving transaction information from mobile devices, processing payment requests, communicating with credit card processors, and enabling secure communications. This multi-functional approach eliminates the need for specialized expensive hardware.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system uses the mobile device's existing communication protocols and capabilities to replicate the functionality of traditional card readers, avoiding the need for expensive specialized hardware while achieving the same wireless payment processing capability.

Inventive Principle:
Principle #26Copying

3Reliability

If secure communication is established through a trusted server via WiFi hotspot without external network access, then communication reliability in isolated environments is improved, but communication complexity increases

Engineering Contradiction:
Improvecommunication reliability in isolated environmentsVSAvoidcommunication protocol complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The trusted server acts as an intermediary that establishes secure communication channels between mobile devices even when external networks are unavailable. The server manages the cryptographic key exchange and session establishment, simplifying the process for individual devices.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary authentication and key exchange with the trusted server before isolated transactions. The server pre-establishes trust relationships and cryptographic parameters, enabling secure peer-to-peer communication between devices without requiring complex real-time key management during transactions.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If cryptographic keys are generated and exchanged through a trusted server, then communication security is improved, but authentication process time increases

Engineering Contradiction:
Improvecommunication securityVSAvoidauthentication process time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The trusted server performs cryptographic key generation and exchange in advance during initial device registration and authentication. These pre-established cryptographic relationships enable rapid secure transactions without repeated key exchange procedures.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses cryptographic certificates and digital signatures that can be verified without time-consuming key exchange during transactions. The trusted server issues digital certificates that enable fast authentication by simple verification of digital signatures rather than complex real-time key management.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8874913B1Secure communications between devices using a trusted server
Publication Date: 2014.10.28 BLOCK INC
  • US8874913B1 patent drawing
  • US8874913B1 patent drawing
  • US8874913B1 patent drawing

AI summary

A method of establishing secure communication between a first mobile computing device and a second mobile computing device includes receiving a first request from the first mobile computing device to securely communicate with the second mobile computing device via a Wi Fi hot spot, verifying that the first mobile computing device is trusted, generating a public key and a private key based on a trusted certificate, sending the private key to the first mobile computing device via the Wi-Fi hot spot, receiving a second request from the second mobile computing device to securely communicate with the first mobile computing device, verifying that the second mobile computing device is trusted, and sending the public key to the second mobile computing device.