Pick-up point correction method, device, equipment and storage medium

Abstract

Embodiments of the present application provide a pickup point correction method, device, equipment and storage medium. The method obtains vehicle navigation data in a pickup process corresponding to a to-be-processed order; determines whether the to-be-processed order has a pickup point exception according to the vehicle navigation data and a preset exception judgment condition, the exception judgment condition being determined based on a route feature in a first route, the first route being a route of a first preset distance before reaching a navigation terminal point in a vehicle navigation route; and if there is a pickup point exception, updating the pickup point based on a starting point position corresponding to the to-be-processed order. The technical solution can accurately correct an inaccurate original pickup point, and reduce communication costs and waiting time caused by pickup point errors.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a method, apparatus, device, and storage medium for correcting the vehicle loading point. Background Technology

[0002] In ride-hailing services, the accuracy of driver-side pick-up navigation directly affects pick-up efficiency and user experience. When a driver receives an order, the driver usually generates a pick-up route based on the order's starting coordinates, the driver's current location, and the navigation service.

[0003] In actual business operations, the starting coordinates given for some orders may fall on elevated roads, expressways, interchanges, tunnels, highways, ramps, internal roads within industrial parks, or non-navigation roads.

[0004] This resulted in the incorrect determination of the pick-up point for the order, thereby increasing costs related to user communication and vehicle usage. Summary of the Invention

[0005] This application provides a method, apparatus, device, and storage medium for correcting the boarding point, in order to achieve the technical effect of improving the accuracy of the boarding point.

[0006] In a first aspect, embodiments of this application provide a method for correcting the boarding point, applied to an electronic device, the method comprising:

[0007] Obtain vehicle navigation data during the passenger pick-up process for orders to be processed;

[0008] Based on the vehicle navigation data and preset anomaly judgment conditions, it is determined whether the pending order has an abnormal pick-up point. The anomaly judgment conditions are determined based on the route characteristics in the first route, which is the route in the vehicle navigation route that is a first preset distance before reaching the navigation destination.

[0009] If an abnormal boarding point exists, the boarding point is updated based on the starting point location corresponding to the order to be processed.

[0010] In one or more embodiments, the route features include at least one of the following: end link type, road class, internal road length, and road type;

[0011] The anomaly detection conditions include at least one of the following: the terminal link type is indicated as a tunnel; the road grade and road type are indicated as expressway, elevated road, rapid transit, grade-separated interchange, and interchange; the internal road length is greater than a first preset length and there are pedestrian hotspots; the road type is a ramp and the route length is greater than a second preset length.

[0012] In one or more embodiments, updating the boarding point based on the starting point location corresponding to the order to be processed includes:

[0013] In a preset recommended point library, at least one recommended point is determined within a first preset range centered on the starting point position. The recommended point library records different recommended points and the positions corresponding to each recommended point.

[0014] At least one recommended point corresponding to the first region is determined from a preset recommended point library, which contains different regions and recommended points corresponding to each region.

[0015] Update the boarding point based on the at least one recommended point and the starting point location.

[0016] In one or more embodiments, updating the boarding point based on the at least one recommended point and the starting point location includes:

[0017] Among the at least one recommended point, determine the recommended point that is closest to the starting point;

[0018] If the walking distance between the nearest recommended point and the starting point is less than the walking distance threshold, the nearest recommended point is determined as the first recommended point;

[0019] If, based on the new vehicle navigation data constructed from the first recommended point and the anomaly judgment conditions, it is determined that the first recommended point does not have any anomalies, then the boarding point is updated according to the first recommended point.

[0020] In one or more embodiments, the electronic device is a user terminal;

[0021] Accordingly, updating the boarding point based on the first recommended point includes:

[0022] Based on the first recommended point, a first prompt message is generated on the user terminal. The first prompt message is used to notify the user that the pick-up point is abnormal, recommend a new pick-up point, and suggest communicating with the customer to change the pick-up point.

[0023] After receiving the confirmation information corresponding to the first prompt information from the customer, the first recommended point is determined as the new pick-up point, and navigation planning is performed based on the first recommended point.

[0024] In one or more embodiments, the electronic device is an in-vehicle infotainment system;

[0025] Accordingly, updating the boarding point based on the first recommended point includes:

[0026] The first recommended point is determined as the new pick-up point, and a second prompt message is sent to the customer terminal, the second prompt message being used to instruct the pick-up point to be updated to the first recommended point;

[0027] Navigation planning is performed in the vehicle system based on the first recommended point.

[0028] In one or more embodiments, the vehicle navigation data includes: the distance of the pick-up route, the time to reach the pick-up point, and the navigation destination;

[0029] Accordingly, determining whether there is an abnormal pick-up point for the pending order based on the vehicle navigation data and preset anomaly judgment conditions includes:

[0030] When the vehicle navigation data meets the first preset condition, the system determines whether the order to be processed has an abnormal pick-up point based on the vehicle navigation data and the anomaly judgment condition.

[0031] The first preset condition includes at least one of the following: the distance of the pick-up route is greater than a first preset distance, the time to reach the pick-up point is greater than a first preset time, and the distance between the navigation endpoint and the starting point is greater than a second preset distance.

[0032] Secondly, embodiments of this application provide a device for correcting the boarding point, applied to an electronic device, the device comprising:

[0033] The acquisition module is used to acquire vehicle navigation data during the passenger pick-up process for orders to be processed;

[0034] The determination module is used to determine whether there is an abnormal pick-up point in the pending order based on the vehicle navigation data and preset abnormal judgment conditions. The abnormal judgment conditions are determined based on the route characteristics in the first route, which is a route in the vehicle navigation route that is a first preset distance before reaching the navigation destination.

[0035] The update module is used to update the boarding point based on the starting position corresponding to the order to be processed when the boarding point is abnormal.

[0036] In one or more embodiments, the route features include at least one of the following: end link type, road class, internal road length, and road type;

[0037] The anomaly detection conditions include at least one of the following: the terminal link type is indicated as a tunnel; the road grade and road type are indicated as expressway, elevated road, rapid transit, grade-separated interchange, and interchange; the internal road length is greater than a first preset length and there are pedestrian hotspots; the road type is a ramp and the route length is greater than a second preset length.

[0038] In one or more embodiments, the update module updates the boarding point based on the starting point location corresponding to the order to be processed, specifically for:

[0039] In a preset recommended point library, at least one recommended point is determined within a first preset range centered on the starting point position. The recommended point library records different recommended points and the positions corresponding to each recommended point.

[0040] At least one recommended point corresponding to the first region is determined from a preset recommended point library, which contains different regions and recommended points corresponding to each region.

[0041] Update the boarding point based on the at least one recommended point and the starting point location.

[0042] In one or more embodiments, the update module updates the boarding point based on the at least one recommended point and the starting point location, specifically for:

[0043] Among the at least one recommended point, determine the recommended point that is closest to the starting point;

[0044] If the walking distance between the nearest recommended point and the starting point is less than the walking distance threshold, the nearest recommended point is determined as the first recommended point;

[0045] If, based on the new vehicle navigation data constructed from the first recommended point and the anomaly judgment conditions, it is determined that the first recommended point does not have any anomalies, then the boarding point is updated according to the first recommended point.

[0046] In one or more embodiments, the electronic device is a user terminal;

[0047] Accordingly, the update module updates the boarding point based on the first recommended point, specifically for:

[0048] Based on the first recommended point, a first prompt message is generated on the user terminal. The first prompt message is used to notify the user that the pick-up point is abnormal, recommend a new pick-up point, and suggest communicating with the customer to change the pick-up point.

[0049] After receiving the confirmation information corresponding to the first prompt information from the customer, the first recommended point is determined as the new pick-up point, and navigation planning is performed based on the first recommended point.

[0050] In one or more embodiments, the electronic device is an in-vehicle infotainment system;

[0051] Accordingly, the update module updates the boarding point based on the first recommended point, specifically for:

[0052] The first recommended point is determined as the new pick-up point, and a second prompt message is sent to the customer terminal, the second prompt message being used to instruct the pick-up point to be updated to the first recommended point;

[0053] Navigation planning is performed in the vehicle system based on the first recommended point.

[0054] In one or more embodiments, the vehicle navigation data includes: the distance of the pick-up route, the time to reach the pick-up point, and the navigation destination;

[0055] Accordingly, the determining module, based on the vehicle navigation data and preset anomaly judgment conditions, determines whether the pending order has an abnormal pick-up point, specifically for:

[0056] When the vehicle navigation data meets the first preset condition, the system determines whether the order to be processed has an abnormal pick-up point based on the vehicle navigation data and the anomaly judgment condition.

[0057] The first preset condition includes at least one of the following: the distance of the pick-up route is greater than a first preset distance, the time to reach the pick-up point is greater than a first preset time, and the distance between the navigation endpoint and the starting point is greater than a second preset distance.

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

[0059] The memory stores computer-executed instructions;

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

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

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

[0063] The pick-up point correction method, apparatus, device, and storage medium provided in this application embodiment are applied to electronic devices. The method involves acquiring vehicle navigation data during the passenger pick-up process corresponding to an order to be processed. Based on the vehicle navigation data and preset anomaly judgment conditions, it determines whether there is an abnormal pick-up point for the order to be processed. The anomaly judgment conditions are determined based on route characteristics in a first route, where the first route is a route within a first preset distance before reaching the navigation endpoint. If an abnormal pick-up point exists, the pick-up point is updated based on the starting position corresponding to the order to be processed. This technical solution, by acquiring vehicle navigation data during the passenger pick-up process corresponding to the order to be processed, allows for real-time or near-real-time monitoring of the vehicle's navigation route, providing an objective data basis for subsequent anomaly judgment. Based on the vehicle navigation data and preset anomaly judgment conditions, it can specifically identify whether the pick-up point near the passenger's navigation endpoint does not conform to normal pick-up logic. If an abnormal pick-up point is determined, the pick-up point is updated based on the starting position corresponding to the order to be processed, thereby dynamically correcting the situation caused by inaccurate original pick-up points and reducing communication costs and waiting time caused by incorrect pick-up points. Attached Figure Description

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

[0065] Figure 1 This is a schematic diagram of the structure of the boarding point correction system provided in the embodiments of this application;

[0066] Figure 2 A flowchart illustrating the method for correcting the boarding point provided in this application embodiment. Figure 1 ;

[0067] Figure 3 A flowchart illustrating the method for correcting the boarding point provided in this application embodiment. Figure 2 ;

[0068] Figure 4 A flowchart illustrating the method for correcting the boarding point provided in this application embodiment. Figure 3 ;

[0069] Figure 5 A flowchart illustrating the method for correcting the boarding point provided in this application embodiment. Figure 4 ;

[0070] Figure 6 This is a schematic diagram of the structure of the device for correcting the boarding point provided in an embodiment of this application;

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

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

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

[0074] During the ride-hailing process, the driver's app typically generates a pick-up route based on the order's origin coordinates, the driver's current location, and navigation services. For orders originating from the platform itself, pick-up points can usually be managed by combining platform-recommended points, geofences, points of interest (POIs), and historical drop-off data. However, when accepting orders from external ride-hailing platforms, the origin information received by the transportation capacity side mainly relies on the latitude, longitude, and POI information transmitted from the external platform, making it difficult to fully control the quality of the origin at the order placement stage.

[0075] In actual operation, the starting coordinates of some orders may fall on elevated roads, expressways, interchanges, tunnels, highways, ramps, internal roads within industrial parks, or non-navigation roads, and may also be some distance from the actual ground road entrance where a meeting point can be reached. The navigation system will plan the pick-up route around these abnormal coordinates, which may lead to the following technical problems:

[0076] 1) Uncontrollable quality of order origin: The origin sent by the external platform may be located in places where drivers and passengers are not suitable to meet, such as elevated roads, tunnels, highways, ramps or internal roads, which may make the pick-up route unfeasible or costly to execute.

[0077] 2) Static verification is prone to misjudgment or omission: It is difficult to accurately determine whether the boarding point is abnormal by relying solely on the original starting point coordinates or POI name, especially when there are complex relationships between the coordinate landing point and road traffic attributes, route end shape, pedestrian settlement points, etc. The current static verification method has limitations.

[0078] Among them, pedestrian checkpoints can be: special markings on roads to indicate that there are pedestrian paths on the road that vehicles cannot travel on; POIs can be: basic data structure units in Geographic Information Systems (GIS), which at the physical level are usually represented as a set of latitude and longitude coordinates with specific attributes; at the logical level, they represent geographic entities in the real world with specific functions and names (such as buildings, shops, bus stops, attractions, etc.).

[0079] 3) The correction result may be unreasonable: the new pick-up point after correction may be too far away, unreasonable, or still trigger abnormal policies (e.g., including no-entry signs). It is necessary to ensure that the correction point is both close to the passenger's original location and can improve the driver's pick-up route.

[0080] 4) Lack of automatic correction and closed-loop management: Existing technology does not automatically correct abnormal boarding points during the pick-up process, does not provide feedback on the reasons and results of corrections to the driver, and lacks the ability to record abnormal samples and iterate strategies.

[0081] Accordingly, in response to the technical problems existing in the prior art, the inventors of this application have the following concept: By analyzing the problem in the prior art where vehicles cannot pick up passengers near the designated pick-up point, it was realized that the root cause of the problem is not the coordinates of the pick-up point itself, but the compliance of the vehicle's driving in the last segment of the route approaching that point. Therefore, it is proposed to: use the vehicle navigation data during the passenger pick-up process to extract and analyze the route characteristics within the first preset distance before the end of the navigation route, and set anomaly judgment conditions accordingly. Once the current pick-up point is determined to be abnormal, it indicates that the original pick-up point is unreasonable or illegal. Then, the pick-up point is actively recalculated and updated based on the actual starting position of the order, thereby fundamentally avoiding guiding the driver into illegal or unstoppable areas and ensuring that the vehicle can pick up passengers in a compliant and smooth manner.

[0082] and then, Figure 1 This is a schematic diagram of the structure of the boarding point correction system provided in the embodiments of this application, as shown below. Figure 1 As shown: This correction system includes the following four layers of implementation:

[0083] Layer 1: Input and Anomaly Detection;

[0084] Triggering conditions: The order is in the pre-pickup / pickup phase; the pick-up route is successfully planned for the first time; the same order will only be processed once.

[0085] Route characteristics: pick-up distance / time, end road link, internal road length, pedestrian hotspots, offset of the destination from the original starting point;

[0086] Anomaly sample accumulation: After anomaly features are detected, AOI / POI information is supplemented, and data such as routes, roads, coordinates, and internal roads are reported;

[0087] Output: Route feature set + outlier sample data.

[0088] Layer 2: Anomaly Detection and Candidate Generation:

[0089] Strategy configuration control: city switch, abnormal type switch, recommended point distance threshold, internal road threshold, ramp distance threshold;

[0090] Anomaly type identification: anomalies in tunnels, highways, elevated roads, ramps, and internal roads / pedestrian routes;

[0091] Recommendation point retrieval and filtering: Call the recommendation point library; select the recommendation point that is closest to the original starting point and meets the threshold;

[0092] Output: Candidate correction starting points.

[0093] Layer 3: Security verification of candidate recommendation points:

[0094] Passenger-side reachability verification: Walk distance is calculated from the original origin to the candidate recommended point; no correction is made if the walking distance exceeds the threshold.

[0095] Driver-side route verification: The driver independently calculates the route from the current location to the candidate point; the new route must not trigger any abnormal policies.

[0096] Restricted and Failure Protection: Maintain the original starting point when there is a restricted area sign, route calculation failure, invalid coordinates, or verification failure;

[0097] Output: The conclusion that the correction starting point 1 passed the verification is not corrected.

[0098] Layer 4: Correcting Execution and Data Loop:

[0099] Modify pick-up point: While the order is still valid and in the pick-up status, update the driver and passenger display / navigation starting point to the recommended point;

[0100] Driver Tips: The system will broadcast abnormality alerts for tunnels, highways, elevated roads, ramps, or pedestrian routes according to the type of abnormality, and guide drivers to communicate their boarding location.

[0101] Data closed loop: Records orders, original starting point, recommended point, anomaly type, walking distance, and correction results for strategy iteration;

[0102] Result: The driver and passengers were directed to the correct pick-up point nearby.

[0103] The above system example is only a brief illustration. Based on this system, the technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems will be described in detail below with specific embodiments. The subject of this technical solution is an electronic device; when the vehicle is an unmanned vehicle, the electronic device can be the vehicle's in-vehicle infotainment system; when the vehicle is driven by a driver, the electronic device can be a user terminal for the driver, such as a mobile phone.

[0104] The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0105] Figure 2 A flowchart illustrating the method for correcting the boarding point provided in this application embodiment. Figure 1 ,like Figure 2 As shown, the method includes:

[0106] Step 21: Obtain vehicle navigation data during the passenger pick-up process for the order to be processed;

[0107] In this step, when the vehicle is in the pre-pickup or pickup state and the pickup route is successfully planned for the first time, the navigation data of the pending order during the process of going to pick up the passenger can be obtained and recorded as vehicle navigation data.

[0108] In one possible implementation, the following vehicle navigation data can be obtained from the vehicle's navigation module or the driver-passenger simultaneous display service: total mileage of the pick-up route, total duration of the pick-up route, road links at the end of the route, road type at the beginning or end of the route, length of continuous internal roads at the end, whether there are vehicle turning points, and the offset distance between the navigation endpoint and the original order starting point.

[0109] Optionally, an order number recording mechanism can be used to ensure that the same order is processed only once, avoiding duplicate calculations or reports.

[0110] Step 22: Based on vehicle navigation data and preset anomaly judgment conditions, determine whether there are any abnormal pick-up points for the orders to be processed;

[0111] Among them, the anomaly judgment condition is determined based on the route characteristics in the first route, which is the route in the vehicle navigation route that is a first preset distance before reaching the navigation destination;

[0112] In this step, the acquired vehicle navigation data is compared with preset anomaly judgment conditions. If any of the vehicle navigation data meets any of the anomaly judgment conditions, it means that the pick-up point given by the vehicle navigation route is abnormal, that is, the pick-up point is unreachable or unreasonable.

[0113] Optionally, route features may include at least one of the following: end link type, road class, internal road length, and road type;

[0114] In this implementation, the end link type can be: tunnel, ramp, etc.; the road level can be: expressway, expressway, grade-separated, interchange, etc.; the internal road length can be obtained by traversing the road links from the end of the route forward and accumulating the length of the non-navigation road; the road type can be: elevated road, tunnel, internal road, etc.

[0115] Optionally, the anomaly detection conditions include at least one of the following: the end link type is indicated as a tunnel, the road grade and road type are indicated as expressway, elevated road, expressway, grade-separated, and interchange, the internal road length is greater than the first preset length and there are pedestrian clusters, the road type is a ramp and the route length is greater than the second preset length.

[0116] In this implementation, if the terminal link is a tunnel, it is identified as a tunnel anomaly; if the road level and road type meet the highway judgment conditions, it is identified as a highway anomaly; if there is a vehicle-to-pedestrian junction and the internal road length exceeds the internal route threshold (i.e., the first preset length), it is identified as an internal road or pedestrian route anomaly; if the road level and road name match the characteristics of elevated road, expressway, grade-separated road, interchange, etc., it is identified as an elevated road anomaly; if the terminal road is a ramp and the route length exceeds the ramp travel threshold (the second preset length), it is identified as a ramp anomaly.

[0117] Optionally, the abnormal judgment conditions may also include at least one of the following: the detour distance of the pick-up route is less than the first preset distance, parking is allowed on the destination road, there are no guardrails near the destination, the route does not cross main or auxiliary roads, the route is not located in a closed park, or the route is not located in a special control area of ​​an airport or train station.

[0118] Furthermore, if any of the above-mentioned anomalies regarding the boarding point exist, then step 23 below shall be executed.

[0119] Furthermore, if the vehicle navigation data fails to match any of the above criteria, no correction of the boarding point will be performed.

[0120] Optional, vehicle navigation data includes: distance to pick-up point, time to reach the pick-up point, and navigation destination;

[0121] Accordingly, one possible implementation of step 22 is: when the vehicle navigation data meets the first preset condition, determine whether there is an abnormal pick-up point for the order to be processed based on the vehicle navigation data and the abnormal judgment condition;

[0122] The first preset condition includes at least one of the following: the distance of the pick-up route is greater than the first preset distance, the time to reach the pick-up point is greater than the first preset time, and the distance between the navigation endpoint and the starting point is greater than the second preset distance.

[0123] In this implementation, before identifying boarding point anomalies, it can be determined whether the first preset condition for triggering correction is met. If it is met, it is considered that the order to be processed has a potential boarding point anomaly, and step 22 needs to be executed.

[0124] That is, if the distance of the pick-up route is greater than the first preset distance, it is considered that the pick-up route is too long; if the time to arrive at the pick-up point is greater than the first preset time, it is considered that the pick-up time is too long; if the distance between the navigation endpoint and the starting point is greater than the second preset distance, it is considered that the navigation endpoint is too far off from the original starting point; and it may also include: the internal route length exceeding the threshold, etc.

[0125] Step 23: If there is an abnormal boarding point, update the boarding point based on the starting point location of the order to be processed.

[0126] In this step, once it is confirmed that there is an abnormal boarding point for the current pending order, the boarding point correction process begins. At this time, a new boarding point is determined based on the starting point position corresponding to the pending order.

[0127] Optionally, before updating the boarding point, policy configurations (such as city switch, distance threshold, whether to check tunnels / highways / elevated roads, etc.) can be read. If any of these configurations exist, corresponding processing can be performed based on them, as detailed in the following embodiments.

[0128] For example, if the current city is not supported or the configuration is empty, the correction will be terminated; otherwise, based on the starting position of the order to be processed, a series of operations such as recommended point recall, filtering, and verification will be initiated to finally complete the boarding point update.

[0129] The pick-up point correction method provided in this application obtains vehicle navigation data during the passenger pick-up process corresponding to the order to be processed; based on the vehicle navigation data and preset anomaly judgment conditions, it determines whether there is an abnormal pick-up point for the order to be processed. The anomaly judgment conditions are determined based on the route characteristics in a first route, where the first route is a route with a first preset distance before reaching the navigation destination in the vehicle navigation route; if an abnormal pick-up point exists, the pick-up point is updated based on the starting position corresponding to the order to be processed. This technical solution, by obtaining vehicle navigation data during the passenger pick-up process corresponding to the order to be processed, can monitor the vehicle's navigation route in real-time or near real-time, thus providing an objective data basis for subsequent anomaly judgment; based on the vehicle navigation data and preset anomaly judgment conditions, it can specifically identify whether the pick-up point near the passenger's navigation destination does not conform to normal pick-up logic; if an abnormal pick-up point is determined, the pick-up point is updated based on the starting position corresponding to the order to be processed, thereby dynamically correcting the situation caused by the inaccuracy of the original pick-up point and reducing communication costs and waiting time caused by incorrect pick-up points.

[0130] Based on the above method embodiments, Figure 3 A flowchart illustrating the method for correcting the boarding point provided in this application embodiment. Figure 2 ,like Figure 3 As shown, step 23, which updates the boarding point based on the starting point location corresponding to the order to be processed, may include:

[0131] Step 31: Determine at least one recommended point within a first preset range centered on the starting point from the preset recommended point library;

[0132] The recommendation point database contains different recommendation points and the location corresponding to each recommendation point;

[0133] In this step, a circular or rectangular area with a first preset range (e.g., 200 meters) centered on the starting point location of the current pending order (e.g., the latitude and longitude of the starting point) is used as the range applicable for the customer to board the vehicle.

[0134] At this point, the recommendation point library can be retrieved from local or cloud sources, and at least one recommended point within the first preset range can be determined using the starting point location as an index.

[0135] In one possible implementation, the recommendation point library can be recommendation points corresponding to each city or region. When calling the recommendation point library, the city identifier (e.g., code) and the geographical coordinates of the starting point of the current pending order can also be input to recall at least one recommendation point within the first region from the recommendation point library.

[0136] Each recommended point can include its location (e.g., latitude and longitude information), and can then be used to determine the distance between the recommended point and the starting point.

[0137] Optionally, the recommended point library can be a third-party map recommended pick-up point library, a company-built POI library, clustering results of historical successful pick-up points, a road parking point database, or a multi-source fusion recommended point library, etc.

[0138] Step 32: Update the boarding point based on at least one recommended point and the starting point location.

[0139] In this step, a candidate recommended point is determined from at least one of the recalled recommended points, based on the original starting point location, as the new boarding point.

[0140] The boarding point correction method provided in this application involves determining at least one recommended point within a first preset range centered on the starting point from a preset recommended point library, which records different recommended points and their corresponding locations; determining at least one recommended point corresponding to a first regional range from the preset recommended point library, which records different regional ranges and their corresponding recommended points; and updating the boarding point based on the at least one recommended point and the starting point location. This technical solution narrows the selection of boarding points from a global search to a geographical interval centered on the starting point location, thereby reducing computational complexity and improving matching efficiency. Furthermore, determining at least one recommended point corresponding to the regional range from the preset recommended point library reduces online computation and improves response speed. Updating the boarding point based on the at least one recommended point and the starting point location allows for the optimization or correction of recommended points based on the user's actual location while preserving regional constraints, thus improving the rationality and accessibility of boarding points.

[0141] Based on the above method embodiments, Figure 4 A flowchart illustrating the method for correcting the boarding point provided in this application embodiment. Figure 3 ,like Figure 4 As shown, step 33 may include:

[0142] Step 41: Among at least one recommended point, determine the recommended point that is closest to the starting point;

[0143] In this step, all recommended points recalled in step 31 are traversed, the distance between each recommended point and the starting point is calculated, and the recommended point with the smallest distance is selected as the candidate recommended point.

[0144] Optionally, this distance can be a straight-line distance or a distance determined based on actual walking conditions; there is no limitation here.

[0145] In addition, a rating mechanism can be added to determine recommended points. Rating factors can include: straight-line distance, walking distance, driving time, availability of parking, historical success rate of pick-up and drop-off, passenger accessibility, road grade and safety, etc.

[0146] Step 42: If the walking distance between the nearest recommended point and the starting point is less than the walking distance threshold, the nearest recommended point is determined as the first recommended point;

[0147] In this step, taking the starting point as the starting point and the candidate recommended point as the ending point, the independent walking route calculation interface is called to calculate the actual walking distance from the starting point to the candidate recommended point.

[0148] If the walking distance is less than the configured walking distance threshold (e.g., 100 meters), the candidate recommended point is determined to be passenger-friendly and can be identified as the first recommended point.

[0149] Otherwise, keep the original boarding point unchanged and record the reason for the verification failure in order to update the algorithm for subsequent exception judgment conditions.

[0150] Step 43: If the new vehicle navigation data and anomaly judgment conditions constructed based on the first recommended point determine that there is no anomaly at the first recommended point, then update the boarding point according to the first recommended point.

[0151] In this step, the vehicle's current location is used as the starting point and the first recommended point is used as the ending point. The independent driving route calculation interface is called to generate the corrected pick-up route, which is the new vehicle navigation data.

[0152] After the route calculation is successful, the logic such as the anomaly judgment condition can be re-executed to check whether the new route still hits the anomaly of tunnel, highway, elevated road, ramp or internal road, and to check whether there are no-entry signs.

[0153] If there are issues such as route calculation failure, invalid coordinates, the new route still hitting the abnormal strategy, or the presence of a no-entry sign, the original boarding point will remain unchanged.

[0154] Only when the vehicle navigation data corresponding to the first recommended point meets expectations (i.e. no longer detects any anomalies) will the first recommended point be used as the starting point for correction after verification, and the process will proceed to the final vehicle entry point update stage.

[0155] Optionally, the electronic device is a user terminal;

[0156] Accordingly, one possible implementation of updating the boarding point based on the first recommended point in step 43 could be:

[0157] Step 1: Based on the first recommended point, generate the first prompt message on the user terminal. The first prompt message is used to notify the user that the pick-up point is abnormal, recommend a new pick-up point, and suggest communicating with the customer to change the pick-up point.

[0158] In this implementation, the first prompt message is generated and displayed on the user terminal (e.g., the driver's mobile application): The original pick-up point is located on an elevated / tunnel / highway section. A safer pick-up point nearby has been recommended for you. It is recommended that you contact the passenger in advance to confirm.

[0159] Step 2: After obtaining the confirmation information corresponding to the first prompt information from the customer, the first recommended point is determined as the new pick-up point, and navigation planning is carried out based on the first recommended point.

[0160] In this implementation, after contacting the passenger, if it is confirmed that the passenger can be picked up at a new pick-up point, the driver-passenger display module is invoked to update the first recommended point to the new pick-up point for the pending order, and the navigation route from the current location to the new pick-up point is replanned.

[0161] At the same time, notifications can be sent to passenger terminals to inform them that the boarding points have been optimized and adjusted.

[0162] Optionally, the electronic device is an in-vehicle infotainment system;

[0163] Accordingly, another possible implementation of updating the boarding point based on the first recommended point in step 43 could be:

[0164] Step 1: Determine the first recommended point as the new pick-up point and send a second prompt message to the customer terminal. The second prompt message is used to instruct the pick-up point to be updated to the first recommended point.

[0165] In this implementation, the first recommended point is automatically set as the new pick-up point in the vehicle system (e.g., the in-vehicle navigation screen), without the need for manual confirmation by the driver or others.

[0166] At the same time, a second notification message is pushed to the passenger's terminal via the cloud: The boarding point has been optimized according to real-time traffic conditions. Please go to the new location to wait.

[0167] Furthermore, if the vehicle's infotainment system receives a passenger's rejection, it will not update the pick-up location.

[0168] Step 2: Based on the first recommended point, perform navigation planning in the vehicle's infotainment system.

[0169] In this implementation, the vehicle system automatically loads the driving route from the current vehicle location to the first recommended point, and can highlight the location of the new pick-up point on the navigation interface.

[0170] Based on the implementation of the above embodiments, detailed information about the overall correction event can be recorded, including: the order number of the order to be processed, the latitude and longitude of the starting point, the POI of the starting point, the latitude and longitude of the recommended point, the anomaly type, the walking distance, the route verification result, and the correction result. This detailed information can be used to evaluate the correction hit rate, false positive rate, and success rate, and to inversely optimize city configuration, distance thresholds, anomaly identification strategies, and the recommended point library, etc.

[0171] The boarding point correction method provided in this application involves determining the nearest recommended point to the starting point from at least one recommended point; if the walking distance between the nearest recommended point and the starting point is less than a walking distance threshold, the nearest recommended point is determined as the first recommended point; if new vehicle navigation data and anomaly judgment conditions constructed based on the first recommended point determine that the first recommended point does not have any anomalies, then the boarding point is updated according to the first recommended point. This technical solution prioritizes the geographically closest candidate pick-up point for users by identifying the nearest recommended point from at least one recommended point, thereby minimizing walking distance and improving the convenience of getting on and off the vehicle. If the walking distance between the nearest recommended point and the starting point is less than a walking distance threshold, this recommended point is designated as the first recommended point. By judging the distance threshold, recommended points that are too far away can be excluded, preventing users from abandoning the service or becoming dissatisfied due to excessive walking distance, thus enhancing practicality and user experience. If new vehicle navigation data and anomaly judgment conditions based on the first recommended point determine that the first recommended point is not abnormal, the pick-up point is updated according to the first recommended point. Here, by combining navigation data and anomaly judgment, recommended points that are actually unusable are further filtered out on the basis of optimal distance, thereby ensuring that the final pick-up point is not only close in distance but also has true vehicle accessibility and safety, improving the success rate and reliability of pick-up point recommendation.

[0172] Based on the above method embodiments, Figure 5 A flowchart illustrating the method for correcting the boarding point provided in this application embodiment. Figure 4 ,like Figure 5 As shown, one possible example of this method could be:

[0173] Step 501: The initial route planning for picking up passengers was successful;

[0174] Step 502: Obtain route information (i.e., vehicle navigation data);

[0175] Step 503: Determine if there is an anomaly. If not, proceed to step 504; if yes, proceed to step 505.

[0176] Among them, the abnormal judgment conditions (any one of the following is sufficient): the route has a no-entry sign; the walking route is greater than or equal to 30m (there is a walking block); the navigation destination is a tunnel / highway / elevated road.

[0177] Step 504: No correction; then end.

[0178] Step 505: Call the recommendation point library to obtain recommended points near the starting point;

[0179] Step 506: Request successful? If yes, proceed to step 507; if no, proceed to step 504.

[0180] Step 507: Obtain the recommended point with the shortest straight-line distance;

[0181] Step 508: Does the recommended point meet the configuration? If yes, proceed to step 509; if no, proceed to step 504.

[0182] Step 509: Call the pedestrian navigation independent route calculation interface; distance between the original starting point and the corrected starting point;

[0183] Step 510: Is the walking distance less than the threshold? If yes, proceed to step 511; otherwise, proceed to step 504.

[0184] Step 511: Call the driver and passenger simultaneous display independent routing interface; do not correct if it fails.

[0185] Step 512: If the correction meets expectations, proceed to step 513; otherwise, proceed to step 504.

[0186] Step 513: Modify the starting point.

[0187] The method for correcting the boarding point provided in this application has the following technical effects:

[0188] Technical benefits 1) Higher recognition accuracy: Based on the actual passenger pick-up route results, the system comprehensively judges whether the driver's actual pick-up is feasible by considering road attributes, end links, internal road length, pedestrian hotspots, and no-entry signs. Compared with solutions that only use coordinates, POI names, or static fences, the system is more accurate in reflecting whether the driver's actual pick-up is feasible.

[0189] Technical effect 2) The correction results are more reliable: Instead of directly replacing the recommended points after recalling them, the recommended points that are closest to the threshold are first screened, and then secondary verification is performed by walking route calculation and driving route calculation. This can reduce the risk of guiding passengers to too far away locations or guiding drivers to still abnormal locations.

[0190] Technical effect 3) Gray scale and operability: City switches, abnormal type switches and distance thresholds are all configurable, and can be gradually scaled up according to different city road structures, recommended point library quality and business strategies, which facilitates online governance and risk control;

[0191] Technical effect 4) Significantly improves the experience for drivers and passengers: By automatically correcting abnormal starting points to nearby recommended pick-up points that are more suitable for meeting, the probability of drivers taking detours, arriving at the wrong point, passengers walking long distances, and failures in driver-passenger communication can be reduced, thereby improving the success rate and efficiency of picking up passengers.

[0192] Technical effect 5) It has the ability to mine samples and iterate strategies: During the process of anomaly detection and correction, information such as order number, original starting point, recommended point, anomaly type, route distance, internal road length, and walking distance are recorded, which can provide a data foundation for the governance of the recommended point library, the quality analysis of the starting point of the external platform, and subsequent strategy optimization.

[0193] Based on the above method embodiments, Figure 6 This is a schematic diagram of the structure of the boarding point correction device provided in the embodiments of this application, as shown below. Figure 6 As shown, the correction device for the boarding point includes:

[0194] Module 61 is used to acquire vehicle navigation data during the passenger pick-up process corresponding to the order to be processed;

[0195] The determination module 62 is used to determine whether there is an abnormal pick-up point for the order to be processed based on vehicle navigation data and preset abnormal judgment conditions. The abnormal judgment conditions are determined based on the route characteristics in the first route, which is the route in the vehicle navigation route that is a first preset distance before reaching the navigation destination.

[0196] The update module 63 is used to update the boarding point based on the starting position of the order to be processed when there is an abnormal boarding point.

[0197] In one or more embodiments, the route features include at least one of the following: end link type, road class, internal road length, and road type;

[0198] The abnormal judgment conditions include at least one of the following: the end link type is indicated as a tunnel, the road level and road type are indicated as expressway, elevated road, expressway, grade-separated, and interchange, the internal road length is greater than the first preset length and there are pedestrian gathering points, the road type is a ramp and the route length is greater than the second preset length.

[0199] In one or more embodiments, the update module 63 updates the boarding point based on the starting point position corresponding to the order to be processed, specifically for:

[0200] In the preset recommended point library, at least one recommended point is determined within a first preset range centered on the starting point position. The recommended point library records different recommended points and the corresponding positions of each recommended point.

[0201] In the preset recommended point library, at least one recommended point corresponding to the first region is determined. The recommended point library contains different regions and the recommended points corresponding to each region.

[0202] Update the boarding point based on at least one recommended point and the starting point location.

[0203] In one or more embodiments, the update module 63 updates the boarding point based on at least one recommended point and the starting point location, specifically for:

[0204] Among at least one recommended point, determine the recommended point that is closest to the starting point;

[0205] If the walking distance between the nearest recommended point and the starting point is less than the walking distance threshold, the nearest recommended point will be determined as the first recommended point.

[0206] If the new vehicle navigation data and anomaly detection conditions based on the first recommended point determine that there is no anomaly at the first recommended point, then the boarding point is updated according to the first recommended point.

[0207] In one or more embodiments, the electronic device is a user terminal;

[0208] Correspondingly, update module 63, based on the first recommended point, to update the boarding point, specifically for:

[0209] Based on the first recommended point, a first prompt message is generated on the user's terminal. The first prompt message is used to notify the user that the pick-up point is abnormal, recommend a new pick-up point, and suggest communicating with the customer to change the pick-up point.

[0210] After receiving confirmation information corresponding to the first prompt from the customer, the first recommended point is determined as the new pick-up point, and navigation planning is performed based on the first recommended point.

[0211] In one or more embodiments, the electronic device is an in-vehicle infotainment system;

[0212] Correspondingly, update module 63, based on the first recommended point, to update the boarding point, specifically for:

[0213] The first recommended point is set as the new pick-up point, and a second prompt message is sent to the customer terminal. The second prompt message is used to instruct the pick-up point to be updated to the first recommended point.

[0214] Navigation planning is performed in the vehicle's infotainment system based on the first recommended point.

[0215] In one or more embodiments, vehicle navigation data includes: pick-up route distance, time to reach the pick-up point, and navigation destination;

[0216] Correspondingly, module 62 determines whether there are any abnormal pick-up points in the pending order based on vehicle navigation data and preset anomaly judgment conditions. Specifically, it is used for:

[0217] When the vehicle navigation data meets the first preset condition, determine whether there is an abnormal pick-up point for the pending order based on the vehicle navigation data and the anomaly judgment condition.

[0218] The first preset condition includes at least one of the following: the distance of the pick-up route is greater than the first preset distance, the time to reach the pick-up point is greater than the first preset time, and the distance between the navigation endpoint and the starting point is greater than the second preset distance.

[0219] It should be noted that the division of the various modules in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical element, or they can be physically separated. Furthermore, these modules can be implemented entirely in software through processing element calls, or entirely in hardware. Alternatively, some modules can be implemented through processing element calls in software, while others can be implemented in hardware. Moreover, these modules can be integrated together or implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. During implementation, each step of the above method or each of the above modules can be completed through the integrated logic circuits in the hardware of the processor element or through software instructions.

[0220] As can be seen from the above, the device for correcting the boarding point provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0221] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 7 As shown, the electronic device provided in this embodiment includes at least one processor 71 and a memory 72.

[0222] Optionally, the electronic device also includes a communication component 73.

[0223] The processor 71, memory 72, and communication component 73 are connected via bus 74.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A method for correcting the boarding point, characterized in that, Applied to electronic devices, the method includes: Obtain vehicle navigation data during the passenger pick-up process for orders to be processed; Based on the vehicle navigation data and preset anomaly judgment conditions, it is determined whether the pending order has an abnormal pick-up point. The anomaly judgment conditions are determined based on the route characteristics in the first route, which is the route in the vehicle navigation route that is a first preset distance before reaching the navigation destination. If an abnormal boarding point exists, the boarding point is updated based on the starting point location corresponding to the order to be processed.

2. The method according to claim 1, characterized in that, The route features include at least one of the following: end link type, road class, internal road length, and road type; The anomaly detection conditions include at least one of the following: the terminal link type is indicated as a tunnel; the road grade and road type are indicated as expressway, elevated road, rapid transit, grade-separated interchange, and interchange; the internal road length is greater than a first preset length and there are pedestrian hotspots; the road type is a ramp and the route length is greater than a second preset length.

3. The method according to claim 1 or 2, characterized in that, The step of updating the boarding point based on the starting position corresponding to the order to be processed includes: In a preset recommended point library, at least one recommended point is determined within a first preset range centered on the starting point position. The recommended point library records different recommended points and the positions corresponding to each recommended point. Update the boarding point based on the at least one recommended point and the starting point location.

4. The method according to claim 3, characterized in that, The step of updating the boarding point based on the at least one recommended point and the starting point location includes: Among the at least one recommended point, determine the recommended point that is closest to the starting point; If the walking distance between the nearest recommended point and the starting point is less than the walking distance threshold, the nearest recommended point is determined as the first recommended point; If, based on the new vehicle navigation data constructed from the first recommended point and the anomaly judgment conditions, it is determined that the first recommended point does not have any anomalies, then the boarding point is updated according to the first recommended point.

5. The method according to claim 4, characterized in that, The electronic device is a user terminal; Accordingly, updating the boarding point based on the first recommended point includes: Based on the first recommended point, a first prompt message is generated on the user terminal. The first prompt message is used to notify the user that the pick-up point is abnormal, recommend a new pick-up point, and suggest communicating with the customer to change the pick-up point. After receiving the confirmation information corresponding to the first prompt information from the customer, the first recommended point is determined as the new pick-up point, and navigation planning is performed based on the first recommended point.

6. The method according to claim 4, characterized in that, The electronic device is a vehicle infotainment system; Accordingly, updating the boarding point based on the first recommended point includes: The first recommended point is determined as the new pick-up point, and a second prompt message is sent to the customer terminal, the second prompt message being used to instruct the pick-up point to be updated to the first recommended point; Navigation planning is performed in the vehicle system based on the first recommended point.

7. The method according to claim 1 or 2, characterized in that, The vehicle navigation data includes: the distance of the pick-up route, the time to reach the pick-up point, and the navigation destination; Accordingly, determining whether there is an abnormal pick-up point for the pending order based on the vehicle navigation data and preset anomaly judgment conditions includes: When the vehicle navigation data meets the first preset condition, the system determines whether the order to be processed has an abnormal pick-up point based on the vehicle navigation data and the anomaly judgment condition. The first preset condition includes at least one of the following: the distance of the pick-up route is greater than a first preset distance, the time to reach the pick-up point is greater than a first preset time, and the distance between the navigation endpoint and the starting point is greater than a second preset distance.

8. A device for correcting the loading point, characterized in that, Applied to electronic devices, the device includes: The acquisition module is used to acquire vehicle navigation data during the passenger pick-up process for orders to be processed; The determination module is used to determine whether there is an abnormal pick-up point in the pending order based on the vehicle navigation data and preset abnormal judgment conditions. The abnormal judgment conditions are determined based on the route characteristics in the first route, which is a route in the vehicle navigation route that is a first preset distance before reaching the navigation destination. The update module is used to update the boarding point based on the starting position corresponding to the order to be processed when the boarding point is abnormal.

9. A vehicle, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-7.

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

Images