Application-Level Load Monitoring for Call Processing Platforms
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing call processing platforms struggle to identify which applications are causing overload conditions during peak traffic, leading to unnecessary rejection of calls and reduced quality of service, as they often reject calls to all applications regardless of their resource demands.
Innovation Solution
Implementing a load monitor within each call processing application to determine its own load level and select operational modes based on predetermined thresholds, allowing for targeted reduction of calls and resource allocation to manage quality of service effectively.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the call processing platform performs call gapping on all incoming calls to reduce overall platform load, then the platform-level load control is maintained, but well-behaved call processing applications operating within engineered parameters are starved and rejected unnecessarily
Solution Approach 1:
The patent divides the monolithic platform-level load control into application-level load control by implementing individual load monitors within each call processing application. This segmentation allows each application to independently monitor its own resource usage and make intelligent decisions about incoming calls, preventing the starvation of well-behaved applications while maintaining overall platform stability.
Solution Approach 2:
The patent applies local quality by enabling each call processing application to have customized load monitoring and call rejection behavior based on its specific resource demands and operational characteristics. Instead of uniform platform-level control, each application can tailor its quality of service management to its local conditions, allowing well-behaved applications to continue operating normally while only rejecting calls from applications that are actually causing overload.
2Reliability
If the call processing platform rejects calls to reduce load during peak traffic periods, then the overload condition is managed, but the platform cannot determine which specific applications are causing the overload
Solution Approach 1:
The patent implements self-service by placing load monitoring capabilities directly within each call processing application. Each application independently monitors its own resource consumption and load conditions, eliminating the need for external observation. This allows the system to maintain information about which applications are causing overload while enabling those applications to make intelligent decisions about call rejection to manage their own load.
Solution Approach 2:
The patent establishes feedback loops within each call processing application where the load monitor continuously observes resource usage and provides information back to the application's call handling logic. This feedback mechanism enables the application to adjust its behavior in real-time based on its actual load conditions, maintaining both load management capability and visibility into which applications are contributing to overall platform load.
Data Source
AI summary
A software platform in one example comprises a plurality of software applications. The plurality of software applications comprise a first software application that performs a determination of a load level associated with the first software application. The first software application employs the determination of the load level to manage a quality of service level associated with the first software application.