Edge Database for Network Data Plane Attribute Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network data plane management systems are limited by the use of pre-programmed ASICs and key value stores, which cannot effectively handle complex attributes and extensions needed for advanced network management.

Innovation Solution

The implementation of an edge database with a multi-dimensional data store that defines a network data model, allowing for the management of complex network attributes and attributes extensions, and enabling dynamic attribute prioritization and re-factorization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If pre-programmed ASICs are used for network data plane management, then device complexity is reduced and reliability is improved, but adaptability and ability to handle complex attributes are limited

Engineering Contradiction:
Improveability to handle complex attributesVSAvoiddata plane management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an edge database as an intermediary component between the network data plane and control plane. This edge database serves as a mediator that stores and manages complex network attributes, allowing the data plane to access sophisticated attribute information without requiring complex processing logic within the data plane itself. The edge database acts as the intermediary that bridges the gap between simple data plane operations and complex attribute management requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If key value stores are used for attribute management, then implementation is simple, but ability to handle complex attributes and extensions is limited

Engineering Contradiction:
Improveattribute extension capabilityVSAvoidimplementation complexity
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent transitions from traditional two-dimensional key-value store structures to a multi-dimensional data model organized around network entities (devices, services, applications). This dimensional transformation allows attributes to be organized hierarchically and relationally, enabling complex attribute relationships and extensions while maintaining structured access patterns. The multi-dimensional organization provides both simplicity in access and complexity in representation.

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

3Productivity

If standard SDN approaches are used, then flexibility is improved, but performance and scalability are limited due to centralized control

Engineering Contradiction:
Improvedata plane processing performanceVSAvoidnetwork function flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent implements local quality by placing edge databases at distributed network locations rather than relying on centralized control. Each edge database locally stores and manages attributes relevant to its specific network segment, enabling fast local access and processing while maintaining flexibility through distributed attribute management. This localizes the intelligence and adaptability needed for complex attribute handling without sacrificing processing performance.

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP3987721B1Edge database management of the network data plane
Publication Date: 2025.02.12 CENTURYLINK INTELLECTUAL PROPERTY LLC
  • EP3987721B1 patent drawingFigure 1
  • EP3987721B1 patent drawingFigure 2
  • EP3987721B1 patent drawingFigure 3

AI summary

Novel tools and techniques for network data plane management are provided. A system includes a host machine that includes a database, processor, and non-transitory computer readable media comprising instructions executable by the processor to obtain, via the database, a network configuration, spawn a container according to the network configuration, wherein the container is configured, based on the network configuration, to be coupled to a network overlay via a network interface, receive, via the network interface, incoming data associated with the container, the incoming data having attached one or more attached network data attributes, and identify, via the database, the attached one or more network data attributes attached to the incoming data as one or more network data attributes of the network data model.