Policy-Based Peer-to-Peer Connections with Relay Authorization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Client devices communicating directly are vulnerable to data exfiltration if one or both have been compromised, as existing systems lack effective methods to ensure secure peer-to-peer connections.

Innovation Solution

A policy-based trusted peer-to-peer connection system where client devices query a relay service, which in turn queries a mobile device management service to determine authorization based on applicable policies, ensuring secure communication by using public keys and potentially shared secret keys for encryption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If client devices establish direct peer-to-peer connections for data transfer, then communication efficiency and speed are improved, but security vulnerability increases due to potential device compromise

Engineering Contradiction:
Improvecommunication speedVSAvoidconnection security
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent introduces a relay service as an intermediary between client devices. This relay service acts as a trusted mediator that facilitates direct peer-to-peer connections while maintaining security oversight. The relay service receives connection requests, verifies device trust status through mobile device management services, and enables secure direct communication between authorized devices, thus resolving the contradiction between communication speed and security.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If direct peer-to-peer communication is allowed without verification, then ease of operation is improved, but data protection capability deteriorates due to potential data exfiltration from compromised devices

Engineering Contradiction:
Improveconnection establishment easeVSAvoiddata exfiltration risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent implements preliminary verification of device trust status before allowing direct peer-to-peer connections. The relay service queries mobile device management services to verify device authorization and policy compliance before establishing connections. This preliminary action ensures that only trusted devices can communicate directly, preventing data exfiltration from compromised devices while maintaining ease of operation for authorized users.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If comprehensive policy verification is performed through relay services and mobile device management services, then security reliability is improved, but system complexity increases due to multiple service interactions

Engineering Contradiction:
Improvesecurity reliabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent employs mobile device management services that perform multiple functions: device registration, trust status verification, policy enforcement, and authorization management. By making these management services multi-functional, the system achieves high security reliability without proportionally increasing complexity, as the same services handle multiple security-related tasks throughout the peer-to-peer connection process.

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

Data Source

PatentUS12461974B2Policy-based trusted peer-to-peer connections
Publication Date: 2025.11.04 OMNISSA LLC
  • US12461974B2 patent drawing
  • US12461974B2 patent drawing
  • US12461974B2 patent drawing

AI summary

Disclosed are various examples for implementations of policy-based trusted peer-to-peer connections. A computing device can receive a message from a first client device, the message specifying an identifier of a second client device. The computing device can then send a query to a computing device, wherein the query specifies the identifier of the second client device. The computing device can also determine that the first client device is authorized to communicate with the second client device based on a response to the query received from the second computing device. In some instances, the computing device can then send the public key of the second client device to the first client device.