Route recommendation method and apparatus, and device, vehicle, medium and program product

Abstract

Provided in the present application are a recommendation method and apparatus, and a device, a vehicle, a medium and a program product, which can be used in the field of intelligent driving. In the method, after a driving style of a target user and route information of multiple routes to be recommended are acquired, a target route type corresponding to the driving style of the user is determined on the basis of a preset correspondence between driving styles and route types; and then, in view of the route information, a target route is determined from among said multiple routes, thereby recommending at least one target route. In the present solution, route recommendation is performed by means of driving styles of users, the route types and the route information, thereby improving the degree of matching between a recommended route and a requirement of the user.

Description

Route recommendation methods, devices, equipment, vehicles, media and procedures products Technical Field

[0001] This application relates to the field of intelligent driving, and more particularly to a route recommendation method, apparatus, device, vehicle, medium, and program product. Background Technology

[0002] With the development of technology, vehicles are able to perform more and more functions, not only assisting users in driving but also providing route recommendations, greatly improving the user's driving experience.

[0003] In existing technologies, route recommendations typically involve the user inputting a starting point and destination. The vehicle then identifies multiple routes that can reach the destination from the starting point, sorts them based on travel time or route length, and displays them for the user to choose from.

[0004] In summary, existing route recommendation methods only consider travel time and route length, resulting in a low degree of matching between recommended routes and user requirements. Summary of the Invention

[0005] This application provides a route recommendation method, apparatus, device, vehicle, medium, and program product to solve the problem that existing route recommendation methods only consider travel time and route length, resulting in a low degree of matching between the recommended routes and user requirements.

[0006] In a first aspect, embodiments of this application provide a route recommendation method, including:

[0007] Obtain the target user's driving style and route information for multiple routes to be recommended. The route information for each route to be recommended includes the route type or information used to characterize the route type.

[0008] Based on the preset correspondence between driving style and route type, determine the target route type corresponding to the driving style of the target user;

[0009] Based on the route information and the target route type, at least one of the multiple routes to be recommended is selected as the target route, and the route type of the target route matches the target route type.

[0010] Recommend at least one of the aforementioned destination routes.

[0011] In one specific embodiment, the route information further includes at least one of distance information, weather information, and traffic information. The distance information is used to characterize the distance between the current location of the target user and the route location of the route to be recommended. The weather information is used to characterize the weather conditions in the area where the route to be recommended is located at the current time or the scheduled travel time. The traffic information is used to characterize the traffic conditions between the current location of the target user and the starting point of the route to be recommended.

[0012] The route information of the target route meets the preset recommendation conditions.

[0013] In one specific implementation, the preset recommendation conditions include at least one of the following:

[0014] The distance between the target user's current location and the location of the route to be recommended is less than a preset distance;

[0015] Alternatively, the weather conditions in the area where the recommended route is located at the current or scheduled travel time meet the preset weather requirements;

[0016] Alternatively, the traffic conditions between the target user's current location and the starting point of the route to be recommended meet preset traffic condition requirements.

[0017] In one specific implementation, each of the routes to be recommended has a route type score, which is used to characterize the degree of matching between the route type of the route to be recommended and the target route type.

[0018] Each of the recommended routes has a distance score corresponding to its distance information, a weather score corresponding to its weather information, and a road condition score corresponding to its road condition information.

[0019] Each of the routes to be recommended has a corresponding recommendation score, which is calculated based on at least one of the route type score, distance score, weather score, and road condition score.

[0020] In one specific implementation, the preset recommendation conditions further include:

[0021] The recommended score for any of the target routes is greater than a preset threshold;

[0022] And / or, the recommended score corresponding to any of the target routes ranks among the top N in the recommended scores corresponding to the plurality of routes to be recommended, where N is a preset integer greater than or equal to 1.

[0023] In one specific implementation, the route type score corresponds to a route type weight, the distance score corresponds to a distance weight, the weather score corresponds to a weather weight, and the traffic condition score corresponds to a traffic condition weight.

[0024] The recommended score is calculated based on at least one of the following: the product of the route type score and the route type weight, the product of the distance score and the distance weight, the product of the weather score and the weather weight, and the product of the road condition score and the road condition weight.

[0025] In one specific implementation, the route type weight is greater than any one of the distance weight, the weather weight, and the traffic condition weight.

[0026] In one specific implementation, the method further includes: receiving the preset recommendation conditions configured by the user.

[0027] In one specific implementation, the degree of matching between the route type of any of the target routes and the target route type is higher than the degree of matching between the route type of any non-target route and the target route type, wherein the non-target routes are those routes among the routes to be recommended that have not been determined as the target routes.

[0028] In one specific implementation, the driving style is configured by the target user.

[0029] In one specific implementation, the driving style is determined based on the user's historical driving data.

[0030] In one specific implementation, the route type of any of the routes to be recommended is one of a plurality of preset route types;

[0031] The route type of any of the recommended routes is related to at least one of the following: route length, average radius of curvature of the route, route curve diversity parameter, route elevation difference, number of natural scenic spots passed through, number of cultural scenic spots passed through, route maintenance level, route passability time, traffic volume, and number of terrain types.

[0032] In one specific embodiment, the plurality of preset route types includes a first preset route type;

[0033] The correlation between the first preset route type and the number of natural scenic spots along the route, the route maintenance level, the route passability time, and the traffic volume is greater than the correlation with the route length, the average radius of curvature of the route, the route curve diversity parameter, the route elevation difference, the number of cultural scenic spots along the route, and the number of terrain types.

[0034] In one specific embodiment, the plurality of preset route types includes a second preset route type;

[0035] The correlation between the second preset route type and the number of cultural attractions along the route, the route maintenance level, the route passability time, and the traffic volume is greater than the correlation with the route length, the average radius of curvature of the route, the route curve diversity parameter, the route elevation difference, the number of natural attractions along the route, and the number of terrain types.

[0036] In one specific embodiment, the plurality of preset route types includes a third preset route type;

[0037] The correlation between the third preset route type and the average radius of curvature of the route, the route curve diversity parameter, the route elevation difference, and the number of terrain types is greater than the correlation between the route length, the number of natural scenic spots along the route, the number of cultural scenic spots along the route, the route maintenance level, the route passability time, and the traffic volume.

[0038] In one specific implementation, the plurality of preset route types includes a fourth preset route type;

[0039] The correlation between the fourth preset route type and the route length, the number of natural scenic spots along the route, and the number of terrain types is greater than the correlation between the average radius of curvature of the route, the route curve diversity parameter, the route elevation difference, the number of cultural scenic spots along the route, the route maintenance level, the route passability time, and the traffic volume.

[0040] In one specific implementation, the target user's driving style is one of a plurality of preset driving styles;

[0041] Each of the preset driving styles is related to historical driving data, which includes at least one of the following: accelerator pedal opening, brake pedal opening, longitudinal acceleration, straight-line speed, corner exit speed, corner entry speed, steering angle, lateral acceleration, and historical driving route information.

[0042] In one specific implementation, the threshold range of historical driving data corresponding to different preset driving styles is different.

[0043] In one specific implementation, the plurality of preset driving styles includes at least two of a first preset driving style, a second preset driving style, and a third preset driving style;

[0044] The plurality of preset route types includes at least two of the following: a first preset route type, a second preset route type, a third preset route type, and a fourth preset route type;

[0045] The preset driving style and route type correspondence is as follows: the first preset driving style corresponds to the fourth preset route type, the second driving style corresponds to the third preset route type, and the third driving style corresponds to the first preset route type and the second preset route type.

[0046] In one specific implementation, recommending at least one of the target routes includes: sending the at least one of the target routes, or displaying the at least one of the target routes.

[0047] In one specific implementation, displaying the at least one target route includes: sorting the target routes according to the degree of matching between the route type and the target route type, and displaying information related to each target route.

[0048] In one specific embodiment, the method further includes: displaying a non-target route, wherein any non-target route is one of the plurality of routes to be recommended other than the target route, and the display position of any non-target route is after any target route.

[0049] In one specific implementation, any two routes to be recommended satisfy the following condition: at least one of the route start point, route end point, and route waypoints is different.

[0050] In one specific implementation, there are at least two target routes that satisfy the condition that at least one of the route start point and the route end point is different.

[0051] In one specific implementation, at least one of the target routes satisfies the condition that the current location of the target user is not the same as the starting point of the target route.

[0052] Secondly, embodiments of this application provide a route recommendation method, the method comprising:

[0053] Obtain the driving style of the target user;

[0054] Based on the preset correspondence between driving style and route type, determine the target route type corresponding to the driving style of the target user;

[0055] At least one target route is recommended, and the route type of each target route matches the target route type.

[0056] Thirdly, embodiments of this application provide a route recommendation method applied to an in-vehicle terminal, the method comprising:

[0057] Obtain the driving style of the target user;

[0058] Send the target user's driving style to the server;

[0059] The system receives at least one target route from the server, and the route type of each target route matches the target user's driving style.

[0060] In one specific embodiment, the method further includes:

[0061] Receive the route sent by the server and store the route as a route to be recommended.

[0062] In one specific embodiment, the method further includes:

[0063] In response to a user's route error reporting operation, a route error reporting request is sent to the server, the route error reporting request including the route to be reviewed;

[0064] Receive the approval message sent by the server;

[0065] Increase users' reward points.

[0066] Fourthly, embodiments of this application provide a route recommendation method applied to a server, the method comprising:

[0067] Receives the target user's driving style sent by the vehicle terminal;

[0068] Obtain route information for multiple routes to be recommended, whereby the route information for each route to be recommended includes the route type;

[0069] Based on the preset correspondence between driving style and route type, determine the target route type corresponding to the driving style of the target user;

[0070] Based on the route information, at least one of the multiple routes to be recommended is selected as the target route, and the route type of the target route matches the target route type.

[0071] Send at least one of the target routes to the vehicle-mounted terminal.

[0072] In one specific embodiment, the method further includes:

[0073] Receive a route error request sent by the vehicle terminal, the route error request including routes to be reviewed;

[0074] Receive the approval message sent by the terminal device;

[0075] The approval message is sent to the vehicle terminal.

[0076] Fifthly, embodiments of this application provide a route recommendation device, characterized in that it includes:

[0077] The acquisition module is used to acquire the driving style of the target user and the route information of multiple routes to be recommended. The route information of each route to be recommended includes the route type or information used to characterize the route type.

[0078] Processing module, used for:

[0079] Based on the preset correspondence between driving style and route type, determine the target route type corresponding to the driving style of the target user;

[0080] Based on the route information and the target route type, at least one of the multiple routes to be recommended is selected as the target route, and the route type of the target route matches the target route type.

[0081] The recommendation module is used to recommend at least one of the target routes.

[0082] Sixthly, embodiments of this application provide a route recommendation device, comprising:

[0083] The acquisition module is used to acquire the driving style of the target user;

[0084] The processing module is used to determine the target route type corresponding to the driving style of the target user based on the preset correspondence between driving style and route type;

[0085] The recommendation module is used to recommend at least one target route, and the route type of each target route matches the target route type.

[0086] Seventhly, embodiments of this application provide a route recommendation device, including:

[0087] The acquisition module is used to acquire the driving style of the target user;

[0088] The sending module is used to send the target user's driving style to the server;

[0089] The receiving module is used to receive at least one target route fed back by the server, and the route type of each target route is matched with the target route type corresponding to the driving style of the target user.

[0090] Eighthly, embodiments of this application provide a route recommendation device, comprising:

[0091] The receiving module is used to receive the driving style of the target user sent by the vehicle terminal;

[0092] The acquisition module is used to acquire route information for multiple routes to be recommended, and the route information for each route to be recommended includes the route type;

[0093] Processing module, used for:

[0094] Based on the preset correspondence between driving style and route type, determine the target route type corresponding to the driving style of the target user;

[0095] Based on the route information, at least one of the multiple routes to be recommended is selected as the target route, and the route type of the target route matches the target route type.

[0096] The sending module is used to send at least one of the target routes to the vehicle-mounted terminal.

[0097] Ninthly, embodiments of this application provide an electronic device, including:

[0098] Processor, memory, communication interface;

[0099] The memory is used to store the executable instructions of the processor;

[0100] The processor is configured to execute the route recommendation method described in either the first or second aspect by executing the executable instructions.

[0101] Tenthly, embodiments of this application provide a vehicle-mounted terminal, including:

[0102] Processor, memory, communication interface;

[0103] The memory is used to store the executable instructions of the processor;

[0104] The processor is configured to execute the route recommendation method described in any of the third aspects by executing the executable instructions.

[0105] Eleventhly, embodiments of this application provide a server, including:

[0106] Processor, memory, communication interface;

[0107] The memory is used to store the executable instructions of the processor;

[0108] The processor is configured to execute the route recommendation method described in any of the fourth aspects by executing the executable instructions.

[0109] In a twelfth aspect, embodiments of this application provide a vehicle, including an in-vehicle terminal;

[0110] The vehicle-mounted terminal is used to execute the route recommendation method described in any one of the first, second, or third aspects above.

[0111] In a thirteenth aspect, embodiments of this application provide a readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the route recommendation method described in any one of the first to fourth aspects.

[0112] In a fourteenth aspect, embodiments of this application provide a computer program product, including a computer program, which, when executed by a processor, is used to implement the route recommendation method described in any one of the first to fourth aspects.

[0113] In a fifteenth aspect, embodiments of this application provide a computer program, which, when executed by a processor, performs the route recommendation method described in any one of the first to fourth aspects.

[0114] In a sixteenth aspect, embodiments of this application provide a chip, the chip including a memory and a processor, the memory storing code and data, the memory being coupled to the processor, and the processor running a program in the memory such that the chip is used to execute the route recommendation method described in any one of the first to fourth aspects above.

[0115] The route recommendation method, apparatus, device, vehicle, medium, and program product provided in this application obtains the driving style of a target user and route information of multiple routes to be recommended. Based on a preset correspondence between driving style and route type, it determines the target route type corresponding to the user's driving style. Then, combining this with the route information, it determines the target route from the multiple routes to be recommended and recommends at least one target route. This solution improves the matching degree between recommended routes and user requirements by recommending routes based on the user's driving style, route type, and route information. Attached Figure Description

[0116] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0117] Figure 1 is a flowchart illustrating an embodiment of the route recommendation method provided in this application;

[0118] Figure 2 is a flowchart illustrating Embodiment 3 of the route recommendation method provided in this application;

[0119] Figure 3 is a flowchart illustrating Embodiment 4 of the route recommendation method provided in this application;

[0120] Figure 4 is a flowchart illustrating Embodiment 5 of the route recommendation method provided in this application;

[0121] Figure 5 is a flowchart illustrating Embodiment Six of the route recommendation method provided in this application;

[0122] Figure 6 is a flowchart illustrating Embodiment 7 of the route recommendation method provided in this application;

[0123] Figure 7 is a flowchart illustrating an eighth embodiment of the route recommendation method provided in this application;

[0124] Figure 8 is a flowchart illustrating Embodiment Nine of the route recommendation method provided in this application;

[0125] Figure 9 is a flowchart illustrating Embodiment 10 of the route recommendation method provided in this application;

[0126] Figure 10 is a flowchart illustrating Embodiment 11 of the route recommendation method provided in this application;

[0127] Figure 11 is a flowchart illustrating Embodiment Twelve of the route recommendation method provided in this application;

[0128] Figure 12 is a flowchart illustrating Embodiment Thirteen of the route recommendation method provided in this application;

[0129] Figure 13 is a flowchart illustrating the scoring process for determining the diversity parameters of road curves provided in this application.

[0130] Figure 14 is a flowchart illustrating Embodiment 18 of the route recommendation method provided in this application;

[0131] Figure 15 is a schematic diagram of a route creation interface provided in an embodiment of this application;

[0132] Figure 16 is a schematic diagram of a route preview interface provided in an embodiment of this application;

[0133] Figure 17 is a schematic diagram of a route details interface provided in an embodiment of this application;

[0134] Figure 18 is a structural schematic diagram of a first embodiment of the route recommendation device provided in this application;

[0135] Figure 19 is a structural schematic diagram of Embodiment 2 of the route recommendation device provided in this application;

[0136] Figure 20 is a structural schematic diagram of Embodiment 3 of the route recommendation device provided in this application;

[0137] Figure 21 is a schematic diagram of the structure of Embodiment 4 of the route recommendation device provided in this application;

[0138] Figure 22 is a schematic diagram of the structure of an electronic device provided in this application;

[0139] Figure 23 is a structural schematic diagram of a vehicle-mounted terminal provided in this application;

[0140] Figure 24 is a schematic diagram of the structure of a server provided in this application. Detailed Implementation

[0141] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments made by those skilled in the art under the guidance of these embodiments are within the scope of protection of this application.

[0142] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0143] With the development of technology, vehicles are able to perform more and more functions, not only assisting users in driving but also providing route recommendations, greatly improving the user's driving experience.

[0144] In existing technologies, route recommendations typically involve the user inputting a starting point and destination. The vehicle then identifies multiple routes that can reach the destination and sorts them based on travel time or route length before displaying them for the user to choose from. However, considering only travel time and route length can lead to a low degree of matching between recommended routes and user requirements.

[0145] To address the problems existing in the prior art, the inventors, during their research on route recommendation methods, discovered that different users have different driving styles, and different routes have different route types. Therefore, it is possible to determine the route type corresponding to a user's driving style, and then determine the target route to recommend to the user based on the route type, thereby improving the matching degree between the recommended route and the user's requirements. Based on the above inventive concept, the route recommendation scheme in this application was designed.

[0146] The route recommendation method in this application can be implemented by an in-vehicle terminal, or by a computer, server, vehicle, etc. This application does not limit it. The following explanation uses an in-vehicle terminal as an example.

[0147] 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.

[0148] The following provides examples illustrating the application scenarios of the route recommendation method provided in this application.

[0149] For example, in this application scenario, a user wants to participate in a sports event, and each event has a corresponding route. The user wants the in-vehicle terminal to recommend a route.

[0150] The in-vehicle terminal acquires the user's driving style and route information for multiple recommended routes. The route information for each recommended route includes the route type or information used to characterize the route type. The recommended routes are those for events or competitions.

[0151] Then, the vehicle terminal determines the target route type corresponding to the user's driving style based on the preset correspondence between driving style and route type.

[0152] Then, based on the route information and the target route type, at least one route to be recommended is selected as the target route from among multiple routes to be recommended, and the route type of the target route matches the target route type.

[0153] The in-vehicle terminal recommends at least one target route, which is displayed. Users can select a route from this list to confirm the event they wish to participate in.

[0154] 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.

[0155] The technical solution of this application will now be described in detail through specific embodiments. It should be noted that the following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0156] Figure 1 is a flowchart illustrating an embodiment of the route recommendation method provided in this application. This embodiment describes the process of recommending routes based on the user's driving style and route information from multiple routes to be recommended. The method in this embodiment can be implemented through software, hardware, or a combination of both. As shown in Figure 1, the route recommendation method specifically includes the following steps:

[0157] S101: Obtain the target user's driving style and route information for multiple routes to be recommended.

[0158] In this step, in order to improve the matching degree between the recommended route and the user's requirements, the vehicle terminal first obtains the target user's driving style and the route information of multiple routes to be recommended. The route information of each route to be recommended includes the route type or information used to characterize the route type.

[0159] It should be noted that the target user's driving style can be configured by the target user in the in-vehicle terminal. Alternatively, the in-vehicle terminal can provide a driving style detection questionnaire, and the corresponding driving style can be determined based on the target user's answers to each question in the questionnaire. It can also be determined based on the target user's historical driving data. Alternatively, the target user can configure the driving style in the in-vehicle terminal when starting to use the vehicle, and then determine the driving style based on historical driving data generated during vehicle use. This application does not limit the method of determining the target user's driving style; it can be determined according to the actual situation.

[0160] It should be noted that the target user's driving style is one of several preset driving styles; each preset driving style is related to historical driving data, which includes at least one of the following: accelerator pedal opening, brake pedal opening, longitudinal acceleration, straight-line speed, corner exit speed, corner entry speed, steering angle, lateral acceleration, and historical driving route information. The threshold range of historical driving data corresponds to different preset driving styles.

[0161] Multiple preset driving styles include at least two of the following: a first preset driving style, a second preset driving style, and a third preset driving style. The first preset driving style is biased towards straight-line driving, the second preset driving style is biased towards curved driving, and the third preset driving style is biased towards a balanced driving style between straight lines and curves.

[0162] The first preset driving style prefers routes with low elevation difference, high traffic speed, and low curvature ratio. The second preset driving style prefers routes with high elevation difference, medium traffic speed, and high curvature ratio. The third preset driving style prefers routes with medium elevation difference, medium traffic speed, and medium curvature ratio.

[0163] The route type of any route to be recommended is one of multiple preset route types; the route type of any route to be recommended is related to information used to characterize the route type, which is related to at least one of the following: route length, average radius of curvature of the route, route curve diversity parameter, route elevation difference, number of natural scenic spots passed through, number of cultural scenic spots passed through, route maintenance level, route passability time, traffic volume, and number of terrain types.

[0164] The average radius of curvature of the route refers to the average radius of curvature of all curves in the route. Route curve diversity parameters include the total number of curves, the average length of curves, and the total number of consecutive curves. The number of natural scenic spots along the route refers to the average number of natural scenic spots per unit distance. The number of cultural scenic spots along the route refers to the average number of cultural scenic spots per unit distance. The route maintenance level indicates the degree of maintenance of the route. The route passability duration refers to the duration during which the route is passable within one year. 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 does not limit the unit distance or unit time; these can be determined according to actual conditions.

[0165] Multiple preset route types include the first preset route type; the first preset route type is more correlated with the number of natural scenic spots along the route, the route maintenance level, the route passable time, and the traffic volume than with the route length, the average radius of curvature of the route, the route curve diversity parameters, the route elevation difference, the number of cultural scenic spots along the route, and the number of terrain types.

[0166] Multiple preset route types include a second preset route type; the second preset route type is more correlated with the number of cultural attractions along the route, the route maintenance level, the route passable time, and the traffic volume than with the route length, the average radius of curvature of the route, the route curve diversity parameters, the route elevation difference, the number of natural attractions along the route, and the number of terrain types.

[0167] Multiple preset route types include a third preset route type; the third preset route type is more correlated with the average radius of curvature of the route, the diversity of curves in the route, the elevation difference of the route, and the number of terrain types than with the route length, the number of natural scenic spots passed through, the number of cultural scenic spots passed through, the route maintenance level, the route passable time, and the traffic volume.

[0168] Multiple preset route types include a fourth preset route type; the fourth preset route type is more correlated with route length, number of natural scenic spots passed through, and number of terrain types than with the average radius of curvature of the route, the diversity of route curves, the elevation difference of the route, the number of cultural scenic spots passed through, the route maintenance level, the route passable time, and the traffic volume.

[0169] It should be noted that weights can be used to represent the degree of correlation. The meaning that the correlation between the preset route type and some parameters is greater than its correlation with others can be: the preset route type has a greater weight on any one of the parameters than on any one of the other parameters. Alternatively, it can mean: the preset route type has a greater overall weight on some parameters than on the other parameters.

[0170] The correlation between the fourth preset route type and route length is greater than that between the first, second, and third preset route types and route length.

[0171] The correlation between the third preset route type and the average radius of curvature of the route is greater than that between the first, second, and fourth preset route types and the average radius of curvature of the route.

[0172] The correlation between the third preset route type and the route curve diversity parameter is greater than that between the first, second, and fourth preset route types and the route curve diversity parameter.

[0173] The correlation between the third preset route type and the route elevation difference is greater than that between the first, second, and fourth preset route types and the route elevation difference.

[0174] The correlation between the first and fourth preset route types and the number of natural attractions is greater than that between the second and third preset route types and the number of natural attractions.

[0175] The correlation between the second preset route type and the number of cultural attractions is greater than that between the first, third, and fourth preset route types and the number of cultural attractions.

[0176] The correlation between the first and second preset route types and the route maintenance level is greater than that between the third and fourth preset route types and the route maintenance level.

[0177] The correlation between the first and second preset route types and the route passability time is greater than that between the third and fourth preset route types and the route passability time.

[0178] The correlation between the first and second preset route types and traffic flow is greater than that between the third and fourth preset route types and traffic flow.

[0179] The correlation between the third and fourth preset route types and the number of terrain types is greater than that between the first and second preset route types and the number of terrain types.

[0180] This application does not limit the preset driving style and preset route type; they can be determined according to the actual situation.

[0181] It should be noted that the recommended routes can be officially set routes, routes created by users, or routes uploaded to the server by other users and then distributed to the vehicle terminal by the server.

[0182] It should be noted that this solution can recommend routes not only for the same start and end point in navigation scenarios, but also for different team activities and events. Therefore, any two routes to be recommended must satisfy the following condition: at least one of the route start, route end, and route waypoints is different. The start or end point of each route to be recommended may be different from the user's current location.

[0183] S102: Based on the preset correspondence between driving style and route type, determine the target route type corresponding to the target user's driving style.

[0184] In this step, after the vehicle terminal obtains the driving style and route information, it determines the target route type corresponding to the target user's driving style based on the preset correspondence between driving style and route type.

[0185] For example, the preset driving style and route type correspondence is as follows: the first preset driving style corresponds to the fourth preset route type, the second driving style corresponds to the third preset route type, and the third driving style corresponds to the first preset route type and the second preset route type. This application embodiment does not limit the preset driving style and route type correspondence, which can be determined according to actual circumstances.

[0186] S103: Based on the route information and the target route type, select at least one route from multiple routes to be recommended as the target route.

[0187] In this step, after the vehicle terminal determines the target route type, it selects at least one route from multiple routes to be recommended as the target route based on the route information and the target route type. The route type of the target route matches the target route type.

[0188] In one implementation, the route whose route type is the target route type among multiple routes to be recommended is taken as the target route.

[0189] In another implementation, the vehicle terminal is configured with a matching degree between route types. Therefore, the matching degree between the route type of each proposed route and the target route type can be determined. Routes whose matching degree is greater than a preset matching degree threshold are designated as target routes. This ensures that the matching degree between the route type of any target route and the target route type is higher than the matching degree between the route type of any non-target route and the target route type. Non-target routes are those proposed routes that were not determined to be target routes.

[0190] It should be noted that the preset matching degree threshold can be 80%, 85%, 90%, etc. This application embodiment does not limit the preset matching degree threshold, and it can be determined according to the actual situation.

[0191] In another implementation, the vehicle terminal is configured with a matching degree between route types. This allows the determination of the matching degree between the route type of each proposed route and the target route type. The proposed routes are then arranged in descending order of their matching degree with the target route type, resulting in a route sequence. If the number of proposed routes exceeds a preset threshold, the first preset threshold of proposed routes in the route sequence are designated as target routes. If the number of proposed routes is less than or equal to the preset threshold, all proposed routes in the route sequence are designated as target routes. This ensures that the matching degree between the route type of any target route and the target route type is higher than the matching degree between the route type of any non-target route and the target route type. Non-target routes are those proposed routes that were not determined to be target routes.

[0192] It should be noted that the preset quantity threshold can be 3, 5, 7, etc. This application embodiment does not limit the preset quantity threshold, and it can be determined according to the actual situation.

[0193] S104: Recommend at least one target route.

[0194] In this step, after the vehicle terminal determines the target route, it recommends at least one target route.

[0195] It should be noted that recommending at least one target route can be done in several ways: displaying at least one target route; sending at least one target route to the target user's terminal device; or sending at least one target route to the target user's terminal device and then displaying it.

[0196] Displaying at least one target route can be achieved by sorting the target routes according to their degree of match with the target route type and displaying information related to each target route. The sorting can be from highest to lowest match degree, or from lowest to highest match degree.

[0197] Information related to the target route includes at least one of the following: waypoints, travel time period, route description, route length, estimated travel time, rating, and road type percentage. The road type percentage is related to the route type. The first preset driving style has the following road type percentages: medium proportion of urban roads, low proportion of highways, medium proportion of mountain roads, and high proportion of suburban roads. The second preset driving style has the following road type percentages: high proportion of urban roads, medium proportion of highways, low proportion of mountain roads, and low proportion of suburban roads. The third preset driving style has the following road type percentages: low proportion of urban roads, medium proportion of highways, high proportion of mountain roads, and medium proportion of suburban roads. The fourth preset driving style has the following road type percentages: low proportion of urban roads, medium proportion of highways, high proportion of mountain roads, and high proportion of suburban roads.

[0198] After the vehicle terminal displays the target route, it can sort the target routes according to parameters such as route length, estimated travel time, and the length between the current user and the route starting point. It can also filter the target routes according to the route location.

[0199] It should be noted that the number of recommended target routes can be a preset number of recommendations, or it can be the rounded-up value of the product of the total number of target routes and the preset recommendation ratio. The preset number of recommendations can be 3, 4, 7, etc., and the preset recommendation ratio can be 60%, 70%, 80%, etc. This application embodiment does not limit the preset number of recommendations and the preset recommendation ratio, and they can be determined according to the actual situation.

[0200] The vehicle terminal can also display non-target routes. Any non-target route is one of multiple routes to be recommended, excluding the target route, and the display position of any non-target route is after any target route.

[0201] In one implementation, there exist at least two target routes that satisfy the condition that at least one of the route's starting point and the route's ending point is different.

[0202] In one implementation, there exists at least one target route that satisfies the condition that the target user's current location is not the same as the starting point of the target route.

[0203] Users can also save their target routes.

[0204] It should be noted that the executing entity of this application can also be a server, or a vehicle-mounted terminal and a server.

[0205] When the execution entities are an in-vehicle terminal and a server, the in-vehicle terminal can obtain the target user's driving style and send it to the server. Upon receiving the driving style, the server obtains route information from multiple routes to be recommended, and then determines the target route type corresponding to the target user's driving style based on a preset correspondence between driving styles and route types. Subsequently, based on the route information and the target route type, the server selects at least one route from the multiple routes to be recommended as the target route and sends this target route to the in-vehicle terminal. The in-vehicle terminal can then receive the target route.

[0206] When the execution entities are an in-vehicle terminal and a server, the in-vehicle terminal can obtain the target user's driving style and route information of multiple routes to be recommended, and then send these information to the server. The server determines the target route type corresponding to the target user's driving style based on a preset correspondence between driving styles and route types; then, based on the route information and target route type, it selects at least one route from the multiple routes to be recommended as the target route and sends this target route to the in-vehicle terminal. The in-vehicle terminal can then receive the target route.

[0207] When the execution entities are an in-vehicle terminal and a server, the in-vehicle terminal can obtain the target user's driving style and route information from multiple routes to be recommended, and then send the driving style to the server. Upon receiving the driving style, the server determines the target route type corresponding to the target user's driving style based on a preset correspondence between driving styles and route types, and sends the target route type to the in-vehicle terminal. Based on the route information and the target route type, the in-vehicle terminal selects at least one route from the multiple routes to be recommended as the target route, and then sends at least one of the target routes to the in-vehicle terminal. The in-vehicle terminal can then receive the target route.

[0208] This application does not limit the execution steps of the vehicle terminal and server when the execution subjects are the vehicle terminal and server, and can be determined according to the actual situation.

[0209] The route recommendation method provided in this embodiment, after obtaining the target user's driving style and route information of multiple routes to be recommended, determines the target route type corresponding to the user's driving style based on a preset correspondence between driving style and route type. Then, combining this with the route information, it identifies the target route from the multiple routes to be recommended and recommends at least one target route. Compared to existing technologies that only consider travel time and route length, this solution improves the matching degree between the recommended route and the user's requirements by recommending routes based on the user's driving style, route type, and route information.

[0210] In addition, routes can be recommended based on the user's driving style, route type, and route information to meet the user's expectations for new journeys and desire for novel experiences, allowing for a better experience of vehicle performance and enhanced driving pleasure.

[0211] The following example, using the second embodiment of the route recommendation method, illustrates the situation where the route information also includes at least one of distance information, weather information, and road condition information, and the route information of the target route also meets the preset recommendation conditions.

[0212] Distance information is used to represent the distance between the target user's current location and the route location of the route to be recommended; weather information is used to represent the weather conditions in the area where the route to be recommended is located at the current time or the scheduled travel time; and traffic information is used to represent the traffic conditions between the target user's current location and the starting point of the route to be recommended.

[0213] The distance between the target user's current location and the route location to be recommended can be either the straight-line distance between the current location and the route location, or the route length from the current location to the route location.

[0214] The location of the route to be recommended can be the starting point, the ending point, or a point along the route.

[0215] The target routes selected from the routes to be recommended must not only match the route type with the target route type, but also meet the preset recommendation conditions.

[0216] In one implementation, the preset recommendation conditions include at least one of the following:

[0217] The distance between the target user's current location and the location of the route to be recommended is less than a preset distance;

[0218] Alternatively, the weather conditions in the area where the recommended route is located at the current time or the scheduled travel time meet the preset weather requirements;

[0219] Alternatively, the traffic conditions between the target user's current location and the starting point of the route to be recommended meet the preset traffic condition requirements.

[0220] It should be noted that the preset distance can be 10 kilometers, 20 kilometers, 50 kilometers, etc., and the preset weather requirements can be a weather set, such as {sunny, cloudy}, {sunny, cloudy, overcast, light rain}, {sunny, cloudy, overcast, light rain, light snow}, etc. The road conditions between the current location and the starting point of the route to be recommended must meet the preset road condition requirements if: the road surface maintenance level between the current location and the starting point of the route to be recommended is greater than the preset level, the number of damaged points between the current location and the starting point of the route to be recommended is less than the preset number of damaged points, and the number of construction points between the current location and the starting point of the route to be recommended is less than the preset number of construction points.

[0221] For example, road surface maintenance levels are divided into 5 levels, with higher maintenance levels indicating better road conditions. Preset levels can be 2, 3, 4, etc. Preset damage quantities can be 5, 7, 10, etc., and preset construction quantities can be 4, 6, 8, etc.

[0222] This application does not limit the preset distance, preset weather requirements, preset damage quantity, preset construction quantity, preset level, or whether the road conditions between the current location and the starting point of the route to be recommended meet the preset road condition requirements; these can be determined according to the actual situation.

[0223] It should be noted that the preset filtering conditions can be configured by the user. Users can configure them directly on the in-vehicle terminal or on the terminal device, which will then send the preset filtering conditions to the in-vehicle terminal. All preset filtering conditions can be configured directly, or specific parameters such as preset distance, preset weather requirements, preset damage quantity, preset construction quantity, and preset severity level can be configured.

[0224] In another implementation, each route type to be recommended corresponds to a route type score, which is used to characterize the degree of matching between the route type of the route to be recommended and the target route type; the higher the road surface type score, the higher the degree of matching between the route type of the route to be recommended and the target route type.

[0225] Each route to be recommended has a distance score corresponding to its distance information, a weather score corresponding to its weather information, and a road condition score corresponding to its road condition information.

[0226] Each route to be recommended has a corresponding recommendation score, which is calculated based on at least one of the following: route type score, distance score, weather score, and road condition score.

[0227] It should be noted that the distance score corresponding to the distance information can be determined based on the correspondence between the distance range and the distance score. For example, when the distance range is [0, 10), the unit is kilometers and the distance score is 10 points; when the distance range is [10, 50), the unit is kilometers and the distance score is 6 points; when the distance range is [50, +∞), the unit is kilometers and the distance score is 3 points. This application does not limit the correspondence between the distance range and the distance score, and it can be determined according to the actual situation.

[0228] It should be noted that the weather score corresponding to the weather information can be determined based on the correspondence between weather range and weather score. For example, the correspondence between weather range and weather score can be as follows: when the weather range is {sunny, cloudy, overcast}, the weather score is 10 points; when the weather range is {light rain, light snow}, the weather score is 6 points; when the weather range is {heavy rain, torrential rain, heavy snow, blizzard, fog, haze, hail, sandstorm}, the weather score is 3 points. This application embodiment does not limit the correspondence between weather range and weather score, and it can be determined according to the actual situation.

[0229] It should be noted that the road condition score corresponding to the road condition information can be determined based on the correspondence between the road maintenance level range and the road condition score. For example, the correspondence between the road maintenance level range and the road condition score can be as follows: when the road maintenance level range is (0, 1], the road condition score is 3 points; when the road maintenance level range is (1, 2], the road condition score is 6 points; and when the road maintenance level range is (2, 3], the road condition score is 10 points. This application embodiment does not limit the correspondence between the road maintenance level range and the road condition score, and it can be determined according to the actual situation.

[0230] The recommended score can be calculated by adding at least one of the following: route type score, distance score, weather score, and road condition score.

[0231] The recommended score can also be calculated as follows: the route type score corresponds to the route type weight, the distance score corresponds to the distance weight, the weather score corresponds to the weather weight, and the road condition score corresponds to the road condition weight; the recommended score is calculated based on at least one of the following: the product of the route type score and the route type weight, the product of the distance score and the distance weight, the product of the weather score and the weather weight, and the product of the road condition score and the road condition weight.

[0232] The recommended score can be obtained by adding or multiplying at least one of the following: the product of route type score and route type weight, the product of distance score and distance weight, the product of weather score and weather weight, and the product of road condition score and road condition weight.

[0233] It should be noted that the route type weight can be greater than any one of the distance weight, weather weight, and road condition weight.

[0234] The recommended score can also be calculated based on the route type score and distance score. Alternatively, the route type score and distance score can be added together to obtain the recommended score. Another method is to sum the product of the route type score and the route type weight, and the product of the distance score and the distance weight, as the recommended score.

[0235] The preset recommendation criteria include: the recommended score for any target route is greater than a preset threshold.

[0236] It should be noted that the preset threshold can be 7, 8, 9, etc. This application embodiment does not limit the preset threshold, and it can be determined according to the actual situation.

[0237] Furthermore, the preset recommendation criteria also include: the recommended score corresponding to any target route ranks among the top N in terms of the recommended scores of multiple routes to be recommended.

[0238] It should be noted that N is a preset integer greater than or equal to 1. N can be 1, 3, 5, etc. This application embodiment does not limit N and can be determined according to the actual situation.

[0239] It should be noted that if N is greater than the number of routes to be recommended, then N will be updated to the number of routes to be recommended.

[0240] It should be noted that the preset filtering conditions can be user-configurable. Users can configure them directly on the in-vehicle terminal or on the terminal device, and then the terminal device will send the preset filtering conditions to the in-vehicle terminal. All preset filtering conditions can be configured directly, and additional settings can be configured such as the correspondence between distance range and distance score, weather range and weather score, road maintenance level range and road condition score, route type weight, distance weight, weather weight, road condition weight, and N.

[0241] In another implementation, each route to be recommended has a corresponding recommendation score, and the preset recommendation conditions include: the recommendation score of any target route ranks among the top N of the recommendation scores of multiple routes to be recommended.

[0242] It should be noted that N is a preset integer greater than or equal to 1. N can be 1, 3, 5, etc. This application embodiment does not limit N and can be determined according to the actual situation.

[0243] It should be noted that if N is greater than the number of routes to be recommended, then N will be updated to the number of routes to be recommended.

[0244] It should be noted that the calculation method for the recommendation score is similar to that in the previous implementation method, and will not be repeated here.

[0245] The route recommendation method provided in this embodiment improves the matching degree between the recommended route and the user's requirements by determining the target route based on at least one of distance information, weather information, and traffic information, as well as the route type.

[0246] Figure 2 is a flowchart illustrating a third embodiment of the route recommendation method provided in this application. This embodiment describes how a target route is determined from multiple routes to be recommended based on the user's driving style. The method in this embodiment can be implemented through software, hardware, or a combination of both. As shown in Figure 2, the route recommendation method specifically includes the following steps:

[0247] S201: Obtain the driving style of the target user.

[0248] S202: Based on the preset correspondence between driving style and route type, determine the target route type corresponding to the target user's driving style.

[0249] S203: Recommend at least one destination route.

[0250] The route type for each target route is matched with the target route type.

[0251] It should be noted that the implementation process of this embodiment is similar to that of the route recommendation method embodiment one, and will not be described again here.

[0252] The route recommendation method provided in this embodiment, after obtaining the target user's driving style, determines the target route type corresponding to the user's driving style based on a preset correspondence between driving style and route type. Then, based on the target route type, it determines the target route from multiple routes to be recommended, and recommends at least one target route. Compared to existing technologies that only consider travel time and route length, this solution improves the matching degree between the recommended route and the user's requirements by recommending routes based on the user's driving style and route type.

[0253] Figure 3 is a flowchart illustrating a fourth embodiment of the route recommendation method provided in this application. This embodiment describes how the vehicle terminal interacts with the server to determine a target route from multiple routes to be recommended based on the user's driving style. The method in this embodiment can be implemented through software, hardware, or a combination of both. As shown in Figure 3, the route recommendation method specifically includes the following steps:

[0254] S301: The vehicle terminal obtains the driving style of the target user.

[0255] It should be noted that this step is similar to the process of obtaining the target user's driving style in S101 of the route recommendation method embodiment one, and will not be described again here.

[0256] S302: The vehicle terminal sends the target user's driving style to the server.

[0257] In this step, after the vehicle terminal obtains the target user's driving style, it sends the driving style to the server so that the server can subsequently determine the target route.

[0258] S303: After receiving the target user's driving style from the vehicle terminal, the server obtains route information for multiple routes to be recommended.

[0259] In this step, after the vehicle terminal sends the target user's driving style to the server, the server can receive the driving style and then obtain route information for multiple routes to be recommended. The route information for each route to be recommended includes the route type.

[0260] It should be noted that this step is similar to the process of obtaining route information for multiple routes to be recommended in S101 of the first embodiment of the route recommendation method, and will not be described again here.

[0261] S304: The server determines the target route type corresponding to the target user's driving style based on the preset correspondence between driving style and route type.

[0262] It should be noted that this step is similar to S102 in Embodiment 1 of the route recommendation method, and will not be described again here.

[0263] S305: Based on the route information, the server selects at least one route from multiple routes to be recommended as the target route.

[0264] It should be noted that this step is similar to S103 in Embodiment 1 of the route recommendation method, and will not be described again here.

[0265] S306: The server sends at least one target route to the vehicle terminal.

[0266] In this step, after the server determines the target route, it sends at least one target route to the vehicle terminal.

[0267] S307: The vehicle terminal receives at least one target route from the server.

[0268] In this step, the server sends at least one target route to the vehicle terminal, and the vehicle terminal can receive at least one target route from the server. The route type of each target route is matched with the target route type corresponding to the driving style of the target user.

[0269] The vehicle-mounted terminal can then sort and display the received target routes, either by ranking them in descending order of their recommendation scores. The calculation method for the recommendation scores is similar to that in Example 2 of the route recommendation method, and will not be repeated here.

[0270] It should be noted that if the vehicle terminal receives a route from the server before this route recommendation, that route will be stored as a route to be recommended and used in this route recommendation process. If the vehicle terminal receives a route from the server after this route recommendation and before the next route recommendation, that route will be stored as a route to be recommended and used in the next route recommendation process.

[0271] The route recommendation method provided in this embodiment interacts with the server through the vehicle terminal, and recommends routes based on the target user's driving style and route information of multiple routes to be recommended, thereby improving the matching degree between the recommended routes and the user's requirements.

[0272] Figure 4 is a flowchart illustrating a fifth embodiment of the route recommendation method provided in this application. Based on embodiment four, this embodiment further explains how the vehicle terminal updates the user's reward score in response to a route error report. As shown in Figure 4, the route recommendation method specifically includes the following steps:

[0273] S401: In response to the user's route error reporting operation, the vehicle terminal sends a route error reporting request to the server.

[0274] In this step, if a user discovers a route error while viewing the route, they can report the route error on the in-vehicle terminal. In response to the user's route error report, the in-vehicle terminal sends a route error request to the server, which includes the route to be reviewed.

[0275] S402: After receiving the route error request sent by the vehicle terminal, the server sends the route to be reviewed to the terminal device.

[0276] In this step, after the vehicle terminal sends a route error request to the server, the server can receive the route error request and then send the route to be reviewed in the route error request to the reviewer's terminal device in order to allow the reviewer to review it.

[0277] If the auditor determines that the route is incorrect, they send an approval message to the server using their terminal device, and the server then forwards the approval message to the vehicle terminal. If the auditor determines that the route is correct, they send a disapproval message to the server using their terminal device, and the server then forwards the disapproval message to the vehicle terminal.

[0278] S403: After receiving the approval message from the terminal device, the server sends the approval message to the vehicle terminal.

[0279] In this step, after the terminal device sends an approval message to the server, the server can receive the approval message and then send the approval message to the vehicle terminal.

[0280] S404: After the vehicle terminal receives the approval message from the server, it increases the user's reward points.

[0281] In this step, after the server sends the approval message to the vehicle terminal, the vehicle terminal can receive the approval message and then increase the user's reward points in order to reward the user.

[0282] It should be noted that the increase in reward points can be 1, 5, 10, 20, etc. This application embodiment does not limit the increase in reward points, and it can be determined according to the actual situation.

[0283] It should be noted that the user's reward points can be used to redeem benefits, prizes, etc., and can also be used to unlock vehicle function permissions, etc. This application embodiment does not limit the reward points.

[0284] It should be noted that if the vehicle terminal receives a message from the server indicating that the review has failed, the vehicle terminal will display a message indicating that the route is correct for the user to view.

[0285] The route recommendation method provided in this embodiment increases the user's reward score by responding to the user's route error operation through the vehicle terminal, thereby improving the user experience and the efficiency of route information maintenance.

[0286] Figure 5 is a flowchart illustrating a sixth embodiment of the route recommendation method provided in this application. This embodiment describes how the vehicle terminal groups routes to be recommended into route groups based on route information, and then recommends route groups. The method in this embodiment can be implemented through software, hardware, or a combination of both. As shown in Figure 5, the route recommendation method specifically includes the following steps:

[0287] S501: Obtain route information for multiple routes to be recommended.

[0288] In this step, in order to achieve route recommendation in the context of event or team activities, the vehicle terminal first obtains route information for multiple routes to be recommended. The route information for each route to be recommended includes the route type or information used to characterize the route type.

[0289] It should be noted that the information used to characterize the route type can be used to determine the route type. The information used to characterize the route type can be at least one of the following parameters: route length, average radius of curvature of the route, route curve diversity parameter, route elevation difference, number of natural scenic spots passed through, number of cultural scenic spots passed through, route maintenance level, route passability time, traffic volume, and number of terrain types.

[0290] Several preset route types can be identified, and the weight of each preset route type for each parameter can be set. Then, the parameter score is determined based on the parameter value of the route to be recommended and the correspondence between the parameter value range and the score. Based on the parameter score and the weight of each preset route type for each parameter, the matching score between the route to be recommended and each preset route type is determined. The preset route type with the largest matching score with the route to be recommended is taken as the route type of the route to be recommended.

[0291] It should be noted that the recommended routes can be officially set routes, routes created by users, or routes uploaded to the server by other users and then distributed to the vehicle terminal by the server.

[0292] It should be noted that this solution can recommend routes not only in the context of sporting events or team activities, where the recommended route is the route of the sporting event or team activity; it can also recommend routes in navigation scenarios, where the recommended route is based on the user's input starting point and the determined route.

[0293] It should be noted that any two routes to be recommended must satisfy the following condition: at least one of the route start point, route end point, and route waypoints must be different.

[0294] S502: Classify multiple routes to be recommended based on route information and generate at least one route group.

[0295] In this step, after the vehicle terminal obtains the route information, it classifies multiple routes to be recommended based on the route information and generates at least one route group.

[0296] Each route group includes at least one target route, and each target route is one of the routes to be recommended. The route types of all target routes in each route group are the same, while the route types of target routes in different route groups are different.

[0297] The vehicle terminal is configured with a matching degree between route types. If the matching degree between two route types is greater than a preset matching degree threshold, the two route types are considered to be consistent; if the matching degree is less than or equal to the preset matching degree threshold, the two route types are considered to be inconsistent. Therefore, multiple routes to be recommended can be classified according to the matching degree between route types, generating at least one route group. The route types of all routes to be recommended in each route group are consistent, while the route types of routes to be recommended in different route groups are inconsistent.

[0298] It should be noted that the preset matching threshold can be 80%, 85%, 90%, etc. This application embodiment does not limit the preset matching threshold, and it can be determined according to the actual situation.

[0299] This allows us to determine the target route within each route group.

[0300] The route information for the target route also includes at least one of the following: distance information, weather information, and traffic information. The distance information is used to represent the distance between the user's current location and the route location of the route to be recommended. The weather information is used to represent the weather conditions in the area where the route to be recommended is located at the current time or the scheduled travel time. The traffic information is used to represent the traffic conditions between the user's current location and the starting point of the route to be recommended.

[0301] The distance between the user's current location and the route location to be recommended can be either the straight-line distance between the current location and the route location, or the route length from the current location to the route location.

[0302] The location of the route to be recommended can be the starting point, the ending point, or a point along the route.

[0303] For any given route group, the route information for each target route meets the preset recommendation criteria.

[0304] In one implementation, the preset recommendation conditions include at least one of the following:

[0305] The distance between the user's current location and the location of the route to be recommended is less than a preset distance;

[0306] Alternatively, the weather conditions in the area where the recommended route is located at the current time or the scheduled travel time meet the preset weather requirements;

[0307] Alternatively, the traffic conditions between the user's current location and the starting point of the route to be recommended meet the preset traffic condition requirements.

[0308] It should be noted that the preset distance can be 10 kilometers, 20 kilometers, 50 kilometers, etc., and the preset weather requirements can be a weather set, such as {sunny, cloudy}, {sunny, cloudy, overcast, light rain}, {sunny, cloudy, overcast, light rain, light snow}, etc. The road conditions between the current location and the starting point of the route to be recommended must meet the preset road condition requirements if: the road surface maintenance level between the current location and the starting point of the route to be recommended is greater than the preset level, the number of damaged points between the current location and the starting point of the route to be recommended is less than the preset number of damaged points, and the number of construction points between the current location and the starting point of the route to be recommended is less than the preset number of construction points.

[0309] For example, road surface maintenance levels are divided into 5 levels, with higher maintenance levels indicating better road conditions. Preset levels can be 2, 3, 4, etc. Preset damage quantities can be 5, 7, 10, etc., and preset construction quantities can be 4, 6, 8, etc.

[0310] This application does not limit the preset distance, preset weather requirements, preset damage quantity, preset construction quantity, preset level, or whether the road conditions between the current location and the starting point of the route to be recommended meet the preset road condition requirements; these can be determined according to the actual situation.

[0311] It should be noted that the preset filtering conditions can be configured by the user. Users can configure them directly on the in-vehicle terminal or on the terminal device, which will then send the preset filtering conditions to the in-vehicle terminal. All preset filtering conditions can be configured directly, or specific parameters such as preset distance, preset weather requirements, preset damage quantity, preset construction quantity, and preset severity level can be configured.

[0312] In another implementation, each route type to be recommended has a corresponding route type score. The route type score is used to characterize the degree of matching between the route type and the route to be recommended. The route type score is also the matching score between the route to be recommended and the route type. The higher the road surface type score, the higher the degree of matching between the route type and the route to be recommended.

[0313] Each route to be recommended has a distance score corresponding to its distance information, a weather score corresponding to its weather information, and a road condition score corresponding to its road condition information.

[0314] Each route to be recommended has a corresponding recommendation score, which is calculated based on at least one of the following: route type score, distance score, weather score, and road condition score.

[0315] It should be noted that the distance score corresponding to the distance information can be determined based on the correspondence between the distance range and the distance score. For example, when the distance range is [0, 10), the unit is kilometers and the distance score is 10 points; when the distance range is [10, 50), the unit is kilometers and the distance score is 6 points; when the distance range is [50, +∞), the unit is kilometers and the distance score is 3 points. This application does not limit the correspondence between the distance range and the distance score, and it can be determined according to the actual situation.

[0316] It should be noted that the weather score corresponding to the weather information can be determined based on the correspondence between weather range and weather score. For example, the correspondence between weather range and weather score can be as follows: when the weather range is {sunny, cloudy, overcast}, the weather score is 10 points; when the weather range is {light rain, light snow}, the weather score is 6 points; when the weather range is {heavy rain, torrential rain, heavy snow, blizzard, fog, haze, hail, sandstorm}, the weather score is 3 points. This application embodiment does not limit the correspondence between weather range and weather score, and it can be determined according to the actual situation.

[0317] It should be noted that the road condition score corresponding to the road condition information can be determined based on the correspondence between the road maintenance level range and the road condition score. For example, the correspondence between the road maintenance level range and the road condition score can be as follows: when the road maintenance level range is (0, 1], the road condition score is 3 points; when the road maintenance level range is (1, 2], the road condition score is 6 points; and when the road maintenance level range is (2, 3], the road condition score is 10 points. This application embodiment does not limit the correspondence between the road maintenance level range and the road condition score, and it can be determined according to the actual situation.

[0318] The recommended score can be calculated by adding at least one of the following: route type score, distance score, weather score, and road condition score.

[0319] The recommended score can also be calculated as follows: the route type score corresponds to the route type weight, the distance score corresponds to the distance weight, the weather score corresponds to the weather weight, and the road condition score corresponds to the road condition weight; the recommended score is calculated based on at least one of the following: the product of the route type score and the route type weight, the product of the distance score and the distance weight, the product of the weather score and the weather weight, and the product of the road condition score and the road condition weight.

[0320] The recommended score can be obtained by adding or multiplying at least one of the following: the product of route type score and route type weight, the product of distance score and distance weight, the product of weather score and weather weight, and the product of road condition score and road condition weight.

[0321] The preset recommendation criteria include: the recommended score for any target route is greater than a preset threshold; or, the recommended score for any target route in each route group ranks among the top N in that route group.

[0322] It should be noted that N is a preset integer greater than or equal to 1, and N can be 1, 3, 5, etc.; the preset threshold can be 7, 8, 9, etc. This application embodiment does not limit N or the preset threshold, and can be determined according to the actual situation.

[0323] It should be noted that the preset filtering conditions can be user-configurable. Users can configure them directly on the in-vehicle terminal or on the terminal device, and then the terminal device will send the preset filtering conditions to the in-vehicle terminal. All preset filtering conditions can be configured directly, and additional settings can be configured such as the correspondence between distance range and distance score, weather range and weather score, road maintenance level range and road condition score, route type weight, distance weight, weather weight, road condition weight, and N.

[0324] It should be noted that there can be at least two target routes that satisfy the condition that at least one of the route's starting point and the route's ending point is different.

[0325] S503: At least one route group is recommended.

[0326] In this step, after the vehicle terminal generates a route group, at least one route group is recommended.

[0327] Recommended methods could include: sending route group information for at least one route group to the user's terminal device; displaying route group information for at least one of the route groups; or displaying route group information for at least one route group after sending it to the target user's terminal device.

[0328] It should be noted that the number of recommended route groups can be a preset number of recommendations, or it can be the rounded-up value of the product of the total number of route groups and the preset recommendation ratio. The preset number of recommendations can be 3, 4, 7, etc., and the preset recommendation ratio can be 60%, 70%, 80%, etc. This application embodiment does not limit the preset number of recommendations and the preset recommendation ratio, and they can be determined according to the actual situation.

[0329] The route group information includes the route type of the route group and the destination routes in the route group. The route type of the route group can be the route type of the destination routes in the route group, or it can be the route type of all routes in the route group.

[0330] When displaying target routes within route group information for at least one route group, for each route group, the target routes in that route group are sorted according to their route type score or recommendation score, and related information for each target route is displayed. The sorting can be in descending order or ascending order.

[0331] Information related to the target route includes at least one of the following: waypoints, travel time period, route description, route length, estimated travel time, and rating.

[0332] Furthermore, for each route group in at least one route group, non-target routes in the route group are displayed. Any non-target route is one of the multiple routes to be recommended in the route group other than the target route, and the display position of any non-target route is after any target route in the route group.

[0333] After the vehicle terminal displays the target route, it can sort the target routes according to parameters such as route length, estimated travel time, and the length between the current user and the route starting point. It can also filter the target routes according to the route location.

[0334] Users can also save their target routes.

[0335] The route recommendation method provided in this embodiment obtains route information for multiple routes to be recommended, determines the road surface type based on the route information, and then classifies the multiple routes to be recommended according to the road surface type to generate at least one route group. Each route group includes at least one target route, and the road surface types of all target routes in each route group are the same, while the road surface types of target routes in different route groups are different; thus, at least one route group is recommended. This solution classifies routes to be recommended based on route information and then makes recommendations, realizing route recommendation in scenarios such as sports events or team activities.

[0336] Figure 6 is a flowchart illustrating a seventh embodiment of the route recommendation method provided in this application. This embodiment describes how the vehicle terminal groups routes to be recommended into route groups based on route information, and then recommends route groups. The method in this embodiment can be implemented through software, hardware, or a combination of both. As shown in Figure 6, the route recommendation method specifically includes the following steps:

[0337] S601: Obtain route information for multiple routes to be recommended.

[0338] In this step, in order to achieve route recommendation in the context of event activities or team activities, the vehicle terminal first obtains route information for multiple routes to be recommended. The route information for each route to be recommended includes at least one route attribute or information used to characterize at least one route attribute.

[0339] At least one route attribute includes at least one of the following: route type, distance information, weather information, and traffic information.

[0340] Distance information is used to represent the distance between the user's current location and the location of the route to be recommended; weather information is used to represent the weather conditions in the area where the route to be recommended is located at the current time or the scheduled travel time; and traffic information is used to represent the traffic conditions between the user's current location and the starting point of the route to be recommended.

[0341] It should be noted that information characterizing at least one route attribute can be used to determine the route attribute. Information characterizing the route type can be at least one of the following parameters: route length, average radius of curvature of the route, route curve diversity parameter, route elevation difference, number of natural scenic spots passed through, number of cultural scenic spots passed through, route maintenance level, route passability time, traffic volume, and number of terrain types.

[0342] Several preset route types can be identified, and the weight of each preset route type for each parameter can be set. Then, the parameter score is determined based on the parameter value of the route to be recommended and the correspondence between the parameter value range and the score. Based on the parameter score and the weight of each preset route type for each parameter, the matching score between the route to be recommended and each preset route type is determined. The preset route type with the largest matching score with the route to be recommended is taken as the route type of the route to be recommended.

[0343] The information used to represent distance can be the location of the route to be recommended. The distance between the user's current location and the location of the route to be recommended can be determined by comparing their current location and the location of the route to be recommended. This distance can be the straight-line distance between the user's current location and the route location, or the route length from the current location to the route location. The location of the route to be recommended can be the starting point of the route, the ending point of the route, or a waypoint along the route.

[0344] The information used to characterize weather information can be the weather conditions in the area where the recommended route is located. Weather information can be obtained by combining the travel time with the weather conditions at the time of travel.

[0345] The information used to characterize traffic conditions can be the traffic conditions between multiple locations and the starting point of the route to be recommended. These multiple locations include the user's current location; by referring to these locations, the traffic conditions between the user's current location and the starting point of the route to be recommended can be determined, thus obtaining the traffic condition information.

[0346] It should be noted that at least one route attribute is preset. This attribute can be set by the user in the terminal device, or it can be set by staff in the terminal device when the vehicle leaves the factory.

[0347] It should be noted that any two routes to be recommended must satisfy the following condition: at least one of the route start point, route end point, and route waypoints must be different.

[0348] S602: Classify multiple routes to be recommended based on route attributes and generate at least one route group.

[0349] In this step, after the vehicle terminal obtains the route information and determines the route attributes, it classifies multiple routes to be recommended based on the route information, that is, based on the route attributes, and generates at least one route group.

[0350] Each route group includes at least one target route, each target route is one of the routes to be recommended, at least one route attribute includes the target route attribute, the target route attributes of all target routes in each route group are consistent, and the target route attributes of target routes in different route groups are inconsistent.

[0351] The vehicle terminal first determines the target route attribute from at least one route attribute.

[0352] It should be noted that the method for determining the target route attribute can be as follows: the user selects from at least one route attribute on the terminal device, and the vehicle terminal responds to the selection operation by using the route attribute selected by the user as the target route attribute. Alternatively, the vehicle terminal can randomly select one from at least one route attribute as the target route attribute. Another method is that the vehicle terminal is configured with a target route attribute selection sequence, and the vehicle terminal randomly selects one from the intersection of the target route attribute selection sequence and the at least one route attribute as the target route attribute. This application does not limit the method for determining the target route type; it can be determined according to the actual situation.

[0353] Then, classify the routes according to their attributes to obtain at least one route group, and determine the target routes in each route group.

[0354] When the target route attribute is route type, the process of classifying and determining the target route is similar to step S502 in Example 6, and will not be repeated here.

[0355] When the target route attribute is distance information, each recommended route has a corresponding distance score. The in-vehicle terminal has multiple preset distance score classification ranges. Distance information belonging to the same preset distance score classification range is consistent, while distance information belonging to different preset distance score classification ranges is inconsistent. Recommended routes with distance scores belonging to the same preset distance score classification range are grouped together as a route group.

[0356] For each route group, the routes whose distance scores rank among the top N in that route group are selected as the target routes.

[0357] It should be noted that N is a preset integer greater than or equal to 1. N can be 1, 3, 5, etc. This application embodiment does not limit N and can be determined according to the actual situation.

[0358] It should be noted that the distance score corresponding to the distance information can be determined based on the correspondence between the distance range and the distance score. For example, when the distance range is [0, 10), the unit is kilometers and the distance score is 10 points; when the distance range is [10, 50), the unit is kilometers and the distance score is 6 points; when the distance range is [50, +∞), the unit is kilometers and the distance score is 3 points. This application does not limit the correspondence between the distance range and the distance score, and it can be determined according to the actual situation.

[0359] The preset distance score classification range can be [0, 3], (3, 5], (5, 7], (7, 10], etc. This application embodiment does not limit the preset distance score classification range, and it can be determined according to the actual situation.

[0360] When the target route attribute is weather information, each recommended route has a corresponding weather score. The in-vehicle terminal has multiple preset weather score classification ranges. Weather information within the same preset weather score classification range is consistent, while weather information within different preset weather score classification ranges is inconsistent. Recommended routes with weather scores within the same preset weather score classification range are grouped together as a route group.

[0361] For each route group, the routes with the best weather scores in the group are selected as the target routes.

[0362] It should be noted that N is a preset integer greater than or equal to 1. N can be 1, 3, 5, etc. This application embodiment does not limit N and can be determined according to the actual situation.

[0363] It should be noted that the weather score corresponding to the weather information can be determined based on the correspondence between weather range and weather score. For example, the correspondence between weather range and weather score can be as follows: when the weather range is {sunny, cloudy, overcast}, the weather score is 10 points; when the weather range is {light rain, light snow}, the weather score is 6 points; when the weather range is {heavy rain, torrential rain, heavy snow, blizzard, fog, haze, hail, sandstorm}, the weather score is 3 points. This application embodiment does not limit the correspondence between weather range and weather score, and it can be determined according to the actual situation.

[0364] The preset weather score classification range can be [0, 3], (3, 5], (5, 7], (7, 10], etc. This application embodiment does not limit the preset weather score classification range, and it can be determined according to the actual situation.

[0365] When the target route attribute is traffic information, each recommended route has a corresponding traffic score. The in-vehicle terminal has multiple preset traffic score classification ranges. Traffic information within the same preset traffic score classification range is consistent, while traffic information within different preset traffic score classification ranges is inconsistent. Recommended routes with traffic scores within the same preset traffic score classification range are grouped together as a route group.

[0366] For each route group, the N routes with the best road condition scores in the route group are selected as the target routes.

[0367] It should be noted that N is a preset integer greater than or equal to 1. N can be 1, 3, 5, etc. This application embodiment does not limit N and can be determined according to the actual situation.

[0368] It should be noted that the road condition score corresponding to the road condition information can be determined based on the correspondence between the road maintenance level range and the road condition score. For example, the correspondence between the road maintenance level range and the road condition score can be as follows: when the road maintenance level range is (0, 1], the road condition score is 3 points; when the road maintenance level range is (1, 2], the road condition score is 6 points; and when the road maintenance level range is (2, 3], the road condition score is 10 points. This application embodiment does not limit the correspondence between the road maintenance level range and the road condition score, and it can be determined according to the actual situation.

[0369] The preset road condition score classification range can be [0, 3], (3, 5], (5, 7], (7, 10], etc. This application embodiment does not limit the preset road condition score classification range, and it can be determined according to the actual situation.

[0370] It should be noted that there can be at least two target routes that satisfy the condition that at least one of the route's starting point and the route's ending point is different.

[0371] S603: At least one route group is recommended.

[0372] In this step, after the vehicle terminal generates a route group, at least one route group is recommended.

[0373] Recommended methods could include: sending route group information for at least one route group to the user's terminal device; displaying route group information for at least one of the route groups; or displaying route group information for at least one route group after sending it to the target user's terminal device.

[0374] It should be noted that the number of recommended route groups can be a preset number of recommendations, or it can be the rounded-up value of the product of the total number of route groups and the preset recommendation ratio. The preset number of recommendations can be 3, 4, 7, etc., and the preset recommendation ratio can be 60%, 70%, 80%, etc. This application embodiment does not limit the preset number of recommendations and the preset recommendation ratio, and they can be determined according to the actual situation.

[0375] The route group information includes the route type of the route group and the destination routes in the route group. The route type of the route group can be the route type of the destination routes in the route group, or it can be the route type of all routes in the route group.

[0376] When displaying the target routes in the route group information of at least one route group, if the target routes are determined based on the road surface type, then for each route group in the at least one route group, the target routes in that route group are sorted and displayed according to the route type score or recommendation score of the target route, and information related to each target route is displayed.

[0377] If the target route is determined based on distance information, then for each route group in at least one route group, the target routes in that route group are sorted and displayed according to the distance score of the target route, and information related to each target route is displayed.

[0378] If the target route is determined based on weather information, then for each route group in at least one route group, the target routes in that route group are sorted and displayed according to the weather score of that target route, and information related to each target route is displayed.

[0379] If the target route is determined based on traffic information, then for each route group in at least one route group, the target routes in that route group are sorted and displayed according to their traffic score, and information related to each target route is displayed.

[0380] Sorting can be done in descending order or in ascending order.

[0381] Information related to the target route includes at least one of the following: waypoints, travel time period, route description, route length, and estimated travel time.

[0382] Furthermore, for each route group in at least one route group, non-target routes in the route group are displayed. Any non-target route is one of the multiple routes to be recommended in the route group other than the target route, and the display position of any non-target route is after any target route in the route group.

[0383] The route recommendation method provided in this embodiment obtains route information for multiple routes to be recommended, determines road surface attributes based on the route information, and then classifies the multiple routes to be recommended according to the road surface attributes to generate at least one route group. The route information includes route attributes. Each route group includes at least one target route. The route attributes of all target routes in each route group are consistent, while the route attributes of target routes in different route groups are inconsistent; thus, at least one route group is recommended. This solution classifies routes to be recommended based on route information and then makes recommendations, realizing route recommendation in scenarios such as sports events or team activities.

[0384] Figure 7 is a flowchart illustrating an eighth embodiment of the route recommendation method provided in this application. This embodiment describes how an in-vehicle terminal recommends routes based on the user's preference information for at least one route parameter, combined with the parameter information of the route to be recommended. The method in this embodiment can be implemented through software, hardware, or a combination of both. As shown in Figure 7, the route recommendation method specifically includes the following steps:

[0385] S701: Obtain parameter information for multiple routes to be recommended, as well as user preference information for at least one route parameter.

[0386] In this step, in order to achieve route recommendation, the vehicle terminal first obtains parameter information of multiple routes to be recommended, as well as user preference information for at least one route parameter.

[0387] The parameter information for each route to be recommended includes at least one route parameter; the user's preference information for at least one route parameter is the ranking of these route parameters.

[0388] It should be noted that the vehicle terminal can obtain the user's preference information for at least one route parameter in the following ways: the vehicle terminal displays all route parameters, and the user selects at least one route parameter in order of preference from highest to lowest according to their own situation. The vehicle terminal can then obtain the user's preference information for at least one route parameter.

[0389] Another way for the vehicle-mounted terminal to obtain the user's preference information for at least one route parameter is: the user sends the preference information for at least one route parameter to the vehicle-mounted terminal using a terminal device, and the vehicle-mounted terminal can then obtain the user's preference information for at least one route parameter.

[0390] Another way for the vehicle terminal to obtain the user's preference information for at least one route parameter is as follows: the vehicle terminal stores the user's preference information for at least one route parameter each time it obtains it. When recommending routes, the vehicle terminal displays the stored preference information, and the user selects from it. In this way, the vehicle terminal can obtain the user's preference information for at least one route parameter.

[0391] This application does not limit the method by which the vehicle terminal obtains the user's preference information for at least one route parameter, and can be determined according to the actual situation.

[0392] It should be noted that this solution can not only recommend routes for the same starting point and destination in navigation scenarios, but also recommend routes for different team activities and events. Therefore, any two routes to be recommended must satisfy the following condition: at least one of the route starting point, route ending point and route waypoints is different.

[0393] S702: Determine the weight of each route parameter based on the user's preference information for at least one route parameter.

[0394] In this step, the vehicle terminal obtains parameter information of multiple routes to be recommended, as well as user preference information for at least one route parameter, and determines the weight of each route parameter based on the user's preference information for at least one route parameter.

[0395] If a user's preference information for at least one route parameter contains only one route parameter, then the weight of that route parameter is 1.

[0396] If a user's preference information for at least one route parameter includes multiple route parameters, then the weight of each route parameter is determined based on the number of route parameters and the correspondence between the number and the weight.

[0397] For example, in a user's preference information for at least one route parameter, there are two route parameters, A and B, respectively. Based on the correspondence between quantity and weight, two weights are determined, which are 0.7 and 0.3 respectively. The weight of A is 0.7 and the weight of B is 0.3.

[0398] The user's preference information for at least one route parameter includes three route parameters, namely C, D, and E. Based on the correspondence between quantity and weight, three weights are determined, namely 0.5, 0.3, and 0.2, respectively. The weight of C is 0.5, the weight of D is 0.3, and the weight of E is 0.2.

[0399] The user's preference information for at least one route parameter includes four route parameters, namely F, G, H, and I. Based on the correspondence between quantity and weight, four weights are determined, namely 0.5, 0.3, 0.1, and 0.1, respectively. The weight of F is 0.5, the weight of G is 0.3, the weight of H is 0.1, and the weight of I is 0.1.

[0400] This application does not limit the correspondence between route parameters, quantity, and weight in the user's preference information for at least one route parameter; it can be determined according to the actual situation.

[0401] S703: Based on the weight of each route parameter and the parameter information of multiple routes to be recommended, select at least one route to be recommended as the target route from the multiple routes to be recommended.

[0402] In this step, after the vehicle terminal determines the weight of each route parameter, it selects at least one route from the multiple routes to be recommended as the target route based on the weight of each route parameter and the parameter information of multiple routes to be recommended.

[0403] Specifically, for each route to be recommended, a recommendation score is calculated based on the parameter information of the route and the weight of each route parameter.

[0404] First, based on the parameter information of the route to be recommended, determine the score for each route parameter. Since each attribute has a corresponding attribute range and score, the score for each route parameter of the route to be recommended can be determined.

[0405] Then, based on the weight of each route parameter and the rating of the route to be recommended for each route parameter, the recommendation score of the route to be recommended is calculated. That is, the recommendation score is obtained by multiplying the weight of each route parameter by its rating and then summing the results.

[0406] After determining the recommendation score for each route to be recommended, the vehicle terminal selects at least one route from the multiple routes to be recommended as the target route based on the recommendation score of each route.

[0407] In one implementation, the vehicle terminal can sort the recommended routes in descending order of recommendation scores to obtain a route sequence, and then select the first preset number of routes in the route sequence as the target routes.

[0408] In another implementation, the vehicle terminal selects routes with a recommended score greater than a preset score as the target routes.

[0409] It should be noted that the preset quantity can be 1, 3, 5, etc., and the preset score can be 6, 7, 9, etc. This application embodiment does not limit the preset quantity and preset score, and can be determined according to the actual situation.

[0410] S704: Recommend at least one destination route.

[0411] In this step, once the vehicle-mounted terminal determines the target route, it can recommend at least one target route.

[0412] Recommending at least one destination route can be done in several ways: Displaying at least one destination route; Sending at least one destination route to the target user's terminal device; or Displaying at least one destination route after sending it to the target user's terminal device.

[0413] Displaying at least one target route can be done by showing them in descending order of recommendation scores. Furthermore, non-target routes can also be displayed; any non-target route is one of multiple routes to be recommended, excluding the target routes, and is displayed after any target route.

[0414] It should be noted that the number of recommended target routes can be a preset number of recommendations, or it can be the rounded-up value of the product of the total number of target routes and the preset recommendation ratio. The preset number of recommendations can be 3, 4, 7, etc., and the preset recommendation ratio can be 60%, 70%, 80%, etc. This application embodiment does not limit the preset number of recommendations and the preset recommendation ratio, and they can be determined according to the actual situation.

[0415] In one implementation, there exist at least two target routes that satisfy the condition that at least one of the route's starting point and the route's ending point is different.

[0416] In one implementation, there exists at least one target route that satisfies the condition that the target user's current location is not the same as the starting point of the target route.

[0417] After a user selects a target route, the vehicle terminal can display the route information for that target route. The route information includes parameter information, as well as at least one of the following: route elevation difference, percentage of forest roads, percentage of mountain roads, percentage of suburban roads, and percentage of urban roads.

[0418] It should be noted that when there is only one route parameter in the user's preference information for at least one route parameter, and the preset number is greater than 1, the routes to be recommended can be sorted and displayed according to the route parameters determined by the user.

[0419] It should be noted that if the user is not satisfied with the recommended target route, they can enter the route start point, route end point, waypoints, and preference information for at least one route parameter, and the vehicle terminal will regenerate the route based on this data.

[0420] It should be noted that users can also send their target route to other users' terminal devices or in-vehicle terminals via their own devices or in-vehicle terminals, thereby sharing routes and improving the driving experience and user engagement.

[0421] The route recommendation method provided in this embodiment determines the weight of each route parameter based on the user's preference information for at least one route parameter, and then selects at least one route from multiple routes to be recommended as the target route, combining the parameter information of each recommended route, and then recommends at least one target route. Compared with the prior art that only considers travel time and route length, this solution determines the target route to be recommended to the user from multiple routes to be recommended by using the user's preference information for at least one route parameter, thereby improving the matching degree between the route and the user's requirements.

[0422] Figure 8 is a flowchart illustrating Embodiment 9 of the route recommendation method provided in this application. This embodiment describes how the vehicle terminal determines the score of each route parameter based on the parameter information of the route to be recommended. As shown in Figure 8, the route recommendation method specifically includes the following steps:

[0423] S801: Determine the score of the curve information for the recommended route based on the total number of curves, the average length of curves, and the total number of consecutive curves.

[0424] In this step, after the vehicle terminal determines the weight of each route parameter, it needs to determine the score of the recommended route for each route parameter based on the parameter information of the route to be recommended.

[0425] At least one route parameter includes curve information, vehicle speed, release time, and driving feedback information. The curve information for each route to be recommended includes at least one of the total number of curves, average curve length, and total number of consecutive curves. The driving feedback information for each route to be recommended includes at least one driving feedback score.

[0426] Therefore, the score for curve information of the recommended route is determined based on the total number of curves, the average length of curves, and the total number of consecutive curves.

[0427] Specifically, the first score is determined based on the total number of curves and the correspondence between the range of the total number of curves and the score.

[0428] The second score is determined based on the average length of the curve and the correspondence between the average length of the curve and the score.

[0429] The third score is determined based on the total number of consecutive curves and the correspondence between the range of consecutive curves and the score.

[0430] The sum of the first, second, and third scores is used as the score for the curve information of the route to be recommended.

[0431] It should be noted that if the curve information only includes any two of the following parameters: total number of curves, average curve length, and total number of consecutive curves, the sum of the scores determined by these two parameters will be used as the score for the curve information of the recommended route. If the curve information only includes any one of the following parameters: total number of curves, average curve length, and total number of consecutive curves, the score determined by this parameter will be used as the score for the curve information of the recommended route.

[0432] For example, the correspondence between the total number of curves and the score can be as follows: when the total number of curves is in the range of [0, 20), the score is 3 points; when the total number of curves is in the range of [20, 100), the score is 6 points; and when the total number of curves is in the range of [100, +∞), the score is 10 points.

[0433] For example, the correspondence between the average curve length range and the score can be as follows: when the average curve length range is [0, 100), the unit is meters and the score is 3 points; when the average curve length range is [100, 300), the unit is meters and the score is 6 points; when the average curve length range is [300, +∞), the unit is meters and the score is 10 points.

[0434] For example, the correspondence between the total number of consecutive curves and the score can be as follows: when the total number of consecutive curves is in the range of [0, 5), the score is 3 points; when the total number of consecutive curves is in the range of [5, 20), the score is 6 points; when the total number of consecutive curves is in the range of [20, +∞), the score is 10 points.

[0435] It should be noted that the embodiments of this application do not limit the correspondence between the total number of curves and the score, the correspondence between the average length of curves and the score, or the correspondence between the total number of consecutive curves and the score; these can be determined according to the actual situation.

[0436] S802: Determine the vehicle speed rating for the recommended route based on the vehicle speed of the route to be recommended and the pre-defined correspondence between the speed range and the rating.

[0437] In this step, the vehicle terminal determines the rating of the recommended route for vehicle speed based on the vehicle speed of the route to be recommended and the pre-defined correspondence between speed range and rating.

[0438] For example, the preset speed range and the corresponding score can be: when the speed range is [0, 30) ∪ [180, +∞), the unit is km / h and the score is 3 points; when the speed range is [30, 50), the unit is km / h and the score is 6 points; when the speed range is [50, 180), the unit is km / h and the score is 10 points.

[0439] It should be noted that the embodiments of this application do not limit the correspondence between the preset speed range and the score, and can be determined according to the actual situation.

[0440] S803: Determine the rating of the route to be recommended based on the release time, the current time, and the preset correspondence between the duration range and the rating.

[0441] In this step, the vehicle terminal calculates the time between the release time of the route to be recommended and the current time, and then determines the rating of the route to be recommended relative to the release time by combining the preset time range and the correspondence between the rating.

[0442] For example, the preset correspondence between duration range and score can be as follows: when the duration range is [0, 2), the unit is hours and the score is 10 points; when the duration range is [2, 12), the unit is hours and the score is 8 points; when the duration range is [12, 36), the unit is hours and the score is 6 points; when the duration range is [36, +∞), the unit is hours and the score is 3 points.

[0443] It should be noted that the embodiments of this application do not limit the correspondence between the preset duration range and the score, and can be determined according to the actual situation.

[0444] S804: Determine the rating of the recommended route for the driving feedback information based on at least one driving feedback score of the recommended route.

[0445] In this step, since the driving feedback information for each route to be recommended includes at least one driving feedback score, the rating of the driving feedback information for the route to be recommended is determined based on at least one driving feedback score for the route to be recommended.

[0446] It should be noted that the average of the driving feedback scores included in the driving feedback information can be used as the score for the recommended route. Alternatively, the maximum value of the driving feedback scores can be used as the score. The mode of the driving feedback scores can also be used as the score. This application does not limit the method of determining the score for the recommended route based on at least one driving feedback score; it can be determined according to the actual situation.

[0447] It should be noted that when the driving feedback information for each route to be recommended includes the number of favorites, the rating of the driving feedback information for the route to be recommended can be determined based on the number of favorites and the preset correspondence between the number of favorites and the rating.

[0448] For example, the preset correspondence between the number of collections and the rating can be as follows: when the number of collections is [0, 30), the rating is 3 points; when the number of collections is [30, 150), the rating is 6 points; when the number of collections is [150, +∞), the rating is 10 points.

[0449] It should be noted that the embodiments of this application do not limit the correspondence between the preset range of collections and the rating, and can be determined according to the actual situation.

[0450] It should be noted that the execution order of steps S801-S804 can be: step S801, step S802, step S803, step S804; or it can be: step S802, step S801, step S804, step S803; or step S804, step S802, step S801, step S803. This embodiment does not limit the execution order of steps S801-S804, and it can be determined according to the actual situation.

[0451] The route recommendation method provided in this embodiment determines the score of the route to be recommended for each route parameter by using the route parameters of the route to be recommended and the corresponding relationship between the route parameter range and the score, thereby improving the accuracy of the score.

[0452] Figure 9 is a flowchart illustrating Embodiment 10 of the route recommendation method provided in this application. This embodiment describes the case where the vehicle-mounted terminal recommends routes based on route type. As shown in Figure 9, the route recommendation method specifically includes the following steps:

[0453] S901: In response to the user's type recommendation operation, obtain the route type for each route to be recommended.

[0454] Different users have different preferences for different route types, and this solution can also recommend routes based on route type.

[0455] In this step, the user wants to view recommended routes under different route types and performs a type recommendation operation on the vehicle terminal. Since the vehicle terminal stores the route type of each route to be recommended, the vehicle terminal can respond to the user's type recommendation operation and obtain the route type of each route to be recommended.

[0456] It should be noted that the number of route types can be 2, 4, 8, etc. This application embodiment does not limit the number of route types and can be determined according to the actual situation.

[0457] S902: Based on the route type and recommendation score of each route to be recommended, recommend a type of recommended route for each route type.

[0458] In this step, after the vehicle terminal determines the route type of each route to be recommended, it recommends a type of recommended route corresponding to each route type based on the route type and recommendation score of each route to be recommended.

[0459] The routes to be recommended are grouped according to route type, with routes in the same group having the same route type and routes in different groups having different route types. Then, within each group, the routes are sorted in descending order of recommendation score to obtain the route sequence corresponding to each route type. Finally, the route sequence corresponding to each route type is recommended for users to view.

[0460] It should be noted that if the number of routes to be recommended in the route sequence is greater than the preset number, the first preset number of routes can be retained, and the remaining routes can be deleted. The preset number can be 1, 3, 5, etc., and this embodiment does not limit the preset number, which can be determined according to the actual situation.

[0461] It should be noted that routes with recommended scores lower than the preset score in the route sequence corresponding to each route type can be deleted before being recommended.

[0462] The route recommendation method provided in this embodiment improves user experience by recommending routes based on their route type and recommendation score, thereby making the recommended routes more closely match the user's requirements.

[0463] Figure 10 is a flowchart illustrating an eleventh embodiment of the route recommendation method provided in this application. This embodiment describes how the vehicle terminal determines the driving style based on initial driving data, as well as the reference average value and reference standard deviation. The method in this embodiment can be implemented through software, hardware, or a combination of both. As shown in Figure 10, the driving style determination method specifically includes the following steps:

[0464] S1001: Acquire at least one initial driving data.

[0465] In this step, in order to determine the user's driving style, at least one type of initial driving data needs to be obtained.

[0466] In one implementation, the at least one type of initial driving data is configured by the user. The in-vehicle terminal may display an initial driving data configuration interface, where the user inputs the initial driving data. The in-vehicle terminal may also display an initial driving data calculation questionnaire, where the user selects options for questions in the questionnaire, and the in-vehicle terminal determines the corresponding initial driving data based on the user's selections.

[0467] In another implementation, the at least one initial driving data is the user's historical driving data.

[0468] It should be noted that the types of initial driving data include accelerator pedal opening, brake pedal opening, longitudinal acceleration, lateral acceleration, straight-line speed, exit speed, entry speed, steering angle, etc. This application embodiment does not limit the types of initial driving data, which can be determined according to the actual situation.

[0469] S1002: For each type of initial driving data, the data in the initial driving data is filtered according to the reference average and reference standard deviation corresponding to the pre-acquired initial driving data to obtain the target driving data corresponding to the initial driving data.

[0470] In this step, after the vehicle terminal obtains various initial driving data from the user, since the user will inevitably pass through some abnormal road sections or encounter abnormal situations during the driving process, such as passing through natural disaster road sections or encountering traffic accidents, some abnormal data will be present in the initial driving data. Therefore, it is necessary to filter the data in the initial driving data to remove abnormal data, which can further improve the accuracy of driving style.

[0471] For each type of initial driving data, the data in the initial driving data is filtered according to the reference average and reference standard deviation corresponding to the pre-acquired initial driving data to obtain the target driving data corresponding to the initial driving data.

[0472] Specifically, for each data point in the initial driving data, a standard score (Z-score, also known as Z score) is calculated based on the data point and the reference mean and reference standard deviation corresponding to the initial driving data.

[0473] Formulas can be used Calculate the standard score, where Z represents the standard score, x represents the data in the initial driving data, μ represents the reference mean corresponding to the initial driving data, and σ represents the reference standard deviation corresponding to the initial driving data.

[0474] Data with a standard score greater than a preset filtering threshold in the initial driving data is deleted to obtain the target driving data corresponding to the initial driving data.

[0475] It should be noted that the preset filtering threshold can be 2.5, 2.7, 3, 3.2, etc. This application embodiment does not limit the preset filtering threshold, which can be determined according to the actual situation.

[0476] Since in a standard normal distribution, 68.27% of the data points fall within one standard deviation of the mean, 95.45% fall within two standard deviations, and 99.73% fall within three standard deviations, the preset filtering threshold can be set to 3. A standard score greater than 3 indicates that the data point differs significantly from the rest of the data, and is therefore considered outlier.

[0477] In one implementation, the reference average for each type of initial driving data is the average of the initial driving data from multiple drivers; the reference standard deviation for each type of initial driving data is the standard deviation of the initial driving data from multiple drivers. Before determining a user's driving style, the on-board terminal needs to acquire multiple types of initial driving data from multiple drivers; then calculate the average of each type of initial driving data to obtain the reference average for each type of initial driving data; calculate the standard deviation of each type of initial driving data, obtain the reference standard deviation for each type of initial driving data, and store it so that it can be used as reference data to determine the driving style later, which can improve the accuracy of driving style determination. Furthermore, determining the reference average and reference standard deviation for each type of initial driving data before determining the driving style can improve the efficiency of subsequent driving style determination.

[0478] In another implementation, the reference mean and reference standard deviation for each type of initial driving data are preset values. These can be set by staff in the vehicle terminal, or the vehicle terminal can obtain the reference mean and reference standard deviation from a server and then set them.

[0479] S1003: Determine the user's driving style based on the reference average, reference standard deviation, and target driving data corresponding to each initial driving data.

[0480] In this step, after the vehicle terminal determines the target driving data corresponding to each type of initial driving data, it combines the reference average value and reference standard deviation corresponding to each type of initial driving data to determine the user's driving style.

[0481] Driving styles can be categorized into straight-line driving style, curve driving style, and balanced driving style. Users of the straight-line driving style prefer driving on straight roads. Users of the curve driving style prefer driving through curves. Users of the balanced driving style prefer a smooth, comfortable driving experience with good fluidity.

[0482] Straight-line driving style is the first preset driving style, curved driving style is the second preset driving style, and balanced driving style is the third preset driving style.

[0483] Therefore, based on the reference average and reference standard deviation corresponding to each initial driving data, at least one style distinction threshold corresponding to each initial driving data can be determined; and the average value of the target driving data corresponding to each initial driving data can be calculated to obtain the target data value corresponding to each initial driving data.

[0484] The at least one style distinction threshold corresponding to each initial driving data includes at least one of a first threshold, a second threshold, a third threshold, and a fourth threshold, wherein the first threshold is greater than the second threshold, the second threshold is greater than the third threshold, and the third threshold is greater than the fourth threshold. The first threshold is μ+2kσ, the second threshold is μ+kσ, the third threshold is μ-kσ, and the fourth threshold is μ-2kσ, where μ is the reference average value corresponding to the initial driving data, σ is the reference standard deviation corresponding to the initial driving data, and k takes a value between 1 and 2, such as 1, 1.2, 1.5, 1.7, 2, etc. The embodiments of this application do not limit the size of k, and it can be determined according to the actual situation.

[0485] Then, based on at least one style distinction threshold and target data value corresponding to each initial driving data, the user's driving style is determined.

[0486] The driving style determination method provided in this embodiment determines the user's driving style by filtering the data in each initial driving data set based on a reference average and reference standard deviation corresponding to at least one type of initial driving data, and then combining the reference average and reference standard deviation. This solution determines the user's driving style using the reference average and reference standard deviation, along with the user's initial driving data, eliminating the need for the user to determine the style based on a driving style name, thus effectively improving the accuracy of the determined driving style.

[0487] Figure 11 is a flowchart illustrating embodiment twelve of the route recommendation method provided in this application. Based on the above embodiments, this application embodiment describes the determination of driving style according to at least one style differentiation threshold and target data value corresponding to each initial driving data. As shown in Figure 11, the driving style determination method specifically includes the following steps:

[0488] S1101: Based on at least one style distinction threshold and target data value corresponding to each initial driving data, determine whether at least one of the preset first condition, preset second condition and preset third condition is true; if at least one of the preset first condition, preset second condition and preset third condition is true, then proceed to step S1102; if all of the preset first condition, preset second condition and preset third condition are false, then proceed to step S1103.

[0489] In this step, driving styles can be categorized into straight-line driving style, curved-course driving style, and balanced driving style. Different driving styles have different relationships with style distinction thresholds. First, it is determined whether at least one of the preset first condition, second condition, and third condition is met to ascertain whether the user's driving style is a straight-line driving style.

[0490] S1102: Determines the user's driving style as straight-line driving style.

[0491] In this step, users with a straight-line driving style prefer to accelerate quickly by pressing the accelerator hard, generate large longitudinal acceleration during acceleration and deceleration, maintain high speed on straight sections, brake hard, and have small steering angles, as well as small entry and exit angles.

[0492] If at least one of the preset first condition, preset second condition, and preset third condition is found to be true, then the user's driving style is determined to be a straight-line driving style.

[0493] The first preset condition is: a0>a2, b0>b2, c0>c2, d0>d2.

[0494] The second condition is assumed to be: a3≤a0≤a1, b3≤b0≤b1, c3≤c0≤c1, d3≤d0≤d1, e0 <e3,f0<f3。

[0495] The third condition is assumed to be: a3≤a0≤a1, b3≤b0≤b1, c3≤c0≤c1, d3≤d0≤d1, g0 <g3。

[0496] a0 represents the target data value corresponding to the accelerator pedal opening, a1 represents the first threshold corresponding to the accelerator pedal opening, a2 represents the second threshold corresponding to the accelerator pedal opening, a3 represents the third threshold corresponding to the accelerator pedal opening, and a4 represents the fourth threshold corresponding to the accelerator pedal opening.

[0497] b0 represents the target data value corresponding to the brake pedal opening, b1 represents the first threshold corresponding to the brake pedal opening, b2 represents the second threshold corresponding to the brake pedal opening, b3 represents the third threshold corresponding to the brake pedal opening, and b4 represents the fourth threshold corresponding to the brake pedal opening.

[0498] c0 represents the target data value corresponding to longitudinal acceleration, c1 represents the first threshold corresponding to longitudinal acceleration, c2 represents the second threshold corresponding to longitudinal acceleration, c3 represents the third threshold corresponding to longitudinal acceleration, and c4 represents the fourth threshold corresponding to longitudinal acceleration.

[0499] d0 represents the target data value corresponding to the linear velocity, d1 represents the first threshold corresponding to the linear velocity, d2 represents the second threshold corresponding to the linear velocity, d3 represents the third threshold corresponding to the linear velocity, and d4 represents the fourth threshold corresponding to the linear velocity.

[0500] e0 represents the target data value corresponding to the exit speed, e1 represents the first threshold corresponding to the exit speed, e2 represents the second threshold corresponding to the exit speed, e3 represents the third threshold corresponding to the exit speed, and e4 represents the fourth threshold corresponding to the exit speed.

[0501] f0 represents the target data value corresponding to the cornering speed, f1 represents the first threshold corresponding to the cornering speed, f2 represents the second threshold corresponding to the cornering speed, f3 represents the third threshold corresponding to the cornering speed, and f4 represents the fourth threshold corresponding to the cornering speed.

[0502] g0 represents the target data value corresponding to the steering angle, g1 represents the first threshold corresponding to the steering angle, g2 represents the second threshold corresponding to the steering angle, g3 represents the third threshold corresponding to the steering angle, and g4 represents the fourth threshold corresponding to the steering angle.

[0503] S1103: Based on at least one style distinction threshold and target data value corresponding to each initial driving data, determine whether at least one of the preset fourth condition, preset fifth condition and preset sixth condition is true; if at least one of the preset fourth condition, preset fifth condition and preset sixth condition is true, then proceed to step S1104; if none of the preset fourth condition, preset fifth condition and preset sixth condition is true, then proceed to step S1105.

[0504] In this step, if it is determined that the first, second, and third preset conditions are all invalid, it means that the user's driving style is not a straight-line driving style. It is necessary to further determine whether the driving style is a curve driving style or a balanced driving style. This requires determining whether at least one of the fourth, fifth, and sixth preset conditions is valid based on at least one style distinction threshold and target data value corresponding to each initial driving data.

[0505] S1104: The user's driving style is determined to be the curve driving style.

[0506] In this step, users with a straight-line driving style prefer larger steering angles, larger cornering and exiting angles, larger lateral acceleration, smaller straight-line speed and longitudinal acceleration, and smaller opening of the accelerator and brake pedals.

[0507] If at least one of the preset fourth, fifth, and sixth conditions is found to be true, then the user's driving style is determined to be the curve driving style.

[0508] The fourth condition is preset as follows: h0>h2, f0>f2, e0>e2, g0>g2.

[0509] The fifth condition is set as follows: h3≤h0≤h1, f3≤f0≤f1, e3≤e0≤e1, g3≤g0≤g1, d4≤d0≤d2, c4≤c0≤c2.

[0510] The sixth condition is set as follows: h3≤h0≤h1, f3≤f0≤f1, e3≤e0≤e1, g3≤g0≤g1, a4≤a0≤a2, b4≤b0≤b2.

[0511] h0 represents the target data value corresponding to lateral acceleration, h1 represents the first threshold corresponding to lateral acceleration, h2 represents the second threshold corresponding to lateral acceleration, h3 represents the third threshold corresponding to lateral acceleration, and h4 represents the fourth threshold corresponding to lateral acceleration.

[0512] S1105: Determines the user's driving style as balanced driving style.

[0513] In this step, users with balanced driving styles prefer moderate steering angles, cornering angles, cornering angles, lateral acceleration, straight-line speed, longitudinal acceleration, accelerator pedal opening, and brake pedal opening.

[0514] If it is determined that the preset fourth, fifth, and sixth conditions are all invalid, that is, the preset first to sixth conditions are all invalid, then the user's driving style is determined to be a balanced driving style.

[0515] The driving style determination method provided in this embodiment determines the user's driving style by using at least one style distinction threshold and target data value corresponding to each initial driving data, which effectively improves the accuracy of the determined driving style.

[0516] Figure 12 is a flowchart illustrating Embodiment 13 of the route recommendation method provided in this application. This embodiment describes how the vehicle terminal determines the route type of the route to be recommended based on the parameter information of the feature parameters of the route to be recommended and the weight information of multiple preset route types. The method in this embodiment can be implemented by software, hardware, or a combination of software and hardware. As shown in Figure 12, the route type determination method specifically includes the following steps:

[0517] S1201: Obtain parameter information of at least one feature parameter of the route to be recommended, as well as weight information of multiple preset route types.

[0518] In this step, in order to determine the route type of the route to be recommended, the vehicle terminal first obtains parameter information of multiple feature parameters of the route to be recommended, as well as weight information of multiple preset route types.

[0519] The weight information for each preset route type includes the weight requirement for each feature parameter for that preset route type.

[0520] The parameter information for each feature parameter is either the parameter value or a score.

[0521] It should be noted that at least one characteristic parameter of the recommended route includes at least one parameter from at least one of the following categories: driving experience parameters, route attraction difference parameters, and route safety parameters. Driving experience parameters include at least one of the following: route length, average radius of curvature, route curve diversity, and route elevation difference. Route attraction difference parameters include at least one of the following: number of natural attractions and number of cultural attractions. Route safety parameters include at least one of the following: route maintenance level, route traversability 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 traversability duration refers to the duration the route can be traversed 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 volume refers to the average traffic volume per unit time. The unit distance can be 5 km, 10 km, 15 km, etc., and the unit time can be half an hour, 1 hour, 2 hours, etc. The embodiments of this application do not limit the feature parameters, unit distance, or unit duration, which can be determined according to the actual situation.

[0522] S1202: Determine the matching score between the route to be recommended and each preset route type based on the parameter information of each feature parameter and the weight information of each preset route type.

[0523] In this step, after the vehicle terminal obtains the feature information and weight information, it determines the matching score between the route to be recommended and each preset route type based on the parameter information of each feature parameter and the weight information of each preset route type.

[0524] Specifically, if the parameter information for each feature parameter is a parameter value, then the score for each feature parameter is determined based on that parameter value. Since each feature parameter has a corresponding range of parameter values ​​and a corresponding score, the score for each feature parameter can be determined based on the parameter value of each feature parameter of the route to be recommended.

[0525] Then, based on the score of each feature parameter and the weight information of each preset route type, the matching score between the route to be recommended and each preset route type is determined.

[0526] If the parameter information for each feature parameter is a score, then the matching score between the route to be recommended and each preset route type is determined based on the score of each feature parameter and the weight information of each preset route type.

[0527] Since the weight information of each preset route type includes the weight requirement of the preset route type for each feature parameter, for each preset route type, the weight of the preset route type for each feature parameter can be generated, and then the weight of the preset route type for each feature parameter can be multiplied by the score of the feature parameter and summed to obtain the matching score between the route to be recommended and the preset route type.

[0528] It should be noted that the weight requirement of the preset route type for each feature parameter can also be the weight of the preset route type for each feature parameter. You can directly multiply the weight of the preset route type for each feature parameter by the score of that feature parameter and then sum them to obtain the matching score between the route to be recommended and the preset route type.

[0529] The matching score is used to characterize the degree of matching between the route to be recommended and the preset route type. The higher the matching score, the greater the degree of matching between the route to be recommended and the preset route type.

[0530] S1203: Determine the route type of the route to be recommended from multiple preset route types based on the matching score between the route to be recommended and each preset route type.

[0531] In this step, after the vehicle terminal determines the matching score between the route to be recommended and each preset route type, the preset route type with the highest matching score among the multiple preset route types is taken as the route type of the route to be recommended.

[0532] The route type determination method provided in this embodiment calculates the matching score between the route to be recommended and each preset route type based on the parameter information of each feature parameter of the route to be recommended and the weight information of multiple preset route types. Then, based on the matching score of the route to be recommended and each preset route type, the route type of the route to be recommended is determined from the multiple preset route types. This solution determines the route type of the route to be recommended by using the feature parameters of the route to be recommended and the weight information of multiple preset route types, eliminating the need for manual determination, effectively improving the efficiency of route type determination, and also improving the accuracy of the determined route type.

[0533] Based on the above embodiments, Embodiment Fourteen of the route recommendation method provided in this application describes the situation where at least one feature parameter includes driving experience parameters, the score of the feature parameter is determined, and the weight information of multiple preset route types is described.

[0534] Route length, average radius of curvature, curve diversity, and elevation difference are all characteristic parameters that reflect the user's driving experience, so the route type can be determined based on these parameters.

[0535] The parameters of route length, route curve diversity, and route elevation difference are directly proportional to the score, while the parameter of average radius of curvature of the route is inversely proportional to the score.

[0536] For the route curve diversity parameter, since the route curve diversity parameter includes at least one of the total number of curves, the average length of curves, and the total number of consecutive curves, it is necessary to determine the score of the route curve diversity parameter by knowing the total number of curves, the average length of curves, the total number of consecutive curves, and the corresponding parameter value ranges and scores for each of them.

[0537] Figure 13 is a flowchart illustrating the scoring process for determining the diversity parameters of road curves provided in this application. As shown in Figure 13, the process includes the following steps:

[0538] S1301: Determine the first score based on the total number of curves.

[0539] In this step, there is a corresponding parameter range and a score relationship between the total number of curves. Therefore, the first score can be determined based on the total number of curves. The total number of curves is directly proportional to the first score.

[0540] S1302: Determine the second score based on the average length of the curve.

[0541] In this step, there is a corresponding parameter range for the average curve length and a corresponding score. Therefore, the second score can be determined based on the average curve length. The average curve length is directly proportional to the second score.

[0542] S1303: Determine the third score based on the total number of consecutive curves.

[0543] In this step, there is a corresponding parameter value range and a scoring relationship between the total number of consecutive curves. Therefore, the third score can be determined based on the value of the total number of consecutive curves. The value of the total number of consecutive curves is directly proportional to the third score.

[0544] S1304: The sum of the first score, the second score, and the third score is used as the score for the route curve diversity parameter.

[0545] In this step, after determining the first score, the second score, and the third score, summing them together will yield the score for the route curve diversity parameter.

[0546] The accuracy of scoring the route curve diversity parameter is improved by determining the score based on the total number of curves, the average length of curves, and the total number of consecutive curves.

[0547] For example, the correspondence between the parameter value range corresponding to the route length and the score can be as follows: when the route length is in the range [0, 20), the unit is kilometers and the score is 3 points; when the route length is in the range [20, 100), the unit is kilometers and the score is 5 points; when the route length is in the range [100, 300), the unit is kilometers and the score is 7 points; when the route length is in the range [300, +∞), the unit is kilometers and the score is 10 points.

[0548] For example, the correspondence between the parameter range corresponding to the average radius of curvature of the route and the score can be as follows: when the average radius of curvature of the route is in [0, 200), the unit is meters and the score is 10 points; when the average radius of curvature of the route is in [200, 500), the unit is meters and the score is 6 points; when the average radius of curvature of the route is in [5000, +∞), the unit is meters and the score is 3 points.

[0549] For example, the correspondence between the parameter value range corresponding to the total number of curves and the score can be as follows: when the total number of curves is [0, 20), the score is 3 points; when the total number of curves is [20, 100), the score is 6 points; and when the total number of curves is [100, +∞), the score is 10 points.

[0550] For example, for the average length of a curve, the correspondence between the parameter value range corresponding to the average length of the curve and the score can be as follows: when the average length of the curve is in the range of [0, 100), the unit is meters and the score is 3 points; when the average length of the curve is in the range of [100, 300), the unit is meters and the score is 6 points; when the average length of the curve is in the range of [300, +∞), the unit is meters and the score is 10 points.

[0551] For example, the correspondence between the parameter value range corresponding to the total number of consecutive curves and the score can be as follows: when the total number of consecutive curves is in [0, 5), the score is 3 points; when the total number of consecutive curves is in [5, 20), the score is 6 points; when the total number of consecutive curves is in [20, +∞), the score is 10 points.

[0552] For example, for the elevation difference of a route, the corresponding parameter value range and the score can be as follows: when the elevation difference of a route is in the range of [0, 100), the unit is meters and the score is 3 points; when the elevation difference of a route is in the range of [100, 500), the unit is meters and the score is 6 points; when the elevation difference of a route is in the range of [500, +∞), the unit is meters and the score is 10 points.

[0553] It should be noted that this application does not limit the correspondence between the parameter value range and the score for route length, average radius of curvature, total number of curves, average length of curves, total number of consecutive curves, and route elevation difference, and can be determined according to the actual situation.

[0554] Multiple preset route types include at least two of the following: a first preset route type, a second preset route type, a third preset route type, and a fourth preset route type.

[0555] The first preset route type is the route preferred by users who prefer relaxed cruising. The route length is short to medium, with small curvature of curves, few curves, short average length of curves, few consecutive curves, and small elevation difference.

[0556] The second preset route type is a route preferred by users who prefer city exploration. The route length is short, the curvature of the curves is moderate, the number of curves is moderate, the average length of the curves is moderate, the total number of consecutive curves is moderate, and the elevation difference of the route is small.

[0557] The third preset route type is the route preferred by users who like mountain driving. The route length is medium to long distance, with large curvature of curves, a large number of curves, a long average length of curves, a large total number of consecutive curves, and a large elevation difference.

[0558] The fourth preset route type is the route preferred by users who like adventure. The route length is medium to long, with small curvature of curves, few curves, short average length of curves, few consecutive curves, and large elevation difference.

[0559] The weight of the route length for the fourth preset route type is greater than the weight of the route lengths for the first, second, and third preset route types.

[0560] It should be noted that the weight of the route length of the fourth preset route type can be 0.2, 0.25, 0.3, etc., and the weight of the route length of the first preset route type, the second preset route type, and the third preset route type can be 0.05, 0.1, 0.15, etc. This application embodiment does not limit the weight of the route length of the first preset route type, the second preset route type, the third preset route type, and the fourth preset route type, nor does it limit the size relationship of the weight of the route length of the first preset route type, the second preset route type, and the third preset route type. It can be determined according to the actual situation.

[0561] The weight of the average radius of curvature of the third preset route type is greater than the weight of the average radius of curvature of the first, second, and fourth preset route types.

[0562] It should be noted that the weight of the average radius of curvature of the third preset route type can be 0.25, 0.3, 0.35, etc., and the weight of the average radius of curvature of the first, second, and fourth preset route types can be 0.05, 0.1, 0.15, etc. This application embodiment does not limit the weight of the average radius of curvature of the first, second, third, and fourth preset route types, nor does it limit the relationship between the magnitudes of the weights of the average radius of curvature of the first, second, and fourth preset route types. It can be determined according to the actual situation.

[0563] The route curve diversity parameter of the third preset route type has a greater weight than the route curve diversity parameters of the first, second, and fourth preset route types.

[0564] It should be noted that the weight of the route curve diversity parameter for the third preset route type can be 0.25, 0.3, 0.35, etc., and the weight of the route curve diversity parameter for the first, second, and fourth preset route types can be 0.05, 0.1, 0.15, etc. This application embodiment does not limit the weight of the route curve diversity parameter for the first, second, third, and fourth preset route types, nor does it limit the magnitude relationship of the weights of the route curve diversity parameter for the first, second, and fourth preset route types. It can be determined according to the actual situation.

[0565] The elevation difference of the third preset route type has a greater weight than the elevation differences of the first, second, and fourth preset route types.

[0566] It should be noted that the weight of the elevation difference of the third preset route type can be 0.15, 0.2, 0.25, etc., and the weight of the elevation difference of the first, second, and fourth preset route types can be 0.05, 0.07, 0.1, etc. This application embodiment does not limit the weight of the elevation difference of the first, second, third, and fourth preset route types, nor does it limit the relationship between the magnitude of the elevation difference of the first, second, and fourth preset route types. It can be determined according to the actual situation.

[0567] The route type determination method provided in this embodiment effectively distinguishes route types and improves the accuracy of route type determination by including at least one feature parameter that reflects the user's driving experience, and by assigning different weights to these parameters for the four preset route types.

[0568] Based on the above embodiments, Embodiment Fifteen of the route recommendation method provided in this application describes the situation where at least one feature parameter includes a route attraction difference parameter, the feature parameter score is determined, and the weight information of multiple preset route types is described.

[0569] The number of natural attractions and cultural attractions are characteristic parameters that reflect the differences in attractions along a route, so the route type can be determined based on these parameters.

[0570] The parameter values ​​for the number of natural attractions and cultural attractions are directly proportional to the score.

[0571] For example, the correspondence between the parameter value range corresponding to the number of natural attractions and the score can be as follows: when the number of natural attractions is in [0, 3), the score is 3 points; when the number of natural attractions is in [3, 10), the score is 6 points; when the number of natural attractions is in [10, +∞), the score is 10 points.

[0572] For example, the relationship between the parameter range corresponding to the number of cultural attractions and the score can be as follows: when the number of cultural attractions is in [0, 2), the score is 3 points; when the number of cultural attractions is in [2, 4), the score is 6 points; and when the number of cultural attractions is in [4, +∞), the score is 10 points.

[0573] It should be noted that this application does not limit the correspondence between the parameter value range and the score for the number of natural attractions and the number of cultural attractions, and can be determined according to the actual situation.

[0574] The first type of preset route has a high number of natural attractions and a moderate number of cultural attractions. The second type of preset route has a moderate number of natural attractions and a high number of cultural attractions. The third type of preset route has a low number of both natural and cultural attractions. The fourth type of preset route has a high number of natural attractions and a low number of cultural attractions.

[0575] The weight of the number of natural attractions in the fourth preset route type is greater than the weight of the number of natural attractions in the second and third preset route types.

[0576] The weight of the number of natural attractions in the first preset route type is greater than the weight of the number of natural attractions in the second and third preset route types.

[0577] It should be noted that the weights of the number of natural attractions in the first and fourth preset route types can be 0.2, 0.25, 0.3, etc., and the weights of the number of natural attractions in the second and third preset route types can be 0.05, 0.1, 0.15, etc. This application does not limit the weights of the number of natural attractions in the first, second, third, and fourth preset route types, nor does it limit the relative magnitudes of the weights of the first and fourth preset route types, nor does it limit the relative magnitudes of the weights of the second and third preset route types; these weights can be determined according to the actual situation.

[0578] The weight of cultural attractions in the second preset route type is greater than the weight of cultural attractions in the first, third, and fourth preset route types.

[0579] It should be noted that the weight of the number of cultural attractions in the second preset route type can be 0.2, 0.25, 0.3, etc., and the weight of the number of cultural attractions in the first, third, and fourth preset route types can be 0.05, 0.1, 0.15, etc. This application embodiment does not limit the weight of the number of cultural attractions in the first, second, third, and fourth preset route types, nor does it limit the size relationship of the weight of the number of cultural attractions in the first, third, and fourth preset route types. It can be determined according to the actual situation.

[0580] The route type determination method provided in this embodiment effectively distinguishes route types and improves the accuracy of route type determination by including at least one parameter in the feature parameters that reflects the differences in scenic spots along the route, and by assigning different weights to these parameters for the four preset route types.

[0581] Based on the above embodiments, Embodiment Sixteen of the route recommendation method provided in this application describes the situation where at least one feature parameter includes a route safety parameter, the score of the feature parameter is determined, and the weight information of multiple preset route types is described.

[0582] The route maintenance level, the route's passability duration, traffic volume, and the number of terrain types are all characteristic parameters that reflect the route's safety, so the route type can be determined based on these parameters.

[0583] The maintenance level of a route is directly proportional to the degree of maintenance of the route. The higher the maintenance level, the higher the degree of maintenance and the less damage to the route.

[0584] The parameters of route maintenance level, route passability duration, and number of terrain types are directly proportional to the score; the parameter of traffic volume is inversely proportional to the score.

[0585] For example, road surface maintenance levels are divided into three levels: 1, 2, and 3. The correspondence between the parameter value range and the score for each road surface maintenance level can be as follows: when the road surface maintenance level is (0, 1], the score is 3 points; when the road surface maintenance level is (1, 2], the score is 6 points; and when the road surface maintenance level is (2, 3], the score is 10 points.

[0586] For example, the correspondence between the parameter value range corresponding to the route passability duration and the score can be as follows: when the route passability duration is in the range of [0, 100), the unit is days, and the score is 3 points; when the route passability duration is in the range of [100, 200), the unit is days, and the score is 6 points; when the route passability duration is in the range of [200, +∞), the unit is days, and the score is 10 points.

[0587] For example, the correspondence between the parameter value range corresponding to traffic flow and the score can be as follows: when the traffic flow is in the range of [0, 50), the score is 10 points; when the traffic flow is in the range of [50, 200), the score is 6 points; and when the traffic flow is in the range of [200, +∞), the score is 3 points.

[0588] For example, the correspondence between the parameter value range corresponding to the number of terrain types and the score can be as follows: when the number of terrain types is (0, 1], the score is 3 points; when the number of terrain types is (1, 2], the score is 6 points; and when the number of terrain types is (2, +∞), the score is 10 points. The terrain types can be plains, mountains, hills, plateaus, etc.

[0589] It should be noted that this application embodiment does not limit the correspondence between the parameter value range and the score corresponding to the route maintenance level, route passability time, traffic flow, and number of terrain types, and can be determined according to the actual situation.

[0590] The first preset route type has a high route maintenance level, long route passability time, low traffic volume, and a small number of terrain types.

[0591] The second preset route type has a high route maintenance level, a long route passability time, moderate traffic volume, and a small number of terrain types.

[0592] The third preset route type has a medium route maintenance level, a medium route passability time, low traffic volume, and a large number of terrain types.

[0593] The fourth preset route type has a high route maintenance level, a medium route passability time, low traffic volume, and a large number of terrain types.

[0594] The route maintenance level of the first preset route type has a greater weight than the route maintenance levels of the third and fourth preset route types.

[0595] The route maintenance level of the second preset route type has a greater weight than the route maintenance levels of the third and fourth preset route types.

[0596] It should be noted that the weights of the route maintenance levels for the first and second preset route types can be 0.15, 0.2, 0.25, etc., and the weights of the route maintenance levels for the third and fourth preset route types can be 0.05, 0.07, 0.1, etc. This application does not limit the weights of the route maintenance levels for the first, second, third, and fourth preset route types, nor does it limit the relative magnitudes of the weights of the first and second preset route types, nor does it limit the relative magnitudes of the weights of the third and fourth preset route types; these can be determined according to the actual situation.

[0597] The weight of the travel time for the first preset route type is greater than the weight of the travel time for the third and fourth preset route types.

[0598] The weight of the travel time for the second preset route type is greater than the weight of the travel time for the third and fourth preset route types.

[0599] It should be noted that the weights of the travel time for the first and second preset route types can be 0.15, 0.2, 0.25, etc., and the weights of the travel time for the third and fourth preset route types can be 0.05, 0.07, 0.1, etc. This application does not limit the weights of the travel time for the first, second, third, and fourth preset route types, nor does it limit the relative magnitude of the weights of the first and second preset route types, nor does it limit the relative magnitude of the weights of the third and fourth preset route types; these weights can be determined according to the actual situation.

[0600] The traffic volume of the first preset route type has a greater weight than that of the third and fourth preset route types.

[0601] The traffic flow weight for the second preset route type is greater than the traffic flow weight for the third and fourth preset route types.

[0602] It should be noted that the weights of traffic flow for the first and second preset route types can be 0.2, 0.25, 0.3, etc., and the weights of traffic flow for the third and fourth preset route types can be 0.05, 0.1, 0.15, etc. This application does not limit the weights of traffic flow for the first, second, third, and fourth preset route types, nor does it limit the relative magnitudes of the weights of the first and second preset route types, nor does it limit the relative magnitudes of the weights of the third and fourth preset route types; these weights can be determined according to actual circumstances.

[0603] The weight of the number of terrain types in the third preset route type is greater than the weight of the number of terrain types in the first and second preset route types.

[0604] The weight of the number of terrain types in the fourth preset route type is greater than the weight of the number of terrain types in the first and second preset route types.

[0605] It should be noted that the weights of the number of terrain types in the first and second preset route types can be 0.05, 0.1, 0.15, etc., and the weights of the number of terrain types in the third and fourth preset route types can be 0.2, 0.25, 0.3, etc. This application does not limit the weights of the number of terrain types in the first, second, third, and fourth preset route types, nor does it limit the relative magnitudes of the weights of the first and second preset route types, nor does it limit the relative magnitudes of the weights of the third and fourth preset route types; these weights can be determined according to the actual situation.

[0606] The route type determination method provided in this embodiment effectively distinguishes route types and improves the accuracy of route type determination by including at least one parameter reflecting route safety in at least one feature parameter, and by assigning different weights to these parameters for the four preset route types.

[0607] Based on the above embodiments, Embodiment Seventeen of the route recommendation method provided in this application describes the weight information of multiple preset route types when at least one feature parameter includes driving experience parameters, route attraction difference parameters, and route safety parameters.

[0608] The weights of the number of natural scenic spots, route maintenance level, route passability time, and traffic volume for the first preset route type are greater than the weights of route length, average radius of curvature, route curve diversity parameters, route elevation difference, number of cultural scenic spots, and number of terrain types.

[0609] It should be noted that this application embodiment does not limit the weight relationship of the number of natural scenic spots, route maintenance level, route passability time, and traffic volume of the first preset route type, nor does it limit the weight relationship of the route length, average radius of curvature of the route, route curve diversity parameter, route elevation difference, number of cultural scenic spots, and number of terrain types of the first preset route type. These can be determined according to the actual situation.

[0610] The weights of the number of cultural attractions, route maintenance level, route passability time, and traffic volume for the second preset route type are greater than the weights of route length, average radius of curvature, route curve diversity parameters, route elevation difference, number of natural attractions, and number of terrain types.

[0611] It should be noted that this application embodiment does not limit the weight relationship of the number of cultural attractions, route maintenance level, route passability time, and traffic volume of the second preset route type, nor does it limit the weight relationship of the route length, average radius of curvature, route curve diversity parameter, route elevation difference, number of natural attractions, and number of terrain types of the second preset route type. These can be determined according to the actual situation.

[0612] The third preset route type has a greater weight for the average radius of curvature, the diversity of curves, the elevation difference, and the number of terrain types than for route length, the number of natural attractions, the number of cultural attractions, the route maintenance level, the route's passability time, and traffic volume.

[0613] It should be noted that this application embodiment does not limit the weight relationship of the average radius of curvature of the route, the route curve diversity parameter, the route elevation difference, and the number of terrain types for the third preset route type, nor does it limit the weight relationship of the route length, the number of natural attractions, the number of cultural attractions, the route maintenance level, the route passability time, and the traffic volume for the third preset route type. These can be determined according to the actual situation.

[0614] The weights of route length, number of natural attractions, and number of terrain types for the fourth preset route type are greater than the weights of average radius of curvature, route curve diversity parameters, route elevation difference, number of cultural attractions, route maintenance level, route passability time, and traffic volume.

[0615] It should be noted that this application embodiment does not limit the weight relationship of the route length, the number of natural scenic spots, and the number of terrain types of the fourth preset route type, nor does it limit the weight relationship of the average radius of curvature of the route, the route curve diversity parameter, the route elevation difference, the number of cultural scenic spots, the route maintenance level, the route passable time, and the traffic volume of the fourth preset route type. These can be determined according to the actual situation.

[0616] For example, Table 1 is a weight table for each feature parameter of the preset route type provided in this application.

[0617] Table 1

[0618] It should be noted that Table 1 is only an example of the weight of each feature parameter of the first preset route type, the second preset route type, the third preset route type and the fourth preset route type. This application embodiment does not limit it and can be determined according to the actual situation.

[0619] For example, based on Table 1, the route length score is 7, the average radius of curvature score is 10, the route curve diversity parameter score is 12, the route elevation difference score is 6, the number of natural attractions score is 10, the number of cultural attractions score is 6, the route maintenance level score is 6, the route passability time score is 6, the traffic volume score is 6, and the number of terrain types score is 6. Combining this with Table 1, the matching score between the recommended route and the first preset route type is calculated to be 9.1, the matching score between the recommended route and the second preset route type is 9, the matching score between the recommended route and the third preset route type is 10.95, and the matching score between the recommended route and the fourth preset route type is 9.5. Therefore, the third preset route type is the route type for the recommended route.

[0620] The route type determination method provided in this embodiment can effectively improve the accuracy of route type determination by setting different weights for different feature parameters for each route type.

[0621] Figure 14 is a flowchart illustrating an eighteenth embodiment of the route recommendation method provided in this application. This embodiment describes how to create and manage routes to be recommended, which are also travel routes. The method in this embodiment can be implemented through software, hardware, or a combination of both. As shown in Figure 14, it specifically includes the following steps:

[0622] S1401. In response to the user's creation command, generate a travel route based on the route-related information entered by the user, and display a route preview interface.

[0623] The route-related information is information related to generating the travel route. The route preview interface includes detailed information about the travel route and preset function controls.

[0624] 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.

[0625] 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.

[0626] 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.

[0627] 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.

[0628] 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.

[0629] 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.

[0630] For example, Figure 15 is a schematic diagram of a route creation interface provided in an embodiment of this application. As shown in Figure 15, the route creation interface 150 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, they click the "Submit" control 151. The vehicle terminal can obtain relevant geographical information and traffic data from the map database based on the route-related information input by the user, and then calculate multiple possible routes based on the route start point, route end point, waypoints, etc., and determine the optimal route according to a preset optimization algorithm, thereby generating a travel route and entering the route preview interface.

[0631] 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.

[0632] 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.

[0633] 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.

[0634] 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.

[0635] 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.

[0636] 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.

[0637] 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.

[0638] 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.

[0639] 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.

[0640] S1402, responding to user touch operations on preset function controls, and processing travel routes.

[0641] 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.

[0642] 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.

[0643] 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.

[0644] 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.

[0645] For example, Figure 16 is a schematic diagram of a route preview interface provided in an embodiment of this application. As shown in Figure 16, the route preview interface 160 displays detailed information of the travel route and preset function controls (only a portion is shown in the figure). Based on the interface 160, the user can view the detailed information of the newly created travel route. When the user clicks the "Save" control 161, the vehicle terminal can save the newly created travel route to "My Created Routes". When the user clicks the "Publish" control 162, the vehicle terminal can share the newly created travel route with other users.

[0646] 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.

[0647] 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.

[0648] 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.

[0649] 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.

[0650] 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.

[0651] 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:

[0652] 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.

[0653] Delete the travel route in response to the user's touch operation on the delete control;

[0654] 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.

[0655] 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.

[0656] 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.

[0657] 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.

[0658] 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.

[0659] 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.

[0660] 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.

[0661] 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.

[0662] 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.

[0663] 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.

[0664] 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.

[0665] 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.

[0666] 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.

[0667] 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.

[0668] 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.

[0669] 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.

[0670] For example, Figure 17 is a schematic diagram of a route details interface provided in an embodiment of this application. As shown in Figure 17, the route details interface 170 displays the details of the travel route clicked by the user and multiple preset function controls (only some are shown in the figure). Based on the interface 180, the user can view the details of a newly created travel route; the user can click the "Personal Travel" control 181, and the vehicle terminal can initiate navigation to start the trip; the user can click the "Fleet Travel" control 182, and the vehicle terminal can jump to the fleet activity interface to participate in fleet activities; the user can click the "Delete" control 183, and the vehicle terminal can delete the travel route; the user can click the "Edit" control 184, and the vehicle terminal can edit the travel route; the user can click the "Report Error" control 185, and the vehicle terminal can report an error for the travel route information; the user can click the "Favorite" control 186, and the vehicle terminal can add the travel route to "My Favorite Routes".

[0671] 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.

[0672] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0673] Figure 18 is a schematic diagram of the structure of a route recommendation device according to a first embodiment of the present application; as shown in Figure 18, the route recommendation device 180 includes:

[0674] The acquisition module 181 is used to acquire the driving style of the target user and the route information of multiple routes to be recommended. The route information of each route to be recommended includes the route type or information used to characterize the route type.

[0675] Processing module 182 is used for:

[0676] Based on the preset correspondence between driving style and route type, determine the target route type corresponding to the driving style of the target user;

[0677] Based on the route information and the target route type, at least one of the multiple routes to be recommended is selected as the target route, and the route type of the target route matches the target route type.

[0678] The recommendation module 183 is used to recommend at least one of the target routes.

[0679] Furthermore, the route information also includes at least one of distance information, weather information, and traffic information. The distance information is used to characterize the distance between the current location of the target user and the route location of the route to be recommended. The weather information is used to characterize the weather conditions in the area where the route to be recommended is located at the current time or the scheduled travel time. The traffic information is used to characterize the traffic conditions between the current location of the target user and the starting point of the route to be recommended.

[0680] The route information of the target route meets the preset recommendation conditions.

[0681] Furthermore, the preset recommendation conditions include at least one of the following:

[0682] The distance between the target user's current location and the location of the route to be recommended is less than a preset distance;

[0683] Alternatively, the weather conditions in the area where the recommended route is located at the current or scheduled travel time meet the preset weather requirements;

[0684] Alternatively, the traffic conditions between the target user's current location and the starting point of the route to be recommended meet preset traffic condition requirements.

[0685] Furthermore, each of the routes to be recommended has a route type score, which is used to characterize the degree of matching between the route type of the route to be recommended and the target route type;

[0686] Each of the recommended routes has a distance score corresponding to its distance information, a weather score corresponding to its weather information, and a road condition score corresponding to its road condition information.

[0687] Each of the routes to be recommended has a corresponding recommendation score, which is calculated based on at least one of the route type score, distance score, weather score, and road condition score.

[0688] Furthermore, the preset recommendation conditions include:

[0689] The recommended score for any of the target routes is greater than a preset threshold;

[0690] And / or, the recommended score corresponding to any of the target routes ranks among the top N in the recommended scores corresponding to the plurality of routes to be recommended, where N is a preset integer greater than or equal to 1.

[0691] Furthermore, the route type score corresponds to a route type weight, the distance score corresponds to a distance weight, the weather score corresponds to a weather weight, and the traffic condition score corresponds to a traffic condition weight.

[0692] The recommended score is calculated based on at least one of the following: the product of the route type score and the route type weight, the product of the distance score and the distance weight, the product of the weather score and the weather weight, and the product of the road condition score and the road condition weight.

[0693] Furthermore, the route type weight is greater than any one of the distance weight, the weather weight, and the traffic condition weight.

[0694] Furthermore, the acquisition module 181 is also used to receive the preset recommendation conditions configured by the user.

[0695] Furthermore, the degree of matching between the route type of any target route and the target route type is higher than the degree of matching between the route type of any non-target route and the target route type, wherein the non-target route is a route among the routes to be recommended that has not been determined as the target route.

[0696] Furthermore, the driving style is configured by the target user.

[0697] Furthermore, the driving style is determined based on the user's historical driving data.

[0698] Furthermore, the route type of any of the routes to be recommended is one of a plurality of preset route types;

[0699] The route type of any of the recommended routes is related to at least one of the following: route length, average radius of curvature of the route, route curve diversity parameter, route elevation difference, number of natural scenic spots passed through, number of cultural scenic spots passed through, route maintenance level, route passability time, traffic volume, and number of terrain types.

[0700] Furthermore, the plurality of preset route types includes a first preset route type;

[0701] The correlation between the first preset route type and the number of natural scenic spots along the route, the route maintenance level, the route passability time, and the traffic volume is greater than the correlation with the route length, the average radius of curvature of the route, the route curve diversity parameter, the route elevation difference, the number of cultural scenic spots along the route, and the number of terrain types.

[0702] Furthermore, the plurality of preset route types includes a second preset route type;

[0703] The correlation between the second preset route type and the number of cultural attractions along the route, the route maintenance level, the route passability time, and the traffic volume is greater than the correlation with the route length, the average radius of curvature of the route, the route curve diversity parameter, the route elevation difference, the number of natural attractions along the route, and the number of terrain types.

[0704] Furthermore, the plurality of preset route types includes a third preset route type;

[0705] The correlation between the third preset route type and the average radius of curvature of the route, the route curve diversity parameter, the route elevation difference, and the number of terrain types is greater than the correlation between the route length, the number of natural scenic spots along the route, the number of cultural scenic spots along the route, the route maintenance level, the route passability time, and the traffic volume.

[0706] Furthermore, the plurality of preset route types includes a fourth preset route type;

[0707] The correlation between the fourth preset route type and the route length, the number of natural scenic spots along the route, and the number of terrain types is greater than the correlation between the average radius of curvature of the route, the route curve diversity parameter, the route elevation difference, the number of cultural scenic spots along the route, the route maintenance level, the route passability time, and the traffic volume.

[0708] Furthermore, the target user's driving style is one of several preset driving styles;

[0709] Each of the preset driving styles is related to historical driving data, which includes at least one of the following: accelerator pedal opening, brake pedal opening, longitudinal acceleration, straight-line speed, corner exit speed, corner entry speed, steering angle, lateral acceleration, and historical driving route information.

[0710] Furthermore, the threshold ranges for historical driving data differ for different preset driving styles.

[0711] Furthermore, the plurality of preset driving styles includes at least two of a first preset driving style, a second preset driving style, and a third preset driving style;

[0712] The plurality of preset route types includes at least two of the following: a first preset route type, a second preset route type, a third preset route type, and a fourth preset route type;

[0713] The preset driving style and route type correspondence is as follows: the first preset driving style corresponds to the fourth preset route type, the second driving style corresponds to the third preset route type, and the third driving style corresponds to the first preset route type and the second preset route type.

[0714] Furthermore, recommending at least one of the target routes includes: sending the at least one target route, or displaying the at least one target route.

[0715] Furthermore, the recommendation module 183 is specifically used to: sort and display information related to each target route according to the degree of matching between the route type and the target route type.

[0716] Furthermore, the recommendation module 183 is also used to: display non-target routes, wherein any non-target route is one of the plurality of routes to be recommended other than the target route, and the display position of any non-target route is after any target route.

[0717] Furthermore, any two routes to be recommended satisfy the following condition: at least one of the route start point, route end point, and route waypoints is different.

[0718] Furthermore, there exist at least two target routes that satisfy the condition that at least one of the route's starting point and the route's ending point is different.

[0719] Furthermore, at least one of the target routes satisfies the condition that the current location of the target user is not the same as the starting point of the target route.

[0720] The route recommendation device provided in this embodiment is used to execute the technical solution in any of the foregoing method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0721] Figure 19 is a schematic diagram of the structure of a second embodiment of the route recommendation device provided in this application. As shown in Figure 19, the route recommendation device 190 includes:

[0722] Module 191 is used to obtain the driving style of the target user;

[0723] Processing module 192 is used to determine the target route type corresponding to the driving style of the target user based on the preset correspondence between driving style and route type;

[0724] The recommendation module 193 is used to recommend at least one target route, and the route type of each target route is matched with the target route type.

[0725] The route recommendation device provided in this embodiment is used to execute the technical solution in any of the foregoing method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0726] Figure 20 is a structural schematic diagram of Embodiment 3 of the route recommendation device provided in this application; this device can be integrated into the vehicle terminal in the above method embodiments, or it can be implemented through the vehicle terminal in the above method embodiments. As shown in Figure 20, the route recommendation device 2000 includes:

[0727] Module 2001 is used to obtain the driving style of the target user;

[0728] Sending module 2002 is used to send the target user's driving style to the server;

[0729] The receiving module 2003 is used to receive at least one target route fed back by the server, wherein the route type of each target route is matched with the target route type corresponding to the driving style of the target user.

[0730] Furthermore, the receiving module 2003 is also used to receive the route sent by the server and store the route as a route to be recommended.

[0731] Furthermore, the sending module 2002 is also used to send a route error request to the server in response to the user's route error reporting operation, the route error request including the route to be reviewed;

[0732] Furthermore, the receiving module 2003 is also used to receive the approval message sent by the server;

[0733] Processing module 2004 is used to increase the user's reward points.

[0734] The route recommendation device provided in this embodiment is used to execute the technical solution of the vehicle terminal in any of the aforementioned method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0735] Figure 21 is a schematic diagram of the structure of the route recommendation device according to Embodiment 4 of this application; the device can be integrated into the server in the above method embodiments, or it can be implemented through the server in the above method embodiments. As shown in Figure 21, the route recommendation device 210 includes:

[0736] The receiving module 211 is used to receive the driving style of the target user sent by the vehicle terminal;

[0737] The acquisition module 212 is used to acquire route information of multiple routes to be recommended, and the route information of each route to be recommended includes route type;

[0738] Processing module 213 is used for:

[0739] Based on the preset correspondence between driving style and route type, determine the target route type corresponding to the driving style of the target user;

[0740] Based on the route information, at least one of the multiple routes to be recommended is selected as the target route, and the route type of the target route matches the target route type.

[0741] The sending module 214 is used to send at least one of the target routes to the vehicle terminal.

[0742] Furthermore, the receiving module 211 is also used for:

[0743] Receive a route error request sent by the vehicle terminal, the route error request including routes to be reviewed;

[0744] Receive the approval message sent by the terminal device;

[0745] Furthermore, the sending module 214 is also used to send the approval message to the vehicle terminal.

[0746] The route recommendation device provided in this embodiment is used to execute the technical solution of the vehicle terminal in any of the aforementioned method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0747] Figure 22 is a schematic diagram of the structure of an electronic device provided in this application. As shown in Figure 22, the electronic device 220 includes:

[0748] Processor 221, memory 222, and communication interface 223;

[0749] The memory 222 is used to store the executable instructions of the processor 221;

[0750] The processor 221 is configured to execute the technical solutions in any of the foregoing method embodiments by executing the executable instructions.

[0751] Optionally, the memory 222 can be either standalone or integrated with the processor 221.

[0752] Optionally, when the memory 222 is a device independent of the processor 221, the electronic device 220 may further include:

[0753] Bus 224, memory 222 and communication interface 223 are connected to processor 221 through bus 224 and complete communication with each other. Communication interface 223 is used to communicate with other devices.

[0754] Optionally, the communication interface 223 can be implemented using a transceiver. The communication interface is used to enable communication between the database access device and other devices (e.g., clients, read-write databases, and read-only databases). The memory may include random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device.

[0755] Bus 224 can be 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 representation, only one thick line is used in the diagram, but this does not indicate that there is only one bus or one type of bus.

[0756] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0757] The electronic device is used to execute the technical solutions in any of the foregoing method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0758] Figure 23 is a structural schematic diagram of a vehicle-mounted terminal provided in this application. As shown in Figure 23, the vehicle-mounted terminal 230 includes:

[0759] Processor 231, memory 232, and communication interface 233;

[0760] The memory 232 is used to store the executable instructions of the processor 231;

[0761] The processor 231 is configured to execute the technical solution of the vehicle terminal in any of the foregoing method embodiments by executing the executable instructions.

[0762] Optionally, the memory 232 can be either standalone or integrated with the processor 231.

[0763] Optionally, when the memory 232 is a device independent of the processor 231, the vehicle terminal 230 may further include:

[0764] Bus 234, memory 232 and communication interface 233 are connected to processor 231 through bus 234 and complete mutual communication. Communication interface 233 is used to communicate with other devices.

[0765] Optionally, the communication interface 233 can be implemented using a transceiver. The communication interface is used to enable communication between the database access device and other devices (e.g., clients, read-write databases, and read-only databases). The memory may include random access memory (RAM) and may also include non-volatile memory, such as at least one disk drive.

[0766] Bus 234 can be 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 representation, only one thick line is used in the diagram, but this does not indicate that there is only one bus or one type of bus.

[0767] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0768] The vehicle-mounted terminal is used to execute the technical solution of the vehicle-mounted terminal in any of the aforementioned method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0769] Figure 24 is a schematic diagram of the structure of a server provided in this application. As shown in Figure 24, the server 240 includes:

[0770] Processor 241, memory 242, and communication interface 243;

[0771] The memory 242 is used to store the executable instructions of the processor 241;

[0772] The processor 241 is configured to execute the server's technical solution in any of the foregoing method embodiments by executing the executable instructions.

[0773] Optionally, the memory 242 can be either standalone or integrated with the processor 241.

[0774] Optionally, when the memory 242 is a device independent of the processor 241, the server 240 may further include:

[0775] Bus 244, memory 242 and communication interface 243 are connected to processor 241 through bus 244 and complete communication with each other. Communication interface 243 is used to communicate with other devices.

[0776] Optionally, the communication interface 243 can be implemented using a transceiver. The communication interface is used to enable communication between the database access device and other devices (e.g., clients, read-write databases, and read-only databases). The memory may include random access memory (RAM) and may also include non-volatile memory, such as at least one disk drive.

[0777] Bus 244 can be 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 representation, only one thick line is used in the diagram, but this does not indicate that there is only one bus or one type of bus.

[0778] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0779] The server is used to execute the technical solution of the server in any of the aforementioned method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0780] This application also provides a vehicle, which includes an on-board terminal.

[0781] The vehicle-mounted terminal is used to execute the technical solutions in any of the foregoing method embodiments. Its implementation principle and technical effect are similar, and will not be repeated here.

[0782] This application also provides a readable storage medium storing a computer program thereon, which, when executed by a processor, implements the technical solutions provided in any of the foregoing embodiments.

[0783] This application also provides a computer program product, including a computer program, which, when executed by a processor, is used to implement the technical solutions provided in any of the foregoing method embodiments.

[0784] This embodiment also provides a chip, which includes a memory and a processor. The memory stores code and data, and the memory is coupled to the processor. The processor runs a program in the memory, enabling the chip to execute the route recommendation method provided in the various embodiments described above.

[0785] This embodiment also provides a computer program, which, when executed by a processor, is used to perform the route recommendation method provided in the foregoing various embodiments.

[0786] 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.

[0787] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A route recommendation method characterized by, include: Obtain the target user's driving style and route information for multiple routes to be recommended. The route information for each route to be recommended includes the route type or information used to characterize the route type. Based on the preset correspondence between driving style and route type, determine the target route type corresponding to the driving style of the target user; Based on the route information and the target route type, at least one of the multiple routes to be recommended is selected as the target route, and the route type of the target route matches the target route type. Recommend at least one of the aforementioned destination routes.

2. The method of claim 1, wherein, The route information also includes at least one of distance information, weather information, and road condition information. The distance information is used to represent the distance between the current location of the target user and the route location of the route to be recommended. The weather information is used to represent the weather conditions in the area where the route to be recommended is located at the current time or the scheduled travel time. The road condition information is used to represent the road conditions between the current location of the target user and the starting point of the route to be recommended. The route information of the target route meets the preset recommendation conditions.

3. The method of claim 2, wherein, The preset recommendation conditions include at least one of the following: The distance between the target user's current location and the location of the route to be recommended is less than a preset distance; Alternatively, the weather conditions in the area where the recommended route is located at the current or scheduled travel time meet the preset weather requirements; Alternatively, the traffic conditions between the target user's current location and the starting point of the route to be recommended meet preset traffic condition requirements.

4. The method of claim 2, wherein, Each of the routes to be recommended has a route type score, which is used to characterize the degree of matching between the route type of the route to be recommended and the target route type; Each of the recommended routes has a distance score corresponding to its distance information, a weather score corresponding to its weather information, and a road condition score corresponding to its road condition information. Each of the routes to be recommended has a corresponding recommendation score, which is calculated based on at least one of the route type score, distance score, weather score, and road condition score.

5. The method of claim 4, wherein, The preset recommendation conditions include: The recommended score for any of the target routes is greater than a preset threshold; And / or, the recommended score corresponding to any of the target routes ranks among the top N in the recommended scores corresponding to the plurality of routes to be recommended, where N is a preset integer greater than or equal to 1.

6. The method according to claim 4 or 5, characterized in that, The route type score corresponds to a route type weight, the distance score corresponds to a distance weight, the weather score corresponds to a weather weight, and the traffic condition score corresponds to a traffic condition weight. The recommended score is calculated based on at least one of the following: the product of the route type score and the route type weight, the product of the distance score and the distance weight, the product of the weather score and the weather weight, and the product of the road condition score and the road condition weight.

7. The method of claim 6, wherein, The route type weight is greater than any one of the distance weight, the weather weight, and the road condition weight.

8. The method of claim 2, wherein, The method further includes: receiving the preset recommendation conditions configured by the user.

9. The method according to any one of claims 1 to 8, characterized in that, The degree of matching between the route type of any of the target routes and the target route type is higher than the degree of matching between the route type of any non-target route and the target route type. The non-target routes are those routes among the routes to be recommended that have not been determined as the target routes.

10. The method according to any one of claims 1 to 9, characterized in that, The driving style is configured by the target user.

11. The method according to any one of claims 1 to 9, characterized in that, The driving style is determined based on the user's historical driving data.

12. The method according to any one of claims 1 to 11, characterized in that, The route type of any of the routes to be recommended is one of a plurality of preset route types; The route type of any of the recommended routes is related to at least one of the following: route length, average radius of curvature of the route, route curve diversity parameter, route elevation difference, number of natural scenic spots passed through, number of cultural scenic spots passed through, route maintenance level, route passability time, traffic volume, and number of terrain types.

13. The method of claim 12, wherein, The plurality of preset route types includes a first preset route type; The correlation between the first preset route type and the number of natural scenic spots along the route, the route maintenance level, the route passability time, and the traffic volume is greater than the correlation with the route length, the average radius of curvature of the route, the route curve diversity parameter, the route elevation difference, the number of cultural scenic spots along the route, and the number of terrain types.

14. The method of claim 12, wherein, The plurality of preset route types includes a second preset route type; The correlation between the second preset route type and the number of cultural attractions along the route, the route maintenance level, the route passability time, and the traffic volume is greater than the correlation with the route length, the average radius of curvature of the route, the route curve diversity parameter, the route elevation difference, the number of natural attractions along the route, and the number of terrain types.

15. The method of claim 12, wherein, The plurality of preset route types includes a third preset route type; The correlation between the third preset route type and the average radius of curvature of the route, the route curve diversity parameter, the route elevation difference, and the number of terrain types is greater than the correlation between the route length, the number of natural scenic spots along the route, the number of cultural scenic spots along the route, the route maintenance level, the route passability time, and the traffic volume.

16. The method of claim 12, wherein, The plurality of preset route types includes a fourth preset route type; The correlation between the fourth preset route type and the route length, the number of natural scenic spots along the route, and the number of terrain types is greater than the correlation between the average radius of curvature of the route, the route curve diversity parameter, the route elevation difference, the number of cultural scenic spots along the route, the route maintenance level, the route passability time, and the traffic volume.

17. The method according to any one of claims 1 to 16, characterized in that, The target user's driving style is one of several preset driving styles; Each of the preset driving styles is related to historical driving data, which includes at least one of the following: accelerator pedal opening, brake pedal opening, longitudinal acceleration, straight-line speed, corner exit speed, corner entry speed, steering angle, lateral acceleration, and historical driving route information.

18. The method of claim 17, wherein, Different preset driving styles correspond to different threshold ranges for historical driving data.

19. The method of claim 17 or 18, wherein, The plurality of preset driving styles includes at least two of the first preset driving style, the second preset driving style, and the third preset driving style; The plurality of preset route types includes at least two of the following: a first preset route type, a second preset route type, a third preset route type, and a fourth preset route type; The preset driving style and route type correspondence is as follows: the first preset driving style corresponds to the fourth preset route type, the second driving style corresponds to the third preset route type, and the third driving style corresponds to the first preset route type and the second preset route type.

20. The method according to any one of claims 1 to 19, characterized in that, The recommendation of at least one of the target routes includes: sending the at least one of the target routes, or displaying the at least one of the target routes.

21. The method of claim 20, wherein, Displaying the at least one target route includes: sorting the target routes according to the degree of matching between the route type and the target route type, and displaying information related to each target route.

22. The method of claim 20 or 21, wherein, The method further includes: displaying non-target routes, wherein any non-target route is one of the plurality of routes to be recommended other than the target route, and the display position of any non-target route is after any target route.

23. The method according to any one of claims 1 to 22, characterized in that, Any two routes to be recommended satisfy the following condition: at least one of the route start point, route end point, and route waypoints is different.

24. The method of claim 23, wherein, There exist at least two target routes that satisfy the condition that at least one of the route's starting point and the route's ending point is different.

25. The method according to any one of claims 1 to 24, characterized in that, There exists at least one target route that satisfies the condition that the current location of the target user is not the same as the starting point of the target route.

26. A route recommendation device characterized by comprising: include: The acquisition module is used to acquire the driving style of the target user and the route information of multiple routes to be recommended. The route information of each route to be recommended includes the route type or information used to characterize the route type. Processing module, used for: Based on the preset correspondence between driving style and route type, determine the target route type corresponding to the driving style of the target user; Based on the route information and the target route type, at least one of the multiple routes to be recommended is selected as the target route, and the route type of the target route matches the target route type. The recommendation module is used to recommend at least one of the target routes.

27. An electronic device, comprising: include: Processor, memory, communication interface; The memory is used to store the executable instructions of the processor; The processor is configured to execute the route recommendation method according to any one of claims 1 to 25 by executing the executable instructions.

28. A vehicle characterized by Including vehicle-mounted terminals; The vehicle-mounted terminal is used to execute the route recommendation method according to any one of claims 1 to 25.

29. A readable storage medium, having stored thereon a computer program, characterized in that, When the computer program is executed by a processor, it implements the route recommendation method according to any one of claims 1 to 25.

30. A computer program product, characterised in that, Includes a computer program, which, when executed by a processor, is used to implement the route recommendation method according to any one of claims 1 to 25.

31. A computer program, characterized in that, When the computer program is executed by a processor, it is used to perform the route recommendation method according to any one of claims 1 to 25.

32. A chip, comprising: The chip comprises a memory, a processor, the memory stores codes and data, the memory is coupled with the processor, and the processor runs the program in the memory so that the chip is used to execute the route recommendation method in any one of claims 1 to 25.

Images