Pluggable Protocol Processors in Service-Oriented Pipeline Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Service-oriented architectures (SOA) face inefficiencies and complexity when supporting multiple communication protocols, leading to duplicated functionality and resource wastage, as they often require significant re-design or re-configuration to accommodate new protocols.
Innovation Solution
A computer-implemented system and method using pluggable protocol processors in a service-oriented pipeline architecture, where protocol-specific processing is made independent of the SOA model, allowing seamless addition of new protocols without altering the processing model, and utilizing a framework that includes a Service Provider Framework (SPF) and Service Invocation Framework (SIF) with modular handlers for message processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the SOA supports multiple protocols with independent message processing models, then protocol versatility is improved, but system complexity and duplicated functionality increase
Solution Approach 1:
The patent implements a universal message processing framework that can handle multiple protocols (SOAP, XML-RPC, JSON-RPC, HTTP) through a single integrated architecture. The framework uses a common interface platform with pluggable protocol processors that share the same processing pipeline, allowing one system to perform multiple protocol-specific functions without requiring separate independent processing models for each protocol.
Solution Approach 2:
The patent segments protocol-specific processing into separate pluggable processors that can be independently loaded and configured. Each protocol has its own processor module (e.g., SOAPProcessor, XMLRPCProcessor) that implements the same standardized interface, allowing the system to divide protocol handling into manageable, independent segments while maintaining overall system unity.
2Adaptability or versatility
If the SOA uses conventional multi-protocol architecture, then protocol support is improved, but resource utilization efficiency deteriorates due to duplicated functionality
Solution Approach 1:
The patent merges the message processing functionality for multiple protocols into a single unified processing pipeline. Instead of having separate independent processing models for each protocol, the system combines authentication, validation, transformation, and routing operations into a shared resource that serves all protocols, thereby eliminating duplication and improving resource utilization efficiency.
3Adaptability or versatility
If the SOA architecture is redesigned to support new protocols, then protocol adaptability is improved, but development time and reconfiguration effort increase
Solution Approach 1:
The patent implements a dynamic architecture where new protocol processors can be added, removed, or updated without modifying the core processing pipeline. The pluggable processor framework allows the system to adapt to new protocols dynamically by simply loading new processor modules, eliminating the need for reconfiguration or redesign of the overall architecture.
4Reliability
If the SOA processes each protocol independently, then protocol-specific optimization is improved, but overall system efficiency deteriorates due to duplicated processing logic
Solution Approach 1:
The patent applies local quality by allowing each protocol processor to implement protocol-specific optimizations and handling logic while sharing the same overall processing framework. Each processor can be tuned for its specific protocol's requirements (e.g., SOAP-specific validation or JSON-RPC parsing) while benefiting from the efficiencies of shared resources like authentication modules, transformation pipelines, and routing logic.
Data Source
AI summary
A computer-implemented system and method for processing messages using pluggable protocol processors in a service-oriented pipeline architecture is disclosed. The method in an example embodiment includes receiving a message having a protocol-specific portion and a protocol-agnostic portion; determining a protocol compatible with the received message; activating one of a plurality of pluggable protocol processors compatible with the received message; processing the protocol-specific portion of the received message using the activated pluggable protocol processor; and processing the protocol-agnostic portion of the received message using a message processing pipeline, the message processing pipeline including a plurality of stages for processing the protocol-agnostic portion of the received message.