Invoice issuing method and device, terminal and computer readable storage medium
By obtaining passenger identification information and automatically identifying the invoice preference type, the problem of high communication cost between drivers and passengers on the choice of invoice type is solved, ensuring that passengers can obtain the required electronic or paper invoices in a timely manner.
Patent Information
- Application Number
- CN202411204746.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-29
- Publication Date
- 2025-01-03
AI Technical Summary
In the prior art, there is a problem that the driver and passenger have high communication costs in selecting invoice types, and the passenger may not be able to obtain the required electronic invoice or paper invoice in time due to forgetting.
By obtaining the passenger's identification information, it automatically identifies its invoice preference type, and issue corresponding types of invoices, including electronic invoices or paper invoices, according to the preference type after the passenger finishes the trip.
It reduces the communication costs between drivers and passengers, ensures that passengers can obtain invoices that meet their needs in a timely manner, and solves the invoice acquisition problem caused by forgetting.
Smart Images
Figure CN119250911A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of vehicle technology, and in particular, relates to an invoice issuance method, device, terminal and computer-readable storage medium. Background Art
[0002] With the development of technology, many processes in the taxi and other vehicle operation industries have been digitized. For example, the invoices after the taxi meter is gradually replaced by electronic invoices instead of traditional paper invoices. However, in real life, not all passengers can accept electronic invoices, especially some elderly people or passengers who need paper invoices for reimbursement. In the current solution, the driver needs to actively ask the passenger for the invoice demand or the passenger actively asks for the paper invoice, which not only increases the communication cost, but also may cause the passenger to forget to obtain the required electronic invoice or paper invoice in time. Summary of the invention
[0003] The present application provides an invoice issuance method, device, terminal and computer-readable storage medium, which can solve the problems in existing solutions such as high communication costs between drivers and passengers due to the selection of invoice types, and the possibility that passengers may not be able to obtain the required electronic invoices or paper invoices in a timely manner due to forgetfulness.
[0004] A first aspect of an embodiment of the present application provides an invoice issuing method, the invoice issuing method comprising:
[0005] Obtaining identification information of passengers;
[0006] Acquire the passenger's invoice preference type according to the identity identification information; the invoice preference type includes electronic invoice and paper invoice;
[0007] After the passenger completes the trip, an invoice of a corresponding type is issued according to the passenger's invoice preference type.
[0008] A second aspect of the present application also provides an invoice issuing device, the invoice issuing device comprising:
[0009] A first acquisition unit, used to acquire the identity information of the passenger;
[0010] A second acquisition unit is used to acquire the invoice preference type of the passenger according to the identity recognition information; the invoice preference type includes electronic invoice and paper invoice;
[0011] The invoice issuing unit is used to issue an invoice of a corresponding type according to the invoice preference type of the passenger after the passenger finishes the trip.
[0012] A third aspect of an embodiment of the present application provides a terminal, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the computer program is executed by the processor, the steps of the invoice issuance method described in the first aspect are implemented.
[0013] A fourth aspect of an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps of the invoice issuance method described in the first aspect are implemented.
[0014] In the embodiment of the present application, by obtaining the passenger's identity identification information and obtaining the passenger's invoice preference type based on the passenger's identity identification information, automatic identification of the passenger's invoice preference type is achieved, and after the passenger completes the trip, a suitable electronic invoice or paper invoice can be issued to the passenger based on the automatically identified passenger invoice preference type, so that the driver and the passenger do not need to communicate about issues related to the selection of invoice issuance type, and the passenger can obtain an invoice that meets his or her needs, which solves the high communication cost between the driver and the passenger due to the selection of invoice type in the existing solution, and the problem that the passenger may not be able to obtain the required electronic invoice or paper invoice in time due to forgetfulness. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Figure 1 A schematic diagram of the first implementation flow of the invoice issuance method provided in an embodiment of the present application.
[0016] Figure 2 This is a schematic diagram of the implementation flow of step 101 of the invoice issuance method provided in an embodiment of the present application.
[0017] Figure 3 This is a schematic diagram of the implementation flow of step 102 of the invoice issuance method provided in an embodiment of the present application.
[0018] Figure 4 This is another implementation flowchart of step 101 and step 102 of the invoice issuance method provided in an embodiment of the present application.
[0019] Figure 5 A schematic diagram of a second implementation flow of the invoice issuance method provided in an embodiment of the present application.
[0020] Figure 6 A schematic diagram of the structure of an invoice issuing device provided in an embodiment of the present application.
[0021] Figure 7 A schematic diagram of the structure of a terminal provided in an embodiment of the present application. DETAILED DESCRIPTION
[0022] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0023] It should be understood that in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.
[0024] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.
[0025] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the phrases "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. appearing in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways.
[0026] It should also be noted that, unless otherwise specified, the passengers mentioned in this application refer to passengers other than the driver.
[0027] At present, the invoices for operating vehicles such as taxis are gradually replaced by electronic invoices instead of traditional paper invoices. However, in real life, not all passengers can accept electronic invoices, especially some elderly people or passengers who need paper invoices for reimbursement. In the current scheme, the driver needs to actively ask the passenger for the invoice demand or the passenger actively asks for the paper invoice, which not only increases the communication cost, but also may cause the passenger to forget to obtain the required electronic invoice or paper invoice in time.
[0028] Based on this, the embodiments of the present application provide an invoice issuance method, device, terminal and computer-readable storage medium, which can solve the high communication cost between drivers and passengers due to the selection of invoice types in the existing solutions, and the problem that passengers may not be able to obtain the required electronic invoices or paper invoices in time due to forgetfulness.
[0029] In an embodiment of the present application, the above-mentioned invoice issuance method can be executed by an on-board computer on a vehicle, or by a cloud server at the vehicle operation end. The vehicle can be an operating vehicle such as a taxi or a bus. The present application does not limit the specific type of vehicle.
[0030] like Figure 1 As shown, it is a first implementation flow chart of an invoice issuance method provided in an embodiment of the present application. The invoice issuance method can be implemented by the following steps 101 to 103.
[0031] Step 101, obtaining the passenger's identity information;
[0032] In an embodiment of the present application, when the above-mentioned invoice issuance method is executed by a cloud server at the vehicle operating end, the above-mentioned acquisition of the passenger's identity identification information may refer to obtaining the passenger's identity identification information collected when the vehicle detects that a passenger has boarded the vehicle.
[0033] Specifically, the vehicle can detect whether a passenger is on board by detecting whether doors other than the main driver's door are opened; and / or by obtaining the empty or loaded state of the vehicle based on a meter installed on the vehicle; and / or by detecting whether a passenger is on board based on an image inside the vehicle captured by a camera installed on the vehicle and detecting whether there are passengers other than the driver on board. When it is detected that doors other than the main driver's door are opened, and / or the vehicle enters a loaded state from an empty state, and / or it is detected that there are other passengers on board except the driver, it is confirmed that a passenger has been detected on board, and the passenger's identity information can be collected.
[0034] In one embodiment of the present application, in the above step 101, obtaining the passenger's identity information may refer to using the device identification information of the passenger's Bluetooth device as the passenger's identity information. Figure 2 As shown, the process can be implemented by using the following steps 201 and 203.
[0035] Step 201, obtaining device identification information of the Bluetooth device already in the vehicle before the passenger gets on the vehicle;
[0036] Step 202, after the passenger gets on the vehicle and the vehicle is in motion, the device identification information of the newly added Bluetooth device in the vehicle is detected based on the device identification information of the existing Bluetooth device in the vehicle before the passenger gets on the vehicle.
[0037] Step 203: Use the device identification information of the newly added Bluetooth device as the device identification information of the passenger's Bluetooth device, and use the device identification information of the passenger's Bluetooth device as the passenger's identity information.
[0038] In this embodiment, before using the device identification information of the passenger's Bluetooth device as the passenger's identity recognition information, the Bluetooth devices in the vehicle that do not belong to the passenger can be marked as the driver's Bluetooth devices. Then, after the passenger gets on the vehicle, the device identification information of the newly added and always existing Bluetooth devices in the vehicle can be used as the device identification information of the passenger's Bluetooth device, and the device identification information of the passenger's Bluetooth device can be used as the passenger's identity recognition information.
[0039] For example, the device identification information of the existing Bluetooth device in the vehicle before the passenger gets on the vehicle is obtained in advance, and the device identification information of the existing Bluetooth device is used as the device identification information of the driver's Bluetooth device.
[0040] The Bluetooth device that is already in the vehicle before the passenger gets on the vehicle refers to a Bluetooth device that can be detected when the vehicle is not carrying passengers and is always detected during the driving process of the vehicle. For example, the Bluetooth device can be a mobile phone, tablet computer, smart watch, etc. of the driver.
[0041] In one embodiment of the present application, the Bluetooth devices already present in the vehicle before the passengers get on the vehicle can be marked and recorded as the Bluetooth devices already present in the vehicle before the passengers get on the vehicle by performing a Bluetooth scan of the vehicle's current environment after the vehicle is started (while the vehicle is driving) and when there are no passengers on board.
[0042] In one embodiment of the present application, the Bluetooth devices already in the vehicle before the passenger gets on the vehicle can also be determined by the driver registering and registering in advance on the cloud server of the vehicle operation end.
[0043] For example, the driver registers in advance in the cloud server of the vehicle operation end, and connects his mobile phone or other portable Bluetooth devices to the cloud server when registering. The cloud server automatically obtains the physical address of the driver's Bluetooth device and marks it as a Bluetooth device already in the vehicle before the passenger gets on the vehicle, that is, the driver's Bluetooth device.
[0044] In this embodiment, the device identification information of the newly added Bluetooth device in the vehicle refers to the device identification information of the Bluetooth device that has always existed in the vehicle, for example, the device identification information of the Bluetooth device whose existence time is greater than the set time.
[0045] In one embodiment of the present application, in the above step 101, the passenger can also swipe a physical card or virtual card carrying personal identity information such as an identity card, social security card, bank card, or phone card to enable the vehicle to collect the passenger's corresponding identity recognition information.
[0046] In one embodiment of the present application, in the above step 101, the passenger can also scan fingerprints, palm veins or perform iris recognition so that the vehicle can collect the identity information corresponding to the passenger.
[0047] In one embodiment of the present application, in the above step 101, the passenger's electronic payment account information may also be used as the passenger's identity identification information.
[0048] Specifically, after the passenger arrives at the destination, if the passenger pays by electronic payment methods such as scanning a code, the passenger's electronic payment account information can be obtained as the passenger's identity identification information. For example, the passenger's electronic payment account and mobile phone number can be used as the passenger's identity identification information.
[0049] It should be noted that the above is only an example of the type and acquisition method of the passenger identification information, and does not limit the scope of protection of this application. In other embodiments of this application, other types of passenger identification information may be included, and other methods may be used to obtain the passenger identification information, and this application does not limit this.
[0050] Step 102, obtaining the passenger's invoice preference type based on the identity identification information.
[0051] In the implementation of this application, the above-mentioned invoice preference types include electronic invoices and paper invoices.
[0052] In one embodiment of the present application, Figure 3 As shown, the above step 102 obtains the passenger's invoice preference type based on the identity recognition information, which can be implemented by the following steps 301 to 302.
[0053] Step 301, obtaining the passenger's most recent preset number of invoice issuance type records based on the passenger's identity identification information.
[0054] In the implementation of this application, when the above-mentioned invoice issuance method is executed by the on-board computer of the vehicle, the above-mentioned step 301 may mean that the vehicle sends the collected passenger's identity identification information to the cloud server at the vehicle operation end, and the cloud server searches for the invoice issuance type records of the passenger's most recent preset number of times.
[0055] Step 302: If the passenger's most recent preset number of invoice issuance type records include paper invoice issuance records, the passenger's invoice preference type is determined to be a paper invoice; otherwise, the passenger's invoice preference type is determined to be an electronic invoice.
[0056] In the embodiment of the present application, the specific value of the above-mentioned preset number of times can be determined according to the actual application scenario. For example, it can be 10 times, 5 times, etc., and the present application does not impose any restrictions on this.
[0057] In the implementation of this application, when the passenger's most recent preset number of invoice issuance type records include paper invoice issuance records, it means that the passenger may be more inclined to choose paper invoices. Therefore, it can be determined that the passenger's invoice preference type is paper invoice.
[0058] It should be noted that the above Figure 3 The illustrated embodiment is merely an example of how to determine a passenger's invoice preference type. In other embodiments of the present application, in addition to determining that the passenger's invoice preference type is a paper invoice when the passenger's most recent preset number of invoice issuance type records include issuance records of paper invoices, the type with the largest cumulative number of issuance types in the passenger's most recent preset number of invoice issuance type records may also be determined as the passenger's invoice preference type, or the passenger's most recent invoice issuance type may be determined as the passenger's invoice preference type. The present application does not impose any restrictions on this.
[0059] Step 103: After the passenger finishes the trip, an invoice of a corresponding type is issued according to the passenger's invoice preference type.
[0060] In an embodiment of the present application, when the above-mentioned invoice issuance method is executed by the cloud server of the vehicle operation end, the above-mentioned step 103 may refer to that the cloud server of the vehicle operation end sends feedback information of the passenger's invoice preference type to the vehicle, and controls the vehicle to issue the corresponding type of invoice according to the passenger's invoice preference type after the passenger ends the trip.
[0061] In the embodiment of the present application, by obtaining the passenger's identity identification information and obtaining the passenger's invoice preference type based on the passenger's identity identification information, automatic identification of the passenger's invoice preference type is achieved, and after the passenger completes the trip, a suitable electronic invoice or paper invoice can be issued to the passenger based on the automatically identified passenger invoice preference type, so that the driver and the passenger do not need to communicate about issues related to the selection of invoice issuance type, and the passenger can obtain an invoice that meets his or her needs, which solves the high communication cost between the driver and the passenger due to the selection of invoice type in the existing solution, and the problem that the passenger may not be able to obtain the required electronic invoice or paper invoice in time due to forgetfulness.
[0062] In one embodiment of the present application, when the passenger is a new passenger for whom no historical invoice issuance type record is stored, or the passenger does not carry any Bluetooth device, and is unable to obtain the corresponding identity information of the vehicle by swiping a physical card or virtual card carrying personal identity information such as an ID card, social security card, bank card, or phone card, Figure 4 As shown, steps 101 and 102 in the above invoice issuance method can also be implemented through the following steps 401 and 402.
[0063] Step 401, obtain a facial image of a passenger, determine the age type of the passenger based on the facial image, and use the age type of the passenger as the passenger's identity identification information.
[0064] In an embodiment of the present application, a passenger's facial image can be collected by an in-vehicle camera, and the facial image can be subjected to image recognition using a preset age recognition model to determine the passenger's age type.
[0065] In one embodiment of the present application, a large number of face sample images can be collected first, and the age type corresponding to each face sample image can be labeled to obtain the age type label corresponding to each face sample image. Then, the face sample images and their corresponding age type labels can be used to train a pre-constructed initial model to obtain the above-mentioned age recognition model.
[0066] Among them, the above-mentioned pre-built initial model can be a convolutional neural network model constructed on the basis of a convolutional neural network architecture such as VGG.
[0067] In order to reduce the amount of calculation, the age type label can be divided into two types: young type and old type. After the age recognition model is trained, the passenger's age type output by the age recognition model can be obtained by inputting the passenger's face image into the age recognition model, that is, the recognition result of the passenger's age type being a young type or an old type.
[0068] Step 402: If the age type of the passenger is a preset age type, the passenger's invoice preference type is determined to be a paper invoice; otherwise, the passenger's invoice preference type is determined to be an electronic invoice.
[0069] In the embodiment of the present application, the preset age type may be an elderly type. When the age type of the passenger is an elderly type, it indicates that the preferred invoice type is a paper invoice, and when the age type of the passenger is a young type, it indicates that the preferred invoice type is an electronic invoice.
[0070] In one embodiment of the present application, when a passenger wants to select his / her preferred invoice type for special reasons, step 103 in the above invoice issuance method may further include: receiving an operation instruction triggered by a user to select or cancel printing of a paper invoice, and issuing an invoice of a corresponding type to the passenger according to the operation instruction, so as to improve the flexibility of invoice issuance. The user may be a driver or a passenger, and the present application does not limit this.
[0071] In an embodiment of the present application, when an operation instruction triggered by a user to cancel printing of a paper invoice is received, an electronic invoice can be issued to the passenger according to the operation instruction.
[0072] In the above-mentioned various embodiments of the present application, after the above-mentioned step 103, the invoice issuance method further includes: storing the invoice issuance type of the passenger's current ride.
[0073] For example, the invoice type used by the passenger this time is recorded as the passenger's latest invoice type and stored in the cloud server at the vehicle operation end, so that the cloud server can query it the next time the passenger takes the bus, and the passenger's invoice preference type can be determined based on the query results.
[0074] It should be noted that, for the sake of simplicity of description, the aforementioned method embodiments are all expressed as a series of action combinations, but those skilled in the art should know that the present application is not limited to the described order of actions, and in some embodiments of the present application, certain steps may be performed in other orders.
[0075] For example, in the process of obtaining the passenger's identity information, the device identification information of the passenger's Bluetooth device can be obtained first, and when the device identification information of the passenger's Bluetooth device is not obtained, the passenger's electronic payment account information is obtained, and when the passenger's electronic payment account information is not obtained, the passenger's age type is obtained; or, the device identification information of the passenger's Bluetooth device and the passenger's age type are obtained at the same time, so that when the device identification information of the passenger's Bluetooth device and the passenger's electronic payment account information are not obtained, the passenger's age type is used as the passenger's identity information, that is, the passenger's age type is identified in advance to improve the efficiency of invoice issuance.
[0076] In an embodiment of the present application, the above-mentioned electronic invoice can be an electronic invoice generated by a pricing module based on information such as the actual travel distance and time that the passenger needs to pay, and can be sent to the passenger's mobile phone or mailbox via text message, email or a specific application.
[0077] In a specific practical application of this application, Figure 5 As shown, the specific implementation process of the above invoice method may include the following steps 501 to 510.
[0078] Step 501: Register and identify the physical address of the driver's Bluetooth device; then, execute step 502.
[0079] Step 502: When the vehicle is carrying passengers and driving, detect whether the physical address of the newly added Bluetooth device is scanned; if the physical address of the newly added Bluetooth device is scanned, execute step 503; if the physical address of the newly added Bluetooth device is not scanned, execute step 504.
[0080] Step 503: Check whether the cloud server stores the invoice issuance type record of the passenger corresponding to the physical address of the newly added Bluetooth device. If not, execute step 504; if stored, execute step 507.
[0081] Step 504, start the in-vehicle camera to collect the passenger's facial image, and determine the passenger's age type based on the passenger's facial image; then, execute step 505;
[0082] Step 505: Detect whether the passenger uses electronic payment to pay when getting off the bus. If yes, execute step 506; if no, execute step 508;
[0083] Step 506: Obtain the electronic payment account information of the passenger, and determine whether the invoice issuance type record of the passenger corresponding to the electronic payment account information is stored in the detection cloud server; if it is stored, execute step 507; if not, execute step 508;
[0084] Step 507: Obtain the passenger's most recent preset number of invoice issuance type records. If the passenger's most recent preset number of invoice issuance type records include paper invoice issuance records, determine that the passenger's invoice preference type is a paper invoice; otherwise, determine that the passenger's invoice preference type is an electronic invoice; then, execute step 509;
[0085] Step 508: If the age type of the passenger is the elderly type, then determine that the passenger's invoice preference type is a paper invoice; otherwise, determine that the passenger's invoice preference type is an electronic invoice, and then execute step 509;
[0086] Step 509: Issue an invoice of the corresponding type according to the passenger's invoice preference type; then, execute step 510.
[0087] Step 510: Record the passenger's invoice issuance type to the cloud server.
[0088] In an embodiment of the present application, the passenger's invoice preference type is determined by obtaining the physical address and / or facial image and / or electronic payment account information of the passenger's Bluetooth device, thereby realizing automatic identification of the passenger's invoice preference type. After the passenger completes the trip, a suitable electronic invoice or paper invoice can be issued to the passenger based on the automatically identified invoice preference type. This eliminates the need for communication between the driver and the passenger regarding issues related to the selection of the invoice issuance type, and enables the passenger to obtain an invoice that meets their needs. This solves the problem of high communication costs between the driver and the passenger due to the selection of the invoice type in the existing solution, as well as the problem that the passenger may not be able to obtain the required electronic invoice or paper invoice in a timely manner due to forgetfulness.
[0089] The present application also provides an invoice issuing device, such as Figure 6 As shown, the invoice issuing device 600 can be configured on the vehicle, or configured on the cloud server of the vehicle operation end, and the invoice issuing device includes:
[0090] The first acquisition unit 601 is used to acquire the identity information of the passenger;
[0091] The second acquisition unit 602 is used to acquire the passenger's invoice preference type according to the identity recognition information; the invoice preference type includes electronic invoice and paper invoice;
[0092] The invoice issuing unit 603 is used to issue an invoice of a corresponding type according to the invoice preference type of the passenger after the passenger completes the trip.
[0093] In one embodiment of the present application, the first acquisition unit 601 is specifically used to: use the device identification information of the passenger's Bluetooth device as the passenger's identity information.
[0094] In one embodiment of the present application, the above-mentioned first acquisition unit 601 is specifically used to: obtain the device identification information of the existing Bluetooth device in the vehicle before the passenger gets on the vehicle; after the passenger gets on the vehicle and the vehicle is in motion, detect the device identification information of the newly added Bluetooth device in the vehicle based on the device identification information of the existing Bluetooth device in the vehicle before the passenger gets on the vehicle; use the device identification information of the newly added Bluetooth device as the device identification information of the passenger's Bluetooth device, and use the device identification information of the passenger's Bluetooth device as the passenger's identity recognition information.
[0095] In one embodiment of the present application, the first acquisition unit 601 is specifically used to use the electronic payment account information of the passenger as the passenger's identity identification information.
[0096] In one embodiment of the present application, the above-mentioned second acquisition unit 602 is specifically used to: obtain the invoice issuance type records of the passenger's most recent preset number of times based on the identity identification information; if the invoice issuance type records of the passenger's most recent preset number of times include the issuance records of paper invoices, then determine that the passenger's invoice preference type is a paper invoice; otherwise, determine that the passenger's invoice preference type is an electronic invoice.
[0097] In one embodiment of the present application, the first acquisition unit 601 is specifically used to: acquire a facial image of a passenger; determine the age type of the passenger based on the facial image, and use the age type of the passenger as the passenger's identity information; the second acquisition unit 602 is specifically used to: if the age type of the passenger is a preset age type, determine the passenger's invoice preference type to be a paper invoice, otherwise, determine the passenger's invoice preference type to be an electronic invoice.
[0098] In one embodiment of the present application, the invoice issuing unit 603 is specifically used to: receive an operation instruction triggered by a user to select printing of a paper invoice or cancel printing of a paper invoice, and issue an invoice of a corresponding type to the passenger according to the operation instruction.
[0099] In one embodiment of the present application, the invoice issuing unit 603 is specifically used to: after issuing the corresponding invoice according to the invoice preference type of the passenger, store the invoice issuance type of the passenger's current ride.
[0100] It should be noted that, for the convenience and simplicity of description, the specific working process of the invoice issuing device 600 described above can refer to the above Figures 1 to 5 The corresponding process of the method described in will not be repeated here.
[0101] like Figure 7 As shown, the embodiment of the present application also provides a terminal. The terminal can be a vehicle at the vehicle operation end, or a cloud server at the vehicle operation end. Figure 7 As shown, the terminal 7 may include: a processor 70, a memory 71, and a computer program 72 stored in the memory 71 and executable on the processor 70. When the processor 70 executes the computer program 72, the steps in the above-mentioned various invoice issuing method embodiments are implemented, for example, Figure 1 Steps 101 to 103 are shown.
[0102] The processor 70 may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.
[0103] The memory 71 may be an internal storage unit of the terminal 7, such as a hard disk or a memory. The memory 71 may also be an external storage device for the terminal 7, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the terminal 7. Further, the memory 71 may also include both an internal storage unit of the terminal 7 and an external storage device. The memory 71 is used to store the above-mentioned computer program and other programs and data required by the terminal.
[0104] The computer program may be divided into one or more units, which are stored in the memory 71 and executed by the processor 70 to complete the present application. The one or more units may be a series of computer program instruction segments capable of completing specific functions, which are used to describe the process of the computer program executing the invoice issuance method in the terminal.
[0105] For example, the above computer program can be divided into: a first acquisition unit, a second acquisition unit and an invoice issuing unit, and the specific functions are as follows:
[0106] A first acquisition unit, used to acquire the identity information of the passenger;
[0107] A second acquisition unit is used to acquire the passenger's invoice preference type according to the identity recognition information; the invoice preference type includes an electronic invoice and a paper invoice;
[0108] The invoice issuing unit is used to issue an invoice of a corresponding type according to the invoice preference type of the passenger after the passenger completes the trip.
[0109] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.
[0110] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0111] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0112] In the embodiments provided in the present application, it should be understood that the disclosed terminals and methods can be implemented in other ways. For example, the terminal embodiments described above are only schematic. For example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, systems or units, which can be electrical, mechanical or other forms.
[0113] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0114] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0115] If the integrated module / 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 this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or recording medium that can carry computer program code, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electric carrier signals and telecommunication signals.
[0116] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.
Claims
1. A method for issuing invoices, characterized in that: The invoice issuance method includes: Obtaining identification information of passengers; Acquire the passenger's invoice preference type according to the identity identification information; the invoice preference type includes electronic invoice and paper invoice; After the passenger completes the trip, an invoice of a corresponding type is issued according to the passenger's invoice preference type.
2. The invoice issuing method according to claim 1, characterized in that: The obtaining of the passenger's identity information includes: Using the device identification information of the passenger's Bluetooth device as the passenger's identity information; or, The passenger's electronic payment account information is used as the passenger's identity identification information.
3. The invoice issuing method according to claim 2, characterized in that: The using the device identification information of the passenger's Bluetooth device as the passenger's identity information includes: Obtain device identification information of Bluetooth devices already in the vehicle before the passenger gets on board; After the passenger gets on the vehicle and the vehicle is in motion, detecting the device identification information of the newly added Bluetooth device in the vehicle based on the device identification information of the Bluetooth device already in the vehicle before the passenger gets on the vehicle; The device identification information of the newly added Bluetooth device is used as the device identification information of the passenger's Bluetooth device, and the device identification information of the passenger's Bluetooth device is used as the identity identification information of the passenger.
4. The invoice issuing method according to any one of claims 1 to 3, characterized in that: The step of obtaining the passenger's invoice preference type according to the identity identification information includes: Obtaining the invoice issuance type records of the passenger for the most recent preset number of times according to the identity identification information; If the passenger's most recent preset number of invoice issuance type records include issuance records of paper invoices, then the passenger's invoice preference type is determined to be paper invoices; otherwise, the passenger's invoice preference type is determined to be electronic invoices.
5. The invoice issuing method according to claim 1, characterized in that: The obtaining of the passenger's identity information comprises: Acquire a facial image of the passenger; determining the age type of the passenger based on the facial image, and using the age type of the passenger as the identity recognition information of the passenger; The step of obtaining the passenger's invoice preference type according to the identity identification information includes: If the age type of the passenger is a preset age type, the invoice preference type of the passenger is determined to be a paper invoice; otherwise, the invoice preference type of the passenger is determined to be an electronic invoice.
6. The invoice issuing method according to any one of claims 1 to 3 and 5, characterized in that: The issuing of an invoice of a corresponding type according to the invoice preference type of the passenger includes: Receive an operation instruction triggered by a user to select printing of a paper invoice or cancel printing of a paper invoice, and issue an invoice of a corresponding type to the passenger according to the operation instruction.
7. The invoice issuing method according to any one of claims 1 to 3 and 5, characterized in that: After issuing the corresponding invoice according to the invoice type preference of the passenger, the invoice issuing method further includes: The invoice issuance type of the passenger's current ride is stored.
8. An invoice issuing device, characterized in that: The invoice issuing device comprises: A first acquisition unit, used to acquire the identity information of the passenger; A second acquisition unit is used to acquire the invoice preference type of the passenger according to the identity recognition information; the invoice preference type includes electronic invoice and paper invoice; The invoice issuing unit is used to issue an invoice of a corresponding type according to the invoice preference type of the passenger after the passenger finishes the trip.
9. A terminal comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the computer program is executed by a processor, the steps of the invoice issuance method according to any one of claims 1 to 7 are implemented.
10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the invoice issuance method according to any one of claims 1 to 7 are implemented.