Target path acquisition method, storage medium and electronic device

Abstract

The application discloses a target path acquisition method, a storage medium and an electronic device, and can also be applied to map, navigation, path recommendation and the like. The method comprises the following steps: in response to a first navigation request triggered on a navigation client logged in by a target account, displaying a first navigation path generated for the target account on the navigation client, wherein a starting path point of the first navigation path is a first starting point, and a terminal path point of the first navigation path is a target terminal point; in the case that a target position currently located by a target device associated with the target account is acquired and the target position is out of a navigation range of the first navigation path, generating a path acquisition request; and acquiring a target path according to historical path information. The application solves the technical problem of low accuracy of target path acquisition.

Description

Technical Field

[0001] This invention relates to the field of computers, and more specifically, to a method for obtaining a target path, a storage medium, and an electronic device. Background Technology

[0002] Navigation technology has developed rapidly in recent years, but it also faces a variety of problems. For example, when a navigation request is received, related technologies often generate a preferred route with the shortest travel time for the user. However, because the user's true intentions are not considered, this preferred route is not necessarily the most accurate target route for the user, especially evident in deviation scenarios. Therefore, there is a problem of low accuracy in obtaining the target route.

[0003] There is currently no effective solution to the above problems. Summary of the Invention

[0004] This invention provides a method for obtaining a target path, a storage medium, and an electronic device to at least solve the technical problem of low accuracy in obtaining the target path.

[0005] According to one aspect of the present invention, a method for obtaining a target path is provided, comprising: responding to a first navigation request triggered on a navigation client logged in by a target account, displaying a first navigation path generated for the target account on the navigation client, wherein the starting point of the first navigation path is a first starting point and the ending point of the first navigation path is a target ending point; generating a path acquisition request when the target location of a target device associated with the target account is obtained and the target location is outside the navigation range of the first navigation path, wherein the target device is configured with the navigation client; responding to the path acquisition request, acquiring historical path information, wherein the historical path information includes information on at least one first path navigated by the target account on the navigation client, the initial point of the first path is the first starting point and the ending point of the first path is the target ending point; and acquiring a target path based on the historical path information, wherein the initial point of the target path is the target location and the ending point of the target path is the target ending point.

[0006] According to another aspect of the present invention, another method for obtaining a target path is provided, comprising: in response to a path acquisition request triggered on a navigation client logged in by a target account, obtaining historical path information, wherein the historical path information includes information on at least one first path navigated by the target account on the navigation client, the initial path point of the first path being a first starting point, and the ending path point of the first path being a target endpoint; obtaining target road data based on the historical path information, wherein the target road data includes segment data of the main roads included in the first path; and, if at least one second path generated based on the historical path information is obtained, determining a target path from the at least one second path based on the target road data, wherein the initial path point of the second path being a second starting point, and the ending path point of the second path being the target endpoint.

[0007] According to another aspect of the present invention, a target path acquisition device is also provided, comprising: a first display unit, configured to display a first navigation path generated for the target account on the navigation client in response to a first navigation request triggered on a navigation client logged in by a target account, wherein the starting path point of the first navigation path is a first starting point and the ending path point of the first navigation path is a target ending point; a first generation unit, configured to generate a path acquisition request when the target location of the target device associated with the target account is obtained and the target location is outside the navigation range of the first navigation path, wherein the navigation client is configured on the target device; a first acquisition unit, configured to acquire historical path information in response to the path acquisition request, wherein the historical path information includes information on at least one first path navigated by the target account on the navigation client, the initial path point of the first path is the first starting point and the ending path point of the first path is the target ending point; and a second acquisition unit, configured to acquire a target path based on the historical path information, wherein the initial path point of the target path is the target location and the ending path point of the target path is the target ending point.

[0008] As an optional solution, the second acquisition unit includes: a first determining module, configured to determine target road data from the candidate road data extracted from the historical path information, wherein the candidate road data includes segment data of each road included in the first path, and the target road data includes segment data of the main roads included in the first path; and a second determining module, configured to determine the target path from the at least one second path generated based on the candidate road data, wherein the initial path point of the second path is the target location, and the ending path point of the second path is the target endpoint.

[0009] As an optional solution, the second acquisition unit includes: an extraction module, used to extract candidate road data from the historical path information, wherein the candidate road data includes segment data of each road included in the first path; and a third determination module, used to determine the target road data from the candidate road data.

[0010] As an optional solution, the extraction module includes: a first acquisition submodule, used to acquire N path points and M paths, wherein the N path points include path points on at least one first path, the M paths include the driving path corresponding to each of the N path points, and each of the M paths carries a corresponding driving direction, where N is a natural number greater than or equal to 2 and M is a natural number; a second acquisition submodule, used to acquire out-degree information and in-degree information of each path point among the N path points, wherein the out-degree information is used to indicate the number of paths associated with the path point with the outward driving direction, and the in-degree information is used to indicate the number of paths associated with the path point with the inward driving direction; a first determination submodule, used to determine a target path point among the N path points based on the out-degree information and the in-degree information, wherein the target path point includes the target location and the target endpoint; and a second determination submodule, used to determine the paths associated with the target path point as candidate paths, wherein the candidate road data includes the road data of the candidate paths.

[0011] As an optional solution, the first determining submodule includes at least one of the following: a first determining subunit, configured to determine, among the N path points, the target path point whose number of paths represented by the out-degree information is not 1; a second determining subunit, configured to determine, among the N path points, the target path point whose number of paths represented by the in-degree information is not 1; and a third determining subunit, configured to determine, among the N path points, the target path point whose number of paths represented by both the out-degree information and the in-degree information is not 1.

[0012] As an optional solution, the first determining module includes: a third determining submodule, used to perform splicing processing on the candidate paths to obtain at least one continuous spliced ​​path before determining the target path from the at least one second path based on the target road data; and a third obtaining submodule, used to construct the at least one second path based on the at least one continuous spliced ​​path before determining the target path from the at least one second path based on the target road data, wherein the second path includes the candidate paths.

[0013] As an optional solution, the third determining module mentioned above includes a fourth obtaining submodule, used to determine the target road data that meets the main road conditions from the candidate road data, wherein the road corresponding to the road data that meets the main road conditions is a main road.

[0014] According to another aspect of the present invention, a target path acquisition apparatus is also provided, comprising: a third acquisition unit, configured to acquire historical path information in response to a path acquisition request triggered on a navigation client logged in by a target account, wherein the historical path information includes information on at least one first path navigated by the target account on the navigation client, the initial path point of the first path being a first starting point, and the ending path point of the first path being a target ending point; a first determination unit, configured to determine target road data from the candidate road data extracted from the historical path information, wherein the candidate road data includes segment data of each road included in the first path, and the target road data includes segment data of the main roads included in the first path; and a second determination unit, configured to determine a target path from the at least one second path generated based on the candidate road data, wherein the initial path point of the second path is a second starting point, and the ending path point of the second path is the target ending point.

[0015] As an optional solution, it includes: a fourth acquisition unit, configured to receive historical navigation information uploaded by the navigation client before acquiring historical path information in response to a path acquisition request triggered on the navigation client logged in by the target account, wherein the historical navigation information includes the historical path information; and a storage unit, configured to store the historical navigation information in a microservice database before acquiring historical path information in response to a path acquisition request triggered on the navigation client logged in by the target account, wherein the microservice database is configured to store path information navigated by any account uploaded by the navigation client according to a timestamp and an account identifier, wherein the timestamp is used to indicate the upload time of the historical navigation data, and the account identifier is used to indicate the login account of the navigation client that uploaded the historical navigation data.

[0016] As an optional solution, it includes: a second display unit, configured to, in response to a first navigation request triggered on the navigation client logged in by the target account, display a first navigation path generated for the target account on the navigation client before obtaining historical path information, wherein the starting point of the first navigation path is the first starting point, and the ending point of the first navigation path is the target endpoint; a fifth acquisition unit, configured to, in response to a path acquisition request triggered on the navigation client logged in by the target account, obtain the current target location of the target device associated with the target account before obtaining historical path information, wherein the target device is configured with the navigation client, and the target location includes the location of the second starting point; and a second generation unit, configured to, in response to a path acquisition request triggered on the navigation client logged in by the target account, generate the path acquisition request when the target location is outside the navigation range of the first navigation path before obtaining historical path information.

[0017] As an optional solution, it includes: a third display unit, configured to, before obtaining historical path information in response to a path retrieval request triggered on the navigation client logged in by the target account, display a first navigation path generated for the target account on the navigation client, wherein the starting point of the first navigation path is the first starting point, and the ending point of the first navigation path is the target endpoint; and a third generation unit, configured to, before obtaining historical path information in response to a path retrieval request triggered on the navigation client logged in by the target account, generate the path retrieval request upon obtaining a second navigation request triggered on the navigation client logged in by the target account, wherein the second navigation request is used to request navigation for the target account to a second navigation route with the second starting point as the starting point and the target endpoint as the ending point, the second navigation route being different from the first navigation route.

[0018] As an optional solution, the above-mentioned device further includes: a fourth display unit, used to display deviation warning information when the target location deviates from the navigation range of the first navigation path, wherein the deviation warning information is used to indicate that the target account has deviated from the navigation range of the first navigation path; the above-mentioned device further includes: a fifth display unit, used to display navigation warning information and the target path after the target path is determined from the at least one second path based on the target road data, wherein the navigation warning information is used to indicate that a new navigation path has been planned for the target account.

[0019] According to another aspect of the embodiments of this application, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, causing the computer device to perform the target path acquisition method as described above.

[0020] According to another aspect of the present invention, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the target path acquisition method described above through the computer program.

[0021] In this embodiment of the invention, the historical path information of the target account is used to respond to the path acquisition request, so that there is a correlation between the target path requested by the path acquisition request and the historical data of the target account. Compared with the method of simply using the current deviation position as the navigation starting point when deviation occurs, this method of acquiring the target path in this embodiment of the invention is more in line with the true intention of the target account (user), thereby achieving the purpose of acquiring the target path efficiently and accurately, thus realizing the technical effect of improving the accuracy of target path acquisition, and solving the technical problem of low accuracy of target path acquisition.

[0022] Furthermore, to improve the utilization efficiency of the aforementioned historical path information, after obtaining the historical path information, instead of directly using it to obtain the target path, further data processing is performed on the historical path information to obtain more practical target road data. Compared to directly using historical path information containing a lot of useless information to obtain the target path, using target road data to obtain the target path can save unnecessary and invalid operations in the data processing process, thereby improving the efficiency of target path acquisition. This achieves the goal of obtaining the target path efficiently and accurately, thus realizing the technical effect of improving the accuracy of target path acquisition and solving the technical problem of low accuracy in target path acquisition. Attached Figure Description

[0023] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0024] Figure 1 This is a schematic diagram of an application environment for an optional target path acquisition method according to an embodiment of the present invention;

[0025] Figure 2 This is a schematic diagram of the flow of an optional target path acquisition method according to an embodiment of the present invention;

[0026] Figure 3 This is a schematic diagram of an optional method for obtaining a target path according to an embodiment of the present invention;

[0027] Figure 4 This is a schematic diagram of another optional method for obtaining a target path according to an embodiment of the present invention;

[0028] Figure 5 This is a schematic diagram of another optional method for obtaining a target path according to an embodiment of the present invention;

[0029] Figure 6This is a schematic diagram of another optional method for obtaining a target path according to an embodiment of the present invention;

[0030] Figure 7 This is a schematic diagram of another optional method for obtaining a target path according to an embodiment of the present invention;

[0031] Figure 8 This is a schematic diagram of another optional method for obtaining a target path according to an embodiment of the present invention;

[0032] Figure 9 This is a schematic diagram of another optional method for obtaining a target path according to an embodiment of the present invention;

[0033] Figure 10 This is a schematic diagram of another optional method for obtaining a target path according to an embodiment of the present invention;

[0034] Figure 11 This is a schematic diagram of the flow of another optional method for obtaining a target path according to an embodiment of the present invention;

[0035] Figure 12 This is a schematic diagram of another optional method for obtaining a target path according to an embodiment of the present invention;

[0036] Figure 13 This is a schematic diagram of another optional method for obtaining a target path according to an embodiment of the present invention;

[0037] Figure 14 This is a schematic diagram of an optional target path acquisition device according to an embodiment of the present invention;

[0038] Figure 15 This is a schematic diagram of another optional target path acquisition device according to an embodiment of the present invention;

[0039] Figure 16 This is a schematic diagram of the structure of an optional electronic device according to an embodiment of the present invention. Detailed Implementation

[0040] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0041] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention 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.

[0042] According to one aspect of the present invention, a method for obtaining a target path is provided. Optionally, as an optional implementation, the above-described method for obtaining a target path may be applied to, but is not limited to, methods such as... Figure 1 The environment shown may include, but is not limited to, user equipment 102, network 110, and server 112. User equipment 102 may include, but is not limited to, a display 108, a processor 106, and a memory 104. User equipment 102 may be, but is not limited to, a target terminal 1022, on which a navigation client logged in by the target account is installed.

[0043] The specific process can be summarized in the following steps:

[0044] In step S102, user equipment 102 obtains a path acquisition request from the navigation client installed on target terminal 1022 and logged in by the target account;

[0045] In steps S104-S106, user equipment 102 sends a path acquisition request to server 112 via network 110;

[0046] In steps S108-S112, server 112 searches for historical path information of the target account through database 114, and processes the historical path information through processing engine 1111 to obtain target road data; then, it further uses the above target road data to generate target path data.

[0047] In steps S114-S118, server 112 sends the target path data to user equipment 102 via network 110. Processor 106 in user equipment 102 displays the target path 1024 corresponding to the target path data on display 108 and stores the target path data in memory 104.

[0048] remove Figure 1Beyond the illustrated example, the above steps can be performed independently by user equipment 102. That is, user equipment 102 can perform steps such as acquiring historical path information, acquiring target road data, and generating target path data, thereby reducing the processing load on the server. User equipment 102 includes, but is not limited to, handheld devices (such as mobile phones), laptops, desktop computers, and in-vehicle devices. This invention does not limit the specific implementation of user equipment 102.

[0049] Alternatively, as an alternative implementation method, such as Figure 2 As shown, the methods for obtaining the target path include:

[0050] S202, in response to the first navigation request triggered on the navigation client logged in by the target account, the first navigation path generated for the target account is displayed on the navigation client, wherein the starting point of the first navigation path is the first starting point, and the ending point of the first navigation path is the target ending point;

[0051] S204, if the target location of the target device associated with the target account is obtained and the target location is outside the navigation range of the first navigation path, a path acquisition request is generated, wherein a navigation client is configured on the target device;

[0052] S206, respond to the path retrieval request and retrieve historical path information, wherein the historical path information includes information on at least one first path that the target account has navigated on the navigation client, the initial path point of the first path is the first starting point, and the ending path point of the first path is the target endpoint.

[0053] S208, Obtain the target path based on historical path information, where the initial path point of the target path is the target location and the ending path point of the target path is the target endpoint.

[0054] Optionally, in this embodiment, the method for obtaining the target path can be applied, but is not limited to, in deviation scenarios. Optionally, the understanding of a deviation scenario can be, but is not limited to, the situation where the target account in navigation mode is detected to have deviated from the navigation path, which is considered a deviation scenario. Specifically, there are various reasons for deviation, which can be divided into active and passive deviation from the user's (target account's) intention. Passive deviation often occurs when roads are complex or navigation broadcasts are inaccurate, causing the user to deviate from the navigation route. Active deviation is a user's voluntary behavior, generally due to dissatisfaction with the current route and a deliberate choice to take an alternate route. However, whether it is active or passive deviation, their commonality lies in the fact that users tend to take routes that are locally flexible but have a similar overall structure. Local flexibility means taking the user's current deviation location as the starting point of the route and the navigation priorities before the deviation as the route priorities, flexibly generating a navigation route that best fits the current situation for the user. Similar overall structure means that it is similar to the main structure of the navigation route before the deviation, that is, the main structure of the generated target route after deviation is similar to the main structure of the navigation route before the deviation.

[0055] Optionally, in this embodiment, the historical path information may be, but is not limited to, the path information of any historical moment that the target account has navigated on the navigation client. The historical path information may also be, but is not limited to, the path information of the previous historical moment or the historical moment closest to the current moment that the target account has navigated on the navigation client.

[0056] Optionally, in this embodiment, after obtaining the target path based on historical path information, deviation prompt information may be displayed, but is not limited to displaying deviation prompt information, wherein the deviation prompt information is used to indicate that the target account has deviated from the navigation range of the first navigation path; navigation prompt information and the target path are displayed, wherein the navigation prompt information is used to indicate that the navigation path has been replanned for the target account.

[0057] It should be noted that, in response to the first navigation request triggered on the navigation client logged into by the target account, a first navigation path generated for the target account is displayed on the navigation client. The starting point of the first navigation path is the first starting point, and the ending point of the first navigation path is the target endpoint. If the target device associated with the target account is found to be currently in the target location, and the target location is outside the navigation range of the first navigation path, a path retrieval request is generated. The target device is configured with a navigation client. In response to the path retrieval request, historical path information is obtained. This historical path information includes information about at least one first path navigated by the target account on the navigation client, where the initial point of the first path is the first starting point, and the ending point of the first path is the target endpoint. The target path is then retrieved based on the historical path information, where the initial point of the target path is the target location, and the ending point of the target path is the target endpoint.

[0058] To further illustrate, optional examples include... Figure 3 As shown, in response to a first navigation request triggered on a navigation client installed on the target terminal 302 (target device) logged in by the target account, a first navigation path 304 generated for the target account is displayed on the navigation client; if the target location 306 of the target terminal 302 associated with the target account is obtained and the target location 306 is outside the navigation range of the first navigation path 304, a path acquisition request is generated; in response to the path acquisition request, historical path information 312 is obtained, wherein the historical path information includes information on at least one first path that the target account has navigated on the navigation client, such as first path 310-1, first path 310-2, first path 310-3, etc.; and the target path 314 is obtained based on the historical path information 312.

[0059] According to the embodiments provided in this application, in response to a first navigation request triggered on a navigation client logged into by a target account, a first navigation path generated for the target account is displayed on the navigation client. The starting point of the first navigation path is a first starting point, and the ending point of the first navigation path is a target ending point. If the current target location of the target device associated with the target account is obtained, and the target location is outside the navigation range of the first navigation path, a path acquisition request is generated. The target device is configured with a navigation client. In response to the path acquisition request, historical path information is obtained. The historical path information includes information about at least one first path navigated by the target account on the navigation client, and the initial path point of the first path is... The first starting point and the ending point of the first path are the target endpoints. The target path is obtained based on historical path information, where the initial path point of the target path is the target location and the ending path point of the target path is the target endpoint. The historical path information of the target account is used to respond to the path acquisition request, so that the target path requested by the path acquisition request has a correlation with the historical data of the target account. Compared with the method of simply using the current deviation position as the navigation starting point when deviation occurs, this method of obtaining the target path in this embodiment of the invention is more in line with the true intention of the target account (user), thereby achieving the purpose of obtaining the target path efficiently and accurately, and thus realizing the technical effect of improving the accuracy of target path acquisition.

[0060] As an optional approach, the target path can be obtained based on historical path information, including:

[0061] S1, when candidate road data extracted from historical path information is obtained, target road data is determined from the candidate road data, wherein the candidate road data includes segment data of each road included in the first path, and the target road data includes segment data of the main road included in the first path.

[0062] S2, if at least one second path generated based on candidate road data is obtained, the target path is determined from the at least one second path according to the target road data, wherein the initial path point of the second path is the target location and the ending path point of the second path is the target endpoint.

[0063] Optionally, in this embodiment, the historical path information may be, but is not limited to, the path information of any historical moment that the target account has navigated on the navigation client. The historical path information may also be, but is not limited to, the path information of the previous historical moment or the historical moment closest to the current moment that the target account has navigated on the navigation client.

[0064] Optionally, in this embodiment, the segmented data (link) may be, but is not limited to, road segmentation data in the road network data, and the segmented data may be, but is not limited to, the smallest unit representing a road in the road network data; the segmented data of arterial roads may be, but is not limited to, data of high-grade roads such as main roads and highways. It is precisely defined as: roads that constitute 15%-85% of the route mileage; are at least county-level roads; have a width of 55 or more; and account for more than 20% of the entire route.

[0065] It should be noted that, when candidate road data extracted from historical path information is obtained, target road data is determined from the candidate road data. The candidate road data includes segment data of each road included in the first path, and the target road data includes segment data of the main roads included in the first path. When at least one second path generated based on the candidate road data is obtained, the target path is determined from the at least one second path according to the target road data. The initial path point of the second path is the target location, and the ending path point of the second path is the target endpoint.

[0066] Optionally, in this embodiment, the second path may be, but is not limited to, a path obtained from the first path that matches the historical path information; the target path may be, but is not limited to, a path that matches the target road data from among a plurality of candidate second paths;

[0067] To further illustrate, optional examples include... Figure 4 As shown, the target terminal 402 displays the first path 404, as follows. Figure 4As shown in (a); further responding to the path acquisition request triggered on the target terminal 402, multiple second paths matching the historical path information are acquired based on the first path 404, such as second path 406, second path 408, second path 410, etc.; furthermore, the aforementioned multiple second paths are used as a candidate path set, and a target path 412 matching the target road data is selected from the candidate path set, and this target path 412 is displayed on the target terminal 402 as the response result of the path acquisition request, such as... Figure 4 As shown in (b) of the diagram.

[0068] Optionally, in this embodiment, the first path may be, but is not limited to, the historical path included in the historical path information; the second path may be, but is not limited to, the path obtained based on the first path that matches the historical path information; the target path may be, but is not limited to, the path that matches the target road data among a plurality of candidate second paths.

[0069] To further illustrate, optional examples include... Figure 5 As shown, multiple first paths are obtained from the historical path information. These multiple first paths include first path 504, first path 506, and first path 508 displayed on the target terminal 502, as shown. Figure 5 As shown in (a); further in response to a path acquisition request triggered on the target terminal 502, multiple second paths matching the historical path information are acquired based on the aforementioned multiple first paths, such as second path 510, second path 512, second path 514, etc.; furthermore, the aforementioned multiple second paths are used as a candidate path set, and a target path 516 matching the target road data is selected from the candidate path set, and this target path 516 is displayed on the target terminal 502 as the response result of the path acquisition request, as shown in (a); Figure 5 As shown in (b) of the diagram.

[0070] According to the embodiments provided in this application, when candidate road data extracted from historical path information is obtained, target road data is determined from the candidate road data. The candidate road data includes segment data of each road included in the first path, and the target road data includes segment data of the main roads included in the first path. When at least one second path generated based on the candidate road data is obtained, the target path is determined from the at least one second path according to the target road data. The initial path point of the second path is the target location, and the ending path point of the second path is the target endpoint. To improve the utilization efficiency of the historical path information, after obtaining the historical path information, the target path is not directly obtained from the historical path information. Instead, further data processing is performed on the historical path information to obtain target road data with higher practicality. Compared with directly using historical path information containing a lot of useless information to obtain the target path, the method of obtaining the target path using the target road data can save unnecessary and invalid operations in the data processing process, thereby improving the efficiency of obtaining the target path and achieving the purpose of obtaining the target path efficiently and accurately. This achieves the technical effect of improving the accuracy of obtaining the target path.

[0071] As an optional approach, target road data can be obtained based on historical path information, including:

[0072] S1, Extract candidate road data from historical path information, wherein the candidate road data includes segment data of each road contained in the first path;

[0073] S2, identify the target road data from the candidate road data.

[0074] Optionally, in this embodiment, the candidate road data may also generate at least one second path.

[0075] Optionally, in this embodiment, the rerouting process using the target road data can, but is not limited to, keeping the endpoint before the yaw as the current route endpoint, and changing the starting point to the user's current location after the yaw.

[0076] It should be noted that candidate road data is extracted from historical route information; and target road data is determined from the candidate road data.

[0077] To further illustrate, optional examples include... Figure 6As shown, in response to a path retrieval request triggered on the navigation client logged into by the target account, historical path information 602 is obtained, wherein the historical path information 602 includes information on at least one first path 604 that the target account has navigated on the navigation client; candidate road data 606 is extracted from the historical path information 602, wherein the candidate road data 606 includes segment data of each road included in the first path 604; target road data 606 is determined from the candidate road data 606, wherein the target road data 606 includes segment data of the main roads included in the first path 604; at least one second path 610 is generated based on the candidate road data 606; and a target path 612 is determined from the at least one second path 610 based on the target road data 608.

[0078] As an alternative approach, candidate road data can be extracted from historical path information, including:

[0079] S1. Obtain N path points and M paths. The N path points include at least one path point on the first path. The M paths include the driving path corresponding to each of the N path points. Each of the M paths carries the corresponding driving direction. N is a natural number greater than or equal to 2, and M is a natural number.

[0080] S2, obtain the out-degree information and in-degree information of each path point among N path points. The out-degree information is used to represent the number of paths associated with the path point with the out direction of travel, and the in-degree information is used to represent the number of paths associated with the path point with the in direction of travel.

[0081] S3, determine the target path point from N path points based on the out-degree and in-degree information, where the target path point includes the second starting point and the target ending point;

[0082] S4, determine the path associated with the target waypoint as the candidate path, where the candidate road data includes the road data of the candidate path.

[0083] Optionally, in this embodiment, the road network data corresponding to the historical path information may include, but is not limited to, multiple path points and path lines, wherein a path line may be understood as a link and a path point may be understood as the endpoint of a link.

[0084] It should be noted that the process involves obtaining N waypoints and M paths. The N waypoints include at least one waypoint on the first path, and the M paths include the driving path corresponding to each of the N waypoints. Each of the M paths carries a corresponding driving direction. N is a natural number greater than or equal to 2, and M is a natural number. The process also involves obtaining the out-degree and in-degree information of each waypoint among the N waypoints. The out-degree information indicates the number of paths associated with the waypoint in the outward direction, and the in-degree information indicates the number of paths associated with the waypoint in the inward direction. Based on the out-degree and in-degree information, a target waypoint is determined from the N waypoints. The target waypoint includes a second starting point and a target ending point. The paths associated with the target waypoint are then identified as candidate paths. The candidate road data includes the road data of the candidate paths.

[0085] To further illustrate, optional examples include... Figure 7 As shown, there are multiple path points (circles) on an original path 702 (first path), multiple path points (circles) on an optional path 704, and at least one path line (line with arrows) associated with each path point. The optional path 704 can be, but is not limited to, a path that can be selected in the road network data. The out-degree information and in-degree information corresponding to each path point can be understood as, but is not limited to, the number of various types of path lines associated with the path point. For example, the out-degree information is the number of path lines associated with the path point that are outside the direction of the arrow, and the in-degree information is the number of path lines associated with the path point that are inside the direction of the arrow.

[0086] As an optional approach, the target path point is determined from N path points based on the out-degree and in-degree information, including at least one of the following:

[0087] S1, determine the target path point among N path points whose out-degree information indicates a path number that is not 1;

[0088] S2, determine the target path point among N path points whose number of paths represented by in-degree information is not 1;

[0089] S3, determine the target path point among N path points where the number of paths represented by the out-degree information is not 1 and the number of paths represented by the in-degree information is also not 1.

[0090] Optionally, in this embodiment, to determine the necessary paths (target path points) included in the target path, path points that provide additional information can be directly filtered out, such as path points whose out-degree and in-degree information are both 1. In addition, optional initial path points and termination path points can be understood as special path points. Therefore, even if the out-degree and in-degree information of the initial path point and termination path point are both 1, the initial path point and termination path point are still retained. The initial path point can be understood as the first starting point of the first path or the second starting point of the second path, and the termination path point can be understood as the target endpoint of the first path and the second path.

[0091] It should be noted that, among N path points, a target path point is identified where the number of paths represented by the out-degree information is not 1; among N path points, a target path point is identified where the number of paths represented by the in-degree information is not 1; and among N path points, a target path point is identified where the number of paths represented by both the out-degree information and the in-degree information are not 1.

[0092] To further illustrate, the optional based on Figure 7 As shown, continue for example Figure 8 As shown, among multiple path points, target path points (shaded circles) are identified where the number of paths represented by out-degree information is not 1, and / or the number of paths represented by in-degree information is also not 1, such as target path point 806 and target path 808; in addition, initial path point 802 and termination path point 804 are also included as target path points.

[0093] The embodiments provided in this application identify target path points among N path points whose out-degree information indicates a path number other than 1; identify target path points among N path points whose in-degree information indicates a path number other than 1; and identify target path points among N path points whose out-degree information indicates a path number other than 1 and whose in-degree information indicates a path number other than 1. This achieves the goal of fully preserving path points with additional information and improves the comprehensiveness of original information preservation during the target path acquisition process.

[0094] As an optional approach, before determining the target path from at least one second path based on the target road data, the following steps are included:

[0095] S1, perform concatenation on the candidate paths to obtain at least one continuous concatenated path;

[0096] S2, construct at least one second path based on at least one continuous splicing path, wherein the second path includes candidate paths.

[0097] Optionally, in this embodiment, when the target path point is obtained, multiple, and not unique, key links (candidate paths) associated with the topological target path point are saved.

[0098] Optionally, in this embodiment, the target path point is used as a waypoint, along with the initial and ending points of the current path. Then, the CH routing engine is used to calculate the optimal path for each segment. The results are then concatenated into a continuous line and finally output.

[0099] It should be noted that the candidate paths are spliced ​​together to obtain at least one continuous spliced ​​path; at least one second path is constructed based on the at least one continuous spliced ​​path, wherein the second path includes the candidate paths.

[0100] To further illustrate, the optional based on Figure 8 The scenario shown continues, for example... Figure 9 As shown in step S902, multiple, non-unique key links (bold dashed lines, i.e., candidate paths 902) associated with the target path points in the original path are obtained; further, as shown in step S902, the candidate paths 902 are spliced ​​to obtain at least one continuous spliced ​​path 904; then, as shown in step S904, at least one second path 906 is constructed based on at least one continuous spliced ​​path 904.

[0101] As an alternative approach, the target road data is determined from the candidate road data, including:

[0102] Target road data that meets the criteria for main roads are identified from the candidate road data. The roads corresponding to the road data that meet the criteria for main roads are main roads.

[0103] Optionally, in this embodiment, based on the definition of a trunk link, road data that does not meet the trunk road conditions in the candidate road data is further reduced to obtain target road data that meets the trunk road conditions in the candidate road data.

[0104] It should be noted that target road data that meets the conditions for main roads are determined from the candidate road data. The roads corresponding to the road data that meet the conditions for main roads are main roads.

[0105] Alternatively, as an alternative implementation method, such as Figure 10 As shown, the methods for obtaining the target path include:

[0106] S1002, in response to the path retrieval request triggered on the navigation client logged in by the target account, retrieve historical path information, wherein the historical path information includes information on at least one first path that the target account has navigated on the navigation client, the initial path point of the first path is the first starting point, and the ending path point of the first path is the target endpoint;

[0107] S1004, when candidate road data extracted from historical path information is obtained, target road data is determined from the candidate road data, wherein the candidate road data includes segment data of each road included in the first path, and the target road data includes segment data of the main road included in the first path.

[0108] S1006, if at least one second path generated based on candidate road data is obtained, a target path is determined from the at least one second path according to the target road data, wherein the initial path point of the second path is the second starting point, and the ending path point of the second path is the target ending point.

[0109] Optionally, in this embodiment, the method for obtaining the target path described above can be applied, but is not limited to, in navigation scenarios, and particularly, can be applied, but is not limited to, in deviation scenarios within navigation scenarios. A deviation scenario can be understood as, for example, when the location of a target account in navigation mode is detected to have deviated from the navigation path; in this case, the target account is considered to be in a deviation scenario. Specifically, there are various reasons for deviation, which, from the perspective of the user's (target account's) intention, can be divided into active and passive deviation. Passive deviation often occurs when roads are complex or navigation broadcasts are inaccurate, causing the user to mistakenly deviate from the navigation route. Active deviation is a user's voluntary behavior, generally indicating dissatisfaction with the current route and a deliberate choice to take an alternate route. However, whether it is an active or passive deviation, the commonality is that users tend to take routes that are flexible in some aspects but similar in the overall main structure. In this case, "flexible in some aspects" means that the route starts from the user's current deviation location and focuses on the navigation priorities before the deviation, so as to generate a navigation route that best fits the current situation. "Similar in the overall main structure" means that the main structure of the target route after the deviation is similar to that of the navigation route before the deviation.

[0110] Optionally, based on the above logic, this embodiment records the determination of target road data representing segmented data of the main road from the historical path information corresponding to the target account, and uses the target road data to generate a target path similar to the overall main road to meet the requirement of overall main road similarity; furthermore, the initial path point of the target path may be different from the initial path point before the yaw, but the ending path point of the target path is the same as the ending path point before the yaw to meet the requirement of local flexibility.

[0111] Optionally, in this embodiment, the method for obtaining the target path can be applied, but is not limited to, in ordinary navigation scenarios. For example, if a user (target account) is dissatisfied with the currently generated navigation route, a path acquisition request is triggered to generate a target path that matches the target account's historical path information. In this case, the first starting point of the first path and the second starting point of the second path can be understood, but is not limited to, as the same starting point. That is, the route generated by the current navigation is from the first starting point to the target destination. Then, based on the historical path information, a target path from the second starting point (first starting point) to the target destination is generated, thereby providing users with more diverse path acquisition methods to meet the increasing user needs.

[0112] Optionally, in this embodiment, the historical path information may be, but is not limited to, the path information of any historical moment that the target account has navigated on the navigation client. The historical path information may also be, but is not limited to, the path information of the previous historical moment or the historical moment closest to the current moment that the target account has navigated on the navigation client.

[0113] Optionally, in this embodiment, the segmented data (link) may be, but is not limited to, road segmentation data in the road network data, and the segmented data may be, but is not limited to, the smallest unit representing a road in the road network data; the segmented data of arterial roads may be, but is not limited to, data of high-grade roads such as main roads and highways. It is precisely defined as: roads that constitute 15%-85% of the route mileage; are at least county-level roads; have a width of 55 or more; and account for more than 20% of the entire route.

[0114] Optionally, in this embodiment, the second path may be, but is not limited to, a path obtained from the first path that matches the historical path information; the target path may be, but is not limited to, a path that matches the target road data from among a plurality of candidate second paths;

[0115] To further illustrate, optional examples include... Figure 4 As shown, the target terminal 402 displays the first path 404, as follows. Figure 4 As shown in (a); further responding to the path acquisition request triggered on the target terminal 402, multiple second paths matching the historical path information are acquired based on the first path 404, such as second path 406, second path 408, second path 410, etc.; furthermore, the aforementioned multiple second paths are used as a candidate path set, and a target path 412 matching the target road data is selected from the candidate path set, and this target path 412 is displayed on the target terminal 402 as the response result of the path acquisition request, such as... Figure 4 As shown in (b) of the diagram.

[0116] Optionally, in this embodiment, the first path may be, but is not limited to, the historical path included in the historical path information; the second path may be, but is not limited to, the path obtained based on the first path that matches the historical path information; the target path may be, but is not limited to, the path that matches the target road data among a plurality of candidate second paths.

[0117] To further illustrate, optional examples include... Figure 5 As shown, multiple first paths are obtained from the historical path information. These multiple first paths include first path 504, first path 506, and first path 508 displayed on the target terminal 502, as shown. Figure 5 As shown in (a); further in response to a path acquisition request triggered on the target terminal 502, multiple second paths matching the historical path information are acquired based on the aforementioned multiple first paths, such as second path 510, second path 512, second path 514, etc.; furthermore, the aforementioned multiple second paths are used as a candidate path set, and a target path 516 matching the target road data is selected from the candidate path set, and this target path 516 is displayed on the target terminal 502 as the response result of the path acquisition request, as shown in (a); Figure 5 As shown in (b) of the diagram.

[0118] It should be noted that, in response to a path retrieval request triggered on the navigation client logged into by the target account, historical path information is obtained. This historical path information includes information on at least one first path that the target account has navigated on the navigation client, where the initial path point of the first path is the first starting point, and the ending path point of the first path is the target destination. If candidate road data extracted from the historical path information is obtained, target road data is determined from the candidate road data. The candidate road data includes segment data of each road included in the first path, and the target road data includes segment data of the main roads included in the first path. If at least one second path generated based on the candidate road data is obtained, the target path is determined from the at least one second path according to the target road data. The initial path point of the second path is the second starting point, and the ending path point of the second path is the target destination.

[0119] To further illustrate, optional examples include... Figure 11As shown, in response to a path retrieval request triggered on the navigation client logged into by the target account, historical path information 1102 is obtained, wherein the historical path information 1102 includes information on at least one first path 1104 that the target account has navigated on the navigation client; candidate road data 1106 is extracted from the historical path information 1102, wherein the candidate road data 1106 includes segment data of each road included in the first path 1104; target road data 1106 is determined from the candidate road data 1106, wherein the target road data 1106 includes segment data of the main roads included in the first path 1104; at least one second path 1110 is generated based on the candidate road data 1106; and a target path 1112 is determined from the at least one second path 1110 based on the target road data 1108.

[0120] According to the embodiments provided in this application, in response to a path retrieval request triggered on the navigation client logged into by the target account, historical path information is obtained. This historical path information includes information about at least one first path navigated by the target account on the navigation client, where the initial path point of the first path is a first starting point, and the ending path point of the first path is a target endpoint. If candidate road data extracted from the historical path information is obtained, target road data is determined from the candidate road data. The candidate road data includes segment data of each road included in the first path, and the target road data includes segment data of the main roads included in the first path. If at least one second path generated based on the candidate road data is obtained, the target road data is used to determine the target road data from at least one first path. The target path is determined from the two paths, where the initial path point of the second path is the second starting point, and the ending path point of the second path is the target endpoint. To improve the utilization efficiency of the historical path information, after obtaining the historical path information, it is not directly used to obtain the target path. Instead, further data processing is performed on the historical path information to obtain more practical target road data. Compared with directly using historical path information containing a lot of useless information to obtain the target path, the method of obtaining the target path using target road data can save unnecessary and invalid operations in the data processing process, thereby improving the efficiency of obtaining the target path and achieving the goal of obtaining the target path efficiently and accurately. This achieves the technical effect of improving the accuracy of target path acquisition.

[0121] As an optional approach, before retrieving historical path information in response to a path retrieval request triggered on the navigation client logged into by the target account, the following steps are included:

[0122] S1, receive historical navigation information uploaded by the navigation client, wherein the historical navigation information includes historical route information;

[0123] S2 stores historical navigation information in a microservice database. The microservice database stores path information that any account has navigated to by the navigation client according to a timestamp and an account identifier. The timestamp indicates the upload time of the historical navigation data, and the account identifier indicates the login account of the navigation client that uploaded the historical navigation data.

[0124] Optionally, in this embodiment, the method for obtaining the target path can be, but is not limited to, an online process. In the case of yaw, it is necessary to obtain the navigation route before yaw online and then start the process of extraction and restoration.

[0125] Optionally, in this embodiment, the overall navigation service associated with the above-mentioned target path acquisition method may, but is not limited to, adopt a microservice architecture. To achieve statelessness, different sub-services typically store session control or context information in a persistent data service. Each route in the route calculation navigation has a globally unique identity document (ID), which is also the key corresponding to the data in the persistent service. Therefore, route data can be retrieved from the persistent service based on the route ID.

[0126] Optionally, in this embodiment, the generalization of the microservice architecture can be understood, but is not limited to, as statelessness between different self-services, i.e., a continuous process on the timeline. For example, if a deviation occurs at a certain point on the timeline, it is necessary to know the route before the deviation, i.e., context information. The context information is stored in the same location, so that the microservice architecture does not need to maintain a separate session control, but can directly extract it from the database.

[0127] It should be noted that the system receives historical navigation information uploaded by the navigation client, which includes historical path information. The system stores the historical navigation information in a microservice database, which stores the path information navigated by any account uploaded by the navigation client according to the timestamp and the account identifier. The timestamp is used to indicate the upload time of the historical navigation data, and the account identifier is used to indicate the login account of the navigation client that uploaded the historical navigation data.

[0128] To further illustrate, optional examples include... Figure 12As shown, the access layer 1202 in the microservice architecture receives historical navigation information uploaded by the navigation client, including historical path information. This historical navigation information is stored in the microservice database within the microservice architecture. The microservice database stores path information uploaded by any account from the navigation client, based on timestamps and account identifiers. The timestamp indicates the upload time of the historical navigation data, and the account identifier indicates the login account of the navigation client that uploaded the historical navigation data. Then, the generalized functions of the microservice architecture are used to implement the navigation route calculation process. For example, when a customer's navigation request arrives, the first step is to use the adsorption module (adsorption service) to convert the coordinates or specified POI in the request into road links in the road network for use by the route calculation engine. Based on the origin and destination links provided by the adsorption module, the route calculation engine uses an optimal path algorithm to calculate N (between 20 and 50) paths from the origin to the destination. These N paths are then filtered, scored, and selected by the sorting module (route sorting), ultimately determining the optimal paths (traffic prediction) to return to the user. The final step is for the guidance module (guidance broadcast) to add some navigation prompts to the above multiple paths. The persistent layer 1204 can be understood, but is not limited to, as the structure responsible for data access in the database.

[0129] The embodiments provided in this application receive historical navigation information uploaded by a navigation client, wherein the historical navigation information includes historical path information; the historical navigation information is stored in a microservice database, wherein the microservice database is used to store path information navigated by any account uploaded by the navigation client according to a timestamp and an account identifier. The timestamp is used to indicate the upload time of the historical navigation data, and the account identifier is used to indicate the login account of the navigation client that uploaded the historical navigation data. This achieves the purpose of realizing a stateless navigation service using a microservice architecture, thereby improving the versatility of navigation.

[0130] As an optional approach, before retrieving historical path information in response to a path retrieval request triggered on the navigation client logged into by the target account, the following steps are included:

[0131] S1, in response to the first navigation request triggered on the navigation client logged in by the target account, the first navigation path generated for the target account is displayed on the navigation client, wherein the starting point of the first navigation path is the first starting point, and the ending point of the first navigation path is the target ending point;

[0132] S2, obtain the current target location of the target device associated with the target account, wherein the target device is configured with a navigation client, and the target location includes the location of the second starting point;

[0133] S3, if the target location is outside the navigation range of the first navigation path, trigger the generation of a path acquisition request.

[0134] Optionally, in this embodiment, the method for obtaining the target path described above can be applied, but is not limited to, in navigation scenarios, and particularly, can be applied, but is not limited to, in deviation scenarios within navigation scenarios. A deviation scenario can be understood as, for example, when the location of a target account in navigation mode is detected to have deviated from the navigation path; in this case, the target account is considered to be in a deviation scenario. Specifically, there are various reasons for deviation, which, from the perspective of the user's (target account's) intention, can be divided into active and passive deviation. Passive deviation often occurs when roads are complex or navigation broadcasts are inaccurate, causing the user to mistakenly deviate from the navigation route. Active deviation is a user's voluntary behavior, generally indicating dissatisfaction with the current route and a deliberate choice to take an alternate route. However, whether it is an active or passive deviation, the commonality is that users tend to take routes that are flexible in some aspects but similar in the overall main structure. In this case, "flexible in some aspects" means that the route starts from the user's current deviation location and focuses on the navigation priorities before the deviation, so as to generate a navigation route that best fits the current situation. "Similar in the overall main structure" means that the main structure of the target route after the deviation is similar to that of the navigation route before the deviation.

[0135] Optionally, based on the above logic, this embodiment records the determination of target road data representing segmented data of the main road from the historical path information corresponding to the target account, and uses the target road data to generate a target path similar to the overall main road to meet the requirement of overall main road similarity; furthermore, the initial path point of the target path may be different from the initial path point before the yaw, but the ending path point of the target path is the same as the ending path point before the yaw to meet the requirement of local flexibility.

[0136] It should be noted that, in response to the first navigation request triggered on the navigation client logged in by the target account, the navigation client displays the first navigation path generated for the target account, where the starting point of the first navigation path is the first starting point, and the ending point of the first navigation path is the target ending point; the target location of the target device associated with the target account is obtained, where the target device is configured with a navigation client, and the target location includes the location of the second starting point; if the target location is outside the navigation range of the first navigation path, a path retrieval request is triggered to generate.

[0137] As an optional approach, before retrieving historical path information in response to a path retrieval request triggered on the navigation client logged into by the target account, the following steps are included:

[0138] S1, in response to the first navigation request triggered on the navigation client logged in by the target account, the first navigation path generated for the target account is displayed on the navigation client, wherein the starting point of the first navigation path is the first starting point, and the ending point of the first navigation path is the target ending point;

[0139] S2, upon obtaining the second navigation request triggered on the navigation client logged in by the target account, generate a path retrieval request. The second navigation request is used to request a second navigation route for the target account, with the second starting point as the starting path point and the target end point as the ending path point. The second navigation route is different from the first navigation route.

[0140] Optionally, in this embodiment, the method for obtaining the target path can be applied, but is not limited to, in ordinary navigation scenarios. For example, if a user (target account) is dissatisfied with the currently generated navigation route, a path acquisition request is triggered to generate a target path that matches the target account's historical path information. In this case, the first starting point of the first path and the second starting point of the second path can be understood, but is not limited to, as the same starting point. That is, the route generated by the current navigation is from the first starting point to the target destination. Then, based on the historical path information, a target path from the second starting point (first starting point) to the target destination is generated, thereby providing users with more diverse path acquisition methods to meet the increasing user needs.

[0141] It should be noted that, in response to the first navigation request triggered on the navigation client logged in by the target account, a first navigation path generated for the target account is displayed on the navigation client. The starting point of the first navigation path is the first starting point, and the ending point of the first navigation path is the target endpoint. If a second navigation request is obtained from the navigation client logged in by the target account, a path retrieval request is generated. The second navigation request is used to request navigation for the target account to a second navigation route with the second starting point as the starting point and the target endpoint as the ending point. The second navigation route is different from the first navigation route.

[0142] As an optional solution, if the target location deviates from the navigation range of the first navigation path, the solution further includes: displaying a deviation warning message, wherein the deviation warning message is used to indicate that the target account has deviated from the navigation range of the first navigation path;

[0143] As an optional approach, after determining the target path from at least one second path based on the target road data, the method includes: displaying navigation prompts and the target path, wherein the navigation prompts are used to indicate that the navigation path has been replanned for the target account.

[0144] It should be noted that the system displays a deviation warning message, which indicates that the target account has deviated from the navigation range of the first navigation path; it also displays navigation prompts and the target path, whereby the navigation prompts indicate that a new navigation path has been planned for the target account.

[0145] The embodiments provided in this application display deviation warning information, which is used to indicate that the target account has deviated from the navigation range of the first navigation path; display navigation warning information and target path, wherein the navigation warning information is used to indicate that the navigation path has been replanned for the target account, thereby achieving the purpose of displaying the target path more intuitively and realizing the effect of improving the intuitiveness of the target path display.

[0146] As an optional approach, for ease of understanding, the method for obtaining the target path described above is applied to the retrieval of the main trunk route after a deviation. This means only identifying and retaining the main trunk link is needed, rather than striving for a perfect restoration. The reason is that user deviations are often due to dissatisfaction with the original route, so a perfect restoration of the original route does not meet user expectations; a certain degree of generalization and variation is necessary. This step ensures that after a deviation, the retrieval process provides the main trunk route selected by the user before the deviation, thus meeting user expectations.

[0147] Optionally, in this embodiment, the main link may be, but is not limited to, a road that is within 15%-85% of the route mileage; is a county-level or higher road; has a width of 55 or more; and accounts for more than 20% of the entire route.

[0148] Optionally, in this embodiment, the backbone link extraction and restoration are online processes. The pre-deviation navigation route needs to be obtained online before the extraction and restoration process begins. The overall navigation service adopts a microservice architecture. To achieve statelessness between different sub-services, session control or context information is generally stored in a persistent data service. Each route in the route calculation and navigation has a globally unique ID, which is also the key corresponding to the data in the persistent service. Therefore, route data can be retrieved from the persistent service based on the route ID.

[0149] Optionally, in this embodiment, the backbone link thinning step is performed first, such as removing points with an in-degree of 1 from the route, except for the start and end links. These links are essential for a route and provide no additional information, so they can be removed. Furthermore, the sparse link string obtained in the first step is further reduced according to the definition of the backbone link, retaining only the backbone links.

[0150] The route is recalculated further. The endpoint before the yaw remains the current endpoint, while the starting point becomes the user's current location after the yaw. The sparse link strings obtained in the above backbone link thinning steps are used as waypoints. Combined with the current start and end points, the CH routing engine calculates the optimal path for each segment by performing point-to-point routing. The results are then concatenated into a continuous route, which is finally output.

[0151] To further illustrate, the overall process of the optional yaw return route is as follows: Figure 13 As shown:

[0152] In step S1302, the client 1302 initiates an algorithm request and sends it to the navigation access module 1302;

[0153] In step S1304, the data persistence module 1304 receives the route data sent by the navigation access module 1302 and saves it to disk.

[0154] Step S1306: The navigation access module 1302 returns the route calculation result to the client 1302;

[0155] In step S1308, client 1302 selects a route and initiates navigation;

[0156] In step S1310, the navigation access module 1302 returns the route and broadcasts it to the client 1302;

[0157] In step S1312, client 1302 detects a yaw in the line;

[0158] Step S1314: Navigation access module 1302 sends a route calculation request to trunk recall module 1306;

[0159] Step S1316, the main trunk recall module 1306 requests to obtain the route before yaw;

[0160] In step S1318, the data persistence module 1304 returns the route before yaw to the trunk recall module 1306;

[0161] In step S1320, the main trunk recall module 1306 returns the restored route to the navigation access module 1302;

[0162] In step S1322, the navigation access module 1302 returns the route after yaw.

[0163] The embodiments of this application meet the user's needs and maximize the likelihood of meeting the user's expectations for the mid-flight deviation scenario.

[0164] It is understood that in the specific embodiments of this application, data such as user information are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0165] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the present invention is not limited to the described order of actions, because according to the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to the present invention.

[0166] According to another aspect of the present invention, an apparatus for obtaining a target path for implementing the above-described target path acquisition method is also provided. For example... Figure 14 As shown, the device includes:

[0167] The first display unit 1402 is used to respond to a first navigation request triggered on the navigation client logged in by the target account and display a first navigation path generated for the target account on the navigation client, wherein the starting point of the first navigation path is a first starting point and the ending point of the first navigation path is a target ending point.

[0168] The first generation unit 1404 is used to generate a path acquisition request when the target location of the target device associated with the target account is obtained and the target location is outside the navigation range of the first navigation path, wherein a navigation client is configured on the target device.

[0169] The first acquisition unit 1406 is used to respond to a path acquisition request and acquire historical path information, wherein the historical path information includes information on at least one first path that the target account has navigated on the navigation client, the initial path point of the first path is the first starting point, and the ending path point of the first path is the target endpoint.

[0170] The second acquisition unit 1408 is used to acquire the target path based on historical path information, wherein the initial path point of the target path is the target location, and the ending path point of the target path is the target endpoint.

[0171] Optionally, in this embodiment, the method for obtaining the target path can be applied, but is not limited to, in deviation scenarios. Optionally, the understanding of a deviation scenario can be, but is not limited to, the situation where the target account in navigation mode is detected to have deviated from the navigation path, which is considered a deviation scenario. Specifically, there are various reasons for deviation, which can be divided into active and passive deviation from the user's (target account's) intention. Passive deviation often occurs when roads are complex or navigation broadcasts are inaccurate, causing the user to deviate from the navigation route. Active deviation is a user's voluntary behavior, generally due to dissatisfaction with the current route and a deliberate choice to take an alternate route. However, whether it is active or passive deviation, their commonality lies in the fact that users tend to take routes that are locally flexible but have a similar overall structure. Local flexibility means taking the user's current deviation location as the starting point of the route and the navigation priorities before the deviation as the route priorities, flexibly generating a navigation route that best fits the current situation for the user. Similar overall structure means that it is similar to the main structure of the navigation route before the deviation, that is, the main structure of the generated target route after deviation is similar to the main structure of the navigation route before the deviation.

[0172] Optionally, in this embodiment, the historical path information may be, but is not limited to, the path information of any historical moment that the target account has navigated on the navigation client. The historical path information may also be, but is not limited to, the path information of the previous historical moment or the historical moment closest to the current moment that the target account has navigated on the navigation client.

[0173] Optionally, in this embodiment, after obtaining the target path based on historical path information, deviation prompt information may be displayed, but is not limited to displaying deviation prompt information, wherein the deviation prompt information is used to indicate that the target account has deviated from the navigation range of the first navigation path; navigation prompt information and the target path are displayed, wherein the navigation prompt information is used to indicate that the navigation path has been replanned for the target account.

[0174] It should be noted that, in response to the first navigation request triggered on the navigation client logged into by the target account, a first navigation path generated for the target account is displayed on the navigation client. The starting point of the first navigation path is the first starting point, and the ending point of the first navigation path is the target endpoint. If the target device associated with the target account is found to be currently in the target location, and the target location is outside the navigation range of the first navigation path, a path retrieval request is generated. The target device is configured with a navigation client. In response to the path retrieval request, historical path information is obtained. This historical path information includes information about at least one first path navigated by the target account on the navigation client, where the initial point of the first path is the first starting point, and the ending point of the first path is the target endpoint. The target path is then retrieved based on the historical path information, where the initial point of the target path is the target location, and the ending point of the target path is the target endpoint.

[0175] For specific embodiments, please refer to the example shown in the target path acquisition device above, which will not be repeated here.

[0176] According to the embodiments provided in this application, in response to a first navigation request triggered on a navigation client logged into by a target account, a first navigation path generated for the target account is displayed on the navigation client. The starting point of the first navigation path is a first starting point, and the ending point of the first navigation path is a target ending point. If the current target location of the target device associated with the target account is obtained, and the target location is outside the navigation range of the first navigation path, a path acquisition request is generated. The target device is configured with a navigation client. In response to the path acquisition request, historical path information is obtained. The historical path information includes information about at least one first path navigated by the target account on the navigation client, and the initial path point of the first path is... The first starting point and the ending point of the first path are the target endpoints. The target path is obtained based on historical path information, where the initial path point of the target path is the target location and the ending path point of the target path is the target endpoint. The historical path information of the target account is used to respond to the path acquisition request, so that the target path requested by the path acquisition request has a correlation with the historical data of the target account. Compared with the method of simply using the current deviation position as the navigation starting point when deviation occurs, this method of obtaining the target path in this embodiment of the invention is more in line with the true intention of the target account (user), thereby achieving the purpose of obtaining the target path efficiently and accurately, and thus realizing the technical effect of improving the accuracy of target path acquisition.

[0177] As an optional solution, the second acquisition unit 1408 includes:

[0178] The first determining module is used to determine the target road data from the candidate road data when the candidate road data extracted from the historical path information is obtained. The candidate road data includes the segment data of each road included in the first path, and the target road data includes the segment data of the main road included in the first path.

[0179] The second determining module is used to determine the target path from the at least one second path generated based on the candidate road data, wherein the initial path point of the second path is the target location and the ending path point of the second path is the target endpoint.

[0180] For specific implementation examples, please refer to the example shown in the above target path acquisition method, which will not be repeated here.

[0181] As an optional solution, the second acquisition unit 1408 includes:

[0182] The extraction module is used to extract candidate road data from historical path information, wherein the candidate road data includes segment data of each road contained in the first path;

[0183] The third determination module is used to determine the target road data from the candidate road data.

[0184] For specific implementation examples, please refer to the example shown in the above target path acquisition method, which will not be repeated here.

[0185] As an optional solution, the extraction module includes:

[0186] The first acquisition submodule is used to acquire N path points and M paths. The N path points include path points on at least one first path, and the M paths include the driving path corresponding to each of the N path points. Each of the M paths carries a corresponding driving direction. N is a natural number greater than or equal to 2, and M is a natural number.

[0187] The second acquisition submodule is used to acquire the out-degree information and in-degree information of each path point among N path points. The out-degree information is used to represent the number of paths associated with the path point with the out direction of travel, and the in-degree information is used to represent the number of paths associated with the path point with the in direction of travel.

[0188] The first determination submodule is used to determine the target path point from N path points based on the out-degree information and the in-degree information. The target path point includes the target location and the target destination.

[0189] The second determination submodule is used to determine the path associated with the target path point as a candidate path, wherein the candidate road data includes the road data of the candidate path.

[0190] For specific implementation examples, please refer to the example shown in the above target path acquisition method, which will not be repeated here.

[0191] As an optional approach, the first identified submodule includes at least one of the following:

[0192] The first determining subunit is used to determine the target path point among N path points whose out-degree information indicates a path number that is not 1.

[0193] The second determining subunit is used to determine the target path point among N path points whose number of paths represented by in-degree information is not 1.

[0194] The third determining subunit is used to determine, among N path points, the target path point whose out-degree information indicates a path number that is not 1 and whose in-degree information indicates a path number that is not 1.

[0195] For specific implementation examples, please refer to the example shown in the above target path acquisition method, which will not be repeated here.

[0196] As an optional solution, it includes:

[0197] The third determination submodule is used to perform concatenation processing on candidate paths to obtain at least one continuous concatenated path before determining the target path from at least one second path based on the target road data.

[0198] The third acquisition submodule is used to construct at least one second path based on at least one continuous spliced ​​path before determining the target path from at least one second path based on the target road data, wherein the second path includes candidate paths.

[0199] For specific implementation examples, please refer to the example shown in the above target path acquisition method, which will not be repeated here.

[0200] As an optional solution, the third determining module includes:

[0201] The fourth acquisition submodule is used to determine the target road data that meets the conditions of main roads from the candidate road data. The road corresponding to the road data that meets the conditions of main roads is a main road.

[0202] For specific implementation examples, please refer to the example shown in the above target path acquisition method, which will not be repeated here.

[0203] According to another aspect of the present invention, another target path acquisition apparatus for implementing the above-described target path acquisition method is also provided. For example... Figure 15 As shown, the device includes:

[0204] The third acquisition unit 1502 is used to respond to a path acquisition request triggered on the navigation client logged in by the target account and acquire historical path information, wherein the historical path information includes information on at least one first path that the target account has navigated on the navigation client, the initial path point of the first path is the first starting point, and the ending path point of the first path is the target endpoint.

[0205] The first determining unit 1504 is used to determine the target road data from the candidate road data when the candidate road data extracted from the historical path information is obtained. The candidate road data includes the segment data of each road included in the first path, and the target road data includes the segment data of the main road included in the first path.

[0206] The second determining unit 1506 is used to determine a target path from at least one second path based on the target road data when at least one second path generated based on the candidate road data is obtained, wherein the initial path point of the second path is the second starting point and the ending path point of the second path is the target ending point.

[0207] Optionally, in this embodiment, the method for obtaining the target path described above can be applied, but is not limited to, in navigation scenarios, and particularly, can be applied, but is not limited to, in deviation scenarios within navigation scenarios. A deviation scenario can be understood as, for example, when the location of a target account in navigation mode is detected to have deviated from the navigation path; in this case, the target account is considered to be in a deviation scenario. Specifically, there are various reasons for deviation, which, from the perspective of the user's (target account's) intention, can be divided into active and passive deviation. Passive deviation often occurs when roads are complex or navigation broadcasts are inaccurate, causing the user to mistakenly deviate from the navigation route. Active deviation is a user's voluntary behavior, generally indicating dissatisfaction with the current route and a deliberate choice to take an alternate route. However, whether it is an active or passive deviation, the commonality is that users tend to take routes that are flexible in some aspects but similar in the overall main structure. In this case, "flexible in some aspects" means that the route starts from the user's current deviation location and focuses on the navigation priorities before the deviation, so as to generate a navigation route that best fits the current situation. "Similar in the overall main structure" means that the main structure of the target route after the deviation is similar to that of the navigation route before the deviation.

[0208] Optionally, based on the above logic, this embodiment records the determination of target road data representing segmented data of the main road from the historical path information corresponding to the target account, and uses the target road data to generate a target path similar to the overall main road to meet the requirement of overall main road similarity; furthermore, the initial path point of the target path may be different from the initial path point before the yaw, but the ending path point of the target path is the same as the ending path point before the yaw to meet the requirement of local flexibility.

[0209] Optionally, in this embodiment, the method for obtaining the target path can be applied, but is not limited to, in ordinary navigation scenarios. For example, if a user (target account) is dissatisfied with the currently generated navigation route, a path acquisition request is triggered to generate a target path that matches the target account's historical path information. In this case, the first starting point of the first path and the second starting point of the second path can be understood, but is not limited to, as the same starting point. That is, the route generated by the current navigation is from the first starting point to the target destination. Then, based on the historical path information, a target path from the second starting point (first starting point) to the target destination is generated, thereby providing users with more diverse path acquisition methods to meet the increasing user needs.

[0210] Optionally, in this embodiment, the historical path information may be, but is not limited to, the path information of any historical moment that the target account has navigated on the navigation client. The historical path information may also be, but is not limited to, the path information of the previous historical moment or the historical moment closest to the current moment that the target account has navigated on the navigation client.

[0211] Optionally, in this embodiment, the segmented data (link) may be, but is not limited to, road segmentation data in the road network data, and the segmented data may be, but is not limited to, the smallest unit representing a road in the road network data; the segmented data of arterial roads may be, but is not limited to, data of high-grade roads such as main roads and highways. It is precisely defined as: roads that constitute 15%-85% of the route mileage; are at least county-level roads; have a width of 55 or more; and account for more than 20% of the entire route.

[0212] Optionally, in this embodiment, the second path may be, but is not limited to, a path obtained from the first path that matches the historical path information; the target path may be, but is not limited to, a path that matches the target road data from among a plurality of candidate second paths;

[0213] Optionally, in this embodiment, the first path may be, but is not limited to, the historical path included in the historical path information; the second path may be, but is not limited to, the path obtained based on the first path that matches the historical path information; the target path may be, but is not limited to, the path that matches the target road data among a plurality of candidate second paths.

[0214] It should be noted that, in response to a path retrieval request triggered on the navigation client logged into by the target account, historical path information is obtained. This historical path information includes information on at least one first path that the target account has navigated on the navigation client, where the initial path point of the first path is the first starting point, and the ending path point of the first path is the target destination. If candidate road data extracted from the historical path information is obtained, target road data is determined from the candidate road data. The candidate road data includes segment data of each road included in the first path, and the target road data includes segment data of the main roads included in the first path. If at least one second path generated based on the candidate road data is obtained, the target path is determined from the at least one second path according to the target road data. The initial path point of the second path is the second starting point, and the ending path point of the second path is the target destination.

[0215] According to the embodiments provided in this application, in response to a path retrieval request triggered on the navigation client logged into by the target account, historical path information is obtained. This historical path information includes information about at least one first path navigated by the target account on the navigation client, where the initial path point of the first path is a first starting point, and the ending path point of the first path is a target endpoint. If candidate road data extracted from the historical path information is obtained, target road data is determined from the candidate road data. The candidate road data includes segment data of each road included in the first path, and the target road data includes segment data of the main roads included in the first path. If at least one second path generated based on the candidate road data is obtained, the target road data is used to determine the target road data from at least one first path. The target path is determined from the two paths, where the initial path point of the second path is the second starting point, and the ending path point of the second path is the target endpoint. To improve the utilization efficiency of the historical path information, after obtaining the historical path information, it is not directly used to obtain the target path. Instead, further data processing is performed on the historical path information to obtain more practical target road data. Compared with directly using historical path information containing a lot of useless information to obtain the target path, the method of obtaining the target path using target road data can save unnecessary and invalid operations in the data processing process, thereby improving the efficiency of obtaining the target path and achieving the goal of obtaining the target path efficiently and accurately. This achieves the technical effect of improving the accuracy of target path acquisition.

[0216] As an optional solution, it includes:

[0217] The fourth acquisition unit is used to receive historical navigation information uploaded by the navigation client before acquiring historical path information in response to a path acquisition request triggered on the navigation client logged in by the target account. The historical navigation information includes historical path information.

[0218] The storage unit is used to store historical navigation information in the microservice database before retrieving historical path information in response to a path retrieval request triggered on the navigation client logged in by the target account. The microservice database is used to store the path information that any account has navigated by, uploaded by the navigation client, according to the timestamp and the account identifier. The timestamp is used to indicate the upload time of the historical navigation data, and the account identifier is used to indicate the login account of the navigation client that uploaded the historical navigation data.

[0219] For specific implementation examples, please refer to the example shown in the above target path acquisition method, which will not be repeated here.

[0220] As an optional solution, it includes:

[0221] The second display unit is used to display a first navigation path generated for the target account on the navigation client in response to a first navigation request triggered on the navigation client logged in by the target account before obtaining historical path information, wherein the starting point of the first navigation path is the first starting point and the ending point of the first navigation path is the target ending point.

[0222] The fifth acquisition unit is used to acquire the target location of the target device associated with the target account before acquiring historical path information in response to a path acquisition request triggered on the navigation client logged in by the target account. The target device is equipped with a navigation client, and the target location includes the location of the second starting point.

[0223] The second generation unit is used to generate a path retrieval request in response to a path retrieval request triggered on the navigation client logged in by the target account, before retrieving historical path information, when the target location is outside the navigation range of the first navigation path.

[0224] For specific implementation examples, please refer to the example shown in the above target path acquisition method, which will not be repeated here.

[0225] As an optional solution, it includes:

[0226] The third display unit is used to display a first navigation path generated for the target account on the navigation client in response to a first navigation request triggered on the navigation client logged in by the target account before obtaining historical path information, wherein the starting point of the first navigation path is the first starting point and the ending point of the first navigation path is the target ending point.

[0227] The third generation unit is used to generate a path retrieval request in response to a path retrieval request triggered on the navigation client logged in by the target account, before retrieving historical path information, and in the case of obtaining a second navigation request triggered on the navigation client logged in by the target account. The second navigation request is used to request a second navigation route for the target account, with a second starting point as the starting path point and a target ending point as the ending path point. The second navigation route is different from the first navigation route.

[0228] For specific implementation examples, please refer to the example shown in the above target path acquisition method, which will not be repeated here.

[0229] As an optional solution, the device further includes: a fourth display unit, used to display a deviation warning message when the target location deviates from the navigation range of the first navigation path, wherein the deviation warning message is used to indicate that the target account has deviated from the navigation range of the first navigation path;

[0230] The device also includes a fifth display unit, used to display navigation prompts and the target path after the target path has been determined from at least one second path based on the target road data, wherein the navigation prompts are used to indicate that the navigation path has been replanned for the target account.

[0231] For specific implementation examples, please refer to the example shown in the above target path acquisition method, which will not be repeated here.

[0232] According to another aspect of the present invention, an electronic device for implementing the above-described method for obtaining a target path is also provided, such as... Figure 16 As shown, the electronic device includes a memory 1602 and a processor 1604. The memory 1602 stores a computer program, and the processor 1604 is configured to execute the steps of any of the above method embodiments via the computer program.

[0233] Optionally, in this embodiment, the aforementioned electronic device may be located in at least one of a plurality of network devices in a computer network.

[0234] Optionally, in this embodiment, the processor can be configured to perform the following steps via a computer program:

[0235] S1, in response to the first navigation request triggered on the navigation client logged in by the target account, the first navigation path generated for the target account is displayed on the navigation client, wherein the starting point of the first navigation path is the first starting point, and the ending point of the first navigation path is the target ending point;

[0236] S2, when the target location of the target device associated with the target account is obtained and the target location is outside the navigation range of the first navigation path, a path acquisition request is generated, wherein a navigation client is configured on the target device;

[0237] S3, respond to the path retrieval request and retrieve historical path information, wherein the historical path information includes information on at least one first path that the target account has navigated on the navigation client, the initial path point of the first path is the first starting point, and the ending path point of the first path is the target endpoint;

[0238] S4, Obtain the target path based on historical path information, where the initial pathpoint of the target path is the target location, and the ending pathpoint of the target path is the target endpoint. Alternatively,

[0239] S1, in response to the path retrieval request triggered on the navigation client logged in by the target account, retrieve historical path information, wherein the historical path information includes information on at least one first path that the target account has navigated on the navigation client, the initial path point of the first path is the first starting point, and the ending path point of the first path is the target endpoint;

[0240] S2, Obtain target road data based on historical path information, wherein the target road data includes segment data of the main roads contained in the first path;

[0241] S3, if at least one second path generated based on historical path information is obtained, determine the target path from the at least one second path according to the target road data, wherein the initial path point of the second path is the second starting point, and the ending path point of the second path is the target ending point.

[0242] Alternatively, as those skilled in the art will understand, Figure 16 The structure shown is for illustrative purposes only. Electronic devices can also be smartphones (such as Android phones, iOS phones, etc.), tablets, PDAs, mobile internet devices (MIDs), PADs, and other terminal devices. Figure 16 This does not limit the structure of the aforementioned electronic devices. For example, the electronic device may also include components that are more... Figure 16 The more or fewer components shown (such as network interfaces, etc.), or having the same Figure 16 The different configurations shown.

[0243] The memory 1602 can be used to store software programs and modules, such as the program instructions / modules corresponding to the target path acquisition method and apparatus in this embodiment of the invention. The processor 1604 executes various functional applications and data processing by running the software programs and modules stored in the memory 1602, thereby realizing the aforementioned target path acquisition method. The memory 1602 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 1602 may further include memory remotely located relative to the processor 1604, and these remote memories can be connected to the terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. Specifically, the memory 1602 may be used, but is not limited to, to store historical path information and target path information. As an example, such as... Figure 16As shown, the memory 1602 may include, but is not limited to, the first display unit 1402, the first generation unit 1404, the first acquisition unit 1406, and the second acquisition unit 1408 (or the third acquisition unit 1502, the first determination unit 1504, and the second determination unit 1506, not shown in the figure) of the target path acquisition device. Furthermore, it may include, but is not limited to, other module units of the target path acquisition device, which will not be described in detail in this example.

[0244] Optionally, the transmission device 1606 described above is used to receive or send data via a network. Specific examples of the network described above may include wired networks and wireless networks. In one example, the transmission device 1606 includes a Network Interface Controller (NIC), which can be connected to other network devices and a router via a network cable to communicate with the Internet or a local area network. In another example, the transmission device 1606 is a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0245] In addition, the aforementioned electronic device also includes: a display 1608 for displaying the aforementioned historical path information and target path information; and a connection bus 1610 for connecting the various module components in the aforementioned electronic device.

[0246] In other embodiments, the aforementioned terminal device or server can be a node in a distributed system, wherein the distributed system can be a blockchain system, which is a distributed system formed by connecting multiple nodes through network communication. The nodes can form a peer-to-peer (P2P) network, and any form of computing device, such as a server, terminal, or other electronic device, can become a node in the blockchain system by joining this peer-to-peer network.

[0247] According to one aspect of this application, a computer program product is provided, comprising a computer program / instructions containing program code for performing the methods shown in the flowchart. In such embodiments, the computer program can be downloaded and installed from a network via a communication component, and / or installed from a removable medium. When the computer program is executed by a central processing unit, it performs various functions provided in embodiments of this application.

[0248] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0249] It should be noted that the computer system of the electronic device is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0250] A computer system includes a Central Processing Unit (CPU), which performs various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) or loaded from RAM. ROM also stores various programs and data required for system operation. The CPU, ROM, and RAM are interconnected via a bus. Input / output interfaces (I / O interfaces) are also connected to the bus.

[0251] The following components are connected to the input / output interface: input sections including keyboards, mice, etc.; output sections including cathode ray tubes (CRTs), liquid crystal displays (LCDs), and speakers; storage sections including hard drives; and communication sections including network interface cards such as LAN cards and modems. The communication section performs communication processing via a network such as the Internet. Drives are also connected to the input / output interface as needed. Removable media, such as disks, optical discs, magneto-optical discs, semiconductor memories, etc., are installed on the drive as needed so that computer programs read from them can be installed into the storage section as required.

[0252] Specifically, according to embodiments of this application, the processes described in the various method flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication component, and / or installed from a removable medium. When the computer program is executed by a central processing unit, it performs various functions defined in the system of this application.

[0253] According to one aspect of this application, a computer-readable storage medium is provided, wherein a processor of a computer device reads computer instructions from the computer-readable storage medium, and executes the computer instructions, causing the computer device to perform the methods provided in the various alternative implementations described above.

[0254] Optionally, in this embodiment, the computer-readable storage medium described above may be configured to store a computer program for performing the following steps:

[0255] S1, in response to a first navigation request triggered on the navigation client logged in by the target account, a first navigation path generated for the target account is displayed on the navigation client, wherein the starting point of the first navigation path is a first starting point, and the ending point of the first navigation path is a target ending point;

[0256] S2, when the target location of the target device associated with the target account is obtained and the target location is outside the navigation range of the first navigation path, a path acquisition request is generated, wherein the navigation client is configured on the target device;

[0257] S3, responding to the path acquisition request, acquire historical path information, wherein the historical path information includes information on at least one first path that the target account has navigated on the navigation client, the initial path point of the first path is the first starting point, and the ending path point of the first path is the target endpoint;

[0258] S4, obtain the target path based on the historical path information, wherein the initial path point of the target path is the target location, and the ending path point of the target path is the target endpoint. Alternatively,

[0259] S1, in response to the path retrieval request triggered on the navigation client logged in by the target account, retrieve historical path information, wherein the historical path information includes information on at least one first path that the target account has navigated on the navigation client, the initial path point of the first path is the first starting point, and the ending path point of the first path is the target endpoint;

[0260] S2, Obtain target road data based on historical path information, wherein the target road data includes segment data of the main roads contained in the first path;

[0261] S3, if at least one second path generated based on historical path information is obtained, determine the target path from the at least one second path according to the target road data, wherein the initial path point of the second path is the second starting point, and the ending path point of the second path is the target ending point.

[0262] Optionally, in this embodiment, those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing the hardware related to the terminal device. The program can be stored in a computer-readable storage medium, which may include: flash drive, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0263] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0264] If the integrated units in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in the aforementioned computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause one or more computer devices (which may be personal computers, servers, or network devices, etc.) to execute all or part of the steps of the methods of the various embodiments of the present invention.

[0265] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0266] In the several embodiments provided in this application, it should be understood that the disclosed client can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or the indirect coupling or communication connection of units or modules may be electrical or other forms.

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

[0268] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0269] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for obtaining a target path, characterized in that, include: In response to a first navigation request triggered on a navigation client logged in by the target account, a first navigation path generated for the target account is displayed on the navigation client, wherein the starting point of the first navigation path is a first starting point, and the ending point of the first navigation path is a target ending point; If the target location of the target device associated with the target account is obtained and the target location is outside the navigation range of the first navigation path, a path acquisition request is generated, wherein the navigation client is configured on the target device; In response to the path acquisition request, historical path information is acquired, wherein the historical path information includes information on at least one first path that the target account has navigated on the navigation client, the initial path point of the first path is the first starting point, and the ending path point of the first path is the target endpoint. Before responding to the path acquisition request and acquiring historical path information, the method further includes: receiving historical navigation information uploaded by the navigation client, wherein the historical navigation information includes the historical path information; storing the historical navigation information in a microservice database, wherein the microservice database is used to store path information navigated by any account uploaded by the navigation client according to a timestamp and an account identifier, wherein the timestamp is used to indicate the upload time of the historical navigation information, and the account identifier is used to indicate the login account of the navigation client that uploaded the historical navigation information, and the architecture of the microservice database is generalized to be stateless between different self-services, storing context information in the same location, wherein the context information includes the route before the deviation occurred at a certain point on the timeline; If candidate road data is obtained from the historical route information, target road data is determined from the candidate road data. The candidate road data includes segment data of each road included in the first route, and the target road data includes segment data of the main roads included in the first route. The main roads are county-level or above roads with a width of 55 or more, accounting for more than 20% of the entire route mileage within 15%-85% of the route mileage. If at least one second path is obtained based on the candidate road data, a target path is determined from the at least one second path according to the target road data, wherein the initial path point of the second path is the target location, and the ending path point of the second path is the target endpoint.

2. The method according to claim 1, characterized in that, Before determining the target road data from the candidate road data, the method further includes: Obtain N path points and M paths, wherein the N path points include path points on at least one first path, the M paths include the driving path corresponding to each of the N path points, and each of the M paths carries a corresponding driving direction, where N is a natural number greater than or equal to 2, and M is a natural number. Obtain the out-degree information and in-degree information of each of the N path points, wherein the out-degree information is used to represent the number of paths associated with the path point with the outward direction of travel, and the in-degree information is used to represent the number of paths associated with the path point with the inward direction of travel. The target path point is determined from the N path points based on the out-degree information and the in-degree information, wherein the target path point includes the target location and the target endpoint; The path associated with the target waypoint is determined as a candidate path, wherein the candidate road data includes the road data of the candidate path.

3. The method according to claim 2, characterized in that, Determining the target path point from the N path points based on the out-degree information and the in-degree information includes at least one of the following: Among the N path points, identify the target path point whose out-degree information indicates a path number that is not 1; Among the N path points, identify the target path point whose in-degree information indicates a path number that is not 1; Among the N path points, determine the target path point where the number of paths represented by the out-degree information is not 1 and the number of paths represented by the in-degree information is also not 1.

4. The method according to claim 2, characterized in that, Before determining the target path from the at least one second path based on the target road data, the process includes: The candidate paths are spliced ​​together to obtain at least one continuous spliced ​​path; The at least one second path is constructed based on the at least one continuous splicing path, wherein the second path includes the candidate path.

5. The method according to claim 1, characterized in that, When the target location of the target device associated with the target account is obtained and the target location is outside the navigation range of the first navigation path, the method further includes: displaying a deviation prompt message, wherein the deviation prompt message is used to indicate that the target account has deviated from the navigation range of the first navigation path; After determining the target path from the at least one second path based on the target road data, the method includes: displaying navigation prompt information and the target path, wherein the navigation prompt information is used to indicate that the navigation path has been replanned for the target account.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program, when executed, performs the method described in any one of claims 1 to 5.

7. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method described in any one of claims 1 to 5.

8. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to execute the method described in any one of claims 1 to 5 through the computer program.

Images