Vehicle-Backend Acknowledgement Control for Adaptive Message Retry
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle-to-cloud systems lack flexibility in managing communication between vehicles and backend devices, particularly in handling message delivery failures and ensuring privacy considerations.
Innovation Solution
Implementing a flexible acknowledgement schema and adaptive retry-mechanism in the vehicle's electronic control unit, which includes setting timers and determining retry schedules based on user-defined or automatically adjusted privacy settings, to ensure message delivery and manage communication units accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a simple send-and-forget approach is used for message transmission, then the device complexity is reduced, but the reliability of message delivery deteriorates
Solution Approach 1:
The system implements an acknowledgment mechanism where the backend device sends confirmation messages back to the vehicle's electronic control unit. The ECU monitors whether acknowledgments are received and triggers retry transmissions when acknowledgments are missing, creating a closed-loop feedback system that ensures reliable message delivery without requiring complex manual intervention
Solution Approach 2:
The electronic control unit autonomously manages the retry mechanism by automatically detecting missing acknowledgments and initiating retransmissions based on predefined retry schedules. This self-service approach eliminates the need for external intervention while maintaining reliable communication, resolving the contradiction between simplicity and reliability
2Reliability
If a fixed retry schedule is implemented for failed messages, then the reliability of message delivery is improved, but the adaptability to different communication environments deteriorates
Solution Approach 1:
The system employs dynamic retry schedules that can be adjusted based on communication conditions and message priorities. The electronic control unit selects from multiple predefined retry schedules or adapts timing parameters according to the specific communication scenario, enabling the system to maintain high reliability across diverse environments while remaining adaptable to changing conditions
Solution Approach 2:
The retry mechanism allows modification of transmission parameters such as retry intervals, maximum retry counts, and scheduling priorities based on message importance and network conditions. This parameter flexibility enables the system to optimize message delivery reliability for different communication scenarios without requiring a completely different approach for each environment
3Reliability
If continuous communication attempts are made to ensure message delivery, then the reliability is improved, but the energy consumption increases
Solution Approach 1:
Instead of continuous communication attempts, the system implements periodic retry actions based on predefined schedules. The electronic control unit waits for specified time intervals between retry attempts and can suspend communication when messages are successfully delivered or when maximum retry limits are reached, significantly reducing energy consumption while maintaining delivery reliability
Solution Approach 2:
The system applies a controlled amount of retry action rather than exhaustive continuous attempts. By implementing a limited number of retry attempts with appropriate timing, the system achieves sufficient message delivery reliability without the excessive energy consumption that would result from persistent continuous transmission
4Ease of operation
If all messages are treated with the same communication protocol, then the ease of operation is improved, but the adaptability to different message priorities deteriorates
Solution Approach 1:
The system applies different communication characteristics to different messages based on their priority or type. The electronic control unit can assign specific retry schedules, timing parameters, or transmission priorities to individual messages or message categories, allowing important messages to receive more aggressive retry handling while less critical messages use simpler protocols, thereby maintaining both ease of operation and adaptability
Data Source
AI summary
Technologies and techniques for controlling communication between a vehicle and a backend device in a vehicle-to-cloud-system. A message may be sent from the vehicle to the backend device, and a timer is set for receiving an acknowledgment from the backend device at the vehicle that the message was successfully received. The message may be resent from the vehicle to the backend device when no acknowledgment from the backend device was received at the vehicle, or when an acknowledgment from the backend device does not correspond to the message sent from the vehicle to the backend device. Different schedules may be configured for receiving the acknowledgment and resending the message from the vehicle to the backend device, according to different settings.