Taxi data processing method, device, equipment and system

Abstract

The present specification provides a car-hailing data processing method, device, equipment and system, a car-hailing applet of different travel service providers is accessed through an address bar of a comprehensive service platform, ensuring that the standards of different travel service providers accessing the comprehensive service platform are unified, and the address selection and other car-hailing service information selection of the user in the car-hailing process are completed by the car-hailing applet of the travel service provider selected by the user, so that the comprehensive service platform does not need to do much data processing, only needs to do some simple jump, realizes the semi-centralized and semi-open management of the car-hailing service, and reduces the data processing pressure of the comprehensive service platform.

Description

[0001] This application is a divisional application of "Ride-hailing data processing method, apparatus, equipment and system (application date: January 29, 2021, application number: 202110123762.0)". Technical Field

[0002] This specification belongs to the field of computer technology, and in particular relates to a method, apparatus, device and system for processing ride-hailing data. Background Technology

[0003] Taking a taxi has become a common choice for daily travel. With the development of the internet, using smart apps to hail a taxi has gradually replaced the traditional method of hailing one on the street, greatly facilitating people's travel. However, with the emergence of different taxi service providers, users need to install different apps developed by each provider, which is inconvenient. Therefore, integrating different taxi service providers into a one-stop travel service platform to provide users with more comfortable and personalized travel options is becoming increasingly important. Summary of the Invention

[0004] The purpose of the embodiments in this specification is to provide a method, apparatus, device and system for processing ride-hailing data, which realizes semi-centralized and semi-open management of ride-hailing services, improves user experience and reduces the time and cost of developing comprehensive management of ride-hailing services.

[0005] In a first aspect, embodiments of this specification provide a method for processing ride-hailing data. This method is applied to an integrated service platform that integrates ride-hailing mini-programs provided by multiple travel service providers. The method includes: Receive a ride-hailing service request, wherein the ride-hailing service request includes the target travel service provider selected by the user; Based on the ride-hailing service request and the received travel address selection request, the user is redirected to the address selection page of the ride-hailing mini-program provided by the target travel service provider. The system receives the travel address and confirmed ride information submitted by the user on the location selection page of the ride-hailing mini-program provided by the target travel service provider, and redirects the user to the ride-hailing mini-program provided by the target travel service provider to call a taxi.

[0006] Secondly, this specification provides a method for processing ride-hailing data, which is applied to a client and includes: Submit a ride-hailing service request to the integrated service platform, wherein the ride-hailing service request includes the target travel service provider selected by the user; The user submits a travel address selection request to the integrated service platform through the ride-hailing address bar, so that the integrated service platform redirects the user to the address selection page of the ride-hailing mini-program provided by the target travel service provider. The user determines their travel address through the location selection page of the ride-hailing mini-program provided by the target travel service provider and submits confirmation of the ride-hailing information to the integrated service platform, so that the integrated service platform can redirect the user to the ride-hailing mini-program provided by the target travel service provider to call a taxi.

[0007] Thirdly, this specification provides a ride-hailing data processing device applied to an integrated service platform, which connects to ride-hailing mini-programs provided by multiple travel service providers. The device includes: The request receiving module is used to receive ride-hailing service requests, which include the target travel service provider selected by the user. The mini-program address redirection module is used to redirect to the address selection page of the ride-hailing mini-program provided by the target travel service provider based on the ride-hailing service request and the received travel address selection request. The taxi-hailing module is used to receive the travel address and confirmed taxi information submitted by the user on the location selection page of the taxi-hailing mini-program provided by the target travel service provider, and to redirect the user to the taxi-hailing mini-program provided by the target travel service provider to call a taxi.

[0008] Fourthly, this specification provides a ride-hailing data processing device for use on a client-side application, the device comprising: The request submission module is used to submit a ride-hailing service request to the integrated service platform, wherein the ride-hailing service request includes the target travel service provider selected by the user; The location selection module is used to submit a travel address selection request to the integrated service platform through the ride-hailing address bar provided by the integrated service platform, so that the integrated service platform can jump to the location selection page of the ride-hailing mini-program provided by the target travel service provider; The taxi calling module is used to determine the travel address through the location selection page of the taxi-hailing mini-program provided by the target travel service provider, and submit the taxi-hailing information to the integrated service platform to enable the integrated service platform to redirect to the taxi-hailing mini-program provided by the target travel service provider for the user to call a taxi.

[0009] Fifthly, embodiments of this specification provide a ride-hailing data processing device, including at least one processor and a memory for storing processor-executable instructions, wherein the processor executes the instructions to implement the ride-hailing data processing method described in the first aspect or the second method above.

[0010] Sixthly, embodiments of this specification provide a ride-hailing data processing system, including: an integrated service platform and a client. The integrated service platform connects to ride-hailing mini-programs provided by multiple travel service providers. The integrated service platform includes at least one processor and a memory for storing processor-executable instructions. When the processor executes the instructions, it implements the method described in the first aspect above. The client system includes at least one processor and a memory for storing processor-executable instructions, wherein the processor executes the instructions to implement the method described in the second aspect above. The ride-hailing data processing method, apparatus, equipment, and system provided in this manual establish address bar access to different ride-hailing service providers' mini-programs through an integrated service platform. This ensures a unified standard for accessing the integrated service platform by different ride-hailing service providers. Furthermore, the user's address selection and selection of other ride-hailing service information during the ride-hailing process are all completed by the ride-hailing service provider's mini-program selected by the user. The integrated service platform does not need to perform extensive data processing, only some simple redirects, achieving a semi-centralized and semi-open management of the ride-hailing service and reducing the data processing pressure on the integrated service platform. Moreover, it requires no extensive development or modification to the integrated service platform, is simple to operate, easy to implement, and widely applicable, reducing the development time of the integrated ride-hailing service platform and lowering the implementation cost. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a flowchart illustrating an embodiment of the ride-hailing data processing method provided in this specification. Figure 2 This is a flowchart illustrating a taxi data processing method in yet another embodiment of this specification. Figure 3 This is a schematic diagram of the client interface flow during the ride-hailing data processing in one embodiment of this specification; Figure 4 This is a schematic diagram of the taxi address bar integration process in one scenario example of this manual; Figure 5 This is a schematic diagram of the module structure of one embodiment of the ride-hailing data processing device provided in this specification; Figure 6 This is a schematic diagram of the module structure of another embodiment of the ride-hailing data processing device provided in this specification; Figure 7 This is a hardware structure block diagram of a ride-hailing data processing server in one embodiment of this specification. Detailed Implementation

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

[0014] Taxi hailing has become a common mode of transportation in people's daily lives. With the development of internet technology, using mobile apps to hail taxis has become the mainstream method. However, different taxi service providers typically develop different online ride-hailing platforms. If users need to hail taxis from different service providers, they may need to install multiple online ride-hailing applications, which consumes memory space on the user's client, is inconvenient to switch between, and affects the user's ride-hailing experience.

[0015] Figure 1 This is a flowchart illustrating an embodiment of the ride-hailing data processing method provided in this specification. While this specification provides method operation steps or apparatus structures as shown in the following embodiments or figures, the method or apparatus may include more or fewer operation steps or module units, either combined or without inventive effort, based on conventional methods or without requiring creative work. In steps or structures where there is no logically necessary causal relationship, the execution order of these steps or the module structure of the apparatus is not limited to the execution order or module structure shown in the embodiments or figures of this specification. When the method or module structure is applied in actual devices, servers, or terminal products, it can be executed sequentially or in parallel according to the method or module structure shown in the embodiments or figures (e.g., in a parallel processor or multi-threaded processing environment, or even in a distributed processing or server cluster implementation environment).

[0016] The ride-hailing data processing method provided in the embodiments of this specification can be applied to a comprehensive service platform. This comprehensive service platform can be understood as a network platform capable of providing various services, such as ride-hailing services, train ticket purchase services, airline ticket purchase services, utility payment services, and online shopping services. The comprehensive service platform can integrate ride-hailing mini-programs provided by multiple travel service providers. These travel service providers can be understood as taxi service companies or companies providing online ride-hailing services. For example, multiple ride-hailing mini-programs developed by travel service providers can be integrated into an existing comprehensive service platform. A mini-program can be understood as an application that can be used without downloading or installation; it can be hosted within a mobile application without independent development. Users can directly use the mini-program within the mobile application, and different mini-programs can provide different services. Each mini-program can meet relatively simple basic application needs. The ride-hailing mini-program in the embodiments of this specification can provide ride-hailing services to users. The comprehensive service platform can be a computer, tablet computer, server, or other terminal. The method may include the following steps: Step 102: Receive a ride-hailing service request, which includes the user's selected target travel service provider.

[0017] In the specific implementation process, users can install the application provided by the integrated service platform on their own client, such as a smartphone, or open the webpage of the integrated service platform using their client. They can then send a ride-hailing service request to the integrated service platform through either the application or the webpage. Generally, the integrated service platform can provide multiple services. Users need to find the ride-hailing service offered by the platform and send a request by clicking the corresponding icon or button. Referring to the description in the above embodiment, the integrated service platform integrates ride-hailing mini-programs provided by multiple travel service providers. That is, the integrated service platform can provide users with ride-hailing services from multiple travel service providers. When submitting a ride-hailing service request to the integrated service platform, users can select their desired travel service provider, and the ride-hailing service request received by the integrated service platform will include the user's selected target travel service provider.

[0018] Furthermore, in the embodiments of this specification, when a user submits a ride-hailing service request to the integrated service platform, they can select their desired travel service provider in the address bar of the ride-hailing service provided by the integrated service platform. Generally, the address bar of the ride-hailing service provided by the integrated service platform can use the travel service provider previously selected by the user or set a default travel service provider. When the user needs to use other travel service providers, they can select to switch travel service providers in the address bar of the ride-hailing service provided by the integrated service platform and select their desired target travel service provider from the list of travel service providers provided by the integrated service platform.

[0019] Step 104: Based on the ride-hailing service request and the received travel address selection request, redirect to the address selection page of the ride-hailing mini-program provided by the target travel service provider.

[0020] In the specific implementation process, after receiving a ride-hailing service request submitted by a user, the integrated service platform can switch to the ride-hailing service page and display the target travel service provider currently selected by the user. The user can send a travel address selection request to the integrated service platform from the ride-hailing service page. At this time, the integrated service platform will automatically redirect to the address selection page of the ride-hailing mini-program provided by the target travel service provider selected by the user.

[0021] In some embodiments of this specification, the step of redirecting to the address selection page of the ride-hailing mini-program provided by the target travel service provider based on the ride-hailing service request and the received travel address selection request includes: Based on the ride-hailing service request, the current location information is displayed in the address bar of the integrated service platform; When the current location information is inconsistent with the user's taxi departure point, the system receives a request from the user to reselect the taxi departure point and redirects the user to the location selection page of the taxi mini-program provided by the target travel service provider, so that the user can select the taxi departure point on the location selection page of the taxi mini-program provided by the target travel service provider. After the user submits their selected departure location, they are redirected back to the address bar of the integrated service platform. The user then enters their submitted departure location in the departure address field of the integrated service platform's address bar. In practice, after submitting a ride-hailing request, the platform obtains the user's current location information and displays it in the address bar. If the current location information does not match the user's desired departure location, the user can send a request to the platform to reselect the departure location. Upon receiving this request, the platform redirects the user to the location selection page of the ride-hailing mini-program provided by the target travel service provider. The user can then select or enter their desired departure location on the mini-program's location selection page. After confirming and submitting the confirmation, the platform redirects the user back to its address bar for selecting their destination. At the same time, after being redirected back to the address bar of the integrated service platform, the user's submitted ride-hailing departure location will be filled back into the departure address field of the integrated service platform's address bar for user confirmation.

[0022] In addition, the method also includes: if the location fails to be displayed in the address bar of the integrated service platform based on the ride-hailing service request, then directly jump to the location selection page of the ride-hailing mini-program provided by the target travel service provider.

[0023] In the specific implementation process, if the integrated service platform fails to obtain the current user's client location information, it will not be able to display the current location information in the address bar. In this case, it can directly jump to the location selection page of the ride-hailing mini-program provided by the user's target travel service provider, so that the user can directly select the departure point for the ride-hailing in the target mini-program.

[0024] This embodiment only requires developing the address bar for the ride-hailing service on the integrated service platform. The address bar displays the current location information. If the user is not satisfied, they are redirected to a ride-hailing mini-program provided by the user's chosen ride-hailing service provider, which then provides the travel address. The integrated service platform does not need to perform extensive data processing, reducing its data processing burden. Furthermore, it requires minimal development or modification to the integrated service platform, is simple to operate, easy to implement, and widely applicable, thus reducing the development time and implementation cost of the integrated ride-hailing service.

[0025] In some embodiments of this specification, the step of redirecting to the address selection page of the ride-hailing mini-program provided by the target travel service provider based on the ride-hailing service request and the received travel address selection request further includes: After the user determines the departure address of the ride-hailing service in the address bar of the integrated service platform or the address selection page of the ride-hailing mini-program provided by the target travel service provider, the system receives the user's request to select the ride-hailing destination in the address bar of the integrated service platform and redirects the user to the address selection page of the ride-hailing mini-program provided by the target travel service provider, so that the user can select the ride-hailing destination on the address selection page of the ride-hailing mini-program provided by the target travel service provider. After the user submits the ride destination, the system redirects back to the address bar of the integrated service platform, and the user enters the submitted ride destination in the destination address field of the integrated service platform's address bar.

[0026] In practice, once a user determines their departure point, or confirms that the current location displayed in the address bar of the integrated service platform is their departure point, the user can send a destination selection request to the platform. Upon receiving this request, the platform automatically redirects the user to the destination selection page of the target ride-hailing service provider's mini-program. The user can then choose their destination on this page. By redirecting the user to the target service provider's mini-program after determining the departure point, the platform reduces its data processing burden by minimizing the need for extensive data processing. Furthermore, after the user submits their destination through the mini-program's selection page, the platform automatically redirects back to the integrated service platform's address bar, filling in the submitted destination for user confirmation.

[0027] Step 106: Receive the travel address and confirmed ride information submitted by the user on the location selection page of the ride-hailing mini-program provided by the target travel service provider, and redirect to the ride-hailing mini-program provided by the target travel service provider to call a taxi.

[0028] In practice, once a user determines their travel address through the location selection page of the ride-hailing mini-program provided by the target travel service provider, this address will be displayed in the address bar of the integrated service platform for the user to verify its accuracy. After confirming the address is accurate, the user can submit confirmation of their ride-hailing information to the integrated service platform. Upon receiving this confirmation, the platform will redirect the user to the ride-hailing mini-program provided by the target travel service provider. The user can then hail a taxi through this mini-program. With the travel address now determined, the user simply needs to select other ride-hailing options or directly submit confirmation of their taxi call within the mini-program to complete the online ride-hailing process. In some embodiments of this specification, receiving the travel address and confirmed ride information submitted by the user on the location selection page of the ride-hailing mini-program provided by the target travel service provider includes: The system receives a travel address selected by the user from the frequently used addresses displayed on the location selection page of the ride-hailing mini-program provided by the target travel service provider, or receives a travel address entered by the user in the input field of the location selection page of the ride-hailing mini-program provided by the target travel service provider. The frequently used addresses include the user's frequently used departure address and frequently used destination address when using the target travel service provider to hail a ride. After the departure and destination points for the ride are determined, the system returns to the address bar of the integrated service platform and receives the ride confirmation information submitted by the user through the address bar of the integrated service platform.

[0029] In practice, when a user selects their departure or destination on the location selection page of the ride-hailing mini-program provided by the target ride-hailing service provider, the page can display the user's frequently used departure and destination addresses when hailing a ride with that service. Specifically, the target ride-hailing service provider saves the departure and destination addresses of different users using its services. When a user hails a ride through the integrated service platform, the platform redirects to the address bar of the target ride-hailing mini-program. Depending on whether the integrated service platform receives a request to select a departure or destination, it can display the corresponding frequently used address options. If it's a request to select a departure, the address bar of the target ride-hailing mini-program will display the user's frequently used departure address; if it's a request to select a destination, the address bar will display the user's frequently used destination.

[0030] Of course, if users are not satisfied with the frequently used addresses displayed in the address bar of the target ride-hailing service provider's mini-program, they can directly enter their desired travel address in the address bar of the mini-program. After the user confirms and selects the departure and destination, the integrated service platform's page will redirect back to the integrated service platform's address bar, which will display the user's confirmed departure and destination addresses for verification. Once the user confirms the travel address is accurate, they can submit a confirmation of the ride-hailing information to the integrated service platform. After receiving the confirmation, the integrated service platform will redirect the user to the target ride-hailing service provider's mini-program.

[0031] In the embodiments described in this specification, the integrated service platform only needs to develop an address bar to access the ride-hailing mini-programs of multiple different travel service providers. When a user needs to select a travel address, the system automatically redirects to the ride-hailing mini-program provided by the selected travel service provider. Based on the user's ride-hailing data recorded by the travel service provider, the system provides the user with the choice of travel address. The integrated service platform does not need to perform excessive data processing, thus reducing the data processing pressure on the integrated service platform.

[0032] In some embodiments of this specification, the step of redirecting to the ride-hailing mini-program provided by the target travel service provider to call a taxi includes: After receiving the user's confirmed ride-hailing information, the system redirects the user to a ride-hailing mini-program provided by the target travel service provider based on the user's selected travel address. This allows the user to select ride-hailing service information within the mini-program, which includes at least one of the following: ride-hailing vehicle type, travel time, number of passengers, and payment method.

[0033] In the specific implementation process, after the integrated service platform receives the user's confirmed ride-hailing information, it can redirect the user to the ride-hailing mini-program provided by the target ride-hailing service provider, carrying the user's submitted travel address. The user only needs to select other ride-hailing service information in the ride-hailing mini-program provided by the target ride-hailing service provider, such as: ride type, travel time, number of passengers, payment method, or one or more of these. After the user confirms the ride-hailing service information in the ride-hailing mini-program provided by the target ride-hailing service provider, they can submit the confirmed taxi call information in the ride-hailing mini-program provided by the target ride-hailing service provider to submit a ride-hailing order. The ride-hailing mini-program provided by the target ride-hailing service provider will publish the ride-hailing order based on the user's submitted travel address and ride-hailing service information, and provide the ride-hailing service to the user. The integrated service platform only needs to develop the address bar to access the ride-hailing mini-programs of different ride-hailing service providers; the ride-hailing service is still provided by the ride-hailing service providers themselves.

[0034] The ride-hailing data processing method provided in this specification establishes a unified service platform by integrating the address bar of different ride-hailing service providers' mini-programs. This ensures a consistent standard for accessing the platform from various service providers. Furthermore, the user's address selection and selection of other ride-hailing service information during the ride-hailing process are all completed by the ride-hailing mini-program of the chosen service provider. The integrated service platform does not require extensive data processing; it only needs to perform simple redirects. This achieves semi-centralized and semi-open management of the ride-hailing service, reducing the data processing burden on the platform. Moreover, it requires minimal development or modification to the integrated service platform, is simple to operate, easy to implement, and widely applicable, thus reducing the development time and implementation cost of the integrated ride-hailing service. The above embodiments describe the process of ride-hailing data processing by the integrated service platform. This specification also provides a method for processing ride-hailing data during the ride-hailing process on the user's client side. Figure 2 This is a flowchart illustrating a ride-hailing data processing method in another embodiment of this specification. The method is applied to a client, which can be a computer, tablet, smartphone, smart wearable device, or other terminal. The method may include the following steps: Step 202: Submit a ride-hailing service request to the integrated service platform. The ride-hailing service request includes the target travel service provider selected by the user.

[0035] In the specific implementation process, users can install the application provided by the integrated service platform on their own client, such as a smartphone, or open the webpage of the integrated service platform using their client and send a ride-hailing service request to the integrated service platform through the application or webpage. Generally, the integrated service platform can provide multiple services. Users need to find the ride-hailing service provided by the integrated service platform and send a ride-hailing service request by clicking the corresponding icon or button. Referring to the description in the above embodiments, the integrated service platform integrates ride-hailing mini-programs provided by multiple travel service providers. The integrated service platform can provide users with ride-hailing services from multiple travel service providers. In the embodiments of this specification, when a user sends a ride-hailing service request to the integrated service platform, they can select the travel service provider they need in the address bar of the ride-hailing service provided by the integrated service platform. Generally, the address bar of the ride-hailing service provided by the integrated service platform can default to the travel service provider previously selected by the user or set a default travel service provider. When the user needs to use other travel service providers, they can switch travel service providers in the address bar of the ride-hailing service provided by the integrated service platform and select the target travel service provider they need from the list of travel service providers provided by the integrated service platform. Step 204: Submit a travel address selection request to the integrated service platform through the ride-hailing address bar provided by the integrated service platform, so that the integrated service platform will redirect to the address selection page of the ride-hailing mini-program provided by the target travel service provider.

[0036] In the specific implementation process, after receiving a ride-hailing service request submitted by a user, the integrated service platform can switch to the ride-hailing service page and display the target travel service provider currently selected by the user. The user can send a travel address selection request to the integrated service platform from the ride-hailing service page. At this time, the integrated service platform will automatically redirect to the address selection page of the ride-hailing mini-program provided by the target travel service provider selected by the user.

[0037] In some embodiments of this specification, submitting a travel address selection request to the integrated service platform through the ride-hailing address field provided by the integrated service platform includes: Receive the current location information displayed in the address bar of the integrated service platform; If the current location information does not match the departure point of the ride or the current location information fails to locate, click the departure address field in the ride address bar provided by the integrated service platform to submit a request to reselect the departure point of the ride to the integrated service platform, and jump to the address selection page of the ride-hailing mini-program provided by the target travel service provider; Alternatively, after determining the departure address for the ride, click the destination address field in the ride-hailing address bar provided by the integrated service platform to jump to the location selection page of the ride-hailing mini-program provided by the target travel service provider.

[0038] In practice, after a user submits a ride-hailing request to the integrated service platform, the platform can obtain the user's current location information and display it in the address bar of the platform's application or webpage within the user's client. If the current location information does not match the user's desired departure point, the user can send a request to the integrated service platform to reselect the departure point by clicking the departure address bar provided by the platform. Upon receiving this request, the platform can redirect the user to the location selection page of the ride-hailing mini-program provided by the chosen travel service provider. If the platform fails to obtain the user's current location information from the user's client, it cannot display the current location information in the address bar and will instead directly redirect the user to the location selection page of the ride-hailing mini-program provided by the chosen travel service provider. After the integrated service platform redirects to the location selection page of the ride-hailing mini-program provided by the target travel service provider, the client interface will also redirect to the location selection page of the ride-hailing mini-program provided by the target travel service provider. On the location selection page of the ride-hailing mini-program provided by the target travel service provider, users can select or enter their desired departure point. After the user confirms the departure point and submits the confirmation, the integrated service platform will redirect back to the address bar of the integrated service platform for the user to select the destination.

[0039] Once a user has determined their departure point through the address bar of the integrated service platform or the location selection page of the ride-hailing mini-program provided by the target travel service provider, they can send a destination selection request to the integrated service platform by clicking the destination address bar. Upon receiving the destination selection request from the user's client, the integrated service platform automatically redirects to the location selection page of the ride-hailing mini-program provided by the target travel service provider, where the user can then select their destination.

[0040] In some embodiments of this specification, determining the travel address through the location selection page of the ride-hailing mini-program provided by the target travel service provider includes: The user can select a travel address from the frequently used addresses displayed on the location selection page of the ride-hailing mini-program provided by the target travel service provider, or enter the travel address in the input field on the location selection page of the ride-hailing mini-program provided by the target travel service provider. The frequently used addresses include the user's frequently used departure address and frequently used destination address when using the target travel service provider to hail a ride.

[0041] In practice, when a user selects their departure or destination on the location selection page of the ride-hailing mini-program provided by the target ride-hailing service provider, the page displays the user's frequently used departure and destination addresses when hailing a ride with that service. The target ride-hailing service provider saves the departure and destination addresses of different users using its services. When a user hails a ride through the integrated service platform, the platform redirects to the address bar of the target ride-hailing mini-program. Depending on whether the integrated service platform receives a request to select a departure or destination, it can display the corresponding frequently used address options. If it's a request to select a departure, the address bar of the target ride-hailing mini-program displays the user's frequently used departure address; if it's a request to select a destination, the address bar displays the user's frequently used destination. Of course, if users are not satisfied with the frequently used addresses displayed in the address bar of the target ride-hailing service provider's mini-program, they can also directly enter their desired travel address in the address bar of the target ride-hailing service provider's mini-program.

[0042] Step 206: Determine the travel address through the location selection page of the ride-hailing mini-program provided by the target travel service provider, and submit the ride-hailing information to the integrated service platform to enable the integrated service platform to redirect the user to the ride-hailing mini-program provided by the target travel service provider so that the user can call a taxi.

[0043] In practice, once a user determines their travel address through the location selection page of the ride-hailing mini-program provided by the target travel service provider, this address will be displayed in the address bar of the integrated service platform for the user to verify its accuracy. After confirming the address is accurate, the user can submit confirmation of their ride-hailing information to the integrated service platform. Upon receiving this confirmation, the platform will redirect the user to the ride-hailing mini-program provided by the target travel service provider. The user can then hail a taxi through this mini-program. With the travel address now determined, the user simply needs to select other ride-hailing options or directly submit confirmation of their taxi call within the mini-program to complete the online ride-hailing process.

[0044] In some embodiments of this specification, the method further includes: after the integrated service platform redirects to the ride-hailing mini-program provided by the target travel service provider, submitting ride-hailing service information to the ride-hailing mini-program provided by the target travel service provider, wherein the ride-hailing service information includes at least one of the following: ride-hailing vehicle type, travel time, number of passengers, and payment method.

[0045] Once the integrated service platform receives a user's confirmed ride-hailing information, it can redirect the user to the ride-hailing mini-program provided by the target ride-hailing service provider, along with the user's submitted travel address. The user's client interface will then redirect to the mini-program. Within the mini-program, the user simply selects one or more ride-hailing service options, such as ride type, travel time, number of passengers, and payment method. After confirming the ride-hailing service within the mini-program, the user can submit a confirmation of the taxi call, effectively placing a ride order. The mini-program will then issue the order based on the user's submitted travel address and ride-hailing information, providing the ride-hailing service. The integrated service platform only needs to integrate the address bar with the different ride-hailing mini-programs provided by each service provider; the actual ride-hailing service remains the responsibility of the respective service provider.

[0046] The ride-hailing data processing method provided in this specification establishes a unified standard for accessing different ride-hailing service providers' mini-programs via the address bar of an integrated service platform. This ensures that the user's address selection and other ride-hailing service information selection during the ride-hailing process are handled by the user-selected ride-hailing service provider's mini-program. The integrated service platform does not need to perform extensive data processing; it only needs to perform simple redirects, thus reducing the data processing burden on the platform. Furthermore, it requires minimal development or modification to the integrated service platform, is simple to operate, easy to implement, and widely applicable, thereby reducing the development time and implementation cost of the integrated ride-hailing service platform.

[0047] Figure 3 This is a schematic diagram of the client interface flow during the ride-hailing data processing in one embodiment of this specification. The following is in conjunction with... Figure 3 The following is a further description of the ride-hailing data processing scenario in the embodiments of this specification: 1. Open travel services: Users can open the integrated service platform application installed in the client and select the travel services provided by the integrated service platform. 2. Select ride-hailing: After entering the travel service interface, you can switch to the "ride-hailing" service.

[0048] 3. Switching ride-hailing methods in the address bar: In the embodiments of this specification, the integrated service platform integrates ride-hailing mini-programs provided by multiple travel service providers, allowing users to choose different ride-hailing methods and supporting users to switch ride-hailing methods in the address bar of the ride-hailing service, such as changing the ride-hailing method of travel service provider A to the ride-hailing method of travel service provider B.

[0049] 4. Ride-hailing method has been switched: After successfully switching ride-hailing methods, the address bar will display the ride-hailing method provided by the user's selected travel service provider.

[0050] 5. Modify pick-up point (provided by the travel service provider): Figure 4 This is a schematic diagram of the taxi address bar integration process in one scenario example of this manual, such as... Figure 4 As shown, if a user is not satisfied with the current location information or the current location is unsuccessful, they can click on the pick-up point to be redirected to the location selection page of the mini-program provided by the target travel service provider, so that the user can manually modify the pick-up point information.

[0051] 6. After modifying the boarding point, return to the address bar: e.g. Figure 4 As shown, after selecting an address on the address selection page of the mini-program provided by the target travel service provider, the user is returned to the address bar of the integrated service platform, and the pick-up point information selected by the user is automatically filled back into the pick-up point location in the address bar of the integrated service platform.

[0052] 7. Select your drop-off point (provided by the travel service provider): e.g. Figure 4 As shown, when a user clicks on the drop-off point, they are redirected to the location selection page of the mini-program provided by the target travel service provider, where they can manually modify the drop-off point information.

[0053] 8. After selecting your drop-off point, return to the address bar: e.g. Figure 4 As shown, after selecting an address on the address selection page of the mini-program provided by the target travel service provider, the user is returned to the address bar of the integrated service platform, and the drop-off point information selected by the user is automatically filled back into the drop-off point location in the address bar of the integrated service platform.

[0054] 9. Confirm Immediate Ride (provided by the ride-hailing service provider): After confirming that the pick-up and drop-off points are correct, the user clicks "Immediate Ride" to be redirected to the merchant's page to select the vehicle type and confirm the ride.

[0055] This embodiment of the specification ensures a unified user experience across all participating parties by self-building the address bar for ride-hailing services on the integrated service platform. Meanwhile, the site selection and ride-hailing capabilities (which are highly specialized) are open to third-party merchants, reducing self-construction costs. This achieves a semi-centralized, semi-open management of ride-hailing services by the integrated service platform: centralized management of address bar access, and open management of site selection and ride-hailing capabilities. This avoids the problems of simply providing a "gateway" service, which degrades user experience and channel brand recognition. It also avoids the excessive costs and long development cycles associated with building an aggregated ride-hailing service platform by self-constructing the front and back ends and relying on third-party ride-hailing service providers for order dispatch.

[0056] The various embodiments of the methods described in this specification are presented in a progressive manner. Similar or identical parts between the embodiments can be referred to interchangeably. Each embodiment focuses on highlighting the differences from other embodiments. Relevant details can be found in the descriptions of the method embodiments.

[0057] Based on the above-described ride-hailing data processing method, one or more embodiments of this specification also provide an apparatus for ride-hailing data processing. The apparatus may include devices (including distributed systems), software (applications), modules, components, servers, clients, etc., using the methods described in the embodiments of this specification, combined with necessary hardware implementations. Based on the same innovative concept, the apparatuses in one or more embodiments provided in this specification are as described in the following embodiments. Since the implementation schemes and methods for solving the problem are similar, the implementation of specific apparatuses in the embodiments of this specification can refer to the implementation of the aforementioned methods, and repeated details will not be repeated. As used below, the terms "unit" or "module" can refer to a combination of software and / or hardware that implements a predetermined function. Although the apparatuses described in the following embodiments are preferably implemented in software, hardware implementations, or combinations of software and hardware, are also possible and contemplated.

[0058] Specifically, Figure 5 This is a schematic diagram of the module structure of one embodiment of the ride-hailing data processing device provided in this specification. This device can be applied to the integrated service platform in the above embodiments, which connects to multiple ride-hailing mini-programs provided by various travel service providers, such as... Figure 5 As shown, the ride-hailing data processing device provided in this specification may include: Request receiving module 51 is used to receive a ride-hailing service request, wherein the ride-hailing service request includes the target travel service provider selected by the user; The mini-program address redirection module 52 is used to redirect to the address selection page of the ride-hailing mini-program provided by the target travel service provider based on the ride-hailing service request and the received travel address selection request. The taxi-hailing module 53 is used to receive the travel address and taxi-hailing information submitted by the user on the location selection page of the taxi-hailing mini-program provided by the target travel service provider, and to jump to the taxi-hailing mini-program provided by the target travel service provider to call a taxi.

[0059] Figure 6 This is a schematic diagram of the module structure of another embodiment of the ride-hailing data processing device provided in this specification. This device can be applied in the user client of the above embodiments, such as... Figure 6 As shown, the ride-hailing data processing device provided in this specification may include: The request submission module 61 is used to submit a ride-hailing service request to the integrated service platform, wherein the ride-hailing service request includes the target travel service provider selected by the user. The location selection module 62 is used to submit a travel address selection request to the integrated service platform through the ride-hailing address bar provided by the integrated service platform, so that the integrated service platform can jump to the location selection page of the ride-hailing mini-program provided by the target travel service provider; The taxi calling module 63 is used to determine the travel address through the location selection page of the taxi-hailing mini-program provided by the target travel service provider, and submit the taxi-hailing information to the integrated service platform to enable the integrated service platform to redirect to the taxi-hailing mini-program provided by the target travel service provider for the user to call a taxi.

[0060] The ride-hailing data processing device provided in this specification ensures a unified user experience across all parties by self-building the address bar for ride-hailing on the integrated service platform. Meanwhile, the site selection and ride-hailing capabilities (which are highly specialized) are open to third-party merchants, reducing self-construction costs. This achieves a semi-centralized, semi-open management of ride-hailing services by the integrated service platform. Specifically, the address bar access is centrally managed, while site selection and ride-hailing capabilities are managed openly. This avoids the problem of simply providing a "gateway" service, which degrades user experience and channel brand recognition. It also avoids the high costs and long development cycles associated with building an aggregated ride-hailing service platform by self-constructing the front and back ends and relying on third-party ride-hailing service providers for order dispatch.

[0061] It should be noted that the apparatus described above may include other implementation methods based on the description of the corresponding method embodiments. Specific implementation methods can be found in the description of the corresponding method embodiments above, and will not be elaborated upon here.

[0062] This specification also provides a ride-hailing data processing device, including: at least one processor and a memory for storing processor-executable instructions. When the processor executes the instructions, it implements the ride-hailing data processing method of the above embodiments, such as: The method is applied to an integrated service platform, which integrates ride-hailing mini-programs provided by multiple travel service providers. The method includes: Receive a ride-hailing service request, wherein the ride-hailing service request includes the target travel service provider selected by the user; Based on the ride-hailing service request and the received travel address selection request, the user is redirected to the address selection page of the ride-hailing mini-program provided by the target travel service provider. The system receives the travel address and confirmed ride information submitted by the user on the location selection page of the ride-hailing mini-program provided by the target travel service provider, and redirects the user to the ride-hailing mini-program provided by the target travel service provider to call a taxi.

[0063] Alternatively, the method may be applied to a client, and the method may include: Submit a ride-hailing service request to the integrated service platform, wherein the ride-hailing service request includes the target travel service provider selected by the user; The user submits a travel address selection request to the integrated service platform through the ride-hailing address bar, so that the integrated service platform redirects the user to the address selection page of the ride-hailing mini-program provided by the target travel service provider. The user determines their travel address through the location selection page of the ride-hailing mini-program provided by the target travel service provider and submits confirmation of the ride-hailing information to the integrated service platform, so that the integrated service platform can redirect the user to the ride-hailing mini-program provided by the target travel service provider to call a taxi.

[0064] This specification also provides a ride-hailing data processing system, including: an integrated service platform and a client. The integrated service platform connects to ride-hailing mini-programs provided by multiple travel service providers. The integrated service platform includes at least one processor and a memory for storing processor-executable instructions. When the processor executes the instructions, it implements the method executed by the integrated service platform in the above embodiment. The client system includes at least one processor and a memory for storing processor-executable instructions. When the processor executes the instructions, it implements the client-side execution method described in the above embodiments.

[0065] It should be noted that the above-described devices and systems, based on the description of the method embodiments, may also include other implementation methods. Specific implementation methods can be found in the descriptions of the relevant method embodiments, and will not be elaborated upon here.

[0066] The ride-hailing data processing device provided in this specification can also be applied to various data analysis and processing systems. The system, server, terminal, or device can be a standalone server, or it can include a server cluster, system (including distributed systems), software (applications), actual operating devices, logic gate circuit devices, quantum computers, etc., combined with necessary hardware implementation, using one or more of the methods or embodiments described in this specification. The detection system for verifying discrepancies may include at least one processor and a memory storing computer-executable instructions. When the processor executes the instructions, it implements the steps of the methods described in any one or more of the above embodiments.

[0067] The methods and embodiments provided in this specification can be executed on mobile terminals, computer terminals, servers, or similar computing devices. Taking execution on a server as an example... Figure 7 This is a hardware structure block diagram of a ride-hailing data processing server in one embodiment of this specification. The computer terminal can be the ride-hailing data processing server or ride-hailing data processing device in the above embodiment. Figure 7 The server 10 shown may include one or more (only one is shown in the figure) processors 100 (processors 100 may include, but are not limited to, microprocessors MCUs or programmable logic devices FPGAs), non-volatile memory 200 for storing data, and a transmission module 300 for communication functions. Those skilled in the art will understand that... Figure 7 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, server 10 may also include components that are more... Figure 7 The components shown may include more or fewer components, and may also include other processing hardware such as databases or multi-level caches, GPUs, or components with similar capabilities. Figure 7 The different configurations shown.

[0068] The non-volatile memory 200 can be used to store software programs and modules of application software, such as the program instructions / modules corresponding to the ride-hailing data processing method in the embodiments of this specification. The processor 100 executes various functional applications and resource data updates by running the software programs and modules stored in the non-volatile memory 200. The non-volatile memory 200 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the non-volatile memory 200 may further include memory remotely located relative to the processor 100, and these remote memories can be connected to a computer terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0069] The transmission module 300 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the computer terminal's communication provider. In one example, the transmission module 300 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission module 300 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0070] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0071] The methods or apparatus described in the embodiments provided in this specification can implement business logic through a computer program and record it on a storage medium. The storage medium can be read and executed by a computer to achieve the effects of the solutions described in the embodiments of this specification, such as: The method is applied to an integrated service platform, which integrates ride-hailing mini-programs provided by multiple travel service providers. The method includes: Receive a ride-hailing service request, wherein the ride-hailing service request includes the target travel service provider selected by the user; Based on the ride-hailing service request and the received travel address selection request, the user is redirected to the address selection page of the ride-hailing mini-program provided by the target travel service provider. The system receives the travel address and confirmed ride information submitted by the user on the location selection page of the ride-hailing mini-program provided by the target travel service provider, and redirects the user to the ride-hailing mini-program provided by the target travel service provider to call a taxi.

[0072] Alternatively, the method may be applied to a client, and the method may include: Submit a ride-hailing service request to the integrated service platform, wherein the ride-hailing service request includes the target travel service provider selected by the user; The user submits a travel address selection request to the integrated service platform through the ride-hailing address bar, so that the integrated service platform redirects the user to the address selection page of the ride-hailing mini-program provided by the target travel service provider. The user determines their travel address through the location selection page of the ride-hailing mini-program provided by the target travel service provider and submits confirmation of the ride-hailing information to the integrated service platform, so that the integrated service platform can redirect the user to the ride-hailing mini-program provided by the target travel service provider to call a taxi.

[0073] The storage medium may include a physical device for storing information, typically digitizing the information and then storing it using electrical, magnetic, or optical methods. The storage medium may include: devices that store information using electrical energy, such as various types of memory, like RAM and ROM; devices that store information using magnetic energy, such as hard disks, floppy disks, magnetic tapes, magnetic core memory, bubble memory, and USB flash drives; and devices that store information using optical methods, such as CDs or DVDs. Of course, there are other readable storage media, such as quantum memories and graphene memories.

[0074] The ride-hailing data processing method or apparatus provided in the embodiments of this specification can be implemented by a processor in a computer executing corresponding program instructions, such as using the C++ language of the Windows operating system on a PC, the Linux system, or other programming languages ​​such as Android and iOS on a smart terminal, as well as processing logic based on a quantum computer, etc.

[0075] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, for hardware + program embodiments, since they are basically similar to the method embodiments, the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0076] The embodiments in this specification are not limited to conforming to industry communication standards, standard computer resource data update and data storage rules, or the situations described in one or more embodiments of this specification. Slightly modified implementations based on certain industry standards or custom methods or embodiments can also achieve the same, equivalent, or similar, or predictable, implementation effects as described above. Embodiments that utilize these modified or modified methods for data acquisition, storage, judgment, and processing still fall within the scope of optional implementations of the embodiments in this specification.

[0077] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0078] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0079] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, a laptop computer, an in-vehicle human-machine interaction device, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0080] While one or more embodiments of this specification provide the operational steps of the methods described in the embodiments or flowcharts, more or fewer operational steps may be included based on conventional or non-inventive means. The order of steps listed in the embodiments is merely one possible order of execution among many steps and does not represent the only possible order. In actual device or end product execution, the methods shown in the embodiments or drawings may be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment, or even a distributed resource data update environment). The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, product, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, product, or apparatus. Without further limitations, the presence of other identical or equivalent elements in a process, method, product, or apparatus that includes said elements is not excluded. The terms "first," "second," etc., are used to denote names and do not indicate any particular order.

[0081] For ease of description, the above devices are described in terms of function, divided into various modules. Of course, when implementing one or more of these specifications, the functions of each module can be implemented in one or more software and / or hardware components, or a module that performs the same function can be implemented by a combination of multiple sub-modules or sub-units. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection between devices or units, and may be electrical, mechanical, or other forms.

[0082] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable resource data updating device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable resource data updating device, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0083] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable resource data updating device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0084] These computer program instructions can also be loaded onto a computer or other programmable resource data updating device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0085] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0086] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0087] Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage, graphene storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0088] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote devices connected via a communication network. In a distributed computing environment, program modules can reside in local and remote computer storage media, including storage devices.

[0089] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, system embodiments are basically similar to method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments. In the description of this specification, the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this specification. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described can be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0090] The above description is merely an embodiment of one or more embodiments of this specification and is not intended to limit the scope of these embodiments. Various modifications and variations can be made to these embodiments by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of the claims.

Claims

1. A method for processing ride-hailing data, the method being applied to an integrated service platform, the integrated service platform connecting to ride-hailing mini-programs provided by multiple travel service providers, the method comprising: Receive a ride-hailing service request, wherein the ride-hailing service request includes the target travel service provider selected by the user; Based on the ride-hailing service request, the user is redirected to the location selection page of the ride-hailing mini-program provided by the target travel service provider. The system receives the travel address and confirmed ride information submitted by the user on the location selection page of the ride-hailing mini-program provided by the target travel service provider, and redirects the user to the ride-hailing mini-program provided by the target travel service provider to call a taxi.

2. The method as described in claim 1, wherein the integrated service platform includes a ride-hailing service, and the ride-hailing service accesses multiple ride-hailing mini-programs provided by various travel service providers through the address bar.

3. The method as described in claim 2, wherein the address bar of the ride-hailing service defaults to the travel service provider previously selected by the user; or, the address bar of the ride-hailing service is set with a default travel service provider.

4. The method as described in claim 1, wherein the step of redirecting to the location selection page of the ride-hailing mini-program provided by the target travel service provider based on the ride-hailing service request includes: Based on the ride-hailing service request, the system switches to the ride-hailing service page; The ride-hailing service page displays the target travel service provider selected by the user. Receive the travel address selection request sent by the user on the ride-hailing service page; Based on the ride-hailing service request and the received travel address selection request, the user is redirected to the address selection page of the ride-hailing mini-program provided by the target travel service provider.

5. The method as described in claim 1, wherein the step of redirecting to the address selection page of the ride-hailing mini-program provided by the target travel service provider based on the ride-hailing service request and the received travel address selection request includes: Based on the ride-hailing service request, the current location information is displayed in the address bar of the integrated service platform; When the current location information is inconsistent with the user's taxi departure point, the system receives a request from the user to reselect the taxi departure point and redirects the user to the location selection page of the taxi mini-program provided by the target travel service provider, so that the user can select the taxi departure point on the location selection page of the taxi mini-program provided by the target travel service provider. After the user submits the departure location for the ride-hailing service, the system will redirect back to the address bar of the integrated service platform, and the user's submitted departure location will be entered in the departure address field of the integrated service platform's address bar.

6. The method of claim 5, further comprising: If the location fails to be displayed in the address bar of the integrated service platform based on the ride-hailing service request, the user will be directly redirected to the location selection page of the ride-hailing mini-program provided by the target travel service provider.

7. The method according to any one of claims 4 to 6, wherein the step of redirecting to the address selection page of the ride-hailing mini-program provided by the target travel service provider based on the ride-hailing service request and the received travel address selection request further includes: After the user determines the departure address of the ride-hailing service in the address bar of the integrated service platform or the address selection page of the ride-hailing mini-program provided by the target travel service provider, the system receives the user's request to select the ride-hailing destination in the address bar of the integrated service platform and redirects the user to the address selection page of the ride-hailing mini-program provided by the target travel service provider, so that the user can select the ride-hailing destination on the address selection page of the ride-hailing mini-program provided by the target travel service provider. After the user submits the ride destination, the system redirects back to the address bar of the integrated service platform, and the user enters the submitted ride destination in the destination address field of the integrated service platform's address bar.

8. The method as described in claim 1, wherein receiving the travel address and confirmed ride information submitted by the user on the location selection page of the ride-hailing mini-program provided by the target travel service provider includes: The system receives a travel address selected by the user from the frequently used addresses displayed on the location selection page of the ride-hailing mini-program provided by the target travel service provider, or receives a travel address entered by the user in the input field of the location selection page of the ride-hailing mini-program provided by the target travel service provider. The frequently used addresses include the user's frequently used departure address and frequently used destination address when using the target travel service provider to hail a ride. After the departure and destination points for the ride are determined, the system returns to the address bar of the integrated service platform and receives the ride confirmation information submitted by the user through the address bar of the integrated service platform.

9. The method of claim 1, further comprising, after receiving the travel address submitted by the user on the location selection page of the ride-hailing mini-program provided by the target travel service provider: The travel address is displayed in the address bar of the integrated service platform.

10. The method of claim 1, wherein the step of redirecting to the taxi-hailing mini-program provided by the target travel service provider to call a taxi includes: After receiving the user's confirmed ride-hailing information, the system redirects the user to a ride-hailing mini-program provided by the target travel service provider based on the user's selected travel address. This allows the user to select ride-hailing service information within the mini-program, which includes at least one of the following: ride-hailing vehicle type, travel time, number of passengers, and payment method.

11. A method for processing ride-hailing data, the method being applied to a client, the method comprising: Submit a ride-hailing service request to the integrated service platform, wherein the ride-hailing service request includes the target travel service provider selected by the user; The user submits a travel address selection request to the integrated service platform through the ride-hailing address bar, so that the integrated service platform redirects the user to the address selection page of the ride-hailing mini-program provided by the target travel service provider. The user determines their travel address through the location selection page of the ride-hailing mini-program provided by the target travel service provider and submits confirmation of the ride-hailing information to the integrated service platform. This allows the integrated service platform to redirect the user to the ride-hailing mini-program provided by the target travel service provider, where the user can call a taxi.

12. The method as described in claim 11, wherein the integrated service platform includes a ride-hailing service, and the ride-hailing service accesses multiple ride-hailing mini-programs provided by various travel service providers through the address bar.

13. The method as described in claim 12, wherein the address bar of the ride-hailing service defaults to the travel service provider previously selected by the user; or, the address bar of the ride-hailing service is set with a default travel service provider.

14. The method as described in claim 11, wherein submitting a travel address selection request to the integrated service platform through the ride-hailing address field provided by the integrated service platform includes: Receive the current location information displayed in the address bar of the integrated service platform; If the current location information does not match the departure point of the ride or the current location information fails to locate, click the departure address field in the ride address bar provided by the integrated service platform to submit a request to reselect the departure point of the ride to the integrated service platform, and jump to the address selection page of the ride-hailing mini-program provided by the target travel service provider; Alternatively, after determining the departure address for the ride, click the destination address field in the ride-hailing address bar provided by the integrated service platform to jump to the location selection page of the ride-hailing mini-program provided by the target travel service provider.

15. The method of claim 11, wherein the integrated service platform redirects to the location selection page of the ride-hailing mini-program provided by the target travel service provider, comprising: After the user determines the departure address of the ride-hailing service in the address bar of the integrated service platform or the address selection page of the ride-hailing mini-program provided by the target travel service provider, the integrated service platform receives the ride-hailing destination selection request submitted by the user in the address bar of the integrated service platform, and redirects to the address selection page of the ride-hailing mini-program provided by the target travel service provider, so that the user can select the ride-hailing destination on the address selection page of the ride-hailing mini-program provided by the target travel service provider. After the user submits the ride-hailing destination, the integrated service platform redirects back to the address bar of the integrated service platform, and the user enters the ride-hailing destination in the destination address field of the integrated service platform's address bar.

16. The method of claim 11, wherein determining the travel address through the location selection page of the ride-hailing mini-program provided by the target travel service provider includes: The user can select a travel address from the frequently used addresses displayed on the location selection page of the ride-hailing mini-program provided by the target travel service provider, or enter the travel address in the input field on the location selection page of the ride-hailing mini-program provided by the target travel service provider. The frequently used addresses include the user's frequently used departure address and frequently used destination address when using the target travel service provider to hail a ride.

17. The method of claim 11, further comprising: After being redirected from the integrated service platform to the ride-hailing mini-program provided by the target travel service provider, the user submits ride-hailing service information to the ride-hailing mini-program provided by the target travel service provider. The ride-hailing service information includes at least one of the following: ride-hailing vehicle type, travel time, number of passengers, and payment method.

18. A ride-hailing data processing device, applied to an integrated service platform, the integrated service platform connecting to ride-hailing mini-programs provided by multiple travel service providers, the device comprising: The request receiving module is used to receive ride-hailing service requests, which include the target travel service provider selected by the user. The mini-program address redirection module is used to redirect to the address selection page of the ride-hailing mini-program provided by the target travel service provider based on the ride-hailing service request. The taxi-hailing module is used to receive the travel address and taxi confirmation information submitted by the user on the location selection page of the taxi-hailing mini-program provided by the target travel service provider, and to redirect the user to the taxi-hailing mini-program provided by the target travel service provider to call a taxi.

19. A ride-hailing data processing device, applied to a client, the device comprising: The request submission module is used to submit a ride-hailing service request to the integrated service platform, wherein the ride-hailing service request includes the target travel service provider selected by the user; The location selection module is used to submit a travel address selection request to the integrated service platform through the ride-hailing address bar provided by the integrated service platform, so that the integrated service platform can jump to the location selection page of the ride-hailing mini-program provided by the target travel service provider; The taxi calling module is used to determine the travel address through the location selection page of the taxi-hailing mini-program provided by the target travel service provider, and submit the taxi-hailing information to the integrated service platform to enable the integrated service platform to redirect to the taxi-hailing mini-program provided by the target travel service provider so that the user can call a taxi in the taxi-hailing mini-program provided by the target travel service provider.

20. A ride-hailing data processing device, comprising: At least one processor and a memory for storing processor-executable instructions, wherein the processor, when executing the instructions, implements the method according to any one of claims 1-10 or 11-17.

21. A ride-hailing data processing system, comprising: The integrated service platform and the client are connected to ride-hailing mini-programs provided by multiple travel service providers. The integrated service platform includes at least one processor and a memory for storing processor-executable instructions. When the processor executes the instructions, it implements the method described in any one of claims 1-10. The client includes at least one processor and a memory for storing processor-executable instructions, wherein the processor, when executing the instructions, implements the method of any one of claims 11-17.

Images