Service Identifier Resolution for Hardware-Independent dSDN Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network solutions are inflexible due to proprietary hardware and software, limiting network operators' ability to add new features or capabilities, leading to time-consuming and resource-intensive standardization processes.

Innovation Solution

A Distributed Software Defined Network (dSDN) architecture that enables secure and flexible programmability across networks, allowing for the deployment of distributed applications through a virtual fabric, with lifecycle management and authentication, using a programmable network device and cloud device powered by a sandboxing operating system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If proprietary hardware and software are used in existing network solutions, then network infrastructure can be provided by vendors, but network operators cannot add new customized features or capabilities

Engineering Contradiction:
Improveability to add new featuresVSAvoidproprietary hardware architecture
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 represents a modular unit of functionality that can be added, removed, or updated without affecting the entire system, enabling flexible feature addition while maintaining system stability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The network device is designed to host multiple different network applications through containerization, making it capable of performing various network functions. The same hardware platform can support different applications (e.g., firewall, routing, load balancing) by loading appropriate container images, eliminating the need for proprietary hardware for each specific function.

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

2Adaptability or versatility

If new features are added through vendor requests or standardization processes in existing networks, then network capabilities can be expanded, but the process becomes time consuming and resource intensive

Engineering Contradiction:
Improvenetwork capability expansionVSAvoidtime for feature deployment
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

Network applications are pre-packaged into container images with all necessary dependencies and configurations included. This allows applications to be deployed quickly to network devices without requiring complex installation processes or vendor coordination, significantly reducing the time needed to add new network capabilities.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of developing and installing new software on proprietary hardware, the system uses container images that can be copied and deployed across multiple network devices. This copying mechanism enables rapid replication of network capabilities across the infrastructure without requiring custom installation procedures for each device.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If distributed applications are deployed through virtual fabric in dSDN, then flexible programmability is achieved, but system complexity increases

Engineering Contradiction:
ImproveprogrammabilityVSAvoidvirtual fabric architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system introduces an application management portal as an intermediary that simplifies the deployment and management of containerized network applications. The portal handles the complexity of virtual fabric configuration, container image distribution, and application lifecycle management, allowing users to achieve flexible programmability without directly managing the underlying system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

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

AI summary

Systems and methods are disclosed for enabling service-based communication among distributed application components in a software-defined network. A centralized application manager registers metadata for application instances, each associated with a common service identifier, and maintains an up-to-date mapping of these identifiers to network addresses across execution environments. When an application component initiates a request to communicate with a service by referencing its service identifier, a name resolution component dynamically resolves the identifier to an active network address using real-time deployment state. Communication is established via a virtual messaging fabric, facilitating reliable service discovery and inter-component messaging. The system supports load-balanced address selection, enforcement of security policy constraints, and synchronization across multiple network zones through a shared service registry. Application instances may include fxDeviceApp and fxCloudApp components executing on network devices and cloud platforms, respectively. These capabilities provide scalable, policy-driven, and secure service-level interaction within distributed application environments.