Swagger-Based Service Model Mapping for Orchestration Integration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The existing gap between REST API data models from domain controllers and service orchestration systems necessitates manual adapter creation, requiring deep knowledge of both systems, leading to a complex, time-consuming, and costly process.

Innovation Solution

A service model engine that generates service delivery models from vendor API swagger, automatically determining API endpoints, methods, and resource specifications, and mapping delivery parameters to align with domain controller interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual adapter creation is used to bridge REST API data models and service orchestration models, then integration between domain controllers and service orchestration systems is achieved, but the process becomes complex, time-consuming, and costly

Engineering Contradiction:

Improveintegration compatibilityVSAvoidadapter creation complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system enables self-service by allowing the service orchestration system to automatically generate adapters through model transformation. The domain controller's REST API swagger documentation is automatically parsed and transformed into service orchestration models without requiring manual adapter creation, making the system self-configuring and eliminating complex manual integration work

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary transformation layer that converts REST API data models into service orchestration models. This intermediary process automatically translates between the two different data model formats, serving as a mediator that bridges the gap without requiring manual intervention or complex adapter development

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If manual adapter creation is used to translate requests between service orchestration system and domain controller, then data model alignment is achieved, but implementation time and cost increase significantly

Engineering Contradiction:

Improvedata model alignmentVSAvoidimplementation time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-generating service delivery models from domain controller swagger documentation. These models are prepared in advance and stored for reuse, eliminating the need for repeated manual adaptation work when integrating new domain controllers or services

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The automatic model transformation process enables self-service by allowing the system to autonomously generate and update service delivery models based on swagger documentation, eliminating manual intervention and significantly reducing implementation time for new integrations

Inventive Principle:

Principle #25Self-service

3Adaptability or versatility

If custom adapters are developed to bridge API data models and service models, then integration functionality is achieved, but development cost and expertise requirements increase

Engineering Contradiction:

Improveintegration functionalityVSAvoiddevelopment cost

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system eliminates the need for expert developers by enabling self-service model generation. The automatic transformation from swagger documentation to service delivery models requires no specialized knowledge of both REST APIs and service orchestration, making the process accessible to general developers and reducing development costs

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary automated transformation process that mediates between REST API specifications and service orchestration models. This intermediary automatically handles the complex translation logic, eliminating the need for expensive custom adapter development while maintaining full integration functionality

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12537881B2Service model engine(s) for generating service delivery models from vendor API swagger

Publication Date: 2026.01.27 ORACLE INT CORP

AI summary

Various embodiments of the present technology generally relate to systems and methods for providing a service model engine. In an aspect a method includes identifying, by a service model engine, a swagger file from a network vendor and parsing the swagger file for API endpoints. The service model engine may generate resource specifications based on the API endpoints and may generate delivery actions for each API endpoint. Each delivery action may include delivery parameters for each API endpoint, The service model engine may also map each of the delivery parameters to corresponding characteristics in the resource specifications to generate parameter mappings. The service model engine may generate a service delivery model including the resource specifications, the delivery actions, and the parameter mappings, where the service delivery model is used by a service orchestration system to deliver respective services.