System Design Support Method for Software-Network Consistency

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In large-scale IT systems, designing a network and configuring software are typically done separately, requiring users to re-design network requirements every time software configurations change, leading to inconsistencies and increased costs.

Innovation Solution

An information processing device and system design support method that convert software component communication requirements into network requirements, generating settings for both network and software components to maintain consistency without re-designing the network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If network and software configuration are designed separately, then design flexibility is improved, but consistency between network requirements and software communication requirements deteriorates

Engineering Contradiction:

Improvedesign flexibilityVSAvoidconsistency between network and software requirements

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system automatically feeds back software communication requirements to generate network configuration settings. When software components are deployed on virtual machines, the system extracts communication requirements from the software configuration and automatically generates corresponding network settings, creating a closed-loop feedback mechanism that maintains consistency without manual re-design.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary system (the information processing device) that translates software communication requirements into network configuration settings. This intermediary automatically converts high-level software communication needs into specific network parameters, bridging the gap between software and network design domains.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If network is re-designed every time software configuration changes, then consistency is improved, but design time and productivity deteriorate

Engineering Contradiction:

Improveconsistency between network and software requirementsVSAvoiddesign time

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary extraction of communication requirements from software configuration and pre-generates network settings before actual deployment. By preparing network configurations in advance based on software requirements, the system eliminates the need for reactive re-design when changes occur.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system enables self-service by automatically generating network configuration settings based on software communication requirements without requiring manual network re-design. The automated process serves itself by extracting requirements and generating corresponding network settings, eliminating repetitive manual work.

Inventive Principle:

Principle #25Self-service

3Reliability

If manual network re-design is performed frequently, then consistency is improved, but operational complexity and cost deteriorate

Engineering Contradiction:

Improveconsistency between network and software requirementsVSAvoidoperational complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent replaces the mechanical process of manual network design and configuration with an automated information processing system. Instead of manually analyzing software requirements and creating network settings, the system uses automated extraction and generation processes to substitute human operational complexity with computational processes.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS10171294B2Information processing device and system design support method

Publication Date: 2019.01.01 NEC CORP

AI summary

Consistency between a requirement for communication with respect to software in a system and a requirement for a network is maintained, without re-designing a network by the user. A requirement conversion unit (110) of a system design support device (100) generates a requirement for communication between computers based on a requirement for communication between software components included in a system, and based on identifiers of the computers in which the software components are deployed. The requirement conversion unit (110) generates a requirement for a network for connecting between the computers based on the requirement for communication between the computers. The setting generation unit (120) generates a setting relating to a network, a setting relating to communication between computers, and a setting relating to communication between software components based on the requirement for the network, the requirement for communication between the computers, and the requirement for communication between the software components.