Driving route synchronization method and device

Abstract

The embodiment of the present application provides a driving route synchronization method and device, which relates to the field of online car-hailing technology. The driving route synchronization method may include: receiving a driver-passenger simultaneous display identification number generated by a taxi-hailing application on the passenger side and sent after the passenger places an order; when it is detected that the taxi driver has accepted the order, setting the order number of the passenger's current taxi ride to the driver-passenger simultaneous display identification number; sending the order number to the taxi driver-side taxi-hailing application, so that the taxi driver-side taxi-hailing application sets the driver-passenger simultaneous display identification number on its own side to the order number. The technical solution provided by the embodiment of the present application can, to a certain extent, solve the problem in the prior art that the taxi driver-side taxi-hailing application does not support the passenger route selection function, which easily leads to a large difference between the estimated cost before the start of the trip and the actual settlement cost after the trip, thereby causing passenger dissatisfaction.

Description

Technical Field

[0001] The present application relates to the field of online car-hailing technology, and in particular to a driving route synchronization method and device. Background Art

[0002] With the development of internet technology, ride-hailing services have gradually become part of people's daily lives. To provide passengers with a better ride-hailing experience, some ride-hailing platforms offer route selection. After passengers select their starting and ending points, they are presented with multiple routes to choose from. The selected route is then synchronized with the driver's app, allowing the driver to follow the selected route.

[0003] With the development of online ride-hailing technology, some online ride-hailing platforms allow users to book not only private cars but also taxis. However, the taxi driver-side ride-hailing app does not support the passenger route selection function, making it impossible to synchronize the passenger's selected route with the taxi driver-side ride-hailing app. Specifically, the passenger-side ride-hailing app sends the driver-passenger simultaneous display identification number used for route synchronization to the taxi driver-side ride-hailing app. However, the taxi driver-side ride-hailing app sets the driver-passenger simultaneous display identification number used for route synchronization to the order number of the taxi order, resulting in different driver-passenger simultaneous display identification numbers on both sides, making route synchronization impossible.

[0004] However, since the route selected by the passenger cannot be synchronized to the taxi driver's taxi app, the actual route of the taxi is likely to be inconsistent with the route selected by the passenger, resulting in a large difference between the estimated fare before the start of the trip (estimated based on the route selected by the passenger) and the actual settlement fee after the end of the trip, causing dissatisfaction among passengers and complaints. Summary of the Invention

[0005] The embodiments of the present application provide a driving route synchronization method and device to, to a certain extent, solve the problem in the prior art that, because the taxi driver-side taxi-hailing application does not support the passenger route selection function, it is easy to cause a large difference between the estimated cost before the start of the trip and the actual settlement cost after the trip, thereby causing passenger dissatisfaction.

[0006] In order to solve the above technical problems, the embodiments of the present application provide the following technical solutions:

[0007] In a first aspect, an embodiment of the present application provides a driving route synchronization method, which is applied to a server. The driving route synchronization method includes:

[0008] Receive the driver and passenger identification number generated by the passenger's ride-hailing app and sent after the passenger places an order;

[0009] If it is detected that the taxi driver has accepted the order, the passenger's order number is set as the driver-passenger identification number;

[0010] The order number is sent to the taxi driver's taxi hailing application, so that the taxi driver's taxi hailing application sets its own driver and passenger identification number to the order number.

[0011] In a second aspect, an embodiment of the present application provides a driving route synchronization device, which is applied to a driver terminal, wherein the driver terminal is installed with a new version of a taxi driver-side taxi-hailing application that supports a passenger route selection function;

[0012] The driving route synchronization method comprises:

[0013] If the taxi driver has accepted the order, the server receives the driver-passenger identification number and the passenger's order number for this taxi ride. The driver-passenger identification number is generated by the passenger's taxi app and sent to the server after the passenger places the order.

[0014] Determining the version of the passenger-side taxi-hailing application based on the driver-passenger simultaneous display identification number; wherein the driver-passenger simultaneous display identification numbers generated by the new and old versions of the passenger-side taxi-hailing application are different;

[0015] If it is determined that the taxi-hailing application on the passenger side is an old version, the server sets the driver-passenger identification number on the server side to the order number; wherein, if the taxi-hailing application on the passenger side is an old version, the server sets the order number to be the same as the driver-passenger identification number sent by the taxi-hailing application on the passenger side;

[0016] When it is determined that the taxi-hailing application on the passenger side is a new version, the driver-passenger simultaneous display identification number on the passenger side is set to the driver-passenger simultaneous display identification number sent by the server.

[0017] In a third aspect, an embodiment of the present application provides a driving route synchronization device, applied to a server, the device comprising:

[0018] The first receiving module is used to receive the driver-passenger simultaneous display identification number generated by the passenger-side taxi-hailing application and sent after the passenger places an order;

[0019] The first setting module is used to set the order number of the passenger's current taxi as the driver-passenger simultaneous display identification number when it is detected that the taxi driver has accepted the order;

[0020] The first sending module is used to send the order number to the taxi driver's taxi hailing application, so that the taxi driver's taxi hailing application sets the driver and passenger simultaneous display identification number on its own side as the order number.

[0021] In a fourth aspect, an embodiment of the present application provides a driving route synchronization device, which is applied to a driver terminal, wherein the driver terminal is installed with a new version of a taxi driver-side taxi-hailing application that supports a passenger route selection function;

[0022] The driving route synchronization device includes:

[0023] The second receiving module is used to receive the driver-passenger simultaneous display identification number and the passenger's order number sent by the server when the taxi driver has accepted the order; wherein the driver-passenger simultaneous display identification number is generated by the passenger-side taxi application and sent to the server after the passenger places the order;

[0024] a determination module for determining a version of the passenger-side taxi-hailing application based on the driver-passenger simultaneous display identification number; wherein the driver-passenger simultaneous display identification numbers generated by the new and old versions of the passenger-side taxi-hailing application are different;

[0025] a second setting module, configured to, if it is determined that the passenger-side taxi-hailing application is an old version, set the driver-passenger simultaneous display identification number on the server side to the order number; wherein, if the passenger-side taxi-hailing application is an old version, the server sets the order number to be the same as the driver-passenger simultaneous display identification number sent by the passenger-side taxi-hailing application;

[0026] The third setting module is used to set the driver and passenger simultaneous display identification number of the passenger side to the driver and passenger simultaneous display identification number sent by the server when it is determined that the taxi-hailing application on the passenger side is a new version.

[0027] In the fifth aspect, an embodiment of the present application provides an electronic device, comprising: a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps in the driving route synchronization method described in the first aspect or the second aspect are implemented.

[0028] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps in the driving route synchronization method described in the first aspect or the second aspect are implemented.

[0029] In the embodiment of the present application, in order to synchronize the driving route selected by the passenger to the taxi driver side, the server sets the order number to be the same as the driver-passenger ID sent by the passenger-side APP. In this way, even if the taxi driver-side APP still uses the order number as the driver-passenger ID, the driver-passenger ID on both sides can be the same, thereby synchronizing the driving route selected by the passenger to the taxi driver-side APP. To achieve this goal, the embodiment of the present application does not require any changes to the passenger-side APP and the taxi driver-side APP, and the program changes are relatively small, which is conducive to saving manpower and costs. And because the driving route selected by the passenger can be synchronized to the taxi driver-side APP, the taxi driver can drive according to the route selected by the passenger, thereby reducing the difference between the estimated cost before the start of the trip and the actual cost after the end of the trip, reducing user complaints and user churn, and reducing the customer service costs of handling complaints. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] To more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for describing the embodiments of the present application. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be derived from these drawings without inventive effort.

[0031] Figure 1 A schematic diagram of a process flow of a driving route synchronization method applied to a server side provided in an embodiment of the present application;

[0032] Figure 2 A schematic diagram of the overall process of the driving route synchronization method provided in an embodiment of the present application;

[0033] Figure 3 A schematic diagram of the application upgrade process provided in an embodiment of the present application;

[0034] Figure 4 A flowchart of a driving route synchronization method applied to a driver terminal provided in an embodiment of the present application;

[0035] Figure 5 A block diagram of a driving route synchronization device applied to a server side provided in an embodiment of the present application;

[0036] Figure 6 A block diagram of a driving route synchronization device applied to a driver terminal provided in an embodiment of the present application;

[0037] Figure 7 A block diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. It should be noted that the embodiments described herein are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments described herein, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0039] According to one aspect of an embodiment of the present application, a driving route synchronization method is provided, which is applied to a server.

[0040] like Figure 1 As shown, the driving route synchronization method may include:

[0041] Step 101: Receive the driver-passenger identification number generated by the passenger-side taxi-hailing application and sent after the passenger places an order.

[0042] Passengers can place orders through the passenger-side taxi application (also known as the passenger-side APP) installed in the passenger terminal, such as Figure 2 As shown, during the ordering process, the passenger can select the starting point and the end point. The passenger-side APP determines the starting point and the end point selected by the passenger, and plans the driving route through the map function, and then displays multiple driving routes for the passenger to choose. After that, the passenger-side APP determines the driving route selected by the passenger, and generates a driver-passenger simultaneous display identification number (also known as the driver-passenger simultaneous display ID, or simply sctxid), and then sets the driver-passenger simultaneous display ID through the map interface, that is: the generated driver-passenger simultaneous display ID is sent to the map SDK (Software Development Kit) for synchronization of the driving route. After the passenger-side APP confirms the passenger's order, it transmits the generated driver-passenger simultaneous display ID and order information (such as the order starting point, order end point, etc.) to the server (corresponding to the online car-hailing platform) through the corresponding interface.

[0043] Step 102: When it is detected that the taxi driver has accepted the order, the order number of the passenger's current taxi is set to the driver-passenger identification number sent by the passenger-side taxi application.

[0044] The reason why the existing technology cannot synchronize the passenger's selected route with the taxi driver's app is that the taxi driver's app sets the driver-passenger ID used for synchronizing the route as the order number (the order number is different from the driver-passenger ID), which results in a difference between the driver-passenger ID set by the passenger's app for synchronizing the route. In an embodiment of the present application, the server can set the order number of the passenger's current taxi ride to be the same as the driver-passenger ID sent by the passenger's app. In this way, even if the taxi driver's app still uses the order number as the driver-passenger ID, the driver-passenger ID on both sides can be the same, thereby synchronizing the passenger's selected route with the taxi driver's app.

[0045] From the above description, it can be seen that in order to achieve the purpose of synchronizing the driving route selected by the passenger to the taxi driver-side APP, the embodiment of the present application only requires the server to set the order number to be the same as the driver and passenger ID sent by the passenger-side APP. The passenger-side APP and the taxi driver-side APP do not need to be modified, and the program changes are relatively small, which is conducive to saving manpower and costs.

[0046] After receiving the driver ID and order information from the passenger app, the server dispatches the order. Upon detecting that a driver has accepted the order, the server determines whether the driver is a taxi driver. If so, the order number for the passenger's current ride is set to the driver ID sent by the passenger app. If not, the server does not need to set the order number to the driver ID sent by the passenger app. This prevents the server from performing unnecessary processing.

[0047] Step 103: Send the order number to the taxi driver's taxi hailing application, so that the taxi driver's taxi hailing application sets its own driver and passenger identification number as the order number.

[0048] After the server sets the order number of the passenger's taxi to the driver-passenger ID sent by the passenger-side APP, it can send the order details including the order number of the passenger's taxi to the taxi driver-side APP. Optionally, the order details can also include the driver-passenger ID sent by the passenger-side APP. After the taxi driver accepts the order, the taxi driver-side APP can obtain the order number from the order details sent by the server, and then set the driver-passenger ID on its own side as the order number, thereby synchronizing the driving route selected by the passenger to the taxi driver-side APP, so that the taxi driver can drive according to the route selected by the passenger, thereby reducing the difference between the estimated cost before the start of the trip and the actual cost after the end of the trip, reducing user complaints and user churn, and reducing the customer service cost of handling complaints. In addition, in the embodiment of the present application, the production problem that the taxi driver-side APP does not support the passenger's route selection can be solved without modifying the server interface, and the server-side resource consumption is small, which is conducive to saving server-side resources.

[0049] As an optional embodiment, in the embodiments of the present application, the passenger-side taxi-hailing application installed in the passenger terminal may include: a new version of the passenger-side taxi-hailing application or an old version of the passenger-side taxi-hailing application. The new and old versions of the passenger-side taxi-hailing application generate different driver and passenger identification codes. Specifically, the difference in the driver and passenger identification codes generated by the new and old versions of the passenger-side taxi-hailing application may be a difference in composition structure, such as a difference in the number of characters included in the character string used to represent the driver and passenger identification code, or a difference in the number of character strings used to represent the driver and passenger identification code.

[0050] In order to solve the problem that the taxi driver-side APP does not support passenger route selection, the taxi driver-side APP can also be upgraded, that is: adjust the application so that the adjusted application can set the driver and passenger ID to the driver and passenger ID sent by the passenger side, thereby obtaining a new version of the taxi driver-side APP. Among them, in order to enable passengers to know the location information of the taxi driver, the location information of the taxi driver can also be synchronized to the passenger-side APP during the order process. The synchronization method is: the passenger-side APP sets the same driver and passenger ID as the taxi driver-side APP. Among them, in the process of synchronizing the driving route selected by the passenger and synchronizing the driver's location information, the passenger-side APP needs to set the driver and passenger ID twice, once to synchronize the driving route selected by the passenger to the taxi driver-side APP, and the other time to synchronize the taxi driver's location information. The taxi driver-side APP only needs to set the driver and passenger ID once. Under this premise, for the upgraded taxi driver-side APP, since it sets the driver-passenger simultaneous display ID to the driver-passenger simultaneous display ID sent by the passenger side, and no longer the order number, in order to enable the passenger-side APP to synchronize the taxi driver's location information (the old version of the passenger-side APP sets the driver-passenger simultaneous display ID to the order number to synchronize the taxi driver's location information), the passenger-side APP can also be upgraded, that is: the application is adjusted so that the adjusted application can set the driver-passenger simultaneous display ID to the driver-passenger simultaneous display ID set for the first time when setting the driver-passenger simultaneous display ID for the second time, thereby obtaining the new version of the passenger-side APP. However, since not all passengers can upgrade the APP in time, the passenger-side APP installed in the passenger terminal may be the new version of the passenger-side APP or the old version of the passenger-side APP. For this case, in order to facilitate the distinction between the new and old versions of the passenger-side APP, the embodiment of the present application designs that the driver-passenger simultaneous display identification numbers generated by the new and old versions of the passenger-side APP are different.

[0051] It should be noted that when the old version of the passenger-side APP synchronizes the taxi driver's location information, it uses the order number as the driver-passenger ID; when the new version of the passenger-side APP synchronizes the taxi driver's location information, it uses the driver-passenger ID generated by itself.

[0052] Step 102: setting the passenger's order number for this taxi as the driver-passenger identification number may include:

[0053] The version of the taxi-hailing application on the passenger side is determined based on the driver-passenger simultaneous display identification number; if it is determined that the taxi-hailing application on the passenger side is an old version, the order number of the passenger's current taxi is set as the driver-passenger simultaneous display identification number.

[0054] Because the new and old versions of the passenger app generate different driver and passenger IDs, the server can determine the passenger app version based on the driver and passenger ID sent by the passenger app. If it determines that the passenger app is an old version, it will set the passenger's order number for the current ride to the driver and passenger ID. This makes the server compatible with both new and old versions of the passenger app, providing a transitional method for passenger app upgrades.

[0055] Among them, when the server determines that the passenger-side APP is a new version based on the driver-passenger simultaneous display ID sent by the passenger-side APP, the order number can be generated according to the original generation rules, and there is no need to set the order number to the driver-passenger simultaneous display ID.

[0056] Optionally, an embodiment of the present application provides a rule for generating a driver and passenger ID for the new and old versions of the passenger-side APP, specifically: the driver and passenger ID generated by the old version of the passenger-side APP is a random unique coding string (i.e., a random and unique coding string), and the driver and passenger ID generated by the new version of the passenger-side APP includes a random unique coding string and a fixed string, that is, the number of strings used to represent the driver and passenger identification number is different. The driver and passenger ID generated by the old version of the passenger-side APP is one string, and the driver and passenger ID generated by the new version of the passenger-side APP is two strings.

[0057] The aforementioned step of determining the version of the passenger-side taxi-hailing application based on the driver-passenger simultaneous identification number may include:

[0058] When the driver and passenger identification numbers displayed together include a fixed string, it is determined that the taxi-hailing application on the passenger side is a new version; when the driver and passenger identification numbers displayed together do not include a fixed string, it is determined that the taxi-hailing application on the passenger side is an old version.

[0059] By adding a fixed string to the driver and passenger ID generated by the new version of the passenger app, the server can distinguish between the new and old versions of the passenger app based on this. Figure 2 As shown, after receiving the driver-passenger ID and order information from the passenger app, the server determines whether the received driver-passenger ID contains a fixed string. If the fixed string is not included in the driver-passenger ID, the server determines that the passenger app is an old version, sets the passenger's order number as the driver-passenger ID, and then dispatches the order. If the driver-passenger ID contains the fixed string, the server determines that the passenger app is a new version and dispatches the order directly.

[0060] As an optional embodiment, since not all taxi drivers can upgrade their APP in a timely manner, the taxi driver-side APP installed in the driver's terminal may be a new version that supports the passenger routing function, or an old version that does not support the passenger routing function. In order to improve the efficiency of application upgrades, the embodiment of the present application also provides an application upgrade method, which may include:

[0061] Count the coverage rate of the new version of the taxi driver-side taxi-hailing application; when the coverage rate is less than the preset value, send a weak upgrade reminder message to the old version of the taxi driver-side APP; when the coverage rate is greater than or equal to the preset value, control the old version of the taxi driver-side APP to automatically upgrade, and send a weak upgrade reminder message to the old version of the passenger-side APP.

[0062] It is not appropriate to force the upgrade of the passenger-side APP. In order to improve the passengers' ride-hailing experience, the new version of the taxi driver-side APP can be released first according to the version release strategy, so that the taxi driver-side APP can be upgraded first. Figure 3 As shown, the server can count the coverage rate of the new version of the taxi driver-side APP (i.e., the upgrade rate of the taxi driver-side APP) in real time or at regular intervals, and determine whether the coverage rate reaches a preset value.

[0063] When the coverage rate of the new version of the taxi driver-side APP is less than a preset value (such as 90%), a weak upgrade reminder is controlled in the old version of the taxi driver-side APP to remind taxi drivers to upgrade the application.

[0064] When the coverage rate of the new version of the taxi driver-side APP is greater than or equal to a preset value (such as 90%), it means that most taxi drivers have upgraded the taxi driver-side APP to the new version. In this case, the new version of the passenger-side APP can be released to the application market, and the server can control the weak upgrade reminder in the old version of the passenger-side APP to remind passengers to upgrade the passenger-side APP. At the same time, for the old version of the taxi driver-side APP, a forced upgrade strategy can be adopted (that is, controlling the old version of the taxi driver-side APP to automatically upgrade) to achieve the purpose of upgrading all taxi driver-side APPs to the new version.

[0065] Among them, the aforementioned preset value can be a larger percentage, such as 90%, 95%, etc., which can be set according to actual needs. The embodiment of the present application does not make specific limitations on this.

[0066] The new version of the taxi driver app supports setting the driver and passenger IDs as the server-sent IDs and the order number as the IDs sent by the server. The old version of the taxi driver app only supports setting the driver and passenger IDs as the order number.

[0067] The above is a description of the driving route synchronization method applied to the server provided in an embodiment of the present application.

[0068] In summary, in the embodiment of the present application, in order to synchronize the driving route selected by the passenger to the taxi driver side, the server sets the order number to be the same as the driver-passenger ID sent by the passenger-side APP. In this way, even if the taxi driver-side APP still uses the order number as the driver-passenger ID, the driver-passenger ID on both sides can be the same, thereby synchronizing the driving route selected by the passenger to the taxi driver-side APP. In order to achieve this goal, the embodiment of the present application does not require any changes to the passenger-side APP and the taxi driver-side APP, and the program changes are relatively small, which is conducive to saving manpower and costs. And because the driving route selected by the passenger can be synchronized to the taxi driver-side APP, the taxi driver can drive according to the route selected by the passenger, thereby reducing the difference between the estimated cost before the start of the trip and the actual cost after the end of the trip, reducing user complaints and user churn, and reducing the customer service costs of handling complaints.

[0069] According to another aspect of an embodiment of the present application, a driving route synchronization method is provided, which is applied to a driver terminal, in which a new version of a taxi driver-side APP that supports a passenger route selection function is installed.

[0070] like Figure 4 As shown, the driving route synchronization method may include:

[0071] Step 401: When the taxi driver has accepted the order, the driver and passenger identification number and the passenger's order number for this taxi ride are received from the server.

[0072] Among them, the driver and passenger identification number mentioned here is generated by the passenger-side APP and sent to the server after the passenger places an order.

[0073] Passengers can place orders through the passenger-side APP installed in the passenger terminal, such as Figure 2As shown, during the ordering process, the passenger can select a starting point and a destination. The passenger-side app determines the passenger's selected starting and ending points, plans a route using the map function, and then displays multiple routes for the passenger to choose from. The passenger-side app then determines the passenger's selected route and generates a driver-passenger ID. The ID is then set via the map interface, i.e., the generated driver-passenger ID is sent to the map SDK for route synchronization. After the passenger-side app confirms the passenger's order, it sends the generated driver-passenger ID and order information (such as the order starting point and destination) to the server (i.e., the online ride-hailing platform) via the corresponding interface. After receiving the driver-passenger ID and order information from the passenger-side app, the server dispatches the order and, if it detects a driver accepting the order, sends the order details, including the driver-passenger ID sent by the passenger-side app and the passenger's order number, to the taxi driver-side app. After the taxi driver accepts the order, the taxi driver-side app can obtain the sctxid field (i.e., the driver-passenger ID) and order number from the order details sent by the server.

[0074] Step 402: Determine the version of the taxi-hailing application on the passenger side based on the driver and passenger identification numbers.

[0075] In an embodiment of the present application, the passenger-side app installed in the passenger terminal may include: a new version of the passenger-side app or an old version of the passenger-side app. The new and old versions of the passenger-side app generate different driver and passenger identification codes. Therefore, the taxi driver-side app can determine the version of the passenger-side app based on the driver and passenger identification codes generated and sent by the passenger-side app. Specifically, the difference in the driver and passenger identification codes generated by the new and old versions of the passenger-side taxi-hailing app may be due to a different composition structure, such as a different number of characters included in the string used to represent the driver and passenger identification code, or a different number of character strings used to represent the driver and passenger identification code.

[0076] The reason why the route selected by the passenger cannot be synchronized to the taxi driver-side APP in the existing technology is that the taxi driver-side APP sets the driver-passenger ID used to synchronize the route to the order number (the order number is different from the driver-passenger ID), which makes it different from the driver-passenger ID set by the passenger-side APP for synchronizing the route. In order to solve the problem that the taxi driver-side APP does not support passenger route selection, the taxi driver-side APP can be upgraded, that is, the application is adjusted so that the adjusted application can set the driver-passenger ID to the driver-passenger ID sent by the passenger side, thereby obtaining a new version of the taxi driver-side APP. Among them, in order to enable passengers to know the location information of the taxi driver, the location information of the taxi driver can also be synchronized to the passenger-side APP during the order process. The synchronization method is: the passenger-side APP sets the same driver-passenger ID as the taxi driver-side APP.

[0077] Among them, in the process of synchronizing the driving route selected by the passenger and synchronizing the driver's location information, the passenger-side APP needs to set the driver-passenger simultaneous display ID twice, once to synchronize the driving route selected by the passenger to the taxi driver-side APP, and the other time to synchronize the taxi driver's location information. The taxi driver-side APP only needs to set the driver-passenger simultaneous display ID once. Under this premise, for the upgraded taxi driver-side APP, since it sets the driver-passenger simultaneous display ID to the driver-passenger simultaneous display ID sent by the passenger side, it is no longer the order number. Therefore, in order to enable the passenger-side APP to synchronize the taxi driver's location information (the old version of the passenger-side APP sets the driver-passenger simultaneous display ID to the order number to synchronize the taxi driver's location information), the passenger-side APP can also be upgraded, that is: adjust the application so that when the adjusted application sets the driver-passenger simultaneous display ID for the second time, it can set the driver-passenger simultaneous display ID to the driver-passenger simultaneous display ID set for the first time, thereby obtaining the new version of the passenger-side APP. However, since not all passengers can upgrade the APP in time, the passenger-side APP installed in the passenger terminal may be the new version of the passenger-side APP or the old version of the passenger-side APP. In this case, in order to facilitate the distinction between the new and old versions of the passenger-side APP, the embodiment of the present application is designed so that the driver and passenger identification numbers generated by the new and old versions of the passenger-side APP are different.

[0078] It should be noted that when the old version of the passenger-side APP synchronizes the taxi driver's location information, it uses the order number as the driver-passenger ID; when the new version of the passenger-side APP synchronizes the taxi driver's location information, it uses the driver-passenger ID generated by itself.

[0079] Step 403: When it is determined that the taxi-hailing application on the passenger side is an old version, the driver-passenger identification number on the own side is set as the order number.

[0080] In an embodiment of the present application, when the passenger-side taxi-hailing application is an old version, the server can set the order number of the passenger's taxi to be the same as the driver-passenger ID sent by the passenger-side APP. In this way, even if the taxi driver-side APP still uses the order number as the driver-passenger ID, the driver-passenger ID on both ends can be made the same, thereby realizing the synchronization of the passenger's selected route to the taxi driver-side APP.

[0081] From the above description, it can be seen that in order to achieve the purpose of synchronizing the driving route selected by the passenger to the taxi driver-side APP, the embodiment of the present application only requires the server to set the order number to be the same as the driver and passenger ID sent by the passenger-side APP. The passenger-side APP and the taxi driver-side APP do not need to be modified, and the program changes are relatively small, which is conducive to saving manpower and costs.

[0082] Step 404: When it is determined that the taxi-hailing application on the passenger side is a new version, the driver-passenger simultaneous display identification number on the passenger side is set to the driver-passenger simultaneous display identification number sent by the server.

[0083] When the taxi driver-side APP determines that the passenger-side taxi application is a new version based on the driver-passenger simultaneous display ID sent by the server, the driver-passenger simultaneous display ID on its own side can be set to the driver-passenger simultaneous display ID sent by the server, thereby synchronizing the driving route selected by the passenger to the taxi driver-side APP.

[0084] To synchronize the driver's location information with the new version of the passenger app, the new version of the passenger app can use its self-generated driver-passenger ID and send it to the map SDK, ensuring that both the driver and passenger have the same ID. Alternatively, the new version of the passenger app can obtain the order details and the sctxid field (i.e., the driver-passenger ID) in the order details, and then directly set the driver-passenger ID through the map interface.

[0085] In the embodiment of the present application, by setting the driver and passenger IDs generated by the new and old versions of the passenger-side taxi application to be different, the new version of the taxi driver-side APP can distinguish between the new and old versions of the passenger-side APP, thereby achieving synchronization of passenger route selection for the new and old versions of the passenger-side APP respectively, achieving compatibility with the new and old versions of the passenger-side APP, and providing a transition method for the upgrade of the passenger-side APP. In addition, in the embodiment of the present application, the production problem that the taxi driver-side APP does not support passenger route selection can be solved without modifying the server interface, and the server-side resource consumption is small, which is conducive to saving server-side resources. In addition, since the synchronization of passenger route selection is achieved, the taxi driver can drive according to the route selected by the passenger, thereby reducing the difference between the estimated cost before the start of the trip and the actual cost after the end of the trip, reducing user complaints and user churn, and reducing the customer service cost of handling complaints. Furthermore, in the embodiment of the present application, the synchronization of passenger route selection is achieved by setting the driver and passenger IDs before the start of the trip, and the implementation method is simple.

[0086] As an optional embodiment, the embodiment of the present application also provides a rule for generating the driver and passenger simultaneous display ID for the new and old versions of the passenger-side APP. Specifically, the driver and passenger simultaneous display ID generated by the old version of the passenger-side APP is a random unique coding string (that is, a random and unique coding string), and the driver and passenger simultaneous display ID generated by the new version of the passenger-side APP includes a random unique coding string and a fixed string, that is, the number of strings used to represent the driver and passenger simultaneous display identification number is different. The driver and passenger simultaneous display ID generated by the old version of the passenger-side APP is one string, and the driver and passenger simultaneous display ID generated by the new version of the passenger-side APP is two strings.

[0087] Step 402: determining the version of the passenger-side taxi-hailing application based on the driver-passenger simultaneous display identification number may include:

[0088] When the driver and passenger identification numbers displayed together include a fixed string, it is determined that the taxi-hailing application on the passenger side is a new version; when the driver and passenger identification numbers displayed together do not include a fixed string, it is determined that the taxi-hailing application on the passenger side is an old version.

[0089] By adding a fixed string to the driver and passenger ID generated by the new version of the passenger app, the taxi driver app can distinguish between the new and old versions of the passenger app based on this. Figure 2 As shown, after the taxi driver's app receives the driver-passenger ID and order information sent by the server, it determines whether the received driver-passenger ID contains a fixed string. If the driver-passenger ID does not contain a fixed string, the passenger's app is determined to be an old version. The passenger's order number is then set as the driver-passenger ID, synchronizing the driving route and displaying the passenger's selected route. If the driver-passenger ID does contain a fixed string, the driver-passenger ID sent by the passenger app is set as the driver-passenger ID on the passenger's app, synchronizing the driving route and displaying the passenger's selected route.

[0090] The above is a description of the driving route synchronization method applied to the driver terminal provided in the embodiment of the present application.

[0091] In summary, in the embodiments of the present application, by setting different driver and passenger IDs generated by the new and old versions of the passenger-side taxi app, the new version of the taxi driver-side app can distinguish between the new and old versions of the passenger-side app, thereby achieving synchronization of passenger route selection for the new and old versions of the passenger-side app, achieving compatibility between the new and old versions of the passenger-side app, and providing a transitional method for passenger-side app upgrades. In addition, since the synchronization of passenger route selection is achieved, taxi drivers can drive according to the route selected by the passenger, thereby reducing the difference between the estimated fare before the trip and the actual fare after the trip, reducing user complaints and user churn, and lowering the customer service costs of handling complaints.

[0092] The driving route synchronization method provided in the embodiment of the present application has been described in detail above. Now, the driving route synchronization device provided in the embodiment of the present application will be described below.

[0093] According to another aspect of the present application, a driving route synchronization device is provided for use in a server. The driving route synchronization device can implement the specific details of the driving route synchronization method embodiment applied to the server and achieve the same technical effects.

[0094] like Figure 5As shown, the driving route synchronization device may include:

[0095] The first receiving module 501 is used to receive the driver-passenger simultaneous display identification number generated by the passenger-side taxi-hailing application and sent after the passenger places an order.

[0096] The first setting module 502 is used to set the order number of the passenger's current taxi as the driver-passenger simultaneous display identification number when it is detected that the taxi driver has accepted the order.

[0097] The first sending module 503 is used to send the order number to the taxi driver's taxi hailing application, so that the taxi driver's taxi hailing application sets its own driver and passenger simultaneous display identification number as the order number.

[0098] Optionally, the passenger-side taxi-hailing application installed in the passenger terminal is: a new version of the passenger-side taxi-hailing application or an old version of the passenger-side taxi-hailing application, wherein the driver and passenger identification numbers generated by the new and old versions of the passenger-side taxi-hailing applications are different.

[0099] The first setting module 502 may include:

[0100] The first determination submodule is used to determine the version of the passenger-side taxi-hailing application according to the driver-passenger simultaneous display identification number.

[0101] A submodule is set up for setting the order number of the passenger's current taxi as the driver-passenger simultaneous display identification number when it is determined that the taxi application on the passenger side is an old version.

[0102] Optionally, the driver and passenger identification number generated by the old version of the passenger-side taxi-hailing application is a random unique coding string; the driver and passenger identification number generated by the new version of the passenger-side taxi-hailing application includes a random unique coding string and a fixed string.

[0103] Optionally, the first determining submodule may include:

[0104] The first determining unit is configured to determine that the passenger-side taxi-hailing application is a new version when the driver-passenger simultaneous display identification number includes the fixed character string.

[0105] The second determining unit is configured to determine that the taxi-hailing application on the passenger side is an old version when the driver-passenger identification code does not include the fixed character string.

[0106] Optionally, the taxi driver-side taxi-hailing application installed in the driver terminal is: a new version of the taxi driver-side taxi-hailing application or an old version of the taxi driver-side taxi-hailing application; wherein, the new version of the taxi driver-side taxi-hailing application supports the passenger routing function, and the old version of the taxi driver-side taxi-hailing application does not support the passenger routing function.

[0107] The apparatus may further comprise:

[0108] The statistics module is used to count the coverage of the new version of the taxi driver-side taxi-hailing application.

[0109] The first upgrade processing module is used to send an upgrade weak reminder message to the old version of the taxi driver-side taxi-hailing application when the coverage rate is less than a preset value.

[0110] The second upgrade processing module is used to control the old version of the taxi driver-side taxi-hailing application to automatically upgrade when the coverage rate is greater than or equal to the preset value, and to send a weak upgrade reminder message to the old version of the passenger-side taxi-hailing application.

[0111] As for the above-mentioned driving route synchronization device embodiment, since it is basically similar to the above-mentioned driving route synchronization method embodiment applied to the server, the relevant parts can be referred to the partial description of the method embodiment. In order to avoid repetition, it will not be described here.

[0112] The driving route synchronization device provided in the embodiment of the present application is to synchronize the driving route selected by the passenger to the taxi driver side. The server sets the order number to be the same as the driver-passenger ID sent by the passenger-side APP. In this way, even if the taxi driver-side APP still uses the order number as the driver-passenger ID, the driver-passenger ID on both ends can be the same, thereby synchronizing the driving route selected by the passenger to the taxi driver-side APP. In order to achieve this purpose, the embodiment of the present application does not require any changes to the passenger-side APP and the taxi driver-side APP, and the program changes are relatively small, which is conducive to saving manpower and costs. And because the driving route selected by the passenger can be synchronized to the taxi driver-side APP, the taxi driver can drive according to the route selected by the passenger, thereby reducing the difference between the estimated cost before the start of the trip and the actual cost after the end of the trip, reducing user complaints and user churn, and reducing the customer service costs of handling complaints.

[0113] According to another aspect of the present application, a driving route synchronization device is provided for use with a driver terminal installed with a new version of a taxi driver-side taxi-hailing app that supports passenger routing. This driving route synchronization device can implement the specific details of the driving route synchronization method embodiment for the driver terminal described above, achieving the same technical effects.

[0114] like Figure 6 As shown, the driving route synchronization device may include:

[0115] The second receiving module 601 is used to receive the driver-passenger simultaneous display identification number and the passenger's order number for this taxi ride sent by the server when the taxi driver has accepted the order.

[0116] Among them, the driver and passenger identification number is generated by the passenger-side taxi application and sent to the server after the passenger places an order.

[0117] The determination module 602 is used to determine the version of the taxi-hailing application on the passenger side according to the driver-passenger simultaneous display identification number.

[0118] Among them, the driver and passenger identification numbers generated by the new and old versions of the passenger-side taxi-hailing application are different.

[0119] The second setting module 603 is used to set the driver and passenger identification number of the self-side as the order number when it is determined that the taxi-hailing application on the passenger side is an old version.

[0120] Among them, when the passenger-side taxi-hailing application is an old version, the server sets the order number to be the same as the driver and passenger identification number sent by the passenger-side taxi-hailing application.

[0121] The third setting module 604 is used to set the driver and passenger simultaneous display identification number of the passenger side to the driver and passenger simultaneous display identification number sent by the server when it is determined that the taxi-hailing application on the passenger side is a new version.

[0122] Optionally, the driver and passenger identification number generated by the old version of the passenger-side taxi-hailing application is a random unique coding string; the driver and passenger identification number generated by the new version of the passenger-side taxi-hailing application includes a random unique coding string and a fixed string.

[0123] Optionally, the determining module 602 may include:

[0124] The second determining submodule is configured to determine that the taxi-hailing application on the passenger side is a new version when the driver-passenger identification number includes the fixed character string.

[0125] The third determining submodule is configured to determine that the taxi-hailing application on the passenger side is an old version when the driver-passenger identification code does not include the fixed character string.

[0126] As for the above-mentioned driving route synchronization device embodiment, since it is basically similar to the above-mentioned driving route synchronization method embodiment applied to the driver terminal, the relevant parts can be referred to the partial description of the method embodiment. In order to avoid repetition, it will not be described here.

[0127] The route synchronization device provided in the embodiments of the present application distinguishes the driver and passenger IDs generated by the new and old versions of the passenger-side taxi app. This allows the new version of the taxi driver-side app to distinguish between the new and old versions of the passenger-side app, thereby synchronizing passenger route selection for the new and old versions of the passenger-side app, achieving compatibility between the new and old versions of the passenger-side app and providing a transitional method for passenger-side app upgrades. Furthermore, since passenger route selection synchronization is achieved, taxi drivers can follow the route selected by the passenger, thereby reducing the difference between the estimated fare before the trip and the actual fare after the trip, reducing user complaints and user churn, and lowering customer service costs for handling complaints.

[0128] According to another aspect of an embodiment of the present application, an electronic device is provided, which includes: a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps in the driving route synchronization method as described above are implemented.

[0129] Here is an example: Figure 7 A schematic diagram of the physical structure of an electronic device is shown.

[0130] like Figure 7 As shown, the electronic device may include: a processor (processor) 710, a communication interface (Communications Interface) 720, a memory (memory) 730 and a communication bus 740, wherein the processor 710, the communication interface 720 and the memory 730 communicate with each other through the communication bus 740.

[0131] In the case where the electronic device is the above-mentioned server, the processor 710 may call the logic instructions in the memory 730 to execute the following method:

[0132] Receive the driver-passenger simultaneous display identification number generated by the passenger-side taxi-hailing application and sent after the passenger places an order; when it is detected that the taxi driver has accepted the order, set the order number of the passenger's taxi ride as the driver-passenger simultaneous display identification number; send the order number to the taxi driver-side taxi-hailing application, so that the taxi driver-side taxi-hailing application sets the driver-passenger simultaneous display identification number on its own side to the order number.

[0133] In the case where the electronic device is the driver terminal described above, the processor 710 may call the logic instructions in the memory 730 to execute the following method:

[0134] If the taxi driver has accepted the order, the server receives the driver-passenger identification number and the passenger's order number for this taxi ride. The driver-passenger identification number is generated by the passenger's taxi app and sent to the server after the passenger places the order.

[0135] Determining the version of the passenger-side taxi-hailing application based on the driver-passenger simultaneous display identification number; wherein the driver-passenger simultaneous display identification numbers generated by the new and old versions of the passenger-side taxi-hailing application are different;

[0136] If it is determined that the taxi-hailing application on the passenger side is an old version, the server sets the driver-passenger identification number on the server side to the order number; wherein, if the taxi-hailing application on the passenger side is an old version, the server sets the order number to be the same as the driver-passenger identification number sent by the taxi-hailing application on the passenger side;

[0137] When it is determined that the taxi-hailing application on the passenger side is a new version, the driver-passenger simultaneous display identification number on the passenger side is set to the driver-passenger simultaneous display identification number sent by the server.

[0138] In addition, the logic instructions in the above-mentioned memory 730 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when sold or used as an independent product. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0139] According to another aspect of the embodiments of the present application, a computer-readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps in the above-mentioned driving route synchronization method are implemented, for example:

[0140] Receive the driver-passenger simultaneous display identification number generated by the passenger-side taxi-hailing application and sent after the passenger places an order; when it is detected that the taxi driver has accepted the order, set the order number of the passenger's taxi ride as the driver-passenger simultaneous display identification number; send the order number to the taxi driver-side taxi-hailing application, so that the taxi driver-side taxi-hailing application sets the driver-passenger simultaneous display identification number on its own side to the order number.

[0141] or,

[0142] When the taxi driver has accepted the order, the driver and passenger simultaneous display identification number and the passenger's order number for this taxi are received from the server; wherein, the driver and passenger simultaneous display identification number is generated by the passenger-side taxi application and sent to the server after the passenger places the order; according to the driver and passenger simultaneous display identification number, the version of the passenger-side taxi application is determined; wherein, the driver and passenger simultaneous display identification numbers generated by the new and old versions of the passenger-side taxi application are different; when it is determined that the passenger-side taxi application is an old version, the driver and passenger simultaneous display identification number of its own side is set to the order number; wherein, when the passenger-side taxi application is an old version, the server sets the order number to be the same as the driver and passenger simultaneous display identification number sent by the passenger-side taxi application; when it is determined that the passenger-side taxi application is a new version, the driver and passenger simultaneous display identification number of its own side is set to the driver and passenger simultaneous display identification number sent by the server.

[0143] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, i.e., they may be located in one location or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of the present embodiment. Persons of ordinary skill in the art will be able to understand and implement the present invention without inventive effort.

[0144] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary general hardware platform, or of course, by hardware. Based on this understanding, the essence of the above technical solution or the part that contributes to the existing technology can be embodied in the form of a software product. The computer software product can be stored in a computer-readable storage medium, such as ROM, RAM, magnetic disk, optical disk, etc., and includes a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute the methods described in each embodiment or certain parts of the embodiment.

[0145] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A driving route synchronization method, applied to a server, characterized in that: The method comprises: Receiving a driver-passenger identification number generated by a passenger-side taxi-hailing application and sent after the passenger places an order, the driver-passenger identification number being generated based on the travel route selected by the passenger; When it is detected that the taxi driver has accepted the order, the order number of the passenger's current taxi is set as the driver-passenger simultaneous display identification number, which includes: determining whether the driver who accepted the order is a taxi driver, if the driver who accepted the order is a taxi driver, setting the order number of the passenger's current taxi as the driver-passenger simultaneous display identification number; if the driver who accepted the order is not a taxi driver, there is no need to set the order number of the passenger's current taxi as the driver-passenger simultaneous display identification number; The order number is sent to the taxi driver's taxi hailing application, so that the taxi driver's taxi hailing application sets its own driver and passenger identification number to the order number.

2. The driving route synchronization method according to claim 1, characterized in that: The passenger-side taxi-hailing application installed on the passenger terminal is: a new version of the passenger-side taxi-hailing application or an old version of the passenger-side taxi-hailing application, wherein the driver and passenger identification numbers generated by the new and old versions of the passenger-side taxi-hailing application are different; The step of setting the order number of the passenger's current taxi as the driver-passenger simultaneous display identification number includes: Determining the version of the passenger-side taxi-hailing application based on the driver-passenger simultaneous display identification number; When it is determined that the taxi-hailing application on the passenger side is an old version, the order number of the passenger's current taxi-hailing application is set as the driver-passenger simultaneous display identification number.

3. The driving route synchronization method according to claim 2, characterized in that: The driver and passenger identification numbers generated by the old version of the passenger-side taxi-hailing application are random unique coding strings; the driver and passenger identification numbers generated by the new version of the passenger-side taxi-hailing application include random unique coding strings and fixed strings.

4. The driving route synchronization method according to claim 3, characterized in that: Determining the version of the passenger-side taxi-hailing application based on the driver-passenger simultaneous display identification number includes: When the driver-passenger identification code includes the fixed character string, determining that the passenger-side taxi-hailing application is a new version; When the driver-passenger identification code does not include the fixed character string, it is determined that the passenger-side taxi-hailing application is an old version.

5. The driving route synchronization method according to claim 2, characterized in that: The taxi driver-side taxi hailing application installed in the driver terminal is: a new version of the taxi driver-side taxi hailing application or an old version of the taxi driver-side taxi hailing application; wherein the new version of the taxi driver-side taxi hailing application supports a passenger routing function, and the old version of the taxi driver-side taxi hailing application does not support a passenger routing function; The method further comprises: Count the coverage of the new version of the taxi driver-side taxi hailing app; When the coverage rate is less than a preset value, a weak upgrade reminder message is sent to the old version of the taxi driver-side taxi hailing application; When the coverage rate is greater than or equal to the preset value, the old version of the taxi driver-side taxi-hailing application is controlled to automatically upgrade, and a weak upgrade reminder message is sent to the old version of the taxi passenger-side taxi-hailing application.

6. A driving route synchronization method, applied to a driver terminal, characterized in that: The driver terminal is installed with a new version of the taxi driver-side taxi-hailing application that supports the passenger routing function; The driving route synchronization method comprises: If the taxi driver has accepted the order, the server receives the driver-passenger identification number and the passenger's order number for this taxi ride. The driver-passenger identification number is generated by the passenger's taxi app and sent to the server after the passenger places the order. Determining the version of the passenger-side taxi-hailing application based on the driver-passenger simultaneous display identification number; wherein the driver-passenger simultaneous display identification numbers generated by the new and old versions of the passenger-side taxi-hailing application are different; If it is determined that the taxi-hailing application on the passenger side is an old version, the server sets the driver-passenger identification number on the server side to the order number; wherein, if the taxi-hailing application on the passenger side is an old version, the server sets the order number to be the same as the driver-passenger identification number sent by the taxi-hailing application on the passenger side; When it is determined that the taxi-hailing application on the passenger side is a new version, the driver-passenger simultaneous display identification number on the passenger side is set to the driver-passenger simultaneous display identification number sent by the server.

7. The driving route synchronization method according to claim 6, characterized in that: The driver and passenger identification numbers generated by the old version of the passenger-side taxi-hailing application are random unique coding strings; the driver and passenger identification numbers generated by the new version of the passenger-side taxi-hailing application include random unique coding strings and fixed strings.

8. The driving route synchronization method according to claim 7, characterized in that: Determining the version of the passenger-side taxi-hailing application based on the driver-passenger simultaneous display identification number includes: When the driver-passenger identification code includes the fixed character string, determining that the passenger-side taxi-hailing application is a new version; When the driver-passenger identification code does not include the fixed character string, it is determined that the passenger-side taxi-hailing application is an old version.

9. A driving route synchronization device, applied to a server, characterized in that: The device comprises: A first receiving module is configured to receive a driver-passenger identification number generated by a passenger-side taxi-hailing application and sent after the passenger places an order, wherein the driver-passenger identification number is generated based on the driving route selected by the passenger; The first setting module is used to set the order number of the passenger's current taxi as the driver-passenger simultaneous display identification number when it is detected that the taxi driver has accepted the order, which includes: determining whether the driver who accepted the order is a taxi driver, and if so, setting the order number of the passenger's current taxi as the driver-passenger simultaneous display identification number; if the driver who accepted the order is not a taxi driver, there is no need to set the order number of the passenger's current taxi as the driver-passenger simultaneous display identification number; The first sending module is used to send the order number to the taxi driver's taxi hailing application, so that the taxi driver's taxi hailing application sets the driver and passenger simultaneous display identification number on its own side as the order number.

10. A driving route synchronization device, applied to a driver terminal, characterized in that: The driver terminal is installed with a new version of the taxi driver-side taxi-hailing application that supports the passenger routing function; The driving route synchronization device includes: The second receiving module is used to receive the driver-passenger simultaneous display identification number and the passenger's order number sent by the server when the taxi driver has accepted the order; wherein the driver-passenger simultaneous display identification number is generated by the passenger-side taxi application and sent to the server after the passenger places the order; a determination module for determining a version of the passenger-side taxi-hailing application based on the driver-passenger simultaneous display identification number; wherein the driver-passenger simultaneous display identification numbers generated by the new and old versions of the passenger-side taxi-hailing application are different; a second setting module, configured to, if it is determined that the passenger-side taxi-hailing application is an old version, set the driver-passenger simultaneous display identification number on the server side to the order number; wherein, if the passenger-side taxi-hailing application is an old version, the server sets the order number to be the same as the driver-passenger simultaneous display identification number sent by the passenger-side taxi-hailing application; The third setting module is used to set the driver and passenger simultaneous display identification number of the passenger side to the driver and passenger simultaneous display identification number sent by the server when it is determined that the taxi-hailing application on the passenger side is a new version.

11. An electronic device, characterized in that: include: A processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps in the driving route synchronization method as described in any one of claims 1 to 5 or claims 6 to 8 are implemented.

12. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a program or instruction, which, when executed by a processor, implements the steps in the driving route synchronization method according to any one of claims 1 to 5 or claims 6 to 8.

Images