Automated Service Dependency Mapping for Network Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing the interdependency of software services and support software in large, geographically distributed networks is challenging due to the organic growth and constant changes in computing systems, making it difficult for administrators to track and maintain proper connections and configurations.

Innovation Solution

A services tool is configured to detect, monitor, and manage software providing services and support software, automatically identifying and linking necessary components based on defined rules, thereby reducing the administrative burden and ensuring proper connectivity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If administrators manually track and maintain computing systems in a large network, then they can identify and fix problems, but the complexity and time required increase significantly as the network grows

Engineering Contradiction:
Improvesystem maintenance reliabilityVSAvoidnetwork management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system enables self-service through automated service dependency mapping. The service dependency graph automatically discovers and tracks relationships between services without requiring manual administrator intervention. The system self-updates the dependency graph as services are added, removed, or modified, eliminating the need for administrators to manually track service interdependencies across the growing network.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The service dependency graph acts as an intermediary between services and administrators. Instead of administrators directly tracking complex service relationships, the dependency graph mediates by automatically discovering, storing, and presenting service dependencies. This intermediary layer simplifies the management interface while maintaining comprehensive tracking of service relationships.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If administrators manually configure service connections, then proper connectivity can be ensured, but the time and effort required increase significantly

Engineering Contradiction:
Improveservice connectivity reliabilityVSAvoidconfiguration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by automatically discovering and mapping service dependencies before administrators need to configure connections. The service dependency graph proactively identifies required service relationships and pre-configures necessary connections, eliminating the need for time-consuming manual configuration efforts while ensuring proper service connectivity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback through continuous monitoring and automatic updating of the service dependency graph. As services are added, removed, or modified, the system automatically detects these changes and updates the dependency relationships accordingly. This feedback mechanism ensures service connectivity is maintained without requiring manual reconfiguration, saving administrators significant time while preserving reliable connections.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If the network grows organically with frequent changes, then the network remains adaptable, but tracking and maintaining service interdependencies becomes increasingly difficult

Engineering Contradiction:
Improvenetwork adaptabilityVSAvoidservice tracking ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The service dependency graph is dynamic and automatically adapts to network changes. As services are added, removed, or modified in the growing network, the system continuously discovers and updates dependency relationships without requiring manual intervention. This dynamic approach maintains ease of operation by automatically handling service tracking despite frequent network changes and growth.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system enables self-service through automated service dependency mapping. The service dependency graph automatically discovers and tracks relationships between services without requiring manual administrator intervention. The system self-updates the dependency graph as services are added, removed, or modified, eliminating the need for administrators to manually track service interdependencies across the growing network.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9280399B2Detecting, monitoring, and configuring services in a netwowk
Publication Date: 2016.03.08 RED HAT INC
  • US9280399B2 patent drawing
  • US9280399B2 patent drawing
  • US9280399B2 patent drawing

AI summary

A services tool can detect, monitor, and manage software providing services in and for the network. The services tool can identify different types of software that provides services for the network (“services software”) and types of software that provide support (“support software”) to the services software. The services tool can determine configuration data for both the services software and the support software. The services tool can automatically identify when particular services software needs to be linked to particular support software. The services tool can configure the services software and/or support software to link the two according to the rules.