Address Translation Module for Overlapping IP Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network management tools are limited in handling overlapping IP addresses across multiple local networks and often require reliable data transport, which is not feasible over an Internet connection, constraining their ability to manage multiple customer networks and lack fault tolerance.

Innovation Solution

A system and method for translating native IP addresses into new IP addresses within XML messages, allowing event data to be forwarded across networks with overlapping addresses, and utilizing an unreliable link like the Internet, while also implementing load balancing and fault tolerance through a network management system with a management server and address translation module.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If network management tools are deployed remotely to manage multiple customer networks, then the ability to leverage management tools across multiple networks is improved, but reliable data transport between managed network and management tools becomes difficult to ensure

Engineering Contradiction:
Improveability to manage multiple customer networksVSAvoiddata transport reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary mechanism (address translation module) that sits between the managed network and the remote management tool. This intermediary translates IP addresses and protocols to enable communication over unreliable links like the Internet, while maintaining the functionality of the management tool. The intermediary handles the complexity of address translation and protocol conversion, allowing the management tool to operate remotely without requiring direct reliable connections to each managed device.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the parameter of IP address representation by translating native IP addresses into a standardized format (XML with new IP addresses). This parameter change allows the system to maintain compatibility across different networks while enabling communication over unreliable transport layers. The address translation module modifies the address parameter dynamically, converting local IP addresses into globally routable addresses that can traverse the Internet reliably.

Inventive Principle:
Principle #35Parameter changes

2Device complexity

If IP addresses are used directly from managed networks, then the system is simple to implement, but overlapping IP addresses across multiple networks cause conflicts and prevent proper management

Engineering Contradiction:
Improvesystem implementation simplicityVSAvoidcapability to handle overlapping IP addresses
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The address translation module serves as an intermediary that translates IP addresses from their native network-specific format into a unified standardized format. This intermediary layer absorbs the complexity of address translation and protocol conversion, allowing the rest of the system to remain simple while gaining the capability to handle overlapping IP addresses across multiple customer networks.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent adds a new dimension to IP address representation by introducing XML-based standardized addresses as an additional layer above the traditional IP address. Instead of working directly with raw IP addresses, the system translates them into XML messages that include the original IP information plus additional context (new IP address, device identifier). This dimensional expansion allows the system to represent the same network resource in multiple ways simultaneously, resolving the overlap problem.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Ease of operation

If a single management tool is used for all managed networks, then the system is easy to operate, but fault tolerance and load balancing capabilities are limited

Engineering Contradiction:
Improvesystem operation simplicityVSAvoidfault tolerance capability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the management function by allowing multiple management tools to coexist in the system, each capable of managing specific networks or functions. The load balancing module then segments the traffic distribution, directing event data to appropriate management tools based on current system conditions. This segmentation enables fault tolerance by allowing the system to switch between different management tools if one fails, while maintaining operational simplicity through automated load balancing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces dynamic load balancing that can adapt its behavior based on real-time conditions. The load balancing module dynamically determines which management tool should handle which event data based on factors like tool availability, performance, and network conditions. This dynamic adjustment provides fault tolerance by automatically redistributing work around failed components, while the system maintains ease of operation through automated decision-making without requiring manual intervention.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS7979521B2Method and system for relocating and using enterprise management tools in a service provider model
Publication Date: 2011.07.12 ORACLE AMERICAN INC
  • US7979521B2 patent drawing
  • US7979521B2 patent drawing
  • US7979521B2 patent drawing

AI summary

An embodiment of the invention provides a method for communicating event data in a network, including: receiving the event data in a first device, the event data including a native IP address associated with a source of the event data; translating a native protocol of the event data into XML, a resulting XML message including the event data and an identifier associated with the first device; transmitting the XML message from a first location to a second location; determining a new IP address based on the native IP address and the identifier; and including the new IP address in the XML message.