Shared Runtime Environment for Multi-Client Service Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Businesses face challenges in efficiently and cost-effectively providing customized business services to multiple clients using proprietary software systems, as developing centralized software suites is expensive and maintaining them requires significant resources, while piecemeal approaches may lack centralized control and integration.

Innovation Solution

Implementing a shared runtime environment managed by a service manager that identifies and routes service requests to appropriate providers based on client configuration data, allowing multiple business organization clients to receive services in a unified and customizable manner, with features like authentication, data processing, and error handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If centralized software suites are developed and maintained, then complete control over design, maintenance, and compatibility is achieved, but development cost and resource requirements increase significantly

Engineering Contradiction:
Improvecontrol over design, maintenance, and compatibilityVSAvoiddevelopment cost and resource requirements
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Multiple service providers and their services are merged into a single shared runtime environment, allowing multiple businesses to share infrastructure resources while maintaining logical separation through configuration data and service routing mechanisms

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The shared runtime environment serves multiple businesses simultaneously, providing a universal platform that can accommodate different service providers, clients, and configurations without requiring separate dedicated systems for each business

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

2Device complexity

If piecemeal approach with out-of-the-box software applications is adopted, then cost savings are achieved, but centralized control and integration are lost

Engineering Contradiction:
Improvecost savingsVSAvoidcentralized control and integration
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

A service manager acts as an intermediary between multiple service providers and clients, centralizing control and integration functions while allowing individual service providers to maintain their independence and cost-effectiveness

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments services into separate service providers while maintaining a unified runtime environment, allowing independent service development and deployment while achieving centralized management through the service manager

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If proprietary software systems are developed for each business, then complete customization and control are achieved, but development expense and resource consumption increase

Engineering Contradiction:
Improvecustomization capabilityVSAvoiddevelopment expense and resource consumption
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Each service provider maintains their own configuration data and service-specific customization while sharing common infrastructure resources, allowing localized customization without requiring complete proprietary systems for each business

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8239553B2Providing services for multiple business consumers
Publication Date: 2012.08.07 ENT SERVICES DEV CORP LP
  • US8239553B2 patent drawing
  • US8239553B2 patent drawing
  • US8239553B2 patent drawing

AI summary

Methods, systems, and apparatus, including computer program products, for providing services to business organization clients involve receiving a request for a particular service, identifying configuration data relating to the request, sending a service request to a service provider of the service, and providing the service to a service consumer in accordance with data returned in response to the service request. The service consumer is identified from the request for a particular service. Configuration data corresponding to the service consumer is identified. The service provider for the service and resource data corresponding to the service are identified from the configuration data. A service request is sent to the service provider and data relating to the service is returned from the service provider. The service is provided to the service consumer in a shared runtime environment based at least in part on the received data relating to the service.