Consolidated Network Repository Schema for Multi-Platform Data

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional communications networks operate with different implementations, feature sets, and application-specific repositories, leading to data inconsistencies and increased maintenance costs due to the lack of a unified platform for disparate communication networks.

Innovation Solution

A consolidated network repository (CNR) is introduced, structured in tiers with a backend layer for data storage, an interface layer for integration, and a data management layer for standardization, allowing multiple networks to share a common schema and reduce redundancy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If each network maintains an application-specific repository with different schemas, then each network can operate independently with its own features and implementations, but data inconsistencies increase and maintenance costs rise

Engineering Contradiction:

Improvenetwork independenceVSAvoiddata consistency

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a unified repository schema that acts as an intermediary between multiple application-specific repositories. This common schema defines standardized data structures and relationships that all networks must adhere to, thereby ensuring data consistency across independent networks while allowing each network to maintain its operational independence through its own application layer.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The unified repository schema serves multiple functions simultaneously: it provides a common data structure for all networks, enables data sharing across different network types, and maintains compatibility with various application-specific requirements. This multi-functional approach allows the system to achieve both data consistency and network independence.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If each network maintains an application-specific repository with different schemas, then each network can operate independently, but maintenance costs increase due to lack of unified platform

Engineering Contradiction:

Improvenetwork independenceVSAvoidmaintenance cost

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent merges multiple application-specific repositories into a single unified repository structure with a common schema. By combining these separate data storage systems into one standardized platform, the patent reduces maintenance costs through economies of scale, simplified updates, and centralized management, while still supporting multiple independent networks through the unified interface.

Inventive Principle:

Principle #5Merging (Combining)

3Reliability

If a consolidated network repository is introduced with common schema, then data consistency improves and maintenance costs reduce, but device complexity increases due to integration requirements

Engineering Contradiction:

Improvedata consistencyVSAvoidintegration complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the repository system into distinct layers: a unified schema layer that defines the common data structure, and application-specific layers that interact with this schema. This segmentation allows the complexity of integration to be confined to the schema definition, while individual networks can interact with the unified repository through standardized interfaces, thereby reducing overall integration complexity.

Inventive Principle:

Principle #1Segmentation

4Productivity

If a consolidated network repository is introduced with common schema, then scalability enhances and redundancy reduces, but ease of operation decreases due to standardized interface requirements

Engineering Contradiction:

ImprovescalabilityVSAvoidinterface compliance

Core Design Contradiction:

ProductivityVSEase of operation

Solution Approach 1:

The patent implements a dynamic unified repository schema that can adapt to different network requirements while maintaining core standardization. The schema allows for configurable parameters and optional extensions, enabling networks to operate with standardized interfaces for common functions while retaining flexibility for specialized operations, thus balancing scalability with ease of operation.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS10367904B2Consolidated network repository (CNR) for storing data associated with different communication network platforms

Publication Date: 2019.07.30 AT&T INTELLECTUAL PROPERTY I L P

AI summary

An architecture that can facilitate support for or integration of disparate communications networks. The architecture can embody a consolidated network repository (CNR) that can be configured as a single logical repository that can potentially be configured according to a common schema regardless of the type or number of schema employed by the disparate communications networks.