License plate data exception processing method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention discloses a license plate data exception processing method and device, electronic equipment and a storage medium, and the method comprises the steps: receiving deduction feedback information, responding to the received deduction feedback information, obtaining a license plate set bound with a user to which a target vehicle belongs, determining push information according to the license plate set, and transmitting the push information. And re-executing the parking fee reduction and remission process according to the push information. Therefore, in the embodiment, when the parking fee generated by charging cannot be reduced due to the fact that the license plate data is abnormal, the push information is determined, and the parking fee reduction process is executed again according to the push information, so that the parking fee reduction failure caused by the license plate data abnormity can be reduced, and the charging experience of a user is improved.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and specifically to a method, apparatus, electronic device, and storage medium for handling abnormal license plate data. Background Technology

[0002] In the parking fee reduction service provided by new energy charging stations, the charging operators will open the gates of each charging station and identify the vehicle when it leaves the charging station after charging. The operators will then implement parking fee reduction strategies (such as limited-time free parking or free parking all day) based on the vehicle's charging status.

[0003] However, in practical applications, when a vehicle leaves a charging station after charging, it may fail to receive a parking fee reduction due to abnormal license plate data, making it unable to exit smoothly. In addition, users may be unable to enjoy the reduction, resulting in a poor charging experience and an increased complaint rate. Summary of the Invention

[0004] In view of this, the purpose of this invention is to provide a method for handling abnormal license plate data, so as to reduce the failure of parking fee reduction due to abnormal license plate data and improve the user charging experience.

[0005] In a first aspect, embodiments of the present invention aim to provide a method for handling abnormal license plate data, the method comprising:

[0006] Receive reduction feedback information, which indicates that the target vehicle cannot be exempted from parking fees incurred during charging due to abnormal license plate data;

[0007] In response to receiving the exemption feedback information, obtain the set of license plates bound to the user to which the target vehicle belongs, the set of license plates including at least one license plate;

[0008] The push information is determined based on the set of license plates;

[0009] Send the push notification to re-execute the parking fee reduction process based on the push notification.

[0010] Furthermore, the push information is the license plate information corresponding to the license plates in the license plate set, and sending the push information includes:

[0011] The license plate information corresponding to the license plates in the set of license plates is pushed according to the preset push order.

[0012] Furthermore, the step of pushing the license plate information corresponding to the license plates in the license plate set according to the preset push order includes:

[0013] The push order is determined based on the attribute information of each license plate in the license plate set, wherein the attribute information includes the binding time and / or the number of bindings;

[0014] The license plate information corresponding to each license plate in the license plate set is pushed out in the specified push order.

[0015] Furthermore, determining the push information based on the license plate set includes:

[0016] Obtain replacement information, which is generated based on the historical license plate exemption records. The historical license plates include license plates in the license plate set and / or other license plates outside the license plate set.

[0017] Modify the license plate information corresponding to the license plates in the license plate set according to the replacement information;

[0018] The modified license plate information will be used as the push notification.

[0019] Furthermore, obtaining the replacement information includes:

[0020] If the parking fee reduction process fails after executing the process based on the license plate information corresponding to the license plate in the license plate set, replacement information is obtained.

[0021] Furthermore, the replacement information is generated using the following method:

[0022] Based on the historical license plate exemption records, each of the historical license plates is filtered to determine at least one target license plate, which is the license plate that has successfully been exempted after the license plate information has been modified;

[0023] Replacement information is generated based on the license plate information before and after the modification of each target license plate.

[0024] Furthermore, the method also includes:

[0025] In response to the successful exemption of the target vehicle, a reminder message is sent to the user to whom the target vehicle belongs, prompting the user to change the currently bound license plate information to the license plate information corresponding to the time of the successful exemption.

[0026] Secondly, embodiments of the present invention aim to provide a method for handling abnormal license plate data, the method comprising:

[0027] Send a reduction feedback message, which indicates that the target vehicle cannot be exempted from parking fees incurred during charging due to abnormal license plate data.

[0028] Receive push notifications, the push notifications being determined based on the set of license plates bound to the user to which the target vehicle belongs;

[0029] The parking fee reduction process will be re-executed based on the push notification information.

[0030] Thirdly, embodiments of the present invention aim to provide a license plate data anomaly processing system, the system comprising:

[0031] The linkage system is configured to receive and push charging record information of a target vehicle, receive parking fee reduction feedback information, and in response to receiving the parking fee reduction feedback information, obtain the set of license plates bound to the user to which the target vehicle belongs, determine push information based on the set of license plates, and send the push information to re-execute the parking fee reduction process based on the push information; wherein, the parking fee reduction feedback information is used to indicate that the target vehicle cannot reduce the parking fees incurred due to abnormal license plate data, and the set of license plates includes at least one license plate.

[0032] The parking management system is configured to execute a parking fee reduction process based on the recorded information and a preset reduction method, send the reduction feedback information, and, in response to receiving the push information, re-execute the parking fee reduction process based on the push information.

[0033] Fourthly, embodiments of the present invention aim to provide a license plate data anomaly processing device, the device comprising:

[0034] A receiving unit is used to receive reduction feedback information, which indicates that the target vehicle cannot be exempted from parking fees incurred during charging due to abnormal license plate data.

[0035] The processing unit is configured to, in response to receiving the exemption feedback information, obtain the set of license plates bound to the user to which the target vehicle belongs, and determine the push information based on the set of license plates, wherein the set of license plates includes at least one license plate;

[0036] The sending unit is used to send the push information to re-execute the parking fee reduction process based on the push information.

[0037] Fifthly, embodiments of the present invention aim to provide a license plate data anomaly processing device, the device comprising:

[0038] An interaction unit is used to send a fee reduction feedback message and receive push notifications; wherein, the fee reduction feedback message is used to indicate that the target vehicle cannot be exempted from parking fees incurred during charging due to abnormal license plate data; the push notifications are determined based on the set of license plates bound to the user to which the target vehicle belongs;

[0039] The execution unit is used to re-execute the parking fee reduction process based on the pushed information.

[0040] Sixthly, embodiments of the present invention aim to provide a computer program product, the computer program product including a computer program / instruction, which, when executed by a processor, implements the method as described in any of the preceding claims.

[0041] In a seventh aspect, embodiments of the present invention aim to provide an electronic device, including a memory and a processor, the memory being used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method as described in any of the preceding claims.

[0042] Eighthly, embodiments of the present invention aim to provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in any of the preceding claims.

[0043] The technical solution of this invention obtains the set of license plates bound to the user of the target vehicle when abnormal license plate data prevents the reduction of parking fees incurred during charging. Based on the set of license plates, push information is determined, so that when abnormal license plate data prevents the reduction of parking fees incurred during charging, the parking fee reduction process can be re-executed based on the push information. This reduces the failure of parking fee reduction due to abnormal license plate data and improves the user charging experience. Attached Figure Description

[0044] The above and other objects, features and advantages of the present invention will become clearer from the following description of embodiments of the invention with reference to the accompanying drawings, in which:

[0045] Figure 1 This is a schematic diagram of the license plate data anomaly processing system according to an embodiment of the present invention;

[0046] Figure 2 This is a flowchart of the license plate data anomaly handling method according to an embodiment of the present invention;

[0047] Figure 3 This is a flowchart illustrating the process of determining push information according to an embodiment of the present invention;

[0048] Figure 4 This is a flowchart illustrating the generation of replacement information according to an embodiment of the present invention;

[0049] Figure 5 This is a schematic diagram illustrating the determination of push information according to an embodiment of the present invention;

[0050] Figure 6 This is a flowchart of the license plate data anomaly handling method according to an embodiment of the present invention;

[0051] Figure 7 This is a flowchart illustrating the parking fee reduction process when license plate data is abnormal, according to an embodiment of the present invention.

[0052] Figure 8 This is a schematic diagram of the license plate data anomaly processing device according to an embodiment of the present invention;

[0053] Figure 9 This is another schematic diagram of the license plate data anomaly processing device according to an embodiment of the present invention;

[0054] Figure 10 This is a schematic diagram of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0055] The present application is described below based on embodiments, but it is not limited to these embodiments. In the detailed description of the present application below, certain specific details are described in detail. Those skilled in the art can fully understand the present application without these details. To avoid obscuring the substance of the present application, well-known methods, processes, flows, elements, and circuits are not described in detail.

[0056] Furthermore, those skilled in the art should understand that the accompanying drawings provided herein are for illustrative purposes only and are not necessarily drawn to scale.

[0057] Unless the context explicitly requires it, words such as "including" or "contains" throughout the application should be interpreted as including rather than exclusive or exhaustive; that is, meaning "including but not limited to".

[0058] In the description of this application, it should be understood that the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Furthermore, in the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0059] In accordance with the present invention and the embodiments, if information acquisition is involved, data will be collected in a legal and compliant manner to ensure the legality of the data source, and appropriate technical and management measures will be taken to ensure data security.

[0060] The solutions described in this specification and embodiments, if involving the processing of personal information, will be processed only on the premise of having a legal basis (such as obtaining the consent of the personal information subject, or being necessary for the performance of a contract), and will only be processed within the scope stipulated or agreed upon. A user's refusal to process personal information beyond what is necessary for basic functions will not affect the user's use of basic functions.

[0061] Figure 1 This is a schematic diagram of a license plate data anomaly processing system according to an embodiment of the present invention. Figure 1As shown in the diagram, the license plate data anomaly handling system in this embodiment includes a linkage system 10 and a parking management system 20. In actual use, users typically bind vehicle information to charging software (including charging apps, mini-programs, etc.) on their terminal devices as a basis for parking fee reduction. When a vehicle needing charging enters the charging station, the parking management system 20 controls the barrier gate system to identify the vehicle. After recognizing the vehicle's license plate information (such as the license plate identifier, i.e., the license plate number), the barrier gate opens, allowing the vehicle to enter the charging station, where the charging piles will charge the vehicle. During the charging process, the charging piles will send the vehicle's charging record information to the linkage system 10, so that the linkage system can reduce the parking fee incurred by the corresponding vehicle in the charging station based on the charging record information. After the vehicle finishes charging, the user initiates a parking fee reduction request through the terminal device. After receiving the parking fee reduction request, the linkage system 10 sends the vehicle's charging record information to the parking management system 20. When a vehicle leaves the charging station, the parking management system 20 re-identifies the vehicle's license plate and determines the actual parking fee based on the vehicle's charging record information, the time the vehicle entered and exited the charging station, and a preset fee reduction method (i.e., preset parking fee reduction rules). After the user pays the actual parking fee, the parking management system 20 controls the gate system to allow the vehicle to pass. Therefore, through the coordinated operation between the linkage system and the parking management system, this embodiment can provide charging services to users, meet their charging needs, and reduce parking fees based on vehicle charging record information, thereby improving the utilization rate of the charging station and the user's charging experience.

[0062] Meanwhile, in cases where users fail to receive parking fee reductions due to errors in binding vehicle information, recognition errors in the parking management system, or license plate recognition errors caused by network anomalies, this embodiment will also handle parking fee reduction anomalies caused by license plate data anomalies through interaction between the linkage system and the parking management system. This will reduce parking fee reduction failures caused by license plate data anomalies and improve the user's charging experience.

[0063] Correspondingly, the linkage system in this embodiment is configured to receive and push charging record information of the target vehicle, receive fee reduction feedback information, and in response to receiving the fee reduction feedback information, obtain the set of license plates bound to the user to which the target vehicle belongs, determine push information based on the license plate set, and send the push information to re-execute the parking fee reduction process based on the push information. The parking management system is configured to execute the parking fee reduction process based on the record information and the preset reduction method, send the fee reduction feedback information, and in response to receiving the push information, re-execute the parking fee reduction process based on the push information. The fee reduction feedback information indicates that the target vehicle cannot receive a parking fee reduction due to abnormal license plate data, and the license plate set includes at least one license plate. Therefore, this embodiment can provide users with parking fee reduction services during charging through the interaction between the charging management system, the linkage system, and the parking management system. Furthermore, when parking fees incurred during charging cannot be reduced due to abnormal license plate data, a push notification is generated and the parking fee reduction process is re-executed based on the notification. This allows for another opportunity to reduce fees without human intervention and automatically handles parking fee reduction failures caused by abnormal license plate data, thereby reducing such failures and improving the user charging experience.

[0064] Below, this embodiment will explain the data processing method for abnormal license plate data from two different perspectives: the linkage system and the parking management system.

[0065] Figure 2 This is a flowchart of a license plate data anomaly handling method according to an embodiment of the present invention. Figure 2 As shown in the figure, the license plate data anomaly handling method in this embodiment is applied to the linkage system, and the parking fees generated by charging are reduced or waived in the event of license plate data anomalies through the following steps.

[0066] In step S210, feedback information on the reduction or exemption is received.

[0067] In this embodiment, the fee reduction feedback information is used to indicate that the target vehicle cannot be exempted from parking fees incurred during charging due to abnormal license plate data. Optionally, the fee reduction feedback information in this embodiment includes the identification information and fee reduction information corresponding to the target vehicle. The identification information includes charging order identification, user identification, license plate identification, charging station identification, gate identification, etc. The fee reduction information includes the fee reduction request time, fee reduction result, etc.

[0068] Optionally, if the parking management system fails to recognize the license plate information or the recognized license plate information does not match the vehicle information in the received charging record information, and it is determined that the target vehicle cannot be exempted from parking fees due to abnormal license plate data, the parking management system will send exemption feedback information to the linkage system. This will allow the linkage system to know that the vehicle exemption failed due to abnormal license plate data, and re-trigger the parking fee exemption process based on the received exemption feedback information, thus providing an opportunity for vehicle parking fee exemption, reducing parking fee exemption failures caused by abnormal license plate data, and improving the user charging experience.

[0069] Alternatively, the feedback information received in this embodiment can also be sent by the user terminal. For example, if a fee reduction appeal portal is provided on the user terminal device, the user can send fee reduction feedback information to the linkage system through the appeal portal after the first parking fee reduction fails. Therefore, sending fee reduction feedback information to the linkage system through the user terminal device allows the linkage system to be aware of the vehicle's fee reduction failure and re-trigger the parking fee reduction process based on the received feedback information. This reduces parking fee reduction failures caused by abnormal license plate data and increases the interactivity between the license plate data anomaly handling system in this embodiment and the user, further improving the user's charging experience.

[0070] Furthermore, to avoid excessive repetition of the parking fee reduction process, which could lead to long queues and congestion at the station exit, this embodiment will, upon receiving the reduction feedback information, first determine whether the parking fee reduction process has been effectively triggered and then proceed with subsequent processing steps if the process has been effectively triggered and re-executed.

[0071] Optionally, when determining whether to effectively trigger the re-execution of the parking fee reduction process based on the reduction feedback information, this embodiment can determine whether to effectively trigger the re-execution of the parking fee reduction process based on the number of times and / or the time of receiving the reduction feedback information.

[0072] Specifically, in this embodiment, the linkage system determines that the parking fee reduction process has been effectively triggered and continues to execute subsequent processing steps when the number of times the reduction feedback information is received does not exceed (i.e., less than or equal to) a preset threshold, and / or the time difference between receiving the reduction feedback information and sending the charging record information does not exceed (i.e., less than or equal to) a time threshold. Conversely, if the number of times the reduction feedback information is received exceeds the preset threshold, and / or the time difference between receiving the reduction feedback information and sending the charging record information exceeds the time threshold, it is determined that the parking fee reduction process has not been effectively triggered. In this case, the system will send a reply message to the parking management system or user terminal to inform the user that the current vehicle reduction has failed and that parking fees must be paid before leaving the charging station.

[0073] In step S220, in response to receiving the exemption feedback information, the set of license plates bound to the user to which the target vehicle belongs is obtained, and the set of license plates includes at least one license plate.

[0074] In this embodiment, after receiving the fee reduction feedback information, the linkage system obtains the set of license plates bound to the user of the target vehicle, and triggers the parking fee reduction process again based on the license plate information corresponding to the license plates in the set, so as to avoid the parking fee not being reduced due to abnormal license plate data.

[0075] Optionally, in this embodiment, the user to whom the target vehicle belongs is a user who has a binding relationship with the target vehicle. By obtaining the user information of the target user bound to the target vehicle, querying the license plates of all vehicles bound to the target user, deduplicating and merging these license plates, and finally adding the deduplicated and merged license plates to the license plate set, the set of license plates bound to the user to whom the target vehicle belongs is obtained.

[0076] In step S230, push information is determined based on the set of license plates.

[0077] In this embodiment, after obtaining the set of license plates bound to the user for the target vehicle, in one optional implementation, considering that users typically bind vehicle information by inputting characters, errors such as incorrect character input or incorrect license plate digits can lead to abnormal license plate data during parking fee reduction; or, if a user has multiple license plates and binds other license plates as the target vehicle while charging, resulting in binding errors, this embodiment directly determines the license plate information (such as the license plate number) corresponding to the license plates in the set as the push information. Therefore, this embodiment can re-execute the parking fee reduction process based on the license plate information corresponding to the license plates in the set, reducing parking fee reduction failures caused by abnormal license plate data and improving the user charging experience.

[0078] In another alternative implementation, since the gate system typically relies on image recognition technology to identify license plate information for parking fee reduction, issues such as insufficient ambient light due to weather conditions, discrepancies between the image captured by the gate and the actual vehicle due to camera angle problems, can easily lead to misidentification of real characters, incomplete character recognition (e.g., recognizing 2 as Z, C as G), or incorrect character input when binding vehicle information for charging. These issues can all result in abnormal license plate data and failure to reduce parking fees. This embodiment can also determine the push information based on replacement information, where replacement information represents the modification correspondence of license plate information, such as 2—Z, C—G, etc. Therefore, by determining the push information based on pre-generated replacement information, this embodiment facilitates subsequent modification of license plate information that failed to reduce fees, allowing the parking fee reduction process to be executed again based on the modified license plate information. This reduces parking fee reduction failures caused by abnormal license plate data and improves the user charging experience.

[0079] Furthermore, in this embodiment, by means of... Figure 3 The method shown in the diagram determines the push notification information, specifically including the following steps.

[0080] In step S310, replacement information is obtained.

[0081] Optionally, to ensure that the replacement information covers more modification correspondences, the replacement information in this embodiment is generated based on historical license plate fee reduction records. Therefore, by generating replacement information based on historical license plate fee reduction records, this embodiment can utilize and analyze historical license plate data to address parking fee reduction failures caused by license plate data anomalies. This facilitates the rapid and accurate generation of replacement information, thereby improving the efficiency of determining push notifications based on the replacement information, and ultimately reducing anomalies and complaints caused by license plate errors at a lower cost.

[0082] Furthermore, in this embodiment, the replacement information can be generated in advance based on historical license plate reduction records; alternatively, it can be generated in real-time based on historical license plate reduction records after the target vehicle is unable to successfully reduce parking fees due to abnormal license plate data. In other words, replacement information is obtained in response to the acquisition of the license plate set, and the choice can be made based on the actual usage scenario. Therefore, when obtaining replacement information based on pre-generation, it is convenient and quick to acquire the information, accelerating the process of determining push notifications based on the replacement information, thereby improving the efficiency of vehicle parking fee reduction processing. When generating and obtaining replacement information in real-time, it is possible to utilize historical license plate information more recent to the current time, making the replacement information more real-time and improving its reference value for accurate vehicle parking fee reduction.

[0083] Furthermore, in this embodiment, by means of... Figure 4The method in the article generates replacement information based on historical license plate exemption records.

[0084] In step S410, historical license plates are obtained.

[0085] In this embodiment, the historical license plates include license plates in the license plate set and / or other license plates outside the license plate set, and each license plate in the historical license plates has a corresponding exemption record. The exemption record includes information such as exemption success, exemption failure, and exemption success after modifying the license plate information to represent the exemption status.

[0086] In step S420, each historical license plate is filtered according to the historical license plate exemption records to determine at least one target license plate.

[0087] In this embodiment, the target license plate is the license plate that successfully underwent a reduction in exemption after its information was modified. By filtering through the exemption records of each license plate in the historical records, the target license plates are those that previously failed to be exempted and whose exemptions failed after the information was modified.

[0088] In step S430, replacement information is generated based on the license plate information before and after modification for each target license plate.

[0089] In this embodiment, since the target vehicles all have license plates that were successfully modified for parking fee reduction, the modification correspondence of the license plate information can be determined by comparing the differences between the license plate information before and after the modification, thereby generating replacement information. For example, assuming the license plate information when the reduction failed was "xxxx2", and the reduction was successful after modifying "xxxx2" to "xxxxZ", then the corresponding replacement information "2-Z" can be determined based on the original license plate information "xxxx2" and the modified "xxxxZ". Therefore, by generating replacement information based on the license plate information before and after the modification of each target license plate, the parking fee reduction process can be executed again based on the replacement information, thereby reducing parking fee reduction failures caused by abnormal license plate data and improving the user charging experience.

[0090] In step S320, the license plate information corresponding to the license plates in the license plate set is modified according to the replacement information.

[0091] In this embodiment, considering that the abnormal license plate data leading to the failure of the fee reduction often occurs when the user's license plate information is incorrectly bound, and that even if the license plate information identified by the barrier gate system (i.e., the license plate identifier in the fee reduction feedback information) is modified when the license plate data is abnormal due to the barrier gate system's recognition of the license plate information, there will still be many other vehicles whose fee reductions fail. Therefore, after generating the replacement information, this embodiment will modify the license plate information corresponding to the license plates in the license plate set according to the replacement information, so as to re-execute the parking fee reduction process based on the modified license plate information. For example, assuming that the license plate information in the target vehicle's license plate set is "xxxx2", and the license plate identifier identified when the fee reduction fails is "xxxxZ", that is, the license plate identifier in the fee reduction feedback information is "xxxxZ", then the modification correspondence "2-Z" in the replacement information is used to modify "xxxx2", and the modified license plate information is "xxxxZ".

[0092] Optionally, when modifying the license plate information corresponding to license plates in the license plate set based on replacement information, this embodiment can modify the license plate information according to a preset modification order. The preset modification order can be determined based on factors such as the number of replacement information items corresponding to the license plate information and the correlation between the license plate information and the license plate identifier in the fee reduction feedback information. Therefore, by modifying the license plate information corresponding to license plates in the license plate set according to a preset modification order, this embodiment ensures the orderly modification of license plate information, thereby enabling efficient modification of the license plate information, improving overall data processing efficiency, and ultimately improving the efficiency of vehicle parking fee reduction processing.

[0093] Furthermore, to balance modification efficiency and parking fee reduction processing efficiency, the preset modification order in this embodiment is determined based on the correlation between the license plate information corresponding to the license plates in the license plate set and the license plate identifiers in the reduction feedback information. When modifying the license plate information, this embodiment first performs similarity matching between the license plate identifiers of each license plate in the license plate set and the license plate identifiers in the reduction feedback information, and then modifies the license plate information corresponding to the license plates in the license plate set in descending order of similarity, so as to re-execute the parking fee reduction process based on the modified license plate information.

[0094] In step S330, the modified license plate information is determined as the push information.

[0095] In this embodiment, after modifying the license plate information corresponding to the license plates in the license plate set according to the replacement information, the modified license plate information is determined as the push information. For example, after modifying the license plate information "xxxx2" in the license plate set using the replacement information "2-Z", the modified license plate information "xxxxZ" is determined as the push information. Therefore, this embodiment uses the above method to modify the license plate information corresponding to the license plates in the license plate set using the replacement information to determine the push information, enabling the subsequent execution of the parking fee reduction process using the push information. This reduces parking fee reduction failures caused by abnormal license plate data and improves the user's charging experience.

[0096] In another optional implementation, this embodiment can first use the license plate information corresponding to the license plates in the license plate set as the push information. If the parking fee reduction process fails after executing the process based on the license plate information corresponding to the license plates in the license plate set, then the push information is determined based on the pre-generated replacement information. Correspondingly, the method for determining the push information includes: determining the license plate information corresponding to the license plates in the license plate set as the push information; in response to the failure of the parking fee reduction process after executing the process based on the license plate information corresponding to the license plates in the license plate set, obtaining replacement information; modifying the license plate information corresponding to the license plates in the license plate set according to the replacement information; and determining the modified license plate information as the push information.

[0097] Specifically, such as Figure 5 As shown in the diagram, in this embodiment, after receiving the parking fee reduction feedback information from the target vehicle, the system obtains the license plate set A bound to the user to which the target vehicle belongs. First, the license plate information "xxxxx" and "xxxx2" corresponding to the license plates in license plate set A are identified as push notification information. If the parking fee reduction based on the license plate information "xxxxx" and "xxxx2" in license plate set A still fails, the license plate information in license plate set A is modified based on replacement information. For example, based on the replacement information "2-Z", "xxxx2" is changed to "xxxxZ", and the modified license plate information "xxxxZ" is used again as push notification information. Therefore, this embodiment combines different methods to determine push notification information, making the determination of push notification information more convenient, which helps to increase the success rate of parking fee reduction for the target vehicle and further improves the user's charging experience.

[0098] In step S240, a push notification is sent to re-execute the parking fee reduction process based on the push notification.

[0099] In this embodiment, the type of push information can be the license plate information corresponding to the license plate in the set of license plates corresponding to the target vehicle, or it can be the license plate information generated after modifying the license plate information corresponding to the license plate in the set of license plates corresponding to the target vehicle according to the replacement information. When the linkage system sends push information to the parking management system, different types of push information can be sent in the same or different ways.

[0100] Optionally, in this embodiment, different methods are used to send different types of push information. Further, when the push information is license plate information corresponding to a license plate in the license plate set, this embodiment will push the license plate information corresponding to the license plate in the license plate set according to a preset push order to send the push information, thereby re-executing the parking fee reduction process based on the push information.

[0101] Optionally, in this embodiment, when sending push information, the push order is first determined based on the attribute information of each license plate in the license plate set, and then the license plate information corresponding to each license plate in the license plate set is pushed according to the push order. The attribute information includes the binding time and / or the number of bindings. In this case, the license plate information with the closest binding time to the current time and / or the most bindings is more likely to be pushed first. Therefore, by determining the push order and pushing the license plate information corresponding to each license plate in the license plate set according to the push order in this embodiment, push information can be sent more orderly and efficiently, improving the processing efficiency of subsequently re-executing the parking fee reduction process based on the push information, thereby improving the overall data processing efficiency.

[0102] When the pushed information is the modified license plate information corresponding to the license plate in the license plate set based on the replacement information, the sending order of the pushed information in this embodiment can be consistent with the generation order of the pushed information. For example, when modifying the license plate information corresponding to the license plate in the license plate set according to the preset modification order to determine the corresponding pushed information, this embodiment sends each pushed information according to the modification order of the license plate information corresponding to each pushed information. This makes the processing of sending pushed information more orderly and efficient, thereby improving the processing efficiency of re-executing the parking fee reduction process based on the pushed information, and thus improving the overall data processing efficiency.

[0103] Furthermore, when there are multiple push notifications, optionally, in this embodiment, each push notification can be sent sequentially according to the aforementioned sending order, and whether to continue sending push notifications can be determined based on the reduction result corresponding to each push notification. Specifically, if the reduction result corresponding to the previous push notification is a failure, then the next push notification is sent; and if the reduction result corresponding to the previous push notification is a success, then the next push notification is stopped.

[0104] Furthermore, after receiving the push notification, the parking management system in this embodiment can use each push notification in the same order as the order in which they were sent to execute the parking fee reduction process, thereby reducing the parking fee for the target vehicle. This avoids situations where parking fee reduction cannot be performed due to abnormal license plate data, thus improving the user's charging experience.

[0105] Alternatively, in this embodiment, each push message can be sent in batches according to the aforementioned sending order. The number of push messages sent in a batch can be all push messages or a portion of all push messages. Further, when the number of push messages sent in a batch is a portion of all push messages, this embodiment first executes the parking fee reduction process based on the push data of the current batch, and determines whether to continue sending the next batch of push messages based on the reduction result corresponding to the push messages of that batch. Specifically, if the reduction results corresponding to the push messages of the current batch are all failures, then the next batch of push messages is sent; if the reduction result corresponding to the push messages of the current batch is a success, then the sending of the next batch of push messages is stopped.

[0106] Furthermore, after receiving the push notifications from each batch, the parking management system in this embodiment can execute the parking fee reduction process using the push notifications in any order or in the same order as the order in which they were sent. It can also execute the parking fee reduction process in parallel using all the push notifications. When the reduction result corresponding to one of the push notifications is successful, a feedback message of successful reduction is sent to the linkage system; or when the reduction results corresponding to all push notifications are unsuccessful, a feedback message of failure is sent to the linkage system. Therefore, by sending push notifications and re-executing the parking fee reduction process based on the push notifications, this embodiment can quickly adjust the license plate information for vehicles that failed to receive a reduction, and re-execute the parking fee reduction process based on the adjusted license plate information. This reduces situations where parking fees could have been reduced but were not, improving the user's charging experience.

[0107] Optionally, after the target vehicle successfully reduces parking fees based on the push notification, to reduce the likelihood of subsequent parking fee reduction errors due to abnormal license plate data, this embodiment sends a reminder message to the user via a linkage system to modify the bound license plate information after the target vehicle successfully reduces fees. Correspondingly, the license plate data anomaly handling method in this embodiment further includes: in response to the successful reduction of fees for the target vehicle, sending a reminder message to the user to whom the target vehicle belongs, prompting the user to modify the currently bound license plate information to the license plate information corresponding to the one at the time of successful reduction. Therefore, by sending a reminder message to the user after the vehicle successfully reduces fees based on the push notification, this embodiment helps the user to be aware of incorrect license plate binding and reminds the user to correct the incorrect binding information, avoiding subsequent parking fee reduction failures due to the same incorrect license plate binding information, thereby improving the efficiency of parking fee reduction processing and further enhancing the user's charging experience.

[0108] Alternatively, in this embodiment, after the target vehicle fails to reduce the parking fee based on the push information, if the cause of the vehicle's abnormality is determined to be an abnormality in the gate system's recognition, the linkage system will send maintenance information to the parking management system or the corresponding equipment maintenance personnel to remind them to optimize the gate system's recognition function. This will prevent the abnormal license plate data caused by the recognition abnormality from continuing to have a negative impact on the vehicle's parking fee reduction, thereby improving the protection of user interests and further enhancing the user's charging experience.

[0109] The technical solution of this embodiment obtains the set of license plates bound to the user of the target vehicle when abnormal license plate data prevents the reduction of parking fees incurred during charging. Based on the set of license plates, push information is determined, so that when abnormal license plate data prevents the reduction of parking fees incurred during charging, the parking fee reduction process can be re-executed based on the push information. This reduces the failure of parking fee reduction due to abnormal license plate data and improves the user charging experience.

[0110] Figure 6 This is a flowchart of a license plate data anomaly handling method according to an embodiment of the present invention. Figure 6 As shown, the license plate data anomaly handling method in this embodiment is applied to a parking management system and specifically includes the following steps.

[0111] In step S610, a reduction feedback message is sent, which indicates that the target vehicle cannot be exempted from parking fees incurred during charging due to abnormal license plate data.

[0112] In this embodiment, the parking management system identifies the license plate information of the target vehicle when it leaves the charging station. If the license plate information is not identified or the identified license plate information does not match the vehicle information in the received charging record, it is determined that the target vehicle cannot be exempted from parking fees incurred during charging, and the reason for the failure to exempt the fee is an abnormal license plate data. At this time, the parking management system sends exemption feedback information to the linkage system so that the linkage system is aware that the vehicle's exemption failed due to an abnormal license plate data.

[0113] In step S620, push information is received, and the push information is determined based on the set of license plates bound to the user to which the target vehicle belongs.

[0114] In this embodiment, after the parking management system sends the exemption feedback information to the linkage system, the linkage system triggers the aforementioned license plate data anomaly handling method, obtains the set of license plates bound to the user to which the target vehicle belongs, determines the push information based on the license plate set, and sends the push information to the parking management system. Meanwhile, the method for the linkage system to determine and send the push information has already been described in the aforementioned license plate data anomaly handling method and will not be repeated here.

[0115] In step S630, the parking fee reduction process is re-executed based on the push information.

[0116] In this embodiment, after receiving the push information, the parking management system re-executes the parking fee reduction process according to the push information to avoid situations where parking fees that could have been reduced were not, thereby improving the user's charging experience.

[0117] Furthermore, when executing the parking fee reduction process, the parking management system matches the license plate information in the push notification with the charging record information to determine the charging record information corresponding to the target vehicle. Then, it compares the target vehicle's charging record information with the preset reduction method to determine if the target vehicle's charging record information meets the preset reduction method. If the charging record information meets the preset reduction method, the parking fee is reduced for the target vehicle, and a successful reduction feedback message is sent to the linkage system. Finally, based on the vehicle's charging record information, the time the vehicle enters and exits the charging station, and the preset reduction method (i.e., the preset parking fee reduction rules), the actual parking fee that the vehicle needs to pay is determined.

[0118] If there is no charging record information corresponding to the license plate information in the push message, or if the charging record information of the target vehicle does not meet the preset reduction method, it is determined not to reduce the parking fee for the target vehicle, and a feedback message of reduction failure is sent to the linkage system so that the linkage system can resend the push message, or if there is no push message to send, the parking fee reduction process is terminated and the user is reminded of the reduction failure message.

[0119] Optionally, when the parking management system in this embodiment receives multiple push notifications at once, it can use each push notification in any order or in the same order as the order in which they were sent to execute the parking fee reduction process. Alternatively, it can use each push notification simultaneously to execute the parking fee reduction process in parallel, thereby reducing the parking fee for the target vehicle. Therefore, by re-executing the parking fee reduction process based on the push notifications using the above method, this embodiment can quickly adjust the license plate information of vehicles that failed to receive a reduction, and re-execute the parking fee reduction process based on the adjusted license plate information. This reduces situations where parking fees could have been reduced but were not, improving the user's charging experience.

[0120] Furthermore, in this embodiment, after re-executing the parking fee reduction process based on the push information, when there is a successful reduction result corresponding to one push information in a batch, a successful reduction feedback message is sent to the linkage system so that the linkage system can generate a reduction record for the target vehicle based on the reduction result of the target vehicle; or, when the reduction results corresponding to all push information are unsuccessful, a reduction failure feedback message is sent to the linkage system so that the linkage system can resend the push information, or when there is no other push information to send, the execution of the parking fee reduction process is terminated, and a prompt message reminding the user of the reduction failure is displayed.

[0121] The technical solution of this embodiment sends a reduction feedback message to the linkage system when the parking fee reduction cannot be waived due to abnormal license plate data. After receiving the push message, the parking fee reduction process is re-executed according to the push message. This can reduce the failure of parking fee reduction caused by abnormal license plate data and improve the user charging experience.

[0122] Figure 7 This is a flowchart illustrating the parking fee reduction process when license plate data is abnormal, according to an embodiment of the present invention. Figure 7 As shown, this embodiment achieves parking fee reduction during vehicle charging through the following steps.

[0123] In step S710, a reduction / exemption feedback message is sent.

[0124] In this embodiment, after the parking management system 20 detects that the abnormal license plate data caused the parking fee reduction to fail when the target vehicle is charging, it sends a reduction feedback message to the linkage system 10 so that the linkage system 10 knows that the vehicle reduction failed due to the abnormal license plate data.

[0125] In step S720, the set of license plates bound to the user to which the target vehicle belongs is obtained.

[0126] In this embodiment, in response to receiving the exemption feedback information sent by the parking management system 20, the linkage system 10 obtains a set of license plates, including at least one license plate, bound to the user to which the target vehicle belongs. The method for obtaining the license plate set has been described in detail above and will not be repeated here.

[0127] In step S730, push information is determined based on the set of license plates.

[0128] In this embodiment, after the linkage system 10 obtains the set of license plates corresponding to the target vehicle, it determines the license plate information corresponding to the license plates in the set as the push information; or, it determines the push information by obtaining replacement information and modifying the license plate information corresponding to the license plates in the set according to the replacement information. The specific process of determining the push information can refer to the method for determining push information described above, and will not be repeated here.

[0129] In step S740, a push notification is sent.

[0130] In this embodiment, after determining the push information, the linkage system 10 sends the determined push information to the parking management system 20 based on the aforementioned method for sending push information.

[0131] In step S750, the parking fee reduction process is re-executed based on the push information.

[0132] In this embodiment, the parking management system 20 responds to the push information sent by the linkage system 10 and re-executes the parking fee reduction process according to the push information, so that the target vehicle that can be exempted from parking fees but failed to be exempted can successfully complete the parking fee reduction.

[0133] In step S760, feedback information on the reduction result is sent.

[0134] In this embodiment, after the parking management system 20 re-executes the parking fee reduction process based on the push information, it will send the execution result of the parking fee reduction process, i.e., the feedback information of the reduction result, to the linkage system 10 so as to generate the reduction record of the target vehicle based on the reduction result of the target vehicle; or, if there is no other push information to send, it will end the execution of the parking fee reduction process and remind the user of the prompt message of reduction failure.

[0135] The technical solution in this embodiment reduces parking fee reduction failures caused by abnormal license plate data by having the linkage system interact with the parking management system when abnormal license plate data prevents the reduction of parking fees incurred during charging. This interaction determines the push information and re-executes the parking fee reduction process based on the push information, thereby improving the user charging experience.

[0136] Figure 8 This is a schematic diagram of a license plate data anomaly processing device according to an embodiment of the present invention. Figure 8 As shown, the license plate data anomaly handling device in this embodiment includes a receiving unit 11, a processing unit 12, and a sending unit 13. The receiving unit 11 receives reduction feedback information, which indicates that the target vehicle cannot receive parking fee reduction due to license plate data anomaly. The processing unit 12, in response to receiving the reduction feedback information, obtains the set of license plates bound to the user of the target vehicle, and determines push information based on the license plate set, where the license plate set includes at least one license plate. The sending unit 13 sends the push information to re-execute the parking fee reduction process based on the push information.

[0137] Optionally, in this embodiment, the processing unit 12, when determining the push information, is further configured to determine the license plate information corresponding to the license plates in the license plate set as the push information. Correspondingly, the sending unit 13 is further configured to push the license plate information corresponding to the license plates in the license plate set according to a preset push order. Further, when pushing the license plate information corresponding to the license plates in the license plate set according to the preset push order, the sending unit 13 is specifically configured to determine the push order based on the attribute information of each license plate in the license plate set, and push the license plate information corresponding to each license plate in the license plate set according to the push order. The attribute information of the license plates includes the binding time and / or the number of bindings.

[0138] Optionally, the processing unit 12 in this embodiment is further configured to obtain replacement information, modify the license plate information corresponding to the license plates in the license plate set according to the replacement information, and determine the modified license plate information as push information. The replacement information is generated based on historical license plate exemption records, and the historical license plates include license plates in the license plate set and / or other license plates outside the license plate set.

[0139] Furthermore, when obtaining replacement information, the processing unit 12 in this embodiment is also used to obtain replacement information in response to the failure of the parking fee reduction process after executing the parking fee reduction process based on the license plate information corresponding to the license plate in the license plate set.

[0140] Furthermore, when generating replacement information based on the historical license plate exemption records, the processing unit 12 is also used to filter each historical license plate according to the historical license plate exemption records, determine at least one target license plate, the target license plate being the license plate that successfully obtained exemption after the license plate information was modified; and generate replacement information based on the license plate information before and after the modification of each target license plate.

[0141] Optionally, the processing unit 12 in this embodiment is further configured to send a reminder message to the user to whom the target vehicle belongs in response to the successful reduction of the vehicle's license plate information, so as to prompt the user to modify the currently bound license plate information to the license plate information corresponding to the successful reduction of the vehicle's license plate information.

[0142] Figure 9 This is another schematic diagram of the license plate data anomaly processing device according to an embodiment of the present invention. (See diagram below.) Figure 9 As shown, the license plate data anomaly handling device in this embodiment includes an interaction unit 21 and an execution unit 22. The interaction unit 21 is used to send reduction feedback information and receive push information. The reduction feedback information indicates that the target vehicle cannot receive a reduction in parking fees incurred due to license plate data anomalies. The push information is determined based on the set of license plates bound to the user to which the target vehicle belongs. The execution unit 22 is used to re-execute the parking fee reduction process based on the push information.

[0143] Figure 10 This is a schematic diagram of an electronic device according to an embodiment of the present invention. (For example...) Figure 10 As shown, Figure 10 The illustrated electronic device is a general-purpose data processing device, comprising a general-purpose computer hardware architecture, including at least a processor 101 and a memory 102. The processor 101 and memory 102 are connected via a bus 103. The memory 102 is adapted to store instructions or programs executable by the processor 101. The processor 101 can be a standalone microprocessor or a collection of one or more microprocessors. Thus, the processor 101 executes the instructions stored in the memory 102, thereby performing the method flow of the embodiments of the present invention as described above to process data and control other devices. The bus 103 connects the aforementioned components together, and also connects these components to a display controller 104, a display device, and an input / output (I / O) device 105. The input / output (I / O) device 105 can be a mouse, keyboard, modem, network interface, touch input device, motion-sensing input device, printer, and other devices known in the art. Typically, the input / output device 105 is connected to the system via an input / output (I / O) controller 106.

[0144] Those skilled in the art will understand that embodiments of this application can be provided as methods, apparatus (devices), or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0145] This application is described with reference to flowchart illustrations of methods, apparatus (devices), and computer program products according to embodiments of this application. It should be understood that each step in the flowchart can be implemented by computer program instructions.

[0146] These computer program instructions may be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including an instruction means, the implementation process of which is described in the instruction means. Figure 1 The function specified in one or more processes.

[0147] These computer program instructions may also be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing device, produce instructions for implementing processes. Figure 1 A device for a function specified in one or more processes.

[0148] Another embodiment of the present invention relates to a non-volatile storage medium for storing a computer-readable program for use by a computer to execute some or all of the above-described method embodiments.

[0149] That is, those skilled in the art will understand that all or part of the steps in the methods of the above embodiments can be implemented by a program specifying the relevant hardware. This program is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0150] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for handling license plate data anomalies, characterized in that, The method includes: Receive reduction feedback information, which indicates that the target vehicle cannot be exempted from parking fees incurred during charging due to abnormal license plate data; In response to receiving the exemption feedback information, obtain the set of license plates bound to the user to which the target vehicle belongs, the set of license plates including at least one license plate; The push information is determined based on the set of license plates; Send the push notification to re-execute the parking fee reduction process based on the push notification.

2. The method according to claim 1, characterized in that, The push information is the license plate information corresponding to the license plates in the license plate set, and sending the push information includes: The license plate information corresponding to the license plates in the set of license plates is pushed according to the preset push order.

3. The method according to claim 2, characterized in that, The step of pushing the license plate information corresponding to the license plates in the license plate set according to the preset push order includes: The push order is determined based on the attribute information of each license plate in the license plate set, wherein the attribute information includes the binding time and / or the number of bindings; The license plate information corresponding to each license plate in the license plate set is pushed out in the specified push order.

4. The method according to claim 1, characterized in that, The step of determining the push information based on the license plate set includes: Obtain replacement information, which is generated based on the historical license plate exemption records. The historical license plates include license plates in the license plate set and / or other license plates outside the license plate set. Modify the license plate information corresponding to the license plates in the license plate set according to the replacement information; The modified license plate information will be used as the push notification.

5. The method according to claim 4, characterized in that, The acquisition of replacement information includes: If the parking fee reduction process fails after executing the process based on the license plate information corresponding to the license plate in the license plate set, replacement information is obtained.

6. The method according to claim 4, characterized in that, The replacement information is generated using the following method: Based on the historical license plate exemption records, each of the historical license plates is filtered to determine at least one target license plate, which is the license plate that has successfully been exempted after the license plate information has been modified; Replacement information is generated based on the license plate information before and after the modification of each target license plate.

7. The method according to claim 1, characterized in that, The method further includes: In response to the successful exemption of the target vehicle, a reminder message is sent to the user to whom the target vehicle belongs, prompting the user to change the currently bound license plate information to the license plate information corresponding to the time of the successful exemption.

8. A method for handling license plate data anomalies, characterized in that, The method includes: Send a reduction feedback message, which indicates that the target vehicle cannot be exempted from parking fees incurred during charging due to abnormal license plate data. Receive push notifications, the push notifications being determined based on the set of license plates bound to the user to which the target vehicle belongs; The parking fee reduction process will be re-executed based on the push notification information.

9. A license plate data anomaly processing system, characterized in that, The system includes: The linkage system is configured to receive and push charging record information of a target vehicle, receive parking fee reduction feedback information, and in response to receiving the parking fee reduction feedback information, obtain the set of license plates bound to the user to which the target vehicle belongs, determine push information based on the set of license plates, and send the push information to re-execute the parking fee reduction process based on the push information; wherein, the parking fee reduction feedback information is used to indicate that the target vehicle cannot reduce the parking fees incurred due to abnormal license plate data, and the set of license plates includes at least one license plate. The parking management system is configured to execute a parking fee reduction process based on the charging record information and a preset reduction method, send the reduction feedback information, and, in response to receiving the push information, re-execute the parking fee reduction process based on the push information.

10. A license plate data anomaly processing device, characterized in that, The device includes: A receiving unit is used to receive reduction feedback information, which indicates that the target vehicle cannot be exempted from parking fees incurred during charging due to abnormal license plate data. The processing unit is configured to, in response to receiving the exemption feedback information, obtain the set of license plates bound to the user to which the target vehicle belongs, and determine the push information based on the set of license plates, wherein the set of license plates includes at least one license plate; The sending unit is used to send the push information to re-execute the parking fee reduction process based on the push information.

11. A license plate data anomaly processing device, characterized in that, The device includes: An interaction unit is used to send a fee reduction feedback message and receive push notifications; wherein, the fee reduction feedback message is used to indicate that the target vehicle cannot be exempted from parking fees incurred during charging due to abnormal license plate data; the push notifications are determined based on the set of license plates bound to the user to which the target vehicle belongs; The execution unit is used to re-execute the parking fee reduction process based on the pushed information.

12. A computer program product, characterized in that, The computer program product includes a computer program / instruction that, when executed by a processor, implements the method of any one of claims 1-8.

13. An electronic device comprising a memory and a processor, characterized in that, The memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method of any one of claims 1-8.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1-8.

Images