Communication Data Handling Ontology Validation for Reliable Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for managing ontologies of data handling facilities in communication systems face challenges in understanding the broader context of the data, validating its trustworthiness, and determining data integrity, often leading to unreliable data representation due to incomplete or inaccurate monitoring.

Innovation Solution

Implement a central monitoring device that performs name-based and inventory-based data validation, determines data integrity, and compares performance metrics across data handling facilities, enabling remedial actions to ensure data reliability and accuracy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data points are collected from multiple nodes in data handling facilities, then the quantity and coverage of monitoring data is improved, but data reliability and accuracy deteriorate due to incomplete or inaccurate monitoring

Engineering Contradiction:
Improvequantity of monitoring dataVSAvoiddata reliability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The system performs preliminary validation of data points before they are fully processed and stored. Name-based validation checks whether data point names conform to expected patterns and formats, while inventory-based validation verifies whether the data points match known inventory records. This preliminary filtering ensures that only reliable data points are accumulated, resolving the contradiction between data quantity and reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where validation results influence data processing decisions. Data points that fail validation are rejected or flagged, preventing unreliable data from propagating through the system. This feedback loop maintains data quality while allowing comprehensive monitoring of multiple nodes, thus resolving the contradiction between extensive data collection and data reliability.

Inventive Principle:
Principle #23Feedback

2Reliability

If comprehensive data validation is performed on all data points, then data reliability is improved, but processing time and system complexity worsen

Engineering Contradiction:
Improvedata reliabilityVSAvoiddata processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The validation process is segmented into distinct stages: name-based validation and inventory-based validation. Each stage performs a specific type of check and can independently filter data points. This segmentation allows the system to validate data thoroughly without requiring all validation checks to be performed on every single data point simultaneously, reducing processing time while maintaining reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs validation selectively rather than uniformly on all data points. Name-based validation is applied as a first pass to quickly filter obviously invalid data, and inventory-based validation is applied to remaining data points as needed. This partial action approach ensures adequate validation of critical data while avoiding unnecessary processing overhead on already-validated or low-priority data points.

Inventive Principle:
Principle #16Partial or excessive action

3Measurement precision

If multiple validation methods are applied to data points, then data accuracy is improved, but device complexity increases

Engineering Contradiction:
Improvedata accuracyVSAvoidvalidation system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The validation system uses universal data structures and processing mechanisms that handle both name-based and inventory-based validation through common code paths. The same data validation module performs both types of validation by switching between different validation rules, rather than requiring separate independent systems. This multi-functionality approach improves data accuracy through multiple validation methods while minimizing the increase in system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Productivity

If performance metrics are compared across data handling facilities, then operational insights are improved, but data integrity requirements worsen

Engineering Contradiction:
Improveoperational insightsVSAvoiddata integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

Data integrity validation is performed preliminarily before metrics are extracted and compared across facilities. The system ensures that data points meet naming conventions and match inventory records before they are used in cross-facility comparisons. This preliminary integrity check guarantees that operational insights derived from metric comparisons are based on reliable, validated data from all participating facilities.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250285063A1Ontology System Data Validation for Monitoring Communication System Data Handling Facilities
Publication Date: 2025.09.11 T MOBILE INNOVATIONS LLC
  • US20250285063A1 patent drawing
  • US20250285063A1 patent drawing
  • US20250285063A1 patent drawing

AI summary

In some examples, a method for managing an ontology of a data handling facility of a communication system includes receiving data points from a node of the data handling facility, the data points indicating the node as a reporting node. The method also includes performing name-based data validation of the data points. The method also includes responsive to the data points passing the name-based data validation, recording the data points in a data store. The method also includes determining a performance metric based on the data points. The method also includes comparing the performance metric to an expected metric. The method also includes responsive to the performance metric having a difference from the expected metric that exceeds a standard deviation, performing remedial actions regarding the data handling facility.