Service Grid Architecture for Web Service Reliability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The adoption of commercial web services is hindered by functional disparities among providers, requiring technical reimplementation when switching, and reliability issues due to variability in client software, which increases complexity and costs for enterprises.

Innovation Solution

A service grid architecture where a single provider manages access to multiple service sources, standardizing request/response protocols, adapting technology, and selecting available sources transparently to clients, ensuring reliability and simplifying business relationships.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If enterprises use multiple service providers to mitigate reliability risk, then reliability is improved, but device complexity and management difficulty increase

Engineering Contradiction:
Improveservice reliabilityVSAvoidbusiness relationship complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a service grid as an intermediary layer between clients and multiple service providers. The service grid abstracts the complexity of managing multiple providers by presenting a unified interface to clients while handling provider selection, load balancing, and failure recovery internally. This resolves the contradiction by maintaining high reliability through multiple providers without exposing clients to the complexity of managing multiple business relationships.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If enterprises switch between service providers, then adaptability is improved, but technical reimplementation is required increasing loss of time and cost

Engineering Contradiction:
Improveprovider switching capabilityVSAvoidtechnical reimplementation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The service grid implements a universal interface layer that works with multiple service providers simultaneously. Clients interact with a standardized service grid interface that can route requests to different providers based on service level agreements, performance metrics, or failover conditions. This eliminates the need for technical reimplementation when switching providers, as the service grid handles provider abstraction and adaptation transparently.

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

3Adaptability or versatility

If commercial web services are adopted without standardization, then adaptability is improved, but manufacturing precision and measurement precision deteriorate due to functional disparities

Engineering Contradiction:
Improveservice varietyVSAvoidservice functional equivalence
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The service grid enforces homogeneity by requiring all service providers to conform to standardized service level agreements and interface specifications. The grid performs normalization and adaptation of provider responses to ensure functional equivalence across different providers. This allows the system to maintain service variety while ensuring that all services meet consistent functional and quality standards.

Inventive Principle:
Principle #33Homogeneity

Data Source

PatentUS8756320B2Web service grid architecture
Publication Date: 2014.06.17 GRID NOVA
  • US8756320B2 patent drawing
  • US8756320B2 patent drawing
  • US8756320B2 patent drawing

AI summary

A system for providing granular functionality called web services to commercial customers includes a web server configured to accept service requests from software application clients, functional implementations of the services, and a means of accounting for usage. The service grid architecture makes practical a reliable commercial provider of web services in the face of unreliable sources of functional implementations. This is accomplished through the commoditization of multiple implementation sources per service, standard forms for each service to which a plurality of sources is adapted, and a rules based approach to source selection per service call.