Bidirectional Tree Schema Modification for Version Compatibility

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Managing schema updates in complex data structures, particularly tree-structured schemas, is challenging due to the need for simultaneous support of multiple versions and the high cost and complexity of data migration, which affects a significant fraction of IT budgets.

Innovation Solution

Implementing bidirectional schema modification operations (BiDEL SMOs) to transform tree-structured schemas between versions, allowing for seamless conversion in both directions, thereby simplifying maintenance of multiple versions and reducing the need for extensive code updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If bidirectional schema modification operations are implemented for tree-structured schemas, then schema version compatibility and flexibility are improved, but system complexity and implementation difficulty increase

Engineering Contradiction:

Improveschema version compatibilityVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The schema modification system is segmented into distinct operation types (add node, delete node, add field, delete field, move node, change field name) with dedicated transformation logic for each. This modular approach allows the complex bidirectional transformation problem to be broken down into manageable, independent components that can be implemented and maintained separately.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A path-based intermediary representation is introduced to mediate between different schema versions. The path notation (e.g., '/a/b/c') serves as a universal coordinate system that allows nodes and fields to be identified and transformed across version boundaries without direct coupling between version-specific schemas.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Manufacturing precision

If manual data migration is performed for schema updates, then data transformation accuracy can be controlled, but time consumption and labor costs increase significantly

Engineering Contradiction:

Improvedata transformation accuracyVSAvoidmigration time

Core Design Contradiction:

Manufacturing precisionVSLoss of time

Solution Approach 1:

Schema modification operations are defined and validated in advance, creating a blueprint for transformation before actual data migration occurs. The system pre-computes transformation paths and validates schema compatibility, ensuring that when migration executes, it follows predetermined accurate transformation rules rather than requiring manual intervention.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system performs self-service data transformation by automatically applying the defined modification operations to convert data between schema versions. The bidirectional transformation engine autonomously handles the migration process without manual data manipulation, reducing labor time while maintaining accuracy through systematic application of transformation rules.

Inventive Principle:

Principle #25Self-service

3Adaptability or versatility

If extensive code updates are made to support new schema versions, then functionality and features can be enhanced, but maintenance burden and error risk increase

Engineering Contradiction:

Improvefeature enhancementVSAvoidmaintenance burden

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The schema modification framework provides universal transformation capabilities that work across all schema versions and operation types. Rather than requiring separate code paths for different version scenarios, the system uses a unified set of modification operations that can transform between any compatible versions, reducing code complexity and maintenance burden.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

Instead of updating existing code to accommodate new schema versions, the system inverts the approach by defining transformation operations that can convert old schemas to new schemas and vice versa. This allows legacy code to remain unchanged while supporting new features through bidirectional transformation capabilities.

Inventive Principle:

Principle #13The other way round (Inversion)

4Ease of operation

If unidirectional schema transformation is used, then implementation simplicity is maintained, but flexibility and bidirectional compatibility are lost

Engineering Contradiction:

Improveimplementation simplicityVSAvoidbidirectional compatibility

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system employs asymmetric transformation operations where forward transformation (old to new) and backward transformation (new to old) use different operation sequences. Each direction has optimized transformation paths tailored to its specific requirements, allowing simple unidirectional implementations while achieving overall bidirectional compatibility through coordinated asymmetric operations.

Inventive Principle:

Principle #4Asymmetry

Data Source

PatentUS12579113B2Bidirectional schema modification on tree-structured schemas

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

AI summary

A system for transforming data instances between two tree-structured schemas using a collection of bidirectional tree-structured schema modification operations.