Persistent Client Connection Routing for Secure Resilient Messaging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing near field communication techniques, such as Bluetooth and Wi-Fi, are insecure and non-resilient, lacking stability and availability for reliable data communication between client devices.

Innovation Solution

A client connection service is used to facilitate secure and resilient persistent communication between devices by identifying and registering devices, assigning resource identifiers, and managing communication through a transport service and registry service to ensure stable and authenticated data exchange.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If near field communication techniques (Bluetooth, Wi-Fi) are used for data communication between client devices, then communication capability is provided, but security and connection stability are insufficient

Engineering Contradiction:
Improveconnection stabilityVSAvoidcommunication system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a server as an intermediary component that establishes and manages communication connections between client devices. The server acts as a mediator that handles connection establishment, message routing, and session management, thereby providing stable and secure communication without requiring direct peer-to-peer connections between clients. This resolves the contradiction by centralizing connection management functions to improve reliability while keeping client devices relatively simple.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If direct peer-to-peer communication is established between devices, then communication efficiency is improved, but security and resilience are reduced

Engineering Contradiction:
Improvecommunication availabilityVSAvoidconnection establishment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-establishing communication sessions and maintaining connection states on the server side before actual data exchange occurs. The server pre-configures routing information, authentication credentials, and connection parameters, so that when communication is needed, the connection is already prepared and can be activated immediately. This eliminates connection establishment delays while maintaining security through server-mediated connections.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If traditional communication protocols are used, then compatibility is maintained, but security vulnerabilities and lack of resilience persist

Engineering Contradiction:
Improvecommunication protocol flexibilityVSAvoidsecurity risks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies parameter changes by transforming traditional communication protocols into a server-mediated architecture with enhanced security parameters. The server implements authentication mechanisms, encryption, and session management that change the fundamental parameters of communication security. This allows the system to maintain protocol compatibility while introducing new security layers that address vulnerabilities in traditional peer-to-peer approaches.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP4118858B1Systems and methods for establishing highly secure & resilient persistent communication connections
Publication Date: 2025.12.17 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP4118858B1 patent drawingFigure 1A
  • EP4118858B1 patent drawingFigure 1B
  • EP4118858B1 patent drawingFigure 2

AI summary

Systems and methods for providing resilient persistent connections for communication are disclosed. Methods include identifying, at a first device, a second device registered with a client connection service; obtaining, from the client connection service, a first resource identifier for delivering request messages to the second device via the client connection service; identifying, based on the obtained first resource identifier, a first target resource for a first request message directed to the second device, wherein the first target resource specifies a first host included in the client connection service; sending, to the client connection service via the data communication network, the first request message to the first target resource for delivery to the second device by the client connection service; and receiving, from the client connection service via the data communication network, a first response message provided by the second device as a response to the first request message.