SOAP File Transfer via String Arrays and Encryption

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing techniques for transferring files via SOAP messages are not of general applicability due to modifications of the standard SOAP specification, and they lack effective security, especially for mobile devices or wireless networks.

Innovation Solution

The method involves representing files as arrays of strings within the body of SOAP messages without modifying the header, using a title and payload structure, and optionally encrypting the payload with public-key cryptography, allowing standard SOAP messages to be used for file transfer across heterogeneous networks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If standard SOAP messages are used for file transfer, then interoperability and compatibility are maintained, but security is insufficient

Engineering Contradiction:
ImproveinteroperabilityVSAvoidsecurity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The file is segmented into an array of strings, where each string represents a portion of the file content. This segmentation allows the file to be transmitted through standard SOAP messages that have string type constraints, while maintaining the integrity of the original file. The segmentation resolves the contradiction by enabling standard SOAP compatibility without compromising security, as each string element can be individually encrypted or validated.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The file content is converted from its original binary or text format into an array of strings format. This parameter change in data representation allows the file to be accommodated within standard SOAP message structures that expect string types, thereby maintaining interoperability while enabling security measures to be applied to each string element.

Inventive Principle:
Principle #35Parameter changes

2Productivity

If existing file transfer techniques via SOAP are used, then file transfer capability is achieved, but they require modifications to SOAP specification reducing general applicability

Engineering Contradiction:
Improvefile transfer capabilityVSAvoidgeneral applicability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The invention makes the SOAP message body universally applicable for both simple data transfer and file transfer by representing files as arrays of strings. This multi-functionality eliminates the need for specialized file transfer extensions, as the same standard SOAP message structure can handle both text data and file content, thereby maintaining general applicability across different applications and systems.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

Instead of modifying the SOAP protocol to support file transfer directly, the invention inverts the approach by representing files in a format (array of strings) that naturally fits within existing SOAP message structures. This inversion avoids protocol modifications while achieving file transfer capability, thus preserving general applicability.

Inventive Principle:
Principle #13The other way round (Inversion)

3Reliability

If VPN is used for secure connections, then security is improved, but resource consumption and startup time increase

Engineering Contradiction:
ImprovesecurityVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The security mechanism is extracted from the transport layer (VPN) and applied directly to the data layer through encryption of the file arrays within SOAP messages. This extraction eliminates the need for establishing separate VPN connections, thereby reducing resource consumption and startup time while maintaining security. The security function is taken out of the network infrastructure and applied at the application level.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Encryption algorithms act as an intermediary between the file data and the transmission channel, providing security without requiring a dedicated secure transport infrastructure like VPN. This intermediary mechanism enables security with lower resource overhead by applying cryptographic protection directly to the data being transmitted through standard SOAP messages.

Inventive Principle:
Principle #24Intermediary (Mediator)

Applied Scientific Principles

This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.

Function Achieved in This Case

This approach enables secure, interoperable file transfer across different nodes without modifying the SOAP specification, ensuring compatibility and reducing resource consumption, making it suitable for various applications including web services and mobile devices.

Implementation Method 1

the payload portion being encrypted with a public key of the receiver node

Methodology Applied
Scientific EffectPublic-key cryptography:

Data Source

PatentUS11153365B2Transfer of files with arrays of strings in soap messages
Publication Date: 2021.10.19 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11153365B2 patent drawing
  • US11153365B2 patent drawing
  • US11153365B2 patent drawing

AI summary

A method of transferring files in a data-processing network using a current node within the network includes reading an outbound content and outbound characteristics of an outbound file. An outbound message is created having outbound strings including a first set of the outbound strings representing the outbound characteristics and a second set of the outbound strings representing the outbound content. The outbound message is sent to a receiver node within the network. An inbound message is received from a sender node within the network. The inbound message has inbound strings including a first set of the inbound strings representing inbound characteristics and a second set of the inbound strings representing inbound content. An inbound file having the inbound content is stored, and the inbound characteristics are applied to the inbound file.