Dynamic Service-Event Management System for Heterogeneous Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems lack a comprehensive and effective method for real-time monitoring and management of service quality in complex, heterogeneous service provider networks, where failures in one service can affect multiple interconnected services, such as electricity, water, gas, and telecommunication services, due to the complexity and interdependence of these networks.

Innovation Solution

A dynamic service-event management system is implemented using a method that converts events from various sources into a common format, projects these events onto a service-oriented architecture, and determines the operational status and failure causes, allowing for unified handling and real-time intervention across different service types.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If real-time monitoring of service status and quality is implemented across multiple heterogeneous service provider networks, then service quality improvement and failure detection capability are improved, but system complexity and difficulty of detecting and measuring increase due to the need to handle diverse event formats and interconnected service dependencies

Engineering Contradiction:
Improveservice qualityVSAvoidcomplexity of monitoring heterogeneous networks
Core Design Contradiction:
ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent introduces an event correlation system that acts as an intermediary between diverse event sources and service monitoring functions. This system receives events from multiple heterogeneous sources, correlates them based on service relationships, and presents unified service-level information, thereby simplifying the monitoring of complex interconnected networks without losing reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements a universal event correlation mechanism that can handle multiple types of events from different service provider networks (electricity, water, gas, telecommunication) through a common processing framework. This multi-functional approach allows single system to monitor diverse service types without requiring separate specialized monitoring systems for each service.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If comprehensive monitoring of interconnected service networks is implemented to detect failures affecting multiple services, then service reliability is improved, but device complexity increases due to the need to manage multiple event sources and failure propagation paths

Engineering Contradiction:
Improveservice reliabilityVSAvoidcomplexity of failure analysis system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the complex failure analysis task into distinct functional components: event collection from various sources, event correlation based on service relationships, failure cause determination, and service status assessment. This segmentation allows each component to handle specific aspects of monitoring independently, reducing overall system complexity while maintaining comprehensive reliability monitoring.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system transitions from monitoring individual service components to monitoring at the service level by adding a new dimensional perspective. Instead of tracking numerous discrete events across multiple networks separately, the system correlates events into service-level failure contexts, thereby simplifying the analytical dimension while improving reliability detection.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Ease of operation

If unified handling of different service types is implemented using common event formats, then ease of operation is improved, but loss of information may occur due to the need to normalize diverse event data into standardized formats

Engineering Contradiction:
Improveunified event handlingVSAvoidinformation loss in event normalization
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent employs a nested event format structure where standardized common event formats contain embedded specific event details. The common format serves as the outer container that provides unified handling and standardization, while inner fields preserve the original specific event information from different service types. This nesting approach enables unified operation while preventing information loss through hierarchical data organization.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS9436541B2Methods of implementing a dynamic service-event management system
Publication Date: 2016.09.06 KNI MUSZAKI TANACSADO KFT
  • US9436541B2 patent drawing
  • US9436541B2 patent drawing
  • US9436541B2 patent drawing

AI summary

Dynamic service-event management methods to implement a dynamic service-event management system. Generally applicable in fields of utility, telecommunication and financial service providers. Therein, events has affect to status or quality of service projecting to service in two steps and using common-format events. In first step, external source originated events (11, 21, 24) are converted in network parser module(s) (1, 2) to a common event-format. In second step, the common format events (12, 22) are processed and their information projected to a service in a service parser module (3). The resulting common format service-event (31) and network events (13, 23) are stored by an alert parser module (4). The stored events are accessible for other connected systems through a database based application programming interface (41). Opening times are effectively handled using opening events (61). A bearer-to-beared object assignment can be handled in two ways. In the easiest solution information originated from an event source is used. Another possible solution uses a static database which is maintained by a database parser module (5). The static database is accessible for other connected systems through a database based application programming interface (51).