Communication log management method and management system, storage medium and vehicle-mounted terminal

Abstract

The invention provides a communication log management method and system, a storage medium and a vehicle-mounted terminal. The method comprises the following steps: acquiring a corresponding communication state based on a real-time monitoring result and an abnormal judgment logic of each communication channel, and acquiring error log data and / or normal log data of each communication channel based on the communication state; and recording the error log data and / or the normal log data into a log data array in combination with the timestamps corresponding to the error log data and / or the normal log data. Communication problems can be found and processed in time, and the stability and reliability of the system are guaranteed; the communication state corresponding to each communication channel can be acquired in a targeted manner, so that error log data can be accurately identified and recorded, and the root of a communication problem can be positioned; and meanwhile, recording is carried out in combination with the timestamp, so that the time period when the communication problem occurs can be quickly identified, the troubleshooting range is narrowed, and the positioning of the communication problem is further accelerated.

Description

Technical Field

[0001] The present application relates to the technical field of log management, and in particular to a communication log management method, management system, storage medium and vehicle-mounted terminal. Background Art

[0002] With the rapid development of autonomous driving technology in the automotive field, domain controllers are becoming more and more complex. The communication media mounted by domain controllers as gateways will also become complex and diverse. The status of the communication media is highly correlated to various functional services. The lack of management and logging of communication status is not conducive to the analysis and location of related communication problems. In addition, when functional services send abnormal exits and degradations, it is impossible to confirm that they are caused by communication problems. Therefore, it is very necessary to manage the status of the communication media and log them. Summary of the invention

[0003] In order to solve the above technical problems, the present application provides a communication log management method, management system, storage medium and vehicle-mounted terminal that can quickly locate communication problems.

[0004] Specifically, the present application provides a communication log management method, comprising the following steps: Monitor multiple communication channels in real time.

[0005] The corresponding communication status is acquired based on the abnormality judgment logic of each communication channel, and the error log data and / or normal log data of each communication channel is acquired based on the communication status.

[0006] And, obtaining the timestamp corresponding to the error log data and / or the normal log data, so as to record the error log data and / or the normal log data into the log data array in combination with the timestamp.

[0007] In the above technical solution, by real-time monitoring of multiple communication channels, communication problems can be discovered and handled in a timely manner to ensure the stability and reliability of the system; different abnormal judgment logics are used for different communication channels to obtain the corresponding communication status in a more targeted manner, and then accurately identify and record error log data, which helps to locate the root cause of the communication problem; by recording in combination with timestamps, the occurrence time of each log data can be clearly identified, helping to quickly identify the time period when the problem occurred, thereby narrowing the scope of investigation and further accelerating the location of communication problems.

[0008] Furthermore, the communication channel includes at least a first channel, a second channel, a third channel and a fourth channel.

[0009] The first channel includes a plurality of bus channels; the abnormality judgment logic of the first channel is specifically as follows: The first communication status of each bus channel is monitored in sequence, and when an abnormality is detected in the first communication status, it is determined whether the first communication status is a bus error status. If so, a first bus error log corresponding to the bus error status is recorded as error log data; otherwise, a first network status log corresponding to the first channel is recorded as normal log data.

[0010] In the above technical solution, by monitoring multiple bus channels in the first channel one by one, communication anomalies can be discovered and identified more accurately, ensuring that the status of each bus channel is effectively tracked; when an anomaly is detected, it can be accurately determined whether it is a bus error state, and the relevant error log can be recorded. This method can improve the accuracy of log records and help to quickly locate and resolve communication faults; by recording normal status logs and error status logs, the operating status of the communication channel can be more clearly understood, which is helpful for system maintenance and problem diagnosis.

[0011] Furthermore, the second channel is used for sending and receiving frame messages; the abnormality judgment logic of the second channel is specifically as follows: Determine whether the second channel has triggered the sending and receiving of the frame message. If so, determine whether the second channel has executed the sending of the frame message; otherwise, end the process.

[0012] If the frame message has been sent, it is determined whether the sending state of the frame message is abnormal; otherwise, it is determined whether the second channel has received the frame message.

[0013] If the sending state is abnormal, the first message error log corresponding to the frame message is recorded as error log data; otherwise, it is determined whether the second channel has executed the reception of the frame message.

[0014] If the frame message has been received, it is determined whether the reception state of the frame message is abnormal; otherwise, the process ends.

[0015] If the receiving state is abnormal, the second message error log corresponding to the frame message is recorded as error log data; otherwise, the message communication log corresponding to the second channel is recorded as normal log data.

[0016] In the above technical solution, by making detailed judgments on the sending and receiving process of the frame message, the status of each step can be accurately tracked to ensure that each link of sending and receiving is monitored; the error logs in the sending and receiving process of the frame message can be recorded separately, which helps to locate the specific source of the error and improve the accuracy of problem diagnosis; distinguishing between normal and abnormal sending and receiving states helps to fully understand the performance of the communication channel and provide more accurate log data to support subsequent analysis and maintenance; by judging the status and recording logs in each step, it helps to quickly discover and solve communication problems, reduce system downtime, and improve the overall efficiency and stability of the system.

[0017] Furthermore, the abnormality judgment logic of the third channel is specifically as follows: Determine whether the second communication state of the third channel is abnormal, if so, determine whether the third channel has completed the preset communication work; otherwise, end the process.

[0018] If the preset communication task has been completed, the second network status log corresponding to the third channel is recorded as normal log data; otherwise, it is determined whether the third communication status of the third channel is abnormal.

[0019] If the third communication state is abnormal, the second bus error log corresponding to the third communication state is recorded as error log data; otherwise, the bus normal log corresponding to the third communication state is recorded as normal log data.

[0020] In the above technical scheme, by gradually judging and recording the different communication states of the third channel, the monitoring process can be refined, which helps to fully understand each link in the communication process; the abnormal situations of the second communication state and the third communication state can be handled separately to ensure that when communication problems occur, they can be recorded and appropriate measures can be taken in time; the log data in normal and abnormal states can be distinguished, and detailed log records can be provided, which is helpful for subsequent fault analysis and system optimization; by recording the second bus error log and the bus normal log, the source of the problem can be located more accurately, improving the efficiency of troubleshooting.

[0021] Furthermore, the abnormality judgment logic of the fourth channel is specifically as follows: Determine whether the network port status is abnormal. If so, record the port error log corresponding to the network port status as error log data; otherwise, determine whether the network communication function is enabled.

[0022] If the network communication function is turned on, determine whether the network communication quality index is within a preset range; otherwise, end the process.

[0023] If the network communication quality indicator is within a preset range, it is determined whether the network communication state is abnormal; otherwise, a quality indicator error log corresponding to the network communication quality indicator is recorded as error log data.

[0024] If the network communication status is abnormal, the third network status log corresponding to the network communication status is recorded as normal log data; otherwise, the process ends.

[0025] In the above technical solution, by gradually checking the network port status, communication function, communication quality indicators and communication status, it is ensured that each link is effectively monitored. This systematic detection method helps to accurately capture and record abnormal situations; it can record detailed error logs (such as port error logs and quality indicator error logs), as well as normal logs (such as the third network status log) according to different abnormal situations. This detailed log record is helpful for subsequent analysis and troubleshooting; by checking whether the network communication quality indicators are within the preset range, it can be ensured that the communication quality meets the expected standards and the quality degradation problem is discovered in time; gradually verifying and recording the status of each stage helps to quickly respond to and handle problems in network communication and improve the stability and reliability of the system.

[0026] In addition, the above inspections for each channel cover various communication media of the vehicle terminal to ensure that when the system communication status is abnormal, it can be monitored and recorded in time.

[0027] Furthermore, it also includes: reporting an exception based on the error log data.

[0028] In the above technical solution, by reporting exceptions based on error log data, a report can be quickly generated and relevant personnel can be notified when an exception occurs, which helps to take timely countermeasures and reduce the impact of system failures on the business; exception reporting provides detailed error log data, which can be used to track the root cause of the problem and help technical personnel conduct in-depth fault analysis and diagnosis; by centrally recording and reporting error logs, duplication of work and human omissions can be reduced, and the work efficiency of maintenance personnel can be improved.

[0029] Based on the same concept, the present application also provides a communication log management system, including: Monitoring module, used for real-time monitoring of multiple communication channels.

[0030] The abnormality acquisition module is used to acquire the corresponding communication status based on the abnormality judgment logic of each communication channel, and acquire the error log data and / or normal log data of each communication channel based on the communication status.

[0031] The recording module is used to obtain the timestamp corresponding to the error log data and / or the normal log data, so as to record the error log data and / or the normal log data into a log data array in combination with the timestamp.

[0032] In the above technical solution, the monitoring module can monitor multiple communication channels in real time to ensure that any problems in the communication process can be quickly responded to and handled; through the abnormal judgment logic of each communication channel, the abnormal acquisition module can accurately obtain the abnormal situation of the communication status, whether it is error log data or normal log data, to ensure the accuracy of the detection results; the recording module integrates the error log data and the normal log data into the log data array, and records them uniformly based on the timestamp, thereby improving the efficiency and accuracy of log management; the combined use of timestamps makes the log data have stronger time sequence and traceability, which helps technicians to analyze historical data, find out the causes and consequences of the problem, so as to quickly locate the problem and implement corresponding repair measures.

[0033] Based on the same concept, the present application also provides a storage medium, in which a computer program is stored, wherein the computer program is configured to execute the communication log management method when running.

[0034] Based on the same concept, the present application also provides a vehicle-mounted terminal, which includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set are loaded and executed by the processor to implement the communication log management method.

[0035] Compared with the prior art, the beneficial effects of this application are: This application monitors multiple communication channels in real time; then obtains the corresponding communication status based on the abnormal judgment logic of each communication channel, and obtains the error log data and / or normal log data of each communication channel based on the communication status; and further obtains the timestamp corresponding to the error log data and / or normal log data, and records the error log data and / or normal log data in the log data array in combination with the timestamp. This application can timely discover and handle communication problems, ensure the stability and reliability of the system; and can specifically obtain the communication status corresponding to each communication channel, so as to accurately identify and record the error log data, and then help locate the source of the communication problem; by recording in combination with the timestamp, the occurrence time of each log data can be clarified, which helps to quickly identify the time period when the problem occurs, thereby narrowing the scope of investigation and further speeding up the location of communication problems. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1This is a flow chart of the communication log management method described in this application.

[0037] Figure 2 This is a logic flow chart of abnormality determination of the first channel described in this application.

[0038] Figure 3 This is a logic flow chart of abnormality determination of the second channel described in this application.

[0039] Figure 4 This is a logic flow chart of abnormality determination of the third channel described in this application.

[0040] Figure 5 This is a logic flow chart of abnormality determination of the fourth channel described in this application.

[0041] Figure 6 This is a framework diagram of the communication log management system described in this application. DETAILED DESCRIPTION

[0042] The following is a further detailed description of a communication log management method, management system, storage medium and vehicle-mounted terminal of the present application in conjunction with specific embodiments and drawings.

[0043] See also Figure 1 The present application embodiment provides a communication log management method, comprising the following steps: Monitor multiple communication channels in real time.

[0044] Furthermore, the communication channel includes at least a first channel, a second channel, a third channel and a fourth channel.

[0045] Optionally, in some embodiments, the first channel is a Can / CanFd communication channel, the second channel is a LIN communication channel, the third channel is a FlexRay communication channel, and the fourth channel is an Ethernet communication channel.

[0046] Further, the corresponding communication status is acquired based on the abnormality judgment logic of each communication channel, and the error log data and / or normal log data of each communication channel is acquired based on the communication status.

[0047] The first channel includes a plurality of bus channels; see Figure 2 , the abnormality judgment logic of the first channel is specifically as follows: The first communication status of each bus channel is monitored in sequence, and when an abnormality is detected in the first communication status, it is determined whether the first communication status is a bus error status. If so, a first bus error log corresponding to the bus error status is recorded as error log data; otherwise, a first network status log corresponding to the first channel is recorded as normal log data.

[0048] In some embodiments, the Can / CanFd communication channel will have multiple bus channels in the domain controller, and polling will monitor whether the communication status (i.e., the first communication status) of each bus channel has changed. If there is a change, it will be determined whether there is a bus error state in the current new communication state. If a bus error state occurs, the channel type, fault type and fault data corresponding to the abnormal bus channel will be recorded.

[0049] The bus error state is, for example, a BUSOFF state; at this time, the first bus error log includes the channel type, fault type and fault data described above, for example: Channel type: Can / CanFd; Fault type: Bus error; Fault data: BUSOFF.

[0050] Further, in other embodiments, if there is no bus error state, the change in the communication state will be caused by the Can / CanFd network management state, and a corresponding first network state log will be generated such as: Channel type: Can / CanFd; status data: communication mode\pre-sleep mode\sleep mode, etc.

[0051] In the above technical solution, by monitoring multiple bus channels in the first channel one by one, communication anomalies can be discovered and identified more accurately, ensuring that the status of each bus channel is effectively tracked; when an anomaly is detected, it can be accurately determined whether it is a bus error state, and the relevant error log can be recorded. This method can improve the accuracy of log records and help to quickly locate and resolve communication faults; by recording normal status logs and error status logs, the operating status of the communication channel can be more clearly understood, which is helpful for system maintenance and problem diagnosis.

[0052] Furthermore, the second channel is used for sending and receiving frame messages; see Figure 3 , the abnormality judgment logic of the second channel is specifically as follows: Determine whether the second channel has triggered the sending and receiving of the frame message. If so, determine whether the second channel has executed the sending of the frame message; otherwise, end the process.

[0053] If the frame message has been sent, it is determined whether the sending state of the frame message is abnormal; otherwise, it is determined whether the second channel has received the frame message.

[0054] If the sending state is abnormal, the first message error log corresponding to the frame message is recorded as error log data; otherwise, it is determined whether the second channel has executed the reception of the frame message.

[0055] If the frame message has been received, it is determined whether the reception state of the frame message is abnormal; otherwise, the process ends.

[0056] If the receiving state is abnormal, the second message error log corresponding to the frame message is recorded as error log data; otherwise, the message communication log corresponding to the second channel is recorded as normal log data.

[0057] In some embodiments, the log data is tracked and generated by monitoring the sending and receiving of frame messages in the LIN communication channel schedule table.

[0058] Among them, it will first be determined whether the execution of the LIN communication channel scheduling table triggers the sending and receiving of frame messages. If so, it will be further determined whether the LIN communication channel scheduling table triggers the sending of frame messages; otherwise, the process ends.

[0059] If the LIN communication channel scheduling table has triggered the sending of the frame message, it is further determined whether the LIN controller returns a successful sending status; otherwise, it is further determined whether the LIN communication channel scheduling table triggers the reception of the frame message.

[0060] Further, if the LIN controller does not return a successful transmission status, it is considered that there is a transmission abnormality. At this time, the first message error log is as follows: Channel type: LIN; Fault type: Failure in sending message frame; Fault data: Frame ID.

[0061] If the return value is successful, the receiving status is further determined.

[0062] Further, if the LIN communication channel scheduling table has triggered the reception of the frame message, it is determined whether the LIN controller has returned a successful reception status. If it has not returned a successful reception status, it is considered that there is a reception anomaly. At this time, the second message error log is as follows: Channel type: LIN; Fault type: Failure to receive the response message frame; Fault data: Frame ID.

[0063] If the returned value is a successful reception, the opening time or closing time of the LIN communication channel is further recorded.

[0064] The message communication log is as follows: Channel type: LIN; Status data: Communication on / off.

[0065] In the above technical solution, by making detailed judgments on the sending and receiving process of the frame message, the status of each step can be accurately tracked to ensure that each link of sending and receiving is monitored; the error logs in the sending and receiving process of the frame message can be recorded separately, which helps to locate the specific source of the error and improve the accuracy of problem diagnosis; distinguishing between normal and abnormal sending and receiving states helps to fully understand the performance of the communication channel and provide more accurate log data to support subsequent analysis and maintenance; by judging the status and recording logs in each step, it helps to quickly discover and solve communication problems, reduce system downtime, and improve the overall efficiency and stability of the system.

[0066] For further information, see Figure 4 , the abnormality judgment logic of the third channel is specifically as follows: Determine whether the second communication state of the third channel is abnormal, if so, determine whether the third channel has completed the preset communication work; otherwise, end the process.

[0067] If the preset communication task has been completed, the second network status log corresponding to the third channel is recorded as normal log data; otherwise, it is determined whether the third communication status of the third channel is abnormal.

[0068] If the third communication state is abnormal, the second bus error log corresponding to the third communication state is recorded as error log data; otherwise, the bus normal log corresponding to the third communication state is recorded as normal log data.

[0069] In some embodiments, the FlexRay communication channel is the backbone communication bus of the domain controller in the vehicle network.

[0070] Among them, first determine whether the communication state corresponding to the FlexRay communication channel (ie, the second communication state) is abnormal. If there is no abnormality, the process ends; otherwise, further determine whether the FlexRay communication channel completes the time synchronization startup work (ie, the preset communication work described below).

[0071] It should be noted that, according to different application requirements, the preset communication task may also be other tasks and is not limited to the time synchronization startup task.

[0072] If it is determined that the FlexRay communication channel has completed the time synchronization startup work, the network management state corresponding to the FlexRay communication channel (ie, the second network state log) is further recorded; if it is not completed, the process proceeds to further abnormality judgment of the third channel.

[0073] Wherein, the second network status log is as follows: Channel type: FlexRay; status data: communication mode\pre-sleep mode\sleep mode, etc.

[0074] Further, when the FlexRay communication channel has not completed the time synchronization startup work, it is determined whether the Err Pin pin state (ie, the third communication state) of the FlexRay communication channel has an error. If so, the second bus error log is obtained, such as: Channel type: FlexRay; Fault type: transceiver fault / StartUp error, etc.; Fault data: FlexRay controller CC (Communication Controller) register data.

[0075] If there is no error in the Err Pin status, only the normal bus log is recorded, such as: Channel type: FlexRay; Status data: FlexRay controller CC (Communication Controller) register data.

[0076] In the above technical scheme, by gradually judging and recording the different communication states of the third channel, the monitoring process can be refined, which helps to fully understand each link in the communication process; the abnormal situations of the second communication state and the third communication state can be handled separately to ensure that when communication problems occur, they can be recorded and appropriate measures can be taken in time; the log data in normal and abnormal states can be distinguished, and detailed log records can be provided, which is helpful for subsequent fault analysis and system optimization; by recording the second bus error log and the bus normal log, the source of the problem can be located more accurately, improving the efficiency of troubleshooting.

[0077] For further information, see Figure 5 , the abnormality judgment logic of the fourth channel is specifically as follows: Determine whether the network port status is abnormal. If so, record the port error log corresponding to the network port status as error log data; otherwise, determine whether the network communication function is enabled.

[0078] If the network communication function is turned on, determine whether the network communication quality index is within a preset range; otherwise, end the process.

[0079] If the network communication quality indicator is within a preset range, it is determined whether the network communication state is abnormal; otherwise, a quality indicator error log corresponding to the network communication quality indicator is recorded as error log data.

[0080] If the network communication status is abnormal, the third network status log corresponding to the network communication status is recorded as normal log data; otherwise, the process ends.

[0081] Optionally, in some embodiments, the network port state is an Ethernet port link state, and whether it is abnormal is detected. If so, a port error log corresponding to the link state is recorded once, such as: Channel type: Ethernet; Fault type: link status; Fault data: link abnormal value.

[0082] If the link status is normal, it is determined whether the Ethernet communication function is enabled. If so, it is further determined whether the network communication quality index is within a preset range; otherwise, the process ends.

[0083] In some embodiments, the network communication quality indicator is, for example, an Ethernet communication channel SQI value. If the Ethernet communication channel SQI value is not within a preset range, the corresponding channel SQI abnormal value is obtained, and then a quality indicator error log is recorded, such as: Channel type: Ethernet; Fault type: SQI abnormality; Fault data: SQI abnormal value.

[0084] If the network communication quality index is within a preset range, it is further determined whether there is any abnormality in the network communication status.

[0085] In some embodiments, if it is found that the Ethernet communication state (ie, the network communication state) is abnormal, a third network state log is further obtained, such as: Channel type = Ethernet; Status data = Communication mode\pre-sleep mode\sleep mode etc. of UDP network management.

[0086] If it is found that there is no abnormality in the Ethernet communication status, the process ends.

[0087] In the above technical solution, by gradually checking the network port status, communication function, communication quality indicators and communication status, it is ensured that each link is effectively monitored. This systematic detection method helps to accurately capture and record abnormal situations; it can record detailed error logs (such as port error logs and quality indicator error logs), as well as normal logs (such as the third network status log) according to different abnormal situations. This detailed log record is helpful for subsequent analysis and troubleshooting; by checking whether the network communication quality indicators are within the preset range, it can be ensured that the communication quality meets the expected standards and the quality degradation problem is discovered in time; gradually verifying and recording the status of each stage helps to quickly respond to and handle problems in network communication and improve the stability and reliability of the system.

[0088] In addition, the above inspections for each channel cover various communication media of the vehicle terminal to ensure that when the system communication status is abnormal, it can be monitored and recorded in time.

[0089] Further, a timestamp corresponding to the error log data and / or the normal log data is obtained, so as to record the error log data and / or the normal log data into a log data array in combination with the timestamp.

[0090] In some embodiments, data recorded as error log data will be considered a fault event. After obtaining the domain controller system time (i.e., the timestamp) corresponding to the fault event, the error log data and the corresponding timestamp are updated to the system's current log data array, and simultaneously updated to the storage module and stored on disk.

[0091] Furthermore, in other embodiments, if normal log data is obtained, the domain controller system time corresponding to the normal log data at this time is also obtained, and the normal log data and the corresponding timestamp are updated to the current log data array of the system, and simultaneously updated to the storage module for disk storage.

[0092] Furthermore, it also includes: reporting an exception based on the error log data.

[0093] In some embodiments, if error log data is obtained, and a corresponding event fault data packet is packaged based on the error log data and uploaded to the application layer and related diagnostic modules, each application layer and diagnostic module then performs further fault processing based on the event fault data packet. The fault processing process is common knowledge among technicians in this field and will not be elaborated here.

[0094] Optionally, the event fault data packet includes a channel type, a fault type, a timestamp and fault data.

[0095] In the above technical solution, by reporting exceptions based on error log data, a report can be quickly generated and relevant personnel can be notified when an exception occurs, which helps to take timely countermeasures and reduce the impact of system failures on the business; exception reporting provides detailed error log data, which can be used to track the root cause of the problem and help technical personnel conduct in-depth fault analysis and diagnosis; by centrally recording and reporting error logs, duplication of work and human omissions can be reduced, and the work efficiency of maintenance personnel can be improved.

[0096] For further information, see Figure 6 , the present application also provides a communication log management system, including: Monitoring module, used for real-time monitoring of multiple communication channels.

[0097] The abnormality acquisition module is used to acquire the corresponding communication status based on the abnormality judgment logic of each communication channel, and acquire the error log data and / or normal log data of each communication channel based on the communication status.

[0098] The recording module is used to obtain the timestamp corresponding to the error log data and / or the normal log data, so as to record the error log data and / or the normal log data into a log data array in combination with the timestamp.

[0099] In the above technical solution, the monitoring module can monitor multiple communication channels in real time to ensure that any problems in the communication process can be quickly responded to and handled; through the abnormal judgment logic of each communication channel, the abnormal acquisition module can accurately obtain the abnormal situation of the communication status, whether it is error log data or normal log data, to ensure the accuracy of the detection results; the recording module integrates the error log data and the normal log data into the log data array, and records them uniformly based on the timestamp, thereby improving the efficiency and accuracy of log management; the combined use of timestamps makes the log data have stronger time sequence and traceability, which helps technicians to analyze historical data, find out the causes and consequences of the problem, so as to quickly locate the problem and implement corresponding repair measures.

[0100] Furthermore, the present application also provides a storage medium, in which a computer program is stored, wherein the computer program is configured to execute the communication log management method when running.

[0101] In some embodiments, the storage medium stores several computer programs for causing a device to execute all or part of the steps of the method described in various embodiments of the present application.

[0102] The medium may include a U disk, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk, and other media that can store program codes.

[0103] Furthermore, the present application also provides a vehicle-mounted terminal, which includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set are loaded and executed by the processor to implement the communication log management method.

[0104] In some embodiments, the memory and processor are interconnected via a bus; the processor may be one or more CPUs. When the processor is a CPU, the CPU may be a single-core CPU or a multi-core CPU. The processor is used to control various functional modules of the vehicle terminal and process signals.

[0105] The memory includes, but is not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), and CD-ROM (Compact Disc Read-Only Memory). The memory is used to store computer programs, operating systems, various applications and data, such as storing a computer program for implementing the communication log management method.

[0106] In summary, the present application provides a communication log management method, management system, storage medium and vehicle-mounted terminal; first, multiple communication channels are monitored in real time; then, the corresponding communication status is obtained based on the abnormal judgment logic of each communication channel, and the error log data and / or normal log data of each communication channel are obtained based on the communication status; and the timestamp corresponding to the error log data and / or normal log data is further obtained, so as to record the error log data and / or normal log data into the log data array in combination with the timestamp. The present application can timely discover and handle communication problems, ensure the stability and reliability of the system; and can specifically obtain the communication status corresponding to each communication channel, so as to accurately identify and record the error log data, and then help locate the root cause of the communication problem; by recording in combination with the timestamp, the occurrence time of each log data can be clearly identified, which helps to quickly identify the time period when the problem occurs, thereby narrowing the scope of investigation and further speeding up the location of the communication problem.

[0107] Although example embodiments have been described herein with reference to the accompanying drawings, it should be understood that the above example embodiments are merely exemplary and are not intended to limit the scope of the present application to this. Those of ordinary skill in the art may make various changes and modifications therein without departing from the scope and spirit of the present application. All these changes and modifications are intended to be included within the scope of the present application as required by the appended claims.

[0108] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0109] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed.

[0110] The various component embodiments of the present application can be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It should be understood by those skilled in the art that a microprocessor or digital signal processor (DSP) can be used in practice to implement some or all functions of some modules according to the embodiments of the present application. The application can also be implemented as a device program (e.g., computer program and computer program product) for executing a part or all of the methods described herein. Such a program implementing the present application can be stored on a computer-readable medium, or can have the form of one or more signals. Such a signal can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.

[0111] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0112] Although the description of the present application is carried out in conjunction with the above specific embodiments, it is obvious that those skilled in the art can make many substitutions, modifications and changes based on the above content. Therefore, all such substitutions, improvements and changes are included in the spirit and scope of the appended claims.

Claims

1. A communication log management method, characterized in that: The following steps are involved: Real-time monitoring of multiple communication channels; Acquire the corresponding communication status based on the abnormality judgment logic of each communication channel, and acquire the error log data and / or normal log data of each communication channel based on the communication status; And, obtaining a timestamp corresponding to the error log data and / or the normal log data, so as to record the error log data and / or the normal log data into a log data array in combination with the timestamp.

2. The communication log management method according to claim 1, characterized in that: The communication channel at least includes a first channel, a second channel, a third channel and a fourth channel.

3. The communication log management method according to claim 2, characterized in that: The first channel includes a plurality of bus channels; The abnormality judgment logic of the first channel is specifically as follows: monitoring the first communication state of each bus channel in sequence, and determining whether the first communication state is a bus error state when an abnormality is detected in the first communication state, and if so, recording a first bus error log corresponding to the bus error state as error log data; Otherwise, the first network status log corresponding to the first channel is recorded as normal log data.

4. The communication log management method according to claim 2, characterized in that: The second channel is used for sending and receiving frame messages; The abnormality judgment logic of the second channel is specifically as follows: Determine whether the second channel has triggered the sending and receiving of the frame message, if so, determine whether the second channel has executed the sending of the frame message; otherwise, end the process; If the frame message has been sent, determining whether there is an abnormality in the sending state of the frame message; Otherwise, determining whether the second channel has executed reception of the frame message; If the sending state is abnormal, recording a first message error log corresponding to the frame message as error log data; Otherwise, determining whether the second channel has executed reception of the frame message; If the frame message has been received, determining whether there is an abnormality in the reception state of the frame message; Otherwise, end the process; If the receiving state is abnormal, the second message error log corresponding to the frame message is recorded as error log data; otherwise, the message communication log corresponding to the second channel is recorded as normal log data.

5. The communication log management method according to claim 2, characterized in that: The abnormality judgment logic of the third channel is specifically as follows: Determine whether the second communication state of the third channel is abnormal, if so, determine whether the third channel has completed the preset communication work; otherwise, end the process; If the preset communication task has been completed, the second network status log corresponding to the third channel is recorded as normal log data; Otherwise, determining whether the third communication state of the third channel is abnormal; If the third communication state is abnormal, recording a second bus error log corresponding to the third communication state as error log data; Otherwise, the normal bus log corresponding to the third communication state is recorded as normal log data.

6. The communication log management method according to claim 2, characterized in that: The abnormality judgment logic of the fourth channel is specifically as follows: Determine whether the network port status is abnormal, if so, record the port error log corresponding to the network port status as error log data; otherwise, determine whether the network communication function is enabled; If the network communication function is turned on, determine whether the network communication quality index is within a preset range; otherwise, end the process; If the network communication quality indicator is within a preset range, determining whether the network communication state is abnormal; otherwise, recording a quality indicator error log corresponding to the network communication quality indicator as error log data; If the network communication status is abnormal, the third network status log corresponding to the network communication status is recorded as normal log data; otherwise, the process ends.

7. The communication log management method according to claim 1, characterized in that: Also includes: Exception reporting is performed based on the error log data.

8. A management system using the communication log management method according to any one of claims 1 to 7, characterized in that: include: Monitoring module, used to monitor multiple communication channels in real time; An abnormality acquisition module, used to acquire the corresponding communication status based on the abnormality judgment logic of each communication channel, and acquire error log data and / or normal log data of each communication channel based on the communication status; The recording module is used to obtain the timestamp corresponding to the error log data and / or the normal log data, so as to record the error log data and / or the normal log data into a log data array in combination with the timestamp.

9. A storage medium, characterized in that: The storage medium stores a computer program, wherein the computer program is configured to execute the communication log management method according to any one of claims 1 to 7 when running.

10. A vehicle-mounted terminal, characterized in that: The vehicle-mounted terminal includes a processor and a memory, and the memory stores at least one instruction, at least one program, a code set or an instruction set. The at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement the communication log management method as described in any one of claims 1-7.

Images