Intelligent cabin stability problem monitoring method, device and system and medium
By obtaining and filtering vehicle-end logs in the smart cockpit stability monitoring system, counting the number of errors, determining the problem level, and designing a log upload strategy, the problem of difficult-to-identify stability problems in smart cockpit stability monitoring is solved, and the vehicle is achieved Efficient identification and handling of driving safety hazards has improved user experience and satisfaction.
Patent Information
- Application Number
- CN202411043884.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-31
- Publication Date
- 2024-12-03
AI Technical Summary
The smart cockpit stability monitoring system is difficult to effectively identify stability problems, resulting in vehicle driving safety hazards and affecting user experience.
By obtaining the car logs, filtering and counting the number of errors reported by stability problems, determining the problem level, conducting cockpit stability analysis, identifying logs that cause vehicle safety hazards, designing analysis processes and log upload strategies of different levels to improve identification efficiency and accuracy sex.
Effectively identify and process logs that cause vehicle driving safety hazards, improve user experience and satisfaction, and ensure the safe use of the vehicle.
Smart Images

Figure CN119066546A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of automobile technology, and in particular to a method, device, system and medium for monitoring stability problems of an intelligent cockpit. Background Art
[0002] Currently, in the intelligent cockpit stability problem monitoring system, it is often difficult to obtain effective stability logs due to the low probability of occasional stability problems. It is also often difficult to identify and distinguish which are valid stability data based on massive user data. As a result, it is impossible to effectively identify such stability problems and locate and solve them, and it is also impossible to ensure the driving safety of the vehicle, which seriously affects the user experience. Summary of the invention
[0003] In view of this, the present invention provides a method, device, system and medium for monitoring stability problems of an intelligent cockpit, so as to solve the problem raised in the above technical background that it is difficult to effectively identify stability problems in the existing intelligent cockpit stability monitoring, which leads to hidden dangers to vehicle driving safety and affects the user experience.
[0004] In a first aspect, the present invention provides a method for monitoring stability problems of an intelligent cockpit, which is applied to a server side, and the method includes:
[0005] Get the vehicle-side log uploaded by the target vehicle;
[0006] The vehicle-side logs are screened to obtain a target log set, where the target log set contains at least one type of vehicle-side log corresponding to the stability problem;
[0007] Count the number of errors corresponding to each type of stability problem in the target log set;
[0008] Determine the problem level corresponding to the stability problem based on each type of stability problem and its corresponding number of error reports;
[0009] The cabin stability of the target vehicle is analyzed based on the problem level, and the corresponding analysis results are obtained.
[0010] The present invention filters the vehicle-side logs uploaded by the acquired target vehicle to obtain a target log set containing vehicle-side logs corresponding to at least one type of stability problem, counts the number of error reports corresponding to each type of stability problem in the set, determines the problem level based on each type of stability problem and its corresponding number of error reports, and performs cabin stability analysis on the target vehicle based on the problem level. This method can effectively identify problem logs corresponding to hidden dangers to vehicle driving safety, has the advantage of high recognition efficiency, and greatly improves the user experience.
[0011] In an optional implementation, determining the problem level corresponding to the stability problem based on each type of stability problem and its corresponding number of error reports includes:
[0012] Determine whether the stability problem is a first preset problem, where the first preset problem is a problem related to starting the vehicle intelligent cockpit software;
[0013] When the stability problem is the first preset problem, determining whether the number of error reports corresponding to the stability problem is less than a preset number threshold;
[0014] If the number of error reports corresponding to the stability problem is not less than the preset number threshold, the problem level is determined to be the first level.
[0015] The present invention takes into account that in actual applications, problems related to the startup of the vehicle's intelligent cockpit software have the greatest impact on the vehicle, and accordingly designs a matching process for stability problems and first preset problems, which can speed up the process of determining the problem level corresponding to the stability problem, and further speed up the identification of problem logs corresponding to hidden dangers to vehicle driving safety, thereby improving the efficiency of intelligent cockpit stability monitoring and ensuring safe use of the vehicle.
[0016] In an optional implementation, the intelligent cockpit stability problem monitoring method further includes:
[0017] When the stability problem is not the first preset problem, if the number of error reports corresponding to the stability problem is not less than the first preset threshold, the problem level is determined to be the first level;
[0018] If the number of error reports corresponding to the stability problem is less than the first preset threshold and not less than the second preset threshold, the problem level is determined to be the second level;
[0019] If the number of errors corresponding to the stability problem is less than the third preset threshold, the problem level is determined to be the third level, wherein the second preset threshold is greater than the third preset threshold and less than the first preset threshold, and the second level is higher than the third level and lower than the first level.
[0020] The present invention determines the specific problem level by the type and the number of error reports corresponding to the stability problem, which not only ensures the accuracy of the problem level, but also guarantees the safe use of the vehicle and improves user satisfaction.
[0021] In an optional implementation, the intelligent cockpit stability problem monitoring method further includes:
[0022] Within the preset time, if the cumulative number of error reports of the third-level corresponding stability problem is greater than the first number threshold, the problem level of the third-level corresponding stability problem is updated to the second level;
[0023] Within the preset time, if the cumulative number of error reports of the second-level corresponding stability problem is greater than the second number threshold, the problem level of the second-level corresponding stability problem is updated to the first level.
[0024] The present invention determines the cumulative number of error reports of stability problems within a preset time and the set number threshold, and optimizes the current problem level according to the determination result, which can ensure the determination accuracy of the problem level to a certain extent, thereby improving the user experience.
[0025] In an optional implementation, a cabin stability analysis is performed on the target vehicle based on the problem level, and corresponding analysis results are obtained, including:
[0026] If the problem level is the first level, a first vehicle-side log corresponding to the first level is obtained and a first warning message is generated, where the first warning message is used to remind the R&D personnel to process the first vehicle-side log;
[0027] If the problem level is the second level, a second vehicle-side log corresponding to the second level is obtained and a second warning information is generated, wherein the second warning information is used to remind the R&D personnel to process the second vehicle-side log, and the processing priority of the second warning information is lower than that of the first warning information;
[0028] If the problem level is the third level, return to the step of obtaining the vehicle-side log uploaded by the target vehicle.
[0029] The present invention can greatly improve the efficiency of cabin stability analysis by designing a cabin stability analysis process corresponding to different problem levels, realizes effective identification of problem logs corresponding to hidden dangers to vehicle driving safety, and greatly improves user satisfaction.
[0030] In an optional implementation, the vehicle-side logs are screened to obtain a target log set, including:
[0031] Extract log keywords corresponding to the vehicle-side log;
[0032] Based on the correspondence between log keywords and preset keywords and stability problem types, determine the stability problem type corresponding to each log keyword;
[0033] Filter the vehicle-side logs corresponding to the log keywords under each stability problem type to obtain the target log set.
[0034] The present invention determines the stability problem type corresponding to each log keyword through the correspondence between the log keyword corresponding to the vehicle-side log and the set preset keyword and stability problem type, and constructs a target log set based on the vehicle-side log corresponding to the log keyword under each stability problem type, which greatly ensures the quality of the target log set, helps to subsequently improve the accuracy and efficiency of cabin stability analysis, and enhances the user experience.
[0035] In a second aspect, the present invention provides a method for monitoring stability problems of an intelligent cockpit, which is applied to a vehicle side, and the method includes:
[0036] Obtain abnormal events of the target vehicle;
[0037] Determine the vehicle-side log and abnormality type corresponding to the abnormal event respectively;
[0038] Determine the upload strategy based on the exception type;
[0039] The vehicle-side logs are uploaded to the server-side based on the upload strategy, so that the server-side obtains the vehicle-side logs uploaded by the target vehicle; the vehicle-side logs are screened to obtain a target log set, which includes vehicle-side logs corresponding to at least one type of stability problem; the number of errors corresponding to each type of stability problem in the target log set is counted; the problem level corresponding to the stability problem is determined based on each type of stability problem and its corresponding number of errors; the cabin stability analysis of the target vehicle is performed based on the problem level, and the corresponding analysis results are obtained.
[0040] The present invention analyzes the acquired vehicle-side abnormal events to obtain the vehicle-side log and the abnormality type, determines the upload strategy corresponding to the abnormality type, and uploads the vehicle-side log to the server-side based on the upload strategy, so that the server-side performs a cabin stability analysis on the target vehicle based on the vehicle-side log, which can ensure the acquisition quality of the vehicle-side log and further improve the effective identification of the corresponding problem logs that cause hidden dangers to vehicle driving safety.
[0041] In an optional implementation, determining an upload strategy based on the exception type includes:
[0042] Determine whether the abnormal type is the vehicle-side preset type;
[0043] If the abnormality type is a vehicle-side preset type, the upload strategy is determined to be a first preset upload strategy, wherein the first preset upload strategy is an instant upload strategy for uploading the log file at a preset time;
[0044] If the exception type is not a vehicle-side preset type, the upload strategy is determined to be a second preset upload strategy, wherein the second preset upload strategy is a periodic upload strategy for uploading log files within a preset period.
[0045] The present invention designs a hierarchical uploading strategy for vehicle-side logs based on different exception types on the vehicle side, which can improve the efficiency of log uploading.
[0046] In a third aspect, the present invention provides an intelligent cockpit stability problem monitoring device, which is applied to a server side, and the device includes:
[0047] The log acquisition module is used to obtain the vehicle-side log uploaded by the target vehicle;
[0048] A log screening module is used to screen the vehicle-side logs to obtain a target log set, where the target log set contains at least one vehicle-side log corresponding to a type of stability problem;
[0049] The problem statistics module is used to count the number of errors corresponding to each type of stability problem in the target log set;
[0050] A level determination module, used to determine the problem level corresponding to the stability problem based on each type of stability problem and its corresponding number of error reports;
[0051] The stability analysis module is used to perform cabin stability analysis on the target vehicle based on the problem level and obtain corresponding analysis results.
[0052] The intelligent cockpit stability problem monitoring device applied to the server side of the present invention can effectively identify the problem logs corresponding to the hidden dangers that cause the vehicle driving safety, has the advantage of high recognition efficiency, and greatly improves the user experience.
[0053] In a fourth aspect, the present invention provides an intelligent cockpit stability problem monitoring device, which is applied to a vehicle side, and the device includes:
[0054] An event acquisition module is used to acquire abnormal events of a target vehicle;
[0055] An abnormality determination module, used to determine the vehicle-side log and abnormality type corresponding to the abnormal event respectively;
[0056] A strategy determination module, used to determine the upload strategy based on the exception type;
[0057] The log upload module is used to upload the vehicle-side log to the server-side based on the upload strategy, so that the server-side obtains the vehicle-side log uploaded by the target vehicle; the vehicle-side log is screened to obtain a target log set, and the target log set contains at least one type of vehicle-side log corresponding to the stability problem; the number of errors corresponding to each type of stability problem in the target log set is counted; based on each type of stability problem and its corresponding number of errors, the problem level corresponding to the stability problem is determined; based on the problem level, the cabin stability analysis of the target vehicle is performed to obtain the corresponding analysis results.
[0058] The present invention is applied to the intelligent cockpit stability problem monitoring device on the vehicle side, which can ensure the acquisition quality of the vehicle side logs, thereby improving the effective identification of corresponding problem logs that cause hidden dangers to vehicle driving safety.
[0059] In a fifth aspect, the present invention provides a smart cockpit stability problem monitoring system, the system includes a server side and a vehicle side, the server side and the vehicle side both include a controller, the controller includes a memory and a processor, the memory and the processor are communicatively connected to each other, computer instructions are stored in the memory, and the processor executes the computer instructions to execute a smart cockpit stability problem monitoring method according to the first aspect or any corresponding embodiment thereof, or executes a smart cockpit stability problem monitoring method according to the second aspect or any corresponding embodiment thereof.
[0060] In a sixth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to cause a computer to execute a method for monitoring stability problems of an intelligent cockpit according to the first aspect or any corresponding embodiment thereof, or to execute a method for monitoring stability problems of an intelligent cockpit according to the second aspect or any corresponding embodiment thereof.
[0061] The intelligent cockpit stability problem monitoring method of the present invention obtains a target log set containing at least one type of vehicle-side log corresponding to stability problems by filtering the vehicle-side logs uploaded by the target vehicle designed on the server side, and counts the number of error reports of each type of stability problem in the set, determines the problem level based on each type of stability problem and its corresponding number of error reports, and performs a cockpit stability analysis process based on the problem level; and a process designed on the vehicle side for obtaining vehicle-side abnormal events and their corresponding abnormal types, and performing a graded upload strategy for the vehicle-side logs based on different abnormal types, which not only ensures the acquisition quality of the vehicle-side logs, but also helps to improve the accuracy and efficiency of identifying the corresponding problem logs that cause hidden dangers to vehicle driving safety, thereby enhancing the user experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0062] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0063] Figure 1 is a flow chart of a method for monitoring stability problems of an intelligent cockpit according to an embodiment of the present invention;
[0064] Figure 2is a flow chart of another intelligent cockpit stability problem monitoring method according to an embodiment of the present invention;
[0065] Figure 3 is a flow chart of another intelligent cockpit stability problem monitoring method according to an embodiment of the present invention;
[0066] Figure 4 It is a flow chart of the overall business set of the stability system;
[0067] Figure 5 It is a flow chart of the big data sorting system;
[0068] Figure 6 It is a flowchart of abnormal self-diagnosis;
[0069] Figure 7 This is a flowchart of event alarm and log path push;
[0070] Figure 8 This is a flow chart of log compression and uploading;
[0071] Fig. 9 It is a flowchart of event definition and log upload policy configuration;
[0072] Fig.10 is a structural block diagram of an intelligent cockpit stability problem monitoring device according to an embodiment of the present invention;
[0073] Fig.11 is a structural block diagram of another intelligent cockpit stability problem monitoring device according to an embodiment of the present invention;
[0074] Fig.12 Schematic diagram of the structure of the controller of the system according to the embodiment of the present invention. DETAILED DESCRIPTION
[0075] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.
[0076] An embodiment of the present invention provides an embodiment of a method for monitoring stability problems of an intelligent cockpit. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.
[0077] In this embodiment, a method for monitoring the stability of an intelligent cockpit is provided, which is applied to a server. Figure 1 FIG. 1 is a flow chart of a method for monitoring stability problems of an intelligent cockpit according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:
[0078] Step S101, obtaining the vehicle-side log uploaded by the target vehicle.
[0079] It should be noted that the acquisition method and specific content of the vehicle-side log in this embodiment are not limited here, and are adaptively adjusted based on actual needs. For example, the target vehicle uploads the vehicle-side log corresponding to the vehicle system restart collected by itself to the server (also known as the backend cloud server) connected to it through the vehicle network, which is only an exemplary explanation.
[0080] Step S102, screening the vehicle-side logs to obtain a target log set, wherein the target log set includes vehicle-side logs corresponding to at least one type of stability problem.
[0081] It should be noted that the target log set of this embodiment contains different types of stability problems, and its specific types are adaptively set based on actual needs, such as abnormal restart of the vehicle computer, abnormal startup, application error and system service abnormality, among which, abnormal restart is the abnormal restart of the vehicle computer software (also known as the vehicle computer soft restart Watchdog); abnormal startup means that the vehicle cannot enter the homepage for a long time after startup; application error includes application no response (Application No Response, ANR), that is, the vehicle computer ANR freeze problem and application abnormal end (Application Force Close); system service abnormality includes system service process abnormal crash (System Service Crash), which is only an exemplary explanation. It should be explained that in Android system development, Crash refers to the crash of the application due to unhandled exceptions or errors during operation.
[0082] Step S103, counting the number of error reports corresponding to each type of stability problem in the target log set.
[0083] In this embodiment, a statistical method commonly used in the art is used to statistically record the number of error reports corresponding to different types of stability problems.
[0084] Step S104, determining the problem level corresponding to the stability problem based on each type of stability problem and its corresponding number of error reports.
[0085] In this embodiment, the specific classification number of the problem level is adaptively determined based on the type and number of vehicle-side log problems contained in different vehicle models. For example, for a certain type of vehicle model, based on the number of modules it contains and the degree of impact on the vehicle side, such as a total of 5 modules including the media center module, its problem level is set accordingly to include high and low levels, which is only for exemplary explanation.
[0086] Step S105 , performing cabin stability analysis on the target vehicle based on the problem level, and obtaining corresponding analysis results.
[0087] The intelligent cockpit stability problem monitoring method of the embodiment of the present invention obtains a target log set containing at least one type of vehicle-side log corresponding to stability problems by screening the vehicle-side logs uploaded by the target vehicle, counts the number of errors corresponding to each type of stability problem in the set, determines the problem level based on each type of stability problem and its corresponding number of errors, and performs cockpit stability analysis on the target vehicle based on the problem level. This method can effectively identify problem logs corresponding to hidden dangers to vehicle driving safety, has the advantage of high recognition efficiency, and greatly improves the user experience.
[0088] In this embodiment, a method for monitoring the stability of an intelligent cockpit is provided, which is applied to a server. Figure 2 FIG. 1 is a flow chart of another intelligent cockpit stability problem monitoring method according to an embodiment of the present invention. Figure 2 As shown, the process includes the following steps:
[0089] Step S201, obtain the vehicle-side log uploaded by the target vehicle. Figure 1 Step S101 of the illustrated embodiment will not be described in detail here.
[0090] Step S202, screening the vehicle-side logs to obtain a target log set, wherein the target log set includes vehicle-side logs corresponding to at least one type of stability problem.
[0091] Specifically, the above step S202 includes:
[0092] Step S2021, extracting log keywords corresponding to the vehicle-side log.
[0093] In actual applications, multiple software (i.e., applications) are installed in the cockpit system on the vehicle side. When a certain software runs abnormally, a corresponding error log (also called the vehicle system log) will be generated to record error information that occurs during the program operation. Among them, the error log or other generated vehicle-side logs contain keywords that describe this type of log, and the specific setting of the keyword can be adaptively set based on actual user needs. For example, if the target vehicle has a vehicle system restart problem, a vehicle system log with the "WATCHDOG KILLING SYSTEM PROCESS" logo will be generated accordingly. This logo is the log keyword, which is only used as an example.
[0094] Step S2022, based on the correspondence between log keywords and preset keywords and stability problem types, determine the stability problem type corresponding to each log keyword.
[0095] In this embodiment, the specific type of the correspondence between the preset keyword and the stability problem type is not limited here, and is adaptively set based on actual needs, such as a mapping table or a mapping file, including mapping relationships between different keywords and stability problem types. For example, if the preset keyword is "WATCHDOG KILLING SYSTEM PROCESS" (which represents the vehicle system restart problem), then the stability problem type that has a mapping relationship with the keyword is the vehicle system restart problem, which is only for exemplary explanation.
[0096] Step S2023, filter the vehicle-side logs corresponding to the log keywords under each stability problem type to obtain a target log set.
[0097] In the embodiment of the present invention, the stability problem type corresponding to each log keyword is determined by the correspondence between the log keyword corresponding to the vehicle-side log and the preset keyword and the stability problem type, and a target log set is constructed based on the vehicle-side log corresponding to the log keyword under each stability problem type, which greatly ensures the quality of the target log set, helps to subsequently improve the accuracy and efficiency of cabin stability analysis, and enhances the user experience.
[0098] Step S203: Count the number of errors corresponding to each type of stability problem in the target log set. Figure 1 Step S103 of the illustrated embodiment will not be described in detail here.
[0099] Step S204, determining the problem level corresponding to the stability problem based on each type of stability problem and its corresponding number of error reports.
[0100] In this embodiment, the problem level includes three levels, and the specific setting methods of the three levels are all based on the actual demand adaptability setting, such as the three levels are the first level, the second level and the third level. Specifically, the above step S204 includes:
[0101] Step A1, determine whether the stability problem is the first preset problem, and the first preset problem is a problem related to the startup of the vehicle intelligent cockpit software.
[0102] It should be noted that the first preset problem in this embodiment is a problem that has a greater impact on the stability of the vehicle cabin system in actual applications, and its specific content is adaptively adjusted based on actual needs, such as the vehicle computer soft restart Watchdog.
[0103] Step A2, when the stability problem is the first preset problem, determine whether the number of error reports corresponding to the stability problem is less than a preset number threshold.
[0104] In this embodiment, the specific value of the preset number of times threshold is not limited here, and is determined based on the adaptability of actual needs. For example, the preset number of times threshold is 1 time, which is only used as an exemplary description.
[0105] Step A3: If the number of error reports corresponding to the stability problem is not less than a preset number threshold, the problem level is determined to be the first level.
[0106] In the embodiment of the present invention, taking into account that in actual applications, problems related to the startup of the vehicle's intelligent cockpit software have the greatest impact on the vehicle, a corresponding process is designed for matching stability problems with the first preset problems. This can speed up the process of determining the problem level corresponding to the stability problem, further speed up the identification of problem logs corresponding to hidden dangers to vehicle driving safety, improve the efficiency of intelligent cockpit stability monitoring, and ensure the safe use of the vehicle.
[0107] Step A4, when the stability problem is not the first preset problem, if the number of error reports corresponding to the stability problem is not less than the first preset threshold, the problem level is determined to be the first level.
[0108] Step A5: If the number of error reports corresponding to the stability problem is less than the first preset threshold and not less than the second preset threshold, the problem level is determined to be the second level.
[0109] Step A6, if the number of errors corresponding to the stability problem is less than the third preset threshold, the problem level is determined to be the third level, wherein the second preset threshold is greater than the third preset threshold and less than the first preset threshold, and the second level is higher than the third level and lower than the first level.
[0110] It should be noted that the specific values of the first preset threshold, the second preset threshold and the third preset threshold in this embodiment are not limited here and can be adaptively determined based on actual needs.
[0111] In the embodiment of the present invention, the specific problem level is determined by the type and the number of error reports corresponding to the stability problem, which not only ensures the accuracy of the problem level, but also guarantees the safe use of the vehicle and improves user satisfaction.
[0112] In actual applications, since the vehicle cockpit system is monitored in real time, the server backend will perform real-time dynamic analysis and problem level updates based on the number of vehicle-side logs to ensure the stability of the vehicle cockpit system. Specifically, the above step S204 also includes:
[0113] Step B1: within a preset time, if the cumulative number of error reports of the third-level corresponding stability problem is greater than the first number threshold, the problem level of the third-level corresponding stability problem is updated to the second level.
[0114] In this embodiment, the specific value of the preset time is adaptively adjusted based on actual needs. For example, the preset time is 1 month, which is only used as an example.
[0115] Step B2: within the preset time, if the cumulative number of error reports of the second-level corresponding stability problem is greater than the second number threshold, the problem level of the second-level corresponding stability problem is updated to the first level.
[0116] In this embodiment, specific values of the first number threshold and the second number threshold are not limited here, and both can be adaptively adjusted based on actual needs.
[0117] In the embodiment of the present invention, by determining the cumulative number of error reports of stability problems within a preset time and the set number threshold, and optimizing the current problem level based on the determination result, the accuracy of determining the problem level can be guaranteed to a certain extent, thereby improving the user experience.
[0118] In a specific embodiment, the backend cloud server divides the problem level (also called the problem severity) according to the type and occurrence frequency of different stability problems (i.e., the custom configuration strategy of the problem log), and obtains different problem severity levels, such as serious problems, general problems and prompt problems. The specific strategies include:
[0119] 1. Serious problems: According to the policy configuration script, the car computer soft restart Watchdog, the hanging problem Hand_detect, the abnormal problem Panic, the memory overflow OOM problem; among them, the car computer soft restart Watchdog, which seriously affects the operation of the vehicle, can be considered a serious problem if it occurs once; for other problems, a single application (the same package name has more than 3000 ANRs within 30 days), a single application (the same package name has more than 1000 crashes within 30 days), and other single applications (the same package name has more than 3000 crashes within 30 days) can all be considered serious problems.
[0120] 2. General issues: According to the policy configuration script, a single application in a Level 4 project (more than 1,000 and less than 3,000 ANRs for the same package name within 30 days), a single application (more than 600 but less than 1,000 crashes for the same package name within 30 days), and other single applications with more than 1,000 but less than 3,000 errors of the same type can all be considered general issues.
[0121] 3. Prompt issues: According to the policy configuration script, a single application in a Level 4 project (the same package name has less than or equal to 1000 ANRs in 30 days), a single application (the same package name has less than or equal to 600 crashes in 30 days), and other single applications with the same type of error less than or equal to 1000 times in total can all be considered prompt issues.
[0122] In this embodiment, since the vehicle cockpit system is monitored in real time, the background cloud server will dynamically update the severity level of the problem in real time. For example, the media center module reported 15 ANRs on the first day. At this time, according to the strategy, the current problem severity level is determined to be a prompt problem. After 2 weeks, the prompt problem has accumulated 1,300 ANR errors. At this time, the level corresponding to the prompt problem will be raised to the general problem level. This is only for illustrative purposes.
[0123] Step S205 , performing cabin stability analysis on the target vehicle based on the problem level, and obtaining corresponding analysis results.
[0124] Specifically, the above step S205 includes:
[0125] Step S2051, if the problem level is the first level, obtain the first vehicle-side log corresponding to the first level and generate a first warning message, the first warning message is used to remind the R&D personnel to process the first vehicle-side log.
[0126] In this embodiment, when the problem level is the first level, that is, a serious problem, manual intervention is required for corresponding processing, such as R&D personnel obtaining the corresponding problem log and analyzing the problem log based on their own experience to decide whether to perform iterative optimization on the project or software code to which the problem log belongs.
[0127] Step S2052: If the problem level is the second level, obtain the second vehicle-side log corresponding to the second level and generate a second warning message, wherein the second warning message is used to remind R&D personnel to process the second vehicle-side log, and the processing priority of the second warning message is lower than that of the first warning message.
[0128] In this embodiment, when the problem level is the second level, that is, a general problem, manual intervention is also required for corresponding processing, such as R&D personnel screening some problem logs, such as TOP5 problem logs for analysis.
[0129] Step S2053: If the problem level is the third level, return to the step of obtaining the vehicle-side log uploaded by the target vehicle.
[0130] In this embodiment, when the problem level is the third level, that is, when the problem is prompted, it is considered that it has little impact on the stability of the vehicle cockpit system and can be ignored, so the process of obtaining the vehicle-side log uploaded by the target vehicle in the intelligent cockpit stability problem monitoring method of this embodiment is returned to execute.
[0131] In the embodiment of the present invention, by designing a cockpit stability analysis process corresponding to different problem levels, the efficiency of the cockpit stability analysis can be greatly improved, the effective identification of the corresponding problem logs that cause hidden dangers to vehicle driving safety is achieved, and the user satisfaction is greatly improved.
[0132] In this embodiment, a method for monitoring the stability of an intelligent cockpit is provided, which is applied to the vehicle side. Figure 3 FIG. 1 is a flow chart of another intelligent cockpit stability problem monitoring method according to an embodiment of the present invention. Figure 3 As shown, the process includes the following steps:
[0133] Step S301, obtaining abnormal events of the target vehicle.
[0134] In this embodiment, the specific type of abnormal event is not limited here, and is determined based on actual demand adaptability. For example, the vehicle running abnormality has a deadlock problem Hand_detect, which is only used as an exemplary description.
[0135] Step S302, respectively determine the vehicle-side log and abnormality type corresponding to the abnormal event.
[0136] It should be noted that the specific contents of the vehicle-side logs and exception types in this embodiment are adaptively adjusted based on actual project requirements. For example, the vehicle-side logs include the flow logs of the vehicle cockpit system, i.e., the vehicle Android system, the JAVA layer stack logs, the C++ layer stack logs, the bottom driver logs, the vehicle-mounted 4G module network message logs, and the vehicle-mounted controller-related CAN signal logs, where CAN is the Controller Area Network, i.e., the controller local area network, which is only used as an example.
[0137] Step S303: determine the upload strategy based on the exception type.
[0138] Specifically, the above step S303 includes:
[0139] Step C1, determine whether the abnormal type is the vehicle-side preset type.
[0140] In this embodiment, the vehicle-side preset type is a customization of the vehicle-side log type, and its specific content is determined based on the adaptability of different vehicle models. For example, for a certain vehicle model, its vehicle-side preset types include vehicle soft restart Watchdog, deadlock problem Hand_detect, abnormal problem Panic, etc., which are only used as an exemplary description.
[0141] Step C2: if the abnormality type is a vehicle-side preset type, the upload strategy is determined to be a first preset upload strategy, wherein the first preset upload strategy is an instant upload strategy for uploading the log file at a preset time.
[0142] In this embodiment, the specific content of the preset time is not limited here, and is adaptively adjusted based on actual needs. For example, the preset time is 01:00 in the morning, which is only used as an exemplary description.
[0143] Step C3: if the abnormality type is not a vehicle-side preset type, the upload strategy is determined to be a second preset upload strategy, wherein the second preset upload strategy is a periodic upload strategy for uploading log files within a preset period.
[0144] In this embodiment, the specific content of the preset period is not limited here, and is adaptively adjusted based on actual needs. For example, the preset period is 7 days, which is only used as an exemplary description.
[0145] In the embodiment of the present invention, by designing a hierarchical uploading strategy for vehicle-side logs based on different exception types on the vehicle side, the efficiency of log uploading can be improved.
[0146] Step S304, uploading the vehicle-side log to the server-side based on the upload strategy, so that the server-side obtains the vehicle-side log uploaded by the target vehicle; filtering the vehicle-side log to obtain a target log set, the target log set contains vehicle-side logs corresponding to at least one type of stability problem; counting the number of errors corresponding to each type of stability problem in the target log set; determining the problem level corresponding to the stability problem based on each type of stability problem and its corresponding number of errors; performing cabin stability analysis on the target vehicle based on the problem level, and obtaining corresponding analysis results.
[0147] The embodiment of the present invention is applied to the intelligent cockpit stability problem monitoring method on the vehicle side. By analyzing the acquired vehicle-side abnormal events, the vehicle-side log and the abnormality type are obtained, the upload strategy corresponding to the abnormality type is determined, and the vehicle-side log is uploaded to the server side based on the upload strategy, so that the server side performs a cockpit stability analysis on the target vehicle based on the vehicle-side log, which can ensure the acquisition quality of the vehicle-side log, and further improve the effective identification of the corresponding problem logs that cause hidden dangers to vehicle driving safety.
[0148] In a specific embodiment, in order to solve the problem that it is difficult to effectively identify stability problems in the existing intelligent cockpit stability monitoring, resulting in hidden dangers to vehicle driving safety and affecting user experience, a smart cockpit stability problem monitoring system is provided, referring to Figure 4 , including the vehicle side and the server side. Among them, the vehicle side is used to collect cockpit system related logs, obtain the vehicle cockpit system set and upload it to the server side, that is, the background cloud server, through the wireless network; the background cloud server contains a big data sorting system, which mainly simulates manual work, that is, locates and analyzes software problem logs through log keywords. Specifically, through automated sorting tools, automatic sorting of problem logs based on massive logs based on big data is realized, and a log sorting system set is obtained. The severity of the problem is confirmed according to the type and cumulative number of stability problems, so as to realize the monitoring of vehicle cockpit stability problems.
[0149] In this embodiment, the stability-related module log collection system based on the user's vehicle-mounted terminal realizes semi-automatic collection of effective logs of stability problems based on real users by pre-setting the automatic trigger logic of problem logs; in addition, based on the daily usage habits of the vehicle-mounted terminal users, a log hierarchical upload strategy is set to complete the weak-perception upload of logs.
[0150] The intelligent cockpit stability problem monitoring system of the embodiment of the present invention effectively identifies the analysis problem of massive data based on the big data sorting system; through the real usage scenarios of real users of the vehicle terminal and the data collected by the massive user, and the identification and sorting stability problems based on the big data sorting system, it effectively solves the problem of difficulty in obtaining effective logs under the occasional low-probability characteristics of stability, and overcomes the dilemma that stability problems cannot be effectively identified with massive user data.
[0151] In one specific embodiment, see Figure 5 The big data sorting system of the backend cloud server locates and analyzes software problems based on log keywords and the number of log repetitions, and implements the process of sorting massive logs of big data and defining and confirming the severity of the problem based on the stability type and cumulative number of times, including:
[0152] 1. Through the Android system log, automatically search the log for the keyword "WATCHDOG KILLING SYSTEMPROCESS" to identify the vehicle system restart problem (such as Figure 5 Type B in the chart has a greater impact on cabin stability, with severity indicated by **); through the Android system log, the keyword "ANR" in the log is automatically retrieved to identify the ANR stuck problem of the vehicle (such as Figure 5 Type A has a general impact on cabin stability, with severity indicated by *).
[0153] 2. Confirm the number of times the problem has occurred by recording the cumulative number of problems. Specifically, for restart problems, according to the associated settings, more than or equal to 1 time is a serious problem; for freeze problems, according to the associated settings, a gradient threshold is used to set different severity levels. For example, the same package list is judged as a serious problem if it is greater than or equal to 3,000 times a day; a general problem if it is greater than or equal to 1,000 times; and a warning problem if it is less than 1,000 times. Customized configuration of the problem log can be made according to the stability type and cumulative number of the BUG system.
[0154] In a specific embodiment, based on the user vehicle terminal stability related module log collection system, by pre-setting the automatic trigger logic, see Figure 6 As shown. Figure 6It can be seen that the system or application on the vehicle side will perform self-diagnosis (i.e., detection of abnormal events) in real time during operation; if the operation is abnormal, the corresponding abnormal event will be triggered; by collecting abnormal information of abnormal events, the corresponding project management module on the vehicle side is improved. This management module is used to monitor the stability of the vehicle cockpit system, also known as the SPM management module (or SPM management platform). Specifically, during the daily operation and use of the vehicle system, such as the occurrence of an ANR crash of the application, the vehicle system will capture the ANR event according to the customized log service module of the SPM system, that is, the SPM management module, and obtain the corresponding problem log (such as the upper-layer flow log, the middle-layer C++, JAVA stack log, the bottom-layer driver layer print log, the vehicle network module message, the vehicle-side controller CAN log, etc.), and based on the set timed upload rules (such as uploading the problem log to the background cloud server at 01:00 am on Saturday), based on the real user's daily usage scenarios, semi-automatic collection of effective logs of stable problems is achieved. The specific event alarm and upload path push process of the SPM management platform is as follows: Figure 7 It should be noted that Figure 7 Kafka in the example is a queue, which is used to build a real-time data pipeline to reliably stream records and process data from producers to consumers; LOT application is the name of an application on the vehicle side. Figure 7 It can be seen that for serious problems or general problems in the TOP10 that occur on the server, it is considered that there are defects in the module development of this project that need to be resolved. Therefore, the corresponding problem log on the server and the warning information obtained by analysis are sent by email to the person in charge of module development of the corresponding project, thereby realizing the email alarm process.
[0155] In a specific embodiment, based on the daily use habits of vehicle terminal users, a hierarchical upload strategy is adopted (for example, three levels are defined as serious, general, and prompt according to different problem types and cumulative occurrence times, and serious problems defined as restart problems are defined as high priority, and timely log upload can be prioritized; general problems such as ANR are defined as low priority, and periodic log upload is performed, among which high-priority problem logs need to be uploaded to the server backend on the same day, and low-priority problem logs are uploaded to the backend cloud server once a week). Specifically, the detailed process of log upload and its related configuration strategies are shown in Figures 8 to 9 It should be noted that Fig. 9 The events in the list are abnormal user issues that require attention and monitoring, such as abnormal restart, application freeze, application crash, abnormal switch opening, etc.
[0156] In the embodiment of the present invention, through the real usage scenarios of real users on the vehicle side and the data collected and uploaded by massive users, and based on the big data sorting system of the background cloud server, the stability problem of massive data is effectively identified, and the problem of difficulty in obtaining effective logs under the occasional low-probability characteristics of stability is effectively solved. The dilemma of being unable to effectively identify stability problems with massive user data is overcome, and the problem logs corresponding to the hidden dangers to vehicle driving safety can be effectively identified, which improves the user experience to a certain extent, and thus helps to improve the stability of the cockpit software system.
[0157] In this embodiment, an intelligent cockpit stability problem monitoring device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and will not be repeated hereafter. As the term "module" is used below, it can implement a combination of software and / or hardware of a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.
[0158] The present invention provides an intelligent cockpit stability problem monitoring device, which is applied to the server side, such as Fig.10 As shown, the device comprises:
[0159] The log acquisition module 1001 is used to acquire the vehicle-side log uploaded by the target vehicle.
[0160] The log screening module 1002 is used to screen the vehicle-side logs to obtain a target log set, where the target log set contains at least one type of vehicle-side log corresponding to stability issues.
[0161] The problem statistics module 1003 is used to count the number of errors corresponding to each type of stability problem in the target log set.
[0162] The level determination module 1004 is used to determine the problem level corresponding to the stability problem based on each type of stability problem and its corresponding number of error reports.
[0163] The stability analysis module 1005 is used to perform cabin stability analysis on the target vehicle based on the problem level and obtain corresponding analysis results.
[0164] In some optional embodiments, the log screening module 1002 includes: a first screening submodule, a second screening submodule and a third screening submodule; wherein the first screening submodule is used to extract log keywords corresponding to the vehicle-side logs; the second screening submodule is used to determine the stability problem type corresponding to each log keyword based on the correspondence between the log keywords and preset keywords and the stability problem type; the third screening submodule is used to screen the vehicle-side logs corresponding to the log keywords under each stability problem type to obtain a target log set.
[0165] In some optional implementations, the level determination module 1004 includes: a first determination submodule, a second determination submodule, a third determination submodule, a fourth determination submodule, a fifth determination submodule and a sixth determination submodule; wherein the first determination submodule is used to determine whether the stability problem is a first preset problem, and the first preset problem is a problem related to the startup of the vehicle intelligent cockpit software; the second determination submodule is used to determine whether the number of error reports corresponding to the stability problem is less than a preset number threshold when the stability problem is the first preset problem; the third determination submodule is used to determine the problem if the number of error reports corresponding to the stability problem is not less than the preset number threshold. The level is the first level; the fourth determination submodule is used to determine that the problem level is the first level when the stability problem is not the first preset problem and the number of error reports corresponding to the stability problem is not less than the first preset threshold; the fifth determination submodule is used to determine that the problem level is the second level if the number of error reports corresponding to the stability problem is less than the first preset threshold and not less than the second preset threshold; the sixth determination submodule is used to determine that the problem level is the third level if the number of error reports corresponding to the stability problem is less than the third preset threshold, wherein the second preset threshold is greater than the third preset threshold and less than the first preset threshold, and the second level is higher than the third level and lower than the first level.
[0166] In some optional embodiments, the level determination module 1004 also includes: a first optimization submodule and a second optimization submodule; wherein the first optimization submodule is used to update the problem level of the third level corresponding stability problem to the second level if the cumulative number of error reports of the third level corresponding stability problem is greater than the first number threshold within a preset time; and the second optimization submodule is used to update the problem level of the second level corresponding stability problem to the first level if the cumulative number of error reports of the second level corresponding stability problem is greater than the second number threshold within a preset time.
[0167] In some optional embodiments, the stability analysis module 1005 includes: a first analysis submodule, a second analysis submodule and a third analysis submodule; wherein the first analysis submodule is used to obtain the first vehicle-side log corresponding to the first level and generate a first warning information if the problem level is the first level, and the first warning information is used to remind the R&D personnel to process the first vehicle-side log; the second analysis submodule is used to obtain the second vehicle-side log corresponding to the second level and generate a second warning information if the problem level is the second level, wherein the second warning information is used to remind the R&D personnel to process the second vehicle-side log, and the processing priority of the second warning information is lower than that of the first warning information; the third analysis submodule is used to return to the step of obtaining the vehicle-side log uploaded by the target vehicle if the problem level is the third level.
[0168] The present invention also provides an intelligent cockpit stability problem monitoring device, which is applied to the vehicle side, such as Fig.11As shown, the device comprises:
[0169] The event acquisition module 1101 is used to acquire abnormal events of the target vehicle.
[0170] The abnormality determination module 1102 is used to respectively determine the vehicle-side log and abnormality type corresponding to the abnormal event.
[0171] The strategy determination module 1103 is used to determine the upload strategy based on the exception type.
[0172] The log uploading module 1104 is used to upload the vehicle-side log to the server-side based on the uploading strategy, so that the server-side obtains the vehicle-side log uploaded by the target vehicle; screens the vehicle-side log to obtain a target log set, which includes at least one type of vehicle-side log corresponding to stability problems; counts the number of errors corresponding to each type of stability problem in the target log set; determines the problem level corresponding to the stability problem based on each type of stability problem and its corresponding number of errors; performs cabin stability analysis on the target vehicle based on the problem level, and obtains corresponding analysis results.
[0173] In some optional embodiments, the strategy determination module 1103 includes: a first determination submodule, a second determination submodule and a third determination submodule; wherein the first determination submodule is used to determine whether the exception type is a vehicle-side preset type; the second determination submodule is used to determine that the upload strategy is the first preset upload strategy if the exception type is a vehicle-side preset type, wherein the first preset upload strategy is an instant upload strategy for uploading the log file at a preset time; the third determination submodule is used to determine that the upload strategy is the second preset upload strategy if the exception type is not a vehicle-side preset type, wherein the second preset upload strategy is a periodic upload strategy for uploading the log file within a preset period.
[0174] The further functional description of each of the above modules is the same as that of the above corresponding embodiments and will not be repeated here.
[0175] The intelligent cockpit stability problem monitoring device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.
[0176] In the embodiment of the present invention, an intelligent cockpit stability problem monitoring device is designed and applied to the server side, which can effectively identify the problem logs corresponding to the hidden dangers to the vehicle driving safety, has the advantage of high identification efficiency, and greatly improves the user experience; in addition, by designing an intelligent cockpit stability problem monitoring device applied to the vehicle side, it is possible to ensure the acquisition quality of the vehicle-side logs, thereby improving the effective identification of the problem logs corresponding to the hidden dangers to the vehicle driving safety.
[0177] The embodiment of the present invention also provides an intelligent cockpit stability problem monitoring system, the system includes a server side and a vehicle side, and both the server side and the vehicle side include a controller. The controller in this embodiment is the overall controller of the system, which is used to perform operations such as power supply / power off, sleep and wake up of the sub-controllers and network nodes under it, and each of its power supply interfaces can collect the real-time output current. Other controllers with the above functions are applicable.
[0178] Fig.12 is a schematic diagram of the structure of the controller provided by an optional embodiment of the present invention, such as Fig.12 As shown, the controller includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. The various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process instructions executed in the controller, including instructions stored in or on the memory to display graphical information of the GUI on an external input / output device (such as a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple controllers can be connected, and each controller provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Fig.12 A processor 10 is taken as an example.
[0179] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.
[0180] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.
[0181] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required by at least one function; the data storage area may store data created according to the use of the controller, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the controller via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0182] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.
[0183] The controller also includes a communication interface 30 for the main control chip to communicate with other devices or a communication network.
[0184] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor main control chip or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor or hardware, the method shown in the above embodiment is implemented.
[0185] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.
Claims
1. A method for monitoring stability problems of an intelligent cockpit, applied to a server, characterized in that: The method comprises: Get the vehicle-side log uploaded by the target vehicle; The vehicle-side logs are screened to obtain a target log set, wherein the target log set includes vehicle-side logs corresponding to at least one type of stability problem; Counting the number of error reports corresponding to each type of stability problem in the target log set; Determine a problem level corresponding to the stability problem based on each type of stability problem and its corresponding number of error reports; A cabin stability analysis is performed on the target vehicle based on the problem level, and a corresponding analysis result is obtained.
2. The intelligent cockpit stability problem monitoring method according to claim 1 is characterized in that: The determining of the problem level corresponding to the stability problem based on each type of stability problem and its corresponding number of error reports includes: Determining whether the stability problem is a first preset problem, where the first preset problem is a problem related to starting the vehicle intelligent cockpit software; When the stability problem is the first preset problem, determining whether the number of error reports corresponding to the stability problem is less than a preset number threshold; If the number of error reports corresponding to the stability problem is not less than the preset number threshold, the problem level is determined to be the first level.
3. The intelligent cockpit stability problem monitoring method according to claim 2 is characterized in that: The method further comprises: When the stability problem is not the first preset problem, if the number of error reports corresponding to the stability problem is not less than the first preset threshold, determining the problem level to be the first level; If the number of error reports corresponding to the stability problem is less than the first preset threshold and not less than the second preset threshold, the problem level is determined to be the second level; If the number of errors corresponding to the stability problem is less than the third preset threshold, the problem level is determined to be the third level, wherein the second preset threshold is greater than the third preset threshold and less than the first preset threshold, and the second level is higher than the third level and lower than the first level.
4. The intelligent cockpit stability problem monitoring method according to claim 3 is characterized in that: The method further comprises: Within a preset time, if the cumulative number of error reports of the third-level corresponding stability problem is greater than the first number threshold, the problem level of the third-level corresponding stability problem is updated to the second level; Within the preset time, if the cumulative number of error reports of the second-level corresponding stability problem is greater than the second number threshold, the problem level of the second-level corresponding stability problem is updated to the first level.
5. The intelligent cockpit stability problem monitoring method according to any one of claims 1 to 4, characterized in that: The cabin stability analysis of the target vehicle is performed based on the problem level, and corresponding analysis results are obtained, including: If the problem level is the first level, a first vehicle-side log corresponding to the first level is obtained and a first warning information is generated, where the first warning information is used to remind the R&D personnel to process the first vehicle-side log; If the problem level is the second level, a second vehicle-side log corresponding to the second level is obtained and a second warning information is generated, wherein the second warning information is used to remind the R&D personnel to process the second vehicle-side log, and the processing priority of the second warning information is lower than that of the first warning information; If the problem level is the third level, return to the step of obtaining the vehicle-side log uploaded by the target vehicle.
6. The intelligent cockpit stability problem monitoring method according to claim 1, characterized in that: The screening of the vehicle-side logs to obtain a target log set includes: Extracting log keywords corresponding to the vehicle-side log; Based on the correspondence between the log keywords and the preset keywords and the stability problem types, determine the stability problem type corresponding to each log keyword; Filter the vehicle-side logs corresponding to the log keywords under each stability problem type to obtain the target log set.
7. A method for monitoring the stability of an intelligent cockpit, applied to a vehicle, characterized in that: The method comprises: Obtain abnormal events of the target vehicle; Respectively determine the vehicle-side log and the abnormality type corresponding to the abnormal event; Determining an upload strategy based on the exception type; The vehicle-side log is uploaded to the server-side based on the upload strategy, so that the server-side obtains the vehicle-side log uploaded by the target vehicle; the vehicle-side log is screened to obtain a target log set, wherein the target log set includes vehicle-side logs corresponding to at least one type of stability problem; the number of errors corresponding to each type of stability problem in the target log set is counted; based on each type of stability problem and its corresponding number of errors, the problem level corresponding to the stability problem is determined; based on the problem level, a cabin stability analysis is performed on the target vehicle to obtain a corresponding analysis result.
8. The intelligent cockpit stability problem monitoring method according to claim 7, characterized in that: The determining of the upload strategy based on the exception type includes: Determine whether the abnormal type is a vehicle-side preset type; If the abnormality type is a vehicle-side preset type, determining the upload strategy to be a first preset upload strategy, wherein the first preset upload strategy is an instant upload strategy for uploading the log file at a preset time; If the abnormality type is not a vehicle-side preset type, the upload strategy is determined to be a second preset upload strategy, wherein the second preset upload strategy is a periodic upload strategy for uploading log files within a preset period.
9. An intelligent cockpit stability problem monitoring device, characterized in that: Applied to the server side, the device comprises: The log acquisition module is used to obtain the vehicle-side log uploaded by the target vehicle; A log screening module, used to screen the vehicle-side logs to obtain a target log set, wherein the target log set includes at least one vehicle-side log corresponding to a type of stability problem; A problem statistics module is used to count the number of errors corresponding to each type of stability problem in the target log set; A level determination module, used to determine the problem level corresponding to each type of stability problem and its corresponding number of error reports; The stability analysis module is used to perform cabin stability analysis on the target vehicle based on the problem level and obtain corresponding analysis results.
10. An intelligent cockpit stability problem monitoring device, characterized in that: Applied to the vehicle end, the device comprises: An event acquisition module is used to acquire abnormal events of a target vehicle; An abnormality determination module, used to respectively determine the vehicle-side log and abnormality type corresponding to the abnormal event; A strategy determination module, used to determine an upload strategy based on the exception type; A log uploading module is used to upload the vehicle-side log to the server-side based on the upload strategy, so that the server-side obtains the vehicle-side log uploaded by the target vehicle; screens the vehicle-side log to obtain a target log set, wherein the target log set contains vehicle-side logs corresponding to at least one type of stability problem; counts the number of errors corresponding to each type of stability problem in the target log set; determines the problem level corresponding to the stability problem based on each type of stability problem and its corresponding number of errors; performs cabin stability analysis on the target vehicle based on the problem level, and obtains corresponding analysis results.
11. An intelligent cockpit stability problem monitoring system, characterized in that: The system includes a server side and a vehicle side, each of which includes a controller, the controller includes a memory and a processor, the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the intelligent cockpit stability problem monitoring method described in any one of claims 1 to 6, or executes the intelligent cockpit stability problem monitoring method described in any one of claims 7 to 8 by executing the computer instructions.
12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the intelligent cockpit stability problem monitoring method described in any one of claims 1 to 6, or to execute the intelligent cockpit stability problem monitoring method described in any one of claims 7 to 8.
