Programmable Radio Virtual Pipe for Reliable Packet Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing radio communication systems require software developers to manually construct and decode data packets, increasing the workload and risk of errors due to the need for consistent data-type identifier management between transmitting and receiving appliances.

Innovation Solution

A programmable radio communication system with transmitter and receiver firmware that operates through a virtual pipe interface, allowing operators and elements to be encoded and decoded, thereby simplifying the process and reducing the burden on software developers by separating the packet construction and deconstruction from the transmit-side and receive-side software applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software applications manually construct and decode data packets, then developers have direct control over data transmission, but the development complexity and risk of incompatibilities increase significantly

Engineering Contradiction:
Improvecompatibility between transmit and receive applicationsVSAvoidsoftware development complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces firmware as an intermediary layer between the software application and the radio communication protocol. The firmware handles all packet construction, encoding, and decoding operations, while the software application interacts with a simplified virtual pipe interface. This mediator approach eliminates the need for developers to understand complex packet structures while ensuring consistent encoding/decoding between transmitter and receiver, directly resolving the contradiction between reliability and complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system architecture is segmented into distinct layers: the software application layer that uses high-level virtual pipe commands, and the firmware layer that handles low-level packet construction and protocol management. This segmentation allows each layer to operate independently with well-defined interfaces, reducing the complexity burden on software developers while maintaining reliable communication through specialized firmware handling.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If developers manage data-type identifiers and packet structures, then precise control over communication protocols is achieved, but the workload and potential for errors increase

Engineering Contradiction:
Improveease of software developmentVSAvoiddevelopment efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The firmware is designed to automatically handle all aspects of packet construction, encoding, and decoding without requiring software developer intervention. The virtual pipe interface provides self-service functionality where simple command-passing operations automatically translate into properly formatted radio packets. This eliminates the manual workload of managing data-type identifiers while maintaining precise protocol control through the firmware's automated processes.

Inventive Principle:
Principle #25Self-service

3Reliability

If consistent data-type identifier management is implemented across transmit and receive appliances, then communication reliability improves, but the burden on software developers increases

Engineering Contradiction:
Improvecommunication consistencyVSAvoidsoftware maintenance burden
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The firmware acts as a consistent intermediary that enforces uniform data-type identifier management on both transmit and receive sides. Since the same firmware logic handles encoding and decoding, consistency is guaranteed by design rather than by developer effort. The virtual pipe interface shields software developers from these consistency requirements, maintaining reliability without increasing software complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8896415B2Programmable radio
Publication Date: 2014.11.25 NORDIC SEMICONDUCTOR
  • US8896415B2 patent drawing
  • US8896415B2 patent drawing

AI summary

A programmable radio communication system comprises a transmitter (1) and a receiver (2). The transmitter comprises radio transmitting means (5) and processing means (3). The processing means is configured to: execute transmitter firmware (6); execute a transmitter software application (4); and operate an interface between the transmitter firmware (6) and the transmitter software application (4), wherein the interface supports one or more operators, each operator acting on one or more elements, wherein the transmitter firmware (6) comprises instructions for: receiving across the interface from the transmitter software application (4), an operator and an element, associated with a virtual pipe; encoding the operator and the element; and using the radio transmitting means (5) to transmit the encoded operator and element by radio, and wherein the receiver (2) comprises radio receiving means (10) and processing means (8), the processing means being configured to: execute receiver firmware (11); execute a receiver software application (9); and operate an interface between the receiver firmware (11) and the receiver software application (9), wherein the receiver firmware (11) comprises instructions for: using the radio receiving means (10) to receive the encoded operator and element; decoding the operator and element; and sending the operator and the element across the interface to the receiver software application (9), thereby creating the virtual pipe between the transmitter software application (4) and the receiver software application (9).