Communication Device State Verification for Code Injection Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increased use of Large Language Models (LLMs) in communication devices poses a security risk as they can be exploited by AI-based hacker systems to inject malicious code, compromising the control and integrity of IoT devices.

Innovation Solution

Implementing a verification system that utilizes blockchain technology to monitor and verify the behavior of communication devices by establishing a baseline for expected behaviors, tracking state changes, and detecting deviations using local and centralized ledgers to prevent code injections.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If Large Language Models are deployed in communication devices to improve efficiency, then productivity is improved, but security vulnerability increases due to code injection risks

Engineering Contradiction:
ImproveefficiencyVSAvoidsecurity risk
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary actions by establishing a baseline of expected device behaviors before code injection can occur. The verification system continuously monitors device states against this pre-established baseline, detecting deviations that indicate potential code injection attacks before they can compromise device integrity

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The verification system acts as an intermediary layer between the LLM operations and the IoT device. It intercepts and verifies device behaviors, comparing actual states against expected baselines stored in ledgers, thereby preventing malicious code execution while allowing legitimate LLM-enhanced operations to proceed

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If verification system continuously monitors device behavior to detect code injection, then security is improved, but device complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system creates simplified copies of device state information in the form of baseline behavior profiles stored in ledgers. Instead of monitoring all possible device parameters, the verification system tracks only the essential behavioral patterns that define normal operation, reducing monitoring complexity while maintaining security effectiveness

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The verification system segments the monitoring function into distinct components: baseline establishment, state tracking, deviation detection, and response actions. This modular approach allows each component to be independently implemented and optimized, reducing overall system complexity while achieving comprehensive security monitoring

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12489764B2Code injection prevention for communication devices
Publication Date: 2025.12.02 T MOBILE US INC
  • US12489764B2 patent drawing
  • US12489764B2 patent drawing
  • US12489764B2 patent drawing

AI summary

Techniques related to the management of communication devices using a combination of local and centralized blockchains to enable the detection of state changes that deviate from the expected behaviors are disclosed. In one example aspect, a method for detecting code injection activity in communication devices by a machine learning based platform includes determining, by a verification system, baseline information about a communication device; detecting a state change of the communication device, responsive to the state change of the communication device; appending, by the verification system, a current-state block representing the state change to a prior-state block representing a previous state of the communication device in a blockchain; and detecting whether a suspicious attack has occurred by comparing the payload of the current-state block to the baseline information.