Radar Control Software Adaptation via Configuration Database

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Radar systems with different hardware architectures require distinct software programs, leading to high maintenance costs, labor intensity, and the risk of errors due to the need for separate inventory and frequent code updates across multiple software products.

Innovation Solution

A method and system for generating or configuring radar control software using a base program and a configuration database, allowing the same software to adapt to various hardware architectures by retrieving and applying specific configuration data, thus eliminating the need for multiple software programs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate software programs are used for each hardware architecture, then each radar system can be optimized for its specific hardware, but maintenance costs and complexity increase significantly

Engineering Contradiction:
Improvehardware-specific optimizationVSAvoidsoftware maintenance complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The software is segmented into a common core portion that remains identical across all radar systems and a configurable portion that is customized for each hardware architecture. This segmentation allows the common core to handle universal radar functions while the configurable portion adapts to specific hardware requirements, reducing overall maintenance complexity while preserving hardware-specific optimization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A single common software program is designed to serve multiple hardware architectures through the use of configuration files. The common core software performs universal radar control functions that can be adapted to different hardware platforms, eliminating the need for separate software programs for each architecture while maintaining hardware-specific capabilities through configuration parameters.

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

2Adaptability or versatility

If multiple software programs are maintained for different radar architectures, then each program can be tailored to specific hardware, but the labor intensity and risk of errors increase

Engineering Contradiction:
Improvehardware tailoring capabilityVSAvoidsoftware error risk
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

By segmenting the software into a common core and configurable portions, the invention reduces the number of software programs that need to be maintained. The common core undergoes single verification and testing, eliminating the propagation of errors across multiple software versions while still allowing hardware-specific customization through configuration files.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Hardware-specific adaptations are achieved through parameter changes in configuration files rather than code modifications. This allows the same verified common software to be safely adapted to different hardware architectures by changing configuration parameters, reducing the risk of errors while maintaining hardware tailoring capability.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If separate software programs are used for each hardware architecture, then specific hardware requirements can be met, but maintenance costs increase

Engineering Contradiction:
Improvehardware architecture supportVSAvoidsoftware maintenance cost
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

A single common software program is designed to support multiple hardware architectures through configuration files, eliminating the need to develop and maintain separate software programs for each hardware platform. This universal approach significantly reduces maintenance costs while continuing to meet specific hardware requirements through configurable parameters.

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

Solution Approach 2:

Instead of creating separate software programs for each hardware architecture, the invention uses configuration files that act as templates or copies for adapting the common software to different hardware. This copying approach allows rapid adaptation to new hardware architectures without the cost of developing entirely new software programs.

Inventive Principle:
Principle #26Copying

4Productivity

If configuration data is stored in a database, then software can be quickly adapted to different hardware, but the system requires additional data management infrastructure

Engineering Contradiction:
Improvesoftware configuration speedVSAvoiddata management infrastructure
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Configuration data is prepared in advance and stored in configuration files or databases, allowing the common software to be quickly adapted to different hardware architectures by simply loading the appropriate configuration data. This preliminary preparation enables rapid software deployment and adaptation without requiring complex real-time data management during operation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9489195B2Method and apparatus for configuring control software for radar systems having different hardware architectures and related software products
Publication Date: 2016.11.08 RAYTHEON COMMAND & CONTROL SOLUTIONS LLC
  • US9489195B2 patent drawing
  • US9489195B2 patent drawing
  • US9489195B2 patent drawing

AI summary

Techniques and systems are provided for generating radar control software for radar systems having a variety of different hardware architectures in an efficient manner. A base radar control program may be provided that is configurable using architecture-specific configuration data. A database may also be provided that includes configuration data associated with a plurality of different radar system architectures. Radar control software may be generated for a radar system of interest by retrieving configuration data associated with a corresponding hardware architecture from the database and using the data to configure the base radar control program.