Diagnosing Service Functions in IP Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for diagnosing service functions in IP networks, such as those using ICMP protocol, fail to detect unavailability of SF functions, provide inadequate diagnostics for SFCs, and do not allow for calculation of delays and jitter, leading to inefficiencies in service quality and reliability.

Innovation Solution

A method and system for diagnosing service functions in IP networks that involves a diagnostic node sending requests to SF nodes, performing diagnostic operations, and sending responses indicating success or failure, allowing for iterative diagnosis of SF function chains and enabling the selection of operational SF functions for optimized traffic processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If ICMP protocol is used for diagnosing service functions, then basic network reachability can be checked, but unavailability of SF functions cannot be detected and inadequate diagnostics for SFCs occur

Engineering Contradiction:
Improvedetection accuracy of SF function availabilityVSAvoiddiagnostic capability for SFCs
Core Design Contradiction:
ReliabilityVSMeasurement precision

Solution Approach 1:

The patent segments the diagnostic process into distinct phases: initial reachability check using ICMP, followed by detailed SFC-specific diagnostics using TCP/UDP packets. This segmentation allows basic network connectivity to be verified with simple protocols while enabling comprehensive SF function availability detection through protocol-specific diagnostic messages that can identify individual SF function failures within an SFC chain.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces diagnostic messages as intermediary carriers that transport SF function identification information and diagnostic data between the diagnostic device and SF nodes. These messages act as mediators that enable the diagnostic device to indirectly query and assess the availability of specific SF functions within SFCs without requiring direct access to each function's internal state.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If comprehensive diagnostic operations are performed on SF functions, then service quality can be monitored, but diagnosis time increases

Engineering Contradiction:
Improveservice quality monitoringVSAvoiddiagnosis time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary diagnostic actions by first checking basic network reachability using ICMP before proceeding to more time-consuming SFC-specific diagnostics. This preliminary check filters out obviously unreachable nodes, allowing the system to skip detailed diagnostics for unavailable nodes and thereby reducing overall diagnosis time while maintaining comprehensive monitoring for reachable nodes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies partial diagnostic action by selectively performing detailed SFC diagnostics only on nodes that pass the initial reachability check. Instead of performing comprehensive diagnostics on all potential SF functions regardless of reachability, the system performs partial diagnostics focused only on reachable nodes, thereby optimizing the balance between monitoring comprehensiveness and diagnosis time.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If detailed diagnostic information is collected, then service quality can be improved, but complexity of the diagnostic system increases

Engineering Contradiction:
Improveservice qualityVSAvoiddiagnostic system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements universal diagnostic messages that can serve multiple functions: basic reachability verification, SFC chain validation, and individual SF function availability detection. This multi-functionality allows a single diagnostic message type to replace multiple specialized diagnostic tools, thereby collecting detailed service quality information while minimizing the increase in system complexity through protocol consolidation.

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

4Reliability

If iterative diagnosis of SF function chains is performed, then operational SF functions can be identified, but the number of diagnostic operations increases

Engineering Contradiction:
Improveidentification of operational SF functionsVSAvoiddiagnostic efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent performs preliminary identification of the SFC chain structure and member SF functions before executing iterative diagnostics. By pre-establishing the diagnostic path and target functions, the system avoids redundant diagnostic operations on already-identified operational functions, thereby improving diagnostic efficiency while maintaining reliable identification of all operational SF functions through the iterative process.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3087701B1Method of diagnosis of service functions in an IP network
Publication Date: 2019.02.06 ORANGE SA
  • EP3087701B1 patent drawingFigure 1~4
  • EP3087701B1 patent drawingFigure 2~3

AI summary

The present invention relates to a method of diagnosis of service functions in an IP domain comprising at least one node, termed the PDP node, responsible for the taking of decisions relating to the structuring of a chain of service functions relying on a set of service functions, termed SF functions, and for the notification of these decisions to other nodes of said IP domain, and to at least one node, termed the SF node, associated with at least one SF function posted on said SF node or accessible via said SF node, said method being characterized in that it comprises the following steps: - a node, termed the diagnoser node, sends a request (DIAG_REQ) to an SF node, termed the diagnosed node, concerning an SF function, termed the diagnosed function, which is identified in the request (DIAG_REQ) and/or which is the only SF function associated with said diagnosed node, - the diagnosed node carries out at least one operation of diagnosis concerning said diagnosed function, and - the diagnosed node sends a response (DIAG_RES) to said diagnoser node, said response (DIAG_RES) comprising at least the indication of the success or of the failure of the diagnosis operation, or of the non-operation, or of the malfunctioning, of the diagnosed function. Application to value added services.