Automatic driving vehicle remote monitoring platform based on VUE and aggregation engineering

Abstract

The invention discloses an automatic driving vehicle remote monitoring platform based on VUE and aggregation engineering. The platform comprises an application layer, a data layer and a gateway. The application layer adopts VUE to quickly construct a website, and the data layer adopts aggregation engineering to quickly construct modular engineering. According to the method, the functions of real-time monitoring, remote starting, remote flameout, automatic driving fault 3D histogram statistics, table real-time statistics and the like of the automatic driving vehicle are mainly achieved, the fault prediction capacity and the fault rapid solving capacity of the automatic driving vehicle in the running process are effectively improved, and the driving safety of the automatic driving vehicle is improved.

Description

Technical Field

[0001] This invention belongs to the field of intelligent connected vehicles, specifically relating to a remote monitoring platform for autonomous vehicles based on VUE and aggregation engineering. Background Technology

[0002] With the strong development trend of advocating for intelligent, connected, and energy-efficient vehicles, vehicle remote monitoring platforms are widely used by major automakers due to their advantages such as real-time monitoring of vehicle driving conditions, prediction of vehicle malfunctions, and control of safe vehicle operation. With the continuous breakthroughs in autonomous driving technology in recent years, autonomous vehicles have become important monitoring targets for remote monitoring platforms. Traditional vehicle remote monitoring platforms mainly monitor vehicle data and GPS data to analyze vehicle driving conditions. They trigger the vehicle controller to operate the vehicle by issuing control commands. The platform uses HTML and CSS published by W3C to build the DOM tree and uses jQuery in conjunction with native JavaScript events and plugins for dynamic interaction. It adopts a self-designed modular engineering approach and uses native SQL for data processing, primarily using small-scale MySQL databases.

[0003] The aforementioned implementation currently only monitors vehicle data and GPS data, and can only monitor vehicle driving status and vehicle controller status, not autonomous driving status. Therefore, it cannot predict faults or provide remote control for autonomous vehicles. Furthermore, the implementation uses outdated technology, resulting in slow platform page response times, long project setup times, and redundant and chaotic module dependency management. To address these issues, this paper removes vehicle data monitoring unrelated to autonomous driving and adds autonomous driving data monitoring, including sensors, perception decision control algorithms, and domain controllers. By comparing and analyzing real-world data with normal data generated during operation, potential faults are predicted, improving fault prediction capabilities. Instead of separate control of the drive-by-wire chassis, a combined control system using the drive-by-wire chassis and autonomous driving domain controller is adopted. This allows for safe and efficient vehicle control via commands when the platform remotely takes over the vehicle, quickly and efficiently resolving autonomous driving faults and providing convenience for remote vehicle use. The development utilizes Vue.js and aggregated engineering to improve platform page response speed, rapidly build modular projects, effectively manage inter-module dependencies, and simplify platform project deployment, laying a solid foundation for building a highly practical software platform. Summary of the Invention

[0004] To overcome the shortcomings of existing technologies, this invention provides a remote monitoring platform for autonomous vehicles based on VUE and aggregation engineering. It collects autonomous driving system data in real time through tcpSocket and uses VUE and Spring Boot aggregation engineering technology to develop a remote monitoring platform for autonomous vehicles to solve the above-mentioned problems.

[0005] To address the aforementioned problems in the existing technology, the technical solution adopted by this invention is as follows:

[0006] A remote monitoring platform for autonomous vehicles based on VUE and aggregation engineering, including

[0007] The application layer is used for view drawing, dynamic event interaction, and route navigation;

[0008] The data layer provides the application layer with data creation, deletion, modification, and query communication interfaces, and provides the gateway with monitoring and control request data.

[0009] The gateway is the layer that connects the platform and the external vehicle, providing vehicle data to the application layer and responding to application layer requests by sending them to the vehicle.

[0010] Furthermore, the application layer includes:

[0011] The login module, as the first interface accessed by the platform, is used for users to log in. In addition to providing username and password login and verification code verification, the upper left corner of the page displays the company logo, the lower center displays the software's parent company, and the background shows the company's best-selling products, so that users can log in with peace of mind.

[0012] The user management module, as a fundamental module of the platform, is used to manage basic user information, including username, password, phone number, email address, and user level. Specifically, it allows users to create new users, update existing users, delete existing users, and query user information.

[0013] The role management module, as a basic module of the platform, is closely related to the user management module. It assigns permissions to roles and assigns roles to users, giving them the module usage rights for that role.

[0014] The vehicle management module, as the basic module of the platform, is used to manage basic vehicle information, including VIN, license plate number, type, load, various sensor models and quantities, and controller models and quantities.

[0015] The alarm management module, as a functional module of the platform, is used to record fault information reported by the vehicle controller and the autonomous driving domain controller in real time, and provides fault handling methods.

[0016] The vehicle monitoring module, as a core functional module of the platform, is mainly used for real-time vehicle monitoring. This includes real-time vehicle location tracking, autonomous driving status data monitoring, overall vehicle data monitoring, and real-time statistics of autonomous driving fault lists.

[0017] The remote control module, as the core functional module of the platform, is mainly used for remote vehicle control. This includes remote vehicle start, remote engine shutdown, command logging, and command detail retrieval.

[0018] The operations reporting module, as a core functional module of the platform, is mainly used for autonomous driving fault statistics. It calculates the number of faults on a weekly, monthly, and yearly basis for the resource usage of various autonomous driving sensors, perception decision-making control algorithm modules, and controllers. It supports fault data recording within one year and fault data statistics for any time period within one year, using 3D bar charts for statistical analysis.

[0019] Furthermore, the real-time vehicle positioning includes:

[0020] Location strategy: Update location information every 3 seconds.

[0021] Location data: longitude and latitude.

[0022] Location operation: Click on the vehicle location point, the map will zoom in 10 times, the location point will be highlighted and centered, and an info box will pop up above the vehicle location point to display the current basic information of the vehicle, including speed, mileage, gear, throttle, fuel consumption, etc.

[0023] Furthermore, the autonomous driving status data monitoring and real-time list statistics of autonomous driving faults include:

[0024] Monitoring data: various sensors for autonomous driving, domain controllers, perception, decision-making and control algorithm modules, CPU, and memory.

[0025] Monitoring strategy: Update information every 3 seconds. If the difference between the monitored vehicle time and the actual time is greater than 5 minutes, monitoring will begin from the current time.

[0026] Monitoring triggered: Select a vehicle from the vehicle list.

[0027] Furthermore, the aforementioned vehicle data monitoring mainly includes:

[0028] Data: Start-up status, speed, mileage, gear, throttle, fuel consumption / gas consumption / SOC, temperature, voltage.

[0029] Monitoring strategy: Update information every 3 seconds. If the difference between the monitored vehicle time and the actual time is greater than 5 minutes, monitoring will begin from the current time.

[0030] Monitoring triggered: Select a vehicle from the vehicle list.

[0031] Furthermore, the data layer includes:

[0032] User services are used for user data processing, including user login / logout, user creation, user modification, user query, and user deletion.

[0033] Vehicle services are used for vehicle data processing, including adding vehicles, modifying vehicle information, querying vehicle information, and deleting obsolete vehicles.

[0034] Alarm service for real-time processing of autonomous driving alarms and vehicle alarm data. This includes sensor faults, domain controller storage faults, memory operation faults, and various vehicle controller faults.

[0035] Reporting services are used for calculating statistical data on autonomous driving faults. This includes various sensors, domain controllers, perception and decision-making control algorithms, memory, and CPU.

[0036] The monitoring service is used for real-time processing of vehicle GPS data, autonomous driving data, and overall vehicle data. It receives vehicle monitoring requests from the application-layer vehicle monitoring module and transmits response data back in real time. It filters alarm data and statistical reports for database storage.

[0037] The control service is used for processing data related to remote vehicle start-up and remote engine shutdown. It records the time, parameters, and results of both types of commands.

[0038] Furthermore, the gateway includes:

[0039] Real-time monitoring service: used to collect vehicle autonomous driving data and whole vehicle data in real time, parse the data, construct a new data format JSON, and provide real-time monitoring data for the application layer.

[0040] Remote control service: Used to receive control command requests initiated by the application layer, forward them to the vehicle, receive the command execution results from the vehicle, and provide the application layer with remote control request responses and execution responses.

[0041] The beneficial effects of this invention are:

[0042] Compared to existing remote monitoring platforms, the autonomous vehicle remote monitoring platform enables the monitoring of autonomous vehicles. By leveraging operational data from various autonomous driving sensors, perception, decision-making, and control systems, as well as resource utilization data from domain controllers (memory, CPU, hard drive), it predicts autonomous driving system malfunctions and improves the operational safety of autonomous vehicles. Remote vehicle control enhances ease of use, facilitates timely troubleshooting, and improves driving safety. Attached Figure Description

[0043] Figure 1 This is a design drawing of a remote monitoring platform for autonomous vehicles.

[0044] Figure 2 This is the login screen;

[0045] Figure 3 It is a vehicle monitoring module;

[0046] Figure 4 It is a remote control module;

[0047] Figure 5It is the operations reporting module;

[0048] Figure 6 It is the alarm management module;

[0049] Figure 7 It is the vehicle management module;

[0050] Figure 8 It is the role management module;

[0051] Figure 9 It is the user management module;

[0052] Figure 10 This is the platform vehicle monitoring operation process;

[0053] Figure 11 This refers to the platform vehicle control operation process; Detailed Implementation

[0054] The present invention will be further described below with reference to the accompanying drawings and reference numerals.

[0055] To better understand the above-mentioned objectives, features, and advantages of the present invention, the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that, unless otherwise specified, the embodiments and features described in these embodiments can be combined with each other.

[0056] The terms “first,” “second,” “third,” etc., are used only to distinguish descriptions and should not be interpreted as indicating or implying relative importance.

[0057] In the description of this invention, it should also be noted that, unless otherwise explicitly specified and limited, the terms "set," "install," "connect," and "link" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0058] The specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for illustration and explanation only and are not intended to limit the present invention.

[0059] Example 1:

[0060] like Figure 1 As shown, an autonomous vehicle remote monitoring platform based on VUE and aggregation engineering includes...

[0061] The application layer is used for view drawing, dynamic event interaction, and route navigation;

[0062] The data layer provides the application layer with data creation, deletion, modification, and query communication interfaces, and provides the gateway with monitoring and control request data.

[0063] The gateway is the layer that connects the platform and the external vehicle, providing vehicle data to the application layer and responding to application layer requests by sending them to the vehicle.

[0064] The application layer uses Vue to quickly build the website, while the data layer uses aggregated engineering to quickly build modular projects. It primarily implements functions such as real-time monitoring of autonomous vehicles, remote start-up, remote shutdown, 3D bar chart statistics of autonomous driving faults, and real-time table statistics. This effectively improves the fault prediction and rapid fault resolution capabilities of autonomous vehicles during operation, thereby enhancing their driving safety.

[0065] Example 2:

[0066] Based on Example 1, the application layer includes:

[0067] The login module, serving as the first interface accessed by the platform, is used for user login. In addition to providing username and password login and verification code verification, the page displays the company logo in the upper left corner, the software's parent company's name in the lower center, and the company's best-selling products in the background, ensuring a secure login experience for users. Figure 2 The image shows the login interface, which serves as the first page for initial access to the platform. Users enter the platform's URL in their browser, run the homepage, and log in using their username, password, and verification code.

[0068] The user management module, as a fundamental module of the platform, is used to manage basic user information, including username, password, phone number, email address, and user level. This includes creating new users, updating existing users, deleting existing users, and querying user information. Figure 9 The user management module shown is a basic module of the platform. It is used to manage platform login users and supports users in changing their passwords, creating new users, and updating personal information.

[0069] The role management module, as a fundamental module of the platform, is closely related to the user management module. It assigns permissions to roles and roles to users, granting them the module usage rights for those roles. For example... Figure 8 The diagram shows the role management module, which serves as a fundamental module of the platform. It manages user permissions for using modules and supports users in updating permissions on a module-by-module basis.

[0070] The vehicle management module, as a fundamental module of the platform, is used to manage basic vehicle information, including VIN, license plate number, type, load capacity, various sensor models and quantities, and controller models and quantities. Figure 7 The image shows the vehicle management module.

[0071] The alarm management module, as a functional module of the platform, is used to record fault information reported by the vehicle controller and the autonomous driving domain controller in real time, and provides fault handling methods.

[0072] The vehicle monitoring module, as a core functional module of the platform, is primarily used for real-time vehicle monitoring. This includes real-time vehicle location tracking, autonomous driving status data monitoring, overall vehicle data monitoring, and real-time statistics of autonomous driving fault lists. Figure 3 The vehicle monitoring module shown is the core monitoring module of the platform, used for real-time vehicle positioning and real-time monitoring of vehicle-side data. It realizes the monitoring of the autonomous driving system and includes various sensors, algorithm modules, and controllers. It realizes the monitoring of the entire vehicle status, including speed, cumulative mileage, gear position, fuel consumption / gas consumption / SOC, etc.

[0073] The remote control module, as a core functional module of the platform, is mainly used for remote vehicle control. This includes remote vehicle start, remote engine shutdown, command logging, and command detail retrieval. Figure 4 The diagram shows the remote control module, which serves as the core control module of the platform and is used to meet the needs of users in remote vehicle use and obstacle avoidance scenarios. It enables the platform to switch between remote, autonomous driving, and vehicle-wide control of the vehicle, including remote start and remote shutdown.

[0074] The operations reporting module, as a core functional module of the platform, is primarily used for autonomous driving fault statistics. It statistically analyzes the number of faults by week, month, and year for various autonomous driving sensors, perception and decision-making control algorithm modules, and controller resource usage. It supports fault data recording within one year and fault data statistics for any time period within one year, using 3D bar charts for statistical analysis. Figure 5 The diagram shows the operation report module, which serves as the platform's statistical function module. It provides monthly and yearly statistics on faults of various sensors, perception and decision-making control algorithms, and domain controllers for autonomous driving, supporting fault statistics for any time period within the past year. This is used by autonomous driving developers for algorithm testing and verification, and by autonomous driving operators for fault prediction and identification, as well as for data analysis of autonomous driving algorithm performance.

[0075] When a user needs to monitor a vehicle in real time, according to... Figure 10 The process operation must ensure that the vehicle is online and that the platform updates location information, autonomous driving data, vehicle data, and fault statistics lists in real time.

[0076] First, log in to your account to access the system, obtain vehicle information, display the vehicle list, obtain real-time GPS data, perform real-time vehicle positioning, receive the vehicles you want to acquire, and display and update the vehicle information.

[0077] When a user issues a control command, according to Figure 11The process operation meets the issuance and control execution conditions, allowing users to remotely control the vehicle.

[0078] Example 3:

[0079] Based on Example 2, the real-time vehicle positioning includes:

[0080] Location strategy: Update location information every 3 seconds.

[0081] Location data: longitude and latitude.

[0082] Location operation: Click on the vehicle location point, the map will zoom in 10 times, the location point will be highlighted and centered, and an info box will pop up above the vehicle location point to display the current basic information of the vehicle, including speed, mileage, gear, throttle, fuel consumption, etc.

[0083] Furthermore, the autonomous driving status data monitoring and real-time list statistics of autonomous driving faults include:

[0084] Monitoring data: various sensors for autonomous driving, domain controllers, perception, decision-making and control algorithm modules, CPU, and memory.

[0085] Monitoring strategy: Update information every 3 seconds. If the difference between the monitored vehicle time and the actual time is greater than 5 minutes, monitoring will begin from the current time.

[0086] Monitoring triggered: Select a vehicle from the vehicle list.

[0087] Furthermore, the aforementioned vehicle data monitoring mainly includes:

[0088] Data: Start-up status, speed, mileage, gear, throttle, fuel consumption / gas consumption / SOC, temperature, voltage.

[0089] Monitoring strategy: Update information every 3 seconds. If the difference between the monitored vehicle time and the actual time is greater than 5 minutes, monitoring will begin from the current time.

[0090] Monitoring triggered: Select a vehicle from the vehicle list.

[0091] Example 4:

[0092] Based on Example 2, the data layer includes:

[0093] User services are used for user data processing, including user login / logout, user creation, user modification, user query, and user deletion.

[0094] Vehicle services are used for vehicle data processing, including adding vehicles, modifying vehicle information, querying vehicle information, and deleting obsolete vehicles.

[0095] Alarm service for real-time processing of autonomous driving alarms and vehicle-wide alarm data. This includes sensor faults, domain controller storage faults, memory operation faults, and various vehicle controller faults. For example... Figure 6 The alarm management module is shown. As a functional module of the platform, the table manages various faults reported by the vehicle and autonomous driving system in real time, provides fault handling methods, and records fault handling feedback results.

[0096] Reporting services are used for calculating statistical data on autonomous driving faults. This includes various sensors, domain controllers, perception and decision-making control algorithms, memory, and CPU.

[0097] The monitoring service is used for real-time processing of vehicle GPS data, autonomous driving data, and overall vehicle data. It receives vehicle monitoring requests from the application-layer vehicle monitoring module and transmits response data back in real time. It filters alarm data and statistical reports for database storage.

[0098] The control service is used for processing data related to remote vehicle start-up and remote engine shutdown. It records the time, parameters, and results of both types of commands.

[0099] Example 5:

[0100] Based on Example 4, the gateway includes:

[0101] Real-time monitoring service: used to collect vehicle autonomous driving data and whole vehicle data in real time, parse the data, construct a new data format JSON, and provide real-time monitoring data for the application layer.

[0102] Remote control service: Used to receive control command requests initiated by the application layer, forward them to the vehicle, receive the command execution results from the vehicle, and provide the application layer with remote control request responses and execution responses.

[0103] This invention is not limited to the above-described optional embodiments. Anyone can derive other various forms of products under the guidance of this invention. However, regardless of any changes made in their shape or structure, any technical solution that falls within the scope of the claims of this invention shall be protected by this invention.

Claims

1. A remote monitoring platform for autonomous vehicles based on VUE and aggregated engineering, characterized in that: The application layer is used for view drawing, dynamic event interaction, and route navigation; The data layer provides data to the application layer and monitoring and control request data to the gateway; The gateway provides vehicle-side data to the application layer and responds to application layer requests by sending them to the vehicle.

2. The remote monitoring platform for autonomous vehicles based on VUE and aggregated engineering according to claim 1, characterized in that: The application layer includes: The login module is used for users to log in; The user management module is used to manage basic user information; The role management module assigns permissions to roles and assigns roles to users, granting them access to the module for that role. The vehicle management module is used to manage basic vehicle information; The alarm management module is used to record fault information reported by the vehicle controller and the autonomous driving domain controller in real time. The vehicle monitoring module is used for real-time vehicle monitoring, including real-time vehicle positioning, autonomous driving status data monitoring, whole vehicle data monitoring, and real-time list statistics of autonomous driving faults. Remote control module, used for remote vehicle control; The operations report module is used for statistics on autonomous driving faults.

3. The remote monitoring platform for autonomous vehicles based on VUE and aggregated engineering according to claim 2, characterized in that: The real-time vehicle location includes: Location strategy: Update location information every 3 seconds; Location data: longitude and latitude.

4. The remote monitoring platform for autonomous vehicles based on VUE and aggregated engineering according to claim 2, characterized in that: The autonomous driving status data monitoring and real-time list statistics of autonomous driving faults include: Monitoring data: various sensors for autonomous driving, domain controllers, perception, decision-making and control algorithm modules, CPU, and memory. Monitoring strategy: Update information every 3 seconds. If the difference between the monitored vehicle time and the actual time is greater than 5 minutes, monitoring will start from the current time.

5. The remote monitoring platform for autonomous vehicles based on VUE and aggregated engineering according to claim 1, characterized in that: The vehicle data monitoring mainly includes: Data: Start-up status, speed, mileage, gear, throttle, fuel consumption / gas consumption / SOC, temperature, voltage; Monitoring strategy: Update information every 3 seconds.

6. The remote monitoring platform for autonomous vehicles based on VUE and aggregated engineering according to claim 1, characterized in that: The data layer includes: User services are used for user data processing; Vehicle services, used for vehicle data processing; Alarm service for real-time processing of autonomous driving alarm and vehicle alarm data; Reporting services are used for calculating statistical data on autonomous driving faults. The monitoring service is used for real-time processing of vehicle GPS data, autonomous driving data, and whole vehicle data, and receives vehicle monitoring requests from the application layer vehicle monitoring module and transmits response data back in real time. Control services are used for data processing related to remote vehicle start-up and remote engine shutdown.

7. The remote monitoring platform for autonomous vehicles based on VUE and aggregated engineering according to claim 1, characterized in that: The gateway includes: Real-time monitoring service: Used to collect vehicle autonomous driving data and vehicle data in real time, analyze the data, and provide real-time monitoring data for the application layer. Remote control service: Used to receive control command requests initiated by the application layer, forward them to the vehicle, receive the command execution results from the vehicle, and provide the application layer with remote control request and execution responses.

Images