SOAP Message Delay Indication for Timestamp Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Queued asynchronous transmission of SOAP messages can lead to prolonged delays, causing security processing faults due to timestamp validity issues, especially when messages are held in queue for extended periods, which compromises the freshness and security of the messages.

Innovation Solution

Incorporating a delay indication into the SOAP message, digitally signed and formatted according to an XML schema, which allows the web service to adjust the timestamp's lifetime by subtracting the delay period, ensuring message freshness and security even after prolonged queuing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If messages are held in queue for extended periods for asynchronous transmission, then system reliability and message delivery assurance are improved, but timestamp validity and message freshness are compromised

Engineering Contradiction:
Improvemessage delivery assuranceVSAvoidtimestamp validity
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-calculating and embedding the queue delay duration into the message metadata before retransmission. The system determines how long a message has been queued and attaches this delay information in advance, allowing the receiving service to adjust timestamp validation thresholds proactively rather than reactively, thus preserving timestamp validity despite extended queuing.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes the timestamp validation parameter dynamically by allowing the receiving service to adjust the acceptable timestamp age threshold based on the queued delay duration. Instead of using a fixed timestamp validity window, the system modifies the validation parameter (time threshold) to account for the known queue delay, thereby maintaining timestamp validity under varying queuing conditions.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If timeout values are increased to accommodate queued messages, then message delivery completeness is improved, but security protection against replay attacks is weakened

Engineering Contradiction:
Improvemessage delivery completenessVSAvoidreplay attack vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary action by embedding queue delay information into the message before retransmission. This allows the receiving service to make informed security decisions in advance by knowing the exact delay duration, rather than using conservative timeout values that either reject valid delayed messages or accept potentially compromised ones.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces dynamics by making the timestamp validation threshold adaptive rather than static. The system dynamically adjusts the acceptable timestamp age based on the actual queue delay experienced by each message, allowing timeout values to flexibly accommodate legitimate delayed messages while maintaining security boundaries against replay attacks.

Inventive Principle:
Principle #15Dynamics

3Reliability

If manual recovery processes are implemented for timeout faults, then security fault handling is improved, but operational complexity and labor intensity increase

Engineering Contradiction:
Improvesecurity fault handlingVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent applies self-service by enabling the receiving service to automatically determine and adjust timestamp validation thresholds based on queue delay information embedded in each message. The system performs its own security validation adjustments without requiring external manual intervention, recovery procedures, or complex fault handling workflows, thereby simplifying operations while maintaining security.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7664867B2Reporting queue delays in SOAP messages
Publication Date: 2010.02.16 ORACLE INT CORP
  • US7664867B2 patent drawing
  • US7664867B2 patent drawing
  • US7664867B2 patent drawing

AI summary

A delay indication can be added to SOAP messages by a queue so that receiving web services get a better understanding of the SOAP message freshness.