Centralized Service Coordination via SDK Adapter

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developers face the challenge of configuring and maintaining multiple versions of mobile applications to interface with various third-party services across different platforms, leading to inefficiencies for both developers and service providers, and limiting user access to features.

Innovation Solution

A centralized system coordinates services across multiple providers by incorporating an SDK within the application, allowing transaction requests to be processed through a centralized platform that determines the appropriate third-party service for execution, eliminating the need for application customization across platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple versions of the application are developed for different service providers, then compatibility with various third-party services is improved, but device complexity and maintenance burden increase

Engineering Contradiction:
Improvecompatibility with third-party servicesVSAvoidapplication version complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal application architecture that can interface with multiple third-party service providers through a single codebase. The system uses a standardized interface layer that abstracts provider-specific implementations, allowing the application to universally communicate with different payment platforms, leaderboards, and other services without requiring separate version development for each provider.

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

Solution Approach 2:

The patent introduces an intermediary layer or adapter pattern that mediates between the core application logic and various third-party service providers. This intermediary handles the translation and adaptation between different service interfaces and the application's internal structure, eliminating the need for multiple application versions while maintaining compatibility with diverse service providers.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the application is customized for each platform, then service integration quality is improved, but development time and cost increase

Engineering Contradiction:
Improveservice integration qualityVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the application into modular components: a core application layer, an adapter layer for service provider-specific implementations, and a configuration layer. This segmentation allows the core application to remain unchanged while only the adapter layer needs to be configured for different providers, significantly reducing development time while maintaining integration quality through dedicated adapter implementations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent utilizes parameter-based configuration and runtime switching to adapt to different service providers without code changes. By changing configuration parameters and using factory patterns or dependency injection, the application can dynamically adapt to different providers, maintaining high integration quality while eliminating repetitive customization development.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If a centralized system coordinates services, then ease of operation is improved, but system complexity increases

Engineering Contradiction:
Improveservice coordination simplicityVSAvoidcentralized system complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements a self-service centralized coordination system where the system automatically discovers, selects, and routes to appropriate service providers based on predefined rules and configuration. The coordination logic includes self-configuration capabilities and automatic adapter selection, reducing the need for manual intervention while managing system complexity through automated decision-making algorithms and rule-based routing.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10382586B2Coordinating services across multiple providers
Publication Date: 2019.08.13 VUNGLE INC
  • US10382586B2 patent drawing
  • US10382586B2 patent drawing
  • US10382586B2 patent drawing

AI summary

Systems and methods are disclosed for coordinating services across multiple providers. In one implementation, a processing device receives, from an application, a request to initiate a transaction, processes the request in relation to one or more service providers to identify a service provider with respect to which the transaction is to be executed, provides the request to the service provider, receives transaction outcome from the service provider with respect to the transaction, and provides the transaction outcome to the application.