Consumer Device Token Binding via Out-of-Band Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems struggle to securely bind a financial instrument to consumer devices like refrigerators or smart speakers, lacking trust relationships established at the time of manufacture, leading to challenges in validating the device's ownership by the financial instrument owner.
Innovation Solution
A system and method for binding a consumer device to a user's identity using an out-of-band challenge process, involving a token service provider and issuer with shared cryptographic keys, ensuring secure device authentication through layered encryption and signature validation to prevent man-in-the-middle attacks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a financial instrument is bound to a consumer device without pre-established trust relationship, then device versatility and ease of operation are improved, but security and reliability deteriorate due to potential fraud and unauthorized access
Solution Approach 1:
The system performs preliminary actions by establishing cryptographic key pairs and generating tokens before the actual financial transaction or device binding occurs. The token service provider pre-establishes trust relationships and security credentials, so that when a device needs to be bound to a financial instrument, the security framework is already in place, enabling both versatility and reliability
Solution Approach 2:
A token service provider acts as an intermediary between the consumer device and the financial instrument issuer. This mediator establishes and manages the trust relationship, using cryptographic tokens to bind devices to financial instruments without requiring pre-existing direct trust between the device and issuer, thus resolving the security-versatility contradiction
2Reliability
If separate identity binding is implemented for each device, then security and fraud prevention are improved, but device complexity and operational steps increase
Solution Approach 1:
The system creates cryptographic copies (tokens) of the financial instrument identity that can be bound to multiple devices. Instead of requiring complex unique binding procedures for each device, the token service provider generates token copies that represent the same financial instrument, simplifying the binding process while maintaining separate device identities and fraud prevention capabilities
Solution Approach 2:
The token service provider implements a universal binding mechanism that works across multiple device types and financial instruments through a common cryptographic framework. This multi-functional approach allows the same token-based binding process to securely associate diverse devices with various financial instruments, reducing overall system complexity
3Reliability
If cryptographic key sharing is used to establish trust between issuer and token service provider, then security is improved, but key management complexity and potential attack surfaces increase
Solution Approach 1:
The system extracts the key management complexity from the device and issuer relationship and places it in the token service provider. By taking out the cryptographic key sharing and management functions to a dedicated service provider, the patent reduces key management complexity for individual devices while maintaining strong security through centralized, professional key management at the token service provider level
Data Source
AI summary
Unknown devices may be bound to an identity using a four step process that involves trusted relationships only between known partner entities and a known user attribute. The identity may be an account, such as a personal account number (PAN). The PAN may be abstracted using a token for use with the device. The unknown device may first be enrolled at a service to establish a cryptographically verifiable identity. A binding request for the enrolled device may be sent to an issuer of the PAN resulting in the issuer generating a challenge. After a successful authentication of the challenge at the token service provider, the binding of the token to the device is complete.