Service Platform Integrating Legacy Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Integrating web services and local services with client applications is challenging, leading to complex coding scenarios and inconsistent user experiences due to the difficulty in exposing services in a graceful and consistent manner.

Innovation Solution

A multi-layered service platform is introduced, comprising a global integration layer, a common control integration layer, and a custom integration layer, which enables seamless integration of services across various applications, including legacy applications unaware of these services, by providing a generic user interface, common controls, and customizable user interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If services are integrated with client applications using traditional methods, then service functionality is provided, but coding complexity increases and user experience consistency deteriorates

Engineering Contradiction:
Improveservice integration capabilityVSAvoidcoding complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a service integration layer as an intermediary component that sits between the service providers and client applications. This layer handles service discovery, binding, and invocation automatically, eliminating the need for complex coding in applications while maintaining service integration capabilities. The integration layer acts as a mediator that manages the complexity internally while presenting a simple interface to applications.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system architecture is segmented into distinct layers: service providers, service integration layer, and client applications. By separating service integration functionality from applications, the patent reduces coding complexity in applications while maintaining versatile service integration. Each layer has specific responsibilities, with the integration layer handling complex service management tasks independently.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If services are integrated with client applications using traditional methods, then service functionality is provided, but user experience consistency deteriorates

Engineering Contradiction:
Improveservice integration capabilityVSAvoiduser experience consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The service integration layer provides universal service access mechanisms that work consistently across different client applications. It implements standardized service discovery, binding, and invocation patterns that ensure uniform user experience regardless of which application or service is being used. The integration layer acts as a universal interface layer that abstracts service-specific details.

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

Solution Approach 2:

The patent enforces homogeneous service access patterns across all client applications through the integration layer. All services are discovered, bound, and invoked through consistent mechanisms and interfaces defined by the integration layer, ensuring that users experience services in a uniform manner across different applications. This homogenization of access patterns guarantees user experience consistency.

Inventive Principle:
Principle #33Homogeneity

3Adaptability or versatility

If legacy applications are made aware of services, then service integration is achieved, but application complexity increases

Engineering Contradiction:
Improveservice awarenessVSAvoidapplication structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts service integration functionality from legacy applications and places it in a dedicated service integration layer. This extraction allows legacy applications to remain simple and unaware of service complexities, while the integration layer handles all service-related operations. The applications only interact with the integration layer through simple interfaces, maintaining their original simplicity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The service integration layer provides self-service capabilities that automatically manage service integration without requiring application modifications. The layer autonomously performs service discovery, binding, and invocation, allowing legacy applications to benefit from service integration without becoming aware of or complex due to service mechanisms.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8146110B2Service platform for in-context results
Publication Date: 2012.03.27 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8146110B2 patent drawing
  • US8146110B2 patent drawing
  • US8146110B2 patent drawing

AI summary

Various embodiments provide a service platform that integrates services, such as web services and/or local services, across a variety of applications. In at least some embodiments, services can be integrated with legacy applications that are “unaware” of such services, as well as applications that are aware of such services.