Dynamic Service Call Protocol Selection for Firewall Traversal

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current Web service technologies face inefficiencies in data conversion and communication processes, particularly when SOAP messages need to pass through firewalls, resulting in high overhead and degradation due to their text-based XML format.

Innovation Solution

The solution involves determining the optimal communication method for service calls based on the communication environment, allowing for either native calls within the client apparatus or traditional SOAP-based calls through a network, thereby reducing the need for data conversion and improving efficiency by using multiple communication protocols like SOAP and EJB.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If SOAP messages are used for service communication, then services can be exchanged through firewalls using standard Internet protocols, but data conversion overhead increases and communication efficiency degrades

Engineering Contradiction:

Improvefirewall compatibilityVSAvoidcommunication efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The system dynamically selects between SOAP-based communication and native method invocation based on whether the service provider is located inside or outside the firewall. This dynamic adaptation allows the system to use the most efficient communication method for each specific scenario, resolving the contradiction between firewall compatibility and communication efficiency.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The communication protocol parameter is changed based on the service provider's location. When the provider is inside the firewall, the system switches from SOAP protocol to native method invocation, changing the communication parameter to eliminate unnecessary data conversion overhead while maintaining firewall compatibility when needed.

Inventive Principle:

Principle #35Parameter changes

2Ease of operation

If SOAP-based Web service technology is used, then standard Internet protocols can be utilized for service exchange, but the text-based XML format causes high overhead and performance degradation

Engineering Contradiction:

Improvestandard protocol usageVSAvoiddata conversion efficiency

Core Design Contradiction:

Ease of operationVSProductivity

Solution Approach 1:

The service invocation mechanism is segmented into two distinct paths: SOAP-based communication for external services and native method invocation for internal services. This segmentation allows each path to use the most appropriate protocol, eliminating unnecessary XML data conversion for internal calls while maintaining standard protocol usage for external communications.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The service proxy acts as an intermediary that determines the appropriate communication method. It mediates between the service requester and provider, selecting whether to use SOAP or native invocation based on the provider's location, thus optimizing data conversion efficiency while maintaining ease of operation through standardized interfaces.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Productivity

If native method invocation is used within the client apparatus, then communication efficiency improves by eliminating data conversion, but the ability to communicate through firewalls is limited

Engineering Contradiction:

Improvecommunication efficiencyVSAvoidfirewall traversal capability

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The system dynamically adapts its communication method based on the service provider's location relative to the firewall. This dynamic selection enables the system to use native method invocation for efficient internal communication while switching to SOAP-based communication for external services that require firewall traversal, thus resolving the contradiction between efficiency and adaptability.

Inventive Principle:

Principle #15Dynamics

4Adaptability or versatility

If temporary files are used for data conversion in SOAP communication, then protocol compatibility is maintained, but system overhead increases and performance decreases

Engineering Contradiction:

Improveprotocol compatibilityVSAvoidsystem overhead

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts and removes the unnecessary data conversion process and temporary file creation for internal service calls. By taking out the SOAP protocol overhead for internal communications and using native method invocation instead, the system eliminates device complexity and system overhead while maintaining protocol compatibility through SOAP for external communications where needed.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS7624404B2Communication method selection for exchanging information between service requester and service provider

Publication Date: 2009.11.24 RICOH CO LTD

AI summary

A service request apparatus, which includes an application using a service provided by another apparatus by connecting to the another apparatus through a network, determines a communication method to call the service in response to a call request for calling a method with respect to the service, the call request sent from the application, and conducts a remote call of the method in response to the call request from the application based on the communication method.