Method and system for troubleshooting abnormal wake-up sources in a vehicle

Abstract

The present invention discloses a method and system for troubleshooting abnormal wake-up sources in a vehicle, which relates to the field of working condition analysis of electric vehicles. The steps of the method include: forming a wake-up source information data stream from the states of all wake-up sources, where the states of the wake-up sources include being in operation and not in operation; determining the type of the abnormal wake-up source according to the wake-up source information data stream, and when the abnormal wake-up source belongs to a basic wake-up source, troubleshooting the abnormal wake-up source among the basic wake-up sources; when the abnormal wake-up source belongs to a maintenance wake-up source, troubleshooting the abnormal wake-up source among the maintenance wake-up sources. The present invention determines the abnormal wake-up source through the state information of all wake-up sources, which not only significantly improves the work efficiency and reduces the work difficulty, but also can find the specific abnormal wake-up source through the subdivision and specific positioning of the basic wake-up source and the maintenance wake-up source, and the troubleshooting accuracy is relatively high.

Description

Technical Field

[0001] The present invention relates to the field of operating condition analysis of electric vehicles, and particularly to a method and system for detecting abnormal wake-up sources in a vehicle. Background Art

[0002] There are various ECUs (electronic control units for vehicles) on new energy electric vehicles. These ECUs are powered by the vehicle's power supply unit (usually a battery). Therefore, the battery power is limited. For new energy vehicles, excessive power consumption will undoubtedly have a huge impact on the battery's driving range. Therefore, in order to save power as much as possible, network management is proposed. That is to say, one of the most important functions of network management is to save power.

[0003] The way network management realizes power saving is as follows: all ECUs communicate with each other through CAN communication, Flexray or Ethernet and are connected together. Then network management sends some commands on the network of each ECU to formulate a set of rules to achieve the cooperative sleep and wake-up of each ECU. The purpose of network management is to make the ECU nodes in the network sleep and wake up orderly. Sleep when there is no communication need and wake up when communication is required, which can save the power of the vehicle battery.

[0004] Usually, an ECU has several working modes, such as the wake-up (working) mode, sleep mode, and boot mode. Among them, the working mode is the normal working mode with high energy consumption; the sleep mode is the standby state, and most functions stop, which is a low-power mode; the boot mode is the ECU flashing mode, usually used for upgrading the ECU.

[0005] When the vehicle is in the dormant state, all ECUs are in the sleep state, and some ECUs such as the body control module (BCM) can be woken up by KL15 power. When these controllers are in the sleep state, the energy consumption is very low and they are always in a wakeable state.

[0006] The common controller wake-up methods for vehicles include hard-wire wake-up and network wake-up. Hard-wire wake-up is usually achieved through low-voltage levels, such as KL15 wake-up, CP and CC wake-up of the charger.

[0007] The network wake-up method is further divided into any-frame wake-up and specific-frame wake-up. Any-frame wake-up means waking up when any signal on the CAN bus is received. A specific frame refers to waking up when the controller receives a specific network management message (NM).

[0008] Wake-up sources can be divided into active wake-up and passive wake-up according to their sources.

[0009] Active Wake up: The ECU acts as the main wake-up node. When it detects an active wake-up source input signal (such as KL15), it wakes itself up actively and tries to wake up other ECUs by sending NMFRAME. Passive Wakeup: The ECU acts as a slave wake-up node and cannot wake itself up actively. It can only wake itself up by receiving NM messages sent by other ECUs.

[0010] Definition of the controller's state:

[0011] BusSpleep state: This is the sleep state. In this state, no network management messages are sent, and no application messages are sent or received. Generally, this state is in a low-power state, which is the collaborative sleep state mentioned above. Of course, when powering on and initializing, it will also default to enter this state. PreSleep state: This state is the preparation state before entering the sleep state. In this state, generally no network management message frames are sent, and no application messages are sent either. It just waits for other ECUs to sleep together. In fact, it is to achieve the word "collaboration", that is, to wait for a period of time to let all ECUs on the vehicle sleep together. The reason why ECUs need to collaborate to sleep is mainly because each ECU is in a collaborative working state. For example, VCU (vehicle controller unit) and INV (inverter). It is possible that when VCU stops sending messages, it will cause INV to report a fault, and thus an incorrect alarm state will occur. Network state: In this state, the ECU can communicate normally. It can send and receive both network management message frames and application messages (including diagnostic messages), which means it is in the wake-up state.

[0012] Currently, when troubleshooting the problem of sleep wake-up (battery power feeding), the traditional method is to unplug each controller one by one to find the final faulty controller. This method is both time-consuming and laborious. Moreover, after the vehicle is delivered to the user, it is even more difficult to implement this processing method.

[0013] The Chinese invention patent with the publication number CN112034818A proposes a controller fault analysis method and system, which discloses that the domain controller monitors the static current data of multiple controllers and uploads it to the cloud for analysis of whether it is abnormal. If it is abnormal, the data is sent to the background, and the background confirms the faulty controller.

[0014] However, battery power feeding is often due to the fact that the whole vehicle fails to enter the sleep state normally or is repeatedly woken up after entering the sleep state. The result is that the static currents of multiple modules of the whole vehicle are too high. That is to say, the above-mentioned patent can only inform which controllers have abnormal static currents, and the abnormal wake-up sources that cause the vehicle to be unable to enter the sleep state or be woken up after entering the sleep state still need to be further determined. Summary of the Invention

[0015] In view of the defects existing in the prior art, the technical problem to be solved by the present invention is: how to respectively locate the abnormal wake-up source and the abnormal maintaining wake-up source.

[0016] To achieve the above object, the method for troubleshooting abnormal wake-up sources in a vehicle provided by the present invention includes the following steps: forming a wake-up source information data stream of the states of all wake-up sources, where the states of the wake-up sources include being in operation and not being in operation; determining the type of the abnormal wake-up source according to the wake-up source information data stream, and when the abnormal wake-up source belongs to the basic wake-up source, troubleshooting the abnormal wake-up source among the basic wake-up sources; when the abnormal wake-up source belongs to the maintaining wake-up source, troubleshooting the abnormal wake-up source among the maintaining wake-up sources.

[0017] Based on the above technical solution, the process of determining the type of the abnormal wake-up source according to the wake-up source information data stream includes: the faulty vehicle sends the wake-up source information data stream in real time, and the receiving end determines whether the number of interruptions of the data stream within a specified period exceeds a specified threshold. If so, it is determined that the abnormal wake-up source belongs to the basic wake-up source; otherwise, it is determined that the abnormal wake-up source belongs to the maintaining wake-up source.

[0018] Based on the above technical solution, in the wake-up source information data stream, the states of the wake-up sources belonging to the basic wake-up source category do not change after the vehicle is woken up, and are updated when the vehicle is woken up again after going to sleep; the states of the wake-up sources belonging to the maintaining wake-up source category are updated dynamically.

[0019] Based on the above technical solution, the wake-up source information data stream includes the basic wake-up source type and the maintaining wake-up source type. The basic wake-up source type and the maintaining wake-up source type each include several wake-up categories, and the states of the specific wake-up sources belonging to each category are recorded under each wake-up category; the process of troubleshooting the abnormal wake-up source among the basic wake-up sources includes: determining the basic wake-up sources with the state of being in operation in the wake-up source information data stream as the abnormal wake-up sources; the process of troubleshooting the abnormal wake-up source among the maintaining wake-up sources includes: determining the maintaining wake-up sources with the state of being in operation in the wake-up source information data stream as the abnormal wake-up sources.

[0020] Based on the above technical solution, the formation process of the wake-up source information data stream includes: the VIU (Vehicle Interface Unit) monitors the activity status of each network management message and its own IO status in real time, and updates the wake-up source information data stream in real time. The update rules include:

[0021] If the vehicle is awakened from the sleep state: When it is detected that it is an IO wake-up, set the IO wake-up bit in the wake-up reason byte to 1, and set the bit corresponding to the status switch of the IO wake-up reason byte to 1; when it is detected that it is an RF wake-up, set the RF wake-up bit in the wake-up reason byte to 1; when it is detected that it is a LIN wake-up, set the LIN wake-up bit in the wake-up reason byte to 1, and set the byte where the LIN wake-up source is located to the value of the corresponding LIN network segment; when it is detected that it is a CAN NM message wake-up, set the CAN NM message wake-up bit in the wake-up reason byte to 1, and set the byte where the network management wake-up source is located to the value of the corresponding CAN node.

[0022] After the vehicle is awakened, when it is detected that the vehicle cannot enter the sleep state because the vehicle mode is not OFF, set the usagemode bit in the byte where the wake-up reason is located to 1; when it is detected that the vehicle cannot enter the sleep state because of the change in the IO state, the VIU will set the IO_TIMER bit in the byte where the wake-up reason is located to 1, and set the byte where the IO sustained wake-up source is located to the value of the corresponding IO; when it is detected that the vehicle cannot enter the sleep state because of the RF trigger, the VIU will set the RF Sleep bit in the byte where the wake-up reason is located to 1; when it is detected that the vehicle cannot enter the sleep state because there are continuously network management messages on the bus to maintain, the VIU will set the NM message timeout bit in the byte where the wake-up reason is located to 1, and set the byte where the network management sustained wake-up source is located to the value of the corresponding network node; when it is detected that the vehicle cannot enter the sleep state because the VIU has a load output, the VIU will set the load output bit in the byte where the wake-up reason is located to 1, and set the bit corresponding to the load output to 1; when it is detected that the vehicle cannot enter the sleep state because of a diagnostic behavior, the VIU will set the DOIP TESTER bit in the byte where the wake-up reason is located to 1.

[0023] The system for troubleshooting abnormal wake-up sources in a vehicle provided by the present invention includes a wake-up source information reporting module and an abnormal wake-up source determination module;

[0024] The wake-up source information reporting module is used to: after forming a wake-up source information data stream of the status of all wake-up sources, send it to the abnormal wake-up source determination module, and the status of the wake-up source includes working and not working;

[0025] The abnormal wake-up source determination module is used to: determine the type of the abnormal wake-up source according to the wake-up source information data stream. When the abnormal wake-up source belongs to the basic wake-up source, troubleshoot the abnormal wake-up source among the basic wake-up sources; when the abnormal wake-up source belongs to the sustained wake-up source, troubleshoot the abnormal wake-up source among the sustained wake-up sources.

[0026] Based on the above technical solution, the process by which the abnormal wake-up source determination module determines the type of abnormal wake-up source according to the wake-up source information data stream includes: determining whether the number of interruptions of the data stream within a specified period exceeds a specified threshold. If so, it is determined that the abnormal wake-up source belongs to the basic wake-up source; otherwise, it is determined that the abnormal wake-up source belongs to the maintenance wake-up source.

[0027] Based on the above technical solution, in the wake-up source information data stream, the status of the wake-up source belonging to the basic wake-up source category does not change after the vehicle is woken up, and is updated when the vehicle is woken up again after going to sleep; the status of the wake-up source belonging to the maintenance wake-up source category is updated dynamically.

[0028] Based on the above technical solution, the wake-up source information data stream includes a basic wake-up source type and a maintenance wake-up source type. The basic wake-up source type and the maintenance wake-up source type each include several wake-up categories, and the status of the specific wake-up source belonging to each category is recorded under each wake-up category; the process of troubleshooting the abnormal wake-up source among the basic wake-up sources includes: determining the basic wake-up source with the status of "working" in the wake-up source information data stream as the abnormal wake-up source; the process of troubleshooting the abnormal wake-up source among the maintenance wake-up sources includes: determining the maintenance wake-up source with the status of "working" in the wake-up source information data stream as the abnormal wake-up source.

[0029] Based on the above technical solution, the wake-up source information reporting module is set on the vehicle's VIU. The process by which the wake-up source information reporting module forms the wake-up source information data stream includes:

[0030] If the vehicle is woken up from the sleep state: when it is detected that it is an IO wake-up, set the IO wake-up bit in the wake-up reason byte to 1, and set the bit corresponding to the status switch of the IO wake-up reason byte to 1; when it is detected that it is an RF wake-up, set the RF wake-up bit in the wake-up reason byte to 1; when it is detected that it is a LIN wake-up, set the LIN wake-up bit in the wake-up reason byte to 1, and set the byte where the LIN wake-up source is located to the value of the corresponding LIN network segment; when it is detected that it is a CAN NM message wake-up, set the CAN NM message wake-up bit in the wake-up reason byte to 1, and set the byte where the network management wake-up source is located to the value of the corresponding CAN node;

[0031] After the vehicle wakes up, when it is detected that the vehicle cannot enter the sleep state because the vehicle mode is not OFF, the usagemode bit in the byte where the wake-up reason is located will be set to 1; when it is detected that the vehicle cannot enter the sleep state due to a change in the IO state, the VIU will set the IO_TIMER bit in the byte where the wake-up reason is located to 1, and set the byte where the IO maintains the wake-up source to the value of the corresponding IO; when it is detected that the vehicle cannot enter the sleep state due to an RF trigger, the VIU will set the RF Sleep bit in the byte where the wake-up reason is located to 1; when it is detected that the vehicle cannot enter the sleep state because there are continuously network management messages on the bus, the VIU will set the NM message timeout bit in the byte where the wake-up reason is located to 1, and set the byte where the network management maintains the wake-up source to the value of the corresponding network node; when it is detected that there is a load output from the VIU, the VIU will set the load output bit in the byte where the wake-up reason is located to 1, and set the bit corresponding to the load output to 1; when it is detected that the vehicle cannot enter the sleep state due to a diagnostic action, the VIU will set the DOIP TESTER bit in the byte where the wake-up reason is located to 1.

[0032] Compared with the prior art, the advantages of the present invention are as follows:

[0033] The present invention determines the abnormal wake-up source through the status information of all wake-up sources. Compared with the prior art that uses a physical method (i.e., unplugging and plugging the controller) to determine the abnormal wake-up source, the working efficiency is significantly improved and the working difficulty is reduced; compared with the prior art that analyzes whether there is an abnormality through static current data, the present invention can find the specific abnormal wake-up source through the subdivision and specific positioning of the basic wake-up source and the maintaining wake-up source, and the troubleshooting accuracy is relatively high.

[0034] On this basis, the present invention can, without increasing costs, cooperate with the existing vehicle power supply warning platform and flexible data acquisition platform of the vehicle manufacturer to quickly and efficiently and accurately locate the faulty controller remotely. Description of the Drawings

[0035] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the following drawings are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0036] Figure 1 It is a flowchart of the method for troubleshooting abnormal wake-up sources in a vehicle in an embodiment of the present invention. Detailed Embodiments

[0037] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the following will clearly and completely describe the technical solutions in the embodiments of this application with reference to the accompanying drawings in the embodiments of this application. Apparently, the described embodiments are some, but not all, of the embodiments of this application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in this application without creative efforts shall fall within the scope of protection of this application.

[0038] The flowchart shown in the accompanying drawings is only an example, and does not necessarily include all contents and operations / steps, nor does it necessarily need to be executed in the described order. For example, some operations / steps can also be decomposed, combined, or partially merged. Therefore, the actual execution order may change according to the actual situation.

[0039] The method for troubleshooting abnormal wake-up sources in a vehicle in an embodiment of the present invention includes the following steps: forming a wake-up source information data stream of the states of all wake-up sources of a faulty vehicle (the state is obtained by real-time monitoring, generally monitored once every about 10 ms), and the states of the wake-up sources include working and not working. Determine the type of the abnormal wake-up source according to the wake-up source information data stream. When the abnormal wake-up source belongs to the basic wake-up source, troubleshoot the abnormal wake-up source among the basic wake-up sources; when the abnormal wake-up source belongs to the maintenance wake-up source, troubleshoot the abnormal wake-up source among the maintenance wake-up sources.

[0040] The research and development principle of the above method is: If it is necessary to locate a specific wake-up source in a non-physical manner (that is, without unplugging and plugging the controller in the prior art), it is necessary to record the state information of all wake-up sources to determine who is working and who is not. On this basis, the inventor divides the wake-up sources into basic wake-up sources and maintenance wake-up sources. If the basic wake-up source is abnormal, there is no need to troubleshoot among the maintenance wake-up sources, because in the case of an abnormal basic wake-up source, it is impossible to determine whether the maintenance wake-up source that depends on the basic wake-up source is abnormal; only when the basic wake-up source is normal, the maintenance wake-up source is troubleshot.

[0041] It can be seen from this that the present invention determines the abnormal wake-up source through the state information of all wake-up sources. Compared with the prior art in which the physical method (that is, unplugging and plugging the controller) is used to determine the abnormal wake-up source, the work efficiency is significantly improved and the work difficulty is reduced; compared with the prior art in which the static current data is analyzed to determine whether it is abnormal, the present invention can find the specific abnormal wake-up source through the subdivision and specific positioning of the basic wake-up source and the maintenance wake-up source, and the troubleshooting accuracy is relatively high.

[0042] Preferably, the process of determining the type of abnormal wake-up source according to the wake-up source information data stream in this method includes: the faulty vehicle sends the wake-up source information data stream in real time, and the receiving end determines whether the number of interruptions of the data stream within a specified period exceeds a specified threshold (considering that the data stream may also be interrupted due to reasons such as communication quality, so the specific value can be multiple times, at least more than 2 times). If so, it means that the vehicle is in a state of being woken up after repeated dormancy, and at this time, it is determined that the abnormal wake-up source belongs to the basic wake-up source; otherwise, it means that the vehicle cannot enter the dormancy state, and at this time, it is determined that the abnormal wake-up source belongs to the maintenance wake-up source.

[0043] The principle of the above process is: the faulty vehicle will only send the data stream when it is woken up and will not send it when it is dormant. Therefore, when the data stream is "intermittent", the faulty vehicle must be in a state of being woken up after repeated dormancy; when the data stream is continuously sent, the faulty vehicle must be in a state of being unable to enter the dormant state.

[0044] Preferably, the wake-up source information data stream in the above method includes the basic wake-up source type and the maintenance wake-up source type. The basic wake-up source type and the maintenance wake-up source type each include several wake-up categories, and the status of the specific wake-up source belonging to each category is recorded under each wake-up category. In this embodiment, the wake-up categories of the basic wake-up source include switches (the specific wake-up sources are horn switches, brake switches, door switches, etc.), RF (the specific wake-up source is radio frequency signal), LIN, and NM (network management message, the specific wake-up source is a specific controller). The wake-up categories of the maintenance wake-up source include switch state change (the specific wake-up sources are horn switch / brake switch / door switch change, etc.), RF timeout (the specific wake-up source is continuous pressing of the remote control key), diagnosis (the specific wake-up source is performing a diagnostic operation), power mode (the specific wake-up source is that the power mode is not OFF), load output (the specific wake-up sources are trunk light on, welcome light on, seat heating, etc.) and NM.

[0045] It can be seen from this that the wake-up source information data stream of the present invention records the status of the corresponding wake-up source according to the category, thereby enabling subsequent rapid positioning of the abnormal wake-up source "from large to small" according to the category, and further improving the troubleshooting efficiency.

[0046] Specifically, the process of troubleshooting the abnormal wake-up source in the basic wake-up source in the above method includes: determining the basic wake-up source with the status of working in the wake-up source information data stream as the abnormal wake-up source; the process of troubleshooting the abnormal wake-up source in the maintenance wake-up source in the above method includes: determining the maintenance wake-up source with the status of working in the wake-up source information data stream as the abnormal wake-up source.

[0047] Preferably, in the above wake-up source information data stream, the status of the wake-up sources belonging to the basic wake-up source category does not change after the vehicle is woken up, and is updated when the vehicle is woken up again after going to sleep; the status of the wake-up sources belonging to the maintenance wake-up source category is dynamically updated (that is, the latest maintenance wake-up sources are recorded in real time). Such a design can identify the wake-up sources with changed status by comparison when locating abnormal wake-up sources later.

[0048] Specifically, the formation process of the above wake-up source information data stream includes: the VIU (zone controller) monitors the activity status of each network management message and its own IO status in real time, and updates the wake-up source information data stream to the bus in real time (sent once every 10 ms) according to the defined matrix. The update rules include:

[0049] If the vehicle is woken up from the sleep state:

[0050] When it is detected that it is an IO wake-up, the corresponding VIU sets the IO wake-up bit in the wake-up reason byte to 1, and sets the bit corresponding to the status switch of the IO wake-up reason byte to 1. For example: when it is detected that the status change of the left front door wakes up, the corresponding VIU sets the IO wake-up bit in the wake-up reason byte to 1, and sets the bit corresponding to the left front door status switch of the IO wake-up reason byte to 1.

[0051] When it is detected that it is an RF wake-up, the corresponding VIU sets the RF wake-up bit in the wake-up reason byte to 1.

[0052] When it is detected that it is a LIN wake-up, the corresponding VIU sets the LIN wake-up bit in the wake-up reason byte to 1, and sets the byte where the LIN wake-up source is located to the value of the corresponding LIN network segment. For example: when it is detected that RRearLIN wakes up VIUR, VIUR sets the LIN wake-up bit in the wake-up reason byte to 1, and sets the byte where the LIN wake-up source is located to 1.

[0053] When it is detected that it is a CAN NM message wake-up, the corresponding VIU sets the CAN NM message wake-up bit in the wake-up reason byte to 1, and sets the byte where the network management wake-up source is located to the value of the corresponding CAN node. For example: when it is detected that NM_BLE (0x63B) wakes up VIUML, VIUML sets the CAN NM message wake-up bit in the wake-up reason byte to 1, and sets the byte where the network management wake-up source is located to 4.

[0054] Note: After each wake-up, the recorded wake-up sources do not change until the vehicle goes to sleep and is woken up again, and the wake-up sources for this wake-up are updated and recorded.

[0055] After the vehicle is woken up, the VIU monitors the maintenance wake-up reason in real time, specifically as follows:

[0056] When it is detected that the vehicle cannot enter the sleep state because the vehicle mode is not OFF, the VIU will set the usagemode bit in the byte where the wake-up reason is located to 1.

[0057] When it is detected that the vehicle cannot enter the sleep state due to a change in the IO status, the VIU will set the IO_TIMER bit in the byte where the wake-up reason is located to 1, and set the byte where the IO maintains the wake-up source to the value of the corresponding IO. For example: When the VIUML detects a change in the left front door status switch during the process of entering the sleep state, the VIUML will set the IO_TIMER bit in the byte where the wake-up reason is located to 1, and set the byte where the IO maintains the wake-up source to 2.

[0058] When it is detected that the vehicle cannot enter the sleep state due to an RF trigger, the VIU will set the RFSleep bit in the byte where the wake-up reason is located to 1.

[0059] When it is detected that the vehicle cannot enter the sleep state because there is a continuous network management message on the bus to maintain, the VIU will set the NM message timeout bit in the byte where the wake-up reason is located to 1, and set the byte where the network management maintains the wake-up source to the value of the corresponding network node. For example: When the VIUMR detects a 0x649 message on the bus during the process of entering the sleep state, the VIUMR will set the NM message timeout bit in the byte where the wake-up reason is located to 1, and set the byte where the network management maintains the wake-up source to 7.

[0060] When it is detected that the vehicle cannot enter the sleep state because the VIU has a load output, the VIU will set the load output bit in the byte where the wake-up reason is located to 1, and set the corresponding load output bit to 1. For example: When it is detected that the vehicle cannot enter the sleep state because the front trunk light drive of the VIUF is always on, the VIUF will set the load output bit in the byte where the wake-up reason is located to 1, and set the bit where the front trunk light drive is located to 1.

[0061] When it is detected that the vehicle cannot enter the sleep state due to a diagnostic action, the VIU will set the DOIP TESTER bit in the byte where the wake-up reason is located to 1.

[0062] Note: Record the latest wake-up source maintained in real time.

[0063] The following is shown Figure 1 to illustrate the method of the present invention through a specific embodiment.

[0064] S1: After the warning platform detects that the vehicle sleep is abnormal, it sends a warning message. The specific implementation method for monitoring the vehicle sleep abnormality can be set according to the actual situation and is not within the protection scope of the present invention. For example, when the energy consumption exceeds the threshold, it represents that the vehicle sleep is abnormal, etc.

[0065] S2: The fault troubleshooting platform obtains the data stream of the wake-up source information sent in real time by the faulty vehicle, and determines whether the number of interruptions in the data stream within 6 hours exceeds 3 times. If so, it means that the vehicle is in a state of being woken up after repeated dormancy, and it is determined that the abnormal wake-up source belongs to the basic wake-up source, and then go to S3; otherwise, it means that the vehicle cannot enter the dormancy state, and it is determined that the abnormal wake-up source belongs to the maintenance wake-up source, and then go to S4.

[0066] S3: Determine the basic wake-up source with the status of "working" in the data stream of the wake-up source information as the abnormal wake-up source.

[0067] S4: Determine the maintenance wake-up source with the status of "working" in the data stream of the wake-up source information as the abnormal wake-up source.

[0068] The system for troubleshooting abnormal wake-up sources in a vehicle in the embodiments of the present invention includes a wake-up source information reporting module provided on the vehicle VIU and an abnormal wake-up source determination module provided on the terminal.

[0069] The wake-up source information reporting module is used for: after forming the data stream of the wake-up source information for all wake-up sources, sending it to the abnormal wake-up source determination module, and the status of the wake-up source includes "working" and "not working".

[0070] The abnormal wake-up source determination module is used for: determining the type of the abnormal wake-up source according to the data stream of the wake-up source information. When the abnormal wake-up source belongs to the basic wake-up source, troubleshooting the abnormal wake-up source among the basic wake-up sources; when the abnormal wake-up source belongs to the maintenance wake-up source, troubleshooting the abnormal wake-up source among the maintenance wake-up sources.

[0071] Those of ordinary skill in the art can understand that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices can be implemented as software, firmware, hardware and their appropriate combinations. In the hardware implementation, the division of the functional modules / units mentioned above does not necessarily correspond to the division of physical components; for example, a physical component can have multiple functions, or a function or step can be executed by several physical components in cooperation. Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable storage medium, and the computer-readable storage medium can include a computer-readable storage medium (or non-transitory medium) and a communication medium (or transitory medium).

[0072] As is well known to those of ordinary skill in the art, the term computer-readable storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disks (DVDs) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. Additionally, as is well known to those of ordinary skill in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and can include any information delivery medium.

[0073] Exemplarily, the computer-readable storage medium can be the internal storage unit of the electronic device in the foregoing embodiments, such as the hard disk or memory of the electronic device. The computer-readable storage medium can also be an external storage device of the electronic device, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device.

[0074] The above are only the specific implementation manners of the embodiments of the present invention, but the protection scope of the embodiments of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed by the embodiments of the present invention can easily think of various equivalent modifications or substitutions, and these modifications or substitutions should all be covered within the protection scope of the embodiments of the present invention. Therefore, the protection scope of the embodiments of the present invention shall be subject to the protection scope of the claims.

Claims

1. A method for troubleshooting abnormal wake-up sources in a vehicle, characterized in that, The method includes the following steps: Form a wake-up source information data stream from the states of all wake-up sources, where the states of the wake-up sources include working and not working; Determine the type of abnormal wake-up source according to the wake-up source information data stream: The faulty vehicle sends the wake-up source information data stream in real time, and the receiving end judges whether the number of interruptions of the data stream within a specified period exceeds a specified threshold. If so, determine that the abnormal wake-up source belongs to the basic wake-up source; otherwise, determine that the abnormal wake-up source belongs to the maintenance wake-up source; The wake-up source information data stream includes the basic wake-up source type and the maintenance wake-up source type. The basic wake-up source type and the maintenance wake-up source type each include several wake-up categories, and the state of the specific wake-up source belonging to each category is recorded under each wake-up category; The state of the wake-up source belonging to the basic wake-up source category does not change after the vehicle is awakened, and is updated when the vehicle is awakened again after going to sleep; The state of the wake-up source belonging to the maintenance wake-up source category is updated dynamically; When the abnormal wake-up source belongs to the basic wake-up source, check for the abnormal wake-up source among the basic wake-up sources: Determine the basic wake-up source with the state of working in the wake-up source information data stream as the abnormal wake-up source; When the abnormal wake-up source belongs to the maintenance wake-up source, check for the abnormal wake-up source among the maintenance wake-up sources: Determine the maintenance wake-up source with the state of working in the wake-up source information data stream as the abnormal wake-up source.

2. The method for troubleshooting abnormal wake-up sources in a vehicle according to claim 1, wherein The formation process of the wake-up source information data stream includes: VIU monitors the activity status of each network management message and its own IO status in real time, and updates the wake-up source information data stream in real time. The update rules include: If the vehicle is awakened from the sleep state: When it is detected that it is an IO wake-up, set the IO wake-up bit of the wake-up reason byte to 1, and set the bit corresponding to the state switch of the IO wake-up reason byte to 1; When it is detected that it is an RF wake-up, set the RF wake-up bit of the wake-up reason byte to 1; When it is detected that it is a LIN wake-up, set the LIN wake-up bit of the wake-up reason byte to 1, and set the byte where the LIN wake-up source is located to the value of the corresponding LIN network segment; When it is detected that it is a CAN NM message wake-up, set the CAN NM message wake-up bit of the wake-up reason byte to 1, and set the byte where the network management wake-up source is located to the value of the corresponding CAN node; After the vehicle is awakened, when it is detected that the vehicle cannot enter the sleep state because the vehicle mode is not OFF, the usagemode bit of the byte where the wake-up reason is located will be set to 1; when it is detected that the vehicle cannot enter the sleep state due to a change in the IO state, the VIU will set the IO_TIMER bit of the byte where the wake-up reason is located to 1 and set the byte where the IO maintain wake-up source is located to the value of the corresponding IO; when it is detected that the vehicle cannot enter the sleep state due to an RF trigger, the VIU will set the RFSleep bit of the byte where the wake-up reason is located to 1; when it is detected that the vehicle cannot enter the sleep state because there are continuously network management messages on the bus, the VIU will set the NM message timeout bit of the byte where the wake-up reason is located to 1 and set the byte where the network management maintain wake-up source is located to the value of the corresponding network node; when it is detected that there is a load output from the VIU, the VIU will set the load output bit of the byte where the wake-up reason is located to 1 and set the bit corresponding to the load output to 1; when it is detected that the vehicle cannot enter the sleep state due to a diagnostic action, the VIU will set the DOIP TESTER bit of the byte where the wake-up reason is located to 1.

3. A system for troubleshooting abnormal wake-up sources in a vehicle, characterized in that: The system includes a wake-up source information reporting module and an abnormal wake-up source determination module; The wake-up source information reporting module is used to: after forming a wake-up source information data stream with the states of all wake-up sources, send it to the abnormal wake-up source determination module. The states of the wake-up sources include working and not working; in the wake-up source information data stream, the states of the wake-up sources belonging to the basic wake-up source category will not change after the vehicle is awakened and will be updated when the vehicle is awakened again after entering the sleep state; the states of the wake-up sources belonging to the maintain wake-up source category are updated dynamically; The abnormal wake-up source determination module is used to: Determine the type of the abnormal wake-up source according to the wake-up source information data stream: The wake-up source information data stream includes a basic wake-up source type and a maintain wake-up source type. The basic wake-up source type and the maintain wake-up source type each include several wake-up categories, and the state of the specific wake-up source belonging to each category is recorded under each wake-up category; judge whether the number of interruptions of the data stream within a specified period exceeds a specified threshold. If so, determine that the abnormal wake-up source belongs to the basic wake-up source; otherwise, determine that the abnormal wake-up source belongs to the maintain wake-up source; When the abnormal wake-up source belongs to the basic wake-up source, search for the abnormal wake-up source among the basic wake-up sources: Determine the basic wake-up source with the state of working in the wake-up source information data stream as the abnormal wake-up source; When the abnormal wake-up source belongs to the maintain wake-up source, search for the abnormal wake-up source among the maintain wake-up sources: Determine the maintain wake-up source with the state of working in the wake-up source information data stream as the abnormal wake-up source.

4. The system for troubleshooting abnormal wake-up sources in a vehicle according to claim 3, wherein The wake-up source information reporting module is set on the VIU of the vehicle. The process of the wake-up source information reporting module forming the wake-up source information data stream includes: If the vehicle is awakened from the sleep state: When it is detected that the wake-up is caused by IO, set the IO wake-up bit in the wake-up reason byte to 1, and set the bit corresponding to the status switch of the IO wake-up reason byte to 1; when it is detected that the wake-up is caused by RF, set the RF wake-up bit in the wake-up reason byte to 1; when it is detected that the wake-up is caused by LIN, set the LIN wake-up bit in the wake-up reason byte to 1, and set the byte where the LIN wake-up source is located to the value of the corresponding LIN network segment; when it is detected that the wake-up is caused by a CAN NM message, set the CAN NM message wake-up bit in the wake-up reason byte to 1, and set the byte where the network management wake-up source is located to the value of the corresponding CAN node. After the vehicle is awakened, when it is detected that the vehicle cannot enter the sleep state because the vehicle mode is not OFF, maintain the usagemode bit in the byte where the wake-up reason is located to 1; when it is detected that the vehicle cannot enter the sleep state because of the change in the IO state, the VIU will maintain the IO_TIMER bit in the byte where the wake-up reason is located to 1, and set the byte where the IO maintenance wake-up source is located to the value of the corresponding IO; when it is detected that the vehicle cannot enter the sleep state because of the RF trigger, the VIU will maintain the RFSleep bit in the byte where the wake-up reason is located to 1; when it is detected that the vehicle cannot enter the sleep state because there are continuously network management messages on the bus to maintain, the VIU will maintain the NM message timeout bit in the byte where the wake-up reason is located to 1, and set the byte where the network management maintenance wake-up source is located to the value of the corresponding network node; when it is detected that the vehicle cannot enter the sleep state because the VIU has a load output, the VIU will maintain the load output bit in the byte where the wake-up reason is located to 1, and set the bit corresponding to the load output to 1; when it is detected that the vehicle cannot enter the sleep state because of a diagnostic action, the VIU will maintain the DOIP TESTER bit in the byte where the wake-up reason is located to 1.

Images