Service Path Verification via Network Service Headers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network service deployment models are static and inflexible, failing to adapt to elastic service environments and virtualization, leading to issues with service function movement, policy binding, and failure detection in complex service chains.

Innovation Solution

The implementation of Network Service Headers (NSHs) for metadata communication and service path verification, enabling detection of failures and degradation at the application/service function layers, and automatic bypass through ECMP manipulation, along with off-board notification and troubleshooting mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If static network service deployment models are used, then service functions can be deployed at fixed network locations, but the system cannot adapt to elastic service environments and virtualization

Engineering Contradiction:
Improveadaptability to elastic service environmentsVSAvoidservice deployment model complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic service deployment by enabling service functions to be moved between different network locations and virtualized platforms. The system dynamically determines service path information and updates forwarding entries in real-time, allowing service functions to adapt to changing service environments rather than being fixed to specific network locations.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent creates a universal service insertion model that works across multiple network infrastructures (WAN, data center, campus) and virtualization platforms. The centralized controller and standardized service path determination mechanism provide a unified approach that can deploy services universally across diverse network environments without requiring location-specific configurations.

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

2Reliability

If service functions are physically located at different network points, then service diversity is achieved, but failure detection and service path verification become difficult

Engineering Contradiction:
Improveservice function reliabilityVSAvoidfailure detection difficulty
Core Design Contradiction:
ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements feedback mechanisms where the centralized controller continuously receives service path information from network nodes and monitors service function status. The system uses service path verification processes that provide feedback about the operational state of distributed service functions, enabling reliable failure detection across geographically dispersed network locations through continuous status reporting and verification.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The centralized controller acts as an intermediary between distributed service functions and the service management system. It consolidates service path information from multiple network nodes, performs centralized verification, and coordinates failure detection across the distributed service chain, making it easier to monitor and detect failures in physically dispersed service functions.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If service policy binding is done at coarse network levels, then deployment is simple, but granular per-subscriber state binding is not achieved

Engineering Contradiction:
Improveper-subscriber state binding capabilityVSAvoidpolicy binding complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments service policy binding into hierarchical levels: the centralized controller handles coarse-grained service path determination, while individual network nodes handle fine-grained per-subscriber state binding. This segmentation allows the system to achieve granular per-subscriber policy enforcement without requiring complex centralized processing of every subscriber state, distributing the complexity across appropriate system levels.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10153951B2Determining the operations performed along a service path/service chain
Publication Date: 2018.12.11 CISCO TECHNOLOGY INC
  • US10153951B2 patent drawing
  • US10153951B2 patent drawing
  • US10153951B2 patent drawing

AI summary

Presented herein are techniques performed in a network comprising a plurality of network nodes each configured to apply one or more service functions to traffic that passes the respective network nodes in a service path. At a network node, an indication is received of a failure or degradation of one or more service functions or applications applied to traffic at the network node. Data descriptive of the failure or degradation is generated. A previous service hop network node at which a service function or application was applied to traffic in the service path is determined. The data descriptive of the failure or degradation is communicated to the previous service hop network node.