Management Function for Dynamic PNF Instance Lifecycle in 5G Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current wireless communication systems lack efficient mechanisms for managing physical network function (PNF) instances within network service (NS) instances, particularly in 5G networks, where dynamic addition, modification, and removal of PNFs are necessary to adapt radio coverage and network capacity.

Innovation Solution

The implementation of a method that allows a management function to send update requests to a network functions virtualization orchestrator (NFVO) to add, modify, or remove PNF instances in an NS, utilizing specific messages and notifications to manage lifecycle operations, including adding PNFs like gNB-DU as virtualized functions in the cloud and physical hardware in cell sites.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If PNF instances are dynamically added, modified, or removed in NS instances, then adaptability and network capacity are improved, but system complexity and management difficulty increase

Engineering Contradiction:
ImproveadaptabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a management function as an intermediary between the NFVO and PNF instances. This management function simplifies the complexity by providing a standardized interface for adding, modifying, and removing PNF instances in NS instances, thereby improving adaptability while managing system complexity through abstraction.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If PNF instances are dynamically managed in NS instances, then network capacity and flexibility are improved, but management overhead and operational complexity increase

Engineering Contradiction:
Improvenetwork capacityVSAvoidmanagement overhead
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The management function provides universal capabilities for managing PNF instances across different NS instances. It handles multiple operations (add, modify, remove) through a unified interface, reducing management overhead while maintaining high network capacity and flexibility through standardized multi-functional management.

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

3Adaptability or versatility

If PNF instances are added or modified in NS instances, then radio coverage and network capacity are enhanced, but system stability and operational reliability may be compromised

Engineering Contradiction:
Improveradio coverageVSAvoidsystem stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The management function performs preliminary validation and preparation before adding or modifying PNF instances in NS instances. This preliminary action ensures that changes are properly configured and validated beforehand, enhancing radio coverage and network capacity while maintaining system stability through pre-verification of operational requirements.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10892957B2Managing physical network function instances in a network service instance
Publication Date: 2021.01.12 INTEL CORP
  • US10892957B2 patent drawing
  • US10892957B2 patent drawing
  • US10892957B2 patent drawing

AI summary

Systems and methods provide solutions to add a physical network function (PNF) instance to a network service (NS), modify PNF instances in an NS, and remove PNF instances from an NS. For example, a process may include sending an update NS request from the management function to a network functions virtualization orchestrator (NFVO) to update the NS instance, the update NS request comprising an NS instance identifier, an update type, and PNF information; receiving an update NS response from the NFVO, the update NS response comprising a lifecycle operation occurrence identifier corresponding to an NS lifecycle operation occurrence; receiving an NS Lifecycle Change notification from the NFVO, the NS Lifecycle Change notification indicating a start of an NS update; and receiving an NS identifier change notification from the NFVO, the NS identifier change notification indicating a result of the NS update.