Multiprocessor UI Inactivity Timing With Reduced IPC Traffic

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional multiprocessor communication devices face excessive inter-processor communication (IPC) bus traffic and increased power drain due to inefficient management of user inactivity, as each processor independently detects different user input events, leading to unnecessary communication and latency.

Innovation Solution

Implement a system where each processor determines user inactivity time by sharing timestamps and synchronizing user input events, allowing one processor to manage user inactivity based on the minimum of both processors' input event times, and adjust timers accordingly to reduce IPC bus usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If each processor independently detects and manages user inactivity events, then user inactivity management reliability is improved, but inter-processor communication traffic and power consumption increase excessively

Engineering Contradiction:
Improveuser inactivity management reliabilityVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent merges user inactivity management responsibilities by having one processor (e.g., the application processor) centrally manage inactivity state across all processors, rather than each processor independently managing its own inactivity detection. This consolidation reduces redundant IPC bus communications while maintaining reliable inactivity management through a single coordinated control mechanism.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If each processor independently detects user input events, then detection coverage is improved, but inter-processor communication traffic increases

Engineering Contradiction:
Improveuser input detection coverageVSAvoidinter-processor communication traffic
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The patent extracts the user inactivity management function from individual processors and consolidates it in one processor. Each processor continues to detect user input events locally, but only the designated managing processor communicates inactivity state changes via IPC bus, extracting the communication burden from all processors and concentrating it in a single coordinated management point.

Inventive Principle:
Principle #2Taking out (Extraction)

3Measurement precision

If continuous monitoring of user inactivity is performed by all processors, then detection accuracy is improved, but processing latency increases

Engineering Contradiction:
Improveuser inactivity detection accuracyVSAvoidprocessing latency
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent implements preliminary action by having processors continuously monitor user input events and locally track inactivity time without immediately communicating status changes. The designated managing processor periodically queries inactivity status from other processors, allowing accurate detection to be maintained while reducing communication frequency and associated latency.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20260064441A1Detecting user inactivity in a multiprocessor communication device
Publication Date: 2026.03.05 MOTOROLA SOLUTIONS INC
  • US20260064441A1 patent drawing
  • US20260064441A1 patent drawing
  • US20260064441A1 patent drawing

AI summary

Examples include a communication device including a user interface (UI), a first electronic processor configured to detect and process UI input events, and a second electronic processor communicatively connected to the first electronic processor and configured to detect and process UI input events. The first electronic processor executes an application having a user inactivity timeout feature by initializing a countdown timer for a first time period, and, in response to expiration of the countdown timer, determining a user inactivity time for the communication device. The user inactivity time is a lesser of a time since a UI input event was last detected by the first electronic processor and a time since a UI input event was last detected by the second electronic processor. In response to the user inactivity time being greater than or equal to the first time period, the first electronic processor performs an application timeout function.