Route data processing method and device
By generating a route preview interface and preset function controls, the problem of poor user experience in traditional navigation systems is solved, and personalized route management and ease of operation are achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- WUHAN LOTUS CARS CO LTD
- Filing Date
- 2024-10-18
- Publication Date
- 2026-04-21
AI Technical Summary
Traditional navigation systems lack personalization and flexibility, preventing users from intuitively previewing route details and lacking further management functions for newly created routes, resulting in a poor user experience.
A method for processing route data is provided to generate a route preview interface for travel routes, which includes detailed information and preset function controls. Users can perform operations such as saving, publishing, modifying, and deleting routes through touch operations, and the method also supports filtering, sorting, favorites, and viewing of all routes.
It enables users to create and manage personalized travel routes more intuitively, improving ease of operation and user experience, and meeting users' personalized needs.
Smart Images

Figure CN121898448A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of intelligent driving technology, and in particular to a method and apparatus for processing route data. Background Technology
[0002] With the development and popularization of intelligent transportation systems, more and more users rely on in-vehicle terminals or other terminal devices such as mobile phone navigation systems to plan and manage travel routes.
[0003] However, traditional navigation systems typically only offer preset routes, limiting users to a limited selection and lacking personalization and flexibility. Furthermore, existing navigation systems offer relatively simple route creation and management functions. Users cannot visually preview route details when creating routes, and there is a lack of further management of newly created routes. This fails to meet users' personalized creation needs and results in a subpar user experience.
[0004] Therefore, there is an urgent need for a new method for processing route data so that users can create and manage routes more intuitively, thereby meeting users' personalized needs and improving user experience. Summary of the Invention
[0005] This application provides a method and apparatus for processing route data, which enables more intuitive route creation and management, thereby meeting users' personalized needs and improving user experience.
[0006] In a first aspect, embodiments of this application provide a method for processing route data, the method comprising:
[0007] In response to the user's creation command, a travel route is generated based on the route-related information input by the user, and a route preview interface of the travel route is displayed; wherein, the route-related information is information related to the generation of the travel route, and the route preview interface includes detailed information of the travel route and preset function controls;
[0008] The travel route is processed in response to a user's touch operation on the preset function control.
[0009] In one possible implementation, the route-related information includes required information and optional information. The required information includes at least one of the following: route start point, route end point, route name, route description, and route image. The optional information includes waypoints.
[0010] In one possible implementation, the preset function control includes a save control and / or a publish control; the process of processing the travel route in response to a user's touch operation on the preset function control includes:
[0011] In response to a user's touch operation on the save control, the travel route is saved to a first file; the first file is a local file used to save user-created routes.
[0012] And / or, in response to a user's touch operation on the publishing control, the travel route is published to a second file; the second file is a file in the cloud used to store the user-published route, and the cloud is used to share the travel route with other users in response to an approval instruction for the travel route.
[0013] In one possible implementation, the method further includes:
[0014] Once the published travel route is approved, it will be displayed in the route recommendation interface using a preset display method.
[0015] In one possible implementation, the method further includes:
[0016] In response to a user's touch operation on a travel route in the route recommendation interface, detailed information about the travel route is displayed.
[0017] In one possible implementation, the route recommendation interface further displays one or more of the following functional controls: edit control, delete control, favorites control, sort control, filter control, and error reporting control; the method further includes:
[0018] In response to a user's touch operation on the modification control, an editing interface for the travel route is displayed; the editing interface is used by the user to edit route-related information of the travel route.
[0019] In response to a user's touch operation on the delete control, the travel route is deleted;
[0020] In response to a user's touch operation on the favorites control, the travel route is saved to a third file; the third file is a local file used to save the user's saved routes.
[0021] In response to a user's touch operation on the sorting control, all routes that can be displayed in the route recommendation interface are sorted according to a preset sorting rule;
[0022] In response to a user's touch operation on the filtering control, all routes that can be displayed in the route recommendation interface are filtered according to preset filtering conditions;
[0023] In response to a user's touch operation on the error reporting control, a route error reporting interface for the travel route is displayed; the route error reporting interface is used by the user to upload error information about the travel route.
[0024] In one possible implementation, the preset sorting rule includes any one of the following: total route length, estimated travel time, and distance between the vehicle's current location and the route start point; the preset filtering conditions include geographic location information and / or route feature information.
[0025] In one possible implementation, the detailed information includes one or more of the following: route trajectory information, route name, geographical location information, altitude information, creator information, total route length, estimated travel time, route rating information, approval progress information, mode of transportation, and distance between the vehicle's current location and the route starting point.
[0026] Secondly, embodiments of this application provide a route data processing apparatus, the apparatus comprising:
[0027] The first processing unit is configured to respond to the user's creation instruction, generate a travel route based on the route-related information input by the user, and display a route preview interface for the travel route; wherein, the route-related information is information related to the generation of the travel route, and the route preview interface includes detailed information of the travel route and preset function controls;
[0028] The second processing unit is used to process the travel route in response to the user's touch operation on the preset function control.
[0029] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;
[0030] The memory stores computer-executed instructions;
[0031] 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.
[0032] Fourthly, embodiments of this application provide an automobile that includes the electronic equipment described in the third aspect.
[0033] 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.
[0034] 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.
[0035] The route data processing method and apparatus provided in this application, in response to a user's creation command, can automatically generate a travel route based on the route-related information input by the user, and display a route preview interface containing detailed information about the travel route and preset functional controls. This processing method reduces the complexity of users manually planning routes. Users can not only input route-related information according to their own needs to generate personalized travel routes, thereby adapting to the needs of different users and providing customized services, but also enable users to complete the creation of travel routes more intuitively. Furthermore, based on this application, various preset functional controls can be designed to be displayed on the interface to achieve better functional scalability. Based on the preset functional controls, users can also perform diversified processing on the travel route, which not only improves the convenience and efficiency of operation, but also improves the user experience. Attached Figure Description
[0036] 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.
[0037] Figure 1 A flowchart illustrating a route data processing method provided in this application;
[0038] Figure 2 A schematic diagram of a route creation interface provided in an embodiment of this application;
[0039] Figure 3 A schematic diagram of a route preview interface provided in an embodiment of this application;
[0040] Figure 4 A schematic diagram of a route details interface provided in an embodiment of this application;
[0041] Figure 5 A schematic diagram of the structure of the route data processing device provided in this application;
[0042] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.
[0043] 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
[0044] 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.
[0045] 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.
[0046] With the development of navigation technology, users' needs for planning and managing travel routes are increasing. However, current methods for generating and processing travel routes often suffer from problems such as complex operations and poor user experience. Users cannot intuitively preview the route details of newly created routes, and the system lacks further management functions for newly created routes, failing to meet users' personalized route creation needs and resulting in a subpar user experience.
[0047] Therefore, this application provides a method for processing route data, which supports users to manually create routes. After creating a route, a route preview interface will be displayed so that users can more intuitively understand the information of the newly created route. In addition, for user-created travel routes, it also supports functions such as saving to local, publishing to the cloud, modifying, deleting, and reporting errors. It also supports functions such as filtering, sorting, collecting, viewing, and recommending all travel routes, which can not only meet the personalized needs of users, but also improve the user experience.
[0048] The execution subject of the route data 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 description takes an in-vehicle terminal as the execution subject.
[0049] The following provides examples illustrating the application scenarios of the route data processing method provided in this application.
[0050] For example, in this application scenario, if a user wants to create and process a new travel route, they can operate on the interface displayed on the in-vehicle terminal, issuing a creation command. The in-vehicle terminal will respond to the user's creation command, generate the travel route based on the route-related information input by the user, and display a route preview interface. The route-related information refers to information related to the generated travel route. The route preview interface displays detailed information about the newly created travel route and preset function controls. The user can further manipulate the preset function controls in the route preview interface to manage the newly created travel route. Correspondingly, the in-vehicle terminal will also respond to the user's touch operation on the preset function controls, processing the travel route, thereby realizing the processing of the newly created travel route.
[0051] 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.
[0052] 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.
[0053] Figure 1 This is a flowchart illustrating a route data processing method provided in this application. The embodiments of this application describe how to create and manage travel routes. The method in this embodiment can be implemented through software, hardware, or a combination of both.
[0054] like Figure 1 As shown, the route data processing method provided in this application embodiment may include:
[0055] S101. In response to the user's creation command, generate a travel route based on the route-related information input by the user, and display a route preview interface for the travel route; wherein, the route-related information is information related to the generation of the travel route, and the route preview interface includes detailed information of the travel route and preset function controls.
[0056] For example, when a user wants to create a new travel route, they can issue a creation command to the in-vehicle terminal according to the instructions displayed on the interface. This command can be input in various ways, such as clicking the "Create Route" control on the in-vehicle terminal's interface, issuing a voice command, or using a gesture. After receiving the creation command, the in-vehicle terminal can enter the route creation interface. This interface may display windows for the user to input route-related information. The user can then input this information, allowing the in-vehicle terminal to obtain it and generate a travel route based on the input.
[0057] Information related to generating travel routes can be referred to as route-related information. To ensure that the vehicle terminal can generate valid travel routes, this route-related information can be divided into required information and optional information.
[0058] Required information refers to the basic information that users must provide to generate a travel route. This information may include at least one of the following: route start point, route end point, route name, route description, and route image. The route start point is the user's departure point, which can be specified by entering an address, selecting a location on a map, or using the current geographic location. The route end point is the user's desired destination, which can also be specified by entering an address or selecting a location on a map. The route name is an identifier assigned to the route by the user. Users can manually enter a name, such as "Commuting Route," "Weekend Getaway," or "Event Route," etc. The route name helps users distinguish and identify multiple routes when saving and managing them. The route description is a brief description of the route. Users can manually enter a text description, such as "This is a scenic route that avoids highways," or "This is a route related to an event or team activity," etc. The route description provides additional route identification information, helping users understand and remember the characteristics and purpose of the route. Route images refer to images related to the travel route, such as map screenshots, photos of scenery along the way, and route trajectory images. Users can upload image files or select from the image library. Route images provide visual references and enhance the visualization of the route.
[0059] Optional information refers to supplementary information that users can choose to provide. While not essential for generating a travel route, this information can further optimize and enrich the route's content. For example, it can include waypoints. Waypoints are intermediate locations that users wish to pass through during their trip. Users can specify one or more waypoints by entering addresses, selecting locations on a map, etc. Waypoints are used to adjust and optimize the travel route; for example, a user might want to pass through a tourist attraction, restaurant, or gas station on their journey from the starting point to the destination.
[0060] In addition, route-related information may also include other information, such as mode of transportation (walking, driving, cycling or public transportation, etc., in this application it is generally driving), travel time, other preferences (such as whether to avoid toll roads, whether to prioritize highways, etc.). Users can input route-related information in a variety of different ways, and this application embodiment does not limit it.
[0061] By clearly distinguishing between required and optional information in route-related information, the generated travel routes can be ensured to have basic validity, while allowing users to personalize and optimize them according to their individual needs. This not only improves the user experience but also ensures the efficiency and accuracy of the route generation process.
[0062] For example, Figure 2 This is a schematic diagram of a route creation interface provided in an embodiment of this application. Figure 2 As shown, the route creation interface 20 displays windows for users to input relevant route information (only a portion is shown in the figure). Users can input route-related information through these windows. After the user inputs the route-related information, clicking the "Submit" control 21 allows the vehicle terminal to retrieve relevant geographic information and traffic data from the map database based on the user's input. Then, based on the route start point, route end point, and waypoints, it calculates multiple possible routes and determines the optimal route using a preset optimization algorithm, thereby generating the travel route and entering the route preview interface.
[0063] The generated travel route should include detailed information. In this embodiment, after the vehicle terminal generates the travel route based on the route-related information, it will display a route preview interface. The route preview interface can display detailed information about the travel route and preset function controls, so that users can clearly understand the route details and manage the route more conveniently.
[0064] Optionally, in one possible embodiment, the detailed information of the travel route displayed in the route preview interface may include one or more of the following: route trajectory information, route name, geographical location information, altitude information, creator information, total route length, estimated travel time, route rating information, approval progress information, mode of transportation, and distance between the vehicle's current location and the route starting point.
[0065] It should be noted that the detailed information of the travel route is determined directly or indirectly through the route-related information input by the user. The route trajectory information refers to the specific path of the travel route on the map, which may include the driving direction and location of each segment. It provides a visual representation of the travel route, allowing users to intuitively see the specific path from the starting point to the destination. The trajectory information is usually displayed on the map in the form of a broken line or arrow. Optionally, the route trajectory information can be presented in 2D or 3D, and the user can choose the corresponding presentation effect when generating the travel route. The route name can be an identifier name specified by the user for the travel route. Geographical location information may include the specific geographic coordinates (such as latitude and longitude) of the route's starting point, ending point, and waypoints, providing accurate geographic positioning to ensure the accuracy and navigability of the route. Altitude information refers to the altitude data of various points along the travel route. For certain specific travel needs (such as travel, competitions, etc.), altitude information can help users understand the undulations and difficulty of the route. Creator information refers to relevant information about the user who generated the travel route, such as username or user ID. This information is used to identify and track the route creator, especially in sharing and collaborative scenarios, helping other users understand the route's origin and credibility. Total route length refers to the total distance from the starting point to the destination, usually measured in kilometers or miles. It provides basic route length information, helping users assess travel distance and time. Estimated travel time is the estimated time required to travel from the starting point to the destination based on the route and traffic conditions. This helps users plan their travel time reasonably and avoid delays. Estimated travel time typically considers factors such as real-time traffic information, road conditions, and travel mode, and its value may vary at different times. Route rating information refers to other users' evaluations and scores of the route. It provides feedback on route quality and experience, helping other users choose the best route. Rating information may include star ratings and reviews. Approval progress information refers to the progress status of the official approval process when a user wants to publish the travel route on a public platform. It displays the approval status of the travel route, such as "Pending Approval," "Approved," or "Rejected." The mode of transportation refers to the user's chosen means of transport, such as walking, driving, cycling, or public transportation (in this application, it is generally driving). This affects route planning and estimated travel time; different modes of transportation may result in different route choices and time estimates. The distance between the vehicle's current location and the route's starting point refers to the straight-line distance or driving distance between the user's current location and the starting point of the route. This helps the user understand the distance from their current location to the route's starting point, facilitating navigation to the starting point and beginning their journey.
[0066] For example, assuming a travel route from point A to point B for a competition on a certain day is generated, the in-vehicle terminal can display the following in the route preview interface: route trajectory information (displaying the specific path from point A to point B on a map, including the direction of travel for each segment); route name (displayed as "Competition Route on XX Day"); geographic location information (displaying the latitude and longitude coordinates of point A, point B, and transit points (such as coffee shops); altitude information (displaying the altitude data of various points along the route, such as point A, point B, and transit points); and creator information (displaying the creator's username). Username (e.g., "User123"); total route length (displaying a total distance of 30 kilometers); estimated travel time (displaying a current estimated travel time of 30 minutes, taking into account real-time traffic conditions); route rating information (displaying other users' ratings of the route as 4.5 stars, with comments such as "smooth route, avoiding congested sections"); approval progress information (displaying "approved"); mode of transportation (displaying "driving"); distance between the vehicle's current location and the route's starting point (displaying that the user's current location is 500 meters from the starting point A), etc.
[0067] By displaying this detailed information in the route preview interface, users can be provided with a comprehensive route description and reference, helping them to better plan and execute their trips. This information not only improves the usability and accuracy of the routes but also enhances the user experience and satisfaction.
[0068] For example, the preset functional controls displayed in the route preview interface are interactive elements that users can interact with through touch operations (such as clicking, swiping, long-pressing, etc.). Optionally, in one possible embodiment, the preset functional controls displayed in the route preview interface may include one or more functional controls such as save controls and publish controls, which users can click to further process the travel route. The save control is used to save the generated travel route to the user's account for later use; the share control is used to generate a shareable link or QR code for the travel route, allowing the user to share the route with others.
[0069] In addition, the preset function controls in the route preview interface may also include modification controls, deletion controls, editing controls, navigation controls, etc. This application embodiment does not impose any restrictions, allowing users to further process the travel route through these function controls.
[0070] This application does not restrict how the route preview interface presents detailed information about the travel route and preset functional controls; a suitable UI interface can be designed according to actual needs.
[0071] The design described in this application simplifies the steps users take when creating and processing travel routes. Users can not only quickly create travel routes, but also preview route details more intuitively, and further process travel routes through preset function controls, thus meeting diverse travel needs and improving user experience.
[0072] S102. Responding to the user's touch operation on the preset function control, process the travel route.
[0073] For example, a user can interact with preset function controls displayed on the route preview interface of a travel route. The in-vehicle terminal can detect the user's touch operation and thus respond to the user's touch operation on the preset function control to process the travel route. Here, touch operation refers to the user's behavior of executing certain instructions by touching the screen. Touch operation can be click, swipe, long press, etc., and this application embodiment does not impose any limitations.
[0074] Optionally, in one possible embodiment, when the preset function control is a save control, the vehicle terminal can respond to the user's touch operation on the save control and save the travel route to a first file, wherein the first file is a local file used to save user-created routes. For example, when the user clicks the save control, the vehicle terminal can save the currently generated travel route to the user's account, and the saved content may include detailed information about the travel route such as the route start point, route end point, waypoints, mode of transportation, and estimated travel time.
[0075] Optionally, in one possible embodiment, when the preset function control is a publish control, the in-vehicle terminal can respond to the user's touch operation on the publish control and publish the travel route to a second file. The second file is a file used by the cloud to store the user-published route. The cloud is used to share the travel route with other users in response to the approval instruction. For example, when the user clicks the share control, the in-vehicle terminal can generate a share link and send the link to the cloud. The cloud will then share the travel route with other users via social media, SMS, email, etc., when the travel route is approved, so that other users can use the travel route. Approval of the travel route is to ensure its authenticity and accuracy. Furthermore, the in-vehicle terminal can also share the travel route with other users by publishing it to a public platform. The public platform can be navigation software or other social software; this embodiment does not impose limitations.
[0076] In this embodiment, the vehicle terminal can respond to the user's touch operation and process the travel route accordingly. This not only improves the user's ease of operation but also enhances the user experience, enabling the user to easily manage and use the travel route.
[0077] For example, Figure 3 This is a schematic diagram of a route preview interface provided in an embodiment of this application. Figure 3 As shown, the route preview interface 30 displays detailed information about the travel route and preset function controls (only a portion is shown in the figure). Based on interface 30, users can view the detailed information of newly created travel routes. When a user clicks the "Save" control 31, the in-vehicle terminal can save the newly created travel route to "My Created Routes". When a user clicks the "Publish" control 32, the in-vehicle terminal can share the newly created travel route with other users.
[0078] The route data processing method provided in this application, in response to a user's creation command, can automatically generate a travel route based on the route-related information input by the user, and display a route preview interface containing detailed information about the travel route and preset functional controls. This processing method reduces the complexity of users manually planning routes. Users can not only input route-related information according to their own needs to generate personalized travel routes, thereby adapting to the needs of different users and providing customized services, but also enable users to complete the creation of travel routes more intuitively. Furthermore, based on this application, various preset functional controls can be designed to be displayed on the interface to achieve better functional scalability. Based on the preset functional controls, users can also perform diversified processing on the travel route, which not only improves the convenience and efficiency of operation, but also enhances the user experience.
[0079] For example, in some other possible embodiments, when the in-vehicle terminal publishes a travel route to a public platform for sharing with other users in response to a user's touch operation on the publishing control, the travel route needs to be sent to the cloud first. After approval, the cloud publishes it to the public platform. In this scenario, once the published travel route is approved, the in-vehicle terminal can display the travel route in a preset display mode on the route recommendation interface so that other users can view and use the travel route. This application does not limit the display method of the travel route; for example, the travel route can be displayed as a list on the route recommendation interface.
[0080] Understandably, the travel routes displayed on the route recommendation interface can include routes created and published by individual users, as well as routes set by the official authorities.
[0081] The user-created travel routes displayed on the route recommendation interface can be viewed and further processed by the user. Optionally, the in-vehicle terminal can respond to the user's touch operation on the travel route in the route recommendation interface and display detailed information about the route. For example, the user can click on a travel route in the route recommendation interface to view its detailed information.
[0082] It should be noted that after a travel route is successfully created, users can choose to travel individually or in a car group after entering the route details interface. If a user clicks on individual travel, the in-vehicle terminal can initiate navigation to start the trip; if a user clicks on car group travel, the in-vehicle terminal can jump to the car group activity interface to participate in car group activities.
[0083] Optionally, in one possible embodiment, the route recommendation interface may also display one or more of the following functional controls: edit control, delete control, favorites control, sort control, filter control, and error reporting control. The vehicle terminal may also:
[0084] In response to a user's touch operation on the modification control, the route editing interface is displayed; the editing interface is used by the user to edit route-related information.
[0085] Delete the travel route in response to the user's touch operation on the delete control;
[0086] In response to a user's touch operation on the favorites control, the travel route is saved to a third file; the third file is a local file used to store the user's saved routes.
[0087] In response to the user's touch operation on the sorting control, all routes that can be displayed in the route recommendation interface are sorted according to the preset sorting rules.
[0088] In response to the user's touch operation on the filter control, the system filters all routes that can be displayed in the route recommendation interface according to preset filter conditions.
[0089] In response to a user's touch operation on the error reporting control, a route error reporting interface is displayed; the route error reporting interface is used by the user to upload error information about the travel route.
[0090] The modification control allows users to edit route-related information. For example, a user can click the "modify control" for a specific route on the route recommendation interface. The in-vehicle terminal will then respond to this touch, displaying the route editing interface. Users can then modify route-related information such as the starting point, destination, and waypoints. After saving the changes, the route information is updated, thus completing the route modification. This allows users to modify their routes according to their actual needs, providing high flexibility and personalization, and improving the user experience.
[0091] The delete control is used to remove unwanted travel routes. For example, a user can click the "Delete Control" on the route recommendation interface. The in-vehicle terminal will then respond to this touch operation, deleting the selected travel route. After the deletion is complete, the route recommendation interface updates and no longer displays the deleted route. Based on this, users can easily delete unnecessary routes, maintaining a clean and efficient interface and avoiding information overload.
[0092] The "Favorites" control allows users to save their favorite routes to a local file used for storing saved routes. For example, a user can click the "Favorites" control on the route recommendation interface. The in-vehicle terminal will then respond to this touch gesture and save the selected route to the file. Users can view the saved routes when needed, and clicking on a saved route will take them to the route details page. This allows users to save frequently used or favorite routes to a local file for easy access and use later, improving the convenience of route management. Users can also unsave routes from their favorites.
[0093] The sorting control is used to sort all recommended travel routes. For example, a user can click the "sorting control" on the route recommendation interface. At this time, the in-vehicle terminal will respond to the user's touch operation, sort all the displayable routes according to the preset sorting rules, and after the sorting is completed, the route recommendation interface will display the routes in the new order.
[0094] This application does not limit the preset sorting rules. Optionally, the preset sorting rules may include any one of the following: total route length, estimated travel time, and distance between the vehicle's current location and the route starting point. Appropriate sorting rules can be set according to the user's actual needs, allowing the on-board terminal to sort travel routes according to the user's actual requirements, so that the user can quickly find the desired route. Through preset sorting rules, users can quickly find the route that best meets their needs, improving the efficiency of route selection.
[0095] The filter control is used to filter travel routes that meet specific criteria. For example, a user can click the "filter control" on the route recommendation interface. At this time, the in-vehicle terminal will respond to the user's touch operation and filter all displayable routes according to preset filter conditions. After the filtering is completed, the route recommendation interface will only display the filtered travel routes that meet the criteria.
[0096] This application does not limit the preset filtering conditions. Optionally, the preset filtering conditions may include geographic location information and / or route feature information. Geographic location information can be used to filter travel routes within certain geographical areas, while route feature information can be used to filter travel routes that meet the user's driving needs. For example, route feature information may include at least one of the following: driving experience parameters, route attraction difference parameters, and route safety parameters. Driving experience parameters may include at least one of the following: route length, average radius of curvature, route curve diversity parameters, and route elevation difference. Route attraction difference parameters may include at least one of the following: number of natural attractions, number of cultural attractions, etc. Route safety parameters may include at least one of the following: route maintenance level, route passability duration, traffic volume, and number of terrain types. The route maintenance level indicates the degree of route maintenance. Route curve diversity parameters include at least one of the following: total number of curves, average curve length, and total number of consecutive curves. Route passability duration refers to the duration during which the route is passable within one year. The number of natural attractions refers to the average number of natural attractions per unit distance, the number of cultural attractions refers to the average number of cultural attractions per unit distance, and traffic flow refers to the average traffic flow per unit time. The unit distance can be 5 kilometers, 10 kilometers, 15 kilometers, etc., and the unit time can be half an hour, 1 hour, 2 hours, etc. This application embodiment does not limit the route feature information and can determine it according to the actual situation. Based on preset filtering conditions, users can quickly filter routes that meet specific needs, reducing search time and improving user decision-making efficiency.
[0097] Error reporting controls are used by users to report errors in their routes. For example, a user can click the "Error Reporting Control" on the route recommendation interface. The in-vehicle terminal will then respond to this touch, displaying an error reporting interface for the route. The user can upload error information about the route, such as blocked routes or traffic congestion. The in-vehicle terminal will receive and process the error information, such as notifying relevant personnel or departments to instruct them to verify the information. Based on user feedback, travel routes can be adjusted and optimized, ensuring the accuracy and timeliness of route information.
[0098] In some examples, after verifying the validity of the error message reported by the user, the user will be given a corresponding achievement reward, such as increasing the user's reward points. The reward points given to the user can be used to redeem benefits, prizes, etc., and can also be used to unlock other functions of the vehicle. This application embodiment does not limit the reward points.
[0099] In some examples, if the vehicle terminal receives a message indicating that the route has failed the review, it can also display a message indicating that the route is correct for the user to view; or, it can also impose corresponding penalties on the user, such as preventing them from initiating route error requests again for a period of time, thereby improving the user interaction experience.
[0100] It should be noted that the various functional controls can be presented in the interface in a variety of different ways, such as as "specific icons", "specific symbols", text, etc., and this application embodiment does not impose any restrictions.
[0101] It should be noted that the routes creation interface, route details interface, route preview interface, route recommendation interface, etc. involved in the embodiments of this application are only functional divisions. In actual scenarios, the information displayed in each interface can be displayed on the vehicle terminal simultaneously according to actual needs. This application embodiment does not impose any restrictions.
[0102] For example, Figure 4 This is a schematic diagram of a route details interface provided in an embodiment of this application. Figure 4 As shown, the route details interface 40 displays detailed information about the user-clicked travel route and several preset function controls (only a portion is shown in the figure). Based on interface 40, the user can view the details of a newly created travel route; by clicking the "Personal Travel" control 41, the in-vehicle terminal can initiate navigation to begin the trip; by clicking the "Fleet Travel" control 42, the in-vehicle terminal can jump to the fleet activity interface to participate in fleet activities; by clicking the "Delete" control 43, the in-vehicle terminal can delete the travel route; by clicking the "Edit" control 44, the in-vehicle terminal can edit the travel route; by clicking the "Report Error" control 45, the in-vehicle terminal can report an error for the travel route information; and by clicking the "Favorite" control 46, the in-vehicle terminal can add the travel route to "My Favorite Routes".
[0103] This application introduces a variety of functional controls, enabling users to modify, delete, favorite, sort, filter, and report errors on user-created travel routes. This significantly improves the user experience and management efficiency, enhancing intelligence and user satisfaction.
[0104] Figure 5 A schematic diagram of the structure of the route data processing device provided in this application. Figure 5As shown, the route data processing device 50 provided in this embodiment includes a first processing unit 501 and a second processing unit 502.
[0105] The first processing unit 501 is used to respond to the user's creation command, generate a travel route based on the route-related information input by the user, and display a route preview interface for the travel route; wherein the route-related information is information related to the generation of the travel route, and the route preview interface includes detailed information of the travel route and preset function controls;
[0106] The second processing unit 502 is used to process travel routes in response to touch operations performed by the user on preset function controls.
[0107] In one possible implementation, the route-related information includes required information and optional information. The required information includes at least one of the following: route start point, route end point, route name, route description, and route image; the optional information includes waypoints.
[0108] In one possible implementation, the preset function controls include a save control and / or a publish control; the second processing unit 502 is specifically used for:
[0109] In response to a user's touch operation on the save control, the travel route is saved to the first file; the first file is a local file used to save user-created routes;
[0110] And / or, in response to a user's touch operation on the publish control, the travel route is published to a second file; the second file is a file used by the cloud to store the user's published route, and the cloud is used to share the travel route with other users in response to the approval instruction of the travel route.
[0111] In one possible implementation, the second processing unit 502 is further configured to:
[0112] Once the published travel route is approved, it will be displayed in the route recommendation interface using a preset display method.
[0113] In one possible implementation, the second processing unit 502 is further configured to:
[0114] In response to the user's touch operation on the route recommendation interface, detailed information about the route is displayed.
[0115] In one possible implementation, the route recommendation interface also displays one or more of the following functional controls: edit control, delete control, favorites control, sort control, filter control, and error reporting control; the second processing unit 502 is further used for:
[0116] In response to a user's touch operation on the modification control, the route editing interface is displayed; the editing interface is used by the user to edit route-related information.
[0117] Delete the travel route in response to the user's touch operation on the delete control;
[0118] In response to a user's touch operation on the favorites control, the travel route is saved to a third file; the third file is a local file used to store the user's saved routes.
[0119] In response to the user's touch operation on the sorting control, all routes that can be displayed in the route recommendation interface are sorted according to the preset sorting rules.
[0120] In response to the user's touch operation on the filter control, the system filters all routes that can be displayed in the route recommendation interface according to preset filter conditions.
[0121] In response to a user's touch operation on the error reporting control, a route error reporting interface is displayed; the route error reporting interface is used by the user to upload error information about the travel route.
[0122] In one possible implementation, the preset sorting rules include any one of the following: total route length, estimated travel time, and distance between the vehicle's current location and the route's starting point; the preset filtering conditions include geographic location information and / or route feature information.
[0123] In one possible implementation, the detailed information includes one or more of the following: route trajectory information, route name, geographical location information, altitude information, creator information, total route length, estimated travel time, route rating information, approval progress information, mode of transportation, and distance between the vehicle's current location and the route's starting point.
[0124] The route data 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.
[0125] 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.
[0126] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 6 As shown, the electronic device 60 provided in this embodiment includes at least one processor 601 and a memory 602. Optionally, the device 60 further includes a communication component 603. The processor 601, memory 602, and communication component 603 are connected via a bus 604.
[0127] In a specific implementation, at least one processor 601 executes computer execution instructions stored in memory 602, causing at least one processor 601 to perform the above-described method.
[0128] The specific implementation process of processor 601 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.
[0129] 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.
[0130] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.
[0131] 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.
[0132] This application also provides a vehicle that includes the electronic devices described above.
[0133] 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.
[0134] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.
[0135] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.
[0136] 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.
[0137] 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.
[0138] 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.
[0139] 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.
[0140] 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.
[0141] 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.
[0142] 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.
[0143] 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 route data, characterized in that, The method includes: In response to the user's creation command, a travel route is generated based on the route-related information input by the user, and a route preview interface of the travel route is displayed; wherein, the route-related information is information related to the generation of the travel route, and the route preview interface includes detailed information of the travel route and preset function controls; The travel route is processed in response to a user's touch operation on the preset function control.
2. The method according to claim 1, characterized in that, The route-related information includes required and optional information. The required information includes at least one of the following: route start point, route end point, route name, route description, and route image. The optional information includes waypoints.
3. The method according to claim 1, characterized in that, The preset function controls include a save control and / or a publish control; the process of processing the travel route in response to a user's touch operation on the preset function controls includes: In response to a user's touch operation on the save control, the travel route is saved to a first file; the first file is a local file used to save user-created routes. And / or, in response to a user's touch operation on the publishing control, the travel route is published to a second file; the second file is a file in the cloud used to store the user-published route, and the cloud is used to share the travel route with other users in response to an approval instruction for the travel route.
4. The method according to claim 3, characterized in that, The method further includes: Once the published travel route is approved, it will be displayed in the route recommendation interface using a preset display method.
5. The method according to claim 4, characterized in that, The method further includes: In response to a user's touch operation on a travel route in the route recommendation interface, detailed information about the travel route is displayed.
6. The method according to claim 4, characterized in that, The route recommendation interface also displays one or more of the following functional controls: edit control, delete control, favorites control, sort control, filter control, and error reporting control; the method further includes: In response to a user's touch operation on the modification control, an editing interface for the travel route is displayed; the editing interface is used by the user to edit route-related information of the travel route. In response to a user's touch operation on the delete control, the travel route is deleted; In response to a user's touch operation on the favorites control, the travel route is saved to a third file; the third file is a local file used to save the user's saved routes. In response to a user's touch operation on the sorting control, all routes that can be displayed in the route recommendation interface are sorted according to a preset sorting rule; In response to a user's touch operation on the filtering control, all routes that can be displayed in the route recommendation interface are filtered according to preset filtering conditions; In response to a user's touch operation on the error reporting control, a route error reporting interface for the travel route is displayed; the route error reporting interface is used by the user to upload error information about the travel route.
7. The method according to claim 6, characterized in that, The preset sorting rules include any one of the following: total route length, estimated travel time, and distance between the vehicle's current location and the route's starting point; the preset filtering conditions include geographical location information and / or route feature information.
8. The method according to any one of claims 1-7, characterized in that, The detailed information includes one or more of the following: route trajectory information, route name, geographical location information, altitude information, creator information, total route length, estimated travel time, route rating information, approval progress information, mode of transportation, and distance between the vehicle's current location and the route starting point.
9. A route data processing device, characterized in that, The device includes: The first processing unit is configured to respond to the user's creation instruction, generate a travel route based on the route-related information input by the user, and display a route preview interface for the travel route; wherein, the route-related information is information related to the generation of the travel route, and the route preview interface includes detailed information of the travel route and preset function controls; The second processing unit is used to process the travel route in response to the user's touch operation on the preset function control.
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.