Vehicle end data remote acquisition method and system suitable for unmanned vehicle

Abstract

The invention discloses a vehicle end data remote acquisition method and system suitable for an unmanned vehicle. The method comprises the steps of issuing a pre-configured vehicle end data uploading strategy to a vehicle end according to a vehicle end data acquisition requirement; wherein the vehicle end data uploading strategy comprises a first data uploading strategy in a non-vehicle end abnormal scene and a second data uploading strategy in a vehicle end abnormal scene; receiving first vehicle end data uploaded by the vehicle end according to the first data uploading strategy; receiving second vehicle end data actively uploaded according to a second data uploading strategy corresponding to the abnormal scene when the vehicle end is in the abnormal scene; wherein the data uploading priority of the second vehicle end data is greater than the data uploading priority of the first vehicle end data; according to the embodiment of the invention, through the above technical scheme, high efficiency of remote acquisition of the vehicle-end data can be realized, pressure and resource loss of vehicle-end data storage are effectively reduced, and loss or coverage of the vehicle-end data in an abnormal scene is avoided.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a method and system for remotely acquiring vehicle-side data applicable to unmanned vehicles. Background Art

[0002] With the rapid development of autonomous driving technology, unmanned vehicles are increasingly used in transportation, logistics, agriculture and other fields. Unmanned vehicles use various sensors and communication devices to perceive the environment, plan paths and perform driving tasks in real time. The large amount of data generated during these operations is of great value for the research and development, debugging, optimization and operation monitoring of unmanned vehicles. Therefore, how to efficiently and reliably obtain and transmit unmanned vehicle-side data has become a key technical issue.

[0003] For the acquisition and management of vehicle-side data, the traditional solution has always been mainly centered around the vehicle side, recording vehicle-side data through external data recorders or local storage, and then after-sales or R&D personnel extract the required data on site for data analysis and comparison. At present, with the increasing functions of unmanned vehicles, the hardware and software data involved are constantly increasing. The traditional vehicle-side data recording and acquisition methods face great challenges in storage space, which makes the already cramped storage resources of the vehicle even more stretched. In addition, from the acquisition method, the traditional solution can only extract data through after-sales operation and maintenance or R&D personnel personally going to the vehicle site. This data acquisition method is inefficient and costly. If there is an occasional vehicle failure problem, it is impossible to obtain the vehicle data at the time in the first time, which seriously affects the troubleshooting and analysis of vehicle problems. Therefore, there is an urgent need for a vehicle-side data acquisition method with lower resource consumption, stronger real-time performance, higher efficiency, and more convenient management, which has become the key to providing strong support for the widespread application of unmanned vehicles. Summary of the invention

[0004] In view of this, the present invention provides a method and system for remotely acquiring vehicle-side data suitable for unmanned vehicles, which can achieve high efficiency in data acquisition, reduce the pressure and resource loss of vehicle-side data storage, and especially provide an effective solution for capturing vehicle-side data in abnormal vehicle scenarios, thereby avoiding the loss or overwriting of vehicle-side data in abnormal scenarios and providing a data basis for locating and troubleshooting vehicle problems and faults of unmanned vehicles.

[0005] According to one aspect of the present invention, an embodiment of the present invention provides a method for remotely acquiring vehicle-side data applicable to an unmanned vehicle, which is applied to a cloud server, and the cloud server communicates with the vehicle-side through the HTTP network communication protocol; the method for remotely acquiring vehicle-side data includes:

[0006] The pre-configured vehicle-side data upload strategy is sent to the vehicle-side according to the vehicle-side data collection requirements; wherein the vehicle-side data upload strategy includes: a first data upload strategy in a non-vehicle-side abnormal scenario and a second data upload strategy in a vehicle-side abnormal scenario;

[0007] Receiving first vehicle-side data uploaded by the vehicle-side according to the first data uploading strategy;

[0008] When the vehicle is in an abnormal scenario, second vehicle data that is actively uploaded according to a second data upload strategy corresponding to the abnormal scenario is received; wherein the data upload priority of the second vehicle data is greater than the data upload priority of the first vehicle data.

[0009] According to another aspect of the present invention, an embodiment of the present invention further provides a method for remotely acquiring vehicle-side data applicable to an unmanned vehicle.

[0010] Applied to the vehicle side, the vehicle side is equipped with a communication module, and communicates with the cloud server through the HTTP network communication protocol. The vehicle side data remote acquisition method includes:

[0011] Obtaining the vehicle-side data upload strategy issued by the cloud server according to the vehicle-side data collection requirements; wherein the vehicle-side data upload strategy includes: a first data upload strategy in a non-abnormal scenario and a second data upload strategy in an abnormal scenario;

[0012] Uploading the first vehicle-side data corresponding to the vehicle-side data collection requirement to the cloud server according to the first data uploading strategy;

[0013] When the vehicle is in an abnormal scenario, the second vehicle data under the abnormal scenario is actively uploaded to the cloud server according to the second data upload strategy corresponding to the abnormal scenario; wherein the data upload priority of the second vehicle data is greater than the data upload priority of the first vehicle data.

[0014] According to another aspect of the present invention, an embodiment of the present invention further provides a vehicle-side data remote acquisition system applicable to an unmanned vehicle, which is applied to a cloud server, and the cloud server communicates with the vehicle-side through the HTTP network communication protocol; the vehicle-side data remote acquisition system includes:

[0015] A strategy delivery module, used to deliver the pre-configured vehicle-side data upload strategy to the vehicle-side according to the vehicle-side data collection requirements; wherein the vehicle-side data upload strategy includes: a first data upload strategy in a non-vehicle-side abnormal scenario and a second data upload strategy in a vehicle-side abnormal scenario;

[0016] A first data receiving module, used for receiving first vehicle-side data uploaded by the vehicle-side according to the first data uploading strategy;

[0017] The second data receiving module is used to receive second vehicle-side data actively uploaded according to a second data upload strategy corresponding to the abnormal scenario when the vehicle-side is in an abnormal scenario; wherein the data upload priority of the second vehicle-side data is greater than the data upload priority of the first vehicle-side data.

[0018] According to another aspect of the present invention, an embodiment of the present invention further provides a vehicle-side data remote acquisition system applicable to an unmanned vehicle, which is applied to the vehicle side, wherein the vehicle side is equipped with a communication module and communicates with a cloud server through an HTTP network communication protocol. The vehicle-side data remote acquisition system includes:

[0019] A strategy acquisition module, used to acquire the vehicle-side data upload strategy issued by the cloud server according to the vehicle-side data collection requirements; wherein the vehicle-side data upload strategy includes: a first data upload strategy in a non-abnormal scenario and a second data upload strategy in an abnormal scenario;

[0020] A first data uploading module, configured to upload first vehicle-side data corresponding to the vehicle-side data collection requirement to a cloud server according to the first data uploading strategy;

[0021] The second data uploading module is used to actively upload the second vehicle-side data in the abnormal scenario to the cloud server according to the second data uploading strategy corresponding to the abnormal scenario when the vehicle-side is in an abnormal scenario; wherein the data uploading priority of the second vehicle-side data is greater than the data uploading priority of the first vehicle-side data.

[0022] The technical effect of the present invention lies in that, by sending a pre-configured vehicle-side data upload strategy to the vehicle-side, and receiving the first vehicle-side data passively uploaded by the vehicle-side according to the first data upload strategy, and the second vehicle-side data actively uploaded according to the second data upload strategy corresponding to the abnormal scene when the vehicle-side is in an abnormal scene, the first data upload strategy is used to enable the vehicle-side to passively upload the first vehicle-side data in real time or periodically according to the strategy, and by pre-configuring the second data upload strategy on the vehicle-side, the vehicle-side actively uploads the corresponding second vehicle-side data to the cloud when it is in the abnormal level corresponding to the abnormal scene, thereby achieving high efficiency of data acquisition, reducing the pressure and resource loss of vehicle-side data storage, and especially providing an effective solution for capturing vehicle-side data in abnormal vehicle scenes, thereby avoiding the loss or overwriting of vehicle-side data in abnormal scenes.

[0023] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0025] Figure 1 A flowchart of a method for remotely acquiring vehicle-side data applicable to an unmanned vehicle provided in one embodiment of the present invention;

[0026] Figure 2 A flowchart of another method for remotely acquiring vehicle-side data applicable to an unmanned vehicle provided by an embodiment of the present invention;

[0027] Figure 3 A flowchart of a method for remotely acquiring vehicle-side data applicable to an unmanned vehicle provided in one embodiment of the present invention;

[0028] Figure 4 A structural diagram of a method for remotely acquiring vehicle-side data applicable to an unmanned vehicle provided in one embodiment of the present invention;

[0029] Figure 5 A structural block diagram of a vehicle-side data remote acquisition system applicable to an unmanned vehicle provided in one embodiment of the present invention;

[0030] Figure 6 A structural block diagram of a vehicle-side data remote acquisition system suitable for an unmanned vehicle provided in one embodiment of the present invention. DETAILED DESCRIPTION

[0031] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0032] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0033] In one embodiment, Figure 1 A flowchart of a method for remotely acquiring vehicle-side data applicable to an unmanned vehicle is provided for one embodiment of the present invention. This embodiment can be applied to the situation when the vehicle-side data of an unmanned vehicle is remotely acquired. The method can be executed by a remote acquisition system for vehicle-side data applicable to an unmanned vehicle.

[0034] like Figure 1 As shown, the vehicle-side data remote acquisition method applicable to the unmanned vehicle in this embodiment is applied to a cloud server, and the cloud server communicates with the vehicle-side through the Hypertext Transfer Protocol (HTTP) network communication protocol; the vehicle-side data remote acquisition method specifically includes the following steps:

[0035] S110. Send the pre-configured vehicle-side data upload strategy to the vehicle-side according to the vehicle-side data collection requirements; wherein the vehicle-side data upload strategy includes: a first data upload strategy in a non-vehicle-side abnormal scenario and a second data upload strategy in a vehicle-side abnormal scenario.

[0036] Among them, the vehicle-side data collection requirements are the user's data collection requirements corresponding to each vehicle-side. The data collection requirements can be set by the user on the cloud server. The data collection requirements corresponding to each vehicle-side can be the same or different, and can be customized according to actual needs.

[0037] In this embodiment, the vehicle-side data upload strategy is a data upload strategy formulated by the user for the terminal communicating with the cloud server. In this embodiment, the vehicle-side data upload strategy may include a first data upload strategy for non-vehicle-side abnormal scenarios and a second data upload strategy for vehicle-side abnormal scenarios, wherein the first data upload strategy is a vehicle-side data upload strategy issued by the cloud server in real time or periodically in non-vehicle-side abnormal scenarios. After the vehicle-side data upload strategy is sent to the vehicle in real time or periodically, the vehicle can passively upload the first vehicle-side data corresponding to the vehicle-side data collection demand to the cloud server according to the first data upload strategy. The passive upload in this embodiment means that the cloud server sends a certain strategy to the vehicle in real time or periodically. When the vehicle receives the strategy, it uploads the vehicle-side data corresponding to the strategy in real time or periodically as required in vehicle-side abnormal scenarios. The second data upload strategy can be understood as the cloud server directly sending the second data upload strategy to the vehicle side after formulating the data upload strategy. After receiving the second data upload strategy, the vehicle side configures it on the vehicle side. During the driving of the unmanned vehicle, the vehicle side detects in real time whether the current scene of the vehicle is abnormal. If there is no abnormal scene on the vehicle side, the corresponding vehicle-side data will not be uploaded, and the vehicle-side data will only be uploaded according to the first data upload strategy. If an abnormal scene occurs on the vehicle side, the vehicle side will actively upload the second vehicle-side data under the abnormal scene to the cloud server according to the second data upload strategy corresponding to the abnormal scene. It should be noted that if the above two scenarios exist at the same time, the data upload priority of the second vehicle-side data is greater than the data upload priority of the first vehicle-side data, that is, the execution priority of the second data upload strategy is higher than the execution priority of the first data upload strategy.

[0038] In this embodiment, the vehicle side is equipped with a communication module, and the cloud server communicates with each vehicle side through the HTTP network communication protocol to upload the corresponding vehicle side data to the cloud server. In this embodiment, since the first data upload strategy and the second data upload strategy are both configured strategies, the configuration of the first data upload strategy may include but is not limited to the vehicle number of each vehicle side, the data collection time of the vehicle side data collected by the vehicle side, the type of data required to be uploaded by each vehicle side, and the data upload time of each vehicle side, one or at least two of them as strategies under the screening conditions. It can be understood that the user can send the vehicle number corresponding to the vehicle side, the data collection time of the vehicle side data, the type of data required to be uploaded by the vehicle side, and the data upload time of each vehicle side as screening conditions to the corresponding vehicle side in the cloud, so as to flexibly select the data to be uploaded through the cloud for data upload.

[0039] In this embodiment, the configuration of the second data upload strategy may include but is not limited to the following situations: in the case of a first level abnormality, the first abnormal data corresponding to the first level abnormality is uploaded to the cloud server according to the first time window; in the case of a second level abnormality, the second abnormal data corresponding to the second level abnormality is uploaded to the cloud server according to the second time window; in the case of a third level abnormality, the third abnormal data corresponding to the third level abnormality is uploaded to the cloud server according to the third time window; wherein the first time window is less than or equal to the second time window; the second time window is less than the third time window, the first abnormal data includes vehicle control data and vehicle status data; the second abnormal data includes: vehicle control data and vehicle status data; the third abnormal data includes: vehicle control data, vehicle log data, and vehicle status data. Exemplarily, the first abnormal data includes CAN data; the second abnormal data includes: CAN data; the third abnormal data includes: CAN data and communication data. It can be understood that, for the abnormal scenario in which the vehicle is located, the corresponding abnormal level, the data upload time range corresponding to the abnormal level, and the abnormal data corresponding to the abnormal level are pre-set. Once the vehicle recognizes the abnormal scenario, it matches the recognized current abnormal scenario with the second data upload strategy issued by the cloud to obtain the abnormal level corresponding to the current abnormal scenario, the data upload time range corresponding to the abnormal level, and the corresponding abnormal data, and upload them to the cloud server.

[0040] S120. Receive first vehicle-side data uploaded by the vehicle-side according to the first data uploading strategy.

[0041] Among them, the first vehicle-side data includes: vehicle control data, vehicle status data and vehicle log data. It can be understood that during the operation of the unmanned vehicle, various types of data will be generated, which can be mainly divided into the following three categories: vehicle control data, vehicle status data and vehicle log data; among them, the vehicle control data includes but is not limited to the driving instructions, steering angle, braking signal and other control information of the unmanned vehicle, and these data can be used to verify the control algorithm and execution effect of the unmanned vehicle. The vehicle status data may include but is not limited to the speed, acceleration, direction, position, engine status, battery power and other information of the vehicle, which are used to monitor the operating status of the vehicle and ensure the safety and reliability of the unmanned vehicle. The vehicle log data may include but is not limited to system logs, fault diagnosis information, event records, etc., which are used to analyze the operation process of the unmanned vehicle, troubleshoot faults and optimize the system. In this embodiment, after the vehicle control data, vehicle status data and vehicle log data are obtained, after-sales and R&D personnel can perform data analysis on the vehicle by obtaining these data, so that the safety, real-time and intelligent level of the vehicle are further improved.

[0042] In this embodiment, the first data upload strategy of the cloud server is sent to each vehicle end. Each vehicle end receives the sent first data upload strategy, and uploads the first vehicle end data corresponding to the vehicle end data collection demand to the cloud server according to the first data upload strategy; specifically, the cloud customizes the sent strategy and specifies multiple vehicles to upload vehicle end data. The first data upload strategy may include the type of vehicle end data uploaded by each vehicle, the time of uploading the vehicle end data, etc. It can be understood that when the cloud server monitors multiple unmanned vehicles at the same time, the user can use the specific number of each vehicle as a filtering condition, and at the same time select the time and type of data, such as CAN data, log data, communication data, etc. After determining the filtering conditions, the specific data desired by the user can be obtained.

[0043] S130, receiving second vehicle-side data actively uploaded according to a second data upload strategy corresponding to the abnormal scenario when the vehicle-side is in an abnormal scenario; wherein the data upload priority of the second vehicle-side data is greater than the data upload priority of the first vehicle-side data.

[0044] The second vehicle-side data in this embodiment also includes: vehicle control data, vehicle status data and vehicle log data. Among them, the vehicle control data includes but is not limited to the driving instructions, steering angles, braking signals and other control information of the unmanned vehicle. The vehicle status data may include but is not limited to the vehicle's speed, acceleration, direction, position, engine status, battery power and other information. The vehicle log data may include but is not limited to system logs, fault diagnosis information, event records, etc. In this embodiment, after the vehicle control data, vehicle status data and vehicle log data are obtained, after-sales and R&D personnel can locate and analyze the abnormal conditions of the vehicle by obtaining these data, so that the safety, real-time and intelligent level of the vehicle are further improved.

[0045] In this embodiment, the cloud server pre-configures the second vehicle-side data upload strategy and sends it to each vehicle-side. The vehicle-side will detect the scene in real time, and when it detects that it is in an abnormal scene, each vehicle-side obtains the vehicle-side data corresponding to the abnormal scene from each vehicle-side based on the second vehicle-side data upload strategy, and uploads the vehicle-side data corresponding to the abnormal scene in the second data upload strategy to the cloud server. The cloud server stores and manages the vehicle-side data uploaded by each vehicle according to the vehicle-side data storage strategy. Since the vehicle-side will correspond to multiple data upload strategies, when uploading vehicle-side data, the data upload priority of the second vehicle-side data in the abnormal scene is used as the optimal priority for data upload.

[0046] In one embodiment, the abnormal scenario corresponds to a corresponding abnormal level; the abnormal levels are divided into first-level abnormality, second-level abnormality and third-level abnormality; the first-level abnormality is smaller than the second-level abnormality; the second-level abnormality is smaller than the third-level abnormality; wherein the first-level abnormality is an abnormal scenario that does not affect vehicle safety and user safety, and components that are not strongly related to vehicle safety; the second-level abnormality is an abnormal scenario that does not affect vehicle driving but is strongly related to vehicle safety; the third-level abnormality is an abnormal scenario that affects vehicle driving or vehicle power supply. Among them, the abnormal scenario may include but is not limited to abnormal vehicle power-off, abnormal component voltage, abnormal chassis information, etc.

[0047] In this embodiment, the abnormal level is divided into first-level abnormality, second-level abnormality and third-level abnormality, among which the first-level abnormality is the lowest level and the third-level abnormality is the highest level. In this embodiment, the first-level abnormality is an abnormal scenario that does not affect vehicle safety and user safety, as well as components that are not strongly related to vehicle safety; the second-level abnormality is an abnormal scenario that does not affect vehicle driving but is strongly related to vehicle safety; the third-level abnormality is an abnormal scenario that affects vehicle driving or vehicle power supply. It can be understood that the first level is the lowest, which is a non-critical component failure; the second level is a critical component reporting abnormality, but it does not affect driving; the third level is a vehicle power supply or driving abnormality, which is the most serious vehicle abnormal failure. Exemplarily, when a first-level or second-level fault occurs, the vehicle-side system will automatically upload the CAN data of the last 5 minutes. When a third-level fault occurs, the CAN data and communication data of the last half an hour will be uploaded.

[0048] The technical solution of the embodiment of the present invention realizes remote real-time or scheduled acquisition of vehicle-side data by issuing a preconfigured vehicle-side data upload strategy to the vehicle-side and receiving the first vehicle-side data passively uploaded by the vehicle-side according to the first data upload strategy, thereby improving the real-time performance of vehicle-side data acquisition and effectively reducing operation and maintenance costs; by issuing and configuring a preconfigured second vehicle-side data upload strategy on the vehicle-side, and receiving the second vehicle-side data actively uploaded according to the second data upload strategy corresponding to the abnormal scenario when the vehicle-side is in an abnormal scenario, thereby pre-configuring the second data upload strategy on the vehicle-side so that the vehicle-side actively uploads the corresponding second vehicle-side data to the cloud when it is in the abnormal level corresponding to the abnormal scenario, thereby achieving high efficiency in data acquisition, reducing the pressure on vehicle-side data storage and resource loss, and providing an effective solution for capturing vehicle-side data in abnormal vehicle scenarios, avoiding the loss or overwriting of vehicle-side data in abnormal scenarios, and providing a data basis for locating and troubleshooting vehicle problems and faults of unmanned vehicles.

[0049] In one embodiment, the method further includes: dynamically adjusting and updating the vehicle-side data uploading strategy.

[0050] In this embodiment, the user can dynamically adjust the first vehicle-side data upload strategy and the second vehicle-side data upload strategy on the cloud server, and the strategy update can be understood as the dynamic configuration of the cloud server to support data upload acquisition strategy. For example, a new vehicle-side data upload strategy can be added on the cloud, a data acquisition strategy for a new abnormal scenario in which the vehicle is located can be added, and the previous vehicle data upload strategy can be adjusted, etc. This embodiment does not limit this.

[0051] In one embodiment, the method further includes: performing data management and / or data analysis on the first vehicle-side data and / or the second vehicle data according to the vehicle-side data storage strategy.

[0052] In this embodiment, the vehicle-side data storage strategy is a data storage strategy configured by the user according to the vehicle-side data storage requirements. The vehicle-side data storage strategy may include but is not limited to dividing the data storage area according to the data type of the vehicle-side data, the data acquisition time, the vehicle number corresponding to the vehicle-side data, the time for scheduled data storage, the amount of data stored each time, etc., so as to store and manage each vehicle-side data, that is, cloud personnel can flexibly formulate management strategies to manage vehicle-side data and conduct subsequent data analysis and screening. It can be understood that the cloud has built a data acquisition and management platform for real-time communication between the vehicle and the cloud, realizing the cloud upload, download, management and analysis functions of vehicle-side data.

[0053] In one embodiment, Figure 2 A flowchart of another method for remotely acquiring vehicle-side data applicable to an unmanned vehicle provided in one embodiment of the present invention. Based on the above embodiments, this embodiment further refines the pre-configured vehicle-side data upload strategy sent to the vehicle-side according to the vehicle-side data collection requirements.

[0054] like Figure 2 As shown, the vehicle-side data remote acquisition method applicable to an unmanned vehicle in this embodiment may specifically include the following steps:

[0055] S210. Based on the vehicle-side data collection requirements, one or at least two of the vehicle number of each vehicle-side, the type of data required to be uploaded by each vehicle-side, and the data upload time of each vehicle-side are sent to the corresponding vehicle-side as screening conditions, so that the vehicle-side can passively upload the corresponding first vehicle-side data according to the screening conditions; wherein the screening conditions represent the first data upload strategy sent down.

[0056] The data types include at least: control data, status data and log data.

[0057] In this embodiment, the vehicle-side data collection requirements are determined, and based on the vehicle-side data collection requirements, one or at least two of the vehicle number of each vehicle-side, the data type required to be uploaded by each vehicle-side, and the data upload time of each vehicle-side are used as screening conditions and sent to one or more vehicle-sides, so that each vehicle-side passively uploads the corresponding first vehicle-side data according to the screening conditions; wherein the screening conditions represent the first data upload strategy sent, which can be understood as the cloud server sending the strategy, and the vehicle-side uploads the corresponding vehicle-side data according to the strategy when receiving the strategy, that is, the cloud formulates a regular upload strategy, and the vehicle-side passively uploads according to the regular upload strategy sent. It can be understood that the user can flexibly select the data to be uploaded by setting the corresponding upload strategy, the upload interval time, the upload data type, etc. according to the time and vehicle number through the cloud server, and after the upload is successful, it can be stored through the cloud server, which is convenient for the subsequent data management and data analysis, which not only releases the pressure of storing a large amount of data on the vehicle side, but also improves the real-time and convenience of data acquisition.

[0058] S220. According to the vehicle-side data collection requirements, the second data upload strategy configured for different abnormal levels when the vehicle-side is in an abnormal scene is sent to the corresponding vehicle-side, so that when the vehicle-side detects the corresponding abnormal scene and abnormal level, it actively uploads the second vehicle-side data in the abnormal scene to the cloud server according to the second data upload strategy corresponding to the abnormal scene.

[0059] In this embodiment, the second data upload strategy configured for different abnormal levels when the vehicle side is in an abnormal scene is sent to the corresponding vehicle side according to the vehicle side data collection requirements, so that when the vehicle side detects the corresponding abnormal scene and abnormal level, it actively uploads the second vehicle side data in the abnormal scene to the cloud server according to the second data upload strategy corresponding to the abnormal scene. Specifically, according to the vehicle side data collection requirements, the second data upload strategy configured for different abnormal levels when the vehicle side is in an abnormal scene is sent to the corresponding vehicle side, that is, the second data upload strategy corresponding to the abnormal scene is configured in the vehicle side. During the driving process of the unmanned vehicle, the scene collection device carried in the vehicle will collect the scene information of the unmanned vehicle during driving in real time, so as to automatically identify whether the vehicle is in an abnormal scene according to the scene information. If the vehicle is in an abnormal scene, the abnormal scene is matched with the corresponding second data upload strategy, and the vehicle side data is uploaded according to the corresponding data upload strategy.

[0060] More specifically, when the vehicle side identifies that the vehicle is in the first level of abnormality, the first abnormal data corresponding to the first level of abnormality is uploaded to the cloud server according to the first time window; when the vehicle side identifies that the vehicle is in the second level of abnormality, the second abnormal data corresponding to the second level of abnormality is uploaded to the cloud server according to the second time window; when the vehicle side identifies that the vehicle is in the third level of abnormality, the third abnormal data corresponding to the third level of abnormality is uploaded to the cloud server according to the third time window; wherein, the first time window, the second time window and the third time window can be understood as the time interception range required for uploading, the first time window is less than or equal to the second time window; the second time window is less than the third time window; exemplary, the first time window is within the last 5 minutes, the second time window is within the last 5 minutes, and the third time window is within the last half an hour. The first abnormal data includes CAN data; the second abnormal data includes: CAN data; the third abnormal data includes: CAN data, communication data. Exemplarily, when a first or second level fault occurs, the vehicle side system will automatically upload the CAN data of the last 5 minutes, and when a third level fault occurs, the CAN data and communication data of the last half an hour will be uploaded.

[0061] S230. Receive first vehicle-side data uploaded by the vehicle-side according to the first data uploading strategy.

[0062] S240, receiving second vehicle-side data actively uploaded according to a second data upload strategy corresponding to the abnormal scenario when the vehicle-side is in an abnormal scenario; wherein the data upload priority of the second vehicle-side data is greater than the data upload priority of the first vehicle-side data.

[0063] The technical solution of the embodiment of the present invention uses the vehicle number of each vehicle end, the type of data required to be uploaded by each vehicle end, and one or at least two of the data upload time of each vehicle end as screening conditions to send to the corresponding vehicle end according to the vehicle-end data collection requirements, so that the vehicle end passively uploads the corresponding first vehicle-end data according to the screening conditions; according to the vehicle-end data collection requirements, the second data upload strategy configured for different abnormal levels when the vehicle end is in an abnormal scene is sent to the corresponding vehicle end, so that when the vehicle end detects the corresponding abnormal scene and abnormal level, it actively uploads the second vehicle-end data in the abnormal scene to the cloud server according to the second data upload strategy corresponding to the abnormal scene, and then the cloud server receives the first vehicle-end data uploaded by the vehicle end according to the first data upload strategy, and the second vehicle-end data actively uploaded according to the second data upload strategy corresponding to the abnormal scene when the vehicle end is in the abnormal scene, which can further achieve high efficiency of data acquisition, reduce the pressure and resource loss of vehicle-end data storage, especially for vehicle-end data capture in vehicle abnormal scenes, providing an effective solution to avoid the loss or overwriting of vehicle-end data in abnormal scenes.

[0064] In one embodiment, Figure 3A flow chart of a method for remotely acquiring vehicle-side data applicable to an unmanned vehicle provided in accordance with one embodiment of the present invention. This embodiment can be applicable to situations in which vehicle-side data of an unmanned vehicle is remotely acquired. The method can be executed by a remote acquisition system for vehicle-side data applicable to an unmanned vehicle. The remote acquisition system for vehicle-side data applicable to an unmanned vehicle can be implemented in the form of hardware and / or software. The remote acquisition system for vehicle-side data applicable to an unmanned vehicle can be configured in an electronic device.

[0065] like Figure 3 As shown, the vehicle-side data remote acquisition method applicable to the unmanned vehicle in this embodiment is applied to the vehicle side, and the vehicle side is equipped with a communication module, and communicates with the cloud server through the HTTP network communication protocol. The vehicle-side data remote acquisition method specifically includes the following steps:

[0066] S310. Obtain the vehicle-side data upload strategy issued by the cloud server according to the vehicle-side data collection requirements; wherein the vehicle-side data upload strategy includes: a first data upload strategy in a non-abnormal scenario and a second data upload strategy in an abnormal scenario.

[0067] S320. Upload the first vehicle-side data corresponding to the vehicle-side data collection requirement to the cloud server according to the first data uploading strategy.

[0068] Specifically, the first vehicle-side data corresponding to the vehicle side can be uploaded to the cloud server according to the vehicle number, data type and data upload time; wherein the data type includes at least: control data, status data and log data; the first vehicle-side data includes at least: vehicle control data, vehicle status data and vehicle log data.

[0069] S330. When the vehicle side is in an abnormal scenario, actively upload the second vehicle side data in the abnormal scenario to the cloud server according to the second data upload strategy corresponding to the abnormal scenario; wherein the data upload priority of the second vehicle side data is greater than the data upload priority of the first vehicle side data.

[0070] Specifically, the second vehicle-side data in the abnormal scenario is actively uploaded to the cloud server according to the second data upload strategy corresponding to the abnormal scenario, including: when it is identified that the vehicle is in the first level of abnormality, the first abnormal data corresponding to the first level of abnormality is uploaded to the cloud server according to the first time window; when it is identified that the vehicle is in the second level of abnormality, the second abnormal data corresponding to the second level of abnormality is uploaded to the cloud server according to the second time window; when it is identified that the vehicle is in the third level of abnormality, the third abnormal data corresponding to the third level of abnormality is uploaded to the cloud server according to the third time window.

[0071] In one embodiment, in order to better understand the vehicle-side data remote acquisition method applicable to unmanned vehicles, Figure 4This is a diagram of a method for remotely acquiring vehicle-side data applicable to an unmanned vehicle provided in one embodiment of the present invention. In this embodiment, through the first data upload strategy in non-vehicle-side abnormal scenarios, remote real-time or scheduled acquisition of vehicle-side data is achieved, which improves the real-time nature of data acquisition, effectively reduces operation and maintenance costs, and solves the pain point that vehicle data must be acquired on-site; through the second data upload strategy in vehicle-side abnormal scenarios, an effective solution is provided for capturing vehicle-side data in vehicle-side abnormal scenarios. It can avoid the loss or overwriting of vehicle-side data in abnormal scenarios, and provide a data basis for locating and troubleshooting vehicle problems and faults of unmanned vehicles; cloud personnel can flexibly formulate management strategies to manage vehicle-side data and conduct subsequent data analysis and screening.

[0072] like Figure 4 As shown, the method for remotely acquiring vehicle-side data applicable to unmanned vehicles specifically includes the following steps:

[0073] a1. The vehicle side records the vehicle side data.

[0074] a2. The recorded data is stored in the vehicle-side database.

[0075] a3. The cloud server sends the pre-configured vehicle-side data upload strategy to the vehicle-side according to the vehicle-side data collection requirements. The vehicle-side data upload strategy includes: a first data upload strategy in a non-vehicle-side abnormal scenario and a second data upload strategy in a vehicle-side abnormal scenario.

[0076] a4. The vehicle side obtains the vehicle side data upload strategy issued by the cloud server according to the vehicle side data collection requirements, and configures the second data upload strategy under the vehicle side abnormal scenario on the vehicle side.

[0077] a5. The cloud uses one or at least two of the vehicle number of each vehicle terminal, the type of data required to be uploaded by each vehicle terminal, and the data upload time of each vehicle terminal as screening conditions, and the vehicle terminal uploads data to the cloud in real time or regularly according to the screening conditions.

[0078] a6. During driving, the vehicle detects the scene information in real time. When it is identified that the vehicle is in an abnormal scene, the vehicle data is automatically uploaded according to the second data uploading strategy corresponding to the abnormal scene. That is, when the vehicle monitors the corresponding abnormal scene and abnormal level, it actively uploads the vehicle data in the abnormal scene to the cloud server according to the second data uploading strategy corresponding to the abnormal scene.

[0079] a7. The cloud manages and analyzes data based on the uploaded vehicle data.

[0080] In one embodiment, Figure 5 A structural block diagram of a vehicle-side data remote acquisition system suitable for an unmanned vehicle provided in one embodiment of the present invention.

[0081] like Figure 5 As shown, the system is applied to a cloud server, and the cloud server communicates with the vehicle end through the HTTP network communication protocol; the vehicle end data remote acquisition system includes:

[0082] The strategy sending module 510 is used to send the pre-configured vehicle-side data uploading strategy to the vehicle-side according to the vehicle-side data collection requirements; wherein the vehicle-side data uploading strategy includes: a first data uploading strategy in a non-vehicle-side abnormal scenario and a second data uploading strategy in a vehicle-side abnormal scenario;

[0083] A first data receiving module 520, configured to receive first vehicle-side data uploaded by the vehicle-side according to the first data uploading strategy;

[0084] The second data receiving module 530 is used to receive second vehicle-side data that is actively uploaded according to a second data upload strategy corresponding to the abnormal scenario when the vehicle-side is in an abnormal scenario; wherein the data upload priority of the second vehicle-side data is greater than the data upload priority of the first vehicle-side data.

[0085] The embodiments of the present invention, by sending a pre-configured vehicle-side data upload strategy to the vehicle-side, and receiving first vehicle-side data passively uploaded by the vehicle-side according to the first data upload strategy, and second vehicle-side data actively uploaded according to the second data upload strategy corresponding to the abnormal scenario when the vehicle-side is in an abnormal scenario, thereby enabling the vehicle-side to passively upload the first vehicle-side data through the first data upload strategy, and pre-configuring the second data upload strategy on the vehicle-side so that the vehicle-side actively uploads the corresponding second vehicle-side data to the cloud when it is in the abnormal level corresponding to the abnormal scenario, thereby achieving high efficiency in data acquisition, reducing the pressure on vehicle-side data storage and resource loss, and especially providing an effective solution for capturing vehicle-side data in abnormal vehicle scenarios, thereby avoiding the loss or overwriting of vehicle-side data in abnormal scenarios.

[0086] In one embodiment, the policy issuing module 510 includes at least one of the following:

[0087] The first strategy issuing unit is used to issue one or at least two of the vehicle number of each vehicle end, the type of data required to be uploaded by each vehicle end, and the data upload time of each vehicle end as screening conditions to the corresponding vehicle end according to the vehicle end data collection requirements, so that the vehicle end can passively upload the corresponding first vehicle end data according to the screening conditions; wherein the screening conditions represent the issued first data upload strategy; wherein the data types at least include: control data, status data and log data;

[0088] The second strategy issuing unit is used to issue the second data uploading strategy configured for different abnormal levels when the vehicle end is in an abnormal scene to the corresponding vehicle end according to the vehicle end data collection demand, so that when the vehicle end detects the corresponding abnormal scene and abnormal level, the second vehicle end data in the abnormal scene is actively uploaded to the cloud server according to the second data uploading strategy corresponding to the abnormal scene;

[0089] Wherein, the first vehicle-side data and the second vehicle-side data both include: vehicle control data, vehicle status data and vehicle log data.

[0090] In one embodiment, the abnormal scenario corresponds to a corresponding abnormal level; the abnormal level is divided into a first level abnormality, a second level abnormality and a third level abnormality; the first level abnormality is smaller than the second level abnormality; the second level abnormality is smaller than the third level abnormality;

[0091] The first level of abnormality is an abnormal scenario that does not affect vehicle safety and user safety, and is not strongly related to vehicle safety.

[0092] The second level of abnormality is an abnormal scenario of key components that does not affect vehicle driving but is strongly related to vehicle safety;

[0093] The third level of abnormality is an abnormal scenario that affects the driving of the vehicle or the power supply of the vehicle.

[0094] In one embodiment, the configuration of the second data upload strategy at least includes:

[0095] In the case of the first level of abnormality, uploading first abnormality data corresponding to the first level of abnormality to the cloud server according to the first time window;

[0096] In the case of the second level abnormality, uploading the second abnormality data corresponding to the second level abnormality to the cloud server according to the second time window;

[0097] In the case of the third level abnormality, the third abnormal data corresponding to the third level abnormality is uploaded to the cloud server according to the third time window; wherein, the first time window is less than or equal to the second time window; the second time window is less than the third time window; the first abnormal data includes vehicle control data and vehicle status data; the second abnormal data includes: vehicle control data and vehicle status data; the third abnormal data includes: vehicle control data, vehicle log data and vehicle status data.

[0098] In one embodiment, the system further comprises:

[0099] The adjustment module is used to dynamically adjust and update the vehicle-side data uploading strategy.

[0100] In one embodiment, the system further comprises:

[0101] A management module is used to manage and / or analyze the first vehicle-side data and / or the second vehicle data according to the vehicle-side data storage strategy.

[0102] The vehicle-side data remote acquisition system for unmanned vehicles provided in an embodiment of the present invention can execute the vehicle-side data remote acquisition method for unmanned vehicles applied to a cloud server provided in any embodiment of the present invention, and has functional modules and beneficial effects corresponding to the execution method.

[0103] In one embodiment, Figure 6 A structural block diagram of a vehicle-side data remote acquisition system suitable for an unmanned vehicle provided in one embodiment of the present invention.

[0104] like Figure 6 As shown, the system is applied to the vehicle side, the vehicle side is equipped with a communication module, and communicates with the cloud server through the HTTP network communication protocol. The vehicle side data remote acquisition system includes:

[0105] The strategy acquisition module 610 is used to acquire the vehicle-side data upload strategy issued by the cloud server according to the vehicle-side data collection requirements; wherein the vehicle-side data upload strategy includes: a first data upload strategy in a non-abnormal scenario and a second data upload strategy in an abnormal scenario;

[0106] A first data uploading module 620, configured to upload the first vehicle-side data corresponding to the vehicle-side data collection requirement to a cloud server according to the first data uploading strategy;

[0107] The second data uploading module 630 is used to actively upload the second vehicle-side data in the abnormal scenario to the cloud server according to the second data uploading strategy corresponding to the abnormal scenario when the vehicle-side is in an abnormal scenario; wherein the data uploading priority of the second vehicle-side data is greater than the data uploading priority of the first vehicle-side data.

[0108] In one embodiment, the second data uploading module 630 includes:

[0109] A first level data uploading unit, configured to, when recognizing that the vehicle is in a first level abnormality, upload first abnormality data corresponding to the first level abnormality to a cloud server according to a first time window;

[0110] A second level data uploading unit, for uploading second abnormality data corresponding to the second level abnormality to a cloud server according to a second time window when recognizing that the vehicle is in a second level abnormality;

[0111] The third level data uploading unit is used to upload the third abnormality data corresponding to the third level abnormality to the cloud server according to the third time window when recognizing that the vehicle is in the third level abnormality.

[0112] The vehicle-side data remote acquisition system suitable for unmanned vehicles provided in an embodiment of the present invention can execute the vehicle-side data remote acquisition method suitable for unmanned vehicles provided in any embodiment of the present invention and applied to the vehicle side, and has the corresponding functional modules and beneficial effects of the execution method.

[0113] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0114] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for remotely acquiring vehicle-side data applicable to unmanned vehicles, characterized in that: Applied to a cloud server, the cloud server communicates with the vehicle end via a hypertext transfer protocol HTTP network communication protocol; The vehicle-side data remote acquisition method comprises: The pre-configured vehicle-side data upload strategy is sent to the vehicle-side according to the vehicle-side data collection requirements; wherein the vehicle-side data upload strategy includes: a first data upload strategy in a non-vehicle-side abnormal scenario and a second data upload strategy in a vehicle-side abnormal scenario; Receiving first vehicle-side data uploaded by the vehicle-side according to the first data uploading strategy; When the vehicle is in an abnormal scenario, second vehicle data that is actively uploaded according to a second data upload strategy corresponding to the abnormal scenario is received; wherein the data upload priority of the second vehicle data is greater than the data upload priority of the first vehicle data.

2. The method according to claim 1, characterized in that The method of sending the pre-configured vehicle-side data upload strategy to the vehicle-side according to the vehicle-side data collection requirements includes at least one of the following: According to the vehicle-side data collection requirements, one or at least two of the vehicle number of each vehicle-side, the data collection time when the vehicle-side collects the vehicle-side data, the type of data required to be uploaded by each vehicle-side, and the data upload time of each vehicle-side are sent to the corresponding vehicle-side as screening conditions, so that the vehicle-side passively uploads the corresponding first vehicle-side data according to the screening conditions; wherein the screening conditions represent the first data upload strategy sent; wherein the data types at least include: control data, status data and log data; According to the vehicle-side data collection requirements, the second data upload strategy configured for different abnormal levels when the vehicle-side is in an abnormal scene is sent to the corresponding vehicle-side, so that when the vehicle-side detects the corresponding abnormal scene and abnormal level, the second vehicle-side data in the abnormal scene is actively uploaded to the cloud server according to the second data upload strategy corresponding to the abnormal scene; Wherein, the first vehicle-side data and the second vehicle-side data both include: vehicle control data, vehicle status data and vehicle log data.

3. The method according to any one of claims 1 or 2, characterized in that: The abnormal scenario corresponds to a corresponding abnormal level; the abnormal levels include first level abnormality, second level abnormality and third level abnormality; the first level abnormality is smaller than the second level abnormality; the second level abnormality is smaller than the third level abnormality; The first level of abnormality is an abnormal scenario that does not affect vehicle safety and user safety, and is not strongly related to vehicle safety. The second level of abnormality is an abnormal scenario of key components that does not affect vehicle driving but is strongly related to vehicle safety; The third level of abnormality is an abnormal scenario that affects the driving of the vehicle or the power supply of the vehicle.

4. The method according to any one of claims 1 or 2, characterized in that: The configuration of the second data upload strategy at least includes: In the case of a first level abnormality, uploading first abnormality data corresponding to the first level abnormality to a cloud server according to a first time window; In the case of a second level of abnormality, uploading second abnormality data corresponding to the second level of abnormality to the cloud server according to a second time window; In the case of a third level abnormality, the third abnormal data corresponding to the third level abnormality is uploaded to the cloud server according to the third time window; wherein, the first time window is less than or equal to the second time window; the second time window is less than the third time window; the first abnormal data includes vehicle control data and vehicle status data; the second abnormal data includes: vehicle control data and vehicle status data; the third abnormal data includes: vehicle control data, vehicle log data and vehicle status data.

5. The method according to claim 1, characterized in that The method further comprises: The vehicle-side data uploading strategy is dynamically adjusted and updated.

6. The method according to claim 1, characterized in that The method further comprises: Data management and / or data analysis are performed on the first vehicle-side data and / or the second vehicle data according to the vehicle-side data storage strategy.

7. A method for remotely acquiring vehicle-side data applicable to unmanned vehicles, characterized in that: Applied to the vehicle side, the vehicle side is equipped with a communication module, and communicates with the cloud server through the HTTP network communication protocol. The vehicle side data remote acquisition method includes: Obtaining the vehicle-side data upload strategy issued by the cloud server according to the vehicle-side data collection requirements; wherein the vehicle-side data upload strategy includes: a first data upload strategy in a non-abnormal scenario and a second data upload strategy in an abnormal scenario; Uploading the first vehicle-side data corresponding to the vehicle-side data collection requirement to the cloud server according to the first data uploading strategy; When the vehicle is in an abnormal scenario, the second vehicle data in the abnormal scenario is actively uploaded to the cloud server according to the second data upload strategy corresponding to the abnormal scenario; wherein the data upload priority of the second vehicle data is greater than the data upload priority of the first vehicle data.

8. The method according to claim 7, characterized in that The actively uploading the second vehicle-side data under the abnormal scenario to the cloud server according to the second data uploading strategy corresponding to the abnormal scenario includes: When it is identified that the vehicle is in a first level of abnormality, uploading first abnormality data corresponding to the first level of abnormality to the cloud server according to a first time window; When it is identified that the vehicle is in a second level of abnormality, uploading second abnormality data corresponding to the second level of abnormality to the cloud server according to a second time window; When it is identified that the vehicle is in a third level abnormality, third abnormality data corresponding to the third level abnormality is uploaded to the cloud server according to a third time window; wherein the first time window is less than or equal to the second time window.

9. A vehicle-side data remote acquisition system suitable for unmanned vehicles, characterized in that: Applied to a cloud server, the cloud server communicates with the vehicle end via the HTTP network communication protocol; The vehicle-side data remote acquisition system comprises: A strategy delivery module, used to deliver the pre-configured vehicle-side data upload strategy to the vehicle-side according to the vehicle-side data collection requirements; wherein the vehicle-side data upload strategy includes: a first data upload strategy in a non-vehicle-side abnormal scenario and a second data upload strategy in a vehicle-side abnormal scenario; A first data receiving module, used for receiving first vehicle-side data uploaded by the vehicle-side according to the first data uploading strategy; The second data receiving module is used to receive second vehicle-side data actively uploaded according to a second data upload strategy corresponding to the abnormal scenario when the vehicle-side is in an abnormal scenario; wherein the data upload priority of the second vehicle-side data is greater than the data upload priority of the first vehicle-side data.

10. A vehicle-side data remote acquisition system suitable for unmanned vehicles, characterized in that: Applied to the vehicle side, the vehicle side is equipped with a communication module, and communicates with the cloud server through the hypertext transfer protocol HTTP network communication protocol. The vehicle side data remote acquisition system includes: A strategy acquisition module, used to acquire the vehicle-side data upload strategy issued by the cloud server according to the vehicle-side data collection requirements; wherein the vehicle-side data upload strategy includes: a first data upload strategy in a non-abnormal scenario and a second data upload strategy in an abnormal scenario; A first data uploading module, configured to upload first vehicle-side data corresponding to the vehicle-side data collection requirement to a cloud server according to the first data uploading strategy; The second data uploading module is used to actively upload the second vehicle-side data in the abnormal scenario to the cloud server according to the second data uploading strategy corresponding to the abnormal scenario when the vehicle-side is in an abnormal scenario; wherein the data uploading priority of the second vehicle-side data is greater than the data uploading priority of the first vehicle-side data.

Images