Asynchronous Ping Messages for Protocol Capability Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data privacy integration protocols in multi-system landscapes face inefficiencies due to applications being offline or misconfigured, leading to unnecessary resource consumption and failed protocol runs.

Innovation Solution

Implementing asynchronous ping messages to determine application availability and configuration before initiating data privacy integration protocols, using 'ping' work packages with empty tasks to assess readiness of applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data privacy integration protocols are executed without prior capability verification, then protocol execution can proceed without preliminary checks, but resource wastage occurs due to failed protocol runs from application unavailability or misconfiguration

Engineering Contradiction:
Improveprotocol execution efficiencyVSAvoidresource wastage
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The system performs a preliminary capability verification by sending a work package with an empty task list to check if applications are available and correctly configured before initiating actual data privacy integration protocol executions. This preliminary action prevents wasted resources on failed protocol runs while maintaining high productivity for successful executions.

Inventive Principle:
Principle #10Preliminary action

2Loss of energy

If capability verification is performed before each protocol run, then resource wastage is reduced, but additional time is consumed for verification steps

Engineering Contradiction:
Improveresource wastageVSAvoidverification time
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The system performs a partial verification by sending a work package with an empty task list rather than a full protocol execution. This partial action suffices to verify application capability without consuming excessive time, reducing both resource wastage and verification time compared to complete protocol runs.

Inventive Principle:
Principle #16Partial or excessive action

3Loss of energy

If work packages with empty task lists are sent to verify application capability, then resource wastage is reduced, but device complexity increases due to additional verification mechanisms

Engineering Contradiction:
Improveresource wastageVSAvoidsystem complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The system uses a universal work package structure that can serve multiple functions: both as a capability verification mechanism (with empty task list) and as a basis for actual protocol execution. This multi-functionality reduces the need for separate verification and execution mechanisms, thereby limiting the increase in device complexity while achieving resource wastage reduction.

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

Data Source

PatentUS12417294B2Asynchronous ping messages for determining capability of systems for executing asynchronous protocols
Publication Date: 2025.09.16 SAP SE
  • US12417294B2 patent drawing
  • US12417294B2 patent drawing
  • US12417294B2 patent drawing

AI summary

The present disclosure involves systems, software, and computer implemented methods for using asynchronous ping messages for determining capability of systems for executing asynchronous protocols. One example method includes sending a work package to at least one application in a multiple-application landscape to determine capabilities of each application for participating in a data privacy integration protocol. Application responses to the sending of the work package are evaluated to determine capabilities of each application for participating in the protocol. A determination is made regarding whether each application is capable of participating in the protocol. In response to determining that at least one application is not capable of participating in the protocol, at least one corrective action regarding the protocol is performed. In response to determining that each application is capable of participating in the protocol, at least one protocol action is performed for the protocol.