IED Protection Firmware Isolation Through Memory Partitioning

Solution Overview

Problem

The complexity of firmware in intelligent electronic devices (IEDs) used for electric power systems, which includes non-protection functions, can compromise the reliability of protection functions and introduce vulnerabilities, potentially leading to system failures and unauthorized access.

Innovation Solution

Implementing a full-featured operating system that manages software execution by prioritizing protection functions using processor interrupts, memory management units, and partitioning code to isolate protection firmware from non-protection functions, allowing protection functions to continue operating even if non-protection firmware becomes corrupted.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If firmware in intelligent electronic devices includes multiple non-protection functions, then the device becomes more versatile and capable of performing additional tasks, but the reliability of protection functions deteriorates due to increased complexity and potential vulnerabilities

Engineering Contradiction:
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the firmware into distinct partitions: a first partition containing protection functions and a second partition containing non-protection functions. This segmentation allows the device to maintain multiple functions while isolating critical protection functions from potential failures in non-protection functions, thereby resolving the contradiction between versatility and reliability.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If firmware complexity increases to include additional features, then the device becomes more feature-rich, but the number of vulnerabilities and bugs increases, potentially compromising system security

Engineering Contradiction:
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

By dividing firmware into separate partitions for protection and non-protection functions, the patent limits the propagation of vulnerabilities. Bugs or security issues in the non-protection functions are contained within the second partition and cannot compromise the protection functions in the first partition, thus maintaining system security despite increased feature richness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism (the partitioning structure and memory management unit) that mediates between the non-protection functions and protection functions. This intermediary prevents direct interaction that could propagate harmful effects, allowing the system to maintain rich features while protecting against vulnerabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If a monolithic firmware architecture is used to simplify system structure, then the device is easier to manufacture and maintain, but a bug in any part can cause the entire system to fail

Engineering Contradiction:
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements segmentation by creating distinct firmware partitions for protection and non-protection functions. This segmentation maintains relative structural simplicity while preventing system-wide failures, as bugs in non-protection functions are isolated and cannot crash the entire system or compromise protection functions.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12105490B2Isolation of protection functions in electrical power systems
Publication Date: 2024.10.01
  • US12105490B2 patent drawing
  • US12105490B2 patent drawing
  • US12105490B2 patent drawing

AI summary

Systems, devices, and methods include protection functions in an electrical power system. A processing subsystem may include a processor. A memory subsystem may comprise a first memory section and a second memory section. A memory management subsystem may, in a first operational mode, enable memory access between the processor and the first memory section and the second memory section and, in a second operational mode, enable memory access between the processor and only the first memory section.