Log extraction method and system

Abstract

The invention provides a log extraction method and system. The method comprises the following steps: acquiring burying point data uploaded by a TBOX, a login state of the TBOX and a current driving state of a vehicle; determining the log extraction opportunity of the TBOX according to the burying point data of the TBOX; according to the log extraction opportunity, the login state and the driving state of the TBOX, whether the TBOX log is extracted or not is determined, and the extraction mode of the TBOX log is determined; and if it is determined that the TBOX log is extracted, extracting the TBOX log according to the burying point data and the extraction mode. According to the method, the extraction of the TBOX log is actively triggered, so that the timeliness and the accuracy of the extraction of the TBOX log are improved, meanwhile, the difficulty of subsequent problem point log analysis is reduced, the time influence on problem solving is reduced, and serious problems caused by problem accumulation are avoided.

Description

Technical Field

[0001] The present invention relates to the field of automotive electronic technology, and more specifically, to a log extraction method and system. Background Art

[0002] With the continuous development of society, the use of automobiles is becoming more and more widespread, and people are paying more and more attention to automobile-related problems and failures.

[0003] In the prior art, when the owner perceives that there is a problem or fault with the vehicle, the corresponding vehicle-mounted telematics box (TBOX) log extraction and problem point analysis instructions are triggered to the car cloud background. When the car cloud background receives the instructions triggered by the owner, it extracts the TBOX internal log and performs the corresponding problem point log analysis. It can be seen that this method will only passively extract the TBOX log and perform problem point log analysis when the owner actually experiences problems. In addition, the space for storing log files in TBOX itself is limited and can only store log files within the last 7-10 days. When the owner perceives that there is a problem or fault with the vehicle, the problem point log file may have been overwritten by the new log file, which increases the difficulty of subsequent problem point log analysis. At the same time, it will also affect the timeliness of solving the problem, which will lead to more serious problems due to the accumulation of problems. Summary of the invention

[0004] In view of this, the present invention provides a log extraction method and system to realize the active triggering of TBOX log extraction, thereby improving the timeliness and accuracy of TBOX log extraction, while reducing the difficulty of subsequent problem point log analysis, reducing the timeliness affecting problem solving, and avoiding serious problems caused by accumulation of problems.

[0005] A first aspect of the present invention provides a log extraction method, the method comprising:

[0006] Obtain the buried point data uploaded by TBOX, the login status of the TBOX and the current driving status of the vehicle;

[0007] Determine the log extraction timing of the TBOX according to the buried data of the TBOX;

[0008] Determining whether to extract the TBOX log and the method of extracting the TBOX log according to the TBOX log extraction timing, the login status and the driving status;

[0009] If it is determined to extract the TBOX log, the TBOX log is extracted according to the buried data and the extraction method.

[0010] Optionally, the buried point data includes a buried point data fault level and a buried point data fault type;

[0011] Determining the log extraction timing of the TBOX according to the buried data of the TBOX includes:

[0012] Determine, from each pre-set log extraction opportunity, a target log extraction opportunity that matches the buried point data fault level and the buried point data fault type;

[0013] The target log extraction timing is determined as the log extraction timing of the TBOX.

[0014] Optionally, the pre-set log extraction timings include immediate extraction, delayed extraction, and no extraction required;

[0015] Determining a target log extraction timing that matches the buried data fault level and the buried data fault type from various pre-set log extraction timings includes:

[0016] If the buried data failure type is a system resource type and the buried data failure level is within a first preset level range, or the buried data failure type is a link status type and the buried data failure level is within a second preset level range, or the buried data failure type is a service status type and the buried data failure level is a first target level, the immediate extraction is determined as the target log extraction timing;

[0017] If the buried data failure type is the system resource type and the buried data failure level is the second target level, or the buried data failure type is the device information type and the buried data failure level is within the third preset level range, or the buried data failure type is the link status type and the buried data failure level is within the fourth preset level range, or the buried data failure type is the service status type and the buried data failure level is within the fifth preset level range, the deferred extraction is determined as the target log extraction timing;

[0018] If the buried data fault type is a system resource type, a device information type, a link status type, or a service status type, and the buried data fault level is the third target level, the time when no extraction is required is determined as the target log extraction time.

[0019] Optionally, the acquiring of the buried data uploaded by the TBOX, the login status of the TBOX and the current driving status of the vehicle includes:

[0020] Acquire the buried point data uploaded by TBOX and the current driving state of the vehicle through the TLS link pre-established with TBOX; wherein the driving state is the parking state, the driving state, or the engine-off state;

[0021] Real-time detection of whether the heartbeat data sent by the TBOX is received within a preset time through the TLS link;

[0022] If the heartbeat data sent by the TBOX is received within the preset time, determining that the login state of the TBOX is the logged-in state;

[0023] If the heartbeat data sent by the TBOX is not received within the preset time, it is determined that the login state of the TBOX is the logout state.

[0024] Optionally, determining whether to extract the TBOX log and the method for extracting the TBOX log according to the TBOX log extraction timing, the login status and the driving status includes:

[0025] If the login status is the logged-in status and the TBOX log extraction timing is immediate extraction, determine to extract the TBOX log, and determine that the TBOX log extraction method is remote extraction;

[0026] If the login state is the login state and the log extraction timing of the TBOX is the delayed extraction, determining whether the driving state is the engine-off state;

[0027] If the driving state is the engine-off state, determining to extract the TBOX log, and determining that the extraction method of the TBOX log is remote extraction;

[0028] If the login state is the logout state and the log extraction timing of the TBOX is immediate extraction, determining whether the driving state is the driving state;

[0029] If the driving state is the driving state, it is determined to extract the TBOX log, and it is determined that the method for extracting the TBOX log is on-site extraction.

[0030] Optionally, the method further includes:

[0031] If the driving state is not the engine-off state, determining not to extract the TBOX log;

[0032] If the driving state is not the driving state, detecting whether the login state is switched to the login state;

[0033] If it is detected that the login state is switched to the login state, it is determined to extract the TBOX log, and it is determined that the extraction method of the TBOX log is remote extraction.

[0034] A second aspect of the present invention provides a log extraction system, the system comprising:

[0035] An acquisition unit, used to acquire the buried point data uploaded by the TBOX, the login status of the TBOX and the current driving status of the vehicle;

[0036] A determination unit, configured to determine a log extraction timing of the TBOX according to the buried data of the TBOX;

[0037] A judgment unit, used to determine whether to extract the TBOX log and a method for extracting the TBOX log according to the TBOX log extraction timing, the login status and the driving status;

[0038] The extraction unit is used to extract the TBOX log according to the embedded data and the extraction method if it is determined to extract the TBOX log.

[0039] Optionally, the buried data includes a buried data fault level and a buried data fault type, and the determining unit includes:

[0040] A first determining unit is used to determine a target log extraction timing that matches the buried point data fault level and the buried point data fault type from various preset log extraction timings;

[0041] The second determining unit is configured to determine the target log extraction timing as the log extraction timing of the TBOX.

[0042] Optionally, the preset log extraction timings include immediate extraction, deferred extraction, and no extraction required, and the first determination unit includes:

[0043] A third determination unit is used to determine the immediate extraction as the target log extraction timing if the buried data failure type is a system resource type and the buried data failure level is within a first preset level range, or the buried data failure type is a link status type and the buried data failure level is within a second preset level range, or the buried data failure type is a service status type and the buried data failure level is a first target level;

[0044] A fourth determination unit is used to determine the postponed extraction as the target log extraction timing if the buried data failure type is the system resource type and the buried data failure level is the second target level, or the buried data failure type is the device information type and the buried data failure level is within the third preset level range, or the buried data failure type is the link status type and the buried data failure level is within the fourth preset level range, or the buried data failure type is the service status type and the buried data failure level is within the fifth preset level range;

[0045] The fifth determination unit is used to determine the target log extraction timing when no extraction is required if the embedded data fault type is a system resource type, a device information type, a link status type, or a service status type, and the embedded data fault level is a third target level.

[0046] Optionally, the acquisition unit includes:

[0047] The acquisition subunit is used to acquire the buried point data uploaded by TBOX and the current driving state of the vehicle through the TLS link pre-established with TBOX; wherein the driving state is the parking state, the driving state, or the engine-off state;

[0048] A real-time detection unit, used for detecting in real time through the TLS link whether the heartbeat data sent by the TBOX is received within a preset time;

[0049] A sixth determining unit, configured to determine that the login state of the TBOX is a logged-in state if the heartbeat data sent by the TBOX is received within the preset time;

[0050] The seventh determining unit is configured to determine that the login state of the TBOX is the logout state if the heartbeat data sent by the TBOX is not received within the preset time.

[0051] The embodiment of the present invention provides a log extraction method, which extracts the buried data uploaded by TBOX, the login status of the TBOX and the current driving status of the vehicle, so as to determine the log extraction timing of the TBOX according to the buried data of the TBOX; after determining the log extraction timing of the TBOX, it can be further combined with the login status of the TBOX and the current driving status of the vehicle to determine whether to extract the TBOX log and the extraction method of the TBOX log, so that when it is determined that the TBOX log needs to be extracted, the TBOX log is extracted in time according to the buried data and the extraction method, thereby realizing active triggering of the extraction of the TBOX log, improving the real-time and accuracy of the extracted TBOX log, and further reducing the difficulty of TBOX after-sales problem analysis, while avoiding the situation where the problem point log file is overwritten by the new log file, thereby reducing the difficulty of subsequent problem point log analysis, reducing the timeliness affecting the solution of the problem, and avoiding serious problems caused by the accumulation of problems. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0053] Figure 1 A flow chart of a log extraction method provided by an embodiment of the present invention;

[0054] Figure 2 A structural schematic diagram of a vehicle cloud backend sending a log extraction control instruction to TBOX is provided for an embodiment of the present invention;

[0055] Figure 3 A structural diagram of a log extraction system provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0056] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only 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 ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0057] In this application, relational terms such as first and second, etc. are used only 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 "comprise", "include" 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, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0058] See also Figure 1 , shows a flow chart of a log extraction method provided by an embodiment of the present invention, the log extraction method is applied to the car cloud background, and the log extraction method specifically includes the following steps:

[0059] S101: Acquire the buried point data of TBOX, the login status of TBOX and the current driving status of the vehicle.

[0060] In the specific process of executing step S101, a secure transport layer protocol TLS link can be established in advance between the vehicle cloud background and TBOX, so as to extract the buried data uploaded by TBOX, the current login status of TBOX and the current driving status of the vehicle through the TLS link established in advance with TBOX.

[0061] It should be noted that the current login state of TBOX can be the login state O1 or the logout state O2; the current driving state of the vehicle can be the parking state P1, or the driving state P2, or the ignition-off state P3, which can be determined according to actual conditions and is not limited in this embodiment of the present invention.

[0062] In some embodiments, the buried data uploaded by TBOX may include a buried data fault level and a buried data fault type, which is not limited in this embodiment of the present invention.

[0063] In actual application, the fault level of TBOX's buried data can be 1, 2, 3, 4, 5, etc., where the lower the level number, the higher the degree of TBOX's fault.

[0064] For example, the level 1 buried point data fault level can indicate that the SOC of TBOX has an abnormal restart, that is, a fatal fault has occurred in TBOX. Therefore, the level 1 buried point data fault level can also be expressed as a fatal fault level L1; the level 2 buried point data fault level can indicate that the SOC inside TBOX has a functional defect caused by a software bug, that is, a serious fault has occurred in TBOX. Therefore, the level 2 buried point data fault level can also be expressed as a serious fault level L2; the level 3 buried point data fault level can indicate that TBOX currently has a fault, but the fault severity is moderate. Therefore, the level 3 buried point data fault level can also be expressed as a warning fault level L3; the level 4 buried point data fault level can indicate that TBOX currently has a fault but the fault severity is low. Therefore, the level 4 buried point data fault level can also be expressed as a minor fault level L4; the level 5 buried point data fault level can indicate that TBOX currently has no fault. Therefore, the level 5 buried point data fault level can also be expressed as no fault L5.

[0065] In some embodiments, the buried data failure type can be system resource type T1, or device information type T2, or link status type T3, or service status type T4. The buried data failure type can be set according to actual application, and this embodiment of the present invention is not limited thereto.

[0066] In the embodiment of the present invention, the current login status of TBOX can be determined according to whether the heartbeat data sent by TBOX is received; specifically, whether the heartbeat data sent by TBOX is received within the preset time is detected in real time through the TLS link; if the heartbeat data sent by TBOX is received within the preset time, the login status of TBOX is determined to be the login status; if the heartbeat data sent by TBOX is not received within the preset time, the login status of TBOX is determined to be the logout status. The preset time can be 10 seconds, 15 seconds, etc., and can be set according to actual applications, which is not limited in this embodiment of the present invention.

[0067] It should be noted that when the login status of TBOX is logged in, it can be considered that TBOX is currently connected to the car cloud background; when the login status of TBOX is logged out, it can be considered that TBOX is currently disconnected from the car cloud background.

[0068] In actual application, a TLS link (based on TCP + national encryption SSL) is established between TBOX and the car cloud background. After TBOX establishes the connection with the car cloud background, it is necessary to send a heartbeat packet (a packet of data) to the car cloud background regularly (under normal working conditions: 10s). Therefore, the current connection status of the car cloud and TBOX can be determined based on the reception of the heartbeat packet. For example, if the heartbeat packet sent by TBOX is not received for more than 30s (preset time), it can be considered that the connection between TBOX and the car cloud background is disconnected, that is, TBOX is in a logged out state.

[0069] S102: Determine the log extraction timing of TBOX according to the buried data of TBOX.

[0070] In the specific process of executing step S102, after extracting the buried data uploaded by TBOX, the timing of TBOX log extraction can be determined according to the buried data fault level and buried data fault type in the extracted buried data, so that the timing of extracting TBOX logs can be determined based on the TBOX log extraction timing in the future. There is no need for the car owner to actively trigger the extraction of TBOX logs and problem point log analysis, which can minimize the impact of extracting TBOX logs on the car owner's use of the car, and improve the real-time and accuracy of extracting TBOX logs, thereby reducing the difficulty of TBOX after-sales problem analysis.

[0071] In an embodiment of the present invention, multiple log extraction opportunities can be pre-set, and the buried data fault type and buried data fault level matching each log extraction opportunity can be set, so that after obtaining the buried data uploaded by TBOX, the target log extraction opportunity matching the buried data fault level and the buried data fault type can be further determined from the pre-set log extraction opportunities, and the target log extraction opportunity can be determined as the log extraction opportunity of the TBOX; wherein, multiple log extraction opportunities can include immediate extraction, deferred extraction, and no extraction, etc., which can be set according to actual applications, and are not limited in this embodiment of the present invention.

[0072] In the actual application process, the inventors have found through research that when the buried data fault type is a system resource type, the overall impact on TBOX is greater and the car owner's perception is high, requiring a higher real-time performance in log extraction, that is, when the buried data fault type is a system resource type, the higher the level of the buried data fault level, the faster the timing of extracting TBOX logs is required, so the first preset level range can be pre-set to level 1-3, the second target level can be set to level 4, and the third target level can be set to level 5. Therefore, the log extraction timing corresponding to the buried data fault type being a system resource type and the buried data fault level being level 1 / 2 / 3 can be set to immediate extraction; the log extraction timing corresponding to the buried data fault type being a system resource type and the buried data fault level being level 4 can be set to deferred extraction; the lifting timing corresponding to the buried data fault type being a system resource type and the buried data fault level being level 5 can be set to no extraction required.

[0073] In the case where the buried data fault type is the device information type, it basically does not affect the vehicle function and the owner's perception is low, and the real-time performance of the extracted logs is generally required, such as the third preset level range can be set to level 1-level 4. Therefore, the log extraction timing corresponding to the buried data fault type of the device information type and the buried data fault level of level 1 / level 2 / level 3 / level 4 can be set to postpone extraction; the log extraction timing corresponding to the buried data fault type of the device information type and the buried data fault level of level 5 can be determined as no need for extraction.

[0074] In the case where the buried data fault type is a link status type, multiple ECUs may be involved, and the link that needs to be checked is relatively long. However, the car owner's perception is average, and it may often be that a specific function is abnormal or failed, so the timeliness of log extraction is generally required. Therefore, the second preset level range can be set to level 1-2, and the fourth preset level range can be set to level 3-4. Therefore, the log extraction timing corresponding to the buried data fault type of the link status type and the buried data fault level of level 1 / 2 can be determined as immediate extraction; the log extraction timing corresponding to the buried data fault type of the link status type and the buried data fault level of level 3 / 4 can be determined as deferred extraction; the log extraction timing corresponding to the buried data fault type of the link status type and the buried data fault level of level 5 can be determined as no extraction is required.

[0075] In the case where the buried data fault type is a service status type, it may be related to a specific function, the owner's perception is low, and generally does not affect the vehicle function, so the timeliness of log extraction is required to be low, so the first target level can be set to level 1, and the fifth preset level range can be set to level 2-level 4. Therefore, the log extraction timing corresponding to the buried data fault type of the service status type and the buried data fault level of level 1 can be determined as immediate extraction; the log extraction timing corresponding to the buried data fault type of the service status type and the buried data fault level of level 2 / level 3 / level 4 can be determined as deferred extraction; the physical extraction timing corresponding to the buried data fault type of the service status type and the buried data fault level of level 5 can be determined as no extraction required.

[0076] The above is a preferred method for log extraction timing corresponding to the buried data fault type and the buried data fault level provided in an embodiment of the present invention. Regarding the specific setting method of the log extraction timing corresponding to the buried data fault type and the buried data fault level, the inventor can set it according to actual application, and the embodiment of the present invention is not limited here.

[0077] As a preferred method of an embodiment of the present invention, the process of determining the target log extraction timing that matches the buried data failure level and the buried data failure type from the pre-set log extraction timings can be specifically as follows: if the buried data failure type in the buried data is a system resource type and the buried data failure level is within a first preset level range, or the buried data failure type in the buried data is a link status type and the buried data failure level is within a second preset level range, or the buried data failure type in the buried data is a service status type and the buried data failure level is the first target level, immediate extraction will be determined as the target log extraction timing.

[0078] If the buried data failure type in the buried data is a system resource type and the buried data failure level is the second target level, or the buried data failure type in the buried data is a device information type and the buried data failure level is within the third preset level, or the buried data failure type in the buried data is a link status type and the buried data failure level is within the fourth preset level, or the buried data failure type in the buried data is a service status type and the buried data failure level is within the fifth preset level, the extraction will be postponed as the target log extraction timing.

[0079] If the point-of-care data failure type in the point-of-care data is a system resource type, a device information type, a link status type, or a service status type, and the point-of-care data failure level is the third target level, there is no need to extract and determine the target log extraction timing.

[0080] S103: Determine whether to extract the TBOX log and the method of extracting the TBOX log according to the TBOX log extraction timing, login status and driving status. If it is determined to extract the TBOX log, execute step S104.

[0081] In an embodiment of the present invention, when the login status of TBOX is the logged-in status, it can be considered that TBOX is currently in a connected state with the vehicle cloud backend, that is, it can be considered that the conditions for remote extraction are currently met. At this time, it is only necessary to determine whether the TBOX log needs to be extracted based on the log extraction timing and / or driving status of TBOX; if it is determined that the TBOX log needs to be extracted, the extraction method of the TBOX log can be determined as remote extraction; if it is determined that the TBOX log does not need to be extracted, there is no need to determine the extraction method of the TBOX log.

[0082] It should be noted that, when the login status of TBOX is logged in, if the log extraction method of TBOX is no need to extract, it means that there is currently no need for TBOX logs to perform problem point log analysis, and thus it can be determined that there is currently no need to extract TBOX logs; if the log extraction timing of TBOX is immediate extraction, it means that there is currently an urgent need for TBOX logs to perform subsequent problem point log analysis, and thus it can be determined that there is currently a need to extract TBOX logs; if the log extraction timing of TBOX is deferred extraction, but the driving status is the engine-off status, it is still considered that there is currently an urgent need for TBOX logs to perform subsequent problem point log analysis, and thus it can be determined that there is currently a need to extract TBOX logs.

[0083] For example, when the login state of TBOX is the logged-in state, the relationship of determining whether to extract the TBOX log according to the TBOX log extraction timing and / or the driving state of the vehicle is shown in Table 1:

[0084] Table 1:

[0085] Parking status P1 Driving status P2 Flame-out state P3 Withdraw Q1 now extract extract extract Delayed withdrawal Q2 No extraction No extraction extract No need to extract Q3 No extraction No extraction No extraction

[0086] In an embodiment of the present invention, when the login status of TBOX is the logged-out status, it can be considered that TBOX is currently disconnected from the vehicle cloud backend, that is, it can be considered that there is no specific condition for remote extraction at present. At this time, it is necessary not only to judge whether the TBOX log needs to be extracted based on the log extraction timing of TBOX, but also to judge whether the conditions for on-site extraction of TBOX logs are met based on the driving status; if it is determined that the TBOX log needs to be extracted and the conditions for on-site extraction of the TBOX log are met, on-site extraction can be used as the extraction method for the TBOX log.

[0087] It should be noted that, when the login status of TBOX is logged out, if the timing of TBOX log extraction is no need to extract, it can be considered that there is no need for TBOX log to analyze the problem log at present, and it can be determined that there is no need to extract TBOX log at present. If the timing of TBOX log extraction is delayed extraction, when the TBOX login status is switched from logged out to logged in, and the vehicle is in the off state, it can be considered that it is currently suitable to extract TBOX log for problem context analysis and problem point tracing, and it can be determined to extract TBOX log, and determine that the extraction method of the TBOX log is remote extraction. If the timing of TBOX log extraction is immediate extraction, it means that there is an urgent problem at this time, but the TBOX login status is logged out, and the TBOX log cannot be obtained by remote extraction. Therefore, the vehicle after-sales service needs to remind the owner to go to the vehicle after-sales service center to deal with the vehicle problem through SMS or phone. If the owner cannot go to the after-sales service center in time, the TBOX log extraction instruction should be issued immediately at the time when the TBOX login status is switched from logged out to logged in, and the log should be extracted in time for subsequent problem analysis.

[0088] For example, when the login state of TBOX is the logout state, the relationship of determining whether to extract the TBOX log according to the TBOX log extraction timing and / or the driving state of the vehicle is shown in Table 2:

[0089] Table 2:

[0090] Parking status P1 Driving status P2 Flame-out state P3 Withdraw Q1 now extract extract extract Delayed withdrawal Q2 No extraction No extraction extract No need to extract Q3 No extraction No extraction No extraction

[0091] To sum up, optionally, according to the log extraction timing, login status and driving status of TBOX, determining whether to extract TBOX logs and the extraction method of TBOX logs can be specifically as follows: if the login status is the login status and the log extraction timing of TBOX is immediate extraction, determining to extract TBOX logs, and determining the extraction method of TBOX logs to be remote extraction; if the login status is the login status and the log extraction timing of TBOX is deferred extraction, determining whether the driving status is the engine-off status; if the driving status is the engine-off status, determining to extract TBOX logs, and determining the extraction method of TBOX logs to be remote extraction; if the driving status is not the engine-off status, determining not to extract TBOX logs; if the login status is the logout status and the log extraction timing of TBOX is immediate extraction, determining the driving status whether the driving state is the driving state; if the driving state is the driving state, it is determined to extract the TBOX log, and the method for extracting the TBOX log is determined to be on-site extraction; if the driving state is not the driving state, it is detected whether the login state is switched to the login state; if it is detected that the login state is switched to the login state, it is determined to extract the TBOX log, and the method for extracting the TBOX log is determined to be remote extraction; if the login state is the login state and the TBOX log extraction timing is delayed extraction, it is determined whether the driving state is the engine-off state, and whether the login state is switched to the login state; if the driving state is the engine-off state and the login state is switched to the login state, it is determined to extract the TBOX log, and the method for extracting the TBOX log is determined to be remote extraction; if the TBOX log extraction timing is no need to extract, it is determined not to extract the TBOX log.

[0092] S104: extracting TBOX logs according to the embedded data and the extraction method.

[0093] In the specific execution process of step S104, after determining that the TBOX log needs to be extracted and the corresponding extraction method, it can be further determined whether the extraction method is remote extraction; if it is remote extraction, a corresponding log extraction control instruction can be generated according to the buried data fault type in the buried data, and the log extraction control instruction can be sent to TBOX, so that TBOX can extract and feedback the TBOX log corresponding to the buried data fault type in the log extraction control instruction, such as Figure 2 shown.

[0094] If the extraction method is not remote extraction, it can be determined that the extraction method is on-site extraction, and corresponding prompt information can be generated according to the buried data failure type in the buried data, and the corresponding prompt information can be output to prompt the user to enter the corresponding after-sales store offline to extract the TBOX log corresponding to the buried data failure type in the prompt information.

[0095] In summary, compared with the traditional separate point-of-care data reporting function and the separate remote extraction of TBOX log function, the present invention directly extracts the corresponding TBOX log remotely when TBOX is connected to the car cloud backend. When TBOX is disconnected from the car cloud backend, the user can also be notified to go to the corresponding after-sales store to extract the corresponding TBOX log. That is, the present invention integrates point-of-care and remote extraction of TBOX logs, without manual intervention, and can reduce operation and maintenance costs to a certain extent.

[0096] The embodiment of the present invention provides a log extraction method, which extracts the buried data uploaded by TBOX, the login status of TBOX and the current driving status of the vehicle, so as to determine the log extraction timing of TBOX according to the buried data of TBOX, without the need for the vehicle owner to actively trigger, thereby improving the real-time and accuracy of extracting TBOX logs, thereby reducing the difficulty of TBOX after-sales problem analysis; after determining the log extraction timing of TBOX, it can be further combined with the login status of TBOX and the current driving status of the vehicle to determine whether to extract the TBOX log and the extraction method of the TBOX log, so that when it is determined that the TBOX log needs to be extracted, the TBOX log is extracted in time according to the buried data and the extraction method, avoiding the situation where the problem point log file is overwritten by the new log file, thereby reducing the difficulty of subsequent problem point log analysis, thereby reducing the timeliness affecting the solution of the problem, and avoiding serious problems caused by the accumulation of problems.

[0097] Based on the log extraction method provided by the above embodiment of the present invention, the embodiment of the present invention also provides a log extraction system, such as Figure 3 As shown, the system is used for the car cloud background, and the log extraction includes:

[0098] The acquisition unit 31 is used to acquire the buried point data uploaded by the TBOX, the login status of the TBOX and the current driving status of the vehicle;

[0099] A determination unit 32, configured to determine a log extraction timing of the TBOX according to the buried point data of the TBOX;

[0100] The judgment unit 33 is used to determine whether to extract the TBOX log and the method of extracting the TBOX log according to the TBOX log extraction timing, login status and driving status;

[0101] The extraction unit 34 is used to extract the TBOX log according to the embedded data and the extraction method if it is determined to extract the TBOX log.

[0102] The specific principles and execution processes of each unit in the log extraction system disclosed in the above embodiment of the present invention are the same as the log extraction protection method disclosed in the above embodiment of the present invention. Please refer to the corresponding parts of the log extraction protection method disclosed in the above embodiment of the present invention, and no further details will be given here.

[0103] The embodiment of the present invention provides a log extraction system, which extracts the buried data uploaded by TBOX, the login status of TBOX and the current driving status of the vehicle, so as to determine the log extraction timing of TBOX according to the buried data of TBOX; after determining the log extraction timing of TBOX, it can further combine the login status of TBOX and the current driving status of the vehicle to determine whether to extract the TBOX log and the extraction method of the TBOX log, so that when it is determined that the TBOX log needs to be extracted, the TBOX log is extracted in time according to the buried data and the extraction method, thereby realizing active triggering of the extraction of the TBOX log, improving the real-time and accuracy of the extracted TBOX log, and further reducing the difficulty of TBOX after-sales problem analysis, while avoiding the situation that the problem point log file is overwritten by the new log file, thereby reducing the difficulty of subsequent problem point log analysis, reducing the timeliness affecting the solution of the problem, and avoiding serious problems caused by the accumulation of problems.

[0104] Optionally, the buried data includes a buried data fault level and a buried data fault type, and the determination unit includes:

[0105] A first determining unit is used to determine a target log extraction timing that matches the buried point data fault level and the buried point data fault type from various preset log extraction timings;

[0106] The second determining unit is used to determine the target log extraction timing as the log extraction timing of the TBOX.

[0107] Optionally, the preset log extraction timings include immediate extraction, deferred extraction, and no extraction required, and the first determination unit includes:

[0108] A third determination unit is used to determine immediate extraction as the target log extraction opportunity if the buried data failure type is a system resource type and the buried data failure level is within a first preset level range, or the buried data failure type is a link status type and the buried data failure level is within a second preset level range, or the buried data failure type is a service status type and the buried data failure level is a first target level;

[0109] A fourth determination unit is used to determine the delayed extraction as the target log extraction timing if the buried data failure type is a system resource type and the buried data failure level is a second target level, or the buried data failure type is a device information type and the buried data failure level is within a third preset level range, or the buried data failure type is a link status type and the buried data failure level is within a fourth preset level range, or the buried data failure type is a service status type and the buried data failure level is within a fifth preset level range;

[0110] The fifth determination unit is used to determine the target log extraction timing without extraction if the buried data failure type is a system resource type, a device information type, a link status type, or a service status type, and the buried data failure level is the third target level.

[0111] Optionally, obtain the unit, including:

[0112] The acquisition subunit is used to acquire the buried point data uploaded by TBOX and the current driving state of the vehicle through the TLS link pre-established with TBOX; wherein the driving state is the parking state, the driving state, or the engine-off state;

[0113] The first detection unit is used to detect in real time through the TLS link whether the heartbeat data sent by the TBOX is received within a preset time;

[0114] A sixth determining unit, configured to determine that the login state of the TBOX is a logged-in state if the heartbeat data sent by the TBOX is received within a preset time;

[0115] The seventh determining unit is configured to determine that the login state of the TBOX is the logout state if the heartbeat data sent by the TBOX is not received within a preset time.

[0116] Optionally, the judging unit comprises:

[0117] an eighth determining unit, for determining to extract the TBOX logs if the login state is the login state and the TBOX log extraction timing is immediate extraction, and determining the TBOX log extraction method as remote extraction;

[0118] a ninth determination unit, configured to determine whether the driving state is an engine-off state if the login state is a login state and the log extraction timing of the TBOX is a delayed extraction;

[0119] a tenth determining unit, configured to determine to extract the TBOX log if the driving state is the engine-off state, and to determine that the extraction method of the TBOX log is remote extraction;

[0120] an eleventh determination unit, for determining whether the driving state is a driving state if the login state is a logout state and the log extraction timing of the TBOX is an immediate extraction;

[0121] The twelfth determining unit is used for determining to extract the TBOX log if the driving state is the driving state, and determining that the method for extracting the TBOX log is on-site extraction.

[0122] Optionally, the log extraction system provided by the embodiment of the present invention further includes:

[0123] A third determination unit, configured to determine not to extract the TBOX log if the driving state is not the engine-off state;

[0124] The second detection unit is used to detect whether the login state is switched to the login state if the driving state is not the driving state;

[0125] The fourteenth determining unit is used to determine to extract the TBOX log if it is detected that the login state is switched to the login state, and to determine that the extraction method of the TBOX log is remote extraction.

[0126] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system or system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, in which the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0127] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may 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 the present invention.

[0128] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

[0129] The above are only preferred embodiments of the present invention. It should be pointed out that, for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A log extraction method, characterized in that: The method comprises: Obtain the buried point data uploaded by TBOX, the login status of the TBOX and the current driving status of the vehicle; Determine the log extraction timing of the TBOX according to the buried data of the TBOX; Determining whether to extract the TBOX log and the method of extracting the TBOX log according to the TBOX log extraction timing, the login status and the driving status; If it is determined to extract the TBOX log, the TBOX log is extracted according to the buried data and the extraction method.

2. The method according to claim 1, characterized in that The buried point data includes a buried point data fault level and a buried point data fault type; Determining the log extraction timing of the TBOX according to the buried data of the TBOX includes: Determine, from each pre-set log extraction opportunity, a target log extraction opportunity that matches the buried point data fault level and the buried point data fault type; The target log extraction timing is determined as the log extraction timing of the TBOX.

3. The method according to claim 2, characterized in that The pre-set log extraction timings include immediate extraction, delayed extraction, and no extraction required; Determining a target log extraction timing that matches the buried data fault level and the buried data fault type from various pre-set log extraction timings includes: If the buried data failure type is a system resource type and the buried data failure level is within a first preset level range, or the buried data failure type is a link status type and the buried data failure level is within a second preset level range, or the buried data failure type is a service status type and the buried data failure level is a first target level, the immediate extraction is determined as the target log extraction timing; If the buried data failure type is the system resource type and the buried data failure level is the second target level, or the buried data failure type is the device information type and the buried data failure level is within the third preset level range, or the buried data failure type is the link status type and the buried data failure level is within the fourth preset level range, or the buried data failure type is the service status type and the buried data failure level is within the fifth preset level range, the deferred extraction is determined as the target log extraction timing; If the buried data fault type is a system resource type, a device information type, a link status type, or a service status type, and the buried data fault level is the third target level, the time when no extraction is required is determined as the target log extraction time.

4. The method according to claim 1, characterized in that: The step of obtaining the buried point data uploaded by the TBOX, the login status of the TBOX and the current driving status of the vehicle includes: Acquire the buried point data uploaded by TBOX and the current driving state of the vehicle through the TLS link pre-established with TBOX; wherein the driving state is the parking state, the driving state, or the engine-off state; Real-time detection of whether the heartbeat data sent by the TBOX is received within a preset time through the TLS link; If the heartbeat data sent by the TBOX is received within the preset time, determining that the login state of the TBOX is the logged-in state; If the heartbeat data sent by the TBOX is not received within the preset time, it is determined that the login state of the TBOX is the logout state.

5. The method according to claim 4, characterized in that According to the TBOX log extraction timing, the login status and the driving status, determining whether to extract the TBOX log and the TBOX log extraction method include: If the login status is the logged-in status and the TBOX log extraction timing is immediate extraction, determine to extract the TBOX log, and determine that the TBOX log extraction method is remote extraction; If the login state is the login state and the log extraction timing of the TBOX is the delayed extraction, determining whether the driving state is the engine-off state; If the driving state is the engine-off state, determining to extract the TBOX log, and determining that the extraction method of the TBOX log is remote extraction; If the login state is the logout state and the log extraction timing of the TBOX is immediate extraction, determining whether the driving state is the driving state; If the driving state is the driving state, it is determined to extract the TBOX log, and it is determined that the method for extracting the TBOX log is on-site extraction.

6. The method according to claim 5, characterized in that The method further comprises: If the driving state is not the engine-off state, determining not to extract the TBOX log; If the driving state is not the driving state, detecting whether the login state is switched to the login state; If it is detected that the login state is switched to the login state, it is determined to extract the TBOX log, and it is determined that the extraction method of the TBOX log is remote extraction.

7. A log extraction system, characterized in that: The system comprises: An acquisition unit, used to acquire the buried point data uploaded by the TBOX, the login status of the TBOX and the current driving status of the vehicle; A determination unit, configured to determine a log extraction timing of the TBOX according to the buried data of the TBOX; A judgment unit, used to determine whether to extract the TBOX log and a method for extracting the TBOX log according to the TBOX log extraction timing, the login status and the driving status; The extraction unit is used to extract the TBOX log according to the embedded data and the extraction method if it is determined to extract the TBOX log.

8. The system according to claim 7, characterized in that The buried point data includes a buried point data fault level and a buried point data fault type, and the determining unit includes: A first determining unit is used to determine a target log extraction timing that matches the buried point data fault level and the buried point data fault type from various preset log extraction timings; The second determining unit is configured to determine the target log extraction timing as the log extraction timing of the TBOX.

9. The system according to claim 8, characterized in that The preset log extraction timings include immediate extraction, deferred extraction, and no extraction required. The first determination unit includes: A third determination unit is used to determine the immediate extraction as the target log extraction timing if the buried data failure type is a system resource type and the buried data failure level is within a first preset level range, or the buried data failure type is a link status type and the buried data failure level is within a second preset level range, or the buried data failure type is a service status type and the buried data failure level is a first target level; A fourth determination unit is used to determine the postponed extraction as the target log extraction timing if the buried data failure type is the system resource type and the buried data failure level is the second target level, or the buried data failure type is the device information type and the buried data failure level is within the third preset level range, or the buried data failure type is the link status type and the buried data failure level is within the fourth preset level range, or the buried data failure type is the service status type and the buried data failure level is within the fifth preset level range; The fifth determination unit is used to determine the target log extraction timing when no extraction is required if the embedded data fault type is a system resource type, a device information type, a link status type, or a service status type, and the embedded data fault level is a third target level.

10. The system according to claim 7, characterized in that The acquisition unit comprises: The acquisition subunit is used to acquire the buried point data uploaded by TBOX and the current driving state of the vehicle through the TLS link pre-established with TBOX; wherein the driving state is the parking state, the driving state, or the engine-off state; A first detection unit, configured to detect in real time through the TLS link whether the heartbeat data sent by the TBOX is received within a preset time; A sixth determining unit, configured to determine that the login state of the TBOX is a logged-in state if the heartbeat data sent by the TBOX is received within the preset time; The seventh determining unit is configured to determine that the login state of the TBOX is the logout state if the heartbeat data sent by the TBOX is not received within the preset time.

Images