Shared vehicle order management method, server and storage medium

Abstract

A shared vehicle order management method, applied to a server, includes: receiving a shared vehicle handover request from a user terminal; obtaining actual usage information and billing rules for the shared vehicle; calculating the vehicle usage remaining amount for the next billing; comparing the vehicle usage remaining amount with a set threshold; if the vehicle usage remaining amount is above the set threshold, obtaining the location information of the shared vehicle; obtaining at least one other user terminal around the location information; sending a handover request to the other user terminal; responding to a confirmation request from the other user terminal; if the confirmation request is a confirmation receipt request, sending a confirmation receipt reminder to the user terminal; and transferring the shared vehicle's occupancy information from the user terminal to the other user terminal. By enabling the shared vehicle to be handed over between multiple users, the shared vehicle usage cost can be shared among multiple users, reducing the cost of a single user using the shared vehicle alone, thereby greatly improving user satisfaction.

Description

Technical Field

[0001] The present invention relates to the technical field of shared vehicles, and in particular to a shared vehicle order management method, server, and storage medium. Background Art

[0002] Currently, shared mobility is becoming an increasingly important mode of transportation. For example, there are shared cars for long-distance travel, and shared bicycles / shared electric motorcycles for short-distance travel. Taking shared bicycles / shared electric motorcycles as an example, the fee is usually calculated based on the user's riding time / riding distance. For example, a ride of 10 minutes is charged a certain fee every 10 minutes. Rides of less than 10 minutes are charged as 10 minutes. Therefore, if a user rides for 11 minutes, they will still be charged for 20 minutes, which will result in a poor user experience. In addition, in the shared mobility sector, the same shared vehicle will serve multiple different users at different times, but there is no communication between multiple users, which is also not conducive to the maintenance and growth of the shared vehicle user base. Summary of the Invention

[0003] The purpose of the present invention is to provide a vehicle order management method to solve the problem that the existing order management method may deteriorate the user experience.

[0004] In one aspect, a method for managing an order for a shared vehicle is provided, which is applied to a server. The method for managing an order for a shared vehicle includes: receiving a handover request for a shared vehicle from a user terminal; obtaining actual usage information and billing rules of the shared vehicle; calculating the vehicle usage balance for the next billing based on the actual usage information and billing rules; comparing the vehicle usage balance with a set threshold; if the vehicle usage balance is above the set threshold, obtaining the location information of the shared vehicle; obtaining at least one other user terminal around the location information based on the location information; sending the handover request to the other user terminal; responding to a confirmation request from the other user terminal; if the confirmation request is a confirmation receipt request, sending a confirmation receipt reminder to the user terminal; and transferring the occupancy information of the shared vehicle from the user terminal to the other user terminal to complete the handover request.

[0005] By allowing shared vehicles to be transferred between multiple users, the cost of using a shared vehicle can be shared among them, reducing the cost for individual users when using a shared vehicle alone, thereby greatly improving user satisfaction. In addition, the transfer of shared vehicles allows multiple users to communicate with each other, which is conducive to the maintenance and growth of the shared vehicle user community.

[0006] Optionally, the actual usage information is the actual driving time, and the billing rule is a rule for charging according to the driving time; or, the actual usage information is the actual driving distance, and the billing rule is a rule for charging according to the driving distance.

[0007] Optionally, in response to the confirmation request of the other user terminal, if the confirmation request is multiple confirmation reception requests, the multiple confirmation reception requests are sorted to obtain the target user terminal, which is the other user terminal that first responds to the confirmation reception request; a confirmation reception reminder is sent to the user terminal; and the occupancy information of the shared vehicle is transferred from the user terminal to the target user terminal to complete the handover request.

[0008] Optionally, after sending the forwarding request to the other user terminal; if no confirmation request from the other user terminal is received, or a confirmation request from the other user terminal is received and the confirmation request is a confirmation non-reception request; a reminder of confirmation non-reception is sent to the user terminal.

[0009] Optionally, after sending a reminder to the user terminal to confirm that it is not received; determine whether the shared vehicle is within the parking spot based on the location information of the shared vehicle; if the shared vehicle is within the parking spot, send a reminder to the user terminal asking whether to return the vehicle; if the shared vehicle is within the parking spot, send a reminder to the user terminal that the vehicle cannot be returned.

[0010] Optionally, the vehicle usage remaining amount is compared with a set threshold; if the vehicle usage remaining amount is less than the set threshold, the location information of the shared vehicle is obtained; based on the location information of the shared vehicle, it is determined whether the shared vehicle is within the range of the parking spot; if the shared vehicle is within the range of the parking spot, a reminder is sent to the user terminal asking whether to return the vehicle; if the shared vehicle is within the range of the parking spot, a reminder is sent to the user terminal that the vehicle cannot be returned.

[0011] Optionally, the order management method further includes sending a locking instruction to the shared vehicle to lock the shared vehicle after receiving the return information of the shared vehicle; calculating the total cost incurred by the shared vehicle based on all the actual usage information of the shared vehicle and the billing rules; and calculating the actual usage information of the user terminal and the other user terminals respectively, and allocating the total cost to the user terminal and the other user terminals in proportion.

[0012] On the other hand, a server for shared vehicles is provided, which includes: an acquisition module, which receives a handover request for a shared vehicle from a user terminal and obtains actual usage information and billing rules of the shared vehicle; a comparison module, which calculates the vehicle usage balance for the next billing based on the actual usage information and billing rules, and compares the vehicle usage balance with a set threshold; if the vehicle usage balance is above the set threshold, the acquisition module is also used to obtain the location information of the shared vehicle, and based on the location information, obtain at least one other user terminal around the location information; a control module, which sends the handover request to the other user terminal and responds to the confirmation request of the other user terminal; if the confirmation request is a confirmation receipt request, the control module sends a confirmation receipt reminder to the user terminal, and transfers the occupancy information of the shared vehicle from the user terminal to the other user terminal to complete the handover request.

[0013] On the other hand, a storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned shared vehicle order management method are executed.

[0014] On the other hand, a server for shared vehicles is provided, which includes a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and is characterized in that the processor executes the steps of the above-mentioned shared vehicle order management method when running the computer program. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 This is an information interaction diagram of shared travel in a specific embodiment of the present invention;

[0016] Figure 2 This is a flow chart of order management for shared vehicles in a specific embodiment of the present invention;

[0017] Figure 3 This is a module diagram for order management of shared vehicles in a specific embodiment of the present invention. DETAILED DESCRIPTION

[0018] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, specific embodiments of the present invention are described in detail below with reference to the accompanying drawings.

[0019] Shared mobility currently falls into the following categories: car-sharing (e.g., Caocao Travel, Shouqi Car-hailing), electric bike-sharing (e.g., Meituan Electric Bike, Xiaoliu Sharing), moped-sharing, and bicycle-sharing (e.g., Hello Moped, Qingju Bicycle). Whether car-sharing, electric bike-sharing, moped-sharing, or bicycle-sharing, the operating principles are similar; the only differences are the applicable distances and the user experience.

[0020] The operating principle of shared travel is generally as follows: a shared vehicle service provider provides shared vehicles and builds an operating platform (i.e., a server), and the shared vehicles are interconnected with the server. Generally, shared vehicles are locked. When a user needs to use a shared vehicle, he or she uses a smart terminal to interact with the shared vehicle's information (such as scanning a code to unlock it) and requests the server to unlock the shared vehicle. After the shared vehicle is unlocked, the user can use the shared vehicle, and the server starts charging. Until the user has finished using the shared vehicle, and interacts with the shared vehicle's information through the smart terminal, requests the server to lock the shared vehicle, and the server stops charging, the order is terminated after the user completes the payment.

[0021] Currently, the server charges for shared vehicles in the following ways: 1) Based on the driving time of the shared vehicle, taking the shared electric motorcycle as an example: for every 10 minutes of use of the shared electric motorcycle, it is charged 2 yuan, and less than 10 minutes is counted as 10 minutes. For example, if user A uses the shared electric motorcycle for 12 minutes, it is charged 4 yuan; user B uses the shared electric motorcycle for 19 minutes, and is also charged 4 yuan. 2) Based on the distance traveled by the user on the shared vehicle, also taking the shared electric motorcycle as an example: for every 4 kilometers of travel of the shared electric motorcycle, it is charged 3 yuan, and less than 4 kilometers is counted as 4 kilometers. For example, if user A uses the shared electric motorcycle to travel 5 kilometers, it is charged 6 yuan; user B uses the shared electric motorcycle to travel 7 kilometers, and is also charged 6 yuan.

[0022] Therefore, for the user who is charged for 20 minutes even though he / she only rides for 12 minutes, the experience will be poor. Similarly, for the user who is charged for 8 kilometers even though he / she only rides for 5 kilometers, the experience will also be poor. Moreover, in the field of shared travel, the same number of shared vehicles will serve multiple different users at different times, but there is no communication between multiple different users, which is also not conducive to the maintenance and growth of the user group of shared vehicles. Therefore, it is urgent to adopt relevant technical means to solve the above problems, improve user experience, and maintain the user group of shared vehicles.

[0023] In order to clearly illustrate the technical solution of the present invention, the following mainly uses shared electric motorcycles as an example for explanation. Shared cars, shared power-assisted bicycles and shared bicycles are also applicable to the technical solution of the present invention and will not be described in detail.

[0024] Reference Figure 1, the server 100 is in communication with the shared vehicle 200, and the user terminal A 300 (e.g., a mobile phone, tablet, etc.) is in communication with the server 100 and the shared vehicle 200. The user terminal A 300 unlocks the shared vehicle 200 through the server 100 and is in the process of occupying and using the shared vehicle 200. At this time, the owner of the user terminal A 300, user A, is about to reach the destination by driving the shared vehicle 200.

[0025] Reference Figure 2 The present invention provides a method for managing an order for a shared vehicle, which is applied to a server. The method for managing an order for a shared vehicle comprises the following steps:

[0026] S11, receiving a shared vehicle transfer request from a user terminal.

[0027] When user A is about to reach the destination by driving the shared vehicle 200 , user A may initiate a transfer request of the shared vehicle 200 to the server 100 through the user A terminal 300 .

[0028] For example, if user A feels they've only ridden for 12 minutes and still have 8 minutes left at the same cost, they might want to transfer the shared vehicle. After the transfer, another person (user B) can share some of the cost, reducing user A's costs. User B, who already needs to pay for the ride, can share user A's remaining time by taking over user A's shared vehicle, thereby reducing user B's costs. This improves the experience for both users A and B.

[0029] S12, obtaining actual usage information and billing rules of the shared vehicle.

[0030] After the server 100 receives the transfer request of the shared vehicle 200 from the A user terminal 300 , the server 100 also obtains actual usage information and charging rules of the shared vehicle 200 .

[0031] The billing rules are pre-set. As previously mentioned, they can be based on the time a user uses a shared vehicle. For example, a 10-minute usage rate for a shared vehicle is 2 yuan, and any usage less than 10 minutes is rounded up. Alternatively, a 4-kilometer usage rate for a shared motorcycle is 3 yuan, and any usage less than 4 kilometers is rounded up. The billing rules can be stored in server 100 and directly accessed by server 100. Alternatively, the billing rules can be stored in another memory and accessed by server 100.

[0032] Actual usage information refers to the shared vehicle's driving information, generally determined by the charging rules. This information can be either driving time or driving distance. If the charging rules base the charge on the time a user drives the shared vehicle, the actual usage information is the driving time. If the charging rules base the charge on the distance a user drives the shared vehicle, the actual usage information is the distance traveled.

[0033] S21, calculating the vehicle usage surplus for the next billing based on the actual usage information and billing rules.

[0034] For example, if the billing rule is to charge users based on the time they use a shared vehicle, and the shared vehicle is charged 2 yuan for every 10 minutes of use, and any time less than 10 minutes is rounded up to 10 minutes, the server 100 obtains the travel time of the shared vehicle 200, for example, 12 minutes or 19 minutes. If the travel time is 12 minutes, the remaining time for the next charge is 8 minutes (10 + 10 - 12); if the travel time is 19 minutes, the remaining time for the next charge is 1 minute (10 + 10 - 19).

[0035] For example, if the charging rule is to charge users based on the distance they travel, and the shared motorcycle is charged 3 yuan for every 4 kilometers, and any distance less than 4 kilometers is counted as 4 kilometers, the server 100 obtains the travel distance of the shared vehicle 200, for example, 5 kilometers or 7 kilometers. Then, if the travel distance is 5 kilometers, the remaining vehicle usage for the next charge is 3 kilometers (4 + 4 - 5); if the travel distance is 7 kilometers, the remaining vehicle usage for the next charge is 1 kilometer (4 + 4 - 7).

[0036] S22, comparing the vehicle usage remaining capacity with a set threshold.

[0037] The threshold is pre-set based on the billing rules. As previously mentioned, for example, if a shared vehicle's driving time is charged 2 yuan for every 10 minutes of use, and any time less than 10 minutes is rounded up to 10 minutes, the threshold could be 2 minutes. For example, if a shared electric motorcycle's driving distance is charged 3 yuan for every 4 kilometers of use, and any time less than 4 kilometers is rounded up to 4 kilometers, the threshold could be 1 kilometer.

[0038] The above threshold values ​​are merely examples and may be set as fixed values ​​or variable values.

[0039] S23: If the remaining usage of the vehicle is above the set threshold, the location information of the shared vehicle is obtained.

[0040] S24: Acquire at least one other user terminal around the location information based on the location information.

[0041] Taking the travel time of a shared vehicle as an example, when the user travels for 12 minutes, the vehicle usage remaining time is 8 minutes, and the threshold is set to 2 minutes. The server 100 determines that the vehicle usage remaining time is above the set threshold, and needs to obtain the location information of the shared vehicle 200, and obtain at least one other user terminal (such as Figure 1 In the example above, the user terminal B is user terminal 400. When the user's driving time is 19 minutes, the vehicle usage remaining time is 1 minute, and the set threshold is 2 minutes, the server 100 determines that the vehicle usage remaining time is not above the set threshold. In this case, the server 100 does not need to obtain the location information of the shared vehicle 200 or the location information of at least one other user terminal in the surrounding area.

[0042] Taking the travel distance of a shared vehicle as an example, when the user travels 5 kilometers, the vehicle usage margin is 3 kilometers, and the threshold is set to 1 kilometer, the server 100 determines that the vehicle usage margin is above the set threshold, and needs to obtain the location information of the shared vehicle 200, and obtain at least one other user terminal (such as Figure 1 In the example above, the user terminal B is user terminal 400. When the user's travel distance is 7.1 kilometers, the vehicle's remaining capacity is 0.9 kilometers, and the threshold is set to 1 kilometer, the server 100 determines that the vehicle's remaining capacity is not above the threshold. In this case, the server 100 does not need to obtain the location information of the shared vehicle 200 or the location information of at least one other user terminal in the surrounding area.

[0043] S31: Send a transfer request to another user terminal.

[0044] If the server 100 obtains the location information of another user terminal (such as user terminal B 400), the server 100 sends a forwarding request to the user terminal. If the server 100 obtains the location information of multiple other user terminals, the server 100 sends a forwarding request to the multiple other user terminals. If the server 100 does not obtain the location information of other user terminals, the server 100 does not send a forwarding request and feeds back to user terminal A 300 information that no other terminal was found.

[0045] It should be noted that the area around the location information of the shared vehicle 200 may be defined as the space within a certain radius centered on the shared vehicle 200. For example, the area around the location information of the shared vehicle 200 may be the space within a 20-meter radius centered on the shared vehicle 200.

[0046] In this embodiment, when the server 100 fails to obtain the location information of other user terminals around, in addition to feeding back information to the user terminal A 300, the server 100 also determines whether the shared vehicle 200 is within the range of the parking spot based on the location information of the shared vehicle 200. The parking spot is pre-set and the server 100 can directly obtain and determine it. If the server 100 determines that the shared vehicle 200 is within the range of the parking spot, it sends a reminder to the user terminal A 300 asking whether to return the vehicle, and executes the action of returning the vehicle according to the instruction of the user terminal A 300. If the server 100 determines that the shared vehicle 200 is outside the range of the parking spot, it sends a reminder to the user terminal A 300 that the vehicle cannot be returned, and guides the user terminal A 300 to move to a nearby parking spot to complete the sending of the return or transfer request.

[0047] The above are the steps when the vehicle usage remaining amount is above the set threshold. When the vehicle usage remaining amount is not above the set threshold, the server 100 of this embodiment will also obtain the location information of the shared vehicle 200 and determine whether the shared vehicle 200 is within the parking spot based on the location information of the shared vehicle 200. If the server 100 determines that the shared vehicle 200 is within the parking spot, it will send a reminder to the user terminal A 300 to ask whether to return the vehicle, and execute the action of whether to return the vehicle according to the instruction of the user terminal A 300. If the server 100 determines that the shared vehicle 200 is outside the parking spot, it will send a reminder to the user terminal A 300 that the vehicle cannot be returned, and guide the user terminal A 300 to move to a nearby parking spot to complete the sending of the return or transfer request.

[0048] S32, responding to confirmation requests from other user terminals.

[0049] S33: If the confirmation request is a reception confirmation request, a reminder for reception confirmation is sent to the user terminal.

[0050] When the server 100 obtains location information of multiple B-user terminals 400 around the server 100 and sends a transfer request to the multiple B-user terminals 400, the B-user terminals 400 will provide feedback according to the transfer request. At this time, the server 100 may receive multiple confirmation reception requests.

[0051] Since user terminal A occupies only one shared vehicle 200 and can only transfer one shared vehicle 200, the server 100 needs to sort multiple confirmation reception requests, for example, sort them in chronological order, and take user terminal B 400 that receives the confirmation reception request first as the target user terminal, send a confirmation reception reminder to user terminal A 300, and send reminders to other non-target user terminals B user terminals 400 that the shared vehicle 200 has been received by other users.

[0052] If all B user terminals 400 feedback confirmation of not receiving the request, that is, the server 100 receives a confirmation of not receiving the request, the server 100 sends a reminder of not receiving the confirmation to the A user terminal.

[0053] Alternatively, there's a scenario where some B-user terminals 400 respond with a confirmation that they didn't receive the request, while others don't. If the server 100 sends a forwarding request to a B-user terminal 400 but doesn't receive a confirmation request from it, the system internally sets a time limit (e.g., 2 minutes) for receiving the feedback signal. If the server 100 doesn't receive a confirmation request from a B-user terminal 400 within the time limit, it defaults to a confirmation that they didn't receive the request. In this case, since some B-user terminals 400 respond with a confirmation that they didn't receive the request, others are defaulted to a confirmation that they didn't receive the request. The server 100 then sends a reminder to the A-user terminal 300 confirming that they didn't receive the request.

[0054] After the server 100 sends a notification to user A's terminal 300 confirming that it has not received the notification, the server 100 also obtains the location information of the shared vehicle 200 and determines whether the shared vehicle 200 is within the parking area based on the location information. If the server 100 determines that the shared vehicle 200 is within the parking area, it sends a notification to user A's terminal 300 asking whether to return the vehicle. The server 100 then executes the vehicle return action based on the instructions of user A's terminal 300. If the server 100 determines that the shared vehicle 200 is outside the parking area, it sends a notification to user A's terminal 300 indicating that the vehicle cannot be returned and directs user A's terminal 300 to move to a nearby parking area to complete the vehicle return or transfer request.

[0055] S34: Transferring the occupancy information of the shared vehicle from the user terminal to other user terminals to complete the handover request.

[0056] After the server 100 receives the confirmation request from user B's terminal 400 and sends a confirmation notification to user A's terminal 300, the server 100 transfers the occupancy information of the shared vehicle 200 from user A's terminal 300 to user B's terminal 400. In other words, the occupancy of the shared vehicle 200 by user A's terminal 300 is transferred to the occupancy of the shared vehicle 200 by user B's terminal 300, completing the handover request for the shared vehicle 200. At this point, user A's terminal 300 releases the shared vehicle 200, and user B's terminal 300 takes over the shared vehicle 200.

[0057] Similarly, when user B uses the shared vehicle 200 to approach the destination, user B can also initiate a transfer request for the shared vehicle 200 through the user B terminal to transfer the shared vehicle 200 to the user C terminal. The principle is similar to that of user A transferring the shared vehicle 200 to user B's terminal, and will not be repeated here.

[0058] Eventually, shared vehicle 200 will be returned. After receiving the return request from shared vehicle 200, server 100 sends a lock command to shared vehicle 200 to lock it. Server 100 also calculates the total cost of shared vehicle 200 based on all actual usage information and billing rules.

[0059] Taking the driving time of a shared vehicle as an example, user terminal A 300 occupies the driving time of shared vehicle 200 for 12 minutes, and user terminal B 400 occupies the driving time of shared vehicle 200 for 7 minutes. The total driving time occupied by shared vehicle 200 is 19 minutes, and the total cost incurred is 4 yuan.

[0060] Taking the driving distance of a shared vehicle as an example, user terminal A 300 occupies the shared vehicle 200 for a driving distance of 5 kilometers, and user terminal B 400 occupies the shared vehicle 200 for a driving distance of 2 kilometers. The total driving distance occupied by the shared vehicle 200 is 7 kilometers, and the total cost incurred is 6 yuan.

[0061] In this embodiment, the server 100 further allocates the total fee to the user terminal and other user terminals in proportion according to the actual usage information of the user terminal and other user terminals.

[0062] Taking the shared vehicle travel time as an example, user A's terminal 300 travels for 12 minutes, while user B's terminal 400 travels for 7 minutes, for a total cost of 4 yuan. Therefore, the cost incurred by user A is 12 / 19 × 4 = 2.5 yuan, and the cost incurred by user B is 1.5 yuan. In this case, user A saves 1.5 yuan and user B saves 0.5 yuan, significantly improving user satisfaction. Furthermore, the information exchange between users A and B also helps maintain and grow the shared vehicle user base.

[0063] Taking the aforementioned shared vehicle's travel distance as an example, user A's terminal 300 travels 5 kilometers, while user B's terminal 400 travels 2 kilometers, for a total cost of 6 yuan. Therefore, the cost incurred by user A is 5 / 7 × 6 = 4.3 yuan, and the cost incurred by user B is 1.7 yuan. In this case, user A saves 1.7 yuan and user B saves 1.3 yuan, significantly improving user satisfaction. Furthermore, information exchange between users A and B also helps maintain and grow the shared vehicle user base.

[0064] This embodiment also provides a shared vehicle server, referring to Figure 3 The server 100 includes an acquisition module 10, which is used to receive a transfer request of a shared vehicle 200 from a user terminal A 300 and obtain actual usage information and charging rules of the shared vehicle 200.

[0065] The server 100 also includes a comparison module 20, which is used to calculate the vehicle usage balance for the next billing based on actual usage information and billing rules, and compare the vehicle usage balance with a set threshold; if the vehicle usage balance is above the set threshold, the acquisition module 20 is also used to obtain the location information of the shared vehicle 200, and based on the location information, obtain at least one other user terminal around the location information.

[0066] The server 100 also includes a control module 30, which is used to send a handover request to the B user terminal 400 and respond to the confirmation request of the B user terminal 400; if the confirmation request is a confirmation reception request, the control module 30 is also used to send a confirmation reception reminder to the A user terminal 300, and transfer the occupancy information of the shared vehicle 200 from the A user terminal 300 to the B user terminal 400 to complete the handover request.

[0067] This embodiment also provides a storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned shared vehicle order management method are executed.

[0068] This embodiment also provides a server for shared vehicles, which includes a memory and a processor. The memory stores a computer program that can be run on the processor. When the processor runs the computer program, the steps of the above-mentioned shared vehicle order management method are executed.

[0069] Although the present invention is disclosed as above, the present invention is not limited thereto. Any person skilled in the art can make various changes and modifications without departing from the spirit and scope of the present invention. Therefore, the scope of protection of the present invention should be based on the scope defined by the claims.

Claims

1. A method for managing shared vehicle orders, applied to a server, characterized in that: include: receiving a shared vehicle transfer request from a user terminal; Obtaining actual usage information and billing rules of the shared vehicle; Calculating the vehicle usage surplus for the next billing based on the actual usage information and billing rules; comparing the vehicle usage margin with a set threshold; If the remaining usage of the vehicle is above a set threshold, obtaining the location information of the shared vehicle; Acquire, based on the location information, at least one other user terminal around the location information; Sending the transfer request to the other user terminal; Responding to the confirmation request of the other user terminal; If the confirmation request is a receipt confirmation request, sending a receipt confirmation reminder to the user terminal; and transferring the occupancy information of the shared vehicle from the user terminal to the other user terminal to complete the transfer request; After receiving the return information of the shared vehicle, sending a locking instruction to the shared vehicle to lock the shared vehicle; Calculating the total cost of the shared vehicle based on all the actual usage information of the shared vehicle and the charging rules; The actual usage information of the user terminal and the other user terminals is calculated respectively, and the total fee is allocated to the user terminal and the other user terminals in proportion.

2. The order management method according to claim 1, wherein: The actual usage information is the actual driving time, and the charging rule is a rule for charging according to the driving time; or, the actual usage information is the actual driving distance, and the charging rule is a rule for charging according to the driving distance.

3. The order management method according to claim 1, wherein: the responding to the confirmation request of the other user terminal, if the confirmation request is a plurality of confirmation reception requests; Then, the plurality of confirmation reception requests are sorted to obtain a target user terminal, where the target user terminal is the other user terminal that first responds to the confirmation reception request; Sending a reminder to the user terminal to confirm receipt; The occupancy information of the shared vehicle is transferred from the user terminal to the target user terminal to complete the transfer request.

4. The order management method according to claim 1, wherein: After sending the transfer request to the other user terminal; If no confirmation request from the other user terminal is received, or if a confirmation request from the other user terminal is received and the confirmation request is a confirmation non-reception request; Then, a reminder is sent to the user terminal to confirm that the notification is not received.

5. The order management method according to claim 4, wherein: After sending a reminder to the user terminal to confirm not to receive the reminder; Determining whether the shared vehicle is within the parking spot range according to the location information of the shared vehicle; If the shared vehicle is within the parking spot, a reminder is sent to the user terminal asking whether to return the vehicle; If the shared vehicle is within the parking spot, a reminder that the vehicle cannot be returned is sent to the user terminal.

6. The order management method according to claim 1, wherein: The comparing the vehicle usage remaining amount with a set threshold; if the vehicle usage remaining amount is less than the set threshold, obtaining the location information of the shared vehicle; Determining whether the shared vehicle is within the parking spot range according to the location information of the shared vehicle; If the shared vehicle is within the parking spot, a reminder is sent to the user terminal asking whether to return the vehicle; If the shared vehicle is within the parking spot, a reminder that the vehicle cannot be returned is sent to the user terminal.

7. A shared vehicle server, characterized in that: include: an acquisition module, the acquisition module receiving a shared vehicle transfer request from a user terminal and acquiring actual usage information and charging rules of the shared vehicle; a comparison module, wherein the comparison module calculates the vehicle usage remaining amount for the next billing based on the actual usage information and the billing rules, and compares the vehicle usage remaining amount with a set threshold; If the vehicle usage remaining capacity is above a set threshold, the acquisition module is further configured to acquire location information of the shared vehicle and, based on the location information, acquire at least one other user terminal around the location information; a control module, wherein the control module sends the transfer request to the other user terminal and responds to the confirmation request of the other user terminal; If the confirmation request is a confirmation receipt request, the control module sends a confirmation receipt reminder to the user terminal, and transfers the occupancy information of the shared vehicle from the user terminal to the other user terminal to complete the transfer request; After the acquisition module receives the return information of the shared vehicle, the control module sends a locking instruction to the shared vehicle to lock the shared vehicle; a calculation module, configured to calculate a total fee incurred by the shared vehicle based on all the actual usage information of the shared vehicle and the charging rules; The calculation module further calculates the actual usage information of the user terminal and the other user terminals respectively, and allocates the total fee to the user terminal and the other user terminals in proportion.

8. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the shared vehicle order management method according to any one of claims 1 to 6 are executed.

9. A shared vehicle server, comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, characterized in that: When the processor runs the computer program, the processor performs the steps of the shared vehicle order management method according to any one of claims 1 to 6.

Images