Subscriber Node Transmission Event Memory for CPU Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In existing communication systems, such as CAN bus, subscriber nodes are hindered by the need to wait for the completion of a transmission job before attending to urgent messages, leading to delays and inefficiencies, as status information is often limited to success and not cancellations, causing CPU blocking and inefficiency.

Innovation Solution

A separate transmission event memory is introduced to store and manage information about transmission jobs, allowing for detailed status tracking of messages, including cancellations, and enabling immediate CPU availability for new tasks by decoupling status information from message memories.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If the CPU waits for the completion of a transmission job before processing the next message, then transmission status can be tracked accurately, but processing speed and CPU efficiency deteriorate due to CPU blocking

Engineering Contradiction:
Improvetransmission status tracking accuracyVSAvoidprocessing speed of transmission jobs
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent divides the monolithic message memory into separate functional components: a message buffer for storing transmission data and a status register for storing transmission results. This segmentation allows the CPU to access status information independently without waiting for the transmission to complete, thus resolving the contradiction between accurate status tracking and processing speed.

Inventive Principle:
Principle #1Segmentation

2Loss of information

If status information is stored in message memory, then transmission results can be recorded, but memory availability and processing efficiency worsen due to CPU blocking

Engineering Contradiction:
Improvetransmission result information availabilityVSAvoidCPU waiting time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent extracts the status information storage function from the message memory and places it in a separate status register. This extraction allows the status information to be stored and accessed independently, preventing the CPU from being blocked while waiting for transmission completion, thus eliminating both information loss and time loss.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If the CPU is blocked during data frame transmission to ensure accurate status reporting, then transmission accuracy is maintained, but system responsiveness and productivity deteriorate

Engineering Contradiction:
Improvetransmission status reporting accuracyVSAvoidsystem responsiveness to urgent messages
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent introduces a status register as an intermediary between the transmission process and the CPU. This intermediary captures and stores transmission status information independently, allowing the CPU to retrieve status data without being blocked during transmission, thus maintaining both reliability and productivity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8732374B2Subscriber node of a communication system having a functionally separate transmission event memory
Publication Date: 2014.05.20 ROBERT BOSCH GMBH
  • US8732374B2 patent drawing
  • US8732374B2 patent drawing
  • US8732374B2 patent drawing

AI summary

A subscriber node of a communication system, a communication system and a method for transmitting a message in the communication system. The message is transmitted from a first subscriber node of the communication system via a data bus of the communication system to a second subscriber node of the communication system. An application program of the first subscriber node files the message, that is to be sent, in a message memory, from where it is retrieved by a communication controller, upon a sending command of the application program, and is transmitted via the data bus. In particular in the case of a cancellation of the transmission job, in order to be able to improve the capacity utilization and the efficiency of a host CPU, it is provided that a transmission event for the message, that is to be sent or that has been sent, is stored in at least one transmission event memory, that is functionally separate from the message memory, and that the application program is able to access the data stored in the event memory at any time.