Electronic ride invoice processing method and apparatus

Abstract

Embodiments of the present specification provide an electronic ride invoice processing method and device, wherein the electronic ride invoice processing method comprises: obtaining a ride order generated according to ride trip information uploaded by a transmission component; querying a target payment order in which payment information matches the ride trip information in at least one payment order generated by a payment platform; establishing an association relationship between the ride order and the target payment order; based on the association relationship, determining an electronic ride invoice of the target payment order and performing invoice application channel configuration.

Description

[0001] This application is a divisional application of Chinese invention patent application filed on November 2, 2020, with application number CN202011202843.1 and title "Method and Apparatus for Processing Electronic Passenger Invoices". Technical Field

[0002] This document relates to the field of data processing technology, and in particular to a method and apparatus for processing electronic bus fares. Background Technology

[0003] Taxis are a mode of transportation service characterized by convenience, comfort, flexibility, all-weather operation, and door-to-door service, comparable to private cars to some extent. They have become a popular mode of transportation for those with strong personalization and purchasing power. Taxis have always provided convenience for users. However, while bringing convenience and comfort, many problems remain unresolved, hindering the development of the taxi industry. Summary of the Invention

[0004] This specification provides one or more embodiments of an electronic travel invoice processing method. The method includes: obtaining a travel order generated based on travel information uploaded by a transmission component; querying a target payment order whose payment information matches the travel information from at least one payment order generated by a payment platform; establishing an association between the travel order and the target payment order; and determining the electronic travel invoice for the target payment order and configuring the invoice application channel based on the association.

[0005] This specification provides one or more embodiments of an electronic travel invoice processing device, comprising: an acquisition module configured to acquire a travel order generated based on travel information uploaded by a transmission component; a query module configured to query a target payment order whose payment information matches the travel information from at least one payment order generated by a payment platform; an association module configured to establish an association between the travel order and the target payment order; and a determination module configured to determine the electronic travel invoice for the target payment order and configure an invoice application channel based on the association.

[0006] This specification provides one or more embodiments of an electronic fare invoice processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: acquire a trip order generated based on fare trip information uploaded by a transmission component; query a target payment order whose payment information matches the fare trip information from at least one payment order generated by a payment platform; establish an association between the trip order and the target payment order; and, based on the association, determine the electronic fare invoice for the target payment order and configure the invoice application channel.

[0007] This specification provides one or more embodiments of a storage medium for storing computer-executable instructions that, when executed, perform the following process: obtaining a trip order generated based on travel information uploaded by a transmission component; querying a target payment order whose payment information matches the travel information from at least one payment order generated by a payment platform; establishing an association between the trip order and the target payment order; and, based on the association, determining an electronic travel invoice for the target payment order and configuring an invoice application channel. Attached Figure Description

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

[0009] Figure 1 A flowchart illustrating an electronic bus ticket processing method provided for one or more embodiments of this specification;

[0010] Figure 2 A flowchart illustrating an electronic fare invoice processing method for a taxi scenario, provided for one or more embodiments of this specification.

[0011] Figure 3 A schematic diagram of an electronic bus ticket processing device provided for one or more embodiments of this specification;

[0012] Figure 4 This is a schematic diagram of the structure of an electronic bus ticket processing device provided for one or more embodiments of this specification. Detailed Implementation

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

[0014] This manual provides an example of an electronic fare invoice processing method:

[0015] Reference Figure 1 It shows a flowchart of an electronic fare invoice processing method provided in this embodiment, with reference to... Figure 2 The diagram illustrates a process flow chart of an electronic fare invoice processing method for taxi scenarios provided in this embodiment.

[0016] Reference Figure 1 The electronic bus ticket processing method provided in this embodiment specifically includes the following steps S102 to S108.

[0017] Step S102: Obtain the trip order generated based on the travel information uploaded by the transmission component.

[0018] In practice, a paper invoice is printed out by default after each taxi ride. To a certain extent, paper invoices are costly, prone to pollution and waste, and difficult to preserve. They are easily damaged or lost, and once lost, they cannot be reissued, causing inconvenience to passengers.

[0019] The electronic fare invoice processing method provided in this embodiment first obtains a trip order generated based on the trip information uploaded by the transmission component. If the trip order is marked as paid, an electronic fare invoice for the corresponding trip is generated. Then, among multiple payment orders generated on the payment platform, a payment order corresponding to the electronic fare invoice is queried. If only one payment order is found, a binding relationship is established between the found payment order and the electronic fare invoice, and an access channel is opened to the user to access the electronic fare invoice, enabling the user to obtain the electronic fare invoice. This enables users to process invoices for online digital orders, saves costs, extends the invoice retention period, and further improves the convenience of using invoices for users.

[0020] In this embodiment, data transmission is achieved through an intermediate connection device (i.e., a transmission component). Furthermore, the transmission component enables data transmission between the taxi's central control system and the server side. Specifically, the transmission component establishes a physical connection with the taxi meter via a cable, and acquires and uploads data based on this physical connection.

[0021] In specific implementation, to ensure the reliability and effectiveness of the obtained data and the validity and authenticity of passenger rides, in an optional implementation of this embodiment, the transmission component is connected to the taxi meter via a ribbon cable. The transmission component obtains the identity identifier from the central control system connected to the meter and obtains the fare information from the ride trip information from the meter. Specifically, when the meter detects the taxi meter deducting or raising, it collects the trip start information and / or trip end information and transmits the trip start information and / or trip end information to the transmission component.

[0022] Specifically, to ensure data accuracy, the taxi information is directly obtained through a transmission component connected to the taxi. In one optional implementation of this embodiment, the transmission component uploads the ride information in the following manner:

[0023] Obtain trip start and end information;

[0024] If the conditions for uploading the trip are met, the trip start information and the trip end information will be uploaded as the travel trip information.

[0025] For example, a transmission component that establishes a physical connection with the taxi via a cable acquires the trip start information transmitted by the taxi meter when it detects the taxi meter deducting and the trip end information transmitted when it detects the taxi meter lifting. Once the transmission system detects that the fare has been received, it uploads the trip start and end information as the trip information. The trip start information includes the taxi driver's identification, the taxi's license plate number, the trip start time, and the trip start location. The trip end information includes the fare, the driver's identification, the taxi's license plate number, the trip end time, and the trip end location.

[0026] In practical applications, the transmission component is configured with at least one image identifier. This image identifier is used to bind drivers. Passengers cannot pay fares through the image identifier if the driver is not bound to it. Specifically, to simplify the fare payment process, before passengers pay by scanning the image identifier at the end of their trip, at least one driver involved in the shift change process of the vehicle belonging to the transmission component needs to bind to at least one image identifier configured on the transmission component. Specifically, one driver can only bind to one image identifier. When the taxi driver on duty scans the image identifier configured on the transmission component, the image identifier is bound to the driver on duty. After binding, the image identifier is configured as the payment identifier corresponding to the driver on duty, and an association is established between the payment identifier and the driver's payment account.

[0027] In practice, to save costs and reduce waste and environmental pollution, an electronic invoice is generated for each ride trip when the corresponding ride order is marked as paid. In one optional implementation of this embodiment, after obtaining the ride order generated from the ride trip data uploaded by the transmission component, the following operations are also performed:

[0028] When the trip order is marked as paid, an electronic travel invoice for the trip corresponding to the travel trip information is generated based on the travel trip information; wherein, the electronic travel invoice is associated with the travel trip information.

[0029] For example, a passenger takes a taxi from position p1 to position p2 at time t1. The taxi meter is connected to a transmission component via a ribbon cable. After the transmission component obtains the trip information from the meter and uploads it, it generates a trip order based on the trip information. After the passenger's trip ends and the fare is paid by scanning a code with the transmission component, the trip order is marked as paid. Based on this, an electronic invoice for the trip is generated. The electronic invoice is associated with the trip information for that particular trip.

[0030] Step S104: Query the target payment order whose payment information matches the travel itinerary information from at least one payment order generated by the payment platform.

[0031] In practice, the payment platform contains payment orders for at least one user's at least one travel trip. To link the electronic travel invoice, which is tied to the travel trip information, to the corresponding passenger's payment information for that trip, allowing the passenger to access the electronic travel invoice when needed, it is necessary to query the target payment order matching the travel trip. This embodiment queries the target payment order from four data dimensions: payment link, receiving account, payment time, and payment amount. These four data dimensions can be implemented in parallel or sequentially.

[0032] To make the retrieved target payment orders more effective and accurate, this embodiment provides an optional implementation method in which the target payment orders are retrieved in the following way:

[0033] In the at least one payment order, the payment link in the payment information is at least one intermediate payment order that corresponds to a specific payment link of the ride identification code;

[0034] In the at least one intermediate payment order, query the payment order in the payment information that matches the corresponding benchmark element in the ride trip information; the benchmark element includes: the receiving account of the driver on duty, the trip end time, and the ride fare;

[0035] Determine if the number of payment orders found is one;

[0036] If so, the queried payment order will be identified as the target payment order;

[0037] If not, it is determined that no payment information matching the travel itinerary information was found.

[0038] In practice, firstly, in the at least one payment order, at least one intermediate payment order containing a payment link corresponding to the ride identification code is queried. Then, in the at least one intermediate payment order, payment orders whose receiving account, payment time, and payment amount in the payment information match the receiving account, trip termination time, and ride fare corresponding to the driver on duty in the ride trip information are queried. Then, the number of payment orders is determined. If the number of payment orders is one, the payment order is determined as the target payment order.

[0039] For example, a passenger takes a taxi driven by driver D, departing from point p1 at time t1 and arriving at point p2 at time t2. The fare is n1, the trip order is in a paid state, and an electronic invoice for the trip is generated. This electronic invoice is associated with the trip information. To find a payment order that matches the trip information, the system first searches for at least one intermediate payment order among at least one payment order generated by the payment platform, where the payment link in the payment information corresponds to a specific payment link of the ride identification code. Then, it searches for payment orders where the payee is the account corresponding to driver D, the payment time is within five minutes before or after time t2, and the payment amount is n1. Finally, it determines whether there is only one such payment order. If there is only one, this payment order is identified as the target payment order matching the trip information.

[0040] In addition, to improve the query efficiency of the target payment order, in an optional implementation of this embodiment, the target payment order can also be queried in the following way:

[0041] In the at least one payment order, query the payment information for at least one first payment order whose payment link corresponds to a specific payment link of the ride identification code;

[0042] In the at least one first payment order, query at least one second payment order in which the payee in the payment information is the receiving account corresponding to the driver on duty in the ride trip information;

[0043] In the at least one second payment order, query the payment information of at least one third payment order whose payment time is within a preset time range of the trip termination time in the travel information;

[0044] In the at least one third payment order, query the payment information of at least one fourth payment order whose payment amount falls within the preset fare range of the travel fare in the travel itinerary information;

[0045] Determine whether the number of the fourth payment orders is one;

[0046] If so, determine that the fourth payment order is the target payment order;

[0047] If not, it is determined that no payment information matching the travel itinerary information was found.

[0048] Specifically, after obtaining the first payment order, it is determined whether the number of the first payment orders is one. If so, the first payment order is determined to be the target payment order. After obtaining the second payment order, it is determined whether the number of the second payment orders is one. If so, the second payment order is determined to be the target payment order. After obtaining the third payment order, it is determined whether the number of the third payment orders is one. If so, the third payment order is determined to be the target payment order. In addition, if the number of the first payment orders is one, the payment elements of the first payment order can also be verified, such as the receiving account, payment time, and payment amount. Similarly, if the number of the second payment order or the third payment order is one, the payment elements of the second payment order or the third payment order can also be verified.

[0049] For example, a passenger takes a taxi driven by driver D, departing from point p1 at time t1 and arriving at point p2 at time t2. The fare is n1, the trip order is in a paid state, and an electronic invoice for the trip P is generated. This electronic invoice is associated with the trip information. To find a payment order that matches the trip information, firstly, among at least one payment order generated by the payment platform, at least one first payment order is searched for that has a payment link corresponding to the ride identification code. Then, among the at least one first payment order, at least one second payment order is searched for that has the payee being the account corresponding to driver D. Next, among the at least one second payment order, at least one third payment order is searched for that has a payment time within five minutes before or after time t2. Finally, among the at least one third payment order, at least one fourth payment order with a payment amount of n1 is searched. Finally, it is determined whether there is only one fourth payment order. If so, this fourth payment order is identified as the target payment order that matches the trip information.

[0050] In practice, if the number of payment orders retrieved is not one, the query result for the target payment order is determined to be empty. To ensure that passengers can obtain the corresponding electronic fare invoice when using the service, in an optional implementation of this embodiment, the query is performed in the following manner when the query result is empty:

[0051] Determine the baseline payment information for the accessed payment orders in the order list;

[0052] Search for a target trip order whose travel information matches the baseline payment information from at least one trip order included in the trip order set;

[0053] Establish the association between the target trip order and the accessed payment order;

[0054] Based on the aforementioned relationship, the electronic travel invoice for the accessed payment order is displayed on the order details page of the accessed payment order.

[0055] Specifically, when a passenger opens a payment order corresponding to a travel trip, the baseline payment information of the accessed payment order is determined. A target travel order whose travel information matches the baseline payment information is queried from the at least one travel order. Based on the queried target travel order, an association is established between the target travel order and the accessed payment order. Based on this association, the electronic travel invoice for the travel trip corresponding to the target travel order is determined as the electronic travel invoice for the accessed payment order, and an association is established between the electronic travel invoice and the accessed payment order. Finally, the electronic travel invoice is displayed on the order details page of the accessed payment order, or a trigger control for viewing the electronic travel invoice is configured on the order details page.

[0056] To improve the matching degree between the travel itinerary information of the retrieved target travel order and the baseline payment information, this embodiment provides an optional implementation method in which the target travel order is retrieved in the following way:

[0057] Determine whether the payment link in the payment information of the accessed payment order is a specific payment link corresponding to the ride identification code;

[0058] In the case where the payment link is the specific payment link, the first trip order in the at least one trip order is queried to find the first trip order in the trip information where the fare in the trip information matches the payment amount in the benchmark payment information;

[0059] Determine whether the number of orders for the first trip is one;

[0060] If so, verify the receiving account corresponding to the identity identifier in the travel information of the first travel order with the receiving account in the benchmark payment information, and / or verify the travel termination time in the travel information with the payment time in the benchmark payment information;

[0061] If the verification is successful, the first trip order will be used as the target trip order.

[0062] In practice, the payment link contained in the accessed payment order is first determined to be the specific payment link corresponding to the ride identification code. If not, it is determined that the accessed payment order cannot issue an electronic ride invoice. If so, the first trip order whose ride fare in the at least one trip order is equal to the payment amount in the baseline payment information is queried, and it is determined whether there is one such trip order. If there is one such trip order, the first trip order is further verified. Specifically, the receiving account corresponding to the driver's identity in the ride information of the first trip order and the trip termination time are verified. Specifically, the receiving account corresponding to the driver's identity is verified to be consistent with the receiving account in the baseline information, and the trip termination time is verified to be consistent with the payment time in the baseline payment information. Finally, if the verification is successful, the first trip order is taken as the target trip order. If the verification fails, it is determined that the accessed payment order does not have a matching electronic ride invoice.

[0063] In one optional implementation of this embodiment, to further ensure the validity and accuracy of the target trip order and to further improve the matching degree between the travel information and the baseline payment information, if it is determined that the number of the first trip orders is at least two, further querying is performed in the following manner:

[0064] In the first trip order, search for the second trip order whose trip termination time in the travel information matches the payment time in the benchmark payment information;

[0065] Determine whether the number of orders for the second trip is one;

[0066] If so, verify the receiving account corresponding to the identity identifier in the travel itinerary information of the second travel order with the receiving account in the benchmark payment information;

[0067] If the verification is successful, the second trip order will be used as the target trip order.

[0068] In practice, among at least two first payment orders, a second trip order is queried whose trip termination information in the trip information matches the payment time in the benchmark payment information. It is then determined whether the number of second trip orders is one. If the number of second trip orders is one, further verification is performed on the second trip order. Specifically, the receiving account corresponding to the driver's identity in the trip information of the second trip order is verified. The receiving account corresponding to the driver's identity is verified to be consistent with the receiving account in the benchmark information. If they are consistent, the second trip order is used as the target trip order; if they are inconsistent, it is determined that the accessed payment order does not have a matching electronic travel invoice. If the number of second trip orders is at least two, a third trip order is queried among the at least two second trip orders whose receiving account corresponding to the driver's identity in the trip information matches the receiving account in the benchmark payment information. It is then determined whether the number of third trip orders is one. If yes, the third trip order is used as the target trip order; if not, it is determined that the accessed payment order does not have a matching electronic travel invoice.

[0069] Step S106: Establish the association between the trip order and the target payment order.

[0070] In practice, after retrieving the target payment order, the target payment order is treated as the payment order for the travel trip corresponding to the trip order, and an association is established between the trip order and the target payment order.

[0071] Step S108: Based on the association, determine the electronic travel invoice for the target payment order and configure the invoice application channel.

[0072] In practice, to simplify the passenger's usage process and enable passengers to use electronic travel invoices conveniently and quickly, after establishing the association between the trip order and the target payment order, the invoice application channel is configured on the order details page of the target payment order.

[0073] In one optional implementation of this embodiment, when a trip order generated based on the trip information uploaded by the transmission component is marked as paid, an electronic travel invoice for the trip corresponding to the trip information is generated. Based on this, the electronic travel invoice for the target payment order is determined and the invoice application channel is configured in the following manner:

[0074] The electronic travel invoice for the aforementioned travel trip is identified as the electronic travel invoice for the target payment order;

[0075] Establish the association between the electronic fare invoice and the target payment order, and configure the invoice application channel on the order details page of the target payment order.

[0076] In specific implementation, firstly, the electronic travel invoice for the travel trip is identified as the electronic travel invoice for the target payment order, and an association is established between the electronic travel invoice and the target payment order. Based on this, there is an association between the travel trip information, the electronic invoice, and the target payment order. Based on this association, the invoice application channel is configured on the order details page of the target payment order. In an optional implementation provided in this embodiment, the invoice application channel is configured in the following way:

[0077] The electronic fare invoice for the target payment order is displayed on the order details page of the target payment order;

[0078] Alternatively, a trigger control for the electronic fare invoice of the target payment order can be configured on the order details page of the target payment order.

[0079] For example, after querying, if a target payment order is found that matches the trip order, the electronic travel invoice for that trip is identified as the electronic travel invoice for the target payment order. Furthermore, an association is established between the electronic travel invoice and the target payment order. Then, the electronic travel invoice is displayed on the order details page of the target payment order, or a trigger control that allows viewing the electronic travel invoice is configured on the order details page.

[0080] The following is in conjunction with the appendix Figure 2 Taking the application of the electronic fare invoice processing method provided in this embodiment in a taxi scenario as an example, the electronic fare invoice processing method provided in this embodiment will be further explained. (Refer to...) Figure 2 The electronic fare invoice processing method applied to taxi scenarios specifically includes steps S202 to S216.

[0081] Step S202: Obtain the trip order generated from the travel information uploaded by the transmission component.

[0082] Step S204: Query the intermediate payment order in at least one payment order generated by the payment platform.

[0083] Specifically, in at least one payment order generated by the payment platform, the payment information is searched to find at least one intermediate payment order whose payment link corresponds to a specific payment link of the ride identification code.

[0084] Further, determine whether the query result for intermediate payment orders is empty;

[0085] If so, determine the base payment information of the accessed payment order in the order list; and query the target trip order whose travel information matches the base payment information in at least one trip order included in the trip order set; if there is only one target trip order, establish the association between the target trip order and the accessed payment order, and display the electronic travel invoice bound to the travel information corresponding to the target trip order on the order details page of the accessed payment order;

[0086] If not, proceed to steps S206 to S208.

[0087] Step S206: In the intermediate payment orders, query the payment orders that match the payment elements with the travel itinerary information.

[0088] Specifically, in the at least one intermediate payment order, the payment elements in the payment information are queried to find payment orders that match the corresponding benchmark elements in the travel itinerary information; the benchmark elements include: the receiving account corresponding to the driver on duty, the trip termination time and / or the travel fare.

[0089] Step S208: Determine whether the number of payment orders found is one;

[0090] If so, proceed to steps S210 to S216;

[0091] If not, it is determined that no target payment order matching the trip order was found.

[0092] Step S210: The queried payment order is identified as the target payment order.

[0093] Step S212: Establish the binding relationship between the target payment order and the trip order.

[0094] Step S214: Determine the electronic travel invoice for the target payment order.

[0095] Step S216: Configure the invoice application channel on the order details page of the target payment order.

[0096] The electronic fare invoice processing method provided in this embodiment first obtains a trip order generated based on the trip information uploaded by the transmission component. Then, it queries at least one payment order generated by the payment platform for a target payment order whose payment information matches the trip information. Based on the found target payment order, it establishes a relationship between the target payment order and the trip order and determines the electronic fare invoice for the target payment order. Finally, it configures the invoice application channel on the order details page of the target payment order. This links the trip information with the passenger's payment information, further saving costs and increasing the invoice retention time by issuing electronic invoices.

[0097] This specification provides an embodiment of an electronic fare invoice processing device as follows:

[0098] In the above embodiments, an electronic fare invoice processing method is provided, and correspondingly, an electronic fare invoice processing device is also provided, which will be described below with reference to the accompanying drawings.

[0099] Reference Figure 3 The diagram shows a schematic of an electronic bus ticket processing device provided in this embodiment.

[0100] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0101] This embodiment provides an electronic fare invoice processing device, including:

[0102] The acquisition module 302 is configured to acquire a trip order generated based on the travel trip information uploaded by the transmission component;

[0103] The query module 304 is configured to query at least one payment order generated by the payment platform for a target payment order whose payment information matches the travel itinerary information;

[0104] The association module 306 is configured to establish an association between the trip order and the target payment order;

[0105] The determination module 308 is configured to determine the electronic travel invoice for the target payment order and configure the invoice application channel based on the association relationship.

[0106] Optionally, the query module 304 includes:

[0107] The intermediate payment order query submodule is configured to query at least one intermediate payment order in the at least one payment order whose payment link is a specific payment link corresponding to the ride identification code in the payment information;

[0108] The element query submodule is configured to query, in the at least one intermediate payment order, payment orders in which payment elements in payment information match the corresponding benchmark elements in the ride trip information; the benchmark elements include: the receiving account corresponding to the identity of the driver on duty, the trip termination time and / or the ride fare;

[0109] The judgment submodule is configured to determine whether the number of queried payment orders is one.

[0110] If so, the target payment order determination submodule is run, which is configured to determine the queried payment order as the target payment order.

[0111] Optionally, the query module 304 includes:

[0112] The first payment order query submodule is configured to query at least one first payment order in the at least one payment order whose payment link in the payment information is a specific payment link corresponding to the ride identification code;

[0113] The second payment order query submodule is configured to query at least one second payment order in the at least one first payment order in which the payee in the payment information is the payee account corresponding to the driver on duty in the ride trip information;

[0114] The third payment order query submodule is configured to query at least one third payment order in the at least one second payment order whose payment time is within a preset time range of the trip termination time in the travel trip information.

[0115] The fourth payment order query submodule is configured to query at least one fourth payment order in the at least one third payment order whose payment amount in the payment information is within a preset fare range of the fare in the travel trip information.

[0116] The number determination submodule is configured to determine whether the number of the fourth payment order is one;

[0117] If so, then the target payment order determination submodule is run.

[0118] Optionally, the electronic fare invoice processing device further includes:

[0119] The electronic travel invoice generation module is configured to generate an electronic travel invoice for the travel trip corresponding to the travel trip information, based on the travel trip information, when the travel order is marked as paid; wherein the electronic travel invoice is associated with the travel trip information;

[0120] Accordingly, the determining module 308 is specifically configured to determine the electronic travel invoice of the travel trip as the electronic travel invoice of the target payment order; establish the association between the electronic travel invoice and the target payment order; and configure the invoice application channel on the order details page of the target payment order.

[0121] Optionally, the determining module 308 includes:

[0122] The display submodule is configured to establish the association between the electronic fare invoice and the target payment order and display the electronic fare invoice of the target payment order on the order details page of the target payment order;

[0123] The trigger control configuration submodule is configured to establish the association between the electronic fare invoice and the target payment order, and to configure the trigger control of the electronic fare invoice of the target payment order on the order details page of the target payment order.

[0124] Optionally, the transmission component uploads the travel information by running the following module:

[0125] The information acquisition module is configured to acquire trip start information and trip end information;

[0126] The information upload module is configured to upload the trip start information and the trip end information as travel trip information when the trip upload conditions are met.

[0127] Optionally, the transmission component is connected to the taxi meter via a ribbon cable. The transmission component obtains an identity identifier from the central control system connected to the meter and obtains the fare information from the trip information from the meter. When the taxi driver scans the image identifier configured by the transmission component, the image identifier is bound to the driver. After binding, the image identifier is configured as the payment identifier corresponding to the driver and an association is established between the payment identifier and the driver's payment account. The meter collects trip start information and / or trip end information when it detects the taxi meter deduction and / or meter lifting, and transmits the trip start information and / or trip end information to the transmission component.

[0128] Optionally, the electronic fare invoice processing device further includes:

[0129] The baseline payment information determination module is configured to determine the baseline payment information of the accessed payment orders in the order list;

[0130] The target trip order query module is configured to query a target trip order whose travel information matches the baseline payment information from at least one trip order included in the trip order set;

[0131] The association establishment module is configured to establish an association between the target trip order and the accessed payment order;

[0132] The page display module is configured to display the electronic travel invoice of the accessed payment order on the order details page of the accessed payment order based on the association relationship.

[0133] Optionally, the target trip order query module includes:

[0134] The payment link determination submodule is configured to determine whether the payment link in the payment information of the accessed payment order is a specific payment link corresponding to the ride identification code;

[0135] The first trip order query submodule is configured to, when the payment link is the specific payment link, query the first trip order in the at least one trip order whose travel fare in the travel information matches the payment amount in the benchmark payment information.

[0136] The first trip order number determination submodule is configured to determine whether the number of the first trip orders is one.

[0137] If so, the first verification submodule is run. The first verification submodule is configured to verify the receiving account corresponding to the identity identifier in the travel information of the first travel order with the receiving account in the benchmark payment information, and to verify the trip termination time in the travel information with the payment time in the benchmark payment information; if the verification is successful, the first travel order is used as the target travel order.

[0138] Optionally, the order number determination submodule includes:

[0139] The second trip order query unit is configured to query the second trip order in the first trip order that matches the trip termination time in the travel information with the payment time in the benchmark payment information;

[0140] The second trip order number determination unit is configured to determine whether the number of the second trip orders is one.

[0141] If so, the second verification unit is run. The second verification unit is configured to verify the receiving account corresponding to the identity identifier in the travel information of the second trip order with the receiving account in the base payment information; if the verification is successful, the second trip order is used as the target trip order.

[0142] This manual provides an example of an electronic fare invoice processing device as follows:

[0143] Corresponding to the electronic fare invoice processing method described above, based on the same technical concept, one or more embodiments of this specification also provide an electronic fare invoice processing device, which is used to execute the above-described electronic fare invoice processing method. Figure 4 This is a schematic diagram of the structure of an electronic bus ticket processing device provided for one or more embodiments of this specification.

[0144] like Figure 4 As shown, electronic fare invoice processing devices can vary significantly due to differences in configuration or performance. They may include one or more processors 401 and memory 402, with memory 402 storing one or more application programs or data. Memory 402 can be temporary or persistent storage. The application programs stored in memory 402 may include one or more modules (not shown), each module including a series of computer-executable instructions within the electronic fare invoice processing device. Furthermore, processor 401 may be configured to communicate with memory 402, executing the series of computer-executable instructions stored in memory 402 on the electronic fare invoice processing device. The electronic fare invoice processing device may also include one or more power supplies 403, one or more wired or wireless network interfaces 404, one or more input / output interfaces 405, one or more keyboards 406, etc.

[0145] In one specific embodiment, the electronic fare invoice processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the electronic fare invoice processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0146] Retrieve trip orders generated based on travel information uploaded by the transmission component;

[0147] Search for the target payment order whose payment information matches the travel itinerary information in at least one payment order generated by the payment platform;

[0148] Establish the association between the trip order and the target payment order;

[0149] Based on the aforementioned relationship, the electronic travel invoice for the target payment order is determined and the invoice application channel is configured.

[0150] Optionally, if the query result for the target payment order is empty, the following operation is performed:

[0151] Determine the baseline payment information for the accessed payment orders in the order list;

[0152] Search for a target trip order whose travel information matches the baseline payment information from at least one trip order included in the trip order set;

[0153] Establish the association between the target trip order and the accessed payment order;

[0154] Based on the aforementioned relationship, the electronic travel invoice for the accessed payment order is displayed on the order details page of the accessed payment order.

[0155] Optionally, querying a target trip order whose travel information matches the baseline payment information from at least one trip order included in the trip order set includes:

[0156] Determine whether the payment link in the payment information of the accessed payment order is a specific payment link corresponding to the ride identification code;

[0157] In the case where the payment link is the specific payment link, the first trip order in the at least one trip order is queried to find the first trip order in the trip information where the fare in the trip information matches the payment amount in the benchmark payment information;

[0158] Determine whether the number of orders for the first trip is one;

[0159] If so, verify the receiving account corresponding to the identity identifier in the travel information of the first travel order with the receiving account in the benchmark payment information, and / or verify the travel termination time in the travel information with the payment time in the benchmark payment information;

[0160] If the verification is successful, the first trip order will be used as the target trip order.

[0161] Optionally, if the determination of whether the number of the first trip orders is the result of a sub-step is negative, the following operation is performed:

[0162] In the first trip order, search for the second trip order whose trip termination time in the travel information matches the payment time in the benchmark payment information;

[0163] Determine whether the number of orders for the second trip is one;

[0164] If so, verify the receiving account corresponding to the identity identifier in the travel itinerary information of the second travel order with the receiving account in the benchmark payment information;

[0165] If the verification is successful, the second trip order will be used as the target trip order.

[0166] This specification provides an example of a storage medium as follows:

[0167] In accordance with the above-described method for processing electronic bus invoices, and based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0168] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process:

[0169] Retrieve trip orders generated based on travel information uploaded by the transmission component;

[0170] Search for the target payment order whose payment information matches the travel itinerary information in at least one payment order generated by the payment platform;

[0171] Establish the association between the trip order and the target payment order;

[0172] Based on the aforementioned relationship, the electronic travel invoice for the target payment order is determined and the invoice application channel is configured.

[0173] Optionally, if the query result for the target payment order is empty, the following operation is performed:

[0174] Determine the baseline payment information for the accessed payment orders in the order list;

[0175] Search for a target trip order whose travel information matches the baseline payment information from at least one trip order included in the trip order set;

[0176] Establish the association between the target trip order and the accessed payment order;

[0177] Based on the aforementioned relationship, the electronic travel invoice for the accessed payment order is displayed on the order details page of the accessed payment order.

[0178] Optionally, querying a target trip order whose travel information matches the baseline payment information from at least one trip order included in the trip order set includes:

[0179] Determine whether the payment link in the payment information of the accessed payment order is a specific payment link corresponding to the ride identification code;

[0180] In the case where the payment link is the specific payment link, the first trip order in the at least one trip order is queried to find the first trip order in the trip information where the fare in the trip information matches the payment amount in the benchmark payment information;

[0181] Determine whether the number of orders for the first trip is one;

[0182] If so, verify the receiving account corresponding to the identity identifier in the travel information of the first travel order with the receiving account in the benchmark payment information, and / or verify the travel termination time in the travel information with the payment time in the benchmark payment information;

[0183] If the verification is successful, the first trip order will be used as the target trip order.

[0184] Optionally, if the determination of whether the number of the first trip orders is the result of a sub-step is negative, the following operation is performed:

[0185] In the first trip order, search for the second trip order whose trip termination time in the travel information matches the payment time in the benchmark payment information;

[0186] Determine whether the number of orders for the second trip is one;

[0187] If so, verify the receiving account corresponding to the identity identifier in the travel itinerary information of the second travel order with the receiving account in the benchmark payment information;

[0188] If the verification is successful, the second trip order will be used as the target trip order.

[0189] It should be noted that the embodiments concerning storage media and the embodiments concerning user resource processing methods in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding methods described above, and the repeated parts will not be described again.

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

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

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

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

[0194] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0195] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

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

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

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

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

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

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

[0202] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

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

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

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

Claims

1. A method for processing electronic travel invoices, comprising: Retrieve trip orders generated from travel information uploaded by the transmission component connected to the fare meter; When the trip order is marked as paid, an electronic travel invoice for the corresponding trip is generated based on the travel trip information; After detecting that the fare has been received, the transmission component uploads the travel information obtained from the meter. The image identifier configured on the transmission component is scanned by the driver changing shifts in the vehicle to which the transmission component belongs and configured as the payment identifier corresponding to the driver. The trip order is paid by scanning the payment identifier. Search for the target payment order whose payment information matches the travel itinerary information in at least one payment order generated by the payment platform; The electronic travel invoice is identified as the electronic travel invoice for the target payment order, the association between the trip order and the target payment order is established, and the electronic travel invoice is displayed on the order details page of the target payment order.

2. The electronic fare invoice processing method according to claim 1, wherein querying the target payment order whose payment information matches the fare itinerary information in at least one payment order generated by the payment platform includes: In the at least one payment order, the payment link in the payment information is at least one intermediate payment order that corresponds to a specific payment link of the ride identification code; In the at least one intermediate payment order, query the payment order in the payment information that matches the corresponding benchmark element in the ride trip information; the benchmark element includes: the receiving account corresponding to the identity of the driver on duty, the trip termination time and / or the ride fare; Determine if the number of payment orders found is one; If so, the queried payment order will be identified as the target payment order.

3. The electronic fare invoice processing method according to claim 1, wherein querying the target payment order whose payment information matches the fare itinerary information in at least one payment order generated by the payment platform includes: In the at least one payment order, query the payment information for at least one first payment order whose payment link corresponds to a specific payment link of the ride identification code; In the at least one first payment order, query at least one second payment order in which the payee in the payment information is the receiving account corresponding to the driver on duty in the ride trip information; In the at least one second payment order, query the payment information of at least one third payment order whose payment time is within a preset time range of the trip termination time in the travel information; In the at least one third payment order, query the payment information of at least one fourth payment order whose payment amount falls within the preset fare range of the travel fare in the travel itinerary information; Determine whether the number of the fourth payment orders is one; If so, the fourth payment order is determined to be the target payment order.

4. The electronic travel invoice processing method according to claim 1, wherein the electronic travel invoice is associated with the travel itinerary information.

5. The electronic fare invoice processing method according to claim 4, wherein determining the electronic fare invoice as the electronic fare invoice for the target payment order includes: Establish the association between the electronic travel invoice and the target payment order.

6. The electronic travel invoice processing method according to claim 1, wherein the transmission component uploads the travel information in the following manner: Obtain trip start and end information; If the fare has been received, the trip start information and trip end information will be uploaded as trip information.

7. The electronic fare invoice processing method according to claim 1, wherein the transmission component is connected to the taxi meter via a ribbon cable, the transmission component obtains an identity identifier from the central control system connected to the taxi meter, and obtains fare information from the fare trip information from the taxi meter; After the image identifier is configured as the payment identifier, an association is established between the payment identifier and the driver's payment account; in, When the taxi meter detects the taxi meter deactivation and / or meter reactivation, the fare meter collects trip start information and / or trip end information, and transmits the trip start information and / or trip end information to the transmission component.

8. In the electronic fare invoice processing method according to claim 1, if the query result of the target payment order is empty, the following operation is performed: Determine the baseline payment information for the accessed payment orders in the order list; the baseline payment information includes the payment amount, the receiving account, and / or the payment time; Search for a target trip order whose travel information matches the baseline payment information from at least one trip order included in the trip order set; Establish the association between the target trip order and the accessed payment order; Based on the established association, the electronic travel invoice for the accessed payment order is displayed on the order details page of the accessed payment order.

9. The electronic travel invoice processing method according to claim 8, wherein querying a target travel order whose travel information matches the baseline payment information in at least one travel order included in the travel order set comprises: Determine whether the payment link in the payment information of the accessed payment order is a specific payment link corresponding to the ride identification code; In the case where the payment link is the specific payment link, the first trip order in the at least one trip order is queried to find the first trip order in the trip information where the fare in the trip information matches the payment amount in the benchmark payment information; Determine whether the number of orders for the first trip is one; If so, verify the receiving account corresponding to the identity identifier in the travel information of the first travel order with the receiving account in the benchmark payment information, and / or verify the trip termination time in the travel information of the first travel order with the payment time in the benchmark payment information; If the verification is successful, the first trip order will be used as the target trip order.

10. The electronic travel invoice processing method according to claim 9, where the execution result of the sub-step of determining whether the number of the first trip orders is one is negative, the following operation is performed: In the first trip order, search for the second trip order whose trip termination time in the travel information matches the payment time in the benchmark payment information; Determine whether the number of orders for the second trip is one; If so, verify the receiving account corresponding to the identity identifier in the travel itinerary information of the second travel order with the receiving account in the benchmark payment information; If the verification is successful, the second trip order will be used as the target trip order.

11. A method for processing electronic bus fare invoices, comprising: Retrieve trip orders generated from travel information uploaded by the transmission component connected to the fare meter; When the trip order is marked as paid, an electronic travel invoice for the corresponding travel trip is generated; After detecting that the fare has been received, the transmission component uploads the travel information obtained from the meter. The image identifier configured on the transmission component is scanned by the driver changing shifts in the vehicle to which the transmission component belongs and configured as the payment identifier corresponding to the driver. The trip order is paid by scanning the payment identifier. Search among the multiple payment orders generated by the payment platform for the target payment order corresponding to the electronic travel invoice; When there is only one target payment order, the electronic fare invoice is identified as the electronic fare invoice of the target payment order, and a binding relationship is established between the target payment order and the electronic fare invoice. Access to the electronic travel invoice is enabled for the target payment order.

12. An electronic passenger ticket processing device, comprising: The acquisition module is configured to acquire trip orders generated based on travel information uploaded from the transmission component connected to the fare meter; When the trip order is marked as paid, an electronic travel invoice for the corresponding trip is generated based on the travel trip information; After detecting that the fare has been received, the transmission component uploads the travel information obtained from the meter. The image identifier configured on the transmission component is scanned by the driver changing shifts in the vehicle to which the transmission component belongs and configured as the payment identifier corresponding to the driver. The trip order is paid by scanning the payment identifier. The query module is configured to query at least one payment order generated by the payment platform for a target payment order whose payment information matches the travel itinerary information; The association module is configured to identify the electronic travel invoice as the electronic travel invoice of the target payment order, establish an association between the trip order and the target payment order, and display the electronic travel invoice on the order details page of the target payment order.

13. An electronic passenger ticket processing device, comprising: processor; as well as, A memory configured to store computer-executable instructions, which, when executed, cause the processor to: Obtain a trip order generated from the travel trip information uploaded by the transmission component connected to the fare meter; if the trip order is marked as paid, generate an electronic travel invoice for the corresponding travel trip based on the travel trip information; After detecting that the fare has been received, the transmission component uploads the travel information obtained from the meter. The image identifier configured on the transmission component is scanned by the driver changing shifts in the vehicle to which the transmission component belongs and configured as the payment identifier corresponding to the driver. The trip order is paid by scanning the payment identifier. Search for the target payment order whose payment information matches the travel itinerary information in at least one payment order generated by the payment platform; The electronic travel invoice is identified as the electronic travel invoice for the target payment order, the association between the trip order and the target payment order is established, and the electronic travel invoice is displayed on the order details page of the target payment order.

14. A storage medium for storing computer-executable instructions, which, when executed, perform the following process: Obtain a trip order generated from the travel trip information uploaded by the transmission component connected to the fare meter; if the trip order is marked as paid, generate an electronic travel invoice for the corresponding travel trip based on the travel trip information; After detecting that the fare has been received, the transmission component uploads the travel information obtained from the meter. The image identifier configured on the transmission component is scanned by the driver changing shifts in the vehicle to which the transmission component belongs and configured as the payment identifier corresponding to the driver. The trip order is paid by scanning the payment identifier. Search for the target payment order whose payment information matches the travel itinerary information from at least one payment order generated by the payment platform; The electronic travel invoice is identified as the electronic travel invoice for the target payment order, the association between the trip order and the target payment order is established, and the electronic travel invoice is displayed on the order details page of the target payment order.

Images