Vehicle use service processing method and device, electronic equipment, computer readable storage medium and computer program product

Abstract

The invention provides a vehicle use service processing method and device, electronic equipment, a computer readable storage medium and a computer program product. The method is applied to the traffic field and vehicle-mounted scenes. The method comprises the following steps: displaying a taxi service interface based on taxi calling account login; in response to an editing operation on the car use service interface, displaying a car use order formed by editing, the car use order at least comprising an end point of the car use account; and in response to a sending trigger operation for the car using order, sending the car using order to the car using account, the car using order being used for the car using account to request a car using service. According to the invention, the accuracy and flexibility of vehicle service can be improved.

Description

Vehicle service processing methods, devices, electronic devices, computer-readable storage media, and computer program products Technical Field

[0001] This application relates to computer technology, and more particularly to a vehicle service processing method, apparatus, electronic device, computer-readable storage medium, and computer program product. Background Technology

[0002] With the advancement of technology, people's demand for ride-hailing services is increasing. However, for certain groups (such as the elderly or others who have difficulty hailing rides online), ride-hailing services often require a third-party service. These services typically involve real-time remote ordering, requiring constant communication between the passenger and the person making the order to obtain information about the pick-up location and pick-up time before an accurate order can be placed. This results in high communication costs, and passengers cannot flexibly adjust their order time or pick-up location based on real-time conditions. Summary of the Invention

[0003] This application provides a method, apparatus, electronic device, computer-readable storage medium, and computer program product for handling ride-hailing services, which can improve the accuracy and flexibility of ride-hailing services.

[0004] The technical solution of this application embodiment is implemented as follows:

[0005] This application provides a method for processing ride-hailing services, the method comprising:

[0006] Displays the ride-hailing service interface based on the ride-hailing account login;

[0007] In response to an editing operation on the car rental service interface, the edited car rental order is displayed, wherein the car rental order includes at least the destination of the car rental account;

[0008] In response to a trigger operation for sending the car rental order, the car rental order is sent to the car rental account, wherein the car rental order is used by the car rental account to request car rental services.

[0009] This application provides a method for processing ride-hailing services, the method comprising:

[0010] The system displays a ride-hailing service interface based on the ride-hailing account login. The ride-hailing service interface includes ride-hailing orders sent by the ride-hailing account, and the ride-hailing orders include at least the destination of the ride-hailing account.

[0011] In response to the triggered operation for the ride-hailing order, a ride-hailing service is requested based on the ride-hailing order.

[0012] In the above scheme, the step of responding to the triggering operation for the ride-hailing order and requesting ride-hailing service based on the ride-hailing order includes:

[0013] If the ride-hailing order does not include a starting point, in response to an edit operation on the starting point field of the ride-hailing order, the edited starting point is displayed, wherein the edit operation can be performed in any of the following ways: marking the location on a map, or providing location instructions via voice.

[0014] Based on the starting point and the ending point formed by the editing, a request for car service is made.

[0015] In the above scheme, the step of responding to the triggering operation for the ride-hailing order and requesting ride-hailing service based on the ride-hailing order includes:

[0016] In response to an edit operation on the starting point field of the ride-hailing order, at least one candidate location is displayed, wherein, when there are multiple candidate locations, the sorting factors for the at least one candidate location include any one of the following: the time interval of historical use, descending order of historical use frequency, the degree of matching with the order parameters specified by the ride-hailing account, and the probability of multiple candidate points of interest being selected in the current environment of the ride-hailing account.

[0017] In response to the selection operation for the at least one candidate location, a ride-hailing service is requested based on the selected candidate location as the starting point and the destination.

[0018] This application provides a vehicle service processing device, the device comprising:

[0019] The first display module is used to display the ride-hailing service interface based on the ride-hailing account login;

[0020] The second display module is used to display the edited car rental order in response to the editing operation on the car rental service interface, wherein the car rental order includes at least the destination of the car rental account;

[0021] The order sending module is used to send the car rental order to the car rental account in response to the sending trigger operation for the car rental order, wherein the car rental order is used for the car rental account to request car rental services.

[0022] This application provides a vehicle service processing device, the device comprising:

[0023] The third display module is used to display the car service interface based on the car account login, wherein the car service interface includes car orders sent by the car-hailing account, and the car orders include at least the destination of the car account;

[0024] The request service module is used to respond to the triggered operation for the car rental order and request car rental service based on the car rental order.

[0025] This application provides an electronic device, the electronic device comprising:

[0026] Memory is used to store executable instructions or computer programs.

[0027] The processor, when executing computer-executable instructions or computer programs stored in the memory, implements the vehicle service processing method provided in the embodiments of this application.

[0028] This application provides a computer-readable storage medium storing a computer program or computer-executable instructions, which, when executed by a processor, implements the vehicle service processing method provided in this application.

[0029] This application provides a computer program product, including a computer program or computer executable instructions. When the computer program or computer executable instructions are executed by a processor, they implement the vehicle service processing method provided in this application.

[0030] The embodiments of this application have the following beneficial effects:

[0031] In response to the ride-hailing account's editing operation on the ride-hailing service interface, the system displays the edited ride-hailing order. In response to the ride-hailing account's trigger operation to send the ride-hailing order, the system sends the ride-hailing order, including the destination of the ride-hailing account, to the ride-hailing account, so that the ride-hailing account can request ride-hailing service based on the ride-hailing order. In other words, the ride-hailing account only needs to edit the ride-hailing order in advance and send the edited ride-hailing order to the ride-hailing account. This allows the ride-hailing account to place orders on demand in real time based on the pre-set destination according to its own needs. Compared with related technologies that require real-time communication between the passenger and the ride-hailing account to place an accurate order, this can effectively reduce communication costs and improve the flexibility of ride-hailing service. Attached Figure Description

[0032] Figure 1 is a schematic diagram of the architecture of the vehicle service processing system 100 provided in an embodiment of this application;

[0033] Figure 2A is a structural schematic diagram of the terminal 400-1 provided in an embodiment of this application;

[0034] Figure 2B is a structural schematic diagram of the terminal 400-2 provided in an embodiment of this application;

[0035] Figure 3A is a schematic diagram of the first process of the vehicle service processing method provided in the embodiment of this application;

[0036] Figure 3B is a schematic diagram of the second process of the vehicle service processing method provided in the embodiment of this application;

[0037] Figure 3C is a schematic diagram of the third process of the vehicle service processing method provided in the embodiments of this application;

[0038] Figure 3D is a schematic diagram of the fourth process of the vehicle service processing method provided in the embodiments of this application;

[0039] Figure 3E is a schematic diagram of the fifth process of the vehicle service processing method provided in the embodiments of this application;

[0040] Figure 3F is a schematic diagram of the sixth process of the vehicle service processing method provided in the embodiments of this application;

[0041] Figure 3G is a schematic diagram of the seventh process of the vehicle service processing method provided in the embodiments of this application;

[0042] Figure 4A is a schematic diagram of the eighth process of the vehicle service processing method provided in the embodiments of this application;

[0043] Figure 4B is a schematic diagram of the ninth process of the vehicle service processing method provided in the embodiments of this application;

[0044] Figure 4C is a schematic diagram of the tenth process of the vehicle service processing method provided in the embodiment of this application;

[0045] Figure 4D is a schematic diagram of the eleventh step of the vehicle service processing method provided in the embodiment of this application;

[0046] Figure 4E is a schematic diagram of the twelfth step of the vehicle service processing method provided in the embodiment of this application;

[0047] Figure 5A is a first schematic diagram of the car rental service provided in an embodiment of this application;

[0048] Figure 5B is a second schematic diagram of the car rental service provided in an embodiment of this application;

[0049] Figure 5C is a third schematic diagram of the car service provided in the embodiment of this application;

[0050] Figure 5D is a fourth schematic diagram of the car service provided in the embodiment of this application;

[0051] Figure 5E is a fifth schematic diagram of the car service provided in the embodiments of this application;

[0052] Figure 5F is a sixth schematic diagram of the car service provided in the embodiment of this application;

[0053] Figure 6 is a seventh schematic diagram of the car service provided in the embodiments of this application;

[0054] Figure 7 is a schematic diagram of account binding provided in an embodiment of this application;

[0055] Figure 8A is an eighth schematic diagram of the car service provided in the embodiment of this application;

[0056] Figure 8B is a ninth schematic diagram of the car service provided in the embodiment of this application;

[0057] Figure 8C is a tenth schematic diagram of the car service provided in the embodiment of this application;

[0058] Figure 8D is the eleventh schematic diagram of the car service provided in the embodiment of this application;

[0059] Figure 9 is a schematic diagram of the thirteenth step of the vehicle service processing method provided in the embodiments of this application.

[0060] It should be noted that the terms "first" and "second" mentioned above are only used to distinguish between different options and do not represent the degree of superiority or inferiority of the options or their priority in the implementation process. Detailed Implementation

[0061] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0062] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0063] In the following description, the terms "first / second / third" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first / second / third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0064] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0065] Unless otherwise specified, "at least one" as used below refers to one or more cases, and "multiple" can refer to two or more cases.

[0066] Unless otherwise defined, all technical and scientific terms used in the embodiments of this application have the same meaning as commonly understood by one of ordinary skill in the art. The terminology used in the embodiments of this application is for the purpose of describing the embodiments of this application only and is not intended to limit this application.

[0067] In the implementation of this application, the collection and processing of relevant data should strictly comply with the requirements of relevant laws and regulations, obtain the informed consent or separate consent of the personal information subject, and carry out subsequent data use and processing within the scope of laws and regulations and the authorization of the personal information subject.

[0068] Before providing a further detailed description of the embodiments of this application, the nouns and terms involved in the embodiments of this application will be explained, and the nouns and terms involved in the embodiments of this application shall be interpreted as follows.

[0069] 1) Responding to: used to indicate the conditions or states on which the operation is performed depends. When the conditions or states on which it depends are met, one or more operations can be performed in real time or with a set delay. Unless otherwise specified, there is no restriction on the order in which the multiple operations are performed.

[0070] 2) Human-Computer Interaction Interface: An interface used to provide human-computer interaction functions. Examples include graphical user interfaces (GUIs), augmented reality (AR) interfaces, virtual reality (VR) interfaces, voice user interfaces (VUIs), interactive projection interfaces (using projection technology to display information on a flat surface), eye-tracking interfaces (interfaces controlled by detecting the user's gaze), holographic interfaces (three-dimensional holograms formed by projecting images using holographic projection technology, allowing viewing of stereoscopic images without special glasses), multimodal interfaces (interfaces combining multiple interaction methods, such as tactile, visual, and auditory interaction), and brain-machine interfaces (BMIs).

[0071] 3) Car Rental Service Interface: This interface provides users with car rental services. For example, users can edit the order parameters for their car rental orders. These parameters may include: vehicle type (e.g., economy, luxury), route (e.g., highway, provincial road), route preferences (e.g., shortest route, least congested, fewest traffic lights), payment method (payment by the booking account, payment by the user account), waypoints, origin, and destination.

[0072] 4) Order Template: A template displayed in the car rental service interface for users to edit car rental order parameters, including origin, destination, vehicle, etc.

[0073] 5) Order parameters: Parameters related to the car service, such as vehicle type (e.g., economy, luxury), driving route (e.g., highway, provincial road), route preference (e.g., shortest route, least congested, fewest traffic lights), payment method (payment by the booking account, payment by the user account), waypoints, origin, and destination.

[0074] 6) Car usage account: The account of a user who needs a car, such as the user's account in the instant messaging client.

[0075] 7) Ride-hailing account: The account of a user who assists other users in requesting ride-hailing services. For example, the users to whom the ride-hailing account and ride-hailing order account belong can be relatives, friends, colleagues, etc.

[0076] The ride-hailing services in related technologies usually involve real-time remote ordering, which requires the passenger and the person ordering the ride to maintain real-time communication in order to obtain information on the pick-up point and the time of use before an accurate order can be placed. This results in relatively high communication costs, and passengers cannot flexibly adjust the origin and destination of the ride according to the real-time situation.

[0077] Based on the above analysis, the applicant found that the relevant technology's car service processing methods cannot guarantee the accuracy and flexibility of car services. In response to the above problems, this application provides a car service processing method, device, electronic device, computer-readable storage medium, and computer program product, which can improve the accuracy and flexibility of car services.

[0078] The following describes exemplary applications of the electronic devices provided in the embodiments of this application. These electronic devices can be implemented as various types of terminals such as laptops, tablets, desktop computers, set-top boxes, smartphones, smart speakers, smartwatches, smart TVs, and in-vehicle terminals, or as servers. Exemplary applications of the electronic devices as terminals will be described below.

[0079] Referring to Figure 1, which is a schematic diagram of the architecture of the car service processing system 100 provided in the embodiment of this application, in order to support a car service processing application, the terminal (terminal 400-1 and terminal 400-2 are shown as examples) connects to the server 200 through the network 300. The network 300 can be a wide area network or a local area network, or a combination of the two.

[0080] Terminal 400-1 is used to display a ride-hailing service interface based on the ride-hailing account login on the human-computer interaction interface 411-1; in response to the editing operation of the user associated with the ride-hailing account on the ride-hailing service interface, it displays the edited ride-hailing order, which includes at least one destination of the ride-hailing account; in response to the user associated with the ride-hailing account triggering the sending of the ride-hailing order, it sends the ride-hailing order to the terminal 400-2 of the instant messaging client logged in with the ride-hailing account via the network 300 and the server 200, so that the ride-hailing account can request ride-hailing service.

[0081] In some embodiments, server 200 may 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, content delivery networks (CDNs), and big data and artificial intelligence platforms. Terminals and servers can be connected directly or indirectly via wired or wireless communication, which is not limited in this embodiment.

[0082] Referring to Figure 2A, which is a schematic diagram of the structure of a terminal 400-1 provided in an embodiment of this application, the terminal 400-1 shown in Figure 2A includes: at least one processor 410-1, a memory 450-1, at least one network interface 420-1, and a user interface 430-1. The various components in the terminal 400-1 are coupled together through a bus system 440-1. It is understood that the bus system 440-1 is used to realize the connection and communication between these components. In addition to a data bus, the bus system 440-1 also includes a power bus, a control bus, and a status signal bus. However, for clarity, all buses are labeled as bus system 440-1 in Figure 2A.

[0083] The processor 410-1 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0084] User interface 430-1 includes one or more output devices 431-1 that enable the presentation of media content, including one or more speakers and / or one or more visual displays. User interface 430-1 also includes one or more input devices 432-1, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

[0085] The memory 450-1 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state storage, hard disk drives, optical disk drives, etc. The memory 450-1 may optionally include one or more storage devices physically located away from the processor 410-1.

[0086] The memory 450-1 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), and the volatile memory may be random access memory (RAM). The memory 450-1 described in this application embodiment is intended to include any suitable type of memory.

[0087] In some embodiments, memory 450-1 is capable of storing data to support various operations, examples of which include programs, modules, and data structures or subsets or supersets thereof, as illustrated below.

[0088] Operating system 451-1 includes system programs for handling various basic system services and performing hardware-related tasks, such as the framework layer, core library layer, driver layer, etc., for implementing various basic business functions and handling hardware-based tasks;

[0089] The network communication module 452-1 is used to reach other electronic devices via one or more (wired or wireless) network interfaces 420-1, such as Bluetooth, WiFi, and Universal Serial Bus (USB).

[0090] Presentation module 453-1 is used to enable the presentation of information (e.g., a user interface for operating peripheral devices and displaying content and information) via one or more output devices 431-1 (e.g., a display screen, a speaker, etc.) associated with user interface 430-1;

[0091] The input processing module 454-1 is used to detect and translate one or more user inputs or interactions from one or more input devices 432-1.

[0092] In some embodiments, the apparatus provided in this application can be implemented in software. Figure 2A shows a car service processing device 455-1 stored in memory 450-1, which can be software in the form of programs and plug-ins, including the following software modules: a first display module 4551-1, a second display module 4552-1, and an order sending module 4553-1. These modules are logically related and can therefore be arbitrarily combined or further split according to the functions they implement. The functions of each module will be described below.

[0093] Referring to Figure 2B, which is a schematic diagram of the structure of a terminal 400-2 provided in an embodiment of this application, the terminal 400-2 shown in Figure 2B includes: at least one processor 410-2, a memory 450-2, at least one network interface 420-2, and a user interface 430-2. The various components in the terminal 400-2 are coupled together via a bus system 440-2. It is understood that the bus system 440-2 is used to implement communication between these components. In addition to a data bus, the bus system 440-2 also includes a power bus, a control bus, and a status signal bus. However, for clarity, all buses are labeled as bus system 440-2 in Figure 2B.

[0094] The processor 410-2 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0095] User interface 430-2 includes one or more output devices 431-2 that enable the presentation of media content, including one or more speakers and / or one or more visual displays. User interface 430-2 also includes one or more input devices 432-2, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

[0096] The memory 450-2 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state storage, hard disk drives, optical disk drives, etc. The memory 450-2 may optionally include one or more storage devices physically located away from the processor 410-2.

[0097] The memory 450-2 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), and the volatile memory may be random access memory (RAM). The memory 450-2 described in this application embodiment is intended to include any suitable type of memory.

[0098] In some embodiments, memory 450-2 is capable of storing data to support various operations, examples of which include programs, modules, and data structures or subsets or supersets thereof, as illustrated below.

[0099] Presentation module 453-2 is used to enable the presentation of information (e.g., a user interface for operating peripheral devices and displaying content and information) via one or more output devices 431-2 (e.g., a display screen, a speaker, etc.) associated with user interface 430-2;

[0100] The input processing module 454-2 is used to detect and translate one or more user inputs or interactions from one or more input devices 432-2.

[0101] In some embodiments, the apparatus provided in this application can be implemented in software. Figure 2B shows a vehicle service processing apparatus 455-2 stored in memory 450-2, which can be software in the form of programs and plug-ins, including the following software modules: a third display module 4551-2 and a request service module 4552-2. These modules are logically related and can therefore be arbitrarily combined or further divided according to the functions they implement. The functions of each module will be described below.

[0102] In some embodiments, the terminal or server can implement the ride-hailing service processing method provided in this application by running various computer-executable instructions or computer programs. For example, computer-executable instructions can be microprogram-level commands, machine instructions, or software instructions. Computer programs can be native programs or software modules in an operating system; they can be native applications (APPs), i.e., programs that need to be installed in the operating system to run, such as instant messaging clients, electronic map clients, ride-hailing clients, etc.; or they can be mini-programs that can be embedded in any APP, i.e., programs that only need to be downloaded to a browser environment to run, such as a ride-hailing mini-program running in an instant messaging client. In summary, the aforementioned computer-executable instructions can be any form of instruction, and the aforementioned computer programs can be any form of application, module, or plugin.

[0103] The method for processing vehicle services applied to a first terminal device, as provided in the embodiments of this application, will be described in conjunction with exemplary applications and implementations of the terminal provided in the embodiments of this application.

[0104] Referring to Figure 3A, which is a first flowchart of the ride-hailing service processing method provided in the embodiment of this application, the steps shown in Figure 3A will be explained using the terminal of the ride-hailing account as the execution subject as an example.

[0105] In step 101, the ride-hailing service interface based on the ride-hailing account login is displayed.

[0106] In some embodiments, an instant messaging client may be running on the first terminal device, providing a user service function entry point within the instant messaging client; in response to a user's triggering operation on the user service function entry point (e.g., a ride-hailing service mini-program), a ride-hailing service interface logged in based on the ride-hailing account is displayed. Alternatively, a ride-hailing service APP may be running directly on the first terminal device, and in response to a user's opening operation on the ride-hailing service APP, a ride-hailing service interface logged in based on the ride-hailing account is displayed.

[0107] Here, a ride-hailing account is an account that assists other users (users associated with ride-hailing accounts) in calling a vehicle.

[0108] In step 102, in response to the editing operation on the car service interface, the edited car service order is displayed, wherein the car service order includes at least the endpoint of the car service account.

[0109] In some embodiments, the editing operation on the car service interface can be an editing operation on the start or end point of the car service order, and the edited car service order can include one or more ends of the car service account.

[0110] In some embodiments, referring to FIG3B, FIG3B is a second flowchart of the vehicle service processing method provided in the embodiments of this application. Step 102 in FIG3A can be implemented by steps 1021 to 1022 in FIG3B, which will be described in detail below.

[0111] In step 1021, an order template for the car rental account is displayed on the car rental service interface.

[0112] In some embodiments, the order template is displayed on a separate ride-hailing page in the ride-hailing service interface, or the order template is displayed on a ride-hailing subpage of the ride-hailing page in the ride-hailing service interface. The ride-hailing page also includes a real-time ride-hailing subpage, which is used to request ride-hailing services at the current moment.

[0113] Taking the example that the order template for a ride-hailing order is displayed in the ride-hailing subpage of the ride-hailing page in the ride-hailing service interface, see Figure 5A. Figure 5A is a first schematic diagram of the ride-hailing service provided in this application embodiment. As shown in the interface on the left side of Figure 5A, the ride-hailing page of the ride-hailing service interface shown in Figure 5A displays two subpages, namely the real-time ride-hailing subpage 511 and the ride-hailing subpage 512. The ride-hailing subpage 512 displays the order template for a ride-hailing order, and the order template displays the starting point field 513 and the destination field 514.

[0114] Taking the example that the order template for a ride-hailing order is displayed on a separate ride-hailing page within the ride-hailing service interface, see Figure 5B. Figure 5B is a second schematic diagram of the ride-hailing service provided in this application embodiment. As shown in the interface on the left side of Figure 5B, the ride-hailing page of the ride-hailing service interface displays an order template for a ride-hailing order, which includes a starting point field 521 and a destination field 522.

[0115] The order template for the ride-hailing service interface provided in this application embodiment can be displayed on a separate ride-hailing page, or the order template can be displayed on a ride-hailing subpage of the ride-hailing page of the ride-hailing service interface. This can provide users with multiple different ride-hailing entry points, making it convenient for users to edit the order template. This can improve user experience, optimize operation processes, enhance service flexibility, and improve the overall quality of ride-hailing services and user satisfaction.

[0116] In step 1022, in response to an edit operation on the endpoint field in the order template, the endpoint formed by the edit is displayed in the order template, wherein the order template including the endpoint is a ride-hailing order.

[0117] In some embodiments, the destination may be determined in advance by the ride-hailing account and the ride-hailing account, for example, through negotiation via an instant messaging client, or it may be edited by the ride-hailing account itself.

[0118] As an example, continuing to refer to Figure 5B, in response to the editing operation on the endpoint field 522, the endpoint formed by the editing is displayed in the interface in the middle of Figure 5B, where the endpoint is location B (East Gate 2).

[0119] In some embodiments, referring to FIG3C, FIG3C is a third flowchart of the vehicle service processing method provided in the embodiments of this application. Step 1022 in FIG3B can be implemented by steps 10221 to 10222 in FIG3C, as described in detail below.

[0120] In step 10221, in response to a trigger operation on the endpoint field in the order template, a candidate list is displayed, wherein the candidate list includes at least one candidate location, and if there are multiple candidate locations, the sorting factor used includes any one of the following: descending order of historical usage frequency, or ascending order of distance from the current location of the ride account.

[0121] In some embodiments, the triggering operation for the destination field in the order template can be a click operation (such as a click or double-click operation). Here, when the candidate list includes multiple candidate locations, if the sorting factor is descending order of historical usage frequency, the candidate location with the highest historical usage frequency is ranked first, and the candidate location with the lowest historical usage frequency is ranked last. If the sorting factor is ascending order of distance from the current location of the ride-hailing account, the candidate location with the smallest distance from the current location of the ride-hailing account is ranked first, and the candidate location with the largest distance from the current location of the ride-hailing account is ranked last.

[0122] As an example, if the sorting factor is descending order of historical usage frequency, and candidate position 1 has been used 7 times, candidate position 2 has been used 1 time, and candidate position 3 has been used 4 times in the past 5 days, then the order of the three candidate positions would be: candidate position 1, candidate position 3, and candidate position 2. If the sorting factor is ascending order of distance from the current location of the user account, for example, candidate position 4 is 10 meters away from the current location of the user account, candidate position 5 is 5 meters away, and candidate position 6 is 8 meters away, then the order of the three candidate positions would be: candidate position 5, candidate position 6, and candidate position 4.

[0123] In step 10222, in response to the selection operation for at least one candidate location, the selected candidate location is displayed as the endpoint in the order template.

[0124] In some embodiments, the selection operation for at least one candidate location can be the first candidate location in the candidate list, or any candidate location selected by the ride-hailing account.

[0125] As an example, in response to an editing operation on the destination field 522 in the order template, the interface in the middle of Figure 5B displays an editing control 523 for the destination field, an editing control 524 for the origin field, and a candidate location list 525. The candidate location list 525 displays four candidate locations: location 1, location 2, location 3, and location 4. In response to a trigger operation on location 4, the interface on the right side of Figure 5B displays the origin and destination of the ride-hailing order 526, vehicle information 527, a sharing control 528, and a one-click order control 529. The origin and destination 526 shows the destination as location 3. The one-click order control 529 allows the called-for-ride account to quickly place an order; the sharing control 528 allows the called-for-ride account to send the edited ride-hailing order to the ride-hailing account when triggered.

[0126] In some embodiments, when multiple endpoints are formed during editing, the multiple endpoints are used for vehicle accounts to select, and the sorting factors for the multiple endpoints include any one of the following: descending order of historical usage frequency, ascending order of distance from the current location of the vehicle account.

[0127] Here, in response to a ride-hailing order generated by a ride-hailing account that includes multiple destinations, these destinations can be selected by the ride-hailing account. The destinations are arranged according to preset sorting factors in the ride-hailing service interface. If the sorting factor is descending order of historical usage frequency, the most frequently used destination is placed first, and less frequently used destinations are placed later. If the sorting factor is ascending order of distance from the ride-hailing account's current location, the destination closest to the current location is placed first, and destinations farther away are placed later.

[0128] As an example, if the sorting factor is descending order of historical usage frequency, and in the past 5 days, destination 1 has been used 7 times, destination 2 has been used 1 time, and destination 3 has been used 4 times, then the order of the three destinations would be destination 1, destination 3, and destination 2. If the sorting factor is ascending order of distance from the current location of the user account, for example, destination 4 is 10 meters away from the current location of the user account, destination 5 is 5 meters away, and destination 6 is 8 meters away, then the order of the three destinations would be destination 5, destination 6, and destination 4.

[0129] The ride-hailing service processing method provided in this application allows ride-hailing accounts to select from multiple candidate locations when editing the destination field, and sends the selected candidate location as the destination to the ride-hailing account. Providing multiple candidate locations for users to choose from reduces problems caused by inaccurate location services, ensuring that passengers can accurately reach their destination. Users can choose the most suitable destination from multiple candidate locations according to their needs, improving the user's personalized experience and flexibility. Furthermore, when the ride-hailing order includes multiple destinations, it supports ride-hailing accounts selecting from multiple destinations and placing an order based on the selected destination. This allows ride-hailing accounts to quickly select from multiple destinations, speeding up the order confirmation process, improving user convenience and selection flexibility, and also enhancing the accuracy and efficiency of the service, thus contributing to increased user satisfaction.

[0130] In some embodiments, step 102 can also be implemented by performing the following process: in response to an edit operation on the start field in the order template, displaying the edited start in the order template including the end, wherein the order template including the start and end is an updated ride order.

[0131] Here, after the editing operation on the origin field is completed, the order template including both the origin and destination is used as the updated ride-hailing order to replace the ride-hailing order that only includes the destination.

[0132] In some embodiments, the starting point can be determined in advance by the ride-hailing account and the user account, for example, through negotiation via an instant messaging client. Alternatively, it can be edited by the ride-hailing account itself. Or, it can be set independently by the user account after receiving a ride order; for example, the starting point can be the user account's current location, or the user account can choose the starting point for boarding.

[0133] In some embodiments, referring to FIG3D, FIG3D is a fourth flowchart of the car service processing method provided in the embodiments of this application. The above-mentioned "in response to the editing operation on the starting point field in the order template, displaying the edited starting point in the order template including the destination" can be implemented through steps 201 to 202 of FIG3D, which will be described in detail below.

[0134] In step 201, in response to an edit operation on the starting point field in the order template, at least one candidate location is displayed, wherein, if there are multiple candidate locations, the sorting factor for the at least one candidate location includes any one of the following: descending order of historical usage frequency, ascending order of distance from the current location of the ride account.

[0135] In some embodiments, the triggering operation for the starting point field in the order template can be a click operation (such as a click or double-click operation). Here, when the candidate list includes multiple candidate locations, if the sorting factor is descending order of historical usage frequency, the candidate location with the highest historical usage frequency is ranked first, and the candidate location with the lowest historical usage frequency is ranked last. If the sorting factor is ascending order of distance from the current location of the user account, the candidate location with the smallest distance from the current location of the user account is ranked first, and the candidate location with the largest distance from the current location of the user account is ranked last.

[0136] As an example, if the sorting factor is descending order of historical usage frequency, and candidate position 1 has been used 7 times, candidate position 2 has been used 1 time, and candidate position 3 has been used 4 times in the past 5 days, then the order of the three candidate positions would be: candidate position 1, candidate position 3, and candidate position 2. If the sorting factor is ascending order of distance from the current location of the user account, for example, candidate position 4 is 10 meters away from the current location of the user account, candidate position 5 is 5 meters away, and candidate position 6 is 8 meters away, then the order of the three candidate positions would be: candidate position 5, candidate position 6, and candidate position 4.

[0137] In step 202, in response to the selection operation for at least one candidate location, the selected candidate location is used as the starting point and the selected starting point is displayed in the order template including the ending point.

[0138] In some embodiments, the selection operation for at least one candidate location can be the first candidate location in the candidate list, or any candidate location selected by the ride-hailing account.

[0139] In some embodiments, the starting point field in a ride-hailing order is blank. The starting point field is used to take the current position of the ride-hailing account as the starting point when the ride-hailing order is triggered by the ride-hailing account.

[0140] Here, the way a ride-hailing order is triggered by a ride-hailing account can be a click operation (such as a single click or double click). When the starting point field is used to retrieve the location information of the ride-hailing account when the ride-hailing order is triggered by the ride-hailing account, the current location of the ride-hailing account can be used as the starting point.

[0141] In this embodiment of the application, when editing the origin field of a ride-hailing order, multiple candidate locations can be selected, or the real-time location of the ride-hailing account can be used as the origin for ordering. This allows the ride-hailing user to choose the most suitable origin from the candidate locations based on the passenger's actual situation, or directly use the passenger's real-time location as the origin, providing more flexible travel options. Passengers do not need to manually enter origin information; they can directly confirm their real-time location or select a candidate location, speeding up the ordering process, improving the user experience, and providing more convenient, accurate, and personalized services for both ride-hailing users and passengers, thereby enhancing user satisfaction and improving market competitiveness.

[0142] In some embodiments, step 102 above can also be implemented by performing the following processing: displaying an order template for a ride-hailing account in the ride-hailing service interface; and displaying the edited ride-hailing order in response to the editing operation of the order parameters in the order template, wherein the order parameters include at least one of the following: the vehicle type specified by the ride-hailing account, the driving segment specified by the ride-hailing account, the route preference specified by the ride-hailing account, the payment method specified by the ride-hailing account, the waypoints specified by the ride-hailing account, and the origin specified by the ride-hailing account.

[0143] Here, the editing of order parameters in the order template can be performed by the ride-hailing account, or it can be edited by the ride-hailing account after the ride-hailing order is sent to the ride-hailing account.

[0144] As an example, the vehicle type can be economy, luxury, or comfort; the route can be highway or provincial road; the route preference can be shortest, least congested, or fewest traffic lights; and the payment method can be either the user account or the ride-hailing account. You can also add notes to the order template, such as "elderly person with mobility issues."

[0145] As an example, refer to Figure 5C, which is a third schematic diagram of the ride-hailing service provided in this application embodiment. As shown in the interface on the left side of Figure 5C, the ride-hailing service interface shown in Figure 5C displays two subpages: a real-time ride-hailing subpage 531 and a ride-hailing subpage 532. The ride-hailing subpage 532 displays an order template for ride-hailing orders. The order template displays a starting point field 533, a destination field 534, a vehicle type 535, and a one-click send control 536. The vehicle type 535 displays "economy" and the estimated fare of 41 to 50 yuan. In response to the ride-hailing account's trigger action on vehicle type 535, the ride-hailing service interface shown on the right side of Figure 5C is displayed. As shown in the interface on the right side of Figure 5C, in addition to vehicle type 534, vehicle types 537 and 538 are also displayed. Vehicle type 537 displays a luxury option with an estimated fare of 60 to 80 yuan; vehicle type 538 displays a comfort option with an estimated fare of 51 to 60 yuan. In response to the trigger action on vehicle type 538, the current vehicle type can be updated to comfort.

[0146] Please refer to Figure 3A for further explanation following step 102 above.

[0147] In step 103, in response to the sending trigger operation for the car rental order, a car rental order is sent to the car rental account, wherein the car rental order is used for the car rental account to request car rental services.

[0148] In some embodiments, in response to a ride-hailing account triggering a ride-hailing order, a ride-hailing order is sent to the terminal associated with the ride-hailing account so that it can be displayed in the terminal's application (e.g., an instant messaging client, a ride-hailing client, or a corresponding mini-program) based on the ride-hailing account login.

[0149] In some embodiments, referring to FIG3E, FIG3E is a schematic diagram of the fifth process of the car service processing method provided in the embodiments of this application. The "sending car order to car account" in step 103 above can be implemented through steps 1031 to 1032 in FIG3E, which will be described in detail below.

[0150] In step 1031, multiple sharing controls are displayed, each with a different sharing method.

[0151] In some embodiments, the multiple sharing controls include a QR code sharing control, a link sharing control, and an SMS sharing control.

[0152] As an example, refer to Figure 5D, which is a fourth schematic diagram of the ride-hailing service provided in this application embodiment. As shown in the interface on the left side of Figure 5D, the ride-hailing service interface shown in Figure 5D displays two subpages on the ride-hailing page: the real-time ride-hailing subpage 541 and the ride-hailing page 542. The ride-hailing page 542 displays an order template for ride-hailing orders. The order template displays a starting point field 543, a destination field 544, a vehicle type 545, and a one-click send control 546. The one-click send control 546 provides three sharing controls: a QR code sharing control, a link sharing control, and an SMS sharing control.

[0153] In step 1032, in response to the selection operation for multiple sharing controls, a car rental order is sent to the car rental account according to the sharing method associated with the selected sharing control.

[0154] As an example, continuing to refer to Figure 5D, in response to the triggered operation of the link sharing control in the one-click send control 546, the ride-hailing order can be sent to the ride-hailing account via a link. As shown in the interface in the middle of Figure 5D, the received ride-hailing order 551 is displayed in the ride-hailing service interface of the ride-hailing account.

[0155] This application provides various order sharing methods, such as QR codes, links, or SMS, enabling users associated with ride-hailing accounts to share ride orders with other users of the same account in different ways. This adds a social element, allowing users to easily share trip information with family, friends, or colleagues. Providing multiple sharing options allows users to choose the most suitable method based on recipient preferences and availability, improving sharing convenience. Users can choose the most appropriate sharing method for the current situation, whether using SMS without a network connection or quickly sharing a link on a social network. The diverse sharing methods enhance the user experience, allowing users to choose the most suitable method according to their preferences and habits; it can meet the needs of different users and provide a more comprehensive and convenient service.

[0156] In some embodiments, after the above-mentioned "sending the car rental order to the car rental account", the following processing may be performed: displaying the real-time progress information of the car rental order on the car rental service interface, wherein the real-time progress information includes at least one of the following: current speed, current location, and remaining trip time.

[0157] Here, in addition to displaying the remaining trip time, you can also display information such as the trip time already used, a real-time image of the ride account, and the current trip fare.

[0158] This application embodiment displays real-time progress information of ride-hailing orders on the ride-hailing service interface, enabling users of ride-hailing accounts (passengers) to understand the progress of their trips, while also allowing users of ride-hailing accounts (ride-hailers) to see the progress of their ride-hailing orders in real time, thus enabling timely tracking of passengers' trip information, reducing communication costs and passenger safety risks.

[0159] In some embodiments, referring to FIG3F, FIG3F is a sixth flowchart of the car service processing method provided in the embodiments of this application. After performing the above-mentioned step 103 "sending the car order to the car account", steps 301 to 303 of FIG3F can be performed, which are described in detail below.

[0160] In step 301, the ride-hailing order is displayed on the instant messaging interface between the ride-hailing account and the ride-using account.

[0161] Here, in response to the ride-hailing account sending a ride order to the ride-using account, the ride order can be displayed simultaneously on the instant messaging interfaces of both the ride-hailing account and the ride-using account.

[0162] As an example, referring to Figure 5E, Figure 5E is a fifth schematic diagram of the ride-hailing service provided in an embodiment of this application. As shown in the interface on the left side of Figure 5E, the ride-hailing order sent by the ride-hailing account is displayed in the instant messaging interface of the ride-hailing account shown on the left side of Figure 5E. In response to the ride-hailing account's trigger operation on the ride-hailing order 551, the ride-hailing service interface shown on the right side of Figure 5E is displayed, where the origin and destination 552, vehicle type 553, one-click order control 554, and communication control 555 are displayed. In response to the ride-hailing account's trigger operation on the communication control 555, the user can return to the instant messaging interface.

[0163] In step 302, the order modification request sent by the car rental account is displayed on the instant messaging interface.

[0164] In some embodiments, a communication control can be displayed on the ride-hailing service interface of the ride-hailing account, so that the user associated with the ride-hailing account can send voice or text messages to the ride-hailing account to request modification of the order without leaving the ride-hailing service interface.

[0165] As an example, see 5F, which is a sixth schematic diagram of the ride-hailing service provided in an embodiment of this application. As shown in the interface on the left side of Figure 5F, the ride-hailing order 551 sent by the ride-hailing account to the ride-using account and the order modification information 552 sent by the user account are shown.

[0166] In step 303, in response to the modification operation of the car rental order, a modified car rental order is obtained, wherein the modified car rental order conforms to the order modification request.

[0167] As an example, continuing to refer to Figure 5F, after receiving the order modification information 552 sent by the ride-hailing account, in response to the ride-hailing account's modification operation on the starting point field shown on the right side of Figure 5F, the starting point location A (South Gate) is changed to location C (South Gate).

[0168] In some embodiments, the order modification request includes at least one order parameter specified by the ride-hailing account. The above-mentioned "modification operation on the ride-hailing order to obtain the modified ride-hailing order" can be achieved by performing the following process: modifying the ride-hailing order based on at least one order parameter specified by the ride-hailing account to obtain the modified ride-hailing order.

[0169] Here, based on at least one order parameter specified by the ride-hailing account, the origin or destination of the ride-hailing order can be manually modified in response to the input operation of the ride-hailing account on the input method keyboard.

[0170] In other embodiments, the above-mentioned "modification operation of the car rental order to obtain the modified car rental order" can also be achieved by performing the following process: displaying an order identification control (such as a one-click identification control) in the order modification request; in response to a trigger operation on the order identification control, displaying at least one order parameter specified by the car rental account identified from the order modification request and the modification control; in response to a trigger operation on the modification control, modifying the car rental order based on at least one order parameter specified by the car rental account to obtain the modified car rental order.

[0171] Here, the appropriate recognition model can be invoked to identify the order modification request based on its format (such as text or audio) to obtain the order parameters. Then, based on the identified order parameters, the origin or destination of the ride-hailing order can be modified to obtain the modified ride-hailing order.

[0172] In some embodiments, an order modification request may include at least one of the following order parameters: vehicle type specified by the user account, driving segment specified by the user account, route preference specified by the user account, payment method specified by the user account, waypoints specified by the user account, origin specified by the user account, and destination specified by the user account.

[0173] Here, the starting point specified by the ride-hailing account refers to the updated starting point set by the ride-hailing account, assuming the original order already includes a starting point. The destination specified by the ride-hailing account is the updated destination set by the ride-hailing account, which differs from the destination in the original ride-hailing order. Order modification requests can also include remarks, such as "passenger has mobility issues."

[0174] This application embodiment modifies orders by specifying order parameters based on the ride-hailing account. This allows the ride-hailing user to explicitly specify the order parameters to be modified, such as origin, destination, time, and vehicle type, according to the passenger's needs. This provides greater user control and flexibility, enabling personalized order customization based on user preferences and actual needs, thus meeting the diverse needs of different users. Users directly specify the parameters to be modified, reducing service deviations caused by misunderstandings or automatic identification errors. Alternatively, automatic identification of order parameter modifications in the modification request reduces manual steps for users, saving time. Automatic identification also reduces human intervention and improves the efficiency of order modification. In summary, the above solutions can provide more flexible and intelligent services, meeting users' needs for control and personalized services while improving efficiency and intelligence through automatic identification, thereby enhancing overall service quality and user experience.

[0175] In some embodiments, referring to Figure 3G, which is a schematic diagram of the seventh process of the car rental service processing method provided in this application embodiment. After performing the above step 103, account binding can be performed by performing steps 401 to 402 of Figure 3G, as described in detail below.

[0176] In step 401, if the car-using account and the ride-hailing account are not bound together, an account binding request is sent to the car-using account. The account binding request is used to display the car-using service interface of the car-using account.

[0177] In one embodiment, when the ride-hailing account and the ride-hailing account are not bound together, the terminal of the ride-hailing account sends an account binding request to the terminal of the ride-hailing account via the server. Here, the account binding request may include information about the user associated with the ride-hailing account.

[0178] In step 402, a successful binding notification is received. The successful binding notification is received after the ride-hailing account confirms the binding request. The binding information is displayed in the ride-hailing account's ride-hailing service interface, and the process proceeds to the step of executing the response to the ride-hailing order sending trigger operation and sending the ride-hailing order to the ride-hailing account.

[0179] In one embodiment, the successful binding notification is sent by the server to the terminal device associated with the ride-hailing account after the terminal device associated with the ride-hailing account sends an agreement binding message to the server via the server.

[0180] The method for processing vehicle services on a second terminal device applied to a vehicle account, as provided in the embodiments of this application, will be described in conjunction with exemplary applications and implementations of the terminal provided in the embodiments of this application.

[0181] This application embodiment binds ride-hailing accounts and user accounts, enabling ride-hailing accounts to directly use the account information of the ride-hailing account to place orders and make payments when hailing a ride, reducing the cumbersome process for passengers; at the same time, it allows users associated with the ride-hailing account to know the passenger's trip information in real time, increasing the passenger's safety during the ride.

[0182] Referring to Figure 4A, which is a schematic diagram of the eighth process of the vehicle service processing method provided in the embodiment of this application, taking the terminal of the vehicle account as the execution subject as an example, the steps 501 to 502 shown in Figure 4A will be explained.

[0183] In step 501, a car service interface based on the car account login is displayed, wherein the car service interface includes car orders sent by the car-hailing account, and the car order includes at least the destination of the car account.

[0184] In some embodiments, an instant messaging client may be run on a second terminal device, providing a user service entry point within the client. In response to a user's triggering action on the user service entry point (e.g., a car service mini-program), a car service interface logged in based on the car account is displayed. Alternatively, a car service app may be run directly on the first terminal device, and in response to a user associated with a car account opening the app, a car service interface logged in based on the car account is displayed.

[0185] In step 502, in response to the triggering operation for the ride-hailing order, a ride-hailing service is requested based on the ride-hailing order.

[0186] In some embodiments, in response to a triggered operation for a ride-hailing order, a ride-hailing service is requested from the vehicle service platform server based on the ride-hailing order.

[0187] As an example, referring to Figure 5F, in response to the triggering operation (such as a single click or double click) of the car rental account on the one-click order control 555, a car rental service can be requested from the vehicle service platform server based on the current car rental order.

[0188] In some embodiments, referring to FIG4B, FIG4B is a schematic diagram of the ninth process of the car service processing method provided in the embodiments of this application. The "request car service based on car order" in step 502 above can be implemented by executing steps 5021 to 5022 of FIG4B, which will be described in detail below.

[0189] In step 5021, if the ride-hailing order includes the starting point specified by the ride-hailing account, a ride-hailing service is requested based on the starting point and the destination.

[0190] In some embodiments, when the starting point of the user account has been pre-filled in the ride-hailing order, the user can request ride-hailing services from the vehicle service platform server based on the starting point and destination.

[0191] In step 5022, if the ride-hailing order does not include the starting point specified by the ride-hailing account, a ride-hailing service is requested based on the current location and destination of the ride-hailing account.

[0192] In some embodiments, when the starting point of the user account is not filled in in the ride-hailing order, the user account can request ride-hailing services from the vehicle service platform server based on the current location and destination of the user account.

[0193] In some embodiments, referring to FIG4C, FIG4C is a tenth flowchart of the car rental service processing method provided in the embodiments of this application. The "request car rental service based on the current location and destination of the car rental account" in step 5022 above can be implemented by executing steps 50221 to 50223 of FIG4C, which will be described in detail below.

[0194] In step 50221, the current location of the ride-hailing account is displayed in the starting point field of the ride-hailing order.

[0195] As an example, refer to Figure 6, which is a seventh schematic diagram of the car rental service provided in the embodiment of this application. As shown in the interface on the left side of Figure 6, the car rental service interface in Figure 6 displays a starting point field 611, a destination field 612, a vehicle type 613, and a one-click order control 614. The starting point field 611 displays the current location of the user account, which is location A (South Gate).

[0196] In step 50222, in response to the confirmation operation for the current location, a car rental service is requested based on the current location and destination of the car rental account.

[0197] As an example, continuing to refer to the car service interface on the left side of Figure 6, in response to the car user's confirmation operation of the current starting point and destination, that is, in response to the car user's trigger operation of the one-click order control 614, the car service can be requested based on the current location and destination of the car user displayed in the current car order.

[0198] In step 50223, in response to the modification operation on the current location, the modified current location is displayed, and a ride-hailing service is requested based on the modified current location and the destination.

[0199] As an example, continuing to refer to the car service interface on the left side of Figure 6, in response to the car user's modification operation on the starting point field 611, the car service interface on the right side of Figure 6 displays the updated starting point location A (South Gate) and the new location C (South Gate).

[0200] This application provides different solutions for two scenarios: ride-hailing orders that include a starting point and those that do not. When the ride-hailing order includes a starting point specified by the ride-hailing account, the order can be placed using a preset starting point or by editing the starting point field. When the ride-hailing order does not include a starting point specified by the ride-hailing account, the current location of the ride-hailing account can be used directly as the starting point. This allows for quick order placement by the ride-hailing account, saving on the order placement process and improving the user experience.

[0201] In some embodiments, step 502 above can be implemented by performing the following process: if the ride-hailing order does not include the starting point specified by the ride-hailing account, in response to the editing operation on the starting point field of the ride-hailing order, the edited starting point is displayed, wherein the editing operation includes any of the following: marking the location on the map, indicating the location by voice; requesting ride-hailing service based on the edited starting point and destination.

[0202] Here, once a ride-hailing account receives a ride-hailing order, it can select the starting point by marking a location on a map; alternatively, it can directly indicate the location via voice. Upon receiving the voice signal, the system can perform voice recognition to obtain the selected starting point. After editing the starting point, the user can request ride-hailing services from the vehicle service platform server based on the selected starting point and the destination in the ride-hailing order.

[0203] In some embodiments, step 502 above can be implemented by performing the following processing: in response to an edit operation on the starting point field of a ride-hailing order, displaying at least one candidate location, wherein, when there are multiple candidate locations, the sorting factors for at least one candidate location include any one of the following: the time interval of historical use, descending order of historical use frequency, the degree of matching with the order parameters specified by the ride-hailing account (or ride-hailing account), and the probability that multiple candidate points of interest in the current environment of the ride-hailing account are selected; in response to a selection operation on at least one candidate location, using the selected candidate location as the starting point, requesting ride-hailing services based on the starting point and destination.

[0204] When there are multiple candidate locations for the starting point, if the ranking factor is the time interval of historical usage, the location with the shortest historical usage interval will be ranked first. If the ranking factor is descending order of historical usage frequency, the candidate location with the highest historical usage frequency will be ranked first, and those with lower historical usage frequency will be ranked later. If the ranking factor is the degree of matching with the order parameters specified by the ride-hailing account, the candidate location with the highest degree of matching with the order parameters specified by the ride-hailing account will be ranked first, and those with lower degree of matching with the order parameters specified by the ride-hailing account will be ranked later. If the ranking factor is the probability of multiple candidate points of interest being selected in the current environment of the ride-hailing account, the candidate location with the highest probability will be ranked first.

[0205] Here, the historical usage time interval refers to the time interval between the historical usage time of each candidate position and the current time. For example, if the historical usage time of candidate position 1 is 10:05 and the current time is 10:55, then the historical usage time interval of candidate position 1 is 50 minutes.

[0206] As an example, if the sorting factor is descending order of historical usage frequency, and in the past 5 days, candidate position 1 has been used 7 times, candidate position 2 has been used 1 time, and candidate position 3 has been used 4 times, then the order of the three candidate positions is candidate position 1, candidate position 3, and candidate position 2.

[0207] In some embodiments, the above-described selection operation for at least one candidate position may start from the first candidate position or from any candidate position selected by the user.

[0208] This application embodiment allows users to select from multiple candidate locations using their ride-hailing account. The selected candidate location serves as the starting point, and a ride-hailing service is requested based on the starting point and destination. Users do not need to manually enter complex addresses; they can simply select from the candidate locations, greatly simplifying the operation process and improving the user experience. At the same time, quickly selecting the starting point can reduce user waiting time and improve order processing speed. Selecting candidate locations can reduce incorrect order assignments or trip delays caused by incorrect address input and can also ensure the accuracy of the starting point information, providing users with more precise services.

[0209] In some embodiments, referring to FIG4D, FIG4D is a schematic flowchart of the eleventh step of the car service processing method provided in the embodiments of this application. Before executing the above-mentioned step 502 "request car service based on car order", the processing of steps 601 to 602 in FIG4D can be executed, which will be described in detail below.

[0210] In step 601, in response to the pre-modification operation of the ride-hailing account on the ride-hailing order, an order modification request is generated and sent to the ride-hailing account. The order modification request includes at least one of the following order parameters: vehicle type specified by the ride-hailing account, driving segment specified by the ride-hailing account, route preference specified by the ride-hailing account, payment method specified by the ride-hailing account, waypoints specified by the ride-hailing account, origin specified by the ride-hailing account, and destination specified by the ride-hailing account.

[0211] Here, the vehicle type can be economy, luxury, or comfort; the route can be highway or provincial road; the route preference can be the shortest route, the least congested route, and the route with the fewest traffic lights; the payment method can be either the user account or the ride-hailing account. You can also add notes to the order template, such as "elderly person with mobility issues."

[0212] In step 602, the modified ride-hailing order is received from the ride-hailing account. The modified ride-hailing order is modified and sent by the ride-hailing account according to the order modification request, and the modified order is displayed on the instant messaging interface of the user account. The modified ride-hailing order conforms to the order modification request.

[0213] As an example, if the ride-hailing account requests to change the starting position 1 to position 2 in the ride-hailing order, then the starting position in the modified ride-hailing order sent by the ride-hailing account will be position 2.

[0214] In some embodiments, before performing the "request car service based on car service order" step 502 above, the following processing may be performed: in response to the car service account's modification operation on the car service order, a modified car service order is obtained, wherein the order parameters modified by the modification operation include at least one of the following: the vehicle type specified by the car service account, the driving segment specified by the car service account, the route preference specified by the car service account, the payment method specified by the car service account, the waypoints specified by the car service account, the origin specified by the car service account, and the destination specified by the car service account; wherein, when modifying the origin or destination, the modification operation method includes any one of the following: marking the location on the map, or indicating the location via voice.

[0215] Here, the vehicle type can be economy, luxury, or comfort; the route can be highway or provincial road; route preferences can be shortest, least congested, or fewest traffic lights; payment methods can be chosen from the user account or the ride-hailing account. Notes can also be added to the order template, such as for elderly people with mobility issues. Once the user account receives a ride order, they can select the starting point by marking a location on a map or by directly indicating the location via voice. The system can then recognize the voice signal to obtain the selected starting point. After editing the starting point, the user can request ride service from the vehicle service platform server based on the selected starting point and the destination in the ride order.

[0216] The car rental service processing method provided in this application embodiment supports the modification of order parameters of car rental orders by car rental accounts, so that users can personalize the order according to their own needs. After placing an order, users can adjust the trip according to the actual situation, such as changing the origin, destination or driving route, making the service more flexible. This enhances the user's sense of control over the service and improves satisfaction. After the order is generated, users can verify and modify the order parameters, reducing trip problems caused by inaccurate information.

[0217] In some embodiments, referring to FIG4E, FIG4E is a schematic diagram of the twelfth process of the car service processing method provided in the embodiments of this application. Before executing the above-mentioned step 502 "request car service based on car order", the processing of steps 701 to 702 in FIG4E can be executed, which will be described in detail below.

[0218] In step 701, when a car rental order includes multiple destinations, the multiple destinations are displayed in the car rental service interface of the car rental account. The sorting factors for the multiple destinations include any one of the following: descending order of historical usage frequency, and ascending order of distance from the current location of the car rental account.

[0219] In some embodiments, when a ride-hailing order includes multiple destinations specified by the ride-hailing account, if the sorting factor is descending order of historical usage frequency, the destination with the highest historical usage frequency will be ranked first, and the destinations with the lowest historical usage frequency will be ranked later. If the sorting factor is ascending order of distance from the current location of the ride-hailing account, the destination with the shortest distance from the current location of the ride-hailing account will be ranked first, and the destinations with the largest distance from the current location of the ride-hailing account will be ranked later.

[0220] As an example, if the sorting factor is descending order of historical usage frequency, and in the past 5 days, destination 1 has been used 7 times, destination 2 has been used 1 time, and destination 3 has been used 4 times, then the order of the three destinations would be destination 1, destination 3, and destination 2. If the sorting factor is ascending order of distance from the current location of the user account, for example, destination 4 is 10 meters away from the current location of the user account, destination 5 is 5 meters away, and destination 6 is 8 meters away, then the order of the three destinations would be destination 5, destination 6, and destination 4.

[0221] In step 702, in response to the user account's selection of multiple destinations, the selected destination among the multiple terminals is taken as the target destination, and the process proceeds to the step of requesting a ride-hailing service based on the ride-hailing order.

[0222] In some embodiments, the user account's selection of multiple destinations can be either selecting the first destination as the target destination or selecting any destination as the target destination, and then requesting the vehicle service platform server based on the selected target destination.

[0223] This application embodiment supports ride-hailing accounts in selecting from multiple displayed destinations and requesting ride-hailing services based on the selected destinations. This allows ride-hailing users to choose one or more destinations from multiple preset destinations according to the passenger's needs, increasing the flexibility and personalization of the service. By allowing users to select destinations, demand and supply can be matched more effectively, optimizing the allocation of vehicle resources and reducing empty runs and waiting time. Supporting ride-hailing users to select from a list of pre-selected destinations reduces the errors that may occur when manually entering destinations.

[0224] In summary, this application embodiment responds to the editing operation of the ride-hailing account on the ride-hailing service interface by displaying the edited ride-hailing order, and responds to the ride-hailing account's sending trigger operation for the ride-hailing order by sending the ride-hailing order to the ride-hailing account, so that the ride-hailing account can request ride-hailing service based on the ride-hailing order; that is, the ride-hailing account only needs to edit the ride-hailing order in advance and send the edited ride-hailing order to the ride-hailing account, so that the ride-hailing account can place orders on demand in real time based on the pre-set ride-hailing order with a destination according to its own needs. Compared with related technologies, which require the passenger and the ride-hailing user to maintain real-time communication in order to place an accurate order, this can effectively reduce communication costs and improve the flexibility of ride-hailing service.

[0225] The ride-hailing service processing method provided in this application is applicable to any scenario that requires assistance in hailing a ride, such as hailing a ride for the elderly, hailing a ride for minors, or hailing a ride for other people with disabilities.

[0226] The following will describe an exemplary application of the embodiments of this application in a real-world application scenario.

[0227] In terms of transportation, ride-hailing has become an increasingly popular mode of transport. In many cases, it's necessary for the user associated with the ride-hailing account to book a ride on behalf of the user associated with the ride-hailing account. For example, elderly people (the users associated with the ride-hailing accounts) often struggle with online ride-hailing due to unfamiliarity with electronic devices and the complex procedures. They may not know how to fill in the origin and destination, or the process of entering and selecting the appropriate origin and destination is too complicated, making it difficult for many elderly people to place an order independently. In response, some elderly people choose to have family members (the users associated with the ride-hailing accounts) book rides for them online. However, remote ride-hailing cannot accurately pinpoint the elderly person's location, leading to significant communication costs when the elderly person meets the driver. Furthermore, the real-time nature of ride-hailing also presents inconveniences for remote booking, as family members must respond to the order constantly for a satisfactory experience.

[0228] In related technologies, ride-hailing on behalf of others involves real-time ordering. Typically, family members fill in the origin, destination, and passenger information remotely. This requires family members to first confirm the passenger's pick-up time before placing the order remotely. Therefore, real-time communication between the passenger and the person ordering the ride is necessary to obtain pick-up point and pick-up time information before an accurate order can be placed, resulting in high communication costs. However, ride orders generated by this technology are real-time, with the order time determined by the person ordering the ride. Passengers cannot flexibly adjust the order time based on real-time circumstances. For example, if they leave a few minutes late, they can order later, or if they need to go to a certain place earlier but haven't confirmed the time in advance, family members cannot flexibly adjust the ride-hailing time according to the elderly person's travel needs.

[0229] To address the aforementioned issues, this application provides a ride-hailing service processing method that allows family members to pre-fill in the origin and destination and share it with the elderly. This effectively solves the problems faced by the elderly in filling in the origin and destination information when booking a ride online, as well as their unfamiliarity with electronic devices and online ride-hailing procedures. It enables the elderly to place orders on demand, using their current location, making it flexible and allowing them to place orders in real time without relying on family members. This allows the elderly to place orders independently and flexibly with the help of their family members.

[0230] The following is a detailed description of the vehicle service processing method provided in the embodiments of this application.

[0231] First, when a passenger uses the ride-hailing service for the first time, they need to authorize and bind their account, linking the ride-hailing and passenger accounts. The ride-hailing passenger is allowed to use their account information to place an order.

[0232] Secondly, add a function module to the ride-hailing service interface of the travel platform to allow users (such as family members of the elderly) to pre-fill their origin and destination information. This could be displayed on a separate ride-hailing page in the ride-hailing service interface, or on a ride-hailing subpage within the ride-hailing page of the ride-hailing service interface.

[0233] Then, in response to the user's editing of the ride order, the user's travel route can be set. For example, when the family member fills in the origin and destination, the pick-up point can be agreed upon with the elderly before filling in the information. Alternatively, the user can choose the elderly's real-time location when they book the ride as the origin, or choose to use a fixed origin, making the ride service more flexible and convenient.

[0234] After editing a ride-hailing order, the order information can be stored on the server. Then, a sharing control is displayed on the user's ride-hailing service interface. In response to the user's activation of the sharing control, the ride-hailing order, including pre-filled origin and destination information, is shared with the passenger via the server. For example, in response to a family member's activation of the sharing control, the ride-hailing order can be shared with an elderly person via QR code, link, or SMS.

[0235] Finally, when a passenger receives the initial ride order from the caller, in response to the passenger's first interaction with the card or link shared by the caller, an account binding request is sent to the server. The server then authorizes the account binding and location. Upon successful binding, the ride order is displayed on the passenger's ride service interface. The passenger's ride service page displays the origin and destination information, as well as a one-click order control. Clicking the one-click order control allows the passenger to immediately place an order and call a driver. The page also displays the driver's order acceptance status and trip progress.

[0236] As an example, refer to Figure 7, which is a schematic diagram of account binding provided in an embodiment of this application. As shown in Figure 7, the ride-hailing service interface of the ride-hailing account displays account binding prompt information 701, an agreement signing control 702, and a function activation control 703. In response to the ride-hailing account's triggering operation on the agreement signing control 702 and the function activation control 703, the account binding process between the ride-hailing account and the ride-hailing account can be completed.

[0237] Since the passenger's account is linked to the ride-hailing user's account, the passenger places the order using the ride-hailing user's information. Therefore, while the passenger can see the trip's progress, the ride-hailing user's page can also view the real-time progress of the ride order. This can be achieved by using WebSocket or long polling technology to push order status and trip progress information to both the ride-hailing and passenger pages in real time. This method allows both the ride-hailing and passenger to understand the trip information, reducing communication costs and safety risks associated with ride-hailing.

[0238] Taking the example of a ride-hailing order template displayed in the ride-hailing subpage of the ride-hailing page in the ride-hailing service interface, see Figure 8A. Figure 8A is the eighth schematic diagram of the ride-hailing service provided in this application embodiment. As shown in the interface on the left side of Figure 8A, the ride-hailing page of the ride-hailing service interface shown in Figure 8A displays two subpages, namely the real-time ride-hailing subpage 801 and the ride-hailing subpage 802. The ride-hailing subpage 802 displays the order template for ride-hailing orders, which displays the origin field 803 and the destination field 804. In response to the editing operation on the origin field 803 and the destination field 804, the edited origin and destination are displayed in the interface on the right side of Figure 8A. The origin is location A (South Gate), and the destination is location B (East Gate 2). Vehicle information 805 is also displayed, including vehicle type and estimated fare, as well as an order sending control 806.

[0239] In response to the ride-hailing account's trigger operation on the order sending control 806, the ride-hailing order is sent to the ride-hailing account. Referring to Figure 8B, which is a ninth schematic diagram of the ride-hailing service provided in this embodiment, as shown in the interface on the left side of Figure 8B, the received ride-hailing order 811 is displayed on the ride-hailing account's ride-hailing service interface, including the origin and destination pre-set by the ride-hailing account. In response to the ride-hailing account's trigger operation on the ride-hailing order 811, the interface on the right side of Figure 8B is displayed, showing the order's origin and destination 812, vehicle information 813, and a one-click order control 814. In response to the ride-hailing account's trigger operation on the one-click order control 814, an order can be quickly placed.

[0240] Taking the example of a ride-hailing order template displayed on a separate ride-hailing page within the ride-hailing service interface, see Figure 8C, which is the tenth schematic diagram of the ride-hailing service provided in this embodiment. As shown in the interface on the left side of Figure 8C, the ride-hailing page of the ride-hailing service interface shown in Figure 8C displays a ride-hailing order template, which includes a starting point field 821 and a destination field 822. In response to editing operations on the starting point field 821 and the destination field 822 in the order template, the interface in the middle of Figure 8C displays an editing control 823 for the destination field, an editing control 824 for the starting point field, and a candidate location list 825. The editing control 824 for the starting point field prompts the user to select the location of the elderly person as the starting point. After editing is completed, the interface on the right side of Figure 8C displays the start and end points of the ride-hailing order 826, vehicle information 827, a sharing control 828, and a one-click order control 829. In response to the ride-hailing account's triggering operation on the one-click order control 829, an order can be placed quickly; in response to the ride-hailing account's triggering operation on the sharing control 828, the edited ride order can be sent to the ride-hailing account.

[0241] Referring to Figure 8D, which is the eleventh schematic diagram of the car-hailing service provided in this application embodiment, as shown in the interface on the left side of Figure 8D, a location authorization prompt box 841 is displayed on the car-hailing service interface of the car-hailing account, including two function keys: agree to authorization and disagree to authorization. In response to the car-hailing account triggering the agree function key, the interface in the middle of Figure 8D is displayed. The interface on the right side of Figure 8D displays the order's origin and destination 842, vehicle information 843, and a one-click order control 844. In response to the car-hailing account triggering the one-click order control 844, an order can be quickly placed, and the car-hailing service interface on the right side of Figure 8D is displayed. The interface displays vehicle information 845, including the driver's estimated arrival time and license plate number, and also displays a cancel order control 846 and a contact control 847. In response to the car-hailing account triggering the cancel order control 846, the current order can be canceled; in response to the car-hailing account triggering the contact control 847, the driver picking up the passenger can be contacted.

[0242] The following is a detailed description of the process flow of the car rental service processing method provided in the embodiments of this application. Referring to Figure 9, which is a schematic diagram of the thirteenth step of the car rental service processing method provided in the embodiments of this application, the process flow will be described in detail with reference to steps 901 to 921 shown in Figure 9.

[0243] In step 901, terminal 400-1 receives a login request for a ride-hailing account and executes the processing in step 902.

[0244] In step 902, server 200 sends the received login verification request to database 500.

[0245] In some embodiments, when server 200 receives a login verification request, it queries database 500 for the login information of the user associated with the ride-hailing account. Upon successful verification of the login information retrieved from database 500, step 903 is executed.

[0246] In step 903, terminal 400-1 receives the login verification response returned by database 500.

[0247] In some embodiments, in response to successful login information verification from database 500, server 200 sends a login verification success response to terminal 400-1.

[0248] In step 904, terminal 400-1, in response to receiving an account binding request for a ride-hailing account, sends the received account binding request to server 200. Then, the process proceeds to step 905.

[0249] In step 905, server 200 stores the received binding information in database 500. Then, it proceeds to step 906.

[0250] In step 906, terminal 400-1 receives a binding success response from database 200 in response to the successful storage of binding information in the database.

[0251] In step 907, in response to receiving the input operation of the pre-filled information of the ride-hailing account, terminal 400-1 sends the pre-filled information to server 200 and proceeds to the processing of step 908.

[0252] In step 908, server 200 stores the pre-filled order information of the ride-hailing account sent by terminal 400-1 into database 500. In response to successful storage, step 909 is executed.

[0253] In step 909, terminal 400-1 receives a response from database 500 indicating that the information has been successfully stored.

[0254] In step 910, in response to receiving a sharing request from a ride-hailing account, terminal 400-1 sends a link generation request to database 500 via server 200.

[0255] In step 911, terminal 400-1, in response to receiving the sharing link returned by database 500, performs the processing in step 912.

[0256] In step 912, in response to receiving the sharing link from the ride-hailing account, terminal 400-1 sends the link to the ride-hailing account of terminal 400-2 via server 200.

[0257] In step 913, when the user account of terminal 400-2 receives the sharing link sent by the ride-hailing account, it responds to the user account's operation of opening the link and proceeds to the processing of step 914.

[0258] In step 914, in response to receiving the first authorization verification request for the ride-hailing account, terminal 400-1 queries the authorization information from database 500 via server 200. In response to successful verification, it proceeds to the processing of step 915.

[0259] In step 915, terminal 400-1 receives a notification of authorization success response returned by database 500.

[0260] In step 916, when terminal 400-2 receives a request from the vehicle user account to view pre-filled information, it sends the request to server 200 and proceeds to step 917 for processing.

[0261] In step 917, server 200 sends the received request to view pre-filled information to database 500, retrieves the pre-filled information from database 500, receives the pre-filled information sent by database 500, and displays it on the vehicle service interface of terminal 400-2.

[0262] In step 918, terminal 400-2, in response to receiving a one-click order request from the car-using account, sends the one-click order request to database 500 via server 200, and proceeds to the processing of step 919.

[0263] In step 919, in response to the database 500 successfully responding to the order request, terminal 400-2 receives a notification of successful order response from the database.

[0264] In step 920, in response to receiving a request from a car-using account to view the order status, terminal 400-1 sends the request to view the order status to database 500 via server 200, and proceeds to the processing of step 921.

[0265] In step 921, in response to the database 500 successfully responding to the request to view the order status, terminal 400-1 receives the order status returned by the database and displays the order status on the car service interface.

[0266] The ride-hailing service processing method provided in this application has wide application value in various scenarios such as daily life, medical visits, visiting relatives and friends, emergencies, tourism, and community activities, and can achieve the following technical effects: Improving the convenience of travel for passengers (such as the elderly): It supports pre-filled information by the person booking the ride (family member) and provides a one-click ordering function. Passengers do not need to remember complex addresses and route information; they only need to complete the simple operation of confirmation and ordering to complete the travel arrangements, reducing complicated operation steps. Enhancing safety: Through real-time push technology, family members and the elderly can check the trip progress in real time. Family members can understand the elderly's travel status at any time, and communication costs and safety risks can be reduced. Improving the flexibility of ride-hailing services: It does not require real-time reliance on family members to place orders. As long as it is communicated in advance, the elderly can place orders independently when using the service, without any obstacles. The ordering time and location are very flexible, and the operation is simple, reducing communication costs and time costs for both parties.

[0267] The following continues to describe the exemplary structure of the vehicle service processing device 455-1 provided in the embodiments of this application as a software module. In some embodiments, as shown in FIG2A, the software module stored in the vehicle service processing device 455-1 in the memory 450-1 may include:

[0268] The first display module 4551-1 is used to display the ride-hailing service interface based on the ride-hailing account login.

[0269] The second display module 4552-1 is used to respond to the editing operation on the car service interface and display the edited car order, wherein the car order includes at least the endpoint of the car account.

[0270] The order sending module 4553-1 is used to send a car rental order to the car rental account in response to the sending trigger operation for the car rental order. The car rental order is used by the car rental account to request car rental services.

[0271] In some embodiments, the second display module 4552-1 is further configured to display an order template for a car-use account in the car-use service interface; in response to an editing operation on the destination field in the order template, the edited destination is displayed in the order template, wherein the order template including the destination is a car-use order.

[0272] In some embodiments, the second display module 4552-1 is further configured to display a candidate list in response to a trigger operation on the destination field in the order template, wherein the candidate list includes at least one candidate location, and when the number of at least one candidate location is multiple, the sorting factor used includes any one of the following: descending order of historical usage frequency, ascending order of distance from the current location of the ride account; in response to a selection operation on at least one candidate location, the selected candidate location is used as the destination and the selected destination is displayed in the order template.

[0273] In some embodiments, when multiple endpoints are formed during editing, the multiple endpoints are used for vehicle accounts to select, and the sorting factors for the multiple endpoints include any one of the following: descending order of historical usage frequency, ascending order of distance from the current location of the vehicle account.

[0274] In some embodiments, the second display module 4552-1 is further configured to display the edited starting point in an order template including the destination in response to an editing operation on the starting point field in the order template, wherein the order template including the starting point and the destination serves as an updated ride order.

[0275] In some embodiments, the second display module 4552-1 is further configured to display at least one candidate location in response to an editing operation on the starting point field in the order template, wherein, when there are multiple candidate locations, the sorting factor for the at least one candidate location includes any one of the following: descending order of historical usage frequency, ascending order of distance from the current location of the ride account; in response to a selection operation on the at least one candidate location, the selected candidate location is used as the starting point and the selected starting point is displayed in the order template including the destination.

[0276] In some embodiments, the starting point field in a ride-hailing order is blank. The starting point field is used to take the current position of the ride-hailing account as the starting point when the ride-hailing order is triggered by the ride-hailing account.

[0277] In some embodiments, the order template is displayed on a separate ride-hailing page in the ride-hailing service interface, or the order template is displayed on a ride-hailing subpage of the ride-hailing page in the ride-hailing service interface. The ride-hailing page also includes a real-time ride-hailing subpage, which is used to request ride-hailing services at the current moment.

[0278] In some embodiments, the order sending module 4553-1 is further configured to display multiple sharing controls, wherein the multiple sharing controls have different sharing methods; in response to a selection operation for the multiple sharing controls, a car rental order is sent to the car rental account according to the sharing method associated with the selected sharing control.

[0279] In some embodiments, the order sending module 4553-1 is further configured to display real-time progress information of the ride-hailing order on the ride-hailing service interface, wherein the real-time progress information includes at least one of the following: current speed, current location, and remaining trip time.

[0280] In some embodiments, the order sending module 4553-1 is further configured to display the ride-hailing order on the instant messaging interface between the ride-hailing account and the ride-using account; display the order modification request sent by the ride-using account on the instant messaging interface; and obtain the modified ride-hailing order in response to the modification operation on the ride-hailing order, wherein the modified ride-hailing order conforms to the order modification request.

[0281] In some embodiments, the order modification request includes at least one order parameter specified by the vehicle user account. The order sending module 4553-1 is further configured to modify the vehicle order based on the at least one order parameter specified by the vehicle user account to obtain the modified vehicle order; or, the order modification request displays an order identification control. In response to a trigger operation on the order identification control, the at least one order parameter specified by the vehicle user account identified from the order modification request and the modification control are displayed. In response to a trigger operation on the modification control, the vehicle order is modified based on the at least one order parameter specified by the vehicle user account to obtain the modified vehicle order.

[0282] In some embodiments, the order sending module 4553-1 is further configured to include at least one of the following order parameters in the order modification request: vehicle type specified by the vehicle user account, driving segment specified by the vehicle user account, route preference specified by the vehicle user account, payment method specified by the vehicle user account, waypoint specified by the vehicle user account, starting point specified by the vehicle user account, and destination specified by the vehicle user account.

[0283] In some embodiments, the order sending module 4553-1 is further configured to send an account binding request to the car user account when the car user account and the ride-hailing account are not bound, wherein the account binding request is used to display in the car user account's car service interface; receive a binding success notification, wherein the binding success notification is received after the car user account confirms the binding request; display the binding information in the ride-hailing account's car service interface; and proceed to the step of sending a car service order to the car user account in response to the sending trigger operation for the car service order.

[0284] In some embodiments, the second display module 4552-1 is further configured to display an order template for a ride-hailing account in the ride-hailing service interface; in response to an editing operation on the order parameters in the order template, display the edited ride-hailing order, wherein the order parameters include at least one of the following: the vehicle type specified by the ride-hailing account, the driving segment specified by the ride-hailing account, the route preference specified by the ride-hailing account, the payment method specified by the ride-hailing account, the waypoints specified by the ride-hailing account, and the origin specified by the ride-hailing account.

[0285] The following continues to describe the exemplary structure of the vehicle service processing device 455-2 provided in the embodiments of this application as a software module. In some embodiments, as shown in FIG2B, the software module stored in the vehicle service processing device 455-2 in the memory 450-2 may include:

[0286] The third display module 4551-2 is used to display the car service interface based on the car account login. The car service interface includes car orders sent by the car-hailing account, and the car order includes at least the destination of the car account.

[0287] The request service module 4552-2 is used to respond to the triggered operation for the ride-hailing order and request the ride-hailing service based on the ride-hailing order.

[0288] In some embodiments, the request service module 4552-2 is further configured to request a ride service based on the origin and destination when the ride order includes the origin specified by the ride-hailing account; and to request a ride service based on the current location and destination of the ride-hailing account when the ride order does not include the origin specified by the ride-hailing account.

[0289] In some embodiments, the request service module 4552-2 is further configured to display the current location of the ride-hailing account in the starting point field of the ride-hailing order; in response to a confirmation operation for the current location, request ride-hailing service based on the current location and destination of the ride-hailing account; in response to a modification operation for the current location, display the modified current location, and request ride-hailing service based on the modified current location and destination.

[0290] In some embodiments, the request service module 4552-2 is further configured to, in response to the pre-modification operation of the ride-hailing account on the ride-hailing order, generate an order modification request and send the order modification request to the ride-hailing account, wherein the order modification request includes at least one of the following order parameters: vehicle type specified by the ride-hailing account, driving segment specified by the ride-hailing account, route preference specified by the ride-hailing account, payment method specified by the ride-hailing account, waypoints specified by the ride-hailing account, origin specified by the ride-hailing account, and destination specified by the ride-hailing account; receive the modified ride-hailing order sent by the ride-hailing account, wherein the modified ride-hailing order is modified and sent by the ride-hailing account according to the order modification request, and the modified order is displayed on the instant messaging interface of the user account, wherein the modified ride-hailing order conforms to the order modification request.

[0291] In some embodiments, the request service module 4552-2 is further configured to respond to the modification operation of the car rental order by the car rental account and obtain the modified car rental order, wherein the order parameters modified by the modification operation include at least one of the following: the vehicle type specified by the car rental account, the driving segment specified by the car rental account, the route preference specified by the car rental account, the payment method specified by the car rental account, the waypoints specified by the car rental account, the origin specified by the car rental account, and the destination specified by the car rental account; wherein, when modifying the origin or the destination, the modification operation method includes any one of the following: marking the location on the map, or indicating the location by voice.

[0292] In some embodiments, the request service module 4552-2 is further configured to display multiple destinations in the user service interface of the car rental account when the car rental order includes multiple destinations, wherein the sorting factors of the multiple destinations include any one of the following: descending order of historical usage frequency, ascending order of distance from the current location of the car rental account; in response to the car rental account's selection operation of multiple destinations, the selected destination among the multiple terminals is taken as the target destination, and the process proceeds to the step of requesting car rental service based on the car rental order.

[0293] In some embodiments, the request service module 4552-2 is further configured to, in response to an editing operation on the starting point field of the ride-hailing order, display the edited starting point when the ride-hailing order does not include the starting point specified by the ride-hailing account. The editing operation may be performed in any of the following ways: marking the location on a map, indicating the location via voice, or requesting ride-hailing service based on the edited starting point and destination.

[0294] In some embodiments, the request service module 4552-2 is further configured to, in response to an edit operation on the starting point field of a ride-hailing order, display at least one candidate location, wherein, when there are multiple candidate locations, the sorting factors for the at least one candidate location include any one of the following: the time interval of historical use, descending order of historical use frequency, the degree of matching with the order parameters specified by the ride-hailing account, and the probability of multiple candidate points of interest being selected in the current environment of the ride-hailing account; in response to a selection operation on at least one candidate location, the selected candidate location is used as the starting point, and a ride-hailing service is requested based on the starting point and the destination.

[0295] This application provides a computer program product, which includes a computer program or computer-executable instructions stored in a computer-readable storage medium. The processor of an electronic device reads the computer-executable instructions from the computer-readable storage medium and executes the computer-executable instructions, causing the electronic device to perform the vehicle service processing method described above in this application.

[0296] This application provides a computer-readable storage medium storing computer-executable instructions or computer programs. When the computer-executable instructions or computer programs are executed by a processor, the processor will execute the vehicle service processing method provided in this application, such as the vehicle service processing method shown in FIG3A or FIG4A.

[0297] In some embodiments, the computer-readable storage medium may be a memory such as RAM, ROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or it may be a variety of devices including one or any combination of the above-mentioned memories.

[0298] In some embodiments, computer-executable instructions may take the form of programs, software, software modules, scripts, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as stand-alone programs or as modules, components, subroutines, or other units suitable for use in a computing environment.

[0299] As an example, computer-executable instructions may, but do not necessarily, correspond to files in a file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple co-located files (e.g., files that store one or more modules, subroutines, or code sections).

[0300] As an example, computer-executable instructions can be deployed to execute on a single electronic device, or on multiple electronic devices located at one location, or on multiple electronic devices distributed across multiple locations and interconnected via a communication network.

[0301] In summary, this application embodiment responds to the editing operation of the ride-hailing account on the ride-hailing service interface by displaying the edited ride-hailing order, and responds to the ride-hailing account's sending trigger operation for the ride-hailing order by sending the ride-hailing order to the ride-hailing account, so that the ride-hailing account can request ride-hailing service based on the ride-hailing order; that is, the ride-hailing account only needs to edit the ride-hailing order in advance and send the edited ride-hailing order to the ride-hailing account, so that the ride-hailing account can place orders on demand in real time based on the pre-set ride-hailing order with a destination according to its own needs. Compared with related technologies, which require the passenger and the ride-hailing user to maintain real-time communication in order to place an accurate order, this can effectively reduce communication costs and improve the flexibility of ride-hailing service.

[0302] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, and improvements made within the spirit and scope of this application are included within the scope of protection of this application.

Claims

1. A method for processing ride-hailing services, characterized in that, The method includes: displaying a ride-hailing service interface based on a ride-hailing account login; in response to an editing operation on the ride-hailing service interface, displaying an edited ride-hailing order, wherein the ride-hailing order includes at least the endpoint of the ride-hailing account; and in response to a sending trigger operation for the ride-hailing order, sending the ride-hailing order to the ride-hailing account, wherein the ride-hailing order is used for the ride-hailing account to request ride-hailing services.

2. The method according to claim 1, characterized in that, The step of displaying the edited car rental order in response to the editing operation on the car rental service interface includes: displaying an order template for the car rental account on the car rental service interface; and displaying the edited destination in the order template in response to the editing operation on the destination field in the order template, wherein the order template including the destination serves as the car rental order.

3. The method according to claim 2, characterized in that, The step of displaying the edited endpoint in the order template in response to an edit operation on the endpoint field in the order template includes: displaying a candidate list in response to a trigger operation on the endpoint field in the order template, wherein the candidate list includes at least one candidate location, and when the number of the at least one candidate location is multiple, the sorting factor used includes any one of the following: descending order of historical usage frequency, ascending order of distance from the current location of the ride-hailing account; and displaying the selected endpoint in the order template in response to a selection operation on the at least one candidate location.

4. The method according to claim 2 or 3, characterized in that, When multiple endpoints are selected in the editing process, the multiple endpoints are used for the user account to select, and the sorting factors of the multiple endpoints include any one of the following: descending order of historical usage frequency, and ascending order of distance from the current location of the user account.

5. The method according to claim 2, characterized in that, The method further includes: in response to an edit operation on the start point field in the order template, displaying the edited start point in the order template including the end point, wherein the order template including the start point and the end point serves as an updated ride-hailing order.

6. The method according to claim 5, characterized in that, The step of displaying the edited starting point in the order template including the ending point in response to an editing operation on the starting point field in the order template includes: displaying at least one candidate location in response to an editing operation on the starting point field in the order template, wherein, when there are multiple candidate locations, the sorting factor for the at least one candidate location includes any one of the following: descending order of historical usage frequency, ascending order of distance from the current location of the ride-hailing account; and displaying the selected starting point as the starting point in the order template including the ending point in response to a selection operation on the at least one candidate location.

7. The method according to claim 2, characterized in that, The starting point field in the ride-hailing order is blank. The starting point field is used to take the current position of the ride-hailing account as the starting point when the ride-hailing order is triggered by the ride-hailing account.

8. The method according to any one of claims 2 to 7, characterized in that, The order template is displayed on a separate ride-hailing page in the ride-hailing service interface, or the order template is displayed on a ride-hailing subpage of the ride-hailing page in the ride-hailing service interface. The ride-hailing page also includes a real-time ride-hailing subpage, which is used to request ride-hailing services at the current moment.

9. The method according to any one of claims 1 to 7, characterized in that, Sending the car rental order to the car rental account includes: displaying multiple sharing controls, wherein the multiple sharing controls have different sharing methods; and in response to a selection operation on the multiple sharing controls, sending the car rental order to the car rental account according to the sharing method associated with the selected sharing control.

10. The method according to any one of claims 1 to 7, characterized in that, After sending the car rental order to the car rental account, the method further includes: displaying the real-time progress information of the car rental order on the car rental service interface, wherein the real-time progress information includes at least one of the following: current speed, current location, and remaining trip time.

11. The method according to any one of claims 1 to 7, characterized in that, After sending the ride-hailing order to the ride-hailing account, the method further includes: displaying the ride-hailing order on the instant messaging interface between the ride-hailing account and the ride-hailing account; displaying the order modification request sent by the ride-hailing account on the instant messaging interface; and obtaining the modified ride-hailing order in response to the modification operation on the ride-hailing order, wherein the modified ride-hailing order conforms to the order modification request.

12. The method according to claim 11, characterized in that, The order modification request includes at least one order parameter specified by the ride-hailing account. Modifying the ride-hailing order to obtain a modified ride-hailing order includes: modifying the ride-hailing order based on the at least one order parameter specified by the ride-hailing account to obtain a modified ride-hailing order; or, displaying an order identification control in the order modification request, and in response to a trigger operation on the order identification control, displaying the at least one order parameter specified by the ride-hailing account identified from the order modification request and the modification control, and in response to a trigger operation on the modification control, modifying the ride-hailing order based on the at least one order parameter specified by the ride-hailing account to obtain a modified ride-hailing order.

13. The method according to claim 11 or 12, characterized in that, The order modification request includes at least one of the following order parameters: the vehicle type specified by the car-using account, the driving segment specified by the car-using account, the route preference specified by the car-using account, the payment method specified by the car-using account, the waypoints specified by the car-using account, the origin specified by the car-using account, and the destination specified by the car-using account.

14. The method according to any one of claims 1 to 7, characterized in that, Before sending the ride-hailing order to the ride-hailing account in response to the triggering operation for sending the ride-hailing order, the method further includes: sending an account binding request to the ride-hailing account when the ride-hailing account and the ride-hailing account are not bound, wherein the account binding request is used to display in the ride-hailing service interface of the ride-hailing account; receiving a binding success notification, wherein the binding success notification is received after the ride-hailing account confirms the binding request; displaying binding information in the ride-hailing service interface of the ride-hailing account; and proceeding to the step of sending the ride-hailing order to the ride-hailing account in response to the triggering operation for sending the ride-hailing order.

15. The method according to any one of claims 1 to 7, characterized in that, The step of displaying the edited ride-hailing order in response to an editing operation on the ride-hailing service interface includes: displaying an order template for the ride-hailing account on the ride-hailing service interface; and displaying the edited ride-hailing order in response to an editing operation on the order parameters in the order template, wherein the order parameters include at least one of the following: the vehicle type specified by the ride-hailing account, the driving segment specified by the ride-hailing account, the route preference specified by the ride-hailing account, the payment method specified by the ride-hailing account, the waypoints specified by the ride-hailing account, and the origin specified by the ride-hailing account.

16. A method for processing ride-hailing services, characterized in that, The method includes: displaying a ride-hailing service interface based on a ride-hailing account login, wherein the ride-hailing service interface includes ride-hailing orders sent by the ride-hailing account, and the ride-hailing orders include at least the destination of the ride-hailing account; and requesting ride-hailing services based on the ride-hailing order in response to a triggering operation for the ride-hailing order.

17. The method according to claim 16, characterized in that, The method of requesting ride-hailing service based on the ride-hailing order includes: if the ride-hailing order includes the starting point specified by the ride-hailing account, requesting ride-hailing service based on the starting point and the destination; if the ride-hailing order does not include the starting point specified by the ride-hailing account, requesting ride-hailing service based on the current location of the ride-hailing account and the destination.

18. The method according to claim 17, characterized in that, The step of requesting car rental service based on the current location of the car rental account and the destination includes: displaying the current location of the car rental account in the starting point field of the car rental order; requesting car rental service based on the current location of the car rental account and the destination in response to a confirmation operation for the current location; and displaying the modified current location in response to a modification operation for the current location, and requesting car rental service based on the modified current location and the destination.

19. The method according to claim 16, characterized in that, Before requesting a ride-hailing service based on the ride-hailing order, the method further includes: in response to the ride-hailing account's pre-modification operation on the ride-hailing order, generating an order modification request and sending the order modification request to the ride-hailing account, wherein the order modification request includes at least one of the following order parameters: the vehicle type specified by the ride-hailing account, the driving segment specified by the ride-hailing account, the route preference specified by the ride-hailing account, the payment method specified by the ride-hailing account, the waypoints specified by the ride-hailing account, the origin specified by the ride-hailing account, and the destination specified by the ride-hailing account; receiving the modified ride-hailing order sent by the ride-hailing account, wherein the modified ride-hailing order is received after the ride-hailing account modifies and sends the ride-hailing order according to the order modification request, and the modified order is displayed on the instant messaging interface of the user account, wherein the modified ride-hailing order conforms to the order modification request.

20. The method according to claim 16, characterized in that, Before requesting a ride-hailing service based on the ride-hailing order, the method further includes: responding to the modification operation of the ride-hailing account on the ride-hailing order, obtaining a modified ride-hailing order, wherein the order parameters modified by the modification operation include at least one of the following: the vehicle type specified by the ride-hailing account, the driving segment specified by the ride-hailing account, the route preference specified by the ride-hailing account, the payment method specified by the ride-hailing account, the waypoints specified by the ride-hailing account, the origin specified by the ride-hailing account, and the destination specified by the ride-hailing account; wherein, when modifying the origin or the destination, the modification operation includes any one of the following: marking the location on a map, or providing location instructions via voice.

21. The method according to claim 16, characterized in that, Before requesting a ride-hailing service based on the ride-hailing order, the method further includes: if the ride-hailing order includes multiple destinations, displaying the multiple destinations in the ride-hailing service interface of the ride-hailing account, wherein the sorting factor of the multiple destinations includes any one of the following: descending order of historical usage frequency, ascending order of distance from the current location of the ride-hailing account; in response to the ride-hailing account's selection operation of the multiple destinations, taking the selected destination among the multiple terminals as the target destination, and proceeding to the step of requesting a ride-hailing service based on the ride-hailing order.

22. A vehicle service processing device, characterized in that, The device includes: a first display module for displaying a ride-hailing service interface based on a ride-hailing account login; a second display module for displaying a ride-hailing order generated by editing in response to an editing operation on the ride-hailing service interface, wherein the ride-hailing order includes at least the endpoint of the ride-hailing account; and an order sending module for sending the ride-hailing order to the ride-hailing account in response to a sending trigger operation for the ride-hailing order, wherein the ride-hailing order is used for the ride-hailing account to request ride-hailing services.

23. An electronic device, characterized in that, The electronic device includes: a memory for storing computer-executable instructions or computer programs; and a processor for executing the computer-executable instructions or computer programs stored in the memory to implement the vehicle service processing method according to any one of claims 1 to 15, or to implement the vehicle service processing method according to any one of claims 16 to 21.

24. A computer-readable storage medium storing computer-executable instructions or a computer program, characterized in that, When the computer-executable instructions or computer program are executed by a processor, they implement the vehicle service processing method according to any one of claims 1 to 15, or the vehicle service processing method according to any one of claims 16 to 21.

25. A computer program product comprising computer-executable instructions or a computer program, characterized in that, When the computer-executable instructions or computer program are executed by a processor, they implement the vehicle service processing method according to any one of claims 1 to 15, or the vehicle service processing method according to any one of claims 16 to 21.

Images