Hosted Platform Wrapper Protocol for Service Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for integrating multiple service providers across various domains require significant custom coding and effort, lacking a unified platform for license management, which is time-consuming and inefficient.

Innovation Solution

A hosted platform with a metadata-based approach and a wrapper protocol (iON TPFP) that standardizes integration across services, using a registration module, API interface, and processor modules to reduce custom integration efforts and manage licenses through a centralized module.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If custom integration methods are used to integrate multiple service providers, then integration flexibility is improved, but integration time and effort increase significantly

Engineering Contradiction:
Improveintegration flexibilityVSAvoidintegration time and effort
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements a universal integration framework that provides a common set of integration capabilities applicable across multiple service providers and domains. The framework includes standardized components for authentication, data exchange, and service orchestration that can be reused across different integrations, eliminating the need to write custom integration code for each service provider while maintaining flexibility through configurable parameters and metadata-driven adaptation.

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

2Adaptability or versatility

If multiple custom integrations are developed for different vendors, then vendor-specific functionality is improved, but code reuse decreases

Engineering Contradiction:
Improvevendor-specific functionalityVSAvoidcode reuse
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the integration logic into modular, reusable components that can be independently developed and configured. The integration framework divides vendor-specific functionality into separate configurable modules (such as authentication modules, data transformation modules, and API adapters) that can be selectively assembled for different service providers. This segmentation enables high code reuse while maintaining vendor-specific capabilities through configuration rather than custom code development.

Inventive Principle:
Principle #1Segmentation

3Productivity

If a unified platform for license management is implemented, then license management efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvelicense management efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary license management layer that sits between the integration framework and multiple service providers. This intermediary component handles all license-related operations (acquisition, validation, renewal, and revocation) centrally, providing a unified interface for license management across different vendors. The intermediary abstracts the complexity of managing multiple vendor licenses, presenting a simplified interface to users while handling the underlying complexity of interacting with various vendor license systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP3512175B1System and protocol for integrating multiple service providers across various domains using a platform
Publication Date: 2022.09.28 TATA CONSULTANCY SERVICES LTD
  • EP3512175B1 patent drawingFigure 1
  • EP3512175B1 patent drawingFigure 2
  • EP3512175B1 patent drawingFigure 3a

AI summary

A system and protocol for integrating a plurality of service providers across a plurality of domains with an application using a hosted platform have been described. The system involves registration of metadata corresponding to the service providers, their services, their types and their set of parameters. When a new integrating application is provided, then it also includes a wrapper protocol. The wrapper protocol includes six predefined methods. The hosted platform in turn can execute the request of the "integrating application" by internally connecting with the plurality of service providers across a plurality of domains and provide the output in a standard format. Since the wrapper protocol standardizes the format of communication (input & output), hence it reduces effort substantially at the end of the integrating application. The ability of the platform to increase the list of service providers is augmented as it relies on metadata for request generation and invocation.