Condition-Based Data Transaction Scheduling Under Network Constraints

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Devices face inefficiencies in executing data transactions due to unsatisfied conditions such as network connectivity, balance thresholds, and transaction limits, leading to increased resource usage and power consumption when reattempts fail.

Innovation Solution

Implementing a condition-based data transaction system where the device schedules transactions to execute when conditions are met, reducing unnecessary processing and power consumption by monitoring and awaiting resolution of errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the device continuously reattempts data transactions when conditions are not satisfied, then the transaction execution reliability is improved, but the power consumption and computational resource usage increase

Engineering Contradiction:
Improvetransaction execution reliabilityVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system performs preliminary monitoring of conditions (network connectivity, balance thresholds, transaction limits) before attempting data transactions. By checking conditions in advance and scheduling transactions only when conditions are satisfied, the system avoids unnecessary continuous reattempts, thereby reducing power consumption while maintaining reliable transaction execution through proactive condition assessment and timing

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the device continuously reattempts data transactions when conditions are not satisfied, then the transaction execution reliability is improved, but the computational resource usage increases

Engineering Contradiction:
Improvetransaction execution reliabilityVSAvoidcomputational resource usage
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary monitoring of conditions (network connectivity, balance thresholds, transaction limits) before attempting data transactions. By checking conditions in advance and scheduling transactions only when conditions are satisfied, the system avoids unnecessary continuous reattempts, thereby reducing computational resource usage while maintaining reliable transaction execution through proactive condition assessment and timing

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements periodic monitoring of transaction conditions at scheduled intervals rather than continuous checking. This periodic approach allows the system to efficiently detect when conditions become satisfied and schedule transactions appropriately, reducing overall computational resource consumption while maintaining the ability to execute transactions reliably when conditions permit

Inventive Principle:
Principle #19Periodic action

3Use of energy by moving object

If the device schedules transactions to execute when conditions are met, then the power consumption is reduced, but the transaction execution timing flexibility decreases

Engineering Contradiction:
Improvepower consumptionVSAvoidtransaction execution timing flexibility
Core Design Contradiction:
Use of energy by moving objectVSEase of operation

Solution Approach 1:

The system dynamically adjusts transaction scheduling based on real-time condition monitoring. When conditions are satisfied, transactions are scheduled for immediate or near-immediate execution, providing timing flexibility. When conditions are not satisfied, the system reduces monitoring intensity and delays scheduling, thereby conserving power. This dynamic adaptation allows the system to balance power consumption with transaction execution timing flexibility based on actual operational conditions

Inventive Principle:
Principle #15Dynamics

4Reliability

If the device monitors conditions continuously to ensure transaction success, then the transaction reliability is improved, but the power consumption increases

Engineering Contradiction:
Improvetransaction execution reliabilityVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by stationary object

Solution Approach 1:

The system implements periodic monitoring of transaction conditions at scheduled intervals rather than continuous monitoring. This approach maintains transaction reliability by regularly checking conditions (network connectivity, balance thresholds, transaction limits) and scheduling transactions when conditions are satisfied, while significantly reducing power consumption by allowing the device to enter lower-power states between monitoring periods

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS20250328901A1Condition-based data transactions
Publication Date: 2025.10.23 MOTOROLA MOBILITY LLC
  • US20250328901A1 patent drawing
  • US20250328901A1 patent drawing
  • US20250328901A1 patent drawing

AI summary

In aspects of condition-based data transactions, a client device can receive a request to execute a data transaction. The client device can detect a condition corresponding to a failure to execute the data transaction at a first time. For example, the condition corresponding to the failure to execute the data transaction at the first time can include at least one of a network connection status, one or more characteristics of a network connection, a server status, a stored balance associated with the payment service, or a threshold numerical quantity of data transactions associated with the payment service for a duration of a timer, a threshold numerical quantity of data transactions for a geographic location, or a threshold transaction value for the geographic location. The client device can execute the data transaction at a later based on a change in the condition corresponding to the failure to execute the data transaction.