Bill printing method, system, electronic device and storage medium

Abstract

The application provides a bill printing method, system, electronic equipment and storage medium. The method comprises the following steps: receiving order information, wherein the order information comprises vehicle refueling amount, refueling oil volume and refueling gun number; collecting money from a customer based on the order information; after the customer successfully pays, checking the order information that has been successfully paid to determine printing information, wherein the printing information is only used for printing a bill once, and the printing information is one-to-one corresponding to the bill; and receiving the printing information to print the corresponding bill. Thus, the uniqueness of the printed bill is determined, overcoming the problems of repeated printing, no printing or delayed printing in a weak network in the traditional bill printing process, improving the operation efficiency and fault tolerance of the gas station, and improving the consumption experience of the customer.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of ticket printing, and more particularly to a ticket printing method, a ticket printing system, an electronic device, and a storage medium. BACKGROUND

[0002] Currently, when a vehicle owner goes to a gas station to refuel, the vehicle owner may have gone to the cash register (usually set indoors) to pay (cash, card swiping, code scanning, etc.) while the attendant is refueling, or the vehicle owner may have paid in advance. After successful payment, the vehicle owner will directly return to the vehicle to wait for refueling. When the attendant finishes refueling, it is necessary to confirm whether the vehicle owner has paid. Among them, a printed ticket can be used as a payment voucher. However, due to various factors such as network, equipment, and communication channels, problems such as repeated printing, delayed printing, or not printing after payment may occur when printing a ticket, thereby affecting the smooth progress of payment verification work, bringing a poor experience to the vehicle owner, and greatly affecting the work efficiency and benefits of the gas station.

[0003] Therefore, there is an urgent need for a new technical solution to solve the above technical problems. SUMMARY

[0004] A series of simplified concepts are introduced in the summary section, which will be further described in detail in the detailed description section. The summary section of the present application does not mean to attempt to limit the key features and essential technical features of the claimed technical solution, nor does it attempt to determine the protection scope of the claimed technical solution.

[0005] According to a first aspect of the present application, a ticket printing method is provided, comprising:

[0006] receiving order information, wherein the order information includes a vehicle refueling amount, a refueling oil volume, and a refueling gun number;

[0007] collecting payment from a customer based on the order information;

[0008] after the customer successfully pays, checking the order information that has successfully paid to determine printing information, wherein the printing information is used to print a ticket only once, and the printing information and the ticket are in one-to-one correspondence;

[0009] receiving the printing information to print the corresponding ticket.

[0010] Optionally, checking the order information that has successfully paid to determine the printing information comprises:

[0011] obtaining json data in the order information that has successfully paid, and then determining a length value of the json data;

[0012] Determine if the length of the JSON data is within a preset length range. For JSON data whose length is within the preset length range, parse the JSON data to obtain the parsed data.

[0013] Extract specific fields from the parsed data to validate the keywords of those fields.

[0014] Optionally, the method further includes:

[0015] Obtain the comparison results of keywords in a specific field with standard keywords, and validate the keywords in the specific field based on the comparison results.

[0016] Optionally, the method further includes:

[0017] The verified order information is added to memory.

[0018] Optionally, the validated order information is added to memory, including:

[0019] Retrieve the keyword from the order code field corresponding to the verified order information;

[0020] Determine if the keyword for the order code field exists in memory. If the keyword does not exist in memory, add the validated order information to memory. If the keyword already exists in memory, discard the validated order information.

[0021] Optionally, the method further includes:

[0022] Monitor the number of order information stored in memory, and if the number of order information stored in memory exceeds a preset threshold, remove the first piece of data from memory, where the first piece of data is the order information that was initially stored in memory.

[0023] Optionally, the method also includes: confirming that the customer has made a successful payment based on the printed receipt.

[0024] Secondly, a receipt printing system is also proposed, including:

[0025] The information receiving module is used to receive order information, which includes the amount of fuel to be refueled, the amount of fuel to be refueled, and the fuel nozzle number.

[0026] The payment module is used to collect payments from customers based on order information;

[0027] The verification module is used to verify the order information after the customer has successfully paid in order to determine the printing information. The printing information is used to print the ticket only once, and there is a one-to-one correspondence between the printing information and the ticket.

[0028] a printing module configured to receive the printing information to print a corresponding ticket.

[0029] In a third aspect, an electronic device is provided, which includes a processor and a memory, wherein the memory stores computer program instructions, and the computer program instructions, when executed by the processor, cause the electronic device to perform the ticket printing method as described above.

[0030] In a fourth aspect, a storage medium is provided, which stores program instructions, and the program instructions, when executed, cause the electronic device to perform the ticket printing method as described above.

[0031] According to the above technical solution, the order information is verified to determine the uniqueness of the printed ticket, which overcomes the problems of repeated printing, no printing or delayed printing in a weak network in the traditional ticket printing process, so that the attendant can quickly determine whether the customer has successfully paid by the uniquely printed ticket information, thereby improving the operation efficiency and fault tolerance of the gas station, and improving the consumer experience of the customer.

[0032] The ticket printing method of the present application, other advantages, objects and features of the present application will be embodied in part by the following description, and will be understood by those skilled in the art through research and practice of the present application. BRIEF DESCRIPTION OF DRAWINGS

[0033] Various other advantages and benefits will become apparent to those of ordinary skill in the art, upon reading the following detailed description of the preferred embodiments. The accompanying drawings are included to provide a description of preferred embodiments, and are not meant to limit the present description. Furthermore, the same reference numerals are used throughout the several drawings to designate the same or similar parts. In the drawings:

[0034] Figure 1 a schematic flow chart of a ticket printing method according to an embodiment of the present application is shown;

[0035] Figure 2 a schematic block diagram of a ticket printing system according to an embodiment of the present application is shown; and

[0036] Figure 3 a schematic block diagram of an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0037] The terms "first", "second", "third", "fourth" and the like in the description and in the claims of the present application and above-mentioned drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a specific sequential or chronological order. It is to be understood that the use of the terms so construed herein is merely for convenience and brevity and that one of the skilled in the art will be able to implement the embodiments in any order of the steps outlined herein. In addition, the terms "comprise", "comprising", "have", "having", "include", "including" and the like, are used inclusively and open- ended and do not exclude the

[0038] To solve the above technical problems, the present application proposes a new ticket printing method. Figure 1 A schematic flow chart of a ticket printing method 100 according to an embodiment of the present application is shown. As shown in Figure 1 The method 100 can include the following steps.

[0039] In step S110, order information is received. The order information includes the amount of fuel to be refueled, the amount of fuel to be refueled, and the fuel gun number. In an embodiment, when any customer refuels at a gas station, the customer first drives the vehicle to the fuel dispenser, and then the fuel attendant starts the refueling service according to the customer's request. At this time, the fuel attendant will inform the customer that the customer can go to the cash register to pay. During the customer's process to the cash register, if the fuel attendant finishes refueling at this time, the fuel dispenser can send order information to the server, and the order information includes the amount of fuel to be refueled, the amount of fuel to be refueled, and the fuel gun number. Alternatively, the server can automatically query the refueling information of all fuel guns in the gas station, and receive the corresponding order information from the corresponding fuel dispenser. Then, the server sends the received order information to the cash register device for the customer to pay for the order.

[0040] Step S120, collect money from the customer based on the order information. As mentioned above, the order information can be sent by the server to the cash register device. Correspondingly, after the refueling is completed, the cash register device has received the corresponding order information, and then can display the content corresponding to the order information through the display device for the customer to check. After confirming that the refueling amount, refueling oil quantity and refueling gun number are correct, the customer pays the gas station through the cash register device. It can be understood that the cash register device can be a device supporting multiple payment methods, such as bank cards, scanning codes, cash and the like. After the customer successfully pays, the cash register device can feed back to the server information that the customer has successfully paid. It can be understood that for the order that the customer has successfully paid, the server can mark it to distinguish it from the unpaid order.

[0041] Step S130, after the customer successfully pays, the order information that has successfully paid is checked to determine the print information. The print information is only used to print a ticket once, and the print information and the ticket are one-to-one.

[0042] Step S140, receive the print information to print the corresponding ticket.

[0043] In the embodiment, the method of how to check the order information that has successfully paid is not limited, and any existing or future technical solution that can achieve information checking is within the protection scope of the present application. However, it can be understood that no matter what means is used to check the order information, the print information generated by the means is used to make the printing device print a ticket once, and only one unique ticket. The print information can be received by the printing device, for example, the printing device can be a printer driven through a USB port, and the corresponding ticket can be printed based on the print information.

[0044] According to the above technical solution, the order information is checked to determine the uniqueness of the printed ticket, which overcomes the problems of repeated printing, no printing or delayed printing in a weak network in the traditional ticket printing process, so that the refueling staff can quickly determine whether the customer has successfully paid through the unique printed ticket information, thereby improving the operation efficiency and fault tolerance of the gas station, and improving the consumer experience of the customer.

[0045] Optionally, step S130, checking the order information that has successfully paid to determine the print information, can include the following steps.

[0046] Step S131, obtain the json data in the order information that has successfully paid, and then determine the length value of the json data.

[0047] It can be understood that the json data can be extracted from the order information by any existing or future technical means, and the length value of the extracted json data is determined, which is not limited herein.

[0048] In step S132, it is judged whether the length value of the json data is within the preset length range. For the json data whose length value is within the preset length range, the json data is parsed to obtain parsed data.

[0049] The preset length range can be set to any reasonable value according to experience or actual situation, which is not limited herein. For the json data that meets the condition, i.e., the length value is within the preset length range, data parsing is performed. It can be understood that any existing or future method that can parse json data is within the protection scope of the present application, which is not limited herein. After the json data is parsed, parsed data can be obtained.

[0050] In step S133, a specific field is taken out from the parsed data to check the keyword of the specific field. Exemplarily, the specific field can be a field push_id agreed with the server. For the specific field, its keyword can be obtained, and then the keyword is checked. Specifically, the comparison result of the keyword of the specific field and a standard keyword can be obtained to check the keyword of the specific field based on the comparison result. For example, the unprinted standard keyword can be pre-stored in the memory, and the keyword obtained from the specific field is compared with the standard keyword to obtain the comparison result of the two. In the case that the comparison result indicates that the two are inconsistent, it is determined through the check that the order information corresponding to the specific field has not printed the corresponding ticket. On the contrary, if the comparison result indicates that the two are consistent, it is determined that the order information corresponding to the specific field has printed the corresponding ticket, and thus it is not necessary to print it repeatedly.

[0051] Therefore, the accuracy and uniqueness of the printed ticket can be ensured by the checking algorithm, and thus the operation efficiency and fault tolerance of the gas station are improved.

[0052] Optionally, the method 100 can further include step S150 of adding the order information that passes the check to the memory.

[0053] It can be understood that when the gas station is normally operated, multiple customers may simultaneously refuel, and thus multiple order information can be sent to the server in a multi-channel communication manner for subsequent payment, ticket printing and the like. The order information that passes the check is stored in the memory, and thus the corresponding ticket can be printed in sequence based on the storage order or payment order, and the perfection and reliability of the printed ticket are ensured.

[0054] Optionally, the step S150 of adding the order information passed the verification to the memory can comprise the following steps.

[0055] In step S151, the key of the order code field corresponding to the order information passed the verification is obtained.

[0056] For example, when a new data (order information passed the verification) is received, the key of the order_code field of the new data can be obtained, wherein the order_code field represents the order code, and it can be understood that the order code is unique for each order. It can be understood that any existing or future method of obtaining the key from the order code field can be used to obtain the key, which is not limited in the present application.

[0057] In step S152, it is determined whether the key of the order code field is stored in the memory. If the key of the order code field is not stored in the memory, the order information passed the verification is added to the memory. If the key of the order code field is stored in the memory, the order information passed the verification is discarded.

[0058] As described above, the order code is unique for each order, so the key of the order code of the currently stored order information in the memory can be obtained, and then the key of the order code of the currently stored order information is compared with the key of the order code passed the verification to determine whether the key of the order code passed the verification is stored in the current memory, and then determine whether the order information passed the verification is stored in the current memory. It can be understood that if the comparison result indicates that they are consistent, it can be determined that the order information passed the verification is stored in the current memory, and at this time the order information passed the verification can be discarded, and then new order information passed the verification is continuously obtained and the above determination is repeated. If the comparison result indicates that they are inconsistent, it can be determined that the order information passed the verification is not stored in the current memory, and at this time the order information passed the verification can be stored in the current memory to update the order information in the current memory.

[0059] Therefore, it can be determined again whether the ticket has been printed, and the accuracy and uniqueness of the ticket are ensured.

[0060] Optionally, the method can further comprise step S160 of monitoring the number of order information stored in the memory, and removing the first data in the memory if the number of order information stored in the memory exceeds a preset number threshold. The first data is the order information stored in the memory at the beginning.

[0061] For example, the preset quantity threshold can be set to any reasonable data, for example, 50. When the order information determined to pass the verification according to the foregoing comparison can be added to the memory, if it is found in the storage process that the order information that passes the verification is stored in the memory, the quantity of the order information stored in the memory exceeds the preset quantity threshold, at this time, the order information stored in the memory at the beginning can be removed. It can be understood that the order information stored at the beginning can represent the longest time from the refueling time, therefore, if the order information in sequence is deleted in the case that the memory exceeds the limit, the time effectiveness and accuracy of the order information stored in the memory can be ensured. In addition, the increase of the data stored in the memory can affect the consumption of the memory and CPU, therefore, setting a reasonable value for the storage quantity of the memory can ensure the efficiency and safety of the memory.

[0062] Optionally, the method 100 can further include a step S170 of confirming that the customer has successfully paid based on the printed ticket.

[0063] It can be understood that after the ticket is successfully printed, the attendant can check the order information through the ticket, and then determine that the customer has paid, and then release the customer. Alternatively, the ticket can also include an identifier for verifying whether the payment is made, and the identifier can be identified by using any code scanning device, so as to confirm that the order corresponding to the ticket has been paid, and the same effect of verifying the payment and then releasing the customer can be achieved.

[0064] According to a second aspect of the present application, a ticket printing system is further provided. Figure 2 A schematic flowchart of a ticket printing system 200 according to an embodiment of the present application is shown. As shown, the system 200 can include an information receiving module 210, a payment receiving module 220, a verification module 230, and a printing module 240. Figure 2

[0065] The information receiving module 210 is configured to receive order information, wherein the order information includes a vehicle refueling amount, a refueling oil quantity, and a refueling gun number.

[0066] The payment receiving module 220 is configured to receive payment from the customer based on the order information.

[0067] The verification module 230 is configured to verify the order information that has been successfully paid after the customer successfully pays, to determine printing information, wherein the printing information is used to print a ticket only once, and the printing information is one-to-one corresponding to the ticket.

[0068] The printing module 240 is configured to receive the printing information to print a corresponding ticket.

[0069] According to a third aspect of the present application, an electronic device is further provided. Figure 3 ​A schematic block diagram of an electronic device 300 according to an embodiment of the present invention is shown. Figure 3 As shown, the electronic device 300 may include a processor 310 and a memory 320. The memory 320 stores computer program instructions, which, when executed by the processor, are used to perform the ticket printing method described above. The processor 310 may be implemented using at least one of the following hardware forms: a microprocessor, a digital signal processor (DSP), a field-programmable gate array (FPGA), or a programmable logic array (PLA). The processor 310 may also be a central processing unit (CPU), a graphics processing unit (GPU), an application-specific integrated circuit (ASIC), or a combination of other processing units with data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 300 to perform desired functions. The memory 320 may include one or more computer program products. The computer program products may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory. Non-volatile memory may include, for example, read-only memory (ROM), a hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, which the processor 310 may execute to implement the client functions (implemented by the processor) in the embodiments of the present invention described below, and / or other desired functions. Various applications and various data may also be stored in the computer-readable storage medium, such as various data used and / or generated by the applications.

[0070] Fourthly, a storage medium is also proposed, on which program instructions are stored. These program instructions, when executed, are used to perform the ticket printing method described above. The storage medium may, for example, include a storage component of a tablet computer, a hard disk of a computer, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a portable compact disc read-only memory (CD-ROM), a USB memory, or any combination of the above storage media. The computer-readable storage medium may be any combination of one or more computer-readable storage media.

[0071] Those skilled in the art can understand the specific details and beneficial effects of the ticket printing system, electronic equipment, and storage medium by reading the above description of the ticket printing method, and will not be repeated here for the sake of brevity.

[0072] In several embodiments provided in the present application, it should be understood that the disclosed apparatus and / or device can be implemented in other manners. For example, the division of the units is only a logical function division, and there can be another division manner for the actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections between different units, or the among different units, can be indirect couplings or communication connections through some interfaces, and electrical, mechanical or other forms.

[0073] The units described as separated components can or can not be physically separated, and the components displayed as units can or can not be physical units, i.e., can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purposes of the embodiments.

[0074] In addition, each functional unit in the embodiments of the present application can be integrated in a processing unit, or each unit can exist physically as a separate unit, or two or more units can be integrated in one unit. The integrated unit can be implemented in the form of hardware, or in the form of a software functional unit.

[0075] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on such an understanding, the technical solutions of the present application essentially, or the part that contributes to the prior art, or all or a part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in the embodiments of the present application. The foregoing storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and various media that can store program codes.

[0076] The above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: it can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for some technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for printing invoices, characterized in that, include: Receive order information, wherein the order information includes the amount of fuel to be refueled, the amount of fuel to be refueled, and the fuel nozzle number; Collect payment from the customer based on the order information; After the customer successfully makes payment, the order information that has been successfully paid is verified to determine the printing information. The printing information is used to print the ticket only once, and the printing information corresponds one-to-one with the ticket. Receive the printing information to print the corresponding ticket; The method also includes: The order information that passes the verification is added to memory; The step of adding the verified order information to memory includes: Obtain the keyword from the order code field corresponding to the order information that has passed the verification; Determine whether the keyword of the order code field is stored in the memory. If the keyword of the order code field is not stored in the memory, add the order information that has passed the verification to the memory. If the keyword of the order code field is already stored in the memory, discard the order information that has passed the verification.

2. The invoice printing method as described in claim 1, characterized in that, The process of verifying successfully paid order information to determine the printed information includes: Obtain the JSON data from the successfully paid order information, and then determine the length of the JSON data; Determine whether the length of the JSON data is within a preset length range. For JSON data whose length is within the preset length range, parse the JSON data to obtain parsed data. Specific fields are extracted from the parsed data to validate the keywords of the specific fields.

3. The invoice printing method as described in claim 2, characterized in that, The method further includes: Obtain the comparison results of the keywords of the specific field with the standard keywords, and verify the keywords of the specific field based on the comparison results.

4. The invoice printing method as described in claim 1, characterized in that, The method further includes: Monitor the number of order information stored in the memory, and if the number of order information stored in the memory exceeds a preset threshold, remove the first piece of data from the memory, wherein the first piece of data is the order information that was initially stored in the memory.

5. The invoice printing method according to any one of claims 1 to 4, characterized in that, The method further includes: Based on the printed receipt, it is confirmed that the customer has made a successful payment.

6. A ticket printing system, characterized in that, include: The information receiving module is used to receive order information, wherein the order information includes the amount of fuel to be refueled, the amount of fuel to be refueled, and the fuel nozzle number; The payment module is used to collect payment from customers based on the order information; The verification module is used to verify the order information that has been successfully paid after the customer has made a successful payment, so as to determine the printing information. The printing information is used to print the ticket only once, and the printing information corresponds one-to-one with the ticket. The verification module is also used to add the order information that passes the verification to memory; Obtain the keyword from the order code field corresponding to the order information that has passed the verification; Determine whether the keyword of the order code field is stored in the memory. If the keyword of the order code field is not stored in the memory, add the order information that has passed the verification to the memory. If the keyword of the order code field is already stored in the memory, discard the order information that has passed the verification. The printing module is used to receive the printing information and print the corresponding ticket.

7. An electronic device, characterized in that, It includes a processor and a memory, wherein the memory stores computer program instructions that, when executed by the processor, are used to perform the ticket printing method as described in any one of claims 1 to 5.

8. A storage medium storing program instructions that, when executed, perform the ticket printing method as described in any one of claims 1 to 5.

Images