EVPN Mobility via Dual Sequence Number Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mobility procedures for EVPNs break endpoint mobility when an endpoint moves from one data center to another, as they do not effectively manage inter-data center and intra-data center movements, leading to incorrect routing and disrupted network connectivity.

Innovation Solution

Implementing a mobility management mechanism that uses two separate sequence numbers, one for intra-data center and one for inter-data center movements, to track and update routing tables at provider edge nodes and gateways, ensuring seamless host mobility across multiple data centers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If current mobility procedures for EVPNs are used, then routing within a single data center is maintained, but endpoint mobility breaks when moving between data centers

Engineering Contradiction:
Improveendpoint mobility continuityVSAvoidinter-data center movement support
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the sequence number tracking into two separate counters: one for intra-data center mobility and one for inter-data center mobility. This segmentation allows each counter to independently track movements within its scope, enabling reliable mobility tracking both within and between data centers without the limitations of a single counter approach.

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If a single sequence number is used for mobility tracking, then intra-data center mobility is tracked, but inter-data center mobility cannot be distinguished

Engineering Contradiction:
Improvemobility tracking accuracyVSAvoidrouting table structure
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent adds a dimensional distinction to sequence number tracking by introducing two separate counters (intra-DC and inter-DC) instead of a single counter. This dimensional change enables precise measurement of mobility events by type, allowing the system to distinguish between local and remote movements while maintaining structured routing tables through the use of extended community attributes.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Ease of operation

If UMR is used for MAC route advertisement, then default routing for unknown MAC addresses is achieved, but specific mobility routes are suppressed

Engineering Contradiction:
Improvedefault route managementVSAvoidspecific mobility route information
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent implements a feedback mechanism where mobility sequence numbers are advertised alongside MAC address routes. This feedback provides specific mobility route information to other data centers, enabling them to track endpoint movements accurately. The sequence number feedback prevents information loss by ensuring that mobility state is communicated even when using UMR for default routing.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20240314060A1Mobility enhancement for interconnected ethernet virtual private networks
Publication Date: 2024.09.19 CISCO TECHNOLOGY INC
  • US20240314060A1 patent drawing
  • US20240314060A1 patent drawing
  • US20240314060A1 patent drawing

AI summary

A method includes creating a first routing table at each of a plurality of provider edge nodes in a first data center, the first routing table including a first sequence number tracking intra-data center movement of the host connected to one of the plurality of provider edge nodes; creating a second routing table at a corresponding gateway of each of a plurality of data centers, the plurality of data centers including the first data center, the second routing table including the first sequence number for the host and a second sequence number for tracking inter-data center movement of the host between the plurality of data centers host; and updating one of (1) the first sequence number when the host makes an intra-data center move, or (2) the second sequence number in the second routing table when the host makes an inter-data center move.