Vehicle remote diagnosis management method, device, equipment and medium

Abstract

The present invention discloses a vehicle remote diagnosis management method, which subscribes to first fault diagnosis information and obtains second fault diagnosis information based on a bus through a first master node, and publishes the first fault diagnosis information and the second fault diagnosis information; based on a data distribution service, subscribes to the first fault diagnosis information and the second fault diagnosis information published by the first master node through a second master node; and sends the first fault diagnosis information and the second fault diagnosis information subscribed by the first master node and / or the second master node to a terminal device through the first master node and / or the second master node. The present invention combines the network system of the vehicle to diagnose various traditional faults on the vehicle, as well as diagnose abnormalities of various embedded controller hardware, systems, and applications, completes the complete vehicle diagnosis of traditional diagnosis and vehicle applications, and the remote PC terminal and the cloud vehicle diagnosis management, thereby improving the ability to diagnose vehicle faults.

Description

Technical Field

[0001] The present invention belongs to the technical field of automobile detection, and in particular relates to a whole vehicle remote diagnosis management method, device, equipment and medium. Background Art

[0002] Under the trend of software-defined cars, the intelligence of the entire vehicle is becoming higher and higher, the embedded controllers on the vehicle are becoming more and more complex, and the application software running is also diverse. In addition to traditional fault diagnosis, the fault information of the embedded controller hardware, system and application running on the vehicle is also becoming more and more complex.

[0003] When various traditional fault diagnoses on the whole vehicle and abnormalities occur in the hardware, systems, and applications of various embedded controllers and need to be diagnosed, how to combine the current network system of the whole vehicle to complete the complete diagnosis of traditional diagnosis and vehicle applications, and how to perform remote vehicle diagnosis management on the PC and cloud are issues that need to be urgently addressed. Summary of the invention

[0004] In view of the above-mentioned shortcomings of the prior art, the present invention provides a whole vehicle remote diagnosis management method, device, equipment and medium to solve the above-mentioned technical problems.

[0005] The present invention provides a vehicle remote diagnosis management method, wherein the vehicle includes a plurality of nodes, the plurality of nodes include a first master node, a second master node and a plurality of slave nodes, and the method includes:

[0006] Subscribe to first fault diagnosis information based on a data distribution service and obtain second fault diagnosis information based on a bus through the first master node, and publish the first fault diagnosis information and the second fault diagnosis information based on the data distribution service; wherein the first fault diagnosis information is collected by the first master node, the second master node, and the slave node and published based on the data distribution service, and the second fault diagnosis information is collected by the first master node, the second master node, and the slave node;

[0007] Based on the data distribution service, subscribing to the first fault diagnosis information and the second fault diagnosis information published by the first master node through the second master node;

[0008] The first fault diagnosis information and the second fault diagnosis information subscribed by the first master node and / or the second master node are sent to a terminal device through the first master node and / or the second master node.

[0009] In one embodiment of the present invention, the first fault diagnostic information includes an application fault diagnostic code, which is generated by an application associated with the first master node, the second master node, and the slave node; the second fault diagnostic information includes a traditional fault diagnostic code, which is generated by an entity associated with the first master node, the second master node, and the slave node.

[0010] In one embodiment of the present invention, the first master node includes:

[0011] A first conventional fault diagnosis component, configured to obtain a conventional fault diagnosis code generated by an entity associated with the first master node based on a UDS protocol of a CAN network;

[0012] A first application fault diagnosis component, used to obtain an application fault diagnosis code generated by an application associated with the first master node;

[0013] The first information subscription and publishing component is used to subscribe to the application fault diagnostic code collected by the first master node, the second master node, and the slave node and published based on the data distribution service and the traditional fault diagnostic code collected by the first master node, the second master node, and the slave node based on the bus based on the data distribution service, and to publish the traditional fault diagnostic code and the application fault diagnostic code.

[0014] In one embodiment of the present invention, the first traditional fault diagnosis component is further used to obtain a traditional fault diagnostic code generated by an entity associated with the first master node based on an in-vehicle Ethernet protocol.

[0015] In one embodiment of the present invention, the second master node includes:

[0016] A second conventional fault diagnosis component, configured to obtain a conventional fault diagnosis code generated by an entity associated with the second master node based on a UDS protocol of a CAN network;

[0017] A second application fault diagnosis component, used to obtain an application fault diagnosis code generated by an application associated with the second master node;

[0018] A second information subscription and publishing component is used to subscribe to the application fault diagnostic code and the traditional fault diagnostic code published by the first master node based on the data distribution service;

[0019] The remote connection component is used to connect to the cloud through OPENSSL two-way authentication, and uses the MQTT communication protocol to send the application fault diagnostic code and traditional fault diagnostic code subscribed by the second information subscription and publishing component to the cloud.

[0020] In one embodiment of the present invention, the slave node includes:

[0021] A third conventional fault diagnosis component, for acquiring a conventional fault diagnosis code generated by an entity associated with the slave node based on a UDS protocol of a CAN network;

[0022] A third application fault diagnosis component, used to obtain an application fault diagnosis code generated by an application associated with the slave node;

[0023] An information publishing component is used to publish the traditional fault diagnostic code and the application fault diagnostic code of the slave node based on a data distribution service.

[0024] In one embodiment of the present invention, the terminal device includes: a cloud terminal, a mobile terminal, and a PC terminal.

[0025] When the terminal device is a PC, the PC subscribes to the traditional fault diagnostic code and the application fault diagnostic code based on a data distribution service, and classifies, displays, and stores the traditional fault diagnostic code and the application fault diagnostic code;

[0026] When the terminal device is a cloud or mobile phone, the cloud connects to the second master node through OPENSSL two-way authentication, receives the traditional fault diagnostic code and the application fault diagnostic code subscribed by the second master node based on the MQTT communication protocol, and classifies, displays and stores the traditional fault diagnostic code and the application fault diagnostic code.

[0027] In one embodiment of the present invention, the method further includes:

[0028] When a failure occurs in the first master node, the application fault diagnostic code collected by the second master node and the slave node and published based on the data distribution service is subscribed to through the second master node.

[0029] In one embodiment of the present invention, the method further includes:

[0030] The traditional fault diagnostic code and the application fault diagnostic code received by the terminal device are compared with the fault diagnostic code table preset in the terminal device to obtain the current fault type of the vehicle; wherein the fault diagnostic code table is used to indicate the correspondence between the traditional fault diagnostic code and the fault type, and the correspondence between the application fault diagnostic code and the fault type.

[0031] The present invention provides a vehicle remote diagnosis management device, characterized in that the vehicle includes multiple nodes, the multiple nodes include a first master node, a second master node and multiple slave nodes, and the device includes:

[0032] A subscription and publishing module, used to subscribe to first fault diagnosis information based on a data distribution service and obtain second fault diagnosis information based on a bus through the first master node, and publish the first fault diagnosis information and the second fault diagnosis information based on the data distribution service; wherein the first fault diagnosis information is collected by the first master node, the second master node, and the slave node and published based on the data distribution service, and the second fault diagnosis information is collected by the first master node, the second master node, and the slave node based on the bus;

[0033] a subscription module, configured to subscribe to the first fault diagnosis information and the second fault diagnosis information published by the first master node through the second master node based on a data distribution service;

[0034] A sending module is used to send the first fault diagnosis information and the second fault diagnosis information subscribed by the first master node and / or the second master node to a terminal device through the first master node and / or the second master node.

[0035] The present invention provides an electronic device, comprising:

[0036] one or more processors;

[0037] A storage device is used to store one or more programs. When the one or more programs are executed by the one or more processors, the electronic device implements the steps of the above-mentioned vehicle remote diagnosis management method.

[0038] The present invention provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor of a computer, the computer executes the steps of the above-mentioned vehicle remote diagnosis management method.

[0039] Beneficial effects of the present invention: A whole vehicle remote diagnosis management method in the present invention comprises a plurality of nodes in the whole vehicle, the plurality of nodes comprising a first master node, a second master node and a plurality of slave nodes, the method comprising: through the first master node, subscribing to first fault diagnosis information based on a data distribution service and obtaining second fault diagnosis information based on a bus, and publishing the first fault diagnosis information and the second fault diagnosis information based on the data distribution service; wherein the first fault diagnosis information is collected by the first master node, the second master node and the slave node and published based on the data distribution service, and the second fault diagnosis information is collected by the first master node, the second master node and the slave node based on the bus; based on the data distribution service, subscribing to the first fault diagnosis information and the second fault diagnosis information published by the first master node through the second master node; through the first master node and / or the second master node, sending the first fault diagnosis information and the second fault diagnosis information subscribed by the first master node and / or the second master node to the terminal device. The present invention combines the network system of the whole vehicle to diagnose various traditional faults on the whole vehicle, as well as diagnose abnormalities in various embedded controller hardware, systems, and applications, completes traditional diagnosis and complete vehicle diagnosis of whole vehicle applications, as well as remote PC and cloud vehicle diagnosis management, thereby improving the ability to diagnose whole vehicle faults.

[0040] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0042] Figure 1 is a schematic diagram of an implementation environment of a vehicle remote diagnosis management method according to an exemplary embodiment of the present application;

[0043] Figure 2 is a flow chart of a vehicle remote diagnosis management method shown in an exemplary embodiment of the present application;

[0044] Figure 3 is a diagram showing the deployment of multiple nodes on a vehicle according to an exemplary embodiment of the present application;

[0045] Figure 4 is a schematic diagram of the composition of each node shown in an exemplary embodiment of the present application;

[0046] Figure 5 This is a schematic diagram of the composition of each node shown in an exemplary embodiment of the present application.

[0047] Figure 6 is a block diagram of a vehicle remote diagnosis management device shown in an exemplary embodiment of the present application;

[0048] Figure 7 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown. DETAILED DESCRIPTION

[0049] The following will describe the embodiments of the present invention with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention, not for limiting the scope of protection of the present invention.

[0050] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present invention, and thus the drawings only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0051] In the following description, numerous details are discussed to provide a more thorough explanation of the embodiments of the present invention. However, it is obvious to those skilled in the art that the embodiments of the present invention can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present invention difficult to understand.

[0052] Figure 1 This is a schematic diagram of an exemplary vehicle remote diagnosis management method implementation environment of this application. Figure 1, the implementation environment includes a terminal device 101 and a vehicle end 102, and the terminal device 101 and the server 102 communicate with each other through a wired or wireless network. The vehicle end subscribes to the first fault diagnosis information based on the data distribution service and obtains the second fault diagnosis information based on the bus through the first master node; wherein the first fault diagnosis information is collected by the first master node, the second master node, and the slave node and published based on the data distribution service, and the second fault diagnosis information is collected by the first master node, the second master node, and the slave node based on the bus; based on the data distribution service, the first fault diagnosis information and the second fault diagnosis information are published through the first master node; based on the data distribution service, the first fault diagnosis information and the second fault diagnosis information published by the first master node are subscribed through the second master node; through the first master node or / and the second master node, the first fault diagnosis information and the second fault diagnosis information subscribed by the first master node or / and the second master node are sent to the terminal device.

[0053] It should be understood that Figure 1 The number of terminal devices 101 and vehicle terminals 102 in the embodiment is only for illustration. Any number of terminal devices 101 and vehicle terminals 102 may be provided according to actual needs.

[0054] Among them, the terminal device 101 corresponds to the client, which can be any electronic device with a user input interface, including but not limited to smart phones, tablets, laptops, computers, car computers, etc., among which the user input interface includes but is not limited to touch screens, keyboards, physical buttons, audio pickup devices, etc.

[0055] Among them, the terminal device 101 can also be a server that provides various services. It can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network) and basic cloud computing services such as big data and artificial intelligence platforms. This is not restricted here.

[0056] The terminal device 101 can communicate with the server 102 through wireless networks such as 3G (third generation mobile information technology), 4G (fourth generation mobile information technology), and 5G (fifth generation mobile information technology), and this is not restricted here.

[0057] The embodiments of the present application respectively propose a whole vehicle remote diagnosis management method, a whole vehicle remote diagnosis management device, an electronic device, and a computer-readable storage medium, and these embodiments will be described in detail below.

[0058] See also Figure 2 , Figure 2 is a flowchart of a vehicle remote diagnosis management method shown in an exemplary embodiment of the present application. The method can be applied to Figure 1 The implementation environment shown is specifically executed by the terminal device 101 in the implementation environment. It should be understood that the method can also be applied to other exemplary implementation environments and be specifically executed by devices in other implementation environments. This embodiment does not limit the implementation environment to which the method is applicable.

[0059] See also Figure 2 , Figure 2 This is a flowchart of an exemplary vehicle remote diagnosis management method of the present application, wherein it can be understood that in the vehicle, each controller can be regarded as a node, and multiple controllers can be regarded as multiple nodes. The vehicle includes multiple nodes, and the multiple nodes include a first master node, a second master node, and multiple slave nodes. The vehicle remote diagnosis management method includes at least steps S210 to S230, which are described in detail as follows:

[0060] Step S210: subscribing to first fault diagnosis information based on a data distribution service and obtaining second fault diagnosis information based on a bus through the first master node, and publishing the first fault diagnosis information and the second fault diagnosis information based on the data distribution service; wherein the first fault diagnosis information is collected by the first master node, the second master node, and the slave node and published based on the data distribution service, and the second fault diagnosis information is collected by the first master node, the second master node, and the slave node based on the bus;

[0061] Step S220: based on the data distribution service, subscribing to the first fault diagnosis information and the second fault diagnosis information published by the first master node through the second master node;

[0062] Step S230: Send the first fault diagnosis information and the second fault diagnosis information subscribed by the first master node and / or the second master node to the terminal device through the first master node and / or the second master node.

[0063] The present invention combines the network system of the whole vehicle to diagnose various traditional faults on the whole vehicle, as well as diagnose abnormalities in various embedded controller hardware, systems, and applications, completes traditional diagnosis and complete vehicle diagnosis of whole vehicle applications, as well as remote PC and cloud vehicle diagnosis management, thereby improving the ability to diagnose whole vehicle faults.

[0064] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.

[0065] See also Figure 3 , Figure 3 FIG. 1 is a diagram showing the deployment of multiple nodes on a vehicle according to an exemplary embodiment of the present application. Figure 3 As shown, the vehicle includes nodes A, B, C, E, and F, wherein nodes A and B are embedded controllers running a system, and nodes C, D, E, and F are single-chip embedded controllers without a running system. The embedded controller with a system can be based on Qnx (Quick UNIX, real-time operating system), Linux, Android, single-chip, RTOS (Real Time Operating System, referred to as RTOS), autoSAR (CP) (AUTOmotive Open System Architecture, automotive open system architecture, CP means classic platform), autoSAR (AUTOmotive Open System Architecture, automotive open system architecture, AP means adaptive platform), single-chip, Windows, etc.

[0066] Embedded control A and embedded controller C can be integrated on the same hardware board to form a simple domain controller G. The single-chip embedded controller C can be connected to a traditional diagnostic instrument through ODB (OBD, On-Board Diagnostic); embedded control B and embedded controller D are integrated on the same hardware board to form a simple domain controller H. Embedded control B has a communication module connected to the public network and can remotely connect to the server. The server here can be a cloud server. The single-chip embedded controllers E and F without the system are used as separate controllers.

[0067] The following is a detailed description of each step of the above-mentioned vehicle remote diagnosis management method.

[0068] In step S210, the first fault diagnosis information is subscribed to based on the data distribution service and the second fault diagnosis information is obtained based on the bus through the first master node, and the first fault diagnosis information and the second fault diagnosis information are published based on the data distribution service; wherein the first fault diagnosis information is collected by the first master node, the second master node, and the slave node and published based on the data distribution service, and the second fault diagnosis information is collected by the first master node, the second master node, and the slave node based on the bus;

[0069] In one embodiment, the first fault diagnostic information includes an application fault diagnostic code, which is generated by an application associated with the first master node, the second master node, and the slave node; the second fault diagnostic information includes a traditional fault diagnostic code, which is generated by an entity associated with the first master node, the second master node, and the slave node.

[0070] In this embodiment, the entity may specifically refer to a hardware device controlled by a node (a first master node, a second master node, and multiple slave nodes). These hardware devices have the ability to self-diagnose, that is, the hardware itself can diagnose faults, and the diagnosis results will generate corresponding diagnostic codes, that is, traditional fault diagnostic codes. The application specifically refers to the operating system running on the node (the first master node, the second master node, and multiple slave nodes) and one or more APP applications (Application) running on the node. Traditional fault diagnostic codes include traditional fault diagnostic codes generated by hardware devices directly controlled by the first master node, traditional fault diagnostic codes generated by hardware devices directly controlled by the second master node, and traditional fault diagnostic codes generated by hardware devices directly controlled by the slave node; and the application fault diagnostic codes include application fault diagnostic codes generated by the APP running on the first master node, application fault diagnostic codes generated by the APP running on the second master node, and application fault diagnostic codes generated by the APP running on the slave node.

[0071] See also Figure 4 , 5 , Figure 4 This is a schematic diagram of the composition of each node shown in an exemplary embodiment of the present application. Figure 5 FIG. 1 is a schematic diagram showing the composition of each node according to an exemplary embodiment of the present application. Figure 4 , 5 As shown, the first master node includes: a first traditional fault diagnosis component, a first application fault diagnosis component and a first information subscription and publishing component;

[0072] a first conventional fault diagnosis component (SWC-DM), configured to obtain a conventional fault diagnosis code generated by an entity associated with the first master node based on a UDS protocol of a CAN network;

[0073] It should be noted that the traditional fault diagnostic code generated by the entity of the first master node may be the first traditional fault diagnostic code, which is generated when the hardware device directly controlled by the first master node diagnoses the fault when a fault occurs. After generating the first traditional fault diagnostic code, the hardware device sends the first traditional fault diagnostic code to the CAN network, and the first traditional fault diagnostic component (SWC-DM) obtains the first traditional fault diagnostic code on the CAN network through the UDS protocol of the CAN network.

[0074] a first application fault diagnosis component (SWC-DMclient), configured to obtain an application fault diagnosis code generated by an application associated with the first master node;

[0075] It should be noted that the application fault diagnostic code generated by the application on the first master node can be recorded as the first application fault diagnostic code. The first application fault diagnostic code belongs to the application fault diagnostic code and is generated when a fault occurs in the system or APP application running on the first master node.

[0076] Of course, in addition to collecting its own first traditional fault diagnostic code and first application fault diagnostic code, the first master node also collects first fault diagnostic information and second fault diagnostic information from the second master node and the slave node.

[0077] The first information subscription and publishing component (SWC-DMservice) is used to subscribe to the application fault diagnostic code collected by the first master node, the second master node, and the slave node and published based on the data distribution service, and the traditional fault diagnostic code collected by the first master node, the second master node, and the slave node based on the bus, based on the data distribution service, and to publish the traditional fault diagnostic code and the application fault diagnostic code.

[0078] In addition to collecting its own first traditional fault diagnostic code and first application fault diagnostic code, the first master node also subscribes to the first fault diagnostic information and the second fault diagnostic information of the second master node and the slave node through the first information subscription and publishing component DDS (DDS, Data Distribution Service) set on the first master node, so that the first master node obtains the first fault diagnostic information and the second fault diagnostic information of the first master node, the second master node, and the slave node.

[0079] In one embodiment, the first traditional fault diagnostic component is also used to obtain a traditional fault diagnostic code generated by an entity associated with the first main node based on the in-vehicle Ethernet protocol, and the second traditional fault diagnostic component is also used to obtain a traditional fault diagnostic code generated by an entity associated with the second main node based on the in-vehicle Ethernet protocol.

[0080] The DOIP (Diagnostic communication over Internet Protocol, based on vehicle-mounted Ethernet diagnosis) protocol stack is developed and deployed on embedded controller A and embedded controller B to complete the traditional diagnostic functions of Ethernet.

[0081] In one embodiment, the second master node includes: a second traditional fault diagnosis component, a second application fault diagnosis component, a second information subscription and publishing component, and a remote connection component;

[0082] a second conventional fault diagnosis component (SWC-DM), configured to obtain a conventional fault diagnosis code generated by an entity associated with the second master node based on a UDS protocol of a CAN network;

[0083] It should be noted that the traditional fault diagnostic code generated by the entity associated with the second main node can be recorded as the second traditional fault diagnostic code, which is generated when the hardware device directly controlled by the second main node diagnoses the fault when a fault occurs. After generating the second traditional fault diagnostic code, the hardware device sends the second traditional fault diagnostic code to the CAN network, and the second traditional fault diagnostic component (SWC-DM) obtains the second traditional fault diagnostic code on the CAN network through the UDS protocol of the CAN network.

[0084] a second application fault diagnosis component (SWC-DMclient), configured to obtain an application fault diagnosis code generated by an application associated with the second master node;

[0085] It should be noted that the application fault diagnostic code generated by the application of the second master node can be recorded as the second application fault diagnostic code, which is generated when a fault occurs in the system or APP application running on the second master node.

[0086] A second information subscription and publishing component (SWC-DMservice), configured to subscribe to application fault diagnostic codes and traditional fault diagnostic codes published by the first master node based on a data distribution service;

[0087] In addition to collecting its own second traditional fault diagnostic code and second application fault diagnostic code, the second master node also subscribes to the second traditional fault diagnostic code and second application fault diagnostic code of the first master node through DDS (DDS, Data Distribution Service) through the second information subscription and publishing component set on the second master node, so that the second master node obtains the traditional fault diagnostic code and application fault diagnostic code of the first master node and the slave node.

[0088] The remote connection component is used to connect to the cloud through OPENSSL two-way authentication, and uses the MQTT communication protocol to send the application fault diagnostic code and traditional fault diagnostic code subscribed by the second information subscription and publishing component to the cloud.

[0089] An application component connected to the remote cloud is developed and deployed on embedded controller B based on the MQTT communication protocol: SWC-DMpub. After the application component uses DDS to subscribe to the vehicle diagnostic information issued by SWC-DMservice, it first uses one vehicle one code (referring to the vehicle's unique VIN code) and OPENSSL two-way authentication to call the communication module to connect to the cloud server, and then uses the MQTT communication protocol to send the vehicle diagnostic information to the cloud.

[0090] In one embodiment, the slave node includes: a third traditional fault diagnosis component, a third application fault diagnosis component, and an information publishing component;

[0091] a third conventional fault diagnosis component (SWC-DM), configured to obtain a conventional fault diagnosis code generated by an entity associated with the slave node based on a UDS protocol of a CAN network;

[0092] It should be noted that the traditional fault diagnostic code generated by the entity of the slave node may be a third traditional fault diagnostic code. The third traditional fault diagnostic code is generated when a hardware device directly controlled by the slave node diagnoses the fault when a fault occurs. After generating the third traditional fault diagnostic code, the hardware device sends the third traditional fault diagnostic code to the CAN network. The third traditional fault diagnostic component (SWC-DM) obtains the third traditional fault diagnostic code on the CAN network through the UDS protocol of the CAN network.

[0093] a third application fault diagnosis component (SWC-DMclient), configured to obtain an application fault diagnosis code generated by an application associated with the slave node;

[0094] It should be noted that the application fault diagnostic code generated from the application on the node can be recorded as the third application fault diagnostic code. The third application fault diagnostic code belongs to the application fault diagnostic code and is generated when a fault occurs in the system or APP application running on the node.

[0095] An information publishing component is used to publish the traditional fault diagnostic code and the application fault diagnostic code of the slave node based on a data distribution service.

[0096] After the slave node collects its own third traditional fault diagnostic code and third application fault diagnostic code, they will be distributed through the information publishing component DDS (DDS, Data Distribution Service) set on the slave node, so that the first master node can subscribe to the traditional fault diagnostic code and application fault diagnostic code of the slave node.

[0097] In step S220, based on the data distribution service, subscribing to the first fault diagnosis information and the second fault diagnosis information published by the first master node through the second master node;

[0098] After the first master node obtains the traditional fault diagnostic codes and application fault diagnostic codes of the first master node, the second master node, and multiple slave nodes, the first master node will publish the obtained traditional fault diagnostic codes and application fault diagnostic codes of the first master node, the second master node, and multiple slave nodes through the data distribution service, and then the second master node will subscribe based on the data distribution service, so that the second master node can obtain the traditional fault diagnostic codes and application fault diagnostic codes of the first master node, the second master node, and multiple slave nodes obtained by the first master node.

[0099] In step S230, the first fault diagnosis information and the second fault diagnosis information subscribed by the first master node and / or the second master node are sent to a terminal device through the first master node and / or the second master node.

[0100] In one embodiment, the terminal device includes: a cloud terminal, a mobile terminal, and a PC terminal.

[0101] When the terminal device is a PC, the PC subscribes to the traditional fault diagnostic code and the application fault diagnostic code based on a data distribution service, and classifies, displays, and stores the traditional fault diagnostic code and the application fault diagnostic code;

[0102] When the terminal device is a cloud or mobile phone, the cloud connects to the second master node through OPENSSL two-way authentication, receives the traditional fault diagnostic code and the application fault diagnostic code subscribed by the second master node based on the MQTT communication protocol, and classifies, displays and stores the traditional fault diagnostic code and the application fault diagnostic code.

[0103] For the PC side, after subscribing through the PC subscription component SWC-DMsub, real-time visual classification display, storage, prompt corresponding processing and other unified management are carried out;

[0104] For the second main node, after the subscription component SWC-DMpub on the embedded controller B subscribes to the traditional fault diagnostic code and the application fault diagnostic code, it calls the communication module to publish it to the cloud using the MQTT protocol, and finally the cloud performs real-time visual classification display, storage, prompts for corresponding processing and other unified management.

[0105] In one embodiment, the method further comprises:

[0106] The traditional fault diagnostic code and the application fault diagnostic code received by the terminal device are compared with the fault diagnostic code table preset in the terminal device to obtain the current fault type of the vehicle; wherein the fault diagnostic code table is used to indicate the correspondence between the traditional fault diagnostic code and the fault type, and the correspondence between the application fault diagnostic code and the fault type.

[0107] A set of fault diagnostic code tables for the entire vehicle is pre-established in the terminal device. Based on the integration of traditional fault diagnosis, according to the actual situation of each, the following fields need to be included: controller identification, hardware identification, system version, diagnostic type (traditional fault diagnosis or application diagnosis), traditional fault diagnostic code, application error information diagnostic code, respective reserved diagnostic identification and other information. This diagnostic code table needs to be used for unified management on the vehicle side, PC side, and cloud side. After obtaining the corresponding fault diagnostic code (traditional fault diagnostic code and application fault diagnostic code), the corresponding fault diagnostic code is queried in the fault diagnostic code table to obtain the fault type corresponding to the fault diagnostic code, thereby realizing the diagnosis of the fault.

[0108] It should be noted that the first application fault diagnosis component, the second application fault diagnosis component and the third application fault diagnosis component are all client application components for collecting diagnostic information developed based on C language.

[0109] In one embodiment, the method further comprises:

[0110] When a fault occurs in the first master node, the second fault diagnosis information collected by the second master node and the slave node and published based on the data distribution service is subscribed to through the second master node.

[0111] If an abnormality occurs in embedded controller A, the corresponding redundant function application component will be started on embedded controller B to take over the function of SWC-DMservice and complete the diagnostic management of the entire vehicle.

[0112] Figure 6 is a block diagram of a vehicle remote diagnosis management device shown in an exemplary embodiment of the present application. The device can be applied to Figure 1The device can also be applied to other exemplary implementation environments and be specifically configured in other devices. This embodiment does not limit the implementation environment to which the device is applied.

[0113] like Figure 6 As shown, the present application provides a vehicle remote diagnosis management device, the vehicle includes multiple nodes, the multiple nodes include a first master node, a second master node and multiple slave nodes, the device includes:

[0114] The subscription and publishing module 610 is used to subscribe to the first fault diagnosis information based on the data distribution service and obtain the second fault diagnosis information based on the bus through the first master node, and publish the first fault diagnosis information and the second fault diagnosis information based on the data distribution service; wherein the first fault diagnosis information is collected by the first master node, the second master node, and the slave node and published based on the data distribution service, and the second fault diagnosis information is collected by the first master node, the second master node, and the slave node based on the bus;

[0115] A subscription module 620, configured to subscribe to the first fault diagnosis information and the second fault diagnosis information published by the first master node through the second master node based on a data distribution service;

[0116] The sending module 630 is used to send the first fault diagnosis information and the second fault diagnosis information subscribed by the first master node and / or the second master node to the terminal device through the first master node and / or the second master node.

[0117] It should be noted that the whole vehicle remote diagnosis management device provided in the above embodiment and the whole vehicle remote diagnosis management method provided in the above embodiment belong to the same concept, wherein the specific manner in which each module and unit performs the operation has been described in detail in the method embodiment, and will not be repeated here. In actual application, the whole vehicle remote diagnosis management device provided in the above embodiment can distribute the above functions to different functional modules as needed, that is, divide the internal structure of the device into different functional modules to complete all or part of the functions described above, and this is not limited here.

[0118] An embodiment of the present application also provides an electronic device, comprising: one or more processors; a storage device for storing one or more programs, and when the one or more programs are executed by the one or more processors, the electronic device implements the vehicle remote diagnosis and management method provided in the above-mentioned embodiments.

[0119] Figure 7The structure diagram of the computer system suitable for implementing the electronic device of the embodiment of the present application is shown. It should be noted that: Figure 7 The computer system 700 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0120] like Figure 7 As shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 702 or the program loaded from the storage part 708 to the random access memory (RAM) 703, such as executing the method described in the above embodiment. In the RAM 703, various programs and data required for system operation are also stored. The CPU 701, ROM 702 and RAM 703 are connected to each other through a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0121] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, a mouse, etc.; an output section 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 708 including a hard disk, etc.; and a communication section 707 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 707 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 710 as needed so that a computer program read therefrom is installed into the storage section 708 as needed.

[0122] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer readable medium, the computer program including a computer program for executing the process. Figure 2 In such an embodiment, the computer program may be downloaded and installed from a network via the communication section 709, and / or installed from a removable medium 711. When the computer program is executed by the central processing unit (CPU) 701, various functions defined in the system of the present application are performed.

[0123] It should be noted that the computer-readable medium shown in the embodiment of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable computer program is carried. This propagated data signal can take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. A computer program contained on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0124] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0125] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0126] Another aspect of the present application further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor of a computer, the computer executes the vehicle remote diagnosis management method as described above. The computer-readable storage medium may be included in the electronic device described in the above embodiment, or may exist independently without being assembled into the electronic device.

[0127] Another aspect of the present application also provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. A processor of a computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the vehicle remote diagnosis management method provided in each of the above embodiments.

[0128] The above embodiments are merely illustrative of the principles and effects of the present invention, and are not intended to limit the present invention. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present invention. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed by the present invention shall still be covered by the claims of the present invention.

Claims

1. A vehicle remote diagnosis and management method, characterized in that: The vehicle includes a plurality of nodes, the plurality of nodes including a first master node, a second master node and a plurality of slave nodes, and the method includes: Through the first master node, subscribe to the first fault diagnosis information based on the data distribution service and obtain the second fault diagnosis information based on the bus, and publish the first fault diagnosis information and the second fault diagnosis information based on the data distribution service; wherein the first fault diagnosis information is collected by the first master node, the second master node, and the slave node and published based on the data distribution service, and the second fault diagnosis information is collected by the first master node, the second master node, and the slave node; the first fault diagnosis information includes an application fault diagnosis code, which is generated by an application associated with the first master node, the second master node, and the slave node; the second fault diagnosis information includes a traditional fault diagnosis code, which is generated by an entity associated with the first master node, the second master node, and the slave node; Based on the data distribution service, subscribing to the first fault diagnosis information and the second fault diagnosis information published by the first master node through the second master node; The first fault diagnosis information and the second fault diagnosis information subscribed by the first master node and / or the second master node are sent to a terminal device through the first master node and / or the second master node.

2. The vehicle remote diagnosis management method according to claim 1, characterized in that: The first master node includes: A first conventional fault diagnosis component, configured to obtain a conventional fault diagnosis code generated by an entity associated with the first master node based on a UDS protocol of a CAN network; A first application fault diagnosis component, used to obtain an application fault diagnosis code generated by an application associated with the first master node; The first information subscription and publishing component is used to subscribe to the application fault diagnostic code collected by the first master node, the second master node, and the slave node and published based on the data distribution service and the traditional fault diagnostic code collected by the first master node, the second master node, and the slave node based on the bus based on the data distribution service, and to publish the traditional fault diagnostic code and the application fault diagnostic code.

3. The vehicle remote diagnosis management method according to claim 2, characterized in that: The first traditional fault diagnosis component is also used to obtain a traditional fault diagnostic code generated by an entity associated with the first master node based on the in-vehicle Ethernet protocol.

4. The vehicle remote diagnosis management method according to claim 3, characterized in that: The second master node includes: A second conventional fault diagnosis component, configured to obtain a conventional fault diagnosis code generated by an entity associated with the second master node based on a UDS protocol of a CAN network; A second application fault diagnosis component, used to obtain an application fault diagnosis code generated by an application associated with the second master node; A second information subscription and publishing component is used to subscribe to the application fault diagnostic code and the traditional fault diagnostic code published by the first master node based on the data distribution service; Remote connection component, used to connect to the cloud through OPENSSL two-way authentication, and adopts MQTT The communication protocol sends the application fault diagnostic code and the traditional fault diagnostic code subscribed by the second information subscription and publishing component to the cloud.

5. The vehicle remote diagnosis and management method according to claim 4, characterized in that: The slave node comprises: A third conventional fault diagnosis component, for acquiring a conventional fault diagnosis code generated by an entity associated with the slave node based on a UDS protocol of a CAN network; A third application fault diagnosis component, used to obtain an application fault diagnosis code generated by an application associated with the slave node; An information publishing component is used to publish the traditional fault diagnostic code and the application fault diagnostic code of the slave node based on a data distribution service.

6. The vehicle remote diagnosis management method according to claim 1, characterized in that: The terminal device includes: a cloud terminal, a mobile terminal, and a PC terminal. When the terminal device is a PC, the PC subscribes to the traditional fault diagnostic code and the application fault diagnostic code based on a data distribution service, and classifies, displays, and stores the traditional fault diagnostic code and the application fault diagnostic code; When the terminal device is a cloud or mobile phone, the cloud connects to the second master node through OPENSSL two-way authentication, receives the traditional fault diagnostic code and the application fault diagnostic code subscribed by the second master node based on the MQTT communication protocol, and classifies, displays and stores the traditional fault diagnostic code and the application fault diagnostic code.

7. The vehicle remote diagnosis and management method according to claim 1, characterized in that: The method further comprises: When a failure occurs in the first master node, the application fault diagnostic code collected by the second master node and the slave node and published based on the data distribution service is subscribed to through the second master node.

8. The vehicle remote diagnosis and management method according to claim 1, characterized in that: The method further comprises: The traditional fault diagnostic code and the application fault diagnostic code received by the terminal device are compared with the fault diagnostic code table preset in the terminal device to obtain the current fault type of the vehicle; wherein the fault diagnostic code table is used to indicate the correspondence between the traditional fault diagnostic code and the fault type, and the correspondence between the application fault diagnostic code and the fault type.

9. A vehicle remote diagnosis and management device, characterized in that: The vehicle includes a plurality of nodes, the plurality of nodes including a first master node, a second master node and a plurality of slave nodes, and the device includes: A subscription and publishing module, used to subscribe to first fault diagnosis information based on a data distribution service and obtain second fault diagnosis information based on a bus through the first master node, and publish the first fault diagnosis information and the second fault diagnosis information based on the data distribution service; wherein the first fault diagnosis information is collected by the first master node, the second master node, and the slave node and published based on the data distribution service, and the second fault diagnosis information is collected by the first master node, the second master node, and the slave node based on the bus; the first fault diagnosis information includes an application fault diagnosis code, which is generated by an application associated with the first master node, the second master node, and the slave node; the second fault diagnosis information includes a traditional fault diagnosis code, which is generated by an entity associated with the first master node, the second master node, and the slave node; a subscription module, configured to subscribe to the first fault diagnosis information and the second fault diagnosis information published by the first master node through the second master node based on a data distribution service; A sending module is used to send the first fault diagnosis information and the second fault diagnosis information subscribed by the first master node and / or the second master node to a terminal device through the first master node and / or the second master node.

10. An electronic device, characterized in that: The electronic device comprises: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the electronic device to implement the steps of the vehicle remote diagnosis management method as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a processor of a computer, the computer is caused to execute the steps of the vehicle remote diagnosis management method according to any one of claims 1 to 8.

Images