Vehicle function fault diagnosis method and device, vehicle and storage medium

Abstract

The embodiment of the application provides a vehicle function fault diagnosis method, device, vehicle and storage medium, and belongs to the technical field of vehicle function fault diagnosis. The method comprises the following steps: generating a function information table based on a vehicle function; acquiring function interface information of the vehicle function; acquiring function signal information of a preset function characteristic signal; wherein the function characteristic signal is a signal for representing the vehicle function, and the function signal information is used for representing the attribute of the function characteristic signal; associating the function interface information, the function signal information and the function information table based on the vehicle function to obtain a function mapping table; and performing fault diagnosis on the vehicle function based on the function mapping table to obtain a fault diagnosis report. The embodiment of the application can monitor, analyze and diagnose the vehicle function to quickly find the function in the fault condition, and improves the fault diagnosis efficiency of the vehicle function.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicle function fault diagnosis, and in particular to a vehicle function fault diagnosis method and device, a vehicle and a storage medium. BACKGROUND

[0002] At present, a vehicle-mounted system is mainly developed based on a service-oriented architecture (SOA), takes Ethernet as a communication medium, and realizes data exchange and interoperation through a SOME / IP protocol stack, thereby improving the communication flexibility and expandability of the vehicle-mounted system.

[0003] However, in an actual application scenario, as the electrification degree of a vehicle is increasingly high and the vehicle functions are increasingly more, the communication link of the vehicle is very complex. When a vehicle function has a problem, due to the complexity of the communication link, fault diagnosis becomes difficult, and the problem cannot be quickly located and solved, and the fault diagnosis efficiency is low.

[0004] Therefore, how to improve the vehicle function fault diagnosis efficiency has become a technical problem to be solved. SUMMARY

[0005] The main purpose of the embodiments of the present application is to provide a vehicle function fault diagnosis method and device, a vehicle and a storage medium, which aims to improve the vehicle function fault diagnosis efficiency.

[0006] To achieve the above purpose, a first aspect of the embodiments of the present application provides a vehicle function fault diagnosis method applied to a vehicle-mounted system, wherein the vehicle-mounted system is provided with a vehicle function, and the method comprises the following steps.

[0007] Generating a function information table based on the vehicle function;

[0008] Obtaining function interface information of the vehicle function;

[0009] Obtaining function signal information of a preset function characteristic signal; wherein the function characteristic signal is a signal for representing the vehicle function, and the function signal information is used to represent the attribute of the function characteristic signal;

[0010] Associating the function interface information, the function signal information and the function information table based on the vehicle function to obtain a function mapping table;

[0011] Performing fault diagnosis on the vehicle function based on the function mapping table to obtain a fault diagnosis report.

[0012] In some embodiments, the vehicle-mounted system comprises communication configuration data, the communication configuration data being data for configuring the vehicle functions; the vehicle functions are diagnosed based on the function mapping table to obtain a fault diagnosis report, comprising:

[0013] The communication configuration data is checked based on the function mapping table to obtain a function configuration check result;

[0014] The vehicle functions are diagnosed based on the function configuration check result to obtain the fault diagnosis report; wherein the fault diagnosis report indicates that the vehicle functions have faults or are normal.

[0015] In some embodiments, the communication configuration data comprises a vehicle communication signal table, the vehicle communication signal table comprising a plurality of vehicle function signals, the number of vehicle functions being at least two, each vehicle function signal corresponding to a vehicle function, each vehicle function corresponding to a function signal information, and the function mapping table containing at least two function signal information; the communication configuration data is checked based on the function mapping table to obtain a function configuration check result, comprising:

[0016] For each function signal information in the function mapping table, the function signal information is matched with the plurality of vehicle function signals in the vehicle communication signal table to obtain a signal matching result;

[0017] The signal matching result corresponding to each function signal information is counted to generate the function configuration check result.

[0018] In some embodiments, the vehicle-mounted system further comprises a protocol stack, and the vehicle functions are diagnosed based on the function configuration check result to obtain the fault diagnosis report, comprising:

[0019] In the case that the function configuration check result indicates that the communication configuration data passes the check, the protocol stack is checked based on the function mapping table to obtain a protocol stack check result;

[0020] The vehicle functions are diagnosed based on the function configuration check result and the protocol stack check result to obtain the fault diagnosis report.

[0021] In some embodiments, the protocol stack is checked based on the function mapping table to obtain a protocol stack check result, comprising:

[0022] Stack data of the protocol stack is obtained; wherein the stack data contains a plurality of function service signal information;

[0023] For each of the function signal information in the function mapping table, the function signal information is information-matched with a plurality of the function service signal information in the stack data, to obtain an information matching result;

[0024] The information matching result corresponding to each of the function signal information is counted, to obtain the protocol stack verification result.

[0025] In some embodiments, the vehicle function is fault-diagnosed based on the function configuration verification result and the protocol stack verification result, to obtain the fault diagnosis report, including:

[0026] In a case where the function configuration verification result represents that the communication configuration data passes the verification, and the protocol stack verification result represents that the protocol stack passes the verification, a plurality of preset function interface files are interface information-verified based on the function mapping table and the vehicle communication signal table, to obtain an interface verification result; wherein the function interface file is configured in the vehicle-mounted system;

[0027] The vehicle function is fault-diagnosed based on the function configuration verification result, the protocol stack verification result and the interface verification result, to obtain the fault diagnosis report.

[0028] In some embodiments, the vehicle communication signal table further includes function definition information corresponding to a plurality of the vehicle function signals, and the interface information verification of the plurality of preset function interface files based on the function mapping table and the vehicle communication signal table to obtain the interface verification result includes:

[0029] For each of the function interface file, header file definition information of the function interface file is acquired, the vehicle function corresponding to the function interface file is determined based on the function mapping table, the function definition information is determined from the vehicle communication signal table based on the vehicle function corresponding to the function interface file, and the header file definition information and the function definition information are matched to obtain interface matching information;

[0030] The interface verification result is generated according to the interface matching information of each of the function interface file.

[0031] To achieve the above object, a second aspect of the embodiment of the present application proposes a vehicle function fault diagnosis device, the device comprising:

[0032] A function information table generation module is configured to generate a function information table based on a vehicle function;

[0033] A function interface information acquisition module is configured to acquire function interface information of the vehicle function;

[0034] The function signal information acquisition module is configured to acquire function signal information of a preset function characteristic signal, wherein the function characteristic signal is a signal used for representing the function of the vehicle, and the function signal information is used for representing an attribute of the function characteristic signal.

[0035] The information association module is configured to associate the function interface information, the function signal information, and the function information table based on the function of the vehicle, to obtain a function mapping table.

[0036] The fault diagnosis module is configured to perform fault diagnosis on the function of the vehicle based on the function mapping table, to obtain a fault diagnosis report.

[0037] To achieve the above object, a third aspect of the embodiments of the present application provides a vehicle, which comprises a memory and a processor, the memory stores a computer program, and the processor implements the method of the first aspect when executing the computer program.

[0038] To achieve the above object, a fourth aspect of the embodiments of the present application provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the method of the first aspect.

[0039] The vehicle function fault diagnosis method, device, vehicle, and storage medium provided by the present application can generate a function information table based on a vehicle function, acquire function interface information of the vehicle function, acquire function signal information of a preset function characteristic signal, wherein the function characteristic signal is a signal used for representing the function of the vehicle, and the function signal information is used for representing an attribute of the function characteristic signal, associate the function interface information, the function signal information, and the function information table based on the function of the vehicle, to obtain a function mapping table, and perform fault diagnosis on the function of the vehicle based on the function mapping table, to obtain a fault diagnosis report. The vehicle function can be monitored, analyzed, and diagnosed to quickly find the function with faults, thereby improving the fault diagnosis efficiency of the vehicle function. BRIEF DESCRIPTION OF DRAWINGS

[0040] Figure 1 is a flowchart of the vehicle function fault diagnosis method provided by the embodiments of the present application;

[0041] Figure 2 is a flowchart of step S105 in Figure 1

[0042] Figure 3 is a flowchart of step S201 in Figure 2

[0043] Figure 4 is a flowchart of step S202 in Figure 2 ​​​

[0044] Figure 5 is Figure 4 the flowchart of step S401 in

[0045] Figure 6 is Figure 4 the flowchart of step S402 in

[0046] Figure 7 is Figure 6 the flowchart of step S601 in

[0047] Figure 8 is a structural schematic diagram of a vehicle function fault diagnosis device provided by an embodiment of the present application;

[0048] Figure 9 is a hardware structure schematic diagram of a vehicle provided by an embodiment of the present application. DETAILED DESCRIPTION

[0049] In order to make the purposes, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in combination with the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and do not limit the present application.

[0050] It should be noted that although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a manner different from the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification and claims and the above-described drawings are used to distinguish similar objects, and do not necessarily describe a specific order or sequence.

[0051] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present 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.

[0052] First, the terms involved in the present application are analyzed:

[0053] Vehicle-mounted system refers to a series of electronic systems and devices installed in the interior of a car. They provide convenience, safety and comfort for drivers and passengers by integrating advanced information technology, communication technology and control technology. Vehicle-mounted systems have multiple functions such as navigation, communication, entertainment, information services, vehicle control and safety, aiming to improve the intelligence and automation level of cars and meet the needs of modern people for high-quality travel.

[0054] Service-Oriented Architecture (SOA) is a software design pattern that allows for the deployment, composition, and use of loosely coupled application components over a distributed network based on service requests. These services can be divided into different layers based on functionality, allowing each service to operate independently without affecting others. These services communicate over a network and can be shared and reused across different applications. SOA aims to decouple the architecture and business processes of complex systems, improving system flexibility, scalability, and reusability.

[0055] Scalable service-Oriented MiddlewarE over IP (SOME / IP) is an automotive / embedded communication protocol designed to implement scalable service-oriented middleware. This protocol is particularly suitable for automotive middleware solutions, supporting remote procedure calls, event notifications, and underlying serialization / wire formats. The design of the SOME / P protocol is adaptable to different operating systems such as AUTOSAR, GENIVI, and OSEK, and even on embedded devices without an operating system.

[0056] Signal deployment: Signals are data units in communication, which can be deployed to different levels of the protocol stack according to different communication protocols and requirements. For signal deployment on vehicles, it specifically refers to the process of managing and configuring various signals in the vehicle system. There are multiple signals in the vehicle system, which may come from various components and sensors of the vehicle, used to monitor and control the running state of the vehicle. Signal deployment on vehicles ensures that these signals can be correctly identified, processed, and applied to achieve safe operation, performance optimization, and intelligent functions of the vehicle.

[0057] Host system base: This is an important hardware or software component responsible for integrating signals defined in different protocol stacks for integration and processing in the host system.

[0058] TCP transport layer: The TCP transport layer is responsible for handling transport layer protocols for establishing reliable communication connections between different devices. TCP is responsible for data segmentation, retransmission, flow control, etc., to ensure reliable data transmission over the network. In the vehicle system, this level may involve communication between different control units within the vehicle and connection between the vehicle and external systems.

[0059] Protocol stack: The protocol stack is located above the TCP transport layer and is responsible for handling higher-level protocols, such as application layer protocols (e.g., HTTP, MQTT, custom protocols, etc.). The protocol stack separates the underlying transmission details from the upper-layer application logic, allowing the application layer to focus on business functions. The protocol stack usually includes protocol parsing, encapsulation, data format conversion, and other operations.

[0060] API layer: The API layer provides a set of interfaces for interaction between the upper-layer application and the protocol stack. The API layer defines functions, methods, and data structures that can be called by the upper-layer application, allowing developers to implement the required functions without needing to understand the underlying details. The API layer can hide the complexity of the underlying layers and provide a higher-level abstraction.

[0061] Upper-layer application: This is the highest layer of the vehicle system, which includes the actual application functions of the vehicle, such as instrument display, vehicle control, data acquisition, etc. At this level, developers can implement the required business logic by calling the interfaces provided by the API layer. The upper-layer application can be a single functional module or a combination of multiple modules.

[0062] With the development of automotive architecture, currently, vehicle systems are mainly developed based on Service-Oriented Architecture (SOA), using Ethernet as the communication medium, and implementing data exchange and interoperability through the SOME / IP protocol stack, which improves the communication flexibility and scalability of vehicle systems.

[0063] A service information table is generated for the functional service, which contains detailed definitions of the functional service. The protocol stack can be generated based on the information in the service information table, and the generated protocol stack will be integrated into the host system base of the vehicle. By subscribing to the service signals of the functional service, communication between various application layers can be achieved.

[0064] However, in actual application scenarios, due to the increasing electrification of vehicles and the increasing number of vehicle functions, the communication link of the vehicle is very complex. When a vehicle function fails, due to the complexity of the communication link, fault diagnosis becomes difficult, and it is difficult to quickly locate and solve the problem, resulting in low fault diagnosis efficiency.

[0065] Based on this, the embodiments of the present application provide a vehicle function fault diagnosis method, device, vehicle, and storage medium, aiming to improve the efficiency of vehicle function fault diagnosis.

[0066] The vehicle function fault diagnosis method, device, vehicle, and storage medium provided by the embodiments of the present application are described in detail as follows. First, the vehicle function fault diagnosis method in the embodiments of the present application is described.

[0067] The vehicle function fault diagnosis method provided in the embodiments of the present application is applied to a vehicle-mounted system, and the vehicle-mounted system is provided with vehicle functions.

[0068] In some embodiments, the vehicle-mounted system is an electronic system on the vehicle, including but not limited to a central control head, a vehicle-mounted navigation system, an instrument display system, a side control system, a safety control system, and the like, without being limited thereto.

[0069] Among them, the vehicle function is provided in the vehicle-mounted system, and is used to realize various functions on the vehicle, including, for example, multimedia control, navigation control, vehicle safety control (ABS, TCS), tire pressure monitoring, and the like, without being limited thereto.

[0070] Specifically, the number of vehicle functions needs to be set according to the actual application scenario.

[0071] In the actual application scenario, the vehicle usually sets multiple vehicle functions, and the embodiments below are implemented under the condition that the number of vehicle functions is multiple.

[0072] Of course, the number of vehicle functions can also be one. If the number of vehicle functions is one, the specific implementation method of the steps provided in the following embodiments is the same, except that the number limit, such as "each", "all", "multiple", and the like, needs to be converted into one number for execution.

[0073] Figure 1 is an optional flowchart of the vehicle function fault diagnosis method provided in the embodiments of the present application, Figure 1 The method in the flowchart can include but is not limited to steps S101 to S105.

[0074] Step S101, generating a function information table based on vehicle functions;

[0075] Step S102, obtaining function interface information of the vehicle functions;

[0076] Step S103, obtaining function signal information of a preset function characteristic signal; wherein the function characteristic signal is a signal used to represent the vehicle function, and the function signal information is used to represent the attribute of the function characteristic signal;

[0077] Step S104, associating the function interface information, the function signal information and the function information table based on the vehicle functions to obtain a function mapping table;

[0078] Step S105, performing fault diagnosis on the vehicle functions based on the function mapping table to obtain a fault diagnosis report.

[0079] The steps S101 to S105 shown in the embodiments of the present application are as follows: generating a function information table based on vehicle functions; obtaining function interface information of the vehicle functions; obtaining function signal information of preset function characteristic signals; wherein the function characteristic signals are signals for characterizing the vehicle functions, and the function signal information is used to represent the attributes of the function characteristic signals; associating the function interface information, the function signal information and the function information table based on the vehicle functions to obtain a function mapping table; and performing fault diagnosis on the vehicle functions based on the function mapping table to obtain a fault diagnosis report. The vehicle functions can be monitored, analyzed and diagnosed to quickly find the functions with faults, thereby improving the fault diagnosis efficiency of the vehicle functions.

[0080] In some embodiments, the step S101 can include but is not limited to the following steps:

[0081] obtaining function definition information of the vehicle functions;

[0082] generating a function information table based on the function definition information.

[0083] It should be noted that the function definition information includes the function name, function description and input / output parameters of the vehicle functions.

[0084] The function information table is used to represent all vehicle functions required by a vehicle, and clear definition information is given for each vehicle function.

[0085] In some embodiments, if the number of vehicle functions is multiple, the step S101 can further include but is not limited to the following steps:

[0086] obtaining function definition information of each vehicle function;

[0087] generating a function information table based on the function definition information.

[0088] It should be noted that the function interface information in the step S102 is an API interface file developed by a technician in advance for each vehicle function, which is deployed in the API layer, thereby realizing the decoupling between the functions and components, improving the flexibility of the vehicle-mounted system and improving the reusability of the code.

[0089] In some embodiments, the function interface information can be the file name of the API interface file.

[0090] It should be noted that each vehicle function will have a function characteristic signal, i.e., an SOA signal, in the vehicle-mounted system, and the function signal information is the attribute of the SOA signal.

[0091] In some embodiments, the function signal information can be the name of the SOA signal, i.e., the name of the SOA signal in the vehicle system, specifically, the function signal information can be a code variable name, or an encoding of the SOA signal, without being limited thereto.

[0092] In some embodiments, for each vehicle function, the function information table, the function interface information, and the function signal information corresponding to the vehicle function are associated to obtain function mapping information of the vehicle function.

[0093] The function mapping information of all vehicle functions is merged to obtain a function mapping table.

[0094] In some embodiments, the function mapping table can also be obtained by directly merging the function definition information, the function interface information, and the function signal information of each vehicle function.

[0095] In some embodiments, the vehicle system includes communication configuration data, which is data used to configure the vehicle function.

[0096] Specifically, the communication configuration data is a file configured by the vehicle based on the function information table during development, and the configuration process is basic communication configuration. Therefore, the communication configuration data is an ARXML file of the basic communication configuration engineering model.

[0097] It should be noted that the ARXML file is an XML format file used in the AUTOSAR (Automotive Open System Architecture) standard, which is used to describe the communication configuration and software components in automotive electronic systems, including the parameter settings of ECU (Electronic Control Unit), communication interface definition, signal routing, and other information related to communication and configuration. The ARXML file serves to establish a unified standard for communication between automotive electronic control units and helps to achieve modular and reusable software design. Through the ARXML file, software and hardware from different manufacturers can work better together, thereby improving the integration performance and development efficiency of automotive electronic systems.

[0098] For details, please refer to Figure 2 In some embodiments, step S105 can include but is not limited to steps S201 to S202.

[0099] In step S201, the communication configuration data is verified based on the function mapping table to obtain a function configuration verification result.

[0100] Step S202, based on the function configuration verification result, the vehicle function is diagnosed to obtain a fault diagnosis report; wherein the fault diagnosis report is used to indicate that the vehicle function has a fault or the function is normal.

[0101] The steps S201 to S202 shown in the embodiment of the application, based on the function mapping table, the communication configuration data is verified to obtain the function configuration verification result, thereby realizing the verification of the ARXML file of the basic communication configuration engineering model, and then judging whether the vehicle function has a fault according to the verification result, and improving the fault diagnosis efficiency of the vehicle function.

[0102] In some embodiments, the communication configuration data includes a vehicle communication signal table, the vehicle communication signal table includes a plurality of vehicle function signals, the number of vehicle functions is at least two, each vehicle function signal corresponds to a vehicle function, and each vehicle function corresponds to a function signal information, and the function mapping table contains at least two function signal information.

[0103] It can be understood that the vehicle function recorded in the function mapping table can be understood as a planned vehicle function, and the vehicle function recorded in the communication configuration data corresponds to a specific function in the actual application scenario of the vehicle. Only when the vehicle function recorded in the communication configuration data and the vehicle function recorded in the function mapping table are the same in the name, definition, input and output parameters and other attributes of the SOA signal, the vehicle function can be called and normally used in the actual use of the vehicle.

[0104] In the above step S201, the "verification processing of the communication configuration data" phase mainly verifies whether the name of the SOA signal matches, and the rest such as definition, input and output parameters are verified in subsequent embodiments.

[0105] Please refer to Figure 3 In some embodiments, step S201 can include but is not limited to steps S301 to S302:

[0106] Step S301, for each function signal information in the function mapping table, signal matching is performed between the function signal information and the plurality of vehicle function signals in the vehicle communication signal table to obtain a signal matching result;

[0107] Step S302, for each function signal information, the signal matching result corresponding to the function signal information is counted to generate a function configuration verification result.

[0108] The steps S301 to S302 shown in the embodiments of the present application are to obtain a signal matching result by signal matching each function signal information in the function mapping table with the plurality of vehicle function signals in the vehicle communication signal table; to generate a function configuration verification result by counting the signal matching result corresponding to each function signal information, thereby completing the inspection of the vehicle function signals in the communication configuration data, and quickly finding out the signals in the communication configuration data that do not match the function mapping table, and improving the efficiency of vehicle function fault diagnosis.

[0109] It can be understood that the signals in the communication configuration data that do not match the function mapping table are specifically: the function signal information of a certain vehicle function recorded in the function mapping table is A, that is, the name of the SOA signal is A, and the communication configuration data corresponds to the vehicle-mounted system. It can be understood that in the actual application scenario, the name of the vehicle function may be named A.1 in the communication configuration data due to version update or other reasons, wherein ".1" may be a version number or other meaning. Therefore, during actual use of the vehicle, since the name "A.1" cannot be matched with "A", the vehicle function cannot be normally used, and a vehicle function fault occurs.

[0110] In step S301 of some embodiments, the signal matching result includes two cases: one is signal matching, and the other is signal mismatching.

[0111] Among them, the signal matching represents that: the vehicle function signal (SOA signal) recorded in the communication configuration data of a certain vehicle function is the same as the function signal information (SOA signal) recorded in the function mapping table in name, and has the basis of calling function.

[0112] The signal mismatching represents that: the vehicle function signal (SOA signal) recorded in the communication configuration data of a certain vehicle function is not the same as the function signal information (SOA signal) recorded in the function mapping table in name, and does not have the basis of calling function.

[0113] In step S302 of some embodiments, the signal matching result corresponding to each function signal information is counted, and it is counted how many function signal information are matched with the vehicle function signal and how many function signal information are not matched with the vehicle function signal, and the vehicle functions that are not matched are recorded at the same time, so as to improve the efficiency of vehicle function fault diagnosis.

[0114] In some embodiments, the function configuration verification result includes two cases: one is that the communication configuration data passes the verification, and the other is that the communication configuration data does not pass the verification.

[0115] Specifically, if there is a mismatch in the signal matching result, the function configuration verification result indicates that the communication configuration data fails to pass the verification; if there is no mismatch in the signal matching result, the function configuration verification result indicates that the communication configuration data passes the verification.

[0116] In some implementations, in the case where the function configuration verification result indicates that the communication configuration data fails to pass the verification, a fault diagnosis report is output, where the fault diagnosis report indicates that there is a fault in the vehicle function and the fault point is found in the communication configuration data verification link.

[0117] Specifically, the fault diagnosis report indicates which vehicle functions have faults, so that the technician can troubleshoot, saving diagnosis time and improving the fault diagnosis efficiency of the vehicle function.

[0118] It should be noted that only when the function configuration verification result indicates that the communication configuration data passes the verification, the subsequent verification processing is performed, because if the communication configuration data has an error, the subsequent verification processing will also be wrong, and thus it is the most efficient way to stop fault diagnosis and troubleshoot and repair the fault based on the function configuration verification result, which can improve the efficiency of vehicle function fault diagnosis.

[0119] In some embodiments, the vehicle-mounted system further includes a protocol stack.

[0120] Referring to Figure 4 In some embodiments, step S202 can include but is not limited to steps S401-S402:

[0121] Step S401, in the case where the function configuration verification result indicates that the communication configuration data passes the verification, the protocol stack is verified based on the function mapping table to obtain a protocol stack verification result;

[0122] Step S402, based on the function configuration verification result and the protocol stack verification result, the vehicle function is diagnosed for faults to obtain a fault diagnosis report.

[0123] The steps S401-S402 shown in the embodiments of the present application, in the case where the function configuration verification result indicates that the communication configuration data passes the verification, the protocol stack is verified based on the function mapping table to obtain a protocol stack verification result; based on the function configuration verification result and the protocol stack verification result, the vehicle function is diagnosed for faults, which can accurately find the fault point through step-by-step troubleshooting without repeated checking, thereby improving the diagnosis efficiency of the vehicle function fault.

[0124] Referring to Figure 5 In some embodiments, step S401 can further include but is not limited to steps S501-S503:

[0125] In step S501, stack data of a protocol stack is acquired; wherein the stack data contains a plurality of function service signal information;

[0126] In step S502, for each function signal information in the function mapping table, the function signal information is matched with the plurality of function service signal information in the stack data to obtain a matching result.

[0127] In step S503, the matching result corresponding to each function signal information is counted to obtain a protocol stack verification result.

[0128] The steps S501 to S503 shown in the embodiments of the present application match the plurality of function service signals contained in the stack data of the protocol stack with each function signal information in the function mapping table to ensure that each vehicle function can find the corresponding function service signal information in the protocol stack, thereby ensuring the consistency of the function mapping.

[0129] Meanwhile, when a vehicle function fails, the protocol stack can be checked to more effectively locate and solve the mismatching of the function service signal information in the protocol stack, thereby providing convenience for troubleshooting.

[0130] It can be understood that the function service signals contained in the stack data of the protocol stack are implemented based on a publish / subscribe model or other communication mechanisms, and communication and data interaction can be achieved by subscribing to the function service signals.

[0131] It should be noted that a certain function service signal contained in the stack data of the protocol stack corresponds to a vehicle function signal and also corresponds to function signal information, and the relationship is: vehicle function A-function signal information A-vehicle function signal A-function service signal A.

[0132] In addition, the number of function service signals contained in the stack data of the protocol stack is greater than the number of vehicle functions set in the vehicle-mounted system, and the function service signals can comprehensively cover the vehicle functions set in the vehicle-mounted system.

[0133] For example, if the number of vehicle functions is 100, then the number of function service signals contained in the stack data is at least 100, and may be 200.

[0134] In step S502 of some embodiments, the matching result includes two cases, one is information matching, and the other is information mismatching.

[0135] The information matching indicates that the function service signal (SOA signal) recorded in the stack data of the protocol stack for a certain vehicle function is the same as the function signal information (SOA signal) recorded in the function mapping table in name, which provides a basis for data communication and interaction.

[0136] Information mismatch representation: a vehicle function, the function service signal (SOA signal) recorded in the stack data of the protocol stack, and the function signal information (SOA signal) recorded in the function mapping table are not the same in name, and do not have the basis for data communication and interaction.

[0137] In step S503 of some embodiments, the information matching results corresponding to each function signal information are counted, and it is counted how many function signal information are matched with the function service signal and how many function signal information are not matched with the function service signal, and the vehicle functions that are not matched are recorded, which saves the diagnosis time and improves the fault diagnosis efficiency of the vehicle functions.

[0138] In some embodiments, the protocol stack verification result includes two cases, one is that the protocol stack passes the verification, and the other is that the protocol stack fails the verification.

[0139] Specifically, if there is a mismatch in the information matching result, the protocol stack verification result represents that the protocol stack fails the verification; if there is no mismatch in the information matching result, the protocol stack verification result represents that the protocol stack passes the verification.

[0140] In some embodiments, in the case where the protocol stack verification result represents that the protocol stack fails the verification, a fault diagnosis report is output, wherein the fault diagnosis report indicates that the vehicle function has a fault and finds the fault point in the protocol stack verification link.

[0141] Specifically, the fault diagnosis report will point out which vehicle functions have faults, so that the technician can troubleshoot, saving diagnosis time and improving the fault diagnosis efficiency of the vehicle functions.

[0142] It should be noted that only when the function configuration verification result represents that the communication configuration data passes the verification and the protocol stack verification result represents that the protocol stack passes the verification, the subsequent verification processing will be performed, because if the communication configuration data passes the verification but the protocol stack fails the verification, the subsequent verification processing will also be wrong, and thus stopping the fault diagnosis and troubleshooting and repairing the fault based on the protocol stack verification result is the most efficient way to improve the efficiency of vehicle function fault diagnosis.

[0143] Please refer to Figure 6 In some embodiments, step S402 includes but is not limited to steps S601 to S602:

[0144] Step S601, in the case that the function configuration verification result represents that the communication configuration data passes the verification, and the protocol stack verification result represents that the protocol stack passes the verification, interface information of a plurality of preset function interface files is verified based on the function mapping table and the vehicle communication signal table to obtain an interface verification result; wherein, the function interface file is configured in the vehicle-mounted system.

[0145] Step S602, vehicle functions are diagnosed based on the function configuration verification result, the protocol stack verification result and the interface verification result to obtain a fault diagnosis report.

[0146] The steps S601 to S602 shown in the embodiments of the present application, in the case that the function configuration verification result represents that the communication configuration data passes the verification, and the protocol stack verification result represents that the protocol stack passes the verification, interface information of a plurality of preset function interface files is verified based on the function mapping table and the vehicle communication signal table to obtain an interface verification result; wherein, the function interface file is configured in the vehicle-mounted system; vehicle functions are diagnosed based on the function configuration verification result, the protocol stack verification result and the interface verification result to obtain a fault diagnosis report. Through the step-by-step troubleshooting method, the fault point can be accurately found without repeated inspection, and the diagnosis efficiency of vehicle function faults is improved.

[0147] In some embodiments, the vehicle communication signal table further includes function definition information corresponding to a plurality of vehicle function signals.

[0148] It should be noted that the function definition information includes but is not limited to parameter type, value range, input and output parameters, etc.

[0149] Please refer to Figure 7 In some embodiments, step S601 can include but is not limited to steps S701 to S702:

[0150] Step S701, for each function interface file, the header file definition information of the function interface file is obtained, the vehicle function corresponding to the function interface file is determined based on the function mapping table, the function definition information is determined from the vehicle communication signal table based on the vehicle function corresponding to the function interface file, and the header file definition information and the function definition information are matched to obtain interface matching information.

[0151] Step S702, the interface matching information of each function interface file is used to generate an interface verification result.

[0152] The steps S701 to S702 shown in the embodiments of the present application obtain interface matching information by matching the header file definition information of the function interface file with the function definition information in the vehicle communication signal table, avoiding problems caused by inconsistent definition information, such as communication errors, function failures, and the like, helping to quickly find and solve differences or errors between function definition information, and improving the efficiency of vehicle function fault diagnosis.

[0153] It should be noted that the function interface file, that is, the API interface file, has a one-to-one correspondence with the vehicle function, that is, one vehicle function corresponds to one function interface file.

[0154] In addition, the function interface file is configured based on communication configuration data and recorded in the vehicle system, that is, the corresponding vehicle function can be realized by calling the function interface file.

[0155] It can be understood that the function interface file (API interface file) defines the attributes of related parameters in the header file, including parameter type, value range, input and output parameters, and the like, and constitutes the header file definition information, and in the API interface file development stage, the function definition information recorded in the vehicle communication signal table in the communication configuration data is configured, and there is a possibility of configuration error, so the potential problem needs to be investigated.

[0156] Therefore, the vehicle function corresponding to the function interface file can be determined through the function mapping table, and then the corresponding function definition information can be found from the vehicle communication signal table based on the vehicle function.

[0157] In step S701 of some embodiments, the interface matching information includes two cases, one is interface information matching, and the other is interface information mismatching.

[0158] The interface information matching represents that the header file definition information recorded in the function interface file corresponding to a vehicle function is the same as the function definition information recorded in the communication configuration data of the vehicle function, which means that the function interface file is configured accurately and correctly, thereby ensuring the accuracy and consistency of the system.

[0159] The interface information mismatching represents that the header file definition information recorded in the function interface file corresponding to a vehicle function is not the same as the function definition information recorded in the communication configuration data of the vehicle function, which means that the function interface file is configured with errors, which will affect the accuracy and consistency of the system.

[0160] In step S702 of some embodiments, the interface matching information of each function interface file is counted to obtain an interface verification result.

[0161] Specifically, the interface matching information of each function interface file is counted, and it is counted how many header file definition information recorded in the function interface file matches the function definition information recorded in the communication configuration data, and how many header file definition information recorded in the function interface file does not match the function definition information recorded in the communication configuration data, and the function interface file that does not match is recorded, which saves the diagnosis time and improves the fault diagnosis efficiency of the vehicle function.

[0162] In some embodiments, the interface verification result includes two cases, one is that all function interface files pass the verification, and the other is that there is a function interface file that does not pass the verification.

[0163] Specifically, if there is a mismatch in the interface matching information, the interface verification result indicates that there is a function interface file that does not pass the verification; if there is no mismatch in the interface matching information, the interface verification result indicates that all function interface files pass the verification.

[0164] In some embodiments, in the case where the interface verification result indicates that there is a function interface file that does not pass the verification, a fault diagnosis report is output, wherein the fault diagnosis report indicates that the vehicle function has a fault and the fault point is found in the function interface file verification link.

[0165] In other embodiments, in the case where the interface verification result indicates that all function interface files pass the verification, a fault diagnosis report is output, wherein the fault diagnosis report indicates that the vehicle function is normal, and no fault point is found in the communication configuration data verification link, the protocol stack verification link and the function interface file verification link.

[0166] It should be noted that if there is still some vehicle function failure in the case where the interface verification result indicates that all function interface files pass the verification, the technician needs to troubleshoot from other aspects other than the communication configuration data, the protocol stack and the function interface file. Since the operation of the technician cannot be automatically executed by the system, it is not within the scope of consideration of the embodiments of the present application.

[0167] It can be understood that in the embodiments of the present application, the communication configuration data of the vehicle-mounted system is verified, the protocol stack of the vehicle-mounted system is verified in the case where the communication configuration data passes the verification, and the function interface file is verified in the case where the protocol stack passes the verification. The communication link of the vehicle-mounted system is fully and completely checked in a step-by-step manner, which can accurately find the fault point without repeated checking, finally realizes the automation of vehicle fault diagnosis, and improves the diagnosis efficiency of vehicle function fault.

[0168] In a specific embodiment, the vehicle function fault diagnosis method is used to realize automatic diagnosis of vehicle faults, so as to comprehensively and completely check the communication link of the vehicle system. Specifically, the vehicle function fault diagnosis method is applied to the vehicle system, the vehicle system is provided with a plurality of vehicle functions, the vehicle system includes communication configuration data, the communication configuration data is data used to configure the vehicle functions, the communication configuration data includes a vehicle communication signal table, the vehicle communication signal table includes a plurality of vehicle function signals, and the vehicle system further includes a protocol stack;

[0169] The specific vehicle function fault diagnosis process is as follows:

[0170] Step 1,

[0171] Obtain the function definition information of each vehicle function, and generate a function information table based on the function definition information;

[0172] Obtain the function interface information of the vehicle function;

[0173] Obtain the function signal information of the preset function characteristic signal; wherein the function characteristic signal is a signal used to represent the vehicle function, and the function signal information is used to represent the attribute of the function characteristic signal;

[0174] Based on the vehicle function, the function interface information, the function signal information and the function information table are associated to obtain a function mapping table;

[0175] Step 2 is executed.

[0176] Step 2, the communication configuration data is checked, specifically as follows:

[0177] For each function signal information in the function mapping table, the function signal information is matched with the plurality of vehicle function signals in the vehicle communication signal table to obtain a signal matching result;

[0178] The signal matching result corresponding to each function signal information is counted to generate a function configuration check result;

[0179] Based on the function configuration check result, the vehicle function is diagnosed for faults,

[0180] In the case where the function configuration check result indicates that the communication configuration data fails the check, a fault diagnosis report is output, wherein the fault diagnosis report indicates that the vehicle function has a fault, and the function fault diagnosis process is exited;

[0181] In the case where the function configuration check result indicates that the communication configuration data passes the check, step 3 is executed.

[0182] Step 3, the protocol stack is checked, specifically as follows:

[0183] Obtaining stack data of the protocol stack; wherein the stack data contains a plurality of function service signal information and function definition information corresponding to the vehicle function signal;

[0184] For each function signal information in the function mapping table, the function signal information is matched with the plurality of function service signal information in the stack data to obtain an information matching result;

[0185] The information matching result corresponding to each function signal information is counted to obtain a protocol stack verification result;

[0186] Based on the function configuration verification result and the protocol stack verification result, the vehicle function is diagnosed for fault,

[0187] In the case that the protocol stack verification result represents that the protocol stack fails the verification, a fault diagnosis report is output, wherein the fault diagnosis report indicates that the vehicle function has a fault, and the function fault diagnosis process is exited;

[0188] In the case that the function configuration verification result represents that the communication configuration data passes the verification, and the protocol stack verification result represents that the protocol stack passes the verification, step 4 is performed.

[0189] Step 4, the function interface file is verified and processed, specifically as follows:

[0190] For each function interface file, the header file definition information of the function interface file is obtained, the vehicle function corresponding to the function interface file is determined based on the function mapping table, the function definition information is determined from the vehicle communication signal table based on the vehicle function corresponding to the function interface file, and the header file definition information and the function definition information are matched to obtain interface matching information;

[0191] The interface verification result is generated according to the interface matching information of each function interface file;

[0192] Based on the function configuration verification result, the protocol stack verification result and the interface verification result, the vehicle function is diagnosed for fault,

[0193] In the case that the interface verification result represents that there is a function interface file that fails the verification, a fault diagnosis report is output, wherein the fault diagnosis report indicates that the vehicle function has a fault, and the function fault diagnosis process is exited;

[0194] In the case that the interface verification result represents that all function interface files pass the verification, a fault diagnosis report is output, wherein the fault diagnosis report indicates that the vehicle function is normal, and the function fault diagnosis process is exited.

[0195] The communication configuration data of the vehicle-mounted system is verified in the embodiments of the present application, the protocol stack of the vehicle-mounted system is verified in the case that the communication configuration data passes the verification, the function interface file is verified in the case that the protocol stack passes the verification, the communication link of the vehicle-mounted system is fully and completely checked in a step-by-step manner, the fault point can be accurately found, repeated checking is not needed, the automation of vehicle fault diagnosis is finally realized, and the diagnosis efficiency of vehicle function faults is improved.

[0196] Please refer to Figure 8 The embodiments of the present application also provide a vehicle function fault diagnosis device, which can implement the vehicle function fault diagnosis method described above, and the device comprises:

[0197] A function information table generation module 801 is configured to generate a function information table based on vehicle functions.

[0198] A function interface information acquisition module 802 is configured to acquire function interface information of vehicle functions.

[0199] A function signal information acquisition module 803 is configured to acquire function signal information of preset function characteristic signals, wherein the function characteristic signals are signals used to represent vehicle functions, and the function signal information is used to represent the attributes of the function characteristic signals.

[0200] An information association module 804 is configured to associate the function interface information, the function signal information and the function information table based on vehicle functions to obtain a function mapping table.

[0201] A fault diagnosis module 805 is configured to perform fault diagnosis on vehicle functions based on the function mapping table to obtain a fault diagnosis report.

[0202] The specific embodiments of the vehicle function fault diagnosis device are basically the same as the specific embodiments of the vehicle function fault diagnosis method described above, and will not be described herein again.

[0203] The embodiments of the present application also provide a vehicle, which comprises a memory and a processor, the memory stores a computer program, and the processor implements the vehicle function fault diagnosis method described above when executing the computer program. The vehicle can be any intelligent terminal, such as a tablet computer or a vehicle-mounted computer.

[0204] Please refer to Figure 9 , Figure 9 The hardware structure of the vehicle of another embodiment is illustrated, and the vehicle comprises:

[0205] The processor 901 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits, and is configured to execute related programs to implement the technical solutions provided by the embodiments of the present application.

[0206] The memory 902 can be implemented by a ROM (ReadOnly Memory), a static storage device, a dynamic storage device, or a RAM (Random Access Memory), and the like. The memory 902 can store an operating system and other application programs, and when the technical solutions provided by the embodiments of the present application are implemented by software or firmware, the related program codes are stored in the memory 902 and called and executed by the processor 901 to implement the vehicle function fault diagnosis method of the embodiments of the present application.

[0207] The input / output interface 903 is configured to implement information input and output.

[0208] The communication interface 904 is configured to implement the communication interaction between the device and other devices, and can realize the communication through a wired manner (for example, a USB, a network cable, or the like) or a wireless manner (for example, a mobile network, WIFI, Bluetooth, or the like).

[0209] The bus 905 is configured to transmit information between various components (for example, the processor 901, the memory 902, the input / output interface 903, and the communication interface 904) of the device.

[0210] The processor 901, the memory 902, the input / output interface 903, and the communication interface 904 are connected to each other through the bus 905 to realize the communication connection between the device.

[0211] In some embodiments, the vehicle can be an oil vehicle or a new energy vehicle. When the vehicle is a new energy vehicle, it can be a hybrid vehicle or a pure electric vehicle.

[0212] The embodiments of the present application further provide a computer readable storage medium, which stores a computer program. The computer program is executed by a processor to implement the vehicle function fault diagnosis method.

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

[0214] The vehicle function fault diagnosis method and device, the vehicle, and the storage medium provided by the embodiments of the present application can generate a function information table based on a vehicle function, obtain function interface information of the vehicle function, and obtain function signal information of a preset function characteristic signal, wherein the function characteristic signal is a signal for representing the vehicle function, and the function signal information is used to represent the attribute of the function characteristic signal. The function interface information, the function signal information, and the function information table are associated based on the vehicle function to obtain a function mapping table. The vehicle function is diagnosed based on the function mapping table to obtain a fault diagnosis report. The embodiments of the present application can monitor, analyze, and diagnose the vehicle function to quickly find the function in a fault condition, thereby improving the fault diagnosis efficiency of the vehicle function.

[0215] In addition, the communication configuration data of the vehicle-mounted system is verified, the protocol stack of the vehicle-mounted system is verified in the case that the communication configuration data passes the verification, the function interface file is verified in the case that the protocol stack passes the verification, the communication link of the vehicle-mounted system is fully and completely checked in a step-by-step checking manner, the fault point can be accurately found without repeated checking, and finally the automation of vehicle fault diagnosis is realized, thereby improving the diagnosis efficiency of the vehicle function fault.

[0216] The embodiments described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. It can be understood by those skilled in the art that, with the evolution of technology and the appearance of new application scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0217] Those skilled in the art can understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and can include more or fewer steps than those shown in the figures, or combine certain steps or different steps.

[0218] The apparatus embodiments described above are merely exemplary, and the units described as separate units can or can not be physically separate, i.e., can be located in one place, or can be distributed over multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the embodiment.

[0219] Those skilled in the art can understand that all or some of the steps in the method disclosed above, the functional modules / units in the system and the device can be implemented as software, firmware, hardware and appropriate combinations thereof.

[0220] The terms "first", "second", "third", "fourth" and the like in the description of the application and in the claims of the foregoing drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the use of the terms so construed can be interchanged, such that the embodiments of the application described herein can be carried out in other than the order discussed herein without departing from the scope of the application. Further, the terms "comprise" and "comprising" and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, product or apparatus that comprises a list of steps or units does not necessarily comprise only those steps or units but can include other not expressly listed steps or units.

[0221] It should be understood that in the present application, "at least one" means one or more, and "multiple" means two or more. "And / or" is used to describe the relationship between the associated objects, which means that there can be three relationships, for example, "A and / or B" can mean that there are three cases: only A, only B, and A and B at the same time, where A and B can be singular or plural. The character " / " generally represents that the associated objects before and after are in an "or" relationship. "At least one of the following" or the like means any combination of these items, including any combination of single or multiple items. For example, at least one of a, b or c can mean a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0222] In several embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented by other manners. For example, the apparatus embodiments described above are merely illustrative, for example, the division of the above units is merely a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units or components shown or discussed can be indirect coupling or communication connection through some interfaces, apparatuses or units, and can be electrical, mechanical or other forms.

[0223] The units described above as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, i.e., they can be located in one place or distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0224] In addition, the functional units in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0225] If the integrated unit is realized in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the part of the prior art that makes a contribution or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, including a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method of each embodiment of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program storage media.

[0226] The preferred embodiments of the embodiments of the present application are described above with reference to the accompanying drawings, but this does not limit the scope of the embodiments of the present application. Any modifications, equivalent replacements and improvements made by those skilled in the art without departing from the scope and essence of the embodiments of the present application shall be within the scope of the embodiments of the present application.

Claims

1. A method for diagnosing vehicle functional faults, characterized in that, Applied to an in-vehicle system, the in-vehicle system having vehicle functions, the method includes: A function information table is generated based on the vehicle functions; Obtain the functional interface information of the vehicle functions; Acquire functional signal information of a preset functional characterization signal; wherein, the functional characterization signal is an SOA signal, the functional characterization signal is a signal used to characterize the vehicle function, and the functional signal information is used to represent the attributes of the functional characterization signal; Based on the vehicle functions, the function interface information, the function signal information, and the function information table are associated to obtain a function mapping table; Based on the function mapping table, fault diagnosis is performed on the vehicle functions to obtain a fault diagnosis report; The in-vehicle system includes communication configuration data, which is an ARXML file of a basic communication configuration engineering model. This communication configuration data is used to configure the vehicle's functions. The step of performing fault diagnosis on the vehicle's functions based on the function mapping table to obtain a fault diagnosis report includes: The communication configuration data is verified based on the function mapping table to obtain the function configuration verification result. Based on the function configuration verification results, the vehicle function is diagnosed to obtain the fault diagnosis report; wherein, the fault diagnosis report is used to indicate whether the vehicle function has a fault or is functioning normally; The communication configuration data includes a vehicle communication signal table, which includes multiple vehicle function signals. The number of vehicle functions is at least two, each vehicle function signal corresponds to one vehicle function, and each vehicle function corresponds to one function signal information. The function mapping table contains at least two function signal information. The step of verifying the communication configuration data based on the function mapping table to obtain a function configuration verification result includes: For each of the functional signal information in the functional mapping table, the functional signal information is matched with multiple vehicle functional signals in the vehicle communication signal table to obtain a signal matching result; The signal matching results corresponding to each of the aforementioned functional signal information are statistically analyzed to generate the functional configuration verification result.

2. The method according to claim 1, characterized in that, The in-vehicle system also includes a SOME / IP protocol stack. The fault diagnosis report obtained by performing fault diagnosis on the vehicle functions based on the function configuration verification results includes: If the function configuration verification result indicates that the communication configuration data has passed the verification, the SOME / IP protocol stack is verified based on the function mapping table to obtain the protocol stack verification result. Based on the function configuration verification results and the protocol stack verification results, the vehicle function is diagnosed for faults, and a fault diagnosis report is obtained.

3. The method according to claim 2, characterized in that, The verification process for the SOME / IP protocol stack based on the function mapping table, to obtain the protocol stack verification result, includes: Obtain the stack data of the SOME / IP protocol stack; wherein the stack data contains multiple functional service signal information; For each of the functional signal information in the functional mapping table, the functional signal information is matched with multiple functional service signal information in the stack data to obtain an information matching result; The information matching results corresponding to each of the aforementioned functional signal information are statistically analyzed to obtain the protocol stack verification result.

4. The method according to claim 2, characterized in that, The fault diagnosis of the vehicle function based on the function configuration verification result and the protocol stack verification result, and the resulting fault diagnosis report, includes: If the function configuration verification result indicates that the communication configuration data has passed verification, and the protocol stack verification result indicates that the SOME / IP protocol stack has passed verification, then based on the function mapping table and the vehicle communication signal table, the interface information of multiple preset API interface files is verified to obtain the interface verification result; wherein, the API interface files are configured in the vehicle system; Based on the function configuration verification results, the protocol stack verification results, and the interface verification results, fault diagnosis is performed on the vehicle functions to obtain the fault diagnosis report.

5. The method according to claim 3, characterized in that, The vehicle communication signal table also includes function definition information corresponding to multiple vehicle function signals. The step of verifying interface information of multiple preset API interface files based on the function mapping table and the vehicle communication signal table to obtain interface verification results includes: For each API interface file, obtain the header definition information of the API interface file, determine the vehicle function corresponding to the API interface file based on the function mapping table, determine the function definition information from the vehicle communication signal table based on the vehicle function corresponding to the API interface file, and match the header definition information and the function definition information to obtain interface matching information. The interface verification result is generated based on the interface matching information of each API interface file.

6. A vehicle functional fault diagnosis device, characterized in that, Applied to an in-vehicle system, the in-vehicle system having vehicle functions, the device includes: The function information table generation module is used to generate a function information table based on the vehicle functions. The function interface information acquisition module is used to acquire the function interface information of the vehicle function. A functional signal information acquisition module is used to acquire functional signal information of a preset functional characterization signal; wherein, the functional characterization signal is an SOA signal, the functional characterization signal is a signal used to characterize the vehicle function, and the functional signal information is used to represent the attributes of the functional characterization signal; The information association module is used to associate the function interface information, the function signal information and the function information table based on the vehicle function to obtain a function mapping table; The fault diagnosis module is used to perform fault diagnosis on the vehicle functions based on the function mapping table and obtain a fault diagnosis report. The in-vehicle system includes communication configuration data, which is an ARXML file of a basic communication configuration engineering model. This communication configuration data is used to configure the vehicle's functions. The step of performing fault diagnosis on the vehicle's functions based on the function mapping table to obtain a fault diagnosis report includes: The communication configuration data is verified based on the function mapping table to obtain the function configuration verification result. Based on the function configuration verification results, the vehicle function is diagnosed to obtain the fault diagnosis report; wherein, the fault diagnosis report is used to indicate whether the vehicle function has a fault or is functioning normally; The communication configuration data includes a vehicle communication signal table, which includes multiple vehicle function signals. The number of vehicle functions is at least two, each vehicle function signal corresponds to one vehicle function, and each vehicle function corresponds to one function signal information. The function mapping table contains at least two function signal information. The step of verifying the communication configuration data based on the function mapping table to obtain a function configuration verification result includes: For each of the functional signal information in the functional mapping table, the functional signal information is matched with multiple vehicle functional signals in the vehicle communication signal table to obtain a signal matching result; The signal matching results corresponding to each of the aforementioned functional signal information are statistically analyzed to generate the functional configuration verification result.

7. A vehicle, characterized in that, The vehicle includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the method according to any one of claims 1 to 5.

8. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method described in any one of claims 1 to 5.

Images