Data Catalog Linking for IoT Equipment Data Retrieval
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In IoT data management, it is challenging to effectively utilize and analyze data collected from multiple equipment sources due to difficulties in identifying the structure and location of data, especially when data is shared among companies, leading to inefficient data processing and utilization.
Innovation Solution
A computer system manages a data lake, data catalog, and asset catalog, generating and linking them to enable equipment-based data obtainment by associating asset catalog data with data catalog data using access keys, facilitating efficient retrieval and analysis of equipment-specific data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If data is accumulated in a data lake from multiple equipment sources, then data collection capability is improved, but data structure identification and location become difficult
Solution Approach 1:
The patent introduces a data catalog as an intermediary between the data lake and users. The data catalog stores structured metadata including data contents, location information, and equipment associations, making it easier to identify and access data without directly searching the entire data lake. This mediator resolves the contradiction by providing an organized interface to the otherwise unstructured data repository.
Solution Approach 2:
The patent segments the data management system into distinct components: the data lake for raw data storage, the data catalog for metadata management, and the asset catalog for equipment information. This segmentation allows each component to specialize in specific functions, with the data catalog handling structure identification and location tracking, thereby resolving the difficulty of searching through accumulated data.
2Adaptability or versatility
If data is shared among companies, then data utilization scope is expanded, but data structure and location information becomes inaccessible
Solution Approach 1:
The data catalog serves as a shared intermediary that both companies can access and contribute to. It standardizes metadata structures and maintains data location information in a mutually accessible format, allowing companies to share data while preserving structure and location information through a common interface rather than direct access to each other's internal systems.
Solution Approach 2:
The patent implements universal data catalog structures that can accommodate data from multiple companies with different formats and systems. The standardized metadata schemas and equipment identification systems work across organizational boundaries, enabling multi-company data sharing while maintaining consistent access to data structure and location information.
3Ease of manufacture
If data is managed without equipment-based organization, then data storage simplicity is maintained, but equipment-based data obtainment becomes inefficient
Solution Approach 1:
The patent segments data management into two layers: simple raw data storage in the data lake maintaining storage simplicity, and structured equipment-based organization in the data catalog and asset catalog. This segmentation allows equipment-based data obtainment to be efficient through structured queries while the underlying storage remains simple and scalable.
Solution Approach 2:
The data catalog acts as an intermediary layer between simple data storage and equipment-based data retrieval. It maintains associations between data, equipment, and locations without complicating the underlying storage structure, enabling efficient equipment-based data obtainment while preserving storage simplicity.
Data Source
AI summary
A computer system manages a data lake storing collected data, which is obtained from a data source, a data catalog storing first catalog data, and an asset catalog storing second catalog data. The computer system comprises: a catalog generation module configured to generate the data catalog, and the asset catalog; and a catalog link generation module configured to associate, in a case where at least one of the data catalog or the asset catalog is generated by the catalog generation module, the asset catalog and the data catalog with each other by adding, as an access key, a value that is stored in the first catalog data stored in the data catalog to the second catalog data stored in the asset catalog.