Remote Vehicle Actuation With Command Validation and Safe-State Checks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing remote vehicle access technologies lack sufficient security and safety measures, particularly in scenarios where unauthorized access or unsafe operational states can occur, such as vehicle rental or collective vehicle control.

Innovation Solution

Implementing a system that validates vehicle actuation commands through CRC, checksums, and parity checks, authorizes entities based on data comparisons, ensures vehicles are in safe operational states (e.g., stationary and within authorized geographic areas), and generates activity logs to monitor and detect suspicious activity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If remote vehicle actuation commands are accepted without validation, then ease of operation is improved, but security and reliability deteriorate due to unauthorized access and unsafe operational states

Engineering Contradiction:
Improveremote vehicle access convenienceVSAvoidsecurity and safety of remote actuation
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary validation of actuation commands before execution by checking command integrity (CRC, checksum, parity), verifying requesting entity authorization, and assessing vehicle operational state safety conditions. This preliminary action ensures that only valid, authorized, and safe commands are executed, resolving the contradiction by maintaining ease of operation while preventing unauthorized or unsafe access.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms that monitor vehicle state, track authorized entities, and validate incoming commands against stored authorization data and safety criteria. This continuous feedback loop ensures that remote actuation maintains both convenience and security by dynamically verifying conditions before allowing system changes.

Inventive Principle:
Principle #23Feedback

2Reliability

If multiple validation checks (CRC, checksum, parity) are implemented, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improvecommand validation accuracyVSAvoidvalidation system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The validation system is segmented into distinct functional modules: CRC validation module, checksum validation module, and parity check module. Each module performs a specific validation function independently, allowing the system to achieve high reliability through multiple checks while managing complexity through modular design and clear separation of validation responsibilities.

Inventive Principle:
Principle #1Segmentation

3Reliability

If authorization verification and safety state checks are performed, then security is improved, but processing time increases

Engineering Contradiction:
Improveauthorization and safety verificationVSAvoidcommand processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary organization of authorization data and safety criteria before actual validation occurs. Authorized entities and their permitted operations are pre-configured and stored, allowing rapid verification during command processing. Safety conditions and geographic boundaries are pre-established, enabling quick determination of whether a command is safe to execute without extensive real-time analysis.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12552345B2Remote vehicle system actuation
Publication Date: 2026.02.17 INT ENGINE INTPROP CO LLC
  • US12552345B2 patent drawing
  • US12552345B2 patent drawing
  • US12552345B2 patent drawing

AI summary

Aspects of the disclosure relate to methods, systems, and non-transitory computer readable media for the actuation of vehicle systems. A vehicle actuation command that includes an indication of a requesting entity and vehicle systems a requesting entity is authorized to actuate may be received. There may be a determination of whether a vehicle actuation command is valid and based on a vehicle actuation command being valid there may be a determination of whether a requesting entity is authorized to actuate a vehicle's systems. Based on a requesting entity being authorized to actuate a vehicle's systems, there may be a determination of whether a vehicle is in a safe operational state that will allow a vehicle actuation command to be safely implemented by a vehicle's systems. Furthermore, based on a vehicle being in a safe operational state, a vehicle systems indicated in a vehicle actuation command may be actuated.