Network Slice Identifier Injection for Fault Diagnosis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing fault reporting systems in network management fail to accurately determine which network slices are affected by a faulty managed network node, as the distinguished name of the faulty node does not reveal the identity of the network slices it supports, making it difficult to identify the cause of underperformance.
Innovation Solution
A method where unique identifiers of network slices are added to the attributes of network nodes and slices, allowing for easy identification of which slices use which nodes and slices, without relying on management information bases, by initiating updates to these attributes during network slice setup and teardown, and reporting underperforming slices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the distinguished name (DN) of a faulty managed network node is used in alarm reports, then the identity of the faulty node can be determined, but the identity of the network slices supported by the faulty node cannot be determined
Solution Approach 1:
The patent applies preliminary action by adding the network slice identifier to the attribute of the managed network node before the fault occurs. This ensures that when an alarm is generated, the information about which network slices are supported by the faulty node is already available in the node's attribute, eliminating the need for complex post-fault navigation through the network hierarchy.
Solution Approach 2:
The patent introduces an intermediary element - the network slice identifier stored in the managed network node's attribute - that acts as a bridge between the faulty node and the network slices it supports. This intermediary contains the necessary information to directly link the node to its supported slices without requiring traversal of the network hierarchy.
2Reliability
If navigation through multiple levels of the network is performed to determine affected network slices, then the faulty managed network node can be identified, but the process becomes complex and time-consuming
Solution Approach 1:
The patent extracts the network slice identifier information from the complex network hierarchy and stores it directly in the managed network node's attribute. This extraction eliminates the need to navigate through multiple levels of the network structure, simplifying the fault diagnosis process while maintaining reliable identification of affected slices.
Solution Approach 2:
The patent creates a copy of the network slice identifier information and stores it in the managed network node's attribute. This copy allows direct access to the relationship between the node and supported slices without requiring access to or navigation through the parent network structures.
3Shape
If the distinguished name hierarchy is used to represent network structure, then the physical network structure is clearly represented, but the logical network slice relationships are not revealed
Solution Approach 1:
The patent merges the physical network structure representation (through the existing DN hierarchy) with the logical network slice relationship information (through the added network slice identifier in the node attribute). This combination allows both the physical structure and logical slice relationships to be represented simultaneously without losing either type of information.
Solution Approach 2:
The patent adds another dimension to the network representation by including the network slice identifier as an additional attribute of the managed network node. This extra dimension captures the logical slice relationships that are not visible in the traditional hierarchical DN structure, enabling comprehensive identification of both physical and logical network structures.
Data Source
AI summary
There is provided a method for network management performed by a first entity (10), which is configured to manage network slices in a network. The method is performed in response to a first request to set up a first network slice. The method comprises identifying (102) one or more network nodes in the network and/or one or more second network slices to support the first network slice. For each identified network node, an update to an attribute of the identified network node is initiated (104) to add a unique identifier of the first network slice to the attribute of the identified network node. For each identified second network slice, an update to an attribute of the identified second network slice is initiated (106) to add the unique identifier of the first network slice to the attribute of the identified second network slice.