Travel information display method and device, computer equipment and storage medium

Abstract

The invention relates to a travel information display method and device, computer equipment, a storage medium and a computer program product. The method comprises the steps of displaying a sharing element matched with a first car-hailing request under the condition that a travel object initiates a car-hailing event on a car-hailing page; in response to a request sharing event initiated to the accompanying object by the triggering sharing element, displaying a shared first car-hailing request on an interaction page with the accompanying object; in response to a trigger event of the accompanying object to the first car-hailing request, displaying a first response state of the first car-hailing request and a second response state of a second car-hailing request initiated by the accompanying object on the shared ordering page; wherein the first car-hailing request is a request generated for a car-hailing event; the first car-hailing request and the second car-hailing request are mutually exclusive requests with the same request content. By adopting the method, order cancelling caused by repeated order placing can be avoided while rapid order placing of the accompanying object is supported, and waste of online car-hailing transport capacity can be reduced.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, computer device, computer-readable storage medium, and computer program product for displaying travel information. Background Technology

[0002] With the rapid development of computer technology, ride-hailing services have emerged, greatly facilitating people's travel. Passengers can send ride requests to ride-hailing platforms, and drivers can respond to these requests and provide corresponding driving services.

[0003] In traditional multi-person travel scenarios, each traveler operates independently, sending their own ride-hailing request to the platform to increase the success rate of order acceptance. If multiple ride-hailing requests are responded to, generating multiple orders for the same route, only one order is retained, and the other travelers manually cancel the others. Using traditional technology, frequent order cancellations are common in multi-person travel scenarios, leading to a waste of ride-hailing capacity. Summary of the Invention

[0004] Therefore, it is necessary to provide a method, device, computer equipment, computer-readable storage medium, and computer program product for displaying travel information that can avoid the waste of ride-hailing capacity, in order to address the aforementioned technical problems.

[0005] Firstly, this application provides a method for displaying travel information, applied to a first terminal corresponding to a traveler. The method includes:

[0006] When the travel subject initiates a ride-hailing event on the ride-hailing page, a shared element matching the first ride-hailing request is displayed; the first ride-hailing request is a request generated in response to the ride-hailing event.

[0007] In response to the event that triggers the sharing element to initiate a sharing request to a peer object, the first ride-hailing request that has been shared is displayed on the interaction page with the peer object;

[0008] In response to the triggering event of the first ride-hailing request from the peer, the first response status of the first ride-hailing request and the second response status of the second ride-hailing request initiated by the peer are displayed on the shared order page; the first ride-hailing request and the second ride-hailing request are mutually exclusive requests with the same request content.

[0009] Secondly, this application also provides a travel information display device, applied to a first terminal corresponding to a traveler. The device includes:

[0010] The shared element display module is used to display shared elements matching the first ride-hailing request when the travel subject initiates a ride-hailing event on the ride-hailing page; the first ride-hailing request is a request generated in response to the ride-hailing event.

[0011] The request sharing module is used to respond to the request sharing event initiated by the sharing element to the peer object, and to display the first ride-hailing request to be shared on the interaction page with the peer object;

[0012] The response status display module is used to respond to the triggering event of the first ride request by the peer object and display the first response status of the first ride request and the second response status of the second ride request initiated by the peer object on the shared order page; the first ride request and the second ride request are mutually exclusive requests with the same request content.

[0013] Thirdly, this application also provides another method for displaying travel information, applied to a second terminal corresponding to a travel companion. The method includes:

[0014] In response to a request to share initiated by a sharing element triggered by a traveler, a first ride-hailing request to be shared is displayed on the interaction page with the traveler; the sharing element is displayed when the traveler initiates a ride-hailing event on the ride-hailing page; the first ride-hailing request is a request generated in response to the ride-hailing event.

[0015] In response to the triggering event of the peer's first ride request, the first response status of the first ride request and the second response status of the second ride request initiated by the peer are displayed on the shared order page; the first ride request and the second ride request are mutually exclusive requests with the same request content.

[0016] Fourthly, this application also provides another travel information display device, applied to a second terminal corresponding to a travel companion. The device includes:

[0017] The request display module is used to respond to a request sharing event initiated by a sharing element triggered by a traveler, and to display the first ride-hailing request to be shared on the interaction page with the traveler; the sharing element is displayed when the traveler initiates a ride-hailing event on the ride-hailing page; the first ride-hailing request is a request generated in response to the ride-hailing event;

[0018] The second status display module is used to respond to the triggering event of the peer object in response to the first ride request, and to display the first response status of the first ride request and the second response status of the second ride request initiated by the peer object on the shared order page; the first ride request and the second ride request are mutually exclusive requests with the same request content.

[0019] Fifthly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the steps of the above-described method.

[0020] Sixthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, implements the steps of the above-described method.

[0021] In a seventh aspect, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps of the above-described method.

[0022] The aforementioned travel information display method, device, computer equipment, computer-readable storage medium, and computer program product, when a traveler initiates a ride-hailing event on the ride-hailing page, display a shared element matching the first ride-hailing request generated in response to the ride-hailing event; in response to a request to share the shared element with a fellow traveler, the shared first ride-hailing request is displayed on the interaction page with the fellow traveler. Sharing ride-hailing requests from a traveler to a fellow traveler reduces the operational costs for the fellow traveler during the ride-hailing process. In response to the fellow traveler's trigger event for the first ride-hailing request, the first response status of the first ride-hailing request and the second response status of the second ride-hailing request initiated by the fellow traveler are displayed on the shared order page. The first and second ride-hailing requests are mutually exclusive requests with identical request content. This ensures that only one ride-hailing request is responded to through request content sharing and mutual exclusion, thus supporting quick order placement by fellow traveler while avoiding order cancellations due to duplicate orders, and reducing the waste of ride-hailing capacity to some extent. Attached Figure Description

[0023] Figure 1 This is an application environment diagram of the travel information display method in one embodiment;

[0024] Figure 2 This is a flowchart illustrating a travel information display method in one embodiment;

[0025] Figure 3 This is a schematic diagram illustrating how shared elements are displayed in one embodiment;

[0026] Figure 4 This is a schematic diagram illustrating the display method of shared elements in another embodiment;

[0027] Figure 5 This is a schematic diagram illustrating the interface changes during the first ride-sharing request process in one embodiment.

[0028] Figure 6 This is a schematic diagram illustrating the interface changes during the first ride-sharing request process in another embodiment;

[0029] Figure 7 This is a schematic diagram illustrating the interface changes before and after a peer object triggers the first ride-hailing request in one embodiment.

[0030] Figure 8 A schematic diagram illustrating the interface changes of the first and second terminals during the process of adding peer objects to a shared order in one embodiment.

[0031] Figure 9 This is a schematic diagram illustrating the interface changes before and after a driver accepts an order in one embodiment.

[0032] Figure 10 This is a schematic diagram illustrating the management logic of multiple peer orders in one embodiment;

[0033] Figure 11 This is a flowchart illustrating the travel information display method in another embodiment;

[0034] Figure 12 This is a schematic diagram illustrating the interface changes when a peer object triggers the first ride-hailing request in one embodiment.

[0035] Figure 13 A schematic diagram illustrating the interface changes when adding shared order placement to peer objects in one embodiment;

[0036] Figure 14 This is a schematic diagram illustrating the interface changes after a driver accepts an order in one embodiment.

[0037] Figure 15 This is a schematic diagram illustrating the interface changes under different circumstances after a travel object initiates a request for content change in one embodiment.

[0038] Figure 16 This is a flowchart illustrating the travel information display method in yet another embodiment;

[0039] Figure 17 This is a flowchart illustrating the travel information display method in another embodiment;

[0040] Figure 18 This is an interactive schematic diagram of a travel information display method in one embodiment;

[0041] Figure 19 This is a structural block diagram of a travel information display device in one embodiment;

[0042] Figure 20 This is a structural block diagram of the travel information display device in another embodiment;

[0043] Figure 21This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0044] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0045] The travel information display method provided in this application embodiment can be applied to, for example, Figure 1 In the application environment shown, both the first terminal 101 and the second terminal 102 can communicate with the server 103 through a communication network. This communication network can be a wired network or a wireless network. Therefore, the first terminal 101 and the server 103, as well as the second terminal 102 and the server 103, can be directly or indirectly connected via wired or wireless communication. For example, the first terminal 101 can be indirectly connected to the server 103 through a wireless access point, or the first terminal 101 can be directly connected to the server 103 through the Internet; this application does not impose any limitations on this.

[0046] The first terminal 101 and the second terminal 102 can be, but are not limited to, various desktop computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, and smart in-vehicle devices. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted devices. This embodiment can be applied to ride-hailing service scenarios involving multiple passengers. Specifically, the first terminal 101 can be the terminal held by the first passenger who initiates the ride-hailing request among the multiple passengers; the second terminal 102 can be the terminal held by other passengers (referred to as fellow passengers) among these multiple passengers. The first terminal 101 and the second terminal 102 are equipped with a client application for the ride-hailing service, which can be software, a webpage, a mini-program, etc.

[0047] Furthermore, server 103 can be a backend server providing ride-hailing services. Server 103 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. The data storage system can store the data that server 103 needs to process. The data storage system can be set up separately, integrated into server 103, or placed in the cloud or on other servers.

[0048] In the process of displaying travel information based on ride-hailing services, the traveler first initiates a ride-hailing event on the ride-hailing page 104 of the first terminal 101. The first terminal 101 then generates a first ride-hailing request in response to this event and displays a sharing element 105 matching the first ride-hailing request. The traveler can then trigger the sharing element 105 to initiate a request-to-share event with fellow travelers. The first terminal 101 can respond to this request-to-share event and display the shared first ride-hailing request 107 on the interaction page 106 with fellow travelers. Furthermore, the second terminal 102 can also respond to this request-to-share event and display the shared first ride-hailing request 107 on the interaction page 108 with the traveler. Fellow travelers can be, for example, "User 2" in 106 and "me" in 108, and the traveler can be, for example, "me" in 106 and "User 1" in 108. Finally, fellow travelers holding the second terminal 102 can initiate a second ride-hailing request by triggering the first ride-hailing request 107. In response to the triggering event, the first terminal 101 can display the first response status 110 of the first ride-hailing request and the second response status 111 of the second ride-hailing request on the shared order page 109. This response status could, for example, be... Figure 1 The "Calling a car" status indicates a waiting state. The first and second ride requests are mutually exclusive requests with identical content.

[0049] In one embodiment, such as Figure 2 As shown, a method for displaying travel information is provided, which is applied to a computer device. The computer device is used as an example. Figure 1 Taking the first terminal 101 corresponding to the travel object as an example, the travel information display method may include the following steps:

[0050] Step S202: If the traveler initiates a ride-hailing event on the ride-hailing page, display the shared element that matches the first ride-hailing request.

[0051] The first ride-hailing request is generated for a ride-hailing event initiated by the travel subject. The travel subject refers to the first person to initiate a ride-hailing request in a multi-person travel scenario. The ride-hailing page is the page where the user makes a ride-hailing reservation; specifically, this page can be the client interface of the ride-hailing client deployed on the first terminal. The user can specifically include both the travel subject and the travel companions. Travel companions refer to all users other than the first user to initiate the ride-hailing request (i.e., the travel subject) in a multi-person travel scenario. Shared elements refer to elements related to the function of sharing requested content. These shared elements can specifically be controls, buttons, or labels, etc. For example, such as... Figure 1As shown, shared element 105 can specifically be a "Call a Ride Together" control. The specific display location of the shared element is not unique; it can float on the map or be displayed separately outside the map area; no limitation is made here. For example... Figure 1 In the middle, shared element 105 is displayed floating in the lower left corner of map 112.

[0052] Specifically, travelers can set their travel information, such as origin, destination, time, and vehicle type, on the ride-hailing page and initiate a ride-hailing event by triggering a confirmation action for that information. The first terminal can then generate a first ride-hailing request for that event and display shared elements matching that request. In essence, the content of the first ride-hailing request corresponds to the ride-hailing information associated with the ride-hailing event.

[0053] In an optional embodiment, such as Figure 3 As shown in section 301, during the process of setting up ride-hailing information, the ride-hailing page may not display shared elements; such as... Figure 3 As shown in 302, when a traveler initiates a ride-hailing event by triggering a confirmation operation on the ride-hailing information, the first terminal can generate a first ride-hailing request for the ride-hailing event and display a shared element 303 matching the first ride-hailing request on the ride-hailing page. The confirmation operation on the ride-hailing information can be triggered by a "confirm" control 304. In some embodiments, the confirmation operation can also be triggered by an "order now" control; this is not limited here.

[0054] In an optional embodiment, such as Figure 4 As shown, during the process of setting up ride-hailing information, the ride-hailing page can display shared element 401, but the shared element 401 is in an untriggerable state. When the traveler initiates a ride-hailing event by triggering a confirmation operation on the ride-hailing information, the first terminal can generate a first ride-hailing request for the ride-hailing event and change the state of shared element 401 from an untriggerable state to a triggerable state, so that the traveler can initiate a request sharing event for the first ride-hailing request by triggering the shared element 401.

[0055] Step S204: In response to the request to share initiated by the shared element to the peer object, the first ride-hailing request to be shared is displayed on the interaction page with the peer object.

[0056] The interactive page refers to a page capable of interactive functionality. Specifically, this interactive page can be the application page of an interactive application mounted on the first terminal. This interactive application and the ride-hailing application can be integrated into the same client that has both interactive and ride-hailing functions, or they can be applications on different clients; this is not limited to these specific applications. These interactive applications include, but are not limited to, communication applications, social applications, entertainment applications, office applications, and resource interaction applications.

[0057] Specifically, a traveler can initiate a sharing request event by triggering a sharing element, and then share the first ride-hailing request with that travel companion through the interaction page with the companion. The first terminal can then respond to this sharing request event and display the shared first ride-hailing request on the interaction page with the travel companion. Furthermore, a traveler can trigger a sharing element to share the first ride-hailing request with one or more travel companions. The specific methods for sharing the first ride-hailing request with multiple travel companions can be either sharing it sequentially with each travel companion or sharing it simultaneously with multiple travel companions belonging to a group.

[0058] In an optional embodiment, the first terminal may, in response to a trigger event for a shared element, redirect to the application page of the interactive application associated with the ride-hailing application. If the traveler identifies a fellow traveler through this application page, an interaction page between the traveler and the fellow traveler is displayed, showing the shared first ride-hailing request. The displayed content may include, for example, a summary of the first ride-hailing request, a link, etc. The association between the ride-hailing application and the interactive application can mean that they belong to the same application (a mini-program); the ride-hailing application is a mini-program under the interactive application; the ride-hailing application provides multiple functional applications for the same client within the interactive application; or the ride-hailing application and the interactive application have pre-authorized each other through the traveler.

[0059] In an optional embodiment, such as Figure 5 As shown, the first terminal can respond to the trigger operation of the shared element 502 in the ride-hailing page 501 and jump to the shared order page 503; the shared order page 503 displays a shared control 504 for the first ride-hailing request; in response to the triggering of the shared control 504 to initiate a request to share with the peer object, the first ride-hailing request 506 to be shared is displayed on the interaction page 505 with the peer object.

[0060] Step S206: In response to the triggering event of the first ride request from the peer, display the first response status of the first ride request and the second response status of the second ride request initiated by the peer on the shared order page.

[0061] The first and second ride-hailing requests are mutually exclusive requests with identical content. Mutually exclusive requests mean that only one of them can be responded to. That is, if one request is responded to, the other will be cancelled. The response status refers to the state after a ride-hailing request is initiated. This response status can specifically include waiting for a response, responded to, and cancelled. Waiting for a response indicates that the ride-hailing request has been sent and is awaiting a driver's response (i.e., not accepted); responded to indicates that a driver has responded to the ride-hailing request (i.e., accepted); and cancelled indicates that the ride-hailing request has been cancelled.

[0062] Specifically, a travel companion can initiate a trigger event for the first ride-hailing request via a second terminal, allowing them to place a shared order. The first terminal can then interact with the server to determine the order status of the second terminal. If the travel companion initiates a second ride-hailing request via the second terminal with the same content as the first request, the shared order page will display the first response status of the first ride-hailing request and the second response status of the second ride-hailing request initiated by the travel companion.

[0063] In an optional embodiment, a return control is displayed on the interaction page with fellow travelers. Travelers can trigger this control to navigate to the shared ride order page and wait for fellow travelers to join. If a fellow traveler initiates a second ride request, the shared ride order page will display a second response status for that second request, indicating that the fellow traveler has joined the shared ride order.

[0064] It should be noted that when a traveler shares a first ride-hailing request with multiple fellow travelers, each traveler's individual second ride-hailing requests are also mutually exclusive. In other words, if any one of the first ride-hailing request or any of the multiple second ride-hailing requests is responded to, the other shared ride-hailing requests will be cancelled.

[0065] The aforementioned method for displaying travel information, when a traveler initiates a ride-hailing event on the ride-hailing page, displays a shared element matching the first ride-hailing request generated in response to the event. In response to a request to share the shared element with a fellow traveler, the shared first ride-hailing request is displayed on the interaction page with the fellow traveler. Sharing ride-hailing requests from a traveler to a fellow traveler reduces the operational costs for the fellow traveler during the ride-hailing process. In response to the fellow traveler's trigger event for the first ride-hailing request, the first response status of the first ride-hailing request and the second response status of the second ride-hailing request initiated by the fellow traveler are displayed on the shared order page. The first and second ride-hailing requests are mutually exclusive requests with identical content. This ensures that only one ride-hailing request is responded to through content sharing and mutual exclusion, thus supporting quick order placement for fellow traveler while avoiding order cancellations due to duplicate orders, thereby reducing the waste of ride-hailing capacity to some extent.

[0066] In one embodiment, in response to a shared request event initiated by a shared element to a peer object, the first shared ride request is displayed on the interaction page with the peer object, including: in response to a triggering operation on the shared element, redirecting to the shared order page; and in response to a shared request event initiated by a shared control to a peer object, displaying the first shared ride request on the interaction page with the peer object.

[0067] In this context, the shared control refers to the control related to the function of sharing requested content. Specifically, the shared element can be associated with the shared order page. By triggering the shared element, users can be redirected to the shared order page. That is, during the sharing process of a ride-hailing request, the traveler can trigger the shared element to jump from the ride-hailing page to the shared order page. This shared order page displays the shared control for the first ride-hailing request. The traveler can trigger this control to initiate a request to share the ride with fellow travelers, and then share the first ride-hailing request with those travelers through the interactive application. Thus, the first terminal can display the shared first ride-hailing request on the interaction page between the traveler and their fellow travelers.

[0068] For example, such as Figure 5 As shown, the first terminal can respond to a user's trigger operation on the shared element 502 in the ride-hailing page 501, and redirect to the shared order page 503. Optionally, the ride-hailing page 501 can also display information such as a map, vehicle type, estimated cost of the first ride-hailing request, and response status. Optionally, the shared order page 502 can display ride-hailing information such as origin and destination, as well as prompts for multiple people sharing an order. Figure 5As shown, the prompt message could be, for example, "During peak travel periods, multiple people are calling for a ride together; see who accepts the order first." Furthermore, the shared order page 503 can also display a shared control 504 for the first ride request. This shared control 504 carries the "Call a ride together" function prompt message, such as... Figure 5 The "Call a ride with a friend" option is used in the context of ride sharing. A traveler can trigger the sharing control 504 to initiate a sharing request event with their travel companion. The first terminal can then respond to this sharing request event, displaying the first shared ride request 506 on the interaction page 505 between the traveler and their travel companion.

[0069] In an optional embodiment, a traveler can trigger a sharing control to invoke an interactive application associated with the ride-hailing application, and share the first ride request with fellow travelers through that interactive application.

[0070] In an optional embodiment, the traveler can trigger a sharing control to navigate to an interactive application selection page and share the first ride request with fellow travelers through the selected target application.

[0071] Furthermore, after the sharing request is completed, the traveler can also trigger the sharing element to jump to the sharing order page to view the order status of the traveler and the response status of the traveler's order.

[0072] In the above embodiments, in response to the triggering operation for the shared element, the user is first redirected to the shared order page, and then a request to share event is initiated by triggering the shared control in the shared order page, which can improve the interactivity of the request to share process.

[0073] In one embodiment, in response to a request to share initiated by a shared control to a peer object, the first ride-hailing request to be shared is displayed on the interaction page with the peer object, including: in response to a triggering operation on the shared control, displaying at least one candidate interactive application; in response to a selection event for a target application in each interactive application, jumping to the service page of the target application; in response to a peer object confirmation event triggered on the service page, displaying the interaction page with the confirmed peer object; and displaying the first ride-hailing request to be shared on the interaction page.

[0074] Interactive applications refer to computer applications that enable information exchange. These interactive applications include, but are not limited to, communication applications, social applications, entertainment applications, office applications, and resource exchange applications.

[0075] Specifically, such as Figure 6As shown, the traveler can trigger the sharing control 601 to jump to the application selection page 602. This application selection page 602 displays application identifiers 603 for multiple interactive applications. The traveler can then select a target application from the interactive applications represented by each application identifier 603 by touching or clicking on the target identifier among them. This target application could be, for example, application C. Thus, the first terminal can respond to the selection event of the target application and jump to the service page 604 of that target application. The traveler can select a travel companion on this service page. Therefore, the first terminal can respond to the travel companion confirmation event and display the interaction page 605 between the traveler and the confirmed travel companion, displaying the shared first ride request. The interaction page can be overlaid on the service page or displayed separately; this is not limited here.

[0076] In the above embodiments, the interactive application used for the ride-sharing request is selected first, and then the fellow passengers are selected. This enables the sharing of request content across platforms, which helps to improve flexibility.

[0077] In one embodiment, the travel information display method further includes: in response to an object selection event triggered on the service page, determining the expected shared objects for the first ride-hailing request; and if the number of expected shared objects matches the vehicle type requested in the first ride-hailing request, triggering a ride-sharing object confirmation event for the first ride-hailing request.

[0078] Specifically, on the one hand, the first terminal can respond to a ride-hailing event initiated by a traveler on the ride-hailing page and obtain ride-hailing information used to generate the first ride-hailing request. As mentioned above, this ride-hailing information may include the origin, destination, time, vehicle type, etc. On the other hand, during the sharing process of the first ride-hailing request, the traveler can trigger an object selection event on the service page of the selected target application. Thus, the first terminal can respond to this object selection event and determine the desired sharing objects for the first ride-hailing request. Then, the first terminal matches the number of desired sharing objects with the vehicle type in the ride-hailing information. If the number of objects meets the load limit of the vehicle type requested in the first ride-hailing request, the first terminal can trigger a companion object confirmation event for the first ride-hailing request. If the number of objects does not meet the load limit of the vehicle type requested in the first ride-hailing request, the first terminal can output a message indicating that the number of people has exceeded the limit, prompting the traveler to reselect desired sharing objects or vehicle type.

[0079] In an optional embodiment, when a traveler selects a desired sharing vehicle for the first ride-hailing request, the first terminal can determine that the number of desired sharing vehicles meets the load limit if the number of such vehicles is less than the passenger capacity limit of the requested vehicle type. It can be understood that the passenger capacity limit of the requested vehicle type is equal to the vehicle type's maximum passenger capacity minus one.

[0080] In an optional embodiment, a traveler may select desired sharing partners multiple times. In this case, the load limit of the vehicle type requested in the first ride request can be updated based on the number of fellow travelers already in the sharing order. For example, the load limit could be that the number of desired sharing partners is less than the difference between the passenger capacity limit of the vehicle type requested in the first ride request and the number of fellow travelers. For instance, for a 5-seater vehicle, the number of desired sharing partners should be less than 4 when selecting desired sharing partners for the first time; if the number of fellow travelers already in the sharing order is 2, the number of desired sharing partners selected should be less than 2.

[0081] In the above embodiments, when the number of objects to be shared matches the vehicle type requested in the first ride-hailing request, a confirmation event for the ride-sharing objects in the first ride-hailing request is triggered. This can avoid the situation where the number of people placing shared orders exceeds the number of passengers that would otherwise be unable to meet the ride-hailing capacity, and it is beneficial to improve the scientific nature of the ride-hailing service process.

[0082] In an optional embodiment, in response to an object selection event triggered on the service page, determining the expected sharing object of the first ride-hailing request includes: in response to an object selection event triggered on the service page, determining the expected sharing group of the first ride-hailing request; and determining the group members in the expected sharing group other than the travel object as the expected sharing object of the first ride-hailing request.

[0083] Specifically, a traveler can choose at least one of a group or an individual to share their initial ride request. If the traveler chooses an individual, the first terminal can respond to the selection event and identify the selected individual as the desired sharing partner for the initial ride request. If the traveler chooses a group, the first terminal can respond to the selection event, identify the desired sharing group, and identify all group members other than the traveler as desired sharing partners for the initial ride request. It can be understood that if the traveler selects multiple desired sharing partners at once, the first terminal can trigger a confirmation event for the traveler's companions in the initial ride request if the number of these desired sharing partners meets the load limit; if the number of these desired sharing partners meets the load limit, a message indicating that the number of participants has exceeded the limit can be output.

[0084] In the above embodiments, when the first ride-hailing request is shared to a group, it can only be shared to groups with a number of members that meet the load limit. This can further ensure that the number of people sharing the order matches the requested vehicle type, which is conducive to further improving the scientific nature of the ride-hailing service process.

[0085] In one embodiment, the travel information display method further includes: determining a threshold N for the number of travel companions corresponding to the first ride-hailing request based on the vehicle type requested in the first ride-hailing request; and displaying placeholders for N travel companions to be added on the shared order page.

[0086] Where N is a positive integer. Placeholders are used to reserve a fixed space in a specific location, waiting for subsequent content to be filled and displayed. Specifically, the first terminal can determine the maximum number of passengers (M) of the vehicle type requested in the first ride-hailing request, and then determine the threshold number N of companions corresponding to the first ride-hailing request. Where N = M - 2. Then, on the shared order page, placeholders for N companions to be added are displayed.

[0087] For example, such as Figure 7 As shown, when the requested vehicle type in the first ride-hailing request is a 5-seater, the shared order page 701 can display three placeholder identifiers for potential ride-sharing participants, including placeholder identifiers 702, 703, and 704. Each placeholder identifier can include an image placeholder and a text placeholder. For example, placeholder identifier 702 includes an image placeholder 7021 and a text placeholder 7022. The image placeholder can be used to fill in the image of the ride-sharing participant joining the shared order; the text placeholder can be used to fill in the name of the ride-sharing participant joining the shared order. Further, as... Figure 7 As shown, both image placeholders and text placeholders can display preset images and preset text. The preset text could be, for example, "Waiting for friends to join".

[0088] In the above embodiments, on the shared order page, placeholder icons for potential ride-sharing participants are displayed, matching the number of participants in the first ride-hailing request. This reminds travelers to share ride-hailing requests according to vehicle type, which helps to further improve the scientific nature of the travel information display method.

[0089] In one embodiment, in response to a triggering event of a fellow traveler's request for a first ride, the first response status of the first ride request and the second response status of a second ride request initiated by the fellow traveler are displayed on the shared order page. This includes: in response to the triggering event of a fellow traveler's request for a first ride, replacing the placeholder identifier with the fellow traveler's identifier; displaying the first response status of the first ride request initiated by the traveler corresponding to the traveler's identifier; and displaying the second response status of the second ride request initiated by the fellow traveler corresponding to the fellow traveler's identifier.

[0090] Among them, the "fellow traveler identifier" refers to identification information that can characterize a fellow traveler; the "traveler identifier" refers to identification information that can characterize a traveler. The specific forms of the fellow traveler identifier and the traveler identifier are not unique; for example, they may include at least one of images or text. Figure 7 In this context, the travel object identifier may include the travel object image 7051 and the travel object name 7052.

[0091] Specifically, in addition to placeholder identifiers for passengers to be added, the shared order page can also display the traveler identifier of the passenger and, corresponding to that traveler identifier, show the first response status of the first ride request initiated by the passenger. For example, as shown... Figure 7 As shown, the travel object identifier may include a travel object image 7051 and a travel object name 7052, and the first response state may be a waiting response state represented by the text "Calling a car...".

[0092] Furthermore, when a fellow traveler initiates a trigger event for the first ride-hailing request, the first terminal can respond to the trigger event by replacing one of the placeholder identifiers with the fellow traveler's identifier. Then, when the traveler initiates a second ride-hailing request, the terminal can display a second response status for the second ride-hailing request corresponding to the fellow traveler's identifier. For example, as shown... Figure 7 As shown, when a ride-hailing request is triggered by a fellow traveler, the placeholder identifier 702 on the shared order page 701 can be replaced with a fellow traveler identifier 705, and corresponding to this identifier 705, the second response status of the second ride-hailing request initiated by the fellow traveler can be displayed. This second response status could, for example, be... Figure 7 The text "Calling a car..." indicates the waiting status for a response.

[0093] It should be noted that the second ride request can be initiated automatically when the first ride request is triggered by the same person in the same group, or it can be initiated through further operations after the first ride request is triggered. If the second ride request needs to be initiated manually, a "Waiting for Order" status message can be displayed on the shared order page, corresponding to the same person's identifier, before the person represented by that identifier initiates the second ride request.

[0094] Furthermore, the relative display positions of the travel companion identifier and the companion identifier on the shared order page are not unique. For example, they could be as follows: Figure 7As shown, different object identifiers can be arranged in a top-to-bottom order, with the travel object identifier displayed at the top, and the companion object identifiers displayed sequentially from top to bottom according to the time when each companion object triggered its first ride-hailing request. That is, when multiple companion objects trigger their first ride-hailing requests, the placeholder identifiers are replaced sequentially from top to bottom. In some other embodiments, the different object identifiers can also be arranged from left to right, or in a circular, radial, or other arrangement. In short, this embodiment does not limit the relative display position of the different object identifiers.

[0095] In the above embodiments, in response to the triggering event of the first ride-hailing request from the travel companion, the placeholder identifier is replaced with the travel companion identifier, corresponding to the traveler's traveler identifier, to display the first response status of the first ride-hailing request initiated by the traveler, and corresponding to the travel companion identifier, to display the second response status of the second ride-hailing request initiated by the travel companion. This allows the traveler to quickly understand the ride-hailing status and improves interaction efficiency.

[0096] In an optional embodiment, corresponding to the peer object identifier, displaying a second response status for the second ride-hailing request initiated by the peer object includes: displaying status information indicating waiting to place an order corresponding to the peer object identifier; and in response to the peer object's confirmation event regarding the request content, canceling the display of status information and displaying the second response status for the second ride-hailing request initiated by the peer object.

[0097] As mentioned earlier, the second ride-hailing request can be initiated automatically if the first ride-hailing request is triggered by a fellow traveler, or it can be manually initiated by the fellow traveler after the first ride-hailing request has been triggered. In the case of manual initiation, the first terminal can display a status indicating a pending order status, corresponding to the fellow traveler's identifier, after the fellow traveler triggers the first ride-hailing request but before initiating the second ride-hailing request. If the fellow traveler triggers a confirmation event for the content of the first response request, the second ride-hailing request is initiated. At this time, the first terminal can respond to the confirmation event by canceling the display of the pending order status information and, corresponding to the fellow traveler's identifier, displaying the second response status of the second ride-hailing request initiated by that fellow traveler.

[0098] For example, such as Figure 8 As shown, when a fellow traveler triggers the first ride-hailing request through the interaction page 801 of the second terminal, both the first and second terminals' shared order pages can correspond to the traveler's identifier "User 2" and display the status information 803 indicating "waiting to place an order". Here, 8021 is the shared order page displayed on the first terminal, and 8022 is the shared order page displayed on the second terminal. Figure 8In this context, the first terminal and the second terminal can be distinguished by the perspective identifier "I" carried by the object identifier. For example, if "User 1" carries the perspective identifier "I", it corresponds to the first terminal; if "User 2" carries the perspective identifier "I", it corresponds to the second terminal. If the same object further triggers a confirmation event for the request content of the first response request, see [link to relevant documentation]. Figure 8 In the shared order page, 8031 ​​and 8032 can cancel the display of the status information representing "waiting for order" and, corresponding to the peer object identifier "User 2", display the second response status "calling a car" for the second ride request initiated by that peer object.

[0099] In the above embodiments, by displaying changes in status information, the operational status of fellow travelers can be accurately expressed, which can further improve the accuracy of the displayed travel information and enhance the interactive experience.

[0100] In one embodiment, the travel information display method further includes: in response to a response event to a target request in the first ride-hailing request and the second ride-hailing request, updating the response status of the target request from a waiting response status to a responded status; identifying non-target requests other than the target request in the first ride-hailing request and the second ride-hailing request; and updating the response status of the non-target requests from a waiting response status to a canceled status.

[0101] Specifically, the first ride-hailing request and the second ride-hailing request are mutually exclusive. The first terminal can respond to the response event of the target request in the first and second ride-hailing requests, updating the response status of the target request from a pending response state to a responded state. For example... Figure 9 In this scenario, the second ride-hailing request initiated by "User 2" changes from a "waiting for response" status (representing "hailing a ride") to a "responded" status (representing "driver has accepted the order"). In this situation, the first terminal can also identify non-target requests (other than the target request) in the first and second ride-hailing requests and update the response status of the non-target requests from a "waiting for response" status to a "cancelled" status. For example... Figure 9 If the first ride request initiated by "User 1" is a non-target request, then the first ride request will change from the waiting response status represented by "Calling a car" to the cancellation status represented by "Order cancelled".

[0102] It is understandable that when multiple users initiate second ride-hailing requests corresponding to the first ride-hailing request, when the target request is answered, multiple non-target requests will be canceled. For example, such as... Figure 10As shown, the ride-hailing request initiated by "User 1" is "Order 1", the ride-hailing request initiated by "User 2" is "Order 2", the ride-hailing request initiated by "User 3" is "Order 3", and the ride-hailing request initiated by "User 4" is "Order 4". These four ride-hailing requests include one first ride-hailing request and three second ride-hailing requests. These ride-hailing requests can be managed in groups. That is, as shown... Figure 10 As shown, a "ride-hailing group" containing "order 1" to "order 4" can be created. If an order in the group is successfully accepted (i.e. answered), other orders in the group can be cancelled; if no orders in the group are answered, the call continues.

[0103] In the above embodiments, when there is a target request that is answered in the first ride-hailing request and the second ride-hailing request, other non-target requests other than the target request are cancelled. This can further ensure that only one of the multiple ride-hailing requests placed by fellow passengers is responded to, which can further avoid order cancellations caused by duplicate orders and help to further reduce the waste of ride-hailing capacity.

[0104] In one embodiment, the travel information display method further includes: when a fellow traveler initiates a request to share an event with a third party, and the third party triggers a second ride-hailing request, displaying the third response status of the third ride-hailing request initiated by the third party on the shared order page.

[0105] In this application, the content of the third ride-hailing request is identical to that of the second ride-hailing request, and any two of the first, second, and third ride-hailing requests are mutually exclusive. Specifically, this application also supports a travel companion actively inviting a third party as a new travel companion. The travel companion can initiate a sharing request event to the third party by triggering a sharing element displayed on the ride-hailing page of the second terminal. The second terminal can then respond to this sharing request event by displaying the shared second ride-hailing request on the interaction page between the travel companion and the third party. When a third party triggers a second ride-hailing request, the shared order page of the first and second terminals can further display the third response status of the third ride-hailing request initiated by the third party. Furthermore, the specific method by which a travel companion initiates a sharing request event to a third party is the same as the method by which a traveler initiates a sharing request event to a travel companion in the above embodiment; the specific method by which a third party triggers a second ride-hailing request is the same as the method by which a travel companion triggers a first ride-hailing request in the above embodiment.

[0106] In the above embodiments, it is supported that a third party can be invited as a new travel companion by sharing a second ride request, which can improve the flexibility of the order processing process for multiple people traveling together.

[0107] It should be noted that after a ride request is initiated, modifications to the request content are supported. Specifically, the person making the first ride request can initiate changes to the request content, or a fellow traveler can initiate changes to the request content for a second ride request, thus modifying the request content.

[0108] In one embodiment, the travel information display method further includes: displaying the changed content on the ride-hailing page in response to a request content change event for the first ride-hailing request; and updating the request content of the first ride-hailing request and the second ride-hailing request in response to a confirmation operation on the changed content.

[0109] The changed content may include at least one of the following: time, vehicle type, origin, or destination. Specifically, a traveler can initiate a request content change event for a first ride-hailing request through a first terminal, and the first terminal can respond to this request content change event by displaying the changed content on the ride-hailing page. Optionally, a request content change entry can be displayed on the ride-hailing page, allowing the traveler to initiate a request content change event through this entry; alternatively, such as... Figure 1 As shown, the request content can be displayed on the ride-hailing page, allowing the passenger to initiate a request content change event by triggering the displayed request content. The method of triggering the request content can be clicking, touching, or swiping.

[0110] Furthermore, regarding the displayed changes, the travel recipient can be further modified, or a confirmation operation can be performed. The first terminal can respond to the confirmation operation regarding the changed content by updating the request content of both the first and second ride-hailing requests.

[0111] In one possible implementation, if the traveler initiates a confirmation operation for the changed content, the request content of the first ride-hailing request and the second ride-hailing request can be updated synchronously without the traveler's approval.

[0112] In one possible implementation, when a traveler initiates a confirmation request for modified content, the traveler's approval is required before the requested content can be updated. Specifically, when a traveler initiates a confirmation request for modified content, the first terminal can send a change notification message to the second terminal via the server to remind the traveler to check the modified content. Then, the first terminal can respond to the traveler's confirmation event for the modified content and simultaneously update the request content of both the first and second ride-hailing requests. If the traveler refuses the change, that traveler can be removed from the first ride-hailing request. In this case, the first terminal can respond to the traveler's refusal event for the modified content by removing the second response status of the second ride-hailing request from the shared order page. Furthermore, the traveler's traveler identifier on the shared order page can be restored to a placeholder identifier to allow for the addition of other traveler traveler later.

[0113] Optionally, when there are multiple travel companions initiating a second ride request, the request content can be updated only after all travel companions confirm the changes; alternatively, if none of the travel companions confirm, the travel companion can leave, and multiple travel companions can continue to share the order as travel partners. In this case, the first travel companion to join will become the new travel companion. If some travel companions do not confirm, the unconfirmed travel companions will leave the shared order, and their information will be removed from the shared order page. This information may specifically include the travel companion's identifier and the second response status of the second ride request initiated by the travel companion. Similarly, the travel companion's identifier on the shared order page can be further restored to a placeholder identifier to allow for the addition of other travel companions later.

[0114] In the above embodiments, the ability for travelers to proactively change their request content not only addresses the issue of incorrect request content during the initial order but also improves the success rate of booking a ride when ride-hailing capacity is tight, thereby further enhancing flexibility.

[0115] In one embodiment, the travel information display method further includes: displaying a change notification message in response to a change event in the request content of the second ride-hailing request from a fellow traveler; and updating the request content of the first ride-hailing request and the second ride-hailing request in response to a confirmation operation on the change notification message.

[0116] In practical applications, a travel companion can also initiate a request content modification event for a second ride-hailing request. When a travel companion initiates a request content modification event, the traveler's approval is required before the request content can be updated. Specifically, after the travel companion confirms the modified content, the second terminal can send a change notification message to the first terminal through the server to remind the traveler to view the updated content. This change notification message can be displayed via instant messaging, a pop-up window, or a dialog box; the method is not limited here.

[0117] If the traveler confirms the change notification, it means they accept the changed content, and the first terminal can simultaneously update the request content of both the first and second ride-hailing requests. If the traveler refuses the change, the traveler can be removed from the first ride-hailing request. In this case, the first terminal can respond to the traveler's refusal of the change notification by canceling the display of the second response status of the second ride-hailing request on the shared order page. Furthermore, the traveler's traveler identifier on the shared order page can be restored to a placeholder identifier for later addition of other traveler ...

[0118] In the above embodiments, supporting peers to actively change the request content can not only deal with the situation where the request content is incorrect when placing an order for the first time, but also improve the success rate of booking a ride by adjusting the request content when the ride-hailing capacity is tight, which is conducive to further improving flexibility.

[0119] In one embodiment, such as Figure 11 As shown, this application also provides another method for displaying travel information, applied to a computer device. Taking this computer device as an example... Figure 1 Taking the second terminal 102 corresponding to the travel companion as an example, the travel information display method may include the following steps:

[0120] In step S1102, in response to the request sharing event initiated by the sharing element triggered by the travel object, the first ride-hailing request to be shared is displayed on the interaction page with the travel object.

[0121] Among them, the shared element is displayed when the traveler initiates a ride-hailing event on the ride-hailing page; the first ride-hailing request is a request generated in response to the ride-hailing event.

[0122] Specifically, a traveler can initiate a ride-hailing event through a ride-hailing page on a first device. In this case, the ride-hailing page on the first device will display a sharing element that matches the initial ride-hailing request. Thus, the traveler can trigger this sharing element to initiate a sharing request event with fellow travelers. The second device held by the fellow travelers can respond to this sharing request event and display the shared initial ride-hailing request on the interaction page with the traveler. For example, as shown... Figure 12 As shown, the interactive page 1201 of the second terminal displays the first ride-hailing request 1202 shared by a travel subject through the first terminal.

[0123] Step S1104: In response to the triggering event of the peer object for the first ride request, display the first response status of the first ride request and the second response status of the second ride request initiated by the peer object on the shared order page.

[0124] In this system, the first and second ride-hailing requests are mutually exclusive requests with identical content. Specifically, a fellow traveler can initiate a trigger event for the first ride-hailing request, allowing them to place a shared ride order. In this scenario, the fellow traveler will then initiate a second ride-hailing request with the same content as the first. Therefore, the second terminal can display the first response status of the first ride-hailing request and the second response status of the second ride-hailing request initiated by the fellow traveler on the shared order page. Furthermore, the second ride-hailing request can be initiated automatically when the fellow traveler triggers the first ride-hailing request, or it can be initiated after the fellow traveler triggers the first ride-hailing request through further operations; this is not limited here. In short, as... Figure 12 As shown, when a fellow traveler initiates a second ride-hailing request, the second terminal can display the first response status 1204 of the first ride-hailing request and the second response status 1205 of the second ride-hailing request initiated by the fellow traveler on the shared order page 1203.

[0125] The aforementioned method for displaying travel information, when a traveler initiates a ride-hailing event on the ride-hailing page, displays a shared element matching the first ride-hailing request generated in response to the event. In response to a request to share the shared element with a fellow traveler, the shared first ride-hailing request is displayed on the interaction page with the fellow traveler. Sharing ride-hailing requests from a traveler to a fellow traveler reduces the operational costs for the fellow traveler during the ride-hailing process. In response to the fellow traveler's trigger event for the first ride-hailing request, the first response status of the first ride-hailing request and the second response status of the second ride-hailing request initiated by the fellow traveler are displayed on the shared order page. The first and second ride-hailing requests are mutually exclusive requests with identical content. This ensures that only one ride-hailing request is responded to through content sharing and mutual exclusion, thus supporting quick order placement for fellow traveler while avoiding order cancellations due to duplicate orders, thereby reducing the waste of ride-hailing capacity to some extent.

[0126] In one embodiment, in response to a triggering event for a first ride-hailing request, displaying a first response status for the first ride-hailing request and a second response status for a second ride-hailing request initiated by a fellow traveler on the shared order page includes: in response to a triggering event for the first ride-hailing request, displaying the request content of the first ride-hailing request on the shared order page; in response to a confirmation event for the request content, initiating a second ride-hailing request; and displaying the first response status of the first ride-hailing request and the second response status of the second ride-hailing request initiated by a fellow traveler on the shared order page.

[0127] As mentioned earlier, the second ride request can be initiated automatically when the first ride request is triggered by the same user, or it can be initiated through further operations after the first ride request is triggered. In cases where the second ride request needs to be initiated manually, such as... Figure 13 As shown, a fellow traveler can initiate a trigger event for the first ride-hailing request 1302 displayed on the interactive page 1301 by clicking or touching it. The second terminal can then respond to this trigger event and redirect to the shared order page 1303, where the request content of the first ride-hailing request is displayed. This request content may include, for example, at least one of the following: origin, terminal, time, or vehicle type. Further, as... Figure 13 As shown, the shared order page 1303 can also correspond to a peer object identifier, and display the status information "waiting to place an order" before the peer object represented by the peer object identifier initiates a second ride request.

[0128] The other party can initiate a confirmation event for the displayed request content, and the second terminal can then respond to this confirmation event by initiating a second ride-hailing request. For example, such as... Figure 13As shown, the shared order page 1303 can also display an "Order Now" control 1304, which allows peers to initiate a confirmation event for the requested content by clicking the "Order Now" control 1304.

[0129] In an optional embodiment, such as Figure 13 As shown, the second terminal can initiate a second ride-hailing request in response to a confirmation event for the requested content and redirect to the ride-hailing page 1305. Furthermore, this ride-hailing page can display shared elements matching the first ride-hailing request. These shared elements could, for example, be... Figure 13 The "Call a Ride Together" control 1306 is used in the middle. Thus, the second terminal can respond to the trigger operation for the shared element, jump to the shared order page 1307, and display the first response status of the first ride request and the second response status of the second ride request initiated by the travel companion on the shared order page 1307.

[0130] Understandable. Figure 13 The shared order pages 1303 and 1307 are shared order pages displayed on the second terminal at different times. The difference lies in that shared order page 1303 is the page displayed before initiating the second ride-hailing request. At this time, corresponding to the peer identifier, it displays the "Waiting to Place Order" status information, and also displays an "Order Now" control 1304 so that the peer can initiate the second ride-hailing request by triggering this control. Shared order page 1307 is the page displayed after initiating the second ride-hailing request. At this time, corresponding to the peer identifier, it displays the second response status of the second ride-hailing request, such as... Figure 13 The "Calling a Ride" status indicates a waiting response state. Furthermore, the shared order page 1307 can also display a "Back" control 1308, allowing fellow travelers to return to the ride-hailing page 1305 by triggering this control. Additionally, if other travelers can be added, the shared order page 1307 can also display a "Call a Ride with Friends" control (i.e., a sharing control), allowing fellow travelers to invite more people by triggering this control.

[0131] In an optional embodiment, such as Figure 14As shown, the second terminal can automatically redirect to the ride-hailing page 1401 in response to the driver's reply to the second ride-hailing request. This ride-hailing page can display information about the ride-hailing vehicle that has responded to the second ride-hailing request. This information may include the vehicle's license plate, vehicle type, location, driver contact information, etc. In this case, the mutually exclusive request for the second ride-hailing request will be cancelled. Correspondingly, on the shared order page 1402, the second response status of the second ride-hailing request will be updated from the waiting response status in 1307 to the "driver has accepted the order" status, indicating a responded state; the first response status of the first ride-hailing request will be updated from the waiting response status in 1307 to the "order has been cancelled" status, indicating a cancelled state.

[0132] In the above embodiments, the second ride request is initiated only after the travel companion confirms the content of the first ride request. This ensures that the request content matches the travel companion's travel needs and helps improve the service quality of ride-hailing services.

[0133] It should be noted that after a ride request is initiated, modifications to the request content are supported. Specifically, the person making the first ride request can initiate changes to the request content, or a fellow traveler can initiate changes to the request content for a second ride request, thus modifying the request content.

[0134] In one embodiment, the travel information display method further includes: displaying a change notification message in response to a change event in the request content of the first ride-hailing request by the travel subject; and updating the request content of the first ride-hailing request and the second ride-hailing request in response to a confirmation event of the change notification message.

[0135] Specifically, when a travel companion requests a change to the content, the first terminal can send a change notification message to the second terminal via the server to remind the travel companion to view the updated content. The second terminal can then respond to this content change event by displaying the change notification message. This notification message can be displayed via instant messaging, a pop-up window, or a dialog box; there is no specific limitation on this method.

[0136] If a fellow traveler initiates a confirmation event regarding the changed content, it indicates that the traveler agrees to the changes. The second terminal can then respond to this confirmation event and simultaneously update the request content of both the first and second ride-hailing requests. If the traveler refuses the changes, they can be removed from the first ride-hailing request. In this case, the first terminal can respond to the traveler's refusal event regarding the changed content by canceling the display of the second response status for the second ride-hailing request on the shared order page. Furthermore, the traveler's identifier on the shared order page can be restored to a placeholder identifier to allow for the addition of other traveler traveler later.

[0137] In the above embodiments, when the traveler actively changes the request content, confirmation from the travel companion is required. This can further ensure that the ride-hailing request placed through the shared booking system can match the traveler's travel needs, thereby improving flexibility while ensuring the service quality of the ride-hailing service.

[0138] In one embodiment, the number of travel companions is multiple. In this embodiment, updating the request content of the first ride-hailing request and the second ride-hailing request in response to a confirmation event for the change notification includes: updating the request content of the first ride-hailing request and each of the second ride-hailing requests in response to a confirmation event for the change notification from each travel companion. The travel information display method further includes: in response to a rejection event for the change notification from each travel companion, canceling the display of the first response status of the first ride-hailing request on the shared order page.

[0139] Specifically, when multiple people are initiating a second ride-hailing request, the request content can be updated only after all people have confirmed the changes; alternatively, if none of the people in the request have confirmed, the first person to join can leave, and multiple people can continue to share the ride as fellow travelers. In this case, the first person to join will become the new person in the ride-hailing request. Furthermore, the travel-hailing identifier on the shared order page can be reset to a placeholder identifier to allow for the addition of other people in the ride-hailing request later.

[0140] For example, consider a scenario where "User 1" is the travel companion, and "User 2," "User 3," and "User 4" are the passengers. If the content change event initiated by "User 1" is confirmed by all passengers, the request content of the first ride-hailing request and each of the second ride-hailing requests will be updated simultaneously. Figure 15 As shown, the requested changes could be, for example, the destination, specifically changing location B in 1501 to location C in 1502. If the content change event initiated by "User 1" is rejected by all fellow travelers, then "User 1" can be removed, and "User 2," "User 3," and "User 4" can continue to share the order as fellow travelers. In this case, the first fellow traveler to join (e.g., "User 2") will become the new travel companion. Figure 15 As shown in page 1503, "User 2" will replace "User 1" as the new travel companion. "User 3" and "User 4" will continue to share the order as "User 1's" travel companions. Since "User 1" has exited, a placeholder can be restored so that other travel companions can be added later. At the same time, the shared order page 1503 can also display the sharing control 1504 for "Call a car with friends," so that "User 2," as the travel companion, can continue to invite other travel companions to join.

[0141] In the above embodiments, if there are multiple travel companions, and all of them refuse to accept the traveler's changes to the requested content, the traveler will exit, and multiple travel companions will continue to share the order as fellow travelers, which can further improve the flexibility of ride-hailing services.

[0142] In one embodiment, the travel information display method further includes: displaying the changed content on the ride-hailing page in response to a request content change event for the second ride-hailing request; and updating the request content of the first ride-hailing request and the second ride-hailing request in response to a confirmation event by the travel subject regarding the changed content.

[0143] In practical applications, a travel companion can also initiate a request content change event for a second ride-hailing request. When a travel companion initiates a request content change event, the traveler's approval is required before the request content can be updated. Specifically, after the travel companion confirms the changed content, the second terminal can display the changed content on the ride-hailing page and simultaneously send a change notification message to the first terminal via the server to remind the traveler to view the changed content. This change notification message can be displayed via instant messaging, a pop-up window, or a dialog box; there is no specific limitation here.

[0144] If the traveler triggers a confirmation event for the change notification, it means the traveler acknowledges the changes, and the second terminal can simultaneously update the request content of both the first and second ride-hailing requests. If the traveler refuses the changes, the traveler can be removed from the first ride-hailing request. In this case, the second terminal can respond to the traveler's refusal of the change notification by canceling the display of the shared order page, and any second ride-hailing request initiated by the removed traveler will also be canceled.

[0145] In the above embodiments, supporting peers to actively change the request content can not only deal with the situation where the request content is incorrect when placing an order for the first time, but also improve the success rate of booking a ride by adjusting the request content when the ride-hailing capacity is tight, which is conducive to further improving flexibility.

[0146] In one embodiment, such as Figure 16 As shown, another method for displaying travel information is provided, applied to a computer device. This computer device is used as an example. Figure 1 Taking the first terminal 101 corresponding to the travel object as an example, the travel information display method may include the following steps:

[0147] Step S1601: If the traveler initiates a ride-hailing event on the ride-hailing page, display the shared element that matches the first ride-hailing request;

[0148] The first ride-hailing request is a request generated in response to a ride-hailing event;

[0149] Step S1602: In response to the trigger operation on the shared element, redirect to the shared order page;

[0150] The shared order page displays a shared control for the first ride request;

[0151] Step S1603: Based on the vehicle type requested in the first ride request, determine the threshold N of the number of fellow passengers corresponding to the first ride request, and display placeholders for N fellow passengers to be added on the shared order page.

[0152] Where N is a positive integer;

[0153] Step S1604: In response to a trigger operation on the shared control, display at least one candidate interactive application;

[0154] Step S1605: In response to the selection event of the target application in each interactive application, redirect to the service page of the target application;

[0155] Step S1606: In response to the object selection event triggered on the service page, determine the expected shared object for the first ride-hailing request;

[0156] The objects of expectation for sharing include individuals who expect to share and groups who expect to share.

[0157] Step S1607: The individuals who wish to share and the group members in the groups who wish to share, excluding the travel recipients, are identified as the intended sharing recipients for the first ride-hailing request.

[0158] Step S1608: If the number of objects to be shared matches the vehicle type requested in the first ride request, trigger a confirmation event for the ride-sharing objects for the first ride request.

[0159] Step S1609: In response to the companion object confirmation event, display the interaction page with the confirmed companion object, and display the first shared ride request on the interaction page;

[0160] Step S1610: In response to the triggering event of the peer object's first ride request, replace the placeholder identifier with the peer object identifier of the peer object.

[0161] Step S1611: Corresponding to the travel object identifier of the travel object, display the first response status of the first ride-hailing request initiated by the travel object;

[0162] Step S1612, corresponding to the peer object identifier, displays status information indicating that the order is waiting to be placed;

[0163] Step S1613: In response to the confirmation event of the peer object regarding the request content, cancel the display of status information and display the second response status of the second ride request initiated by the peer object;

[0164] Among them, the first ride-hailing request and the second ride-hailing request are mutually exclusive requests with the same content.

[0165] Step S1614: In response to the response event of the target request in the first ride request and the second ride request, update the response status of the target request from the waiting response status to the responded status.

[0166] Step S1615: Identify non-target requests other than the target request in the first ride request and the second ride request;

[0167] Step S1616: Update the response status of the non-target request from the waiting response status to the canceled status.

[0168] In one embodiment, such as Figure 17 As shown, another method for displaying travel information is provided, applied to a computer device. This computer device is used as an example. Figure 1 Taking the second terminal 102 corresponding to the travel object as an example, the travel information display method may include the following steps:

[0169] Step S1701: In response to the request sharing event initiated by the sharing element triggered by the travel object, the first ride-hailing request to be shared is displayed on the interaction page with the travel object.

[0170] Among them, the shared element is displayed when the traveler initiates a ride-hailing event on the ride-hailing page; the first ride-hailing request is a request generated in response to the ride-hailing event.

[0171] Step S1702: In response to the triggering event for the first ride-hailing request, display the request content of the first ride-hailing request on the shared order page;

[0172] Step S1703: In response to the confirmation event for the requested content, initiate a second ride-hailing request;

[0173] Step S1704: Display the first response status of the first ride-hailing request and the second response status of the second ride-hailing request initiated by the fellow passenger on the shared order page;

[0174] Among them, the first ride-hailing request and the second ride-hailing request are mutually exclusive requests with the same content;

[0175] Step S1705: In response to the change event of the request content of the travel subject for the first ride request, display the change prompt information;

[0176] Step S1706: In response to the confirmation event for the change notification information, update the request content of the first ride request and the second ride request;

[0177] Step S1707: In response to the response event of the target request in the first ride request and the second ride request, update the response status of the target request from the waiting response status to the responded status.

[0178] Step S1708: Identify non-target requests other than the target request in the first ride request and the second ride request;

[0179] Step S1709: Update the response status of the non-target request from the waiting response status to the canceled status.

[0180] The aforementioned method for displaying travel information, when a traveler initiates a ride-hailing event on the ride-hailing page, displays a shared element matching the first ride-hailing request generated in response to the event. In response to a request to share the shared element with a fellow traveler, the shared first ride-hailing request is displayed on the interaction page with the fellow traveler. Sharing ride-hailing requests from a traveler to a fellow traveler reduces the operational costs for the fellow traveler during the ride-hailing process. In response to the fellow traveler's trigger event for the first ride-hailing request, the first response status of the first ride-hailing request and the second response status of the second ride-hailing request initiated by the fellow traveler are displayed on the shared order page. The first and second ride-hailing requests are mutually exclusive requests with identical content. This ensures that only one ride-hailing request is responded to through content sharing and mutual exclusion, thus supporting quick order placement for fellow traveler while avoiding order cancellations due to duplicate orders, thereby reducing the waste of ride-hailing capacity to some extent.

[0181] The following section uses a mini-program as an example to illustrate the method for displaying travel information provided in this application.

[0182] In one embodiment, such as Figure 18As shown, User 1 can place a ride-hailing order with the service provider by opening a mini-program deployed on the first terminal, submitting the first ride-hailing request. The request information (i.e., order information) of the first ride-hailing request will be stored in the database and then fed back to User 1 through the server and the mini-program. User 1 can share the order based on this order information, carrying a unique order identifier during the sharing process. For example, User 1 can share the first ride-hailing request with User 2 through an interactive page with User 2. User 2 can then request the request information of the first ride-hailing request matching the unique order identifier from the server through the mini-program. This request information may include the origin, destination, etc. After confirming this information, User 2 can place the order directly without manual editing. At this point, the request initiated by User 2 is called the second ride-hailing request. The second ride-hailing request carries the same unique order identifier as the first ride-hailing request; the two are mutually exclusive requests with identical request content. The request information (i.e., order information) of the second ride-hailing request will also be stored in the database. Mutually exclusive requests with identical content can be linked through a unique order identifier. This allows the server to cancel other orders and notify the users who initiated them, even if a driver accepts one order. In other words, once someone's order is accepted, all other orders are automatically canceled. Accessing the "Call a Ride Together" function page from the group entry point reveals the order status for each person; only one person will have a "Driver Accepted" status, while the others will have their status changed to "Order Cancelled." In case of concurrency (e.g., simultaneous order acceptance), the server can select the optimal driver based on arrival time and cancel other orders.

[0183] The above methods can improve the efficiency of ride-hailing during peak hours and provide a better user experience, allowing travelers to place orders together within the same group without spatial limitations. Furthermore, while meeting travelers' needs, it minimizes the waste of transportation resources. Instead of waiting for order acceptance results to decide whether to cancel, the system can dynamically adjust the order acceptance status of other travelers within the group, allowing orders to be canceled even if other drivers haven't accepted them.

[0184] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0185] Based on the same inventive concept, this application also provides a travel information display device for implementing the travel information display method described above. The solution provided by this device is similar to the solution described in the above method; therefore, the specific limitations in one or more travel information display device embodiments provided below can be found in the limitations of the travel information display method described above, and will not be repeated here.

[0186] In one embodiment, such as Figure 19 As shown, a travel information display device is provided, applied to a first terminal corresponding to a traveler. The device includes:

[0187] The shared element display module 1901 is used to display shared elements that match the first ride request when a traveler initiates a ride request event on the ride request page; the first ride request is a request generated in response to the ride request event.

[0188] The request sharing module 1902 is used to respond to the request sharing event initiated by the sharing element to the peer object, and to display the first ride-hailing request to be shared on the interaction page with the peer object;

[0189] The first status display module 1903 is used to respond to the triggering event of the first ride request from the peer object and display the first response status of the first ride request and the second response status of the second ride request initiated by the peer object on the shared order page; the first ride request and the second ride request are mutually exclusive requests with the same request content.

[0190] In one embodiment, the request sharing module 1902 includes: a sharing control display unit, used to jump to a sharing order page in response to a trigger operation on a sharing element; the sharing order page displays a sharing control for the first ride request; and a request sharing unit, used to display the shared first ride request on the interaction page with the peer object in response to a request sharing event initiated by the sharing control to the peer object.

[0191] In one embodiment, the request sharing unit is specifically configured to: display at least one candidate interactive application in response to a trigger operation on the sharing control; jump to the service page of the target application in response to a selection event of the target application in each interactive application; display an interaction page with the confirmed ride-sharing object in response to a ride-sharing object confirmation event triggered on the service page; and display the first ride-hailing request to be shared on the interaction page.

[0192] In one embodiment, the travel information display device further includes: a desired sharing object determination module, configured to determine the desired sharing object of the first ride-hailing request in response to an object selection event triggered on the service page; and a fellow traveler object confirmation module, configured to trigger a fellow traveler object confirmation event for the first ride-hailing request if the number of desired sharing objects matches the vehicle type requested in the first ride-hailing request.

[0193] In one embodiment, the desired sharing object determination module is specifically used to: in response to an object selection event triggered on the service page, determine the desired sharing group of the first ride-hailing request; and determine the group members in the desired sharing group other than the travel object as the desired sharing objects of the first ride-hailing request.

[0194] In one embodiment, the travel information display device further includes: a quantity threshold determination module, used to determine the quantity threshold N of the ride-sharing objects corresponding to the first ride-sharing request based on the vehicle type requested in the first ride-sharing request; N is a positive integer; and a placeholder display module, used to display placeholders of N ride-sharing objects to be added on the shared order page.

[0195] In one embodiment, the first status display module 1903 includes: an identifier replacement unit, configured to replace a placeholder identifier with the peer identifier of the peer in response to a triggering event of a peer object's first ride request; a first response status display unit, configured to display the first response status of the first ride request initiated by the traveler corresponding to the traveler's traveler identifier; and a second response status display unit, configured to display the second response status of the second ride request initiated by the peer in response to the peer identifier.

[0196] In one specific embodiment, the second response status display unit is specifically used to: display status information indicating waiting to place an order corresponding to the peer object identifier; and, in response to the peer object's confirmation event for the request content, cancel the display of status information and display the second response status of the second ride-hailing request initiated by the peer object.

[0197] In one embodiment, the travel information display device further includes a response status update module, configured to: update the response status of the target request from a waiting response status to a responded status in response to a response event to the target request in the first ride request and the second ride request; determine non-target requests other than the target request in the first ride request and the second ride request; and update the response status of the non-target requests from a waiting response status to a canceled status.

[0198] In one embodiment, the first status display module 1903 is specifically used to: display the third response status of the third ride request initiated by the third party on the shared order page when a peer object initiates a request to share an event with a third party and the third party triggers a second ride request; the request content of the third ride request is the same as that of the second ride request, and any two of the first ride request, the second ride request and the third ride request are mutually exclusive requests.

[0199] In one embodiment, the travel information display device further includes a first content modification module, configured to: display modified content on the ride-hailing page in response to a request content modification event for the first ride-hailing request; and update the request content of the first ride-hailing request and the second ride-hailing request in response to a confirmation operation for the modified content.

[0200] In one embodiment, the travel information display device further includes a first content modification module, configured to: display modification prompt information in response to a modification event of the request content of the second ride-hailing request by a fellow traveler; and update the request content of the first ride-hailing request and the second ride-hailing request in response to a confirmation operation of the modification prompt information.

[0201] In one embodiment, such as Figure 20 As shown, a travel information display device is provided, applied to a second terminal corresponding to a travel companion. The device includes:

[0202] The request display module 2001 is used to respond to a request sharing event initiated by a sharing element triggered by a traveler, and to display the first ride-hailing request to be shared on the interaction page with the traveler; the sharing element is displayed when the traveler initiates a ride-hailing event on the ride-hailing page; the first ride-hailing request is a request generated in response to the ride-hailing event;

[0203] The second status display module 2002 is used to respond to the triggering event of the peer object for the first ride request, and to display the first response status of the first ride request and the second response status of the second ride request initiated by the peer object on the shared order page; the first ride request and the second ride request are mutually exclusive requests with the same request content.

[0204] In one embodiment, the second status display module 2002 is specifically used to: display the request content of the first ride-hailing request on the shared order page in response to a trigger event for the first ride-hailing request; initiate a second ride-hailing request in response to a confirmation event for the request content; and display the first response status of the first ride-hailing request and the second response status of the second ride-hailing request initiated by the peer on the shared order page.

[0205] In one embodiment, the travel information display device further includes a second content modification module, configured to: display modification prompt information in response to a request content modification event of the travel subject for the first ride-hailing request; and update the request content of the first ride-hailing request and the second ride-hailing request in response to a confirmation event of the modification prompt information.

[0206] In one embodiment, the number of ride-sharing objects is multiple. In this embodiment, the second content modification module is specifically used to: update the request content of the first ride-hailing request and each of the second ride-hailing requests in response to a confirmation event from each ride-sharing object regarding the modification prompt information. The second content modification module is also used to: cancel the display of the first response status of the first ride-hailing request on the shared order page in response to a rejection event from each ride-sharing object regarding the modification prompt information.

[0207] In one embodiment, the travel information display device further includes a second content modification module, configured to: display modified content on the ride-hailing page in response to a request content modification event for the second ride-hailing request; and update the request content of the first ride-hailing request and the second ride-hailing request in response to a confirmation event by the travel subject regarding the modified content.

[0208] The various modules in the aforementioned travel information display device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the corresponding operations of each module.

[0209] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 21As shown, the computer device includes a processor, memory, input / output interface, communication interface, display unit, and input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interface. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage medium. The input / output interface is used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a method for displaying travel information. The display unit of the computer device is used to form a visually visible image. It can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0210] Those skilled in the art will understand that Figure 21 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0211] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0212] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0213] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0214] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0215] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0216] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0217] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for displaying travel information, characterized in that, The method, applied to a first terminal corresponding to a traveler, includes: When the travel subject initiates a ride-hailing event on the ride-hailing page, a shared element matching the first ride-hailing request is displayed; the first ride-hailing request is a request generated in response to the ride-hailing event. In response to the event that triggers the sharing element to initiate a sharing request to a peer object, the first ride-hailing request that has been shared is displayed on the interaction page with the peer object; In response to the triggering event of the first ride-hailing request from the peer, the first response status of the first ride-hailing request and the second response status of the second ride-hailing request initiated by the peer are displayed on the shared order page; the first ride-hailing request and the second ride-hailing request are mutually exclusive requests with the same request content.

2. The method according to claim 1, characterized in that, In response to the event triggering the sharing request initiated by the sharing element to the peer object, the first shared ride request is displayed on the interaction page with the peer object, including: In response to a trigger operation on the shared element, the user is redirected to the shared order page; the shared order page displays a shared control for the first ride request. In response to the event that triggers the sharing control to request sharing with the peer object, the first ride-hailing request to be shared is displayed on the interaction page with the peer object.

3. The method according to claim 2, characterized in that, In response to the event triggering the sharing control to initiate a sharing request to a fellow traveler, the first shared ride request is displayed on the interaction page with the fellow traveler, including: In response to a triggering operation on the shared control, at least one candidate interactive application is displayed; In response to a selection event for a target application in each of the aforementioned interactive applications, the user is redirected to the service page of the target application. In response to a peer object confirmation event triggered on the service page, an interaction page with the confirmed peer object is displayed; The interactive page displays the first shared ride request.

4. The method according to claim 3, characterized in that, The method further includes: In response to an object selection event triggered on the service page, determine the desired shared object for the first ride-hailing request; If the number of objects to be shared matches the vehicle type requested in the first ride-hailing request, a ride-sharing object confirmation event is triggered for the first ride-hailing request.

5. The method according to claim 4, characterized in that, In response to an object selection event triggered on the service page, the desired shared object for the first ride-hailing request is determined, including: In response to an object selection event triggered on the service page, determine the desired sharing group for the first ride request; The group members in the desired sharing group, excluding the travel recipient, are identified as the desired sharing recipients of the first ride-hailing request.

6. The method according to claim 2, characterized in that, The method further includes: Based on the vehicle type requested in the first ride-hailing request, determine the threshold N for the number of fellow passengers corresponding to the first ride-hailing request; N is a positive integer. On the shared order page, placeholders for N peers to be added are displayed.

7. The method according to claim 6, characterized in that, The response to the triggering event of the first ride-hailing request from the peer object, displaying the first response status of the first ride-hailing request and the second response status of the second ride-hailing request initiated by the peer object on the shared order page, includes: In response to the triggering event of the first ride request from the peer object, the placeholder identifier is replaced with the peer object identifier of the peer object; The first response status of the first ride-hailing request initiated by the traveler is displayed, corresponding to the traveler's traveler identifier. Corresponding to the peer object identifier, the second response status of the second ride-hailing request initiated by the peer object is displayed.

8. The method according to claim 7, characterized in that, The second response status, corresponding to the identifier of the fellow traveler, for displaying the second ride-hailing request initiated by the fellow traveler, includes: Corresponding to the peer object identifier, display status information indicating that the order is pending; In response to the confirmation event of the peer object regarding the request content, the status information is canceled and the second response status of the second ride request initiated by the peer object is displayed.

9. The method according to claim 1, characterized in that, The method further includes: In response to a response event to the target request in the first ride request and the second ride request, the response status of the target request is updated from the waiting response status to the responded status; Identify non-target requests other than the target request in the first and second ride-hailing requests; Update the response status of the non-target request from the waiting response status to the canceled status.

10. The method according to any one of claims 1 to 9, characterized in that, The method further includes: When the peer initiates a request to share an event with a third party, and the third party triggers the second ride-hailing request, the third response status of the third ride-hailing request initiated by the third party is displayed on the sharing order page. The third ride-hailing request and the second ride-hailing request have the same request content, and any two of the first ride-hailing request, the second ride-hailing request and the third ride-hailing request are mutually exclusive requests.

11. The method according to any one of claims 1 to 9, characterized in that, The method further includes: In response to a request content change event for the first ride-hailing request, the changed content is displayed on the ride-hailing page; In response to the confirmation operation for the changed content, the request content of the first ride-hailing request and the second ride-hailing request is updated.

12. The method according to any one of claims 1 to 9, characterized in that, The method further includes: In response to a change in the request content of the second ride-hailing request from the peer, a change notification message is displayed; In response to the confirmation operation of the change prompt information, the request content of the first ride-hailing request and the second ride-hailing request is updated.

13. A method for displaying travel information, characterized in that, The method, applied to a second terminal corresponding to a peer object, includes: In response to a request to share initiated by a sharing element triggered by a traveler, a first ride-hailing request to be shared is displayed on the interaction page with the traveler; the sharing element is displayed when the traveler initiates a ride-hailing event on the ride-hailing page; the first ride-hailing request is a request generated in response to the ride-hailing event. In response to the triggering event of the peer's first ride request, the first response status of the first ride request and the second response status of the second ride request initiated by the peer are displayed on the shared order page; the first ride request and the second ride request are mutually exclusive requests with the same request content.

14. The method according to claim 13, characterized in that, The response to the triggering event for the first ride-hailing request, displaying the first response status of the first ride-hailing request and the second response status of the second ride-hailing request initiated by the fellow traveler on the shared order page, includes: In response to the triggering event for the first ride-hailing request, the request content of the first ride-hailing request is displayed on the shared order page; In response to a confirmation event regarding the requested content, a second ride-hailing request is initiated; The shared order page displays the first response status of the first ride-hailing request and the second response status of the second ride-hailing request initiated by the fellow traveler.

15. The method according to claim 13, characterized in that, The method further includes: In response to a change in the request content of the travel subject regarding the first ride-hailing request, a change notification message is displayed; In response to a confirmation event for the change notification information, update the request content of the first ride-hailing request and the second ride-hailing request.

16. The method according to claim 15, characterized in that, The number of the peers is multiple; the step of updating the request content of the first ride-hailing request and the second ride-hailing request in response to the confirmation event of the change prompt information includes: In response to the confirmation event of each of the aforementioned peer objects regarding the change prompt information, update the request content of the first ride-hailing request and each of the second ride-hailing requests; The method further includes: In response to the rejection event of each of the aforementioned peers regarding the change prompt information, the first response status of the first ride-hailing request is removed from the shared order page.

17. The method according to claim 13, characterized in that, The method further includes: In response to a request content change event for the second ride-hailing request, the changed content is displayed on the ride-hailing page; In response to the travel subject's confirmation of the changed content, the request content of the first ride-hailing request and the second ride-hailing request are updated.

18. A travel information display device, characterized in that, The device, applied to a first terminal corresponding to a traveler, includes: The shared element display module is used to display shared elements matching the first ride-hailing request when the travel subject initiates a ride-hailing event on the ride-hailing page; the first ride-hailing request is a request generated in response to the ride-hailing event. The request sharing module is used to respond to the request sharing event initiated by the sharing element to the peer object, and to display the first ride-hailing request to be shared on the interaction page with the peer object; The first status display module is used to respond to the triggering event of the first ride request by the peer object and display the first response status of the first ride request and the second response status of the second ride request initiated by the peer object on the shared order page; the first ride request and the second ride request are mutually exclusive requests with the same request content.

19. A travel information display device, characterized in that, The device, applied to a second terminal corresponding to a peer object, includes: The request display module is used to respond to a request sharing event initiated by a sharing element triggered by a traveler, and to display the first ride-hailing request to be shared on the interaction page with the traveler; the sharing element is displayed when the traveler initiates a ride-hailing event on the ride-hailing page; the first ride-hailing request is a request generated in response to the ride-hailing event; The second status display module is used to respond to the triggering event of the peer object in response to the first ride request, and to display the first response status of the first ride request and the second response status of the second ride request initiated by the peer object on the shared order page; the first ride request and the second ride request are mutually exclusive requests with the same request content.

20. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 17.

21. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 17.

22. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 17.

Images