Service Definition Document Framework for Blended Service Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developers face difficulties in creating and deploying software applications that integrate multiple services from different service providers due to cumbersome sandbox environments and the need for multiple software development kits, which hinders efficient development and testing of blended applications.

Innovation Solution

A service definition document (SDD) framework is introduced, allowing for the creation, testing, and deployment of blended services by defining and executing multiple service endpoints through a graphical blended service creation environment and service execution environment, using XML structure, and service endpoint simulators to simulate service endpoints locally.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If developers use sandbox environments provided by service providers for testing, then they can access and test services, but the process becomes difficult and time-consuming requiring registration or payment and lacking full-featured interfaces

Engineering Contradiction:
Improveease of testingVSAvoidtime for testing
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent creates local copies of service endpoints through service endpoint simulators that replicate the functionality of remote services. These simulators allow developers to test blended services locally without needing to register with or pay sandbox environments, eliminating the time-consuming registration process while providing full-featured testing interfaces.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The service endpoint simulators act as intermediaries between the developer's local environment and the remote service providers. These simulators translate local test requests into appropriate service endpoint interactions, enabling easy and rapid testing without direct dependency on the actual service providers or their sandbox environments.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If developers use multiple different software development kits for accessing multiple services, then they can integrate services from different providers, but the complexity of development increases

Engineering Contradiction:
Improveability to integrate multiple servicesVSAvoidcomplexity of development
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a universal service endpoint simulator framework that can simulate multiple different service endpoints from various service providers using a single unified approach. Instead of requiring separate software development kits for each service provider, the simulator framework provides a common interface and toolset that handles all service endpoint simulations, thereby reducing development complexity while maintaining the ability to integrate multiple services.

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

Solution Approach 2:

The patent merges the functionality of multiple service endpoint simulators into a unified framework that manages and coordinates simulations of different service endpoints. This consolidation allows developers to work with multiple services through a single integrated environment rather than managing multiple separate development kits, thus reducing overall development complexity.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If developers write code to separately access each service from multiple providers, then they can integrate services, but the effort and time required for development increases

Engineering Contradiction:
Improveability to access multiple servicesVSAvoiddevelopment efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The service endpoint simulators create local copies of service endpoint interfaces that mirror the actual remote services. Developers can write code once against these local copies and test it thoroughly before deployment, eliminating the need to rewrite or re-test for each different service provider. This copying approach significantly improves development efficiency while maintaining the ability to access multiple services.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The simulators allow developers to perform preliminary testing and validation of service integration code locally before actual deployment. By pre-testing against simulated service endpoints, developers can identify and fix issues early in the development process, thereby improving overall productivity and reducing the time required for final deployment to production environments.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8504989B2Service definition document for providing blended services utilizing multiple service endpoints
Publication Date: 2013.08.06 INFOSYS LTD
  • US8504989B2 patent drawing
  • US8504989B2 patent drawing
  • US8504989B2 patent drawing

AI summary

A service definition document (SDD) framework is provided for defining blended services that utilize multiple service endpoints. The SDD framework can comprise a first category that defines a service endpoint representing a blended service, a second category that defines a plurality of service endpoints utilized by the blended service, and a third category that defines execution of the blended service. Blended services can be provided by creating a model of a blended service and saving a representation of the model of the blended service in a service definition document (SDD) framework. A blended service defined in a SDD framework can be executed by receiving the SDD and executing the blended service as defined by the SDD using a service execution environment (SEE).