Open Communication Manager for Parallel Thread Termination

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Massively parallel computing applications face significant challenges in transitioning between modes or applications due to lengthy initialization and shutdown sequences, which reduce operational capability in real-time environments, particularly in systems like multi-mode radar systems.

Innovation Solution

A system and method that utilize an open communication manager to track and complete open communications between threads of a process and other processes, allowing for fast and graceful termination of threads without leaving incomplete communications, thereby minimizing transition time and maintaining system stability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If threads are terminated using traditional shutdown sequences, then system stability is maintained through proper communication completion, but transition time becomes excessively long

Engineering Contradiction:
Improvesystem stabilityVSAvoidtransition time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by maintaining information about open communications between threads and other processes before termination. When a thread termination command is received, the system proactively completes these open communications on behalf of the threads, ensuring proper shutdown protocols are followed without requiring the threads to actively participate in the completion process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system acts as an intermediary by taking over the communication completion task from the threads themselves. Instead of requiring threads to gracefully close their communications with other processes, the system intercepts the termination command, identifies pending communications, and completes them on behalf of the threads, thereby decoupling the termination trigger from the communication completion process.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of time

If fast thread termination is implemented without completing open communications, then transition time is reduced, but incomplete communications are left hanging causing system instability

Engineering Contradiction:
Improvetransition timeVSAvoidsystem stability
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system extracts the communication completion task from the thread termination process. By separating these two operations, the system can terminate threads immediately while independently handling the completion of their open communications, thus eliminating the coupling that previously forced a choice between speed and stability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system provides self-service by automatically completing open communications without requiring external intervention or thread participation. When termination is commanded, the system autonomously identifies and completes pending communications, ensuring proper shutdown behavior occurs automatically as part of the termination process.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10102032B2Fast transitions for massively parallel computing applications
Publication Date: 2018.10.16 RAYTHEON CO
  • US10102032B2 patent drawing
  • US10102032B2 patent drawing
  • US10102032B2 patent drawing

AI summary

Embodiments relate to facilitating quick and graceful transitions for massively parallel computing applications. A computer-implemented method for facilitating termination of a plurality of threads of a process is provided. The method maintains information about open communications between one or more of the threads of the process and one or more of other processes. In response to receiving a command to terminate one or more of the threads of the process, the method completes the open communications on behalf of the threads after terminating the threads.