Dynamic Service Name Resolution for Hardware-Independent Network Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network solutions are built on proprietary hardware and software, limiting network operators' ability to add new and customized features, leading to time-consuming and resource-intensive standardization processes.

Innovation Solution

A method for hosting network applications on programmable devices and cloud devices with secure communication through a virtual fabric, using an application management portal for seamless upgrades and lifecycle management, powered by a sandboxing operating system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If proprietary hardware and software are used to build network solutions, then network infrastructure stability is maintained, but network operators lose the ability to add new and customized features

Engineering Contradiction:
Improveability to add new and customized featuresVSAvoidproprietary hardware and software dependency
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The network application is divided into multiple container images that can be independently deployed and managed. Each container image represents a modular unit that can be updated, scaled, or removed without affecting the entire network infrastructure, enabling flexible feature addition while maintaining system stability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The platform uses standardized container technology that can run multiple different network applications on the same hardware infrastructure. This universal approach allows network operators to deploy various customized features using the same underlying platform, eliminating the need for proprietary hardware for each specific function.

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

2Productivity

If standardization processes are pursued to add new features, then network compatibility is improved, but the process becomes time consuming and resource intensive

Engineering Contradiction:
Improvefeature deployment speedVSAvoidstandardization process duration
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

Network applications are pre-packaged into container images with all dependencies and configurations included. This preliminary preparation allows for rapid deployment without requiring time-consuming standardization processes during implementation, as the containers are self-contained and ready to run immediately upon deployment.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention uses container image copying and replication to rapidly deploy identical or modified applications across multiple network elements. Instead of going through lengthy standardization processes for each deployment, pre-validated container images can be copied and instantiated quickly, dramatically reducing deployment time while maintaining consistency.

Inventive Principle:
Principle #26Copying

3Reliability

If application upgrades are performed on network devices, then application functionality is improved, but operational interruption occurs

Engineering Contradiction:
Improvecontinuous operation during upgradesVSAvoidupgrade process simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system dynamically manages multiple container instances, allowing upgrades to be performed on individual containers while others continue to operate. The platform can dynamically load new container versions and transition traffic between old and new instances, enabling seamless upgrades without operational interruption.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The upgrade process is structured as a periodic, controlled sequence where containers are updated in stages rather than all at once. This allows the system to maintain operational continuity by keeping some containers running while others are being upgraded, and to rollback if issues arise, simplifying the upgrade process while ensuring reliability.

Inventive Principle:
Principle #19Periodic action

4Reliability

If secure communication is implemented between network applications, then data security is enhanced, but system complexity increases

Engineering Contradiction:
Improvesecure communicationVSAvoidvirtual fabric architecture
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The platform introduces a virtual fabric as an intermediary layer that handles secure communication between containerized applications. This intermediary manages encryption, authentication, and network policies centrally, so individual applications don't need to implement complex security logic themselves, enhancing security while keeping application-level complexity low.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20260059013A1Method for managing updates to a distributed network independent of hardware
Publication Date: 2026.02.26 EDGE NETWORKING SYST LLC
  • US20260059013A1 patent drawing
  • US20260059013A1 patent drawing
  • US20260059013A1 patent drawing

AI summary

Systems and methods are provided for dynamic name resolution in a distributed software-defined network. An fxDeviceApp registers service metadata with a centralized application manager that maintains authoritative deployment information. A name resolution service receives requests to resolve service names and identifies active instances of the requested services based on real-time deployment state. The name resolution service then returns corresponding network addresses, enabling service-to-service communication within and across network zones. The system supports localized caching, zone-specific resolution rules governed by policy managers, and dynamic updates in response to changes in application deployment. Resolution decisions may account for service health or load metrics, and service lookup requests may be handled using a standardized message format compatible with a virtual messaging fabric. These features enable reliable, scalable, and policy-aware service discovery for distributed applications deployed across heterogeneous execution environments.