Metadata-Driven Interface Orchestration for Telecommunication Integration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current integration between telecommunication systems requires manual coding for static mapping of internal to external business models and predefined activities, making it time-consuming and inefficient.

Innovation Solution

A metadata-driven system that defines job items, specifications, and lists in a master enterprise catalogue to automatically generate job plans and interfaces with external systems, enabling dynamic orchestration and mapping based on business requests and use cases.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual coding is used for static mapping of internal to external business models, then integration between telecommunication systems can be achieved, but development time and complexity increase significantly

Engineering Contradiction:

Improveintegration reliabilityVSAvoiddevelopment time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent replaces manual coding mechanisms with automated metadata-driven generation. Instead of manually writing code to map internal business models to external interfaces, the system uses metadata definitions to automatically generate the mapping code, thereby reducing development time while maintaining integration reliability.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system enables self-service through automated code generation from metadata. The metadata-driven interface generator automatically creates interface code based on predefined metadata, allowing the system to generate its own integration code without requiring extensive manual programming intervention.

Inventive Principle:

Principle #25Self-service

2Productivity

If pre-defined activities and dependencies are used for orchestration, then integration can be accomplished per use-case, but adaptability to new business models decreases

Engineering Contradiction:

Improveintegration efficiencyVSAvoidadaptability to new business models

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent introduces dynamic adaptability through metadata-driven generation. Instead of using static pre-defined activities, the system dynamically generates interface code based on metadata that can be updated to reflect new business models. This allows the system to adapt to changing requirements without requiring redefinition of fundamental orchestration mechanisms.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system achieves adaptability by changing metadata parameters rather than rewriting code. When new business models are required, the metadata definitions are updated with new parameters and structures, and the metadata-driven interface generator automatically produces updated interface code, enabling flexible adaptation to new requirements.

Inventive Principle:

Principle #35Parameter changes

3Stability of the object's composition

If static code mapping is used for internal to external models, then integration structure is established, but ease of modifying integration decreases

Engineering Contradiction:

Improveintegration structure stabilityVSAvoidease of modifying integration

Core Design Contradiction:

Stability of the object's compositionVSEase of manufacture

Solution Approach 1:

The patent segments the integration structure into separate components: stable metadata definitions and generated interface code. The metadata layer provides structural stability while the generated code can be easily modified by regenerating from updated metadata, separating the concerns of structural stability and modification ease.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system replaces manual code modification with automated code regeneration. Instead of manually modifying integration code to adapt to changes, the system uses metadata-driven generation to automatically create updated code, making modifications easier while maintaining structural stability through consistent metadata-based approaches.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS10832191B1System, method, and computer program for metadata driven interface orchestration and mapping

Publication Date: 2020.11.10 AMDOCS DEV LTD

AI summary

A system, method, and computer program product are provided for metadata driven interface orchestration and mapping. In operation, a system defines a plurality of job items in a master enterprise catalogue by mapping all possible business requests to one or more pre-defined job items. The system defines job specifications in the master enterprise catalogue by mapping the plurality of job items to one or more pre-defined job specifications. Further, the system defines a job list in the master enterprise catalogue by building a sequence of outgoing requests based on possible use cases and the job specifications. The system defines an order context associated with one or more orders. Additionally, the system automatically generates a job plan including a plurality of activities utilizing the job list from the master enterprise catalogue and the order context. Moreover, the system automatically generates interfaces with a plurality of external systems based on the job plan including the plurality of activities.