Modular Network Service Construction Through Bundle-Based Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies struggle to flexibly construct network services that cater to diverse needs and requirements.

Innovation Solution

A computer system comprising a reception module, construction module, and monitoring management module to receive, construct, and manage network services based on bundle files containing functional unit groups and monitoring policies, enabling flexible network service construction.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If network services are constructed using existing technologies (Patent Literatures 1-3), then network services can be deployed with basic functionality, but the system cannot flexibly construct network services that satisfy diverse needs and requirements

Engineering Contradiction:
Improveflexibility of network service constructionVSAvoidcomplexity of service construction system
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments network services into functional units that can be independently defined, constructed, and managed. Each functional unit represents a discrete component with specific capabilities, allowing the system to assemble diverse network services from standardized building blocks. This segmentation enables flexible construction while maintaining manageable complexity through modular design.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal framework where a single service construction system can handle multiple types of network services through standardized interfaces and bundle files. The system provides multi-functionality by supporting various service models (IaaS, PaaS, SaaS) and deployment scenarios through a common architecture, eliminating the need for separate systems for each service type.

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

2Ease of operation

If purchasers want to easily specify service requirements without detailed implementation knowledge, then ease of operation improves, but the system loses the ability to handle complex service configurations

Engineering Contradiction:
Improveease of service specificationVSAvoidservice configuration capability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent introduces bundle files as an intermediary between purchasers and the service construction system. These bundle files encapsulate complex service configurations in a standardized, easy-to-specify format. Purchasers can reference bundle files without needing to understand the underlying implementation details, while the system automatically processes these files to construct the appropriate functional unit groups, thus bridging the gap between simplicity and complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent employs preliminary action by pre-defining functional units and their relationships in bundle files before the actual service construction process. This allows purchasers to specify requirements by selecting from pre-configured options rather than configuring everything from scratch. The system has already performed the complex work of defining valid configurations, so purchasers only need to make high-level selections.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12376026B2Computer system and network service construction method
Publication Date: 2025.07.29 RAKUTEN SYMPHONY INC
  • US12376026B2 patent drawing
  • US12376026B2 patent drawing
  • US12376026B2 patent drawing

AI summary

A network operating system receives a bundle file transmitted from a vendor terminal of a vendor providing a network service, the bundle file including first data defining a functional unit group that achieves the network service and second data defining a monitoring policy for the network service. The NOS constructs the functional unit group based on the first data of the bundle file when the network service is purchased by a purchaser. The NOS executes a monitoring process on the functional unit group based on information on the functional unit group to be constructed and the second data of the bundle file.