Vehicular MCU Protocol Translation for Cloud-Automotive Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud-based transport protocols are not compatible with automotive/embedded communication protocols, posing challenges for secure and efficient communication between vehicles and external systems, particularly in Car-2-X applications that require secure on-board communication and support for remote and distributed services.

Innovation Solution

A vehicular communication controller apparatus with a microcontroller (MCU) that determines the protocol type of a received protocol data unit (PDU) and serializes or deserializes it accordingly, using protocols like SOME/IP for automotive communication and cloud-based protocols like MQTT or CloudEvents, ensuring seamless communication between vehicles and cloud services without modifying the payload.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If cloud-based transport protocols are used for vehicle communication, then communication with external systems is enabled, but compatibility with automotive/embedded communication protocols is lost

Engineering Contradiction:
Improvecommunication compatibilityVSAvoidprotocol compatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a protocol translation layer that acts as an intermediary between cloud-based transport protocols (MQTT, CloudEvents) and automotive communication protocols (SOME/IP, DDS). This translation layer receives messages in cloud protocol format, extracts the payload, repackages it into automotive protocol format, and forwards it to the vehicle's internal systems, thereby enabling compatibility between otherwise incompatible protocol families.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the parameter of protocol format by dynamically selecting and transforming between different protocol types. The system detects the incoming protocol type and converts it to the appropriate automotive protocol format, changing the structural parameters of the communication data to match the target protocol requirements while preserving the semantic meaning of the message.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If protocol translation is implemented, then compatibility between cloud and automotive protocols is achieved, but system complexity increases

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidcommunication system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the communication system into distinct functional layers: a cloud protocol reception layer, a translation/processing layer, and an automotive protocol transmission layer. This segmentation allows each layer to handle specific protocol types independently, reducing overall system complexity by localizing protocol-specific logic rather than requiring a monolithic translation engine.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a universal message structure that can carry payloads from multiple different cloud protocols (MQTT, CloudEvents) and translate them to multiple automotive protocols (SOME/IP, DDS). This multi-functional translation layer handles various protocol types through a unified interface, reducing complexity by avoiding separate dedicated translation paths for each protocol combination.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11843685B1Method and apparatus for embedded in-vehicle device-to-device cloud communications optimization
Publication Date: 2023.12.12 GM GLOBAL TECHNOLOGY OPERATIONS LLC
  • US11843685B1 patent drawing
  • US11843685B1 patent drawing
  • US11843685B1 patent drawing

AI summary

A vehicular communication controller includes a microcontroller (MCU) located within a vehicle to publish a newly defined protocol data unit (PDU) including a header and a payload portion to a destination device. The destination device may utilize a first protocol or a second protocol. If the destination device utilizes the first protocol that includes an automotive/embedded communication protocol then the MCU serializes the payload portion of the PDU and binds the PDU to the first protocol. The destination device may then receive the PDU using the first protocol, deserialize the payload portion, and remove the header leaving the payload portion unchanged and recreate, based on the deserialized payload portion, the PDU.