Vehicle-mounted ECU data monitoring method and device, electronic equipment and medium

Abstract

The invention provides a vehicle-mounted ECU data monitoring method and device, electronic equipment and a medium. The method comprises the steps of configuring a reporting rule of vehicle-mounted ECU data in advance according to a service type, sending the reporting rule to a vehicle end, receiving the ECU data reported by the vehicle end according to the reporting rule, analyzing the ECU data according to an analysis rule to generate ECU index data, and analyzing the ECU index data to obtain a data monitoring result. According to the technical scheme provided by the invention, the cloud can effectively monitor various vehicle-mounted ECU data based on the service type, the monitoring efficiency and the monitoring capability are improved, and a reliable solution is provided for the vehicle cloud to cooperatively monitor the ECU data.

Description

Technical Field

[0001] The present application relates to the field of vehicle networking technology, and in particular to a vehicle-mounted ECU data monitoring method, device, electronic device and medium. Background Art

[0002] At present, the intelligentization of automobiles is developing rapidly, and the application of ECU (Electronic Control Unit) in the car is also increasing. ECU is usually composed of microprocessor, memory, input and output interface, analog-to-digital converter, and large-scale integrated circuits such as shaping and driving. ECU is actually a microcomputer. On the one hand, it receives signals from sensors, and on the other hand, it completes the processing of these signals and issues corresponding control instructions to control the correct action of the actuator. Various ECU data generated by the vehicle can be reported to the cloud for vehicle-cloud collaborative processing. With the increase of ECU data, it becomes more and more important for the cloud to effectively monitor various ECU data. Summary of the invention

[0003] The embodiment of the present application provides a vehicle-mounted ECU data monitoring method, device, electronic device and medium to improve the monitoring capability of ECU data. The technical solution is as follows:

[0004] In a first aspect, an embodiment of the present application provides a vehicle-mounted ECU data monitoring method, comprising:

[0005] Pre-configure the reporting rules of vehicle ECU data according to the business type;

[0006] Sending the reporting rules to the vehicle end;

[0007] Receiving ECU data reported by the vehicle end according to the reporting rules;

[0008] Parsing the ECU data according to the parsing rules to generate ECU indicator data;

[0009] The ECU indicator data is analyzed to obtain data monitoring results.

[0010] In a second aspect, an embodiment of the present application provides a vehicle-mounted ECU data monitoring device, comprising:

[0011] Configuration module, used to configure the reporting rules of vehicle ECU data in advance according to the business type;

[0012] A sending module, used for sending the reporting rule to the vehicle end;

[0013] A receiving module, used for receiving ECU data reported by the vehicle end according to the reporting rule;

[0014] A parsing module, used for parsing the ECU data according to parsing rules to generate ECU indicator data;

[0015] The monitoring module is used to analyze the ECU indicator data to obtain data monitoring results.

[0016] In a third aspect, an embodiment of the present application provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor so that the at least one processor can execute the above method.

[0017] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a computer, the method in any one of the above-mentioned embodiments is executed.

[0018] The advantages or beneficial effects of the above technical solution include at least:

[0019] By pre-configuring the reporting rules for vehicle-mounted ECU data according to the business type, sending the reporting rules to the vehicle side, receiving the ECU data reported by the vehicle side according to the reporting rules, parsing the ECU data according to the parsing rules to generate ECU indicator data, and analyzing the ECU indicator data to obtain data monitoring results, the cloud can effectively monitor various vehicle-mounted ECU data based on business types, improve monitoring efficiency and monitoring capabilities, and provide a reliable solution for vehicle-cloud collaborative monitoring of ECU data.

[0020] The above summary is for illustrative purposes only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments and features described above, further aspects, embodiments and features of the present application will be readily apparent by reference to the accompanying drawings and the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the multiple drawings represent the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings only depict some embodiments disclosed in the present application and should not be regarded as limiting the scope of the present application.

[0022] Figure 1 This is a flow chart of a vehicle ECU data monitoring method according to an embodiment of the present application;

[0023] Figure 2 This is a flow chart of a vehicle ECU data monitoring method according to another embodiment of the present application;

[0024] Figure 3A schematic diagram of the process of issuing rules and reporting data according to another embodiment of the present application;

[0025] Figure 4 A schematic diagram of cloud monitoring according to another embodiment of the present application;

[0026] Figure 5 A schematic diagram of a vehicle-cloud collaboration scenario according to another embodiment of the present application;

[0027] Figure 6 This is a structural diagram of a vehicle-mounted ECU data monitoring device according to another embodiment of the present application;

[0028] Figure 7 It is a block diagram of an electronic device used to implement the vehicle-mounted ECU data monitoring method of an embodiment of the present application. DETAILED DESCRIPTION

[0029] In the following, only some exemplary embodiments are briefly described. As those skilled in the art will appreciate, the described embodiments may be modified in various ways without departing from the spirit or scope of the present application. Therefore, the drawings and descriptions are considered to be exemplary and non-restrictive in nature.

[0030] The embodiments of the present application provide a method and device for monitoring vehicle-mounted ECU data to improve the monitoring capability of ECU data. The technical solution can be applied to the monitoring and processing of vehicle-mounted ECU data in the cloud, effectively monitor various ECU data based on business types, improve monitoring efficiency, and can be applicable to big data scenarios. The above method and device can be applied to electronic devices, including but not limited to: computers, laptops, servers or mobile terminals. Exemplarily, the electronic device can be a cloud server that performs vehicle-cloud collaborative communication with the vehicle-mounted terminal, and the server can be one or more, which is not specifically limited in the embodiments of the present application.

[0031] Figure 1 FIG. 1 is a flow chart of a vehicle ECU data monitoring method according to an embodiment of the present application. Figure 1 As shown, the method may include:

[0032] S101: Pre-configure the reporting rules of the vehicle ECU data according to the service type.

[0033] In one implementation, the above step S101 may include: pre-dividing the service into multiple service types according to service characteristics, generating corresponding ECU reporting parameter information for each service type, saving the correspondence between the service type and the ECU reporting parameter information, and obtaining the reporting rules for the vehicle-mounted ECU data.

[0034] The business type in the embodiments of the present application may include at least one of the following: system type, application type, data embedding type or diagnostic data type.

[0035] In an embodiment of the present application, the ECU reporting parameter information may include at least one of the following: ECU name, reporting frequency, reporting data packet size, reporting data type, reporting level, reporting trigger or data collection frequency.

[0036] In the embodiments of the present application, the reporting rules of the vehicle-mounted ECU data can also be updated in a variety of ways, including automatic updates and / or manual updates. Among them, automatic updates refer to updates that can be made according to specified rules, including but not limited to: regular automatic updates or automatic updates when the ECU is upgraded. For example, the reporting rules are updated once a month, or when new ECU reporting parameters are added during the ECU upgrade, they are updated to the reporting rules. Manual updates refer to operations such as adding, deleting or modifying the business type and / or ECU reporting parameter information according to the information entered by the configuration personnel. The embodiments of the present application do not specifically limit the above-mentioned update methods.

[0037] S102: Send reporting rules to the vehicle end.

[0038] S103: receiving ECU data reported by the vehicle according to the reporting rules.

[0039] Among them, the ECU data reported by the vehicle side can be ECU data generated by the current business, or can also be ECU data generated in the past, without specific limitation.

[0040] S104: Analyze the ECU data according to the analysis rules to generate ECU indicator data.

[0041] The parsing rules may be preset. For example, different parsing rules may be set according to the business type, thereby generating different ECU indicator data accordingly.

[0042] In one implementation, the above step S104 may include:

[0043] Determine the business type of ECU data and parse it according to the business type; if it is a system type, parse and obtain at least one of system abnormality, memory index and hardware index as ECU index data; if it is an application type, parse and obtain at least one of application abnormality, user operation index and operation statistical index as ECU index data; if it is a data embedding type, parse and obtain at least one of upstream link index and downstream link index as ECU index data; if it is a diagnostic data type, parse and obtain at least one of ECU operation abnormality index and ECU acquisition abnormality index as ECU index data.

[0044] S105: Analyze the ECU indicator data to obtain data monitoring results.

[0045] In this embodiment, the obtained data monitoring results can be displayed on the interface in a visual manner for monitoring personnel to view and process, which is flexible, convenient and highly practical.

[0046] In one implementation, the above step S105 may include: analyzing the ECU indicator data to obtain the current status information and business information of the vehicle, and when the vehicle is determined to be abnormal based on the status information, sending an alarm message to the vehicle, and generating data analysis statistical results based on the business information for problem troubleshooting and business monitoring.

[0047] In one implementation, the method may further include: pre-configuring a collection rule for vehicle-mounted ECU data according to a service type, and sending the collection rule to the vehicle end to instruct the vehicle end to collect ECU data according to the collection rule.

[0048] The above method provided in this embodiment configures the reporting rules of the on-board ECU data according to the business type in advance, sends the reporting rules to the vehicle side, receives the ECU data reported by the vehicle side according to the reporting rules, parses the ECU data according to the parsing rules to generate ECU indicator data, and analyzes the ECU indicator data to obtain the data monitoring results, thereby realizing the cloud-based effective monitoring of various on-board ECU data based on the business type, improving the monitoring efficiency and monitoring capabilities, and providing a reliable solution for the vehicle-cloud collaborative monitoring of ECU data.

[0049] Figure 2 FIG. 2 shows a flow chart of a vehicle ECU data monitoring method according to another embodiment of the present application. Figure 2 As shown, the method may include:

[0050] S201: Divide the service into multiple service types in advance according to the service characteristics, and generate corresponding ECU reporting parameter information for each service type.

[0051] In the embodiment of the present application, there is a one-to-one correspondence between the business type and the ECU reported parameter information. Among them, the business type may include at least one of the following: system type, application type, data embedding type or diagnostic data type. The ECU reported parameter information may include at least one of the following: ECU name, reporting frequency, reporting data packet size, reporting data type, reporting level, reporting trigger or data collection frequency. Through the configurable management of ECU reported parameter information, a strong scalability effect can be achieved.

[0052] S202: Save the correspondence between the service type and the ECU reporting parameter information, and obtain the reporting rules of the vehicle-mounted ECU data.

[0053] S203: Send reporting rules to the vehicle side, and receive ECU data reported by the vehicle side according to the reporting rules.

[0054] In this embodiment, the cloud can send the reporting rules to one or more specified vehicles, or to all vehicles in the Internet of Vehicles, without specific limitation.

[0055] S204: Determine the business type of the ECU data and parse it according to the business type.

[0056] The business type of the ECU data can be determined based on the received ECU data, and different types of ECU data can then be parsed differently.

[0057] S205: Analyze and obtain ECU indicator data corresponding to each business type.

[0058] The above step S205 may be specifically performed as follows:

[0059] If it is a system type, at least one of system abnormality, memory index and hardware index is obtained by parsing as ECU index data;

[0060] If it is an application type, at least one of application exception, user operation index and operation statistical index is obtained by parsing as ECU index data;

[0061] If it is a data embedding type, at least one of the upstream link indicator and the downstream link indicator is parsed and obtained as the ECU indicator data;

[0062] If the data type is diagnostic data, at least one of the ECU operation abnormality index and the ECU acquisition abnormality index is parsed and obtained as the ECU index data.

[0063] S206: Analyze the ECU indicator data to obtain the current status information and business information of the vehicle.

[0064] In the embodiment of the present application, the current state information of the vehicle refers to whether the vehicle is in a normal state or an abnormal state, and if it is in an abnormal state, what type of abnormal state it is in, etc. The business information of the vehicle refers to the information related to the business reflected by the ECU data.

[0065] S207: When it is determined that the vehicle is abnormal based on the status information, an alarm message is sent to the vehicle end.

[0066] The cloud can also send alarm information to the terminal devices of operators, monitoring personnel or data analysts, so that relevant personnel can promptly understand the abnormal conditions of the vehicle and respond and handle them quickly.

[0067] S208: Generate data analysis statistics based on business information for use in problem troubleshooting and business monitoring.

[0068] The statistical results of data analysis can be displayed in a visual manner on the interface for relevant personnel to view, analyze or process. For example, it can be displayed in various forms such as tables, statistical graphs, histograms or animation demonstrations, and the embodiments of the present application do not specifically limit this.

[0069] In one implementation, the method may further include: configuring the collection rules of the vehicle-mounted ECU data in advance according to the business type, and sending the collection rules to the vehicle side to instruct the vehicle side to collect the ECU data according to the collection rules. Accordingly, after receiving the collection rules, the vehicle side can collect the ECU data according to the collection rules, and then report the collected ECU data to the cloud according to the reporting rules. This method can realize the customization of the collection method and reporting method of the vehicle-side ECU data, achieve personalized monitoring, improve the monitoring capability, and realize the diversity of monitoring means.

[0070] In addition, it is worth mentioning that the collection rules and reporting rules of the vehicle-mounted ECU data in the embodiments of the present application can be updated in a variety of ways, including but not limited to: automatic update and / or manual update, without specific limitation.

[0071] The above method provided in this embodiment configures the reporting rules of the on-board ECU data according to the business type in advance, sends the reporting rules to the vehicle side, receives the ECU data reported by the vehicle side according to the reporting rules, parses the ECU data according to the parsing rules to generate ECU index data, and analyzes the ECU index data to obtain the data monitoring results, thereby realizing the cloud-based effective monitoring of various on-board ECU data based on the business type, improving the monitoring efficiency and monitoring capabilities, and improving and refining the ECU data monitoring intensity, providing a comprehensive and reliable solution for the vehicle-cloud collaborative monitoring of ECU data.

[0072] Figure 3 FIG. 1 is a schematic diagram of a rule issuance and data reporting process according to another embodiment of the present application. Figure 3 As shown, the cloud operator can configure the corresponding ECU business type and reporting parameters as needed. After generating the reporting rules for ECU data, the cloud can send the reporting rules to the specified vehicle. After receiving the reporting rules, the vehicle first collects ECU data, compresses the generated data file, and then reports the compressed ECU data file to the cloud according to the reporting rules. After receiving the ECU data file, the cloud decompresses it and stores it in the database for easy operation and maintenance.

[0073] Figure 4 FIG. 1 is a schematic diagram of cloud monitoring according to another embodiment of the present application. Figure 4As shown, the cloud retrieves the received ECU data from the database, analyzes the ECU indicator data according to the parsing rules to obtain the current status information and business information of the vehicle, and generates ECU indicator data. Among them, when the vehicle is determined to be abnormal based on the status information, an alarm message is sent to the vehicle end and data analysts to facilitate problem troubleshooting and business monitoring.

[0074] Figure 5 FIG. 1 is a schematic diagram of a vehicle-cloud collaboration scenario according to another embodiment of the present application. Figure 5 As shown, the process of steps A1 to A8 includes: the cloud generates and sends the reporting rules of ECU data to the vehicle side, the vehicle side collects data and generates log files, compresses and reports to the cloud side according to the reporting rules. The process of steps B1 to B4 includes: the cloud side parses and generates ECU indicator data according to the log files reported by the vehicle side, generates BI data tables for problem troubleshooting after analysis and statistics, and generates alarm information in the event of vehicle abnormalities, so that relevant personnel can be quickly notified for processing.

[0075] Figure 6 FIG. 2 shows a structural diagram of a vehicle-mounted ECU data monitoring device according to another embodiment of the present application. Figure 6 As shown, the device may include:

[0076] Configuration module 601, used to configure the reporting rules of vehicle ECU data in advance according to the business type;

[0077] A sending module 602 is used to send the reporting rules to the vehicle end;

[0078] The receiving module 603 is used to receive the ECU data reported by the vehicle end according to the reporting rules;

[0079] The parsing module 604 is used to parse the ECU data according to the parsing rules to generate ECU indicator data;

[0080] The monitoring module 605 is used to analyze the ECU indicator data to obtain data monitoring results.

[0081] In one implementation, the configuration module 601 can be used to: pre-divide the service into multiple service types according to service characteristics, generate corresponding ECU reporting parameter information for each service type, save the correspondence between the service type and the ECU reporting parameter information, and obtain the reporting rules for the vehicle-mounted ECU data.

[0082] In one implementation, the configuration module 601 can also be used to configure the collection rules of the vehicle ECU data in advance according to the service type. Accordingly, the sending module can also be used to send the collection rules to the vehicle to instruct the vehicle to collect ECU data according to the collection rules.

[0083] In an embodiment of the present application, the above-mentioned business type may include at least one of the following: system type, application type, data embedding type or diagnostic data type.

[0084] In one embodiment, the above-mentioned parsing module 604 can be used to: determine the business type of ECU data, and parse according to the business type. If it is a system type, then parse and obtain at least one of system abnormality, memory indicator and hardware indicator as ECU indicator data; if it is an application type, then parse and obtain at least one of application abnormality, user operation indicator and operation statistical indicator as ECU indicator data; if it is a data embedding type, then parse and obtain at least one of upstream link indicator and downstream link indicator as ECU indicator data; if it is a diagnostic data type, then parse and obtain at least one of ECU operation abnormality indicator and ECU acquisition abnormality indicator as ECU indicator data.

[0085] In an embodiment of the present application, the above-mentioned ECU reporting parameter information may include at least one of the following: ECU name, reporting frequency, reporting data packet size, reporting data type, reporting level, reporting trigger or data collection frequency.

[0086] In an embodiment of the present application, the above-mentioned monitoring module 605 can be used to: analyze the ECU indicator data to obtain the current status information and business information of the vehicle, and when the vehicle is determined to be abnormal based on the status information, send an alarm message to the vehicle end, and generate data analysis statistical results based on the business information for problem troubleshooting and business monitoring.

[0087] The functions of each module in each device in the embodiments of the present application can be found in the corresponding description in the above method, and will not be repeated here.

[0088] The above-mentioned device provided in this embodiment can execute the method provided in any of the above-mentioned method embodiments. The detailed process is described in the method embodiment and will not be repeated here.

[0089] The above-mentioned device provided in this embodiment configures the reporting rules of the on-board ECU data according to the business type in advance, sends the reporting rules to the vehicle side, receives the ECU data reported by the vehicle side according to the reporting rules, parses the ECU data according to the parsing rules to generate ECU indicator data, and analyzes the ECU indicator data to obtain the data monitoring results, thereby realizing the cloud-based effective monitoring of various on-board ECU data based on the business type, improving the monitoring efficiency and monitoring capabilities, and providing a reliable solution for the vehicle-cloud collaborative monitoring of ECU data.

[0090] Figure 7 FIG. 1 is a block diagram showing a structure of an electronic device according to an embodiment of the present application. Figure 7As shown, the electronic device includes: a memory 710 and a processor 720, and the memory 710 stores instructions that can be run on the processor 720. When the processor 720 executes the instruction, the vehicle-mounted ECU data monitoring method in the above embodiment is implemented. The number of the memory 710 and the processor 720 can be one or more. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or required herein.

[0091] The electronic device may also include a communication interface 730 for communicating with external devices and performing data exchange transmission. Each device is connected to each other using different buses and can be installed on a common mainboard or installed in other ways as needed. The processor 720 can process instructions executed in the electronic device, including instructions stored in or on a memory to display graphical information of a GUI on an external input / output device (such as a display device coupled to an interface). In other embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple electronic devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0092] Optionally, in a specific implementation, if the memory 710, the processor 720 and the communication interface 730 are integrated on a chip, the memory 710, the processor 720 and the communication interface 730 can communicate with each other through an internal interface.

[0093] It should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc. It is worth noting that the processor may be a processor supporting the Advanced RISC Machines (ARM) architecture.

[0094] An embodiment of the present application provides a computer-readable storage medium (such as the memory 710 mentioned above), which stores computer instructions. When the program is executed by a processor, the method provided in the embodiment of the present application is implemented.

[0095] Optionally, the memory 710 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the electronic device for data management, etc. In addition, the memory 710 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 710 may optionally include a memory remotely arranged relative to the processor 720, and these remote memories may be connected to the electronic device for data management 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.

[0096] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine different embodiments or examples described in this specification and the features of different embodiments or examples, unless they are contradictory.

[0097] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0098] Any process or method description in the flow chart or otherwise described herein can be understood to represent a module, fragment or portion of a code including one or more (two or more) executable instructions for implementing the steps of a specific logical function or process. And the scope of the preferred embodiment of the present application includes other implementations, in which the functions may not be performed in the order shown or discussed, including in a substantially simultaneous manner or in a reverse order according to the functions involved.

[0099] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, which can be embodied in any computer-readable medium for use by an instruction execution system, apparatus or device (such as a computer-based system, a system including a processor or other system that can fetch instructions from an instruction execution system, apparatus or device and execute instructions), or used in combination with these instruction execution systems, apparatuses or devices.

[0100] It should be understood that the various parts of the present application can be implemented with hardware, software, firmware or a combination thereof. In the above embodiments, multiple steps or methods can be implemented with software or firmware stored in a memory and executed by a suitable instruction execution system. All or part of the steps of the above embodiment method can be completed by instructing the relevant hardware through a program, which can be stored in a computer-readable storage medium, and when the program is executed, it includes one of the steps of the method embodiment or a combination thereof.

[0101] In addition, each functional unit in each embodiment of the present application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into one module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of a software functional module. If the above-mentioned integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. The storage medium can be a read-only memory, a disk or an optical disk, etc.

[0102] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A vehicle-mounted ECU data monitoring method, characterized in that: include: Pre-configure the reporting rules of vehicle ECU data according to the business type; Sending the reporting rules to the vehicle end; Receiving ECU data reported by the vehicle end according to the reporting rules; Parsing the ECU data according to the parsing rules to generate ECU indicator data; The ECU indicator data is analyzed to obtain data monitoring results.

2. The method according to claim 1, characterized in that Pre-configure the reporting rules for vehicle ECU data according to the business type, including: Divide the business into multiple business types in advance according to business characteristics; Generate corresponding ECU reporting parameter information for each business type; The correspondence between the service type and the ECU reporting parameter information is saved to obtain the reporting rules for the vehicle-mounted ECU data.

3. The method according to claim 1, characterized in that: Also includes: Pre-configure the collection rules of vehicle ECU data according to the business type; The collection rules are sent to the vehicle side to instruct the vehicle side to collect ECU data according to the collection rules.

4. The method according to claim 1, characterized in that: The business type includes at least one of the following: system type, application type, data embedding type or diagnostic data type.

5. The method according to claim 4, characterized in that The ECU data is parsed according to the parsing rules to generate ECU indicator data, including: Determine the business type of the ECU data; Parsing according to the business type; If it is a system type, at least one of system abnormality, memory index and hardware index is obtained by parsing as ECU index data; If it is an application type, at least one of application exception, user operation index and operation statistical index is obtained by parsing as ECU index data; If it is a data embedding type, at least one of the upstream link indicator and the downstream link indicator is parsed and obtained as the ECU indicator data; If the data type is diagnostic data, at least one of the ECU operation abnormality index and the ECU acquisition abnormality index is parsed and obtained as the ECU index data.

6. The method according to claim 2, characterized in that The ECU reporting parameter information includes at least one of the following: ECU name, reporting frequency, reporting data packet size, reporting data type, reporting level, reporting trigger or data collection frequency.

7. The method according to claim 1, characterized in that The ECU indicator data is analyzed to obtain data monitoring results, including: Analyze the ECU indicator data to obtain the current status information and business information of the vehicle; When the vehicle is determined to be abnormal according to the status information, an alarm message is sent to the vehicle end; Generate data analysis statistics based on the business information for use in problem troubleshooting and business monitoring.

8. A vehicle-mounted ECU data monitoring device, characterized in that: include: Configuration module, used to configure the reporting rules of vehicle ECU data in advance according to the business type; A sending module, used for sending the reporting rule to the vehicle end; A receiving module, used for receiving ECU data reported by the vehicle end according to the reporting rule; A parsing module, used for parsing the ECU data according to parsing rules to generate ECU indicator data; The monitoring module is used to analyze the ECU indicator data to obtain data monitoring results.

9. An electronic device, characterized in that: include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the computer instructions are executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images