Dynamic Metadata Management for Enterprise Service Frameworks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing business software applications face challenges in dynamically managing meta data to ensure compatibility between front-end and back-end components, particularly in large-scale systems where changes to the back-end data require updates to the front-end, leading to inflexibility and compatibility issues across different versions.

Innovation Solution

A computer program product and system that enables dynamic meta data management by associating meta data elements with attributes, calculating values based on application states, user roles, and predefined configurations, and storing them in a repository with a separation layer between the front-end and back-end, allowing for dynamic changes and compatibility checks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the back-end data structure is changed, then the data storage and processing capability is improved, but the front-end compatibility deteriorates requiring updates

Engineering Contradiction:
Improveback-end data structure flexibilityVSAvoidfront-end back-end compatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a service layer as an intermediary component between the front-end and back-end. This service layer includes a metadata repository and service factory that dynamically generate and manage service interfaces. The intermediary translates and adapts data structures, allowing the back-end to change without directly impacting the front-end, thus resolving the compatibility issue while maintaining flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements dynamic metadata that can be calculated and modified at runtime based on application state, user roles, and configuration. The service factory dynamically generates service interfaces based on current system state rather than using fixed static interfaces. This dynamic approach allows the system to adapt to back-end changes automatically without requiring front-end updates, resolving the contradiction between flexibility and compatibility.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If the front-end is customized for specific customers, then the customer-specific functionality is improved, but the system complexity increases

Engineering Contradiction:
Improvecustomer-specific customizationVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal service layer that handles multiple functions including dynamic metadata management, service interface generation, and configuration handling. This universal layer serves all customers and applications through a common architecture, eliminating the need for separate customizations for each customer. The service factory generates customer-specific configurations dynamically from a unified metadata repository, reducing system complexity while maintaining customization capability.

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

Solution Approach 2:

The patent pre-defines a comprehensive metadata schema and service interface framework that can accommodate various customer requirements. By establishing this preliminary structure with extensibility built-in, the system can adapt to specific customer needs through configuration rather than structural changes, avoiding the complexity of extensive customizations while maintaining versatility.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If dynamic metadata calculation is implemented, then the data presentation flexibility is improved, but the processing time increases

Engineering Contradiction:
Improvedata presentation flexibilityVSAvoidmetadata calculation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent pre-calculates and stores metadata templates and service interface definitions in the metadata repository during system initialization or configuration phases. These pre-computed metadata structures serve as templates that can be quickly instantiated and adapted at runtime without performing full calculations. This preliminary action significantly reduces the processing time required for dynamic metadata generation while maintaining flexibility.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements selective metadata calculation where only the specific metadata elements relevant to the current user, application state, and configuration are calculated and retrieved, rather than computing the entire metadata set. The service factory generates only the necessary service interfaces based on current needs, reducing processing time while maintaining the flexibility of dynamic data presentation for relevant portions of the system.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS7908248B2Dynamic meta data
Publication Date: 2011.03.15 SAP SE
  • US7908248B2 patent drawing
  • US7908248B2 patent drawing
  • US7908248B2 patent drawing

AI summary

Methods and apparatus, including computer program products, for using dynamic meta data for an enterprise service framework. There is a meta data element associated with a meta data element attribute. A value for the meta data element attribute is calculated in response to a request associated with the meta data element.