Algebraic Query Language Dynamic Typing for GPS Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database management systems are inadequate for handling large amounts of dynamic, incomplete, and incompatible data from Global Positioning System (GPS) Earth Observatory systems, as they require flexible data migration and manipulation capabilities that current SQL-based solutions cannot efficiently provide due to security and structural compatibility issues.

Innovation Solution

The development of an Algebraic Query Language (AQL) and functional Database Management System (DBMS) that allows for dynamic typing of relations, enabling rapid structural changes and flexible querying of databases with an algebraic syntax, treating relations as types and supporting open workflows.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If SQL-based database management systems are used, then data structure stability is maintained, but flexibility and adaptability for handling dynamic incomplete data are reduced

Engineering Contradiction:
Improveflexibility for handling dynamic incomplete dataVSAvoiddata structure stability
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent implements dynamic typing in the AQL database management system, allowing data types and structures to be determined and modified at runtime rather than requiring fixed pre-definition. This enables the system to adapt to dynamic incomplete data from GPS Earth Observatory systems while maintaining operational stability through algebraic query processing.

Inventive Principle:
Principle #15Dynamics

2Ease of operation

If dynamic typing is implemented, then adaptability and ease of operation are improved, but system complexity increases

Engineering Contradiction:
Improveease of data migration and manipulationVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent replaces traditional mechanical SQL-based database operations with algebraic query language processing. The AQL system uses mathematical algebraic operations to manipulate data, providing dynamic typing and flexibility while managing complexity through formal mathematical frameworks rather than ad-hoc procedural operations.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Productivity

If algebraic query language is used, then productivity and ease of operation are improved, but compatibility with existing SQL systems creates complexity

Engineering Contradiction:
Improvedata migration efficiencyVSAvoidsystem compatibility complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent positions AQL as an intermediary system between data sources and traditional database interfaces. The algebraic query language serves as a mediator that can process data from various sources including GPS Earth Observatory systems and migrate data to relational databases, managing compatibility complexity through its abstract algebraic processing layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10915531B2Algebraic query language (AQL) database management system
Publication Date: 2021.02.09 CALIFORNIA INST OF TECH
  • US10915531B2 patent drawing
  • US10915531B2 patent drawing
  • US10915531B2 patent drawing

AI summary

A method and system provide an algebraic database management system (ADBMS) that maintains ADBMS type system. The type system includes an ADBMS type database (ATD) and provides a collection of rules that assign a type to constructs. The ATD is a catalog with each record holding typing information. An interpreter dynamically processes, at execution time, a query (that is syntactically modeled on relational algebra). The interpreter: determines inputs of the query; searches the ATD for a data type of each of the inputs, determines compatibility between each of data types of the inputs based on an operator of the query, determines a resultant of the query and a data type of the resultant (based on the operator of the query), and saves the resultant of the query by adding a new record in the catalog.