Vehicle Communication Routing via Cloud and MEC Offloading

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing vehicle communication systems face inefficiencies in managing requests, leading to battery drain and denial-of-service scenarios due to unfiltered requests processing, especially when vehicles are in an off state or have limited resources.

Innovation Solution

A cloud-based communication management system that utilizes non-volatile storage and mobile edge computing (MEC) devices to process requests intended for vehicles, allowing the system to redirect non-critical or resource-intensive tasks from vehicles to MEC devices, thereby conserving vehicle resources and optimizing power consumption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the vehicle processes all received requests directly, then the vehicle can fulfill user requests, but the vehicle experiences battery drain and resource exhaustion

Engineering Contradiction:
Improverequest processing capabilityVSAvoidbattery consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent introduces a cloud server as an intermediary between the requesting device and the vehicle. The cloud server receives requests, determines whether they can be handled by MEC devices, and only forwards requests that require vehicle processing. This mediator filters out requests that can be handled elsewhere, preventing unnecessary vehicle wake-ups and battery consumption while ensuring critical requests are still processed.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the request filtering and routing function from the vehicle system and places it in the cloud server. By removing the decision-making logic for request handling from the vehicle, the system eliminates the need for the vehicle to continuously monitor and evaluate all incoming requests, thereby reducing computational overhead and energy consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

2Use of energy by moving object

If the vehicle remains in off state to conserve power, then battery life is extended, but the vehicle cannot process requests in a timely manner

Engineering Contradiction:
Improvepower consumptionVSAvoidrequest response time
Core Design Contradiction:
Use of energy by moving objectVSSpeed

Solution Approach 1:

The patent implements preliminary action by having the cloud server determine request routability to MEC devices before forwarding requests to the vehicle. This pre-processing of requests at the cloud level ensures that only necessary requests reach the vehicle, allowing the vehicle to remain in low-power states longer while still maintaining responsive service for critical functions through the MEC infrastructure.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If the vehicle processes resource-intensive tasks, then functionality is maintained, but the vehicle resources become unavailable and denial-of-service scenarios occur

Engineering Contradiction:
Improvefeature execution capabilityVSAvoidsystem availability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The cloud server acts as an intermediary that assesses request requirements against vehicle resource availability. By introducing this mediation layer, the system can redirect resource-intensive tasks to MEC devices with adequate resources, while preserving the vehicle's ability to handle critical functions and maintain system-wide availability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements multi-functionality by enabling the same request to be potentially handled by different entities (vehicle or MEC device) depending on resource availability. This universal approach ensures that functionality is maintained across the distributed system, with the MEC infrastructure serving as a backup or alternative processing venue when vehicle resources are constrained.

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

Data Source

PatentUS11968606B2Cloud-based vehicle communication manager
Publication Date: 2024.04.23 FORD GLOBAL TECH LLC
  • US11968606B2 patent drawing
  • US11968606B2 patent drawing
  • US11968606B2 patent drawing

AI summary

Cloud-based communication management is provided. Status information regarding vehicles is maintained to a non-volatile storage. A request intended to be performed by one of the vehicles is received to a cloud server over a communications network from a requesting device. Responsive to the request being performable by a mobile edge computing (MEC) device in a cell of the communications network instead of the one of the vehicles, the request is sent by the cloud server to the MEC device to be processed by the MEC device instead of being performed by the one of the vehicles.