Bill processing method and device and computer program product

Abstract

The embodiment of the invention discloses a bill processing method and device and a computer program product, which are applied to a carpooling trip scene, and the main technical scheme comprises the following steps: in response to an operation of triggering the display of cost information, displaying a bill on a page, the bill at least comprising the shared cost information of passenger users participating in the sharing of the pass cost of a payment road; wherein the shared fee information is determined according to the independent mileage of the passenger user participating in the passage fee allocation on the payment road and / or the shared mileage of the passenger user and other users participating in the passage fee allocation. According to the method and the device, the problem that the carpooling travel service relates to the passing cost of the paid road is solved in a reasonable mode, and the experience of the user in the carpooling travel service is improved. In addition, disputes between the driver users and the passenger users are reduced through the mode, the customer service cost for solving the disputes is further reduced, and therefore the service cost of the carpooling travel service is reduced.

Description

Technical Field

[0001] This application relates to the technical field of shared travel, and particularly to a method, device, and computer program product for bill processing. Background Art

[0002] With the rapid development and wide application of mobile Internet technology, platforms providing shared travel services have emerged. As one type of shared travel service, carpooling travel has also developed rapidly. Carpooling travel refers to a travel mode in which two or more travelers jointly complete a journey by sharing the same vehicle, such as hitchhiking services, carpooling services, etc. The carpooling travel service platform can efficiently match the supply and demand information of carpooling travel, making it easier for driver users and passenger users to find each other. On the one hand, it reduces the travel costs of driver users and passenger users, and on the other hand, it also reduces traffic congestion pressure, resource consumption, and exhaust emissions.

[0003] However, for the problem of toll road tolls in carpooling travel services, there is currently no reasonable method to solve this problem. Summary of the Invention

[0004] This application provides a method, device, and computer program product for bill processing to reasonably solve the problem of toll road tolls involved in carpooling travel services and improve the user experience in carpooling travel services.

[0005] This application provides the following solutions:

[0006] According to a first aspect, a bill processing method is provided, which is applied to the client corresponding to the driver user in the carpooling travel scenario. The method includes: in response to an operation of triggering the display of fee information, displaying a bill on the page, where the bill at least includes the sharing fee information of the passenger users participating in the sharing of the toll road tolls; wherein, the sharing fee information is determined based on the solo mileage of the passenger users participating in the sharing of the tolls on the toll road and / or the shared mileage with other users participating in the sharing of the tolls.

[0007] According to a second aspect, a bill processing method is provided, which is applied to the client corresponding to the passenger user in the carpooling travel scenario. The method includes: receiving the information of the bill; in response to an operation of triggering the fee prompt information, displaying the bill on the page, where the bill at least includes the sharing fee information of the passenger user; wherein, the sharing fee information is determined based on the solo mileage of the passenger users participating in the sharing of the tolls on the toll road and / or the shared mileage with other users participating in the sharing of the tolls.

[0008] According to a third aspect, a bill processing method is provided, which is applied to the server side in the carpooling travel scenario. The method includes: determining the sharing cost information of the passenger user according to the solo mileage of the passenger user on the toll road and / or the carpooling mileage with other users participating in the sharing of the toll; sending the bill information to the client corresponding to the driver user and / or the client corresponding to the passenger user, where the bill at least includes the sharing cost information.

[0009] According to a fourth aspect, a bill processing device is provided, which is set in the client corresponding to the driver user in the carpooling travel scenario. The device includes: a first operation acquisition unit configured to acquire an operation for triggering the display of cost information; a first page display unit configured to, in response to the operation for triggering the display of cost information, display a bill on the page, where the bill at least includes the sharing cost information of the passenger user participating in the sharing of the toll on the toll road; wherein, the sharing cost information is determined according to the solo mileage of the passenger user participating in the sharing of the toll on the toll road and / or the carpooling mileage with other users participating in the sharing of the toll.

[0010] According to a fifth aspect, a bill processing device is provided, which is set in the client corresponding to the passenger user in the carpooling travel scenario. The device includes: a second receiving unit configured to receive the bill information; a second operation acquisition unit configured to acquire an operation for triggering the cost prompt information; a second page display unit configured to, in response to the operation for triggering the cost prompt information, display the bill on the page, where the bill at least includes the sharing cost information of the passenger user; wherein, the sharing cost information is determined according to the solo mileage of the passenger user participating in the sharing of the toll on the toll road and / or the carpooling mileage with other users participating in the sharing of the toll.

[0011] According to a sixth aspect, a bill processing device is provided, which is set in the server side in the carpooling travel scenario. The device includes: a cost determination unit configured to determine the sharing cost information of the passenger user according to the solo mileage of the passenger user participating in the sharing of the toll on the toll road and / or the carpooling mileage with other users participating in the sharing of the toll; a sending unit configured to send the bill information to the client corresponding to the driver user and / or the client corresponding to the passenger user, where the bill at least includes the sharing cost information.

[0012] According to a seventh aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the program is executed by a processor, the steps of the method described in any one of the first aspect, the second aspect, and the third aspect are implemented.

[0013] According to an eighth aspect, there is provided an electronic device, comprising:

[0014] one or more processors; and

[0015] a memory associated with the one or more processors, the memory being configured to store program instructions, which when read and executed by the one or more processors, perform the steps of the method according to any one of the first, second, and third aspects described above.

[0016] According to a ninth aspect, there is provided a computer program product, comprising a computer program which, when executed by a processor, implements the steps of the method according to any one of the first, second, and third aspects described above.

[0017] According to the specific embodiments provided in the present application, the following technical effects are disclosed in the present application:

[0018] In the scenario of shared ride travel, the method of the present application can determine the sharing cost information of the passenger users participating in the sharing of the toll road based on the solo mileage of the passenger users on the toll road participating in the sharing of the toll and / or the shared mileage of other users participating in the sharing of the toll, and display the sharing cost information in the form of a bill, so as to facilitate the driver user and the passenger user to clearly understand the sharing cost information of the passenger user, and reasonably solve the problem of the toll road toll involved in the shared ride travel service, and improve the experience of the user in the shared ride travel service. In addition, this method also reduces the disputes between the driver user and the passenger user, thereby reducing the customer service cost for resolving disputes, and thus reducing the service cost of the shared ride travel service. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application, and those of ordinary skill in the art can obtain other drawings based on these drawings without creative efforts.

[0020] Figure 1 is a system architecture diagram applicable to the embodiments of the present application;

[0021] Figure 2 is a flowchart of the bill processing method executed by the server side provided in the embodiments of the present application;

[0022] Figure 3 is a schematic diagram of a bill page displayed on the client corresponding to the driver user provided in the embodiments of the present application;

[0023] Figure 4Schematic diagram of the page for triggering and displaying fee information on the client corresponding to the driver user provided by the embodiments of the present application;

[0024] Figure 5 Schematic diagram of another bill page displayed on the client corresponding to the driver user provided by the embodiments of the present application;

[0025] Figure 6a Schematic diagram of a page after the end of the trip displayed on the client corresponding to the driver user provided by the embodiments of the present application;

[0026] Figure 6b Schematic diagram of the page for displaying the bill after the end of the trip displayed on the client corresponding to the driver user provided by the embodiments of the present application;

[0027] Figure 7 Schematic diagram of the page for initiating the collection of toll fees displayed on the client corresponding to the driver user provided by the embodiments of the present application;

[0028] Figure 8a Schematic diagram of the first modification interface displayed on the client corresponding to the driver user provided by the embodiments of the present application;

[0029] Figure 8b Schematic diagram of the second modification interface displayed on the client corresponding to the driver user provided by the embodiments of the present application;

[0030] Figure 8c Schematic diagram of the interface for uploading vouchers displayed on the client corresponding to the driver user provided by the embodiments of the present application;

[0031] Figure 8d Schematic diagram of the interface for modifying the toll fee amount displayed on the client corresponding to the driver user provided by the embodiments of the present application;

[0032] Figure 9 Flowchart of the bill processing method executed on the client corresponding to the passenger user provided by the embodiments of the present application;

[0033] Figure 10a Schematic diagram of the fee prompt information displayed on the client corresponding to the passenger user provided by the embodiments of the present application;

[0034] Figure 10b Schematic diagram of a bill page displayed on the client corresponding to the passenger user provided by the embodiments of the present application;

[0035] Figure 11a Schematic diagram of another bill page displayed on the client corresponding to the passenger user provided by the embodiments of the present application;

[0036] Figure 11bSchematic diagram of the payment completion page displayed on the client corresponding to the passenger user provided by the embodiment of the present application;

[0037] Figure 12 Schematic diagram of the passenger user corresponding to the client of the embodiment of the present application initiating a bill objection;

[0038] Figure 13a Schematic diagram of a page before generating an order displayed on the client corresponding to the passenger user provided by the embodiment of the present application;

[0039] Figure 13b Schematic diagram of the toll sharing option displayed on the client corresponding to the passenger user provided by the embodiment of the present application;

[0040] Figure 14 Schematic block diagram of the bill processing device provided in the client corresponding to the driver user according to the embodiment of the present application;

[0041] Figure 15 Schematic block diagram of the bill processing device provided in the client corresponding to the passenger user according to the embodiment of the present application;

[0042] Figure 16 Schematic block diagram of the bill processing device provided on the server side according to the embodiment of the present application;

[0043] Figure 17 Schematic block diagram of the electronic device provided by the embodiment of the present application. Detailed implementation manners

[0044] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0045] The terms used in the embodiments of the present invention are only for the purpose of describing specific embodiments, and are not intended to limit the present invention. The singular forms of "a", "the" and "said" used in the embodiments of the present invention and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise.

[0046] It should be understood that the term " / and" used herein is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " herein generally represents an "or" relationship between the associated objects before and after.

[0047] Depending on the context, as used herein, the word "if" can be interpreted as "when" or "while" or "in response to determining" or "in response to detecting". Similarly, depending on the context, the phrase "if determined" or "if detecting (stated condition or event)" can be interpreted as "when determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)".

[0048] Currently, there are already some billing processing technologies, which generally rely on the autonomous negotiation between driver users and passenger users for sharing the costs of toll roads. However, such a method relies on the manual negotiation and operation between driver users and passenger users, and contradictions may be caused during the process, reducing the experience of the carpooling service.

[0049] In view of this, the present application provides a new idea. For the convenience of understanding the present application, the system architecture on which the present application is based will be described first. Figure 1 An exemplary system architecture to which embodiments of the present application can be applied is shown, as Figure 1 shown in, the system architecture may include: a client corresponding to a driver user in a carpooling scenario, a client corresponding to a passenger user in a carpooling scenario, and a server side in a carpooling scenario.

[0050] The server side and the client are two main parts of the application service. Among them, the server side uses the server as the main hardware infrastructure and may include one or more service modules in software form. In the embodiments of the present application, it is mainly responsible for processing the carpooling service logic and forming a front-end and back-end that work together with the client.

[0051] The user terminal where the client is located may include, but is not limited to, such as: intelligent mobile terminals, wearable devices, PCs (Personal Computers), etc. Among them, intelligent mobile devices may include, such as mobile phones, tablet computers, PDAs (Personal Digital Assistants), Internet car terminals, etc. Wearable devices may include, such as smart watches, smart glasses, smart bracelets, VR (Virtual Reality) devices, AR (Augmented Reality devices), mixed reality devices (i.e., devices that can support virtual reality and augmented reality), and so on.

[0052] The client corresponding to the driver user and the client corresponding to the passenger user may be an application located on the user terminal, or may also be functional units such as plugins or software development kits (SDKs) set in the application.

[0053] The server can be an independent server, a server group, or a cloud server. A cloud server, also known as a cloud computing server or a cloud host, is a host product in the cloud computing service system, which is used to solve the problems of high management difficulty and weak service scalability existing in traditional physical hosts and virtual private servers (VPS, Virtual Private Server) services.

[0054] It should be understood that Figure 1 the server side and the client side in are merely illustrative. According to the implementation requirements, there can be any number of server sides and client sides.

[0055] Next, the bill processing methods applied to the client corresponding to the driver user, the client corresponding to the passenger user, and the server side in this application will be introduced one by one. It should be noted that the "first", "second", etc. limitations involved in this disclosure do not have limitations in terms of size, order, quantity, etc., and are only used to distinguish in name. For example, "the first component" and "the second component" are used to distinguish two components, and for another example, "the first modification interface" and "the second modification interface" are used to distinguish two modification interfaces.

[0056] Figure 2 is the flowchart of the bill processing method provided by the embodiment of this application. This method can be executed by Figure 1 the server side in the carpooling travel scenario in the system shown in Figure 2 As shown in , this method can include the following steps:

[0057] Step 201: Determine the sharing cost information of the passenger user according to the solo mileage of the passenger user participating in the sharing of the toll on the toll road and / or the shared mileage with other users participating in the sharing of the toll.

[0058] Step 202: Send the bill information to the client corresponding to the driver user and / or the client corresponding to the passenger user. The bill includes at least the sharing cost information.

[0059] As can be seen from the above process, in the carpooling travel scenario, the method of the present application can determine the sharing cost information of the passenger users participating in the sharing of the toll road based on the single-rider mileage of the passenger users on the toll road who participate in the sharing of the toll and / or the carpooling mileage of other users participating in the sharing of the toll, and display the sharing cost information in the form of a bill, so as to facilitate the driver users and passenger users to clearly understand the sharing cost information of the passenger users, and reasonably solve the problem of the toll for the toll road involved in the carpooling travel service, and improve the experience of users in the carpooling travel service. In addition, this method also reduces the disputes between driver users and passenger users, thereby reducing the customer service costs for resolving disputes, and thus reducing the service costs of the carpooling travel service.

[0060] The carpooling travel scenarios involved in the embodiments of the present application may include, but are not limited to, the hitchhiking scenario and the carpooling scenario. The toll roads may include, but are not limited to, highways, independent bridges or tunnels that require payment.

[0061] In the embodiments of the present application, when the server determines the sharing cost information of the passenger users, it is based on the toll actually paid by the driver user for the toll road. During the trip of the carpooling travel service, it may pass through one toll road or multiple toll roads. For each toll road passed, the driver user needs to pay the toll for the toll road. The ways for the driver user to pay the toll for the toll road may include payment by payment code, scanning code payment, ETC payment, cash payment, etc. When the driver user completes the payment of the toll for each toll road or the driver user completes the payment of the tolls for all toll roads, the payment system will send a message to the server of the carpooling travel service indicating that the driver user has paid the toll for the toll road. At the same time, it also supports the driver user to manually add / modify the toll, such as in the case of cash payment.

[0062] In response to receiving the message that the driver user has paid the toll for the toll road, the server determines the sharing cost information of the passenger users based on the single-rider mileage of the passenger users on the toll road who participate in the sharing of the toll and / or the carpooling mileage of other users participating in the sharing of the toll, and sends the bill information to the client corresponding to the driver user and / or the client corresponding to the passenger user.

[0063] Moreover, in the subsequent process, each time the server receives the message that the driver user has paid the toll for the toll road, it can determine the sharing cost information of the passenger users on this toll road, generate a new bill, and send the information of the new bill to the client corresponding to the driver user and / or the client corresponding to the passenger user.

[0064] As one of the achievable ways, the server side can receive the option information selected by the passenger user from the toll sharing options, and this option information is usually included in the carpool service order of the passenger user. Among them, the option information can include one of not sharing the toll, bearing all the tolls, and sharing the tolls. According to the option information, determine the passenger users who participate in the toll sharing of the toll road, that is, use the passenger users corresponding to the option information of sharing the toll as the passenger users who participate in the toll sharing of the toll road. How the passenger user selects the option information from the toll sharing options will be described in detail in the subsequent embodiments.

[0065] In addition to determining the passenger users who participate in the toll sharing of the toll road based on the option information of the passenger user as described above, other methods can also be adopted. For example, by default, all passenger users in the carpool trip are passenger users who participate in the toll sharing of the toll road.

[0066] To help understanding, several possible situations are listed here:

[0067] The first situation: In the whole journey of a carpool service, all passenger users do not share the toll, then the process of the embodiment of the present application is not executed, but the driver user bears all the tolls of the toll road.

[0068] The second situation: In the whole journey of a carpool service, only one passenger user shares the toll. Then, on the toll road where this passenger user participates, the users who participate in the toll sharing are the driver user and this passenger user; on other toll roads, only the driver user bears the toll of this section of the toll road.

[0069] The third situation: In the whole journey of a carpool service, there are multiple passenger users sharing the toll. Then, if there are at least two of these multiple passenger users on a toll road, the users who participate in the toll sharing on this toll road are these at least two passenger users; if there is only one of these multiple passenger users on a toll road, the user who participates in the toll sharing on this toll road is this one passenger user.

[0070] The fourth situation: In the whole journey of a carpool service, there is one passenger user who chooses to bear all the tolls. Then, on the toll road where this passenger user participates, this passenger user bears the toll of this toll road, and on other toll roads, the users who participate in the toll sharing are the driver users.

[0071] Fifth scenario: During the entire trip of a carpooling service, if there are multiple passenger users sharing the toll expenses, then if there are at least two of the multiple passenger users on a toll road, the users participating in the toll expense sharing on this toll road are the at least two passenger users and the driver user; if there is only one of the multiple passenger users on a toll road, the users participating in the toll expense sharing on this toll road are the one passenger user and the driver user.

[0072] In the embodiments of this application, for each toll road, the server determines the sharing expense information of the passenger users on this toll road based on the solo mileage of the passenger users participating in the toll expense sharing on the toll road and / or the shared mileage with other users participating in the toll expense sharing.

[0073] As one possible implementation, taking the passenger user U1 participating in the toll expense sharing as an example, its sharing expense C a on the toll road L a,U1 can be:

[0074]

[0075] Where K U1 is the solo mileage of the passenger user U1 on this toll road L a . Q U1 is the shared mileage of the passenger user U1 on this toll road L a with other users participating in the toll expense sharing on this toll road L a . is the unit price of this toll road L a , for example, the toll per kilometer, which can be obtained from the toll standard of the toll road. This toll standard can be obtained by calling a specific database, configuration file or the interface of other systems. is the number of shared users participating in the toll expense sharing on this toll road L a .

[0076] It should be noted that the shared mileage of the above-mentioned passenger users participating in the toll expense sharing and other users participating in the toll expense sharing refers to the mileage when both the passenger user and the other user participate in the toll expense sharing and pass through the toll road in the vehicle at the same time. The solo mileage of the above-mentioned passenger users participating in the toll expense sharing on the toll road refers to the mileage passed through on this toll road when there are no other passenger users participating in the toll expense sharing except this passenger user.

[0077] It should be noted that the "mileage" involved in the embodiments of the present application refers to a physical quantity for measuring the driving distance of a vehicle on a toll road, which can be characterized by common units such as kilometers and miles, or other units such as the number of segments of the toll road. For example, a highway is divided into multiple segments, and the driving distance of the vehicle on the highway is measured according to the number of segments.

[0078] For a toll road, there may be a situation where only one passenger user participating in the sharing of the toll travels alone, or there may be a situation where multiple passenger users participating in the sharing of the toll travel together. There may also be a situation where part of the mileage is traveled alone by one passenger user participating in the sharing of the toll, and part of the mileage is traveled together by multiple passenger users participating in the sharing of the toll. For example, passenger user 1 starts an order before getting on the previous highway and travels alone for 10 kilometers on the highway. Then, passenger user 2 gets on the bus at the service area, and passenger user 1 and passenger user 2 start traveling together for 30 kilometers on the highway and then get off the highway. In this case, the solo mileage of passenger user 1 is 10 kilometers, and the co-riding mileage with passenger user 2 is 30 kilometers. The toll paid by the driver user for this toll road is 40 yuan. Then, the sharing fee of passenger user 1 is 25 yuan, and the sharing ratio is 62.5%; the sharing fee of passenger user 2 is 15 yuan, and the sharing ratio is 37.5%.

[0079] If there are multiple toll roads, the above-mentioned sharing fee information can be calculated for each toll road, and then the sharing fee information of multiple toll roads can be displayed in the bill. That is to say, for the entire itinerary of a carpooling service, if it passes through multiple toll roads, the sharing fee information of the passenger users participating in the sharing of the toll on each toll road is calculated respectively using the above formula (1). If there may be different toll standards for multiple toll roads, the C corresponding to different toll roads in the above formula (1) La is different. Then, the sharing fee information corresponding to multiple toll roads is integrated and displayed. The integration and display method can be as Figure 5 shown, and the sharing fee information corresponding to each passenger user is displayed separately according to the passenger users; it can also be as Figure 8a shown, and the sharing fee information corresponding to multiple toll roads is displayed separately according to the toll roads.

[0080] In order to enable the driver user to understand the sharing fee information of each passenger user in the itinerary, the information of the order can be sent to the driver user. The order includes the sharing fee information of each passenger user, and may also include at least one of the solo mileage, co-riding mileage, and fee sharing ratio of the passenger user on the toll road.

[0081] After determining the split fee information, the server side can send the order information to the client corresponding to the driver user, or can also send the order information to the client corresponding to the driver user in response to the order display request sent by the client corresponding to the driver user.

[0082] In order to enable the passenger user to clearly understand the split fee information of the toll, the server side can send the order information to the passenger user, and the order includes the split fee information of the passenger user. In order to make the process of determining the split fee information more open and transparent, the bill can also include at least one of the single-rider mileage, shared-rider mileage, and fee split ratio of the passenger user on the toll road.

[0083] After determining the split fee information, the server side can send the order information to the client corresponding to the passenger user, or can also send the order information to the client corresponding to the passenger user in response to the order display request sent by the client corresponding to the passenger user.

[0084] It should be noted that, for the privacy and security of each passenger user, the bill sent by the server side to the client corresponding to the driver user is for all passenger users, and the bill sent to the client corresponding to the passenger user is the bill corresponding to that passenger user. That is to say, a certain passenger can only view his own bill and cannot view the bills of other passengers in the shared ride order.

[0085] How the bill is presented on the client corresponding to the driver user and on the client corresponding to the passenger user will be described in detail in the subsequent embodiments.

[0086] Furthermore, in order to enable the passenger user to have a psychological expectation of the toll on the toll road before starting the shared ride order, the server side can display the estimated toll to the passenger user. Specifically, the server side can also estimate the estimated toll based on the travel information of the passenger user and the toll standard of the toll road, and send the information of the estimated toll to the client corresponding to the passenger user, so that the client can display the estimated toll and the toll split method options on the page for the passenger user to refer to.

[0087] After the order corresponding to the passenger user is completed, the server side can also perform anomaly recognition. As an implementable method, when the toll for a toll road exceeds the estimated toll by a degree reaching a preset threshold, the server side recognizes toll anomaly information and sends the toll anomaly information to the passenger user. That is to say, when the actual toll for a toll road significantly exceeds the estimated toll, it can be considered that an anomaly has occurred. An anomaly recognition interface can be called for anomaly recognition, where the anomaly recognition interface can be an interface provided by an anomaly recognition system based on a machine learning model. The obtained toll anomaly information mainly includes the reasons for the toll anomaly, for example, it can include route changes, sudden controls, etc. Then the obtained toll anomaly information is sent to the passenger users participating in the toll sharing so that the passenger users can know the reasons and thus avoid disputes or complaints.

[0088] The following describes in detail the processing performed by the client corresponding to the driver user in the carpooling travel scenario in combination with the embodiments.

[0089] In response to an operation that triggers the display of toll information, a bill is displayed on the page, and the bill includes at least the sharing cost information of the passenger users participating in the toll sharing for the toll road; wherein, the sharing cost information is determined based on the solo mileage of the passenger users participating in the toll sharing on the toll road and / or the shared mileage with other users participating in the toll sharing.

[0090] Furthermore, in addition to the sharing cost information, the bill can also include at least one of the solo mileage, shared mileage, and cost sharing ratio of the passenger users on the toll road. In this way, the driver user can learn from the page of the client the sharing cost information that each passenger user should share and how the sharing cost information is generated, improving the interpretability and rationality of the sharing cost information and enhancing the user experience of the driver user.

[0091] As a preferred implementation, as Figure 3 shown, the bill can include the sharing cost information of passenger user 1 and passenger user 2. For passenger user 1, the sharing cost information can be Figure 3 "55 yuan" in Figure 3 and for passenger user 2, the sharing cost information can be Figure 3 "15 yuan" in Figure 3 . The bill can also include at least one of the solo mileage, shared mileage, and cost sharing ratio of the passenger users on the toll road. For passenger user 1, the shared mileage can be Figure 3 "Shared 30 kilometers" in Figure 3For the "30-kilometer shared ride" in Figure 3 the "suggested share of 21.5%".

[0092] In Figure 3 the page only shows the sharing cost information of the passenger users participating in the sharing. If the driver user also participates in the sharing of the toll, then in addition to showing the sharing cost information of the passenger users participating in the sharing, the sharing cost information of the driver user can also be shown on the page.

[0093] Specifically, if the driver user participates in the sharing of the toll and there is one passenger user participating in the sharing of the toll, the sharing cost information is determined based on the shared mileage of the passenger user with the driver user on the toll road; if the driver user participates in the sharing of the toll and there are multiple passenger users participating in the sharing of the toll, the sharing cost information is determined based on the single-rider mileage of the passenger user on the toll road and the shared mileage with other passenger users and the driver user; if the driver user does not participate in the sharing of the toll and there are multiple passenger users participating in the sharing of the toll, the sharing cost information is determined based on the single-rider mileage of the passenger user on the toll road and the shared mileage with other passenger users.

[0094] Such a method can reasonably determine the sharing cost information between the driver user and the passenger user, make the sharing rule more refined, make the sharing cost more in line with the psychological expectations of the driver user and the passenger user, avoid disputes caused by excessive sharing of a certain user, and enhance the experience of the driver user and the passenger user.

[0095] In order to further reasonably resolve the contradiction between the passenger user and the driver user caused by the uneven sharing of the toll, as an achievable embodiment, if the driver user only accepts a carpooling order initiated by one passenger user and the passenger user participates in the sharing of the toll, then the other users participating in the sharing of the toll include the driver user; if the driver user accepts carpooling orders initiated by multiple passenger users and multiple passenger users all participate in the sharing of the toll, then the other users participating in the sharing of the toll may not include the driver user or may include the driver; if the driver user accepts carpooling orders initiated by multiple passenger users but only one passenger user participates in the sharing of the toll, then the other users participating in the sharing of the toll include the driver user.

[0096] That is to say, in addition to the driver user's own willingness to participate, this application also needs to consider the number of passenger users who participate in the sharing of tolls during a carpool trip. In a carpool trip, when there is only one passenger user who participates in the sharing of tolls, the driver user's participation in the sharing can prevent a single passenger user from bearing a large amount of tolls, thus bringing a better travel experience to the passenger user. If there are multiple passenger users who participate in the sharing of tolls, then the driver user can choose not to participate in the sharing of tolls to improve the driver user's order-taking experience.

[0097] Here is a simple explanation. A carpool trip is usually determined by the starting and ending positions of the driver user. A carpool trip may include an order from one passenger user or multiple passenger users' orders. For example, multiple passenger users share a ride, or multiple passenger users are picked up in a hitchhiking service. The end of an order from one passenger user does not mean the end of a carpool trip.

[0098] In the embodiments of this application, usually after a passenger user issues a carpool trip order, the driver user can choose to accept the carpool trip order according to his own itinerary and whether the passenger user shares the tolls. For example, a carpool trip order contains information that the passenger user does not share the tolls. If the driver user chooses to accept the order, he needs to bear all the tolls. For another example, a carpool trip order contains information that the passenger shares the tolls. If the driver user chooses to accept only one carpool trip order with toll sharing, then the driver user needs to share the tolls on the toll road; if the driver user chooses to accept two or more carpool trip orders with toll sharing, then the driver user may not need to share the tolls on the toll road.

[0099] To facilitate the driver user to view the order, the embodiments of this application provide multiple paths to trigger the display of fee information. That is, the operation to trigger the display of fee information may include but is not limited to at least one of the following:

[0100] The first operation: The operation of triggering the first component used to view fee information during the trip.

[0101] The operation of triggering the first component used to view fee information during the trip may refer to that when the trip has not ended, the driver user clicks on the first component, which is used to view fee information. As Figure 4 shown, Figure 4 the position "toll fee" enclosed by the yellow box in Figure 3 is the first component. When the driver user clicks on the first component, the driver user's corresponding client responds to the operation of triggering the first component and displays the bill on the page. As Figure 4 shown, that is, when the driver user clicks on the first component, Figure 3The middle page is to be shown to the driver user Figure 3 the bill in

[0102] The second operation: The operation triggered when the second component for ending the order is triggered.

[0103] The operation triggered when the second component for ending the order is triggered may mean that when a certain passenger user arrives at the corresponding destination, the driver user can end the order corresponding to the passenger user through the second component. For example, Figure 4 as shown Figure 4 the position "Arrival at Passenger's Destination" enclosed by the blue box in Figure 4 is the second component. When a certain passenger user arrives at the destination, the driver user triggers the second component (for example, swiping the second component to the right). The client corresponding to the driver user responds to the operation of the second component being triggered and changes from the page shown in Figure 5 to the page shown in Figure 5 to show the bill to the driver user.

[0104] The third operation: The operation triggered when the third component for viewing the collection progress after the trip is triggered.

[0105] The operation triggered when the third component for viewing the collection progress after the trip is triggered may mean that when all passenger users and the driver user have arrived at the destination, the driver user can view the bill through the third component. The third component is used to view the collection progress. For example, Figure 6a as shown Figure 6a the position enclosed by the yellow box in Figure 6a is the third component. After the trip ends, the driver user can click on the third component in the page shown in Figure 6b so that the client responds to the operation of the third component being triggered and shows the page shown in Figure 6b which can show the collection progress for each passenger user in this trip.

[0106] In addition to the above three operations, the operation to trigger the display of fee information can also be other operations, such as voice operations performed by the driver user on the corresponding client, that is, the driver user wakes up the corresponding client in a voice manner so that the corresponding client shows the bill, which will not be listed one by one here.

[0107] This application can provide multiple triggering methods to display the bill information. Whether during or after a trip, the driver user can view the bill information at any time. The display process is more convenient and fast, and it is convenient for the driver user to keep track of the shared expenses of each passenger user at any time, improving the experience of the driver user.

[0108] Generally speaking, in the above second operation, when the client corresponding to the driver user responds to the operation of triggering the second component, the order corresponding to a certain passenger user during the trip will change to an end state, that is, the passenger user arrives at the destination. At this time, the driver user can charge the shared toll to this passenger user. As a feasible method, the page for displaying the bill can also include a fourth component (such as Figure 5 the "Initiate Online Collection" button for passenger user 1 in Figure 7 ) used to initiate collection from the passenger user who ends the order. When the client corresponding to the driver user responds to the operation of triggering the fourth component, it can display the collection code of the driver user, as shown in Figure 6b , or it can also display the collection progress interface as shown in Figure 6b . In addition, if the driver user believes that the bill is incorrect, they can also click the "Withdraw Bill" button in Figure 7 to return to the page shown in Figure 5 . In this way, when a certain passenger user arrives at the destination, the driver user can timely collect the shared toll of this passenger user, improving the charging efficiency of the driver user and enhancing the usage experience of the driver user.

[0109] Of course, the driver user can also use other methods to collect the toll, such as offline cash payment, etc. At this time, the driver user can click the "I Have Collected" button in Figure 5 to indicate that the driver user has collected the shared toll of passenger user 1 through other means.

[0110] In the above second operation, if the operation of triggering the display of expense information is the operation of triggering the second component used to end the order, the page for displaying the bill can also include the toll of the paid road already paid by the driver user, and a fifth component used to modify the toll. For example, as shown in Figure 8a , the page for displaying the bill can include the tolls of each section of the paid road (XX Expressway and XXXX Expressway in the figure) ( Figure 8a the content boxed by the yellow rectangle in Figure 8a ), and each section of the expressway toll corresponds to a fifth component ( Figure 8a the content boxed by the blue rectangle in Figure 8a ). When the client corresponding to the driver user responds to the operation of triggering the fifth component, it displays a second modification interface, as shown in Figure 8b . Among them, the second modification interface includes: an input box for modifying the toll amount ( Figure 8bThe content enclosed by the yellow square box) and the sixth component for uploading vouchers Figure 8b The component enclosed by the blue square box). Then, in response to the operation of triggering the modification of the toll, the modification of the toll includes uploading vouchers and modifying the toll amount, and updating the displayed bill. That is, when the driver user has an objection to the toll of the paid road that has been paid, the toll can be modified in the second modification interface.

[0111] It can be seen that in order to further improve the experience of the driver user, this application allows the driver user to modify the toll in the second modification interface. However, in order to ensure the authenticity of the toll, the driver user also needs to upload vouchers while modifying the toll amount. After the uploaded vouchers can prove the authenticity and correctness of the modified toll amount, the displayed bill can be updated to ensure the experience of all users.

[0112] In actual application, there can be multiple segments of paid roads passed by a trip. In order to facilitate the driver user to accurately modify the toll for each segment of the road, this application can first display the total toll of the paid roads that have been paid and the ninth component for modifying the total toll on the page of the displayed bill (such as Figure 5 The position enclosed by the yellow square box).

[0113] Then, the client corresponding to the driver user displays the first modification interface in response to the operation of the ninth component being triggered, as shown in Figure 8a shown. Among them, the first modification interface includes the tolls of each segment of the paid road (such as Figure 8a The position enclosed by the yellow square box) and the fifth component for modifying the toll (such as Figure 8a The position enclosed by the blue square box). Further, in response to the operation of the fifth component being triggered, the second modification interface is displayed (as shown in Figure 8b shown). Among them, the second modification interface includes an input box for modifying the toll amount (such as Figure 8b The position enclosed by the yellow square box) and the sixth component for uploading vouchers (such as Figure 8b The position enclosed by the blue square box). The driver user can modify the toll amount in the second modification interface and click the sixth component to jump from the second modification interface to the photo-taking page (as shown in Figure 8c shown) to upload vouchers. After the voucher upload is completed (as shown in Figure 8d shown), the driver user can click the Figure 8d "Confirm Modification" button in. After the server-side review is passed, the displayed bill is updated based on the modified toll amount.

[0114] If the operation that triggers the display of the fare information is an operation triggered by the third component used to view the collection progress after the trip, the third component can be, for example, Figure 6a the position outlined by the yellow box in Figure 6b . The page for displaying the bill also includes a seventh component for sending a payment reminder to the passenger users who have not paid. The seventh component can be, for example,

[0115] the position outlined by the yellow box in (i.e., the "Remind" button). The client corresponding to the driver user responds to the operation triggered by the seventh component and sends a payment reminder to the passenger users who have not paid through the server. Among them, the payment reminder can be an in-app message sent to the client or other forms of messages such as text messages.

[0116] It should be noted that for the above embodiments in which the driver user modifies the toll, if the modified toll passes the server-side review, the sharing cost information of the passenger user on the corresponding toll road can be re-determined so that the sharing cost information can be dynamically adjusted with the modification of the driver user to ensure the fairness and real-time nature of the sharing cost information. Specifically, the sharing cost information is also determined based on the toll of the toll road that the driver user has paid. When the driver user modifies the toll of the toll road that has been paid, that is, the client corresponding to the driver user responds to the change in the toll of the toll road that the driver user has paid and updates the displayed bill.

[0117] Figure 9 This is a flowchart of the bill processing method executed by the client corresponding to the passenger user provided in the embodiments of the present application. As Figure 9 shown in, the method may include the following steps:

[0118] Step 901, receiving the information of the bill.

[0119] Step 902, in response to the operation that triggers the expense prompt information, display the bill on the page. The bill at least includes the sharing cost information of the passenger user; among them, the sharing cost information is determined based on the single-rider mileage of the passenger user participating in the toll sharing on the toll road and / or the shared mileage with other users participating in the toll sharing.

[0120] In the embodiments of the present application, the information of the received bill may be sent by the server side. For the determination of the sharing cost information of the passenger users participating in the toll sharing by the server side and the relevant records for sending the bill, reference may be made to the relevant records in the previous embodiments, which will not be elaborated here.

[0121] Among them, the bill at least includes the sharing cost information of the passenger user corresponding to the client. It should be noted that, in order to ensure the privacy and security of each passenger user, the client may only receive and display the sharing cost information corresponding to the passenger user corresponding to the current client. In addition, the bill may further include at least one of the single-rider mileage, shared-rider mileage, and cost sharing ratio of the passenger user on the toll road.

[0122] In the embodiments of the present application, the client corresponding to the passenger user responds to the operation of triggering the cost prompt information and displays the bill on the page. Among them, the cost prompt information may include the sharing cost information and an eighth component for triggering the payment process. When the passenger user triggers the eighth component, the client corresponding to the passenger user responds to the operation of triggering the eighth component and displays the bill on the page. The present application can enable the passenger user to timely learn the sharing cost information through the prompt for the passenger user, improve the experience of the passenger user, and remind the passenger user to timely pay the toll on the toll road, thereby improving the efficiency of order completion.

[0123] As one possible implementation, the above-mentioned cost prompt information may be displayed when the shared ride order corresponding to the passenger user has not ended, such as Figure 10a the position framed by the yellow square; it may also be displayed when the shared ride order corresponding to the passenger user has ended, such as Figure 10b the position circled by the yellow square. The ninth component may refer to Figure 10a or Figure 10b the position framed by the blue square.

[0124] Further, in response to the operation of triggering the ninth component in the cost prompt information, the client corresponding to the passenger user may jump to the Figure 11a shown page and display the bill corresponding to the passenger user in Figure 11a . Here, in addition to the sharing cost information, the bill may further include at least one of the single-rider mileage, shared-rider mileage, and cost sharing ratio of the passenger user on the toll road. This can inform the passenger user how the sharing cost information is determined, the sharing rules are open and transparent, and the interpretability is strong, avoiding disputes between the passenger user and the driver user and improving the trust of the passenger user.

[0125] Further, when the passenger user approves the Figure 11a shown bill, the passenger user may click the Figure 11a button of "Confirm and Pay 15 yuan for highway toll" to jump toFigure 11b , Figure 11b displays all the expense bills in the order to the passenger user in addition to the shared toll fees.

[0126] In the embodiment of the present application, the driver user can modify the toll fees for the paid roads that have been paid. Therefore, the client corresponding to the passenger user can, in response to a change in the toll fees for the paid roads paid by the driver user, receive the information of the new bill, and use the received information of the new bill to update the displayed bill.

[0127] In addition, after the carpooling order corresponding to the passenger user ends, as one possible implementation, when displaying the bill, in addition to including the shared expense information, the bill can also include a tenth component for raising objections to the bill, such as Figure 11a the position outlined by the yellow square in. The client corresponding to the passenger user, in response to an operation triggering the tenth component, sends a message of objecting to the bill to the server side (as shown in Figure 12 ).

[0128] As another possible implementation, the passenger user can also directly send a message of objecting to the bill to the server side through the customer service module in the client, and attach the bill number of the bill considered to be objected.

[0129] To meet the requirements of different passenger users, before generating the carpooling order, the client corresponding to the passenger user can, in response to an operation by the passenger user triggering the selection of the toll fee sharing method, display toll fee sharing options, where the toll fee sharing options can include not sharing the toll fees, fully bearing the toll fees, and sharing the toll fees. This method provides a mechanism for the passenger user to select the toll fee sharing method, and the passenger user can make a flexible selection according to their own wishes, thereby improving the user experience.

[0130] When the passenger user selects the option of fully bearing the toll fees or the option of not sharing the toll fees, the client corresponding to the passenger user does not need to use the method in the embodiment of the present application to receive the bill information and display the order. When the passenger user selects the option of sharing the toll fees, the client corresponding to the passenger user executes the method in the embodiment of the present application to receive the bill information and display the order.

[0131] Before generating the carpooling order, the client can display a page as shown in Figure 13a to the passenger user. The passenger user can click on the eleventh component corresponding to the yellow square and jump to Figure 13b . Figure 13b displays three toll fee sharing options, and the passenger user can select the desired toll fee sharing method in Figure 13b .

[0132] Furthermore, if the passenger user selects the option of not sharing the toll, when the driver user views the carpooling order sent by the passenger user, the driver user can send a message to the passenger user to negotiate whether the passenger user is willing to share the toll. After receiving the message, the passenger user can modify the option they selected to sharing the toll through the components included in the message or by replying to the message, or can also refuse to negotiate through the components included in the message or by replying to the message.

[0133] As a preferred embodiment, when the passenger user selects the option of sharing the toll, the estimated toll can be further displayed on the page showing the toll sharing option, so that the passenger user can have a psychological expectation of the shared toll in advance, which is convenient for timely payment of the toll subsequently and improves the efficiency of the entire carpooling process. The estimated toll is estimated based on the travel information of the passenger user and the highway toll standard, and the estimated toll can refer to Figure 13b the position framed by the yellow box in

[0134] When the toll of the toll road exceeds the estimated toll by a degree reaching a preset threshold, a fee anomaly information is generated. Here, the fee anomaly information can be detected and generated by the server side and sent to the client corresponding to the passenger user. The client corresponding to the passenger user obtains the fee anomaly information and puts it into the bill, and displays the fee anomaly information to the passenger user while displaying the bill. The fee anomaly information mainly includes the reason for the fee anomaly, such as route change, sudden control, etc. The passenger user can know the reason why the toll exceeds the estimated toll, thus avoiding disputes or complaints.

[0135] The above describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve the desired result. Additionally, the processes depicted in the figures do not necessarily require the particular order or sequential order shown to achieve the desired result. In certain implementations, multitasking and parallel processing are also possible or may be advantageous.

[0136] Figure 14 A schematic block diagram of the bill processing device according to an embodiment is shown. The device is arranged in Figure 1 the client corresponding to the driver user in the architecture shown. As Figure 14 shown, the device 1400 includes:

[0137] A first operation acquisition unit 1401, configured to acquire an operation that triggers the display of fee information.

[0138] The first page display unit 1402 is configured to display a bill on the page in response to an operation of triggering the display of fee information. The bill includes at least the share fee information of passenger users participating in the sharing of tolls on the paid road. The share fee information is determined based on the single-rider mileage of the passenger users participating in the sharing of tolls on the paid road and / or the shared-ride mileage with other users participating in the sharing of tolls.

[0139] As one possible implementation, the bill further includes at least one of the single-rider mileage, shared-ride mileage, and fee sharing ratio of the passenger user on the paid road.

[0140] As one possible implementation, if the driver user participates in the sharing of tolls and there is one passenger user participating in the sharing of tolls, the share fee information is determined based on the shared-ride mileage of the passenger user with the driver user on the paid road; if the driver user participates in the sharing of tolls and there are multiple passenger users participating in the sharing of tolls, the share fee information is determined based on the single-rider mileage of the passenger users and the shared-ride mileage with other passenger users and the driver user on the paid road; if the driver user does not participate in the sharing of tolls and there are multiple passenger users participating in the sharing of tolls, the share fee information is determined based on the single-rider mileage of the passenger users and the shared-ride mileage with other passenger users.

[0141] As one possible implementation, the operation of triggering the display of fee information includes at least one of the following: the operation of triggering the first component for viewing fee information during the trip, the operation of triggering the second component for ending the order, and the operation of triggering the third component for viewing the collection progress after the trip.

[0142] As one possible implementation, if the operation of triggering the display of fee information is the operation of triggering the second component for ending the order, the page for displaying the bill further includes: a fourth component for initiating collection from the passenger user who ends the order.

[0143] The first operation acquisition unit 1401 may also be configured to: acquire the operation of triggering the fourth component.

[0144] The first page display unit 1402 may also be configured to: display the collection code of the driver user in response to the operation of triggering the fourth component.

[0145] As one possible implementation, if the operation of triggering the display of fee information is the operation of triggering the second component for ending the order, the page for displaying the bill further includes: the tolls of the paid road already paid by the driver user, and a fifth component for modifying the tolls.

[0146] The first operation acquisition unit 1401 may also be configured to: acquire the operation triggered by the fifth component.

[0147] The first page display unit 1402 may also be configured to: in response to the operation triggered by the fifth component, display a second modification interface, where the second modification interface includes: an input box for modifying the toll amount and a sixth component for uploading vouchers; in response to the operation of triggering the modification of the toll, modifying the toll includes uploading vouchers and modifying the toll amount, and updating the displayed bill.

[0148] As one possible implementation, if the operation of triggering the display of fee information is the operation triggered by the third component for viewing the collection progress after the trip, the page for displaying the bill further includes: a seventh component for sending a payment reminder to the passenger user who has not paid.

[0149] The first operation acquisition unit 1401 may also be configured to: acquire the operation triggered by the seventh component.

[0150] The payment reminder unit 1403 may be configured to: in response to the operation triggered by the seventh component, send a payment reminder to the passenger user who has not paid through the server side.

[0151] As one possible implementation, the shared fee information is also determined based on the tolls of the paid roads that the driver user has paid.

[0152] The first page display unit 1402 may also be configured to: in response to a change in the tolls of the paid roads that the driver user has paid, update the displayed bill.

[0153] As one possible implementation, if the driver user only accepts a carpooling order initiated by one passenger user and the passenger user participates in the sharing of the toll, then the other users include the driver user; if the driver user accepts carpooling orders initiated by multiple passenger users and all the multiple passenger users participate in the sharing of the toll, then the other users do not include the driver user; if the driver user accepts carpooling orders initiated by multiple passenger users but only one passenger user participates in the sharing of the toll, then the other users include the driver user.

[0154] According to an embodiment of another aspect, a bill processing device is provided. Figure 15 A schematic block diagram showing the bill processing device according to an embodiment, the device is arranged in Figure 1 the client corresponding to the passenger user in the shown architecture. As Figure 15 shown, the device 1500 includes:

[0155] A second receiving unit 1501, configured to receive information about the bill.

[0156] The second operation acquisition unit 1502 is configured to acquire an operation for triggering the fee prompt information.

[0157] The second page display unit 1503 is configured to, in response to an operation for triggering the fee prompt information, display a bill on the page, where the bill at least includes the shared fee information of the passenger user. Among them, the shared fee information is determined based on the single-rider mileage of the passenger user participating in the toll sharing on the toll road and / or the shared mileage with other users participating in the toll sharing.

[0158] As one possible implementation, the fee prompt information includes the shared fee information and an eighth component for triggering the payment process; the operation for triggering the fee prompt information includes: an operation for triggering the eighth component.

[0159] As a possible implementation, the bill further includes at least one of the single-rider mileage, shared mileage, and fee sharing ratio of the passenger user on the toll road.

[0160] Furthermore, the second operation acquisition unit 1502 can also be configured to acquire an operation for triggering the selection of the toll sharing method.

[0161] The second page display unit 1503 can also be configured to: in response to an operation for triggering the selection of the toll sharing method, display toll sharing options, where the toll sharing options include not sharing the toll, fully bearing the toll, and sharing the toll; in the case where the passenger user selects the option of sharing the toll, perform the step of receiving the information of the bill.

[0162] Furthermore, the second operation acquisition unit 1502 can also be configured to acquire an operation for selecting the option of sharing the toll.

[0163] The second page display unit 1503 can also be configured to: in response to selecting the option of sharing the toll, further display an estimated toll, where the estimated toll is estimated based on the trip information of the passenger user and the highway toll standard.

[0164] Furthermore, the exception acquisition unit 1504 can be configured to: acquire fee exception information, where the fee exception information is generated when the toll on the toll road exceeds the estimated toll by a degree reaching a preset threshold.

[0165] According to an embodiment of another aspect, a bill processing device is provided. Figure 16 The schematic block diagram of the bill processing device according to an embodiment is shown, and the device is arranged in Figure 1 the server side in the architecture shown. As Figure 16 shown, the device 1600 includes:

[0166] A cost determination unit 1601, configured to determine the shared cost information of a passenger user based on the single-rider mileage of the passenger user on a toll road and / or the shared mileage with other users participating in the toll sharing.

[0167] A sending unit 1602, configured to send the information of the bill to the client corresponding to the driver user and / or the client corresponding to the passenger user, where the bill at least includes the shared cost information.

[0168] Each embodiment in this specification is described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other. The key point of each embodiment is to illustrate the differences from other embodiments. In particular, for the apparatus embodiments, since they are basically similar to the method embodiments, the description is relatively simple. For the relevant parts, reference can be made to the description of the method embodiments. The apparatus embodiments described above are only illustrative. The units described as separate components may or may not be physically separated. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement it without creative work.

[0169] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. And the collection, use, and processing of relevant data need to comply with the relevant laws, regulations, and standards of relevant countries and regions, and corresponding operation entrances are provided for users to choose to authorize or refuse.

[0170] In addition, the embodiment of this application also provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, the steps of the method described in any one of the foregoing method embodiments are implemented.

[0171] And an electronic device, including:

[0172] One or more processors; and

[0173] A memory associated with the one or more processors, where the memory is used to store program instructions, and when the program instructions are read and executed by the one or more processors, the steps of the method described in any one of the foregoing method embodiments are executed.

[0174] The present application also provides a computer program product, including a computer program which, when executed by a processor, implements the steps of the method described in any one of the foregoing method embodiments.

[0175] Among them, Figure 17 an exemplary architecture of an electronic device is shown, which may specifically include a processor 1710, a video display adapter 1711, a disk drive 1712, an input / output interface 1713, a network interface 1714, and a memory 1720. The above-mentioned processor 1710, video display adapter 1711, disk drive 1712, input / output interface 1713, network interface 1714, and the memory 1720 may be communicatively connected through a communication bus 1730.

[0176] Among them, the processor 1710 may be implemented in a general-purpose CPU, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, etc., and is used to execute relevant programs to implement the technical solution provided by the present application.

[0177] The memory 1720 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, etc. The memory 1720 may store an operating system 1721 for controlling the operation of the electronic device 1700, and a basic input / output system (BIOS) 1722 for controlling the low-level operations of the electronic device 1700. In addition, a web browser 1723, a data storage management system 1724, a bill processing device 1725, etc. may also be stored. The above-mentioned bill processing device 1725 may be the application program that specifically implements the operations of the foregoing steps in the embodiments of the present application. In short, when implementing the technical solution provided by the present application through software or firmware, the relevant program codes are stored in the memory 1720 and are called and executed by the processor 1710.

[0178] The input / output interface 1713 is used to connect to an input / output module to implement information input and output. The input / output module may be configured as a component in the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Among them, the input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

[0179] The network interface 1714 is used to connect to a communication module (not shown in the figure) to enable communication and interaction between this device and other devices. The communication module can achieve communication through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0180] The bus 1730 includes a path for transmitting information between various components of the device (such as the processor 1710, video display adapter 1711, disk drive 1712, input / output interface 1713, network interface 1714, and memory 1720).

[0181] It should be noted that although the above device only shows the processor 1710, video display adapter 1711, disk drive 1712, input / output interface 1713, network interface 1714, memory 1720, bus 1730, etc., in the specific implementation process, the device may also include other components necessary for normal operation. In addition, those skilled in the art can understand that the above device may also only include the components necessary to implement the solution of this application, and does not necessarily include all the components shown in the figure.

[0182] From the description of the above embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer program product. This computer program product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or some parts of the embodiments of this application.

[0183] The above has introduced the technical solution provided by this application in detail. Specific examples are used in this article to elaborate on the principle and implementation manner of this application. The description of the above embodiments is only used to help understand the method and its core idea of this application; at the same time, for those of ordinary skill in the art, according to the idea of this application, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to this application.

Claims

1. A bill processing method, applied to the client corresponding to the driver user in the carpooling travel scenario, characterized in that The method includes: In response to an operation for triggering the display of fee information, a bill is displayed on a page, and the bill at least includes the sharing fee information of passenger users participating in the sharing of tolls for a toll road; Wherein, the sharing fee information is determined based on the single-rider mileage of the passenger users participating in the sharing of the tolls on the toll road and / or the shared mileage with other users participating in the sharing of the tolls.

2. The method according to claim 1, wherein The bill further includes at least one of the single-rider mileage, shared mileage, and fee sharing ratio of the passenger user on the toll road.

3. The method according to claim 1, wherein The operation for triggering the display of fee information includes at least one of the following: An operation of triggering a first component for viewing fee information during a trip, an operation of triggering a second component for ending an order, and an operation of triggering a third component for viewing the collection progress after a trip.

4. The method according to claim 3, wherein If the operation for triggering the display of fee information is an operation of triggering a second component for ending an order, the page for displaying the bill further includes: a fourth component for initiating collection from the passenger user who ends the order; In response to an operation of triggering the fourth component, a collection code of the driver user is displayed.

5. The method according to claim 3, characterized in that, If the operation for triggering the display of fee information is an operation of triggering a second component for ending an order, the page for displaying the bill further includes: the toll paid by the driver user for the toll road, and a fifth component for modifying the toll; In response to an operation of triggering the fifth component, a second modification interface is displayed, and the second modification interface includes: an input box for modifying the toll amount and a sixth component for uploading a voucher; In response to an operation of triggering the modification of the toll, the modification of the toll includes uploading a voucher and modifying the toll amount, and the displayed bill is updated.

6. The method according to claim 3, characterized in that, If the operation for triggering the display of fee information is an operation of triggering a third component for viewing the collection progress after a trip, the page for displaying the bill further includes: a seventh component for sending a payment reminder to the passenger user who has not made a payment; In response to an operation of triggering the seventh component, a payment reminder is sent to the passenger user who has not made a payment through the server side.

7. The method according to any one of claims 1 to 6, characterized in that The sharing fee information is further determined based on the toll paid by the driver user for the toll road; The method further includes: In response to a change in the toll paid by the driver user for the toll road, the displayed bill is updated.

8. The method according to any one of claims 1 to 6, characterized in that, If the driver user participates in the sharing of the tolls and there is one passenger user participating in the sharing of the tolls, the sharing fee information is determined based on the shared mileage of the passenger user with the driver user on the toll road; If the driver user participates in the sharing of the tolls and there are multiple passenger users participating in the sharing of the tolls, the sharing fee information is determined based on the single-rider mileage of the passenger users and the shared mileage with other passenger users and the driver user on the toll road; If the driver user does not participate in the sharing of the toll, and there are multiple passenger users participating in the sharing of the toll, the sharing cost information is determined based on the single-rider mileage of the passenger user on the toll road and the shared-rider mileage with other passenger users.

9. The method according to any one of claims 1 to 6, characterized in that, The method further includes: If the driver user only accepts a carpooling order initiated by one passenger user, and the passenger user participates in the sharing of the toll, the other users include the driver user; If the driver user accepts carpooling orders initiated by multiple passenger users, and all the multiple passenger users participate in the sharing of the toll, the other users do not include the driver user; If the driver user accepts carpooling orders initiated by multiple passenger users, but only one passenger user participates in the sharing of the toll, the other users include the driver user.

10. A bill processing method, applied to the client corresponding to the passenger user in the carpooling travel scenario, characterized in that, The method includes: Receiving bill information; In response to an operation triggering a cost prompt message, displaying the bill on a page, where the bill at least includes the sharing cost information of the passenger user; Wherein, the sharing cost information is determined based on the single-rider mileage of the passenger user participating in the sharing of the toll on the toll road and / or the shared-rider mileage with other users participating in the sharing of the toll.

11. The method according to claim 10, wherein The cost prompt message includes the sharing cost information and an eighth component for triggering a payment process; The operation triggering the cost prompt message includes: an operation triggering the eighth component.

12. The method according to claim 10, wherein The bill further includes at least one of the single-rider mileage, shared-rider mileage, and cost sharing ratio of the passenger user on the toll road.

13. The method according to any one of claims 10 to 12, characterized in that The method further includes: In response to an operation by the passenger user triggering the selection of a toll sharing method, displaying toll sharing options, where the toll sharing options include not sharing the toll, fully bearing the toll, and sharing the toll; In the case where the passenger user selects the option of sharing the toll, performing the step of receiving the bill information.

14. The method according to claim 13, characterized in that, In response to the passenger user selecting the option of sharing the toll, further displaying an estimated toll, which is estimated based on the trip information of the passenger user and the toll standard of the toll road.

15. The method according to claim 14, wherein The method further includes: Obtaining cost exception information, which is generated when the toll of the toll road exceeds the estimated toll by a degree reaching a preset threshold.

16. A bill processing method, applied to the server side in the carpooling travel scenario, characterized in that, The method includes: Determining the sharing cost information of the passenger user based on the single-rider mileage of the passenger user participating in the sharing of the toll on the toll road and / or the shared-rider mileage with other users participating in the sharing of the toll; Sending the bill information to the client corresponding to the driver user and / or the client corresponding to the passenger user, where the bill at least includes the sharing cost information.

17. A bill processing device is provided in the client corresponding to the driver user in the carpooling scenario, and is characterized in that The device includes: A first operation acquisition unit configured to acquire an operation triggering the display of cost information; A first page display unit configured to, in response to the operation triggering the display of cost information, display a bill on a page, where the bill at least includes the sharing cost information of the passenger user participating in the sharing of the toll on the toll road; Among them, the shared cost information is determined based on the single-rider mileage of the passenger user participating in the toll sharing on the toll road and / or the shared mileage with other users participating in the toll sharing.

18. A bill processing device is provided in a client corresponding to a passenger user in a shared ride scenario, and is characterized in that The device includes: A second receiving unit, configured to receive information of the bill; A second operation obtaining unit, configured to obtain an operation triggering the cost prompt information; A second page display unit, configured to display the bill on the page in response to the operation triggering the cost prompt information, where the bill at least includes the shared cost information of the passenger user; Among them, the shared cost information is determined based on the single-rider mileage of the passenger user participating in the toll sharing on the toll road and / or the shared mileage with other users participating in the toll sharing.

19. A bill processing device is provided at the server side in the scenario of shared ride-hailing, characterized in that, The device includes: A cost determination unit, configured to determine the shared cost information of the passenger user based on the single-rider mileage of the passenger user participating in the toll sharing on the toll road and / or the shared mileage with other users participating in the toll sharing; A sending unit, configured to send the information of the bill to the client corresponding to the driver user and / or the client corresponding to the passenger user, where the bill at least includes the shared cost information.

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

21. An electronic device, characterized in that, Including: One or more processors; And A memory associated with the one or more processors, where the memory is used to store program instructions, and when the program instructions are read and executed by the one or more processors, they execute the steps of the method according to any one of claims 1 to 16.

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

Images