MEC Server Gateway for V2X-CAN Data Sharing in Autonomous Driving
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current autonomous driving systems lack an efficient method for data sharing between autonomous and non-autonomous vehicles, particularly in adapting data formats and correcting delay times, which hinders seamless communication and coordination on the road.
Innovation Solution
A method and device utilizing a Mobile Edge Computing (MEC) server to process and transmit Controller Area Network (CAN) messages, converting between V2X and CAN message formats, and correcting delay times to enable data sharing between autonomous and non-autonomous vehicles, facilitating their communication and coordination.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data is shared directly between autonomous and non-autonomous vehicles using different communication protocols (V2X and CAN), then communication between vehicles is enabled, but data format incompatibility and timing synchronization issues occur
Solution Approach 1:
The patent introduces a gateway device as an intermediary between V2X and CAN networks. This gateway performs protocol conversion, transforming V2X messages into CAN messages and vice versa, while also handling timing synchronization. The gateway acts as a mediator that resolves the incompatibility between different communication protocols without requiring changes to the vehicle systems themselves.
Solution Approach 2:
The patent applies parameter changes by adjusting timing parameters and data format parameters during protocol conversion. The gateway modifies message timing stamps, adjusts data representation formats, and transforms message structures to ensure compatibility between V2X and CAN protocols while preserving the essential information content.
2Adaptability or versatility
If V2X messages are converted to CAN messages without timing correction, then protocol compatibility is achieved, but delay time synchronization errors occur
Solution Approach 1:
The patent implements preliminary timing correction at the gateway before converting V2X messages to CAN messages. The gateway pre-calculates and applies timing offset corrections based on the known delay characteristics of each protocol. This preliminary action ensures that timing synchronization is established before the messages are forwarded to the target system, preventing cumulative timing errors.
Solution Approach 2:
The patent employs feedback mechanisms where the gateway monitors actual transmission delays and timing synchronization status. Based on this feedback, the gateway dynamically adjusts timing correction parameters to maintain accurate synchronization between V2X and CAN message streams, compensating for variable delays in real-time.
3Device complexity
If protocol conversion is performed without a gateway device, then system complexity is reduced, but data sharing between different vehicle types becomes inefficient
Solution Approach 1:
The gateway device serves as a specialized intermediary that handles protocol conversion and timing synchronization centrally. This approach concentrates the complexity in a single device rather than requiring complex integration logic in each vehicle system, thereby improving data sharing efficiency without significantly increasing overall system complexity.
Solution Approach 2:
The gateway device is designed with multi-functionality, handling both protocol conversion and timing synchronization tasks in a single unit. This universal approach consolidates multiple functions into one device, improving data sharing efficiency while avoiding the need for separate conversion and synchronization systems that would increase overall complexity.
Data Source
AI summary
A method for sharing data using a mobile edge computing (MEC) server in an autonomous driving system includes receiving a first controller area network (CAN) message from a first vehicle, generating a V2X message including information of the first CAN message when autonomous vehicle information is registered in the MEC server, and transmitting the V2X message to an autonomous vehicle connected to the MEC server via broadcast. This allows data to be shared between vehicles using different data types. At least one of an autonomous vehicle, a user terminal, and a server of the present disclosure may be associated with an artificial intelligence module, a drone (Unmannered Aerial Vehicle, UAV) robot, an augmented reality (AR) device, a virtual reality (VR) device, a device related to a 5G service, and the like.