Secure Aggregated Event Reporting in Utility Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current aggregated event reporting systems in utility networks lack end-to-end security, making them vulnerable to malicious attacks where compromised devices can falsely report widespread outages, leading to inefficient resource deployment and increased costs.

Innovation Solution

A computer-implemented method and system that generates secure aggregated event reports by using cryptographically secured information, including a unique identifier and message integrity check, to verify the authenticity of each record, thereby preventing malicious tampering and ensuring the integrity of data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If aggregated event reports are transmitted through the network to reduce message volume, then communication efficiency is improved, but end-to-end security is compromised because each device that the aggregate report passes through must be able to modify the report

Engineering Contradiction:
Improvecommunication efficiencyVSAvoidend-to-end security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the aggregated event report into individual device records, each with its own cryptographic signature. This allows the report to be processed as an aggregate for efficiency while maintaining security at the individual record level through digital signatures that prevent unauthorized modification.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces cryptographic hash functions and digital signatures as intermediaries between the data aggregation process and security verification. These mathematical constructs enable secure verification without requiring trust in intermediate network devices, resolving the contradiction between aggregation and security.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If aggregated reports allow devices to modify the report for flexibility, then adaptability is improved, but the system becomes vulnerable to malicious hackers who can falsely report outages

Engineering Contradiction:
Improvereport modification capabilityVSAvoidmalicious attacks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary cryptographic hashing and digital signature generation to each record before aggregation. This preliminary security action ensures that while records can be aggregated and processed flexibly, any subsequent malicious modification would be detectable through signature verification at the receiving end.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent converts the potential harm of unauthorized modification into a benefit by using cryptographic techniques that make any modification easily detectable. The ability to modify records is transformed into a controlled process where only authorized modifications (those with valid signatures) are accepted, turning a security vulnerability into a secure verification mechanism.

Inventive Principle:
Principle #22Blessing in disguise (Convert harm into benefit)

Data Source

PatentEP3371930B1Method and apparatus for secure aggregated event reporting
Publication Date: 2021.10.13 TRILLIANT NETWORKS INC
  • EP3371930B1 patent drawingFigure 1
  • EP3371930B1 patent drawingFigure 2
  • EP3371930B1 patent drawingFigure 3

AI summary

A computer implemented method and system for secure aggregated event reports. The method comprises determining, by a device, that a status change has occurred at the device; receiving, by the device, a status change report from one or more child devices; generating, by the device, a device status change record; generating a record verification field, comprising: combining a nonce, an event type, and a unique device identifier; generating a message integrity check code for the combined nonce, event type and device identifier; and appending the message integrity check code to the device status change record; appending the device status change record to the received status change report; and transmitting, by the device, the status change report to one or more parent devices toward a head end system.