Telecommunication Cloud Exception Handling via Direct IaaS Channels
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In telecommunication cloud systems, the long notification path between the IaaS management central node and the application layer management central node reduces the reliability of exception event handling, leading to delayed notifications and potential service disruptions.
Innovation Solution
Establishing a direct failure notification channel between the IaaS agent process and the application layer agent/process management process within a host machine, allowing for immediate transmission of resource state exception events, thereby bypassing the central nodes and shortening the notification path.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the exception event notification passes through the IaaS management central node and application layer management central node, then the system architecture maintains centralized management, but the notification path becomes long and reliability decreases
Solution Approach 1:
The notification path is segmented into two channels: a long path through central management nodes for general notifications, and a short direct path from IaaS agent process to application layer for critical exception events. This segmentation allows different notification types to use different paths based on urgency and importance.
Solution Approach 2:
The IaaS agent process acts as an intermediary that directly communicates with the application layer management process for exception events, bypassing the central management nodes. This intermediary mechanism enables fast notification while maintaining the overall centralized management architecture.
2Reliability
If the notification path includes multiple central management nodes, then centralized control is maintained, but notification latency increases
Solution Approach 1:
The direct notification channel between IaaS agent process and application layer management process is pre-established and configured before exception events occur. This preliminary setup ensures that when exceptions happen, the fast path is immediately available without needing to route through central nodes, reducing notification latency while maintaining centralized control.
3Device complexity
If central management nodes serve as failure notification channels, then unified management is achieved, but the reliability of the notification channel decreases
Solution Approach 1:
The notification system is segmented into multiple independent channels: the standard channel through central management nodes for routine notifications, and a direct channel for exception events. This segmentation isolates the reliability issues of central nodes from critical exception notifications, allowing the direct channel to maintain high reliability independent of central node status.
Data Source
AI summary
The present invention discloses a method and a device for handling an exception event in a telecommunication cloud to shorten the notification path and increase the reliability. The method of the present invention includes: detecting a resource state; transmitting a detected resource state exception event to the application layer agent process via a failure notification channel between an infrastructure as a service (IaaS) agent process and an application layer agent process as pre-established inside a host machine Host, and/or transmitting a detected resource state exception event to the application layer management process via a failure notification channel between the IaaS agent process and an application layer management process as pre-established inside the host machine Host. By means of the present invention, the notification path is shortened and the reliability is increased.