A parking lot refund method and related device

Abstract

Embodiments of the present application disclose a parking lot refund method and related device, which are used for automatically performing refund when a user repeatedly pays. The method comprises the following steps: obtaining a target vehicle off-site request; obtaining consumption of the target vehicle according to the off-site request; generating a first payment order of the target vehicle according to the consumption; sending the first payment order to the target vehicle; receiving callback notification of the first payment order; judging whether the number of callback notifications is 1; if not, retaining the first callback notification, the first callback notification being a callback notification generated according to the first payment order of the target vehicle; initiating refund to the target vehicle according to a second callback notification, the second callback notification being all notifications except the first callback notification.

Description

Technical Field

[0001] This application relates to the field of parking lots, and more particularly to a parking lot refund method and related apparatus. Background Technology

[0002] With the advent of intelligent parking systems, entry, exit, and payment no longer require manual intervention. The intelligent parking system can directly obtain vehicle information and automatically generate an order linked to the vehicle.

[0003] In existing technologies, when parking lot systems send payment requests to target vehicles, poor network conditions and data transmission delays can cause users of vehicles that need to pay to make repeated payments. Summary of the Invention

[0004] This application provides a parking fee refund method and related device for automatically refunding fees when a user makes duplicate payments.

[0005] The first aspect of this application provides a method for refunding parking fees, including:

[0006] Obtain the target vehicle's departure request;

[0007] The consumption information of the target vehicle is obtained based on the departure request;

[0008] Generate the first payment order for the target vehicle based on the aforementioned consumption details;

[0009] Send the first payment order to the target vehicle;

[0010] Receive the callback notification for the first payment order;

[0011] Determine whether the number of callback notifications is 1;

[0012] If not, the first callback notification is retained, which is a callback notification generated based on the first payment order of the target vehicle;

[0013] A refund is initiated to the target vehicle based on a second callback notification, which is all notifications other than the first callback notification.

[0014] Optionally, before retaining the first callback notification, the method further includes:

[0015] Obtain the generation time of all callback notifications, including a first generation time and a second generation time;

[0016] Determine whether the first generation time is earlier than the second generation time;

[0017] If so, the callback notification generated at the first generation time is the first callback notification;

[0018] If not, the callback notification generated at the second generation time is the first callback notification.

[0019] Optionally, initiating a refund to the target vehicle based on the second callback notification includes:

[0020] Retrieve the target payment order bound to the second callback notification;

[0021] The refund amount will be determined based on the target payment order.

[0022] The payment channel will be determined based on the target payment order.

[0023] The refund amount will be returned to the payment channel.

[0024] Optionally, after sending the first payment order to the target vehicle, the method further includes:

[0025] If no callback notification for the first payment order is received after the preset time has expired, then the second payment order is retrieved.

[0026] Determine whether the second payment order and the first payment order are the same order;

[0027] If not, generate a multi-order instruction.

[0028] Optionally, determining whether the number of callback notifications is 1 includes:

[0029] Determine whether the number of callback notifications is 1 based on the multi-order instruction.

[0030] Optionally, after initiating a refund to the target vehicle based on the second callback notification, the method further includes:

[0031] Receive feedback information indicating that the refund has been completed.

[0032] A second aspect of this application provides a parking lot refund device, comprising:

[0033] The first acquisition unit is used to acquire the departure request of the target vehicle;

[0034] The second acquisition unit is used to acquire the consumption information of the target vehicle based on the departure request;

[0035] The first generation unit is used to generate a first payment order for the target vehicle based on the consumption information.

[0036] The first sending unit is used to send the first payment order to the target vehicle;

[0037] The first receiving unit is used to receive the callback notification of the first payment order;

[0038] The first judgment unit is used to determine whether the number of callback notifications is 1;

[0039] A retention unit is used to retain the first callback notification when the first judgment unit determines that the result is negative. The first callback notification is a callback notification generated based on the first payment order of the target vehicle.

[0040] A refund unit is used to initiate a refund to the target vehicle based on a second callback notification, which is all notifications other than the first callback notification.

[0041] Optionally, the device further includes:

[0042] The third acquisition unit is used to acquire the generation time of all callback notifications, the generation time including the first generation time and the second generation time;

[0043] The second judgment unit is used to determine whether the first generation time is earlier than the second generation time;

[0044] The second generation unit is used to generate a first callback notification when the second judgment unit determines that the callback notification generated at the first generation time is the first callback notification.

[0045] The third generation unit is used to generate a callback notification at the second generation time if the result of the second judgment unit is negative.

[0046] Optionally, the refund unit includes:

[0047] The acquisition module is used to acquire the target payment order bound to the second callback notification based on the second callback notification;

[0048] The first determining module is used to determine the refund amount based on the target payment order;

[0049] The second determining module is used to determine the payment channel based on the target payment order;

[0050] The refund module is used to return the refund amount to the payment channel.

[0051] Optionally, the device further includes:

[0052] The fourth acquisition unit is used to acquire the second payment order if no callback notification of the first payment order is received after the preset time has expired.

[0053] The third judgment unit is used to determine whether the second payment order and the first payment order are the same order;

[0054] The fourth generation unit is used to generate multiple order instructions when the judgment result of the third judgment unit is negative.

[0055] Optionally, the first determining unit is further configured to:

[0056] Determine whether the number of callback notifications is 1 based on the multi-order instruction.

[0057] Optionally, the device includes:

[0058] The second receiving unit is used to receive feedback information indicating that the refund has been completed.

[0059] A third aspect of this application provides a parking lot refund device, comprising:

[0060] Processor, memory, input / output unit, bus;

[0061] The processor is connected to the memory, the input / output unit, and the bus;

[0062] The processor specifically performs the same operations as described in the first aspect above.

[0063] As can be seen from the above technical solution, when this application receives callback notifications generated after multiple successful payments, it will automatically trace back the order based on the callback notifications generated from payment orders other than the first one, and refund the user based on the information contained in the order, thereby achieving the purpose of automatic refund. Attached Figure Description

[0064] Figure 1 This is a schematic flowchart of one embodiment of the parking fee refund method in this application.

[0065] Figure 2 This is a schematic flowchart of another embodiment of the parking fee refund method in this application.

[0066] Figure 3 This is a schematic diagram of one embodiment of the parking lot refund device in this application.

[0067] Figure 4 This is a schematic diagram of another embodiment of the parking lot refund device in this application.

[0068] Figure 5 This is a schematic diagram of another embodiment of the parking lot refund device in this application. Detailed Implementation

[0069] This application provides a parking fee refund method and related device for automatically refunding fees when a user makes duplicate payments.

[0070] The technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0071] The execution subject in this application embodiment includes, but is not limited to, all devices containing logical computing and operation capabilities, such as terminals, servers, and systems. No specific limitation is made here. This application embodiment uses a terminal as an example for description.

[0072] Please see Figure 1 This application provides an embodiment of a parking lot refund method, including:

[0073] 101. Obtain the target vehicle's departure request;

[0074] In practice, the parking lot terminal will collect vehicle information and related data associated with the vehicle, including but not limited to monthly payment information, prepaid balance, and other parking service information associated with the vehicle. Specific details are not limited here.

[0075] When the target vehicle enters the parking lot, the parking lot's terminal will use the vehicle information as a tag to monitor the target vehicle within the parking lot. This allows the terminal to directly obtain the target vehicle's actions within the parking lot when the target vehicle leaves. These actions include, but are not limited to, changes in parking spaces or use of charging piles within the parking lot, which can further determine the vehicle information or the target vehicle's consumption information within the parking lot.

[0076] 102. Obtain the consumption information of the target vehicle based on the departure request;

[0077] The departure request is generally sent by the user by scanning the QR code at the parking lot exit. At the same time, the terminal will obtain the vehicle information through an external camera. In this embodiment, the vehicle information is the license plate information.

[0078] After obtaining the license plate of the target vehicle, the terminal will bind its business with the user terminal that scanned the QR code, and obtain the target vehicle's consumption information in the parking lot based on the license plate.

[0079] 103. Generate the first payment order for the target vehicle based on the aforementioned consumption details;

[0080] Once the terminal obtains the consumption information of the target vehicle, it will generate the first payment order for the target vehicle based on the consumption information. The information contained in the first payment order includes the vehicle information of the target vehicle, the details of the generated fees, and the total fee.

[0081] 104. Send the first payment order to the target vehicle;

[0082] After generating the first payment order, the terminal will send the first payment order to the user terminal bound to the target vehicle, so that the user can pay for the target vehicle and drive it away from the parking lot.

[0083] 105. Receive the callback notification for the first payment order;

[0084] After the target vehicle successfully pays the fee, the payee will generate a callback notification and send the callback notification back to the terminal, so that the terminal can confirm that the target vehicle has completed the payment based on the callback notification.

[0085] 106. Determine whether the number of callback notifications is 1;

[0086] In practice, there may be situations where users experience delays during data interaction when making payments, resulting in the inability to receive callback notifications. This could lead to users making payments a second time. However, since callback notifications are generated after successful payment, there may be more than one callback notification for that user when data interaction on the terminal returns to normal.

[0087] The terminal needs to determine the number of callback notifications. If the number of callback notifications is 1, the service will be terminated directly and the gate will be opened to allow the target vehicle to pass. If the number of callback notifications is greater than 1, step 107 will be executed.

[0088] 107. If not, retain the first callback notification, which is a callback notification generated based on the first payment order of the target vehicle;

[0089] Specifically, after the terminal receives multiple callback notifications, it will retain the order payment record of the earliest generated callback notification based on the generation time of the callback notification, and retain that callback notification as the payment basis for the target vehicle, and release the vehicle.

[0090] 108. Initiate a refund to the target vehicle according to the second callback notification, wherein the second callback notification is all notifications other than the first callback notification.

[0091] In addition to the first callback notification, other callback notifications, namely the second callback notification, are used by the terminal to trace back to the payment order that generated the notification and to refund the target vehicle for multiple payments according to the payment method of that order.

[0092] As can be seen from the above technical solution, when this application receives callback notifications generated after multiple successful payments, it will automatically trace back the order based on the callback notifications generated from payment orders other than the first one, and refund the user based on the information contained in the order, thereby achieving the purpose of automatic refund.

[0093] Please see Figure 2 This application provides another embodiment of a parking lot refund method, including:

[0094] 201. Obtain the target vehicle's departure request;

[0095] 202. Obtain the consumption information of the target vehicle based on the departure request;

[0096] 203. Generate the first payment order for the target vehicle based on the aforementioned consumption details;

[0097] 204. Send the first payment order to the target vehicle;

[0098] Steps 201 to 204 in this embodiment are similar to steps 101 to 104 in the previous embodiment, and will not be repeated here.

[0099] 205. If no callback notification for the first payment order is received after the preset time has expired, then the second payment order is retrieved.

[0100] After the terminal sends the first payment order to the target, the terminal will start a timer to count down the preset time. The purpose of this timer is to control the service time for the target vehicle and avoid the inability to actively reset the process if there is no response for a long time, which would reduce the efficiency of the parking lot.

[0101] The second payment order is the latest order generated by the user who picked up the target vehicle, and this second payment order can be the same as the first payment order.

[0102] 206. Determine whether the second payment order and the first payment order are the same order;

[0103] Specifically, if the second payment order is the same as the first payment order, it means that the user has not completed the payment process for the first order. The terminal will generate a notification to remind the user to make the payment in time. If the second payment order is different from the first payment order, step 207 will be executed.

[0104] 207. If not, generate a multi-order instruction.

[0105] Specifically, the multi-order instruction terminal generates the instruction after determining that the target vehicle may have made more than one payment. This multi-order instruction is mainly used to activate the determination of the number of callback notifications.

[0106] 208. Receive the callback notification for the first payment order;

[0107] Step 208 in this embodiment is similar to step 105 in the previous embodiment, and will not be described again here.

[0108] 209. Determine whether the number of callback notifications is 1 based on the multi-order instruction.

[0109] The terminal generates a multi-order instruction. After the terminal receives the callback notification of the target vehicle, the terminal will determine the number of callback notifications. The purpose of determining the callback notifications through the multi-order instruction is to reduce the terminal's service process. When the number of callback notifications is 1, step 210 is executed.

[0110] 210. If not, obtain the generation time of all callback notifications, the generation time including the first generation time and the second generation time;

[0111] Once the terminal determines that there is more than one callback notification, it will obtain the generation time of all callback notifications. The key element for generating a callback notification is that the user of the target vehicle has successfully paid the payment order.

[0112] Specifically, the number of generation times is the same as the number of callback notifications. The first generation time refers to the time when the first generated payment order is successfully paid. All other generation times are the second generation times.

[0113] 211. Determine whether the first generation time is earlier than the second generation time;

[0114] Specifically, since the number of callback notifications may be greater than 2, when making the judgment, all the generation times will be compared one by one. The earliest time in the comparison result is the first generation time. Until the comparison is completed, the first generation time can be determined as the generation time of the callback notification for the first payment order's successful payment. If it is, then proceed to step 212; otherwise, proceed to step 213.

[0115] 212. If so, the callback notification generated at the first generation time is the first callback notification;

[0116] If the first generation time is earlier, it means that the callback notification generated at the first generation time is the first callback notification.

[0117] 213. If not, then the callback notification generated at the second generation time shall be the first callback notification;

[0118] If the second generation time is earlier, it means that the notification generated at the second generation time is the second callback notification.

[0119] 214. Retain the first callback notification, which is a callback notification generated based on the first payment order of the target vehicle;

[0120] Step 214 in this embodiment is similar to step 107 in the previous embodiment, and will not be repeated here.

[0121] 215. Obtain the target payment order bound to the second callback notification according to the second callback notification;

[0122] The terminal will retrieve and trace the relevant payment orders for all callback notifications except the first callback notification.

[0123] Specifically, if the terminal determines that more than one callback notification has been generated, it means that the user of the target vehicle has made more than one payment. In this case, the terminal needs to refund the excess payment amount.

[0124] 216. Determine the refund amount based on the target payment order;

[0125] When the terminal traces back to the payment order based on the callback notification, the terminal will determine the amount paid by the user based on the payment order data, so that the terminal can refund the user's payment in full.

[0126] 217. Determine the payment channel based on the target payment order;

[0127] Specifically, payment orders need to identify the payment channel used by the user through the payment order, so that the terminal can obtain the refund channel and thus determine the refund target.

[0128] 218. Return the refund amount to the payment channel, and the second callback notification is all notifications except the first callback notification.

[0129] Specifically, after the terminal obtains the refund amount and refund channel, the terminal will return the refund amount to the payment channel.

[0130] 219. Receive feedback information indicating that the refund has been completed.

[0131] Specifically, after confirming that the user has received the refund, the user's terminal will send a feedback message to the parking lot's terminal indicating that the refund has been received. This message indicates that the refund has been completed.

[0132] In this embodiment of the application, the number of callback notifications to be issued is determined by comparing payment orders, and valid callback notifications are obtained, thereby improving the working efficiency of the parking terminal.

[0133] Please see Figure 3This application provides an embodiment of a parking lot refund device, including:

[0134] The first acquisition unit 301 is used to acquire the target vehicle's departure request;

[0135] The second acquisition unit 302 is used to acquire the consumption information of the target vehicle based on the departure request;

[0136] The first generation unit 303 is used to generate a first payment order for the target vehicle based on the consumption information.

[0137] The first sending unit 304 is used to send the first payment order to the target vehicle;

[0138] The first receiving unit 305 is used to receive the callback notification of the first payment order;

[0139] The first judgment unit 306 is used to determine whether the number of callback notifications is 1;

[0140] The retention unit 307 is used to retain the first callback notification when the judgment result of the first judgment unit is negative. The first callback notification is a callback notification generated based on the first payment order of the target vehicle.

[0141] Refund unit 308 is used to initiate a refund to the target vehicle according to a second callback notification, wherein the second callback notification is all notifications other than the first callback notification.

[0142] In this embodiment, the functions of each unit are the same as those described above. Figure 1 The steps in the illustrated embodiments are the same and will not be repeated here.

[0143] Please see Figure 4 This application provides another embodiment of a parking lot refund device, including:

[0144] The first acquisition unit 401 is used to acquire the target vehicle's departure request;

[0145] The second acquisition unit 402 is used to acquire the consumption information of the target vehicle based on the departure request;

[0146] The first generation unit 403 is used to generate a first payment order for the target vehicle based on the consumption information.

[0147] The first sending unit 404 is used to send the first payment order to the target vehicle;

[0148] The fourth acquisition unit 405 is used to acquire the second payment order when no callback notification of the first payment order is received after a preset time has elapsed.

[0149] The third judgment unit 406 is used to determine whether the second payment order and the first payment order are the same order;

[0150] The fourth generation unit 407 is used to generate a multi-order instruction when the judgment result of the third judgment unit is negative.

[0151] The first receiving unit 408 is used to receive the callback notification of the first payment order;

[0152] The first judgment unit 409 is used to determine whether the number of callback notifications is 1;

[0153] The third acquisition unit 410 is used to acquire the generation time of all callback notifications when the judgment result of the first judgment unit is negative. The generation time includes the first generation time and the second generation time.

[0154] The second judgment unit 411 is used to determine whether the first generation time is earlier than the second generation time;

[0155] The second generation unit 412 is used to generate a first callback notification when the second judgment unit determines that the callback notification generated at the first generation time is the first callback notification.

[0156] The third generation unit 413 is used to generate a callback notification at the second generation time when the second judgment unit determines that the result is negative, and the callback notification generated at the second generation time is the first callback notification.

[0157] Retention unit 414 retains the first callback notification, which is a callback notification generated based on the first payment order of the target vehicle;

[0158] Refund unit 415 is used to initiate a refund to the target vehicle according to a second callback notification, wherein the second callback notification is all notifications other than the first callback notification.

[0159] The second receiving unit 416 is used to receive feedback information indicating that the refund has been completed.

[0160] In this embodiment of the application, the refund unit 415 includes:

[0161] The acquisition module 4151 is used to acquire the target payment order bound to the second callback notification according to the second callback notification;

[0162] The first determining module 4152 is used to determine the refund amount based on the target payment order;

[0163] The second determining module 4153 is used to determine the payment channel based on the target payment order;

[0164] The refund module 4154 is used to return the refund amount to the payment channel.

[0165] In this embodiment of the application, the first determining unit 409 is further configured to:

[0166] Determine whether the number of callback notifications is 1 based on the multi-order instruction.

[0167] In this embodiment, the functions of each unit are the same as those described above. Figure 2 The steps in the illustrated embodiments are the same and will not be repeated here.

[0168] Please see Figure 5 This application provides another embodiment of a parking lot refund device, including:

[0169] Processor 501, memory 502, input / output unit 503, bus 504;

[0170] The processor 501 is connected to the memory 502, the input / output unit 503 and the bus 504;

[0171] The processor 501 specifically executes... Figures 1 to 2 The steps in the method correspond to the operations.

[0172] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0173] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

[0174] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0175] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0176] If the integrated unit is implemented as 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 technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A method for refunding parking fees, characterized in that, include: Obtain the target vehicle's departure request; The consumption information of the target vehicle is obtained based on the departure request; Generate the first payment order for the target vehicle based on the aforementioned consumption details; Send the first payment order to the target vehicle; Receive the callback notification for the first payment order; Determine whether the number of callback notifications is 1; If not, obtain the generation time of all callback notifications, including the first generation time and the second generation time; Determine whether the first generation time is earlier than the second generation time; If so, the callback notification generated at the first generation time is the first callback notification; If not, the callback notification generated at the second generation time shall be the first callback notification; The first callback notification is retained, which is a callback notification generated based on the first payment order of the target vehicle. A refund is initiated to the target vehicle based on the second callback notification, which is all notifications except the first callback notification. Initiating a refund for the target vehicle according to the second callback notification includes: Retrieve the target payment order bound to the second callback notification according to the second callback notification, and issue a refund.

2. The method according to claim 1, characterized in that, Initiating a refund for the target vehicle according to the second callback notification includes: Retrieve the target payment order bound to the second callback notification; The refund amount will be determined based on the target payment order. The payment channel will be determined based on the target payment order. The refund amount will be returned to the payment channel.

3. The method according to claim 1 or 2, characterized in that, After sending the first payment order to the target vehicle, the method further includes: If no callback notification for the first payment order is received after the preset time has expired, then the second payment order is retrieved. Determine whether the second payment order and the first payment order are the same order; If not, generate a multi-order instruction.

4. The method according to claim 3, characterized in that, The step of determining whether the number of callback notifications is 1 includes: Determine whether the number of callback notifications is 1 based on the multi-order instruction.

5. The method according to any one of claims 1 or 2, characterized in that, After initiating a refund to the target vehicle based on the second callback notification, the method further includes: Receive feedback information indicating that the refund has been completed.

6. A parking lot refund device, characterized in that, include: The first acquisition unit is used to acquire the departure request of the target vehicle; The second acquisition unit is used to acquire the consumption information of the target vehicle based on the departure request; The first generation unit is used to generate a first payment order for the target vehicle based on the consumption information. The first sending unit is used to send the first payment order to the target vehicle; The first receiving unit is used to receive the callback notification of the first payment order; The first judgment unit is used to determine whether the number of callback notifications is 1; The third acquisition unit is used to acquire the generation time of all callback notifications, the generation time including the first generation time and the second generation time; The second judgment unit is used to determine whether the first generation time is earlier than the second generation time; The second generation unit is used to generate a first callback notification when the second judgment unit determines that the callback notification generated at the first generation time is the first callback notification. The third generation unit is used to generate a callback notification at the second generation time when the second judgment unit determines that the result is no; A retention unit is used to retain the first callback notification when the first judgment unit determines that the result is negative. The first callback notification is a callback notification generated based on the first payment order of the target vehicle. A refund unit is used to initiate a refund to the target vehicle based on a second callback notification, wherein the second callback notification is all notifications other than the first callback notification. The refund unit is also used for: Retrieve the target payment order bound to the second callback notification according to the second callback notification, and issue a refund.

7. The apparatus according to claim 6, characterized in that, The refund unit includes: The acquisition module is used to acquire the target payment order bound to the second callback notification based on the second callback notification; The first determining module is used to determine the refund amount based on the target payment order; The second determining module is used to determine the payment channel based on the target payment order; The refund module is used to return the refund amount to the payment channel.

8. The apparatus according to any one of claims 6 or 7, characterized in that, The device further includes: The fourth acquisition unit is used to acquire the second payment order if no callback notification of the first payment order is received after the preset time has expired. The third judgment unit is used to determine whether the second payment order and the first payment order are the same order; The fourth generation unit is used to generate multiple order instructions when the judgment result of the third judgment unit is negative.

Images