Service Chaining via SPID Encapsulation in Provider Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network technologies face challenges in efficiently enabling services chaining, where data packets need to be processed by multiple services in a sequential order, requiring a flexible and scalable mechanism to direct traffic through the correct inline service paths within a service provider network.

Innovation Solution

A method involving a flexible map and encapsulation mechanism that uses Service Path Identifiers (SPIDs) to determine Endpoint Identifiers (EIDs) and Routing Locators (RLOCs) for data packet encapsulation and re-encapsulation, ensuring data packets are steered through the required services in accordance with the service chaining policy, implemented in network nodes with processors and persistent memory.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a flexible map and encapsulation mechanism is implemented to enable services chaining, then adaptability and versatility of service routing is improved, but device complexity increases due to the need for EID/RLOC mapping and double encapsulation

Engineering Contradiction:
Improveservice routing flexibilityVSAvoidmapping mechanism complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary mapping mechanism that translates between EIDs (endpoint identifiers) and RLOCs (routing locators). This intermediary layer enables flexible service chaining by decoupling the identification of service endpoints from their physical routing locations, allowing operators to dynamically steer traffic through selected service nodes without reconfiguring the entire network infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements double encapsulation where data packets are wrapped with both EID headers (for service identification) and RLOC headers (for physical routing). This nested structure allows the network to simultaneously maintain simple physical routing paths while supporting complex service chaining policies, as the outer RLOC layer handles transport while the inner EID layer enables service-specific routing decisions.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Reliability

If multiple services are chained in sequential order, then service processing completeness is improved, but loss of time increases due to sequential processing requirements

Engineering Contradiction:
Improveservice processing completenessVSAvoidsequential processing delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by pre-establishing EID/RLOC mappings and pre-configuring service chaining policies at the network nodes. When data packets arrive, the ingress node can immediately look up the appropriate RLOC based on the EID and service chaining policy, avoiding real-time computation delays. This preliminary configuration enables fast forwarding decisions while maintaining complete service processing sequences.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If service locations are made dynamic to improve adaptability, then adaptability is improved, but reliability may deteriorate due to potential mapping inconsistencies

Engineering Contradiction:
Improveservice location flexibilityVSAvoidmapping consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements feedback mechanisms where network nodes continuously maintain and update EID/RLOC mapping information. The mapping mechanism provides feedback about the current state of service locations, enabling the network to dynamically adapt service routing while maintaining consistency. This feedback loop ensures that even as service locations change dynamically, all nodes have synchronized information about current mappings, preventing routing inconsistencies.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3014859B1Method for enabling services chaining in a provider network
Publication Date: 2019.08.14 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP3014859B1 patent drawingFigure 1~2
  • EP3014859B1 patent drawingFigure 3A~4
  • EP3014859B1 patent drawingFigure 5~6A

AI summary

A system and method for chaining one or more services in a service provider network. A service chaining policy and associated Service Path Identifier (SPID) are determined at an ingress node with respect to a particular data packet flow. If the service chaining policy involves one or more service nodes to be traversed by the data packet flow, each service node's EIDs and RLOCs are determined. A sequential data exchange process with the service nodes is effectuated using encapsulation of data packets based on the EIDs and RLOCs for obtaining services in accordance with the order of services set forth in the chaining policy.