Communication Queue Management for Real-Time Traffic Prioritization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Communication channels in electronic systems often face issues with traffic overload, leading to unwanted system behavior and violations of time constraints, as they may refuse or delay communications from computing devices, which can negatively impact real-time operations.

Innovation Solution

A communication queue management system that employs multiple queues with priority levels, reserving portions for higher priority traffic and blocking lower priority traffic to ensure that real-time computing devices meet their timing constraints by prioritizing higher priority communications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If communication channels refuse or delay traffic to handle overload, then traffic volume is managed, but time constraints are violated

Engineering Contradiction:
Improvetraffic volumeVSAvoidtime constraint violation
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The communication queue is divided into multiple priority levels (first priority level for real-time traffic, second priority level for non-real-time traffic). This segmentation allows the system to handle different types of traffic differently, ensuring that real-time traffic meets time constraints while non-real-time traffic can be delayed or refused during overload conditions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different portions of the queue are allocated to different priority levels, with the first portion reserved for high-priority real-time traffic and the second portion for lower-priority traffic. This local differentiation in quality ensures that critical communications receive preferential treatment while managing overall traffic volume.

Inventive Principle:
Principle #3Local quality

2Reliability

If communication channels accept all traffic, then no traffic is refused, but system stability deteriorates under overload

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidsystem stability
Core Design Contradiction:
ReliabilityVSStability of the object's composition

Solution Approach 1:

The queue is segmented into priority levels, allowing the system to maintain reliable communication for critical real-time traffic while selectively refusing or delaying non-critical traffic during overload conditions, thus preserving system stability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system applies partial action by selectively accepting high-priority traffic while refusing low-priority traffic when the queue is full. This partial acceptance strategy maintains system stability by preventing overload while ensuring critical communications are not lost.

Inventive Principle:
Principle #16Partial or excessive action

3Loss of time

If priority-based queue allocation is implemented, then real-time traffic meets timing constraints, but device complexity increases

Engineering Contradiction:
Improvetiming constraint adherenceVSAvoidqueue management complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The queue is divided into distinct priority levels with clear allocation rules. Each incoming communication is classified into a priority level and placed in the appropriate portion of the queue, enabling real-time traffic to meet timing constraints through structured organization rather than complex dynamic management.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The queue structure is pre-configured with reserved portions for different priority levels. This preliminary arrangement eliminates the need for complex real-time decisions about traffic management, as the priority-based allocation rules are established in advance and applied automatically.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10298511B2Communication queue management system
Publication Date: 2019.05.21 APPLE INC
  • US10298511B2 patent drawing
  • US10298511B2 patent drawing
  • US10298511B2 patent drawing

AI summary

In some embodiments, a system includes a memory system, plurality of computing devices, and plurality of queues. The plurality of computing devices perform actions dependent on data stored at the memory device, where traffic between the plurality of computing devices and the memory device has at least a first priority level and a second priority level. The first priority level is higher than the second priority level. The plurality of queues pass data between the memory device and the plurality of computing devices. A particular queue allocates a first portion of the particular queue to traffic having the first priority level and allocates a second portion of the particular queue to traffic having the first priority level and to traffic having the second priority level.