IP Multicast Connectivity Checks for Remote Peer Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing communication networks lack efficient methods for nodes to determine multicast connectivity with other nodes, particularly in determining connectivity with remote peer endpoints.

Innovation Solution

Implementing a multicast connectivity check (MCC) mechanism using IP packets, where nodes send and receive MCC packets on predefined intervals, update databases based on packet reception, and manage connectivity states through counter mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multicast connectivity check is implemented using existing methods, then connectivity determination between nodes is achieved, but the method is inefficient and lacks automation for remote peer endpoint connectivity

Engineering Contradiction:
Improveconnectivity check efficiencyVSAvoidconfiguration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs self-service by automatically generating and processing MCC packets without requiring manual configuration or intervention. The connectivity check mechanism operates autonomously, with nodes independently determining their connectivity status through automated packet exchange and counter management, eliminating the need for external configuration services

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The connectivity check operates periodically through scheduled MCC packet transmissions at defined intervals. This periodic action allows the system to continuously monitor connectivity status without constant intervention, maintaining up-to-date connectivity information through regular automated checks rather than on-demand operations

Inventive Principle:
Principle #19Periodic action

2Productivity

If automated connectivity monitoring is implemented, then productivity is improved, but CPU usage increases

Engineering Contradiction:
Improveautomated connectivity monitoringVSAvoidCPU usage
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The system applies partial action by using counter mechanisms that track connectivity status without requiring full processing of every MCC packet. The counter-based approach allows the system to monitor connectivity with reduced processing overhead, performing only the minimum necessary actions to maintain accurate connectivity state information

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent replaces complex processing mechanisms with simpler counter-based tracking. Instead of performing elaborate analysis for each connectivity check, the system uses incremental counter updates and comparisons, substituting mechanical processing with a more efficient counting and threshold-based decision system that consumes less CPU resources

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentEP3637681B1Multicast connectivity check based on IP packets
Publication Date: 2025.09.10 NOKIA SOLUTIONS & NETWORKS OY
  • EP3637681B1 patent drawingFigure 1
  • EP3637681B1 patent drawingFigure 2
  • EP3637681B1 patent drawingFigure 3

AI summary

Examples disclose an apparatus (101) which comprises means for performing sending a multicast connectivity check, MCC, packet (105) to a plurality of receiving nodes (110), wherein the MCC packet (105) is an Internet Protocol, IP, packet. Further examples disclose an apparatus (111) included in a receiving node (110). Further examples disclose methods implemented by the apparatuses.