Ontology-Based User Requirement Decomposition for AMF Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity of the Availability Management Framework (AMF) domain makes it difficult to manually create AMF configurations that meet user requirements, especially in highly available systems and cloud computing environments, where there is a gap between user requirements and available components, and existing model-driven approaches are limited in flexibility and customization.

Innovation Solution

A computer-implemented method and system that automatically generates configuration requirements from user requirements using an ontology to decompose functionalities, map them to available components, and calculate the required number of service instances, enabling the creation of multiple component sets that satisfy user needs and facilitate system evolution and maintainability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual creation of AMF configurations is used, then flexibility and customization are improved, but complexity and time consumption increase significantly

Engineering Contradiction:
Improveflexibility and customizationVSAvoidcomplexity of AMF domain
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the complex AMF configuration process into distinct modules: user requirement decomposition module, ontology-based functionality decomposition module, component mapping module, and configuration generation module. Each module handles a specific aspect of the configuration process, making the overall complex system manageable and maintainable while preserving flexibility through the modular architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an ontology as an intermediary layer between user requirements and available components. The ontology stores structured knowledge about functionality decompositions and component relationships, acting as a mediator that automatically translates high-level user requirements into detailed component configurations, thereby reducing manual effort while maintaining adaptability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If automated generation of AMF configurations is implemented, then productivity and time efficiency are improved, but adaptability to customize configurations may be reduced

Engineering Contradiction:
Improveefficiency in generating AMF configurationsVSAvoiduser-friendly customization
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent implements a dynamic configuration system where the level of automation can be adjusted. Users can specify their requirements at different levels of detail, and the system adapts its automation程度 accordingly. The ontology allows for flexible decomposition depths, enabling users to customize configurations interactively when needed while accepting fully automated generation when productivity is the priority.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system incorporates feedback mechanisms where users can review and modify the automatically generated configurations. The ontology-based approach provides traceability from user requirements to generated configurations, allowing users to understand and adjust the automation output. This feedback loop maintains adaptability while preserving the productivity benefits of automation.

Inventive Principle:
Principle #23Feedback

3Reliability

If comprehensive decomposition of user requirements is performed, then reliability and correctness of configuration are improved, but loss of time and computational resources increase

Engineering Contradiction:
Improvecorrectness of AMF configurationVSAvoidtime for decomposing functionalities
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary action by pre-building the ontology with known functionality decompositions and component relationships during system setup or offline processing. This pre-computed knowledge base enables faster online configuration generation, as the system can directly query the pre-structured ontology rather than performing comprehensive decomposition from scratch each time, thus maintaining reliability while reducing time loss.

Inventive Principle:
Principle #10Preliminary action

4Manufacturing precision

If detailed mapping to vendor components is performed, then manufacturing precision and component selection accuracy are improved, but device complexity and difficulty of management increase

Engineering Contradiction:
Improveaccuracy of component selectionVSAvoidcomplexity of managing component relationships
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent creates a universal ontology framework that can map to multiple vendor components through a common interface. The ontology defines standardized functionality concepts that can be instantiated with different vendor-specific components, allowing accurate component selection without directly managing the complexity of each vendor's component model. This universal layer abstracts the complexity while maintaining mapping precision.

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

Data Source

PatentUS9164734B2Ontology-based user requirement decomposition for component selection for service provision
Publication Date: 2015.10.20 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US9164734B2 patent drawing
  • US9164734B2 patent drawing
  • US9164734B2 patent drawing

AI summary

Configuration requirements that specify the provision of services using a system-level description are automatically generated from user requirements. The user requirements are decomposed into one or more levels of decomposed functionalities using an ontology as input. The ontology stores known decompositions of functionalities and relations between the known decompositions. The lowest level of the decomposed functionalities is mapped into a set of components provided by vendors, and additional components on which the set of components depend are identified. Based on the set of components and the additional components, a required number of instances of service workload is calculated to generate the configuration requirements of the system that satisfy the user requirements.