Token-Based Secure Data Sharing Between Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Applications face challenges in securely sharing confidential data over untrusted or insecure communications channels, as existing technologies lack robust security measures to prevent data interception or unauthorized access.

Innovation Solution

The solution involves a first application obtaining a token associated with authorized confidential information, which is then provided to a second application. This token is used to securely share the confidential information across an insecure communications channel, ensuring that only authorized parties can access the data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If applications share data through shared memory space or shared files, then data sharing capability is improved, but security against unauthorized access deteriorates

Engineering Contradiction:
Improvedata sharing capabilityVSAvoidsecurity against unauthorized access
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a secure channel as an intermediary component that mediates all data sharing operations between applications. Instead of applications directly accessing shared memory or files, they communicate through the secure channel which enforces authentication and authorization protocols, thus maintaining security while enabling data sharing

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the data sharing process into distinct authenticated communication channels. Each channel is independently secured with its own authentication and authorization mechanisms, allowing multiple applications to share data securely without compromising the entire system's security

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If applications communicate over network channels, then remote data sharing is improved, but vulnerability to interception deteriorates

Engineering Contradiction:
Improveremote data sharing capabilityVSAvoidvulnerability to interception
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The secure channel acts as a trusted intermediary between communicating applications, establishing encrypted communication paths that prevent third-party interception. The intermediary verifies the identities of communicating parties and protects the confidentiality of transmitted data

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the security parameters of network communication by implementing encryption and authentication protocols. These parameter changes transform vulnerable network channels into secure communication paths that resist interception and unauthorized access

Inventive Principle:
Principle #35Parameter changes

3Speed

If applications use shared memory space, then communication speed is improved, but susceptibility to malicious access deteriorates

Engineering Contradiction:
Improvecommunication speedVSAvoidsusceptibility to malicious access
Core Design Contradiction:
SpeedVSObject-affected harmful factors

Solution Approach 1:

The secure channel intermediary maintains high communication speed by optimizing data transfer protocols while simultaneously providing security checks. The intermediary is designed to minimize overhead and maximize throughput while enforcing authentication and authorization

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250055691A1Secure sharing of data between applications
Publication Date: 2025.02.13 AMERICAN EXPRESS TRAVEL RELATED SERVICES CO INC
  • US20250055691A1 patent drawing
  • US20250055691A1 patent drawing
  • US20250055691A1 patent drawing

AI summary

Disclosed are various embodiments for securely sharing confidential data between applications. A deep link request can be received from a first computing device, the deep link request identifying a set of data to be shared and a deep link schema. A token that represents the set of data can then be created. Also, a deep link that complies with the deep link schema and includes the token can also be created. The deep link and the token can then be returned to the first computing device. Later, a data request containing the token can be received from a second computing device. The set of data associated with the token can then be return to the second computing device.