Objectclass Versioning for Directory Server Migration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current directory server migration processes are hindered by schema changes, as not all products can seamlessly transition from older to newer versions, leading to deployment issues and the need for costly upgrades.

Innovation Solution

Implementing objectclass versioning in directory servers, allowing multiple versions of an objectclass to be maintained and selected based on compatibility, enabling migration to newer versions without requiring dependent products to upgrade, and providing per-application mapping for schema conformance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If directory server schema is upgraded to newer version to provide new features, then functionality and feature-set are improved, but compatibility with existing products is lost

Engineering Contradiction:

Improvefeature-setVSAvoidcompatibility

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The schema is segmented into multiple versions (v1, v2, etc.) where each version represents a distinct feature-set. The directory server maintains separate schema definitions for different versions, allowing products to select the appropriate version that matches their capabilities while the server provides access to newer features through alternative schema paths.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The schema versioning system is dynamic, allowing the directory server to adaptively select which schema version to apply based on the requesting product's capabilities. The server can switch between schema versions on-demand, providing newer features to capable products while maintaining backward compatibility with older products through their native schema versions.

Inventive Principle:

Principle #15Dynamics

2Reliability

If all products are upgraded to work with newer directory server version, then compatibility is improved, but cost and complexity increase

Engineering Contradiction:

ImprovecompatibilityVSAvoidupgrade complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The directory server is designed with multi-functionality to support multiple schema versions simultaneously. It can serve as both a v1-compliant server and a v2-compliant server depending on which products are connected, eliminating the need for separate directory server instances for different product versions and reducing overall system complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If schema changes are made to support new features, then functionality is improved, but migration difficulty increases

Engineering Contradiction:

Improvefeature-setVSAvoidmigration ease

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

Multiple schema versions are prepared in advance before migration is needed. The v2 schema is developed and tested independently while v1 continues to serve existing products. When migration occurs, the server already has both schemas ready, allowing for a smooth transition without last-minute schema changes that would complicate migration.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS9760585B2Objectclass versioning

Publication Date: 2017.09.12 BEIJING ZITIAO NETWORK TECH CO LTD

AI summary

Techniques for objectclass versioning in directory server schema are provided. The techniques include migrating from one version of a directory server to another version of the directory server, maintaining one or more versions of an objectclass while migrating from one version of a directory server to another version of the directory server, and selecting one of the one or more versions of an objectclass for normal functioning of an application.