Network Data Buffering Before Initialization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Time-sensitive applications in data networks, such as automotive systems, face challenges in transferring and processing data before the network is fully initialized, as the initialization process is often too slow to meet safety constraints like activating audio and video feeds.

Innovation Solution

A method that involves receiving data packets and selecting a delay time based on average delay times from previous communications, allowing data to be processed before full network initialization by using a data buffer to store and process data at a predetermined time, even when the network is uninitialized.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the network performs full initialization to set up control parameters and distribute timing information, then network reliability and timing precision are improved, but the initialization time increases too slowly to meet time-sensitive application requirements

Engineering Contradiction:
Improvenetwork initialization completenessVSAvoidinitialization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary data buffering and processing in advance during the initialization period. Data packets are received and stored in buffers before the network is fully initialized, allowing time-sensitive applications to access data without waiting for complete network setup. This preliminary action resolves the contradiction by preparing data ahead of time when the network is still initializing.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The initialization process is segmented into multiple stages: early stage where data can be buffered with average delay calculations, middle stage with partial network functionality, and final stage with full initialization. This segmentation allows time-sensitive applications to operate during earlier stages while the network continues initializing in the background, resolving the time vs. reliability contradiction.

Inventive Principle:
Principle #1Segmentation

2Speed

If the network processes data before full initialization, then time-sensitive application requirements are met, but errors increase during the transition from uninitialized to initialized state

Engineering Contradiction:
Improvedata processing speedVSAvoiddata processing accuracy
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system continuously monitors network initialization status and adjusts data processing parameters accordingly. During early initialization, the system uses feedback from timing information and delay measurements to calculate average delays and adjust buffer management strategies. This feedback mechanism maintains data processing speed while compensating for the uninitialized state, reducing errors during the transition.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system dynamically changes processing parameters based on initialization stage. In the uninitialized state, it uses average delay times and buffered data with adjusted timing parameters. As initialization progresses, it transitions to using real-time timing information and updated delay calculations. This parameter adaptation allows fast data processing before initialization while maintaining accuracy during the transition.

Inventive Principle:
Principle #35Parameter changes

3Loss of time

If the network uses average delay time from previous communications for data buffering, then data processing timing is improved during initialization, but the system complexity increases

Engineering Contradiction:
Improvedata transmission delayVSAvoiddelay calculation and buffer management complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The system uses its own historical communication data to calculate average delays and manage buffers autonomously during initialization. Each node self-services by maintaining local statistics of previous communications and using this information to optimize its own data buffering and timing, without requiring complex centralized control. This self-service approach reduces overall system complexity while improving timing.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary delay measurements and average calculations during the initialization period using historical data. By pre-calculating average delays from previous communications before full initialization, the system establishes timing parameters in advance that simplify subsequent data processing. This preliminary calculation reduces the need for complex real-time delay management during critical time-sensitive operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10091119B2Managing data in a static network prior to initialization
Publication Date: 2018.10.02 HARMAN INT IND INC
  • US10091119B2 patent drawing
  • US10091119B2 patent drawing
  • US10091119B2 patent drawing

AI summary

One embodiment of the present disclosure sets forth a method for managing data received over a network. The method includes receiving at a first time a data packet from a node of the network, selecting a delay time associated with the node, where the delay time comprises an average delay time associated with previous communications involving the node, and processing data included in the data packet at a second time, where the second time is equal to the sum of the first time and the delay time.