Gateway NMD Piggyback Addressing for IP Management Traffic

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of IP and MPLS networks makes it difficult and costly to configure and maintain reliable network management connections across multiple service providers and IP address spaces, especially in heterogeneous environments where traditional PVC-based solutions are impractical.

Innovation Solution

A network management system that uses a piggyback addressing scheme with a gateway NMD to route management traffic, encapsulating messages with customer IP addresses to traverse IP/MPLS networks efficiently, allowing reliable communication across multiple server providers and IP address spaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If PVC-based management overlay networks are configured in traditional Frame Relay or ATM networks, then reliable point-to-point management communication is achieved, but device complexity and configuration difficulty increase significantly in IP/MPLS mesh networks

Engineering Contradiction:
Improvemanagement communication reliabilityVSAvoidPVC configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a network address translator (NAT) device as an intermediary between management devices and the network management system. The NAT device translates management traffic between private IP addresses used within the enterprise network and public IP addresses used by the network management system, eliminating the need for complex PVC configurations in IP/MPLS mesh networks while maintaining reliable communication paths

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the addressing parameter from traditional PVC-based permanent virtual circuit identifiers to dynamic IP address translation. By using NAT to translate between private and public IP addresses, the system adapts to the mesh nature of IP/MPLS networks while maintaining reliable management communication without requiring complex circuit-based configurations

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If multiple service providers are used to serve an enterprise network, then network coverage and service options increase, but the cost and complexity of setting up management connections increases prohibitively

Engineering Contradiction:
Improvemulti-service-provider supportVSAvoidmanagement connection setup complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent makes the NAT device universal by enabling it to handle management traffic from multiple service providers through a single interface. The NAT device can translate addresses for management connections arriving from different service providers using different IP address spaces, providing multi-functionality that simplifies management across heterogeneous service provider environments

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

Solution Approach 2:

The NAT device serves as a universal intermediary between the enterprise network and multiple service providers. It abstracts the complexity of multi-provider IP address spaces by translating all management traffic to a unified private address space, allowing the network management system to communicate with management devices regardless of which service provider the traffic originates from

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If PVCs are provisioned to each network management device from the main service provider, then direct management access is achieved, but the cost becomes prohibitive when accessing competing service provider networks

Engineering Contradiction:
Improvedirect management accessVSAvoidmanagement connection cost
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The NAT device acts as a cost-effective intermediary that enables direct management access without requiring expensive PVCs to competing service providers. Management traffic from competing service providers is translated by the NAT device using existing IP routing infrastructure, eliminating the need for costly dedicated circuit provisions while maintaining direct access capability

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces expensive, permanent PVC connections with more economical IP-based routing and NAT translation. Instead of provisioning costly dedicated circuits to each management device through multiple service providers, the system uses dynamic IP address translation that leverages existing IP network infrastructure, significantly reducing management connection costs

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Data Source

PatentEP1848160B1Methods and apparatus for IP management traffic consolidation
Publication Date: 2012.11.14 FLUKE CORP
  • EP1848160B1 patent drawingFigure 1
  • EP1848160B1 patent drawingFigure 2
  • EP1848160B1 patent drawingFigure 3

AI summary

Consolidation of management traffic is performed in a network by employing a gateway network management device (NMD) to route management messages between a controller and NMDs located at sites in the network. Management addresses are assigned to components of a network management system, including the management controller and NMDs. The management addresses are distinct from customer addresses associated with equipment located at the sites. These customer addresses can serve as piggyback addresses for routing encapsulated management messages through the network. Management messages from the management controller contain the management address of the destination NMD and are first sent to the gateway NMD. The gateway NMD looks up the piggyback address corresponding to the destination management address and generates an encapsulated management message containing the management message and the piggyback address. Using the piggyback address, the encapsulated message is then routed through the network to the destination NMD.