Distributed Database for Virtual Network Function Constraint Tracking

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current systems lack transparency and tamper-proof mechanisms for configuring and tracking operational constraints of virtual network functions (VNFs) in field devices, especially when multiple stakeholders are involved, and fail to manage dynamic reconfigurations based on environmental conditions.

Innovation Solution

A node with a retrieval module to monitor and log the operational state of field devices in a distributed database (dDB), which is consensus-driven across infrastructure nodes, allowing for conditional activation/deactivation of operational constraints based on trigger criteria, ensuring transparent and secure tracking and fulfillment verification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If virtual network functions are configured with operational constraints, then security and integrity of communications are improved, but system complexity and difficulty of configuration tracking increase

Engineering Contradiction:

Improveintegrity of communicationsVSAvoidconfiguration tracking

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

A distributed database system acts as an intermediary between multiple stakeholders and the VNF configuration system. The dDB stores constraint definitions, operational states, and fulfillment records in a decentralized manner, allowing all parties to access and verify configuration data without direct interaction, thus reducing system complexity while maintaining security and integrity

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements continuous feedback loops where operational states of VNFs are automatically monitored and compared against defined constraints. The distributed database records and tracks fulfillment status, providing real-time feedback to stakeholders about whether operational constraints are being met, enabling automated detection of deviations without manual intervention

Inventive Principle:

Principle #23Feedback

2Reliability

If operational constraints are tracked transparently across multiple stakeholders, then trust and validation are improved, but information management complexity increases

Engineering Contradiction:

Improvetransparent validationVSAvoidinformation management

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The distributed database serves multiple functions simultaneously: it stores constraint definitions, records operational states, tracks fulfillment status, and provides access to all stakeholders. This multi-functional approach consolidates information management tasks into a single system, reducing overall complexity while enabling transparent validation across the ecosystem

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

Operational constraints and their definitions are pre-configured and stored in the distributed database before VNF deployment. This preliminary action allows all stakeholders to have prior knowledge of expected behaviors and constraints, simplifying subsequent monitoring and validation processes by having reference data already in place

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If dynamic reconfigurations are allowed based on environmental conditions, then adaptability is improved, but risk of malicious circumvention increases

Engineering Contradiction:

Improveruntime reconfigurationVSAvoidmalicious circumvention

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system enables dynamic reconfiguration of VNFs based on environmental conditions by allowing operational constraints to be updated in the distributed database during runtime. Stakeholders can modify constraint parameters or activate/deactivate constraints based on changing conditions, with all changes automatically recorded and tracked in the dDB, maintaining adaptability while preserving auditability

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The distributed database acts as a trusted intermediary that mediates between dynamic reconfiguration needs and security concerns. All reconfiguration requests and environmental condition assessments are recorded in the dDB, creating an immutable audit trail that prevents malicious circumvention while allowing legitimate dynamic adaptations

Inventive Principle:

Principle #24Intermediary (Mediator)

4Measurement precision

If operational states are continuously monitored and logged, then fulfillment tracking is improved, but data storage and processing requirements increase

Engineering Contradiction:

Improvefulfillment trackingVSAvoiddata storage

Core Design Contradiction:

Measurement precisionVSQuantity of substance

Solution Approach 1:

The system extracts and stores only the essential fulfillment tracking data in the distributed database - specifically, the operational state values and constraint fulfillment status - rather than logging all raw operational data. This selective extraction approach maintains precise fulfillment tracking while minimizing data storage requirements by storing only what is necessary for verification

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentEP3804231B1Operational constraints for operational functions of field devices

Publication Date: 2023.03.08 SIEMENS AG

Figure 1
Figure 2
Figure 3

AI summary

According to various examples, an operational constraint associated with an operational function – e.g., a virtual network function – implemented on a field device (112) can be configured. According to further examples, the fulfillment of the operational constraint can be tracked. For these purposes, a distributed database (111) is used, e.g., a blockchain.