Machine Initialization Module for Network Device Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The automation of network device initialization is complex and inefficient, requiring manual intervention and dedicated DHCP servers, which are costly and resource-intensive in large-scale network deployments.

Innovation Solution

The implementation of a machine initialization module that uses a COBBLER-based approach to detect hardware, install operating systems, and configure network services, eliminating the need for dedicated DHCP servers by using a distributed file store and smart routing for efficient deployment and management of network services across multiple data centers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If dedicated DHCP servers are used for network device initialization, then network service deployment is reliable, but system complexity and cost increase

Engineering Contradiction:
Improvenetwork service deployment reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the DHCP server functionality from the traditional dedicated server architecture and integrates it into the existing storage system. The storage system's file sharing capabilities are repurposed to provide DHCP services, eliminating the need for separate dedicated DHCP servers while maintaining network initialization reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The storage system is designed to perform multiple functions: it serves as both a file sharing storage system and a DHCP server. This multi-functionality allows the same system to handle both data storage and network device initialization, reducing overall system complexity while maintaining reliability.

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

2Manufacturing precision

If manual intervention is required for network device initialization, then configuration precision is high, but productivity decreases

Engineering Contradiction:
Improveconfiguration precisionVSAvoidinitialization speed
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The system performs preliminary configuration by pre-defining network service templates and initialization parameters. When a new network device is deployed, the system automatically applies these pre-configured settings, ensuring configuration precision while eliminating the need for manual intervention during the initialization process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The network device initialization process is designed to be self-service, where the storage system automatically detects new devices, assigns network parameters, and configures services without requiring manual intervention. This automation maintains configuration precision through structured processes while dramatically improving initialization speed.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If distributed file store with smart routing is used, then resource utilization improves, but system complexity increases

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the file store and DHCP server functionalities into a single integrated system. The smart routing capability of the distributed file store is leveraged to route DHCP requests and responses efficiently, combining multiple functions into one system and improving resource utilization without proportionally increasing complexity.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11750451B2Batch manager for complex workflows
Publication Date: 2023.09.05 RAKUTEN SYMPHONY INC
  • US11750451B2 patent drawing
  • US11750451B2 patent drawing
  • US11750451B2 patent drawing

AI summary

A workflow may include function calls to functions executed with respect to instances of elements. Health checks of elements of the workflow may be performed with reference to topology such that health checks of elements are omitted where a health check is performed by a parent in the topology. Batch processing of stages of a workflow may be performed with commencement of a stage being initiated based on completion percentage and execution time of a previous stage. Tasks of each stage may be performed by a pool of workers that are reused with pool size being selected based on expected completion time of each stage.