Standardized Declarative Service Interface Definition

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current solutions for integrating web services with client-side applications face challenges in delivering a rich user experience due to differences in service capacity and defining clear, easily implementable interfaces between clients and services.

Innovation Solution

A standardized, declarative format using a hierarchical tag-based language, such as XML, is introduced to describe services, including common and service-specific properties, allowing for easy extension and addition of new services by defining their properties and functionalities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If loose integration hooks are used to enable service integration, then service capacity differences can be accommodated, but user experience consistency deteriorates

Engineering Contradiction:
Improveservice capacity accommodationVSAvoiduser experience consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies universality by creating a standardized service interface definition format that can accommodate multiple different service types and capacities while maintaining consistent integration patterns. This universal interface framework allows diverse services to be integrated without compromising user experience consistency, resolving the contradiction between adaptability and reliability.

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

2Reliability

If service interfaces are clearly defined, then integration reliability improves, but implementation complexity increases

Engineering Contradiction:
Improveinterface definition clarityVSAvoidimplementation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent changes the parameter of interface definition from complex executable code to a simpler declarative format with standardized properties. This parameter transformation maintains clear interface definitions for reliability while reducing implementation complexity through the use of lightweight, standardized service interface definitions rather than complex code-based interfaces.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If standardized service descriptions are implemented, then integration ease improves, but service-specific functionality may be lost

Engineering Contradiction:
Improveintegration easeVSAvoidservice-specific functionality
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent applies segmentation by dividing service interface definitions into distinct property elements that can independently describe both standardized aspects and service-specific functionalities. This segmentation allows the standardized format to maintain ease of integration while preserving the ability to define unique service characteristics through individual property elements.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8898580B2Definition for service interface
Publication Date: 2014.11.25 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8898580B2 patent drawing
  • US8898580B2 patent drawing
  • US8898580B2 patent drawing

AI summary

Various embodiments provide a model through which service providers can describe offered services using a standardized format. In one or more embodiments, the standardized format is declarative and enables service providers to describe their associated services in a standardized way. In at least some embodiments, the standardized format includes a set of common service properties that are shared across multiple different services. Additionally, service specific properties can be described in addition to the common service properties. In one or more embodiments, existing services can be extended by including, in the standardized format, a description of an extension. In one or more other embodiments, new services can be added for consumption by simply including a description of the new service using the standardized format.