Remote fault monitoring method, system and device based on vehicle cloud and medium

Abstract

The invention provides a vehicle cloud-based remote fault monitoring method, system and device and a medium, and the method comprises the steps: transmitting a remote fault diagnosis starting request to a vehicle-mounted network terminal through a cloud, carrying out the vehicle condition inspection after receiving the request through a vehicle end, guaranteeing that a vehicle is in a safe state, and when the condition is satisfied, carrying out the remote fault diagnosis. The vehicle end sends a remote fault diagnosis starting instruction to a plurality of subordinate electronic control units, establishes a connection, activates a route, triggers each electronic control unit to execute fault diagnosis work, summarizes diagnosis feedback information, forwards the diagnosis feedback information to the cloud end through the vehicle-mounted network terminal for processing and analysis, and sends the diagnosis feedback information to the cloud end through the vehicle-mounted network terminal. And the cloud analyzes the received diagnosis feedback and presents a fault diagnosis result, so that remote monitoring of the vehicle fault is realized. Through the method, the vehicle health condition can be monitored in real time, and the fault detection efficiency and the vehicle safety are improved.

Description

Technical Field

[0001] The present application relates to the field of intelligent vehicle technology, and specifically to a vehicle-cloud-based remote fault monitoring method, system, device and medium. Background Art

[0002] With the rapid development of the automotive industry, modern vehicles have shifted from traditional mechanical structures to highly integrated electronic systems. This shift has brought many advantages, but also introduced new challenges, especially regarding vehicle fault diagnosis. Traditional fault diagnosis usually requires sending the vehicle to a professional repair station for inspection, which is not only time-consuming and inconvenient, but also difficult to detect potential problems in a timely manner. In addition, during vehicle software updates or maintenance, traditional diagnostic methods may be limited, affecting the accuracy and efficiency of diagnosis.

[0003] In recent years, with the advancement of Internet of Vehicles technology, remote fault diagnosis methods based on cloud services have gradually become a research hotspot. These methods allow remote access to the electronic control units (ECUs) of vehicles through wireless communication technology to achieve real-time monitoring of the vehicle's health status. However, existing remote fault diagnosis technologies still have some shortcomings, such as communication security during the diagnosis process and diagnostic adaptability of vehicles in special conditions. Summary of the invention

[0004] In view of the above-mentioned shortcomings of the prior art, the present application provides a vehicle-cloud-based remote fault monitoring method, system, device and medium to solve the above-mentioned technical problems.

[0005] The present application provides a vehicle-cloud-based remote fault monitoring method, the method comprising: in response to a remote fault diagnosis start request, sending a remote fault diagnosis start request instruction to an electronic control unit, the remote fault diagnosis start request is forwarded by the cloud through a vehicle network terminal, and there are multiple electronic control units; if the feedback result of the electronic control unit is a successful start, forwarding the remote fault diagnosis start success instruction to the cloud through the vehicle network terminal; establishing a communication connection with the electronic control unit and activating the route, and sending a remote fault diagnosis start instruction to the electronic control unit to trigger the electronic unit to perform fault diagnosis work and obtain diagnostic feedback; forwarding the diagnostic feedback to the cloud through the vehicle network terminal to remotely monitor the fault information of the vehicle, and the diagnostic feedback includes the fault diagnosis result of the vehicle.

[0006] In one embodiment of the present application, after sending a remote fault diagnosis start request instruction to the electronic control unit, it also includes: checking the current vehicle conditions, the inspection at least including checking the vehicle's OTA flashing status, checking the vehicle's OBD occupancy status, and checking the vehicle's cockpit self-test status; when the OTA flashing status is that there is no OTA update in progress, the OBD occupancy status is that no diagnostic tool is using the OBD interface, and the cockpit self-test status is that the vehicle cockpit is not in self-test status, it is determined that the vehicle condition inspection result meets the prerequisite for remote fault diagnosis, and a feedback result of successful startup is sent to the on-board network terminal.

[0007] In one embodiment of the present application, the diagnostic feedback is forwarded to the cloud via the vehicle-mounted network terminal, including: receiving the diagnostic feedback uploaded by the electronic control unit, the diagnostic feedback including fault information and alarm messages; logging into the cloud via the vehicle-mounted network terminal with the current configuration information of the vehicle; if the login is successful, uploading the diagnostic feedback to the cloud via the vehicle-mounted network terminal, so as to process the fault information and alarm information based on the cloud to obtain a conclusion of vehicle fault monitoring.

[0008] In one embodiment of the present application, the vehicle-cloud based remote fault monitoring method further includes: starting a local timer based on the remote fault diagnosis start instruction; when the vehicle condition inspection result does not meet the prerequisites for remote fault diagnosis, the vehicle side performs a fallback operation, disconnects the link, and generates a remote fault diagnosis close instruction; sends the remote fault diagnosis close instruction to the vehicle network terminal, so as to forward the remote fault diagnosis close instruction to the cloud based on the vehicle network terminal.

[0009] The present application provides a vehicle-cloud-based remote fault monitoring method, the method comprising: sending a remote fault diagnosis start request to a vehicle-mounted network terminal, and receiving a remote fault diagnosis start success instruction forwarded by the vehicle-mounted network terminal, the remote fault diagnosis start success instruction is sent by the vehicle after completing a vehicle condition inspection and confirming that a prerequisite for remote fault diagnosis is met; establishing a communication connection with a vehicle-side port and activating a route, and sending a diagnostic communication instruction to a vehicle-side control center to instruct the vehicle-side control center to establish a communication connection with an electronic control unit and activate a route; receiving diagnostic feedback from the electronic control unit to parse and present the remote fault diagnosis results, the diagnostic feedback including the vehicle's fault diagnosis results.

[0010] In one embodiment of the present application, the vehicle-cloud-based remote fault monitoring method also includes: starting a timer after sending a remote fault diagnosis start request; if no remote fault diagnosis start response is received within a preset time, sending a remote fault diagnosis close request to the vehicle network terminal to trigger the vehicle end to issue a remote fault diagnosis close instruction; receiving the remote fault diagnosis close instruction forwarded by the vehicle network terminal, and parsing the remote fault diagnosis close instruction to obtain the reason for the remote fault diagnosis close; updating the task status of the remote fault diagnosis to closed, and recording a log of the remote fault diagnosis close, the content of the log including the close time and reason.

[0011] The present application provides a vehicle-cloud-based remote fault monitoring method, the method comprising: receiving a remote fault diagnosis start request issued by the cloud, and converting the remote fault diagnosis start request into an intermediate instruction recognizable by the vehicle; sending the intermediate instruction to the vehicle, so that the vehicle performs a vehicle condition check based on the remote fault diagnosis start request, and generates a remote fault diagnosis start success instruction when the vehicle condition check result meets the prerequisite of remote fault diagnosis; receiving the remote fault diagnosis start success instruction and forwarding it to the cloud, so as to trigger the cloud to generate a diagnostic communication instruction, the diagnostic communication instruction is used to establish a connection with the vehicle side and activate the route; forwarding the diagnostic communication instruction to the vehicle side control center, so that the vehicle side control center establishes a communication connection with the electronic control unit based on the diagnostic communication instruction and activates the route; receiving the diagnostic results fed back by each electronic control unit, and sending the diagnostic results to the cloud, so as to realize remote fault monitoring of the vehicle.

[0012] The present application provides a vehicle-cloud-based remote fault monitoring system, the system comprising: a cloud, for sending a remote fault diagnosis start request to a vehicle network terminal, establishing a connection with a vehicle-side port and activating a route, parsing diagnostic feedback information uploaded from the vehicle side and displaying it, and sending a remote fault diagnosis shutdown request to the vehicle network terminal when a timer times out or a remote fault diagnosis shutdown instruction is received; the vehicle network terminal, for converting the remote fault diagnosis start request sent by the cloud into an intermediate instruction recognizable by the vehicle, and sending the intermediate instruction to the vehicle side, and forwarding the remote fault diagnosis start success instruction fed back by the vehicle to the cloud, and forwarding the remote fault diagnosis shutdown instruction to the cloud when receiving the remote fault diagnosis shutdown instruction; the vehicle side, for performing a vehicle condition check, sending a remote fault diagnosis start success instruction to the vehicle network terminal when the condition is met, establishing a communication connection with an electronic control unit and activating a route, and uploading diagnostic feedback information to the cloud; and performing a fallback operation when the condition is not met, disconnecting the link, and sending the remote fault diagnosis shutdown instruction to the vehicle network terminal.

[0013] The present application provides an electronic device, including a processor, a memory and a communication bus; the communication bus is used to connect the processor and the memory; the processor is used to execute a computer program stored in the memory to implement the vehicle-cloud-based remote fault monitoring method as described above.

[0014] The present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program is used to enable a computer to execute the vehicle-cloud-based remote fault monitoring method as described above.

[0015] Beneficial effects of the present application: In the vehicle-cloud-based remote fault monitoring method of the present application, the cloud sends a remote fault diagnosis start request to the vehicle side through the vehicle network terminal to start the fault diagnosis process; after receiving the remote fault diagnosis start request, the vehicle side first performs a series of condition checks to ensure that the vehicle is in a safe and reliable diagnostic environment; when the condition check is passed, the vehicle side sends a remote fault diagnosis start request instruction to multiple electronic control units related to the vehicle and establishes a diagnostic communication connection; then the electronic control unit performs the fault diagnosis work and feeds back the diagnostic results to the vehicle side, and finally the vehicle side summarizes the diagnostic results and forwards the diagnostic feedback to the cloud through the vehicle network terminal for further data analysis and processing. Fault diagnosis can be achieved in special states such as software updates or maintenance of the vehicle to ensure the accuracy and effectiveness of the diagnostic process. In addition, the diagnostic needs of the vehicle under different operating conditions are also taken into account, making fault diagnosis more flexible and efficient.

[0016] 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

[0017] 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:

[0018] Figure 1 is a schematic diagram of an implementation environment of a remote fault monitoring method based on a vehicle cloud according to an exemplary embodiment of the present application;

[0019] Figure 2 is a vehicle-side perspective flow chart of a vehicle-cloud-based remote fault monitoring method according to an exemplary embodiment of the present application;

[0020] Figure 3 is a schematic diagram of a vehicle-cloud-based remote fault monitoring system structure shown in an exemplary embodiment of the present application;

[0021] Figure 4 is a multi-terminal interaction flow chart of a remote fault monitoring method based on vehicle cloud, shown in an exemplary embodiment of the present application;

[0022] Figure 5 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

[0023] The following will describe the implementation methods of the present application with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific implementation methods, 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 application. It should be understood that the preferred embodiments are only for illustrating the present application, not for limiting the scope of protection of the present application.

[0024] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present application, and thus the drawings only show components related to the present application 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 at will, and the component layout may also be more complicated.

[0025] In the following description, a large number of details are discussed to provide a more thorough explanation of the embodiments of the present application. However, it is obvious to those skilled in the art that the embodiments of the present application 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 application difficult to understand.

[0026] First of all, it should be explained that VHR, "Vehicle Health Records or Vehicle History Records", is a technical solution that uses vehicle network signals and key ECU logs as data sources, and collects and processes data from the vehicle cloud to achieve vehicle monitoring, fault monitoring and other applications. The corresponding VHR technology is an indispensable part of vehicle network remote diagnosis, and can monitor the health of the vehicle in real time.

[0027] DID, "Data Identifier", is an identifier used to identify and obtain specific parameter data in the vehicle's electronic control unit (ECU).

[0028] DOIP, (Diagnostic communication over Internet Protocol) is an automotive diagnostic protocol based on TCP / IP, which allows diagnosis, programming and configuration of ECU (electronic control unit) over IP network.

[0029] The SOME / IP (Scalable service-oriented middleware over IP) instruction is a scalable service-oriented middleware communication instruction based on the TCP / IP protocol.

[0030] OTA, "Over-the-Air" means "over-the-air download", which mainly refers to a technology for remotely updating and upgrading the software and firmware of mobile terminal devices (such as smart phones, tablets, car systems, etc.) through the air interface of mobile communications (such as 2G, 3G, 4G, 5G).

[0031] Figure 1 It is a schematic diagram of the implementation environment of a vehicle-cloud-based remote fault monitoring method shown as an exemplary embodiment of the present application.

[0032] like Figure 1As shown, the implementation environment of the remote fault monitoring method based on the vehicle cloud includes a vehicle end 101, a vehicle network terminal 102 and a cloud 103. Among them, the vehicle end 101 refers to the electronic system inside the vehicle, including but not limited to multiple electronic control units (ECUs), which are responsible for different functions of the vehicle, such as engine management, braking system, transmission system, etc. The vehicle end 101 is responsible for receiving the remote fault diagnosis start request forwarded by the vehicle network terminal, and sending a remote fault diagnosis start request instruction to multiple electronic control units related to the vehicle. Once the remote fault diagnosis start success instruction feedback from the electronic control unit is received, the vehicle end 101 will forward this instruction to the cloud 103 through the vehicle network terminal. The vehicle network terminal 102 is a key component connecting the vehicle end 101 and the cloud 103. It can exchange data with the cloud through wireless communication technology (such as cellular network, Wi-Fi, etc.). The vehicle network terminal 102 is responsible for forwarding the remote fault diagnosis start request to the vehicle end 101 and forwarding the diagnostic feedback of the vehicle end 101 to the cloud 103. In addition, the vehicle network terminal 102 can also receive diagnostic communication instructions sent from the cloud and forward them to the vehicle end 101 to establish connections with multiple electronic control units and activate routing. The cloud 103 refers to a server cluster that integrates powerful computing power and data analysis capabilities. The cloud 103 is responsible for receiving remote fault diagnosis start requests and sending corresponding instructions to the vehicle end 101 through the vehicle network terminal 102. The cloud 103 is also responsible for receiving diagnostic feedback from the vehicle end 101 and analyzing and processing it to achieve remote monitoring of vehicle fault information. The cloud 103 can also perform further data analysis and processing based on the vehicle's fault diagnosis results, and even predict future fault trends, thereby providing guidance and suggestions for vehicle maintenance.

[0033] During the implementation of the remote fault monitoring method based on the vehicle cloud, the cloud 103 sends a remote fault diagnosis start request to the vehicle end 101 through the vehicle network terminal 102; then the vehicle end 101 receives the request, and sends a remote fault diagnosis start request instruction to the relevant electronic control unit, and establishes a diagnostic communication connection, so that each electronic control unit performs the fault diagnosis work and feeds back the diagnostic results to the vehicle end 101; finally, the vehicle end 101 forwards the diagnostic feedback to the cloud 103 through the vehicle network terminal 102 for remote fault monitoring and data analysis. It should be noted that in this implementation environment, the vehicle network terminal 102 can adopt various forms of hardware devices, such as a dedicated vehicle communication module or an intelligent gateway integrated in the vehicle; and the cloud 103 can be a high-performance server cluster, including but not limited to GPU computers, GPU computing clusters, neural network computers, etc., or it can be a cloud computing service provided by a third party. This application does not impose any restrictions on the specific implementation form of these devices.

[0034] Figure 2It is a vehicle-side perspective flowchart of a vehicle-cloud-based remote fault monitoring method shown as an exemplary embodiment of the present application.

[0035] like Figure 2 As shown, in an exemplary embodiment, the remote fault monitoring method based on the vehicle cloud includes at least steps S210 to S240, which are described in detail as follows:

[0036] Step S210, in response to the remote fault diagnosis start request, a remote fault diagnosis start request instruction is sent to the electronic control unit, the remote fault diagnosis start request is forwarded by the cloud through the vehicle network terminal, and there are multiple electronic control units.

[0037] In one embodiment of the present application, when the vehicle side (vehicle-side control center) receives a remote fault diagnosis start request forwarded by the vehicle network terminal (such as a T-box or other vehicle networking equipment), it is first necessary to verify the validity and security of the request. This includes at least verifying the validity of the request information and confirming the vehicle status. First, check whether the request comes from a legitimate remote server by verifying the message signature, serial number, etc., and ensure that the data format of the request is correct. If it is confirmed that the request comes from a legitimate remote server and the data format is correct, then further verify the vehicle status, such as the OTA upgrade status. When the request is verified to be valid and the vehicle is in a state that allows remote fault diagnosis, the vehicle side needs to establish a communication connection with each relevant electronic control unit (ECUs) and send a remote fault diagnosis start request instruction, which specifically includes establishing a communication link with ECUs through a diagnostic protocol (such as ISO 14229-1 / UDS) to ensure the security and reliability of data transmission, and using diagnostic services (such as Read DTCs, Clear DTCs, etc.) to send a remote fault diagnosis start request instruction to each ECU. The instruction contains a specific diagnostic session mode or test ID to instruct the ECU to enter the remote fault diagnosis mode.

[0038] In one embodiment of the present application, after sending a remote fault diagnosis start request instruction to the electronic control unit, it also includes: checking the current vehicle condition, the inspection at least includes checking the vehicle's OTA flashing status, checking the vehicle's OBD occupancy status, and checking the vehicle's cabin self-test status; when the OTA flashing status is that there is no OTA update in progress, the OBD occupancy status is that no diagnostic tool is using the OBD interface, and the cabin self-test status is that the vehicle cabin is not in self-test status, it is determined that the vehicle condition inspection result meets the prerequisite for remote fault diagnosis, and a remote fault diagnosis start success instruction is sent to the vehicle-mounted network terminal.

[0039] Step S220: If the feedback result of the electronic control unit is that the system is turned on successfully, the instruction indicating that the remote fault diagnosis is turned on successfully is forwarded to the cloud through the vehicle network terminal.

[0040] In one embodiment of the present application, first verify whether the received feedback comes from the correct ECUs and ensure the integrity of the feedback data; then, after confirming that all necessary ECUs have successfully entered the remote fault diagnosis mode and are ready, assemble the remote fault diagnosis successful activation instructions of all ECUs into a data packet, and convert the data packet into a SOME / IP instruction, and send the SOME / IP instruction to the vehicle network terminal through the in-vehicle network (such as CAN bus or Ethernet), and finally the vehicle network terminal converts the received SOME / IP instruction into an MQTT protocol message, and forwards the remote fault diagnosis successful activation instruction to the cloud through the Internet.

[0041] Step S230, establishing a communication connection with the electronic control unit and activating the route, and sending a remote fault diagnosis start instruction to the electronic control unit to trigger the electronic unit to perform fault diagnosis work and obtain diagnosis feedback.

[0042] In one embodiment of the present application, first, check whether the diagnostic communication instruction comes from a legitimate remote server, ensure that the data format of the instruction is correct, and confirm whether the vehicle is currently in a state that allows remote fault diagnosis, such as the vehicle cannot be in a driving state, or is performing other critical operations such as OTA updates. When the instruction is verified to be valid and the vehicle is in a state that allows remote fault diagnosis, a communication link with ECUs is established through a diagnostic protocol (such as ISO 14229-1 / UDS), and a network routing table is configured or a specific network interface is activated to ensure that data can reach the target ECU through the correct path. Then, a corresponding instruction is constructed according to the diagnostic request sent from the cloud, which at least contains a specific diagnostic session mode or test ID to instruct the ECU to enter the remote fault diagnosis mode, and a remote fault diagnosis start instruction is sent to each ECU using diagnostic services (such as Read DTCs, Clear DTCs, etc.) to ensure that the ECU can correctly identify and process these instructions. Finally, after the ECUs receive the remote fault diagnosis start command, the control ECUs perform corresponding fault detection according to the received command, including but not limited to reading fault codes and performing specific diagnostic tests, and the ECUs send the diagnostic results back to the vehicle-side control center, and the diagnostic results include but are not limited to fault codes, sensor readings and other information.

[0043] Step S240, forwarding the diagnostic feedback to the cloud via the vehicle network terminal to remotely monitor the vehicle's fault information, wherein the diagnostic feedback includes the vehicle's fault diagnosis results.

[0044] In one embodiment of the present application, it is first checked whether the diagnostic feedback comes from the correct ECUs. After confirming that all necessary ECUs have provided diagnostic results and that these results are valid, the diagnostic results of all ECUs are aggregated and the aggregated diagnostic results are formatted into a format that the cloud can understand; then, the diagnostic feedback data packet is converted into a SOME / IP instruction, and the SOME / IP instruction is sent to the vehicle network terminal through the in-vehicle network (such as CAN bus or Ethernet), so that the vehicle network terminal converts the received SOME / IP instruction into a message of the MQTT protocol and forwards the diagnostic feedback to the cloud through the Internet.

[0045] In one embodiment of the present application, the diagnostic feedback is forwarded to the cloud via the vehicle-mounted network terminal, including: receiving diagnostic feedback uploaded by the electronic control unit, the diagnostic feedback including fault information and alarm messages; logging into the cloud via the vehicle-mounted network terminal with the current configuration information of the vehicle; if the login is successful, uploading the diagnostic feedback to the cloud via the vehicle-mounted network terminal, so as to process the fault information and alarm information based on the cloud to obtain a conclusion of vehicle fault monitoring.

[0046] In one embodiment of the present application, the vehicle-side control center needs to assemble the received diagnostic results into a data packet, and obtain the current configuration information from the vehicle, including hardware configuration, software version, etc., use the vehicle network terminal to carry the vehicle configuration information to log in to the cloud, and verify the login credentials. Then, after the login is successful, the diagnostic feedback data packet is converted into a SOME / IP instruction, and the SOME / IP instruction is sent to the vehicle network terminal through the in-vehicle network (such as CAN bus or Ethernet), so that the vehicle network terminal converts the received SOME / IP instruction into a message of the MQTT protocol, and forwards the diagnostic feedback to the cloud through the Internet. After receiving the diagnostic feedback, the cloud parses the received diagnostic feedback data packet, extracts the fault information and warning messages therein, and uses the data analysis algorithm to perform fault analysis based on the received fault information and warning messages, and finally draws a conclusion on vehicle fault monitoring based on the analysis results, and takes corresponding measures as needed.

[0047] In one embodiment of the present application, the vehicle-cloud based remote fault monitoring method also includes: starting a local timer based on a remote fault diagnosis start instruction; when the vehicle condition inspection result does not meet the prerequisites for remote fault diagnosis, the vehicle side performs a fallback operation, disconnects the link, and generates a remote fault diagnosis close instruction; sends the remote fault diagnosis close instruction to the vehicle network terminal, so as to forward the remote fault diagnosis close instruction to the cloud based on the vehicle network terminal.

[0048] In one embodiment of the present application, the vehicle-cloud-based remote fault monitoring method also includes: starting a timer after sending a remote fault diagnosis start request; if no remote fault diagnosis start response is received within a preset time, sending a remote fault diagnosis close request to the vehicle network terminal to trigger the vehicle end to issue a remote fault diagnosis close instruction; receiving the remote fault diagnosis close instruction forwarded by the vehicle network terminal, and parsing the remote fault diagnosis close instruction to obtain the reason for the remote fault diagnosis close; updating the remote fault diagnosis task status to closed, and recording the log of the remote fault diagnosis close, the content of the log includes the close time and reason.

[0049] In a specific embodiment of the present application, when the vehicle-side control center receives the remote fault diagnosis start instruction issued by the cloud, it first checks whether the remote fault diagnosis start instruction is valid. Once the instruction is confirmed to be valid, the local timer is immediately started to monitor the duration and status of the remote fault diagnosis. Then, the vehicle-side control center determines whether the vehicle meets the conditions for remote fault diagnosis by checking whether the vehicle power is in the ON state, whether the network connection between the vehicle and the cloud is stable, whether all relevant ECUs are online and working normally, and whether the vehicle is in a stationary state and there is no critical operation in progress. If it is found that any of the inspection results do not meet the requirements, that is, it is determined that the vehicle does not meet the conditions for remote fault diagnosis, the connection between the vehicle and the cloud is immediately disconnected and a remote fault diagnosis shutdown instruction is generated. Once the remote fault diagnosis shutdown instruction is generated, the vehicle-side control center encapsulates the remote fault diagnosis shutdown instruction into an appropriate communication protocol, such as SOME / IP, and sends the encapsulated instruction to the vehicle network terminal through the in-vehicle network (such as CAN bus or Ethernet). After receiving the remote fault diagnosis shutdown instruction, the vehicle network terminal converts the received instruction into a format suitable for cloud reception, such as MQTT protocol, and sends the converted instruction to the cloud via the Internet. After receiving the remote fault diagnosis shutdown command, the cloud parses the received remote fault diagnosis shutdown command, extracts the information, updates the status of the vehicle remote fault diagnosis, and records the cause of the failure. In addition, the cloud can also send notifications to users or send alerts to maintenance service centers as needed.

[0050] Figure 3 This is a schematic diagram of the structure of a remote fault monitoring system based on vehicle cloud, which is an exemplary embodiment of the present application. Figure 1 The device may also be applicable to other exemplary implementation environments and specifically configured in other devices, and this embodiment does not limit the implementation environment to which the device is applicable.

[0051] The present application provides a vehicle-cloud-based remote fault monitoring method, which includes: sending a remote fault diagnosis start request to a vehicle-mounted network terminal, and receiving a remote fault diagnosis start success instruction forwarded by the vehicle-mounted network terminal, the remote fault diagnosis start success instruction is sent by the vehicle after completing the vehicle condition inspection and confirming that the prerequisites for remote fault diagnosis are met; establishing a communication connection with the vehicle-side port and activating the route, and sending a diagnostic communication instruction to the vehicle-side control center to instruct the vehicle-side control center to establish a communication connection with the electronic control unit and activate the route; receiving diagnostic feedback from the electronic control unit to parse and present the remote fault diagnosis results, the diagnostic feedback including the vehicle's fault diagnosis results.

[0052] The present application also provides a vehicle-cloud-based remote fault monitoring method, which includes: receiving a remote fault diagnosis start request issued by the cloud, and converting the remote fault diagnosis start request into an intermediate instruction recognizable by the vehicle; sending the intermediate instruction to the vehicle, so that the vehicle performs a vehicle condition check based on the remote fault diagnosis start request, and generates a remote fault diagnosis start success instruction when the vehicle condition check result meets the prerequisite of remote fault diagnosis; receiving the remote fault diagnosis start success instruction and forwarding it to the cloud to trigger the cloud to generate a diagnostic communication instruction, the diagnostic communication instruction is used to establish a connection with the vehicle side and activate the route; forwarding the diagnostic communication instruction to the vehicle side control center, so that the vehicle side control center establishes a communication connection and activates the route with the electronic control unit based on the diagnostic communication instruction; receiving the diagnostic results fed back by each electronic control unit, and sending the diagnostic results to the cloud to realize remote fault monitoring of the vehicle.

[0053] like Figure 3 As shown, the exemplary vehicle-cloud-based remote fault monitoring system includes: a cloud side, a vehicle-mounted network terminal, and a vehicle side.

[0054] Among them, the cloud side is used to send a remote fault diagnosis start request to the vehicle network terminal, establish a connection with the vehicle port and activate the route, parse the diagnostic feedback information uploaded from the vehicle and display it, and send a remote fault diagnosis shutdown request to the vehicle network terminal when the timer times out or a remote fault diagnosis shutdown command is received; the vehicle network terminal is used to convert the remote fault diagnosis start request sent by the cloud into an intermediate command recognizable by the vehicle, and send the intermediate command to the vehicle side, and forward the remote fault diagnosis start success command fed back by the vehicle to the cloud, and forward the remote fault diagnosis shutdown command to the cloud when receiving the remote fault diagnosis shutdown command; the vehicle side is used to perform vehicle condition checks, send a remote fault diagnosis start success command to the vehicle network terminal when the conditions are met, establish a communication connection with the electronic control unit and activate the route, and upload the diagnostic feedback information to the cloud; when the conditions are not met, a fallback operation is performed, the link is disconnected, and a remote fault diagnosis shutdown command is sent to the vehicle network terminal.

[0055] In one embodiment of the present application, Figure 3 As shown in the figure, the VHR cloud platform is regarded as the cloud, the vehicle-mounted network terminal is regarded as the vehicle-mounted network terminal, and the vehicle-side control center is regarded as the vehicle-side. Among them, the VHR cloud platform includes a remote diagnosis service platform and a remote fault monitoring service platform, which are mainly responsible for issuing remote diagnosis instructions to the vehicle-mounted network terminal and collecting and monitoring vehicle-side fault alarms in real time, and obtaining remote diagnosis instructions fed back by the vehicle-side. The vehicle-mounted network terminal is mainly responsible for converting the MQTT instructions issued by the remote diagnosis service platform into SOMEIP instructions and passing them to the diagnosis task management center of the vehicle-side control center. At the same time, it also forwards the fault information and alarm messages uploaded by the vehicle-side domain controller. The vehicle-side control center includes a diagnosis task management center, a diagnosis command filtering center and a diagnosis gateway, which are mainly responsible for coordinating the diagnosis needs of various electronic control units and controllers, and are also responsible for actively uploading the alarm messages of various domain controllers to the cloud. A remote fault monitoring method and diagnosis system based on the vehicle cloud VHR can mainly realize the following functions: VHR big data monitoring, online monitoring of fault alarms, remote online diagnosis of vehicle faults, remote online reading of vehicle data streams, and remote online clearing of vehicle faults.

[0056] In a specific embodiment of the present application, the remote fault diagnosis wake-up strategy, remote fault diagnosis on / off, remote fault diagnosis execution and remote fault monitoring are implemented through the above-mentioned vehicle-cloud-based remote fault monitoring system, and the specific contents are as follows:

[0057] First, the cloud uses the remote diagnosis service platform to send a remote fault diagnosis start request to the vehicle-mounted network terminal using the MQTT protocol, and then converts the start request command into a SOMEIP command and sends it to the vehicle. After receiving the remote fault diagnosis start request from the cloud, the vehicle needs to perform a vehicle condition check, such as whether the vehicle is in OTA flashing, whether it is in OBD occupancy, whether it is in the cockpit self-check state, etc. If the vehicle-side condition checks meet the requirements, the remote fault diagnosis start success command is fed back to the vehicle-mounted network terminal, and then forwarded to the cloud to start the remote fault diagnosis command;

[0058] Secondly, the cloud platform uses the cloud port and the vehicle port to use DOIP instructions to connect the link and activate the route. At the same time, the vehicle control center needs to establish the DOIP link and activate the route with multiple subordinate electronic control units through the diagnostic gateway;

[0059] Then, the vehicle-side control center receives the diagnostic request sent from the cloud and routes it to the corresponding electronic control unit node. The destination node executes the diagnostic request and replies with a positive or negative response, and uses the same routing path to feed back the diagnostic response to the cloud. The cloud platform then parses and presents the remote fault diagnosis results.

[0060] Then, after the vehicle control center receives the relevant configuration created by the cloud remote fault monitoring platform, the vehicle needs to carry the current configuration version of the vehicle when logging into the cloud and verify the configuration version with the cloud. After receiving the corresponding configuration and initializing the alarm-related master control service, the vehicle domain controller will filter and encapsulate its own fault information and alarm messages, upload them in real time, and the cloud will parse and display the alarm information.

[0061] Finally, both the cloud and the vehicle support shutting down remote fault monitoring and diagnosis tasks. After the cloud starts the remote fault diagnosis request, the cloud will start the timer. If the cloud does not receive the remote fault diagnosis start response within the specified time, the cloud will send a remote fault diagnosis shutdown request to the vehicle-mounted network terminal. After the vehicle receives the remote fault diagnosis start command, it will also start the local timer. If the vehicle-side conditions are not met, it will perform a rollback operation, disconnect the link, and send the remote fault diagnosis shutdown command to the vehicle-mounted network terminal and forward it to the cloud.

[0062] It should be noted that the vehicle-cloud-based remote fault monitoring device provided in the above embodiment and the vehicle-cloud-based remote fault monitoring 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 applications, the vehicle-cloud-based remote fault monitoring 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.

[0063] Figure 4 It is a multi-terminal interaction flow chart of a vehicle-cloud-based remote fault monitoring method shown as an exemplary embodiment of the present application.

[0064] like Figure 4 As shown, according to the above-mentioned vehicle-cloud-based remote fault monitoring system, remote fault monitoring and diagnosis are realized, and the specific steps are as follows:

[0065] Step 1: After the vehicle is awake and TBOX logs in to the cloud, a remote diagnosis start request is sent to the vehicle through the VHR cloud platform. At the same time, the vehicle-side start condition check and feedback of the cloud start result are sent;

[0066] Step 2: When the vehicle determines that the conditions are met to enable remote diagnosis, a successful enablement response is sent to the vehicle control center and the vehicle-mounted network terminal;

[0067] Step 3: After receiving the successful response from the vehicle, the VHR cloud platform sends a link establishment and routing activation request to the vehicle control center through the port DOIP command;

[0068] Step 4: After receiving the routing activation request and link establishment command, the vehicle control center sends a DOIP command to each electronic control unit through the diagnostic gateway to enable the remote diagnostic function;

[0069] Step 5: After the remote diagnosis function is turned on, the corresponding components on the vehicle start to detect faults and report them to the cloud through the corresponding protocol. At the same time, the cloud can monitor and analyze these fault information;

[0070] Step 6: After establishing a link and enabling remote fault diagnosis, the cloud and vehicle need to start their own timers. If the cloud timer, the cloud and vehicle support turning off remote diagnosis, the link will be disconnected.

[0071] It should be noted that the Cheyun VHR remote fault monitoring method and diagnostic system proposed in this application can shorten the distance between fault diagnosis and the actual vehicle, perform fault diagnosis and monitoring anytime and anywhere, have real-time and high efficiency, improve work efficiency, and save manpower and material costs for actual vehicle diagnosis. Moreover, the Cheyun VHR remote fault monitoring method and diagnostic system can use VHR big data to predict vehicle faults in advance, greatly reduce the probability of risk occurrence, and can also shorten maintenance time, increase user experience, and meet user vehicle comfort and safety. In addition, the Cheyun VHR remote fault monitoring method and diagnostic system provide more comprehensive functions, including not only fault code reading and display, but also vehicle alarm monitoring, clearing, and data flow analysis. It also has the ability to monitor and analyze vehicle VHR big data, which is more conducive to operation and maintenance personnel to conduct a comprehensive inspection of the vehicle.

[0072] 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 one or more processors, the electronic device implements the vehicle-cloud-based remote fault monitoring method provided in the above-mentioned embodiments.

[0073] Figure 5 The 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 5 The computer system 500 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.

[0074] like Figure 5As shown, the computer system 500 includes a central processing unit (CPU) 501, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 502 or the program loaded from the storage part 508 to the random access memory (RAM) 503, such as executing the method described in the above embodiment. In the RAM 503, various programs and data required for system operation are also stored. The CPU 501, the ROM 502 and the RAM 503 are connected to each other through the bus 504. The input / output (I / O) interface 505 is also connected to the bus 504.

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

[0076] 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, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 509, and / or installed from a removable medium 511. When the computer program is executed by a central processing unit (CPU) 501, various functions defined in the system of the present application are executed.

[0077] 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 may 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.

[0078] 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.

[0079] 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.

[0080] 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-cloud-based remote fault monitoring 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.

[0081] 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-cloud-based remote fault monitoring method provided in each of the above embodiments.

[0082] The above embodiments are merely illustrative of the principles and effects of the present application, and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. 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 in the present application shall still be covered by the claims of the present application.

Claims

1. A remote fault monitoring method based on vehicle cloud, characterized in that: The method comprises: In response to a remote fault diagnosis start request, sending a remote fault diagnosis start request instruction to an electronic control unit, wherein the remote fault diagnosis start request is forwarded by a cloud through an in-vehicle network terminal, and there are multiple electronic control units; If the feedback result of the electronic control unit is that the startup is successful, the remote fault diagnosis startup success instruction is forwarded to the cloud through the vehicle network terminal; Establishing a communication connection with the electronic control unit and activating a route, and sending a remote fault diagnosis start instruction to the electronic control unit to trigger the electronic unit to perform fault diagnosis work and obtain diagnostic feedback; The diagnostic feedback is forwarded to the cloud through the vehicle network terminal to remotely monitor the fault information of the vehicle, and the diagnostic feedback includes the fault diagnosis result of the vehicle.

2. The vehicle-cloud-based remote fault monitoring method according to claim 1 is characterized in that: After sending a remote fault diagnosis start request command to the electronic control unit, it also includes: Checking the current vehicle condition, wherein the checking at least includes checking the OTA flashing status of the vehicle, checking the OBD occupancy status of the vehicle, and checking the cockpit self-check status of the vehicle; When the OTA flashing status is that there is no OTA update in progress, the OBD occupation status is that no diagnostic tool is using the OBD interface, and the cockpit self-check status is that the vehicle cockpit is not in self-check status, it is determined that the vehicle condition inspection result meets the prerequisites for remote fault diagnosis, and a feedback result of successful startup is sent to the vehicle network terminal.

3. The vehicle-cloud-based remote fault monitoring method according to claim 1 is characterized in that: Forwarding the diagnostic feedback to the cloud via the vehicle network terminal includes: Receiving diagnostic feedback uploaded by the electronic control unit, the diagnostic feedback including fault information and warning messages; Log into the cloud with the vehicle's current configuration information through the vehicle network terminal; If the login is successful, the diagnostic feedback is uploaded to the cloud through the vehicle network terminal, so that the fault information and alarm information obtained are processed based on the cloud to obtain the conclusion of vehicle fault monitoring.

4. The vehicle-cloud-based remote fault monitoring method according to claim 2 is characterized in that: The method further comprises: Starting a local timer based on the remote fault diagnosis start instruction; When the vehicle condition check result does not meet the prerequisites for remote fault diagnosis, the vehicle side performs a rollback operation, disconnects the link, and generates a remote fault diagnosis shutdown instruction; The remote fault diagnosis shutdown instruction is sent to the vehicle network terminal, so that the remote fault diagnosis shutdown instruction is forwarded to the cloud based on the vehicle network terminal.

5. A remote fault monitoring method based on vehicle cloud, characterized in that: The method comprises: Sending a remote fault diagnosis start request to the vehicle network terminal, and receiving a remote fault diagnosis start success instruction forwarded by the vehicle network terminal, wherein the remote fault diagnosis start success instruction is sent after the vehicle completes the vehicle condition inspection and confirms that the prerequisite for remote fault diagnosis is met; Establish a communication connection with the vehicle-side port and activate the route, and send a diagnostic communication instruction to the vehicle-side control center to instruct the vehicle-side control center to establish a communication connection with the electronic control unit and activate the route; A diagnostic feedback is received from an electronic control unit to parse and present a remote fault diagnosis result, wherein the diagnostic feedback includes a fault diagnosis result of the vehicle.

6. The vehicle-cloud-based remote fault monitoring method according to claim 5 is characterized in that: The method further comprises: After sending a remote fault diagnosis start request, start the timer; If no remote fault diagnosis start response is received within the preset time, a remote fault diagnosis close request is sent to the vehicle network terminal to trigger the vehicle end to issue a remote fault diagnosis close instruction; Receiving a remote fault diagnosis shutdown instruction forwarded by the vehicle network terminal, and parsing the remote fault diagnosis shutdown instruction to obtain a reason for shutting down the remote fault diagnosis; The task status of the remote fault diagnosis is updated to closed, and a log of the remote fault diagnosis closing is recorded, wherein the content of the log includes the closing time and reason.

7. A remote fault monitoring method based on vehicle cloud, characterized in that: The method comprises: Receiving a remote fault diagnosis start request sent by the cloud, and converting the remote fault diagnosis start request into an intermediate instruction recognizable by the vehicle; sending the intermediate command to the vehicle so that the vehicle performs a vehicle condition check based on the remote fault diagnosis start request, and generating a remote fault diagnosis start success command when a vehicle condition check result satisfies a prerequisite for remote fault diagnosis; Receive the remote fault diagnosis start success instruction and forward it to the cloud to trigger the cloud to generate a diagnostic communication instruction, the diagnostic communication instruction is used to establish a connection with the vehicle end and activate routing; Forwarding the diagnostic communication instruction to the vehicle-side control center, so that the vehicle-side control center establishes a communication connection with the electronic control unit based on the diagnostic communication instruction and activates routing; Receive the diagnostic results fed back by each electronic control unit and send the diagnostic results to the cloud to achieve remote fault monitoring of the vehicle.

8. A remote fault monitoring system based on vehicle cloud, characterized in that: The system comprises: The cloud is used to send a remote fault diagnosis start request to the vehicle network terminal, establish a connection with the vehicle port and activate the route, parse the diagnostic feedback information uploaded from the vehicle and display it, and send a remote fault diagnosis close request to the vehicle network terminal when the timer times out or a remote fault diagnosis close command is received; The vehicle network terminal is used to convert the remote fault diagnosis start request sent by the cloud into an intermediate command recognizable by the vehicle, and send the intermediate command to the vehicle end, and forward the remote fault diagnosis start success command fed back by the vehicle to the cloud, and when receiving the remote fault diagnosis close command, forward the remote fault diagnosis close command to the cloud; The vehicle side is used to perform vehicle condition checks. When the conditions are met, a remote fault diagnosis startup instruction is sent to the vehicle network terminal, a communication connection is established with the electronic control unit, the routing is activated, and the diagnostic feedback information is uploaded to the cloud. When the conditions are not met, a fallback operation is performed, the link is disconnected, and a remote fault diagnosis shutdown instruction is sent to the vehicle network terminal.

9. An electronic device, characterized in that: It includes a processor, a memory and a communication bus; the communication bus is used to connect the processor and the memory; the processor is used to execute a computer program stored in the memory to implement the vehicle-cloud-based remote fault monitoring method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and the computer program is used to enable a computer to execute the vehicle-cloud-based remote fault monitoring method as described in any one of claims 1-7.

Images