Intermediary Service Facade for Request Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Datacenters face inefficiencies due to providing both generalized and business-specific services, leading to resource burdens and processing challenges when handling service requests from client systems.

Innovation Solution

An intermediary service is introduced to process service requests and determine which registered services are best suited to handle the requests, offloading generic system functionality and processing tasks to alleviate these burdens, allowing for service-specific processing and efficient resource management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If datacenters provide both generalized system services and business-specific services, then service functionality is comprehensive, but system efficiency deteriorates due to resource burdens and processing challenges

Engineering Contradiction:
Improveservice functionalityVSAvoidsystem efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments service processing into two distinct parts: generic system functionality handled by a business facade service and service-specific functionality handled by individual registered services. This segmentation allows the system to maintain comprehensive functionality while improving efficiency by directing requests to appropriate processing components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The business facade service acts as an intermediary between client systems and registered services. It receives service requests, processes generic system functionality, determines which registered service should handle the request, and forwards the processed request accordingly. This intermediary approach resolves the contradiction by centralizing common processing tasks.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If service providers handle all service requests directly, then service-specific processing is accurate, but resource load on providers increases

Engineering Contradiction:
Improveservice-specific processing accuracyVSAvoidresource load
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts generic system functionality processing from individual service providers and consolidates it in the business facade service. This extraction reduces the resource load on service providers while maintaining their ability to perform accurate service-specific processing when needed.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Service providers register their services and functional capabilities with the business facade service, enabling the facade to autonomously determine and route requests to appropriate providers. This self-service mechanism reduces manual configuration and resource overhead.

Inventive Principle:
Principle #25Self-service

3Productivity

If an intermediary service processes all requests, then resource utilization is optimized, but system complexity increases

Engineering Contradiction:
Improveresource utilizationVSAvoidsystem architecture
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The business facade service is designed with multi-functionality, handling service request reception, generic functionality processing, service determination, and request forwarding. This universal approach consolidates multiple functions in a single component, improving resource utilization while managing complexity through functional integration.

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

Data Source

PatentUS8407346B2Service facade design and implementation
Publication Date: 2013.03.26 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8407346B2 patent drawing
  • US8407346B2 patent drawing
  • US8407346B2 patent drawing

AI summary

In one embodiment, a computer system receives registration information for available services provided by a service provider. The registration information includes information identifying functionality provided by the available services, and the registration information is used to register the available services with the intermediary service. The computer system receives a service request from a client computer system identifying a function that is to be performed by at least one of the available services registered at the intermediary service. The computer system determines which of the registered available services is configured to provide the functionality requested by the client and processes the received service request using various system functionality components, so that the service request is configured for service-specific processing provided by a registered available service. The computer system also sends the processed service request to the registered service determined to be configured to provide the functionality requested by the client.