Vehicle communication fault processing method, system and device and medium
Patent Information
- Application Number
- CN202411027047.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-30
- Publication Date
- 2024-12-06
AI Technical Summary
The existing vehicle communication system cannot operate normally when the node fails, resulting in driving safety risks, especially in complex environments such as rainy days or nights, resulting in functions such as wipers and lights not being turned on normally.
By setting up a demand detection node, a master node and a function execution node between multiple communication nodes of the vehicle, the signal transmission and reception status is used to determine whether there is a communication failure, and send a function execution signal to the function execution node in the event of a failure to ensure the target function action Can be executed and meet the target functional requirements.
Even if there is a communication failure between nodes, the vehicle can still perform target function actions to avoid safety risks caused by communication failure and ensure driving safety.
Smart Images

Figure CN119094324A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of vehicle fault handling, and in particular, to a vehicle communication fault handling method, system, device and medium. Background Art
[0002] As cars gradually turn toward automation and intelligence, automotive electrical systems are becoming increasingly complex. More and more ECUs (Electronic Control Units) or sensors are being used in cars, and data exchange between ECUs is becoming increasingly complex. In existing vehicle communications, some normal functions often fail to operate due to a communication failure at a node in the communication link. For example, in rainy days, at night, etc., wipers and lights cannot be turned on normally due to a communication failure at a node, which greatly affects driving safety. There is a safety risk caused by a communication failure. Summary of the invention
[0003] The present application provides a vehicle communication fault processing method, system, device and medium, which can still execute target function actions to meet target function requirements when there is a communication failure between nodes, thereby avoiding the risk of driving safety caused by communication failure.
[0004] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.
[0005] According to one aspect of an embodiment of the present application, a vehicle communication fault processing method is provided, which is applied to a master node of multiple communication nodes of the vehicle, wherein the multiple communication nodes further include a demand detection node and a function execution node, and the demand detection node, the master node, and the function execution node are sequentially connected to form a communication link, and the method includes:
[0006] Determine whether there is a first communication failure with the demand detection node according to the signal receiving and sending state with the demand detection node, wherein, when the first communication failure occurs, a function request signal sent by the demand detection node cannot be normally received, and the function request signal is used to indicate that the vehicle has a target function requirement;
[0007] If the first communication failure exists, then in the case that the function request signal cannot be received normally, a function execution signal is still sent to the function execution node, so that the function execution node determines whether there is a second communication failure between the function execution node and the main node based on the signal receiving and sending status between the function execution node and the main node. If the second communication failure exists, then in the case that the function execution signal cannot be received normally, the target function action corresponding to the function execution signal is still executed to meet the target function requirement.
[0008] In one embodiment of the present application, based on the above solution, the demand detection node includes a data acquisition unit and a central domain controller, and determining whether there is a first communication failure with the demand detection node according to the signal transmission and reception status between the demand detection node and the demand detection node includes:
[0009] If a first message failure signal sent by the central domain controller is received, it is determined that the first communication failure exists with the central domain controller;
[0010] If the function request signal sent by the central domain controller is not received within the first preset time, it is determined that a timeout failure exists between the central domain controller and the master node, and it is determined that the first communication failure exists between the central domain controller and the master node;
[0011] Among them, the first message fault signal is used to indicate that the verification data obtained by the master node from the central domain controller has a first verification fault or a second verification fault; the function request signal is generated by the data acquisition unit according to the target function requirement and sent to the central domain controller.
[0012] In one embodiment of the present application, based on the above solution, the demand detection node includes a touch response node, and determining whether there is a first communication failure with the demand detection node according to the signal transmission and reception state between the demand detection node and the demand detection node includes:
[0013] If a second message fault signal sent by the touch response node is received, determining that the first communication fault exists with the touch response node;
[0014] If the function request signal sent by the touch response node is not received within the second preset time, it is determined that there is a timeout fault between the touch response node and the master node, and a detection signal is sent to the touch response node; if the feedback signal generated by the touch response node according to the detection signal is not received within the third preset time, it is determined that there is the first communication fault with the touch response node;
[0015] Among them, the second message fault signal is used to indicate that the verification data obtained by the master node from the touch response node has a first verification fault or a second verification fault; the function request signal is generated by the touch response node according to the target function requirement and sent to the master node.
[0016] In one embodiment of the present application, based on the above solution, whether the second communication failure exists between the master node and the function execution node is determined by the following method:
[0017] If the function execution node receives the third message fault signal sent by the master node, it is determined that the second communication fault exists between the master node and the function execution node;
[0018] If the function execution node does not receive the function execution signal sent by the master node within a fourth preset time, it is determined that the second communication failure exists between the function execution node and the master node;
[0019] The third message fault signal is used to indicate that the verification data obtained by the function execution node from the master node has a first verification fault or a second verification fault.
[0020] In one embodiment of the present application, based on the above solution, the verification data includes a verification code, and the first verification fault is determined by the following method:
[0021] If the verification code is inconsistent with a preset reference verification code, it is determined that the first verification failure exists.
[0022] In one embodiment of the present application, based on the aforementioned scheme, if the first verification failure exists between the data acquisition unit and the central domain controller, the central domain controller stops sending the function request signal to the master node, so that the master node still sends the function execution signal to the function execution node when it cannot receive the function request signal.
[0023] In one embodiment of the present application, based on the above scheme, the verification data includes a message count value, and the second verification fault is determined by the following method: if the message count value is inconsistent with a preset reference message count value, it is determined that the second verification fault exists
[0024] According to one aspect of an embodiment of the present application, a vehicle communication fault processing system is further provided, the system comprising the communication link described in the above embodiment, the communication link comprising a master node, a demand detection node and a function execution node; the demand detection node, the master node and the function execution node are sequentially connected to form the communication link;
[0025] The demand detection node is configured to send a function execution signal to the master node when detecting that the vehicle has a target function demand;
[0026] The master node is configured to determine whether there is a first communication failure between the master node and the demand detection node according to the signal receiving and sending status between the master node and the demand detection node, and when the first communication failure exists and the function execution signal cannot be received normally, the master node still sends a function execution signal to the function execution node;
[0027] The function execution node is configured to determine whether there is a second communication failure between the node and the main node based on the signal receiving and sending status between the node and the main node. When the second communication failure exists and the function execution signal cannot be received normally, the target function action corresponding to the function execution signal is still executed to meet the target function requirement.
[0028] According to one aspect of an embodiment of the present application, a vehicle communication fault processing device is provided, the device comprising: a master node applied to a plurality of communication nodes of the vehicle, the plurality of communication nodes further comprising a demand detection node and a function execution node, the demand detection node, the master node and the function execution node are sequentially connected to form a communication link, the device comprising:
[0029] a determining unit, configured to determine whether there is a first communication failure between the vehicle and the demand detection node according to a signal receiving and sending state between the vehicle and the demand detection node, wherein, when the first communication failure occurs, a function execution signal sent by the demand detection node cannot be normally received, and the function execution signal is used to indicate that the vehicle has a target function requirement;
[0030] A sending unit is used for sending a function execution signal to the function execution node even if the first communication failure exists and the function execution signal cannot be received normally, so that the function execution node can determine whether there is a second communication failure between the function execution node and the main node according to the signal receiving and sending status between the function execution node and the main node. If the second communication failure exists, the target function action corresponding to the function execution signal is still executed to meet the target function requirement even if the function execution signal cannot be received normally.
[0031] In one embodiment of the present application, based on the above solution, the demand detection node includes a data acquisition unit and a central domain controller, and the determination unit is configured to: if a first message fault signal sent by the central domain controller is received, determine that the first communication fault exists between the node and the central domain controller;
[0032] If the function request signal sent by the central domain controller is not received within the first preset time, it is determined that a timeout failure exists between the central domain controller and the master node, and it is determined that the first communication failure exists between the central domain controller and the master node;
[0033] Among them, the first message fault signal is used to indicate that the verification data obtained by the master node from the central domain controller has a first verification fault or a second verification fault; the function request signal is generated by the data acquisition unit according to the target function requirement and sent to the central domain controller.
[0034] In one embodiment of the present application, based on the above solution, the demand detection node includes a touch response node, and the determination unit may also be configured to: if a second message fault signal sent by the touch response node is received, determine that the first communication fault exists between the touch response node and the touch response node;
[0035] If the function request signal sent by the touch response node is not received within the second preset time, it is determined that there is a timeout fault between the touch response node and the master node, and a detection signal is sent to the touch response node; if the feedback signal generated by the touch response node according to the detection signal is not received within the third preset time, it is determined that there is the first communication fault with the touch response node;
[0036] Among them, the second message fault signal is used to indicate that the verification data obtained by the master node from the touch response node has a first verification fault or a second verification fault; the function request signal is generated by the touch response node according to the target function requirement and sent to the master node.
[0037] In one embodiment of the present application, based on the above solution, the determining unit is configured as follows: whether the second communication failure exists between the master node and the function execution node is determined by the following method:
[0038] If the function execution node receives the third message fault signal sent by the master node, it is determined that the second communication fault exists between the master node and the function execution node;
[0039] If the function execution node does not receive the function execution signal sent by the master node within a fourth preset time, it is determined that the second communication failure exists between the function execution node and the master node;
[0040] The third message fault signal is used to indicate that the verification data obtained by the function execution node from the master node has a first verification fault or a second verification fault.
[0041] In one embodiment of the present application, based on the above solution, the determination unit is configured as follows: the verification data includes a verification code, and the first verification fault is determined by the following method:
[0042] If the verification code is inconsistent with a preset reference verification code, it is determined that the first verification failure exists.
[0043] In one embodiment of the present application, based on the aforementioned scheme, the determination unit is configured as follows: if the first verification failure exists between the data acquisition unit and the central domain controller, the central domain controller stops sending the function request signal to the master node, so that the master node still sends the function execution signal to the function execution node when it cannot receive the function request signal.
[0044] In one embodiment of the present application, based on the aforementioned scheme, the determination unit is configured as follows: the verification data includes a message count value, and the second verification fault is determined by the following method: if the message count value is inconsistent with a preset reference message count value, it is determined that the second verification fault exists.
[0045] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which a computer program is stored. The computer program includes executable instructions. When the executable instructions are executed by a processor, the vehicle communication fault handling method described in the above embodiment is implemented.
[0046] In the technical solution of the embodiment of the present application, when the vehicle has a target demand function, it can be detected by the demand detection node and then a corresponding function request signal is generated and sent to the main node. When there is a first communication failure between the demand detection node and the main node, the main node cannot normally receive the function request signal sent by the demand detection node. At this time, the function execution signal is still sent to the function execution node, so that the function execution node can still execute the target function action corresponding to the function execution signal to meet the target function demand when there is a second communication failure between the function execution node and the main node and the function execution signal cannot be received normally.
[0047] The above method can ensure that when a vehicle has target function requirements, even if there is a communication failure between nodes, the function execution node can still execute the corresponding target function action to meet the target function requirements, thereby avoiding the safety risk caused by the failure to respond to the target function requirements due to communication failure.
[0048] 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
[0049] 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 ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:
[0050] Figure 1 It is a flow chart of a vehicle communication failure processing method according to an embodiment of the present application;
[0051] Figure 2 is a specific block diagram of a vehicle communication fault processing system according to an embodiment of the present application;
[0052] Figure 3 The block diagram of the vehicle communication fault processing device according to the embodiment of the present application is shown. DETAILED DESCRIPTION
[0053] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.
[0054] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the application.
[0055] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or micro-control node devices.
[0056] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.
[0057] It should be noted that the "multiple" mentioned in this article refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.
[0058] The implementation details of the technical solution of the embodiment of the present application are described in detail below:
[0059] First of all, it should be noted that the vehicle communication fault handling solution proposed in the embodiment of the present application can be applied to the relevant technical fields of vehicle fault handling. Each communication node is connected in sequence to form a corresponding communication link. In the embodiment of the present application, two different communication links can be used as examples for illustration, where one communication link can be formed by connecting a data acquisition unit, a central domain controller, a master node and a function execution node in sequence, wherein the data acquisition unit is an RLS (Recursive Least Square) module, the master node is a master controller, and the function execution node is a lighting control system. It should be noted that the lighting control system is only one type of function execution node. In other embodiments, the function execution node can also be a body domain control system, etc., which is not limited here.
[0060] Another communication link can be formed by connecting the touch response node, the main node and the function execution node in sequence, where the touch response node can be specifically a touch screen system, the main node can be the main controller of the vehicle, and the function execution node can also be a lighting control system. Figure 2 As shown, the lighting control system is composed of a front domain controller and a headlight system. Here, the front domain controller and the headlight system can be regarded as a whole, that is, a node for presentation.
[0061] The embodiment of the present application proposes a judgment mechanism between nodes to determine whether there is a communication failure, that is, an E2E (End to End) mechanism, which can also be understood as an end-to-end mechanism. In this way, it can be determined that the communication failure has occurred between the nodes in which part of the communication link, and then subsequent processing can be performed based on the identified fault, so that when the vehicle has the target function requirement, the demand will not be unresponsive due to some communication failure, thereby ensuring the safety of using the vehicle.
[0062] According to one aspect of the present application, a vehicle communication fault processing method is provided, which is applied to a master node of a plurality of communication nodes of the vehicle, wherein the plurality of communication nodes further include a demand detection node and a function execution node, wherein the demand detection node, the master node and the function execution node are sequentially connected to form a communication link; Figure 1 Flow chart of a vehicle communication fault processing method provided according to an embodiment of the present application, the vehicle communication fault processing method at least includes steps 110-120:
[0063] In step 110, based on the signal receiving and sending status between the demand detection node and the demand detection node, it is determined whether there is a first communication failure with the demand detection node, wherein, when the first communication failure occurs, the function request signal sent by the demand detection node cannot be received normally, and the function request signal is used to characterize that the vehicle has the target function requirement.
[0064] Specifically, according to the signal receiving and sending status between the demand detection node and the master node, that is, judging whether the master node can normally receive the function request signal sent by the demand detection node, the first communication failure is used to characterize that the master node cannot normally receive the function request signal sent by the demand detection node. At this time, the function request signal can be as follows Figure 2 The LIN bus signal of the low beam lighting request or the CAN bus signal of the low beam lighting request or the CAN bus signal of the lighting case status signal shown, but other forms of signals can be received, such as fault signals, error signals, etc. If the master node receives a fault signal or other forms of error signals, it means that the function request signal sent by the demand detection node cannot be received normally at this time.
[0065] In step 120, if the first communication failure exists, then even if the function request signal cannot be received normally, a function execution signal is still sent to the function execution node, so that the function execution node determines whether there is a second communication failure between the function execution node and the main node based on the signal receiving and sending status between the function execution node and the main node. If the second communication failure exists, then even if the function execution signal cannot be received normally, the target function action corresponding to the function execution signal is still executed to meet the target function requirement.
[0066] Specifically, if there is a first communication failure between the master node and the demand detection node, which makes the master node unable to normally receive the function request signal, in order to enable the target function demand to continue to be responded to, the function execution signal will continue to be sent to the function execution node to ensure that the function execution signal can be smoothly responded to by the function execution node through the communication link. If there is no communication failure between the master node and the function execution node, then of course the function execution node can respond to the function execution signal to execute the target function action corresponding to the function execution signal. However, if there is a second communication failure between the master node and the function execution node, the function execution node cannot normally receive the function execution signal. At this time, the function execution node itself will make a logical judgment, that is, if it receives the third message failure signal sent by the master node, the third message failure signal is used to characterize that the verification data obtained by the function execution node from the master node has a first verification failure or a second verification failure. At this time, the function execution node will still execute the target function action corresponding to the function execution signal, or the function execution node does not receive the function execution signal sent by the master node within the fourth preset time, and it will also execute the target function action corresponding to the function execution signal.
[0067] In one embodiment of the present application, the demand detection node includes a data acquisition unit and a central domain controller, and determining whether there is a first communication failure with the demand detection node according to a signal transceiver status with the demand detection node includes:
[0068] If a first message failure signal sent by the central domain controller is received, it is determined that the first communication failure exists with the central domain controller;
[0069] If the function request signal sent by the central domain controller is not received within the first preset time, it is determined that a timeout failure exists between the central domain controller and the master node, and it is determined that the first communication failure exists between the central domain controller and the master node;
[0070] Among them, the first message fault signal is used to indicate that the verification data obtained by the master node from the central domain controller has a first verification fault or a second verification fault; the function request signal is generated by the data acquisition unit according to the target function requirement and sent to the central domain controller.
[0071] In one embodiment of the present application, the verification data includes a verification code, and the first verification fault is determined by the following method:
[0072] If the verification code is inconsistent with the preset reference verification code, it is determined that the first verification fault exists;
[0073] If the first verification failure exists between the data acquisition unit and the central domain controller, the central domain controller stops sending the function request signal to the master node, so that the master node still sends the function execution signal to the function execution node when the master node cannot receive the function request signal;
[0074] The verification data includes a message count value, and the second verification fault is determined by the following method: if the message count value is inconsistent with a preset reference message count value, it is determined that the second verification fault exists.
[0075] Specifically, the communication link formed by the data acquisition unit, the central domain controller, the main node and the function execution node connected in sequence can be judged by the following judgment logic, which can be divided into three types of faults, namely the first check fault, the second check fault and the timeout fault mentioned in the embodiment of the present application; the first check fault is a CRC (Cyclic Redundancy Check) fault, which is a data transmission error detection technology commonly used in the field of data communication. The check code is calculated according to a certain algorithm for the data at the sending end (communication node), and the obtained check code is attached to the back of the data frame and sent together to the receiving end (communication node). The receiving end verifies the received data and the check code according to the same algorithm to determine whether the received data is correct and complete.
[0076] The second verification failure is a Rolling counter failure, that is, a message counting failure, that is, an error in the message counting value occurs during signal transmission, resulting in frame loss, which is also a communication failure.
[0077] A timeout fault (Time Out) means that no function execution signal is received within a certain preset time, which indicates that a corresponding communication fault has occurred.
[0078] The RLS module in the embodiment of the present application is used to sense the light brightness and rainfall amount of the vehicle's external environment. When the light brightness or rainfall amount reaches a certain threshold, the RLS module will generate a corresponding function request signal, that is, a LIN bus signal for requesting the low beam to be turned on. The central domain controller is used to convert the LIN bus signal sent by the RLS module into a CAN bus signal and send it to the main controller. The touch screen system is used to sense the user's manual operation and send the light button status signal to the main controller through the CAN bus. The main controller calculates the control state of the low beam according to the vehicle state and the received low beam lighting request signal and light button status signal, and outputs the low beam control signal through the CAN bus. The front domain controller directly routes the control signal of the main controller to the headlight system. The headlight system responds to the low beam state according to the control signal. In order to meet the functional safety requirements and ensure the integrity and correctness of the data interaction of the headlight function during operation, the following safety mechanism and corresponding fault handling strategy are designed for the data transmission link of the headlight to prevent unreasonable risks caused by the failure of the headlight communication link and improve the safety of the headlight function.
[0079] First, according to Figure 2 As shown in the figure, an E2E diagnostic mechanism and corresponding fault handling strategy are set between the RLS module and the central domain controller. The low beam lighting request signal sent by the RLS module supports the E2E diagnostic mechanism (CRC, Rolling counter, Time out). The central domain controller can diagnose the communication fault of the RLS low beam lighting request signal through the E2E diagnostic mechanism. After the fault is diagnosed, the processing strategy of the central domain controller is as follows:
[0080]
[0081]
[0082] Second, an E2E diagnostic mechanism and corresponding fault handling strategy are set between the central domain controller and the main controller. The low beam lighting request signal sent by the central domain controller supports the E2E diagnostic mechanism (CRC, Rolling counter, Time out). The main controller can diagnose the communication fault of the low beam lighting request signal sent by the central domain controller and RLS through the E2E diagnostic mechanism. After diagnosing the fault, the main controller's processing strategy is as follows:
[0083]
[0084] In one embodiment of the present application, the demand detection node includes a touch response node, and determining whether there is a first communication failure with the demand detection node according to a signal receiving and sending state between the demand detection node and the demand detection node includes:
[0085] If a second message fault signal sent by the touch response node is received, determining that the first communication fault exists with the touch response node;
[0086] If the function request signal sent by the touch response node is not received within the second preset time, it is determined that there is a timeout fault between the touch response node and the master node, and a detection signal is sent to the touch response node; if the feedback signal generated by the touch response node according to the detection signal is not received within the third preset time, it is determined that there is the first communication fault with the touch response node;
[0087] Among them, the second message fault signal is used to indicate that the verification data obtained by the master node from the touch response node has a first verification fault or a second verification fault; the function request signal is generated by the touch response node according to the target function requirement and sent to the master node.
[0088] In one embodiment of the present application, whether the second communication failure exists between the master node and the function execution node is determined by the following method:
[0089] If the function execution node receives the third message fault signal sent by the master node, it is determined that the second communication fault exists between the master node and the function execution node;
[0090] If the function execution node does not receive the function execution signal sent by the master node within a fourth preset time, it is determined that the second communication failure exists between the function execution node and the master node;
[0091] The third message fault signal is used to indicate that the verification data obtained by the function execution node from the master node has a first verification fault or a second verification fault.
[0092] Specifically, the first preset time, the second preset time, the third preset time and the fourth preset time can be set according to actual needs, and can be 0.5 seconds, 0.3 seconds, etc., and are not limited here. The following is an explanation of the communication link formed by connecting the touch response node, the main node and the function execution node in sequence:
[0093] First, set up an E2E diagnostic mechanism and corresponding fault handling strategy between the touch screen system and the main controller. The light button status signal sent by the touch screen system supports the E2E diagnostic mechanism (CRC, Rolling counter, Time out). The main controller can diagnose the communication fault of the light button status signal sent by the touch screen system through the E2E diagnostic mechanism. After diagnosing the fault, the main controller's handling strategy is as follows:
[0094]
[0095]
[0096] Second, set up an E2E diagnostic mechanism and corresponding fault handling strategy between the main controller and the headlight system. The low beam control signal sent by the main controller supports the E2E diagnostic mechanism (CRC, Rolling counter, Time out). The headlight system can use the E2E diagnostic mechanism to diagnose the fault sent by the main controller.
[0097] The communication failure of the low beam control signal. When the fault is diagnosed, the processing strategy of the headlight system is as follows:
[0098]
[0099] Specifically, by setting corresponding processing strategies at each node, when a communication failure is identified, the headlights can be turned on according to the corresponding processing strategy, that is, the target function requirement can be responded to, and then the target function action can be executed to meet the corresponding target function requirement.
[0100] To sum up, in the technical solution of the embodiment of the present application, when the vehicle has a target demand function, it can be detected by the demand detection node and then a corresponding function request signal is generated and sent to the main node. When there is a first communication failure between the demand detection node and the main node, the main node cannot normally receive the function request signal sent by the demand detection node. At this time, the function execution signal is still sent to the function execution node, so that the function execution node can still execute the target function action corresponding to the function execution signal to meet the target function demand when there is a second communication failure between the function execution node and the main node and the function execution signal cannot be received normally.
[0101] The above method can ensure that when a vehicle has target function requirements, even if there is a communication failure between nodes, the function execution node can still execute the corresponding target function action to meet the target function requirements, thereby avoiding the safety risk caused by the failure to respond to the target function requirements due to communication failure.
[0102] According to one aspect of an embodiment of the present application, a vehicle communication fault processing system is further provided, the system comprising the communication link described in the above embodiment, the communication link comprising a master node, a demand detection node and a function execution node; the demand detection node, the master node and the function execution node are sequentially connected to form the communication link;
[0103] The demand detection node is configured to send a function request signal to the master node when detecting that the vehicle has a target function demand;
[0104] The master node is configured to determine whether there is a first communication failure between the master node and the demand detection node according to the signal receiving and sending status between the master node and the demand detection node, and when the first communication failure exists and the function request signal cannot be received normally, the master node still sends a function execution signal to the function execution node;
[0105] The function execution node is configured to determine whether there is a second communication failure between the node and the main node based on the signal receiving and sending status between the node and the main node. When the second communication failure exists and the function execution signal cannot be received normally, the target function action corresponding to the function execution signal is still executed to meet the target function requirement.
[0106] Figure 3 This is a block diagram of a vehicle communication fault processing device 300 according to an embodiment of the present application. The vehicle communication fault processing device 300 according to an embodiment of the present application is applied to a main node of multiple communication nodes of the vehicle, and the multiple communication nodes also include a demand detection node and a function execution node. The demand detection node, the main node and the function execution node are connected in sequence to form a communication link. The device 300 includes: a determination unit 301 and a sending unit 302.
[0107] The determination unit 301 is used to determine whether there is a first communication failure between the vehicle and the demand detection node based on the signal reception and transmission status between the vehicle and the demand detection node, wherein, when the first communication failure occurs, the function request signal sent by the demand detection node cannot be received normally, and the function request signal is used to characterize that the vehicle has a target function requirement.
[0108] The sending unit 302 is used for sending a function execution signal to the function execution node even if the function request signal cannot be received normally when the first communication failure exists, so that the function execution node can determine whether there is a second communication failure between the function execution node and the main node according to the signal receiving and sending status between the function execution node and the main node. If the second communication failure exists, the target function action corresponding to the function execution signal is still executed to meet the target function requirement even if the function execution signal cannot be received normally.
[0109] In one embodiment of the present application, based on the above solution, the demand detection node includes a data acquisition unit and a central domain controller, and the determination unit is configured to: if a first message fault signal sent by the central domain controller is received, determine that the first communication fault exists between the node and the central domain controller;
[0110] If the function request signal sent by the central domain controller is not received within the first preset time, it is determined that a timeout failure exists between the central domain controller and the master node, and it is determined that the first communication failure exists between the central domain controller and the master node;
[0111] Among them, the first message fault signal is used to indicate that the verification data obtained by the master node from the central domain controller has a first verification fault or a second verification fault; the function request signal is generated by the data acquisition unit according to the target function requirement and sent to the central domain controller.
[0112] In one embodiment of the present application, based on the above solution, the demand detection node includes a touch response node, and the determination unit may also be configured to: if a second message fault signal sent by the touch response node is received, determine that the first communication fault exists between the touch response node and the touch response node;
[0113] If the function request signal sent by the touch response node is not received within the second preset time, it is determined that there is a timeout fault between the touch response node and the master node, and a detection signal is sent to the touch response node; if the feedback signal generated by the touch response node according to the detection signal is not received within the third preset time, it is determined that there is the first communication fault with the touch response node;
[0114] Among them, the second message fault signal is used to indicate that the verification data obtained by the master node from the touch response node has a first verification fault or a second verification fault; the function request signal is generated by the touch response node according to the target function requirement and sent to the master node.
[0115] In one embodiment of the present application, based on the above solution, the determining unit is configured as follows: whether the second communication failure exists between the master node and the function execution node is determined by the following method:
[0116] If the function execution node receives the third message fault signal sent by the master node, it is determined that the second communication fault exists between the master node and the function execution node;
[0117] If the function execution node does not receive the function execution signal sent by the master node within a fourth preset time, it is determined that the second communication failure exists between the function execution node and the master node;
[0118] The third message fault signal is used to indicate that the verification data obtained by the function execution node from the master node has a first verification fault or a second verification fault.
[0119] In one embodiment of the present application, based on the above solution, the determination unit is configured as follows: the verification data includes a verification code, and the first verification fault is determined by the following method:
[0120] If the verification code is inconsistent with a preset reference verification code, it is determined that the first verification failure exists.
[0121] In one embodiment of the present application, based on the aforementioned scheme, the determination unit is configured as follows: if the first verification failure exists between the data acquisition unit and the central domain controller, the central domain controller stops sending the function request signal to the master node, so that the master node still sends the function execution signal to the function execution node when it cannot receive the function request signal.
[0122] In one embodiment of the present application, based on the aforementioned scheme, the determination unit is configured as follows: the verification data includes a message count value, and the second verification fault is determined by the following method: if the message count value is inconsistent with a preset reference message count value, it is determined that the second verification fault exists.
[0123] As another aspect, the present application further provides a computer-readable storage medium on which a program product capable of implementing the method provided above in this specification is stored. In some possible implementations, various aspects of the present application may also be implemented in the form of a program product, which includes a program code, and when the program product is run on a terminal device, the program code is used to cause the terminal device to execute the steps according to various exemplary implementations of the present application described in the above "Embodiment Method" section of this specification.
[0124] According to the program product for implementing the above method in the embodiment of the present application, it can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product of the present application is not limited thereto. In this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus or a device.
[0125] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or 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.
[0126] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a 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.
[0127] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.
[0128] Program code for performing the operations of the present application may be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C++, etc., and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).
[0129] In addition, the above-mentioned figures are only schematic illustrations of the processes included in the method according to the exemplary embodiments of the present application, and are not intended to be limiting. It is easy to understand that the processes shown in the above-mentioned figures do not indicate or limit the time sequence of these processes. In addition, it is also easy to understand that these processes can be performed synchronously or asynchronously, for example, in multiple modules.
[0130] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be performed without departing from the scope thereof. The scope of the present application is limited only by the appended claims.
Claims
1. A vehicle communication fault processing method, characterized in that: A master node applied to a plurality of communication nodes of the vehicle, the plurality of communication nodes further comprising a demand detection node and a function execution node, the demand detection node, the master node and the function execution node are sequentially connected to form a communication link, the method comprising: Determine whether there is a first communication failure with the demand detection node according to the signal receiving and sending state with the demand detection node, wherein, when the first communication failure occurs, a function request signal sent by the demand detection node cannot be normally received, and the function request signal is used to indicate that the vehicle has a target function requirement; If the first communication failure exists, then in the case that the function request signal cannot be received normally, a function execution signal is still sent to the function execution node, so that the function execution node determines whether there is a second communication failure between the function execution node and the main node based on the signal receiving and sending status between the function execution node and the main node. If the second communication failure exists, then in the case that the function execution signal cannot be received normally, the target function action corresponding to the function execution signal is still executed to meet the target function requirement.
2. The method according to claim 1, characterized in that The demand detection node includes a data acquisition unit and a central domain controller, and determining whether there is a first communication failure with the demand detection node according to a signal receiving and sending state between the demand detection node and the demand detection node includes: If a first message failure signal sent by the central domain controller is received, it is determined that the first communication failure exists with the central domain controller; If the function request signal sent by the central domain controller is not received within the first preset time, it is determined that a timeout failure exists between the central domain controller and the master node, and it is determined that the first communication failure exists between the central domain controller and the master node; Among them, the first message fault signal is used to indicate that the verification data obtained by the master node from the central domain controller has a first verification fault or a second verification fault; the function request signal is generated by the data acquisition unit according to the target function requirement and sent to the central domain controller.
3. The method according to claim 1, characterized in that: The demand detection node includes a touch response node, and determining whether there is a first communication failure with the demand detection node according to a signal receiving and sending state between the demand detection node and the demand detection node includes: If a second message fault signal sent by the touch response node is received, determining that the first communication fault exists with the touch response node; If the function request signal sent by the touch response node is not received within the second preset time, it is determined that there is a timeout fault between the touch response node and the master node, and a detection signal is sent to the touch response node; if the feedback signal generated by the touch response node according to the detection signal is not received within the third preset time, it is determined that there is the first communication fault with the touch response node; Among them, the second message fault signal is used to indicate that the verification data obtained by the master node from the touch response node has a first verification fault or a second verification fault; the function request signal is generated by the touch response node according to the target function requirement and sent to the master node.
4. The method according to claim 1, characterized in that: Whether the second communication failure exists between the master node and the function execution node is determined by the following method: If the function execution node receives the third message fault signal sent by the master node, it is determined that the second communication fault exists between the master node and the function execution node; If the function execution node does not receive the function execution signal sent by the master node within a fourth preset time, it is determined that the second communication failure exists between the function execution node and the master node; The third message fault signal is used to indicate that the verification data obtained by the function execution node from the master node has a first verification fault or a second verification fault.
5. The method according to any one of claims 2 to 4, characterized in that: The verification data includes a verification code, and the first verification fault is determined by the following method: If the verification code is inconsistent with a preset reference verification code, it is determined that the first verification failure exists.
6. The method according to claim 5, characterized in that If the first verification failure exists between the data acquisition unit and the central domain controller, the central domain controller stops sending the function request signal to the master node, so that the master node still sends the function execution signal to the function execution node when it cannot receive the function request signal.
7. The method according to any one of claims 2 to 4, characterized in that: The verification data includes a message count value, and the second verification fault is determined by the following method: if the message count value is inconsistent with a preset reference message count value, it is determined that the second verification fault exists.
8. A vehicle communication fault handling system, characterized in that: The communication link comprises the communication link according to any one of claims 1 to 7, wherein the communication link comprises a master node, a demand detection node and a function execution node; the demand detection node, the master node and the function execution node are connected in sequence to form the communication link; The demand detection node is configured to send a function request signal to the master node when detecting that the vehicle has a target function demand; The master node is configured to determine whether there is a first communication failure between the master node and the demand detection node according to the signal receiving and sending status between the master node and the demand detection node, and when the first communication failure exists and the function request signal cannot be received normally, the master node still sends a function execution signal to the function execution node; The function execution node is configured to determine whether there is a second communication failure between the node and the main node based on the signal receiving and sending status between the node and the main node. When the second communication failure exists and the function execution signal cannot be received normally, the target function action corresponding to the function execution signal is still executed to meet the target function requirement.
9. A vehicle communication fault processing device, characterized in that: A master node applied to a plurality of communication nodes of the vehicle, the plurality of communication nodes further comprising a demand detection node and a function execution node, the demand detection node, the master node and the function execution node are sequentially connected to form a communication link, the device comprising: a determining unit, configured to determine whether there is a first communication failure between the vehicle and the demand detection node according to a signal receiving and sending state between the vehicle and the demand detection node, wherein, when the first communication failure occurs, a function request signal sent by the demand detection node cannot be normally received, and the function request signal is used to indicate that the vehicle has a target function requirement; A sending unit is used for sending a function execution signal to the function execution node even if the function request signal cannot be received normally when the first communication failure exists, so that the function execution node can determine whether there is a second communication failure between the function execution node and the main node according to the signal receiving and sending status between the function execution node and the main node. If the second communication failure exists, the target function action corresponding to the function execution signal is still executed to meet the target function requirement even if the function execution signal cannot be received normally.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one program code, and the at least one program code is loaded and executed by a processor to implement the operations performed by the method according to any one of claims 1 to 7.
Citation Information
Patent Citations
Fault processing method, device and apparatus and automobile
CN113341906A
Aircraft control system, flight control method and storage medium
CN116243594A
Vehicle light control method and device, storage medium and vehicle
CN117507998A
Vehicle communication fault processing method and device, vehicle and storage medium
CN117850395A
Automated vehicle safety response methods and corresponding vehicle safety systems with serial-parallel computing architectures
US20220185339A1
