Web Service Middleware Dynamic Provider Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Service providers are limited by static business contracts with content providers, preventing dynamic selection based on customer profiles or performance, and lack the ability to leverage market-driven infrastructure, especially with the adoption of universal service interface standards.

Innovation Solution

A Web services-oriented middleware architecture that integrates performance monitoring and contextual conditions for dynamic selection of content providers, using metarules for workflow filtering and ranking, and evaluator processes to assess business and service-level parameters.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If static business contracts with content providers are used, then service delivery is enabled, but dynamic selection based on customer profiles or performance is prevented

Engineering Contradiction:
Improvedynamic service selectionVSAvoidservice selection mechanism
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic service selection by replacing static contracts with a dynamic service selection mechanism that evaluates content providers based on real-time customer profiles, performance metrics, and contextual conditions. The service provider can dynamically switch between multiple content providers using standard web service interfaces, enabling adaptability while maintaining manageable complexity through automated evaluation processes.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If tightly integrated third-party services are used, then service delivery is enabled, but leverage of market-driven infrastructure is restricted

Engineering Contradiction:
Improvemarket-driven service infrastructureVSAvoidservice integration
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent adopts universal web service interface standards (such as SOAP, REST, and UDDI) that enable content providers to be accessed through standardized protocols rather than proprietary integrations. This universal interface allows the service provider to leverage market-driven infrastructure by selecting from multiple content providers using common standards, improving ease of integration while enabling market flexibility.

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

3Adaptability or versatility

If multiple content providers are integrated, then service reach is expanded, but service implementation and management costs increase

Engineering Contradiction:
Improveservice reachVSAvoidservice management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements self-service mechanisms where the service provider automatically evaluates and selects content providers based on predefined criteria such as performance metrics, customer profiles, and contextual conditions. The system autonomously manages multiple content providers through automated service selection and routing, expanding service reach while reducing manual management overhead through intelligent decision-making algorithms.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7707173B2Selection of web services by service providers
Publication Date: 2010.04.27 X CORP
  • US7707173B2 patent drawing
  • US7707173B2 patent drawing
  • US7707173B2 patent drawing

AI summary

A Web services-oriented service provider middleware architecture and implementation is provided that integrates the performance monitoring of individual CPs, along with other dynamic contextual conditions, in the automatic selection of appropriate CPs. In the architecture, a CP's performance is evaluated not only in terms of network or service-level parameters, but also via other business processes (e.g., complaint handling). The selection of multiple Web services occurs through an initial filtering of a set of feasible workflows for each task depending on business agreements and end user needs, and a subsequent dynamic context-based selection of the most appropriate workflow. A workflow filtering and ranking engine uses metarules to guide the optimisation process and help in selecting and ranking the feasible workflows. The component services in the workflows are evaluated by evaluator processes of information sources. The workflow engine outputs the workflows in their preference ranking. At runtime, if the workflow and/or its components meet all the runtime requirements (performance, for example), then the workflow is selected and executed.