Charging appearance control method and device, computer device and storage medium

Abstract

The application discloses a charging exit control method and device, a computer device and a storage medium. The method comprises the following steps: in response to an exit request of a target vehicle, determining a user account associated with the target vehicle; determining the unpaid fees of all vehicles in the user account, generating a total fee to be paid and pushing the total fee to the target user; and controlling the target vehicle to exit when the total fee to be paid is paid in full. The application can effectively avoid fee accumulation, reduce the risk of fee evasion, reduce the cost of subsequent manual recovery, significantly improve the efficiency of parking fee collection and the standardization of management, and improve the user payment experience.

Description

Technical Field

[0001] This application relates to the field of parking management technology, and in particular to a billing exit control method, device, computer equipment and storage medium. Background Technology

[0002] With the development of smart parking technology, parking fee collection models that link multiple parking spaces and vehicles to the same user account have become widely used. In existing multi-space, multi-vehicle parking fee collection schemes, users typically register one account and link multiple vehicles. When one vehicle enters or exits the parking lot, the system independently records the parking duration and calculates the parking fee separately. When the vehicle initiates an exit request, the system only verifies the payment status of the currently exiting vehicle. If the vehicle has not paid, the system prompts the user to complete the payment before allowing the vehicle to leave.

[0003] However, the aforementioned independent billing and verification method has obvious drawbacks: since only the fee status of the vehicle is verified when it leaves the parking lot, users only need to pay the fee for the vehicle currently leaving to be released, while other bound vehicles in the parking lot continue to be charged, which can easily lead to the accumulation of arrears and result in untimely payments; at the same time, some users can avoid the collection of fees for some vehicles by taking turns leaving the parking lot and paying in installments, which poses a risk of evasion and causes revenue losses for the parking lot operator; in addition, a large number of scattered arrears require the operator to manually collect them, which also increases management costs and operational burden.

[0004] Existing parking fee collection technologies lack an effective mechanism for uniformly calculating and settling all fees for all vehicles on site under a user's account when the vehicle leaves the site. This makes it difficult to prevent the accumulation of arrears and evasion of fees from the source, resulting in low collection efficiency and management standardization. Summary of the Invention

[0005] Therefore, it is necessary to provide a billing exit control method, apparatus, computer equipment, and storage medium to address the above-mentioned technical problems and solve at least one of the problems existing in the prior art.

[0006] Firstly, a billing exit control method is provided, including: In response to a request for the target vehicle to be dispatched, the user account associated with the target vehicle is determined; Identify all outstanding fees for vehicles present under the user's account, generate the total outstanding fees, and push them to the target user; Once the total outstanding fees have been paid, the target vehicle is controlled to leave the premises.

[0007] In one possible implementation, determining the outstanding fees for all vehicles present under the user account, generating the total outstanding fees, and pushing it to the target user includes: Query all vehicle information associated with the user account and filter out the vehicles present. Calculate the unpaid fees for each vehicle present, according to the pre-design fee rules; The outstanding fees of all vehicles present are summarized to generate the total outstanding fees and fee details. The fee details include the license plate number, entry time and outstanding amount of each vehicle present. The total amount due and fee details will be sent to the target user.

[0008] In one possible implementation, calculating the outstanding fees for each vehicle present according to the pre-design fee rules includes: Determine the entry time and parking duration for each vehicle on site; If the entry time is abnormal or the parking time exceeds the preset parking time threshold, the unpaid fees for the corresponding vehicle will be marked as abnormal fees. When generating the total amount due, the vehicle information and reason for the abnormal fee are marked separately and pushed to the target user and the parking lot management terminal. If the abnormal fee is confirmed to be correct, the abnormal fee will be treated as the unpaid fee. If the abnormal fee is confirmed to be incorrect, the abnormal fee will be corrected, and the corrected fee will be treated as the unpaid fee.

[0009] In one possible implementation, generating the total amount due and pushing it to the target user includes: Determine if the user account has any historical arrears. If the user account has historical arrears, the historical arrears amount will be combined with the total amount due to generate a combined total amount due to pay. The system pushes the total outstanding fees and details of the consolidated fees to the target user, with the details of the consolidated fees distinguishing between historical arrears and the current outstanding amount.

[0010] In one possible implementation, determining the user account associated with the target vehicle includes: Obtain vehicle information of the target vehicle, wherein the vehicle information includes at least one of license plate number and vehicle identification number; Based on the preset association between vehicles and user accounts, the corresponding user account is queried and determined according to the vehicle information of the target vehicle. If no associated user account is found, the system will query the user information associated with the target vehicle from the current parking lot management system, and then query whether there are any other bound vehicles among the vehicles in the parking lot based on the user information.

[0011] In one possible implementation, controlling the target vehicle to leave the premises after the total outstanding fees have been paid includes: Obtain the payment result from the payment terminal, verify the payment result, and confirm whether the total amount due has been paid in full. If the payment verification is successful, the billing status of all vehicles on site under the user account will be updated, and the unpaid fees will be marked as paid. The control gate is opened to allow the target vehicle to exit; Once the target vehicle has completely left the exit detection area, the control gate closes and the target vehicle's status is updated to "departure status".

[0012] In one possible implementation, the method further includes: If the total amount due is not paid within the first preset time, or if the payment verification fails, a payment reminder and an error handling prompt will be sent to the target user. If the target user abandons payment or fails to make payment within a second preset time, the exit process of the target vehicle will be suspended. Generate the outstanding payment information for the target vehicle and record the outstanding payment information to the user account.

[0013] Secondly, a billing exit control device is provided, comprising: The user account determination unit is used to determine the user account associated with the target vehicle in response to the vehicle's dispatch request. The unit for determining total outstanding fees is used to determine the unpaid fees of all vehicles present under the user account, generate the total outstanding fees, and push them to the target user. The vehicle exit control unit is used to control the exit of the target vehicle after the total outstanding fees have been paid.

[0014] Thirdly, a computer device is provided, including a memory, a processor, and computer-readable instructions stored in the memory and running on the processor, wherein the processor, when executing the computer-readable instructions, implements the billing exit control method as described above.

[0015] Fourthly, a computer-readable storage medium is provided that stores computer-readable instructions thereon, which, when executed by a processor, implement the billing and exit control method as described above.

[0016] The aforementioned billing and exit control method, apparatus, computer equipment, and storage medium, implemented as follows: In response to an exit request from a target vehicle, determine the user account associated with the target vehicle; determine the unpaid fees of all vehicles present under the user account, generate a total outstanding fee, and push it to the target user; once the total outstanding fee is paid, control the target vehicle to exit. This embodiment of the application, by uniformly calculating the unpaid parking fees of all vehicles present under the user account upon exit and releasing the vehicle only after full payment, effectively avoids the accumulation of arrears, reduces the risk of evasion, reduces subsequent manual collection costs, significantly improves parking fee collection efficiency and management standardization, and enhances the user payment experience. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a flowchart illustrating a billing and exit control method in one embodiment of this application. Figure 1 ; Figure 2 This is a flowchart illustrating a billing and exit control method in one embodiment of this application. Figure 2 ; Figure 3 This is a flowchart illustrating a billing and exit control method in one embodiment of this application. Figure 3 ; Figure 4 This is a flowchart illustrating a billing and exit control method in one embodiment of this application. Figure 4 ; Figure 5 This is a flowchart illustrating a billing and exit control method in one embodiment of this application. Figure 5 ; Figure 6 This is a flowchart illustrating a billing and exit control method in one embodiment of this application. Figure 6 ; Figure 7 This is a schematic diagram of a billing exit control device according to one embodiment of this application; Figure 8 This is a schematic diagram of a computer device according to one embodiment of this application. Detailed Implementation

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

[0020] In one embodiment, such as Figure 1 As shown, a billing exit control method is provided, including the following steps: In step S110, in response to the exit request of the target vehicle, the user account associated with the target vehicle is determined; Optionally, when the target vehicle arrives at the parking lot exit lane, the license plate recognition device (such as a high-definition recognition camera), ground sensor, or radio frequency identification module (such as an RFID reader, vehicle electronic tag reader / writer, ETC on-board unit reader, etc.) at the exit will detect the vehicle's arrival and generate a corresponding exit request signal. The system responds to this exit request in real time, collecting the target vehicle's license plate number through the license plate recognition device or reading the vehicle's identification information through the radio frequency identification module, thereby obtaining the target vehicle's information. The system pre-stores the binding relationship between vehicles and user accounts. Based on the obtained target vehicle information, it performs a matching query in a preset association database to determine the user account corresponding to the target vehicle.

[0021] It should be noted that when a vehicle enters the parking lot, the system collects vehicle information through license plate recognition or radio frequency identification devices and associates the vehicle information with the user account; the same user account can be bound to multiple vehicles, and the relevant binding relationships are pre-stored in the system's association database so that the corresponding user account can be quickly matched when the vehicle leaves the parking lot.

[0022] In step S120, the outstanding fees of all vehicles present under the user account are determined, the total amount to be paid is generated and pushed to the target user; Optionally, after identifying the user account associated with the target vehicle, the system can retrieve all vehicle information bound to that user account from the parking management system and filter out all vehicles currently in the parking lot that have not yet left. For each vehicle, the system calculates the corresponding parking duration and unpaid parking fees based on its entry time, current time, and preset parking fee rules. Then, the system aggregates all unpaid parking fees for all vehicles under that user account, generating a total outstanding fee and a detailed fee statement including the license plate number, entry time, parking duration, and fee for each vehicle. Finally, the total outstanding fee and the complete fee statement are simultaneously pushed to the user's terminal for easy viewing and one-time payment.

[0023] In step S130, after the total amount due is paid, the target vehicle is controlled to leave the premises.

[0024] Optionally, after receiving payment success information from the payment terminal and verifying the payment status of the total outstanding fees, the system determines that all parking fees for all vehicles on site under the user's account have been paid in full. At this point, the system controls the gate at the parking lot exit to open, allowing the target vehicle to leave normally.

[0025] For example, suppose a user registers an account in a parking management system and pre-binds three vehicles: vehicle A, vehicle B, and vehicle C. In a certain scenario, vehicle A and vehicle B enter and park in the parking lot one after the other, while vehicle C does not enter. Vehicle A parks for 2 hours, incurring a parking fee of 10 yuan; vehicle B parks for 3 hours, incurring a parking fee of 15 yuan. When vehicle A reaches the parking lot exit and requests to leave, the system identifies that vehicle A belongs to the aforementioned user account and iterates through all vehicles currently in use under that account, namely vehicles A and B, calculating the unpaid parking fees for both vehicles and summing them up to a total unpaid fee of 25 yuan. After the user completes the payment of the 25 yuan fee via mobile payment, the system confirms the payment success, controls the exit gate to open and allow vehicle A to pass, and simultaneously marks the parking fees for vehicles A and B as paid. Subsequently, when vehicle B requests to leave, the system detects that the parking fee for that vehicle has been paid and directly controls the gate to allow passage, without requiring the user to pay again. By calculating and settling all fees at the time of vehicle departure as described above, it can be ensured that all fees for vehicles under a user's account are fully settled when the vehicle leaves the premises, effectively preventing the accumulation of outstanding fees and reducing the risk of evasion.

[0026] In addition, when vehicle B leaves the parking lot, the system can detect in real time whether vehicle B has continued to park and generated new parking fees since the last fee payment (the new parking fees are calculated based on the last fee payment time as the new entry time). If there are new fees, the user must pay the new fees before the vehicle is released. If no new fees are generated, the vehicle is released directly, further ensuring the completeness and accuracy of parking fee collection.

[0027] In this embodiment of the application, a billing exit control method is provided, comprising: in response to an exit request of a target vehicle, determining a user account associated with the target vehicle; determining the unpaid fees of all vehicles present under the user account, generating a total fee to be paid and pushing it to the target user; and controlling the exit of the target vehicle after the total fee to be paid is completed. In this embodiment, when a target vehicle initiates an exit request, the outstanding parking fees of all vehicles present under the corresponding user account are uniformly calculated and obtained, a total fee to be paid is generated and pushed to the user, and the vehicle is only released after the user has paid in full. This can prevent the problem of continuous accumulation of arrears for other vehicles due to the release of a single vehicle after payment, effectively preventing users from evading payment by taking turns to exit, and ensuring the revenue security of the parking lot operator. At the same time, the operator does not need to carry out a large amount of manual collection of arrears, which greatly reduces the operation and management costs and labor burden, and significantly improves the overall efficiency and standardization of parking fee collection. In addition, the one-time calculation and unified collection method simplifies the user payment process. With clear display of fee details, it not only ensures payment transparency, but also improves the user's parking exit experience and user satisfaction.

[0028] like Figure 2 As shown, in one embodiment of this application, determining the unpaid fees of all vehicles present under the user account, generating the total outstanding fees, and pushing it to the target user includes: In step S210, all vehicle information associated with the user account is queried, and the vehicles present are filtered out. In step S220, the unpaid fees for each vehicle on site are calculated according to the pre-design fee rules; In step S230, the unpaid fees of all vehicles present are summarized to generate the total unpaid fees and fee details. The fee details include the license plate number, entry time and unpaid amount of each vehicle present. In step S240, the total amount due and fee details are pushed to the target user.

[0029] Optionally, after determining the user account associated with the target vehicle, a preset vehicle-account association database can be invoked. Using the unique identifier of the user account (such as user ID or bound mobile phone number), all vehicle information that has been pre-associated and bound under that account can be queried and retrieved. The vehicle information includes the license plate number, vehicle identification number, binding time, and other information for each vehicle. Then, the system can interact with the parking lot entrance and exit detection system and the vehicle status management module to filter out vehicles that are currently parked in the parking lot, have not yet triggered the exit detection, or have not completed payment settlement, while excluding vehicles that have left the parking lot, have paid, or are in an abnormal state, ensuring the accuracy of the selection of vehicles in the parking lot.

[0030] After filtering out all vehicles present, the system calculates the unpaid fees (such as parking fees, charging fees, etc.) for each vehicle according to the parking lot's pre-set billing rules. These pre-set rules can be set according to the parking lot's operational needs, such as hourly billing (e.g., 5 yuan for the first hour and 3 yuan for each subsequent hour), per-use billing, and peak-hour surcharge billing. The system automatically retrieves the actual entry time of each vehicle and combines it with the current real-time time (if the vehicle has not initiated an exit request, the current system time is used as the calculation node; if the vehicle has initiated an exit request, the exit detection time is used as the calculation node) to calculate the actual parking time of each vehicle. Then, the system calculates the unpaid parking fees for each vehicle according to the billing rules and records the basis for fee calculation to ensure transparency and traceability of fee calculation.

[0031] After calculating the outstanding fees for each vehicle present, the system aggregates all outstanding fees for all vehicles under the user's account, summing them up to obtain the total outstanding fees. Simultaneously, a detailed fee breakdown is automatically generated, clearly listing the core information of each vehicle, including but not limited to license plate number, actual entry time, current calculated parking duration, outstanding amount per vehicle, and fee calculation rules. This allows users to clearly verify the source of each fee. Finally, the total outstanding fees and complete fee breakdown are simultaneously pushed to the target user through pre-bound push channels, such as the user's linked mobile app, SMS, and parking lot exit display pop-ups. The push message also includes a payment entry link or payment operation instructions, allowing users to quickly view fee details and complete the payment process. This ensures users are promptly informed of the total amount and details to be paid, improving payment convenience.

[0032] like Figure 3 As shown in one embodiment of this application, calculating the unpaid fees for each vehicle present according to the pre-design fee rules includes: In step S310, the entry time and parking duration of each vehicle on site are determined; In step S320, if the entry time is abnormal or the parking time exceeds the preset parking time threshold, the unpaid fees for the corresponding vehicle are marked as abnormal fees. In step S330, when generating the total amount to be paid, the vehicle information and reason for the abnormal fee are marked separately and pushed to the target user and the parking lot management terminal. In step S340, if the abnormal fee is confirmed to be correct, the abnormal fee is treated as the unpaid fee. In step S350, if it is confirmed that the abnormal fee is incorrect, the abnormal fee is corrected and the corrected fee is used as the unpaid fee.

[0033] Optionally, the entry records of each vehicle in the parking lot are retrieved, and the accurate entry time of the vehicle is obtained from the parking lot entry detection system. Combined with the real-time time of the current accounting node (if the vehicle has initiated an exit request, the exit detection time is used; if no exit request has been initiated, the current system time is used), the actual parking time of each vehicle in the parking lot is calculated by the time difference. Then, the entry time and parking time of each vehicle in the parking lot can be checked for anomalies. Preset entry time anomaly scenarios include empty entry time, entry time later than the current accounting time, and duplicate entry time. The preset parking time threshold can be set according to the parking lot operation needs (e.g., 72 hours, i.e., 3 days). If the entry time of a vehicle in the parking lot has the above-mentioned anomalies, or the actual parking time exceeds the preset parking time threshold, the system will automatically mark the unpaid fees of the vehicle as abnormal fees, and record the preliminary reason for the anomaly (e.g., "abnormal entry time, no valid entry record detected" or "parking time exceeds the threshold of 72 hours, suspected abnormal parking"). When all unpaid fees from vehicles on site are aggregated to generate the total outstanding fees, vehicles marked as having abnormal fees will be individually flagged. The fee details will clearly list the vehicle's license plate number, entry time, calculated parking duration, initial abnormal fee amount, and specific reason for the abnormality. At the same time, the relevant information on the abnormal fees will be pushed to the target user (through the user's linked mobile APP, SMS, etc.) and the parking lot management terminal, making it convenient for users to verify the abnormality and for management to intervene and investigate in a timely manner. Meanwhile, the system verifies and confirms any marked abnormal charges: If the user reports that the abnormal charge is correct, or if the parking lot management verifies that the abnormal charge is a normal occurrence by reviewing entry monitoring and vehicle parking records (e.g., the user has indeed parked for an extended period exceeding the threshold, or the entry time error has been verified), then the system confirms that the abnormal charge is correct and includes it in the total outstanding charges along with other normal unpaid charges. If the user reports that the abnormal charge is incorrect, or if the management verifies that there is indeed an anomaly (e.g., an incorrect entry time, or a malfunction in the detection equipment causing a deviation in the calculation of parking duration), then the system corrects the abnormal charge based on the verification results. After correction, the system recalculates the vehicle's unpaid charges and uses the corrected charge as the vehicle's final unpaid charges, including it in the total outstanding charges along with other normal unpaid charges.

[0034] like Figure 4 As shown in one embodiment of this application, generating the total amount to be paid and pushing it to the target user includes: In step S410, it is determined whether the user account has any historical arrears. In step S420, if the user account has historical arrears, the historical arrears amount is combined with the total amount due to generate a combined ... In step S430, the total outstanding fees and details of the merged fees are pushed to the target user. The details of the merged fees distinguish between historical arrears and current outstanding fees.

[0035] Optionally, before generating the total outstanding fee for this trip, the system first checks the user's payment and arrears records to determine if the user's account has any historical arrears. If an outstanding historical arrears are detected, the outstanding historical arrears are combined with the total outstanding fee calculated this time to generate a combined total outstanding fee. Then, the combined total outstanding fee is pushed to the target user, along with a clearly distinguished detailed breakdown of the combined fee. This breakdown lists the historical arrears, the amount due this time, and the corresponding vehicle and parking information, making it easy for the user to clearly check and complete the payment of all fees at once.

[0036] like Figure 5 As shown in one embodiment of this application, determining the user account associated with the target vehicle includes: In step S510, the vehicle information of the target vehicle is obtained, and the vehicle information includes at least one of the license plate number and vehicle identification number; In step S520, based on the preset association between vehicles and user accounts, the corresponding user account is queried and determined according to the vehicle information of the target vehicle. In step S530, if no associated user account is found, the user information associated with the target vehicle is queried from the current parking lot management system, and the user information is used to query whether there are other bound vehicles among the vehicles in the parking lot.

[0037] Optionally, when a target vehicle reaches the parking lot exit lane and triggers an exit request, the system first obtains the vehicle information of the target vehicle through the identification equipment deployed at the exit. This vehicle information includes at least one of the following: license plate number and vehicle identification number (VIN). The license plate number can be captured and identified in real time by a high-definition license plate recognition camera to ensure clear capture of the vehicle license plate information and avoid recognition errors caused by obstruction or blurring. The vehicle identification number can be obtained by reading the vehicle's own electronic tag through a radio frequency identification device (such as an RFID card reader or ETC on-board unit reader), or by retrieving the vehicle identification number information collected and stored when entering the parking lot. After obtaining the target vehicle's information, a pre-set database of vehicle-user account associations can be accessed. This database is uniformly maintained by the parking lot management system and pre-stores the one-to-one correspondence between all vehicle information (license plate number, vehicle identification number) bound to user accounts during registration and user accounts. It also records auxiliary information such as vehicle binding time and binding status for easy and quick query matching. The system precisely compares the acquired target vehicle information with the vehicle information stored in the database. If a complete match is found, the corresponding user account is identified as the user account associated with the target vehicle. The system can also simultaneously retrieve the user account's basic information (such as user ID and linked mobile phone number) to facilitate payment push operations. If, after multiple rounds of comparison and querying, no matching user account is found in the association database, the system immediately triggers a fallback query mechanism. This mechanism retrieves the user information associated with the target vehicle from the current parking lot management system. This user information may include the mobile phone number recorded when the vehicle entered the parking lot via self-service payment machine, QR code registration, manual registration, temporary entry registration information, or registration information associated with captured images of the vehicle entering the parking lot, access passes (such as paper parking tickets or electronic entry codes), ensuring accurate identification of the actual user or registrant of the target vehicle. Furthermore, the system checks whether there are other linked vehicles among the vehicles present based on this user information. If other vehicles associated with the user's information are found, the target vehicle and these vehicles can be grouped together under the temporary billing entity corresponding to the user's information. The outstanding fees for all vehicles will be aggregated, and a total outstanding fee and details will be generated. This information will be sent to the contact information associated with the user's information via SMS, on-site display screen, or other means. If no other vehicles associated with the user's information are found, the outstanding fees will be calculated separately for the target vehicle, and a payment reminder will be sent. The user will also be prompted to complete the temporary payment on-site or quickly bind their user account for subsequent unified management of multiple vehicles.

[0038] In addition, if the user account cannot be found, account association prompts (including association operation instructions) can be pushed to the target user through various channels. These channels may include pop-up windows on the parking lot exit display screen, voice broadcasts, and temporary SMS notifications (obtaining the user's mobile phone number by scanning a QR code on-site). This ensures that the user can receive prompts in a timely manner and understand the operation method. At the same time, the system suspends the exit process of the current target vehicle and keeps the exit gate closed until the user completes the association and binding operation between the target vehicle and the user account according to the prompts. After the system detects that the association is successful, the exit process is resumed, and subsequent fee calculation, release, and other related steps are executed. This ensures that every exiting vehicle can be accurately associated with the corresponding user account, guaranteeing a smooth and orderly toll collection process.

[0039] like Figure 6 As shown in one embodiment of this application, controlling the target vehicle to leave the premises after the total outstanding fees have been paid includes: In step S610, the payment result fed back by the payment terminal is obtained, the payment result is verified, and it is confirmed whether the total amount to be paid has been paid in full. In step S620, if the payment verification is successful, the billing status of all vehicles on site under the user account is updated, and the unpaid fees are marked as paid in full. In step S630, the control gate is opened to allow the target vehicle to exit; In step S640, after the target vehicle has completely left the exit detection area, the control gate is closed and the status of the target vehicle is updated to the exit status.

[0040] Optionally, the system can obtain payment results from the payment terminal in real time, perform consistency verification on the payment amount, payment status, and user account information, and confirm whether the total amount due has been successfully paid by the user. If the verification confirms successful payment and correct amount, the system will uniformly update the billing status of all vehicles on site under the user account, batch mark the unpaid parking fees for each vehicle as paid, and simultaneously record the payment time and payment voucher. Then, the system will send an opening command to the parking lot exit gate controller to control the gate to lift and allow the target vehicle to exit normally. When the ground sensor or video detection device in the gate area detects that the target vehicle has completely left the exit detection area, the system will immediately control the gate to automatically close and update the on-site status of the target vehicle to the exit status, completing the complete exit and settlement process.

[0041] In one embodiment of this application, the method further includes: If the total amount due is not paid within the first preset time, or if the payment verification fails, a payment reminder and an error handling prompt will be sent to the target user. If the target user abandons payment or fails to make payment within a second preset time, the exit process of the target vehicle will be suspended. Generate the outstanding payment information for the target vehicle and record the outstanding payment information to the user account.

[0042] Optionally, after pushing the total amount due and fee details to the target user, a payment timer is simultaneously started to monitor the user's payment operation in real time. The first preset time can be reasonably set according to the parking lot operation needs, such as 15 minutes, to limit the effective time for the user to complete the payment. If the system detects that the user has not completed the payment operation within the first preset time since the total amount due was pushed, or if the payment result fed back by the payment terminal (such as a mobile payment platform or parking lot payment terminal) after multiple rounds of verification is determined to be a payment failure (including situations such as the payment amount not matching the total amount due, insufficient payment account balance, payment network abnormality, invalid payment voucher, etc.), the system will immediately activate the payment reminder mechanism.

[0043] Clear payment reminders and error handling prompts are sent to target users through pre-bound push channels. The payment reminders explicitly inform users that "the payment has timed out and you should complete the payment as soon as possible." The error handling prompts provide corresponding guidance for different payment failure scenarios, such as "Payment amount does not match, please check the total amount due and pay again," "Insufficient account balance, please change the payment method or recharge and try again," and "Payment network error, please check the network connection and re-initiate the payment." Push channels may include pop-ups in the user's bound parking lot APP, SMS notifications, voice broadcasts in the exit lane, and scrolling prompts on the display screen, ensuring that users can receive reminder information in a timely manner, quickly understand the cause of the error and the solution, and guide users to complete the payment smoothly.

[0044] If, after viewing the reminder, the target user actively confirms their intention to forgo payment via the app, on-site terminal, or by contacting parking lot management personnel, or if the system continues to wait for the second preset time (which can be set to 10 minutes, connecting with the first preset time, with the total payment time not exceeding 25 minutes to avoid occupying exit lane resources), and the user still has not completed the payment operation or the payment verification has still failed, the exit process for the current target vehicle will be immediately suspended, the parking lot exit gate will be kept closed, and the user will be informed via voice broadcast and display screen that "Payment not completed, exit is temporarily unavailable. Please complete the payment before proceeding with the exit procedures" to prevent the vehicle from leaving illegally.

[0045] At the same time, the system automatically generates the outstanding payment information for the target vehicle. The outstanding payment information records the following core information in detail: the target vehicle's license plate number, vehicle identification number, entry time of this parking, parking duration, outstanding amount, time of outstanding payment, and reason for outstanding payment (such as "payment timeout", "payment verification failed and payment not re-submitted", "user voluntarily waives payment"). The system accurately links this outstanding payment information to the corresponding target user's account, updates the user's account's outstanding payment record synchronously, marks the outstanding payment as unsettled, and stores it in the user's account's historical outstanding payment ledger. This allows the system to automatically query the historical outstanding payment when any vehicle under the user's account initiates an exit request in the future, and combine it with the current outstanding payment for accounting purposes. This ensures that outstanding payments can be collected in a timely manner, protects the revenue security of the parking lot operator, and standardizes the abnormal handling process for parking fees.

[0046] In this embodiment, when a target vehicle initiates an exit request, the outstanding parking fees of all vehicles present under the corresponding user account are uniformly calculated and obtained, a total fee to be paid is generated and pushed to the user, and the vehicle is only released after the user has paid in full. This can prevent the problem of other vehicles accumulating unpaid fees due to the release of a single vehicle after payment from the source, effectively preventing users from evading fees by taking turns to exit, and ensuring the revenue security of the parking lot operator. At the same time, the operator does not need to carry out a large amount of manual collection of unpaid fees, which greatly reduces the operation and management costs and labor burden, and significantly improves the overall efficiency and standardization of parking fee collection. In addition, the one-time calculation and unified collection method simplifies the user payment process. With clear display of fee details, it not only ensures payment transparency, but also improves the user's parking exit experience and user satisfaction.

[0047] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0048] In one embodiment, a billing exit control device is provided, which corresponds one-to-one with the billing exit control method described in the above embodiments. For example... Figure 7 As shown, the billing and exit control device includes a user account determination unit 10, a total outstanding fee determination unit 20, and a vehicle exit control unit 30. Detailed descriptions of each functional module are as follows: User account determination unit 10 is used to determine the user account associated with the target vehicle in response to the vehicle's exit request; The total outstanding fees determination unit 20 is used to determine the unpaid fees of all vehicles present under the user account, generate the total outstanding fees, and push them to the target user. The vehicle exit control unit 30 is used to control the exit of the target vehicle after the total outstanding fees have been paid.

[0049] In one embodiment of this application, the total fee to be paid determination unit 20 is further configured to: Query all vehicle information associated with the user account and filter out the vehicles present. Calculate the unpaid fees for each vehicle present, according to the pre-design fee rules; The outstanding fees of all vehicles present are summarized to generate the total outstanding fees and fee details. The fee details include the license plate number, entry time and outstanding amount of each vehicle present. The total amount due and fee details will be sent to the target user.

[0050] In one embodiment of this application, the total fee to be paid determination unit 20 is further configured to: Determine the entry time and parking duration for each vehicle on site; If the entry time is abnormal or the parking time exceeds the preset parking time threshold, the unpaid fees for the corresponding vehicle will be marked as abnormal fees. When generating the total amount due, the vehicle information and reason for the abnormal fee are marked separately and pushed to the target user and the parking lot management terminal. If the abnormal fee is confirmed to be correct, the abnormal fee will be treated as the unpaid fee. If the abnormal fee is confirmed to be incorrect, the abnormal fee will be corrected, and the corrected fee will be treated as the unpaid fee.

[0051] In one embodiment of this application, the total fee to be paid determination unit 20 is further configured to: Determine if the user account has any historical arrears. If the user account has historical arrears, the historical arrears amount will be combined with the total amount due to generate a combined total amount due to pay. The system pushes the total outstanding fees and details of the consolidated fees to the target user, with the details of the consolidated fees distinguishing between historical arrears and the current outstanding amount.

[0052] In one embodiment of this application, the user account determination unit 10 is further configured to: Obtain vehicle information of the target vehicle, wherein the vehicle information includes at least one of license plate number and vehicle identification number; Based on the preset association between vehicles and user accounts, the corresponding user account is queried and determined according to the vehicle information of the target vehicle. If no associated user account is found, the system will query the user information associated with the target vehicle from the current parking lot management system, and then query whether there are any other bound vehicles among the vehicles in the parking lot based on the user information.

[0053] In one embodiment of this application, the vehicle exit control unit 30 is further configured to: Obtain the payment result from the payment terminal, verify the payment result, and confirm whether the total amount due has been paid in full. If the payment verification is successful, the billing status of all vehicles on site under the user account will be updated, and the unpaid fees will be marked as paid. The control gate is opened to allow the target vehicle to exit; Once the target vehicle has completely left the exit detection area, the control gate closes and the target vehicle's status is updated to "departure status".

[0054] In one embodiment of this application, the device further includes an exception handling unit, used for: If the total amount due is not paid within the first preset time, or if the payment verification fails, a payment reminder and an error handling prompt will be sent to the target user. If the target user abandons payment or fails to make payment within a second preset time, the exit process of the target vehicle will be suspended. Generate the outstanding payment information for the target vehicle and record the outstanding payment information to the user account.

[0055] In this embodiment, under the multi-vehicle, multi-location charging model, the principle of "whoever exits pays" forces the exiting vehicle to pay all outstanding fees owed by related vehicles present. Vehicles are only released after full payment by the user, preventing the accumulation of unpaid fees for other vehicles due to payment by a single vehicle. This effectively prevents users from evading payment through multiple vehicles exiting in turn, ensuring the revenue security of the parking lot operator. Furthermore, it eliminates the need for extensive manual collection of outstanding fees, significantly reducing operational and management costs and manpower burden, and substantially improving the overall efficiency and standardization of parking fee collection. In addition, the one-time calculation and unified collection method simplifies the user payment process, and the clear display of fee details ensures payment transparency and enhances the user's parking exit experience and satisfaction.

[0056] Specific limitations regarding the billing exit control device can be found in the limitations of the billing exit control method described above, and will not be repeated here. Each module in the aforementioned billing exit control device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of each module.

[0057] In one embodiment, a computer device is provided, which may be a terminal device, and its internal structure diagram may be as follows: Figure 8 As shown, the computer device includes a processor, memory, and network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes a readable storage medium storing computer-readable instructions. The network interface communicates with external terminals via a network connection. When executed by the processor, the computer-readable instructions implement a billing and exit control method. The readable storage medium provided in this embodiment includes both non-volatile and volatile readable storage media.

[0058] In this application embodiment, a computer device is provided, including a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor. When the processor executes the computer-readable instructions, it implements the steps of the billing and exit control method described above.

[0059] In this embodiment of the application, a readable storage medium is provided, which stores computer-readable instructions. When the computer-readable instructions are executed by a processor, they implement the steps of the billing and departure control method described above.

[0060] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing related hardware with computer-readable instructions. These computer-readable instructions can be stored in a non-volatile readable storage medium or a volatile readable storage medium. When executed, these computer-readable instructions can include the processes of the embodiments of the methods described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0061] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to 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.

[0062] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A billing and exit control method, characterized in that, The method includes: In response to a request for the target vehicle to be dispatched, the user account associated with the target vehicle is determined; Identify all outstanding fees for vehicles present under the user's account, generate the total outstanding fees, and push them to the target user; Once the total outstanding fees have been paid, the target vehicle is controlled to leave the premises.

2. The billing and exit control method as described in claim 1, characterized in that, The process of determining the outstanding fees for all vehicles present under the user account, generating the total outstanding fees, and pushing it to the target user includes: Query all vehicle information associated with the user account and filter out the vehicles present. Calculate the unpaid fees for each vehicle present, according to the pre-design fee rules; The outstanding fees of all vehicles present are summarized to generate the total outstanding fees and fee details. The fee details include the license plate number, entry time and outstanding amount of each vehicle present. The total amount due and fee details will be sent to the target user.

3. The billing and exit control method as described in claim 2, characterized in that, The calculation of unpaid fees for each vehicle present, according to the pre-design fee rules, includes: Determine the entry time and parking duration for each vehicle on site; If the entry time is abnormal or the parking time exceeds the preset parking time threshold, the unpaid fees for the corresponding vehicle will be marked as abnormal fees. When generating the total amount due, the vehicle information and reason for the abnormal fee are marked separately and pushed to the target user and the parking lot management terminal. If the abnormal fee is confirmed to be correct, the abnormal fee will be treated as the unpaid fee. If the abnormal fee is confirmed to be incorrect, the abnormal fee will be corrected, and the corrected fee will be treated as the unpaid fee.

4. The billing and exit control method as described in any one of claims 1-3, characterized in that, The process of generating the total amount due and sending it to the target user includes: Determine if the user account has any historical arrears. If the user account has historical arrears, the historical arrears amount will be combined with the total amount due to generate a combined total amount due to pay. The system pushes the total outstanding fees and details of the consolidated fees to the target user, with the details of the consolidated fees distinguishing between historical arrears and the current outstanding amount.

5. The billing and exit control method as described in claim 1, characterized in that, The process of determining the user account associated with the target vehicle includes: Obtain vehicle information of the target vehicle, wherein the vehicle information includes at least one of license plate number and vehicle identification number; Based on the preset association between vehicles and user accounts, the corresponding user account is queried and determined according to the vehicle information of the target vehicle. If no associated user account is found, the system will query the user information associated with the target vehicle from the current parking lot management system, and then query whether there are any other bound vehicles among the vehicles in the parking lot based on the user information.

6. The billing and exit control method as described in claim 1, characterized in that, The step of controlling the target vehicle to leave the premises after the total outstanding fees have been paid includes: Obtain the payment result from the payment terminal, verify the payment result, and confirm whether the total amount due has been paid in full. If the payment verification is successful, the billing status of all vehicles on site under the user account will be updated, and the unpaid fees will be marked as paid. The control gate is opened to allow the target vehicle to exit; Once the target vehicle has completely left the exit detection area, the control gate closes and the target vehicle's status is updated to "departure status".

7. The billing and exit control method as described in claim 1, characterized in that, The method further includes: If the total amount due is not paid within the first preset time, or if the payment verification fails, a payment reminder and an error handling prompt will be sent to the target user. If the target user abandons payment or fails to make payment within a second preset time, the exit process of the target vehicle will be suspended. Generate the outstanding payment information for the target vehicle and record the outstanding payment information to the user account.

8. A billing and exit control device, characterized in that, The device includes: The user account determination unit is used to determine the user account associated with the target vehicle in response to the vehicle's dispatch request. The unit for determining total outstanding fees is used to determine the unpaid fees of all vehicles present under the user account, generate the total outstanding fees, and push them to the target user. The vehicle exit control unit is used to control the exit of the target vehicle after the total outstanding fees have been paid.

9. A computer device comprising a memory, a processor, and computer-readable instructions stored in the memory and running on the processor, characterized in that, When the processor executes the computer-readable instructions, it implements the billing exit control method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing computer-readable instructions thereon, characterized in that, When the computer-readable instructions are executed by the processor, they implement the billing exit control method as described in any one of claims 1 to 7.

Images