VoIP Service Component Modeling for Root Cause Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is a need for a method and apparatus to effectively represent, analyze, and determine root cause errors in VoIP networks that incorporate additional services such as e-mail, instant messaging, ERP, and SAP services, and to manage their impact on network performance.
Innovation Solution
A method and apparatus for modeling and analyzing VoIP configurations by representing selected components and their relationships, mapping events, and determining causality between them, using a computerized device with a load manager application to perform root cause analysis and impact assessment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If additional services (e-mail, instant messaging, ERP, SAP) are added to VoIP networks, then service functionality and versatility are improved, but network complexity and difficulty of management increase
Solution Approach 1:
The patent segments the VoIP network into distinct service components (VoiceMailService, VoiceConferenceService, ITServices, ERPServices, CRMServices, WebServices, SupportServices) that can be independently modeled and managed. Each service type is represented as a separate configurable entity, allowing administrators to manage individual services without affecting the entire network, thus reducing management complexity while maintaining service versatility.
Solution Approach 2:
The patent creates a universal service representation model that can accommodate multiple service types (VoIP, e-mail, instant messaging, ERP, SAP) through a common framework. The service representation includes universal attributes and relationships that apply across all service types, enabling standardized management approaches while supporting diverse service functionalities.
2Measurement precision
If comprehensive monitoring of additional services is implemented, then problem detection capability is improved, but system complexity and resource consumption increase
Solution Approach 1:
The patent extracts the monitoring and analysis functions into a separate service representation and event correlation system. Instead of monitoring all services uniformly, the system extracts specific events from each service type and correlates them through a unified model, enabling precise problem detection without requiring complex integration of all service monitoring mechanisms.
Solution Approach 2:
The patent introduces an intermediary service representation layer that mediates between individual service events and overall network status. This intermediary model correlates events from multiple services and identifies root causes without requiring direct complex interactions between all monitoring components, thus reducing system complexity while maintaining detection precision.
3Measurement precision
If root cause analysis is performed across multiple service types, then error identification accuracy is improved, but computational requirements and processing time increase
Solution Approach 1:
The patent applies local quality by creating service-specific event representations that capture the unique characteristics and event types of each service (e.g., VoiceMailService events differ from ERPServices events). This allows the root cause analysis to focus on service-specific patterns and relationships, improving error identification accuracy while avoiding unnecessary computational analysis of irrelevant service data.
Solution Approach 2:
The patent implements partial action by performing root cause analysis on correlated events only when necessary, rather than continuously analyzing all service events. The service representation model enables selective analysis of event correlations that are most likely to indicate root causes, reducing computational requirements while maintaining accurate error identification.
Data Source
AI summary
A method, apparatus and computer product for modeling and analyzing additional services incorporated into a Voice-over-IP (VoIP) configuration composed of a plurality of components is disclosed. The method comprises the steps of representing selected ones of the plurality of components and relationships among the selected components, wherein said component representations are selected from the group of configuration non-specific representations consisting of: VoIP VoiceMailService, VoIPVoiceConferenceService, ITServices, ERPServices, CRMServices, WebServices and SupportServices, and wherein the representations of relationships are selected from the group of configuration non-specific representations consisting of: HostedBy/HostsServices and Integrates/IntegratedIn, providing a mapping between a plurality of first events and a plurality of second events occurring in the selected components, the mapping representing the relationships along which the first events propagate among the selected components, and determining at least one first event based on at least one of the plurality of second events by determining a measure between each of a plurality of relationship values associated with the plurality of first events and the plurality of second events.