Vehicle trip processing method and vehicle

Abstract

The application discloses a vehicle trip processing method and a vehicle, and relates to the technical field of vehicle control. The vehicle trip processing method comprises the following steps: in the case that driving data is not received on the vehicle within a first preset time, acquiring a first power-on condition of the vehicle before the first preset time and a second power-on condition of the vehicle after the first preset time; determining that the vehicle has an abnormal driving trip based on the first power-on condition and / or the second power-on condition; and processing two adjacent trips based on the abnormal driving trip and a current recorded driving duration of the vehicle. The method can effectively avoid the problems of trip missegmentation or incorrect merging caused by unreliable network, thereby improving the accuracy and integrity of the trip data.

Description

Technical Field

[0001] This application relates to the field of vehicle control technology, and in particular to a vehicle trip processing method and a vehicle. Background Technology

[0002] With the development of vehicle connectivity, vehicles continuously report driving-related data (location, speed, engine / ignition status, system power mode, etc.) to the cloud through onboard terminals (such as in-vehicle infotainment systems). Under stable network conditions, the reported data can be accurately segmented according to ignition status, timestamps, etc.

[0003] However, in unreliable network / latency / packet loss scenarios, data on vehicles in motion may not be reported for a long time or may be reported late, which may cause the server to misjudge the trip as ending / starting, resulting in the trip being incorrectly segmented (missegmented) or incorrectly merged, affecting downstream indicators and statistical results such as mileage and duration, and consequently affecting business decisions such as driving behavior analysis. Summary of the Invention

[0004] This application aims to at least partially address one of the technical problems in related technologies. To this end, the first objective of this application is to propose a vehicle trip processing method. By comprehensively analyzing multi-dimensional data reported by vehicles, when data gaps, time jumps, or abnormal states are detected at the start or end time of a trip, an abnormal trip identification mechanism is automatically triggered. For example, if there is a apparent jump between the end time of an abnormal trip and the start time of a subsequent trip, but the recorded vehicle driving time does not show any stationary or engine-off time that meets the trip end criteria, then these two trips are determined to belong to the same complete trip, and merging is performed. Conversely, if the currently recorded vehicle driving time indicates a significant interruption in the actual driving process of two trips, such as a shorter driving time, the two trips can be determined to be independent trips and not merged, thus avoiding erroneous merging. This effectively avoids trip missegmentation or erroneous merging caused by unreliable networks, thereby improving the accuracy and completeness of trip data.

[0005] The second objective of this application is to propose a vehicle.

[0006] To achieve the above objectives, a first aspect of this application proposes a vehicle trip processing method, the method comprising: if no vehicle-uploaded driving data is received within a first preset time, acquiring a first power-on status of the vehicle before the first preset time and a second power-on status of the vehicle after the first preset time; determining that the vehicle has an abnormal driving trip based on the first power-on status and / or the second power-on status; and processing two adjacent trip segments based on the abnormal driving trip and the currently recorded driving time of the vehicle.

[0007] According to the vehicle trip processing method of this application embodiment, if no vehicle-uploaded driving data is received within a first preset time, the method acquires the vehicle's first power-on status before the first preset time and the vehicle's second power-on status after the first preset time. Based on the first power-on status and / or the second power-on status, it determines that the vehicle has an abnormal driving trip. Then, it processes two adjacent trip segments based on the abnormal driving trip and the vehicle's currently recorded driving duration. Therefore, this method can effectively avoid trip mis-segmentation or incorrect merging caused by network unreliability, thereby improving the accuracy and completeness of trip data.

[0008] In addition, the vehicle trip processing method according to the above embodiments of this application may also have the following additional technical features: According to one embodiment of this application, determining that the vehicle has an abnormal driving trip based on the first power-on condition and / or the second power-on condition includes: obtaining a flag bit of the vehicle's power mode before and after the first preset time; determining that the vehicle is in a power-on state when the flag bit is a first preset flag bit; determining that the vehicle's current trip is an abnormally ended driving trip when the first power-on condition is the power-on state; and / or determining that the vehicle's current trip is an abnormally started driving trip when the second power-on condition is the power-on state.

[0009] According to one embodiment of this application, the processing of two adjacent trip segments based on the abnormal travel distance and the travel duration includes: when the previous trip of the vehicle ended normally and the current trip of the vehicle started abnormally, the current trip and the previous trip are not merged; when the current trip of the vehicle ended abnormally and the next trip of the vehicle started normally, the current trip and the next trip are not merged.

[0010] According to one embodiment of this application, the processing of two adjacent trip segments based on the abnormal travel route and the travel duration includes: when the current trip of the vehicle is the abnormally ended trip and the next trip of the vehicle is the abnormally started trip, obtaining a first interval duration between the abnormally ended trip and the abnormally started trip; and processing the two adjacent trip segments based on the first interval duration and the travel duration.

[0011] According to one embodiment of this application, the processing of two adjacent trip segments based on the first interval duration and the travel duration includes: when the first interval duration is within a preset time interval range and the travel duration is less than or equal to the first interval duration, the current trip segment and the next trip segment are not merged.

[0012] According to one embodiment of this application, the processing of two adjacent trip segments based on the first interval duration and the travel duration includes: merging the current trip segment with the next trip segment when the first interval duration is within the preset time interval range and the travel duration is greater than the first interval duration.

[0013] According to one embodiment of this application, the method further includes: when the first interval duration is greater than the upper limit of the preset time interval range, performing non-merging processing on the current trip and the next trip segment.

[0014] According to one embodiment of this application, the method further includes: when the flag bit changes from the first preset flag bit to the second preset flag bit, determining that the current trip of the vehicle is a normal end of the trip; when the flag bit changes from the second preset flag bit to the first preset flag bit, determining that the current trip of the vehicle is a normal start of the trip, wherein when the flag bit is the second preset flag bit, determining that the vehicle is in a power-off state.

[0015] According to one embodiment of this application, the method further includes: obtaining a second interval duration between the previous normally ended driving trip and the current normally started driving trip; if the second interval duration is greater than or equal to a preset interval duration threshold, performing non-merging processing on the current trip and the previous trip; if the second interval duration is less than the preset interval duration threshold, performing merging processing on the current trip and the previous trip.

[0016] To achieve the above objectives, a vehicle is provided in a second aspect of this application, including a memory, a processor, and a program stored in the memory and executable on the processor. When the processor executes the program, it implements the above-described vehicle trip processing method.

[0017] According to the embodiments of this application, by executing the above-described vehicle trip processing method, the vehicle can effectively avoid trip missegmentation or erroneous merging caused by network unreliability, thereby improving the accuracy and completeness of trip data.

[0018] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0019] Figure 1 This is a flowchart of a vehicle trip processing method according to an embodiment of this application.

[0020] Figure 2 This is a flowchart of a vehicle trip processing method according to an embodiment of this application.

[0021] Figure 3 This is a schematic diagram of the vehicle's travel distance according to an embodiment of this application.

[0022] Figure 4 This is a flowchart of a vehicle trip processing method according to another embodiment of this application.

[0023] Figure 5 This is a flowchart illustrating a specific example of a vehicle trip processing method according to this application.

[0024] Figure 6 This is a block diagram of a vehicle according to an embodiment of this application. Detailed Implementation

[0025] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0026] The vehicle trip processing method and vehicle proposed in this application are described below with reference to the accompanying drawings.

[0027] Figure 1 This is a flowchart of a vehicle trip processing method according to an embodiment of this application.

[0028] like Figure 1 As shown, the vehicle trip processing method of this application embodiment may include the following steps: S1, if no vehicle-uploaded driving data is received within a first preset time, obtain the vehicle's first power-on status before the first preset time and the vehicle's second power-on status after the first preset time. The first preset time can be determined based on actual circumstances.

[0029] Specifically, during vehicle operation, the vehicle-mounted terminal continuously reports driving-related data to the cloud server. This data can include various driving-related parameters such as the vehicle's real-time location, speed, acceleration, battery level, and engine operating status. The cloud server stores and analyzes the received vehicle-mounted data in real time to monitor and manage the vehicle's journey status throughout the entire trip. For example, the journey can be accurately segmented based on engine operating status. When the vehicle switches from an off state to an on state, the engine operating status changes from stopped to started, and this moment can be taken as the starting point of a new journey. Conversely, when the vehicle switches from an on state to an off state, the engine operating status changes from started to stopped, and this moment is taken as the ending point of the current journey. By using this method based on changes in engine operating status, the boundaries of the journey can be accurately captured, avoiding missegmentation of the journey due to short-term stops (such as waiting at red lights or temporary stops), and ensuring the integrity and independence of each journey.

[0030] The first preset time can be flexibly set according to the actual application scenario, such as 5 minutes or 10 minutes. Its main function is to determine whether the vehicle is in an abnormal state of not uploading data. If the cloud server does not receive any of the aforementioned driving data from the vehicle within this set first preset time, it indicates that the vehicle may have experienced data transmission interruption due to network issues, equipment malfunction, or other special reasons. This allows the system to obtain the vehicle's first power-on status before the first preset time and the vehicle's second power-on status after the first preset time.

[0031] The first power-on condition refers to the most recent vehicle power-on record before the start of the first preset time, while the second power-on condition refers to the first vehicle power-on record after the end of the first preset time. This can be achieved, for example, by monitoring the vehicle's ignition signal or power mode field. If the vehicle has already been powered on and started driving before the start of the first preset time, this status will be recorded; if the vehicle is found to be powered on after the first preset time, this status will also be recorded. All recorded data (including power-on conditions and any successfully reported driving data) is synchronized and stored in the vehicle's local storage, and uploaded to a cloud database when a network connection is available. This power-on data is crucial for detecting and processing abnormal driving trips in subsequent steps; that is, it provides direct evidence of whether the vehicle was in motion during a specific time period.

[0032] S2, based on the first power-on condition and / or the second power-on condition, determine that the vehicle has an abnormal driving trip.

[0033] Specifically, after obtaining the first power-on condition, it can be determined whether the vehicle has engaged in abnormal driving. After obtaining the second power-on condition, it can be determined whether the vehicle is engaged in abnormal driving. After obtaining both the second and second power-on conditions, it can also be determined whether the vehicle has engaged in abnormal driving based on both the first and second power-on conditions.

[0034] For example, if the first power-on condition shows that the vehicle was powered on and driving before the start of the first preset time, the trip is determined to be abnormal. For instance, if the vehicle is driving normally on a road with network access and enters a tunnel within the first preset time, the onboard terminal cannot report driving data to the cloud in real time, thus confirming the trip is abnormal; the cloud has experienced a change from normally obtaining vehicle data to not obtaining data. Similarly, if the second power-on condition shows that the vehicle was powered on and driving after the first preset time, the trip is determined to be abnormal. For instance, if the vehicle is driving in a tunnel without network access for the entire first preset time, and then leaves the tunnel after the first preset time, the cloud server can normally obtain the vehicle's power-on status, thus confirming the trip is abnormal; the cloud has experienced a change from not obtaining vehicle data to normally obtaining data. Furthermore, if the vehicle's power-on status can be obtained from before entering the tunnel to after exiting the tunnel, and it remains in the tunnel for the first preset time, the cloud has experienced a change from obtaining vehicle driving data to not obtaining driving data and then obtaining driving data again, thus confirming the trip is abnormal.

[0035] This refers to situations where, due to network issues or other reasons, the vehicle's actual driving data fails to be reported to the cloud in a timely or accurate manner. By analyzing the vehicle's power-on status, potential abnormal driving trips can be identified, which is crucial for subsequent trip processing and data correction.

[0036] S3 processes two adjacent trip segments based on the abnormal trip and the vehicle's currently recorded travel time.

[0037] Specifically, after identifying abnormal driving trips, adjacent trip segments can be processed based on the abnormal trip segment and the vehicle's currently recorded driving time. The vehicle's currently recorded driving time refers to the actual length of time the vehicle travels during this trip, which is recorded and stored in real-time by the onboard terminal based on the vehicle's driving status (such as speed, engine running status, etc.). For example, if the vehicle has accumulated 45 minutes of driving from startup to the current moment, then the vehicle's currently recorded driving time is 45 minutes. If the vehicle is currently started, then turned off, and then restarted and driven for 30 minutes, then the vehicle's currently recorded driving time is 30 minutes. Trip processing can include merging adjacent trips or not merging them. Merging means treating two adjacent trips as a single continuous trip, while not merging means treating two adjacent trips as independent trips.

[0038] When processing two adjacent trip segments, the current abnormal trip can be considered in conjunction with the vehicle's currently recorded driving time. For example, if both adjacent trip segments are abnormal, the current driving time and the time interval between the two abnormal trip segments can be used to determine the duration. If the driving time is longer than the time interval, it indicates a strong continuity between the two abnormal trip segments, suggesting the vehicle may be in a continuous abnormal driving state. In this case, the two adjacent abnormal trip segments can be merged to more accurately reflect the overall abnormal driving situation of the vehicle within that time period. If the driving time is less than or equal to the time interval, it indicates a relatively long non-driving interval between the two abnormal trip segments, suggesting the abnormal driving state is not continuous. In this case, the two trip segments should be treated as independent trips and not merged to avoid masking the abnormal characteristics of each segment. Thus, by comprehensively judging the driving time and time interval of adjacent abnormal trip segments, intelligent processing of trip merging is achieved. The result of merging or not merging directly affects the accuracy and reliability of subsequent applications such as trip analysis, energy consumption calculation, and driving behavior analysis, thereby enabling more precise capture of abnormal driving patterns of the vehicle. This processing method makes the presentation of trip data more in line with actual driving scenarios, improving the practicality and accuracy of trip processing results.

[0039] Therefore, by identifying and processing abnormal travel trips, the continuity and accuracy of trip data can be maintained even in the event of network anomalies. This effectively avoids trip missegmentation or erroneous merging caused by unreliable networks, thereby improving the accuracy and integrity of trip data.

[0040] According to one embodiment of this application, determining that a vehicle has an abnormal driving trip based on a first power-on condition and / or a second power-on condition includes: obtaining a flag bit of the vehicle's power mode before and after a first preset time; determining that the vehicle is in a powered-on state when the flag bit is a first preset flag bit; determining that the vehicle's current trip is an abnormally ended driving trip when the first power-on condition is a powered-on state; and / or determining that the vehicle's current trip is an abnormally started driving trip when the second power-on condition is a powered-on state.

[0041] Specifically, when determining whether the vehicle has experienced abnormal travel based on a first power-on condition, or a second power-on condition, or both, the vehicle power mode flags before and after a first preset time can be obtained. The vehicle power mode flags are specific parameters in the vehicle power system used to indicate the power status. Different flags correspond to different power modes; for example, the power mode field flags are represented as 0x0 and 0x2. Specifically, flag 0x0 corresponds to the second preset flag, indicating that the vehicle is in a non-power-on state, such as a shutdown or hibernation mode, where the vehicle's power system and main electrical equipment are stopped. Flag 0x2 corresponds to the first preset flag, indicating that the vehicle is in a power-on state, i.e., running or driving mode. At this time, the vehicle's power system has started, and related sensors and control systems are all operational, capable of collecting and transmitting vehicle operating data in real time. Therefore, by acquiring the flag data before and after the first preset time, it is possible to clearly understand the changes in the vehicle's power status during that time period, providing a crucial data foundation for subsequent judgment on whether the vehicle has experienced abnormal driving.

[0042] The system assesses the first power-on condition. If the vehicle is in a powered-on state, the current trip is determined to have ended abnormally. In other words, if the vehicle's power mode flag (power-on status flag) was active before a first preset time, it indicates the vehicle was normally powered on before that time. The absence of uploaded driving data within the first preset time means the vehicle was initially in a normal powered-on driving state, but data transmission was suddenly interrupted, preventing the cloud server from continuously acquiring driving data. In this case, the currently ongoing trip failed to end normally due to data interruption and is therefore judged as an abnormally ended trip. For example, if the first preset time is set to 5 minutes, and the cloud server does not receive any uploaded driving data for 5 consecutive minutes due to a sudden loss of network signal, even if the vehicle may still be moving, from a data reception perspective, the trip is considered abnormally ended. This determination of abnormally ended trips provides a clear identification basis for subsequent correction and completion of trip data, enabling appropriate handling measures to be taken for such anomalies and ensuring the continuity of trip data.

[0043] Alternatively, when determining whether a vehicle has an abnormal driving trip based on the second power-on condition, the second power-on condition is judged. If the second power-on condition indicates a power-on state, the current trip can be determined to be an abnormally started trip. That is, after a first preset time, the vehicle's power mode flag is the first preset flag (i.e., the power-on state flag), indicating that the vehicle is normally powered on after the first preset time. If no driving data is received from the vehicle during the first preset time, it means the vehicle is not sending driving data to the cloud server during that time. Later, when network conditions are good, the driving data is sent to the cloud server, confirming the vehicle is powered on. In this case, because there is no driving data recorded during the previous power-off phase, the starting data of the current trip is incomplete, thus it is determined to be an abnormally started trip. For example, if the first preset time is set to 5 minutes, and the vehicle has not uploaded any driving data to the cloud for the past 5 minutes, but the second power-on condition detects that the vehicle is powered on and has started generating driving data, then the cloud will recognize that the start of the trip lacks preceding data continuity, constituting an abnormally started trip. This determination of abnormal start also provides direction for subsequent data processing. For example, when integrating trip data, it is necessary to specifically mark the start state of the trip to avoid incorrectly associating it with the previous trip that ended normally. At the same time, it can also remind the system to consider the possible data gaps in the initial stage when analyzing the trip data, so as to more accurately assess the trip integrity and apply the data.

[0044] Alternatively, it is also possible to determine whether the vehicle has an abnormal driving journey based on both the first and second power-on conditions. If the first power-on condition is that the vehicle is powered on, the current journey can be determined as an abnormally ended journey. When determining whether the vehicle has an abnormal driving journey based on the second power-on condition, the second power-on condition is evaluated. If the second power-on condition is that the vehicle is powered on, the next segment of the journey can be determined as an abnormally started journey.

[0045] Therefore, by combining real-time monitoring of vehicle driving data with preset time thresholds, abnormal start and end times of driving trips caused by data transmission interruptions can be accurately identified. Once an abnormal start or end time of a trip is determined, corresponding follow-up processes can be triggered, such as sending a data retransmission request to the vehicle or performing reasonable data interpolation and repair in the cloud based on historical data and vehicle models. This minimizes the impact of data loss on trip analysis, user driving behavior assessment, and vehicle status monitoring. Simultaneously, for users, marking abnormal start and end times helps them understand potential problems during data recording, enhancing user trust in trip data and improving the user experience.

[0046] According to one embodiment of this application, processing two adjacent trip segments based on abnormal travel distance and travel duration includes: when the previous trip segment ended normally and the current trip segment started abnormally, the current trip segment and the previous trip segment are not merged; when the current trip segment ended abnormally and the next trip segment started normally, the current trip segment and the next trip segment are not merged.

[0047] Specifically, the system determines whether the vehicle's previous trip ended normally and whether the current trip started abnormally. If the previous trip ended normally but the current trip started abnormally, the two trips are not merged. In other words, when the previous trip is determined to have ended normally, it means the trip's end met preset normal end conditions, such as the vehicle being turned off and stationary for a specified time, or the driver actively ending the trip recording. In this case, the information from the previous trip is complete and valid. However, if the current trip is identified as starting abnormally, it indicates that its initial stage did not conform to normal trip start conditions, possibly due to a short-term accidental start, abnormal sensor triggering, or network problems encountered during driving. In this case, since the previous trip has completed a normal loop, its data boundaries are clear. The abnormal start characteristic of the current trip makes it logically unrelated to the previous trip. Forcibly merging them might lead to data confusion and fail to accurately reflect the actual driving situation; therefore, the current trip is not merged with the previous trip.

[0048] The system determines whether the vehicle's current trip has ended abnormally and whether the next trip will begin normally. If the current trip has ended abnormally but the next trip will begin normally, the current and next trips can be processed separately. In other words, when the current trip is determined to have ended abnormally, it means the trip's termination did not meet the preset normal termination conditions. For example, the vehicle might have stalled due to a sudden malfunction, been interrupted by a traffic accident, or failed to report to the cloud server within a preset time due to network issues. In this case, the current trip information may be incomplete or contain abnormal data. Conversely, if the next trip is identified as beginning normally, it means its starting phase meets the standard conditions for starting a regular trip, such as the driver starting the vehicle normally and the trip recording system initializing and starting data collection normally. In this situation, the abnormal termination of the current trip blurs its data boundaries or results in missing data, while the normal start of the next trip marks the beginning of a new, complete trip cycle. Logically, the two are independent trip units. If the current trip that ends abnormally is merged with the next trip that starts normally, incomplete or abnormal data may be mixed into the normal trip, which will interfere with the accurate analysis and evaluation of the data of the next normal trip and will not be able to truly reflect the actual driving conditions of the next trip. Therefore, the current trip and the next trip are not merged.

[0049] For example, such as Figure 2 As shown, the vehicle trip processing method of this application embodiment may include the following steps: S11, if no vehicle-uploaded driving data is received within a first preset time, obtain the first power-on status of the vehicle before the first preset time and the second power-on status of the vehicle after the first preset time.

[0050] S12, based on the first power-on condition and the second power-on condition, it is determined that the vehicle has an abnormal driving journey.

[0051] S13, determine whether the first power-on condition is a power-on state. If yes, proceed to step S14; if no, proceed to step S16.

[0052] S14, It is determined that the vehicle's current trip is an abnormally terminated trip.

[0053] S15: If the next segment of the vehicle's journey is a normal start of driving, the current journey and the next segment of the journey will not be merged.

[0054] S16, Determine whether the second power-on condition is a power-on state. If yes, proceed to step S17; otherwise, proceed to step S11.

[0055] S17, It has been determined that the vehicle's current journey is an abnormal start-up journey.

[0056] S18: If the vehicle's previous trip ended normally, the current trip and the previous trip will not be merged.

[0057] Therefore, by specifically judging and processing the combination of abnormal and normal driving trips in adjacent trips, the problem of trip data distortion caused by improper merging of abnormal and normal trips can be effectively avoided. This processing method fully considers the integrity, logic, and independence of trip data, ensuring that each trip data segment can reflect the actual driving process of the vehicle as accurately as possible. This provides a reliable data foundation for subsequent applications such as trip data analysis, statistics, and evaluation, and helps to improve the accuracy and effectiveness of vehicle trip management.

[0058] According to one embodiment of this application, processing two adjacent trip segments based on abnormal travel routes and travel duration includes: when the current trip of the vehicle is an abnormally ended trip and the next trip of the vehicle is an abnormally started trip, obtaining a first interval duration between the abnormally ended trip and the abnormally started trip; and processing the two adjacent trip segments based on the first interval duration and travel duration.

[0059] Specifically, the system determines whether the vehicle's current trip has an abnormal ending and whether the next trip will begin abnormally. If the current trip has an abnormal ending and the next trip will begin abnormally, the system obtains the first interval between the two trips and processes the adjacent trip segments based on this first interval and the travel duration. The first interval refers to the time difference between the end time of the abnormally ending trip and the start time of the abnormally starting trip. The travel duration is the travel time recorded by the onboard equipment during the current trip, representing the actual time the vehicle is in motion during that trip.

[0060] When determining whether to merge trips, the first interval duration can be compared with the travel time. For example, if the first interval duration is significantly shorter than the travel time, it indicates that the two abnormal trips have strong temporal continuity, possibly due to a brief signal interruption, momentary equipment failure, or other reasons that caused the trips to be incorrectly segmented. In this case, the trips ending and beginning abnormally can be merged into a single complete trip. If the first interval duration is longer than the travel time, it indicates that there is a long time interval between the two trips, and they are highly independent. Merging these trips may introduce discontinuous travel data, affecting the accuracy of the trip data and the reliability of the analysis results. Therefore, merging is not performed.

[0061] Therefore, by comparing the first interval duration with the travel time, it is possible to effectively identify trip segmentation errors caused by non-substantial reasons (such as brief signal or equipment malfunctions), enabling accurate merging of abnormal trips. This ensures the integrity and continuity of trip data, providing a more reliable data foundation for subsequent vehicle driving behavior analysis, route planning optimization, and operational efficiency evaluation based on trip data. This merging judgment logic fully considers the temporal correlation between trips and the authenticity of data, avoiding data distortion problems that may result from blind merging, and improving the scientific nature and accuracy of vehicle trip processing.

[0062] According to one embodiment of this application, processing two adjacent trip segments based on a first interval duration and a travel duration includes: when the first interval duration is within a preset time interval range and the travel duration is less than or equal to the first interval duration, the current trip segment and the next trip segment are not merged.

[0063] Specifically, when processing two adjacent trip segments based on the first interval duration and the travel time, the system first determines whether the first interval duration falls within a preset time interval range. If the first interval duration is within the preset time interval range, the system then determines the relationship between the travel time and the first interval duration. If the travel time is less than or equal to the first interval duration, the current trip and the next trip segment can be processed without merging. The preset time interval range can be determined according to actual conditions; for example, it can be set to 5 to 45 minutes, which fully considers the brief communication delays that may occur due to network fluctuations during actual driving.

[0064] In other words, when the first interval duration falls within this range, it means the communication delay between the two trips is within a reasonable threshold. At this point, comparing the travel time with the first interval duration to determine whether to merge the trips provides a more accurate reflection of the user's actual travel continuity. For example, refer to... Figure 3 As shown, if a vehicle starts normally from point A and reaches point B, but the cloud server does not receive driving data uploaded by the vehicle within 5 minutes, then point B is determined to be an abnormally ended journey. For example, if the vehicle passes through a tunnel and continues for 10 minutes, and then the network returns to normal at point C, the cloud server receives the driving data sent by the vehicle, then point C is determined to be an abnormally started journey. The vehicle then continues to point D and ends normally. In other words, the vehicle travels normally from point A to point B and ends normally. Assuming the time from point A to point D is 60 minutes and the time from point B to point C is 10 minutes, the interval between points B and C can be determined to be within the preset time interval. Since the vehicle is not currently stopped, the vehicle's recorded travel time is 60 minutes from point A to point D. That is, the current travel time of 60 minutes is greater than the first interval of 10 minutes. Therefore, the journey from the normal start of travel at point A to the abnormal end at point B, the abnormal stop phase from point B to point C, and the journey from the abnormal start of travel at point C to the normal end at point D should be combined into a complete continuous journey. After this processing, the trip information recorded by the cloud server can accurately cover the user's entire travel process from point A to point D, avoiding the trip being divided into multiple discontinuous segments due to factors such as brief network interruptions that are not caused by the user's voluntary stopping of travel. This makes the trip more consistent with the user's actual travel trajectory and continuity requirements.

[0065] Therefore, by comparing the travel time with the first interval duration, it is possible to effectively distinguish between brief data interruptions caused by network anomalies and situations where the user intentionally stops. When the travel time is longer than the first interval duration, it indicates that the vehicle was actually in continuous motion between the two trip segments, but the data upload was interrupted due to network issues. In this case, merging the trips can restore the user's true continuous travel process. However, when the travel time is less than or equal to the first interval duration, it indicates that the pause between the two trip segments may not be caused by network latency. For example, the user may have intentionally stopped to rest or handle other matters during the trip. In this case, not merging the trips can more accurately reflect the user's actual trip division, avoiding the incorrect inclusion of irrelevant pauses in the same trip. This further improves the accuracy and rationality of trip data recording, providing a reliable data foundation for subsequent trip data analysis and applications.

[0066] According to one embodiment of this application, processing two adjacent trip segments based on a first interval duration and a travel time includes: merging the current trip segment with the next trip segment when the first interval duration is within a preset time interval range and the travel time is greater than the first interval duration. The preset time interval range can be determined according to actual circumstances.

[0067] Specifically, it is determined whether the first interval duration is within the preset time interval range. If the first interval duration is within the preset time interval range, the relationship between the travel time and the first interval duration is then determined. If the travel time is greater than the first interval duration, the current trip and the next trip can be merged.

[0068] In other words, when a vehicle experiences a temporary interruption in trip recording due to factors such as network fluctuations or brief signal loss during operation, the system will first calculate the initial interval between the two trip segments. If this initial interval falls within a preset time interval range... (Reference) Figure 3As shown, if a vehicle starts normally from point A and reaches point B, but the cloud server does not receive the vehicle's driving data within 5 minutes, then point B is determined to be an abnormal end to the journey. For example, if the vehicle passes through a tunnel and the journey continues for 30 minutes, then the network returns to normal at point C, and the cloud server receives the vehicle's driving data, then point C is determined to be an abnormal start to the journey. The vehicle then continues to point D and ends the journey normally. In other words, the vehicle travels normally from point A to point B and ends normally. Assuming the time from A to D is 60 minutes, the time from A to B is 15 minutes, the time from B to C is 30 minutes, and the time from C to D is 15 minutes, and considering that the vehicle stops within the tunnel due to a malfunction or the driver handling an abnormal situation, the stopping time is 20 minutes. When the driver restarts the vehicle, the onboard equipment recalculates the travel time. The actual travel time from point B to point C is 10 minutes. Upon reaching point D, the accumulated travel time is 25 minutes. Since the currently recorded travel time of 25 minutes is less than the first time interval of 30 minutes, the trip from point A to point D will not be merged. For example, the trip from point A to point B is divided into the first segment (15 minutes), and the trip from point C to point D is the second segment (15 minutes). The 30 minutes from point B to point C (including 20 minutes of parking and 10 minutes of actual driving) is not considered an independent trip or merged into other trips because it is in an abnormal data upload state and the accumulated travel time does not trigger the trip merging condition. This achieves accurate splitting and rational division of vehicle trips in abnormal data upload scenarios.

[0069] Alternatively, the second leg of the journey can be determined based on the normal end time and the recorded travel time of 25 minutes, and the first leg can be deduced by working backwards. That is, the second leg is point E, 25 minutes before point D. Figure 3 (Not shown in the image) The first segment of the journey is recorded as point A to point E. This allows for accurate definition of the start and end boundaries of different journeys, even when there is a discrepancy between the recorded duration and the actual driving time due to abnormal data uploads. This ensures the integrity and independence of each journey unit, effectively avoids confusion in journey division caused by abnormal parking, data upload delays, and other issues, and further improves the reliability and accuracy of vehicle journey data processing.

[0070] Therefore, by dynamically adjusting the trip merging strategy, accurate identification and flexible processing of trip status at different times during vehicle operation can be achieved. When the first interval duration is within a preset range, if the travel time does not exceed this interval duration, it indicates that the pause or data interruption between the two trip segments is within a reasonable range, and maintaining their independence can more accurately reflect the actual operation segments of the vehicle. When the travel time exceeds the first interval duration, it indicates that the two trip segments have strong continuity in the time dimension. Merging processing can avoid trip fragmentation caused by brief data anomalies or unnecessary pauses, ensuring the continuity and integrity of trip data. This judgment mechanism based on both interval duration and travel time considers reasonable intervals during normal driving and effectively addresses the problem of ambiguous trip boundaries caused by factors such as data upload fluctuations. This provides a more scientific and reliable basis for the intelligent management of vehicle trips, further optimizing the application value of trip data.

[0071] According to one embodiment of this application, the vehicle trip processing method further includes: when the first interval duration is greater than the upper limit of a preset time interval range, the current trip and the next trip are not merged.

[0072] Specifically, the relationship between the first interval duration and the preset time interval range is assessed. If the first interval duration exceeds the upper limit of the preset time interval range, it indicates that the time interval between the abnormal end of the journey and the start of the next abnormal journey is too long, exceeding the reasonable duration of a brief network interruption. In this case, the two journeys are logically independent in time, each representing the vehicle's operating status at different times. Forcibly merging them may incorrectly associate unrelated journey segments, causing the journey data to deviate from the actual operating situation and affecting the accuracy of the journey analysis.

[0073] For example, if the current first interval is 10 hours, and the maximum preset time interval is 45 minutes, then 10 hours far exceeds the preset limit, indicating a significant period of non-driving activity between the current trip and the next trip. This could be due to the vehicle being parked for an extended period, used across multiple days, or other scenarios unrelated to normal continuous driving. For instance, the current driving situation might be that after the vehicle has been driving normally for a period, the network becomes abnormal, the cloud server does not receive driving data uploaded by the vehicle, and the vehicle stops at this time. If the user resumes using the vehicle overnight, the network will recover after a period of time due to the vehicle restarting, and the cloud server will resume receiving driving data uploaded by the vehicle. In this case, the first trip ended due to both network abnormality and vehicle parking, while the second trip began after the overnight break. The interval between the two trips is 10 hours, far exceeding the preset 45-minute limit. In this situation, the two trips clearly belong to different usage scenarios; the former might be a trip taken that day, while the latter is a trip taken the following day. If these two trips are merged, key information such as total trip duration, route, and stops will become confused, failing to accurately reflect the user's actual travel behavior. For example, the merged trip might incorrectly show that the vehicle traveled for extended periods at night, or it might combine two independent short trips into a single "abnormal" trip with long non-driving intervals. This would not only mislead applications such as fuel consumption analysis and driving behavior assessment based on trip data, but could also negatively impact decisions regarding vehicle scheduling and maintenance. Therefore, when the first interval duration exceeds a preset upper limit, merging the trips is not performed. This ensures the independence of each trip and the accuracy of the data, providing a reliable foundation for subsequent trip management and analysis.

[0074] Therefore, when the first interval exceeds the preset upper limit, maintaining the independence of the trip is a necessary processing method to ensure the authenticity of the data. It can accurately distinguish vehicle operation segments under different spatiotemporal backgrounds, laying an accurate foundation for subsequent trip management and data analysis.

[0075] In summary, as Figure 4 As shown, the vehicle trip processing method of this application embodiment may include the following steps: S21, if no vehicle-uploaded driving data is received within a first preset time, it is determined that the vehicle has an abnormal driving journey based on the first power-on condition and the second power-on condition.

[0076] S22, based on the first power-on condition and the second power-on condition, it is determined that the vehicle has an abnormal driving journey.

[0077] S23, if it is determined that the current trip of the vehicle is an abnormally ended trip and the next trip of the vehicle is an abnormally started trip, obtain the first interval duration between the abnormally ended trip and the abnormally started trip.

[0078] S24. Determine whether the first interval duration is within the preset time interval range and whether the travel time is less than or equal to the first interval duration. If yes, proceed to step S25; otherwise, proceed to step S26.

[0079] S25, the current trip and the next trip segment are not merged.

[0080] S26, determine whether the first interval duration is within the preset time interval range and whether the travel time is greater than the first interval duration. If yes, proceed to step S27; if no, proceed to step S28.

[0081] S27, merges the current trip with the next trip segment.

[0082] S28. Determine whether the duration of the first interval is greater than the upper limit of the preset time interval range. If yes, proceed to step S25; otherwise, proceed to step S23.

[0083] According to one embodiment of this application, the vehicle trip processing method further includes: determining that the current trip of the vehicle is a normal end of a trip when the flag position changes from a first preset flag position to a second preset flag position; determining that the current trip of the vehicle is a normal start of a trip when the flag position changes from a second preset flag position to a first preset flag position, wherein the vehicle is in a power-off state when the flag position is the second preset flag position.

[0084] Specifically, the changes in the flag position can be judged. When the flag position changes from the first preset flag position to the second preset flag position, it is determined that the current trip of the vehicle has ended normally. That is, the vehicle switches from the previous power-on state (such as driving or running mode) to the non-power-on state (such as power off or hibernation mode). At this time, the vehicle's power system stops working, and the collection of relevant operating data also stops, which means that the trip has been completed normally.

[0085] When the flag changes from the second preset flag to the first preset flag, it can be determined that the vehicle's current journey has begun a normal driving journey. That is, the vehicle transitions from a non-powered state to a powered state, the power system starts, and sensors and other devices begin collecting data, indicating that the vehicle has begun a new normal driving journey. By monitoring this state transition of the flag, the start and end times of the journey can be accurately captured, ensuring the completeness and accuracy of the journey record. This provides a reliable time point basis for subsequent journey data analysis, statistics, and related applications.

[0086] Specifically, when the flag is at the second preset flag position, the vehicle is determined to be in a power-off state. At this time, the vehicle's power system is shut down, all core components cease operation, and the vehicle cannot be driven by the power system. The vehicle's power-off state typically occurs after the vehicle has completed its driving task, either when the user turns off the engine or when the system automatically enters sleep mode. In this state, the vehicle's energy consumption is minimized, retaining power only for essential basic functions such as the anti-theft system and remote unlocking system to ensure basic vehicle safety and ease of restarting. By clearly defining the vehicle's power-off state when the flag is at the second preset flag position, a clear distinction can be made from the vehicle's power-on state, providing crucial status information for determining the start and end of a trip, further ensuring the rigor and accuracy of the trip processing logic.

[0087] In other words, when the vehicle finishes normal driving or the vehicle's journey ends, this method of determining the start and end of the journey based on the change of the flag position can effectively avoid misjudging the journey status due to non-end-of-journey situations such as the vehicle being briefly turned off (such as when the engine start-stop function is activated while waiting at a red light) or temporary power failure, thus ensuring the accuracy and rationality of the journey division.

[0088] According to one embodiment of this application, the vehicle trip processing method further includes: obtaining a second interval duration between the previous normally ended trip and the current normally started trip; if the second interval duration is greater than or equal to a preset interval duration threshold, not merging the current trip and the previous trip; if the second interval duration is less than the preset interval duration threshold, merging the current trip and the previous trip. The preset interval duration threshold can be determined according to actual conditions.

[0089] Specifically, when the vehicle is in normal driving or has just finished driving, the system can obtain the second interval between the previous normally ended driving segment and the current normally started driving segment. The system then compares this second interval with a preset interval threshold. If the second interval is greater than or equal to the preset threshold, the current and previous segments are not merged. If the second interval is less than the preset threshold, the current and previous segments are merged. The preset interval threshold represents the maximum time interval between two normal driving segments that can be considered a continuous journey. For example, it can be set to 5 minutes or 30 minutes. The specific value can be flexibly configured by the system administrator based on the usage scenarios of different vehicle models (such as short-interval trips for taxis with frequent orders, or short stops during a single trip for private cars), or customized by the user based on their personal driving habits. This time-interval-based trip merging strategy effectively avoids unreasonable trip segmentation caused by users' temporary stops (such as short shopping trips, waiting at traffic lights, or temporary passenger pick-up and drop-off), ensuring the integrity and continuity of trip data and providing more accurate basic data for subsequent trip statistical analysis (such as total mileage, average speed, fuel consumption calculation, etc.).

[0090] For example, if the end time of the previous trip is T1 and the start time of the current trip is T2, then the second interval is the difference between T2 and T1. When this difference is greater than or equal to the preset interval threshold, it indicates that the time interval between the two trips is long enough, and the vehicle may have experienced a long period of parking or non-use. In this case, the current trip and the previous trip are treated as two independent trips, recorded and processed separately, to avoid incorrect merging due to too short an interval. When the second interval is less than the preset interval threshold, it indicates that the two trips are relatively close in time, and may be continuous driving behavior by the user in a short period of time (such as temporarily stopping to run errands and then quickly starting again). In this case, the current trip and the previous trip are merged into a complete trip for recording, to more accurately reflect the user's continuous travel process and prevent the trip from being unnecessarily divided into multiple segments, affecting the continuity of trip data and the accuracy of analysis. For example, if the preset interval time threshold is set to 30 minutes, and the vehicle starts driving again 20 minutes after the end of the previous trip, the two trips will be merged because 20 minutes is less than 30 minutes; if the vehicle starts driving again 40 minutes after the end of the previous trip, it will be treated as two independent trips.

[0091] It should be noted that each trip segment must be greater than 0.1km to be considered valid. If the travel distance of a segment is less than or equal to 0.1km, the segment is considered invalid and will not be recorded separately or merged into other trips. This design is mainly to filter out vehicle movements over extremely short distances, such as users adjusting parking spaces or briefly moving their cars in a parking lot—non-essential travel behaviors. This prevents such minute movement data from interfering with the accuracy of normal trip recordings, ensuring that the recorded trip data represents the user's real and valid travel trajectory, and further improving the reliability of trip analysis results.

[0092] Therefore, by comparing the second interval duration with the preset interval duration threshold, the continuity of the trip can be flexibly determined based on the time interval characteristics between normal vehicle trips, enabling accurate identification and merging of users' continuous travel behavior. At the same time, it avoids incorrectly associating independent trips with excessively long intervals, further optimizing the logic and usability of trip data, and providing more reliable data support for various applications based on trip data (such as travel trajectory analysis, driving behavior assessment, vehicle energy consumption management, etc.).

[0093] The following is combined Figure 5 The method described in this application is used to describe the method.

[0094] As a specific example, the vehicle trip processing method of this application may include the following steps: S101, if no vehicle-uploaded driving data is received within a first preset time, obtain the first power-on status of the vehicle before the first preset time and the second power-on status of the vehicle after the first preset time.

[0095] S102, based on the first power-on condition and the second power-on condition, it is determined that the vehicle has an abnormal driving journey.

[0096] S103, determine whether the first power-on condition is a power-on state. If yes, proceed to step S104; if no, proceed to step S114.

[0097] S104, the vehicle's current trip has been determined to have ended abnormally.

[0098] S105, determine whether the next segment of the vehicle's journey is a normal start-up journey. If yes, proceed to step S106; if no, proceed to step S107.

[0099] S106, the current trip and the next trip segment are not merged.

[0100] S107, determine whether the next segment of the vehicle's journey is an abnormal start to the journey. If yes, proceed to step S108; if no, proceed to step S101.

[0101] S108, obtain the first interval duration between the abnormal end of the driving trip and the abnormal start of the driving trip.

[0102] S109, determine whether the first interval duration is within the preset time interval range and whether the travel time is less than or equal to the first interval duration. If yes, proceed to step S110; if no, proceed to steps S111 and S112.

[0103] S110, the current trip and the next trip segment are not merged.

[0104] S111, determine whether the duration of the first interval is greater than the upper limit of the preset time interval range. If yes, proceed to step S113; if no, proceed to step S108.

[0105] S112, determine whether the first interval duration is within the preset time interval range and whether the travel time is greater than the first interval duration. If yes, proceed to step S113; if no, proceed to step S108.

[0106] S113, merges the current trip with the next trip segment.

[0107] S114, determine whether the second power-on condition is a power-on state. If yes, proceed to step S115; if no, proceed to step S101.

[0108] S115, the vehicle's current journey has been determined to be an abnormal start of the journey.

[0109] S116, determine whether the vehicle's previous trip was a normal end to the journey. If yes, proceed to step S117; if no, proceed to step S101.

[0110] S117, the current trip segment and the previous trip segment are not merged.

[0111] In summary, the vehicle trip processing method according to the embodiments of this application, when no vehicle-uploaded driving data is received within a first preset time, obtains the vehicle's first power-on status before the first preset time and the vehicle's second power-on status after the first preset time. Based on the first power-on status and / or the second power-on status, it is determined that the vehicle has an abnormal driving trip. Then, based on the abnormal driving trip and the vehicle's currently recorded driving duration, two adjacent trip segments are processed. Therefore, this method can effectively avoid trip mis-segmentation or incorrect merging caused by network unreliability, thereby improving the accuracy and completeness of trip data.

[0112] Corresponding to the above embodiments, this application also proposes a vehicle.

[0113] like Figure 6As shown, the vehicle 200 in this embodiment may include: a memory 210, a processor 220, and a program stored in the memory 210 and executable on the processor 220. When the processor 220 executes the program, it implements the above-described vehicle trip processing method.

[0114] According to the embodiments of this application, by executing the above-described vehicle trip processing method, the vehicle can effectively avoid trip missegmentation or erroneous merging caused by network unreliability, thereby improving the accuracy and completeness of trip data.

[0115] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0116] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0117] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0118] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0119] In this application, unless otherwise expressly specified and limited, the terms "installation," "connection," "joining," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components, unless otherwise expressly limited. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.

[0120] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A method for processing vehicle travel, characterized in that, The method includes: If no vehicle-uploaded driving data is received within a first preset time, the first power-on status of the vehicle before the first preset time and the second power-on status of the vehicle after the first preset time are obtained. Based on the first power-on condition and / or the second power-on condition, it is determined that the vehicle has an abnormal driving journey; The two adjacent trip segments are processed based on the abnormal travel route and the vehicle's currently recorded travel time.

2. The vehicle trip handling method according to claim 1, characterized in that, The step of determining that the vehicle has an abnormal driving journey based on the first power-on condition and / or the second power-on condition includes: Obtain the flags of the vehicle power mode before and after the first preset time; When the flag is set to the first preset flag, the vehicle is determined to be powered on. If the first power-on condition is the power-on state, then the vehicle's current journey is determined to be an abnormally terminated journey; and / or If the second power-on condition is the power-on state, the current journey of the vehicle is determined to be an abnormal start of driving journey.

3. The vehicle trip handling method according to claim 2, characterized in that, The process of processing two adjacent trip segments based on the abnormal travel distance and the travel duration includes: If the vehicle's previous trip ended normally and the vehicle's current trip started abnormally, the current trip and the previous trip will not be merged. If the current trip of the vehicle is an abnormally ended trip, and the next trip of the vehicle is a normally started trip, the current trip and the next trip will not be merged.

4. The vehicle trip handling method according to claim 2, characterized in that, The process of processing two adjacent trip segments based on the abnormal travel distance and the travel duration includes: If the current trip of the vehicle is the trip that ends abnormally, and the next trip of the vehicle is the trip that begins abnormally, then obtain the first interval duration between the trip that ends abnormally and the trip that begins abnormally; The two adjacent trip segments are processed based on the first interval duration and the travel duration.

5. The vehicle trip handling method according to claim 4, characterized in that, The process of processing two adjacent trip segments based on the first interval duration and the travel duration includes: If the first interval duration is within a preset time interval range and the travel time is less than or equal to the first interval duration, the current trip and the next trip segment will not be merged.

6. The vehicle trip handling method according to claim 4, characterized in that, The process of processing two adjacent trip segments based on the first interval duration and the travel duration includes: If the first interval duration is within the preset time interval range and the travel duration is greater than the first interval duration, the current trip and the next trip segment are merged.

7. The vehicle trip handling method according to claim 5, characterized in that, The method further includes: If the duration of the first interval is greater than the upper limit of the preset time interval range, the current trip and the next trip segment will not be merged.

8. The vehicle trip handling method according to claim 2, characterized in that, The method further includes: When the flag position changes from the first preset flag position to the second preset flag position, the current journey of the vehicle is determined to be a normal end of the journey. When the flag position changes from the second preset flag position to the first preset flag position, the current journey of the vehicle is determined to be a normal start journey, wherein when the flag position is the second preset flag position, the vehicle is determined to be in a power-off state.

9. The vehicle trip handling method according to claim 8, characterized in that, The method further includes: Obtain the second interval duration between the previous normally ended driving trip and the current normally started driving trip of the vehicle; If the second interval duration is greater than or equal to the preset interval duration threshold, the current trip and the previous trip will not be merged. If the second interval duration is less than the preset interval duration threshold, the current trip and the previous trip are merged.

10. A vehicle, characterized in that, include: A memory, a processor, and a program stored in the memory and executable on the processor, wherein when the processor executes the program, it implements the vehicle trip processing method according to any one of claims 1-9.

Images