Hydraspace: Computational Data Storage for Autonomous Vehicles

Hydraspace: Computational Data Storage for Autonomous Vehicles

HydraSpace: Computational Data Storage for Autonomous Vehicles Ruijun Wang, Liangkai Liu and Weisong Shi Wayne State University fruijun, liangkai, [email protected] Abstract— To ensure the safety and reliability of an The current vehicle data logging system is designed autonomous driving system, multiple sensors have been for capturing a wide range of signals of traditional CAN installed in various positions around the vehicle to elim- bus data, including temperature, brakes, throttle settings, inate any blind point which could bring potential risks. Although the sensor data is quite useful for localization engine, speed, etc. [4]. However, it cannot handle sensor and perception, the high volume of these data becomes a data because both the data type and the amount far burden for on-board computing systems. More importantly, exceed its processing capability. Thus, it is urgent to the situation will worsen with the demand for increased propose efficient data computing and storage methods for precision and reduced response time of self-driving appli- both CAN bus and sensed data to assist the development cations. Therefore, how to manage this massive amount of sensed data has become a big challenge. The existing of self-driving techniques. As it refers to the installed vehicle data logging system cannot handle sensor data sensors, camera and LiDAR are the most commonly because both the data type and the amount far exceed its used because the camera can show a realistic view processing capability. In this paper, we propose a computa- of the surrounding environment while LiDAR is able tional storage system called HydraSpace with multi-layered to measure distances with laser lights quickly [5], [6]. storage architecture and practical compression algorithms to manage the sensor pipe data, and we discuss five Both produce a massive amount of data that would be open questions related to the challenge of storage design multiplied with the increased resolution and number of for autonomous vehicles. According to the experimental channels. results, the total reduction of storage space is achieved by Many researchers have investigated image compres- 88.6% while maintaining the comparable performance of sion to save storage spaces [7]–[11]. The authors in the self-driving applications. [12], [13] proposed an efficient image compression al- I. INTRODUCTION gorithm for gray-scale images based on the quadtree The data captured by an autonomous vehicle is grow- decomposition method. Other researchers have focused ing quickly, typically generating between 20TB and on bit-error aware lossless compression algorithms for 40TB per day, per vehicle [1]. This includes cam- color image compression subject to the bit-error rate eras, which tend to generate 20 to 60Mbps, depending during transmission [14]. In order to largely reduce the on the quality of the image, as well as sonar (10 compressed size, lossy compression has been proposed; to100kbps), radar (10kbps), LiDAR (10 to 70Mbps), it does not restore the original data entirely, but the infor- and GPS (50kbps) [2], [3]. Storing data securely and mation loss has little impact on the understanding of the efficiently can accelerate overall system performance. original image, resulting in a much larger compression Take object detection as an example; the variation of ratio [15]–[17]. However, none of these methods have historical data could contribute to the improvement of been utilized on the vehicular dataset to reduce the size detection precision using machine learning algorithms. and save storage space. With more data produced by Map generation can also benefit from the stored data connected and autonomous vehicles, there is a need to in updating traffic and road conditions appropriately. In create an effective data store and management plan to addition, the sensor data can be utilized for ensuring facilitate the development of autonomous vehicles and public security as well as predicting and preventing their applications. crime. The biggest challenge is to ensure that sensors are In this paper, we propose a novel computational data collecting the right data, and it is processed immediately, storage solution for autonomous vehicles by adopting stored securely, and transferred to other technologies in effective compression algorithms based on different in- the chain, such as infrastructure, Road-Side Unit (RSU), coming sources. Comprehensive and intensive experi- and cloud data center. More importantly, how to create ments were conducted to verify the effectiveness of our hierarchical storage and workflow that enables smooth proposed method. The major contributions of this paper data accessing and computing is still an open question are as follows: for the future development of autonomous vehicles. • Propose a computational storage architecture named 1 Cloud server multiple sensors, various data access frequency, infor- Cellular tower Road-Side Unit mation backup, as well as data retrieving and analysis. As shown in Figure 1, there are three types of on- Sensed & CAN Bus data Computation Access frequency Applications board computing applications that need the support of Sensor pipe sensed data. To satisfy the requirements of hard real-time ultrasonic Hard real-time requirement Compress Cache Camera Data Object Cruise Collision Detection Control Avoidance processing applications, such as adaptive cruise control LiDAR Reduce Transfer GPS noise Soft real-time requirement SSD and object detection, the data will be placed directly into Map Oriented Infrastructure V2X generation CAN bus a high-speed cache to accelerate the response time. For Detect Non time-critical applications Engine abnormal HDD Speed Space Health Traffic Social features Assistant information Media Brake less time-critical applications that are defined as a soft real-time requirement in Figure 1, the sensor data will Data collector HydraSpace Vehicle Computing Unit adopt a fast lossy compression algorithm and be stored Fig. 1. An overview of HydraSpace. in lower latency SSD to save storage space and meet the quick response requirement. For those non time-critical applications, the data will first be compressed using a HydraSpace to efficiently support a variety of ap- lossless algorithm and stored in HDD to satisfy the needs plications leveraging diverse data sources for au- of large capacity while reducing the total cost. tonomous vehicles. B. Access Frequency • Apply various compression algorithms to investi- gate the compression performance to find an opti- The sensed data should be placed in different levels mal solution for HydraSpace. of storage architecture based on its access frequencies. • Conduct intensive experiments on an indoor Mobile The highly frequently utilized data can be arranged into platform HydraOne [18] to collect a real vehicular a high-speed cache with limited space; others could dataset, and test the system performance as well as be stored in SSDs or HDDs based on their volume the power consumption of multiple sensors. and the application demands. For those hard real-time • Discuss five open questions to envision the future applications, the tasks will be running periodically to storage design challenge for autonomous vehicles. generate the results for the vehicle control system to The rest of the paper is organized in the following take corresponding action. In other words, these data structure. Section II focuses on the system design and are considered as “hot” data, which will be accessed implementation of our proposed data storage HydraS- frequently by time-critical applications, such as object pace. The experimental setup and observation results are detection, collision avoidance, adaptive cruise control, presented in Section III. Section IV presents the open etc. As we mentioned in the II-A, the less utilized data questions and challenge regarding storage system design, can be put into SSD or HDD for backup and later Section V describes the related works and our work is analysis. concluded in Section VI. C. Data Amount and Type II. HYDRASPACE DESIGN There are two major types of data flowing into Hy- draSpace in autonomous vehicles, which are sensor pipe In this section, we present the system design of our data and CAN bus data. The sensor pipe data contains the proposed HydraSpace. It is a multilevel computational camera, LiDAR, millimeter radar, ultrasonic, and GPS. storage system that is designed for autonomous vehicles The CAN bus data consists of traditional vehicle data to compute and manage vehicular data based on access such as speed, engine information, brake, temperature, frequency, data type and volume, as well as real time ap- etc. Compared to the can bus data, sensor pipe data will plication requirements. More importantly, how to support generate more data due to its complicated data structure applying multiple machine learning models to the same and number of different sensors. In this paper, the data data set concurrently also poses a challenge in the design produced by the camera and LiDAR are the major con- of HydraSpace. This calls for creating an intermediate cerns we considered in our design. The detailed analysis results layer in storage to avoid redundant computations. of the vehicular data-set structure is presented below Figure 1 shows the overall architecture of HydraSpace. to demonstrate the in-depth analysis of our proposed solution. A. Real-time Application Requirement 1) Camera Image dataset: The image data that we The storage architecture of HydraSpace includes a used

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    8 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us