CN112016980A

CN112016980A - Method and device for issuing travel invoice, server and storage medium

Info

Publication number: CN112016980A
Application number: CN201910465484.XA
Authority: CN
Inventors: 谭名钧; 卓越强; 辛建华; 赵浩辰; 盛理; 冯明鹏; 张颖; 喻佼焱; 王跃; 肖洁欣; 梁伟强; 王萌; 张瑞; 李伟宗; 刘春燕; 徐长胜; 张磊; 张雅楠; 彭君航; 梁轲
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-05-30
Filing date: 2019-05-30
Publication date: 2020-12-01

Abstract

The application relates to a method, a device, a server and a storage medium for issuing a travel invoice, wherein the method comprises the following steps: receiving an invoicing request sent by a user terminal; the billing request comprises a vehicle identifier corresponding to a vehicle driver and payment time corresponding to the payment certificate; acquiring a target travel according to the vehicle identification and the payment time, wherein the target travel is a travel corresponding to the payment certificate; and issuing a travel invoice corresponding to the target travel. The scheme provided by the embodiment of the application can enable the terminal to directly apply for issuing the travel invoice after one payment operation is finished, and the process of specifically searching the target travel is automatically finished by the server. Therefore, the method and the device can reduce the operation of the user and improve the efficiency of issuing the travel invoice.

Description

Method and device for issuing travel invoice, server and storage medium

Technical Field

The embodiment of the application relates to the technical field of electronic invoices, in particular to a method, a device, a server and a storage medium for issuing a travel invoice.

Background

In modern socioeconomic activities, invoices are legally valid vouchers used to document transactions.

In the related art, in some scenarios of issuing a travel invoice for a taxi, after a user pays a fee, if the user needs to issue the travel invoice, the user is required to scan a travel two-dimensional code provided on a vehicle-mounted terminal of the taxi, and then the user terminal sends a billing application containing travel information to a server, so as to obtain the travel invoice.

However, the process of issuing a travel invoice shown in the related art is cumbersome to operate, resulting in inefficient issuing of a travel invoice.

Disclosure of Invention

The embodiment of the application provides a method, a device, a server and a storage medium for issuing a travel invoice, which can solve the problem that the operation of the issuing process of the travel invoice in the related technology is complicated, and the technical scheme is as follows:

in one aspect, a method for issuing a trip invoice is provided, the method being performed by a server, and the method including:

receiving an invoicing request sent by a user terminal; the billing request is a request sent by the user terminal when the user terminal displays a payment certificate after successfully paying to a second account through a first account and receives a trigger operation of the payment certificate, wherein the second account is a fund account of a vehicle driver; the billing request comprises a vehicle identifier corresponding to the vehicle driver and payment time corresponding to the payment certificate;

acquiring a target travel according to the vehicle identification and the payment time, wherein the target travel is a travel corresponding to the payment certificate;

and issuing a travel invoice corresponding to the target travel.

In yet another aspect, there is provided a method of invoicing a trip, the method being performed by a user terminal, the method comprising:

after the payment to the second account through the first account is successful, displaying the payment certificate; the second account is a vehicle driver's funds account;

generating an invoicing request when the triggering operation of the payment voucher is received; the billing request comprises a vehicle identifier corresponding to the vehicle driver and payment time corresponding to the payment certificate;

sending the billing request to a server, wherein the billing request is used for indicating the server to obtain a target trip according to the vehicle identification and the payment time, and billing a trip invoice corresponding to the target trip; the target itinerary is an itinerary to which the payment credential corresponds.

after the payment to the second account through the first account is successful, a payment certificate containing an invoicing reminding control is displayed in the first application interface; the second account is a vehicle driver's funding account, the first application interface is a parent application's application interface;

when the triggering operation of the invoicing reminding control is received, a second application interface is displayed, wherein the second application interface is an application interface of a sub-application program, and the sub-application program runs depending on the parent application program;

and displaying a travel invoice reminder after receiving the triggering operation of the invoicing application control in the second application interface, wherein the travel invoice reminder is used for reminding a server of issuing a travel invoice of a target travel corresponding to the payment certificate.

In yet another aspect, there is provided a device for issuing a trip invoice, the device including:

the billing request receiving module is used for receiving a billing request sent by a user terminal; the billing request is a request sent by the user terminal when the user terminal displays a payment certificate after successfully paying to a second account through a first account and receives a trigger operation of the payment certificate, wherein the second account is a fund account of a vehicle driver; the billing request comprises a vehicle identifier corresponding to the vehicle driver and payment time corresponding to the payment certificate;

the travel acquisition module is used for acquiring a target travel according to the vehicle identifier and the payment time, wherein the target travel is a travel corresponding to the payment certificate;

and the invoice issuing module is used for issuing an invoice corresponding to the target trip.

the first certificate display module is used for displaying the payment certificate after the payment to the second account through the first account is successful; the second account is a vehicle driver's funds account;

the billing request generation module is used for generating a billing request when receiving the triggering operation of the payment certificate; the billing request comprises a vehicle identifier corresponding to the vehicle driver and payment time corresponding to the payment certificate;

the billing request sending module is used for sending the billing request to a server, wherein the billing request is used for indicating the server to obtain a target trip according to the vehicle identifier and the payment time and issuing a trip invoice corresponding to the target trip; the target itinerary is an itinerary to which the payment credential corresponds.

the second certificate display module is used for displaying the payment certificate containing the invoicing reminding control in the first application interface after the payment to the second account through the first account is successful; the second account is a vehicle driver's funding account, the first application interface is a parent application's application interface;

the interface display module is used for displaying a second application interface when receiving the triggering operation of the invoicing reminding control, wherein the second application interface is an application interface of a sub-application program, and the sub-application program runs depending on the parent application program;

and the reminding display module is used for displaying the travel invoice reminding after receiving the triggering operation of the invoicing application control in the second application interface, and the travel invoice reminding is used for reminding the server to issue the travel invoice of the target travel corresponding to the payment certificate.

In yet another aspect, a computer-readable storage medium is provided, in which at least one instruction, at least one program, a set of codes, or a set of instructions is stored, and the at least one instruction, the at least one program, the set of codes, or the set of instructions is loaded and executed by a processor to implement the method for invoicing a trip provided by the embodiments of the present application.

The technical scheme provided by the application can comprise the following beneficial effects:

according to the method for issuing the travel invoice, the server can determine the target travel according to the vehicle identification and the payment time after the user terminal successfully pays, and the travel invoice corresponding to the target travel is issued. The scheme provided by the embodiment of the application can enable the terminal to directly apply for issuing the travel invoice after one payment operation is finished, and the process of specifically searching the target travel is automatically finished by the server. Therefore, the method and the device can reduce the operation of the user, improve the efficiency of issuing the travel invoice, and reduce the time of the vehicle staying in the road due to the waiting of the invoice, thereby reducing the urban congestion and improving the safety of the operating vehicle.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.

FIG. 1 is a block diagram illustrating a system for invoicing trips according to an exemplary embodiment;

fig. 2 is a schematic view of a scenario involved in a method for issuing a trip invoice according to an embodiment of the present application;

FIG. 3 is a flow chart of a method for invoicing itineraries provided by an embodiment of the present application;

FIG. 4 illustrates a method flow diagram of a method for invoicing a trip provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of a pay code presentation page provided in accordance with the embodiment shown in FIG. 4;

FIG. 6 is a schematic illustration of a payment page provided based on the embodiment shown in FIG. 4;

FIG. 7 is a schematic diagram of a payment credential provided based on the embodiment shown in FIG. 4;

FIG. 8 is a schematic diagram of page jump provided based on the embodiment shown in FIG. 4;

FIG. 9 is a schematic diagram of a second application interface provided according to the embodiment shown in FIG. 4;

FIG. 10 is a drawing illustration of a billing process progress viewing interface provided in accordance with the embodiment shown in FIG. 4;

FIG. 11 is a schematic illustration of a new incoming invoice notification provided in accordance with the embodiment shown in FIG. 4;

FIG. 12 is a schematic illustration of invoice details provided based on the embodiment shown in FIG. 4;

FIG. 13 is a flow chart of a method of invoice issuing for a trip provided in accordance with an embodiment of the present application;

FIG. 14 is a flow chart illustrating a method for invoicing a trip provided by an embodiment of the present application;

FIG. 15 is a block diagram illustrating the structure of an apparatus for invoicing itineraries, according to an exemplary embodiment;

FIG. 16 is a block diagram illustrating the structure of an apparatus for invoicing itineraries, according to an exemplary embodiment;

FIG. 17 is a block diagram illustrating the structure of an apparatus for invoicing itineraries, according to an exemplary embodiment;

FIG. 18 is a schematic diagram illustrating the structure of a server in accordance with an exemplary embodiment;

fig. 19 shows a block diagram of a user terminal 1900 according to an exemplary embodiment of the present application.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

As a possible implementation manner, when the user terminal executes the method for issuing the trip invoice described in the present application, the user terminal can implement the function through a preset application. Optionally, the preset application is provided with a payment function. In another possible implementation manner, the user terminal may also implement the method for issuing the travel invoice described in this application through an applet or a fast application in a preset application, which is not limited in this application.

Referring to fig. 1, fig. 1 is a block diagram illustrating a system for invoicing itineraries according to an exemplary embodiment. As shown in fig. 1, the system for invoicing a trip may include a user terminal 110 and a server 120. Alternatively, the server 120 may include an electronic invoice server, a vehicle trip server, a payment server, and a card server. Optionally, the system for issuing the trip invoice can further comprise a blockchain invoice server and a vehicle-mounted terminal.

The user terminal 110 may be a mobile terminal used by a user, which is capable of data exchange with an electronic invoice server through a wireless network. Optionally, the mobile terminal can also exchange data with the card and ticket server through a wireless network. In one possible implementation, the user terminal 110 may be an electronic device such as a mobile phone, a wearable smart device, or a tablet computer.

The electronic invoice server is a cloud device. The electronic invoice server may be one server or a server cluster formed by a plurality of servers. When the electronic invoice server is one server, other software systems may also be loaded in the server, which is not limited in the embodiment of the present application. For example, in one possible implementation, the electronic invoice server may host both the electronic invoice system and the payment system.

The vehicle journey server is a cloud device. The server is used for receiving operation data uploaded by a vehicle-mounted terminal on an operation vehicle, wherein the operation data is used for indicating the detailed condition of each order, basic information of the vehicle and basic information of a driver. In one possible scenario, the vehicle trip server is a system managed by a public transportation government department for collecting and processing objective data for operating vehicles.

The in-vehicle terminal is an electronic device mounted on an operating vehicle, and the device has a function of a meter. The vehicle-mounted terminal can start recording the driving distance and the waiting time when the charging button is triggered. Meanwhile, the vehicle-mounted terminal can confirm the end of the travel when the charging button is triggered again, calculate the operation amount according to the accumulated running distance and the accumulated waiting time and display the operation amount in a display screen of the vehicle-mounted terminal. Optionally, the vehicle-mounted terminal is further provided with a printing function of a paper invoice. That is, the in-vehicle terminal can print the paper invoice that the operation amount of money corresponds.

The payment server is used for receiving a payment request sent by the user terminal 110. The payment server can transfer funds for the payment amount in the user account logged in the user terminal 110 to the driver account. It should be noted that, the driver can post the payment graphic code printed in advance on a paper plate in the operating vehicle. When the user terminal 110 scans the payment graphic code, the user terminal 110 will send a payment request to the payment server. Optionally, the payment graphic code may also be displayed on a display screen of the vehicle-mounted terminal, and a specific display position of the payment graphic code is not limited in the embodiment of the present application.

And the block chain invoice server is used for receiving a block chain invoice generation request sent by the electronic invoice server and generating a tamper-proof trustable travel invoice by a block chain technology. And the block chain invoice server sends the trip invoice to the electronic invoice server after issuing the trip invoice according to the invoice head-up information and the payment amount provided by the electronic invoice server.

Optionally, the system provided by the present application further includes a card server. The electronic invoice server can transmit the travel invoice to the card and ticket server after the travel invoice is issued, be managed by the card and ticket server, and transmit the travel invoice to the user terminal 110.

Referring to fig. 2, fig. 2 is a schematic view of a scenario involved in a method for issuing a trip invoice according to an embodiment of the present application. In fig. 2, when the user 210 arrives at the destination by taking a taxi, the user terminal 211 scans the driver's receipt graphic code posted in the taxi and pays 61 yuan for the taxi, and then gets off the vehicle. The payment server 220 receives the payment request sent by the user terminal 211, transfers the 61 yuan of riding fee from the user account logged in the user terminal 211 to the driver account corresponding to the driver's collection graphic code, and sends the information of the transaction, including the account number of the payer, the account number of the receiver, the payment time and the payment amount, to the electronic invoice server.

The electronic invoice server 230 queries data backed up in advance from the vehicle journey server according to the account number of the payee in the transaction, and obtains the driver identifier and the license plate number corresponding to the driver identifier. It should be noted that the driver identifier includes, but is not limited to, at least one of an identification number, a driving license number, a professional qualification number, or an identification number. The license plate number corresponding to the driver identifier indicates the license plate number currently driven by the driver identifier. Optionally, when the driver starts driving the taxi, the driver identifier and the license plate number of the driver are bound in the vehicle journey server in a check-in mode. The electronic invoice server 230 can synchronize the bound information.

The electronic invoice server 230 can also obtain the travel information within a specified time before the payment time according to the license plate number. For example, the electronic invoice server 230 obtains travel information within 3 minutes before the payment time. In one possible manner, when the trip information within 3 minutes is 1, the electronic invoice server 230 confirms the trip corresponding to the trip information as the target trip. When the difference between the operation amount of the target trip, that is, the amount displayed by the in-vehicle terminal, and the payment amount paid by the user 210 belongs to the preset amount interval, the electronic invoice server 230 issues an electronic invoice corresponding to the payment amount according to the invoice top-up information provided by the user 210.

It should be noted that the preset money interval is an interval preset by a technician according to the passing fee of the area where the taxi is located. For example, in the city S, the highest passing fee is set to 30 yuan, and the upper limit of the toll wiping zero of the driver is set to 4 yuan, the preset amount interval is [4, -30 ]. Accordingly, when the amount displayed by the in-vehicle terminal is different from the payment amount paid by the user 210 and does not belong to the preset amount interval, the electronic invoice server 230 returns an error message to the user terminal 210. For example, "invoice fails, if there is a problem, please contact human customer service".

In another possible implementation scenario, in the invoice issuing scenario of fig. 2, the payment time and the payment amount are used as variables to introduce whether the invoice issuing of the itinerary is performed. Please refer to table one, wherein the trip ending time and the payment time are both a time within 5 and 29 months in 2018, and the specific time values refer to the numerical values in the table.

Watch 1

It should be noted that the first table shows a scenario in which 4 groups of users pay the riding fee. The end-of-trip times shown in table one are 10 hours, 32 minutes, and 3 seconds, and the running amount is 43 dollars. In the data shown in sequence number 1, the actual payment amount of the user is 40 yuan, the difference between the operation amount and the payment amount is 3, 3 belongs to the preset amount interval of [4, -30], and the end-of-travel time is in the period within the first 3 minutes of the payment time. Therefore, the data shown in the serial number 1 meet the invoice issuing conditions of the itinerary invoice, and the electronic invoice system will issue the itinerary invoice.

In the data shown in the serial number 2, the actual payment amount of the user is 43 yuan, and in the period within the first 3 minutes of the payment time acquired by the electronic invoice system, there is no travel. Therefore, the data shown in the serial number 2 does not meet the invoice issuing condition, and the electronic invoice system does not issue the invoice.

In the data shown in sequence number 3, the actual payment amount of the user is 61 yuan, the difference between the operation amount and the payment amount is-18, the preset amount interval is [ 4-30 ], and the end-of-travel time is in the period within the first 3 minutes of the payment time. Therefore, the data shown in the serial number 3 is in accordance with the invoice issuing condition of the itinerary invoice, and the electronic invoice system will issue the itinerary invoice.

In the data shown in the serial number 4, the actual payment amount of the user is 80 dollars, and the difference between the operation amount and the payment amount is-37 dollars. Since-37 does not belong to the preset monetary interval [4, -30 ]. Therefore, the data indicated by the serial number 4 does not meet the invoice issuing condition, and the electronic invoice system does not issue the invoice.

It should be noted that one possible scenario of the data with serial number 1 is to operate the taxi driver to reduce the overhead fee of the passenger. One possible scenario for the serial number 4 data is that the user pays a small fee to the driver, or the driver receives money transferred by another payer. Aiming at the data with the serial number of 4, the user terminal can display error information and provide a complaint interface so that the user can complain to customer service personnel and obtain a travel invoice which should be issued.

Alternatively, in the above scenario, the trip end time may be a time when a charging button is triggered in the in-vehicle terminal in the charging state. Alternatively, the trip end time may be a time at which the in-vehicle terminal stops billing. Alternatively, the operation amount is a fee amount displayed in the in-vehicle terminal.

Referring to fig. 3, fig. 3 is a flowchart of a method for issuing a trip invoice according to an embodiment of the present application. In the method shown in fig. 3, the server and the user terminal cooperate to complete a process of a method for issuing a trip invoice, where the method includes:

in step 310, after the payment to the second account through the first account is successful, the user terminal displays the payment certificate.

Wherein the second account is a vehicle driver's funds account.

And 320, generating an invoicing request by the user terminal when the triggering operation of the payment certificate is received.

The billing request comprises a vehicle identification corresponding to a vehicle driver and payment time corresponding to the payment certificate.

In step 330, the user terminal sends an invoicing request to the server.

The billing request is used for indicating the server to obtain a target travel according to the vehicle identification and the payment time, and billing a travel invoice corresponding to the target travel; the target itinerary is an itinerary to which the payment voucher corresponds.

Correspondingly, the server receives the invoicing request sent by the user terminal.

The billing request is a request sent when the user terminal displays a payment certificate after successfully paying to a second account through a first account and receives a trigger operation of the payment certificate, wherein the second account is a fund account of a vehicle driver; the billing request comprises a vehicle identification corresponding to a vehicle driver and payment time corresponding to the payment certificate.

And 340, acquiring a target travel according to the vehicle identifier and the payment time by the server, wherein the target travel is a travel corresponding to the payment certificate.

And step 350, the server invoices the itinerary corresponding to the target itinerary.

In one possible implementation, the server may also send the invoice issued for the journey to the user terminal.

In summary, according to the method for issuing the travel invoice provided by the embodiment of the application, after the user terminal successfully pays, the server determines the target travel according to the vehicle identifier and the payment time, and issues the travel invoice corresponding to the target travel. The scheme provided by the embodiment of the application can enable the terminal to directly apply for issuing the travel invoice after one payment operation is finished, and the process of specifically searching the target travel is automatically finished by the server. Therefore, the method and the device can reduce the operation of the user, improve the efficiency of issuing the travel invoice, and reduce the time of the vehicle staying in the road due to the waiting of the invoice, thereby reducing the urban congestion and improving the safety of the operating vehicle.

Referring to fig. 4, fig. 4 is a flowchart illustrating a method for issuing a trip invoice according to an embodiment of the present application. In the method shown in fig. 4, the server and the user terminal cooperate to complete a process of a method for issuing a trip invoice, where the method includes:

in step 411, the server sends the payment credentials to the user terminal.

In the embodiment of the application, the payment voucher comprises an invoicing reminding control, and the invoicing reminding control is used for generating an invoicing request when being triggered.

Optionally, in this embodiment of the application, the user can use the user terminal to scan the payment two-dimensional code after completing the taxi taking service. It should be noted that the user pays for the vehicle using the first account, the payment two-dimensional code corresponds to the second account, and the second account is the fund account of the vehicle driver.

Please refer to fig. 5, which is a schematic diagram of a payment code display page provided based on the embodiment shown in fig. 4. Where the payment two-dimensional code 510 is the payee code for the second account, the interface includes the driver's authority identification 520 and the driver's name 530.

In fig. 5, the payment two-dimensional code 510 may be that shown in the a application. The driver 'S administrative department is the S city traffic management department and the driver' S name is Jack.

In step 412, after the payment to the second account through the first account is successful, the user terminal displays the payment certificate.

In the embodiment of the application, after the user successfully scans the payment two-dimensional code, the user terminal displays the payment interface and transfers the riding expense to the second account. And after the payment is successful, the server sends a payment certificate containing the invoicing reminding control to the user terminal.

Referring to fig. 6, fig. 6 is a schematic diagram of a payment page provided based on the embodiment shown in fig. 4. In fig. 6, a ride fee input box 610, a payment control 620, and a remark control 630 are included. The user can enter the fare to be paid in fare entry box 610, can confirm the payment by triggering payment control 620, and can add a note to the order for the payment by triggering note control 630.

Referring to fig. 7, fig. 7 is a schematic diagram of a payment credential provided based on the embodiment shown in fig. 4. In fig. 7, the invoicing reminder control 710 is located at the bottom of the payment certificate 700, and when the detail control 720 is clicked, the detailed information of the payment certificate is displayed. Optionally, the payment credential 700 further includes payment amount, offer information, payee, license plate information of the rental car, and transaction status.

In another possible implementation manner, the terminal can acquire the sign-in state identifier corresponding to the vehicle identifier. And when the vehicle identification corresponds to the check-in state identification of the vehicle. The sign-in state identification is used for indicating the specific content of the latest sign-in and sign-off operation of the corresponding vehicle.

In one possible scenario, if 0 indicates that the last operation is check-in and 1 indicates that the last operation is check-out, when the server acquires that the check-in status flag is 0, the check-in status flag is used to indicate that the driver of the corresponding vehicle is on duty. In this scenario, it is illustrated that the driver corresponding to the driver identifier is on duty.

And when the sign-in state identification indicates that the vehicle driver is on duty, sending payment credentials to the user terminal.

In step 413, the user terminal generates an invoicing request when receiving the triggering operation of the payment certificate.

In the embodiment of the present application, the execution manner of step 413 is the same as the execution manner of step 320, and the execution manner may refer to the execution manner of step 320.

In a possible implementation manner, the trigger operation may be at least one of a click operation, a double-click operation, a long-press operation, and the like, which is not limited in this embodiment of the application.

It should be noted that the billing request generated by the user terminal includes a vehicle identifier corresponding to a vehicle driver and a payment time corresponding to the payment certificate. Optionally, since the payment voucher carries the license plate number, the license plate number can be directly used as the vehicle identifier corresponding to the vehicle driver in the billing request.

In a possible implementation manner, the vehicle identifier may be any one of a ticket number, a driving license number, an operation license number, an engine number, and a frame number, which can uniquely represent the vehicle identifier, and the embodiment of the present application does not limit this.

It should be noted that, as a refinement, the present invention is described. In one possible implementation manner of the present application, the function shown in step 412 can be implemented by the user terminal by executing step (10) and step (20).

And (10) receiving the payment certificate sent by the server after the payment to the second account through the first account is successful.

And (20) displaying the payment voucher containing the invoicing reminding control, wherein the invoicing reminding control is used for generating an invoicing request when being triggered.

In one possible implementation manner of the present application, the function shown in step (20) can be implemented by the user terminal by executing step (21). Meanwhile, the function shown in step 413 can be implemented by the user terminal by performing step (22) and step (23).

And (21) the user terminal displays the payment certificate in the first application interface.

In an embodiment of the application, the first application interface is an application interface of a parent application. It should be noted that, in one possible implementation, the parent application is an application capable of running the child application. In one implementation, the parent application may be an application installed by an installation package in an android operating system or an apple operating system, and the child application may be an applet.

In this embodiment, the user terminal is capable of presenting the payment credentials in the first application interface.

And (22) when the triggering operation of the invoicing reminding control is received, the user terminal displays a second application interface.

In this embodiment of the application, the second application interface is an application interface of a child application, and the child application runs depending on the parent application.

It should be noted that, in a possible implementation manner, when the user terminal receives the trigger operation on the ticket issuing reminding control, the user terminal jumps from the user interface of the parent application program to the application interface of the child application program, so as to implement the function of the child application program.

And (23) generating a billing request according to the billing information set in the second application interface.

In an embodiment of the present application, the billing information includes at least one of a billing amount, a billing type, and a top-up of the invoice.

Referring to fig. 8, fig. 8 is a schematic diagram of page jump provided based on the embodiment shown in fig. 4. In the first application interface 810 in fig. 8, a billing reminder control 811 is displayed, when the billing reminder control 811 is triggered, the user terminal displays a second application interface 820, and at least one of a billing amount input box 821, a billing type setting control 822 and an invoice top-up setting control 823 is displayed in the second application interface 820. It should be noted that the information in the invoicing amount, the invoicing type and the invoice heading may be default information, and when the invoicing reminding control 811 is triggered, the invoicing request is directly generated according to the default information.

For example, the default value for the invoiced amount may be the corresponding value in the payment credential. The billing type may be a type preset in advance by the user. The invoice head-up can also be head-up information preset by the user in advance. On the basis, the user terminal can provide the setting control of the information in the second application interface, or can not provide the setting control of the information, and a default value is adopted.

In one possible implementation manner, the user terminal sets the billing information through two second application interfaces. The two second application interfaces are a first sub-interface and a second sub-interface, respectively.

Referring to fig. 9, fig. 9 is a schematic diagram of a second application interface provided based on the embodiment shown in fig. 4. In the first application interface 910 of fig. 9, an invoicing reminding control 911 is displayed, and when the invoicing reminding control 911 is triggered, the user terminal displays a first sub-interface 920. In the first sub-interface 920, trip information provided by the sub-application "taxi assistant" is displayed. In the first sub-interface 920, the invoiced amount has been set by default to the corresponding value of 61 dollars in the payment instrument. Optionally, an approval button 921 is also displayed in the first sub-interface 920, and when the approval button 921 is triggered, the driver will get a good comment. A billing application button 922 is also displayed in the first sub-interface 920, and when the billing application button 922 is triggered, the user terminal displays a second sub-interface 930. In the second sub-interface 930, an invoice type selection control 931 and an invoice head-up selection control 932 are included. It should be noted that, in one possible approach, the invoice heading includes a heading name and a tax number. In the second sub-interface 930, a submit button 933 is also displayed, and when the submit button 933 is triggered, the user terminal generates a billing request.

In step 414, the user terminal sends a billing request to the server.

Referring to fig. 10, fig. 10 is a view showing a process progress of billing provided based on the embodiment shown in fig. 4. In fig. 10, three phase information are shown, namely a "submit an application" phase 1001, a "commission platform review" phase 1002, and a "invoicing complete" phase 1003. The left side of each phase corresponds to a progress mark which is used for indicating whether the current phase is executed or not. In fig. 10, progress indicator 1004 on the left of "submit application" phase 1001 is illuminated, indicating that "submit application" phase 1001 has been executed. The progress indicator 1005 on the left of the "committee platform audit" stage 1002 is not illuminated, and the progress indicator 1006 on the left of the "invoicing completion" stage 1003 is also not illuminated, indicating that neither the "committee platform audit" stage 1002 nor the "invoicing completion" stage 1003 is executed. When the done button 1007 is triggered, the progress viewing interface 1000 is closed.

In step 415, the server obtains the itinerary within the specified time period as a candidate itinerary.

In step 416, a target trip is determined among the candidate trips.

In the embodiment of the present application, the target trip is a candidate trip having the shortest duration between the trip end time and the payment time. It should be noted that the server may also query a billing state of the vehicle-mounted invoice corresponding to the target trip, and when the paper invoice corresponding to the target trip has been issued, the terminal will not execute the subsequent step of issuing the trip invoice.

In the embodiment of the present application, the specified time period is a time period of a specified duration with the payment time as the start time. For example, if the payment time is 22 minutes 30 seconds at 13 hours on 29 days on 5 months in 2018 and the specified time length is 3 minutes, the specified period is a period having a start time of 22 minutes 30 seconds at 13 hours on 29 days on 5 months in 2018 and an end time of 25 minutes 30 seconds at 13 hours on 29 days on 5 months in 2018.

In one possible implementation, when the number of candidate trips is 1, the server directly determines the candidate trip as the target trip.

In another possible implementation manner, when the number of the candidate trips is at least 2, the server compares the respective trip end time lengths from the payment time of the at least 2 candidate trips, and the electronic invoice server determines the candidate trip with the trip end time closest to the payment time as the target trip.

For example, there are 2 candidate trips in a specified period of a period when the start time is 22 minutes 30 seconds at 13 on 29 th 5 th 2018 and the end time is 25 minutes 30 seconds at 13 th 29 th 2018. The end-of-travel time of the candidate trip a is 22 minutes 37 seconds at 13 hours on 29 months in 2018, and the end-of-travel time of the candidate trip B is 25 minutes 15 seconds at 13 hours on 29 days in 5 months in 2018. The trip end time of the candidate trip a is closer to the payment time, and the candidate trip a is determined as the target trip.

And 417, issuing a travel invoice corresponding to the target travel when the payment amount corresponding to the payment certificate meets the preset condition.

In the embodiment of the application, the preset condition includes that a difference value between a payment amount and a trip amount belongs to a preset amount interval, and the trip amount is an amount corresponding to a target trip.

For example, in a city S, the highest passing fee is set to 30 yuan, and the upper limit of the toll wiping zero of the driver is set to 4 yuan, the preset amount interval is [ -4,30 ]. The trip amount is an amount displayed on the in-vehicle terminal or the meter. And when the difference value between the payment amount and the trip amount is within the preset amount range of [ -4,30], the server issues a trip invoice corresponding to the target trip.

In another possible implementation manner, the server can implement the function of issuing the itinerary invoice corresponding to the target itinerary by executing the step (31) and the step (32).

And (31) sending a blockchain invoicing request to a blockchain server.

And (32) receiving a travel invoice sent by the blockchain server, wherein the travel invoice is issued by the blockchain server based on a blockchain technology.

It should be noted that the issued travel invoice is issued based on the block chain, and has the characteristics of tamper resistance and truthfulness and credibility.

After the server issues the trip invoice, the server may send the trip invoice to the user terminal.

In one possible approach, the electronic invoice server sends the travel invoice to the card and ticket server, and the card and ticket server records the travel invoice and provides the data of the travel invoice to the user terminal.

In one possible approach, the user terminal will display a new arrival invoice notification after the delivery of the travel invoice is completed, and will display an invoice detail page when the detail control is triggered.

Please refer to fig. 11, which is a schematic diagram of a new invoice notification provided based on the embodiment shown in fig. 4. In FIG. 11, a payee 1110, payer 1120, billing amount 1130, billing time 1140, remarks 1150 and details control 1160 are displayed in the user interface for the new incoming invoice notification.

Please refer to fig. 12, which is a schematic diagram of details of an invoice provided based on the embodiment shown in fig. 4. When the details control 1160 is triggered, the user terminal displays an invoice details page 1200, shown in fig. 12 as payee 1210, payer 1220, billing amount 1230, time of billing 1240, item 1250, draw control 1260, forward mailbox control 1270, share friends control 1280, and public number jump control 1290.

To sum up, this application embodiment can confirm whether the vehicle driver is on duty through the state sign of registering that acquires the vehicle sign correspondence to can in time show the warning controlling part of making out an invoice when the user actually pays the expense, be convenient for be used for in time applying for making out an invoice.

In addition, the user terminal can also stimulate the interface display of the subprogram in the interface of the main program, and provide the modification of the invoicing information through the interface display of the subprogram, so that the efficiency of filling in the invoice information is improved.

In addition, the server can also issue the travel invoice through the block chain server, so that the travel invoice can be prevented from being tampered, and the safety of the travel invoice is improved.

Referring to fig. 13, fig. 13 is a flowchart illustrating a method for issuing a trip invoice according to an embodiment of the present disclosure. The method is applied to a user terminal, and in fig. 13, the method includes:

step 1310, after the payment to the second account through the first account is successful, the payment voucher containing the invoicing reminding control is displayed in the first application interface.

In an embodiment of the application, the second account is a vehicle driver's funding account and the first application interface is an application interface of a parent application;

in step 1320, when the trigger operation for the invoicing reminding control is received, a second application interface is displayed.

In the embodiment of the application, the second application interface is an application interface of a sub-application, and the sub-application runs depending on the parent application;

step 1330, after receiving the trigger operation of the invoicing application control in the second application interface, displaying the travel invoice reminder.

In the embodiment of the application, the travel invoice reminder is used for reminding the server of issuing the travel invoice of the target travel corresponding to the payment certificate.

It should be noted that, referring to fig. 11, the interface shown in fig. 11 is in the form of an invoice reminder for an itinerary.

In summary, the user terminal can display the payment certificate containing the invoicing reminding control in the application interface of the parent application program after the payment to the second account is successful through the first account, display the application interface of the child application program depending on the parent application program when the triggering operation of the invoicing reminding control is received, and display the travel invoice reminding after the triggering operation of the invoicing application control in the application interface of the child application program is received, wherein the travel is used for reminding the server of issuing the travel invoice of the target travel corresponding to the payment certificate. The travel invoice can be issued when the user terminal triggers the one-time invoice reminding control, so that the step of issuing the travel invoice by the user is saved, and the issuing efficiency of the travel invoice is improved.

Referring to fig. 14, fig. 14 is a flowchart illustrating a method for issuing a trip invoice according to an embodiment of the present application. The method shown in fig. 14 is completed by the cooperation of a user terminal, an electronic invoice server, a vehicle journey server, a payment server, a card ticket server, a block chain invoice server and a vehicle-mounted terminal.

Step 1401, the electronic invoice server queries the vehicle journey server for the newly added driver registration record.

And 1402, recording the registration information of the newly added driver by the electronic invoice server.

In step 1403, the vehicle-mounted terminal receives a check-in operation of a driver.

In step 1404, the in-vehicle terminal transmits the driver's check-in information to the vehicle trip server.

Step 1405, when the passenger starts to take the car, the vehicle-mounted terminal starts to charge.

And step 1406, when the target journey is finished, the vehicle-mounted terminal stops charging.

In step 1407, the in-vehicle terminal transmits the information of the target trip to the vehicle trip server.

The user terminal sends a payment request to the payment server, step 1408.

Step 1409, the payment server completes the operation that the user terminal pays the second account of the vehicle driver through the first account according to the payment request.

At step 1410, the payment server synchronizes payment information for the target trip to the electronic invoice server.

At step 1411, the electronic invoice server verifies the driver's on Shift situation with the vehicle trip server.

And step 1412, when the driver is on duty, the electronic invoice server sends a taxi journey service notice to the user terminal.

In step 1413, the user terminal sends an invoicing request to the electronic invoice server.

In step 1414, the electronic invoice server matches the target itinerary from the vehicle itinerary server according to the invoicing request.

In step 1415, when the electronic invoice server matches the target itinerary, an invoice request is issued to the blockchain invoice server.

In step 1416, the blockchain invoice server invoices the itinerary according to the invoicing request.

In step 1417, the blockchain invoice server sends the trip invoice to the electronic invoice server.

At step 1418, the electronic invoice server inserts the travel invoice into the card server.

In step 1419, the electronic invoice server sends a notification of the invoice result to the user terminal.

The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.

Fig. 15 is a block diagram illustrating a structure of an apparatus for issuing a trip invoice according to an exemplary embodiment. The invoice issuing device may be used in a server to perform all or part of the steps performed by the server in the embodiment shown in fig. 3 or 4. The apparatus for issuing a trip invoice may include:

the billing request receiving module 1510 is configured to receive a billing request sent by a user terminal; the billing request is a request sent by the user terminal when the user terminal displays a payment certificate after successfully paying to a second account through a first account and receives a trigger operation of the payment certificate, wherein the second account is a fund account of a vehicle driver; the billing request comprises a vehicle identifier corresponding to the vehicle driver and payment time corresponding to the payment certificate;

a journey obtaining module 1520, configured to obtain a target journey according to the vehicle identifier and the payment time, where the target journey is a journey corresponding to the payment credential;

and an invoice issuing module 1530 for issuing an invoice of the itinerary corresponding to the target itinerary.

Optionally, before the receiving the request for making out an invoice sent by the user terminal, the apparatus further includes: a credential sending module;

the voucher sending module is used for sending the payment voucher to the user terminal, the payment voucher comprises an invoicing reminding control, and the invoicing reminding control is used for generating the invoicing request when being triggered.

Optionally, the apparatus further comprises: a sign-in identifier acquisition module;

the check-in identifier acquisition module is used for acquiring a check-in state identifier corresponding to the vehicle identifier;

and the certificate sending module is used for sending the payment certificate to the user terminal when the sign-in state identification indicates that the vehicle driver is on duty.

Optionally, a trip acquisition module 1520 to:

acquiring a journey in a specified time period as a candidate journey, wherein the specified time period is a time period with specified duration taking the payment time as a starting time;

determining the target trip in the candidate trips, wherein the target trip is the candidate trip with the shortest duration between the trip ending time and the payment time.

Optionally, an invoicing module 1530 to:

and issuing the travel invoice corresponding to the target travel when the payment amount corresponding to the payment certificate meets a preset condition, wherein the preset condition comprises that the difference value between the payment amount and the travel amount belongs to a preset amount interval, and the travel amount is the amount corresponding to the target travel.

Optionally, an invoicing module 1530 to:

sending a block chain billing request to a block chain server;

receiving the travel invoice sent by the blockchain server, wherein the travel invoice is issued by the blockchain server based on blockchain technology.

Fig. 16 is a block diagram illustrating a structure of an apparatus for issuing a trip invoice according to an exemplary embodiment. The invoice issuing device can be used in a user terminal to execute all or part of the steps executed by the user terminal in the embodiment shown in fig. 3 or fig. 4. The apparatus for issuing a trip invoice may include:

a first credential presentation module 1610 configured to present a payment credential after successful payment to a second account through a first account; the second account is a vehicle driver's funds account;

an invoicing request generating module 1620, configured to generate an invoicing request when the triggering operation on the payment credential is received; the billing request comprises a vehicle identifier corresponding to the vehicle driver and payment time corresponding to the payment certificate;

an invoicing request sending module 1630, configured to send the invoicing request to a server, where the invoicing request is used to instruct the server to obtain a target trip according to the vehicle identifier and the payment time, and to invoice a trip corresponding to the target trip; the target itinerary is an itinerary to which the payment credential corresponds.

Optionally, after the payment to the second account through the first account is successful, the first credential presenting module 1610 is configured to:

after the payment to the second account through the first account is successful, receiving the payment certificate sent by the server;

and displaying the payment voucher containing an invoicing reminding control, wherein the invoicing reminding control is used for generating the invoicing request when triggered.

Optionally, a first credential presentation module 1610 is configured to:

displaying the payment credential in a first application interface, the first application interface being an application interface of a parent application;

billing request Generation Module 1620, for

generating the invoicing request according to the invoicing information set in the second application interface; the billing information comprises at least one of billing amount, billing type and invoice new line.

Fig. 17 is a block diagram illustrating a structure of an apparatus for issuing a trip invoice according to an exemplary embodiment. The invoice issuing device can be used in a user terminal to execute all or part of the steps executed by the user terminal in the embodiment shown in fig. 3 or fig. 4. The apparatus for issuing a trip invoice may include:

a second credential presentation module 1710, configured to present, in the first application interface, a payment credential including the invoicing reminder control after successful payment is made to the second account through the first account; the second account is a vehicle driver's funding account, the first application interface is a parent application's application interface;

the interface display module 1720 is used for displaying a second application interface when the triggering operation of the invoicing reminding control is received, wherein the second application interface is an application interface of a sub-application program, and the sub-application program runs depending on the parent application program;

the reminding display module 1730 is configured to display a travel invoice reminder after receiving a trigger operation on the invoicing application control in the second application interface, where the travel invoice reminder is used to remind a server that a travel invoice of a target travel corresponding to the payment certificate has been issued.

FIG. 18 is a schematic diagram illustrating a configuration of a computer device, according to an example embodiment. The computer device 1800 includes a Central Processing Unit (CPU)1801, a system memory 1804 including a Random Access Memory (RAM)1802 and a Read Only Memory (ROM)1803, and a system bus 1805 that couples the system memory 1804 and the central processing unit 1801. The computer device 1800 also includes a basic input/output system (I/O system) 1806 for transferring information between various devices within the computer, and a mass storage device 1807 for storing an operating system 1813, application programs 1814, and other program modules 1815.

The basic input/output system 1806 includes a display 1808 for displaying information and an input device 1809 such as a mouse, keyboard, etc. for user input of information. Wherein the display 1808 and the input device 1809 are coupled to the central processing unit 1801 via an input/output controller 1810 coupled to the system bus 1805. The basic input/output system 1806 may also include an input/output controller 1810 for receiving and processing input from a number of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, input-output controller 1810 also provides output to a display screen, a printer, or other type of output device.

The mass storage device 1807 is connected to the central processing unit 1801 through a mass storage controller (not shown) connected to the system bus 1805. The mass storage device 1807 and its associated computer-readable media provide non-volatile storage for the computer device 1800. That is, the mass storage device 1807 may include a computer-readable medium (not shown) such as a hard disk or CD-ROM drive.

Without loss of generality, the computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, DVD, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that the computer storage media is not limited to the foregoing. The system memory 1804 and mass storage device 1807 described above may be collectively referred to as memory.

The computer device 1800 may be connected to the internet or other network devices through the network interface unit 1811 connected to the system bus 1805.

The memory further includes one or more programs, the one or more programs are stored in the memory, and the central processing unit 1801 implements all or part of the steps performed by the server in the method shown in fig. 3 or fig. 4 by executing the one or more programs.

Fig. 19 shows a block diagram of a user terminal 1900 according to an exemplary embodiment of the present application. The terminal 1900 may be: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion video Experts compression standard Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer IV, motion video Experts compression standard Audio Layer 4), a notebook computer, or a desktop computer. Terminal 1900 may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, and so on.

Generally, terminal 1900 includes: a processor 1901 and a memory 1902.

The processor 1901 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so forth. The processor 1901 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 1901 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 1901 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed by the display screen. In some embodiments, the processor 1901 may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.

The memory 1902 may include one or more computer-readable storage media, which may be non-transitory. The memory 1902 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in the memory 1902 is used to store at least one instruction for execution by the processor 1901 to implement all or part of the steps performed by the terminal in the method embodiments illustrated in fig. 3 or fig. 4 described above.

In some embodiments, terminal 1900 may further optionally include: a peripheral interface 1903 and at least one peripheral. The processor 1901, memory 1902, and peripheral interface 1903 may be connected by bus or signal lines. Various peripheral devices may be connected to peripheral interface 1903 via a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of a radio frequency circuit 1904, a touch screen display 1905, a camera 1906, an audio circuit 1907, a positioning component 1908, and a power supply 1909.

The peripheral interface 1903 may be used to connect at least one peripheral associated with an I/O (Input/Output) to the processor 1901 and the memory 1902. In some embodiments, the processor 1901, memory 1902, and peripherals interface 1903 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 1901, the memory 1902, and the peripheral interface 1903 may be implemented on separate chips or circuit boards, which is not limited in this embodiment.

The Radio Frequency circuit 1904 is used for receiving and transmitting RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuit 1904 communicates with a communication network and other communication devices via electromagnetic signals. The rf circuit 1904 converts an electrical signal into an electromagnetic signal to transmit, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 1904 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuit 1904 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: the world wide web, metropolitan area networks, intranets, generations of mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the rf circuit 1904 may further include NFC (Near field communication) related circuits, which are not limited in this application.

The display screen 1905 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display screen 1905 is a touch display screen, the display screen 1905 also has the ability to capture touch signals on or above the surface of the display screen 1905. The touch signal may be input to the processor 1901 as a control signal for processing. At this point, the display 1905 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, display 1905 may be one, providing the front panel of terminal 1900; in other embodiments, the displays 1905 can be at least two, each disposed on a different surface of the terminal 1900 or in a folded design; in still other embodiments, display 1905 can be a flexible display disposed on a curved surface or on a folding surface of terminal 1900. Even more, the display 1905 may be arranged in a non-rectangular irregular figure, i.e., a shaped screen. The Display 1905 may be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), or the like.

The camera assembly 1906 is used to capture images or video. Optionally, camera assembly 1906 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments, camera head assembly 1906 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.

The audio circuitry 1907 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals into the processor 1901 for processing, or inputting the electric signals into the radio frequency circuit 1904 for realizing voice communication. The microphones may be provided in a plurality, respectively, at different locations of the terminal 1900 for stereo sound capture or noise reduction purposes. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 1901 or the radio frequency circuitry 1904 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, the audio circuitry 1907 may also include a headphone jack.

The positioning component 1908 is configured to locate a current geographic Location of the terminal 1900 for navigation or LBS (Location Based Service). The Positioning component 1908 may be a Positioning component based on the Global Positioning System (GPS) in the united states, the beidou System in china, or the galileo System in russia.

Power supply 1909 is used to provide power to the various components in terminal 1900. The power source 1909 can be alternating current, direct current, disposable batteries, or rechargeable batteries. When power supply 1909 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. The wired rechargeable battery is a battery charged through a wired line, and the wireless rechargeable battery is a battery charged through a wireless coil. The rechargeable battery may also be used to support fast charge technology.

In some embodiments, terminal 1900 also includes one or more sensors 1910. The one or more sensors 1910 include, but are not limited to: acceleration sensor 1911, gyro sensor 1912, pressure sensor 1913, fingerprint sensor 1914, optical sensor 1915, and proximity sensor 1916.

Acceleration sensor 1911 may detect the magnitude of acceleration in three coordinate axes of the coordinate system established with terminal 1900. For example, the acceleration sensor 1911 may be used to detect components of the gravitational acceleration in three coordinate axes. The processor 1901 may control the touch screen 1905 to display a user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 1911. The acceleration sensor 1911 may also be used for acquisition of motion data of a game or a user.

The gyro sensor 1912 may detect a body direction and a rotation angle of the terminal 1900, and the gyro sensor 1912 may collect a 3D motion of the user on the terminal 1900 in cooperation with the acceleration sensor 1911. From the data collected by the gyro sensor 1912, the processor 1901 may implement the following functions: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.

Pressure sensor 1913 may be disposed on a side bezel of terminal 1900 and/or on a lower layer of touch display 1905. When the pressure sensor 1913 is disposed on the side frame of the terminal 1900, the user can detect a grip signal of the terminal 1900, and the processor 1901 can perform right-left hand recognition or shortcut operation based on the grip signal collected by the pressure sensor 1913. When the pressure sensor 1913 is disposed at the lower layer of the touch display 1905, the processor 1901 controls the operability control on the UI interface according to the pressure operation of the user on the touch display 1905. The operability control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.

The fingerprint sensor 1914 is configured to collect a fingerprint of the user, and the processor 1901 identifies the user according to the fingerprint collected by the fingerprint sensor 1914, or the fingerprint sensor 1914 identifies the user according to the collected fingerprint. Upon identifying that the user's identity is a trusted identity, the processor 1901 authorizes the user to perform relevant sensitive operations including unlocking a screen, viewing encrypted information, downloading software, paying for, and changing settings, etc. Fingerprint sensor 1914 may be disposed on a front, back, or side of terminal 1900. When a physical button or vendor Logo is provided on terminal 1900, fingerprint sensor 1914 may be integrated with the physical button or vendor Logo.

The optical sensor 1915 is used to collect the ambient light intensity. In one embodiment, the processor 1901 may control the display brightness of the touch screen 1905 based on the ambient light intensity collected by the optical sensor 1915. Specifically, when the ambient light intensity is high, the display brightness of the touch display screen 1905 is increased; when the ambient light intensity is low, the display brightness of the touch display screen 1905 is turned down. In another embodiment, the processor 1901 may also dynamically adjust the shooting parameters of the camera assembly 1906 according to the intensity of the ambient light collected by the optical sensor 1915.

Proximity sensor 1916, also referred to as a distance sensor, is typically disposed on the front panel of terminal 1900. Proximity sensor 1916 is used to gather the distance between the user and the front face of terminal 1900. In one embodiment, when proximity sensor 1916 detects that the distance between the user and the front surface of terminal 1900 gradually decreases, processor 1901 controls touch display 1905 to switch from the bright screen state to the rest screen state; when the proximity sensor 1916 detects that the distance between the user and the front surface of the terminal 1900 gradually becomes larger, the processor 1901 controls the touch display 1905 to switch from the breath-screen state to the bright-screen state.

Those skilled in the art will appreciate that the configuration shown in FIG. 19 is not intended to be limiting of terminal 1900 and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be used.

In an exemplary embodiment, a non-transitory computer readable storage medium comprising instructions, such as a memory comprising computer programs (instructions), executable by a processor of a computer device to perform all or part of the steps of the methods shown in the various embodiments of the present application, is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A method of invoice issuing for a trip, the method being performed by a server, the method comprising:

and issuing a travel invoice corresponding to the target travel.

2. The method of claim 1, wherein prior to receiving the invoice request sent by the user terminal, the method further comprises:

and sending the payment voucher to the user terminal, wherein the payment voucher comprises an invoicing reminding control, and the invoicing reminding control is used for generating the invoicing request when being triggered.

3. The method of claim 2, further comprising:

acquiring a sign-in state identifier corresponding to the vehicle identifier;

and when the sign-in state identification indicates that the vehicle driver is on duty, sending the payment certificate to the user terminal.

4. The method of claim 1, wherein said obtaining a target trip based on the vehicle identification and the payment time comprises:

5. The method of claim 1, wherein said invoicing a trip corresponding to the target trip comprises:

6. The method of claim 1, wherein said invoicing a trip corresponding to the target trip comprises:

sending a block chain billing request to a block chain server;

7. A method of invoice issuing for a trip, the method being performed by a user terminal, the method comprising:

8. The method of claim 7, wherein presenting payment credentials after successful payment to the second account via the first account comprises:

9. The method of claim 8, wherein the presenting the payment credential including an invoice reminder control comprises:

when the triggering operation of the payment voucher is received, generating an invoicing request, including:

10. A method of invoice issuing for a trip, the method being performed by a user terminal, the method comprising:

11. An apparatus for issuing a travel invoice, the apparatus comprising:

12. An apparatus for issuing a travel invoice, the apparatus comprising:

13. An apparatus for issuing a travel invoice, the apparatus comprising:

14. A computer device comprising a processor and a memory, the memory having stored therein at least one instruction, at least one program, set of codes, or set of instructions, which is loaded and executed by the processor to implement the method of any one of claims 1 to 10.

15. A computer readable storage medium having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, which is loaded and executed by a processor to implement the method according to any one of claims 1 to 10.