Decentralized Revision Control for Telecom Configuration Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing telecommunications systems and devices face challenges in managing and accessing large amounts of complex configuration data in real-time applications, particularly in maintaining version history and ensuring data synchronization across systems, which is not adequately addressed by prior solutions.

Innovation Solution

The implementation of a decentralized revision control system in conjunction with a data provisioning component provides a data storage and runtime configuration framework that is data agnostic, application agnostic, and user agnostic, enabling version history tracking and real-time data management through a decentralized repository and messaging interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a decentralized revision control system is implemented for storing configuration data, then version history tracking and data synchronization capabilities are improved, but system complexity increases

Engineering Contradiction:
Improveversion history trackingVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a data provisioning component as an intermediary layer between the decentralized revision control system and the telecommunications device. This mediator handles the complexity of version control operations, allowing the core device to benefit from reliable version history tracking without directly implementing the complex decentralized control logic. The intermediary abstracts the complexity while preserving the reliability benefits.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system is segmented into distinct functional components: the decentralized revision control system for data storage, the data provisioning component for access management, and the telecommunications device for application execution. This segmentation allows each component to be optimized independently, with the revision control system focusing on reliability while the overall architecture manages complexity through modular design.

Inventive Principle:
Principle #1Segmentation

2Reliability

If configuration data is accessed in a controlled manner with change tracking, then data integrity is improved, but access speed and real-time performance deteriorate

Engineering Contradiction:
Improvedata integrityVSAvoidaccess speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The decentralized revision control system performs preliminary actions by pre-establishing version control mechanisms and change tracking infrastructure before data access operations begin. This allows the system to quickly determine whether access operations need full validation or can proceed with simplified checks, improving real-time performance while maintaining data integrity through pre-configured control mechanisms.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements dynamic access control where the level of controlled access varies based on the operation type and data criticality. Frequently accessed configuration data can use streamlined access paths with essential integrity checks, while critical changes undergo full version control validation. This dynamic approach balances data integrity requirements with real-time access speed needs.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9270528B2Systems and methods of provisioning data storage and runtime configuration in telecommunications systems and devices
Publication Date: 2016.02.23 DIALOGIC INC
  • US9270528B2 patent drawing
  • US9270528B2 patent drawing
  • US9270528B2 patent drawing

AI summary

Systems and methods of provisioning data storage and runtime configuration in telecommunications systems and devices. The systems and methods employ at least one decentralized revision control system as a data repository for storing data, such as configuration data, and at least one data provisioning component as an interface for accessing the configuration data stored in the data repository. By employing the decentralized revision control system in conjunction with the data provisioning component, the systems and methods can provide a data storage and runtime configuration provisioning framework that is data agnostic, application agnostic, and user agnostic, while further providing at least the capability of tracking and maintaining the version history of the configuration data.