Data Converting Apparatus Using Metadata Codes for Flexible Type Conversion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data conversion systems face challenges in expanding data types and type attributes, leading to inconsistencies and increased developer burden due to the lack of units for ensuring type attribute consistency and efficient selection of cleansing functions.

Innovation Solution

A data converting apparatus that utilizes encoded meta-definition information to assign metadata codes, a conversion rule table, and a converting function to match metadata codes for data conversion, enabling flexible and efficient conversion between different data types and attributes without requiring pre-defined conversion logic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional cleansing functions with pre-determined data type combinations are used, then data conversion can be performed with existing types, but expandability deteriorates when new data types or type attributes need to be added

Engineering Contradiction:
Improveexpandability of data types and type attributesVSAvoidcomplexity of managing data type combinations and cleansing functions
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The invention segments the data type system into distinct components: data type definitions, type attribute definitions, and cleansing function definitions are separated into independent units. This allows each component to be defined, stored, and managed separately, enabling easy expansion of data types and attributes without complicating the overall system structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The invention creates a universal cleansing function selection mechanism that works across all data type combinations through a common framework. The system uses type attribute information and cleansing function definition information that can be applied universally to any data type, eliminating the need for separate pre-determined combinations for each specific type pair.

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

2Adaptability or versatility

If multiple data types and type attributes are combined and used, then data conversion capability increases, but consistency between type attributes and processes deteriorates without a unit for ensuring consistency

Engineering Contradiction:
Improvedata conversion capability across multiple typesVSAvoidconsistency of type attributes and processes
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The invention implements feedback mechanisms where the system refers to stored type attribute information and cleansing function definition information to automatically determine appropriate cleansing functions. This closed-loop approach ensures that type attribute consistency is maintained by continuously referencing the defined specifications during data conversion operations.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary actions by pre-defining and storing type attribute information and cleansing function definition information in a structured manner before actual data conversion occurs. This advance preparation ensures consistency is built into the system architecture, eliminating the need for runtime consistency checks.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If the number of data types, type attributes, type converting functions, and cleansing functions is increased, then conversion coverage improves, but developer burden and management complexity increase

Engineering Contradiction:
Improveconversion coverage across data typesVSAvoiddeveloper burden and management effort
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The invention enables the system to self-configure cleansing functions by automatically referring to stored type attribute information and cleansing function definition information. This self-service mechanism eliminates the need for developers to manually configure each cleansing function for every data type combination, significantly reducing developer burden while maintaining comprehensive conversion coverage.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses templates and definition information that can be copied and reused across multiple data types and scenarios. By storing cleansing function definition information in a standardized format, the same definitions can be referenced repeatedly, reducing the effort required to manage extensive data type conversions.

Inventive Principle:
Principle #26Copying

4Productivity

If conventional cleansing functions are used without an efficient selection mechanism, then all cleansing functions must be considered for each combination, but performance deteriorates due to inability to efficiently select necessary functions

Engineering Contradiction:
Improvedata conversion performanceVSAvoidtime to select and execute appropriate cleansing functions
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-defining and storing cleansing function definition information that includes type attribute information and function characteristics. This advance organization allows the system to quickly identify and select appropriate cleansing functions without exhaustive searching, significantly improving performance while reducing selection time.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8655897B2Data converting apparatus, method, and computer product
Publication Date: 2014.02.18 FUJITSU LTD
  • US8655897B2 patent drawing
  • US8655897B2 patent drawing
  • US8655897B2 patent drawing

AI summary

A data converting apparatus includes a storage unit that stores encoded meta-definition information, a data converting function, a conversion rule table, and a conversion rule; an input unit that receives input of data to be converted; a detecting unit that uses the encoded meta-definition information to detect metadata codes for a conversion source and a conversion destination for which the conversion rule code matches; a determining unit that determines whether the detected metadata codes match; a specifying unit that, by referring to a conversion rule and based on the determination result at the determining unit, specifies the data converting function, according to the combination of the metadata codes for the conversion source and for the conversion destination; and a converting unit that uses the specified data converting function to convert the data of the conversion source to have a property prescribed by metadata for the conversion destination.