Bus monitoring method, device and equipment of vehicle and medium

Abstract

The invention relates to a bus monitoring method, device and equipment for a vehicle and a medium, and the method comprises the steps: responding to a received bus monitoring request of the vehicle, and obtaining the calibration information of the vehicle; inquiring a preset corresponding relation according to the calibration information of the vehicle, and determining a target equipment description file corresponding to the calibration information of the vehicle from a plurality of equipment description files; wherein the corresponding relationship comprises a relationship between the calibration information and the equipment description file; and monitoring the bus of the vehicle based on the target equipment description file to obtain a bus monitoring result. According to the technical scheme provided by the invention, when the buses of different versions of vehicles are monitored, the equipment description file does not need to be uploaded every time, so that the operation is simplified.

Description

Technical Field

[0001] The present disclosure relates to the field of vehicle technology, and in particular to a bus monitoring method, device, equipment and medium for a vehicle. Background Art

[0002] With the continuous improvement of vehicle safety requirements, monitoring various vehicle data has become a common function. Bus monitoring is an important part of vehicle monitoring and is of great significance to the safety and reliability of vehicle operation.

[0003] Currently, when a vehicle is monitored by bus, software is installed in a computer device and the device description file of the vehicle is uploaded. The vehicle is connected to the computer device to implement bus monitoring. The monitoring solution adopts a C / S architecture, and resource files cannot be shared. When the computer device is used to perform bus monitoring on vehicles with different vehicle system versions, the device description file needs to be uploaded again, which is cumbersome. Summary of the invention

[0004] In order to solve the above technical problems, the present disclosure provides a vehicle bus monitoring method, device, equipment and storage medium.

[0005] In a first aspect, an embodiment of the present disclosure provides a bus monitoring method for a vehicle, comprising:

[0006] In response to receiving a bus monitoring request from a vehicle, obtaining calibration information of the vehicle; the calibration information is used to indicate a vehicle system version of the vehicle;

[0007] According to the calibration information of the vehicle, a preset corresponding relationship is searched, and a target device description file corresponding to the calibration information of the vehicle is determined from a plurality of device description files; wherein the corresponding relationship includes a relationship between the calibration information and the device description file;

[0008] The bus of the vehicle is monitored based on the target device description file to obtain a bus monitoring result.

[0009] In a second aspect, an embodiment of the present disclosure provides a bus monitoring device for a vehicle, comprising:

[0010] An acquisition module, configured to acquire calibration information of the vehicle in response to receiving a bus monitoring request from the vehicle; the calibration information is used to indicate a vehicle system version of the vehicle;

[0011] A query module, configured to query a preset correspondence relationship according to the calibration information of the vehicle, and determine a target device description file corresponding to the calibration information of the vehicle from a plurality of device description files; wherein the correspondence relationship includes a relationship between the calibration information and the device description file;

[0012] The monitoring module is used to monitor the bus of the vehicle based on the target device description file to obtain a bus monitoring result.

[0013] In a third aspect, an embodiment of the present disclosure provides an electronic device, comprising: a processor; a memory for storing executable instructions of the processor; the processor is used to read the executable instructions from the memory and execute the instructions to implement the vehicle bus monitoring method described in the first aspect above.

[0014] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, the vehicle bus monitoring method described in the first aspect is implemented.

[0015] In a fifth aspect, an embodiment of the present disclosure provides a vehicle, comprising a bus monitoring device for a vehicle as described in the second aspect above, or an electronic device as described in the third aspect above.

[0016] The technical solution provided by the embodiment of the present disclosure has the following advantages compared with the prior art: in response to receiving a bus monitoring request of a vehicle, the calibration information of the vehicle is obtained, a preset corresponding relationship is queried according to the calibration information of the vehicle, and a target device description file corresponding to the calibration information of the vehicle is determined from multiple device description files, and then the bus of the vehicle is monitored based on the target device description file to obtain a bus monitoring result. Therefore, the relationship between the calibration version and the device description file is pre-maintained on the server side, and the corresponding target device description file is determined according to the calibration information of the vehicle during monitoring to realize vehicle bus monitoring. Compared with the monitoring solution of the C / S architecture, when monitoring the bus of vehicles of different versions, there is no need to upload the device description file each time, thereby simplifying the operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0018] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0019] Figure 1 A schematic flow chart of a vehicle bus monitoring method provided by an embodiment of the present disclosure;

[0020] Figure 2 A schematic flow chart of another vehicle bus monitoring method provided by an embodiment of the present disclosure;

[0021] Figure 3 A schematic structural diagram of a vehicle bus monitoring device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0022] In order to more clearly understand the above-mentioned objectives, features and advantages of the present disclosure, the scheme of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features in the embodiments can be combined with each other without conflict.

[0023] In the following description, many specific details are set forth to facilitate a full understanding of the present disclosure, but the present disclosure may also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present disclosure, rather than all of the embodiments.

[0024] Figure 1 This is a flow chart of a vehicle bus monitoring method provided in an embodiment of the present disclosure. The method provided in an embodiment of the present disclosure can be executed by a bus monitoring device of the vehicle, which can be implemented in software and / or hardware and can be integrated on any electronic device with computing capabilities, such as a server.

[0025] like Figure 1 As shown, the bus monitoring method for a vehicle provided by an embodiment of the present disclosure may include:

[0026] Step 101 : in response to receiving a bus monitoring request from a vehicle, obtaining calibration information of the vehicle.

[0027] The method of the embodiment of the present disclosure is used in a bus monitoring scenario of a vehicle to monitor bus signals, wherein the bus includes a CAN (Controller Area Network) bus and a LIN (Local Interconnect Network) bus.

[0028] In this embodiment, when the bus monitoring is performed on the vehicle, the vehicle sends a bus monitoring request to the server, and the bus monitoring request carries the calibration information of the vehicle. Then, after receiving the bus monitoring request of the vehicle, the server parses the bus monitoring request to obtain the calibration information of the vehicle. The calibration information of the vehicle is used to indicate the system version of the vehicle computer. Different vehicles may have different system versions. Optionally, the calibration information of the vehicle includes a software identifier and a controller baseline version.

[0029] Step 102 : querying a preset correspondence relationship according to the calibration information of the vehicle, and determining a target device description file corresponding to the calibration information of the vehicle from a plurality of device description files.

[0030] Among them, the corresponding relationship includes the relationship between the calibration information and the device description file, wherein the device description file is applied to vehicle data monitoring, and is used to monitor and analyze the operating status of each logical node in the network. For example, the device description file includes a DBC (Database file CAN, a device description file of a device on the CAN) file and an LDF (LIN description file, a device description file of a device on the LIN) file. Taking the DBC file as an example, the DBC file describes the information of each logical node in the CAN. The DBC file can be used to monitor and analyze the operating status of each logical node in the CAN network. The DBC file includes messages and signals, and defines the attributes of the messages and signals. During the bus monitoring process of the vehicle, the DBC file is associated with the vehicle, and the vehicle collects the corresponding type of signal on the CAN bus of the vehicle according to the signal type defined in the DBC file.

[0031] In this embodiment, all versions of device description files are uploaded to the server in advance, and the server parses the device description files. After the parsing is completed, the corresponding relationship between the calibration information and the device description files is established. Optionally, at each version update, an update command is executed to update the existing version of the device description file to the latest version, and then the latest version of the device description file is uploaded to the server. The server parses the latest version of the device description file and establishes the relationship between the latest version of the device description file and the calibration information corresponding to the version. Thus, the relationship between the current version of the device description file and the corresponding calibration information can be established at each version update. After multiple version updates, the server stores the relationship between each version of the device description file and the corresponding calibration information.

[0032] As an example, the calibration information is the software identification and the controller baseline version. According to the vehicle's software identification and the controller baseline version, the correspondence is queried to determine the file name corresponding to the software identification and the controller baseline version. The server determines the device description file consistent with the file name from all device description files as the target device description file.

[0033] Step 103: monitor the bus of the vehicle based on the target device description file to obtain a bus monitoring result.

[0034] In this embodiment, the corresponding signal on the bus is monitored according to the signal content in the target device description file to obtain the bus monitoring result.

[0035] As an example, the target description file includes DBC files of body CAN (BDCAN), audio and video entertainment CAN (ECAN), chassis CAN (CHCAN), and power CAN (PTCAN). According to the signal content of the DBC file, the corresponding signals on the body CAN bus, audio and video entertainment CAN bus, chassis CAN bus, and power CAN bus are monitored respectively to obtain bus monitoring results. The bus monitoring results are used to monitor whether each signal is normal. The bus monitoring results include single signal single value, single signal multiple values, time series and other forms.

[0036] According to the technical solution of the embodiment of the present disclosure, in response to receiving a bus monitoring request of a vehicle, the calibration information of the vehicle is obtained, a preset correspondence is queried according to the calibration information of the vehicle, and a target device description file corresponding to the calibration information of the vehicle is determined from multiple device description files. Then, the bus of the vehicle is monitored based on the target device description file to obtain a bus monitoring result. Therefore, the relationship between the calibration version and the device description file is pre-maintained on the server side, and the corresponding target device description file is determined according to the calibration information of the vehicle during monitoring to realize vehicle bus monitoring. Compared with the monitoring solution of the C / S architecture, when monitoring the bus of vehicles of different versions, there is no need to upload the device description file each time, thereby simplifying the operation.

[0037] Based on the above embodiments, Figure 2 A flow chart of another vehicle bus monitoring method provided by an embodiment of the present disclosure is shown as follows: Figure 2 As shown, the method includes:

[0038] Step 201: receiving a first device description file to be parsed, and parsing the first device description file.

[0039] The first device description file includes a DBC file and / or an LDF file. The DBC file is encoded using gb2312, and the LDF file is encoded using utf-8.

[0040] In this embodiment, after each parsing of the device description file, the hash value of the device description file is calculated and saved for subsequent deduplication. The hash value of the device description file is obtained by processing the file content of the device description file according to a preset hash algorithm, such as the sha256 algorithm.

[0041] Optionally, taking the parsing process of the first device description file as an example, the server receives the first device description file to be parsed, and calculates the first hash value of the first device description file. If the first hash value is different from any pre-stored second hash value, the first device description file is parsed and the first hash value is stored, wherein the second hash value is the hash value of the parsed second device description file; if at least one of the pre-stored second hash values ​​is the same as the first hash value, it is determined that the same device description file has been parsed, in which case the first device description file is skipped and the parsing operation on the first device description file is not performed. Thus, in the parsing process, deduplication is performed through the hash value of the device description file, and for the case where the file name is the same but the file content is different, the parsed device description file can be accurately determined, repeated parsing can be avoided, and processing efficiency can be improved.

[0042] Step 202 : in response to receiving a bus monitoring request from a vehicle, obtaining a software identification and a controller baseline version of the vehicle.

[0043] In this embodiment, the calibration information is the software identifier and the controller baseline version. The calibration information can be obtained based on the car-cloud remote calibration system. Each time the version is updated, the calibration software identifier is: KuDDCI_XCUSWID_null, the controller baseline version is: KuDDCI_XCUVersion_null, and the uncalibrated software defaults to 0000-0000.

[0044] Step 203 , according to the vehicle software identification and the controller baseline version, query the preset corresponding relationship to determine the target device description file corresponding to the vehicle software identification and the controller baseline version.

[0045] In this embodiment, the server stores the hash value of each device description file, and the corresponding relationship is the relationship between the software identification, the controller baseline version and the hash value of the corresponding device description file. Optionally, based on the vehicle's software identification and the controller baseline version, the corresponding relationship is queried to determine the third hash value corresponding to the software identification and the controller baseline version, and the second hash values ​​of multiple device description files are compared with the third hash values, and the device description file with consistent comparison results is determined as the target device description file.

[0046] As an example, there may be multiple hash values ​​corresponding to each software identifier and controller baseline version. For example, for version one of the software identifier and controller baseline version, the corresponding hash values ​​include A and B. A and B correspond to the device description file of version one, respectively. The server determines the device description file with hash value A and the device description file with hash value B from multiple device description files as the target device description files.

[0047] Step 204 , monitoring the bus of the vehicle based on the target device description file to obtain a bus monitoring result.

[0048] In this embodiment, the monitoring content recorded in the target device description file is extracted, and at least one monitoring item is generated according to the monitoring content, so as to display at least one monitoring item on the front-end interface. The user can select one or more target monitoring items from the at least one monitoring item displayed on the front-end interface and trigger monitoring. In response to the triggering operation of the target monitoring item from the at least one monitoring item displayed on the front-end interface, the bus of the vehicle is monitored to obtain the bus monitoring result of the target monitoring item.

[0049] As an example, for the bus type in the monitoring content, the first monitoring item corresponding to each bus type is generated to display the first monitoring item on the front-end interface. For example, the software identifier is 0010, the controller baseline version is 0008, and the corresponding first monitoring items include BDCAN1, BDCAN2, BDCAN3, ECAN, CHCAN1, CHCAN2, PTCAN1, PTCAN2, LIN1, LIN2, LIN3, LIN4, and LIN5, and the above-mentioned first monitoring items are displayed on the front-end interface. The user selects BDCAN1 in the above-mentioned first monitoring items and triggers the monitoring button. According to the DBC file W01_CAN_Matrix_V2.1.3_20220929_XCU_BDCAN1 corresponding to BDCAN1, the corresponding type signal of the vehicle body CAN bus is monitored to obtain the bus monitoring result of BDCAN1.

[0050] As another example, for the signal names under the bus types in the monitoring content, a second monitoring item corresponding to each signal name under the bus type is generated to display the second monitoring item on the front-end interface. In this example, the bus types include, for example, BDCAN1, BDCAN2, BDCAN3, ECAN, CHCAN1, CHCAN2, PTCAN1, PTCAN2, LIN1, LIN2, LIN3, LIN4, LIN5, etc. Based on any of the above bus types, for each signal name under the bus type, a second monitoring item corresponding to the signal name is set. For example, for the signal names S1 and S2 under BDCAN1, the monitoring item corresponding to S1 and the monitoring item corresponding to S2 are set respectively. Therefore, according to the needs of different scenarios, the user can accurately determine the specific signal content that needs to be monitored under each bus type from the provided monitoring items, without the need to monitor all signals, thereby improving the control accuracy of bus monitoring.

[0051] In one embodiment of the present disclosure, the signal content can also be customized to meet a wider range of application requirements. In this embodiment, the server is also provided with a relationship between the calibration information and the detection content, wherein the detection content includes, for example, CPU (Central Processing Unit) load, memory usage, etc. After obtaining the calibration information of the vehicle, the server queries the corresponding relationship according to the calibration information of the vehicle to determine the target detection content corresponding to the calibration information of the vehicle, detects the vehicle according to the target detection content, and generates a detection result of the target detection content.

[0052] As an example, the software identifier is 0010, the controller baseline version is 0008, and the corresponding detection content is CPU load. The CPU load of the vehicle is detected to generate a CPU load detection result. In this way, the custom signal monitoring function is realized, which is not limited to the fixed monitoring content in the device description file, and can meet a wider range of vehicle monitoring needs.

[0053] In the disclosed embodiment, when monitoring the vehicle's bus, the DBC and LDF file contents of that version are obtained through the version written in the calibration, and the values ​​of the monitored items and signals on the bus are displayed through the front-end interface. In addition, signal monitoring and collection can be customized as needed to meet a wider range of vehicle monitoring needs.

[0054] The disclosed embodiment also provides a bus monitoring device for a vehicle.

[0055] Figure 3 A schematic diagram of the structure of a bus monitoring device for a vehicle provided by an embodiment of the present disclosure is shown in FIG. Figure 3 As shown, the bus monitoring device of the vehicle includes: an acquisition module 31 , a query module 32 , and a monitoring module 33 .

[0056] The acquisition module 31 is used to obtain the calibration information of the vehicle in response to receiving the bus monitoring request of the vehicle; the calibration information is used to distinguish the vehicle system version of the vehicle;

[0057] A query module 32, configured to query a preset correspondence according to the calibration information of the vehicle, and determine a target device description file corresponding to the calibration information of the vehicle from a plurality of device description files; wherein the correspondence includes a relationship between the calibration information and the device description file;

[0058] The monitoring module 33 is used to monitor the bus of the vehicle based on the target device description file to obtain a bus monitoring result.

[0059] In one embodiment of the present disclosure, after querying the preset corresponding relationship according to the calibration information of the vehicle, the bus monitoring device of the vehicle further includes:

[0060] A parsing module, configured to receive a first device description file to be parsed, and calculate a first hash value of the first device description file;

[0061] If the first hash value is different from any pre-stored second hash value, parsing the first device description file and storing the first hash value; wherein the second hash value is a hash value of the parsed second device description file;

[0062] Otherwise, skip the first device description file.

[0063] In one embodiment of the present disclosure, the query module 32 is specifically used to:

[0064] According to the software identification and the baseline version of the controller of the vehicle, query the corresponding relationship to determine a third hash value corresponding to the software identification and the baseline version of the controller;

[0065] The second hash values ​​of the multiple device description files are compared with the third hash value, and the device description file with consistent comparison results is determined as the target device description file.

[0066] In one embodiment of the present disclosure, the monitoring module 33 is specifically used to:

[0067] Extracting the monitoring content recorded in the target device description file, generating at least one monitoring item according to the monitoring content, and displaying the at least one monitoring item on the front-end interface;

[0068] In response to a triggering operation on a target monitoring item among at least one monitoring item displayed on the front-end interface, a bus of the vehicle is monitored to obtain a bus monitoring result of the target monitoring item.

[0069] In one embodiment of the present disclosure, the corresponding relationship also includes the relationship between the calibration information and the detection content, and the bus monitoring device of the vehicle also includes:

[0070] A custom signal monitoring module, used to query the corresponding relationship according to the calibration information of the vehicle to determine the target detection content corresponding to the calibration information of the vehicle;

[0071] The vehicle is detected according to the target detection content, and a detection result of the target detection content is generated.

[0072] The bus monitoring device for a vehicle provided in the embodiment of the present disclosure can execute any bus monitoring method for a vehicle provided in the embodiment of the present disclosure, and has the corresponding functional modules and beneficial effects of the execution method. The contents not described in detail in the embodiment of the device of the present disclosure can refer to the description in any method embodiment of the present disclosure.

[0073] An embodiment of the present disclosure also provides an electronic device, which includes one or more processors and a memory.

[0074] The processor may be a central processing unit (CPU) or other forms of processing units having data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device to perform desired functions.

[0075] The memory may include one or more computer program products, and the computer program product may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory (cache), etc. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on a computer-readable storage medium, and a processor may run the program instructions to implement the method of the embodiments of the present disclosure above and / or other desired functions. Various contents such as input signals, signal components, noise components, etc. may also be stored in the computer-readable storage medium.

[0076] In one example, the electronic device may further include: an input device and an output device, and these components are interconnected through a bus system and / or other forms of connection mechanisms. In addition, the input device may also include, for example, a keyboard, a mouse, etc. The output device may output various information to the outside, including determined distance information, direction information, etc. The output device may include, for example, a display, a speaker, a printer, a communication network and a remote output device connected thereto, etc.

[0077] Of course, for simplicity, only some of the components in the electronic device related to the present disclosure are shown, omitting components such as a bus, an input / output interface, etc. In addition, the electronic device may further include any other appropriate components according to specific application scenarios.

[0078] In addition to the above methods and devices, the embodiments of the present disclosure may also be a computer program product, which includes computer program instructions. When the computer program instructions are executed by a processor, the processor executes any method provided by the embodiments of the present disclosure.

[0079] The computer program product may be written in any combination of one or more programming languages ​​to write program code for performing the operations of the disclosed embodiments, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0080] In addition, the embodiments of the present disclosure may also be a computer-readable storage medium on which computer program instructions are stored. When the computer program instructions are executed by a processor, the processor executes any method provided by the embodiments of the present disclosure.

[0081] Computer readable storage media can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can include, for example, but is not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0082] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0083] The above description is only a specific embodiment of the present disclosure, so that those skilled in the art can understand or implement the present disclosure. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments described herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A vehicle bus monitoring method, characterized in that: include: In response to receiving a bus monitoring request from a vehicle, acquiring calibration information of the vehicle; The calibration information is used to indicate the vehicle system version of the vehicle; According to the calibration information of the vehicle, a preset corresponding relationship is searched, and a target device description file corresponding to the calibration information of the vehicle is determined from a plurality of device description files; wherein the corresponding relationship includes a relationship between the calibration information and the device description file; The bus of the vehicle is monitored based on the target device description file to obtain a bus monitoring result.

2. The method according to claim 1, characterized in that Before searching for a preset correspondence relationship according to the calibration information of the vehicle and determining a target device description file corresponding to the calibration information of the vehicle from a plurality of device description files, the method further includes: Receiving a first device description file to be parsed, and calculating a first hash value of the first device description file; If the first hash value is different from any pre-stored second hash value, parsing the first device description file and storing the first hash value; wherein the second hash value is a hash value of the parsed second device description file; Otherwise, skip the first device description file.

3. The method according to claim 2, characterized in that The step of querying a preset correspondence relationship according to the calibration information of the vehicle and determining a target device description file corresponding to the calibration information of the vehicle from a plurality of device description files includes: According to the software identification and the baseline version of the controller of the vehicle, query the corresponding relationship to determine a third hash value corresponding to the software identification and the baseline version of the controller; The second hash values ​​of the multiple device description files are compared with the third hash value, and the device description file with consistent comparison results is determined as the target device description file.

4. The method according to claim 1, characterized in that The monitoring of the bus of the vehicle based on the target device description file to obtain a bus monitoring result includes: Extracting the monitoring content recorded in the target device description file, generating at least one monitoring item according to the monitoring content, and displaying the at least one monitoring item on the front-end interface; In response to a triggering operation on a target monitoring item among at least one monitoring item displayed on the front-end interface, a bus of the vehicle is monitored to obtain a bus monitoring result of the target monitoring item.

5. The method according to claim 4, characterized in that Generating at least one monitoring item according to the monitoring content to display the at least one monitoring item on the front-end interface includes: For the bus types in the monitoring content, generate a first monitoring item corresponding to each bus type, so as to display the first monitoring item on the front-end interface; or, For the signal names under the bus type in the monitoring content, a second monitoring item corresponding to each signal name under the bus type is generated to display the second monitoring item on the front-end interface.

6. The method according to claim 1, characterized in that The corresponding relationship also includes the relationship between the calibration information and the detection content. After obtaining the calibration information of the vehicle, the method further includes: querying the corresponding relationship according to the calibration information of the vehicle to determine the target detection content corresponding to the calibration information of the vehicle; The vehicle is detected according to the target detection content, and a detection result of the target detection content is generated.

7. A bus monitoring device for a vehicle, characterized in that: include: an acquisition module, configured to acquire calibration information of the vehicle in response to receiving a bus monitoring request from the vehicle; The calibration information is used to indicate the vehicle system version of the vehicle; A query module, configured to query a preset correspondence relationship according to the calibration information of the vehicle, and determine a target device description file corresponding to the calibration information of the vehicle from a plurality of device description files; wherein the correspondence relationship includes a relationship between the calibration information and the device description file; The monitoring module is used to monitor the bus of the vehicle based on the target device description file to obtain a bus monitoring result.

8. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is used to read the executable instructions from the memory and execute the instructions to implement the vehicle bus monitoring method described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the bus monitoring method for a vehicle described in any one of claims 1 to 6 is implemented.

10. A vehicle, characterized in that: include: The device as claimed in claim 7, or the electronic device as claimed in claim 8.

Images