Vehicle operating state monitoring method, system, device and storage medium

Abstract

This invention provides a vehicle operation status monitoring method, system, device, and storage medium. The method includes: monitoring the operation status of various modules of a preset type in the vehicle; determining whether to generate a preset type of fault code based on the operation status; collecting the generated fault code information, the fault code information including the generated fault code and its corresponding fault level; determining the vehicle's global fault level based on the fault levels of the collected fault code information; and selecting a corresponding vehicle control strategy based on the vehicle's global fault level. This invention improves vehicle driving safety by monitoring various modules of the vehicle and uniformly processing fault codes, automatically selecting a vehicle control strategy based on the fault level.

Description

Technical Field

[0001] This invention relates to the field of vehicle control technology, and in particular to a method, system, device, and storage medium for monitoring vehicle operating status. Background Technology

[0002] The control program for autonomous vehicles typically consists of multiple modules. Each module processes the input from the other modules and then sends the results to other modules that are interested in the results via inter-process communication. Each module operates independently, following its own rules, and should not interfere with each other. Ideally, this works without problems, but in reality, the following issues arise:

[0003] 1. The module may experience functional abnormalities. These abnormalities often occur due to incorrect or missing input information, which may prevent the module from performing its functions properly.

[0004] 2. The module may experience abnormal software operation. Such abnormalities are often caused by the software developer's implementation, such as program vulnerabilities.

[0005] 3. The module may crash and exit directly, and this serious anomaly may have a fatal impact on the autonomous driving system.

[0006] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of the present invention, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0007] In view of the problems in the prior art, the purpose of this invention is to provide a vehicle operation status monitoring method, system, device and storage medium, which improves vehicle driving safety by monitoring various modules of the vehicle and uniformly processing fault codes, automatically selecting vehicle control strategies according to the fault level.

[0008] This invention provides a method for monitoring vehicle operating status, comprising the following steps:

[0009] Monitor the operating status of each module of the vehicle's preset type;

[0010] Based on the operating status, determine whether to generate a preset type of fault code;

[0011] Collect generated fault code information, which includes the generated fault code and the corresponding fault level;

[0012] The overall fault level of the vehicle is determined based on the fault level of each fault code information collected.

[0013] Based on the vehicle's global fault level, select the corresponding vehicle control strategy.

[0014] In some embodiments, determining the overall fault level of the vehicle based on the fault level of each collected fault code information includes the following steps:

[0015] Extract the corresponding fault level from each of the collected fault code information;

[0016] The priority of the fault levels of the collected fault codes is compared, and the fault level with the highest priority is selected as the global fault level of the vehicle.

[0017] In some embodiments, the fault code information further includes the human intervention level corresponding to the fault code, and after collecting and generating the fault code information, the following steps are also included:

[0018] Extract the corresponding level of human intervention from each of the collected fault code information;

[0019] The overall human intervention level of the vehicle is determined based on the human intervention level of each fault code information collected.

[0020] Select the corresponding fault reset conditions based on the vehicle's overall human intervention level.

[0021] In some embodiments, determining the overall human intervention level of the vehicle based on the human intervention level of each collected fault code information includes the following steps:

[0022] The priority of the human intervention levels of the collected fault code information is compared, and the human intervention level with the highest priority is selected as the global human intervention level for the vehicle.

[0023] In some embodiments, determining whether to generate a preset type of fault code based on the operating status includes the following steps:

[0024] For each type of operating status, determine whether it meets the generation conditions for the corresponding type of fault code;

[0025] If so, generate the corresponding type of fault code, obtain the fault level and human intervention level corresponding to the fault code, and generate fault code information.

[0026] In some embodiments, after selecting the corresponding vehicle control strategy, the following steps are further included:

[0027] The vehicle's actuators are controlled according to the corresponding vehicle control strategy, causing the vehicle to transition from the first state to the second state.

[0028] Determine whether the fault reset condition is met;

[0029] If the condition is met, the vehicle's actuators are controlled to return the vehicle to the first state;

[0030] Otherwise, the vehicle remains in the second state.

[0031] In some embodiments, the following steps are also included:

[0032] A strategy configuration page is provided, which includes a vehicle control strategy configuration area and a fault reset condition configuration area.

[0033] The user sets the correspondence between each fault level and the vehicle control strategy according to the configuration information in the vehicle control strategy configuration area; and / or sets the correspondence between each human intervention level and the fault reset condition according to the configuration information in the fault reset condition configuration area.

[0034] In some embodiments, the monitoring of the operating status of each module of a preset type of vehicle includes:

[0035] Monitor at least one of the following: the system resource usage status of each system module of the vehicle, the software operation status of each software module, and the hardware operation status of each hardware module.

[0036] In some embodiments, the preset type of fault code includes system fault codes, software fault codes, and hardware fault codes. Determining whether to generate a preset type of fault code based on the operating status includes the following steps:

[0037] Determine whether to generate a system fault code based on the system resource occupancy status of the vehicle's system modules;

[0038] Determine whether to generate a software fault code based on the software operating status of the vehicle's software modules.

[0039] The system determines whether to generate a hardware fault code based on the hardware operating status of the vehicle's hardware modules.

[0040] In some embodiments, the operating state includes parameter values ​​of operating state parameters, and the fault code generation conditions include at least one parameter value range of the operating state parameter.

[0041] The process of determining whether each type of operating state meets the generation conditions for the corresponding type of fault code includes the following steps:

[0042] For each type, determine whether the parameter value of the operating status parameter belongs to the parameter value range of each fault code of that type;

[0043] If so, then determine to generate the corresponding fault code for that type.

[0044] In some embodiments, the following steps are also included:

[0045] A fault code configuration page is provided, which includes a fault code generation condition configuration area and a level configuration area;

[0046] The user sets the fault code generation conditions according to the configuration information in the generation condition configuration area; and / or sets the fault level and / or human intervention level corresponding to the fault code according to the configuration information in the level configuration area.

[0047] This invention also provides a vehicle operation status monitoring system for implementing the aforementioned vehicle operation status monitoring method, the system comprising:

[0048] The status monitoring module is used to monitor the operating status of various modules of the vehicle in a preset type;

[0049] The status determination module is used to determine whether to generate a preset type of fault code based on the operating status;

[0050] The fault level determination module is used to collect generated fault code information, which includes the generated fault code and the corresponding fault level, and to determine the vehicle's global fault level based on the fault level of each collected fault code.

[0051] The strategy selection module is used to select the corresponding vehicle control strategy based on the vehicle's global fault level.

[0052] This invention also provides a vehicle operation status monitoring device, comprising:

[0053] processor;

[0054] A memory in which executable instructions of the processor are stored;

[0055] The processor is configured to execute the steps of the vehicle operation status monitoring method by executing the executable instructions.

[0056] This invention also provides a computer-readable storage medium for storing a program, which, when executed by a processor, implements the steps of the vehicle operation status monitoring method.

[0057] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure.

[0058] The vehicle operation status monitoring method, system, device, and storage medium of the present invention have the following beneficial effects:

[0059] This invention monitors and diagnoses faults in various modules of a vehicle and provides a convenient fault reporting mechanism. Based on the fault level of the collected fault codes, it controls the vehicle's operating strategy, quickly and effectively responds to various vehicle faults, and improves vehicle driving safety. Attached Figure Description

[0060] Other features, objects, and advantages of the invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings.

[0061] Figure 1 This is a flowchart of a vehicle operation status monitoring method according to an embodiment of the present invention;

[0062] Figure 2 This is a schematic diagram of the structure of a vehicle operation status monitoring system according to an embodiment of the present invention;

[0063] Figure 3 This is a schematic diagram illustrating the interaction between a monitoring system and various modules of a vehicle according to an embodiment of the present invention;

[0064] Figure 4 This is a flowchart illustrating the execution of a vehicle control strategy according to an embodiment of the present invention;

[0065] Figure 5 This is a schematic diagram of the structure of a vehicle operation status monitoring device according to an embodiment of the present invention;

[0066] Figure 6 This is a schematic diagram of the structure of a computer-readable storage medium according to an embodiment of the present invention. Detailed Implementation

[0067] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that this disclosure will be more comprehensive and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0068] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0069] The flowchart shown in the attached diagram is merely an illustrative example and does not necessarily include all steps. For example, some steps may be broken down, while others may be combined or partially combined. Therefore, the actual execution order may change depending on the specific circumstances.

[0070] To address the technical problems of existing technologies, embodiments of the present invention provide a vehicle operation status monitoring method. This method monitors and diagnoses faults in various modules of the vehicle and provides a convenient fault reporting mechanism. Based on the fault level of the collected fault codes, the method controls the vehicle's operating strategy, quickly and effectively responding to various vehicle faults and improving vehicle driving safety. The method of the present invention can be applied to autonomous vehicles, semi-autonomous vehicles, and driver-assisted vehicles. The following description uses an autonomous vehicle as an example to illustrate the implementation of the present invention, but the invention is not limited thereto.

[0071] like Figure 1 As shown, the vehicle operation status monitoring method includes the following steps S100 to S500.

[0072] S100: Monitors the operating status of various modules of the vehicle's preset type.

[0073] In this embodiment, the various preset types of modules in the vehicle may include, for example, system modules, software modules, and hardware modules, covering all parts of the information that the autonomous vehicle needs to monitor. The system module corresponds to the vehicle operating system (OS) and may specifically be a module that executes specific functions of the vehicle operating system. The software module is a module that executes specific software processes, such as a path planning module, a collision detection module, and a strategy control module. The hardware module is a hardware product module, such as a LiDAR, camera, temperature sensor, or other hardware used in the vehicle. By dividing the modules into three types according to their functions, different motion states can be collected for each type of module in a targeted manner, and the parts that the vehicle needs to monitor can be fully covered.

[0074] In this embodiment, monitoring the operating status of each module of the preset type of the vehicle includes: monitoring the system resource occupancy status of each system module of the vehicle, the software operating status of each software module, and the hardware operating status of each hardware module.

[0075] S200: Based on the operating status, determine whether to generate a preset type of fault code.

[0076] In this embodiment, the preset types may include, for example, system fault codes, software fault codes, and hardware fault codes, corresponding to faults in system modules, software modules, and hardware modules, respectively. A fault code is a unique identifier for a fault and can be obtained from a combination of numbers and / or letters, or may include some special characters. The encoding method of the fault codes can be set as needed; for example, different letter identifiers can be used for fault codes of system modules, software modules, and hardware modules.

[0077] In this embodiment, step S200, determining whether to generate a preset type of fault code based on the operating status, includes the following steps:

[0078] Determine whether to generate a system fault code based on the system resource occupancy status of the vehicle's system modules;

[0079] Determine whether to generate a software fault code based on the software operating status of the vehicle's software modules.

[0080] The system determines whether to generate a hardware fault code based on the hardware operating status of the vehicle's hardware modules.

[0081] S300: Collect the generated fault code information, which includes the generated fault code and the corresponding fault level; further, the fault code information may also include the fault occurrence time and fault information description, which is a description of the fault code, such as specific status parameters and possible causes of the fault.

[0082] The fault code information collected here includes fault code information generated by all modules, such as fault code information generated by system module 1, fault code information generated by system module 2, fault code information generated by software module 1, fault code information generated by hardware module 1, and so on.

[0083] In this embodiment, a pre-set correspondence between different fault codes and fault levels is provided. After a fault code is generated, the corresponding fault level can be queried.

[0084] The specific classification of fault levels can be set as needed, such as INFO level, WARNING level, ERROR level, and FATAL level. The severity of the fault level increases in that order, and the priority also increases in that order.

[0085] S400: Determine the vehicle's global fault level based on the fault level of each fault code information collected; for example, the final global fault level of the vehicle is determined to be one of the following: INFO level, WARNING level, ERROR level, or FATAL level.

[0086] S500: Based on the vehicle's global fault level, select the corresponding vehicle control strategy. Vehicle control strategies may include, for example, vehicle deceleration, vehicle deceleration to a stop, or immediate vehicle stop. A higher global fault level indicates a more severe fault, requiring a more urgent vehicle control strategy.

[0087] The correspondence between various global fault levels and various vehicle control strategies is preset. For example, if the global fault level is INFO, no operation is required; if the global fault level is WARNING, the vehicle will slow down; if the global fault level is ERROR, the vehicle will slowly stop; and if the global fault level is FATAL, the vehicle will quickly stop.

[0088] By employing this vehicle operation status monitoring method, the operating status of each module of a preset type in the vehicle is first monitored in step S100. Fault codes of each preset type are generated in step S200. The global fault level of the vehicle is determined based on the fault level in the generated fault code information in steps S300 and S400. Finally, a vehicle control strategy is selected based on the global fault level in step S500. This provides a convenient fault reporting mechanism, controls the vehicle's operating strategy based on the fault level of the collected fault codes, and quickly and effectively responds to various vehicle faults, improving vehicle driving safety. The vehicle operation status monitoring method of this invention can be deployed in the vehicle's own control system or separately in a controller, and can communicate with the vehicle's own control system.

[0089] like Figure 2 As shown, this embodiment of the invention also provides a vehicle operation status monitoring system for implementing the vehicle operation status monitoring method described above. The system includes:

[0090] The status monitoring module M100 is used to monitor the operating status of each module of the vehicle's preset type, which corresponds to the function of step S100 above.

[0091] The status judgment module M200 is used to determine whether to generate a preset type of fault code based on the operating status, which corresponds to the function of the above step S200.

[0092] The fault code determination module M300 is used to collect generated fault code information, which includes the generated fault code and the corresponding fault level, and to determine the global fault level of the vehicle based on the fault level of each collected fault code information, which can realize the functions of the above steps S300 and S400.

[0093] The strategy selection module M400 is used to select the corresponding vehicle control strategy based on the vehicle's global fault level, which can achieve the function of step S500 above.

[0094] By employing this vehicle operation status monitoring system, the status monitoring module M100 first monitors the operating status of each module of a preset type in the vehicle. The status judgment module M200 generates fault codes for each preset type. The level determination module M300 determines the global fault level of the vehicle based on the fault level in the generated fault code information. The strategy selection module M400 selects a vehicle control strategy based on the global fault level, providing a convenient fault reporting mechanism. By controlling the vehicle's operating strategy based on the fault level of the collected fault codes, it quickly and effectively responds to various vehicle faults, improving vehicle driving safety. This vehicle operation status monitoring system can be deployed within the vehicle's own control system or separately on a controller, and can communicate with the vehicle's own control system. The level determination module M300 collects fault information from all modules, comprehensively processes and judges it to obtain the global fault level, and the strategy selection module M400 automatically executes corresponding operations for the vehicle.

[0095] Figure 3 This illustration demonstrates the interaction between the vehicle operation status monitoring system and various vehicle modules. In this embodiment, the vehicle's preset modules may include, for example, system modules, software modules, and hardware modules. The status monitoring module communicates with each module to monitor its operational status. The status monitoring module may include a system monitoring unit, a software detection unit, and a hardware monitoring unit. The system monitoring unit monitors the resources of the system modules, primarily by obtaining information on resource usage of each system module from the operating system. The operational status of the system modules includes, for example, CPU utilization, number of CPU threads, currently used memory, free memory, total memory, GPU core utilization, CPU bandwidth utilization, current GPU video memory, free video memory, total video memory, used hard disk space, free hard disk space, and total space. The software monitoring unit monitors the operational status of each software module, including software process ID, software process running frequency, CPU / memory status, PID parameters, state machine, etc., and can directly obtain fault code information generated internally by the module. The hardware monitoring unit monitors the operational status of each hardware module, including data timestamps, data frequency, data latency, timeout detection, data content checks, etc. Figure 3 The example shows two system modules, two software modules, and two hardware modules. The actual number of system modules, software modules, and hardware modules being monitored can be set as needed. For example, the entire operating system of the vehicle can be used as a system module, and more software modules and more hardware modules can be added.

[0096] like Figure 3As shown, the status judgment module includes a system status judgment unit, a software status judgment unit, and a hardware status judgment unit. The system status judgment unit obtains the operating status of system modules from the system monitoring unit and determines whether a system fault code is generated. The software status judgment unit obtains the operating status of software modules from the software monitoring unit and determines whether a software fault code is generated. The hardware status judgment unit obtains the operating status of hardware modules from the hardware status judgment unit and determines whether a hardware fault code is generated. The level determination module collects fault codes and fault code levels of each module from the system status judgment unit, the software status judgment unit, and the hardware status judgment unit. Then, it determines the global fault level based on the fault code levels of each module, and can also determine the global human intervention level based on the human intervention level corresponding to the fault codes of each module (described in detail below). The level determination module then outputs recording information to the information recording module. The output recording information may include: fault code information for all modules, global fault level, global human intervention level, and other detailed operating status statistics, such as the name, PID, CPU / memory usage, program execution cycle, and GPU bandwidth / video memory / core usage for each process.

[0097] The strategy selection module selects the corresponding vehicle control strategy based on the global fault level and the global human intervention level, and sends the corresponding vehicle control strategy to the vehicle's strategy execution module. The strategy execution module then controls the vehicle's actuators to perform the corresponding actions. For example, if the selected vehicle control strategy is slow stopping, the actuators will first control the vehicle to decelerate, and then control the vehicle to stop when the speed reaches a certain range.

[0098] In this embodiment, step S400, determining the vehicle's global fault level based on the fault levels of the collected fault code information, includes the following steps:

[0099] Extract the corresponding fault level from each of the collected fault code information;

[0100] The priority of the fault levels of the collected fault codes is compared, and the fault level with the highest priority is selected as the vehicle's global fault level. The priorities of each fault level are pre-set; for example, the priorities of WARNING, ERROR, and FATAL levels are pre-set to increase sequentially, with higher priorities indicating more severe faults. Therefore, this embodiment iterates through the fault levels of all fault codes generated by all modules and selects the most severe fault level as the vehicle's global fault level.

[0101] In this embodiment, the fault code information also includes the human intervention level corresponding to the fault code. For example, the human intervention levels are pre-set to include NotNeeded, LOW, MEDIUM, and HIGH levels, with the priority increasing sequentially, meaning the corresponding faults become increasingly severe.

[0102] After step S300: collecting the generated fault code information, the following steps are also included:

[0103] Extract the corresponding level of human intervention from each of the collected fault code information;

[0104] The global human intervention level of the vehicle is determined based on the human intervention level of each fault code information collected. Specifically, the priority of the human intervention level of each fault code information collected is compared, and the human intervention level with the highest priority is selected as the global human intervention level of the vehicle. Therefore, this embodiment selects the most severe fault level as the global human intervention level of the vehicle by traversing the human intervention levels of all fault codes generated by all modules.

[0105] Based on the vehicle's overall human intervention level, select the corresponding fault reset condition. Here, the fault reset condition refers to the human operation conditions required for the vehicle to return to the driving state before the fault occurred.

[0106] The system pre-defines the correspondence between various global human intervention levels and fault reset conditions. For example, at the NotNeeded level, the vehicle's responses after a fault can be automatically recovered, meaning the autonomous vehicle can automatically resume operation. Low, Medium, and High levels all require user input (e.g., clicking a button on the terminal's user interface) to manually confirm fault resolution before the autonomous vehicle can continue operating. The user actions differ for each level. For instance, at the LOW level, a single button click confirms fault resolution; at the MEDIUM level, the user needs to check the vehicle's operating status and confirm it's normal before confirming fault resolution; and at the HIGH level, the user needs to physically inspect the vehicle before confirming fault resolution. Specifically, the human intervention levels and corresponding fault reset conditions can be selected and set as needed.

[0107] like Figure 4 As shown, in this embodiment, after step S400: selecting the corresponding vehicle control strategy, the following steps are also included:

[0108] S510: Control the vehicle's actuator according to the corresponding vehicle control strategy, so that the vehicle enters the second state from the first state; here the first state is the normal operating state before the vehicle's actuator executes the vehicle control strategy, and the second state is the operating state after the vehicle's actuator executes the vehicle control strategy. For example, if the vehicle control strategy is to decelerate the vehicle, then the first state is the state before the vehicle decelerates, and the second state is the state after the vehicle decelerates.

[0109] S520: Determine whether the fault reset condition is met; that is, whether the user has performed the operation corresponding to the fault reset condition.

[0110] If the condition is met, then S530: Control the actuator of the vehicle to return the vehicle to the first state and the vehicle continues to perform the operation;

[0111] Otherwise, the vehicle still poses a safety hazard, and S540 is executed: the vehicle remains in the second state until the user performs the operation corresponding to the fault reset condition.

[0112] Table 1 below illustrates, for example, the correspondence between vehicle control strategies and fault reset conditions for several fault levels and manual intervention levels.

[0113] Table 1

[0114]

[0115] Table 1 categorizes vehicle fault levels into INFO, WARN, ERROR, and FATAL, with increasing priority. The corresponding vehicle control strategies are: no special operation, vehicle deceleration, vehicle deceleration to a stop, and emergency stop. Human intervention levels are divided into NotNeeded, Low, Medium, and High. The corresponding fault reset conditions are: none, Level 1 concern, Level 2 concern, and Level 3 concern. For example, if the current global fault level is WARNING and the global human intervention level is NotNeeded, after the vehicle decelerates and the global fault level returns to INFO, the vehicle can accelerate back to its previous speed and resume normal operation without user confirmation. If the current global fault level is WARNING and the global human intervention level is LOW, the current vehicle control strategy is deceleration. After the user selects the confirmation button on the user terminal, the global fault level can be reset, and the autonomous vehicle can return to its working state before deceleration and continue normal operation.

[0116] Table 1 above illustrates only one exemplary implementation. In other alternative implementations, fault levels may be classified in other ways, and the corresponding vehicle control strategies may be adjusted as needed. Manual intervention levels may be classified in other ways, and the corresponding fault reset conditions may be adjusted as needed.

[0117] In this embodiment, the vehicle operating status monitoring method further includes the following steps:

[0118] A strategy configuration page is provided, which includes a vehicle control strategy configuration area and a fault reset condition configuration area. This strategy configuration page can be pushed to the user's terminal device, and the user can use the terminal device to configure the vehicle control strategy and / or fault reset condition on the strategy configuration page.

[0119] The user sets the correspondence between each fault level and the vehicle control strategy according to the configuration information in the vehicle control strategy configuration area; and / or sets the correspondence between each human intervention level and the fault reset condition according to the configuration information in the fault reset condition configuration area.

[0120] Therefore, by providing a strategy configuration page, users can freely configure vehicle control strategies corresponding to various fault levels, and also freely configure fault reset conditions corresponding to various levels of human intervention. For example, users can modify the vehicle control strategy for the WARNING level to decelerate and stop, or modify the fault reset condition for the MEDIUM level to level two concern. Furthermore, level one, level two, and level three concern can themselves serve as configuration interfaces, allowing users to freely configure the actions required for different levels of concern. Thus, by providing a strategy configuration page, the different needs of different vehicle types in different scenarios can be met, ensuring vehicle safety while preventing unreasonable vehicle control strategies and fault reset conditions from affecting normal vehicle operation.

[0121] In this embodiment, step S200, determining whether to generate a preset type of fault code based on the operating status, includes the following steps:

[0122] For each type of operating status, determine whether it meets the generation conditions of the corresponding type of fault code; specifically, this includes: for each type, determining whether the parameter value of the operating status parameter belongs to the parameter value range of each type of fault code;

[0123] If so, generate the corresponding type of fault code, and obtain the fault occurrence time, fault level, human intervention level and fault information description corresponding to the fault code, and generate fault code information.

[0124] Specifically, the generation conditions, fault levels, and human intervention levels for various fault codes are pre-set. The generation conditions for the fault codes include the parameter value range of specific operating state parameters. For example, for a hardware module, the generation conditions for fault code A are set as follows: data frequency is lower than a first threshold; the generation conditions for fault code B are set as follows: data timeout is lower than a second threshold; and the generation conditions for fault code C are set as follows: network latency is greater than a third threshold. Then, if the data frequency, data timeout, and network latency of a hardware module are obtained and the generation conditions for fault code A are met, fault code A is generated, and the fault level of fault code A is found to be WARNING and the human intervention level is Low.

[0125] In this embodiment, the generation conditions, fault level, and human intervention level corresponding to each fault code can also be configured by the user as needed. The vehicle operating status monitoring method further includes the following steps:

[0126] A fault code configuration page is provided, which includes a fault code generation condition configuration area and a level configuration area. The fault code configuration page can be pushed to the user terminal used by the user. The user can view the fault code configuration page through the user terminal and configure one or more fault codes, specifically including configuring their generation conditions and / or configuring the conditions corresponding to the fault codes.

[0127] The user sets the fault code generation conditions according to the configuration information in the generation condition configuration area; and / or sets the fault level and / or human intervention level corresponding to the fault code according to the configuration information in the level configuration area.

[0128] For example, users can set the parameter value range for the operating parameters corresponding to the fault code, adjusting the upper / lower limit of the parameter value range. They can also set the fault level corresponding to the fault code; for example, if a fault code requires special attention, its fault level can be increased. Alternatively, they can set the level of human intervention corresponding to the fault code.

[0129] This invention also provides a vehicle operation status monitoring device, including a processor; a memory storing executable instructions of the processor; wherein the processor is configured to execute the steps of the vehicle operation status monitoring method by executing the executable instructions.

[0130] Those skilled in the art will understand that various aspects of the present invention can be implemented as systems, methods, or program products. Therefore, various aspects of the present invention can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software aspects, collectively referred to herein as a "circuit," "module," or "platform."

[0131] The following reference Figure 5 To describe an electronic device 600 according to this embodiment of the present invention. Figure 5 The electronic device 600 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0132] like Figure 5 As shown, the electronic device 600 is presented in the form of a general-purpose computing device. The components of the electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one storage unit 620, a bus 630 connecting different system components (including storage unit 620 and processing unit 610), a display unit 640, etc.

[0133] The storage unit stores program code that can be executed by the processing unit 610, causing the processing unit 610 to perform the steps described in the above-described vehicle operation status monitoring method section of this specification, according to various exemplary embodiments of the present invention. For example, the processing unit 610 can perform, as follows: Figure 1 The steps are shown in the figure.

[0134] The storage unit 620 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 6201 and / or a cache storage unit 6202, and may further include a read-only memory unit (ROM) 6203.

[0135] The storage unit 620 may also include a program / utility 6204 having a set (at least one) program module 6205, such program module 6205 including but not limited to: an operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.

[0136] Bus 630 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0137] Electronic device 600 can also communicate with one or more external devices 700 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with electronic device 600, and / or with any device that enables electronic device 600 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 650. Furthermore, electronic device 600 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 660. Network adapter 660 can communicate with other modules of electronic device 600 via bus 630. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0138] In the vehicle operation status monitoring device, when the program in the memory is executed by the processor, it implements the steps of the vehicle operation status monitoring method. Therefore, the device can also achieve the technical effects of the above-mentioned vehicle operation status monitoring method.

[0139] This invention also provides a computer-readable storage medium for storing a program that, when executed by a processor, implements the steps of the vehicle operation status monitoring method. In some possible implementations, various aspects of the invention can also be implemented as a program product comprising program code, which, when executed on a terminal device, causes the terminal device to perform the steps described in the above-described vehicle operation status monitoring method section of this specification according to various exemplary embodiments of the invention.

[0140] refer to Figure 6 As shown, a program product 800 for implementing the above-described method according to an embodiment of the present invention is described. It may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may be executed on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, the readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.

[0141] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0142] The computer-readable storage medium may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The readable storage medium may also be any readable medium other than a readable storage medium, capable of transmitting, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0143] Program code for performing the operations of this invention can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0144] When the program in the computer storage medium is executed by the processor, it implements the steps of the vehicle operation status monitoring method. Therefore, the computer storage medium can also achieve the technical effects of the above-mentioned vehicle operation status monitoring method.

[0145] The above description, in conjunction with specific preferred embodiments, provides a further detailed explanation of the present invention. It should not be construed that the specific implementation of the present invention is limited to these descriptions. For those skilled in the art, various simple deductions or substitutions can be made without departing from the concept of the present invention, and all such modifications and substitutions should be considered within the scope of protection of the present invention.

Claims

1. A method for monitoring vehicle operating status, characterized in that, Includes the following steps: Monitor the operating status of each module of the vehicle's preset type; Based on the operating status, determine whether to generate a preset type of fault code; Collect generated fault code information, which includes the generated fault code, the corresponding fault level, and the human intervention level corresponding to the fault code; The overall fault level of the vehicle is determined based on the fault level of each fault code information collected. Based on the vehicle's global fault level, select the corresponding vehicle control strategy; After collecting and generating the fault code information, the following steps are also included: Extract the corresponding level of human intervention from each of the collected fault code information; The overall human intervention level of the vehicle is determined based on the human intervention level of each fault code information collected. Based on the pre-defined correspondence between various global human intervention levels and fault reset conditions, and based on the vehicle's global human intervention level, the corresponding fault reset condition is selected. The fault reset condition is the human operation condition required for the vehicle to return to the driving state before the fault occurred. The human operation condition includes automatic recovery and requires a user input to manually confirm the fault resolution. After selecting the corresponding vehicle control strategy, the following steps are also included: The vehicle's actuators are controlled according to the corresponding vehicle control strategy, causing the vehicle to transition from the first state to the second state. Determine whether the fault reset condition is met; If the condition is met, the vehicle's actuators are controlled to return the vehicle to the first state; Otherwise, the vehicle remains in the second state; The method further includes the following steps: A strategy configuration page is provided, which includes a vehicle control strategy configuration area and a fault reset condition configuration area. The user sets the correspondence between each level of human intervention and the fault reset condition based on the configuration information in the fault reset condition configuration area.

2. The vehicle operation status monitoring method according to claim 1, characterized in that, Determining the vehicle's overall fault level based on the fault levels of the collected fault code information includes the following steps: Extract the corresponding fault level from each of the collected fault code information; The priority of the fault levels of the collected fault codes is compared, and the fault level with the highest priority is selected as the global fault level of the vehicle.

3. The vehicle operation status monitoring method according to claim 1, characterized in that, The process of determining the overall human intervention level of the vehicle based on the human intervention levels of the collected fault code information includes the following steps: The priority of the human intervention levels of the collected fault code information is compared, and the human intervention level with the highest priority is selected as the global human intervention level for the vehicle.

4. The vehicle operation status monitoring method according to claim 1, characterized in that, Determining whether to generate a preset type of fault code based on the operating status includes the following steps: For each type of operating status, determine whether it meets the generation conditions for the corresponding type of fault code; If so, generate the corresponding type of fault code, obtain the fault level and human intervention level corresponding to the fault code, and generate fault code information.

5. The vehicle operation status monitoring method according to claim 1, characterized in that, It also includes the following steps: The user sets the correspondence between each fault level and the vehicle control strategy based on the configuration information in the vehicle control strategy configuration area.

6. The vehicle operation status monitoring method according to claim 1, characterized in that, The monitoring of the operating status of each module of the preset type of vehicle includes: Monitor at least one of the following: the system resource usage status of each system module of the vehicle, the software operation status of each software module, and the hardware operation status of each hardware module.

7. The vehicle operation status monitoring method according to claim 6, characterized in that, The preset fault codes include system fault codes, software fault codes, and hardware fault codes. Determining whether to generate a preset fault code based on the operating status includes the following steps: Determine whether to generate a system fault code based on the system resource occupancy status of the vehicle's system modules; Determine whether to generate a software fault code based on the software operating status of the vehicle's software modules. The system determines whether to generate a hardware fault code based on the hardware operating status of the vehicle's hardware modules.

8. The vehicle operation status monitoring method according to claim 4, characterized in that, The operating status includes the parameter values ​​of the operating status parameters, and the generation conditions of the fault code include at least one range of parameter values ​​for the operating status parameters. The process of determining whether each type of operating state meets the generation conditions for the corresponding type of fault code includes the following steps: For each type, determine whether the parameter value of the operating status parameter belongs to the parameter value range of each fault code of that type; If so, then determine to generate the corresponding fault code for that type.

9. The vehicle operation status monitoring method according to claim 8, characterized in that, It also includes the following steps: A fault code configuration page is provided, which includes a fault code generation condition configuration area and a level configuration area; The user sets the fault code generation conditions according to the configuration information in the generation condition configuration area; And / or, set the fault level and / or human intervention level corresponding to the fault code according to the configuration information of the user in the level configuration area.

10. A vehicle operation status monitoring system, characterized in that, The system for implementing the vehicle operation status monitoring method according to any one of claims 1 to 9, the system comprising: The status monitoring module is used to monitor the operating status of various modules of the vehicle in a preset type; The status determination module is used to determine whether to generate a preset type of fault code based on the operating status; The fault level determination module is used to collect generated fault code information, which includes the generated fault code and the corresponding fault level, and to determine the vehicle's global fault level based on the fault level of each collected fault code. The strategy selection module is used to select the corresponding vehicle control strategy based on the vehicle's global fault level.

11. A vehicle operation status monitoring device, characterized in that, include: processor; A memory in which executable instructions of the processor are stored; The processor is configured to perform the steps of the vehicle operating status monitoring method according to any one of claims 1 to 9 by executing the executable instructions.

12. A computer-readable storage medium for storing a program, characterized in that, When the program is executed by the processor, it implements the steps of the vehicle operation status monitoring method according to any one of claims 1 to 9.

Images