Network Management Event Pool Mapping for Scalable Forwarding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network management systems face scalability issues due to exponential increase in event load as the number of Event Consumption Component (ECC) instances and application instances grow, leading to impractical fully-meshed forwarding schemes that are difficult to configure and manage.

Innovation Solution

A method is introduced to determine a mapping between pools of consumers and instances of network management applications, allowing connections to be defined between members of these pools, with options for round robin or load-based allocation, enabling efficient forwarding of network management event data while avoiding duplication and manual configuration complexities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a fully-meshed forwarding scheme is used to connect multiple ECC instances to multiple application instances, then event delivery completeness is improved, but system complexity and event load increase exponentially

Engineering Contradiction:
Improveevent delivery completenessVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the system into pools of consumers (ECC instances) and pools of applications, with each pool managed independently. Instead of creating a fully-meshed connection between every consumer and every application, the system segments the forwarding relationships into manageable groups defined by mapping rules, thereby reducing complexity while maintaining event delivery completeness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a pool controller as an intermediary component that manages the mapping between consumer pools and application pools. The controller receives mapping rules, determines appropriate mappings, and configures forwarders accordingly, thereby simplifying the system architecture by centralizing the complexity of managing many-to-many relationships rather than requiring direct peer-to-peer connections between all components.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If the number of ECC instances and application instances is increased to improve system scalability, then processing capacity is improved, but event load and duplication increase exponentially

Engineering Contradiction:
Improveprocessing capacityVSAvoidevent load
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The patent implements dynamic mapping rules that can adapt to changing system conditions. The pool controller can adjust mappings based on current load, consumer capabilities, and application requirements, allowing the system to scale efficiently without generating excessive event duplication. This dynamic approach enables the system to optimize event routing as instances are added or removed from pools.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameters of event forwarding by introducing mapping rules that control which consumers forward events to which applications. Instead of every consumer forwarding to every application (resulting in exponential event duplication), the mapping rules selectively route events based on criteria such as consumer type, application type, event type, or load conditions, thereby maintaining processing capacity while reducing event load.

Inventive Principle:
Principle #35Parameter changes

3Manufacturing precision

If manual configuration of forwarding relationships is used to ensure precise event routing, then routing precision is improved, but ease of operation deteriorates

Engineering Contradiction:
Improverouting precisionVSAvoidease of configuration
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The patent implements self-service mechanisms where the pool controller automatically determines and configures mappings based on mapping rules provided by administrators. The system can automatically discover consumers and applications, evaluate mapping criteria, and configure forwarding relationships without requiring manual intervention for each connection, thereby maintaining routing precision while significantly improving ease of operation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent incorporates feedback mechanisms where the pool controller monitors system state, consumer capabilities, and application requirements to dynamically adjust mappings. The controller receives information about system conditions and uses this feedback to optimize event routing, ensuring precise delivery while adapting to changing conditions without requiring manual reconfiguration.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10498581B2Event processing in a network management system
Publication Date: 2019.12.03 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US10498581B2 patent drawing
  • US10498581B2 patent drawing
  • US10498581B2 patent drawing

AI summary

A network management system (10) of a communication network (5) determines members of a pool (20, 30, 40) of consumers (21, 31, 41) in the network management system (10). Consumers are arranged to receive network management event data from network elements (5, 6, 7) of the communication network (5). The network management system (10) determines members of a pool (50, 60, 70) of instances (51, 61, 71) of a network management application (A, B, N) in the network management system (10). Instances of the network management application are arranged to process the network management event data. The network management system (10) determines a mapping between the pool (20) of consumers (21) and the pool (50) of instances (51) of the network management application (A). The mapping defines connections (15) for forwarding network management event data. Each of the connections is defined between a member (21) of the pool (20) of consumers and a member (51) of the pool (50) of instances of the network management application.