Vehicle quality inspection method and device, vehicle, medium and program product

Abstract

The invention provides a vehicle quality inspection method and device, a vehicle, a medium and a program product. The method is applied to a central control domain controller of a vehicle, and the central control domain controller comprises a first data distribution service DDS interface corresponding to a to-be-tested vehicle-mounted device; the method comprises the following steps: acquiring a quality inspection item of to-be-tested vehicle-mounted equipment; determining a first DDS interface corresponding to the to-be-tested vehicle-mounted equipment from a first mapping relation, and establishing connection with the first DDS interface; the first mapping relation is used for representing a corresponding relation between the to-be-tested vehicle-mounted equipment and the DDS interface; sending a first instruction to the vehicle-mounted equipment to be tested through the first DDS interface; the first instruction is a quality inspection instruction obtained based on the quality inspection item; receiving feedback information of the first instruction sent by the to-be-tested vehicle-mounted equipment through the first DDS interface; and determining a quality inspection result of the to-be-tested vehicle-mounted equipment at least based on feedback information of the first instruction.

Description

Technical Field

[0001] This application relates to the field of automation, and particularly to a vehicle quality inspection method and device, a vehicle, a medium, and a program product. Background Art

[0002] Before the vehicle is assembled and rolled off the production line, generally, quality inspectors need to conduct a random inspection of the vehicle's functions to confirm whether the functions of commonly used vehicle parts are working properly, such as lights, windows, zero-gravity seats, air conditioners, tire pressure, etc. However, due to physiological limitations, the operation speed during manual inspection is limited; and it depends on manually triggering function switches to execute and detect sequentially; and in case of problems, manual recording is required, and the test results also need to be manually recorded. Therefore, it is impossible to track the vehicle inspection situation in a timely manner, and the inspection efficiency is low. Summary of the Invention

[0003] This application provides a vehicle quality inspection method and device, a vehicle, a medium, and a program product, and this method is beneficial to improving the efficiency of vehicle quality inspection.

[0004] In a first aspect, an embodiment of this application provides a vehicle quality inspection method. The method is applied to a central control domain controller of a vehicle. The central control domain controller includes: a first Data Distribution Service (DDS) interface corresponding to a to-be-tested in-vehicle device. The method includes: obtaining a quality inspection item of the to-be-tested in-vehicle device; determining the first DDS interface corresponding to the to-be-tested in-vehicle device from a first mapping relationship, and establishing a connection with the first DDS interface; the first mapping relationship is used to represent the corresponding relationship between the to-be-tested in-vehicle device and the DDS interface; sending a first instruction to the to-be-tested in-vehicle device through the first DDS interface; the first instruction is a quality inspection instruction obtained based on the quality inspection item; receiving feedback information of the first instruction sent by the to-be-tested in-vehicle device through the first DDS interface; determining the quality inspection result of the to-be-tested in-vehicle device at least based on the feedback information of the first instruction.

[0005] It can be understood that in the vehicle quality inspection method provided by the embodiment of this application, the DDS interface is used as the communication channel between the central control domain controller and the to-be-tested in-vehicle device, so as to send a quality inspection instruction from the central control domain controller to the to-be-tested in-vehicle device through the DDS interface, and enable the central control domain controller to receive the feedback information of the quality inspection instruction returned by the to-be-tested in-vehicle device through the DDS interface, so that the central control domain controller determines whether the quality inspection of the to-be-tested in-vehicle device is successful. That is to say, an automated test of the to-be-tested in-vehicle device based on the central control domain controller is realized, thereby improving the efficiency of vehicle quality inspection.

[0006] In some embodiments, sending the first instruction to the in-vehicle device under test through the first DDS interface includes: when the quality inspection item is to inspect the current state of the in-vehicle device under test, sending the first instruction to the in-vehicle device under test through the first DDS interface; the first instruction is used to instruct to detect the first state of the in-vehicle device under test; the first state is the current state of the in-vehicle device under test; correspondingly, determining the quality inspection result of the in-vehicle device under test based on at least the feedback information of the first instruction includes: when the first state included in the feedback information of the first instruction is consistent with the preset state, determining that the quality inspection of the in-vehicle device under test is successful.

[0007] It can be understood that in the vehicle quality inspection method provided in the embodiments of the present application, the central control domain controller sends the first instruction for detecting the current state of the in-vehicle device under test to the in-vehicle device under test through the first DDS interface corresponding to the in-vehicle device under test, and the central control domain controller receives the feedback information of the first instruction returned by the in-vehicle device under test through the first DDS interface, so that the central control domain controller compares the first state included in the feedback information of the first instruction with the preset state, and when the first state is consistent with the preset state, determines that the quality inspection of the in-vehicle device under test is successful. That is to say, the automated test of the state of the in-vehicle device under test based on the central control domain controller is realized, thereby improving the efficiency of vehicle quality inspection.

[0008] In some embodiments, sending the first instruction to the in-vehicle device under test through the first DDS interface includes: when the quality inspection item is to inspect the function of the in-vehicle device under test, sending the first instruction to the in-vehicle device under test through the first DDS interface; the first instruction is used to instruct to detect the first state of the in-vehicle device under test; the first state is the current state of the in-vehicle device under test; correspondingly, determining the quality inspection result of the in-vehicle device under test based on at least the feedback information of the first instruction sent by the in-vehicle device under test through the first DDS interface includes: generating a second instruction based on the function of the in-vehicle device under test and the first state; the second instruction is used to instruct to set the state of the in-vehicle device under test to a second state; the second state is different from the first state; sending the second instruction to the in-vehicle device under test through the first DDS interface based on the first communication mode; receiving the feedback information of the second instruction sent by the in-vehicle device under test through the first DDS interface; when the second state is included in the feedback information of the second instruction, determining that the quality inspection of the in-vehicle device under test is successful.

[0009] It can be understood that in the vehicle quality inspection method provided in the embodiments of the present application, the central control domain controller sends a first instruction for detecting the function of the to-be-tested vehicle-mounted device to the to-be-tested vehicle-mounted device through the first DDS interface corresponding to the to-be-tested vehicle-mounted device, and through the first DDS interface, the central control domain controller receives the feedback information of the first instruction returned by the to-be-tested vehicle-mounted device, so that the central control domain controller generates a second instruction based on the feedback information of the first instruction and the function of the to-be-tested vehicle-mounted device; and sends the second instruction to the to-be-tested vehicle-mounted device through the first DDS interface; and receives the feedback information of the second instruction sent by the to-be-tested vehicle-mounted device through the first DDS interface; in the case of the second state included in the feedback information of the second instruction, it is determined that the quality inspection of the to-be-tested vehicle-mounted device is successful. That is to say, the automated test of the function of the to-be-tested vehicle-mounted device based on the central control domain controller is realized, thereby improving the efficiency of vehicle quality inspection.

[0010] In some embodiments, the method further includes: in the case of successful quality inspection, sending a third instruction to the to-be-tested vehicle-mounted device through the first DDS interface; the third instruction is used to instruct to set the state of the to-be-tested vehicle-mounted device back to the first state; receiving the feedback information of the third instruction sent by the to-be-tested vehicle-mounted device through the first DDS interface; in the case where the third state included in the feedback information of the third instruction is consistent with the first state, ending the current quality inspection item.

[0011] It can be understood that in the vehicle quality inspection method provided in the embodiments of the present application, after restoring the state of the to-be-tested vehicle-mounted device in the case of successful quality inspection, the current quality inspection item is ended. In this way, it is beneficial to ensure the consistency before and after vehicle quality inspection and avoid introducing new problems due to vehicle quality inspection.

[0012] In some embodiments, determining the first DDS interface corresponding to the to-be-tested vehicle-mounted device from the first mapping relationship includes: in the case of determining that the vehicle meets the first condition, determining the first DDS interface corresponding to the to-be-tested vehicle-mounted device from the first mapping relationship; wherein, the first condition includes one or more of the following: the vehicle is in a stationary state; the vehicle is in a powered-on state; the electronic control unit of the to-be-tested vehicle-mounted device is in a wake-up state; the power or fuel quantity of the vehicle is greater than or equal to a quantity threshold.

[0013] It can be understood that in the vehicle quality inspection method provided by the embodiments of the present application, considering that some quality inspection items require the vehicle to be in a stationary state, otherwise the corresponding quality inspection items cannot be implemented; and since some functions of the vehicle require the vehicle to be powered on to be used, therefore, to ensure that the vehicle is in a powered-on state, the corresponding quality inspection items can be implemented; since some functions of the vehicle require the participation of the electronic control unit, therefore, to ensure that the electronic control unit of the vehicle-mounted device to be tested is in a wake-up state, the corresponding quality inspection items can be implemented; and since quality inspection requires the power or fuel level of the vehicle to meet the quantity threshold, otherwise the quality inspection items may fail due to insufficient power or fuel. Therefore, setting the first condition as the vehicle being in a stationary state, the vehicle being in a powered-on state, the electronic control unit of the vehicle-mounted device to be tested being in a wake-up state, and the power or fuel level of the vehicle being greater than or equal to the quantity threshold is beneficial to improving the success rate of vehicle quality inspection.

[0014] In some embodiments, the method further includes: when receiving a stop quality inspection signal, determining the current quality inspection state; when the current quality inspection state is that there is a quality inspection item being executed, stopping the quality inspection after the quality inspection item is completed.

[0015] It can be understood that in the vehicle quality inspection method provided by the embodiments of the present application, when receiving a stop quality inspection signal, if there is a quality inspection item being executed currently, the quality inspection will be stopped after the quality inspection item is completed. In this way, compared with forcibly stopping the quality inspection item being executed, it is beneficial to avoid the problem of data loss during storage and the problem of vehicle damage.

[0016] In a second aspect, an embodiment of the present application provides a vehicle quality inspection method, which is applied to a domain controller of a vehicle. The domain controller includes: a vehicle-mounted device to be tested and its corresponding second DDS interface; the method includes: receiving a connection request sent by a first DDS interface in a central control domain controller through the second DDS interface, and establishing a connection between the second DDS interface and the first DDS interface; receiving a first instruction sent by the first DDS interface to the vehicle-mounted device to be tested through the second DDS interface; the first instruction is a quality inspection instruction obtained by the central control domain controller based on the quality inspection items of the vehicle-mounted device to be tested; sending feedback information of the vehicle-mounted device to be tested on the first instruction to the first DDS interface through the second DDS interface, so that the central control domain controller determines the quality inspection result of the vehicle-mounted device to be tested at least based on the feedback information of the first instruction.

[0017] It can be understood that in the vehicle quality inspection method provided in the embodiments of the present application, the second DDS interface is used as the communication channel between the central control domain controller and the vehicle-mounted device to be tested. Thus, through the second DDS interface, the vehicle-mounted device to be tested can receive the quality inspection instructions sent by the central control domain controller, and through the second DDS interface, the vehicle-mounted device to be tested can send the feedback information of the quality inspection instructions to the central control domain controller. In this way, the central control domain controller determines whether the quality inspection of the vehicle-mounted device to be tested is successful based on the feedback information of the quality inspection instructions. That is to say, the automatic test of the vehicle-mounted device to be tested based on the central control domain controller is realized, thereby improving the efficiency of vehicle quality inspection.

[0018] In some embodiments, receiving, by the second DDS interface, the first instruction sent by the first DDS interface to the vehicle-mounted device to be tested includes: receiving, by the second DDS interface, the first instruction sent by the first DDS interface to the vehicle-mounted device to be tested; the first instruction is used to indicate detecting a first state of the vehicle-mounted device to be tested; the first state is the current state of the vehicle-mounted device to be tested; the quality inspection item is to quality inspect the current state of the vehicle-mounted device to be tested; correspondingly, sending, by the second DDS interface, the feedback information of the vehicle-mounted device to be tested on the first instruction to the first DDS interface, so that the central control domain controller determines the quality inspection result of the vehicle-mounted device to be tested based at least on the feedback information of the first instruction, includes: sending, by the second DDS interface, the feedback information of the vehicle-mounted device to be tested on the first instruction to the first DDS interface; the feedback information of the first instruction includes the first state; so that when the central control domain controller determines that the first state included in the feedback information of the first instruction is consistent with the preset state, it determines that the quality inspection of the vehicle-mounted device to be tested is successful.

[0019] It can be understood that in the vehicle quality inspection method provided in the embodiments of the present application, through the second DDS interface, the vehicle-mounted device to be tested can receive the first instruction for detecting the current state of the vehicle-mounted device sent by the central control domain controller, and through the second DDS interface, the vehicle-mounted device to be tested can send the feedback information of the first instruction to the central control domain controller. In this way, when the first state included in the feedback information of the first instruction is consistent with the preset state, the central control domain controller determines whether the quality inspection of the vehicle-mounted device to be tested is successful. That is to say, the automatic test of the state of the vehicle-mounted device to be tested based on the central control domain controller is realized, thereby improving the efficiency of vehicle quality inspection.

[0020] In some embodiments, receiving, via the second DDS interface, a first instruction sent by the first DDS interface to the in-vehicle device under test includes: receiving, via the second DDS interface, the first instruction sent by the first DDS interface to the in-vehicle device under test; the first instruction is used to indicate detecting a first state of the in-vehicle device under test; the first state is the current state of the in-vehicle device under test; the quality inspection item is to inspect the functions of the in-vehicle device under test; correspondingly, sending, via the second DDS interface, feedback information of the in-vehicle device under test on the first instruction to the first DDS interface, so that the central control domain controller determines the quality inspection result of the in-vehicle device under test based at least on the feedback information of the first instruction, includes: sending, via the second DDS interface, the feedback information of the in-vehicle device under test on the first instruction to the first DDS interface; the feedback information of the first instruction includes the first state; receiving, via the second DDS interface, a second instruction sent by the first DDS interface to the in-vehicle device under test; the second instruction is used to indicate setting the state of the in-vehicle device under test to a second state; the second state is different from the first state; the second instruction is generated by the central control domain controller based on the functions of the in-vehicle device under test and the first state; sending, via the second DDS interface, the feedback information of the in-vehicle device under test on the second instruction to the first DDS interface; so that the central control domain controller determines that the quality inspection of the in-vehicle device under test is successful when it is determined that the feedback information of the second instruction includes the first state.

[0021] It can be understood that in the vehicle quality inspection method provided in the embodiments of the present application, through the second DDS interface, the in-vehicle device under test can receive the first instruction sent by the central control domain controller to detect the current state of the in-vehicle device under test, and through the second DDS interface, the in-vehicle device under test can send the feedback information of the first instruction to the central control domain controller, so that the central control domain controller generates a second instruction based on the feedback information of the first instruction and the functions of the in-vehicle device under test; and receives, via the second DDS interface, the second instruction sent to the in-vehicle device under test; and sends, via the second DDS interface, the feedback information of the second instruction to the central control domain controller; so that the central control domain controller determines that the quality inspection of the in-vehicle device under test is successful when it is determined that the feedback information of the second instruction includes the second state. That is to say, the automated test of the functions of the in-vehicle device under test based on the central control domain controller is realized, thereby improving the efficiency of vehicle quality inspection.

[0022] In some embodiments, the method further includes: receiving, through a second DDS interface, a third instruction sent by the first DDS interface to the in-vehicle device under test; the third instruction is used to instruct to set the state of the in-vehicle device under test back to the first state; the third instruction is sent by the central control domain controller when determining that the quality inspection is successful; sending, through the second DDS interface, feedback information of the in-vehicle device under test on the third instruction to the first DDS interface; the feedback information of the third instruction includes a third state; so that the central control domain controller ends the current quality inspection item when determining that the third state included in the feedback information of the third instruction is consistent with the first state.

[0023] It can be understood that in the vehicle quality inspection method provided in the embodiments of the present application, when the quality inspection is successful, a third instruction for setting the state of the in-vehicle device under test back to the first state sent by the central control domain controller is received through the second DDS interface, and the feedback information of the third instruction is sent to the in-vehicle device under test through the second DDS interface; in this way, the central control domain controller ends the current quality inspection item only after determining that the state of the in-vehicle device under test is restored. In this way, it is beneficial to ensure the consistency before and after the vehicle quality inspection and avoid introducing new problems due to the vehicle quality inspection.

[0024] In a third aspect, an embodiment of the present application provides a vehicle quality inspection device, the device includes: an acquisition module configured to acquire a quality inspection item of an in-vehicle device under test; a first determination module configured to determine, from a first mapping relationship, a first DDS interface corresponding to the in-vehicle device under test; the first mapping relationship is used to represent the corresponding relationship between the in-vehicle device under test and the DDS interface; a first connection module configured to establish a connection with the first DDS interface; a first sending module configured to send a first instruction to the in-vehicle device under test through the first DDS interface; the first instruction is a quality inspection instruction obtained based on the quality inspection item; a first receiving module configured to receive feedback information of the first instruction sent by the in-vehicle device under test through the first DDS interface; a second determination module configured to determine the quality inspection result of the in-vehicle device under test at least based on the feedback information of the first instruction.

[0025] Fourth aspect, an embodiment of the present application provides a vehicle quality inspection device, and the device includes: a second receiving module configured to receive a connection request sent by a first DDS interface in a central control domain controller through a second DDS interface; a second connection module configured to establish a connection between the second DDS interface and the first DDS interface; the second receiving module configured to receive a first instruction sent by the first DDS interface to a vehicle-mounted device to be tested through the second DDS interface; the first instruction is a quality inspection instruction obtained by the central control domain controller based on quality inspection items of the vehicle-mounted device to be tested; a second sending module configured to send feedback information of the vehicle-mounted device to be tested on the first instruction to the first DDS interface through the second DDS interface, so that the central control domain controller determines a quality inspection result of the vehicle-mounted device to be tested at least based on the feedback information of the first instruction.

[0026] Fifth aspect, an embodiment of the present application provides a vehicle, including a central control domain controller and at least one domain controller. The central control domain controller is used to implement the method described in the first aspect; the domain controller is used to implement the method described in the second aspect.

[0027] Sixth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed, it implements the method described in the first aspect; or when the computer program is executed, it implements the method described in the second aspect.

[0028] Seventh aspect, an embodiment of the present application provides a computer program product, including a computer program or instruction. When the computer program or instruction is executed, it implements the method described in the first aspect; or when the computer program or instruction is executed, it implements the method described in the second aspect. Description of the Drawings

[0029] Figure 1 Schematic implementation process of a vehicle quality inspection method provided by an embodiment of the present application Figure 1 ; Figure 2 Schematic implementation process of a vehicle quality inspection method provided by an embodiment of the present application Figure 2 ; Figure 3 Schematic implementation process of a vehicle quality inspection method provided by an embodiment of the present application Figure 3 ; Figure 4 Schematic implementation process of a vehicle quality inspection method provided by an embodiment of the present application Figure 4 ; Figure 5 Schematic implementation process of a vehicle quality inspection method provided by an embodiment of the present application Figure 5 ; Figure 6 Schematic diagram of the implementation process of a vehicle quality inspection method provided by an embodiment of the present application Figure 6 ; Figure 7 Schematic diagram of a vehicle quality inspection system provided by an embodiment of the present application; Figure 8 Schematic diagram of the implementation process of a vehicle quality inspection method provided by an embodiment of the present application Figure 7 ; Figure 9 Schematic diagram of a vehicle quality inspection device provided by an embodiment of the present application Figure 1 ; Figure 10 Schematic diagram of a vehicle quality inspection device provided by an embodiment of the present application Figure 2 . Detailed implementation manners

[0030] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application.

[0031] In order to make the purpose, technical solutions, and advantages of the present application clearer, the present application will be further described in conjunction with the accompanying drawings. The described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Therefore, the described embodiments should not be regarded as a limitation of the present application. All other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of the present application.

[0032] In the following description, "some embodiments / other embodiments" are involved, which describe a subset of all possible embodiments. However, it can be understood that "some embodiments / other embodiments" can be the same subset or different subsets of all possible embodiments, and can be combined with each other without conflict.

[0033] In the following description, the terms "first / second" only distinguish similar objects and do not represent a specific order for the objects. It can be understood that "first / second" can be interchanged with a specific order or sequence when allowed, so that the embodiments of the present application described here can be implemented in an order other than that illustrated or described here.

[0034] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those of ordinary skill in the technical field to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.

[0035] In an embodiment of the present application, a vehicle quality inspection method is provided. The method is applied to the central control domain controller of a vehicle. The central control domain controller includes: a first DDS interface corresponding to a vehicle-mounted device to be tested; Figure 1 Schematic implementation process of a vehicle quality inspection method provided by an embodiment of the present application Figure 1 , as Figure 1 shown, the method includes steps 101 to 105: Step 101, obtain the quality inspection items of the vehicle-mounted device to be tested; Step 102, determine the first DDS interface corresponding to the vehicle-mounted device to be tested from the first mapping relationship, and establish a connection with the first DDS interface; the first mapping relationship is used to represent the corresponding relationship between the vehicle-mounted device to be tested and the DDS interface; Step 103, send a first instruction to the vehicle-mounted device to be tested through the first DDS interface; the first instruction is a quality inspection instruction obtained based on the quality inspection items; Step 104, receive the feedback information of the first instruction sent by the vehicle-mounted device to be tested through the first DDS interface; Step 105, determine the quality inspection result of the vehicle-mounted device to be tested based at least on the feedback information of the first instruction.

[0036] It can be understood that in the vehicle quality inspection method provided by the embodiment of the present application, the DDS interface is used as the communication channel between the central control domain controller and the vehicle-mounted device to be tested, so as to send a quality inspection instruction from the central control domain controller to the vehicle-mounted device to be tested through the DDS interface, and enable the central control domain controller to receive the feedback information of the quality inspection instruction returned by the vehicle-mounted device to be tested through the DDS interface, so that the central control domain controller determines whether the quality inspection of the vehicle-mounted device to be tested is successful. That is to say, the automated test of the vehicle-mounted device to be tested is realized based on the central control domain controller, thereby improving the efficiency of vehicle quality inspection.

[0037] The following further optional implementation manners of the above respective steps and related terms, etc. will be described separately.

[0038] In step 101, obtain the quality inspection items of the vehicle-mounted device to be tested.

[0039] It should be understood that in the embodiment of the present application, the specific implementation manner of obtaining the quality inspection items of the vehicle-mounted device to be tested is not limited. In some embodiments, obtaining the quality inspection items of the vehicle-mounted device to be tested includes: receiving the quality inspection items of the vehicle-mounted device to be tested from the display in the central control domain controller. In other embodiments, obtaining the quality inspection items of the vehicle-mounted device to be tested includes: receiving the quality inspection items of the vehicle-mounted device to be tested sent by a cloud device. In still other embodiments, obtain the quality inspection items of the vehicle-mounted device to be tested from the memory in the central control domain controller.

[0040] In the embodiments of the present application, the quality inspection items are not limited. The quality inspection items refer to the specific items or indicators that need to be inspected and tested for the whole vehicle or parts. In some embodiments, the quality inspection items include: inspecting the current state of the in-vehicle device to be tested. In other embodiments, the quality inspection items include: inspecting the functions of the in-vehicle device to be tested.

[0041] It should be understood that in the embodiments of the present application, the in-vehicle device to be tested is not limited. In some embodiments, the in-vehicle device to be tested includes but is not limited to at least one of the following: lights, windows, seats, air conditioners, tires, cameras, windshield wipers, batteries, etc.

[0042] In some embodiments, obtaining the quality inspection items of the in-vehicle device to be tested includes: when the vehicle assembly is completed, obtaining the quality inspection items of the in-vehicle device to be tested.

[0043] In step 102, determine the first DDS interface corresponding to the in-vehicle device to be tested from the first mapping relationship, and establish a connection with the first DDS interface; the first mapping relationship is used to represent the corresponding relationship between the in-vehicle device to be tested and the DDS interface.

[0044] It should be understood that in the embodiments of the present application, the first mapping relationship is not limited; based on the first mapping relationship, the DDS interface corresponding to the in-vehicle device to be tested can be determined. In some embodiments, the first mapping relationship represents the corresponding relationship between the in-vehicle device to be tested and the DDS interface in the form of a mapping table.

[0045] In some embodiments, determining the first DDS interface corresponding to the in-vehicle device to be tested from the first mapping relationship includes: when it is determined that the vehicle meets the first condition, determining the first DDS interface corresponding to the in-vehicle device to be tested from the first mapping relationship; where the first condition includes one or more of the following: the vehicle is in a stationary state; the vehicle is in a powered-on state; the electronic control unit of the in-vehicle device to be tested is in a wake-up state; the power or fuel level of the vehicle is greater than or equal to a quantity threshold.

[0046] It can be understood that in the vehicle quality inspection method provided by the embodiments of the present application, considering that some quality inspection items require the vehicle to be in a static state, otherwise the corresponding quality inspection items cannot be realized; and since some functions of the vehicle need to be powered on to be used, it is necessary to ensure that the vehicle is in a powered-on state to realize the corresponding quality inspection items; since some functions of the vehicle require the participation of the electronic control unit, it is necessary to ensure that the electronic control unit of the vehicle-mounted device to be tested is in a wake-up state to realize the corresponding quality inspection items; and since quality inspection requires the power or fuel quantity of the vehicle to meet the quantity threshold, otherwise the quality inspection item may fail due to insufficient power or fuel. Therefore, setting the first condition as the vehicle being in a static state, the vehicle being in a powered-on state, the electronic control unit (ECU) of the vehicle-mounted device to be tested being in a wake-up state, and the power or fuel quantity of the vehicle being greater than or equal to the quantity threshold is beneficial to improving the success rate of vehicle quality inspection.

[0047] It should be understood that in the embodiments of the present application, the static state is not limited. The static state generally refers to the state where the vehicle completely stops and does not move. In some embodiments, the static state includes but is not limited to at least one of the following: the vehicle does not have displacement; the engine of the vehicle is turned off; most of the electrical systems of the vehicle are turned off; the engine of the vehicle stops running; the headlights and other power-consuming devices of the vehicle are turned off, etc.

[0048] In the embodiments of the present application, the quantity threshold is not limited. The quantity threshold is greater than or equal to the quantity of power or fuel required to complete the quality inspection item. In some embodiments, the quantity threshold is a preset quantity threshold. In other embodiments, the quantity threshold is determined based on the quality inspection item.

[0049] Exemplarily, in a possible implementation manner, if the quality inspection item is to detect the air quality inside the vehicle, then the vehicle needs to be in a static state. If the detection item is to detect the charging temperature of the power battery, then the vehicle needs to be in a powered-on state. If the quality inspection item is to detect the sending and receiving of network management messages, etc., then the ECU needs to be in a wake-up state. If the quality inspection item is to detect the speed change of the vehicle, then the power or fuel quantity of the vehicle needs to be greater than or equal to the quantity threshold.

[0050] In step 103, a first instruction is sent to the vehicle-mounted device to be tested through the first DDS interface; the first instruction is a quality inspection instruction obtained based on the quality inspection item.

[0051] In some embodiments, sending a first instruction to the on-vehicle device under test through the first DDS interface includes: when the quality inspection item is to inspect the current state of the on-vehicle device under test, sending a first instruction to the on-vehicle device under test through the first DDS interface; the first instruction is used to instruct to detect a first state of the on-vehicle device under test; the first state is the current state of the on-vehicle device under test.

[0052] In some other embodiments, sending a first instruction to the on-vehicle device under test through the first DDS interface includes: when the quality inspection item is to inspect the function of the on-vehicle device under test, sending a first instruction to the on-vehicle device under test through the first DDS interface; the first instruction is used to instruct to detect a first state of the on-vehicle device under test; the first state is the current state of the on-vehicle device under test.

[0053] In step 104, receive the feedback information of the first instruction sent by the on-vehicle device under test through the first DDS interface.

[0054] It should be understood that in the embodiments of the present application, the feedback information of the first instruction is not limited, and the feedback information of the first instruction is used to characterize the execution result of the on-vehicle device under test for the first instruction. In some embodiments, different first instructions result in different feedback information of the first instruction.

[0055] In some embodiments, receiving the feedback information of the first instruction sent by the on-vehicle device under test through the first DDS interface includes: when the quality inspection item is to inspect the current state of the on-vehicle device under test, the feedback information of the first instruction includes the first state.

[0056] In some other embodiments, receiving the feedback information of the first instruction sent by the on-vehicle device under test through the first DDS interface includes: when the quality inspection item is to inspect the function of the on-vehicle device under test, the feedback information of the first instruction includes the first state.

[0057] Exemplarily, in a possible implementation, if the first instruction is to detect the tire pressure, then the feedback information of the first instruction includes: the tire pressure.

[0058] In step 105, determine the quality inspection result of the on-vehicle device under test based at least on the feedback information of the first instruction.

[0059] In some embodiments, sending the first instruction to the in-vehicle device under test through the first DDS interface includes: when the quality inspection item is to inspect the current state of the in-vehicle device under test, sending the first instruction to the in-vehicle device under test through the first DDS interface; the first instruction is used to instruct to detect the first state of the in-vehicle device under test; the first state is the current state of the in-vehicle device under test; correspondingly, determining the quality inspection result of the in-vehicle device under test based on at least the feedback information of the first instruction includes: when the first state included in the feedback information of the first instruction is consistent with the preset state, determining that the quality inspection of the in-vehicle device under test is successful.

[0060] It can be understood that in the vehicle quality inspection method provided in the embodiments of the present application, the central control domain controller sends a first instruction for detecting the current state of the in-vehicle device under test to the in-vehicle device under test through the first DDS interface corresponding to the in-vehicle device under test, and the central control domain controller receives the feedback information of the first instruction returned by the in-vehicle device under test through the first DDS interface, so that the central control domain controller compares the first state included in the feedback information of the first instruction with the preset state, and when the first state is consistent with the preset state, determines that the quality inspection of the in-vehicle device under test is successful. That is to say, an automated test of the state of the in-vehicle device under test based on the central control domain controller is realized, thereby improving the efficiency of vehicle quality inspection.

[0061] In some embodiments, sending the first instruction to the in-vehicle device under test through the first DDS interface includes: based on the second communication mode, sending the first instruction to the in-vehicle device under test through the first DDS interface.

[0062] It should be understood that in the embodiments of the present application, the second communication mode is not limited. In some embodiments, the second communication mode is a Remote Procedure Call Protocol (RPC) interface; the characteristic of the RPC interface is that it blocks and waits for the return result after the call; the RPC interface is suitable for calls that require immediate results.

[0063] Exemplarily, in one possible implementation Figure 2 is a schematic implementation process of a vehicle quality inspection method provided in the embodiments of the present application Figure 2 , as Figure 2 shown, for the quality inspection of the state of the in-vehicle device under test, it can be implemented through the following steps 201 to 206.

[0064] Step 201, initiate a DDS connection request.

[0065] Among them, the quality inspection software deployed on the central control domain controller initiates a connection to the DDS service (an example of a DDS interface) to which the component to be tested (an example of an in-vehicle device to be tested) belongs.

[0066] Step 202, determine whether the connection is successful; if so, execute step 203, otherwise execute step 205.

[0067] Step 203, obtain the component status through the RPC interface.

[0068] Among them, the quality inspection software deployed on the central control domain controller obtains the status of the component to be tested through the RPC interface to determine whether the status of the component to be tested meets the standard; the RPC interface is a blocking software interface, which waits for the interface return value all the time after the software calls the communication interface until the interface returns and then continues to execute the next step.

[0069] Step 204, whether it meets the expected status; if so, execute step 206; otherwise execute step 205.

[0070] Step 205, quality inspection fails.

[0071] In some embodiments, when the quality inspection fails, the quality inspection result is also recorded, and the DDS connection is released.

[0072] Step 206, quality inspection succeeds.

[0073] In some embodiments, when the quality inspection succeeds, the quality inspection result is also recorded, and the DDS connection is released.

[0074] In some other embodiments, sending the first instruction to the in-vehicle device to be tested through the first DDS interface includes: when the quality inspection item is to inspect the function of the in-vehicle device to be tested, sending the first instruction to the in-vehicle device to be tested through the first DDS interface; the first instruction is used to instruct to detect the first state of the in-vehicle device to be tested; the first state is the current state of the in-vehicle device to be tested; correspondingly, determining the quality inspection result of the in-vehicle device to be tested based at least on the feedback information of the first instruction sent by the in-vehicle device to be tested through the first DDS interface includes: generating a second instruction based on the function of the in-vehicle device to be tested and the first state; the second instruction is used to instruct to set the state of the in-vehicle device to be tested to a second state; the second state is different from the first state; sending the second instruction to the in-vehicle device to be tested through the first DDS interface based on the first communication mode; receiving the feedback information of the second instruction sent by the in-vehicle device to be tested through the first DDS interface; when the feedback information of the second instruction includes the second state, determining that the quality inspection of the in-vehicle device to be tested is successful.

[0075] It can be understood that in the vehicle quality inspection method provided in the embodiments of the present application, the central control domain controller sends a first instruction for detecting the function of the vehicle-mounted device to be tested through the first DDS interface corresponding to the vehicle-mounted device to be tested, and the central control domain controller receives the feedback information of the first instruction returned by the vehicle-mounted device to be tested through the first DDS interface, so that the central control domain controller generates a second instruction based on the feedback information of the first instruction and the function of the vehicle-mounted device to be tested; and sends the second instruction to the vehicle-mounted device to be tested through the first DDS interface; and receives the feedback information of the second instruction sent by the vehicle-mounted device to be tested through the first DDS interface; in the case of the second state included in the feedback information of the second instruction, it is determined that the quality inspection of the vehicle-mounted device to be tested is successful. That is to say, the automatic test of the function of the vehicle-mounted device to be tested based on the central control domain controller is realized, thereby improving the efficiency of vehicle quality inspection.

[0076] In some embodiments, sending the first instruction to the vehicle-mounted device to be tested through the first DDS interface includes: sending the first instruction to the vehicle-mounted device to be tested through the first DDS interface based on the second communication mode.

[0077] It should be understood that in the embodiments of the present application, the second communication mode is not limited. In some embodiments, the second communication mode is an RPC interface; among them, the characteristic of the RPC interface is to block and wait for the return result after the call; the RPC interface is suitable for calls that require immediate result acquisition.

[0078] In the embodiments of the present application, the first communication mode is not limited. In some embodiments, the first communication mode is a subscription interface; among them, the subscription interface is a technical interface that allows real-time acquisition of server data updates or event notifications through a subscription mechanism.

[0079] It can be understood that in the vehicle quality inspection method provided in the embodiments of the present application, compared with obtaining the feedback information of the second instruction by polling; communicating based on the communication mode of the subscription interface is beneficial to reducing invalid queries and avoiding the problem of untimely result acquisition caused by setting too large a polling period, thereby maximizing the improvement of the quality inspection efficiency.

[0080] In some embodiments, the feedback information of the second instruction includes: the state of the vehicle-mounted device to be tested. In other embodiments, the feedback information of the second instruction includes: the execution result of the second instruction, for example, the second instruction is executed successfully, the second instruction is executed failed.

[0081] In some embodiments, Figure 3 is a schematic implementation process of a vehicle quality inspection method provided in the embodiments of the present application Figure 3 , such as Figure 3As shown, the vehicle quality inspection method further includes the following steps 301 to 303: Step 301, in the case of successful quality inspection, send a third instruction to the in-vehicle device under test through the first DDS interface; the third instruction is used to instruct to set the state of the in-vehicle device under test back to the first state. Step 302, receive the feedback information of the third instruction sent by the in-vehicle device under test through the first DDS interface. Step 303, in the case that the third state included in the feedback information of the third instruction is consistent with the first state, end the current quality inspection item.

[0082] It can be understood that in the vehicle quality inspection method provided in the embodiments of the present application, after restoring the state of the in-vehicle device under test in the case of successful quality inspection, the current quality inspection item is ended. In this way, it is beneficial to ensure the consistency before and after vehicle quality inspection and avoid introducing new problems due to vehicle quality inspection.

[0083] It should be understood that in the embodiments of the present application, the feedback information of the third instruction is not limited, and the feedback information of the third instruction can characterize the state of the in-vehicle device under test. In some embodiments, the feedback information of the third instruction includes: the third state. In other embodiments, the feedback information of the third instruction includes: the execution result of the third instruction, for example, the third instruction is executed successfully, the third instruction is executed failed.

[0084] Exemplarily, in one possible implementation, Figure 4 is a schematic implementation process of a vehicle quality inspection method provided in the embodiments of the present application Figure 4 , as Figure 4 shown, for the quality inspection of the functions of the in-vehicle device under test, it can be implemented through the following steps 401 to 410: Step 401, initiate a DDS connection request.

[0085] Among them, the quality inspection software deployed on the central control domain controller initiates a connection to the DDS service (an example of the DDS interface) to which the in-vehicle component under test (an example of the in-vehicle device under test) belongs.

[0086] Step 402, determine whether the connection is successful; if so, execute Step 403, otherwise execute Step 410.

[0087] Step 403, obtain and record the status of the component (i.e., the in-vehicle component under test, that is, the in-vehicle device under test) through the RPC interface.

[0088] Among them, the quality inspection software deployed on the central control domain controller obtains the status of the in-vehicle component under test through the RPC interface and records the status of the in-vehicle component under test.

[0089] Step 404, subscribe to the topic corresponding to the function.

[0090] Among them, the quality inspection software deployed on the central control domain controller subscribes to the topic of the corresponding function service.

[0091] Step 405, adjust the vehicle function state through the RPC interface.

[0092] Among them, the quality inspection software deployed on the central control domain controller sets the component state through the RPC interface.

[0093] Step 406, monitor whether the vehicle state change meets the expectation; if so, execute Step 407, otherwise execute Step 410.

[0094] Among them, the quality inspection software deployed on the central control domain controller monitors the function callback state of the component to be tested through the subscription interface.

[0095] Step 407, determine whether the detection is completed; if so, execute Step 408, otherwise execute Step 405.

[0096] Step 408, quality inspection is successful.

[0097] In some embodiments, when the quality inspection is successful, release the DDS connection.

[0098] Step 409, set and restore the component state through the RPC interface.

[0099] Step 410, quality inspection fails.

[0100] In some embodiments, when the quality inspection fails, release the DDS connection.

[0101] In some embodiments, the method further includes: when receiving a stop quality inspection signal, determining the current quality inspection state; when the current quality inspection state is that there is a quality inspection item being executed, after the quality inspection item is completed, stop the quality inspection.

[0102] It can be understood that in the vehicle quality inspection method provided in the embodiments of the present application, when receiving a stop quality inspection signal, if there is a quality inspection item being executed currently, the quality inspection will be stopped after the quality inspection item is completed. In this way, compared with forcibly stopping the quality inspection item being executed, it is beneficial to avoid the problem of data loss during storage and the problem of vehicle damage.

[0103] In other embodiments, the method further includes: when receiving a stop quality inspection signal, determining the current quality inspection state; when the current quality inspection state is that there is no quality inspection item being executed, stop the quality inspection.

[0104] Exemplarily, in one possible implementation Figure 5Schematic implementation process of a vehicle quality inspection method provided by an embodiment of the present application Figure 5 , such as Figure 5 shown, the vehicle quality inspection method further includes the following steps 501 to 506: Step 501, receive a stop quality inspection signal; Step 502, determine whether there is a quality inspection item being executed; if so, execute Step 503, otherwise execute Step 505; Step 503, continue the current quality inspection; Step 504, the current quality inspection is completed, record the current quality inspection result; Step 505, release the DDS connection; Step 506, report the current quality inspection result.

[0105] In an embodiment of the present application, a vehicle quality inspection method is provided. The method is applied to the domain controller of a vehicle, and the domain controller includes: a to-be-tested in-vehicle device and its corresponding second DDS interface; Figure 6 Schematic implementation process of a vehicle quality inspection method provided by an embodiment of the present application Figure 6 , such as Figure 6 shown, the method includes steps 601 to 603: Step 601, receive a connection request sent by the first DDS interface in the central control domain controller through the second DDS interface, and establish a connection between the second DDS interface and the first DDS interface; Step 602, receive a first instruction sent by the first DDS interface to the to-be-tested in-vehicle device through the second DDS interface; the first instruction is a quality inspection instruction obtained by the central control domain controller based on the quality inspection items of the to-be-tested in-vehicle device; Step 603, send the feedback information of the to-be-tested in-vehicle device on the first instruction to the first DDS interface through the second DDS interface, so that the central control domain controller determines the quality inspection result of the to-be-tested in-vehicle device based on at least the feedback information of the first instruction.

[0106] It can be understood that in the vehicle quality inspection method provided by the embodiment of the present application, the second DDS interface is used as the communication channel between the central control domain controller and the to-be-tested in-vehicle device. Thus, through the second DDS interface, the to-be-tested in-vehicle device can receive the quality inspection instruction sent by the central control domain controller, and through the second DDS interface, the to-be-tested in-vehicle device can send the feedback information of the quality inspection instruction to the central control domain controller. In this way, the central control domain controller determines whether the quality inspection of the to-be-tested in-vehicle device is successful based on the feedback information of the quality inspection instruction. That is to say, the automated test of the to-be-tested in-vehicle device based on the central control domain controller is realized, thereby improving the efficiency of vehicle quality inspection.

[0107] It should be understood that in the embodiments of the present application, the first DDS interface and the second DDS interface are not the same DDS interface. The first DDS interface is located in the central control domain controller, and the second DDS interface is located in the domain controller.

[0108] The further optional implementation manners of the above respective steps, related terms, etc. will be described below.

[0109] In step 601, a connection request sent by the first DDS interface in the central control domain controller is received through the second DDS interface, and a connection between the second DDS interface and the first DDS interface is established.

[0110] In step 602, a first instruction sent by the first DDS interface to the vehicle-mounted device to be tested is received through the second DDS interface; the first instruction is a quality inspection instruction obtained by the central control domain controller based on the quality inspection items of the vehicle-mounted device to be tested.

[0111] In some embodiments, the receiving, through the second DDS interface, the first instruction sent by the first DDS interface to the vehicle-mounted device to be tested includes: receiving, through the second DDS interface, the first instruction sent by the first DDS interface to the vehicle-mounted device to be tested; the first instruction is used to instruct to detect a first state of the vehicle-mounted device to be tested; the first state is the current state of the vehicle-mounted device to be tested; the quality inspection item is to quality inspect the current state of the vehicle-mounted device to be tested.

[0112] In other embodiments, the receiving, through the second DDS interface, the first instruction sent by the first DDS interface to the vehicle-mounted device to be tested includes: receiving, through the second DDS interface, the first instruction sent by the first DDS interface to the vehicle-mounted device to be tested; the first instruction is used to instruct to detect a first state of the vehicle-mounted device to be tested; the first state is the current state of the vehicle-mounted device to be tested; the quality inspection item is to quality inspect the function of the vehicle-mounted device to be tested.

[0113] In step 603, feedback information of the vehicle-mounted device to be tested on the first instruction is sent to the first DDS interface through the second DDS interface, so that the central control domain controller determines the quality inspection result of the vehicle-mounted device to be tested based at least on the feedback information of the first instruction.

[0114] In some embodiments, receiving, via the second DDS interface, a first instruction sent by the first DDS interface to the in-vehicle device under test includes: receiving, via the second DDS interface, the first instruction sent by the first DDS interface to the in-vehicle device under test; the first instruction is used to indicate detecting a first state of the in-vehicle device under test; the first state is the current state of the in-vehicle device under test; the quality inspection item is to inspect the current state of the in-vehicle device under test; correspondingly, sending, via the second DDS interface, feedback information of the in-vehicle device under test on the first instruction to the first DDS interface, so that the central control domain controller determines a quality inspection result of the in-vehicle device under test at least based on the feedback information of the first instruction, includes: sending, via the second DDS interface, the feedback information of the in-vehicle device under test on the first instruction to the first DDS interface; the feedback information of the first instruction includes the first state; so that when the central control domain controller determines that the first state included in the feedback information of the first instruction is consistent with a preset state, it determines that the quality inspection of the in-vehicle device under test is successful.

[0115] It can be understood that in the vehicle quality inspection method provided in the embodiments of the present application, through the second DDS interface, the in-vehicle device under test can receive the first instruction sent by the central control domain controller to detect the current state of the in-vehicle device, and through the second DDS interface, the in-vehicle device under test can send the feedback information of the first instruction to the central control domain controller, so that when the first state included in the feedback information of the first instruction is consistent with the preset state, the central control domain controller determines whether the quality inspection of the in-vehicle device under test is successful. That is to say, an automated test of the state of the in-vehicle device under test based on the central control domain controller is realized, thereby improving the efficiency of vehicle quality inspection.

[0116] In some embodiments, receiving, via the second DDS interface, a first instruction sent by the first DDS interface to the vehicle under test, includes: receiving, via the second DDS interface, the first instruction sent by the first DDS interface to the vehicle under test; the first instruction is used to instruct to detect a first state of the vehicle under test; the first state is the current state of the vehicle under test; the quality inspection item is to inspect the functions of the vehicle under test; correspondingly, sending, via the second DDS interface, feedback information of the vehicle under test on the first instruction to the first DDS interface, so that the central control domain controller determines the quality inspection result of the vehicle under test based at least on the feedback information of the first instruction, includes: sending, via the second DDS interface, the feedback information of the vehicle under test on the first instruction to the first DDS interface; the feedback information of the first instruction includes the first state; receiving, via the second DDS interface, a second instruction sent by the first DDS interface to the vehicle under test; the second instruction is used to instruct to set the state of the vehicle under test to a second state; the second state is different from the first state; the second instruction is generated by the central control domain controller based on the functions of the vehicle under test and the first state; sending, via the second DDS interface, the feedback information of the vehicle under test on the second instruction to the first DDS interface; so that the central control domain controller determines that the quality inspection of the vehicle under test is successful when it determines that the feedback information of the second instruction includes the first state.

[0117] It can be understood that in the vehicle quality inspection method provided in the embodiments of the present application, the second DDS interface enables the vehicle under test to receive the first instruction sent by the central control domain controller to detect the current state of the vehicle under test, and the second DDS interface enables the vehicle under test to send the feedback information of the first instruction to the central control domain controller, so that the central control domain controller generates a second instruction based on the feedback information of the first instruction and the functions of the vehicle under test; and receives, via the second DDS interface, the second instruction sent to the vehicle under test; and sends, via the second DDS interface, the feedback information of the second instruction to the central control domain controller; so that the central control domain controller determines that the quality inspection of the vehicle under test is successful when it determines that the feedback information of the second instruction includes the second state. That is to say, the automated test of the functions of the vehicle under test based on the central control domain controller is realized, thereby improving the efficiency of vehicle quality inspection.

[0118] In some embodiments, the method further includes: receiving, through a second DDS interface, a third instruction sent by the first DDS interface to the in-vehicle device under test; the third instruction is used to indicate setting the state of the in-vehicle device under test back to the first state; the third instruction is sent by the central control domain controller when it determines that the quality inspection is successful; sending, through the second DDS interface, feedback information of the in-vehicle device under test on the third instruction to the first DDS interface; the feedback information of the third instruction includes a third state; so that when the central control domain controller determines that the third state included in the feedback information of the third instruction is consistent with the first state, the current quality inspection item is ended.

[0119] It can be understood that in the vehicle quality inspection method provided in the embodiments of the present application, when the quality inspection is successful, a third instruction for setting the state of the in-vehicle device under test back to the first state sent by the central control domain controller is received through the second DDS interface, and feedback information of the third instruction is sent to the in-vehicle device under test through the second DDS interface; in this way, the central control domain controller ends the current quality inspection item only after determining that the state of the in-vehicle device under test is restored. In this way, it is beneficial to ensure the consistency before and after vehicle quality inspection and avoid introducing new problems due to vehicle quality inspection.

[0120] The exemplary application of the embodiments of the present application in an actual application scenario will be described below.

[0121] Automobile manufacturing plants are making efforts to improve the level of intelligence and automation, thereby reducing labor costs, improving the overall vehicle production efficiency, and ensuring the delivery speed and delivery experience. However, the related technologies lack an end-cloud integrated monitoring platform for the factory and cannot track the vehicle detection situation in a timely manner, resulting in low detection efficiency; at the same time, new cars are developing towards integrated domain controllers, and more and more hard-wired switches are being replaced by soft switches, making the detection of software channels increasingly important.

[0122] And the related technologies have the following problems: (1) Lack of steps and judgment criteria for detecting the state function of vehicle components based on the DDS interface; (2) Lack of design and implementation of DDS services for completing vehicle function detection; (3) Lack of configuration process for using DDS services in vehicle function detection; (4) Lack of measures to ensure the success rate during vehicle function detection; (5) Lack of fault tolerance design and Quality of Service (QOS) strategies for some abnormal scenarios in vehicle function detection.

[0123] An embodiment of the present application proposes a vehicle quality inspection method based on DDS communication. Combining the advantages of DDS in terms of distribution, low latency, and data-centricity, functional services based on DDS are deployed on each domain controller of the vehicle, and quality inspection software is deployed on the central control domain controller. The quality inspection software controls each component of the vehicle to execute functions through the DDS interface, and obtains the functional status of the components through the functional services and the DDS interface, realizing the inspection of the functions and statuses of vehicle components.

[0124] In some embodiments, the quality inspection can be understood as the inspection of the status and functions of vehicle components; the quality inspection software is an executable program running in the domain controller, with capabilities such as visualization, cloud communication, and logical processing; the quality inspection software is a distributed software.

[0125] In some embodiments, the central control domain controller is a central controller with capabilities such as visualization and networking.

[0126] The method provided by the embodiment of the present application is developed based on the DDS communication framework. During the development process of the quality inspection software, there is no need to process complex raw byte stream data such as common Ethernet / Controller Area Network (CAN) messages. As long as the topic data is defined, the data service interfaces corresponding to the detection items are integrated, and communication is carried out through the data service interfaces to send and parse the custom topic data, which greatly reduces the workload brought by byte stream parsing and encapsulation in the communication process of the quality inspection software and improves the development efficiency of the quality inspection software.

[0127] It can be understood that in the embodiment of the present application, since the DDS communication framework supports polymorphic languages such as C++ / Java, it makes the design of the quality inspection software easier to abstract and implement polymorphism, improves the reusability of software interfaces, and reduces the amount of software code; the highly abstract feature makes the quality inspection software more adaptable to various vehicle models, without caring about the complex communication protocols of each vehicle component. As long as the relevant DDS communication libraries are deployed on each central controller of the vehicle, the rapid transplantation of the quality inspection software can be achieved. The quality inspection software interface is developed using common languages such as C++ / Java, which is more friendly to external callers and supports direct cloud control, facilitating remote operation.

[0128] The vehicle quality inspection method provided by the embodiments of the present application can detect components with multi-state setting functions through the subscription and publication method. When the component function meets the requirements of the control instruction, it can immediately feedback the result and make a judgment. This method reduces the ineffective queries compared with polling the result at the application layer, and also avoids the problem that the result cannot be obtained in time due to too large polling cycle, which can maximize the improvement of the quality inspection efficiency; by constructing the DDS service to adapt to the communication capabilities of each ECU in the vehicle and supporting the QOS policy configuration at the same time, it greatly reduces the failure caused by the mismatch of the communication capabilities of both ends and ensures the success rate of the quality inspection process.

[0129] In some embodiments, the quality inspection software communicates through the service interface generated by the DDS tool chain. Non-matching interfaces cannot communicate, and at the same time, it supports the identity verification during the communication process to ensure the security when the components are being quality inspected. After the quality inspection software finishes execution, it will control the ECU to return to the initial state to ensure the consistency before and after the vehicle quality inspection and avoid introducing new problems after the vehicle quality inspection.

[0130] Figure 7 It is a schematic diagram of a vehicle quality inspection system provided by the embodiments of the present application, as Figure 7 shown, the vehicle quality inspection system includes: a cloud device 701, a central control domain controller 702, domain controllers 703, 704, 705, and an ECU 706; among them, the quality inspection software 7021 is deployed in the central control domain controller 702; the domain controller 703 includes: a DDS interface 7031 and a function service 7032; the DDS interface 7031 and the function service 7032 communicate through an internal channel; different ECUs support different communication protocols; for example: CAN, Local Interconnect Network (LIN), Serial Peripheral Interface (SPI), Inter-Integrated Circuit (I2C), etc.; and the cloud device 701, the central control domain controller 702 communicate with different domain controllers through DDS.

[0131] In some embodiments, software supporting the DDS protocol stack is deployed in the domain controller of the vehicle. The domain controller is a central controller that controls the integrated functions of the vehicle cockpit, chassis power, body, driving, etc., and supports the Ethernet protocol stack. The DDS protocol stack is recommended to support both User Datagram Protocol (UDP) and Transmission Control Protocol (TCP) at the same time to facilitate more flexible QOS configuration for applications.

[0132] In some embodiments, each domain controller develops a DDS-based service interface based on the DDS protocol stack for the function control of the currently implemented ECUs. The service interface mainly implements the acquisition of ECU status and the control of ECU functions. The ECU function control is the implementation of ECU functions completed by each domain controller based on the protocols supported by the ECU through the protocols. Common communication protocols include CAN, Controller Area Network with Flexible Data Rate (CAN FD), Diagnostic Communication over Internet Protocol (DoIP), TCP, UDP, I2C, LIN, SPI, etc.

[0133] In some embodiments, to implement the DDS service interface, it is necessary to first define the data structure used by the DDS service. The data structure contains various types of information about ECU functions, such as voltage, temperature, memory, switch status, etc. After the definition of the data structure is completed, the definition of the service interface is carried out, including defining the interface name, the data structure corresponding to the input parameters, and the data structure corresponding to the return result.

[0134] In some embodiments, the quality inspection software is deployed on the central control domain controller. According to the ECU objects to be quality inspected, the client proxy interface of the corresponding domain controller DDS service is integrated, and the development of the quality inspection process is completed.

[0135] In some embodiments, to ensure the success rate of quality inspection, the preconditions relied on during quality inspection execution include: the vehicle is in a stationary state and no one is operating the vehicle; the vehicle is in the power ON gear; each ECU is in a wake-up state; the vehicle has sufficient power or fuel to complete the quality inspection process; the remaining cruising range is more than 10 kilometers.

[0136] Based on the above preconditions, the quality inspection process is mainly divided into two categories. One is the detection of the vehicle's state after power-on, such as whether the value of the tire pressure is within the healthy range; the second is the detection of the vehicle's function settings after power-on, such as the angle adjustment of the rearview mirror, the adjustment of the seat, the light switch, etc.

[0137] In some embodiments, the detection of the vehicle's state after power-on can be achieved through the following steps 11 to 15: Step 11, the quality inspection software initializes DDS and initiates a DDS connection. According to the issued quality inspection items, the quality inspection software initiates a DDS connection to the corresponding server through the quality inspection item client proxy. The connection process requires configuring DDS parameters, including Domain, Internet Protocol (IP), Port, QOS, etc.; after initiation, the DDS communication middleware will assist in completing the connection process. If the DDS middleware returns a connection failure, it is also regarded as a failure of the quality inspection item, and jumps to Step 14, indicating that there is a problem with the software channel.

[0138] Considering that the quality inspection item status judgment may involve multiple DDS services, referring to Step 11, in the case of depending on multiple DDS services, initialization is completed in sequence. If one or more of them have connection failures, it is also regarded as a failure of the quality inspection item.

[0139] Step 12, after the connection is successful, obtain the status value of the corresponding ECU through the client RPC interface; the DDS middleware triggers the corresponding service interface of the client. The peer DDS service obtains the ECU status value through the internal protocol after receiving the interface message, encapsulates it according to the defined data structure, and returns the result.

[0140] Step 13, after the quality inspection software obtains the returned data, parse the data content and compare it according to the expected standard. If it meets the standard, the comparison is successful, and jumps to Step 15; if it does not meet the standard, the comparison fails, and jumps to Step 14.

[0141] Step 14, the quality inspection item comparison fails, record the result, and release the DDS connection.

[0142] Step 15, the quality inspection item comparison is successful, record the result, and release the DDS connection.

[0143] The release of the DDS connection is to clean up and disconnect the DDS calls related to the quality inspection item after a single quality inspection item is completed, and timely release the DDS resource occupation triggered by the current detection item.

[0144] For further improvement, if there is a risk of blocking in the DDS RPC interface, the quality inspection software can add a timeout judgment. If the connection result cannot be returned within the specified time, it is determined that the communication times out. The timeout time should be set according to the performance of both controllers and the actual debugging situation.

[0145] In some embodiments, for the detection of function settings after the vehicle is powered on, it can be implemented through the following Steps 21 to 27: Step 21, the quality inspection software initializes DDS and initiates a DDS connection. According to the issued quality inspection items, the quality inspection software initiates a DDS connection to the corresponding server through the quality inspection item client proxy. The connection process requires configuring initialization parameters, including Domain, IP, Port, QOS, etc.; if the connection interface returns a failure, it is regarded as a failure of the quality inspection item, indicating that there is a problem with the software channel.

[0146] Step 22, after the connection is successful, obtain the initial state of the current ECU through the client RPC interface; the DDS middleware triggers the corresponding service interface of the client, and the peer DDS service, upon receiving the interface message, obtains the ECU status value through the internal protocol, completes the encapsulation according to the defined data structure, and returns the result; the quality inspection software obtains the initial state value and records it.

[0147] Step 23, the quality inspection software subscribes to the status of the corresponding ECU through the DDS interface. When the functional service at the domain controller end implements the DDS publish interface, it should promptly callback through the service interface when there is a status change in the ECU.

[0148] When configuring communication with subscription and publication, the QOS policy should consider the business scenarios of the ECU on the corresponding server of the quality inspection item. If the ECU supports multiple application scenarios simultaneously and the required callback frequencies for different application scenarios are inconsistent, the ECU will default to using the scenario with the highest callback frequency for callback and quality inspection.

[0149] Step 24, the quality inspection software sets the ECU status through the RPC interface, waits for the ECU control result callback through the subscription and publication interface, and determines whether the ECU status callback result meets the expectations. If it meets the expectations, proceed to the next call until all settings are judged; if one of the settings does not meet the expectations, judge it as a failure and jump to Step 25.

[0150] Step 25, if all function settings are detected successfully, the quality inspection item comparison is successful, and the result is recorded; set the ECU back to the initial state through the RPC interface.

[0151] Step 26, if the quality inspection item comparison fails, record the result and release the DDS connection. When the quality inspection fails, it is recommended not to perform status recovery, retain the scene for convenient problem analysis, and promptly notify the technical personnel to handle it.

[0152] Step 27, if the quality inspection item comparison is successful, record the result and release the DDS connection.

[0153] In some embodiments, if there is a risk of blocking in the DDS RPC interface, timeout judgment can be added. If the connection result cannot be returned within the specified time, communication timeout is determined. If there is no callback in the DDS publish-subscribe interface, timeout judgment can be added. If there is no result callback within the specified time, communication timeout is determined. Communication timeout is also regarded as a quality inspection failure. The timeout should be set according to the performance of both controllers and the actual debugging situation.

[0154] In some embodiments, since DDS cannot guarantee 100% data transmission reliability, a more stringent QOS policy is set. On the premise that there is sufficient storage space in the ECU, set Reliability = RELIABLE and HISTORY = KEEP_LAST in the corresponding DDS server, and at the same time set the depth of the history record (that is, how many historical data to retain, depending on the actual debugging situation) to improve the ability to resend lost data; the quality inspection software is set on the key communication interface, and a retry mechanism is added. If the information content is not obtained, it will be tried again after a delay, and the number of retries is determined according to the specific debugging situation.

[0155] In some embodiments, since the DDS service corresponding to the ECU may need to support multiple business scenario requirements, when data is called back, data will be published for the business with the fastest frequency, but some quality inspection items do not require these frequently published data, such as the rearview mirror and seat adjustment. The quality inspection software should set an appropriate callback frequency minimum_separation (minimum interval time), and it is recommended that the time size ≥ 1S, and the most suitable one is set according to the time when the set state can be obtained in the actual test.

[0156] In some embodiments, to achieve remote control, the DDS protocol stack can also be deployed on the cloud corresponding to the quality inspection software. At this time, the quality inspection software is used as the server and the cloud is used as the client. The cloud issues quality inspection tasks and control commands through DDS to remotely control the vehicle to achieve quality inspection, and at the same time, it can subscribe to the quality inspection result topic of the quality inspection software to achieve real-time detection result monitoring.

[0157] In some embodiments, after the quality inspection software receives the stop signal, the quality inspection software scans the current quality inspection status for differential processing: 1) If there is no currently executing quality inspection item, record the current quality inspection result and release the DDS connection with each domain controller; 2) If there is a currently executing quality inspection item, wait for the current execution item to complete, notify the application layer to wait, wait for the current quality inspection item to complete, record the current quality inspection result, and release the DDS connection with each domain controller. After the quality inspection software receives the resume signal, traverse the currently completed quality inspection items and establish a DDS connection to continue the unfinished task items.

[0158] In some embodiments, Figure 8Schematic of the implementation process of a vehicle quality inspection method provided by an embodiment of this application Figure 7 , as Figure 8 shown, this method includes the following steps 801 to step 815: Step 801, the quality inspection software initiates a connection to the DDS middleware 1 (i.e., an example of the first DDS interface); Step 802, the DDS middleware 1 sends the connection signal to the DDS middleware 2 (i.e., an example of the second DDS interface); Step 803, the DDS middleware 2 sends the connection signal to the function service; Step 804, the function service sends the connection success to the DDS middleware 2; Step 805, the DDS middleware 2 transfers the signal to the DDS middleware 1; Step 806, the DDS middleware 1 sends the connection success to the quality inspection software; Step 807, the quality inspection software sends a call to the DDS interface to the DDS middleware 1 to obtain data; Step 808, the DDS middleware 1 transfers the interface to the DDS middleware 2; Step 809, the DDS middleware 2 sends a data acquisition call to the function service; Step 810, the function service uses the agreed protocol to acquire data; Step 811, the ECU returns the result to the function service; Step 812, the function service processes and encapsulates the result; Step 813, the function service sends the returned data to the DDS middleware 2; Step 814, the DDS middleware 2 transfers the data to the DDS middleware 1; Step 815, the DDS middleware 1 returns the data to the quality inspection software.

[0159] It can be understood that in the embodiment of this application, the automation of quality inspection is realized without manual participation.

[0160] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application rather than to limit them. Although this application has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that the technical solutions of this application can be modified or equivalently replaced without departing from the purpose and scope of the technical solutions of this application, and they should all be covered within the protection scope of this application.

[0161] It should be noted that although the steps of the method in this application are described in a specific order in the accompanying drawings, this does not require or imply that these steps must be executed in that specific order, or that all the steps shown must be executed to achieve the desired result. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step for execution, and / or one step may be decomposed into multiple steps for execution; or, the steps in different embodiments may be combined into a new technical solution. Based on the foregoing embodiments, an embodiment of this application provides a device, which includes each module included and each unit included in each module, and can be implemented by a processor; of course, it can also be implemented by specific logic circuits; during the implementation process, the processor may be an AI acceleration engine (such as an NPU, etc.), a graphics processing unit (GPU), a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP), or a field programmable gate array (FPGA), etc.

[0162] Figure 9 Schematic diagram of a vehicle quality inspection device provided by an embodiment of this application Figure 1 as Figure 9 shown, the vehicle quality inspection device 90 includes: an acquisition module 901, a first determination module 902, a first connection module 903, a first sending module 904, a first receiving module 905, and a second determination module 906; wherein, The acquisition module 901 is configured to acquire the quality inspection items of the in-vehicle device to be tested. The first determination module 902 is configured to determine the first DDS interface corresponding to the in-vehicle device to be tested from the first mapping relationship; the first mapping relationship is used to represent the corresponding relationship between the in-vehicle device to be tested and the DDS interface. The first connection module 903 is configured to establish a connection with the first DDS interface. The first sending module 904 is configured to send a first instruction to the in-vehicle device to be tested through the first DDS interface; the first instruction is a quality inspection instruction obtained based on the quality inspection items. The first receiving module 905 is configured to receive the feedback information of the first instruction sent by the in-vehicle device to be tested through the first DDS interface. The second determination module 906 is configured to determine the quality inspection result of the in-vehicle device to be tested at least based on the feedback information of the first instruction.

[0163] In some embodiments, the first sending module 904 is configured to, when the quality inspection item is to inspect the current state of the vehicle-mounted device to be tested, send a first instruction to the vehicle-mounted device to be tested through the first DDS interface; the first instruction is used to instruct to detect a first state of the vehicle-mounted device to be tested; the first state is the current state of the vehicle-mounted device to be tested; the second determination module 906 is configured to determine that the quality inspection of the vehicle-mounted device to be tested is successful when the first state included in the feedback information of the first instruction is consistent with a preset state.

[0164] In some embodiments, the first sending module 904 is configured to, when the quality inspection item is to inspect the function of the vehicle-mounted device to be tested, send a first instruction to the vehicle-mounted device to be tested through the first DDS interface; the first instruction is used to instruct to detect a first state of the vehicle-mounted device to be tested; the first state is the current state of the vehicle-mounted device to be tested; the second determination module 906 is configured to generate a second instruction based on the function of the vehicle-mounted device to be tested and the first state; the second instruction is used to instruct to set the state of the vehicle-mounted device to be tested to a second state; the second state is different from the first state; send the second instruction to the vehicle-mounted device to be tested through the first DDS interface based on a first communication mode; receive the feedback information of the second instruction sent by the vehicle-mounted device to be tested through the first DDS interface; determine that the quality inspection of the vehicle-mounted device to be tested is successful when the second state is included in the feedback information of the second instruction.

[0165] In some embodiments, the vehicle quality inspection device 900 further includes an end module; wherein, the first sending module 904 is further configured to, when the quality inspection is successful, send a third instruction to the vehicle-mounted device to be tested through the first DDS interface; the third instruction is used to instruct to set the state of the vehicle-mounted device to be tested back to the first state; the first receiving module 905 is configured to receive the feedback information of the third instruction sent by the vehicle-mounted device to be tested through the first DDS interface; the end module is configured to end the current quality inspection item when the third state included in the feedback information of the third instruction is consistent with the first state.

[0166] In some embodiments, the first determination module 902 is configured to determine the first DDS interface corresponding to the vehicle-mounted device to be tested from a first mapping relationship when determining that the vehicle meets a first condition; wherein, the first condition includes one or more of the following: the vehicle is in a stationary state; the vehicle is in a powered-on state; the electronic control unit of the vehicle-mounted device to be tested is in a wake-up state; the power or fuel quantity of the vehicle is greater than or equal to a quantity threshold.

[0167] In some embodiments, the vehicle quality inspection device 900 further includes a stop module; wherein, the first determination module 902 is further configured to determine the current quality inspection status when receiving a stop quality inspection signal; the stop module is configured to stop the quality inspection after the quality inspection item is completed when the current quality inspection status is that there is a quality inspection item being executed.

[0168] Figure 10 Schematic diagram of a vehicle quality inspection device provided by an embodiment of the present application Figure 2 , such as Figure 10 shown, the vehicle quality inspection device 100 includes: a second receiving module 1001, a second connection module 1002 and a second sending module 1003; wherein, The second receiving module 1001 is configured to receive a connection request sent by a first DDS interface in a central control domain controller through a second DDS interface; The second connection module 1002 is configured to establish a connection between the second DDS interface and the first DDS interface; The second receiving module 1001 is configured to receive a first instruction sent by the first DDS interface to the to-be-tested vehicle-mounted device through the second DDS interface; the first instruction is a quality inspection instruction obtained by the central control domain controller based on the quality inspection items of the to-be-tested vehicle-mounted device; The second sending module 1003 is configured to send feedback information of the to-be-tested vehicle-mounted device on the first instruction to the first DDS interface through the second DDS interface, so that the central control domain controller determines the quality inspection result of the to-be-tested vehicle-mounted device at least based on the feedback information of the first instruction.

[0169] In some embodiments, the second receiving module 1001 is configured to receive a first instruction sent by the first DDS interface to the to-be-tested vehicle-mounted device through the second DDS interface; the first instruction is used to instruct to detect a first state of the to-be-tested vehicle-mounted device; the first state is the current state of the to-be-tested vehicle-mounted device; the quality inspection item is to quality inspect the current state of the to-be-tested vehicle-mounted device; the second sending module 1003 is configured to send feedback information of the to-be-tested vehicle-mounted device on the first instruction to the first DDS interface through the second DDS interface; the feedback information of the first instruction includes the first state; so that the central control domain controller determines that the quality inspection of the to-be-tested vehicle-mounted device is successful when determining that the first state included in the feedback information of the first instruction is consistent with a preset state.

[0170] In some embodiments, the second receiving module 1001 is configured to receive, through the second DDS interface, a first instruction sent by the first DDS interface to the in-vehicle device under test; the first instruction is used to instruct to detect a first state of the in-vehicle device under test; the first state is the current state of the in-vehicle device under test; the quality inspection item is to inspect the functions of the in-vehicle device under test; the second sending module 1003 is configured to send, through the second DDS interface, feedback information of the in-vehicle device under test on the first instruction to the first DDS interface; the feedback information of the first instruction includes the first state; receive, through the second DDS interface, a second instruction sent by the first DDS interface to the in-vehicle device under test; the second instruction is used to instruct to set the state of the in-vehicle device under test to a second state; the second state is different from the first state; the second instruction is generated by the central control domain controller based on the functions of the in-vehicle device under test and the first state; send, through the second DDS interface, feedback information of the in-vehicle device under test on the second instruction to the first DDS interface; so that when the central control domain controller determines that the feedback information of the second instruction includes the first state, it determines that the quality inspection of the in-vehicle device under test is successful.

[0171] In some embodiments, the second receiving module 1001 is further configured to receive, through the second DDS interface, a third instruction sent by the first DDS interface to the in-vehicle device under test; the third instruction is used to instruct to set the state of the in-vehicle device under test back to the first state; the third instruction is sent by the central control domain controller when it determines that the quality inspection is successful; the second sending module 1003 is further configured to send, through the second DDS interface, feedback information of the in-vehicle device under test on the third instruction to the first DDS interface; the feedback information of the third instruction includes a third state; so that when the central control domain controller determines that the third state included in the feedback information of the third instruction is consistent with the first state, it ends the current quality inspection item.

[0172] The description of the above device embodiments is similar to that of the above method embodiments and has similar beneficial effects to those of the method embodiments. For the technical details not disclosed in the device embodiments of the present application, please refer to the description of the method embodiments of the present application for understanding.

[0173] It should be noted that the division of modules in the embodiments of the present application is illustrative, merely a logical function division, and there may be other division methods in actual implementation. In addition, in each embodiment of the present application, each functional unit may be integrated in a processing unit, may exist independently physically, or two or more units may be integrated in one unit. The above integrated unit may be implemented in the form of hardware, or in the form of a software functional unit, or in the form of a combination of software and hardware.

[0174] It should be noted that in the embodiments of the present application, if the above method is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the embodiments of the present application, in essence, or the part that contributes to the related technology, may be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a vehicle to execute all or part of the methods described in the embodiments of the present application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (ROMs), magnetic disks, or optical discs that can store program codes. In this way, the embodiments of the present application are not limited to any specific combination of hardware and software.

[0175] The embodiments of the present application provide a vehicle, including a central control domain controller and at least one domain controller. The central control domain controller is used for the method applied to the central control domain controller; the domain controller is used for the method applied to the domain controller.

[0176] The embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed, it implements the steps in the method provided in the above embodiments. The embodiments of the present application provide a computer program product containing instructions, and when it runs on a computer, it enables the computer to execute the steps in the method provided in the above method embodiments.

[0177] It should be pointed out here that: the descriptions of the above storage medium and vehicle embodiments are similar to the descriptions of the above method embodiments and have beneficial effects similar to those of the method embodiments. For the technical details not disclosed in the storage medium and vehicle embodiments of the present application, please refer to the descriptions of the method embodiments of the present application for understanding.

[0178] It should be understood that the "one embodiment" or "an embodiment" or "some embodiments" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, the "in one embodiment" or "in an embodiment" or "in some embodiments" that appear throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present application, the magnitudes of the serial numbers of the above processes do not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. The serial numbers of the embodiments of the present application above are only for description and do not represent the advantages or disadvantages of the embodiments. The above descriptions of the various embodiments tend to emphasize the differences between the various embodiments, and their similarities or similarities can be referred to each other. For the sake of brevity, they will not be elaborated herein.

[0179] As used herein, the term "and / or" is merely a description of the relationship between associated objects, indicating that there can be three relationships. For example, object A and / or object B means: object A exists alone, object A and object B exist simultaneously, and object B exists alone.

[0180] It should be noted that, as used herein, 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 not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, article or vehicle. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of additional identical elements in the process, method, article or device including the element.

[0181] In several embodiments provided in the present application, it should be understood that the disclosed vehicle and method can be implemented in other ways. The embodiments described above are merely illustrative. For example, the division of the modules is only a logical function division, and there can be other division methods in actual implementation. For example, multiple modules or components can be combined, or can be integrated into another system, or some features can be ignored, or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed with each other can be through some interfaces. The indirect coupling or communication connection of the vehicle or module can be electrical, mechanical or other forms.

[0182] The modules described above as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules; they may be located in one place or distributed across multiple network elements; some or all of the modules may be selected according to actual needs to achieve the objectives of the solution of this embodiment.

[0183] In addition, each functional module in the embodiments of the present application may be all integrated in one processing unit, or each module may be separately regarded as one unit, or two or more modules may be integrated in one unit; the above-mentioned integrated modules may be implemented in the form of hardware, or in the form of a combination of hardware and software functional units.

[0184] Those of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiments can be completed by hardware related to program instructions. The foregoing program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps including the above method embodiments; and the foregoing storage medium includes: removable storage devices, read-only memory (ROM), magnetic disks, or optical disks and other various media that can store program codes.

[0185] Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of the present application, in essence, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a vehicle to execute all or part of the methods described in the various embodiments of the present application. And the foregoing storage medium includes: removable storage devices, ROM, magnetic disks, or optical disks and other various media that can store program codes.

[0186] The methods disclosed in the several method embodiments provided by the present application can be arbitrarily combined without conflict to obtain new method embodiments. The features disclosed in the several product embodiments provided by the present application can be arbitrarily combined without conflict to obtain new product embodiments. The features disclosed in the several method or vehicle embodiments provided by the present application can be arbitrarily combined without conflict to obtain new method embodiments or vehicle embodiments.

[0187] The above is only the implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present application, and all of them should be covered by the protection scope of the present application.

Claims

1. A vehicle quality inspection method, characterized in that, The method is applied to the central control domain controller of a vehicle, and the central control domain controller includes: a first Data Distribution Service (DDS) interface corresponding to a vehicle-mounted device to be tested; the method includes: Obtain the quality inspection items of the vehicle-mounted device to be tested; Determine the first DDS interface corresponding to the vehicle-mounted device to be tested from the first mapping relationship, and establish a connection with the first DDS interface; the first mapping relationship is used to represent the corresponding relationship between the vehicle-mounted device to be tested and the DDS interface; Send a first instruction to the vehicle-mounted device to be tested through the first DDS interface; the first instruction is a quality inspection instruction obtained based on the quality inspection items; Receive the feedback information of the first instruction sent by the vehicle-mounted device to be tested through the first DDS interface; Determine the quality inspection result of the vehicle-mounted device to be tested based at least on the feedback information of the first instruction.

2. The vehicle quality inspection method according to claim 1, wherein The step of sending a first instruction to the vehicle-mounted device to be tested through the first DDS interface includes: When the quality inspection item is to inspect the current state of the vehicle-mounted device to be tested, send a first instruction to the vehicle-mounted device to be tested through the first DDS interface; the first instruction is used to instruct to detect the first state of the vehicle-mounted device to be tested; the first state is the current state of the vehicle-mounted device to be tested; Correspondingly, the step of determining the quality inspection result of the vehicle-mounted device to be tested based at least on the feedback information of the first instruction includes: When the first state included in the feedback information of the first instruction is consistent with the preset state, determine that the quality inspection of the vehicle-mounted device to be tested is successful.

3. The vehicle quality inspection method according to claim 1, characterized in that, The step of sending a first instruction to the vehicle-mounted device to be tested through the first DDS interface includes: When the quality inspection item is to inspect the function of the vehicle-mounted device to be tested, send a first instruction to the vehicle-mounted device to be tested through the first DDS interface; the first instruction is used to instruct to detect the first state of the vehicle-mounted device to be tested; the first state is the current state of the vehicle-mounted device to be tested; Correspondingly, the step of determining the quality inspection result of the vehicle-mounted device to be tested based at least on the feedback information of the first instruction received from the vehicle-mounted device to be tested through the first DDS interface includes: Generate a second instruction based on the function of the vehicle-mounted device to be tested and the first state; the second instruction is used to instruct to set the state of the vehicle-mounted device to be tested to a second state; the second state is different from the first state; Send the second instruction to the vehicle-mounted device to be tested through the first DDS interface based on the first communication mode; Receive the feedback information of the second instruction sent by the vehicle-mounted device to be tested through the first DDS interface; When the feedback information of the second instruction includes the second state, determine that the quality inspection of the vehicle-mounted device to be tested is successful.

4. The vehicle quality inspection method according to claim 3, wherein The method further includes: When the quality inspection is successful, send a third instruction to the vehicle-mounted device to be tested through the first DDS interface; the third instruction is used to instruct to set the state of the vehicle-mounted device to be tested back to the first state; Receive the feedback information of the third instruction sent by the vehicle-mounted device to be tested through the first DDS interface; When the third state included in the feedback information of the third instruction is consistent with the first state, end the current quality inspection item.

5. The vehicle quality inspection method according to claim 1, wherein Determining the first DDS interface corresponding to the to-be-tested in-vehicle device from the first mapping relationship includes: When it is determined that the vehicle meets the first condition, determining the first DDS interface corresponding to the to-be-tested in-vehicle device from the first mapping relationship; Wherein, the first condition includes one or more of the following: The vehicle is in a stationary state; The vehicle is in a powered-on state; The electronic control unit of the to-be-tested in-vehicle device is in a wake-up state; The power or fuel level of the vehicle is greater than or equal to a quantity threshold.

6. The vehicle quality inspection method according to claim 1, wherein The method further includes: When receiving a stop quality inspection signal, determining the current quality inspection state; When the current quality inspection state is that there is a quality inspection item being executed, stop the quality inspection after the quality inspection item is completed.

7. A vehicle quality inspection method, characterized in that, The method is applied to a domain controller of a vehicle, and the domain controller includes: a to-be-tested in-vehicle device and its corresponding second DDS interface; the method includes: Receiving, through the second DDS interface, a connection request sent by the first DDS interface in the central control domain controller, and establishing a connection between the second DDS interface and the first DDS interface; Receiving, through the second DDS interface, a first instruction sent by the first DDS interface to the to-be-tested in-vehicle device; the first instruction is a quality inspection instruction obtained by the central control domain controller based on the quality inspection items of the to-be-tested in-vehicle device; Sending, through the second DDS interface, the feedback information of the to-be-tested in-vehicle device on the first instruction to the first DDS interface, so that the central control domain controller determines the quality inspection result of the to-be-tested in-vehicle device at least based on the feedback information of the first instruction.

8. The vehicle quality inspection method according to claim 7, wherein, The receiving, through the second DDS interface, the first instruction sent by the first DDS interface to the to-be-tested in-vehicle device includes: Receiving, through the second DDS interface, the first instruction sent by the first DDS interface to the to-be-tested in-vehicle device; the first instruction is used to instruct to detect the first state of the to-be-tested in-vehicle device; the first state is the current state of the to-be-tested in-vehicle device; the quality inspection item is to quality inspect the current state of the to-be-tested in-vehicle device; Correspondingly, the sending, through the second DDS interface, the feedback information of the to-be-tested in-vehicle device on the first instruction to the first DDS interface, so that the central control domain controller determines the quality inspection result of the to-be-tested in-vehicle device at least based on the feedback information of the first instruction, includes: Sending, through the second DDS interface, the feedback information of the to-be-tested in-vehicle device on the first instruction to the first DDS interface; the feedback information of the first instruction includes the first state; so that the central control domain controller determines that the to-be-tested in-vehicle device passes the quality inspection when it is determined that the first state included in the feedback information of the first instruction is consistent with the preset state.

9. The vehicle quality inspection method according to claim 7, wherein The receiving, through the second DDS interface, the first instruction sent by the first DDS interface to the to-be-tested in-vehicle device includes: Receive a first instruction sent by the first DDS interface to the in-vehicle device under test through the second DDS interface; the first instruction is used to instruct to detect a first state of the in-vehicle device under test; the first state is the current state of the in-vehicle device under test; the quality inspection item is to quality-inspect the functions of the in-vehicle device under test. Correspondingly, sending, through the second DDS interface, feedback information of the in-vehicle device under test on the first instruction to the first DDS interface, so that the central control domain controller determines the quality inspection result of the in-vehicle device under test based at least on the feedback information of the first instruction, includes: Send, through the second DDS interface, feedback information of the in-vehicle device under test on the first instruction to the first DDS interface; the feedback information of the first instruction includes the first state. Receive a second instruction sent by the first DDS interface to the in-vehicle device under test through the second DDS interface; the second instruction is used to instruct to set the state of the in-vehicle device under test to a second state; the second state is different from the first state; the second instruction is generated by the central control domain controller based on the functions of the in-vehicle device under test and the first state. Send, through the second DDS interface, feedback information of the in-vehicle device under test on the second instruction to the first DDS interface; so that the central control domain controller determines that the quality inspection of the in-vehicle device under test is successful when it is determined that the feedback information of the second instruction includes the first state.

10. The vehicle quality inspection method according to claim 9, characterized in that, The method further includes: Receive a third instruction sent by the first DDS interface to the in-vehicle device under test through the second DDS interface; the third instruction is used to instruct to set the state of the in-vehicle device under test back to the first state; the third instruction is sent by the central control domain controller when it determines that the quality inspection is successful. Send, through the second DDS interface, feedback information of the in-vehicle device under test on the third instruction to the first DDS interface; the feedback information of the third instruction includes a third state; so that the central control domain controller ends the current quality inspection item when it is determined that the third state included in the feedback information of the third instruction is consistent with the first state.

11. A vehicle quality inspection device, characterized in that, The device includes: An acquisition module configured to acquire the quality inspection item of the in-vehicle device under test. A first determination module configured to determine, from a first mapping relationship, the first DDS interface corresponding to the in-vehicle device under test; the first mapping relationship is used to represent the corresponding relationship between the in-vehicle device under test and the DDS interface. A first connection module configured to establish a connection with the first DDS interface. A first sending module configured to send a first instruction to the in-vehicle device under test through the first DDS interface; the first instruction is a quality inspection instruction obtained based on the quality inspection item. A first receiving module configured to receive the feedback information of the first instruction sent by the in-vehicle device under test through the first DDS interface. A second determination module configured to determine the quality inspection result of the in-vehicle device under test based at least on the feedback information of the first instruction.

12. A vehicle quality inspection device, characterized in that, The device includes: A second receiving module, configured to receive a connection request sent by a first DDS interface in a central control domain controller through the second DDS interface; A second connection module, configured to establish a connection between the second DDS interface and the first DDS interface; The second receiving module is configured to receive a first instruction sent by the first DDS interface to the in-vehicle device under test through the second DDS interface; the first instruction is a quality inspection instruction obtained by the central control domain controller based on the quality inspection items of the in-vehicle device under test; A second sending module, configured to send feedback information of the in-vehicle device under test on the first instruction to the first DDS interface through the second DDS interface, so that the central control domain controller determines the quality inspection result of the in-vehicle device under test at least based on the feedback information of the first instruction.

13. A vehicle, comprising a central control domain controller and at least one domain controller, characterized in that, The central control domain controller is used to implement the method according to any one of claims 1 to 6; the domain controller is used to implement the method according to any one of claims 7 to 10.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed, it implements the method according to any one of claims 1 to 6; or, when the computer program is executed, it implements the method according to any one of claims 7 to 10.

15. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instruction is executed, it implements the method according to any one of claims 1 to 6; or, when the computer program or instruction is executed, it implements the method according to any one of claims 7 to 10.

Images