Web Services Runtime Protocol Hibernation for Message Processing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The existing Web services message processing runtime frameworks lack efficiency in handling business models requiring confidentiality, ordered message processing, and support for diverse transport protocols, while also being scalable and capable of hibernation to manage out-of-order messages.

Innovation Solution

The improved runtime framework eliminates the mapping registry and context intermediary, redesigns protocols to be state-less, and supports hibernation, enabling efficient processing and storage of protocol state information externally, allowing for the implementation of WS-Reliable Messaging and other extensions like WS-Security and WS-Addressing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the existing runtime framework uses mapping registry and context intermediary to handle message processing, then it can support multiple protocols and business models, but it results in reduced processing efficiency and increased system complexity

Engineering Contradiction:

Improvesupport for diverse business models and protocolsVSAvoidmessage processing efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent extracts and removes the mapping registry and context intermediary from the message processing framework. By taking out these intermediary components, the system eliminates the overhead they introduce while maintaining protocol support through direct protocol implementation in the stateless protocol class, thereby improving processing efficiency without sacrificing adaptability

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the protocol handling into independent stateless protocol classes, each responsible for specific protocol operations. This segmentation allows protocols to be processed independently without requiring centralized registry lookup, improving efficiency while maintaining the ability to support multiple protocols through modular class design

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If the runtime framework maintains protocol state information within protocols during execution, then it can handle complex business logic, but it prevents hibernation and reduces scalability

Engineering Contradiction:

Improvehandling of complex business logicVSAvoidprotocol state management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements protocols as stateless, disposable objects that can be created, used, and discarded independently. Each protocol operation creates a new protocol instance that performs its function without maintaining persistent state, enabling hibernation and improving scalability while handling complex business logic through method-level operations rather than object-level state

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

3Reliability

If the framework processes messages in strict order with synchronous protocol execution, then it ensures reliable message processing, but it cannot effectively manage out-of-order messages

Engineering Contradiction:

Improvemessage processing reliabilityVSAvoidhandling of out-of-order messages

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces dynamic message processing where the framework can adapt between synchronous and asynchronous processing modes based on message requirements. Out-of-order messages are handled through dynamic queue management and selective processing, allowing the system to maintain reliability for ordered messages while accommodating out-of-order scenarios through flexible protocol execution timing

Inventive Principle:

Principle #15Dynamics

4Adaptability or versatility

If the runtime framework includes mapping registry and context intermediary components, then it can provide comprehensive message processing capabilities, but it increases the number of components and system complexity

Engineering Contradiction:

Improvecomprehensive message processing capabilitiesVSAvoidnumber of system components

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the functionality of the mapping registry and context intermediary directly into the protocol implementation and message processing pipeline. By combining these separate components into integrated protocol operations, the system maintains comprehensive processing capabilities while reducing the number of distinct components and simplifying the overall architecture

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS8745252B2Headers protocol for use within a web services message processing runtime framework

Publication Date: 2014.06.03 SAP SE

AI summary

A method is described that involves processing a Web services message within an object oriented runtime environment. The processing itself involves executing a plurality of protocols to support a Web service that the message pertains to. Each one of the protocols perform one or more operations that contribute to a different part of the processing. The executing is hibernated by storing state information of the protocols externally from the protocols. The executing is resumed by loading the saved state information back into the protocols. The executing includes one of the protocols performing the following: receiving from an object information retrieved from the message's header; and, providing at least a portion of the information to another protocol amongst the plurality of protocols.