Abstract
Automotive radar interference mitigation is expected to be inherent in all future ADAS and AD vehicles. Joint radar communications is a candidate technology for removing this interference by coordinating radar sensing through communication. Coordination of radars requires strict time synchronization among vehicles, and our formerly proposed protocol (RadChat) achieves this by a precise absolute time, provided by GPS clocks of vehicles. However, interference might appear if synchronization among vehicles is lost in case GPS is spoofed, satellites are blocked over short intervals, or GPS is restarted/updated. Here we present a synchronization-free version of RadChat (Sync-free RadChat), which relies on using the relative time for radar coordination, eliminating the dependency on the absolute time provided by GPS. Simulation results obtained for various use cases show that Sync-free RadChat is able to mitigate interference without degrading the radar performance.
Highlights
Automotive radar interference occurs when another radar signal interferes with one’s own radar reflection
We propose a radar communications (RadCom)-based interference mitigation protocol that does not rely on GNSS or such vehicular ad hoc networks (VANET) synchronization protocols; but is designed to eliminate the need for synchronization
Since we ignore reflections from other vehicles and since each vehicle is assumed to be equipped with one front-end and one back-end radar communication units (RCU) with long-range radar sensing functionality, we do not have any radar interference among radars within a single vehicle
Summary
Automotive radar interference occurs when another radar signal interferes with one’s own radar reflection. To achieve coordination among vehicles, radars mounted on different vehicles need to be synchronized with microsecond-level precision. RadChat is a distributed cooperative radar communications protocol, especially designed to mitigate interfence. By RadChat, radar sensing of various RCUs are coordinated via a communication control channel. RCUs switch to communication functionality whenever FMCW radar chirps are sent and the radar sensing is idle over the period T f. Radar and communication use disjointed allocated bandwidths Br and Bc. By RadChat, the whole radar bandwidth can be divided to chunks in the frequency domain, as shown in Figure 2 in order to allow scheduling of different types of automotive radars, such as medium-range radars to a larger bandwidth, and long-range radars to a smaller bandwidth in order to meet the various distance resolution requirements. We assume that Br is used for only one type of radar and is not divided in frequency for simplicity
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
