Service Function Chain Data Distribution via Layer 3 Routing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing technologies for deploying network services in computer networks are tightly coupled to the underlying network topology, making it difficult to configure or modify service function chains without altering the physical resources.

Innovation Solution

The use of a layer 3 routing protocol to distribute service function data and service function chain data, enabling the decoupling of service function chaining from the underlying network topology and allowing for the use of alternate or redundant service functions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If service function chains are tightly coupled to the underlying network topology, then network services can be deployed using existing infrastructure, but it becomes difficult to configure or modify service function chains without altering physical resources

Engineering Contradiction:

Improveconfigurability of service function chainsVSAvoidcoupling between service function chaining and network topology

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the service function chain management from the underlying network topology by introducing virtual service nodes and logical service function chains that operate independently from physical network infrastructure. This allows service function chains to be configured, modified, and managed as separate logical entities without requiring changes to physical network resources.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer consisting of virtual service nodes and control plane entities that mediate between service function chain configurations and the underlying network topology. This intermediary enables flexible service chain management while maintaining stable physical network infrastructure, resolving the coupling issue by providing a buffer layer.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If service function instances are co-located with primary service functions, then network latency is reduced, but flexibility to use alternate or redundant service functions is limited

Engineering Contradiction:

Improveability to use alternate service functionsVSAvoidservice function processing speed

Core Design Contradiction:

Adaptability or versatilityVSSpeed

Solution Approach 1:

The patent implements dynamic service function instantiation where service function instances can be dynamically selected, activated, or deactivated based on network conditions, service requirements, and availability. This dynamic approach allows the system to switch between co-located instances for low latency and remote instances for redundancy or load balancing, optimizing both speed and adaptability.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of service function instance location from fixed to variable, allowing instances to be distributed across multiple locations and selected based on current needs. Service function chains can specify preferred locations or latency thresholds, and the system dynamically adjusts instance selection to meet these parameters while maintaining flexibility for alternate functions.

Inventive Principle:

Principle #35Parameter changes

3Adaptability or versatility

If routing protocols are used to distribute service function data, then service function chaining is decoupled from network topology, but additional protocol extensions and data structures are required

Engineering Contradiction:

Improvedecoupling of service function chaining from network topologyVSAvoidrouting protocol extensions required

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extends existing routing protocols to serve multiple functions: traditional routing based on network topology and service function chain distribution based on virtual service node locations. By making the routing protocol universal and multi-functional, the system achieves decoupling of service chaining from topology while reusing existing protocol infrastructure rather than creating entirely new mechanisms.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent uses copying of routing protocol data structures and message formats to distribute service function information. Instead of creating entirely new protocols, the system copies and adapts existing routing protocol frameworks, adding service-specific fields and semantics to existing structures, thereby reducing implementation complexity while achieving the desired decoupling.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS12289235B2Distributing service function chain data and service function instance data in a network

Publication Date: 2025.04.29 HEWLETT PACKARD ENTERPRISE DEV LP

AI summary

In some examples, a computing device comprises a first service function instance to apply a service function and a service function forwarder to: receive a first layer 3 routing protocol route advertisement that includes service function instance data for a second service function instance, the service function instance data indicating a service function type and a service identifier for the service function instance; receive a second layer 3 routing protocol route advertisement that includes service function chain data for a service function chain, the service function chain data indicating a service path identifier and one or more service function items; and send, to the second service function instance and based at least on determining a service function item of the one or more service function items indicates the second service function instance, a packet classified to the service function chain.