Vehicle fault data sending method and device, equipment, storage medium and vehicle

Abstract

The invention provides a vehicle fault data sending method, device and equipment, a storage medium and a vehicle, and belongs to the technical field of vehicle fault diagnos.The method comprises the steps that original vehicle fault data are obtained, and the original vehicle fault data comprise a plurality of signals; in response to at least one triggered preset diagnosis event, freezing a signal associated with each triggered preset diagnosis event in the plurality of signals to obtain at least one frozen signal data packet; and sending the at least one frozen signal data packet and the corresponding preset diagnosis event to the cloud, wherein the at least one frozen signal data packet and the corresponding preset diagnosis event are used for remote fault diagnosis. According to the embodiment of the invention, more comprehensive fault data can be sent to the cloud, so that the remote fault diagnosis efficiency is improved.

Description

Technical Field

[0001] The present disclosure relates to the technical field of vehicle fault diagnosis, and in particular to a method, device, equipment, storage medium and vehicle for sending vehicle fault data. Background Art

[0002] As cars become more and more intelligent, the outside world can remotely obtain vehicle operation information, so that after-sales personnel can remotely diagnose vehicle faults based on the vehicle operation information, reducing the number of on-site repairs caused by vehicle failures.

[0003] At present, remote fault diagnosis can only obtain the vehicle's fault code, but the fault code cannot accurately reflect the cause of the vehicle's fault, resulting in low accuracy in vehicle fault diagnosis. Summary of the invention

[0004] The present disclosure provides a vehicle fault data sending method, device, equipment, storage medium and vehicle, which can send more comprehensive fault data to the cloud and improve the accuracy of remote fault diagnosis.

[0005] A first aspect of an embodiment of the present disclosure provides a method for sending vehicle fault data, comprising:

[0006] Acquire original vehicle fault data, where the original vehicle fault data includes multiple signals;

[0007] In response to at least one triggered preset diagnostic event, freezing a signal associated with each triggered preset diagnostic event among a plurality of signals to obtain at least one frozen signal data packet;

[0008] At least one freeze signal data packet and a corresponding preset diagnostic event are sent to the cloud, and the at least one freeze signal data packet and the corresponding preset diagnostic event are used for remote fault diagnosis.

[0009] A second aspect of an embodiment of the present disclosure provides a vehicle fault data sending device, the vehicle fault data sending device comprising:

[0010] A first acquisition module is used to acquire original vehicle fault data, where the original vehicle fault data includes multiple signals;

[0011] A freezing module, configured to freeze, in response to at least one triggered preset diagnostic event, a signal associated with each triggered preset diagnostic event among a plurality of signals to obtain at least one frozen signal data packet;

[0012] The sending module is used to send at least one freeze signal data packet and a corresponding preset diagnostic event to the cloud, and the at least one freeze signal data packet and the corresponding preset diagnostic event are used for remote fault diagnosis.

[0013] A third aspect of an embodiment of the present disclosure provides an electronic device, the electronic device comprising a memory and a processor, the memory storing a computer program, and the processor implementing the vehicle fault data sending method of the first aspect when executing the computer program.

[0014] The fourth aspect of the embodiment of the present disclosure provides a computer-readable storage medium, in which instructions are stored. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the vehicle fault data sending method of the first aspect mentioned above is implemented.

[0015] A fifth aspect of an embodiment of the present disclosure provides a vehicle, comprising the electronic device as described in the third aspect.

[0016] In the technical solution provided by the embodiment of the present disclosure, original vehicle fault data is obtained, and the original vehicle fault data includes multiple signals; in response to at least one triggered preset diagnostic event, the signal associated with each triggered preset diagnostic event in the multiple signals is frozen to obtain at least one frozen signal data packet; the at least one frozen signal data packet and the corresponding preset diagnostic event are sent to the cloud, and the at least one frozen signal data packet and the corresponding preset diagnostic event are used for remote fault diagnosis. In the embodiment of the present disclosure, for each signal corresponding to the triggered preset diagnostic event, the signal is frozen within a target time period before and after the triggering moment to obtain at least one frozen signal data packet; the frozen signal data packet reflects the signal data flow within the target time period before and after the triggering moment of the preset diagnostic event, and the number of signals is greater, so more comprehensive fault data can be sent to the cloud, thereby improving the accuracy of remote fault diagnosis. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 A system framework diagram of the vehicle fault data sending method applied in the embodiment of the present disclosure;

[0018] Figure 2 It is a schematic diagram of an overall flow of the method for sending vehicle fault data in an embodiment of the present disclosure;

[0019] Figure 3 In the embodiments of the present disclosure Figure 2 A specific flow chart of step 220;

[0020] Figure 4 In the embodiments of the present disclosure Figure 3 A specific flow chart of step 310;

[0021] Figure 5 In the embodiments of the present disclosure Figure 3 A specific flow chart of step 340;

[0022] Figure 6 In the embodiments of the present disclosure Figure 2 A specific flow chart of step 230;

[0023] Figure 7 It is another flowchart of the method for sending vehicle fault data in an embodiment of the present disclosure;

[0024] Figure 8 It is another flowchart of the method for sending vehicle fault data in an embodiment of the present disclosure;

[0025] Fig. 9 It is another flowchart of the method for sending vehicle fault data in an embodiment of the present disclosure;

[0026] Fig.10 In the embodiments of the present disclosure Fig. 9 A specific flow chart of step 227;

[0027] Fig.11 In the embodiments of the present disclosure Figure 7 A specific flow chart of step 231 in FIG.

[0028] Fig.12 A schematic diagram of a vehicle fault data sending device according to an embodiment of the present disclosure;

[0029] Fig.13 It is a structural schematic diagram of an electronic device in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0030] In order to make the purpose, technical solution and advantages of the present disclosure more clear, the present disclosure is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present disclosure and are not used to limit the present disclosure.

[0031] Before further describing the embodiments of the present disclosure in detail, the nouns and terms involved in the embodiments of the present disclosure are described. The nouns and terms involved in the embodiments of the present disclosure are subject to the following interpretations:

[0032] Preset diagnostic events: In the field of automotive electronics, diagnostic events refer to events related to vehicle fault diagnosis. Diagnostic events are usually monitored by the electronic control unit (ECU) and sensors inside the vehicle, and can be used to identify and report faults, abnormal conditions or performance changes in the vehicle. With the continuous development of automotive electronics technology, a large number of electronic control systems and sensors are integrated into the vehicle to monitor the working status of various components of the vehicle. Diagnostic events are usually monitored and triggered by the ECU inside the vehicle. The ECU monitors the working status of various components of the vehicle in real time by receiving signals from sensors and actuators. When an abnormal signal is detected or exceeds the preset threshold, the ECU will trigger the corresponding diagnostic event and record the relevant fault information. When a vehicle fails, the ECU will generate a corresponding diagnostic event and send it to the cloud, helping the cloud to quickly locate the fault point, improve maintenance efficiency and accuracy, and thus ensure the safety and reliability of the vehicle.

[0033] Freeze frame: In the field of automobile fault diagnosis, freeze frame refers specifically to when the car is abnormal or faulty, the ECU will record the vehicle operating status information at the moment the fault occurs to confirm the fault. These recorded vehicle operating status information are called freeze frames, which contain key data parameters when the fault occurs, such as engine speed, vehicle speed, throttle opening and various sensor readings, which are of great significance for fault diagnosis. Maintenance personnel can quickly locate the fault point by reading the freeze frame data and combining the fault code with the actual symptoms of the vehicle.

[0034] CAN channel: The full name is Controller Area Network (CAN) channel, which is a serial communication protocol channel commonly used in automotive and industrial control systems. It realizes data transmission and communication by transmitting electrical signals of different voltages on the communication line. The CAN channel consists of one or more buses to connect various nodes; each node contains its own processor and CAN bus interface controller, which is responsible for sending and receiving data. CAN communication uses a frame structure for data transmission. Each CAN frame consists of a start bit, a frame ID, a data field, a CRC checksum, and an end bit.

[0035] At present, vehicle fault diagnosis is performed through fault code or freeze frame analysis. However, the fault code can only indicate the result of the fault, and other useful information cannot be obtained from the fault code. At the same time, the freeze frame only includes the vehicle operation status information at the time of the fault, and the amount of data is relatively small. The amount of vehicle information carried by the fault code or freeze frame sent to the cloud by the vehicle is relatively small, resulting in low accuracy when the staff performs remote fault diagnosis. In order to solve the above problems, there is a need to send more vehicle signals to the cloud. To this end, the disclosed embodiment can send more comprehensive fault data to the cloud to improve the accuracy of remote fault diagnosis.

[0036] It should be noted that in each specific implementation of the present application, when it comes to the need to perform relevant processing based on data related to the user's identity or characteristics such as vehicle information, vehicle behavior data, vehicle historical data, and vehicle location information, the user's permission or consent will be obtained first, and the collection, use, and processing of these data will comply with relevant laws, regulations, and standards. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the disclosed embodiment will be obtained.

[0037] Description of the system architecture of the present disclosure embodiment

[0038] Figure 1 This is a system architecture diagram used by the vehicle fault data sending method according to the embodiment of the present disclosure. In this network, the vehicle terminal: various sensors, controllers, communication modules and other equipment installed on the vehicle, responsible for collecting and transmitting vehicle information. Communication network: including wireless communication technology (such as Wi-Fi, Bluetooth, cellular network, etc.) and wired communication technology (such as CAN bus, etc.), responsible for realizing information exchange between the vehicle and the cloud. Cloud: responsible for processing and analyzing the collected vehicle information and providing remote fault diagnosis services to users.

[0039] The vehicle can be a private car, such as a sedan, SUV, MPV or pickup truck. The vehicle can also be an operating vehicle, such as a van, bus, small truck or large trailer. The vehicle can be a gasoline vehicle or a new energy vehicle. When the vehicle is a new energy vehicle, it can be a hybrid vehicle or a pure electric vehicle.

[0040] General description of the disclosed embodiments

[0041] See also Figure 2 , a flow chart of a vehicle fault data sending method provided by an embodiment of the present disclosure, specifically comprising:

[0042] 210. Acquire original vehicle fault data, where the original vehicle fault data includes multiple signals;

[0043] 220. In response to at least one triggered preset diagnostic event, freeze a signal associated with each triggered preset diagnostic event among a plurality of signals to obtain at least one frozen signal data packet;

[0044] 230. Send at least one freeze signal data packet and a corresponding preset diagnostic event to the cloud, where the at least one freeze signal data packet and the corresponding preset diagnostic event are used for remote fault diagnosis.

[0045] First, the above steps 210 - 230 are briefly described.

[0046] In one embodiment, in step 210, the original vehicle fault data refers to signals related to preset diagnostic events. The preset signal arrangement table records multiple preset diagnostic events that the vehicle needs to report, and each signal involved in these preset diagnostic events needs to be acquired. Signals unrelated to the preset diagnostic events need to be discarded to avoid sending unnecessary signals to the cloud, resulting in a waste of transmission resources.

[0047] The signal arrangement table is shown in Table 1.

[0048]

[0049] Table 1

[0050] In one embodiment, in step 220, although the signal arrangement table records all preset diagnostic events that can be triggered, at the same time, the vehicle will usually only trigger a small number of preset diagnostic events. Different implementations can be used to determine the signals that need to be frozen and freeze them. For example, in one implementation, all associated signals corresponding to the preset diagnostic events that may be triggered are first grouped to obtain a candidate signal group corresponding to each preset diagnostic event; then the candidate signal group corresponding to the triggered preset diagnostic event is screened out and frozen. In another implementation, when the preset diagnostic event is triggered, the signal to be frozen is obtained according to the signal arrangement table and frozen to generate a frozen signal data packet for each preset diagnostic event.

[0051] In one embodiment, in step 230, the vehicle terminal can communicate and exchange data with the outside world through the CAN bus. The vehicle first sends the freeze signal data packet to TBOX through its own multiple CAN channels, and then TBOX forwards it to the cloud. The cloud needs to parse the received freeze signal data packet and preset diagnostic event according to the preset DBC file and signal arrangement table, so as to realize remote fault diagnosis of the vehicle. Among them, the DBC file (Database CAN) is a standard file format for describing the CAN communication protocol. Technicians can quickly parse the freeze signal data packet sent by the CAN bus through the DBC file, understand the physical meaning of different signals in the freeze signal data packet, and thus perform remote fault diagnosis. In addition to the preset diagnostic event that is triggered, the cloud also receives the freeze signal data packet corresponding to the preset diagnostic event. The signal data received by the cloud is more diversified, and more comprehensive vehicle fault data can be obtained, which improves the accuracy of remote fault diagnosis in the cloud.

[0052] The disclosed embodiment sends the preset diagnostic event and the corresponding freeze signal data packet to the cloud together, thereby improving the diversity of the signal data received by the cloud, enabling remote fault diagnosis based on more comprehensive vehicle fault data, and improving the accuracy of remote fault diagnosis.

[0053] See also Figure 3 In one embodiment, step 220 may include:

[0054] 310. Arrange the multiple signals to obtain multiple candidate signal groups, each candidate signal group corresponding to a preset diagnostic event;

[0055] 320. In response to at least one triggered preset diagnostic event, determine a triggering time and a corresponding candidate signal group corresponding to each triggered preset diagnostic event;

[0056] 330. Determine a target time period corresponding to each triggered preset diagnostic event based on each triggering moment, where the target time period includes the corresponding triggering moment;

[0057] 340. Freeze the candidate signal groups corresponding to each triggered preset diagnostic event according to the corresponding target time period to obtain at least one frozen signal data packet.

[0058] Steps 310 - 340 are described in detail below.

[0059] In step 310, when arranging multiple signals, it is necessary to refer to a preset signal arrangement table, which also records the correspondence between the preset diagnostic events and the signals involved. For example, the signal arrangement table is shown in Table 1, which records the preset diagnostic event ID and the associated signal ID. According to the ID of each preset diagnostic event, the ID of the associated signal can be obtained by looking up the table. All associated signals corresponding to each preset diagnostic event are taken as a candidate signal group.

[0060] Assume that two preset diagnostic events, abnormal engine noise (Event2) and brake failure (Event4), are triggered at the same time at the first moment. Freeze the data streams of multiple related signals (signals BA, BB, BC, BD) in the candidate signal group (Group-2) corresponding to Event2 to obtain a frozen signal data packet corresponding to Event2; at the same time, freeze the data streams of multiple related signals (signals DA, DB, DC, DD) in the candidate signal group (Group-4) corresponding to Event4 to obtain a frozen signal data packet corresponding to Event4.

[0061] In step 320, if at least one preset diagnostic event is triggered within a target time period, the triggering time of each triggered preset diagnostic event and the candidate signal group corresponding to each triggered preset diagnostic event are determined. The detailed arrangement process of the candidate signal group has been completed in step 310, and step 320 is to select at least one candidate signal group that needs to be monitored within the target time period from the multiple candidate signal groups that have been determined.

[0062] In step 330, for each preset diagnostic event that is triggered, it is necessary to acquire the signal data stream within the target time period. When the number of preset diagnostic events that are triggered is two or more, if the triggering time of each of the preset diagnostic events that are triggered is the same, then the target time period for collecting the signal data stream is also the same. For example, assuming that the triggering time of preset diagnostic event 1 is 15:00:00, and the triggering time of preset diagnostic event 2 is also 15:00:00, the target time periods corresponding to preset diagnostic event 1 and preset diagnostic event 2 are both 14:55:00 to 15:05:00, that is, the target time periods are the same.

[0063] If the triggering time of each triggered preset diagnostic event is different, then the target time period for collecting the signal data stream is also different. For example, assuming that the triggering time of preset diagnostic event 3 is 15:00:00, and the triggering time of preset diagnostic event 4 is also 15:00:02, the target time period corresponding to preset diagnostic event 3 is 14:55:00 to 15:05:00, and the target time period corresponding to preset diagnostic event 4 is 14:55:02 to 15:05:02, that is, the target time periods are different.

[0064] In step 340, the signal data stream of the candidate signal group corresponding to each triggered preset diagnostic event is frozen within the target time period to obtain a frozen signal data packet of each triggered preset diagnostic event, thereby saving signal data reflecting the vehicle status before and after the preset diagnostic event occurs.

[0065] The advantage of steps 310-340 is that, for each triggered preset diagnostic event, different target time periods are determined, and the signals that may need to be frozen are divided into candidate signal groups in advance, and then the corresponding candidate signal groups are frozen for the triggered preset diagnostic events, thereby reducing the time consumed in searching for the associated signals of each preset diagnostic event, reducing the time consumed from the triggering of the preset diagnostic event to the completion of signal freezing, and improving the accuracy of the acquired frozen signal data packets.

[0066] The above steps 310-340 provide a method for obtaining a freeze signal data packet. There are multiple ways to determine the target time period in step 330. In one embodiment, step 330 may include:

[0067] For each triggering moment of at least one triggering moment, determining a first preset time length before the triggering moment as a first time length range;

[0068] The triggering moment and the first duration range are determined as a target time period corresponding to each triggering moment.

[0069] In this embodiment, the target time period may be limited to the triggering moment of the preset diagnostic event and the signal data of a period of time before the triggering moment, so as to provide more data for remote fault diagnosis.

[0070] In another embodiment, step 330 may include:

[0071] For each triggering moment of at least one triggering moment, determining a first preset time length before the triggering moment as a first time length range;

[0072] Determine a second preset time after the triggering moment as a second time range;

[0073] The triggering moment, the first duration range, and the second duration range are determined as a target time period corresponding to each triggering moment.

[0074] This embodiment provides a method for determining a target time period, which includes, in addition to a first time range before the trigger moment, a second time range after the trigger moment, and performs remote fault diagnosis through data before and after the trigger moment, thereby improving the accuracy of remote fault diagnosis.

[0075] It should be noted that the target time period must include the triggering moment. Generally, the triggering moment is in the middle of the target time period, that is, the duration before and after the triggering moment is the same. The proportion of the duration before and after the triggering moment can also be adjusted according to the actual situation, and the specifics are not limited here. For example, the duration before the triggering moment can be greater than the duration after the triggering moment, so as to obtain more data before the triggering moment of the preset diagnostic event.

[0076] See also Figure 4 In one embodiment, step 310 may include:

[0077] 410. Determine multiple preset diagnostic events that need to be reported based on a preset signal arrangement table;

[0078] 420. Associate the multiple signals with each preset diagnostic event that needs to be reported, respectively, to obtain multiple candidate signal groups, where the candidate signal groups include multiple trigger source signals and multiple driving condition signals associated with the preset diagnostic events.

[0079] Steps 410 - 420 are described in detail below.

[0080] In step 410, for different types of vehicles, the preset diagnostic events collected from the vehicle will be different, and the preset diagnostic events that need to be reported will also be different. For example, for fuel vehicles and electric vehicles, the preset diagnostic events that can be collected from the fuel vehicle are not exactly the same as the preset diagnostic events that can be collected from the electric vehicle. For example, the preset diagnostic events that can be collected from the fuel vehicle include preset diagnostic events related to the engine: abnormal engine noise, sudden engine shutdown, etc.; preset diagnostic events related to the gearbox: gearbox overheating, gearbox abnormal noise, etc.; preset diagnostic events related to the chassis: abnormal tire pressure, brake pad overheating, brake failure, etc. The preset diagnostic events that can be collected from the electric vehicle include preset diagnostic events related to the motor: abnormal motor noise, abnormal motor speed, etc.; preset diagnostic events related to the battery: battery overheating, abnormal battery voltage, abnormal battery current, etc.; preset diagnostic events related to the chassis: abnormal tire pressure, brake pad overheating, brake failure, etc. Referring to Table 1, it can be seen that the preset diagnostic events that can be collected from different types of vehicles are not exactly the same, so different signal arrangement tables can be set for different types of vehicles.

[0081] It is understandable that the signal arrangement table may include a local signal arrangement table and a global signal arrangement table. For vehicles of the same model, the corresponding vehicle configurations are different, and the signals that can be collected may also be different. A corresponding local signal arrangement table may be configured for each vehicle. The global signal arrangement table containing the largest number of signals may also be configured for vehicles of different models, thereby improving the configuration efficiency of the signal arrangement table.

[0082] It should be noted that the signal arrangement table is a database that records all preset diagnostic events, which at least includes the preset diagnostic event name, preset diagnostic event ID, candidate signal group ID, and associated signal ID. The preset diagnostic event ID is represented by EventX, where X is a different digital number; the candidate signal group ID is represented by Group-X, where X is a different digital number; the associated signal ID is represented by hexadecimal, and the number of associated signals corresponding to each preset diagnostic event (EventX) is not exactly the same, which is not limited in this disclosure. For example, Event1-Event4 all include 4 associated signals, and Event5-Event6 all include 5 associated signals.

[0083] In step 420, for each preset diagnostic event that needs to be reported, multiple signals are screened, and associated signals related to the preset diagnostic event that needs to be reported are selected, and the associated signals include multiple trigger source signals and multiple driving condition signals, wherein the trigger source signal is a signal that will cause the preset diagnostic event, and the driving condition signal is a signal that reflects the vehicle state during the vehicle driving process. By analyzing multiple trigger source signals, technicians can determine the cause of the preset diagnostic event. By analyzing multiple driving condition signals, technicians can restore the vehicle control scene when the preset diagnostic event occurs. For example, the trigger source signals corresponding to the injector failure event are: injector feedback signal, injection command signal, accelerator pedal signal. When the injection command signal indicates injection, the accelerator pedal signal indicates increasing the throttle, and the injector feedback signal is abnormal and indicates no injection, the injector failure can be determined. For example, the driving condition signals corresponding to the injector failure event include: left turn signal, vehicle speed signal, and gear signal. When the left turn signal indicates that the left turn signal is on, the vehicle speed signal indicates acceleration, and the gear signal indicates switching from low gear to high gear, it can be determined that the vehicle is in a left acceleration lane change scenario. Assume that the trigger mechanism signals corresponding to the brake failure event include: brake signal DA, engine speed signal DB, accelerator pedal signal DC, and brake oil pressure signal DD. When the brake signal DA indicates braking, the engine speed signal DB indicates no change in speed, the accelerator pedal signal DC indicates no accelerator, and the brake oil pressure signal DD indicates that the pressure is too low, it can be determined that the brake failure has occurred.

[0084] The advantage of steps 410-420 is that the signals involved in the preset diagnostic events that may need to be reported are grouped in advance, which narrows the signal search range when the preset diagnostic events are triggered and reduces the time consumed in searching for related signals when the preset diagnostic events are triggered.

[0085] See also Figure 5 In one embodiment, step 340 may include:

[0086] 510. For each candidate signal group corresponding to each triggered preset diagnostic event, determine the data stream of each associated signal in the corresponding target time period to obtain multiple associated signal data streams of each triggered preset diagnostic event;

[0087] 520. Synchronously compress multiple associated signal data streams of each triggered preset diagnostic event to obtain compressed packets of multiple associated signal data streams of each triggered preset diagnostic event;

[0088] 530. Combining multiple associated signal data stream compression packets of each triggered preset diagnostic event into a single frozen signal data packet to obtain at least one frozen signal data packet.

[0089] In step 510, each triggered preset diagnostic event corresponds to a candidate signal group, and each candidate signal group needs to obtain the data stream of each signal in the candidate signal group based on the corresponding target time period. For example, as shown in Table 1, for Event4, assuming that the target time range is 10 seconds, the candidate signal group Group-4 includes 4 related signals, namely the brake signal DA, the engine speed signal DB, the accelerator pedal signal DC, and the brake oil pressure signal DD. It is necessary to obtain the signal data streams of multiple related signals DA, DB, DC, and DD of Event4 within 5 seconds before and after the triggering moment.

[0090] In step 520, different candidate signal groups need to be frozen synchronously to ensure that the frozen data is accurate. For multiple associated signals in a candidate signal group, it is necessary to compress the signal data stream of a single associated signal to obtain corresponding multiple associated signal data compression packages to avoid interference between the data streams of multiple associated signals and to avoid increasing the difficulty of parsing the data stream.

[0091] In step 530, different associated signal data compression packages are merged to obtain frozen signal data packages of corresponding candidate signal groups, and different candidate signal groups correspond to different frozen signal data packages. Among them, for multiple candidate signal groups, if the corresponding preset diagnostic events occur at the same time, then when freezing the signal, it is necessary to freeze it synchronously.

[0092] The advantage of steps 510-530 is that when multiple preset diagnostic events are triggered simultaneously, multiple candidate signal groups can be frozen simultaneously, realizing a multi-fault parallel freezing mechanism, improving freezing efficiency, and avoiding inaccurate frozen signal data streams due to freezing delays.

[0093] See also Figure 6 In one embodiment, step 230 may include:

[0094] 610. In response to at least one triggered preset diagnostic event, determine a triggering time corresponding to each of the triggered preset diagnostic events and a plurality of corresponding associated signals;

[0095] 620. Determine a target time period corresponding to each of the triggered preset diagnostic events based on each of the triggering moments, wherein the target time period includes the corresponding triggering moment;

[0096] 630. Freeze the multiple associated signals corresponding to each of the triggered preset diagnostic events according to the corresponding target time period to obtain at least one frozen signal data packet.

[0097] Steps 610-630 are described in detail below.

[0098] In step 610, if at least one preset diagnostic event is triggered, the triggering time of each triggered preset diagnostic event and multiple associated signals of each triggered preset diagnostic event are determined. The corresponding relationship between the associated signals and the preset diagnostic events is recorded in the signal arrangement table, which will not be repeated here.

[0099] In step 620, the process of step 620 is the same as step 330, and will not be repeated here.

[0100] In step 630, after determining the multiple associated signals corresponding to each triggered preset diagnostic event, the signal data stream of each associated signal within the target time period is frozen to obtain a frozen signal data packet of each triggered preset diagnostic event, thereby saving signal data reflecting the vehicle status before and after the preset diagnostic event occurs.

[0101] The advantage of steps 610-630 is that only after the preset diagnostic event is triggered will the corresponding associated signal be determined from the stored historical data, and the data of each associated signal within the target time period will be searched. There is no need to arrange the associated signals of each preset diagnostic event in advance, thereby reducing the computing resources consumed by signal arrangement.

[0102] The above steps 210-230 describe the process of determining the freeze signal data packet and sending it to the cloud. In one embodiment, refer to Figure 7 , between step 220 and step 230, the following may also be included:

[0103] 221. Obtain the event priority corresponding to each triggered preset diagnostic event;

[0104] 222. Sort at least one triggered preset diagnostic event according to the event priority to obtain an event sending order;

[0105] Step 230 may include:

[0106] 231. Send at least one freeze signal data packet and a corresponding preset diagnostic event to the cloud according to the event sending order.

[0107] In step 221, if only one preset diagnostic event is triggered, the preset diagnostic event can be sent directly. If two or more preset diagnostic events are triggered, because the vehicle's CAN channel sending capacity is limited, the triggered preset diagnostic events need to be sorted to obtain the event priority of each triggered preset diagnostic event.

[0108] In step 222, each triggered preset diagnostic event is sorted according to the event priority corresponding to each triggered preset diagnostic event. For example, preset diagnostic events with higher event priorities can be sent first, and preset diagnostic events with lower event priorities can be sent later. For example, if the preset diagnostic event involves vehicle driving safety, the corresponding event priority is high, and the preset diagnostic event involving the use failure of the vehicle entertainment device has a low event priority. The event sending order of each triggered preset diagnostic event is determined, that is, the sending order of each frozen data packet is determined.

[0109] The advantage of steps 221-222 is that when a large number of preset diagnostic events are triggered, a solution is provided to determine the order of event sending according to the event priority, ensuring that more important preset diagnostic events can be sent first, thereby improving the timeliness of important data sending.

[0110] In another embodiment, see Figure 8 , between step 220 and step 230, the following may also be included:

[0111] 223. Obtain the size of a freeze signal data packet corresponding to each triggered preset diagnostic event;

[0112] 224. Sort at least one triggered preset diagnostic event according to the size of the freeze signal data packet to obtain an event sending order;

[0113] Step 230 may include:

[0114] 231. Send at least one freeze signal data packet and a corresponding preset diagnostic event to the cloud according to the event sending order.

[0115] In step 223, if there is only one preset diagnostic event triggered, then no sorting is required. If there are two or more preset diagnostic events triggered, because the number of CAN channels is limited and the sending capacity is limited, the triggered preset diagnostic events need to be sorted, and the frozen signal data packet size of each triggered preset diagnostic event is obtained. The frozen signal data packet size can reflect the number of frozen signals, that is, the coverage signal range is wider.

[0116] In step 224, each triggered preset diagnostic event is sorted according to the data packet size corresponding to each triggered preset diagnostic event. Preset diagnostic events with larger freeze signal data packets can be sent first, and preset diagnostic events with smaller freeze signal data packets can be sent later. For example, if the preset diagnostic event involved is battery voltage abnormality, the corresponding freeze signal data packet size is 5M, and if the preset diagnostic event involved is vehicle horn abnormality, the corresponding freeze signal data packet size is 1M. The determined event sending order is: battery voltage abnormality is sent first, and vehicle horn abnormality is sent later.

[0117] The advantage of steps 223-224 is that when a large number of preset diagnostic events are triggered, a scheme is provided to determine the order of event sending according to the size of the freeze signal data packet. The preset diagnostic events with a larger freeze signal data packet size are sent first, and then the preset diagnostic events with a smaller freeze signal data packet size are sent. The preset diagnostic events covering a wider signal range are sent first, thereby improving the utilization rate of the byte segments in the data frame.

[0118] It is understandable that preset diagnostic events with smaller freeze signal data packets may be sent first, and preset diagnostic events with larger freeze signal data packets may be sent later, which is not limited here.

[0119] In another embodiment, see Fig. 9 , between step 220 and step 230, the following may also be included:

[0120] 225. Obtain the event priority corresponding to each triggered preset diagnostic event;

[0121] 226. Obtain the size of a freeze signal data packet corresponding to each triggered preset diagnostic event;

[0122] 227. Sort at least one triggered preset diagnostic event according to the event priority and the freeze signal data packet size to obtain an event sending order;

[0123] Step 230 may include:

[0124] 231. Send at least one freeze signal data packet and a corresponding preset diagnostic event to the cloud according to the event sending order.

[0125] The above steps 225-227 are described in detail below.

[0126] Step 225 is similar to step 221 and will not be described in detail.

[0127] Step 226 is similar to step 223 and will not be described in detail.

[0128] In one embodiment, Fig.10 As shown, step 227 specifically includes:

[0129] 1010. Determine a ranking score of each triggered preset diagnostic event according to the freeze signal data packet size and the event priority;

[0130] 1020. Obtain an event sending order corresponding to at least one triggered preset diagnostic event based on the ranking score of each triggered preset diagnostic event.

[0131] In one embodiment, step 1010 may include:

[0132] determining a first score based on the event priority;

[0133] determining a second score based on the freeze signal packet size;

[0134] A ranking score of each triggered preset diagnostic event is calculated based on the first score and the second score.

[0135] The first score represents the importance of the triggered preset diagnostic event from the perspective of the event priority. If the event priority is high, the triggered preset diagnostic event needs to be sent first. If the event priority is low, the triggered preset diagnostic event can be sent later. The first score can be determined by a table lookup method. Table 2 shows the corresponding relationship between the priority and the first score.

[0136] Event Priority First Score Priority 1 100 Priority 2 90 Priority 3 80 Priority 4 70 …… ……

[0137] Table 2

[0138] The second score represents the importance of the preset diagnostic event triggered from the size of the freezing signal data packet. If the freezing signal data packet is large, the triggered preset diagnostic event needs to be sent first, and if the freezing signal data packet is small, the triggered preset diagnostic event can be sent later. The second score can be determined by a table lookup method or a formula method. Table 3 shows a corresponding relationship table between the freezing signal data packet size and the second score.

[0139] Freeze signal packet size range Second score 1-20 bytes 10 21-40 bytes 20 41-60 bytes 30 61-80 bytes 40 81-100 bytes 50 …… ……

[0140] Table 3

[0141] When the formula method is used, the size size of the frozen signal data packet may be multiplied by the first coefficient a to obtain the second score score, score=size*a.

[0142] For the first score and the second score, the ranking score can be determined by direct summation or weighted summation. For example, when weighted summation is adopted, different weights are set for the first score and the second score, and the weights reflect the different influences of the size of the freeze signal data packet and the event priority on the event sending order, so that the event sending order setting has high flexibility, and the sending order of each triggered preset diagnostic event can be adjusted according to the actual situation, thereby improving the universality of different preset diagnostic events.

[0143] Based on the event sending order determined in the above embodiment, Fig.11 As shown, step 231 may include:

[0144] 1110. Determine a first corresponding relationship according to a preset signal arrangement table, where the first corresponding relationship is used to indicate a corresponding relationship between each signal in at least one frozen signal data packet and a plurality of preset CAN channels;

[0145] 1120. Based on the first corresponding relationship, the event sending order and each signal in at least one freeze signal data packet, generate a data frame sequence corresponding to each CAN channel, and send the data frame sequence corresponding to each CAN channel to the cloud through multiple CAN channels.

[0146] In step 1110, the first corresponding relationship is determined by querying the signal arrangement table, that is, the corresponding relationship between each signal in the frozen signal data packet of the preset diagnostic event triggered and any CAN channel is determined. For example, as shown in Table 4, the first byte of the data field in the data frame sent by a CAN channel is used to store the preset diagnostic event ID, the second byte is used to store the signal group number, and the third byte to the eighth byte are used to store the specific content of each signal. Table 4 shows the content stored in each byte in the data field in the data frame.

[0147] EventX Group-X signal-xx signal-xx signal-xx signal-xx signal-xx signal-xx

[0148] Table 4

[0149] In step 1120, according to the first corresponding relationship, the event sending order can allocate each signal to the data frame of each CAN channel in turn, and obtain the data frame sequence corresponding to each CAN channel; and send the corresponding data frame sequence to the cloud through each CAN channel.

[0150] The advantage of steps 1110-1120 is that freeze signal data packets of different preset diagnostic events are sent in time-sharing, and multiple signals of the same preset diagnostic event are grouped according to the number of CAN channels, thereby improving the signal sending capacity of the CAN channel and improving the richness of data received by the cloud.

[0151] Description of the apparatus and device of the present disclosure

[0152] It is to be understood that, although the steps in the above-mentioned flowcharts are sequentially displayed according to the characterization of arrows, these steps are not necessarily executed in sequence according to the order of arrow characterization. Unless there is a clear description in the present embodiment, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the above-mentioned flowcharts can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the steps or stages in other steps.

[0153] It should be noted that in each specific embodiment of the present disclosure, when it comes to relevant processing of signal data related to the characteristics of the target object, the permission or consent of the target object will be obtained first, and the collection, use and processing of these data will comply with relevant laws, regulations and standards. In addition, when the embodiment of the present application needs to obtain original vehicle fault data, the separate permission or separate consent of the target object will be obtained through a pop-up window or jump to a confirmation page. After clearly obtaining the separate permission or separate consent of the target object, the necessary original vehicle fault data for the normal operation of the embodiment of the present application is obtained.

[0154] Reference Fig.12 , Fig.12 The structure diagram of the vehicle fault data sending device 1200 provided in the embodiment of the present disclosure includes:

[0155] A first acquisition module 1210 is used to acquire original vehicle fault data, where the original vehicle fault data includes multiple signals;

[0156] A freezing module 1220, configured to freeze, in response to at least one triggered preset diagnostic event, a signal associated with each triggered preset diagnostic event among a plurality of signals to obtain at least one frozen signal data packet;

[0157] The sending module 1230 is used to send at least one freeze signal data packet and a corresponding preset diagnostic event to the cloud, and the at least one freeze signal data packet and the corresponding preset diagnostic event are used for remote fault diagnosis.

[0158] In one embodiment, the freezing module 1220 is specifically used to:

[0159] Arranging the multiple signals to obtain multiple candidate signal groups, each candidate signal group corresponding to a preset diagnostic event;

[0160] In response to at least one triggered preset diagnostic event, determining a triggering time and a corresponding candidate signal group corresponding to each triggered preset diagnostic event;

[0161] Determine, based on each triggering moment, a target time period corresponding to each triggered preset diagnostic event, the target time period including the corresponding triggering moment;

[0162] The candidate signal group corresponding to each triggered preset diagnostic event is frozen according to the corresponding target time period to obtain at least one frozen signal data packet.

[0163] In one embodiment, the freezing module 1220 is specifically used to:

[0164] Determine a plurality of preset diagnostic events that need to be reported based on a preset signal arrangement table;

[0165] The multiple signals are respectively associated with each preset diagnostic event that needs to be reported to obtain multiple candidate signal groups, where the candidate signal groups include multiple trigger source signals and multiple driving condition signals associated with the preset diagnostic events.

[0166] In one embodiment, the freezing module 1220 is specifically used to:

[0167] For each candidate signal group corresponding to each triggered preset diagnostic event, determine the data stream of each associated signal in the corresponding target time period to obtain multiple associated signal data streams of each triggered preset diagnostic event;

[0168] Synchronously compressing multiple associated signal data streams of each triggered preset diagnostic event to obtain multiple associated signal data stream compression packages of each triggered preset diagnostic event;

[0169] Combining multiple associated signal data stream compression packets of each triggered preset diagnostic event into a single frozen signal data packet to obtain at least one frozen signal data packet.

[0170] In one embodiment, the freezing module 1220 is specifically used to:

[0171] In response to at least one triggered preset diagnostic event, determining a triggering time corresponding to each triggered preset diagnostic event and a plurality of corresponding associated signals;

[0172] Determine, based on each triggering moment, a target time period corresponding to each triggered preset diagnostic event, the target time period including the corresponding triggering moment;

[0173] A plurality of associated signals corresponding to each triggered preset diagnostic event are frozen according to a corresponding target time period to obtain at least one frozen signal data packet.

[0174] In one embodiment, the vehicle fault data sending device further includes:

[0175] A second acquisition module, used to acquire the freeze signal data packet size and event priority corresponding to each triggered preset diagnostic event;

[0176] The sorting module is used to sort at least one triggered preset diagnostic event according to the freeze signal data packet size and the event priority to obtain the event sending order.

[0177] The sending module 1230 is specifically used for:

[0178] According to the event sending sequence, at least one freeze signal data packet and a corresponding preset diagnostic event are sent to the cloud.

[0179] In one embodiment, the sending module 1230 is specifically used for:

[0180] Determine a ranking score of each triggered preset diagnostic event according to the freeze signal data packet size and the event priority;

[0181] Based on the ranking score of each triggered preset diagnostic event, an event sending order corresponding to at least one triggered preset diagnostic event is obtained.

[0182] In one embodiment, the sending module 1230 is specifically used for:

[0183] Determine a first corresponding relationship according to a preset signal arrangement table, where the first corresponding relationship is used to indicate a corresponding relationship between each signal in at least one frozen signal data packet and a plurality of preset CAN channels;

[0184] Based on the first corresponding relationship, the event sending order and each signal in at least one frozen signal data packet, a sending message sequence corresponding to each CAN channel is generated, and the sending message sequence corresponding to each CAN channel is sent to the cloud through multiple CAN channels.

[0185] See also Fig.13 The present disclosure also provides a hardware structure of an electronic device, the electronic device comprising:

[0186] The processor 1301 may be implemented by a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present disclosure;

[0187] The memory 1302 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1302 can store an operating system and other application programs. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 1302, and the processor 1301 calls and executes the vehicle fault data sending method of the embodiment of the present disclosure;

[0188] Input / output interface 1303, used to implement information input and output;

[0189] The communication interface 1304 is used to realize the communication interaction between the device and other devices. The communication can be realized through a wired manner (such as USB, network cable, etc.) or a wireless manner (such as mobile network, WIFI, Bluetooth, etc.);

[0190] A bus 1305 that transmits information between the various components of the device (e.g., the processor 1301, the memory 1302, the input / output interface 1303, and the communication interface 1304);

[0191] The processor 1301 , the memory 1302 , the input / output interface 1303 and the communication interface 1304 are connected to each other in communication within the device via a bus 1305 .

[0192] The embodiment of the present disclosure also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned vehicle fault data sending method is implemented.

[0193] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0194] The disclosed embodiment also provides an electronic device, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the above-mentioned vehicle fault data sending method when executing the computer program. The electronic device can be any intelligent terminal including a tablet computer, a vehicle-mounted computer, etc.

[0195] In combination with the electronic device in the above embodiment, an embodiment of the present application further provides a vehicle, which includes the electronic device in the above embodiment.

[0196] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0197] In the description of the present disclosure, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., indicating the orientation or positional relationship, are based on the orientation or positional relationship shown in the drawings, and are only for the convenience of describing the present disclosure and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation of the present disclosure. In addition, the terms "first", "second", and "third" are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance.

[0198] Finally, it should be noted that the above embodiments are only specific implementation methods of the present disclosure, which are used to illustrate the technical solutions of the present disclosure, rather than to limit them. The protection scope of the present disclosure is not limited thereto. Although the present disclosure is described in detail with reference to the above embodiments, those skilled in the art should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above embodiments within the technical scope disclosed in the present disclosure, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure, and should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. A method for sending vehicle fault data, characterized in that: The method comprises: Acquire original vehicle fault data, where the original vehicle fault data includes multiple signals; In response to at least one triggered preset diagnostic event, freezing a signal associated with each of the triggered preset diagnostic events among the plurality of signals to obtain at least one frozen signal data packet; The at least one freeze signal data packet and the corresponding preset diagnostic event are sent to the cloud, and the at least one freeze signal data packet and the corresponding preset diagnostic event are used for remote fault diagnosis.

2. The vehicle fault data sending method according to claim 1, characterized in that: In response to at least one triggered preset diagnostic event, freezing a signal associated with each of the triggered preset diagnostic events among the multiple signals to obtain at least one frozen signal data packet includes: Arranging the multiple signals to obtain multiple candidate signal groups, each of the candidate signal groups corresponding to a preset diagnostic event; In response to at least one triggered preset diagnostic event, determining a triggering time and a corresponding candidate signal group corresponding to each of the triggered preset diagnostic events; Determine, based on each triggering moment, a target time period corresponding to each of the triggered preset diagnostic events, wherein the target time period includes the corresponding triggering moment; The candidate signal group corresponding to each of the triggered preset diagnostic events is frozen according to the corresponding target time period to obtain at least one frozen signal data packet.

3. The vehicle fault data sending method according to claim 2, characterized in that: The step of freezing the candidate signal groups corresponding to each of the triggered preset diagnostic events according to the corresponding target time period to obtain at least one frozen signal data packet includes: For each candidate signal group corresponding to the triggered preset diagnostic event, determine the data stream of each associated signal in the corresponding target time period to obtain multiple associated signal data streams of each triggered preset diagnostic event; Synchronously compressing the multiple associated signal data streams of each of the triggered preset diagnostic events to obtain compressed packets of the multiple associated signal data streams of each of the triggered preset diagnostic events; The plurality of associated signal data stream compression packets of each of the triggered preset diagnostic events are combined into a single frozen signal data packet to obtain at least one frozen signal data packet.

4. The vehicle fault data sending method according to claim 1, characterized in that: In response to at least one triggered preset diagnostic event, freezing a signal associated with each of the triggered preset diagnostic events among the multiple signals to obtain at least one frozen signal data packet includes: In response to at least one triggered preset diagnostic event, determining a triggering time corresponding to each of the triggered preset diagnostic events and a plurality of corresponding associated signals; Determine, based on each triggering moment, a target time period corresponding to each of the triggered preset diagnostic events, wherein the target time period includes the corresponding triggering moment; The plurality of associated signals corresponding to each of the triggered preset diagnostic events are frozen according to the corresponding target time period to obtain at least one frozen signal data packet.

5. The vehicle fault data sending method according to claim 1, characterized in that: After freezing the signal associated with each of the triggered preset diagnostic events in the plurality of signals in response to at least one triggered preset diagnostic event to obtain at least one frozen signal data packet, and before sending the at least one frozen signal data packet and the corresponding preset diagnostic event to the cloud, the method further includes: Obtain the event priority corresponding to each triggered preset diagnostic event; Obtaining the freeze signal data packet size corresponding to each triggered preset diagnostic event; Sorting the at least one triggered preset diagnostic event according to the event priority and the freeze signal data packet size to obtain an event sending order; The sending of the at least one freeze signal data packet and the corresponding preset diagnostic event to the cloud comprises: According to the event sending sequence, the at least one freeze signal data packet and the corresponding preset diagnostic event are sent to the cloud.

6. The vehicle fault data transmission method according to claim 5, characterized in that: The step of sorting the at least one triggered preset diagnostic event according to the event priority and the freeze signal data packet size to obtain an event sending sequence includes: Determining a ranking score of each triggered preset diagnostic event according to the freeze signal data packet size and the event priority; Based on the ranking score of each triggered preset diagnostic event, an event sending order corresponding to the at least one triggered preset diagnostic event is obtained.

7. The vehicle fault data transmission method according to claim 5, characterized in that: The step of sending the at least one freeze signal data packet and the corresponding preset diagnostic event to the cloud according to the event sending sequence includes: Determining a first corresponding relationship according to a preset signal arrangement table, wherein the first corresponding relationship is used to indicate a corresponding relationship between each signal in the at least one freeze signal data packet and a plurality of preset CAN channels; Based on the first corresponding relationship, the event sending order and each signal in the at least one freeze signal data packet, a data frame sequence corresponding to each CAN channel is generated, and the data frame sequence corresponding to each CAN channel is sent to the cloud through multiple CAN channels.

8. A vehicle fault data sending device, characterized in that: The vehicle fault data sending device comprises: A first acquisition module, used to acquire original vehicle fault data, wherein the original vehicle fault data includes a plurality of signals; A freezing module, configured to freeze, in response to at least one triggered preset diagnostic event, a signal associated with each of the triggered preset diagnostic events among the plurality of signals to obtain at least one frozen signal data packet; The sending module is used to send the at least one freeze signal data packet and the corresponding preset diagnostic event to the cloud, and the at least one freeze signal data packet and the corresponding preset diagnostic event are used for remote fault diagnosis.

9. An electronic device, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program, and the processor implements the vehicle fault data sending method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the vehicle fault data sending method according to any one of claims 1 to 7 is implemented.

11. A vehicle, characterized in that: Comprising the electronic device as claimed in claim 9.

Images