Model-Based Network Communications for Deterministic Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technical computing environments using Ethernet for network communication often experience variable and unpredictable latency, which is problematic for real-time applications that require deterministic data transmission.

Innovation Solution

Implementing custom Ethernet drivers and network buffer aware blocks within the technical computing environment to directly manage network communications, reducing reliance on the operating system's communication stack and minimizing non-deterministic delays.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If standard Ethernet networking technologies are used for network communication, then ease of operation and compatibility are improved, but latency becomes variable and unpredictable

Engineering Contradiction:
Improveease of operationVSAvoidlatency
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The network communication functionality is segmented into two paths: a standard Ethernet path for general compatibility and a dedicated real-time network path for deterministic low-latency communication. This segmentation allows the system to use different communication mechanisms depending on the application requirements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A real-time operating system kernel acts as an intermediary between the application and the standard Ethernet network stack. The kernel provides direct access to network interface cards and manages network buffers, eliminating the non-deterministic delays introduced by the standard OS network stack while maintaining compatibility with standard Ethernet protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If standard Ethernet networking technologies are used for network communication, then adaptability to existing networks is improved, but latency predictability deteriorates

Engineering Contradiction:
ImproveadaptabilityVSAvoidlatency predictability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system dynamically switches between standard Ethernet communication and real-time network communication based on application requirements. The real-time network driver can be activated when deterministic latency is required, while standard Ethernet is used for general-purpose communication, providing both adaptability and reliability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the operational parameters of network communication by using a real-time OS kernel that provides deterministic scheduling and direct hardware access. This changes the latency parameter from variable to predictable while maintaining Ethernet protocol compatibility through the real-time network driver.

Inventive Principle:
Principle #35Parameter changes

3Loss of time

If custom Ethernet drivers are implemented within the technical computing environment, then latency is reduced and predictability is improved, but device complexity increases

Engineering Contradiction:
ImprovelatencyVSAvoiddevice complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The real-time operating system kernel serves multiple functions: it provides deterministic scheduling for real-time applications, manages network buffers directly, and interfaces with standard Ethernet network interface cards. This multi-functionality reduces the need for separate dedicated hardware while achieving low-latency communication.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The real-time network driver implements self-service by directly managing network buffer memory and interface card operations without requiring services from the standard OS network stack. This self-management eliminates the sources of non-deterministic delays while the real-time OS kernel handles resource allocation and scheduling.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8200849B1Model based network communications
Publication Date: 2012.06.12 MATHWORKS INC
  • US8200849B1 patent drawing
  • US8200849B1 patent drawing
  • US8200849B1 patent drawing

AI summary

In an implementation, a model executing at a target device may use networking services integrated within the model instead of using networking services of the operating system kernel. Latency and non-deterministic behavior associated with using networking services of the operating system kernel may be reduced. Computer-readable media may include instructions for compiling a model, that represents a design, for execution on a target computing device, the compiled model including one or more software components for directly communicating with a network adapter on the target computing device to handle network communications. The computer-readable media may additionally include instructions for transmitting the compiled model to the target computing device, the model, when executed, providing control over network communications at the target computing device.