Network Service Header for Scalable Network Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

As service provider networks grow in scale, network management and maintenance complexity increase exponentially, and existing technologies struggle to efficiently manage network services across diverse forwarding elements and control planes, leading to challenges in routing and service provisioning.

Innovation Solution

The use of Network Service Headers (NSH) with path identifiers and metadata enables transparent mapping between control plane elements and forwarding elements, facilitating inter-process communication and policy-based routing, thereby creating a unified routing view and scalable network infrastructure through virtualized control planes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If network scale increases, then network capacity and coverage improve, but network management complexity increases exponentially

Engineering Contradiction:
Improvenetwork scaleVSAvoidnetwork management complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent introduces a Service Header as an intermediary element that carries service identification information and metadata between network elements. This header acts as a mediator that enables centralized service management and policy enforcement across distributed network infrastructure, thereby managing complexity while maintaining scalability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments network management into distinct functional components: service identification, policy enforcement, and traffic routing. By dividing the management function into separate manageable segments handled by different network elements, the system can scale without proportionally increasing overall management complexity.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If diverse forwarding elements are used, then network versatility and functionality improve, but routing and service provisioning efficiency deteriorate

Engineering Contradiction:
Improvenetwork versatilityVSAvoidrouting efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The Service Header provides a universal interface that works across diverse forwarding elements regardless of their specific implementations. By encoding service information in a standardized header format, the system achieves multi-functionality where a single management approach can handle various network elements uniformly, maintaining both versatility and efficiency.

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

3Device complexity

If control plane and data plane are coupled, then system simplicity is maintained, but scalability and flexibility are limited

Engineering Contradiction:
Improvesystem simplicityVSAvoidnetwork flexibility
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent separates control plane functions (service policy management, routing decisions) from data plane functions (packet forwarding, service execution). This segmentation allows independent optimization and scaling of each plane, with the Service Header serving as the communication interface between them, thereby achieving both flexibility and managed complexity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10165092B2Using a network service header to manage a network-as-a-system
Publication Date: 2018.12.25 CISCO TECHNOLOGY INC
  • US10165092B2 patent drawing
  • US10165092B2 patent drawing
  • US10165092B2 patent drawing

AI summary

Aspects of the embodiments are directed to augmenting a control packet with an interface identifier, the interface identifier identifying an interface at a physical network forwarding element; and transmitting the control packet with the interface identifier to the physical network forwarding element. The interface identifier can be included in metadata of a network service header (NSH). The NSH is encapsulated with the control packet, which is transmitted with the control packet. The NSH can be extracted and the interface identifier used to identify a user interface (or a presenting interface) based on a metadata lookup.