Log processing method and system of auxiliary driving system and storage medium

Abstract

The invention relates to the technical field of automatic driving, and provides a log processing method and system for an auxiliary driving system and a storage medium, and the method comprises the steps: generating a trigger instruction corresponding to a target application module according to a log trigger request based on the corresponding target application module and a to-be-output log type; and sending the trigger command to a target application module to realize that the target application module extracts the log of the log type from a module operation log cache region and / or a problem investigation log cache region and outputs the log. The technical effects that intelligent triggering can be achieved, cross-application linkage is supported, and key contexts before and after a fault can be completely stored are achieved.

Description

Technical Field

[0001] This invention relates to the field of autonomous driving technology, and in particular to a log processing method, system, and computer-readable storage medium for an assisted driving system. Background Technology

[0002] Logs in intelligent driving systems serve as the core basis for recording operational status, locating root causes of faults, and evaluating performance. The efficiency of their management mechanism directly impacts system maintainability. However, the traditional logging mode, which commonly adopts continuous full output, has the following technical drawbacks in assisted driving scenarios: 1) High-priority and low-priority logs are mixed in output. When sporadic or related faults occur, the high-priority logs necessary for problem localization are often obscured by irrelevant information streams, leading to low problem localization efficiency; 2) Continuous output mode consumes a large amount of system resources for a long time. In resource-constrained in-vehicle embedded environments, this affects the real-time performance of embedded systems, thus posing a potential threat to driving safety; 3) Due to limitations in in-vehicle hardware memory capacity, traditional solutions typically cannot cache historical logs for a sufficient time span locally. For sporadic defects triggered by specific state sequences that are difficult to reproduce, the failure to retain key system state and environmental data before the fault occurs results in a lack of clues for root cause analysis; 4) In multi-application collaborative scenarios, the lack of a unified log triggering mechanism makes it difficult to achieve a comprehensive analysis of related faults.

[0003] In existing technologies, improvements have been made by dynamically adjusting log levels and using log caching based on circular buffers, but these still cannot achieve intelligent log triggering based on system status and cross-application linkage, thus failing to meet the problem diagnosis needs of complex embedded systems such as intelligent driving.

[0004] Therefore, there is an urgent need for an efficient log management method that can intelligently trigger, support cross-application linkage, and completely save the key context before and after a fault, while meeting the real-time requirements and resource constraints of the vehicle system. Summary of the Invention

[0005] This invention provides a log processing method, system, and storage medium for an assisted driving system to solve at least one problem existing in the prior art.

[0006] To achieve the above objectives, the present invention adopts the following technical solution: In a first aspect, embodiments of the present invention provide a log processing method for an assisted driving system, applied to an electronic device, comprising: Obtain a log trigger request, determine the target application module corresponding to the log trigger request according to a preset mapping relationship, and obtain the log type to be output; wherein, each application module includes a module operation log cache area for caching regular operation logs, and a problem investigation log cache area for caching specific problem investigation logs; Based on the target application module and the log type to be output, a trigger instruction corresponding to the target application module is generated according to the log trigger request; Send a corresponding trigger command to the target application module so that the target application module can extract and output the logs of the specified log type from the module operation log cache and / or the problem investigation log cache.

[0007] Alternatively, an optional technical solution is to receive trigger requests from at least one trigger source through a central log management module.

[0008] In addition, an optional technical solution is that the triggering request of the triggering source includes at least one of the following: The triggering source is the target application module itself, and the triggering request is a self-triggered request generated based on the internal logic of the target application module itself. The triggering source is an initiating application that is different from the target application module; The trigger source is the system status monitoring module, and the trigger request is a trigger request generated based on the monitored vehicle driving status data meeting preset conditions.

[0009] In addition, an optional technical solution is that the log triggering request includes a time range parameter; The trigger command controls the target application module to output cached logs within a specified time range.

[0010] In addition, optional technical solutions also include: The application module is provided with a first log printing interface for printing regular operation logs to the module operation log cache area; A second log printing interface is provided for the application module to print specific problem investigation logs to the problem investigation log cache.

[0011] In addition, an optional technical solution is that the problem investigation log cache area includes multiple areas, each of which is used to cache different specific problem investigation logs; wherein the cache size of each problem investigation log cache area is configured according to preset conditions.

[0012] In addition, an optional technical solution is that the triggering command controls the target application module to output at least one of the following logs: Only output logs from the module's runtime log cache; Output only the logs in the specified issue investigation log buffer; It also outputs logs from the module's runtime log cache and logs from the specified issue investigation log cache.

[0013] Secondly, the present invention provides a log processing system for an assisted driving system, comprising: a trigger request acquisition unit, configured to acquire a log trigger request, determine the target application module corresponding to the log trigger request according to a preset mapping relationship, and acquire the log type to be output; wherein, each application module includes a module operation log cache area for caching regular operation logs, and a problem investigation log cache area for caching specific problem investigation logs; The trigger instruction generation unit is used to generate a trigger instruction corresponding to the target application module based on the corresponding target application module and the log type to be output, according to the log trigger request. The log output unit is used to send a corresponding trigger command to the target application module so that the target application module can extract and output the logs of the specified log type from the module operation log cache and / or the problem investigation log cache.

[0014] Thirdly, the present invention provides an electronic device, the electronic device including a memory, a processor, and a log processing program for an assisted driving system stored in the memory and executable on the processor, wherein the log processing program for the assisted driving system, when executed by the processor, implements the log processing method for the assisted driving system as described above.

[0015] Fourthly, embodiments of the present invention provide a computer-readable storage medium storing instructions that, when executed on an electronic device, cause the electronic device to perform a log processing method for an assisted driving system as described in any of the first aspects.

[0016] Based on the log processing method, system, and storage medium of the assisted driving system of the present invention, a unified log collection command channel is established through the CacheLogMgr management hub and a standardized cross-application triggering mechanism. When facing related faults involving multiple functional modules, all relevant applications can be triggered to synchronously output their cached logs with a single click. The present invention supports dynamic configuration of multiple dimensions such as cache size, log level, trigger conditions, and output time range, and adopts a plug-in framework to manage the triggering logic. This allows the same log system to flexibly adapt to various vehicle application scenarios, from simple to complex, from performance analysis to safety fault diagnosis, with strong scalability and low maintenance costs. It achieves the technical effects of intelligent triggering, support for cross-application linkage, and complete preservation of key context before and after a fault.

[0017] Understandably, the system described in the second aspect, the electronic device described in the third aspect, and the computer storage medium described in the fourth aspect are all used to execute the corresponding method in the first aspect provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding method provided above, and will not be repeated here. Attached Figure Description

[0018] Figure 1 A flowchart illustrating the log processing method of the driver assistance system provided in this application embodiment; Figure 2 A schematic diagram of the system architecture for the log processing method of the assisted driving system provided in this application embodiment; Figure 3 A schematic diagram of the dual-buffering mechanism inside the application module of the log processing method for the assisted driving system provided in this embodiment of the application; Figure 4 A schematic diagram illustrating the principle of self-triggered application of the log processing method for the assisted driving system provided in this application embodiment; Figure 5 A schematic diagram illustrating the principle of cross-application triggering of the log processing method for the assisted driving system provided in this application embodiment; Figure 6 A schematic diagram illustrating the principle of system condition triggering for the log processing method of the assisted driving system provided in this application embodiment; Figure 7 A block diagram of a log processing system for an assisted driving system provided in an embodiment of this application; Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0019] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0020] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0021] This invention provides a log processing method for a driver assistance system. (Refer to...) Figure 1 The diagram shown is a flowchart illustrating the log processing method of the driver assistance system provided in an embodiment of the present invention. Figure 2 This is a schematic diagram of the system architecture for the log processing method of the assisted driving system provided in the embodiments of this application; the method can be executed by a device, which can be implemented by software and / or hardware.

[0022] like Figure 1 As shown, the present invention provides a log processing method for an assisted driving system, comprising the following steps.

[0023] S110. Obtain a log trigger request, determine the target application module corresponding to the log trigger request according to a preset mapping relationship, and obtain the log type to be output; wherein, each application module includes a module operation log cache area for caching regular operation logs, and a problem investigation log cache area for caching specific problem investigation logs.

[0024] like Figure 2 As shown, the system architecture of the log processing method for the assisted driving system of the present invention includes multiple application modules, a central log management module, and multiple trigger sources. Each application module contains an independent module operation log cache area and a problem investigation log cache area. In specific implementation, the central log management module is the CacheLogMgr central management hub. That is, trigger requests from at least one trigger source are processed through the central log management module. The CacheLogMgr central management hub is the core control unit in the system responsible for receiving, managing, and forwarding all log trigger requests. Its core functions include maintaining trigger configurations, monitoring system conditions, forwarding trigger requests, and a plug-in condition judgment mechanism that supports a combination of static configuration and dynamic triggering. For trigger configuration management, static configurations are read from configuration files to maintain the mapping relationship between trigger requests and target applications. For monitoring system conditions, system status data is subscribed to, and trigger condition judgment is implemented using plug-in custom code. For trigger management, trigger requests are converted into trigger commands according to the configuration and sent to the target applications. Specifically, the log context of all applications is registered with the CacheLogMgr central management hub. When an application needs to output logs, CacheLogMgr quickly locates the application's context in the registry using its application ID, and then accesses its corresponding cache memory.

[0025] In the specific implementation process, for the target application module corresponding to the log trigger request determined according to the preset mapping relationship, the present invention realizes the standardized forwarding of the trigger request based on the CacheLogMgr management center, and establishes the mapping relationship between the trigger request and multiple target applications through the indexing mechanism of the application and the trigger name.

[0026] Figure 3 This is a schematic diagram of the dual-buffering mechanism within the application module of the log processing method for the assisted driving system provided in this embodiment. Figure 3As shown, this invention employs a dual-caching mechanism, designing a caching strategy based on log type differentiation. Specifically, the module operation log cache and the issue investigation log cache are independent of each other. The module operation log cache is a memory area used for cyclically caching logs generated during the normal operation of the application that are below the current print level. The issue investigation log cache is a memory area used for caching logs printed for specific issue investigation purposes.

[0027] The issue investigation log cache includes multiple caches, each used to cache different specific issue investigation logs. The cache size of each cache is configured according to preset conditions. In implementation, the cache memory blocks of each application are completely independent and do not interfere with each other. A cache overflow in one application will not affect other applications. Parameters such as cache size and log level can be set from the header file at compile time, the configuration file at startup, or the runtime dynamic API. In other words, it can cache issue investigation logs in memory; it can cache multiple different issue investigation logs simultaneously; and the cache size for each cached log can be configured independently. Multiple instances of the issue investigation log cache are managed using a unique label identifier. Utilizing configurable memory caches and combining them with time-sequential output control, it is possible to completely capture and save the system state sequence and environmental data before, during, and after a failure. This provides crucial clues for analyzing the root causes of intermittent defects that are difficult to reproduce.

[0028] It's important to note that the system supports caching multiple investigation logs for different issues simultaneously. Each log is identified by a unique label, and its cache size and enabling status are independently configured to meet the needs of multi-scenario problem diagnosis. In other words, the module runtime log cache is a circular buffer used to cache regular logs by level; the problem investigation log cache is a cache pool indexed by labels, supporting parallel recording of multiple investigation tasks. For example, a dedicated log cache management structure is defined for each application module, containing pointers to its two caches and management information. During application initialization, dedicated cache memory is allocated to each application according to the configuration. The module runtime log cache can be allocated a fixed-size circular array. The problem investigation log cache pool can be allocated an array of cache descriptors, with each descriptor managing an independent investigation log cache. That is, an array of descriptors used to manage multiple problem investigation log caches.

[0029] In a specific embodiment, the system further includes: providing a first log printing interface for the application module to print regular operation logs to the module operation log cache; and providing a second log printing interface for the application module to print specific problem investigation logs to the problem investigation log cache. Specifically, a regular printing interface for module operation logs is provided for printing regular logs. A dedicated printing interface for problem investigation logs is provided for use during specific problem investigations. In the actual implementation, when the application calls the log printing interface, a preset logic determines which partition to write to. When the application calls the printing interface for the module operation log cache, the system automatically writes the logs to a circular cache array under the application context. When the application calls the printing interface for the problem investigation log cache, the system first searches for a matching cache in the descriptor array based on the Label parameter, and then writes the logs to that dedicated area.

[0030] The log trigger request includes a time range parameter; the trigger instruction controls the target application module to output cached logs within a specified time range. The time range parameter includes a historical time period and a future time period relative to the trigger time. It should be noted that, based on level-based intelligent caching, when the log level is between the print level and the cache level, it is automatically written to the circular buffer, achieving on-demand retention of low-priority logs. For example, outputting by time range is supported; relative to the current time, the time range parameter includes a historical time period and a future time period relative to the trigger time; where historical logs can be up to 10 seconds and future logs can be up to 5 seconds. In summary, the output range control for module operation logs is implemented based on time offsets, combined with a custom timestamp transmission mechanism, ensuring the temporal relevance and integrity of the logs.

[0031] S120. Based on the corresponding target application module and the log type to be output, generate a trigger instruction corresponding to the target application module according to the log trigger request.

[0032] In specific implementation, this invention supports three triggering scenarios. Specifically, the triggering request from the triggering source includes at least one of the following: the triggering source is the target application module itself, and the triggering request is a self-triggered request generated based on the internal logic of the target application module. The triggering source is an initiating application different from the target application module. The triggering source is the system status monitoring module, and the triggering request is a triggering request generated based on the monitored vehicle driving status data meeting preset conditions. Flexible triggering source configuration meets the needs of different fault diagnosis scenarios. The traditional continuous log output is converted to a cache-trigger mode, ensuring that the majority of low-priority logs only perform I / O operations when needed. This reduces invalid log I / O writing by an average of over 90%, significantly saving CPU, memory, and storage bandwidth. In environments with limited in-vehicle resources, system real-time performance is guaranteed, eliminating the potential threat to driving safety posed by log system overload.

[0033] For example, Figure 4 A schematic diagram illustrating the principle of self-triggered application of the log processing method for the assisted driving system provided in this application embodiment; as shown Figure 4 As shown, when the application module determines that it needs to output logs based on its internal business logic, it directly calls the trigger interface to output the application's cached logs. Figure 5 This is a schematic diagram illustrating the principle of cross-application triggering of the log processing method for the assisted driving system provided in this application embodiment; as follows: Figure 5 As shown, an application module, acting as the initiator, can send log trigger requests to other application modules via CacheLogMgr to achieve collaborative diagnosis. In other words, by providing a standardized trigger request interface through CacheLogMgr, it supports the transmission of log trigger commands between applications, enabling collaborative collection of logs from multiple applications related to faults. Figure 6 A schematic diagram illustrating the principle of system condition triggering for the log processing method of the assisted driving system provided in this application embodiment; as follows: Figure 6 As shown, the system status monitoring module continuously monitors preset conditions, and automatically triggers relevant applications to output logs when the conditions are met via CacheLogMgr. Specifically, the system condition monitoring module monitors system status by subscribing to vehicle status table data, and automatically triggers relevant applications to output cached logs when preset conditions are met. By supporting multiple scenarios such as self-triggered, cross-application triggered, and system condition triggered, it meets the diagnostic needs of different fault types.

[0034] By employing a dual-caching mechanism to hierarchically and categorize logs, and combining multi-scenario triggering to achieve on-demand and precise output, the problem of mixed high-priority and low-priority logs is fundamentally solved. When a fault occurs, key logs strongly related to the problem can be directly retrieved, reducing the diagnosis and localization time of intermittent and related problems by more than 70%, and ensuring that critical information is no longer overwhelmed by irrelevant log streams.

[0035] S130. Send a corresponding trigger command to the target application module so that the target application module can extract and output the logs of the log type from the module operation log cache and / or problem investigation log cache.

[0036] The trigger command controls the target application module to output at least one of the following logs: output only the logs in the module operation log cache; output only the logs in the specified problem investigation log cache; or output both the logs in the module operation log cache and the logs in the specified problem investigation log cache simultaneously. In other words, in specific implementations, depending on the specific driving scenario, a trigger command interface is provided for in-application or external calls to trigger the output of cached logs; for example, only the module operation log can be output; only the problem investigation log can be output; or both the module operation log and one of the problem investigation logs can be output simultaneously.

[0037] For example, the API interface definition for triggering the output of cached logs is as follows: Cint Flog_flushCacheLog(AppID_t appID, LogLevel_t logLevel, inttmOffset_sta, int tmOffset_end, String LogLabel); Where appID is the name of the module whose logs are to be output; logLevel is the level of the module's running logs that trigger the output; tmOffset_sta / tmOffset_end is the time range of the logs that trigger the output; and LogLabel is the label of the issue investigation logs to be output.

[0038] For example, in an automated driving assistance system, when the ParkPlan application detects a parking failure, it triggers the Name2 trigger to simultaneously collect cached logs from related applications such as ParkObsFusion and ParkLocation. This comprehensively records the environmental perception data and decision-making process before and after the failure, significantly improving the efficiency of fault reproduction and localization. Through the system condition monitoring module, when CPU utilization is detected to continuously exceed a threshold, it automatically triggers relevant applications to output DEBUG-level logs, enabling preliminary location of performance bottlenecks without manual intervention and shortening the problem analysis cycle.

[0039] The log processing method of the assisted driving system of the present invention differs from the existing technology in that it suffers from continuous high resource consumption, single application logs, and weak correlation. The present invention provides a log cache and a problem investigation log cache through independent modules, which realize differentiated storage and trigger output of different types of logs. The problem investigation log is identified by a unique label to realize parallel management of multiple cache areas. Compared with the poor configuration flexibility and single log output of the existing technology, the present invention realizes system status monitoring by subscribing to vehicle status table data, and uses plug-in customized code to embed CacheLogMgr, which supports dynamic expansion of trigger condition judgment logic. The serialized processing of trigger output tasks adopts a batch smooth output strategy to avoid log loss caused by excessive instantaneous log traffic, and at the same time records discarded trigger requests to ensure traceability.

[0040] like Figure 7 The diagram shown is a block diagram of the log processing system of the driver assistance system of the present invention.

[0041] The log processing system 100 of the assisted driving system described in this invention can be installed in an electronic device. Depending on the functions implemented, the log processing system 100 may include: a trigger request acquisition unit 101, a trigger instruction generation unit 102, and a log output unit 103. The unit described in this invention can also be called a module, which mainly refers to a series of computer program segments that can be executed by the processor of an electronic device and can perform a fixed function, and which are stored in the memory of the electronic device.

[0042] In this embodiment, the functions of each module / unit are as follows: Trigger request acquisition unit 101 is used to acquire log trigger requests, determine the target application module corresponding to the log trigger request according to a preset mapping relationship, and acquire the log type to be output; wherein, each application module includes a module operation log cache area for caching regular operation logs, and a problem investigation log cache area for caching specific problem investigation logs; The trigger instruction generation unit 102 is used to generate a trigger instruction corresponding to the target application module based on the corresponding target application module and the log type to be output, according to the log trigger request. The log output unit 103 is used to send a corresponding trigger command to the target application module so that the target application module can extract and output the log of the log type from the module operation log cache and / or the problem investigation log cache.

[0043] The log processing system 100 of the assisted driving system described in this invention provides a complete local path planning system based on scene recognition, adaptive weight adjustment, trajectory optimization, and trajectory verification. Through a dynamic weight adaptive mechanism, it can adapt to various complex scenarios such as low-speed parking, high-speed cruising, emergency obstacle avoidance, and lane changing / overtaking. By adaptively adjusting the control quantity to smooth the weights, it avoids abrupt changes in control quantity, improving ride comfort. Through a hard constraint mechanism at the end of the trajectory, it avoids lateral overshoot or heading angle deviation at the end. Through adaptive regularization and dynamic step size search mechanisms, it improves algorithm convergence efficiency and meets real-time requirements.

[0044] It should be noted that the embodiments of the log processing system of the above-mentioned driver assistance system and the embodiments of the log processing method of the driver assistance system can be used for reference, and will not be described in detail here.

[0045] Figure 8 This is a schematic diagram of the electronic device that implements the log processing method of the driver assistance system according to the present invention.

[0046] like Figure 8 As shown, the electronic device 1 may include a processor 10, a memory 11 and a bus, and may also include a computer program stored in the memory 11 and executable on the processor 10, such as a log processing program 12 for an assisted driving system.

[0047] The memory 11 includes at least one type of readable storage medium, such as flash memory, portable hard drive, multimedia card, card-type memory (e.g., SD or DX memory), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 11 can be an internal storage unit of the electronic device 1, such as a portable hard drive. In other embodiments, the memory 11 can be an external storage device of the electronic device 1, such as a plug-in portable hard drive, smart media card (SMC), secure digital card (SD), flash card, etc., equipped on the electronic device 1. Furthermore, the memory 11 can include both internal and external storage units of the electronic device 1. The memory 11 can be used not only to store application software and various types of data installed on the electronic device 1, such as the code of the log processing program for an assisted driving system, but also to temporarily store data that has been output or will be output.

[0048] In some embodiments, the processor 10 may be composed of integrated circuits, such as a single packaged integrated circuit or multiple integrated circuits packaged with the same or different functions, including combinations of one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and various control chips. The processor 10 is the control unit of the electronic device, connecting various components of the entire electronic device through various interfaces and lines. It executes programs or modules stored in the memory 11 (e.g., log processing programs for assisted driving systems) and calls data stored in the memory 11 to perform various functions of the electronic device 1 and process data.

[0049] The bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. This bus can be divided into an address bus, a data bus, a control bus, etc. The bus is configured to enable communication between the memory 11 and at least one processor 10, etc.

[0050] Figure 8 Only electronic devices with components are shown; it will be understood by those skilled in the art that... Figure 8 The structure shown does not constitute a limitation on the electronic device 1, and may include fewer or more components than shown, or combine certain components, or have different component arrangements.

[0051] For example, although not shown, the electronic device 1 may also include a power supply (such as a battery) to power the various components. Preferably, the power supply can be logically connected to the at least one processor 10 through a power management device, thereby enabling functions such as charging management, discharging management, and power consumption management. The power supply may also include one or more DC or AC power supplies, recharging devices, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components. The electronic device 1 may also include various sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be described in detail here.

[0052] Furthermore, the electronic device 1 may also include a network interface. Optionally, the network interface may include a wired interface and / or a wireless interface (such as a Wi-Fi interface, a Bluetooth interface, etc.), which is typically used to establish communication connections between the electronic device 1 and other electronic devices.

[0053] Optionally, the electronic device 1 may further include a user interface, which may be a display, an input unit (such as a keyboard), and optionally, a standard wired interface or a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, or an OLED (Organic Light-Emitting Diode) touchscreen, etc. The display may also be appropriately referred to as a screen or display unit, used to display information processed in the electronic device 1 and to display a visual user interface.

[0054] It should be understood that the embodiments described are for illustrative purposes only and are not limited to this structure in the scope of the patent application.

[0055] The log processing program 12 of the driver assistance system stored in the memory 11 of the electronic device 1 is a combination of multiple instructions. When it is run in the processor 10, it can implement the log processing method of the driver assistance system.

[0056] Furthermore, if the modules / units integrated in the electronic device 1 are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. The computer-readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, or a read-only memory (ROM).

[0057] In the several embodiments provided by this invention, it should be understood that the disclosed devices, systems, and methods can be implemented in other ways. For example, the system embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and other division methods may be used in actual implementation.

[0058] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention.

Claims

1. A log processing method for a driver assistance system, applied to electronic devices, characterized in that, The method includes: Obtain a log trigger request, determine the target application module corresponding to the log trigger request according to a preset mapping relationship, and obtain the log type to be output; wherein, each application module includes a module operation log cache area for caching regular operation logs, and a problem investigation log cache area for caching specific problem investigation logs; Based on the target application module and the log type to be output, a trigger instruction corresponding to the target application module is generated according to the log trigger request; Send a corresponding trigger command to the target application module so that the target application module can extract and output logs of the specified log type from the module operation log cache and / or the problem investigation log cache.

2. The log processing method for the driver assistance system as described in claim 1, characterized in that, The central log management module receives trigger requests from at least one trigger source.

3. The log processing method for the driver assistance system as described in claim 2, characterized in that, The triggering request from the triggering source includes at least one of the following: The triggering source is the target application module itself, and the triggering request is a self-triggered request generated based on the internal logic of the target application module itself. The triggering source is an initiating application that is different from the target application module; The trigger source is the system status monitoring module, and the trigger request is a trigger request generated based on the monitored vehicle driving status data meeting preset conditions.

4. The log processing method for the driver assistance system as described in claim 1, characterized in that, The log trigger request includes a time range parameter; The trigger command controls the target application module to output cached logs within a specified time range.

5. The log processing method for the driver assistance system as described in claim 1, characterized in that, Also includes: The application module is provided with a first log printing interface for printing regular operation logs to the module's operation log cache. A second log printing interface is provided for the application module to print specific problem investigation logs to the problem investigation log cache.

6. The log processing method for the driver assistance system as described in claim 1, characterized in that, The issue investigation log cache area includes multiple areas, each of which is used to cache different specific issue investigation logs; the cache size of each issue investigation log cache area is configured according to preset conditions.

7. The log processing method for the driver assistance system as described in claim 1, characterized in that, The trigger command controls the target application module to output at least one of the following logs: Only output the logs in the module's runtime log cache; Output only the logs in the specified issue investigation log buffer; Simultaneously, the logs in the module's running log cache and the logs in the specified problem investigation log cache are output.

8. A log processing system for a driver assistance system, characterized in that, include: The trigger request acquisition unit is used to acquire log trigger requests, determine the target application module corresponding to the log trigger request according to a preset mapping relationship, and acquire the log type to be output; wherein, each application module includes a module operation log cache area for caching regular operation logs, and a problem investigation log cache area for caching specific problem investigation logs; The trigger instruction generation unit is used to generate a trigger instruction corresponding to the target application module based on the corresponding target application module and the log type to be output, according to the log trigger request. The log output unit is used to send a corresponding trigger command to the target application module so that the target application module can extract and output logs of the log type from the module operation log cache and / or the problem investigation log cache.

9. An electronic device, characterized in that, The system includes a memory, a processor, and a log processing program for an assisted driving system stored in the memory and executable on the processor. When executed by the processor, the log processing program for the assisted driving system implements the log processing method for an assisted driving system as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing instructions, characterized in that, When the instruction is executed on the electronic device, the electronic device causes the electronic device to perform the log processing method of the driver assistance system as described in any one of claims 1-7.

Images