Web Service Commercial Extensions for Client Maintenance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The adoption of commercial web services is hindered by the need for significant client development due to various technical options in security, quality of service, and other characteristics, as well as changes in service interfaces over time, which introduce substantial risk and cost for enterprises.
Innovation Solution
The implementation of commercial extensions to web service interactions, including a special client component that supports software updates and audit logging, and a maintenance protocol between the subscriber and provider to facilitate client updates and usage reconciliation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If commercial web services are adopted with multiple providers and technical options, then service functionality and versatility are improved, but client development complexity and maintenance cost increase significantly
Solution Approach 1:
The patent introduces a service registry and standardized interface layer as an intermediary between multiple web service providers and the client. This mediator abstracts the complexity of interacting with multiple providers by providing a unified access point, allowing the client to interact with diverse services through consistent interfaces while the registry manages provider-specific implementations and technical options.
Solution Approach 2:
The patent creates universal client components and standardized service interfaces that can work with multiple different web service providers. The client architecture is designed with pluggable adapters and configuration mechanisms that enable a single client implementation to access functionality from various providers without requiring separate development for each provider, thus achieving multi-functionality through universal design.
2Reliability
If service interfaces and technical modes are updated over time, then service quality and reliability are improved, but downstream development effort and maintenance risk increase
Solution Approach 1:
The patent implements forward compatibility mechanisms and versioning strategies in advance. The service interface definitions include version identifiers and evolution paths are planned beforehand. When service interfaces need updates, the changes are prepared and communicated through the service registry in advance, allowing clients to anticipate and prepare for updates without emergency development efforts, thus reducing maintenance time while maintaining service quality.
Solution Approach 2:
The patent creates dynamic service interfaces that can adapt to changes without requiring rigid reconfiguration. The client architecture includes automatic service discovery and interface adaptation capabilities that allow the system to dynamically adjust to updated service interfaces. This dynamic approach enables service quality improvements through interface updates while minimizing the downstream development effort required, as the system automatically handles adaptations rather than requiring manual maintenance for each change.
3Ease of manufacture
If current web service standards are used without business enablers, then technical implementation is simpler, but commercial viability and invoicing reconciliation are compromised
Solution Approach 1:
The patent merges technical web service interfaces with business enablers into a unified service framework. Business functionality such as usage tracking, invoicing reconciliation, and commercial terms management are integrated directly into the service interface layer rather than being separate concerns. This combination maintains technical implementation simplicity by using the same standardized interfaces while adding commercial capabilities, thus achieving both ease of implementation and commercial viability simultaneously.
Data Source
AI summary
A system for providing granular functionality called web services to commercial customers includes among other things a client to issue service requests and receive responses, a web server configured to accept and process service requests, and a means of accounting for usage. The current art specifies standards for functional interactions between web service clients and servers. A set of commercial extensions are defined herein to enable maintenance interactions. This “maintenance protocol” includes operations such as client software that is self-updating in response to server changes and the capability of reconciling client usage logs with service provider invoicing.


