Distributed Application Latency Control via Core Server Mediation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for ensuring low and stable latency in distributed applications are inefficient, lacking precision, security, and compatibility with encryption, particularly when multiple terminal devices execute various applications with varying latency requirements.

Innovation Solution

A method where an application frontend initiates an initialization request to a registration server, which selects an appropriate application backend instance and transmits its IP address, and a core server selects a quality service to apply a service quality to the communication connection, optimizing latency and security through a registration and quality booking database.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If methods based on APN, application ID or address are used to identify distributed applications, then service quality can be applied to communication connections, but implementation effort becomes very high and security is insufficient

Engineering Contradiction:
Improveservice quality applicationVSAvoidimplementation effort
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a core server as an intermediary component that receives initialization requests from application frontends, identifies the distributed applications, and applies appropriate service qualities. This mediator simplifies the identification process by centralizing it in a dedicated server rather than requiring complex client-side implementation using APN, application IDs, or addresses.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If methods based on APN, application ID or address are used to identify distributed applications, then service quality can be applied to communication connections, but security is not sufficient

Engineering Contradiction:
Improveservice quality applicationVSAvoidsecurity vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The core server acts as a secure intermediary that validates initialization requests and applies service qualities based on authorized identification. This centralized approach enhances security by controlling the identification and service quality assignment process in a single secure location, rather than relying on potentially vulnerable client-side methods.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If methods based on port numbers are used to identify distributed applications, then communication can be established, but port numbers vary during operation making identification unreliable

Engineering Contradiction:
Improvecommunication establishmentVSAvoidapplication identification precision
Core Design Contradiction:
Ease of operationVSMeasurement precision

Solution Approach 1:

The core server intermediary receives initialization requests that include communication parameters and uses these to identify the distributed application and apply appropriate service qualities. This approach avoids relying on port numbers alone by using the initialization request as a stable identification basis that remains consistent even when port numbers change during operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If a large plurality of terminal devices execute various distributed applications with different latency requirements, then network utilization is maximized, but precision in identifying applications requiring low and stable latency is insufficient

Engineering Contradiction:
Improvenetwork utilizationVSAvoidapplication identification precision
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The core server intermediary processes initialization requests from multiple terminal devices and applications, identifying which applications require low and stable latency based on the request information. This centralized identification mechanism provides the precision needed to differentiate between applications with different latency requirements while maintaining high network utilization through efficient resource allocation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11736591B2Method for operating a distributed application
Publication Date: 2023.08.22 DEUTSCHE TELEKOM AG
  • US11736591B2 patent drawing

AI summary

A method for operating a distributed application includes: transmitting, by an application frontend of the distributed application, upon a launch of the application frontend, an initialization request to a registration server via a communication network; selecting, by the registration server, upon receipt of the initialization request, an instance of an application backend of the distributed application and transmitting an IP address of the selected instance to the application frontend; transmitting, by the application frontend, upon receipt of the IP address, application data to the transmitted IP address via a connection provided by the communication network; selecting, by a core server of the communication network, upon transmission of the application data, a quality service for the distributed application; applying, by the communication network, a service quality determined by the selected quality service to the connection; and operating the distributed application with the applied service quality.