Controller installation inspection method, device, equipment, medium and vehicle

Abstract

The application discloses a controller installation verification method, device, equipment, medium and vehicle, which comprises the following steps: obtaining first identification information and first software version information of a target controller in a vehicle; matching the first identification information and the first software version information with a baseline description file of the vehicle to obtain a matching result, wherein the matching result is used to indicate whether the first identification information and the first software version information exist in the baseline description file; and if the matching result is that the first identification information and the first software version information both exist in the baseline description file, it is confirmed that the target controller is installed correctly. In the above, whether the first identification information of the target controller is matched with the baseline description file is first judged, and then whether the first software version information of the target controller is matched with the baseline description file is judged, so that the influence of different manufacturers on the detection result caused by the same first software version information is reduced, and the verification accuracy of the vehicle controller is improved.

Description

TECHNICAL FIELD

[0001] The present application belongs to the field of equipment installation inspection, and particularly relates to a controller installation inspection method, device, equipment, medium and vehicle. BACKGROUND

[0002] The vehicle has a baseline description file, and software version information of each controller in the vehicle can be obtained according to the baseline description file; with the development of the vehicle and the controller, more and more vehicle models start to support a mixed installation mode in which controllers of different manufacturers are installed on the same vehicle.

[0003] The controllers in the mixed installation vehicle are provided by different manufacturers, but the same version number may appear when the same type of controller is provided by different manufacturers.

[0004] Therefore, for the vehicle with mixed installation of controllers, the manufacturer of the controller cannot be accurately known, and even if the first software version information of the target controller obtained from the vehicle exists in the baseline description file, it is impossible to determine whether the target controller is recorded in the baseline, which undoubtedly affects the accuracy of the vehicle controller inspection. SUMMARY

[0005] The embodiments of the present application provide a controller installation inspection method, device, equipment, medium and vehicle, which improves the accuracy of vehicle controller inspection.

[0006] According to a first aspect of the present application, a controller installation inspection method is provided, which can include:

[0007] Obtaining first identification information and first software version information of a target controller in a vehicle, the first identification information being used to identify information of a manufacturer of the target controller;

[0008] Matching the first identification information and the first software version information with a baseline description file of the vehicle to obtain a matching result, wherein the matching result is used to indicate whether the first identification information and the first software version information exist in the baseline description file;

[0009] If the matching result is that the first identification information and the first software version information both exist in the baseline description file, it is confirmed that the target controller is installed correctly.

[0010] Optionally, before obtaining the first identification information and the first software version information of the target controller in the vehicle, the first identification information being used to identify information of a manufacturer of the target controller, the method includes:

[0011] Receiving an update request sent by the manufacturer of the controller, the update request carrying second version information and second identification information;

[0012] In response to the update request, the second version information and the second identification information are configured to the baseline description file.

[0013] Optionally, the baseline description file includes a plurality of mapping relationships, each mapping relationship including preset identification information and preset software version information.

[0014] If the matching result is that the first identification information and the first software version information both exist in the baseline description file, it is confirmed that the target controller is installed correctly, including:

[0015] If the matching result is that the first identification information and the first software version information both exist in the baseline description file, and there is a mapping relationship between the first identification information and the first software version information, it is confirmed that the target controller is installed correctly.

[0016] Optionally, the matching of the first identification information, the first software version information and the baseline description file of the vehicle includes:

[0017] The first identification information is matched with the preset identification information in the baseline description file to obtain an identification information matching result, the identification information matching result being used to indicate whether there is preset identification information matching the first identification information in the baseline description file.

[0018] In a case where the identification information matching result indicates that there is preset identification information matching the first identification information in the baseline description file, the first software version information is matched with the preset software version information in the baseline description file to obtain a matching result, wherein:

[0019] In a case where there is preset software version information matching the first software version information in the baseline description file, the matching result is used to indicate that the first identification information and the first software version information exist in the baseline description file.

[0020] In a case where there is no preset identification information matching the first identification information in the baseline description file, the matching result is used to indicate that the first identification information and the first software version information do not exist in the baseline description file.

[0021] Optionally, the first identification information is unique identification information generated by a manufacturer of the controller.

[0022] According to a second aspect of the present application, an embodiment of the present application provides a controller installation verification device, including:

[0023] An acquisition module is configured to acquire first identification information and first software version information of a target controller in a vehicle, the first identification information being used to identify information of a manufacturer of the target controller.

[0024] The matching module is configured to sequentially match the first identification information and the first software version information with the baseline description file of the vehicle to obtain a matching result, wherein the matching result is used to indicate whether the first identification information and the first software version information exist in the baseline description file.

[0025] The confirming module is configured to confirm that the target controller is installed correctly if the matching result indicates that the first identification information and the first software version information both exist in the baseline description file.

[0026] According to a third aspect of the present application, an embodiment of the present application provides a controller installation verification device, which comprises a processor and a memory storing computer program instructions.

[0027] The processor implements the controller installation verification method according to any one of the first aspect when executing the computer program instructions.

[0028] According to a fourth aspect of the present application, an embodiment of the present application provides a computer storage medium, and the computer readable storage medium stores computer program instructions, and the computer program instructions are executed by the processor to implement the controller installation verification method according to any one of the first aspect.

[0029] According to a fifth aspect of the present application, an embodiment of the present application provides a computer program product, and instructions in the computer program product are executed by the processor of an electronic device to enable the electronic device to execute the controller installation verification method according to any one of the first aspect.

[0030] According to a sixth aspect of the present application, an embodiment of the present application provides a vehicle, and the vehicle comprises the controller installation verification apparatus according to the second aspect or the controller installation verification device according to the third aspect.

[0031] The technical scheme provided by the embodiments of the present application at least brings the following beneficial effects:

[0032] The embodiment of the present application provides a controller installation verification method, device, equipment and computer storage medium, first identification information and first software version information are obtained from a target controller, the first identification information and the first software version information are matched with information recorded in a baseline description file in sequence, whether the first identification information of the target controller is matched with the baseline description file is judged first, so that the manufacturer of the target controller is confirmed, under the premise that the manufacturer is confirmed, whether the first software version information of the target controller is matched with the baseline description file is judged again, so that a matching result is obtained, if the matching result indicates that the first identification information and the first software version both exist in the baseline description file, it is considered that the first identification information and the first software version information of the target controller are consistent with the information recorded in the baseline description file, that is, the target controller is installed correctly, the influence of different manufacturers on the detection result is reduced, and the verification accuracy of the vehicle controller is improved.

[0033] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present application. BRIEF DESCRIPTION OF DRAWINGS

[0034] The accompanying drawings incorporated in and forming a part of the specification illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the application, but are not to be construed as setting forth any undue limitations on the application.

[0035] Figure 1 is a flow chart of a controller installation verification method according to an exemplary embodiment;

[0036] Figure 2 is another flow chart of a controller installation verification method according to an exemplary embodiment;

[0037] Figure 3 is still another flow chart of a controller installation verification method according to an exemplary embodiment;

[0038] Figure 4 is still another flow chart of a controller installation verification method according to an exemplary embodiment;

[0039] Figure 5 is a structural block diagram of a controller installation verification device according to an exemplary embodiment;

[0040] Figure 6 is a structural block diagram of a controller installation verification device according to an exemplary embodiment. DETAILED DESCRIPTION

[0041] In order to enable a more clear understanding of the above-mentioned objects, features and advantages of the present disclosure, the schemes 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.

[0042] In the following description, a large number of specific details are set forth in order to facilitate a thorough understanding of the present disclosure, but the present disclosure can also be implemented in other manners different from those described herein; obviously, the embodiments described in the specification are only a part of the embodiments of the present disclosure, and not all the embodiments.

[0043] As described in the background, with the development of vehicles and controllers, more and more vehicle models begin to support the mixed mounting mode of the same controller of different manufacturers on the same vehicle. Since the controllers in the mixed mounting vehicle are provided by different manufacturers, but different manufacturers may provide the same version number for the same controller. Therefore, for the vehicle with mixed mounting of the controller, the manufacturer of the controller cannot be accurately known, and even if the version number of the target controller is obtained by querying the baseline description file, it is still impossible to determine whether the controller installed on the vehicle is the target controller, which undoubtedly affects the inspection accuracy of the vehicle controller.

[0044] Based on this, the present application provides a controller installation inspection method, device, equipment, medium and vehicle. First, the controller installation inspection method provided by the embodiments of the present application will be introduced.

[0045] Figure 1 A flowchart of a controller installation inspection method provided by an embodiment of the present application is shown. As shown in Figure 1 The method can include the following steps:

[0046] S101, obtaining first identification information and first software version information of a target controller in a vehicle, the first identification information being used to identify the information of the manufacturer of the target controller;

[0047] S102, matching the first identification information, the first software version information and the baseline description file of the vehicle to obtain a matching result, wherein the matching result is used to indicate whether the first identification information and the first software version information exist in the baseline description file;

[0048] S103, if the matching result is that the first identification information and the first software version information both exist in the baseline description file, it is confirmed that the target controller is installed correctly.

[0049] Based on the above embodiment, by obtaining the first identification information and the first software version information from the target controller, sequentially matching the first identification information and the first software version information with the information recorded in the baseline description file, first determining whether the first identification information of the target controller matches the baseline description file, and then determining whether the first software version information of the target controller matches the baseline description file, a matching result is obtained. If the matching result indicates that both the first identification information and the first software version exist in the baseline description file, it means that the first identification information and the first software version information of the target controller are consistent with the information recorded in the baseline description file, that is, the target controller is installed correctly. This reduces the influence of different manufacturers having the same first software version information on the detection result, and improves the accuracy of vehicle controller inspection.

[0050] In the above step S101, the controller installation inspection device can detect the controller installed on the vehicle through a detection tool to obtain the first identification information and the first software version information of the target controller in the vehicle.

[0051] The above target controller is any one of all controllers installed on the vehicle; wherein the controller can be an electronic control unit (ECU).

[0052] The above first identification information can be used to identify the manufacturer of the target controller, wherein the first identification information can be unique identification information generated by the manufacturer of the controller, or unique identification information generated by the vehicle manufacturer or other institutions. Specifically, the first identification information can be a digital code indicating the manufacturer, such as 001, or an identification information such as the manufacturer's letter abbreviation, icon, etc.

[0053] The above first software version information is the version number or version text description information of the target controller, for example, 1.0, or the first edition.

[0054] In the above step S102, the baseline description file includes multiple mapping relationships, each mapping relationship includes preset identification information and preset software version information. After obtaining the first identification information and the first software version information of the target controller, the first identification information and the first software version information are compared with the preset identification information and the preset software version information in the baseline description file, and a matching result is obtained.

[0055] The above preset identification information can include the identification information of all controllers in the vehicle, and the above preset software version information can include the version information corresponding to all controllers in the vehicle.

[0056] Specifically, as shown in Table 1 below, the baseline description file actually corresponds to a list in which preset identification information and preset version information of each controller contained in the baseline are listed.

[0057] Table 1 Content of baseline description file

[0058]

[0059] In step S103 described above, if the matching result shows that the first identification information exists in the baseline description file and the first software version information also exists in the baseline description file, it indicates that the first identification information and the first software version information of the target controller are consistent with those recorded in the baseline description file, that is, the target controller is installed correctly.

[0060] To improve the accuracy of controller installation verification, the application further provides another implementation of the controller installation verification method.

[0061] As Figure 2 Another flowchart of the controller installation verification method provided by an embodiment of the application is shown in FIG. 2. Figure 2 As shown in FIG. 2, before step S101 described above, the following steps can be included:

[0062] S201, receiving an update request sent by a manufacturer of the controller, the update request carrying second version information and second identification information;

[0063] S202, in response to the update request, configuring the second version information and the second identification information to the baseline description file.

[0064] Based on the above embodiment, by receiving the update request sent by the manufacturer of the controller, responding to the update request, and updating the baseline description file in a timely manner, the updated content is carried in the baseline description file, which reduces the possibility of misjudging the controller installation error due to the untimely update of the baseline description file, and improves the accuracy of the controller installation verification.

[0065] In step S201 described above, both the vehicle and the controller are constantly developing, and more and more different manufacturers and different types of controllers will be applied to the vehicle, therefore, the controller installation verification device needs to receive the update request sent by the manufacturer of the controller, and the update request can carry the second version information and the second identification information.

[0066] The second version information described above can be version information corresponding to a new controller that is originally not installed on the vehicle and does not exist in the baseline description file, and correspondingly, the second identification information described above can also be version information corresponding to a new controller that is originally not installed on the vehicle.

[0067] For example, if only 001 and 002 are preset in the baseline description file, and the identification information of the new controller is 003, the identification information 003 of the new controller needs to be added to the baseline description file to form a new baseline description file, and the preset identification information in the new baseline description file is 001, 002 and 003; similarly, the version information of the new controller also needs to be added to the baseline description file.

[0068] Furthermore, if the controller manufacturer produces a second controller to replace the original first controller, the identification information and the software version information corresponding to the second controller also need to be replaced in the baseline file.

[0069] In the step S202, if the vehicle uses a new controller, the controller installation verification device needs to respond to the update request issued by the manufacturer, and configure the second identification information and the second version information corresponding to the new controller in the baseline description file of the vehicle.

[0070] In order to improve the accuracy of controller installation verification, the application further provides another implementation manner of the controller installation verification method.

[0071] As Figure 3 Another flowchart of the controller installation verification method provided by an embodiment of the application is shown in FIG. 3. Figure 3 As shown in S103, the step can include:

[0072] S301, if the matching result is that the first identification information and the first software version information both exist in the baseline description file, and the first identification information and the first software version information have a mapping relationship, it is confirmed that the target controller is installed correctly.

[0073] Based on the above embodiment, after it is determined that the first identification information and the first software version information both exist in the baseline description file, and the preset identification information and the preset software version information in the baseline description file have a mapping relationship, it is further determined whether the first identification information and the first software version information have a mapping relationship. When the first identification information and the first software version information have a mapping relationship, it is proved that the first identification information exists in the preset identification information, and the corresponding first software version information exists in the preset version information. By judging whether the manufacturer of the target controller corresponds to the first software version information through the mapping relationship, the accuracy of the controller installation verification judgment is improved.

[0074] In step S301, the preset identification information and the preset software version information in the baseline description file have a mapping relationship, so that the controller installation verification can confirm that the first identification information exists in the preset identification information in the baseline description file, and then check whether the first software version information exists in the preset version information in the baseline description file. If the first software version information exists in the preset version information, it indicates that the first identification information and the first software version information also have a corresponding relationship, so that the target controller installation can be confirmed to be correct.

[0075] To improve the accuracy of the controller installation verification, the application further provides another implementation of the controller installation verification method.

[0076] As Figure 4 Another flowchart of the controller installation verification method provided by an embodiment of the application is shown in FIG. 4. Figure 4 As shown in S103, the method further includes:

[0077] S401, match the first identification information with the preset identification information in the baseline description file to obtain an identification information matching result, the identification information matching result indicating whether the baseline description file has the preset identification information matching the first identification information;

[0078] S402, in the case that the identification information matching result indicates that the baseline description file has the preset identification information matching the first identification information, match the first software version information with the preset software version information in the baseline description file to obtain a matching result.

[0079] Based on the above embodiment, the first identification information is matched with the preset identification information in the baseline description file to obtain an identification information matching result. In the case that the identification information matching result indicates that the first identification information exists in the preset identification information in the baseline description file, the first software version information is matched with the preset software version information in the baseline description file to obtain a matching result. That is, it is confirmed whether the manufacturer of the target controller exists in the baseline description file. The controller whose manufacturer exists in the baseline description file is matched with the first software version information and the baseline description file. The probability of the case that the first identification information of the target controller does not correspond to the software version number is reduced, and the accuracy of the target controller installation detection is improved.

[0080] In step S401, the controller installation verification device queries whether the first identification information exists in the baseline description file, and generates the query result as the identification information matching result.

[0081] In step S402, if the identification information matching result indicates that the first identification information matches the preset identification information in the baseline description file, the controller installation verification device queries whether the first software version information exists in the preset software version information in the baseline description file, and generates a query result as the matching result.

[0082] Specifically, if the first software version information is queried in the preset software version information in the baseline description file, the matching result indicates that the first identification information and the first software version information both exist in the baseline description file.

[0083] If the preset identification information matching the first identification information does not exist in the baseline description file, the matching result indicates that the first identification information and the first software version information do not exist in the baseline description file.

[0084] It should be noted that the application scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems as new application scenarios appear.

[0085] Based on the same inventive concept, the present application also provides a controller installation verification device. The specific combination Figure 5 will be described in detail.

[0086] Figure 5 The hardware structure of the controller installation verification device 500 provided by the embodiments of the present application is shown.

[0087] As Figure 5 shown, the controller installation verification device 500 can include:

[0088] The acquisition module 501 is configured to acquire first identification information and first software version information of a target controller in a vehicle, the first identification information being used to identify information of a manufacturer of the target controller.

[0089] The matching module 502 is configured to sequentially match the first identification information and the first software version information with a baseline description file of the vehicle to obtain a matching result, wherein the matching result is used to indicate whether the first identification information and the first software version information exist in the baseline description file.

[0090] The confirmation module 503 is configured to confirm that the target controller is installed correctly if the matching result indicates that the first identification information and the first software version information both exist in the baseline description file.

[0091] In the controller installation inspection device 500 provided in this embodiment, the acquisition module 501 obtains the first identification information and the first software version information from the target controller. The matching module 502 sequentially matches the first identification information and the first software version information with the information recorded in the baseline description file. First, it determines whether the first identification information of the target controller matches the baseline description file, and then it determines whether the first software version information of the target controller matches the baseline description file, thereby obtaining the matching result. If the matching result indicates that both the first identification information and the first software version exist in the baseline description file, it means that the first identification information and the first software version information of the target controller are consistent with those recorded in the baseline description file. The confirmation module 503 then confirms that the target controller is installed correctly, reducing the impact of the same first software version information from different manufacturers on the test results and improving the inspection accuracy of the vehicle controller.

[0092] Optionally, the controller mounting inspection device 500 may include:

[0093] The receiving module is used to receive update requests sent by the controller manufacturer. The update requests carry second version information and second identification information.

[0094] The configuration module is used to configure the second version information and the second identification information into the baseline description file in response to an update request.

[0095] Optionally, the matching module 502 may include:

[0096] The confirmation unit confirms that the target controller is installed correctly if the matching result shows that both the first identification information and the first software version information exist in the baseline description file and there is a mapping relationship between the first identification information and the first software version information.

[0097] Optionally, the matching module 502 may also include:

[0098] The first matching unit is used to match the first identification information with the preset identification information in the baseline description file to obtain the identification information matching result. The identification information matching result is used to indicate whether there is preset identification information in the baseline description file that matches the first identification information.

[0099] The second matching unit, when the identification information matching result indicates that there is preset identification information in the baseline description file that matches the first identification information, is used to match the first software version information with the preset software version information in the baseline description file to obtain a matching result.

[0100] The controller installation inspection device 500 provided in this application embodiment can achieve... Figures 1 to 4The method embodiments of the application implement the various processes described above and achieve the same technical effects. To avoid repetition, the details are not described here.

[0101] Figure 6 A hardware structure schematic diagram of the controller installation verification device provided by the embodiment of the application is shown.

[0102] The controller installation verification device can include a processor 601 and a memory 602 storing computer program instructions.

[0103] Specifically, the processor 601 described above can include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or can be configured as one or more integrated circuits implementing the embodiments of the application.

[0104] The memory 602 can include a mass storage for data or instructions. By way of example and not limitation, the memory 602 can include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. Where appropriate, the memory 602 can include removable or non-removable (or fixed) media. Where appropriate, the memory 602 can be internal or external to the integrated gateway disaster recovery device. In certain embodiments, the memory 62 is a non-volatile solid-state memory.

[0105] In certain embodiments, the memory 602 can include read-only memory (ROM), random access memory (RAM), a disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical, or other physical / tangible memory storage device. Thus, in general, the memory 602 includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software that, when executed (e.g., by the one or more processors 601), is operable to perform operations described with reference to the methods according to an aspect of the present application.

[0106] The processor 601 implements any one of the controller installation verification methods described above by reading and executing the computer program instructions stored in the memory 602.

[0107] In one example, the controller installation verification device can further include a communication interface 603 and a bus 604. As shown, the processor 601, the memory 602, and the communication interface 603 are connected through the bus 604 and complete communication with each other.

[0108] The communication interface 603 is mainly configured to implement the communication between the modules, devices, units and / or equipment in the embodiments of the present application.

[0109] The bus 604 includes hardware, software, or both. By way of example and not limitation, the bus 604 can include an accelerated graphics port (AGP) or other graphics bus, an enhanced industry standard architecture (EISA) bus, a front-side bus (FSB), a HyperTransport (HT) interconnect, an industry standard architecture (ISA) bus, an InfiniBand™ bus, a low pin count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a peripheral component interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a serial advanced technology attachment (SATA) bus, a video electronics standards board (VLB) bus, or another suitable bus or a combination of two or more of these. Where appropriate, the bus 604 can include one or more buses 604. Although the present application is described and illustrated with a particular bus 604, the present application contemplates any suitable bus or interconnect.

[0110] The controller installation verification device can be based on the current controller installation verification method, thereby realizing the combination Figures 1 to 5 of the described controller installation verification method and device.

[0111] In addition, the embodiments of the present application also provide a computer program product, including computer program instructions, and the computer program product can realize the steps and corresponding contents of the foregoing method embodiments when executed by the processor 601.

[0112] It needs to be clear that the present application is not limited to the specific configurations and processes described above and shown in the drawings. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps, after understanding the spirit of the present application.

[0113] The functional blocks shown in the structural block diagrams described above can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application specific integrated circuits (ASICs), appropriate firmware, plug-ins, functional cards, and the like. When implemented in software, the elements of the present application are program or code segments that are used to perform the required tasks. The program or code segments can be stored in a machine-readable medium or transmitted through a data signal carried in a carrier wave over a transmission medium or communication link. The "machine-readable medium" can include any medium that can store or transfer information. Examples of the machine-readable medium include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, and the like. The code segments can be downloaded via a computer network such as the Internet, an intranet, and the like.

[0114] It is also necessary to note that the exemplary embodiments mentioned in the present application describe some methods or systems based on a series of steps or devices. However, the present application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiments, or in an order different from the embodiments, or several steps can be performed simultaneously.

[0115] The above describes aspects of the present disclosure with reference to flowcharts and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer, a special-purpose computer, or other programmable controller installation verification device processor to produce a machine, so that the instructions executed by the computer or other programmable controller installation verification device processor enable the implementation of the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It can also be understood that each block of the block diagram and / or flowchart, and the combination of blocks in the block diagram and / or flowchart, can also be implemented by special hardware that performs the specified functions or acts, or can be implemented by a combination of special hardware and computer instructions.

[0116] Based on the same inventive concept, the present application also provides a vehicle comprising the controller installation verification device 500 or the controller installation verification apparatus described above.

[0117] The above merely describes a specific implementation of the present application. Those skilled in the art can clearly understand the specific working processes of the system, modules and units described above for the convenience and brevity of description, and can refer to the corresponding processes in the foregoing method embodiments, which will not be described herein again. It should be understood that the protection scope of the present application is not limited to this, and any person skilled in the art can easily think of various equivalent modifications or replacements within the technical range disclosed by the present application, and these modifications or replacements should be covered within the protection scope of the present application.

Claims

1. A method for inspecting controller installation, characterized in that, include: Obtain first identification information and first software version information of the target controller in the vehicle, wherein the first identification information is used to identify the manufacturer of the target controller; The first identification information and the first software version information are matched with the baseline description file of the vehicle to obtain a matching result, wherein the matching result is used to indicate whether the first identification information and the first software version information exist in the baseline description file; the baseline description file includes multiple sets of mapping relationships, each mapping relationship including preset identification information and preset software version information; If the matching result shows that both the first identification information and the first software version information exist in the baseline description file, then the target controller is confirmed to be installed correctly. The step of matching the first identification information, the first software version information, and the baseline description file of the vehicle to obtain a matching result includes: The first identification information is matched with the preset identification information in the baseline description file to obtain the identification information matching result. The identification information matching result is used to indicate whether there is preset identification information in the baseline description file that matches the first identification information. If the identification information matching result indicates that there is preset identification information in the baseline description file that matches the first identification information, the first software version information is matched with the preset software version information in the baseline description file to obtain the matching result.

2. The controller installation inspection method as described in claim 1, characterized in that, Before acquiring the first identification information and first software version information of the target controller in the vehicle, wherein the first identification information is used to identify the manufacturer of the target controller, the method includes: Receive an update request sent by the controller manufacturer, the update request carrying second version information and second identification information; In response to the update request, the second version information and the second identification information are configured into the baseline description file.

3. The controller installation inspection method as described in claim 1, characterized in that, If the matching result indicates that both the first identification information and the first software version information exist in the baseline description file, then the target controller is confirmed to be installed correctly, including: If the matching result shows that both the first identification information and the first software version information exist in the baseline description file, and there is a mapping relationship between the first identification information and the first software version information, then the target controller is confirmed to be installed correctly.

4. The controller installation inspection method as described in claim 3, characterized in that, If a preset identifier that matches the first identifier exists in the baseline description file, the matching result is used to indicate that the first identifier and the first software version information exist in the baseline description file. If no preset identifier information matching the first identifier information exists in the baseline description file, the matching result is used to indicate that the first identifier information and the first software version information do not exist in the baseline description file.

5. The controller installation inspection method as described in claim 1, characterized in that, The first identification information is a unique identification information generated by the controller manufacturer.

6. A controller installation inspection device, characterized in that, include: The acquisition module is used to acquire first identification information and first software version information of the target controller in the vehicle, wherein the first identification information is used to identify the manufacturer of the target controller. The matching module is used to sequentially match the first identification information and the first software version information with the baseline description file of the vehicle to obtain a matching result. The matching result is used to indicate whether the first identification information and the first software version information exist in the baseline description file. The baseline description file includes multiple sets of mapping relationships, and each mapping relationship includes preset identification information and preset software version information. The confirmation module, if the matching result shows that both the first identification information and the first software version information exist in the baseline description file, is used to confirm that the target controller is installed correctly; The matching module is specifically used for: The first identification information is matched with the preset identification information in the baseline description file to obtain the identification information matching result. The identification information matching result is used to indicate whether there is preset identification information in the baseline description file that matches the first identification information. If the identification information matching result indicates that there is preset identification information in the baseline description file that matches the first identification information, the first software version information is matched with the preset software version information in the baseline description file to obtain the matching result.

7. A controller installation inspection device, characterized in that, The device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the controller installation verification method as described in any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the controller installation verification method as described in any one of claims 1-5.

9. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device performs the controller installation verification method as described in any one of claims 1-5.

10. A vehicle, characterized in that, The vehicle includes the controller installation inspection device as described in claim 6 or the controller installation inspection equipment as described in claim 7.

Images