Domain-Specific Language for Serverless Network Function Placement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network function virtualization technologies face inefficiencies and disadvantages when running network functions on virtual machines and containers, leading to resource wastage and inflexible network operations.

Innovation Solution

Utilizing a domain-specific language (DSL) to express and compile serverless network functions, optimizing their deployment on network devices by determining optimal execution components based on characteristics such as resource availability and network architecture.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If network functions are run directly on hardware of network devices, then network functions can be executed with low latency, but hardware complexity and cost increase significantly

Engineering Contradiction:
Improveexecution latencyVSAvoidhardware complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent segments network functions into separate virtualized components that can be independently deployed on network devices. Instead of running all network functions directly on hardware, the system divides functions into VNFs that can be selectively instantiated only where needed, reducing hardware complexity while maintaining execution performance.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a network function virtualization layer as an intermediary between hardware and network function execution. This virtualization layer enables network functions to be abstracted from physical hardware, allowing flexible deployment while reducing the need for complex dedicated hardware configurations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If virtual machines are used for network function virtualization, then hardware resources are shared, but resource allocation is inflexible and costly

Engineering Contradiction:
Improveresource flexibilityVSAvoidhardware resources
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent implements dynamic resource allocation for network functions, allowing the system to automatically adjust resource distribution based on current network conditions and function requirements. This dynamic approach replaces static VM resource allocation, enabling flexible adaptation to varying workloads without over-provisioning hardware resources.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of resource allocation from fixed VM-based allocations to dynamic, demand-driven resource assignment. Network functions can be deployed with precise resource parameters matched to actual needs, eliminating the resource wastage associated with traditional VM over-provisioning.

Inventive Principle:
Principle #35Parameter changes

3Ease of manufacture

If containers are used for network function virtualization, then OS virtualization is achieved, but network functions still require complex deployment configurations

Engineering Contradiction:
Improvedeployment simplicityVSAvoidconfiguration complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent enables network functions to be deployed through self-service mechanisms where the virtualization system automatically handles function instantiation, resource allocation, and configuration. This eliminates the need for complex manual configurations, allowing network functions to be deployed simply by providing function definitions and desired locations.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent performs preliminary actions by pre-defining network function characteristics, deployment policies, and resource requirements before actual deployment. This allows the system to automatically handle complex configuration tasks during deployment, simplifying the process while maintaining flexibility in function placement.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If network functions are updated by replacing hardware, then software updates can be applied, but network disruption and downtime occur

Engineering Contradiction:
Improvesoftware update capabilityVSAvoidnetwork downtime
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments network functions into independent virtualized units that can be updated individually without affecting the entire network infrastructure. This allows selective replacement of specific VNFs with updated versions while other functions continue to operate, eliminating comprehensive network downtime during updates.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic function deployment and replacement capabilities, allowing network functions to be updated in real-time or during low-traffic periods without disrupting overall network operation. The system can dynamically migrate functions between different hardware locations during updates, ensuring continuous availability.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP4217848B1Domain-specific language for serverless network functions
Publication Date: 2025.10.29 CISCO TECHNOLOGY INC
  • EP4217848B1 patent drawingFigure 1
  • EP4217848B1 patent drawingFigure 2
  • EP4217848B1 patent drawingFigure 3

AI summary

This disclosure describes techniques and mechanisms for using a domain-specific language (DSL) to express and compile serverless network functions, and optimizing the deployment location for the serverless network functions on network devices. In some examples, the serverless network functions may be expressed entirely in the DSL (e.g., via a text-based editor, a graphics-based editor, etc.), where the DSL is a computer language specialized to a particular domain, such as a network function domain. In additional examples, the serverless network functions may be expressed and compiled using a DSL in combination with a general-purpose language (GSL). Once the serverless network function have been expressed and/or compiled, the techniques of this disclosure further include determining an optimized network component on which the serverless network function is to execute, and deploying the serverless function to the optimized network component.