Methods and devices for calculating bus fares
By installing a transmission component in taxis, data can be transmitted between the meter and the ETC system to generate the total fare, solving the problem of passengers manually entering the total fare and improving user trust and payment convenience.
Patent Information
- Application Number
- CN202410020871.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-11-02
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2040-11-02
AI Technical Summary
The inability to effectively integrate the fare data of taxi meters and the ETC system forces passengers to manually enter the total fare, which is cumbersome, has low trust levels, and negatively impacts the user experience.
By installing transmission components in taxis, data transmission between the fare meter and the ETC system is realized, the total fare is generated, and the data is provided to the billing server through an intermediate server to generate an unpaid trip order, thus integrating the fare of the fare meter and the ETC system.
It enables one-time payment of the total fare, increasing users' trust in fare information and the convenience of the payment process, thus improving the user experience.
Smart Images

Figure CN117935383B_ABST
Abstract
Description
[0001] This application is a divisional application of Chinese invention patent application filed on November 2, 2020, with application number CN202011202393.6 and title "Method and Apparatus for Calculating Bus Fares". Technical Field
[0002] This document relates to the field of data processing technology, and in particular to a method and apparatus for calculating travel expenses. 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 a method for calculating travel expenses. The method includes: obtaining travel information from a transmission component submitted to an intermediate server; querying the surcharge for a specific road segment based on the identity identifier in the travel information and the fare calculation time of the travel trip; calculating the total travel expense by combining the surcharge with the travel expense in the travel information; and querying whether there are any unpaid travel orders based on a query request sent by a payment system; the query request is generated after the transmission component and the user terminal scan together. If so, sending travel expense details, including the total travel expense of the unpaid travel order, to the payment system.
[0005] This specification provides one or more embodiments of a fare payment method, comprising: monitoring a payment request for a ride submitted by a user terminal after scanning a code with a transmission component; the transmission component being connected to the vehicle to which the identity identifier in the payment request belongs; sending a query request to a billing server based on the monitored payment request; receiving fare details of the total fare for unpaid ride orders carrying the identity identifier from the billing server; loading a payment order containing the fare details and sending it to the user terminal for display; and processing the payment order based on the user terminal's confirmation of the payment order.
[0006] This specification provides one or more embodiments of a data transmission method, including: acquiring trip start information at the trip start node and trip termination information at the trip end node for a user's travel itinerary. Upon detecting that trip reporting conditions are met, the trip start information and the trip termination information are reported as trip information to an intermediate server, which then provides this information to a billing server. The transmission component is connected to the vehicle corresponding to the trip information and acquires the trip start information and trip termination information through the vehicle.
[0007] This specification provides one or more embodiments of a fare calculation device, comprising: an acquisition module configured to acquire trip information submitted by a transmission component to an intermediate server; a fare query module configured to query a segment surcharge for a specific road segment of the trip based on an identity identifier in the trip information and the fare calculation time of the trip; a fare calculation module configured to calculate the total fare by combining the segment surcharge with the fare in the trip information; and an order query module configured to query for the existence of unpaid trip orders based on a query request sent by a payment system, wherein the query request is generated after the transmission component and the user terminal scan. If so, a query result sending module is executed, configured to send fare details carrying the total fare of the unpaid trip orders to the payment system.
[0008] This specification provides one or more embodiments of a fare payment device, comprising: a monitoring module configured to monitor a payment request for a ride submitted by a user terminal after scanning a code with a transmission component; the transmission component being connected to the vehicle to which the identity identifier in the payment request belongs; a query request sending module configured to send a query request to a billing server based on the monitored payment request; a query result receiving module configured to receive fare details of the total fare for unpaid ride orders carrying the identity identifier sent by the billing server; a payment order loading module configured to load a payment order containing the fare details and send it to the user terminal for display; and a payment processing module configured to process the payment order based on the user terminal's confirmation operation of the payment order.
[0009] This specification provides one or more embodiments of a data transmission apparatus, including: an acquisition module configured to acquire trip start information at a trip start node and trip termination information at a trip termination node for a user's travel itinerary; and a reporting module configured to, upon detecting that trip reporting conditions are met, report the trip start information and the trip termination information as trip information to an intermediate server, which then provides this information to a billing server. The transmission component is connected to the vehicle corresponding to the trip information and acquires the trip start information and trip termination information through the vehicle.
[0010] This specification provides one or more embodiments of a fare calculation device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: acquire trip information of a trip submitted by a transmission component to an intermediate server; query a segment surcharge for the trip on a specific road segment based on an identity identifier in the trip information and the fare calculation time of the trip; calculate the total fare by combining the segment surcharge with the fare in the trip information; and query for the existence of an unpaid trip order based on a query request sent by a payment system; the query request is generated after the transmission component and the user terminal cooperate in scanning; if so, send fare details carrying the total fare of the unpaid trip order to the payment system.
[0011] This specification provides one or more embodiments of a fare payment device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: monitor a payment request for a ride submitted by a user terminal after scanning a code with a transmission component; the transmission component being connected to the vehicle to which the identity identifier in the payment request belongs. Based on the monitored payment request, the processor sends a query request to a billing server. It receives fare details from the billing server, including the total fare of unpaid ride orders carrying the identity identifier. It loads a payment order containing the fare details and sends it to the user terminal for display. Based on the user terminal's confirmation of the payment order, it processes the payment.
[0012] This specification provides one or more embodiments of a data transmission device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: acquire trip start information at a trip start node and trip end information at a trip end node for a user's travel trip. Upon detecting that trip reporting conditions are met, the processor reports the trip start information and the trip end information as trip information to an intermediate server, which then provides this information to a billing server. The transmission component is connected to the vehicle corresponding to the trip information and acquires the trip start information and trip end information through the vehicle.
[0013] This specification provides one or more embodiments of a storage medium for storing computer-executable instructions that, when executed, implement the following process: Obtaining trip information of a travel itinerary submitted by a transmission component to an intermediate server; querying the segment surcharge for a specific road segment based on the identity identifier in the trip information and the fare calculation time of the travel itinerary; calculating the total fare by combining the segment surcharge with the fare in the trip information; querying whether there are any unpaid travel orders based on a query request sent by a payment system; the query request is generated after the transmission component and the user terminal cooperate in scanning; if so, sending travel fare details carrying the total fare of the unpaid travel order to the payment system.
[0014] This specification provides one or more embodiments of a second storage medium for storing computer-executable instructions, which, when executed, perform the following process: monitoring a payment request for a ride submitted by a user terminal after scanning a code with a transmission component; the transmission component is connected to the vehicle to which the identity identifier in the payment request belongs; sending a query request to a billing server based on the monitored payment request; receiving ride fare details (total fare for unpaid ride orders carrying the identity identifier) sent by the billing server; loading a payment order containing the ride fare details and sending it to the user terminal for display; and processing the payment order based on the user terminal's confirmation of the payment order.
[0015] This specification provides one or more embodiments of a third storage medium for storing computer-executable instructions. When executed, these instructions implement the following process: acquiring trip start information at the trip start node and trip end information at the trip end node for a user's travel itinerary. Upon detecting that the trip reporting conditions are met, the trip start information and trip end information are reported as trip information to an intermediate server, which then provides this information to a billing server. The transmission component is connected to the vehicle corresponding to the trip information and acquires the trip start information and trip end information through the vehicle. Attached Figure Description
[0016] 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.
[0017] Figure 1 A flowchart illustrating a method for calculating travel expenses provided in one or more embodiments of this specification;
[0018] Figure 2 A fare calculation timing diagram for a taxi scenario is provided for one or more embodiments of this specification;
[0019] Figure 3 A flowchart illustrating a method for paying fares for public transportation, provided for one or more embodiments of this specification;
[0020] Figure 4 A flowchart illustrating a data transmission method provided in one or more embodiments of this specification;
[0021] Figure 5 A schematic diagram of a fare calculation device provided for one or more embodiments of this specification;
[0022] Figure 6 A schematic diagram of a fare payment device provided for one or more embodiments of this specification;
[0023] Figure 7 A schematic diagram of a data transmission device provided for one or more embodiments of this specification;
[0024] Figure 8 A schematic diagram of a fare calculation device provided for one or more embodiments of this specification;
[0025] Figure 9A schematic diagram of a fare payment device provided for one or more embodiments of this specification;
[0026] Figure 10 This is a schematic diagram of the structure of a data transmission device provided for one or more embodiments of this specification. Detailed Implementation
[0027] 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.
[0028] This instruction manual provides an example of a method for calculating travel expenses:
[0029] Reference Figure 1 It shows a flowchart of a fare calculation method provided in this embodiment, with reference to... Figure 2 This illustrates a fare calculation timeline diagram for a taxi scenario provided in this embodiment.
[0030] The fare calculation method provided in this embodiment is executed by a billing server. The fare payment method embodiment provided in this specification is executed by a payment system. The data transmission method is executed by a transmission component. The fare calculation method applied to the billing server provided in this embodiment cooperates with the fare payment method applied to the payment system and the data transmission method applied to the transmission component provided in the following method embodiments during execution. Therefore, please refer to the corresponding content of the following method embodiments when reading this embodiment.
[0031] Reference Figure 1 The fare calculation method provided in this embodiment is applied to a billing server and specifically includes the following steps S102 to S110.
[0032] Step S102: Obtain the travel information of the travel itinerary submitted by the transmission component to the intermediate server.
[0033] In practical applications, taxi rides often pass through specific road sections such as highway toll stations where additional road fees are required. These additional road fees are usually paid by the driver and then communicated to the passenger at the end of the trip. The passenger then manually enters the total fare based on the meter reading and the additional road fees provided by the driver. This process is cumbersome and leads to low user trust.
[0034] The fare calculation method provided in this embodiment integrates the fees generated by the taxi meter and a third-party system (such as ETC (Electronic Toll Collection) system) by installing a transmission component in the taxi. This allows the user to pay both the meter and third-party system fees in one transaction. Specifically, the transmission component is connected to the taxi meter via a cable. The meter obtains the license plate number and the driver's identification from the taxi's central control system, as well as the trip start and end information. This trip information is then reported to an intermediate server, which in turn provides it to the billing server. Specifically, the transmission component first obtains the vehicle identification, driver identification, and fare information from the vehicle during the trip. Based on these information, it queries the ETC system for additional road surcharges for the trip. Finally, it calculates the fare based on the additional road surcharges and the fare information in the fare calculation. The system determines the total fare for the ride. Based on this, it generates an unpaid ride order including the total fare, vehicle identifier, and fare calculation time. Upon receiving a query request from the payment system, it checks whether an unpaid ride order corresponding to the driver identifier exists based on the driver identifier in the query request. If so, it sends the total fare and fare details of the unpaid ride order to the payment system. This integrates the taxi meter system and the electronic toll collection system, consolidating the fare and road surcharges, making the payment process more convenient for users, increasing user trust in the ride and the total fare, and thus improving the user's ride experience.
[0035] To integrate the taxi meter and the ETC system, this embodiment employs an intermediate connection device (i.e., a transmission component) to achieve data transmission. This transmission component facilitates data transmission between the taxi's central control system and the server. Specifically, the transmission component establishes a physical connection with the taxi meter via a cable, acquires data based on this physical connection, and uploads it to the intermediate server. Finally, the intermediate server provides this data to the billing server. The trip information refers to the driver identifier, vehicle identifier, fare, trip start time, trip end time, trip start location, and trip end location corresponding to a passenger's single trip. This trip information is acquired by the transmission component through the vehicle corresponding to the trip information. The trip start and end times, along with the trip end time, constitute the fare calculation time for the trip.
[0036] In specific implementation, to ensure the reliability and validity of the obtained data, optionally, the transmission component is connected to the taxi meter via a cable. The transmission component obtains the identity identifier from the central control system connected to the meter and obtains the fare information from the trip information from the meter; the identity identifier includes the taxi's vehicle identifier and the driver's identifier for the driver on duty. The meter sends the trip information to the transmission component at a specified time or when a certain instruction is triggered.
[0037] To ensure the validity and authenticity of passenger rides, the taxi deducts the meter and begins fare calculation at the start of the passenger's trip, and raises the meter and ends fare calculation at the end of the trip. In one optional implementation of this embodiment, the meter collects trip start information and / or trip end information when it detects the taxi deducting the meter and / or raising the meter, and transmits the trip start information and / or trip end information to the transmission component.
[0038] 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, before obtaining the trip information submitted from the transmission component to the intermediate server, the transmission component also performs the following operations:
[0039] Obtain the user's trip start information at the trip start node and trip termination information at the trip end node;
[0040] If the trip reporting conditions are met, the trip start information and the trip end information are reported as trip information to the intermediate server, which then provides them to the billing server.
[0041] For example, passenger P takes a taxi driven by driver D at time t1 from point p1 to point p2. The taxi's meter is connected to a transmission component via a cable. This transmission component obtains the taxi's license plate number and driver D's identification information through a central control system connected to the meter. At the start of the trip, driver D deducts the fare from the meter, and the meter begins calculating the fare. At this time, the meter sends the deducting time and location to the transmission component. At time t2, upon arriving at the destination p2, driver D raises the meter, and the meter stops calculating the fare. The fare is displayed, and the meter sends the meter-up time, meter-up location, and fare to the transmission component. Upon receiving these information, the transmission component reports the vehicle's license plate number, driver identification, meter-down time, meter-down location, meter-up time, meter-up location, and fare to the intermediate server, which then provides this information to the billing server. Alternatively, the license plate number and driver identification can be reported to the intermediate server in advance, while the meter-down time and meter-down location can be reported to the transmission component at time t2 along with the meter-up time, meter-up location, and fare. This physical connection to the transmission component enables data transmission between the meter and the billing server, improving the convenience and effectiveness of data transmission.
[0042] In practice, after detecting that the transmission component sends the trip information to the intermediate server, the billing server requests the trip information from the intermediate server; in addition, after receiving the trip information, the intermediate server actively sends the trip information to the billing server.
[0043] In practical applications, to prevent fatigue driving, the taxi industry implements a shift system where at least two drivers take turns on duty for each taxi. Specifically, to accommodate the trips and fare payments of multiple drivers in a single taxi, the transmission component may optionally be equipped with at least one image tag. The number of image tags on the transmission component corresponds to the number of drivers on duty participating in the shift change process. The image tags are mounted on an image tag component and connected via a slot or radio frequency identification (RFID) technology. For example, if two drivers participate in the shift change for a taxi, the transmission component connected to the vehicle will have two image tags on its front and back. Specifically, the image tag component contains a magnetic induction chip, allowing the transmission component to sense the image tag when it is attached to the transmission component. Furthermore, the image tag component is connected via a slot on the transmission component.
[0044] Based on this, the image identifier configured on the transmission component is for binding the driver. When the driver is not bound to the image identifier, the passenger cannot make payment through the image identifier. To simplify passenger payment, in an optional implementation of this embodiment, before the passenger finishes the ride and makes payment by scanning the image identifier configured on the transmission component, the taxi driver on duty needs to scan the 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 fare identifier corresponding to the driver on duty, and an association is established between the fare identifier and the driver's fare account.
[0045] Furthermore, to strengthen driver management, taxi companies use a check-in / clock-out system to determine the driver on duty for the current shift. To ensure that the driver on duty receives the fare from the passenger, in one optional implementation of this embodiment, the transmission component, upon detecting a clock-in command sent by the central control system, marks the fare identification associated with the driver corresponding to the clock-in command as active; and upon detecting the end of the driver's shift, marks the fare identification as frozen.
[0046] For example, a taxi has two drivers participating in a shift change, namely driver D1 and driver D2. Driver D1 and driver D2 each scan two image identifiers configured on the transmission component connected to the taxi's meter. Driver D1 is bound to image identifier 1, that is, image identifier 1 is configured as driver D1's payment identifier, and D2 is bound to image identifier 2, that is, image identifier 2 is configured as driver D2's payment identifier. When driver D1 is detected to have clocked in, the payment identifier configured for driver D1 by image identifier 1 is activated, and the payment identifier configured for driver D2 by image identifier 2 is frozen.
[0047] Step S104: Based on the identity identifier in the trip information and the fare calculation time of the trip, query the surcharge for the trip on a specific road segment.
[0048] When taking a taxi, one often passes through sections of road that require additional fees, such as highway tolls; the specific road sections mentioned in this embodiment are those requiring additional road fees. In practice, data interaction between different systems is achieved by obtaining the trip information and the additional road fees. In one optional implementation method provided in this embodiment, the additional road fees are queried in the following way:
[0049] Call the fee query interface provided by the third-party system, and send the identity identifier and pricing time in the trip information to the fee query interface. The third-party system will then query the segment surcharge of the transaction record of the identity identifier at the pricing time.
[0050] Obtain the additional charges for the road segment returned by the third-party system;
[0051] The third-party system includes the ETC system, and the specific road segment includes the ETC toll road segment.
[0052] Following the previous example, after obtaining the trip information for this ride, the query interface of the ETC system is called to send the identity of the driver D, license plate number, meter deduction time, and meter lifting time to the ETC system through the query interface. The ETC system receives this information and queries the ETC toll records of the taxi corresponding to the license plate number for the time period consisting of the meter deduction time and the meter lifting time, and returns the additional road surcharge for ETC tolling to the query interface.
[0053] Step S106: Calculate the additional cost of the road segment and the travel cost in the trip information to obtain the total travel cost.
[0054] In specific implementation, to avoid passenger distrust and non-cooperation caused by the driver verbally informing passengers of additional charges for certain routes, and to reduce economic losses due to driver calculation errors, this embodiment uses a billing server to calculate the total cost of the ride. Based on the total cost, in an optional implementation of this embodiment, the following operation is also performed: Based on the trip information and the additional charges for certain routes, an unpaid trip order is generated for the ride; wherein, the trip information includes at least one of the following: pricing information, driver identification, and vehicle identification; the pricing information includes at least one of the following: ride cost, trip start time, trip end time, trip start location, and trip end location; the trip start and end times and the trip end time constitute the pricing time for the ride.
[0055] In practical applications, each passenger's trip corresponds to a trip order, and each trip order has an order number that identifies the trip. Specifically, before generating an unpaid trip order for the trip, a unique order number is generated to identify the uniqueness of the trip. The order number includes the vehicle identifier, the trip start time, the trip end time, the total fare, the trip start location, and the GPS (Global Positioning System) location of the trip end location.
[0056] In practice, to verify the identity information of the driver to whom the driver identifier belongs and to ensure the security of passenger payments, this embodiment provides an optional implementation method that uses the following approach to determine the driver's identity:
[0057] Search for the identity identifier in the preset identity list;
[0058] If the identity identifier is found, it is determined that the identity identifier is in a tagged state.
[0059] For example, during a taxi ride taken by passenger P in a taxi driven by driver D, if the ETC system returns a road surcharge, this surcharge is added to the original fare to determine the total cost of passenger P's ride. After obtaining passenger P's trip information, an order number for the trip is generated based on this information. Based on the order number and the total fare, an unpaid trip order for passenger P's trip is generated and stored. After generating the unpaid trip order, to ensure passenger P's financial security and prevent others from mistakenly binding the image identifier configured on the transmission component, the identity identifier of driver D is queried from a pre-set driver information table to further verify the security of the receiving account. After finding driver D's identity identifier in the pre-set driver information table, driver D's identity identifier is marked as tagged.
[0060] Step S108: Check whether there are any unpaid travel orders based on the query request sent by the payment system.
[0061] In this embodiment, the query request is generated after the transmission component and the user terminal cooperate to scan; the transmission component is configured with an image identification component or an image acquisition component; when the transmission component is configured with the image identification component, it completes the scanning operation by scanning the image identification component bound to the driver on duty through the user terminal; when the transmission component is configured with the image acquisition component, it completes the scanning operation by acquiring the user identifier of the user terminal.
[0062] The payment system senses the payment request submitted by the transmission component in cooperation with the user terminal, confirms the identity of the receiving account in the payment request, generates a query request containing the receiving account, and sends the query request to the billing system. Upon receiving the query request, the system checks whether there are any unpaid trip orders corresponding to the receiving account based on the receiving account contained in the query request.
[0063] For example, after passenger P finishes a ride in a taxi driven by driver D, passenger P pays by scanning the payment identifier configured on the transmission component connected to the taxi's meter. After sensing passenger P's payment request for driver D's payment identifier, the payment system checks whether driver D is tagged. If driver D's identifier is tagged, the system generates a query request including driver D's identifier and sends it to the billing server. The billing server then checks whether there are any unpaid trip orders corresponding to driver D based on driver D's identifier.
[0064] In addition, the payment request also includes the time during which the transmission component and the user terminal cooperate to scan. If multiple unpaid trip orders are found corresponding to the driver identifier in the query request, the unpaid trip orders for the current ride are queried according to the time.
[0065] Step S110: Send the fare details, carrying the total fare of the unpaid trip order, to the payment system.
[0066] In this embodiment, upon finding the unpaid trip order, the system sends a fare detail including the total fare and fare breakdown of the unpaid trip order to the payment system. Specifically, to enable passengers to obtain the specific fare for their trip after scanning a code with the transmission component, the billing system sends a fare detail containing the total fare and fare breakdown of the unpaid order to the payment system. In one optional implementation of this embodiment, the fare detail is sent to the payment system in the following manner:
[0067] Read the total fare and fare details of the unpaid trip order;
[0068] Send the fare details, including the total fare and the fare breakdown, to the payment system.
[0069] In practice, when an unpaid trip order is found, the total fare and fare details of the unpaid trip order are read and sent to the payment system. In addition, to further enhance the passenger's perception, the fare details may also include the travel time.
[0070] The following is in conjunction with the appendix Figure 2 The provided fare calculation timeline diagram for taxi scenarios illustrates the application of the fare calculation method provided in this embodiment in taxi scenarios. It also explains the fare payment method and data transmission method for taxi scenarios provided below.
[0071] Reference Figure 2 The fare calculation method applied to the taxi scenario specifically includes steps S202 to S232.
[0072] Step S202: Obtain the user's travel itinerary start information at the trip start node and the trip termination information at the trip end node.
[0073] The trip start information includes at least one of the following: vehicle identification, driver identification of the driver on duty, trip start time, and trip start location;
[0074] Trip termination information includes at least one of the following: vehicle identification, driver's identification of the driver on duty, fare, trip termination time, and trip termination location.
[0075] Step S204: After obtaining the fare, report the trip information to the intermediate server.
[0076] The itinerary information includes the start and end information of the itinerary.
[0077] Step S206: Obtain the travel information of the journey submitted by the transmission component to the intermediate server.
[0078] The trip information includes: the taxi driver's identification, the taxi's license plate number, the trip start time, the trip start location, the trip end time, the trip end location, and the fare.
[0079] Step S208: Generate an order number for this trip based on the trip information.
[0080] Step S210: Call the query interface provided by the ETC system and send the identity identifier and the billing time to the query interface.
[0081] By calling the query interface provided by the ETC system and sending the identity identifier and billing time from the trip information to the query interface, the ETC system, after receiving the identity identifier and billing time, queries the road segment surcharge of the transaction records of the identity identifier at that billing time.
[0082] Step S212: Obtain the additional road segment fees returned by the ETC system.
[0083] Step S214: Calculate the total cost of the ride and the additional road segment fees to obtain the total cost of the ride.
[0084] Step S216: Generate an unpaid trip order including an identity identifier based on the trip information, order number, and total fare.
[0085] Step S218: Monitor the payment request for the ride submitted by the user terminal after scanning the code in cooperation with the transmission component.
[0086] In this process, the user terminal works with the transmission component to scan a payment identifier configured on the transmission component or to collect the user identifier of the user terminal using the image acquisition component configured on the transmission component.
[0087] Step S220: Generate a query request based on the payment request.
[0088] Step S222: Send the query request to the billing server.
[0089] Step S224: Check if there is an unpaid trip order corresponding to the identity identifier in the payment request.
[0090] Step S226: If yes, send the fare details, including the total fare for the unpaid trip order, to the payment system.
[0091] Step S228: Load the payment order containing fare details.
[0092] Step S230: Send the payment order to the user terminal.
[0093] Step S232: Based on the user terminal's confirmation operation of the payment order, process the payment order.
[0094] In summary, the fare calculation method provided in this embodiment first obtains the trip information of the trip submitted by the transmission component to the intermediate server. Then, based on the trip information, it queries the ETC system for the road segment surcharge of the trip. Next, it calculates the total fare in the trip information and the road segment surcharge to obtain the total fare. Based on the query request sent by the payment system, it queries the unpaid trip orders corresponding to the identity identifier in the query request. Finally, it sends the total fare and fare details of the unpaid trip orders to the payment system, thereby realizing the connection between the meter and the ETC system. This allows the fare of the trip to be displayed to the user at once, increasing the user's trust in the total fare.
[0095] This manual provides an example of a method for paying bus fares, as follows:
[0096] Reference Figure 3 The diagram illustrates a fare payment method processing flowchart provided in this embodiment.
[0097] The fare payment method provided in this embodiment is executed by a payment system, and it works in conjunction with the fare calculation method with a billing server as the execution subject and the data transmission method with a transmission component as the execution subject. Therefore, when reading this embodiment, please refer to the corresponding content of the above-mentioned method embodiments and the following method embodiments.
[0098] Reference Figure 3 The fare payment method provided in this embodiment is applied to a payment system and specifically includes the following steps S302 to S310.
[0099] Step S302: Monitor the payment request for the ride submitted by the user terminal after scanning the code in cooperation with the transmission component.
[0100] The fare payment method provided in this embodiment first monitors whether the payment identifier configured on the transmission component is scanned. If the payment identifier is scanned, the payment request is obtained, and a query request is generated and sent to the billing server based on the payment request. Upon receiving the fare details sent by the billing server, which carry the total fare of the unpaid trip order corresponding to the payment account in the payment request, the payment order containing the fare details is loaded and displayed on the user terminal. Based on the user terminal's confirmation operation of the payment order, and according to the total fare, the resources in the user terminal are transferred to the payment account. This improves the convenience of user payment and increases the user's awareness of the trip, saving the user time that would otherwise have to manually enter the fare after the trip.
[0101] To integrate the taxi meter and the ETC system, this embodiment uses an intermediate connection device (i.e., a transmission component) to achieve data transmission. 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, acquires data based on this physical connection, and uploads it to the intermediate server, which then provides it to the billing server. After the ride, passengers pay using their user terminals by scanning a payment identifier associated with the driver on duty, configured on the transmission component. The transmission component is equipped with an image identifier component or an image acquisition component. When configuring the image identifier component, the transmission component scans the image identifier associated with the driver on duty using the user terminal. When configuring the image acquisition component, the transmission component scans the user identifier of the user terminal. The payment request includes the user identifier of the user terminal and the driver identifier corresponding to the payment identifier.
[0102] In one optional implementation of this embodiment, in order to simplify the payment process for users after their journey, the payment system specifically monitors the payment request submitted by the user terminal by scanning the payment identifier configured in the transmission component when performing step S302.
[0103] In addition, when the transmission component is configured with an image acquisition component, the payment system monitors the payment request submitted by the image acquisition component of the user terminal by acquiring the image identification code of the user terminal, and monitors the payment request submitted by the transmission component after acquiring and parsing the user identifier of the user terminal through the configured image acquisition component.
[0104] In specific implementation, in order to achieve effective management of drivers and to verify the identity information of the driver to which the driver identifier belongs, and to ensure the security of passenger payment, in an optional implementation of this embodiment, after the query request is detected, the following operation is performed: First, it is checked whether the identity identifier contained in the payment request is in a tagged state. If so, a query request containing the identity identifier is generated.
[0105] For example, after passenger P finishes his ride in a taxi driven by driver D, he scans the payment identifier configured on the transmission component connected to the taxi's meter and is bound to driver D to make payment. After detecting user P's scan of the payment identifier, the system queries whether driver D's identifier is tagged. If driver D's identifier is tagged, a query request carrying driver D's identifier is generated.
[0106] In specific implementation, the image identifier configured on the transmission component is for driver binding. Therefore, passengers cannot pay through the image identifier if the driver is not bound to it. To simplify passenger payment, in an optional implementation of this embodiment, before the passenger pays by scanning the image identifier configured on the transmission component at the end of the trip, the taxi driver on duty needs to scan the 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 fare identifier corresponding to the driver on duty, and an association is established between the fare identifier and the driver's fare account.
[0107] In practical applications, taxi companies use a check-in / clock-out system to determine the driver on duty for the current shift in order to strengthen driver management. To ensure that the driver on duty receives the fare from the passenger, in one optional implementation of this embodiment, the transmission component marks the fare identification associated with the driver on duty corresponding to the check-in / clock-out instruction as active when it detects a clock-in / clock-out instruction sent by the central control system; and marks the fare identification as frozen when it detects that the driver's shift has ended.
[0108] For example, a taxi has two drivers participating in a shift change, namely driver D1 and driver D2. Driver D1 and driver D2 each scan two image identifiers configured on the transmission component connected to the taxi's meter. Driver D1 is bound to image identifier 1, that is, image identifier 1 is configured as driver D1's payment identifier, and D2 is bound to image identifier 2, that is, image identifier 2 is configured as driver D2's payment identifier. When driver D1 is detected to have clocked in, the payment identifier configured for driver D1 by image identifier 1 is activated, and the payment identifier configured for driver D2 by image identifier 2 is frozen.
[0109] Step S304: Based on the detected payment request, send a query request to the billing server.
[0110] In specific implementation, after detecting a payment request submitted by the transmission component and the user terminal through QR code scanning, the status of the driver's identity identifier in the receiving account carried in the payment request is queried. If the identity identifier is found to be tagged, a query request including the identity identifier is generated and sent to the billing server. The billing server then queries whether there are any unpaid orders corresponding to the identity identifier. Specifically, if multiple unpaid trip orders are found to correspond to the identity identifier, the query is based on the time the payment request was generated, and the unpaid trip orders within a preset number of minutes before and after the time the payment request was generated are considered as the unpaid trip orders corresponding to the payment request.
[0111] For example, after detecting that passenger P's ride in a taxi driven by driver D has ended, the system scans the payment identifier configured on the transmission component connected to the taxi and sends a secondary request bound to driver D. Based on the identity identifier of driver D contained in the payment request, the system sends a query request to the billing server to check if there are any unpaid trip orders for driver D. If driver D has multiple unpaid trip orders, the system searches for unpaid trip orders of driver D within x minutes before and after the time of the payment request included in the query request, and identifies them as unpaid trip orders for passenger P's ride.
[0112] In addition, before receiving a query request, the billing server generates an unpaid trip order in the following manner: First, it obtains the trip information of the travel trip submitted by the transmission component to the intermediate server; then, based on the identity identifier in the trip information and the fare calculation time of the travel trip, it queries the road segment surcharge for the travel trip on a specific road segment; then, it calculates the road segment surcharge and the travel fare in the trip information to obtain the total travel fare; finally, based on the trip information and the road segment surcharge, it generates an unpaid trip order for the travel trip.
[0113] Step S306: Receive fare details from the billing server, which includes the total fare for the unpaid trip order carrying the identity identifier.
[0114] The total fare refers to the total cost obtained by the billing server by calculating the fare for the trip and any additional charges for the route. The fare details include the total fare and a breakdown of the fare. For example, if a passenger's trip has a fare of m1 on the meter, and the passenger's trip includes an ETC (Electronic Toll Collection) section with an ETC charge of m2, adding m1 and m2 gives the total fare for the trip. The details include m1, m2, and the specific route through which the charges were incurred.
[0115] In addition, after receiving the query request, the billing server shall perform the following operations: First, it shall check whether there are any unpaid trip orders based on the query request sent by the payment system; if so, it shall send the payment system a fare detail including the total fare of the unpaid trip order. If not, it shall return that the trip does not exist.
[0116] Step S308: Load the payment order containing the fare details and send it to the user terminal for display.
[0117] The payment order refers to the order displayed on the user terminal, which includes the fare details and operation buttons. To improve passenger convenience, save passengers time manually entering the total fare, and avoid traffic violations caused by excessively long taxi waiting times for payment, the specific implementation involves first rendering an initial payment order that the user terminal can operate on. Then, based on the fare details sent by the billing server, the total fare and the fare details are filled into the initial payment order to generate the payment order. Finally, the payment order is sent to the user terminal for display.
[0118] To further enhance the ease of use for passengers, this embodiment provides an optional implementation method in which the payment order is loaded in the following manner:
[0119] Detect whether the user has a password-free payment agreement with the payment system;
[0120] If so, the user's resources will be transferred to the resource space corresponding to the identity identifier according to the total fare.
[0121] If not, render the payment order for the user's ride trip; write the ride fare details into the payment order and display it to the user.
[0122] In practice, upon receiving the unpaid trip order, the system checks whether there is a password-free payment agreement between the user terminal and the payment system. If so, the payment order is processed directly. If not, a payment order for the trip is rendered, the fare details are written into the payment order, and displayed to the user. After receiving confirmation of the payment order from the user terminal, a reminder to activate password-free payment is sent to the user to whom the user terminal belongs.
[0123] For example, if the system obtains the fare details of passenger P's taxi ride with driver D on duty, it checks whether passenger P has a password-free payment agreement with the payment system. If so, it processes the payment for the ride based on the total fare details and displays the total fare and the fare details for the ride to passenger P. If not, it renders an initial payment order for passenger P's ride, writes the fare details into the initial payment order, and displays it to passenger P's user terminal.
[0124] Step S310: Based on the user terminal's confirmation operation of the payment order, process the payment order for payment.
[0125] In practice, after displaying the payment order to the user terminal, the user terminal's confirmation operation for the payment order is obtained. Based on the user's confirmation operation for the payment order, the payment order is processed, that is, the resources of the user terminal are transferred to the resource space of the driver on duty corresponding to the payment identifier.
[0126] For example, passenger P confirms a payment order for a taxi ride with driver D. Based on this confirmation, the total fare m0 in the payment order is deducted from passenger P's account, and the deducted amount is transferred to driver D's receiving account. Furthermore, after processing the payment, the transmission component announces the payment result via voice.
[0127] Reference Figure 2 The method for calculating fares in taxi scenarios includes the following steps.
[0128] Step S218: Monitor the payment request for the ride submitted by the user terminal after scanning the code in cooperation with the transmission component.
[0129] In this process, the user terminal works with the transmission component to scan a payment identifier configured on the transmission component or to collect the user identifier of the user terminal using the image acquisition component configured on the transmission component.
[0130] Step S220: Generate a query request based on the payment request.
[0131] Step S222: Send the query request to the billing server.
[0132] Step S228: Load the payment order containing fare details.
[0133] Step S230: Send the payment order to the user terminal.
[0134] Step S232: Based on the user terminal's confirmation operation of the payment order, process the payment order.
[0135] The fare payment method provided in this embodiment first monitors the payment request submitted by the user terminal after scanning a code with the transmission component. Based on the monitored payment request, a query request is generated and sent to the billing server. The billing server sends fare details carrying the total fare. Then, a payment order including the fare details is loaded and sent to the user terminal for display. Finally, based on the user terminal's confirmation of the payment order, the payment order is processed. In this way, the total fare of the trip is automatically filled into the payment order, improving user convenience, saving time, and avoiding traffic violations caused by long waiting times for user payment after the trip.
[0136] The following is an example of a data transmission method provided in this specification:
[0137] Reference Figure 4 The diagram illustrates a data transmission method processing flowchart provided in this embodiment.
[0138] The data transmission method provided in this embodiment is executed by a transmission component, and it works in conjunction with the fare calculation method with a billing server as the execution subject and the fare payment method with a payment system as the execution subject. Therefore, please refer to the corresponding content of the above-mentioned method embodiments when reading this embodiment.
[0139] Reference Figure 4The data transmission method provided in this embodiment is applied to a transmission component and specifically includes the following steps S402 to S404.
[0140] Step S402: Obtain the user's travel itinerary start information at the trip start node and the trip termination information at the trip end node.
[0141] The data transmission method provided in this embodiment first obtains the user's travel trip start information and trip end information; then, when the travel reporting conditions are met, the travel start information and trip end information are reported as travel trip information to an intermediate server, which then provides this information to the billing server. This ensures the reliability and validity of the data and improves the integrity of the data during transmission.
[0142] The transmission component described in this embodiment is connected to the vehicle corresponding to the trip information, and obtains the trip start information and trip end information through the vehicle. In specific implementation, to ensure the reliability and validity of the obtained data, optionally, the transmission component is connected to the taxi's meter via a cable. The transmission component obtains the identity identifier from the central control system connected to the meter, and obtains the fare information from the trip information from the meter; the identity identifier includes the taxi's vehicle identifier and the driver's identifier for the driver on duty.
[0143] To ensure the validity and authenticity of passenger rides, the taxi deducts the meter and starts calculating the fare when the passenger's trip begins, and raises the meter and stops calculating the fare when the trip ends. In one optional implementation of this embodiment, the meter collects trip start information and / or trip end information when it detects the taxi deducting the meter and / or raising the meter, and transmits the trip start information and / or trip end information to the transmission component.
[0144] To ensure data timeliness, reduce the amount of data during data transmission, and improve data transmission efficiency, this embodiment provides an optional implementation method in which the trip start information and trip end information are obtained in the following way:
[0145] Obtain the vehicle identifier of the vehicle and the driver identifier of the driver on duty who is associated with the vehicle;
[0146] Send the vehicle identifier and the driver identifier to the intermediate server;
[0147] Obtain the user's travel itinerary information at the start node and the end node.
[0148] The trip start information includes at least one of the following: trip start time and trip start location; the trip end information includes at least one of the following: trip end time, trip end location, and travel fare.
[0149] In specific implementation, the vehicle identifier and the driver identifier of the on-duty driver of the vehicle are first obtained and sent to the intermediate server; when a passenger takes a ride, the obtained ride information for that vehicle is matched with the vehicle identifier and the driver identifier; wherein, the trip start information only includes the trip start time and trip start location; the trip end information only includes the trip end time, trip end location and ride fare.
[0150] For example, passenger P takes a taxi driven by driver D at time t1 from point p1 to point p2. The taxi's meter is connected to a transmission component via a cable. This transmission component obtains the taxi's license plate number and driver D's identification information through a central control system connected to the meter. At the start of the trip, driver D deducts the fare from the meter, and the meter begins calculating the fare. At this time, the meter sends the deducting time and location to the transmission component. At time t2, upon arriving at the destination p2, driver D raises the meter, and the meter stops calculating the fare. The fare is displayed. At this time, the meter sends the meter-up time, meter-up position, and fare to the transmission component. Upon detecting that the meter-up time, meter-up position, and fare have been received, the transmission component reports the license plate number, driver identification, meter-down time, meter-down position, meter-up time, meter-up position, and fare to the intermediate server, which then provides this information to the billing server. Alternatively, the license plate number and driver identification can be reported to the intermediate server in advance, while the meter-down time and meter-down position can be reported to the transmission component at time t2 along with the meter-up time, meter-up position, and fare. Data transmission between the meter and the billing server is achieved through a physical connection to the transmission component.
[0151] In addition, this embodiment also provides a method for obtaining the trip start information and trip end information of the user's ride trip: First, the trip start information of the user's ride trip at the trip start node is obtained; wherein, the trip start information includes at least one of the following: the vehicle identifier of the vehicle, the driver identifier of the driver on duty bound to the vehicle, the trip start time, and the trip start location; then, the trip end information of the user's ride trip at the trip end node is obtained; wherein, the trip end information includes at least one of the following: the vehicle identifier of the vehicle, the driver identifier of the driver on duty bound to the vehicle, the fare, the trip end time, and the trip end location. When the meter detects that preset conditions are met, it sends the trip information to the transmission component.
[0152] In practical applications, to prevent fatigue driving, the taxi industry implements a shift system where each taxi has at least two drivers on duty. Specifically, to accommodate the travel and fare payment needs of multiple drivers in a single taxi, the transmission component may optionally be equipped with at least one image tag. The number of image tags on the transmission component corresponds to the number of drivers on duty participating in the shift change process. The image tags are mounted on an image tag component and connected via a slot or radio frequency identification (RFID) technology. For example, if a taxi has two drivers participating in shift changes, the transmission component connected to the vehicle will have two image tags on its front and back. Specifically, the image tag component contains a magnetic induction chip, allowing the transmission component to sense the image tag when it is attached to the transmission component. Furthermore, the image tag component is connected via a slot on the transmission component.
[0153] Based on this, the image identifier configured on the transmission component is for driver binding. Therefore, passengers cannot pay through the image identifier if the driver is not bound to it. To simplify passenger payment, in an optional implementation of this embodiment, before the passenger pays by scanning the image identifier configured on the transmission component at the end of the trip, the taxi driver on duty needs to scan the 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 fare identifier corresponding to the driver on duty, and an association is established between the fare identifier and the driver's fare account.
[0154] Furthermore, to strengthen driver management, taxi companies use a check-in / clock-out system to determine the driver on duty for the current shift. To ensure that the driver on duty receives the fare from the passenger, in one optional implementation of this embodiment, the transmission component, upon detecting a clock-in command sent by the central control system, marks the fare identification associated with the driver corresponding to the clock-in command as active; and upon detecting the end of the driver's shift, marks the fare identification as frozen.
[0155] For example, a taxi has two drivers participating in a shift change, namely driver D1 and driver D2. Driver D1 and driver D2 each scan two image identifiers configured on the transmission component connected to the taxi's meter. Driver D1 is bound to image identifier 1, that is, image identifier 1 is configured as driver D1's payment identifier, and D2 is bound to image identifier 2, that is, image identifier 2 is configured as driver D2's payment identifier. When driver D1 is detected to have clocked in, the payment identifier configured for driver D1 by image identifier 1 is activated, and the payment identifier configured for driver D2 by image identifier 2 is frozen.
[0156] Step S404: If the trip reporting conditions are met, the trip start information and the trip end information are reported as trip information to the intermediate server, which then provides them to the billing server.
[0157] The trip reporting conditions described in this embodiment refer to preset time points or triggering specified operations.
[0158] Upon detecting that the trip termination information has been received, the trip information is reported to the intermediate server. Alternatively, the trip information is sent by the fare meter to the transmission component after detecting specific information.
[0159] For example, during a ride in a taxi driven by driver D, if the meter has already reported the fare, the trip reporting conditions are met. The taxi's license plate number, driver D's identification, the meter's debit and debit times and positions reported at time t1, the meter's fare lift time and position reported at time t2, and the fare are then reported to the intermediate server as trip information for that ride.
[0160] Reference Figure 2 The data transmission method applied to taxi scenarios specifically includes the following steps:
[0161] Step S202: Obtain the user's travel itinerary start information at the trip start node and the trip termination information at the trip end node.
[0162] The trip start information includes at least one of the following: vehicle identification, driver identification of the driver on duty, trip start time, and trip start location;
[0163] Trip termination information includes at least one of the following: vehicle identification, driver's identification of the driver on duty, fare, trip termination time, and trip termination location.
[0164] Step S204: After obtaining the fare, report the trip information to the intermediate server.
[0165] The itinerary information includes the start and end information of the itinerary.
[0166] The data transmission method provided in this embodiment first obtains the user's travel trip start information and trip end information; then, when the travel reporting conditions are met, the travel start information and trip end information are reported as travel trip information to an intermediate server, which then provides this information to the billing server. This ensures the reliability and validity of the data and improves the integrity of the data during transmission.
[0167] The following is an embodiment of a fare calculation device provided in this manual:
[0168] In the above embodiments, a method for calculating travel expenses is provided, and correspondingly, a device for calculating travel expenses is also provided, which will be described below with reference to the accompanying drawings.
[0169] Reference Figure 5 The diagram shows a fare calculation device provided in this embodiment.
[0170] 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.
[0171] This embodiment provides a fare calculation device, including:
[0172] The acquisition module 502 is configured to acquire travel information of the travel itinerary submitted to the intermediate server by the transmission component;
[0173] The fare query module 504 is configured to query the surcharge for a specific road segment of the trip based on the identity identifier in the trip information and the fare calculation time of the trip.
[0174] The cost calculation module 506 is configured to calculate the additional cost of the road segment and the fare in the trip information to obtain the total fare.
[0175] The order query module 508 is configured to query whether there are any unpaid travel orders based on a query request sent by the payment system; the query request is generated after the transmission component and the user terminal cooperate to scan.
[0176] If so, the query result sending module 510 is run. The query result sending module is configured to send the fare details, which include the total fare of the unpaid trip order, to the payment system.
[0177] Optionally, the fee query module 504 includes:
[0178] The query interface call submodule is configured to call the fee query interface provided by a third-party system and send the identity identifier and pricing time in the trip information to the fee query interface. The third-party system then queries the route surcharge of the transaction record of the identity identifier at the pricing time.
[0179] The road segment additional fee acquisition submodule is configured to acquire the road segment additional fee returned by the third-party system; wherein, the third-party system includes an ETC system, and correspondingly, the specific road segment includes an ETC toll road segment.
[0180] Optionally, the transmission component submits the travel information to the intermediate server by running the following module:
[0181] The information acquisition module is configured to acquire the user's trip start information at the trip start node and trip end information at the trip end node;
[0182] The condition monitoring module is configured to report the trip start information and the trip end information as trip information to the intermediate server when the trip reporting conditions are met, and then the intermediate server provides the trip information to the billing server.
[0183] Optionally, 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 trip information from the meter. The identity identifier includes the vehicle identifier of the taxi and the driver identifier of the driver on duty.
[0184] Optionally, the acquisition module 502 is specifically configured to collect trip start information and / or trip end information when the taxi meter detects the taxi meter debiting action and / or the taxi meter lifting action, and transmit the trip start information and / or the trip end information to the transmission component.
[0185] Optionally, the transmission component is configured with at least one image identifier; the number of image identifiers configured in the transmission component corresponds to the number of drivers on duty participating in the vehicle shift change process; wherein, the image identifier is configured on an image identifier component, and the image identifier component is connected to the transmission component via a card slot or radio frequency identification technology.
[0186] Optionally, when the taxi driver scans the image identifier configured by the transmission component, the image identifier is bound to the driver on duty. After binding, the image identifier is configured as the fare identifier corresponding to the driver on duty, and an association is established between the fare identifier and the driver's fare account.
[0187] Optionally, when the transmission component detects a check-in instruction sent by the central control system, it marks the toll collection identifier bound to the driver corresponding to the check-in instruction as active; when it detects that the driver's shift has ended, it marks the toll collection identifier as frozen.
[0188] Optionally, the fare calculation module further includes:
[0189] The order generation module is configured to generate an unpaid trip order for the ride trip based on the trip information and the additional road segment fees; wherein the trip information includes at least one of the following: pricing information, driver identification, and vehicle identification; the pricing information includes at least one of the following: ride fare, trip start time, trip end time, trip start location, and trip end location; the trip start and end times and the trip end time constitute the pricing time of the ride trip.
[0190] Optionally, the fare calculation module also includes:
[0191] The identity query module is configured to query the identity identifier in a preset identity list;
[0192] The tagging module is configured to determine that the identity identifier is tagged when the identity identifier is found.
[0193] Optionally, the query result sending module 510 includes:
[0194] The details reading submodule is configured to read the total fare and fare details of the unpaid trip order;
[0195] The details sending submodule is configured to send fare details, including the total fare and the fare breakdown, to the payment system.
[0196] This manual provides an example of a fare payment device as follows:
[0197] In the above embodiments, a method for paying fare is provided, and correspondingly, a device for paying fare is also provided, which will be described below with reference to the accompanying drawings.
[0198] Reference Figure 6The diagram shows a fare payment device provided in this embodiment.
[0199] 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.
[0200] This embodiment provides a fare payment device, including:
[0201] The monitoring module 602 is configured to monitor payment requests for ride trips submitted by user terminals after scanning codes in cooperation with the transmission component; the transmission component is connected to the vehicle to which the identity identifier in the payment request belongs;
[0202] The query request sending module 604 is configured to send a query request to the billing server based on the detected payment request;
[0203] The query result receiving module 606 is configured to receive fare details of the total fare of the unpaid trip order carrying the identity identifier, sent by the billing server;
[0204] The payment order loading module 608 is configured to load a payment order containing the details of the fare and send it to the user terminal for display.
[0205] The payment processing module 610 is configured to process the payment order based on the user terminal's confirmation operation of the payment order.
[0206] Optionally, the monitoring module 602 includes:
[0207] The first monitoring submodule is configured to monitor payment requests submitted by the user terminal by scanning the payment identifier configured in the transmission component.
[0208] Optionally, the monitoring module 602 is specifically configured to monitor the payment request submitted by the transmission component after it has collected and parsed the user identifier of the user terminal through the configured image acquisition component.
[0209] Optionally, the fare payment device further includes:
[0210] The status query module is configured to query whether the identity identifier contained in the payment request is in a tagged state;
[0211] If so, the query request generation module is run, which is configured to generate a query request containing the identity identifier.
[0212] Optionally, the vehicle includes a taxi. 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 fare identifier corresponding to the driver and an association is established between the fare identifier and the driver's fare account.
[0213] Optionally, when the transmission component detects a check-in instruction sent by the central control system, it marks the toll collection identifier of the driver on duty corresponding to the check-in instruction as active; when it detects that the driver's shift has ended, it marks the toll collection identifier as frozen. When the toll collection identifier is marked as active, during the payment process, the payment system transfers the resources submitted by the user terminal after scanning the toll collection identifier to the driver's toll collection account based on the association between the toll collection identifier and the driver's toll collection account.
[0214] Optionally, the payment order loading module 608 includes:
[0215] The password-free detection submodule is configured to detect whether the user has signed a password-free payment agreement with the payment system;
[0216] If so, the processing submodule is run, which is configured to transfer the user's resources to the resource space corresponding to the identity identifier according to the total fare.
[0217] If not, the payment order generation submodule is run, which is configured to render a payment order for the user's travel itinerary; write the travel fare details into the payment order and display it to the user.
[0218] The following is an embodiment of a data transmission device provided in this specification:
[0219] In the above embodiments, a data transmission method is provided, and correspondingly, a data transmission device is also provided, which will be described below with reference to the accompanying drawings.
[0220] Reference Figure 7 The diagram shows a data transmission device provided in this embodiment.
[0221] 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.
[0222] This embodiment provides a data transmission device, including:
[0223] The acquisition module 702 is configured to acquire the user's travel itinerary start information at the start node and the travel termination information at the end node.
[0224] The reporting module 704 is configured to report the trip start information and the trip end information as trip information to an intermediate server when the trip reporting conditions are met, and the intermediate server provides this information to the billing server. The transmission component is connected to the vehicle corresponding to the trip information and obtains the trip start information and trip end information through the vehicle.
[0225] Optionally, the acquisition module 702 is specifically configured to acquire the vehicle identifier of the vehicle and the driver identifier of the driver on duty bound to the vehicle; send the vehicle identifier and the driver identifier to the intermediate server; acquire the trip start information of the user's trip at the trip start node and the trip end information at the trip end node; wherein, the trip start information includes at least one of the following: trip start time and trip start location; the trip end information includes at least one of the following: trip end time, trip end location, and fare.
[0226] Optionally, the acquisition module 702 is specifically configured to acquire the user's travel trip start information at the trip start node; wherein the trip start information includes at least one of the following: the vehicle identifier of the vehicle, the driver identifier of the driver on duty bound to the vehicle, the trip start time, and the trip start location; and to acquire the user's travel trip end information at the trip end node; wherein the trip end information includes at least one of the following: the vehicle identifier of the vehicle, the driver identifier of the driver on duty bound to the vehicle, the fare, the trip end time, and the trip end location; correspondingly, the trip reporting conditions include at least one of the following: a preset time point and triggering a specified operation.
[0227] Optionally, 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 trip information from the meter. The identity identifier includes the vehicle identifier of the taxi and the driver identifier of the driver on duty.
[0228] Optionally, the acquisition module 702 is specifically configured to transmit the trip start information and / or trip end information collected by the taxi meter when it detects the taxi meter deduction action and / or the taxi meter lifting action, and transmit the trip start information and / or the trip end information to the transmission component.
[0229] Optionally, the vehicle includes a taxi. 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 fare identifier corresponding to the driver and an association is established between the fare identifier and the driver's fare account.
[0230] Optionally, the transmission component is configured with at least one image identifier; the number of image identifiers configured in the transmission component corresponds to the number of drivers on duty participating in the vehicle shift change process; wherein, the image identifier is configured on an image identifier component, and the image identifier component is connected to the transmission component via a card slot or radio frequency identification technology.
[0231] Optionally, when the transmission component detects a check-in instruction sent by the central control system, it marks the toll collection identifier bound to the driver corresponding to the check-in instruction as active; when it detects that the driver's shift has ended, it marks the toll collection identifier as frozen.
[0232] This manual provides an example of a fare calculation device as follows:
[0233] Corresponding to the fare calculation method described above, based on the same technical concept, one or more embodiments of this specification also provide a fare calculation device, which is used to execute the fare calculation method described above. Figure 8 This is a schematic diagram of a fare calculation device provided for one or more embodiments of this specification.
[0234] like Figure 8 As shown, fare calculation devices can vary significantly due to differences in configuration or performance. They may include one or more processors 801 and a memory 802, where one or more application programs or data can be stored. The memory 802 can be temporary or persistent storage. The application programs stored in the memory 802 may include one or more modules (not shown), each module including a series of computer-executable instructions for the fare calculation device. Furthermore, the processor 801 may be configured to communicate with the memory 802, executing the series of computer-executable instructions in the memory 802 on the fare calculation device. The fare calculation device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input / output interfaces 805, one or more keyboards 806, etc.
[0235] In one specific embodiment, the fare calculation 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 fare calculation and detection 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:
[0236] Obtain the travel itinerary information submitted by the transmission component to the intermediate server;
[0237] Based on the identity identifier in the trip information and the fare calculation time of the trip, query the additional fare for the trip on a specific road segment;
[0238] The surcharge for the aforementioned road segment and the fare in the trip information are calculated to obtain the total fare.
[0239] The system checks for unpaid travel orders based on a query request sent by the payment system; the query request is generated after the transmission component and the user terminal cooperate to scan.
[0240] If so, send the fare details, including the total fare for the unpaid trip order, to the payment system.
[0241] Optionally, 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 trip information from the meter. The identity identifier includes the vehicle identifier of the taxi and the driver identifier of the driver on duty.
[0242] Optionally, the transmission component is configured with at least one image identifier; the number of image identifiers configured in the transmission component corresponds to the number of drivers on duty participating in the vehicle shift change process; wherein, the image identifier is configured on an image identifier component, and the image identifier component is connected to the transmission component via a card slot or radio frequency identification technology.
[0243] Optionally, when the taxi driver scans the image identifier configured by the transmission component, the image identifier is bound to the driver on duty. After binding, the image identifier is configured as the fare identifier corresponding to the driver on duty, and an association is established between the fare identifier and the driver's fare account.
[0244] Optionally, when the transmission component detects a check-in instruction sent by the central control system, it marks the toll collection identifier bound to the driver corresponding to the check-in instruction as active; when it detects that the driver's shift has ended, it marks the toll collection identifier as frozen.
[0245] This manual provides an example of a fare payment device as follows:
[0246] Corresponding to the fare payment method described above, based on the same technical concept, one or more embodiments of this specification also provide a fare payment device for executing the aforementioned fare payment method. Figure 9 This is a schematic diagram of a fare payment device provided for one or more embodiments of this specification.
[0247] like Figure 9 As shown, fare payment devices can vary significantly due to differences in configuration or performance. They may include one or more processors 901 and a memory 902, where one or more application programs or data can be stored. The memory 902 can be temporary or persistent storage. The application programs stored in the memory 902 may include one or more modules (not shown), each module including a series of computer-executable instructions for the fare payment device. Furthermore, the processor 901 may be configured to communicate with the memory 902, executing the series of computer-executable instructions stored in the memory 902 on the fare payment device. The fare payment device may also include one or more power supplies 903, one or more wired or wireless network interfaces 904, one or more input / output interfaces 905, one or more keyboards 906, etc.
[0248] In one specific embodiment, the fare payment 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 fare payment 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:
[0249] The system monitors payment requests for rides submitted after the user terminal scans a code in conjunction with the transmission component; the transmission component is connected to the vehicle to which the identity identifier in the payment request belongs.
[0250] Based on the detected payment requests, a query request is sent to the billing server;
[0251] Receive fare details from the billing server, which include the total fare for the unpaid trip order carrying the identity identifier;
[0252] Load the payment order containing the fare details and send it to the user terminal for display;
[0253] Based on the user terminal's confirmation of the payment order, the payment order is processed.
[0254] Optionally, the vehicle includes a taxi. 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 fare identifier corresponding to the driver and an association is established between the fare identifier and the driver's fare account.
[0255] Optionally, when the transmission component detects a check-in instruction sent by the central control system, it marks the toll collection identifier of the driver on duty corresponding to the check-in instruction as active; when it detects that the driver's shift has ended, it marks the toll collection identifier as frozen.
[0256] When the toll identifier is marked as active, during the payment process, the payment system transfers the resources submitted by the user terminal after scanning the toll identifier to the toll account of the driver on duty, based on the association between the toll identifier and the toll account of the driver on duty.
[0257] The following is an embodiment of a data transmission device provided in this specification:
[0258] Corresponding to the data transmission method described above, based on the same technical concept, one or more embodiments of this specification also provide a data transmission device for performing the aforementioned data transmission method. Figure 10 This is a schematic diagram of the structure of a data transmission device provided for one or more embodiments of this specification.
[0259] like Figure 10As shown, data transmission devices can vary considerably due to differences in configuration or performance. They may include one or more processors 1001 and memory 1002, with memory 1002 storing one or more application programs or data. Memory 1002 can be temporary or persistent storage. The application programs stored in memory 1002 may include one or more modules (not shown), each module including a series of computer-executable instructions from a fare payment device. Furthermore, processor 1001 may be configured to communicate with memory 1002, executing the series of computer-executable instructions in memory 1002 on the data transmission device. The data transmission device may also include one or more power supplies 1003, one or more wired or wireless network interfaces 1004, one or more input / output interfaces 1005, one or more keyboards 1006, etc.
[0260] In one specific embodiment, the data transmission 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 data transmission 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:
[0261] Obtain the user's travel itinerary information at the start node and the end node.
[0262] If the trip reporting conditions are met, the trip start information and the trip end information are reported as trip information to the intermediate server, which then provides them to the billing server.
[0263] The transmission component is connected to the vehicle corresponding to the trip information, and obtains the trip start information and trip end information through the vehicle.
[0264] Optionally, 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 trip information from the meter. The identity identifier includes the vehicle identifier of the taxi and the driver identifier of the driver on duty.
[0265] Optionally, the vehicle includes a taxi. 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 fare identifier corresponding to the driver and an association is established between the fare identifier and the driver's fare account.
[0266] Optionally, the transmission component is configured with at least one image identifier; the number of image identifiers configured in the transmission component corresponds to the number of drivers on duty participating in the vehicle shift change process.
[0267] The image identifier is configured on the image identifier component, and the image identifier component is connected to the transmission component via a card slot or radio frequency identification technology.
[0268] Optionally, when the transmission component detects a check-in instruction sent by the central control system, it marks the toll collection identifier bound to the driver corresponding to the check-in instruction as active; when it detects that the driver's shift has ended, it marks the toll collection identifier as frozen.
[0269] This specification provides an example of a storage medium as follows:
[0270] Corresponding to the above-described method for calculating travel expenses, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.
[0271] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process:
[0272] Obtain the travel itinerary information submitted by the transmission component to the intermediate server;
[0273] Based on the identity identifier in the trip information and the fare calculation time of the trip, query the additional fare for the trip on a specific road segment;
[0274] The surcharge for the aforementioned road segment and the fare in the trip information are calculated to obtain the total fare.
[0275] The system checks for unpaid travel orders based on a query request sent by the payment system; the query request is generated after the transmission component and the user terminal scan together.
[0276] If so, send the fare details, including the total fare for the unpaid trip order, to the payment system.
[0277] Optionally, 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 trip information from the meter. The identity identifier includes the vehicle identifier of the taxi and the driver identifier of the driver on duty.
[0278] Optionally, the transmission component is configured with at least one image identifier; the number of image identifiers configured in the transmission component corresponds to the number of drivers on duty participating in the vehicle shift change process; wherein, the image identifier is configured on an image identifier component, and the image identifier component is connected to the transmission component via a card slot or radio frequency identification technology.
[0279] Optionally, when the taxi driver scans the image identifier configured by the transmission component, the image identifier is bound to the driver on duty. After binding, the image identifier is configured as the fare identifier corresponding to the driver on duty, and an association is established between the fare identifier and the driver's fare account.
[0280] Optionally, when the transmission component detects a check-in instruction sent by the central control system, it marks the toll collection identifier bound to the driver corresponding to the check-in instruction as active; when it detects that the driver's shift has ended, it marks the toll collection identifier as frozen.
[0281] The second storage medium embodiment provided in this specification is as follows:
[0282] Corresponding to the above-described method for paying fare, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.
[0283] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process:
[0284] The system monitors payment requests for rides submitted after the user terminal scans a code in conjunction with the transmission component; the transmission component is connected to the vehicle to which the identity identifier in the payment request belongs.
[0285] Based on the detected payment requests, a query request is sent to the billing server;
[0286] Receive fare details from the billing server, which include the total fare for the unpaid trip order carrying the identity identifier;
[0287] Load the payment order containing the fare details and send it to the user terminal for display;
[0288] Based on the user terminal's confirmation of the payment order, the payment order is processed.
[0289] Optionally, the vehicle includes a taxi. 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 fare identifier corresponding to the driver and an association is established between the fare identifier and the driver's fare account.
[0290] Optionally, when the transmission component detects a check-in instruction sent by the central control system, it marks the toll collection identifier of the driver on duty corresponding to the check-in instruction as active; when it detects that the driver's shift has ended, it marks the toll collection identifier as frozen.
[0291] When the toll identifier is marked as active, during the payment process, the payment system transfers the resources submitted by the user terminal after scanning the toll identifier to the toll account of the driver on duty, based on the association between the toll identifier and the toll account of the driver on duty.
[0292] The third storage medium embodiment provided in this specification is as follows:
[0293] Corresponding to the data transmission method described above, and based on the same technical concept, one or more embodiments of this specification also provide a storage medium.
[0294] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process:
[0295] Obtain the user's travel itinerary information at the start node and the end node.
[0296] If the trip reporting conditions are met, the trip start information and the trip end information are reported as trip information to the intermediate server, which then provides them to the billing server.
[0297] The transmission component is connected to the vehicle corresponding to the trip information, and obtains the trip start information and trip end information through the vehicle.
[0298] Optionally, 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 trip information from the meter. The identity identifier includes the vehicle identifier of the taxi and the driver identifier of the driver on duty.
[0299] Optionally, the vehicle includes a taxi. 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 fare identifier corresponding to the driver and an association is established between the fare identifier and the driver's fare account.
[0300] Optionally, the transmission component is configured with at least one image identifier; the number of image identifiers configured in the transmission component corresponds to the number of drivers on duty participating in the vehicle shift change process.
[0301] The image identifier is configured on the image identifier component, and the image identifier component is connected to the transmission component via a card slot or radio frequency identification technology.
[0302] Optionally, when the transmission component detects a check-in instruction sent by the central control system, it marks the toll collection identifier bound to the driver corresponding to the check-in instruction as active; when it detects that the driver's shift has ended, it marks the toll collection identifier as frozen.
[0303] 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.
[0304] 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.
[0305] 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.
[0306] 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.
[0307] 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.
[0308] 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.
[0309] 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.
[0310] 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.
[0311] 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.
[0312] 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.
[0313] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0314] 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.
[0315] 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.
[0316] 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.
[0317] 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.
[0318] 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.
[0319] 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 calculating fare, applied to a billing server, comprising: Obtain trip information from the intermediate server, including fare calculation time, fare, and driver identification. The trip information is obtained from the meter by a transmission component installed in the taxi and uploaded to the intermediate server; The transmission component is used to connect the fare meter and the ETC system; the taxi driver on duty scans the image identifier configured on the transmission component and binds it to the image identifier; The transmission component scans the user identifier of the user terminal or the user terminal scans the image identifier and then sends a payment request to the payment system. Based on the identity identifier and the billing time, the query interface of the ETC system is called to query the road segment surcharge of the ride in the ETC system and integrate it with the ride fare to obtain the total ride fare; The system queries the corresponding unpaid trip order based on the identity identifier in the query request sent by the payment system and sends the trip fare details, including the total fare of the queried unpaid trip order, to the payment system. The payment system generates the query request after receiving the payment request.
2. According to the fare calculation method of claim 1, the transmission component submits the trip information to the intermediate server in the following manner: Obtain the user's trip start information at the trip start node and the trip end information at the trip end node; If the trip reporting conditions are met, the trip start information and the trip end information are reported as trip information to the intermediate server, which then provides them to the billing server.
3. The fare calculation method according to claim 1, wherein the transmission component is connected to the taxi meter via a ribbon cable; the identification includes the vehicle identification of the taxi and the driver identification of the driver on duty.
4. In the fare calculation method according to claim 3, when the meter detects the taxi meter deducting and / or the taxi meter raising, the meter collects trip start information and / or trip end information, and transmits the trip start information and / or the trip end information to the transmission component.
5. The fare calculation method according to claim 1, wherein the transmission component is configured with at least one image identifier; the number of image identifiers configured in the transmission component corresponds to the number of drivers on duty participating in the vehicle shift change process; in, The image identifier is configured on the image identifier component, which is connected to the transmission component via a card slot or radio frequency identification technology.
6. In the fare calculation method according to claim 1, after binding the image identifier with the driver on duty, the image identifier is configured as the fare identifier corresponding to the driver on duty, and an association relationship is established between the fare identifier and the fare account of the driver on duty.
7. In the fare calculation method according to claim 6, when the transmission component detects a check-in instruction sent by the central control system of the taxi, it marks the fare identifier bound to the driver corresponding to the check-in instruction as active; when it detects that the driver's shift has ended, it marks the fare identifier as frozen.
8. The method for calculating travel expenses according to claim 1, after the step of integrating the additional road segment fee with the travel expenses in the trip information to obtain the total travel expense, further includes: Based on the trip information and the additional charges for the route, an unpaid trip order is generated for the travel trip; The trip information includes at least one of the following: fare information, driver identification, and vehicle identification; the fare information includes at least one of the following: fare, trip start time, trip end time, trip start location, and trip end location; the trip start time and the trip end time constitute the fare calculation time for the trip.
9. The method for calculating travel expenses according to claim 1, after the step of calling the query interface of the ETC system based on the identity identifier and the pricing time to query the road segment surcharge of the travel trip in the ETC system and integrating it with the travel fare to obtain the total travel fare, further includes: Search for the identity identifier in the preset identity list; If the identity identifier is found, it is determined that the identity identifier is in a tagged state.
10. The fare calculation method according to claim 1, wherein sending fare details to the payment system carrying the total fare of the queried unpaid trip order includes: Read the total fare and fare details of the unpaid trip order; Send the fare details, including the total fare and the fare breakdown, to the payment system.
11. A method for paying fare, applied in a payment system, comprising: The system monitors the payment requests for the ride submitted by the user terminal after scanning a QR code using the transmission component connected to the meter. The transmission component is installed in the taxi to which the identity identifier in the payment request belongs, and is used to connect the fare meter and the ETC system; the taxi driver on duty scans the image identifier configured in the transmission component and binds it to the image identifier; The transmission component scans the user identifier of the user terminal or the user terminal scans the image identifier and then sends the payment request to the payment system. Based on the payment request, a query request containing the identity identifier is sent to the billing server; Receive fare details from the billing server, which include the total fare for the unpaid trip order carrying the identity identifier; The total fare is obtained by integrating the fare in the trip information uploaded by the transmission component, the fare in the ETC system based on the identity identifier and the billing time of the trip, and querying the road segment surcharge of the trip in the ETC system through the query interface of the ETC system. Load the payment order containing the fare details and send it to the user terminal for display; Based on the user terminal's confirmation of the payment order, the payment order is processed.
12. A data transmission method, applied to a transmission component, comprising: Obtain the user's travel itinerary information at the start node and the end node. If the trip reporting conditions are met, the trip start information and trip end information are reported as trip information to the intermediate server, which then provides them to the billing server. The billing server, based on the driver's identity and the billing time of the trip in the trip information, calls the query interface of the ETC system to query the road segment surcharge of the trip in the ETC system, and integrates it with the trip fare in the trip information to obtain the total trip fare. The transmission component is installed in the taxi corresponding to the trip information to connect the fare meter and the ETC system. The taxi driver scans the image identifier configured on the transmission component and binds it to the image identifier. The transmission component scans the user identifier of the user terminal or the user terminal scans the image identifier and then sends a payment request to the payment system.
13. A fare calculation device, comprising: The acquisition module is configured to acquire trip information provided by an intermediate server, including the fare calculation time, fare, and driver's identification. The trip information is obtained from the meter by a transmission component installed in the taxi and uploaded to the intermediate server; The transmission component is used to connect the fare meter and the ETC system; the taxi driver on duty scans the image identifier configured on the transmission component and binds it to the image identifier; The transmission component scans the user identifier of the user terminal or the user terminal scans the image identifier and then sends a payment request to the payment system. The fee query module is configured to call the query interface of the ETC system based on the identity identifier and the billing time to query the road segment surcharge of the ride in the ETC system and integrate it with the ride fare in the trip information to obtain the total ride fare; The order query module is configured to query the corresponding unpaid trip order based on the identity identifier in the query request sent by the payment system, and send the fare details carrying the total fare of the queried unpaid trip order to the payment system; The payment system generates the query request after receiving the payment request.
14. A fare payment device, comprising: The monitoring module is configured to monitor the payment requests for the ride submitted by the user terminal after scanning the code through the transmission component connected to the fare meter. The transmission component is installed in the taxi to which the identity identifier in the payment request belongs, and is used to connect the fare meter and the ETC system; the taxi driver on duty scans the image identifier configured in the transmission component and binds it to the image identifier; The transmission component scans the user identifier of the user terminal or the user terminal scans the image identifier and then sends the payment request to the payment system. The query request sending module is configured to send a query request containing the identity identifier to the billing server based on the payment request; The query result receiving module is configured to receive fare details of the total fare for unpaid trip orders carrying the identity identifier, sent by the billing server; The total fare is obtained by integrating the fare in the trip information uploaded by the transmission component and the additional road surcharge of the trip obtained by querying the ETC system through the query interface based on the identity and the billing time of the trip. The payment order loading module is configured to load a payment order containing the details of the fare and send it to the user terminal for display. The payment processing module is configured to process the payment order based on the user terminal's confirmation operation of the payment order.
15. A data transmission apparatus, operating on a transmission component, comprising: The acquisition module is configured to acquire the user's travel itinerary information at the start node and the end node. The reporting module is configured to report the trip start information and trip end information as trip information to the intermediate server when the trip reporting conditions are met. The intermediate server then provides this information to the billing server. The billing server uses the driver's identity identifier in the trip information and the billing time of the trip to query the ETC system's query interface to find the road segment surcharge for the trip in the ETC system. The query results are then combined with the trip fare in the trip information to obtain the total trip fare. The transmission component is installed in the taxi corresponding to the trip information to connect the fare meter and the ETC system. The taxi driver scans the image identifier configured on the transmission component and binds it to the image identifier. The transmission component scans the user identifier of the user terminal or the user terminal scans the image identifier and then sends a payment request to the payment system.
16. A fare calculation device, comprising: processor; as well as, A memory configured to store computer-executable instructions, which, when executed, cause the processor to perform the fare calculation method as described in any one of claims 1 to 10.
17. A fare payment device, comprising: processor; as well as, A memory configured to store computer-executable instructions, which, when executed, cause the processor to perform the fare payment method as described in claim 11.
18. A data transmission device, comprising: processor; as well as, A memory configured to store computer-executable instructions, which, when executed, cause the processor to perform the data transfer method as described in claim 12.
19. A storage medium for storing computer-executable instructions, which, when executed, implement the fare calculation method as described in any one of claims 1 to 10.
20. A storage medium for storing computer-executable instructions, which, when executed, implement the fare payment method as described in claim 11.
21. A storage medium for storing computer-executable instructions, which, when executed, implement the data transmission method of claim 12.
Citation Information
Patent Citations
System and method for obtaining mobile payment information
CN103824181A
Taxi payment system and method
CN107464294A
Travel bill information generating method and device
CN108510295A
Electronic charging method and system based on intelligent networked vehicle and vehicle networking service platform
CN110379025A
