Display screen log management method and system and storage medium

Abstract

The invention provides a display screen log management method and system and a storage medium, and is mainly characterized in that a log storage component is configured for each display screen, the log storage component at least comprises a starting area and a log management area, and the log management area comprises a plurality of storage pages; the display screen log management method comprises the steps of collecting log data of a display screen in real time and caching the log data to a storage queue; writing the log data into the log management area based on a starting guide unit stored in a starting area; wherein when any storage page in the log management area is fully written, a boot start unit updating request is sent out, so that the boot start unit is updated; and reading target log data from the log management area based on a received log reading instruction, and exporting the target log data based on a preset communication protocol. According to the method, independent storage of the display screen log data is realized, and the analysis difficulty and the operation and maintenance cost of the display screen log are remarkably reduced.

Description

Technical Field

[0001] This application belongs to the field of automotive electronics technology, specifically relating to a display screen log management method, system, and storage medium. Background Technology

[0002] With the rapid development of automotive electronics technology, the split screen, as a core component of human-machine interaction, undertakes important tasks such as information display, user interaction, and entertainment functions, and its application in automobiles is becoming increasingly widespread. However, as the functions of the split screen become more complex and intelligent, various problems that are difficult to reproduce may occur during system operation. When detailed log records are lacking, developers and maintenance personnel cannot accurately trace the context and root cause of the problem, greatly increasing the difficulty of problem analysis.

[0003] Currently, the log storage for the split screen relies entirely on the vehicle's infotainment system. However, with the continuous addition of functions, the storage resources and processing capabilities of the infotainment system are limited, sometimes unable to provide independent and efficient log storage for the split screen. This results in the split screen's log data not being recorded, making it difficult for developers and maintenance personnel to obtain sufficient log data for analysis and troubleshooting when problems occur, severely impacting problem-solving efficiency. Because the split screen lacks an independent log storage mechanism, critical data such as its operating status, user operations, and error messages cannot be fully recorded, leading to a lack of sufficient contextual information for problem analysis when issues occur. Summary of the Invention

[0004] To address the aforementioned technical issues, this application proposes a display screen log management method, system, and storage medium, aiming to provide independent log storage for vehicle-mounted displays or split screens, thereby improving log management efficiency and problem-solving efficiency.

[0005] Specifically, this application configures a log storage component for each display screen, the log storage component including at least a startup area and a log management area, the log management area including multiple storage pages; the proposed display screen log management method includes: Log data from the display screen is collected in real time and cached in a storage queue.

[0006] The log data is written to the log management area based on the boot boot unit stored in the boot area; wherein, when any storage page in the log management area is full, a boot boot unit update request is issued to update the boot boot unit.

[0007] Furthermore, the system reads target log data from the log management area based on the received log read command and exports the target log data based on a preset communication protocol.

[0008] In the above technical solution, by configuring an independent log storage component for each display screen, independent storage of display screen log data is achieved, ensuring the integrity of log data, reducing the difficulty and cost of display screen log analysis, and improving the efficiency of display screen problem solving. By caching log data to a storage queue before writing it to the log management area, the smoothness and stability of log data storage are ensured. Reading target log data from the log management area improves the efficiency and accuracy of log data querying. Exporting the target log data through a preset communication protocol avoids disassembling the display screen, thereby effectively improving the efficiency of log data analysis.

[0009] In one implementation, the boot area includes at least a primary boot area and a secondary boot area; updating the bootloader includes: The amount of boot boot unit data in the main boot area and the secondary boot area is detected. When the amount of boot boot unit data in the main boot area reaches a preset data threshold, the boot boot unit is written to the secondary boot area, and the boot boot unit in the main boot area is erased.

[0010] By writing the bootloader to the secondary boot sector and erasing the bootloader in the primary boot sector, a circular storage method is used to avoid insufficient storage resources and ensure the continuity and stability of the bootloader. This prevents bootloader overflow and avoids operational interruptions or data corruption due to insufficient storage space.

[0011] Furthermore, the primary boot area and secondary boot area at least include a primary boot page and a backup boot page; updating the boot unit further includes: When the boot unit stored in the main boot page is damaged, the backup boot page is activated.

[0012] The bootloader unit includes at least a storage queue head index and a storage queue tail index; when the storage queue head index or the storage queue tail index is updated, the new bootloader unit is saved to the main boot page and the backup boot page.

[0013] When the bootloader stored in the primary boot page is corrupted, such as due to data verification failure or hardware malfunction, the backup boot page is activated, ensuring that a usable bootloader is always available and preventing anomalies caused by missing or damaged bootloaders. Writing the bootloader to both the primary and backup boot pages simultaneously ensures data consistency between them, preventing index loss or logical corruption due to single-page corruption.

[0014] Furthermore, before the real-time acquisition of log data from the display screen and its caching to the storage queue, the process further includes: Initialize the log storage component and check if there is any abnormality in the log storage component. If so, take corresponding abnormality handling based on the obtained abnormality type; otherwise, return an initialization success signal.

[0015] By initializing the log storage component and performing anomaly detection, faults can be detected in advance, allowing for corresponding solutions to be implemented. This prevents data loss or system crashes caused by anomalies when the log storage component stores log data. Anomaly detection in the log storage component also prevents log data from being written to unreliable areas, thus avoiding data loss or errors during subsequent log analysis.

[0016] Furthermore, the initialization of the log storage component and the detection of whether the log storage component is abnormal include: Check whether the initialization of the log storage component is successful. If it is, return an initialization success signal; otherwise, record that the initialization of the log storage component is abnormal.

[0017] If the total number of pages in the storage is less than a preset page count threshold, it is determined that the log storage component has a fatal anomaly; otherwise, it is determined that the log storage component does not have an anomaly.

[0018] Furthermore, based on the startup boot unit, it is determined whether the log storage component is abnormal. If so, it is recorded that the log storage component has a startup area abnormality; otherwise, it is determined that the log storage component is not abnormal.

[0019] By employing multiple anomaly detection methods, the limitations of a single detection dimension are avoided, improving the comprehensiveness of anomaly detection in the log storage component and ensuring its reliability. These multiple anomaly detection methods enable operations and maintenance personnel to quickly pinpoint the root cause of problems.

[0020] Furthermore, the corresponding exception handling based on the acquired exception type includes: No exception handling is performed when a fatal exception occurs in the log storage component.

[0021] When the log storage component experiences an initialization exception, an initialization request is issued to re-initialize the component.

[0022] When the log storage component has a startup area abnormality, a formatting request signal is initiated to format the log storage component based on the formatting request signal and then re-initialize the log storage component.

[0023] By employing different exception handling methods for different anomalies, system stability is ensured. When a fatal anomaly occurs in the log storage component—that is, when the log storage component is physically damaged and the hardware is unrecoverable—meaningless repair attempts are avoided, thus preventing waste of system resources. In the event of initialization or startup area anomalies, initialization requests are re-initiated to prevent functional loss due to a single failure.

[0024] Furthermore, the step of writing the log data into the log management area based on the boot boot unit stored in the boot area includes: Obtain the remaining storage capacity of the log management area and calculate the amount of log data in the storage queue.

[0025] Based on the data volume and remaining storage capacity, it is determined whether the log data can be written to the log management area. If so, the head and tail of the storage queue in the log management area are obtained based on the startup boot unit, and the log data is written to the log management area based on the position of the tail of the storage queue.

[0026] Otherwise, log data with the remaining storage capacity is stored based on the tail position of the storage queue, and then the log data starting from the head position of the storage queue is overwritten in a loop to store the remaining log data.

[0027] By cyclically overwriting stored log data, log data overflow is effectively prevented. When remaining storage space is insufficient, indiscriminate writing that could lead to data corruption is avoided, ensuring the integrity of the log data. Furthermore, when remaining storage is low, the earliest written log data is overwritten starting from the head of the queue, ensuring the continuous writing of new log data.

[0028] Furthermore, the step of reading the target log data based on the received log reading instruction and exporting the target log data based on a preset communication protocol includes: When the log read instruction is received, the writing of log data in the log storage component is paused, and a log retrieval request is issued based on the log read instruction.

[0029] Based on the log retrieval request, the log data stored in the log storage component is retrieved to obtain the target log data, and the target log data is exported through a preset communication protocol.

[0030] Once the target log data has been exported, resume writing log data in the log storage component.

[0031] When reading log data, writing to the logs is paused to avoid read-write conflicts, prevent data misalignment caused by new log data being written during the retrieval process, and prevent accidental deletion of target log data to be exported due to loop overwriting.

[0032] Based on the same inventive concept, this application also proposes a system for managing display screen logs, the system comprising: The log collection module is used to collect log data from the display screen in real time and cache it in a storage queue.

[0033] The log storage module is used to write the log data into the log management area based on the boot boot unit stored in the boot area.

[0034] The boot unit update module is used to issue a boot unit update request when any storage page in the log management area is full, so as to update the boot unit.

[0035] In addition, a log export module is used to read target log data from the log management area based on the received log read command, and export the target log data through a preset communication protocol.

[0036] Based on the same inventive concept, this application also proposes a computer-readable storage medium storing computer-executable instructions, which are read and executed by a control processor to implement the display screen log management method.

[0037] Compared with the prior art, this application has at least the following beneficial effects: This application addresses the technical problem of reliance on the vehicle's infotainment system for display screen log storage. This reliance leads to difficulties for developers and maintenance personnel in obtaining sufficient log data for analysis and troubleshooting, impacting problem-solving efficiency. Independent storage of display screen log data ensures data integrity, reduces the difficulty and cost of display screen log analysis, and improves problem-solving efficiency. Caches log data in a storage queue before writing it to the log management area, ensuring smooth and stable log data storage. Reading target log data from the log management area improves query efficiency and accuracy. Exporting target log data via a preset communication protocol avoids disassembling the display screen, effectively improving log data analysis efficiency. Attached Figure Description

[0038] Figure 1 This is a flowchart illustrating a display log management method according to an embodiment of this application.

[0039] Figure 2 This is a schematic diagram illustrating the flash memory distribution in an embodiment of this application.

[0040] Figure 3 This is a schematic diagram of the structure of the flash boot area shown in the embodiments of this application.

[0041] Figure 4 This is a schematic diagram of the structure of the main or secondary startup area shown in the embodiments of this application.

[0042] Figure 5 This is a schematic diagram illustrating the writing of data to the log management area in an embodiment of this application.

[0043] Figure 6 This is a schematic diagram of a display log management system shown in an embodiment of this application. Detailed Implementation

[0044] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0045] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or server that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0046] Example 1: Please refer to Figure 1 The display log management method mainly includes steps S100 to S300.

[0047] Step S100 includes: real-time acquisition of log data from the display screen and caching it to a storage queue. By configuring an independent log storage component for each display screen, the system is no longer entirely dependent on the vehicle infotainment system, which previously made it difficult for developers and maintenance personnel to obtain sufficient log data for analysis and troubleshooting. The log storage component includes a startup area and a log management area. The startup area includes a main startup area and a secondary startup area, which in turn include a main startup page and a backup startup page for storing the startup boot unit. The log management area includes multiple storage pages for storing the log data.

[0048] Step S200 includes: writing the log data into the log management area based on the startup boot unit stored in the startup area; wherein, when any storage page in the log management area is full, a startup boot unit update request is issued to update the startup boot unit. The startup boot unit includes at least a storage queue head index and a storage queue tail index. The storage queue head and storage queue tail in the log storage area are obtained through the storage queue head index and storage queue tail index. When there is sufficient remaining storage in the log management area, the log data is written to the log management area starting from the storage queue tail; when there is insufficient remaining storage in the log management area, the remaining log data is stored starting from the storage queue tail position, and the earliest stored log data is cyclically overwritten starting from the storage queue head position. When any storage page in the log management area is full, a startup boot unit update request is initiated to update the startup boot unit.

[0049] Furthermore, step S300 includes: reading target log data from the log management area based on the received log read instruction, and exporting the target log data based on a preset communication protocol. The log read instruction can be issued by the vehicle's infotainment system or a log retrieval tool. Upon receiving the log read instruction, log data is retrieved from all storage pages in the log management area based on the instruction, and the target log data is exported via the communication protocol.

[0050] In practice, the log storage component can primarily be a flash chip, but is not limited to it. Log storage components compatible with different manufacturers and capacities can be used to achieve cross-platform compatibility and improve system applicability and stability. For example, please refer to [link to relevant documentation]. Figure 2 The flash memory chip contains a boot area and a log management area; refer to Figure 3 The boot area of ​​a flash chip also includes a main boot area and a secondary boot area, see reference. Figure 4 The main boot area also includes a main boot page (sector0) and a backup boot page (sector1), each boot page storing boot boot units 0 to N. Log data is collected in real-time and cached in a storage queue; based on the boot boot units stored in the boot area of ​​the log storage component, the log data in the storage queue is written to the log management area. The log management area includes multiple storage pages; when any storage page is full, a boot boot unit update request is issued to update the boot boot unit. Upon receiving a log read command from the host computer, the log data stored in the log management area is retrieved, and the target log data is exported via a communication protocol.

[0051] In some embodiments, the boot sector includes at least a primary boot sector and a secondary boot sector; updating the boot unit includes: The amount of boot boot unit data in the main boot area and the secondary boot area is detected. When the amount of boot boot unit data in the main boot area reaches a preset data threshold, the boot boot unit is written to the secondary boot area, and the boot boot unit in the main boot area is erased.

[0052] In other words, once the primary boot sector is full, the remaining boot units are written to the secondary boot sector, and the process of erasing the full primary boot sector begins. Upon receiving a boot unit update request, the system checks if the primary boot sector is full. If not, it finds unused boot units and updates them to that sector; otherwise, it updates them to the secondary boot sector and initiates a request to erase the primary boot sector. Upon receiving an erase request, the system erases the primary boot page and backup boot page of that sector.

[0053] Preferably, the primary boot area and the secondary boot area include at least a primary boot page and a backup boot page; updating the boot unit further includes: When the boot unit stored in the main boot page is damaged, the backup boot page is activated.

[0054] The startup guidance unit includes at least a storage queue head index and a storage queue tail index.

[0055] When the storage queue head index or storage queue tail index is updated, the new boot unit is saved to the main boot page and the backup boot page.

[0056] Please refer to Figure 4 The system includes a primary boot page and a backup boot page in the primary or secondary boot area, which serve as backups for each other. When the data in the primary boot page is corrupted, the data in the backup boot page is used to start the system. The boot unit may include at least a storage queue head index, a storage queue tail index, a reservation, and a checksum. When the storage queue head index or storage queue tail index is updated, the updated boot unit is saved to both the primary boot page and the backup boot page.

[0057] Preferably, before collecting the log data from the display screen in real time and caching it in the storage queue, the method further includes: Initialize the log storage component and check if there is any abnormality in the log storage component. If so, take corresponding abnormality handling based on the obtained abnormality type; otherwise, return an initialization success signal.

[0058] The initialization of the log storage component and the detection of any abnormalities in the log storage component include: Check whether the initialization of the log storage component is successful. If it is, return an initialization success signal; otherwise, record that the initialization of the log storage component is abnormal.

[0059] The system checks whether the total number of pages in the storage is less than a preset page count threshold. If so, it determines that the log storage component has a fatal anomaly. Otherwise, it determines that the log storage component does not have an anomaly. Furthermore, based on the startup boot unit, it is determined whether the log storage component is abnormal. If so, it is recorded that the log storage component has a startup area abnormality; otherwise, it is determined that the log storage component is not abnormal.

[0060] In practice, the system checks whether the total number of pages in the log storage component is less than the number of pages required for normal system operation. If the total number of pages is insufficient, the log storage component is deemed to have a fatal error. If the total number of pages in the log storage component is sufficient, the log storage component is initialized. If initialization is successful, an initialization success signal is returned; otherwise, an initialization error is recorded.

[0061] The system reads the first boot boot unit 0 and the last boot boot unit N in the boot area of ​​the log storage component. It also reads the boot boot units 0 and N of the main boot page and the backup boot page of the primary and secondary boot areas. Based on these 8 boot boot units, it determines which boot area to load the boot boot unit from.

[0062] When the boot unit of the primary boot sector is started and the boot unit of the secondary boot sector is not used, the boot unit of the primary boot page in the primary boot sector is the same as that of the backup boot page. If the boot unit of the primary boot page in the secondary boot sector is different from that of the backup boot page, the boot unit of the secondary boot sector is erased.

[0063] When the boot unit of the secondary boot sector is started and the boot unit of the primary boot sector is not used, the boot unit of the primary boot page in the secondary boot sector is the same as that of the backup boot page. If the boot unit of the primary boot page in the primary boot sector is different from that of the backup boot page, the boot unit of the primary boot sector is erased.

[0064] If there are other issues with the boot boot units in the primary and secondary boot sectors, then the log storage component is recorded as having a boot sector anomaly.

[0065] Preferably, the step of taking corresponding exception handling based on the acquired exception type includes: No exception handling is performed when a fatal exception occurs in the log storage component.

[0066] When the log storage component experiences an initialization exception, an initialization request is issued to re-initialize the component.

[0067] When the log storage component has a startup area abnormality, a formatting request signal is initiated to format the log storage component based on the formatting request signal and then re-initialize the log storage component.

[0068] For example, if a fatal exception occurs in the flash chip, no exception handling is performed. If an initialization exception occurs in the flash chip, an initialization request is initiated to re-initialize in an attempt to recover from the error. If a boot sector exception occurs in the flash chip, a formatting request signal is initiated to format the flash chip, that is, to erase all data in the flash chip, and then re-initialize.

[0069] Preferably, the step of writing the log data to the log management area based on the boot boot unit stored in the boot area includes: Obtain the remaining storage capacity of the log management area and calculate the amount of log data in the storage queue.

[0070] Based on the data volume and remaining storage capacity, it is determined whether the log data can be written to the log management area. If so, the head and tail of the storage queue in the log management area are obtained based on the startup boot unit, and the log data is written to the log management area based on the position of the tail of the storage queue.

[0071] Otherwise, log data with the remaining storage capacity is stored based on the tail position of the storage queue, and then the log data starting from the head position of the storage queue is overwritten in a loop to store the remaining log data.

[0072] Please refer to Figure 5 The startup boot unit includes at least a storage queue head index, a storage queue tail index, a reservation, and a checksum. The storage queue head and tail in the log management area are obtained using the storage queue head index and storage queue tail index. When there is sufficient remaining storage in the log management area, log data is written starting from the storage queue tail position until all log data is written to the log management area. When there is insufficient remaining storage in the log management area, the remaining log data is stored starting from the storage queue tail position, and then the remaining log data is sequentially overwritten starting from the storage queue head position.

[0073] Preferably, the step of reading the target log data based on the received log reading instruction and exporting the target log data based on a preset communication protocol includes: When the log read instruction is received, the writing of log data in the log storage component is paused, and a log retrieval request is issued based on the log read instruction.

[0074] Based on the log retrieval request, the log data stored in the log storage component is retrieved to obtain the target log data, and the target log data is exported through a preset communication protocol; after the target log data is exported, the writing of log data in the log storage component is resumed.

[0075] For example, when a command to read the log is received, the system pauses the saving of log data in the Flash chip, begins reading the log data from the Flash chip and sending it out, and resumes the function of saving log data in the Flash chip when the log reading is complete.

[0076] Example 2: Please refer to Figure 6 This application also proposes a system using the display screen log management method described in Embodiment 1, the system comprising: a log acquisition module, a log storage module, a guidance unit update module, and a log export module.

[0077] The log collection module is used to collect log data from the display screen in real time and cache it in a storage queue.

[0078] The log storage module is used to write log data into the log management area based on the startup boot unit stored in the startup area. The startup boot unit includes at least a storage queue head index and a storage queue tail index. The head position of the storage queue in the log management area is obtained based on the head index, and the tail position of the storage queue in the log management area is obtained based on the tail index. The module continuously monitors the amount of log data in the storage queue and the remaining storage space in the log management area. When the remaining storage space is sufficient to write the log data, the log data is written to the log management area starting from the tail position of the storage queue. When the remaining storage space is insufficient, the remaining log data is written starting from the tail position of the storage queue, and then the remaining log data is used to cyclically overwrite the oldest log data, starting from the head position of the storage queue.

[0079] The boot unit update module is used to issue a boot unit update request when any storage page in the log management area is full, so as to update the boot unit. Specifically, when the boot unit stored in the primary boot page is damaged, a backup boot page is activated; the primary boot page and the backup boot page serve as backups for each other. The module detects the amount of boot unit data in the primary and secondary boot areas; when the boot unit in the primary boot area is full, the boot unit is written to the secondary boot area, and the erasure of the boot units in the primary boot area begins. The system also includes a log export module, used to read target log data from the log management area based on a received log read command, and export the target log data through a preset communication protocol. Specifically, this can be achieved by the vehicle-mounted system or a host computer sending a log read command to the system, reading the target log data from the log management area based on the command, and then exporting the target log data through a communication protocol.

[0080] Example 3: This application also proposes a computer-readable storage medium, the computer-readable storage medium comprising: The computer-readable storage medium stores computer-executable instructions.

[0081] When the computer-executable instructions are executed by the control processor, the display log management method described in Embodiment 1 is implemented.

[0082] The computer-readable storage medium can be implemented entirely or partially by software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented entirely or partially as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in the computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0083] In summary, this application solves the technical problem of reliance on the vehicle system for display screen log storage, which makes it difficult for developers and maintenance personnel to obtain sufficient log data for analysis and troubleshooting when problems occur, thus affecting the efficiency of problem solving. It achieves independent storage of display screen log data, ensuring log data integrity, reducing the difficulty and cost of display screen log analysis, and improving the efficiency of display screen problem solving. By caching log data to a storage queue before writing it to the log management area, the smoothness and stability of log data storage are ensured. Reading target log data from the log management area improves the efficiency and accuracy of log data querying. Exporting the target log data through a preset communication protocol avoids disassembling the display screen, thereby effectively improving the efficiency of log data analysis.

[0084] In the several embodiments provided in this application, it will be understood that each block in the flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those shown in the figures. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved.

[0085] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an electronic device to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0086] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above descriptions are merely specific embodiments of this application and are not intended to limit the scope of protection of this application. In particular, it should be noted that any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application for those skilled in the art.

Claims

1. A method for managing display screen logs, characterized in that, Each display screen is configured with a log storage component, the log storage component including at least a startup area and a log management area, the log management area including multiple storage pages; The display screen log management method includes: Real-time collection of log data from the display screen and caching to a storage queue; The log data is written to the log management area based on the boot boot unit stored in the boot area; wherein, when any storage page in the log management area is full, a boot boot unit update request is issued to update the boot boot unit; Furthermore, the system reads target log data from the log management area based on the received log read command and exports the target log data based on a preset communication protocol.

2. The display screen log management method according to claim 1, characterized in that, The boot area includes at least a primary boot area and a secondary boot area; updating the bootloader includes: The amount of boot boot unit data in the main boot area and the secondary boot area is detected. When the amount of boot boot unit data in the main boot area reaches a preset data threshold, the boot boot unit is written to the secondary boot area, and the boot boot unit in the main boot area is erased.

3. The display screen log management method according to claim 2, characterized in that, The primary boot area and secondary boot area include at least a primary boot page and a backup boot page; The update of the bootloader unit also includes: When the boot loader stored in the main boot page is damaged, the backup boot page is activated; The startup boot unit includes at least a storage queue head index and a storage queue tail index; When the storage queue head index or storage queue tail index is updated, the new boot unit is saved to the main boot page and the backup boot page.

4. The display screen log management method according to claim 3, characterized in that, Before the real-time acquisition of log data from the display screen and its caching to the storage queue, the method further includes: Initialize the log storage component and check if there is any exception in the log storage component. If so, take corresponding exception handling based on the obtained exception type; otherwise, return an initialization success signal.

5. The display screen log management method according to claim 4, characterized in that, The initialization of the log storage component and the detection of any abnormalities in the log storage component include: Check whether the initialization of the log storage component is successful. If it is, return an initialization success signal; otherwise, record that the initialization of the log storage component is abnormal. The system checks whether the total number of pages in the storage is less than a preset page number threshold. If so, it determines that there is a fatal anomaly in the log storage component. Otherwise, it is determined that the log storage component is not abnormal; Furthermore, based on the startup boot unit, it is determined whether the log storage component is abnormal. If so, it is recorded that the log storage component has a startup area abnormality; otherwise, it is determined that the log storage component is not abnormal.

6. The display screen log management method according to claim 5, characterized in that, The corresponding exception handling based on the acquired exception type includes: When a fatal exception occurs in the log storage component, no exception handling is performed; When the log storage component experiences an initialization exception, an initialization request is issued to re-initialize the component. When the log storage component has a startup area abnormality, a formatting request signal is initiated to format the log storage component based on the formatting request signal and then re-initialize the log storage component.

7. The display screen log management method according to claim 6, characterized in that, The boot boot unit based on the boot area writes the log data into the log management area, including: Obtain the remaining storage capacity of the log management area and calculate the amount of log data in the storage queue; Based on the data volume and remaining storage capacity, determine whether the log data can be written to the log management area. If so, obtain the head and tail of the storage queue in the log management area based on the startup boot unit, and write the log data to the log management area based on the position of the tail of the storage queue. Otherwise, log data with the remaining storage capacity is stored based on the tail position of the storage queue, and then the log data starting from the head position of the storage queue is overwritten in a loop to store the remaining log data.

8. The display screen log management method according to claim 7, characterized in that, The step of reading target log data based on the received log read instruction and exporting the target log data based on a preset communication protocol includes: When the log read instruction is received, the writing of log data in the log storage component is paused, and a log retrieval request is issued based on the log read instruction. Based on the log retrieval request, the log data stored in the log storage component is retrieved to obtain the target log data, and the target log data is exported through a preset communication protocol; Once the target log data has been exported, resume writing log data in the log storage component.

9. A system based on the display screen log management method according to any one of claims 1-8, characterized in that, The system includes: The log collection module is used to collect log data from the display screen in real time and cache it to a storage queue; The log storage module is used to write the log data into the log management area based on the boot boot unit stored in the boot area; The boot unit update module is used to issue a boot unit update request to update the boot unit when any storage page in the log management area is full. In addition, a log export module is used to read target log data from the log management area based on the received log read command, and export the target log data through a preset communication protocol.

10. A computer-readable storage medium storing computer-executable instructions, characterized in that, When the computer-executable instructions are executed by the control processor, the display log management method as described in any one of claims 1-8 is implemented.

Images