Provider Edge Device Memory Segmentation for Ethernet Tree Services

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Provider edge devices face memory resource conservation challenges due to the need to store route information for leaf devices, which are typically numerous in Ethernet Tree services, while also ensuring security by prohibiting leaf-to-leaf communications.

Innovation Solution

Implementing a memory management system where provider edge devices selectively store route information for leaf devices in high latency memory and for root devices in low latency memory, based on their categorization within the Ethernet Tree service, to conserve low latency memory resources and prevent unnecessary processing for leaf-to-leaf communication prohibition.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If route information for all customer edge devices is stored in low latency memory, then packet forwarding speed is improved, but memory resource consumption increases significantly

Engineering Contradiction:
Improvepacket forwarding speedVSAvoidmemory resource consumption
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent segments the routing table into two parts: a first portion containing route information for root devices stored in low latency memory, and a second portion containing route information for leaf devices stored in high latency memory. This segmentation allows the system to optimize for both speed and memory usage by placing frequently accessed root device routes in fast memory while storing less frequently accessed leaf device routes in slower memory.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by assigning different storage locations based on the specific characteristics of each device type. Root devices, which require faster access, have their route information stored in low latency memory, while leaf devices, which can tolerate slower access, have their route information stored in high latency memory. This differentiated approach optimizes overall system performance.

Inventive Principle:
Principle #3Local quality

2Speed

If route information for leaf devices is stored in low latency memory, then access speed is improved, but security enforcement complexity increases due to need to prohibit leaf-to-leaf communications

Engineering Contradiction:
Improveroute information access speedVSAvoidsecurity enforcement complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent extracts route information for leaf devices from the low latency memory and stores it separately in high latency memory. This extraction simplifies the security enforcement mechanism by eliminating the need to track and block leaf-to-leaf communications in the fast path, as leaf device routes are not present in the low latency memory where security checks occur.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of storing all route information in low latency memory and using complex security checks to prohibit leaf-to-leaf communications, the patent inverts the approach by selectively excluding leaf device routes from low latency memory. This inversion simplifies security enforcement by making leaf-to-leaf communication prohibition automatic through the absence of leaf device routes in the fast path.

Inventive Principle:
Principle #13The other way round (Inversion)

3Quantity of substance

If all route information is stored in high latency memory, then memory resource usage is optimized, but packet forwarding performance deteriorates

Engineering Contradiction:
Improvememory resource usageVSAvoidpacket forwarding performance
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent segments the routing information storage into two locations: low latency memory for root device routes and high latency memory for leaf device routes. This segmentation ensures that packet forwarding performance is maintained for root device communications while optimizing memory resource usage by storing leaf device routes in slower memory.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the storage parameter (memory latency) based on the device type and access frequency. Root device routes, which require frequent access for packet forwarding, are stored in low latency memory, while leaf device routes are stored in high latency memory. This parameter change optimizes the balance between performance and resource usage.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10887223B1Conserving memory resources of a provider edge device in an ethernet tree
Publication Date: 2021.01.05 JUNIPER NETWORKS INC
  • US10887223B1 patent drawing
  • US10887223B1 patent drawing
  • US10887223B1 patent drawing

AI summary

A provider edge device, capable of accessing a first type of memory and a second type of memory, may determine a network address associated with a customer edge device. The provider edge device may determine whether the customer edge device is categorized as a leaf device in an Ethernet Tree service provided by the provider edge device. The provider edge device may selectively store the network address in the first type of memory or the second type of memory based on determining whether the customer edge device is categorized as a leaf device in the Ethernet Tree service.