Vehicle travel information processing method and device

Abstract

The embodiment of the invention provides a vehicle travel information processing method and device which can be applied to the technical field of intelligent driving. The method comprises the steps of displaying a historical travel report in a list form according to a preset format in a historical travel overview interface; wherein the preset format is a preset plain text format or a preset image-text combined format; displaying detail information of the historical travel report in a report detail interface in response to a viewing instruction of a user for the historical travel report; wherein the detailed information is used for describing travel data of the vehicle in the process of completing the travel route. The method is used for displaying the historical travel report more visually and more clearly, so that the user is helped to deeply know the travel condition, and the user experience is improved.

Description

Technical Field

[0001] This application relates to the field of intelligent driving technology, and in particular to a method and apparatus for processing vehicle trip information. Background Technology

[0002] As living standards continue to improve, more and more users are traveling by car. Currently, some vehicles can generate corresponding trip reports after the user completes their trip.

[0003] However, current trip reports are typically limited to vehicle driving data during the journey, resulting in overly simplistic data and format. This not only hinders users from reviewing their trips but also lacks engagement. Furthermore, the management of trip reports lacks user interaction; users cannot perform further operations on the reports, failing to meet their actual needs and resulting in a subpar user experience.

[0004] Therefore, there is an urgent need for a new method for processing vehicle trip information to meet user needs and improve user experience. Summary of the Invention

[0005] This application provides a method and apparatus for processing vehicle trip information, which can display historical trip reports more intuitively and clearly, so as to help users understand the trip situation in depth and improve the user experience.

[0006] In a first aspect, embodiments of this application provide a method for processing vehicle trip information, the method comprising:

[0007] In the historical itinerary overview interface, historical itinerary reports are displayed in a list format according to a preset format; wherein, the preset format is a preset plain text format or a preset combined text and image format;

[0008] In response to the user's instruction to view the historical trip report, the detailed information of the historical trip report is displayed in the report details interface; wherein, the detailed information is used to describe the trip data of the vehicle during the completion of the travel route.

[0009] In one possible implementation, the historical itinerary overview interface further displays one or more of the following functional controls: sorting control, filtering control, and deletion control; the method further includes:

[0010] In response to a user's touch operation on the sorting control, the historical trip reports that can be displayed in the historical trip overview interface are sorted according to a preset sorting rule, and the sorted historical trip reports are displayed.

[0011] In response to a user's touch operation on the filtering control, the historical trip reports that can be displayed in the historical trip overview interface are filtered according to preset filtering conditions, and the filtered historical trip reports are displayed.

[0012] In response to a user's touch operation on the delete control, the user-selected historical trip report is deleted.

[0013] In one possible implementation, the report details interface further displays one or more of the following functional controls: a sharing control and a rating control; the method also includes:

[0014] In response to a user's touch operation on the sharing control, a sharing link for the historical itinerary report is generated and sent to the target platform; wherein, the sharing link is used by other users to view the historical itinerary report on the target platform;

[0015] In response to a user's touch operation on the evaluation control, the evaluation interface of the historical trip report is displayed, and after the user completes the evaluation, the user's evaluation of the historical trip report is displayed in the report details interface.

[0016] In one possible implementation, before displaying the historical itinerary report in a list format according to a preset format, the method further includes:

[0017] In response to the user's travel instructions, the vehicle's travel data is acquired during the process of the vehicle completing its journey based on the navigation information corresponding to the travel route;

[0018] After the trip is finalized, a historical trip report of the travel route is generated based on the trip data.

[0019] In one possible implementation, prior to responding to the user's travel instructions, the method further includes:

[0020] It receives user settings instructions and determines the trip data to be collected during the driving process.

[0021] In one possible implementation, the trip data includes one or more of the following information: activity name, route name, mileage information, time consumption information, vehicle speed information, acceleration information, user information, vehicle body data information, driving trajectory information, and driving environment video.

[0022] In one possible implementation, when the trip data includes travel trajectory information, the historical trip report includes a playback video of the travel trajectory; generating the historical trip report of the travel route based on the trip data includes:

[0023] Based on the driving trajectory information, a driving trajectory video is generated;

[0024] A data layer is constructed on the driving trajectory video, and target layer data is filled into the data layer to obtain the driving trajectory playback video; wherein, the target layer data includes at least one of the activity name, the route name, the mileage information, the time consumption information, the vehicle speed information, the acceleration information, the user information, and the vehicle body data information;

[0025] The hyperlink to the playback video of the driving trajectory is recorded in the historical trip report of the travel route.

[0026] In one possible implementation, when the trip data includes driving environment video, the historical trip report includes driving environment playback video; generating the historical trip report of the travel route based on the trip data includes:

[0027] A data layer is constructed on the driving environment video, and target layer data is filled into the data layer to obtain the driving environment playback video; wherein, the target layer data includes at least one of the activity name, the route name, the mileage information, the time consumption information, the vehicle speed information, the acceleration information, the user information, and the vehicle body data information;

[0028] The hyperlink to the driving environment playback video is recorded in the historical trip report of the travel route.

[0029] Secondly, embodiments of this application provide a vehicle trip information processing apparatus, the apparatus comprising:

[0030] The first processing unit is used to display the historical itinerary report in a list format according to a preset format in the historical itinerary overview interface; wherein, the preset format is a preset plain text format or a preset combined text and image format;

[0031] The second processing unit is configured to respond to the user's instruction to view the historical trip report and display detailed information of the historical trip report in the report details interface; wherein the detailed information is used to describe the trip data of the vehicle during the completion of the travel route.

[0032] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0033] The memory stores computer-executed instructions;

[0034] The processor executes computer execution instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0035] Fourthly, embodiments of this application provide an automobile that includes the electronic equipment described in the third aspect.

[0036] Fifthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0037] In a sixth aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0038] The vehicle trip information processing method and apparatus provided in this application display historical trip reports in a list format according to a preset format in the historical trip overview interface; wherein the preset format is a preset plain text format or a preset combined text and graphics format; and in response to the user's command to view the historical trip report, display detailed information of the historical trip report in the report details interface; wherein the detailed information describes the trip data of the vehicle during the completion of the travel route; based on this, a more intuitive and clearer historical trip report is displayed. In this way, the vehicle terminal can also quickly respond to the user's viewing command, provide comprehensive trip data, help users understand the trip situation in depth, and the combined text and graphics display method also makes the trip data more intuitive and easy to understand, improving the user experience. Attached Figure Description

[0039] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0040] Figure 1 A flowchart illustrating a method for processing vehicle trip information provided in an embodiment of this application;

[0041] Figure 2 A schematic diagram of a historical itinerary overview interface provided in an embodiment of this application;

[0042] Figure 3 A schematic diagram of yet another historical itinerary overview interface provided in an embodiment of this application;

[0043] Figure 4 A schematic diagram of a report details interface provided in an embodiment of this application;

[0044] Figure 5 A flowchart illustrating another method for processing vehicle trip information provided in this application embodiment;

[0045] Figure 6 A schematic diagram of a vehicle trip information processing device provided in this application;

[0046] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0047] The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation

[0048] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0049] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0050] With the development of intelligent transportation systems, the management and display of vehicle trip information has become increasingly important. In some possible examples, vehicles can generate trip reports after a user completes their journey. However, current trip reports are typically limited to vehicle driving data during the trip, with overly simplistic data and format. This not only hinders user review but also lacks engagement. Furthermore, the management of trip reports lacks user interaction; users cannot perform further operations or processing on the reports, failing to meet their actual needs and resulting in a subpar user experience.

[0051] Therefore, this application provides a method for processing vehicle trip information, which supports displaying multiple historical trip reports in a list on the interface. Users can click on any historical trip report to view the report details, thereby gaining a more intuitive understanding of the overall trip information. In addition, it also supports sorting, filtering, deleting, sharing, and rating of trip reports to achieve multi-faceted management of trip reports, which not only meets the user's multi-faceted interaction needs but also improves the user experience.

[0052] The execution subject of the vehicle trip information processing method in this application can be an in-vehicle terminal, or other electronic devices such as computers, servers, and mobile phones. This application does not limit it. The following explanation takes an in-vehicle terminal as the execution subject.

[0053] The following is an example illustrating one application scenario of the vehicle trip information processing method provided in this application.

[0054] For example, in this application scenario, if a user wants to view the details of a historical trip report, the user can operate on the interface displayed on the in-vehicle terminal to enter the historical trip overview interface. In the historical trip overview interface, the in-vehicle terminal will display multiple historical trip reports in a list format according to a preset plain text format or a preset combination of text and images. When the user clicks on any historical trip report they want to view, the in-vehicle terminal will respond to the user's command to view the historical trip report and display the detailed information of that historical trip report in the report details interface. In this way, the user can know the trip data of the vehicle during the completion of the travel route through the displayed details.

[0055] It should be noted that the above scenario is only an example of an application scenario provided by the embodiments of this application. The embodiments of this application do not limit the actual form of the various devices included in the scenario. In the specific application of the solution, it can be set according to actual needs.

[0056] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0057] Figure 1 This is a flowchart illustrating a method for processing vehicle trip information provided in an embodiment of this application. This embodiment describes how to display and manage historical trip reports. The method in this embodiment can be implemented using software, hardware, or a combination of both.

[0058] like Figure 1 As shown in the embodiments of this application, the method for processing vehicle trip information may include:

[0059] S101. In the historical itinerary overview interface, the historical itinerary report is displayed in a list format according to the preset format; wherein, the preset format is either a preset plain text format or a preset combined text and image format.

[0060] For example, the historical trip overview interface is the main entry point for users to view the details of the vehicle's historical trip report. In this embodiment of the application, the vehicle terminal will display the historical trip report in a list format according to a preset format in the historical trip overview interface.

[0061] The historical trip report is generated based on the vehicle's trip data. It can be generated immediately after the trip ends or in real-time when a historical trip report is needed. This embodiment does not limit the generation time of the historical trip report. The generation process of the historical trip report can be executed by the in-vehicle terminal or by the cloud server. When generated by the in-vehicle terminal, the generated historical trip report is uploaded to the cloud server for storage; when generated by the cloud server, the generated historical trip report is sent to the in-vehicle terminal for display; in addition, the cloud server can also send the historical trip report to a mobile device for display as needed, so that users can view the historical trip report on their mobile devices. It is understood that information can be exchanged between the in-vehicle terminal, the cloud server, and the mobile device, and this embodiment does not limit this.

[0062] In one possible embodiment, before displaying the historical trip report in a list format according to a preset format, the vehicle terminal may also: in response to the user's travel instructions, acquire the vehicle's trip data during the process of the vehicle completing its journey based on the navigation information corresponding to the travel route; and generate a historical trip report of the travel route based on the trip data after the trip is completed.

[0063] For example, before the trip begins, the vehicle terminal first receives the user's travel instructions, which may be a destination or trip request entered by the user through the system, mobile application or other interface on the vehicle terminal. After the vehicle starts driving according to the travel route specified by the user, the vehicle terminal will start collecting trip data.

[0064] Optionally, the vehicle's trip data may include one or more of the following information: activity name, route name, mileage information, time consumption information, vehicle speed information, acceleration information, user information, vehicle body data information, driving trajectory information, and driving environment video.

[0065] It should be noted that when a user participates in a travel activity, the vehicle's trip data may include the activity name; when the user is traveling alone, the vehicle's trip data may include the route name. Mileage information may include the trip's origin, destination, and total mileage; time information may include the trip's departure time, arrival time, and total travel time; vehicle speed information may include average speed, maximum speed, minimum speed, and real-time speed; acceleration information may include maximum acceleration G-force and maximum braking G-force; user information may include username, account, and nickname; vehicle data may include the vehicle's brand logo, model, accelerator pedal depth, brake pedal depth, and steering wheel angle; driving trajectory information refers to the geographical location data recorded by the vehicle during driving, which may include the vehicle's GPS (Global Positioning System) coordinates (such as longitude and latitude) at different times, timestamps, vehicle speed, and acceleration at each time point; driving environment video may include some or all of the environmental video captured by the vehicle during its journey. In addition to the information mentioned above, the vehicle's trip data may also include other information as needed, such as fuel consumption during the trip, the number of stops and the location of stops, driving behavior analysis data (sudden braking, sudden acceleration, etc.). This application embodiment does not limit this.

[0066] It should be noted that vehicle trip data can be collected directly or indirectly through data collection devices such as GPS devices, various sensors, and cameras installed on the vehicle, and this application embodiment does not impose any limitations on this. In one possible embodiment, the user can also independently select the vehicle trip data to be acquired. Before responding to the user's travel instructions, the vehicle terminal can also receive the user's setting instructions to determine the trip data to be collected during the journey. For example, the user can set whether to collect vehicle body data information, whether to collect driving environment video, and when to collect driving environment video, etc. In addition, during the vehicle's journey, the user can also modify or determine the trip data to be collected. For example, when encountering scenery that they want to keep, the user can control the camera to collect the corresponding scenery video / image, etc. After the journey begins, the vehicle terminal will collect the required trip data during the vehicle's journey according to the user's settings, so as to generate a historical trip report later.

[0067] When the vehicle reaches the user-defined destination, or the user manually ends the trip, or the vehicle enters a parked state and remains there for a period of time, the on-board terminal can determine that the trip has ended. After determining that the trip has ended, the on-board terminal can generate a historical trip report based on the collected vehicle trip data, and the historical trip report will also display the vehicle's trip data. This application does not impose any restrictions on how the vehicle's trip data is presented in the historical trip report; in practical applications, a suitable UI interface can be designed according to actual needs.

[0068] Understandably, different collected trip data will result in different historical trip reports. In one possible embodiment, when the collected trip data includes driving trajectory information, the historical trip report may include a playback video of the driving trajectory; in this case, generating a historical trip report based on the trip data may include:

[0069] S1. Generate a driving trajectory video based on the driving trajectory information;

[0070] S2. Construct a data layer on the driving trajectory video, and fill the data layer with the target layer data to obtain the driving trajectory playback video; wherein, the target layer data includes at least one of the following: activity name, route name, mileage information, time consumption information, vehicle speed information, acceleration information, user information, and vehicle body data information;

[0071] S3. Record the hyperlinks to the driving trajectory playback videos in the travel route history report.

[0072] For example, when the collected trip data includes driving trajectory information, the vehicle terminal can draw the vehicle's driving trajectory on a map based on the acquired driving trajectory information, such as the vehicle's GPS coordinates, timestamps, speed information, and acceleration information at different times. For instance, different colors or lines can be used to represent different speeds or accelerations. The drawn trajectory is then used to generate a video in chronological order, with each frame corresponding to a trajectory position at a specific time point. This video visualizes the vehicle's driving path, showing the entire journey from the starting point to the destination. Understandably, when a user drives along the planned route, the generated driving trajectory video is similar to a route summary playback video. Furthermore, the vehicle terminal can create one or more data layers on the driving trajectory video according to actual needs. Target layer data to be included in the video, such as activity name / route name, mileage information, time consumption information, vehicle speed information, and acceleration information, can then be filled into the data layers. By combining the driving trajectory video and the data layers, a driving trajectory playback video containing trip data can be generated. In this way, the driving trajectory playback video of this application not only shows the driving route, but also provides various trip data related to the trip, so that users can have a more comprehensive understanding of the trip details, making it easier for users to review the trip, and also increasing the fun.

[0073] In this embodiment, the data layer refers to an additional information layer superimposed on the driving trajectory video to display more travel data, making the video more than just a simple trajectory playback. Optionally, in practical applications, the data layer can be fixed at a certain position in the video, such as the upper left corner or lower right corner, or it can dynamically change with the video content. The style of the data layer, including font, color, and transparency, can be customized to ensure that the information is clearly visible.

[0074] Optionally, the generated driving trajectory playback video can be optimized, such as by adjusting the resolution and compressing the video size, to improve playback quality and loading speed.

[0075] To facilitate users' viewing of driving trajectory playback videos and reduce the memory usage of in-vehicle terminals, the generated driving trajectory playback videos can be further uploaded to the cloud or video server, and an access link for the video can be generated. The hyperlink of the video can be recorded in the historical trip report, so that users can directly access and watch the video by clicking the link.

[0076] In another possible embodiment, when the collected trip data includes driving environment video, the historical trip report may also include driving environment playback video; in this case, generating a historical trip report of the travel route based on the trip data may include:

[0077] S10. Construct a data layer on the driving environment video, and fill the data layer with the target layer data to obtain the driving environment playback video; wherein, the target layer data includes at least one of the following: activity name, route name, mileage information, time consumption information, vehicle speed information, acceleration information, user information, and vehicle body data information;

[0078] S20. Record the hyperlinks to the driving environment playback videos in the historical trip report of the travel route.

[0079] For example, when the collected trip data includes driving environment video, the in-vehicle terminal can create one or more data layers on the driving environment video. Then, target layer data to be included in the video, such as activity name / route name, mileage information, time consumption information, vehicle speed information, acceleration information, user information, vehicle body data information, route thumbnails, etc., can be filled into the data layers. By combining the driving environment video and the data layers, a driving environment playback video containing trip data can be generated. In this way, the driving environment playback video not only displays the driving environment but also provides various trip-related data, allowing users to view the scenery along the way while also gaining a comprehensive understanding of the trip details, facilitating trip review.

[0080] In this embodiment, the data layer refers to an additional information layer superimposed on the driving environment video to display more trip data, making the video more than just a simple playback of the driving environment. Optionally, in practical applications, this data layer can also be fixed at a certain position in the video, such as the upper left corner or lower right corner, or it can change dynamically with the video content. The style of the data layer, including font, color, and transparency, can be customized to ensure that the information is clearly visible.

[0081] After generating the driving environment playback video, it can be optimized, such as by adjusting the resolution and compressing the video size, to improve playback quality and loading speed. For example, if a Digital Video Recorder (DVR) is used to capture driving environment video, the generated playback video will also be a DVR video. To ensure better presentation, the video specifications can be adjusted to 1080P, 30FPS, etc.

[0082] To facilitate users' viewing of driving environment playback videos and reduce the memory usage of in-vehicle terminals, the generated driving environment playback videos can be further uploaded to the cloud or video server, and a video access link can be generated. The hyperlink of the video can be recorded in the historical trip report, so that users can directly access and watch the video by clicking the link.

[0083] Based on this, users can not only view trip reports in text and data formats, but also intuitively review the entire trip through video and obtain detailed data analysis related to the trip. This is of great help for trip optimization, driving behavior analysis, and vehicle management, thus improving the user experience.

[0084] Understandably, when displaying historical trip reports in a list format according to a preset format on the historical trip overview interface, multiple historical trip reports are usually displayed simultaneously. In this case, only the report overview of the historical trip reports can be displayed, that is, only the main information in the report details can be displayed, and all the details can be displayed in the report details interface. In this embodiment, the preset format can be a preset plain text format. The plain text format mainly displays the main information of the historical trip report in text form. The main information in this mode can include activity name or route name, mileage information, time information, vehicle speed information, user information, etc. The advantage of the plain text format is that the information is concise and clear, the loading speed is fast, and it is suitable for quick browsing. In addition, the preset format can also be a preset graphic and text combined format. The graphic and text combined format adds graphic elements to the plain text information and displays the main information of the historical trip report in a graphic and text combined format. The main information in this mode may also include the trip route map, trip statistics charts, etc. The advantage of the graphic and text combined format is that the information is more intuitive, and users can more easily understand the trip data through graphics.

[0085] This application does not limit how historical trip reports are displayed in list form. For example, Figure 2 This is a schematic diagram of a historical trip overview interface provided in an embodiment of this application. Figure 2 As shown, the historical itinerary overview interface 20 follows a preset graphic and text combination format. Figure 2 The list shown displays key information for each historical trip report, including route map, route name, travel time, total travel time, mileage, and maximum speed. Figure 3 This is a schematic diagram of yet another historical itinerary overview interface provided in an embodiment of this application. For example... Figure 3 As shown, the historical itinerary overview interface 30 follows another preset graphic and text combination format. Figure 3 The list shown displays key information for each historical trip report, including route images, route name, travel time, total travel time, mileage, and maximum speed.

[0086] Understandably, Figure 2 and Figure 3 This is merely an example of a historical itinerary overview interface and should not be considered a limitation of this application. In some possible examples, it may also be possible to... Figure 2 and Figure 3 Set up a toggle control in the middle so that users can select... Figure 2 or Figure 3 The historical itinerary report is displayed in a manner that is not limited in this embodiment.

[0087] S102. In response to the user's instruction to view the historical trip report, display the detailed information of the historical trip report in the report details interface; wherein, the detailed information is used to describe the trip data of the vehicle during the completion of the trip route.

[0088] For example, when a user selects and clicks on a historical trip report in the historical trip overview interface, the in-vehicle terminal can respond to the user's viewing command and enter the report details interface. In the report details interface, the in-vehicle terminal will display the detailed information of the selected historical trip report. This detailed information describes the trip data of the vehicle during the completion of the travel route; that is, the detailed information includes, but is not limited to, activity name, route name, mileage information, time consumption information, vehicle speed information, acceleration information, user information, vehicle body data information, driving trajectory information, driving environment video, and other vehicle trip data. In this embodiment, the detailed information can be presented in plain text or in a combination of text and images; this embodiment does not impose any limitations.

[0089] For example, a user can click Figure 2 The first historical trip report in the historical trip overview interface shown will be accessed by the in-vehicle terminal in response to the user's viewing command. The in-vehicle terminal will then load and display the detailed information of that historical trip report. For example, Figure 4 This is a schematic diagram of a report details interface provided in an embodiment of this application. Figure 4 As shown, when the user clicks Figure 2 After the first historical trip report in the historical trip overview interface shown, the vehicle terminal can display, as follows: Figure 4 The report details interface shown will display the detailed information of this historical trip report. Figure 4 In the details, information such as route name, travel time, mileage, total travel time, average speed, maximum speed, and maximum G-force are presented in text form. The route trajectory map is presented in a combination of text and images. Hyperlinks to the driving trajectory playback video are presented as "icon" 44 (clicking "icon" 44 will play the driving trajectory playback video on the in-vehicle terminal). Hyperlinks to the driving environment playback video are presented as "icon" 45 (clicking "icon" 45 will play the driving environment playback video on the in-vehicle terminal).

[0090] It should be noted that, Figure 4 This is merely an example of a report details interface and should not be considered a limitation of this application. In practical applications, the details may be presented in other forms, and appropriate UI interfaces can be designed for them.

[0091] It should be noted that the interface size of the vehicle terminal is limited. In some examples, a single report details interface may not be able to display all the details in the historical trip report at the same time. All the details in the historical trip report can be viewed by pulling down the progress bar, etc. This application embodiment does not impose any restrictions.

[0092] The vehicle trip information processing method provided in this application displays historical trip reports in a list format according to a preset format in the historical trip overview interface; wherein the preset format is a preset plain text format or a preset combined text and graphics format; and in response to the user's command to view the historical trip report, displays detailed information of the historical trip report in the report details interface; wherein the detailed information describes the trip data of the vehicle during the completion of the travel route; based on this, a more intuitive and clearer historical trip report is displayed. In this way, the vehicle terminal can also quickly respond to the user's viewing command, provide comprehensive trip data, help users understand the trip situation in depth, and complete the trip review more quickly. The combined text and graphics display method also makes the trip data more intuitive and easy to understand, improving the user experience.

[0093] Optionally, based on the above embodiments, in some possible embodiments, one or more of the following functional controls may also be displayed in the historical trip overview interface: sorting control, filtering control, and deletion control; the vehicle terminal may also execute one or more of steps S01 to S03:

[0094] S01. In response to the user's touch operation on the sorting control, sort the historical trip reports that can be displayed in the historical trip overview interface according to the preset sorting rules, and display the sorted historical trip reports.

[0095] S02. In response to the user's touch operation on the filter control, filter the historical trip reports that can be displayed in the historical trip overview interface according to the preset filter conditions, and display the filtered historical trip reports.

[0096] S03. In response to the user's touch operation on the delete control, delete the historical trip report selected by the user.

[0097] For example, in the historical itinerary overview interface, in addition to displaying an overview list of historical itinerary reports, one or more functional controls such as sorting controls, filtering controls, and delete controls can also be displayed. The sorting control is used to sort the historical itinerary reports; the filtering control is used to filter the historical itinerary reports; and the delete control is used to delete the selected historical itinerary reports. These functional controls are usually placed at the top or side of the interface for easy user operation. For example, they can be like... Figure 2 and Figure 3 As shown, it is placed at the top of the interface.

[0098] The sorting control can be a drop-down menu, a group of buttons, or other forms. Users can choose different sorting rules, such as ascending or descending by the total length of the trip, ascending or descending by the trip time, ascending or descending by the rating, etc. Users can click the sorting control in the historical trip overview interface, select a sorting rule, and the vehicle terminal will sort the historical trip reports that can be displayed in the historical trip overview interface according to the sorting rule selected by the user. The sorted historical trip reports will be re-rendered to the interface, and users can view the sorted results.

[0099] The filter control can be a checkbox, drop-down menu, or other form, allowing users to select different filter criteria, such as filtering by geographical location information of the travel route, filtering by route name, filtering by activity name, etc. Users can click the filter control in the historical trip overview interface to select a filter criterion. The in-vehicle terminal will then filter the historical trip reports displayed in the historical trip overview interface according to the user's selected filter criteria. The filtered historical trip reports will be re-rendered onto the interface, and users can view the filtered results.

[0100] The delete control can be a button or icon, etc. Users can select one or more trip reports to delete. Users can select one or more trip reports in the historical trip overview interface, click the delete control, and the vehicle terminal can pop up a confirmation dialog box to prompt the user to confirm the deletion operation. After the user confirms the deletion operation, the vehicle terminal will delete the selected historical trip reports from the database or cloud, update the historical trip overview interface, and remove the deleted trip reports.

[0101] by Figure 2 For example, the historical trip overview interface 20 can also display a sorting control 21, a filtering control 22, and a deletion control 23. Users can click the sorting control 21 to sort the historical trip reports, click the filtering control 22 to filter the historical trip reports, and click the deletion control 23 to delete the historical trip reports. Based on this, the in-vehicle terminal can not only quickly respond to users' sorting, filtering, and deletion operations and ensure smooth interface switching, but also make it easier for users to find and manage historical trip reports through the sorting, filtering, and deletion functions, realizing multi-faceted management of historical trip reports and improving the user experience.

[0102] Optionally, based on the above embodiments, in some possible embodiments, in addition to displaying the detailed information of the historical trip report, the report details interface may also display one or more of the following functional controls: sharing control, rating control; the vehicle terminal may also execute one or more of steps S001 to S002:

[0103] S001. In response to a user's touch operation on the share control, generate a share link for the historical itinerary report and send the share link to the target platform; wherein, the share link is used by other users to view the historical itinerary report on the target platform;

[0104] S002. In response to the user's touch operation on the evaluation control, display the evaluation interface of the historical trip report, and after the user completes the evaluation, display the user's evaluation of the historical trip report in the report details interface.

[0105] For example, in addition to displaying detailed information about historical trip reports, the report details interface can also display functional controls such as sharing controls and rating controls for user use. The sharing controls are used to control the link for generating and sharing trip reports, while the rating controls are used by users to rate the trip reports.

[0106] When a user clicks or touches the share control, the in-vehicle terminal creates a link to the historical trip report indicated by the user and sends the generated link to the target platform selected by the user, such as social media such as a club for the corresponding brand of vehicle, so that other users can view the trip report through that platform.

[0107] When a user clicks or touches the rating control, the in-vehicle terminal can pop up or switch to an interface allowing the user to rate the trip report. After the user completes the rating on the rating interface, the in-vehicle terminal will save the rating and display it in the report details interface so that the user and other viewers can see the rating. In some examples, the user's rating may also be presented in the details of the travel route corresponding to the historical trip report, so that the user can see the ratings of other users through the details interface of the travel route. This application embodiment does not impose any limitations.

[0108] In addition, the report details interface can also be configured with control functions such as modification, deletion, editing, re-departure, and video export, according to actual needs. This allows users to further manage historical travel reports through these control functions, thereby improving user convenience and enhancing user experience.

[0109] by Figure 4For example, the report details interface 40 can also display a "Restart" control 41, a "Share" control 42, and a "Rating" control 43. Users can click the "Restart" control 41 to restart based on the travel route corresponding to the historical travel report, click the "Share" control 42 to share the historical travel report, and click the "Rating" control 43 to rate the historical travel report. This enhances the interactivity between users and the travel report, allowing users to easily share information and express their opinions on the trip. This interactive design not only improves the user experience but also promotes information dissemination and feedback collection.

[0110] It should be noted that the historical trip overview interface, report details interface, and other interfaces involved in the embodiments of this application are only functional divisions. In actual scenarios, the information displayed in each interface can be displayed simultaneously on the vehicle terminal according to actual needs, and this embodiment of the application does not impose any restrictions. In addition, the various functional controls involved in the embodiments of this application can also be presented in the interface in a variety of different ways, such as in the form of "specific icons", "specific symbols", text, etc. Each interface can also be set with functional controls such as modification controls, deletion controls, and editing controls according to actual needs, so as to allow users to further manage historical travel reports through these functional controls, thereby improving the user's operational convenience and enhancing the user experience. This embodiment of the application does not impose any restrictions in this regard.

[0111] Figure 5 This is a flowchart illustrating another method for processing vehicle trip information provided in this application. This embodiment describes how to generate, display, and manage historical trip reports. The method in this embodiment can be implemented using software, hardware, or a combination of both.

[0112] like Figure 5 As shown, the vehicle trip information processing method provided in this embodiment may include:

[0113] S501, in response to the user's travel instructions, acquires the vehicle's trip data while the vehicle is driving based on the navigation information corresponding to the travel route.

[0114] S502. After the trip is finalized, a historical trip report of the travel route is generated based on the trip data.

[0115] S503. In the historical itinerary overview interface, the historical itinerary report is displayed in a list format according to the preset format; wherein, the preset format is either a preset plain text format or a preset combined text and image format.

[0116] S504. In response to the user's command to view the historical trip report, the detailed information of the historical trip report is displayed on the report details interface; wherein, the detailed information is used to describe the trip data of the vehicle during the completion of the trip route.

[0117] It should be noted that the specific implementation process of this embodiment can be referred to the description in other embodiments of this application, and will not be repeated here.

[0118] The vehicle trip information processing method provided in this embodiment, in response to the user's travel instructions, acquires the vehicle's trip data during the vehicle's journey based on navigation information corresponding to the travel route. After the trip is completed, a historical trip report is generated based on the trip data. Furthermore, the historical trip report is displayed in a list format according to a preset format on the historical trip overview interface. In response to the user's instruction to view the historical trip report, detailed information of the historical trip report is displayed on the report details interface. This solution acquires vehicle trip data promptly and accurately during vehicle operation, and subsequently generates accurate historical trip reports, presenting them in a more intuitive and clear manner. This not only helps users gain a deeper understanding of the trip but also makes the trip data more intuitive and easy to understand, improving the user experience.

[0119] Figure 6 This is a schematic diagram of a vehicle trip information processing device provided in this application. Figure 6 As shown, the vehicle trip information processing device 60 provided in this embodiment includes a first processing unit 601 and a second processing unit 602.

[0120] The first processing unit 601 is used to display historical itinerary reports in a list format according to a preset format in the historical itinerary overview interface; wherein the preset format is a preset plain text format or a preset combined text and image format.

[0121] The second processing unit 602 is used to respond to the user's command to view the historical trip report and display the detailed information of the historical trip report in the report details interface; wherein, the detailed information is used to describe the trip data of the vehicle in the process of completing the trip route.

[0122] In one possible implementation, the historical itinerary overview interface also displays one or more of the following functional controls: sorting control, filtering control, and deletion control; the second processing unit 602 is further configured to:

[0123] In response to the user's touch operation on the sorting control, the historical trip reports that can be displayed in the historical trip overview interface are sorted according to the preset sorting rules, and the sorted historical trip reports are displayed.

[0124] In response to the user's touch operation on the filter control, the historical trip reports that can be displayed in the historical trip overview interface are filtered according to the preset filter conditions, and the filtered historical trip reports are displayed.

[0125] In response to a user's touch operation on the delete control, delete the historical trip report selected by the user.

[0126] In one possible implementation, the report details interface also displays one or more of the following functional controls: a sharing control and a rating control; the second processing unit 602 is further configured to:

[0127] In response to a user's touch operation on the share control, a share link for the historical itinerary report is generated and sent to the target platform; the share link is used by other users to view the historical itinerary report on the target platform.

[0128] In response to the user's touch operation on the rating control, the rating interface of the historical trip report is displayed, and after the user completes the rating, the user's rating of the historical trip report is displayed in the report details interface.

[0129] In one possible implementation, the first processing unit 601 is further configured to:

[0130] Before displaying historical trip reports in a list format according to a preset format, in response to the user's travel instructions, the vehicle's trip data is acquired as the vehicle completes its journey based on the navigation information corresponding to the travel route.

[0131] After the itinerary is finalized, a historical itinerary report is generated based on the itinerary data.

[0132] In one possible implementation, the first processing unit 601 is further configured to:

[0133] Before responding to the user's travel instructions, it receives the user's settings instructions and determines the trip data that needs to be collected during the journey.

[0134] In one possible implementation, the trip data includes one or more of the following information: activity name, route name, mileage information, time consumption information, vehicle speed information, acceleration information, user information, vehicle body data information, driving trajectory information, and driving environment video.

[0135] In one possible implementation, when the trip data includes driving trajectory information, the historical trip report includes a driving trajectory playback video; the first processing unit 601 is further configured to:

[0136] Generate a driving trajectory video based on the driving trajectory information;

[0137] A data layer is constructed on the driving trajectory video, and the target layer data is filled into the data layer to obtain the driving trajectory playback video; wherein, the target layer data includes at least one of the following: activity name, route name, mileage information, time consumption information, vehicle speed information, acceleration information, user information, and vehicle body data information;

[0138] Hyperlinks to the driving trajectory playback videos are recorded in the travel history report of the route.

[0139] In one possible implementation, when the trip data includes driving environment video, the historical trip report includes driving environment playback video; the first processing unit 601 is further configured to:

[0140] A data layer is constructed on the driving environment video, and the target layer data is filled into the data layer to obtain the driving environment playback video; wherein, the target layer data includes at least one of the following: activity name, route name, mileage information, time consumption information, vehicle speed information, acceleration information, user information, and vehicle body data information;

[0141] Hyperlinks to driving environment playback videos are recorded in the historical trip report of the travel route.

[0142] The vehicle trip information processing device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0143] It should be noted that the division of the various modules in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. These modules can be implemented entirely in software via processing element calls; they can be fully implemented in hardware; or some modules can be implemented in software via processing element calls, while others are implemented in hardware. Furthermore, they can be stored as program code in the device's memory, and the data processing modules can be called and executed by a specific processing element. The implementation of other modules is similar. These modules can be fully or partially integrated together, or implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. During implementation, each step of the above method or each of the above modules can be completed through integrated logic circuits in the hardware of the processor element or through software instructions.

[0144] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 7As shown, the electronic device 70 provided in this embodiment includes at least one processor 701 and a memory 702. Optionally, the device 70 further includes a communication component 703. The processor 701, memory 702, and communication component 703 are connected via a bus 704.

[0145] In a specific implementation, at least one processor 701 executes computer execution instructions stored in memory 702, causing at least one processor 701 to perform the above-described method.

[0146] The specific implementation process of processor 701 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0147] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0148] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0149] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0150] This application also provides a vehicle that includes the electronic devices described above.

[0151] It should be noted that the solution proposed in this application can be applied not only to automobiles, but also to other terminal devices such as mobile phones.

[0152] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0153] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0154] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0155] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0156] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0157] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0158] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0159] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0160] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0161] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A method for processing vehicle trip information, characterized in that, The method includes: In the historical itinerary overview interface, historical itinerary reports are displayed in a list format according to a preset format; wherein, the preset format is a preset plain text format or a preset combined text and image format; In response to the user's instruction to view the historical trip report, the detailed information of the historical trip report is displayed in the report details interface; wherein, the detailed information is used to describe the trip data of the vehicle during the completion of the travel route.

2. The method according to claim 1, characterized in that, The historical itinerary overview interface also displays one or more of the following functional controls: sorting control, filtering control, and deletion control; the method further includes: In response to a user's touch operation on the sorting control, the historical trip reports that can be displayed in the historical trip overview interface are sorted according to a preset sorting rule, and the sorted historical trip reports are displayed. In response to a user's touch operation on the filtering control, the historical trip reports that can be displayed in the historical trip overview interface are filtered according to preset filtering conditions, and the filtered historical trip reports are displayed. In response to a user's touch operation on the delete control, the user-selected historical trip report is deleted.

3. The method according to claim 1, characterized in that, The report details interface also displays one or more of the following functional controls: a share control and a rating control; the method further includes: In response to a user's touch operation on the sharing control, a sharing link for the historical itinerary report is generated and sent to the target platform; wherein, the sharing link is used by other users to view the historical itinerary report on the target platform; In response to a user's touch operation on the evaluation control, the evaluation interface of the historical trip report is displayed, and after the user completes the evaluation, the user's evaluation of the historical trip report is displayed in the report details interface.

4. The method according to any one of claims 1-3, characterized in that, Before displaying the historical itinerary report in a list format according to a preset format, the method further includes: In response to the user's travel instructions, the vehicle's travel data is acquired during the process of the vehicle completing its journey based on the navigation information corresponding to the travel route; After the trip is finalized, a historical trip report of the travel route is generated based on the trip data.

5. The method according to claim 4, characterized in that, Prior to responding to the user's travel instructions, the method further includes: It receives user settings instructions and determines the trip data to be collected during the driving process.

6. The method according to claim 5, characterized in that, The trip data includes one or more of the following: activity name, route name, mileage information, time consumption information, vehicle speed information, acceleration information, user information, vehicle data information, driving trajectory information, and driving environment video.

7. The method according to claim 6, characterized in that, When the trip data includes driving trajectory information, the historical trip report includes a driving trajectory playback video; generating the historical trip report of the travel route based on the trip data includes: Based on the driving trajectory information, a driving trajectory video is generated; A data layer is constructed on the driving trajectory video, and target layer data is filled into the data layer to obtain the driving trajectory playback video; wherein, the target layer data includes at least one of the activity name, the route name, the mileage information, the time consumption information, the vehicle speed information, the acceleration information, the user information, and the vehicle body data information; The hyperlink to the playback video of the driving trajectory is recorded in the historical trip report of the travel route.

8. The method according to claim 6, characterized in that, When the trip data includes driving environment video, the historical trip report includes driving environment playback video; generating the historical trip report of the travel route based on the trip data includes: A data layer is constructed on the driving environment video, and target layer data is filled into the data layer to obtain the driving environment playback video; wherein, the target layer data includes at least one of the activity name, the route name, the mileage information, the time consumption information, the vehicle speed information, the acceleration information, the user information, and the vehicle body data information; The hyperlink to the driving environment playback video is recorded in the historical trip report of the travel route.

9. A device for processing vehicle trip information, characterized in that, The device includes: The first processing unit is used to display the historical itinerary report in a list format according to a preset format in the historical itinerary overview interface; wherein, the preset format is a preset plain text format or a preset combined text and image format; The second processing unit is configured to respond to the user's instruction to view the historical trip report and display detailed information of the historical trip report in the report details interface; wherein the detailed information is used to describe the trip data of the vehicle during the completion of the travel route.

10. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-8.

11. A car, characterized in that, The vehicle includes the electronic equipment as described in claim 10.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-8.

13. A computer program product comprising a computer program that, when executed by a processor, implements the method of any one of claims 1-8.

Images