Hitchhiking order recalling method and device, computer equipment and computer program product

Abstract

The invention is suitable for the technical field of hitchhiking, and provides a hitchhiking order recall method and device, computer equipment and a computer program product, and the method comprises the steps: obtaining a terminal position in a driving route and terminal time for reaching the terminal position, determining a recommended order based on the terminal position and the terminal time, and displaying the recommended order on a terminal interface. Therefore, the time and the operation complexity of finding orders after the vehicle owner finishes the travel are effectively reduced, and the user experience is improved.

Description

Technical Field

[0001] The present application belongs to the field of ride-sharing technology, and in particular, relates to a ride-sharing order recall method, apparatus, computer equipment and computer program product. Background Art

[0002] At present, carpooling has become a relatively common way of carpooling. Carpooling refers to a way of carpooling in which the car owner picks up passengers going the same way as the passenger when the car owner's route and direction are the same or similar to the passenger's route and direction. Among them, the existing methods of finding passengers going the same way are all based on the navigation route, that is, after the car owner provides the starting point and end point information, the navigation route is first calculated, and then the "passengers going the same way" are found along the navigation route. Among them, after the car owner arrives at the end point, he needs to re-issue the order recall request and perform the order search operation, which is cumbersome and time-consuming. Summary of the invention

[0003] The embodiments of the present application provide a ride-sharing order recall method, apparatus, computer equipment and computer program product, which can solve the technical problems in existing methods that require reissuing order recall requests and performing order search operations, which are cumbersome and time-consuming.

[0004] In a first aspect, an embodiment of the present application provides a method for recalling a ride-sharing order, comprising:

[0005] Obtaining the destination location in the driving route and the destination time of arriving at the destination location;

[0006] determining a recommended order based on the destination location and the destination time;

[0007] The recommended order is displayed on the terminal interface.

[0008] In a possible implementation manner of the first aspect, the method further includes:

[0009] The method further comprises:

[0010] Displaying an order viewing control on the terminal interface;

[0011] In response to a triggering operation on the order viewing control, an order tab page is displayed on the terminal interface; wherein the order tab page includes an order view;

[0012] The displaying of the recommended order on the terminal interface includes:

[0013] The recommended order is displayed in the order view of the order tab page.

[0014] In a possible implementation of the first aspect, the order tab page includes a city tab and a cross-city tab, the city tab corresponds to a city order view, and the cross-city tab corresponds to a cross-city order view; the recommended orders include city orders and cross-city orders;

[0015] The displaying of the recommended order in the order view of the order tab page includes:

[0016] Displaying the in-city order in the in-city order view;

[0017] The cross-city order is displayed in the cross-city order view.

[0018] In a possible implementation manner of the first aspect, the method further includes:

[0019] Determine the driving route type of the driving route based on the end point position and the starting point position of the driving route; wherein the driving route type includes an intra-city type and an inter-city type;

[0020] When the driving route type is the city type, the city order view is displayed on the terminal interface;

[0021] When the driving route type is the inter-city type, the inter-city order view is displayed on the terminal interface;

[0022] In response to a triggering operation on the intra-city tag or the inter-city tag, the currently displayed order view is switched.

[0023] In a possible implementation manner of the first aspect, the method further includes:

[0024] When it is detected that the currently displayed order view is a city order view, in response to the user's filtering operation on the recommended orders, a first filtered order is generated, and the first filtered order is displayed in the city order view;

[0025] When it is detected that the currently displayed order view is a cross-city order view, in response to the user's filtering operation on the recommended order, a second filtered order is generated, and the second filtered order is displayed in the cross-city order view;

[0026] The screening operation includes any combination of time screening, price screening, distance screening, destination screening, and riding mode screening.

[0027] In a possible implementation manner of the first aspect, determining the recommended order based on the destination location and the destination time includes:

[0028] Determine a recall area based on the end point location, and determine a recall time period based on the end point time;

[0029] The order recall is performed based on the recall area and the recall time period to obtain the recommended order; wherein the order recall includes intra-city order recall and inter-city order recall.

[0030] In a possible implementation manner of the first aspect, the method further includes:

[0031] Analyzing the recommended order based on the destination location and the starting location of the driving route to determine a return order;

[0032] The label of the return order is displayed on the terminal interface.

[0033] In a second aspect, an embodiment of the present application provides a ride-sharing order recall device, comprising:

[0034] An acquisition module, used to acquire a destination position in a driving route and a destination time of reaching the destination position;

[0035] A determination module, configured to determine a recommended order based on the destination location and the destination time;

[0036] A display module is used to display the recommended order on the terminal interface.

[0037] In a third aspect, an embodiment of the present application provides a computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method for recalling a ride-sharing order as described in any one of the first aspects above is implemented.

[0038] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method for recalling a ride-sharing order described in any one of the first aspects above is implemented.

[0039] In a fifth aspect, an embodiment of the present application provides a computer program product. When the computer program product runs on a computer device, the computer device executes the ride-sharing order recall method described in any one of the first aspects above.

[0040] Compared with the prior art, the embodiment of the present application has the following beneficial effects: when the car owner is driving, by obtaining the destination location and estimated arrival time (i.e., the destination time) in the car owner's driving route, the recommended order is determined using this information, and the recommended order is displayed on the terminal interface. Through the above operation, the car owner can browse and select orders in advance before reaching the destination or even while driving, without having to re-issue an order recall request and perform an order search operation after arriving, which effectively reduces the time and operation complexity of the car owner looking for orders after completing the trip, and improves the user experience.

[0041] It can be understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0043] Figure 1 It is a flowchart of a ride-sharing order recall method provided in an embodiment of the present application;

[0044] Figure 2 It is a flowchart of a method for recalling a ride-sharing order provided by another embodiment of the present application;

[0045] Figure 3-1 to Figure 3-6 is a schematic diagram of an order viewing control in an embodiment of the present application;

[0046] Figure 4-1 to Figure 4-2 is a schematic diagram of an order tab page in an embodiment of the present application;

[0047] Figure 5 It is a flowchart of a method for recalling a ride-sharing order provided by another embodiment of the present application;

[0048] Figure 6 It is a flowchart of a method for recalling a ride-sharing order provided by another embodiment of the present application;

[0049] Figure 7 It is a flowchart of a method for recalling a ride-sharing order provided in yet another embodiment of the present application;

[0050] Figure 8 It is a schematic diagram of order screening for recalling rideshare orders provided in an embodiment of the present application;

[0051] Fig. 9It is a schematic diagram of order screening for recalling rideshare orders provided in an embodiment of the present application;

[0052] Fig.10 It is a structural schematic diagram of a ride-sharing order recall device provided in an embodiment of the present application;

[0053] Fig.11 It is a schematic diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0054] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0055] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0056] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0057] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.

[0058] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0059] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0060] Hitchhiking service is a carpooling service, which means that the car owner picks up passengers who are traveling in the same or similar route and direction as himself to realize a way of shared travel. Among them, the existing methods of finding passengers along the way are all based on the navigation route, that is, after the car owner provides the starting point and end point information, the navigation route is calculated first, and then the "passengers along the way" are found along the navigation route. Among them, after the car owner arrives at the end point, he needs to re-issue the order recall request and perform the order search operation, which is cumbersome and time-consuming.

[0061] To solve the above problems, Figure 1 A schematic flowchart of a ride-sharing order recall method provided in one embodiment of the present application is shown.

[0062] S101, obtaining a destination position in a driving route and a destination time for reaching the destination position.

[0063] The navigation route is the optimal path calculated based on the map and navigation system. The driving route refers to the specific path or route taken by the vehicle during driving. The driving route is not limited to the path provided by the navigation system, but also includes any path selected by the owner during actual driving.

[0064] The final location is the destination of the last passenger. Specifically, the current ride modes of a ride-sharing car include exclusive mode and shared mode. When in exclusive mode, it corresponds to a single passenger, and the final location is the destination of the single passenger; when in shared mode, it may correspond to at least one passenger, and the final location is the destination of the last passenger.

[0065] The destination time indicates the estimated time of arrival at the destination location. For example, the destination time can be obtained using an online map service or a navigation application.

[0066] S102: Determine a recommended order based on the destination location and the destination time.

[0067] In the embodiment of the present application, the recall area is determined based on the destination location, and the recall time period is determined based on the destination time. Based on the order database of the ride-sharing platform, the passenger orders in the recall area and in the recall time period are queried to determine the recommended order.

[0068] Specifically, the recall area is determined with the end point as the dot and the preset length as the radius, and the recall time period is determined by expanding the preset time period backward with the end point as the time starting point. For example, the recall area is a circle with the end point as the center and a radius of 2 km, and the recall time period is a time period of 1 hour backward with the end point as the recall time point.

[0069] Among them, the above-mentioned radius length and preset time length can be preset fixed values ​​or dynamically adjusted.

[0070] Optionally, the above-mentioned recommended orders include return orders and / or non-return orders.

[0071] Among them, the recommended orders include return orders and / or non-return orders. Return orders refer to passenger orders that match the return route of the driver. Non-return orders refer to passenger orders that do not completely overlap with the destination of the driver's current trip, but are still within an acceptable range of travel, or passenger orders that do not go to the new destination.

[0072] In a possible implementation, order recall is performed based on the recall area and the recall time period to obtain the recommended order; wherein the order recall includes intra-city order recall and inter-city order recall.

[0073] In the embodiment of the present application, after the car owner touches the order viewing control, the order recall process will be immediately entered. In the order recall process, both the city order recall and the cross-city order recall will be carried out at the same time. The implementation process of the city order recall and the cross-city order recall is the same. The recall area is determined based on the terminal location, the recall time period is determined based on the terminal time, and the recommended order is determined based on the terminal location and the terminal time (the recommended order includes the city order and the cross-city order), and then the order list is presented in the corresponding order view.

[0074] S103, displaying the recommended order on a terminal interface.

[0075] Among them, the display of recommended orders can usually be realized in the following places, including but not limited to: application apps, navigation systems, vehicle systems, smart wearable devices, etc.

[0076] In the embodiment of the present application, when the owner is driving, the destination location and estimated arrival time (i.e., the destination time) in the owner's driving route are obtained, and the recommended orders are determined using this information, and the recommended orders are displayed on the terminal interface. Through the above operations, the owner can browse and select orders in advance before reaching the destination, or even while driving, without having to re-issue order recall requests and perform order search operations after arriving, effectively reducing the time and operation complexity of the owner looking for orders after completing the trip, and improving the user experience.

[0077] In one possible implementation, Figure 2 A schematic flowchart of a ride-sharing order recall method provided in yet another embodiment of the present application is shown.

[0078] S201, displaying an order viewing control on the terminal interface.

[0079] The order view control is a component in the user interface. It is an order view portal that provides users with the function of interacting with orders. Figure 3-1 , 3-2 The “view and check orders near the end point in advance” shown in 3-3, 3-4, 3-5 and 3-6 are order viewing controls.

[0080] Optionally, when the car owner provides ride-sharing service, the order viewing control can be displayed on the interface.

[0081] In the embodiments of the present application, Figure 3-1 , 3-2 and the exclusive mode shown in 3-3, when the passenger has confirmed to travel with you and is ready to pick up the passenger ( Figure 3-1 ) or, when the passenger has confirmed to travel with you and is leaving to pick you up ( Figure 3-2 ), or, while waiting for the passenger to confirm boarding ( Figure 3-2 ) scenario, the order viewing control "View orders near the destination in advance, go and view" will be displayed on the interface. Figure 3-4 and 3-5 The shared seat mode shown (there is only one order in this shared seat mode) is when the passenger has confirmed to travel with you and is ready to pick up the passenger ( Figure 3-4 ) or, when the passenger has confirmed to travel with you and is leaving to pick you up ( Figure 3-5 ) scenario, the order viewing control "View orders near the destination in advance, go and view" will be displayed on the interface. Figure 3-6 In the seat-sharing mode shown (in this seat-sharing mode, two orders have been combined, one order has been paid, and the other order has not been paid), when the passengers have confirmed their travel, the order viewing control "View orders near the destination in advance and go to check" will be displayed on the interface.

[0082] S202, in response to a triggering operation on the order viewing control, displaying an order tab page on the terminal interface; wherein the order tab page includes an order view.

[0083] The trigger operation refers to the behavior of the user interacting with the device by touching the screen. On a touch screen device, the user can perform operations through different touch gestures, including but not limited to: single click, double click, long press, etc.

[0084] The order tab page generally refers to a component in the terminal interface, and the recommended orders can be displayed in the order view of the order tab page.

[0085] On the order tab page, users are allowed to view different categories of order information by clicking or touching different tabs. When users click on different tabs, the page content will switch to the order list or details related to the tab accordingly, allowing users to quickly switch between different order views without leaving the current page or screen.

[0086] In a possible implementation, the order tab page includes a city tab and a cross-city tab, the city tab corresponds to a city order view, and the cross-city tab corresponds to a cross-city order view; the recommended orders include city orders and cross-city orders. The city orders are displayed in the city order view, and the cross-city orders are displayed in the cross-city order view.

[0087] The In-City Tag and the Cross-City Tag are both options in the Orders tab page. Users can click them to view the corresponding orders. The Orders view is a view in the Orders tab page that is specifically used to display order details. The In-City Tag is associated with the In-City Orders view. The Cross-City Tag is associated with the Cross-City Orders view.

[0088] In the embodiment of the present application, when the user (i.e. the car owner in the above text) interacts with the order viewing control (such as clicking the order viewing control), there should be corresponding feedback, such as jumping to the order interface, displaying recommended orders, etc. For details, please refer to Figure 4-1 and Figure 4-2 . When you click on the order view control "View orders near the end point in advance, go to view", if Figure 4-1 and Figure 4-2 As shown, the city label "city order" and the cross-city label "cross-city order" are displayed. Each label corresponds to its own view. The "city order" label corresponds to the city order view, and the "cross-city order" label corresponds to the cross-city order view. The city order view is used to display city orders, and the cross-city order view is used to display cross-city orders.

[0089] In the embodiment of the present application, through clear label classification (intra-city label and cross-city label), users can quickly find the order type of interest (intra-city order and cross-city order), which improves the efficiency of finding and processing orders and enhances the user experience. In addition, the order tab page provides an intuitive way to organize and browse different types of orders, and users can easily switch between different order types.

[0090] In one possible implementation, Figure 5 A schematic flowchart of a ride-sharing order recall method provided in yet another embodiment of the present application is shown.

[0091] S501, determining a driving route type of the driving route based on the end point position and the starting point position of the driving route; wherein the driving route type includes an intra-city type and an inter-city type.

[0092] The starting point is the starting point of the driving route, which may be the location where the driver starts driving, or the location where the driver picks up the first passenger.

[0093] Among them, it can be determined based on the end point location and the starting point location whether the two are located in the same city or administrative division. If they are located in the same city or administrative division, the driving route type is the urban type; if they are not located in the same city or administrative division, the driving route type is the cross-city type.

[0094] S502: When the driving route type is the city type, the city order view is displayed on the terminal interface.

[0095] S503: When the driving route type is the cross-city type, the cross-city order view is displayed on the terminal interface.

[0096] In the embodiment of the present application, when the driving route type is an inner-city type, the inner-city order view is displayed on the terminal interface, such as Figure 4-1 As shown; when the driving route type is cross-city type, the cross-city order view is displayed on the terminal interface, such as Figure 4-2 shown.

[0097] S504, in response to a triggering operation on the intra-city tag or the inter-city tag, switching the currently displayed order view.

[0098] In an embodiment of the present application, when a user clicks on different tags, the order view corresponding to the tag will be switched, so that the user can quickly switch between different order views without leaving the current page or screen, thereby improving the user experience.

[0099] In a possible implementation, the above S103 determines the recommended order based on the destination location and the destination time, specifically including:

[0100] Determine candidate orders based on the destination location and the destination time; filter and / or sort the candidate orders to obtain the recommended order.

[0101] In an embodiment of the present application, a recall area is first determined based on the destination location, and a recall time period is determined based on the destination time. Passenger orders in the recall area and in the recall time period are queried in the order database of the ride-sharing platform to determine candidate orders. Afterwards, the candidate orders are filtered and / or sorted to obtain recommended orders, thereby providing the car owner with the most suitable order selection.

[0102] Among them, the above sorting process usually involves multiple factors to ensure that car owners can see the orders they most want to accept first.

[0103] Here are some key factors that may be used for ranking, including but not limited to this.

[0104] Time matching: Considering the estimated departure time of the passenger's order and the driver's estimated arrival time, the orders with the best time match are displayed first.

[0105] Order distance: Considering the distance from the car owner to the passenger’s starting point, orders within a short distance may be prioritized.

[0106] Order Price: Consider the price of the order or what the passenger is willing to pay.

[0107] Historical order-taking behavior: Predict the owner’s preferences based on the owner’s historical order-taking behavior, and adjust the order sorting accordingly.

[0108] The sorting algorithm will take into account the above factors and use weighted scoring, machine learning and other methods to determine the final sorting results, that is, recommended orders.

[0109] In one possible implementation, Figure 6 A schematic flowchart of a ride-sharing order recall method provided in yet another embodiment of the present application is shown.

[0110] like Figure 6As shown, after the car owner receives the confirmation from the passenger (the passenger has confirmed to travel together or the passenger has paid), the order viewing control "View the orders near the destination in advance, go and view" is displayed. When the car owner touches the order viewing control, the order tab page will be displayed. In the process of displaying the order tab page, it is determined whether the car owner's route is within the city or across the city, so as to enter the corresponding order label and order view, and the orders near the destination will be displayed in the order view under the corresponding label. After the car owner touches the order viewing control, the order recall process will be entered immediately. In the order recall process, both city recall and cross-city recall will be carried out at the same time. The implementation process of city recall and cross-city recall is the same. The recall area is determined based on the destination location, the recall time period is determined based on the destination time, and the candidate orders are determined based on the destination location and the destination time. After that, the candidate orders are sorted to obtain recommended orders. Then the order list is presented in the corresponding order view. For example, when it is judged that the car owner's route is of the city type, the currently displayed order view is the city order view, and the city orders are presented in the city order view; when it is judged that the car owner's route is of the cross-city type, the currently displayed order view is the cross-city order view, and the cross-city orders are presented in the cross-city order view.

[0111] Optional, such as Figure 6 As shown, in the order recall process, the recommended order will also be analyzed based on the end point location and the starting point location of the driving route, a return order will be determined, and the return order label will be displayed on the terminal interface. Specifically: determine whether the order starting point is within the recall radius and whether the order end point is within the starting point radius of the owner's route. If the order starting point is within the recall radius and the order end point is within the starting point radius of the owner's route, then the order is a return order and a return order label will be placed on the corresponding order. Figure 4-1 and Figure 4-2 shown.

[0112] Optionally, the recommended orders are sorted as described above, such as Figure 4-1 and Figure 4-2 As shown, the return trip is prioritized at the top of the order list. By giving priority to the return trip, the driver does not need to drive back to the original departure point after completing the current order, which helps to reduce the empty mileage, improve the travel efficiency, and increase the acceptance rate of the return trip.

[0113] In one possible implementation, Figure 7 A schematic flowchart of a ride-sharing order recall method provided in yet another embodiment of the present application is shown.

[0114] S701, when it is detected that the currently displayed order view is a city order view, in response to the user's filtering operation on the recommended orders, a first filtered order is generated, and the first filtered order is displayed in the city order view.

[0115] The screening operation includes any combination of time screening, price screening, distance screening, destination screening, and riding mode screening.

[0116] In the embodiments of the present application, Figure 8 As shown, intelligent sorting can be performed based on any one of departure time, order price or pick-up distance, or destination filtering can be performed based on area, or advanced filtering can be performed based on any combination of departure time, price, pick-up distance and riding mode.

[0117] S702, when it is detected that the currently displayed order view is a cross-city order view, in response to the user's filtering operation on the recommended orders, a second filtered order is generated, and the second filtered order is displayed in the cross-city order view.

[0118] The screening operation includes any combination of time screening, price screening, distance screening, destination screening, and riding mode screening.

[0119] In the embodiments of the present application, Fig. 9 As shown, intelligent sorting can be performed based on any one of the departure time, order price or pick-up distance, or the destination city can be filtered based on the city. After the city filtering, further district and county filtering can be performed, or advanced filtering can be performed based on any combination of departure time, price, pick-up distance and riding mode.

[0120] In an embodiment of the present application, a first filtered order and a fourth candidate order are generated through flexible filtering operations on time, price, distance, destination, and riding mode, and these orders are displayed in the corresponding intra-city order view and cross-city order view. This can more accurately match the needs of car owners, reduce invalid browsing and selection, and improve the efficiency of order matching.

[0121] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0122] Corresponding to the ride-sharing order recall method described in the above embodiment, Fig.10 A structural block diagram of a ride-sharing order recall device provided in an embodiment of the present application is shown. For ease of explanation, only the parts related to the embodiment of the present application are shown.

[0123] Reference Fig.10 , the ride-sharing order recall device includes:

[0124] An acquisition module, used to acquire a destination position in a driving route and a destination time of reaching the destination position;

[0125] A determination module, configured to determine a recommended order based on the destination location and the destination time;

[0126] A display module is used to display the recommended order on the terminal interface.

[0127] In a possible implementation, the display module is used to:

[0128] Displaying an order viewing control on the terminal interface;

[0129] In response to a triggering operation on the order viewing control, an order tab page is displayed on the terminal interface; wherein the order tab page includes an order view;

[0130] The recommended order is displayed in the order view of the order tab page.

[0131] In a possible implementation, the order tab page includes a city tab and a cross-city tab, the city tab corresponds to a city order view, and the cross-city tab corresponds to a cross-city order view; the recommended orders include city orders and cross-city orders; the determination module is used to:

[0132] Displaying the in-city order in the in-city order view;

[0133] The cross-city order is displayed in the cross-city order view.

[0134] In a possible implementation, the ride-sharing order recall device further includes a route type determination module and a switching module;

[0135] A route type determination module, used to determine the driving route type of the driving route based on the end point position and the starting point position of the driving route; wherein the driving route type includes an intra-city type and an inter-city type;

[0136] A display module, for displaying the city order view on the terminal interface when the driving route type is the city type; and for displaying the cross-city order view on the terminal interface when the driving route type is the cross-city type;

[0137] The switching module is used to switch the currently displayed order view in response to a triggering operation on the intra-city tag or the inter-city tag.

[0138] In a possible implementation, the ride-sharing order recall device further includes a screening module;

[0139] A screening module, for generating a first screening order in response to a user's screening operation on the recommended order when it is detected that the currently displayed order view is an intra-city order view, and displaying the first screening order in the intra-city order view; for generating a second screening order in response to a user's screening operation on the recommended order when it is detected that the currently displayed order view is an inter-city order view, and displaying the second screening order in the inter-city order view;

[0140] The screening operation includes any combination of time screening, price screening, distance screening, destination screening, and riding mode screening.

[0141] In a possible implementation, a module is determined to:

[0142] Determine a recall area based on the end point location, and determine a recall time period based on the end point time;

[0143] The order recall is performed based on the recall area and the recall time period to obtain the recommended order; wherein the order recall includes intra-city order recall and inter-city order recall.

[0144] In a possible implementation, the ride-sharing order recall device further includes a return order module;

[0145] A return order module, configured to analyze the recommended order based on the destination location and the starting location of the driving route to determine a return order;

[0146] A display module is used to display the label of the return order on the terminal interface.

[0147] It should be noted that the information interaction, execution process and other contents between the above-mentioned modules are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0148] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0149] An embodiment of the present application also provides a computer device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, wherein the processor implements the steps in any of the above-mentioned method embodiments when executing the computer program.

[0150] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0151] An embodiment of the present application provides a computer program product. When the computer program product runs on a mobile terminal, the mobile terminal can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0152] If the integrated unit is implemented in the form of 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 present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium can at least include: any entity or device that can carry the computer program code to the camera / terminal device, recording medium, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, RandomAccess Memory), electric carrier signal, telecommunication signal and software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electric carrier signals and telecommunication signals.

[0153] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0154] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0155] In the embodiments provided in the present application, it should be understood that the disclosed devices / network equipment and methods can be implemented in other ways. For example, the device / network equipment embodiments described above are merely schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0157] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

[0158] Fig.11 This is a schematic diagram of the structure of a computer device provided in one embodiment of the present application. Fig.11 As shown, the computer device of this embodiment includes: at least one processor 20 ( Fig.11 Only one is shown), a memory 21, and a computer program 22 stored in the memory 21 and executable on the at least one processor 20, wherein the processor 20 implements the steps in any of the above-mentioned embodiments of the ride-sharing order recall method when executing the computer program 22.

[0159] The computer device may include, but is not limited to, a processor 20 and a memory 21. Those skilled in the art will appreciate that Fig.11 It is only an example of a computer device and does not constitute a limitation of the computer device. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, it may also include input and output devices, network access devices, etc.

[0160] The processor 20 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0161] In some embodiments, the memory 21 may be an internal storage unit of the computer device, such as a hard disk or memory of the computer device. In other embodiments, the memory 21 may also be an external storage device of the computer device, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the computer device. Further, the memory 21 may also include both an internal storage unit of the computer device and an external storage device. The memory 21 is used to store an operating system, an application program, a boot loader (BootLoader), data, and other programs, such as the program code of the computer program. The memory 21 may also be used to temporarily store data that has been output or is to be output.

[0162] The relevant user personal information that may be involved in the various embodiments of this application is strictly in accordance with the requirements of laws and regulations, following the principles of legality, legitimacy and necessity, based on the reasonable purposes of business scenarios, to process the personal information that users actively provide during the use of products / services or generated due to the use of products / services, as well as the personal information obtained with the user's authorization.

[0163] The user personal information processed by the applicant will vary depending on the specific product / service scenario, and shall be based on the specific scenario in which the user uses the product / service, which may involve the user's account information, device information, driving information, vehicle information or other related information. The applicant will treat the user's personal information and its processing with a high degree of diligence.

[0164] The Applicant attaches great importance to the security of user personal information and has adopted reasonable and feasible security protection measures that comply with industry standards to protect user information and prevent personal information from being accessed, disclosed, used, modified, damaged or lost without authorization.

Claims

1. A method for recalling a ride-sharing order, characterized in that: include: Obtaining the destination location in the driving route and the destination time of arriving at the destination location; determining a recommended order based on the destination location and the destination time; The recommended order is displayed on the terminal interface.

2. The method for recalling a rideshare order according to claim 1, characterized in that: The method further comprises: Displaying an order viewing control on the terminal interface; In response to a triggering operation on the order viewing control, an order tab page is displayed on the terminal interface; wherein the order tab page includes an order view; The displaying of the recommended order on the terminal interface includes: The recommended order is displayed in the order view of the order tab page.

3. The method for recalling a rideshare order according to claim 2, characterized in that: The order tab page includes an intra-city tab and an inter-city tab, wherein the intra-city tab corresponds to an intra-city order view, and the inter-city tab corresponds to an inter-city order view; The recommended orders include intra-city orders and inter-city orders; The displaying of the recommended order in the order view of the order tab page includes: Displaying the in-city order in the in-city order view; The cross-city order is displayed in the cross-city order view.

4. The method for recalling a rideshare order according to claim 3, characterized in that: The method further comprises: Determine the driving route type of the driving route based on the end point position and the starting point position of the driving route; wherein the driving route type includes an intra-city type and an inter-city type; When the driving route type is the city type, the city order view is displayed on the terminal interface; When the driving route type is the inter-city type, the inter-city order view is displayed on the terminal interface; In response to a triggering operation on the intra-city tag or the inter-city tag, the currently displayed order view is switched.

5. The method for recalling a rideshare order according to claim 3 or 4, characterized in that: The method further comprises: When it is detected that the currently displayed order view is a city order view, in response to the user's filtering operation on the recommended orders, a first filtered order is generated, and the first filtered order is displayed in the city order view; When it is detected that the currently displayed order view is a cross-city order view, in response to the user's filtering operation on the recommended order, a second filtered order is generated, and the second filtered order is displayed in the cross-city order view; The screening operation includes any combination of time screening, price screening, distance screening, destination screening, and riding mode screening.

6. The method for recalling a rideshare order according to any one of claims 1 to 3, characterized in that: The determining of the recommended order based on the destination location and the destination time includes: Determine a recall area based on the end point location, and determine a recall time period based on the end point time; The order recall is performed based on the recall area and the recall time period to obtain the recommended order; wherein the order recall includes intra-city order recall and inter-city order recall.

7. The method for recalling a rideshare order according to any one of claims 1 to 3, characterized in that: The method further comprises: Analyzing the recommended order based on the destination location and the starting location of the driving route to determine a return order; The label of the return order is displayed on the terminal interface.

8. A ride-sharing order recall device, characterized in that: include: An acquisition module, used to acquire a destination position in a driving route and a destination time of reaching the destination position; A determination module, configured to determine a recommended order based on the destination location and the destination time; A display module is used to display the recommended order on the terminal interface.

9. A computer device, characterized in that: The method comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method according to any one of claims 1 to 7 when executing the computer program.

10. A computer program product, characterized in that When the computer program product is executed on a computer device, the computer device is caused to execute the method according to any one of claims 1 to 7.

Images