Network Localization via Probe-Based Location Identifiers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network localization methods in SD-WANs rely on geolocation or IP addresses, which are often unavailable or inaccurate, making it difficult to determine the optimal network configuration for ensuring quality of service (QoS) across different locations.

Innovation Solution

A device generates location identifiers based on probe results from multiple entities in the network, allowing it to select and deploy configurations to other nodes based on their proximity, using a predictive routing engine to optimize application performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If geolocation or IP addresses are used to identify network endpoints, then network localization can be performed, but the accuracy and reliability of location identification deteriorates due to unavailability or misallocation of such information

Engineering Contradiction:
Improvelocation identification accuracyVSAvoidavailability of geolocation/IP information
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The patent introduces probe results as an intermediary mechanism to indirectly determine network location. Instead of directly using unreliable geolocation or IP data, the system sends probes to multiple entities and uses the responses as mediators to infer accurate location identifiers, resolving the contradiction between measurement precision and information availability

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the traditional mechanical/geolocation-based location identification system with a network-based probing system. Instead of relying on physical location data (geolocation) or network assignment data (IP addresses), the system substitutes a dynamic probing mechanism that actively queries network entities to derive location information, thereby improving both accuracy and reliability

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If network configurations are optimized for specific locations, then quality of service improves, but the complexity of managing multiple location-specific configurations increases

Engineering Contradiction:
Improvequality of serviceVSAvoidconfiguration management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent changes the fundamental parameter used for configuration selection from static geolocation/IP data to dynamic location identifiers derived from probe results. This parameter change enables the system to maintain location-specific optimizations while simplifying management, as the new parameter is automatically generated through probing rather than manually assigned

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system implements self-service by automatically generating location identifiers through probing and selecting appropriate configurations without manual intervention. Each endpoint autonomously performs probing to determine its location and retrieves the suitable configuration, eliminating the need for complex centralized management of location-specific settings

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20240007387A1Network localization based on probing results
Publication Date: 2024.01.04 CISCO TECHNOLOGY INC
  • US20240007387A1 patent drawing
  • US20240007387A1 patent drawing
  • US20240007387A1 patent drawing

AI summary

In one embodiment, a device obtains probe results generated by probing a plurality of entities in a network from a first node in the network. The device generates a location identifier for the first node that represents its location in the network, based on the probe results. The device selects a configuration associated with the first node for use by a second node in the network, based on a difference between the location identifier for the first node and a location identifier for the second node. The device causes the configuration to be deployed to the second node.