Asynchronous Web Service Notification Conversion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing web services rely on synchronous communication methods, which are expensive and impractical for wireless devices due to limited resources and high data traffic costs, and lack notification-based capabilities, leading to inefficient information delivery.
Innovation Solution
A system and method to convert schema-based synchronous web services into asynchronous web services, utilizing a subscription module, artifact module, and integration module to generate an asynchronous service description, enabling notification-based communication by transforming synchronous service definitions into asynchronous ones.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If synchronous communication methods are used for web services, then service reliability and response accuracy are improved, but communication cost and latency increase significantly for wireless devices
Solution Approach 1:
The patent applies dynamics by transforming the static synchronous communication model into a dynamic asynchronous notification model. The system dynamically adapts the communication pattern based on data availability - pushing notifications only when data changes occur, rather than maintaining continuous synchronous connections. This resolves the contradiction by making communication cost variable rather than fixed, reducing energy loss while preserving reliability through event-driven notifications.
Solution Approach 2:
The patent implements periodic action through the use of scheduled polling as a fallback mechanism. When push notifications are not available or acknowledged, the system periodically retries data delivery at intervals. This periodic retry mechanism ensures service reliability is maintained while avoiding continuous expensive synchronous communication, as polling only occurs when necessary rather than constantly.
2Measurement precision
If synchronous request/response web services are used, then data accuracy is ensured, but latency and user wait time increase
Solution Approach 1:
The patent applies preliminary action by pre-processing and validating data on the server side before pushing notifications to clients. Data is prepared, formatted, and verified for accuracy in advance, so when the notification is pushed, the client receives already-validated accurate data immediately without needing to wait for synchronous verification. This eliminates latency while preserving data accuracy through upfront validation.
Solution Approach 2:
The patent introduces an intermediary notification service layer that mediates between the data source and clients. This intermediary validates and buffers data, then pushes it to multiple clients simultaneously through asynchronous notifications. This mediator ensures data accuracy through centralized validation while eliminating the need for each client to wait for individual synchronous responses, thus reducing latency.
3Loss of information
If wireless devices repeatedly poll the server for data, then information is eventually retrieved, but bandwidth consumption and connection time increase
Solution Approach 1:
The patent applies self-service by implementing a server-side push notification system that automatically delivers data to clients without requiring their active participation. The server monitors for data changes and autonomously pushes updates to subscribed clients, eliminating the need for clients to repeatedly poll. This ensures information is delivered reliably while minimizing bandwidth consumption, as data is transmitted only when changes occur rather than on every poll cycle.
4Adaptability or versatility
If standard request/response web service protocols are used, then service compatibility is maintained, but adaptability to notification-based communication is lost
Solution Approach 1:
The patent applies universality by designing a notification service that maintains compatibility with standard web service protocols while adding push notification functionality. The system can operate in both synchronous request/response mode and asynchronous push notification mode, making it universally applicable to different client types and scenarios. This achieves adaptability to notification-based communication without increasing implementation complexity, as the same service infrastructure supports both communication paradigms.
Data Source
AI summary
A system and method for converting a schema based synchronous service to a schema based asynchronous service. The asynchronous service for implementing on a server configured for communication with a respective client over a network. The system and method comprising a subscription module for identifying a port type with each notification method added to a description of the synchronous service and for associating a subscription operation with the identified port type. The system and method can also include an artifact module for generating at least one conversion artifact related to the added notification method, the conversion artifact configured for use by a developer to assist in developing the supporting clients of the asynchronous service as well as the asynchronous service itself. The system and method can also include an integration module for combining the notification methods and subscription operations and conversion artifacts to produce a description of the asynchronous service. The developer uses the asynchronous service description for generating a service implementation of the schema based asynchronous service to include appropriate business logic for subsequent installation in the server as an asynchronous service interface.