Managed Object Operations Triggering VNF Lifecycle Automation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In Network Function Virtualization (NFV) environments, existing systems lack efficient automation for managing the lifecycle of Virtual Network Functions (VNFs) and their associated Managed Objects (MOs), leading to manual and inefficient operations during network installation and management.

Innovation Solution

The integration of Managed Object (MO) operations with lifecycle management operations, allowing for automated creation, instantiation, termination, and attribute management of VNFs and MOs through a network architecture that includes a Network Manager (NM), Element Manager (EM), and Virtual Network Function Manager (VNFM), enabling seamless interaction via defined reference points for operations like createMO, deleteMO, and VNF lifecycle management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual operations are used for managing VNF lifecycle, then system complexity is reduced, but productivity and efficiency deteriorate

Engineering Contradiction:

Improvenetwork management efficiencyVSAvoidsystem complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system enables automated self-service through the correlation between MO operations and VNF lifecycle operations. The EM automatically triggers VNF instantiation, termination, and other lifecycle events based on MO creation, deletion, and attribute changes without requiring manual intervention, thereby improving productivity while managing complexity through standardized automation rules

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary correlation mechanism between MO operations and VNF lifecycle operations. This intermediary layer, implemented through the EM, automatically translates MO events into corresponding VNF actions, improving efficiency while abstracting the complexity of direct system interactions away from operators

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If automated lifecycle management is implemented, then productivity improves, but device complexity increases

Engineering Contradiction:

Improveautomation efficiencyVSAvoidarchitecture complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The EM serves multiple functions within the automated lifecycle management system: it manages MO operations, correlates them with VNF lifecycle events, triggers appropriate actions, and handles notifications. This multi-functionality consolidates automation logic into a single manager, improving productivity while containing architecture complexity through functional integration

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system segments automation responsibilities into distinct operational domains: MO management, lifecycle correlation, action triggering, and notification handling. Each segment is handled by specific components or processes within the EM, allowing automated productivity improvements while managing complexity through modular functional segmentation

Inventive Principle:

Principle #1Segmentation

3Ease of operation

If MO operations trigger VNF lifecycle operations, then ease of operation improves, but reliability requirements increase

Engineering Contradiction:

Improvemanagement simplicityVSAvoidautomation reliability

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The system implements feedback mechanisms where the EM monitors MO operation results and VNF lifecycle operation outcomes. Notifications are sent back through the reference points to confirm successful execution or report failures, enabling automated ease of operation while maintaining reliability through continuous state verification and error handling

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The correlation mechanism between MO operations and VNF lifecycle operations includes predefined handling for various scenarios and error conditions. The system prepares for potential failures by establishing predetermined response protocols, thereby simplifying operator interaction while ensuring reliability through advance contingency planning

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS11327787B2Using a managed object operation to control a lifecycle management operation

Publication Date: 2022.05.10 INTEL CORP

AI summary

Techniques for linking managed object (MO) operations and lifecycle operations associated with VNFs (Virtual Network Functions) are discussed. In various actions, MO operations can trigger associated lifecycle operations, or lifecycle operations can trigger associated MO operations. In some aspects, MO instance creation by an EM (Element Manager) can trigger associated VNF instantiation by a VNFM (VNF Manager), or vice versa. In the same or other aspects, MO instance deletion by an EM can trigger termination of an associated VNF by a VNFM, or vice versa.