Paging Console Queue Dependency Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional paging systems do not ensure that a subsequent page is transmitted only after the successful transmission of an earlier page, leading to potential failures in maintaining a predetermined sequence of page delivery.

Innovation Solution

A system and method where each page includes a Dependent-Upon (DU) field indicating dependency on earlier pages, ensuring that subsequent pages are only attempted after successful transmission of preceding pages, with a paging console managing a queue and maintaining transmission records to track success or failure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If pages are transmitted in a traditional paging system without sequence control, then the transmission process is simple and fast, but the predetermined sequence of page delivery cannot be ensured

Engineering Contradiction:
Improvesequence delivery reliabilityVSAvoidpaging system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-configuring dependency relationships between pages before transmission. Each page is assigned a Dependent-Upon (DU) field indicating which earlier pages must succeed before this page can be transmitted. The system proactively checks transmission records before attempting to send each page, preventing sequence violations before they occur.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by maintaining transmission records that track the success or failure of each page transmission. Before transmitting a dependent page, the system checks the transmission record of the preceding page to determine whether to proceed with transmission. This feedback mechanism ensures sequence reliability without requiring complex real-time coordination.

Inventive Principle:
Principle #23Feedback

2Reliability

If subsequent pages are transmitted regardless of prior page failure, then the paging system operates continuously with high productivity, but the intended sequence and reliability of page delivery is compromised

Engineering Contradiction:
Improvepage delivery reliabilityVSAvoidpaging throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary verification by checking transmission records before initiating each page transmission. This preliminary action prevents wasted transmission attempts on pages that depend on failed preceding pages, improving overall reliability without significantly impacting productivity since transmissions are only blocked when necessary.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The feedback mechanism monitors transmission outcomes and uses this information to control subsequent page transmissions. When a page transmission fails, the feedback loop prevents dependent pages from being transmitted, ensuring reliability. The system only reduces throughput when sequence violations would occur, maintaining high productivity in normal operating conditions.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8060120B2System and method for transmitting a sequence of pages in a communication system
Publication Date: 2011.11.15 MOTOROLA SOLUTIONS INC
  • US8060120B2 patent drawing
  • US8060120B2 patent drawing
  • US8060120B2 patent drawing

AI summary

A system and method for transmitting a series of pages in a communication system. The system includes a paging console for placing a plurality of pages in a queue for transmission to one or more targets devices. Each page includes a Dependent-Upon (DU) field that indicates whether the page is dependent upon an earlier page in the queue. Upon initiating a paging event, the plurality of pages are attempted based upon their order in the queue. Prior to transmitting each page, it is determined whether the DU field of that page indicates a dependency upon an earlier page. If there is no dependency, the page is attempted as normal. If the current page is dependent upon an earlier page, a record is checked to determine whether the earlier page was successful. If the earlier page was successful, the current page is attempted. If the earlier page was unsuccessful, the current page is not attempted and is recorded as unsuccessful.