Managed Node Operational State Control via Domain Manager
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Self-organized network (SON) based managed nodes in telecommunication systems face challenges in predicting installation time and initiating dialog with network operation and management systems, leading to unpredictable operational states and inefficient bandwidth utilization.
Innovation Solution
Implementing a domain manager that prepares and enforces a pre-plan configuration for managed nodes, including trigger points for entering an operational state, allowing for controlled initiation of user traffic and dialog with the network operation and management system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a SON-based managed node is installed and begins operating immediately, then the node can carry user traffic without much guidance from network operators, but the installation time cannot be predicted and the node may become operational at an inopportune time
Solution Approach 1:
The patent implements a pre-plan configuration mechanism where the domain manager prepares and stores operational parameters, trigger conditions, and configuration data before the managed node is actually installed. When the node is deployed, it can quickly activate using the pre-prepared configuration, eliminating the unpredictability of installation timing while maintaining autonomous operation capabilities.
Solution Approach 2:
The patent introduces a domain manager as an intermediary between network operators and SON-based managed nodes. The domain manager facilitates communication by providing pre-planned configurations and receiving status updates, enabling operators to indirectly control and predict node activation times without compromising the nodes' autonomous operation capabilities.
2Extent of automation
If a SON-based managed node operates autonomously without guidance, then network management costs are reduced, but the node is unable to support dialog with the network operation and management system at installation time
Solution Approach 1:
The domain manager pre-prepares configuration data, operational parameters, and dialog protocols before the managed node is installed. This preliminary preparation ensures that when the node becomes operational, it can immediately engage in meaningful dialog with the OAM system without requiring real-time guidance or manual configuration.
Solution Approach 2:
The managed node is designed to autonomously initiate dialog with the domain manager upon installation, using pre-configured communication protocols and identifiers. The node independently retrieves its pre-plan configuration and activates services without requiring manual intervention, thereby maintaining high automation while establishing necessary communication channels.
3Productivity
If the managed node enters operational state immediately upon installation, then user traffic can be carried without delay, but bandwidth utilization may be inefficient and misaligned with network plans
Solution Approach 1:
The domain manager pre-configures the managed node with trigger conditions and operational parameters that align with network plans and bandwidth allocation strategies. The node remains in a prepared state until predefined triggers are met, ensuring that traffic carrying begins at the optimal moment rather than immediately upon installation.
Solution Approach 2:
The managed node's operational state is made dynamic rather than static. It can transition between prepared, active, and dormant states based on real-time network conditions, traffic demand, and pre-configured triggers. This dynamic behavior allows the node to carry traffic efficiently when needed while conserving bandwidth resources when demand is low.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
A device (110) associated with a network (100) receives a fetch request (320) from a managed node (120) connected to the network (100), and provides, to the managed node (120), trigger information (330) specifying one or more conditions under which the managed node (120) is to be enabled and is to receive traffic (360) from the network (100). The device (110) also receives an operational state (350) associated with the managed node (120) based on the trigger information (330).