Service Management Function for Virtual Network SLA Coordination

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network management systems face challenges in consistently and reliably satisfying service level agreements (SLAs) as they evolve, particularly in integrating resources across different network domains and managing resource allocation efficiently in virtualized network environments.

Innovation Solution

A Service Management Function (SvMF) is introduced in the control plane of virtual networks to process SLA requirements and generate corresponding requests for physical resource allocation, coordinating with resource management units within the operator network and subnetworks, including 3GPP and non-3GPP compliant entities, to ensure efficient resource division and allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional network management systems are used to manage virtualized network functions, then existing infrastructure can be maintained, but service level agreements cannot be consistently and reliably satisfied

Engineering Contradiction:
ImproveSLA satisfaction reliabilityVSAvoidmanagement system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The management system is segmented into multiple specialized subsystems: Service Management Function (SMF) for SLA processing, Resource Management Function (RMF) for resource allocation, and Virtualization Management Function (VMF) for VNF coordination. Each subsystem handles specific aspects of management, improving reliability through specialized functionality while maintaining overall system coherence through standardized interfaces.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A Service Management Function acts as an intermediary layer between service level agreements and the underlying virtualized network functions. The SMF translates high-level SLA requirements into specific resource allocation requests, coordinating with RMF and VMF to ensure reliable SLA satisfaction without requiring direct complex interactions between all management components.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If resources are allocated statically across network domains, then resource allocation is simple to manage, but resource utilization efficiency decreases

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidresource allocation complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The resource allocation system transitions from static to dynamic allocation. The Resource Management Function continuously monitors resource usage across network domains and dynamically adjusts allocations based on current demand and SLA requirements. This allows resources to be moved between domains in real-time, improving utilization efficiency while the automated nature of the system manages the complexity of dynamic coordination.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms where the RMF receives status information from VMF and SLA compliance data from SMF, then adjusts resource allocations accordingly. This closed-loop control enables the system to respond to changing conditions and optimize resource utilization dynamically, with the feedback process automating what would otherwise be complex manual coordination.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If multiple network domains are integrated for resource sharing, then resource allocation flexibility improves, but coordination complexity increases

Engineering Contradiction:
Improveresource allocation flexibilityVSAvoiddomain coordination complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The Service Management Function and Resource Management Function are designed as universal coordination entities that can manage resources across multiple different network domains through standardized interfaces. These functions can handle diverse resource types and domain-specific protocols uniformly, providing flexible cross-domain resource allocation while the standardized approach reduces the complexity that would arise from custom integration for each domain.

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

4Productivity

If manual resource allocation is used across domains, then system complexity is low, but resource allocation efficiency and SLA satisfaction decrease

Engineering Contradiction:
Improveresource allocation efficiencyVSAvoidautomation level
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The Resource Management Function implements self-service capabilities by automatically monitoring resource availability, detecting allocation opportunities, and executing resource transfers between domains without manual intervention. The system can autonomously respond to SLA violations or optimization opportunities, significantly improving allocation efficiency. The automation is managed through structured processes and standardized interfaces, keeping system complexity controllable despite the high level of automation.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP3590233B1Architecture for integrating service, network and domain management subsystems
Publication Date: 2021.06.02 HUAWEI TECH CO LTD
  • EP3590233B1 patent drawingFigure 1
  • EP3590233B1 patent drawingFigure 2
  • EP3590233B1 patent drawingFigure 3

AI summary

A method of controlling a service instance in a virtual network, the method comprising providing a Service Management Function entity in a control plane of the virtual network, the Service Management Function being configured to process requirements of a Service Level Agreement and generate corresponding control plane requests for physical resources to satisfy the Service Level Agreement.