Dynamic Firmware Interface for Electronic Warfare Jamming

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Electronic Warfare (EW) systems require costly and time-consuming changes to the Operational Flight Program (OFP) when updating firmware, limiting the ability to dynamically reconfigure jamming techniques during missions due to hardware limitations in storing register mappings.

Innovation Solution

The EW system employs a dynamic reconfiguration method that allows updating FPGA firmware without altering the OFP, using a waveform infrastructure with an API and technique application abstraction layer to generate and update jamming waveforms, enabling the use of different techniques without changing the OFP by adjusting parameter mappings and orders.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the firmware is updated with a new register mapping to provide effective countermeasures, then the EW system's adaptability is improved, but the OFP must be changed which increases cost and time consumption

Engineering Contradiction:
Improvefirmware adaptabilityVSAvoidOFP change complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system separates the firmware update process into independent segments: the register mapping file can be updated and loaded without triggering OFP changes. This segmentation allows the firmware layer to be modified independently from the OFP layer, resolving the contradiction between firmware adaptability and OFP complexity

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A register mapping file serves as an intermediary layer between the firmware and the OFP. This intermediary allows the OFP to remain unchanged while the firmware register mappings are updated, effectively decoupling the two components and eliminating the requirement for costly OFP changes

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the firmware is reloaded with a new register mapping to counter changing emitters, then the EW system's effectiveness is improved, but the mission time is increased due to OFP changes

Engineering Contradiction:
Improvecountermeasure effectivenessVSAvoidmission time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-configuring multiple register mapping files that can be rapidly loaded during missions. When emitter changes are detected, pre-prepared register mappings can be immediately activated without time-consuming OFP changes, maintaining countermeasure effectiveness while minimizing mission time loss

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements dynamic register mapping that can be changed in real-time during missions. The firmware can dynamically load different register mapping files based on detected emitter characteristics, allowing rapid adaptation without the static constraints of OFP changes and thereby reducing mission time

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If the OFP is changed to support new firmware, then the system's functionality is improved, but the cost and time required for updates increase

Engineering Contradiction:
Improvesystem functionalityVSAvoidupdate cost and time
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The register mapping file acts as an intermediary that absorbs the complexity of firmware updates. By routing firmware changes through this intermediary layer rather than directly through the OFP, the system achieves enhanced functionality while minimizing update costs and time, as the OFP itself requires no modification

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Instead of modifying the OFP for each firmware update, the system creates and loads copy instances of register mapping files with updated configurations. This copying approach allows new functionality to be implemented in the firmware while the original OFP remains unchanged, significantly reducing update costs and time

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9965267B2Dynamic interface for firmware updates
Publication Date: 2018.05.08 RAYTHEON CO
  • US9965267B2 patent drawing
  • US9965267B2 patent drawing
  • US9965267B2 patent drawing

AI summary

An electronic warfare (EW) devices and a method of providing jamming techniques are generally described. Firmware is updated by eliminating an existing jamming technique, adding a new technique and/or changing parameters of one of the techniques in the firmware. Changing the technique parameters includes adding a new parameter, deleting an existing parameter, changing the range of values for an existing parameter and changing the order of the parameters to be transmitted by an Operational Flight Program (OFP) to the firmware to generate the technique. The OFP reads a published a register mapping specifying parameters to use in generating the jamming techniques in the EW firmware, a range of the parameters and an order of the parameters. The jamming techniques are generated using parameters transmitted by the OFP to the firmware. The same OFP is used to trigger generation of jamming techniques prior to and after the updating of the firmware.