Secure Type-Enforced Actions in ROS Middleware

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Autonomous vehicle and robot systems face security and integrity issues due to malicious attacks, environmental conditions, and programming errors that can lead to unsafe message exchanges, particularly in ROS-based systems where messages can be intercepted, delayed, or lost, compromising safety and security.

Innovation Solution

Implementing secure type-enforced actions and distributed notifications through the integration of action clients and servers with type-enforcement verification, along with integrity and confidentiality message protection, using cryptographic definitions and Trusted Execution Environments (TEEs) to ensure secure communication pathways and message integrity within the ROS framework.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If standard ROS message passing is used for communication between nodes, then ease of operation and system flexibility are improved, but security and message integrity are compromised due to susceptibility to malicious attacks, environmental conditions, and programming errors

Engineering Contradiction:
Improvemessage passing simplicityVSAvoidmessage security and integrity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces an intermediary verification mechanism that acts as a mediator between message publishers and subscribers. This intermediary checks message types and enforces security protocols before messages are exchanged, preventing malicious attacks and programming errors while maintaining the simplicity of ROS message passing. The intermediary layer validates messages without requiring changes to the underlying ROS communication infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary type verification and security checks before messages are exchanged between ROS nodes. By performing these checks in advance, the system prevents unsafe message exchanges caused by programming errors or malicious attacks. The type enforcement mechanism verifies message compatibility and security requirements before allowing communication, ensuring reliability while maintaining ease of operation.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If type enforcement and security verification are implemented in ROS message exchanges, then message security and integrity are improved, but device complexity increases due to additional verification mechanisms

Engineering Contradiction:
Improvemessage security and integrityVSAvoidverification mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent changes the parameter of type verification from a complex, generic type-checking mechanism to a simplified parameter-based verification system. By focusing verification on specific message parameters and types rather than comprehensive structural analysis, the system achieves adequate security with reduced complexity. The verification mechanism checks essential parameters without requiring complex type inference or analysis.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent extracts the essential security verification functions from the complex ROS message passing system and implements them as separate, focused checks. By taking out only the critical verification steps needed for security and type enforcement, the system avoids the complexity of comprehensive message validation while maintaining adequate security. The extraction approach focuses verification on essential elements rather than attempting to verify all message aspects.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If cryptographic protection and Trusted Execution Environments are used for message exchanges, then confidentiality and security are improved, but use of energy and computational resources increases

Engineering Contradiction:
Improveconfidentiality and securityVSAvoidcomputational energy consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies partial cryptographic protection only to critical messages and communication channels that require enhanced security, rather than encrypting all messages uniformly. By applying cryptographic measures selectively to high-risk communications, the system achieves adequate confidentiality and security for critical operations while minimizing energy consumption on less sensitive message exchanges. This partial action approach balances security requirements with energy constraints.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent implements local quality by applying different security levels to different message types and communication channels based on their sensitivity and risk profile. Critical messages involving safety-critical operations receive full cryptographic protection and TEE verification, while less sensitive messages use lighter verification mechanisms. This localized approach to security ensures adequate protection where needed while reducing overall energy consumption.

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP3547651B1Secure type-enforced actions
Publication Date: 2021.10.27 INTEL CORP
  • EP3547651B1 patent drawingFigure 1
  • EP3547651B1 patent drawingFigure 2
  • EP3547651B1 patent drawingFigure 3

AI summary

In some examples, a robot middleware system including a first robot middleware node, a second robot middleware node, and one or more secure encrypted type-enforced context message between the first robot middleware node and the second robot middleware node.