Sender Node Idling and Wake-Up for Reliable Event Retry

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In distributed computing environments, particularly those with limited resources like battery-operated devices, continuously polling for event messages leads to unnecessary consumption of computing resources and power, which is inefficient.

Innovation Solution

An event broker manages event messages by storing them in queues specific to each event consumer, causing the sender node to enter an idle state after transmission, and upon error, wakes the node to retry the transmission, conserving resources and maintaining message order.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the sender node continuously polls for event messages, then message delivery reliability is improved, but power consumption and resource usage increase

Engineering Contradiction:

Improvemessage delivery reliabilityVSAvoidpower consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The sender node transitions between active and idle states periodically, polling for messages only when needed rather than continuously. The node enters idle state after successful message transmission and wakes up only when new messages are available, converting continuous polling into periodic action to reduce power consumption while maintaining delivery reliability.

Inventive Principle:

Principle #19Periodic action

Solution Approach 2:

The system uses publish-subscribe mechanisms where consumers automatically receive notifications when messages are available, eliminating the need for senders to continuously poll. The architecture itself provides the service of notifying when action is needed, allowing nodes to remain idle until naturally woken by event-driven notifications.

Inventive Principle:

Principle #25Self-service

2Use of energy by moving object

If the sender node enters idle state after message transmission, then power consumption is reduced, but message delivery latency may increase

Engineering Contradiction:

Improvepower consumptionVSAvoidmessage delivery latency

Core Design Contradiction:

Use of energy by moving objectVSLoss of time

Solution Approach 1:

The sender node proactively enters idle state immediately after successful message transmission, preparing for the next message in advance. The node maintains readiness to wake up and process new messages, balancing the timing of state transitions to minimize latency while maximizing power savings during idle periods.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the sender node is notified when new messages are available, triggering wake-up from idle state. This feedback loop ensures the node responds promptly to new work while remaining idle when no messages are pending, optimizing the trade-off between power consumption and response time.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS12554535B2Idling and waking a sender node for event message delivery in a computing environment

Publication Date: 2026.02.17 RED HAT INC

AI summary

Event delivery can be managed by an event broker in a distributed computing environment. The event broker can receive an event message from a producer device, the event message having a payload and a key. The event broker can store the event message in an event queue based on the key. A sender node can transmit the event message to an event consumer. Subsequent to transmitting the event message, the event broker can cause the sender node to enter an idle state. The event broker can receive an error message from the event consumer while the sender node is in the idle state. After receiving the error message, the event broker can wake the sender node from the idle state. The sender node can initiate a retry process involving iteratively re-transmitting the event message to the event consumer.