C-end user-oriented parking payment automatic invoicing method and system

Through the automatic processing of license plate identification and payment information, the cumbersome problems of parking payment and invoice is solved, and the technical effect of simplifying the process and invoice accuracy is achieved.

CN120564282APending Publication Date: 2025-08-29INTELLIGENT INTER CONNECTION TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510616252.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-05-14
Publication Date
2025-08-29

AI Technical Summary

Technical Problem

The existing parking payment and invoice procedures are cumbersome, users are inconvenient to operate, and invoice errors are frequently issued.

Method used

The license plate information is automatically obtained through the license plate recognition unit and associated with the user account, obtain payment information and automatically generate electronic invoices, push it to the user and encrypted storage.

Benefits of technology

Simplify the parking payment and invoice process, improve user operation convenience, and ensure the accuracy of invoice generation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120564282A_ABST
    Figure CN120564282A_ABST
Patent Text Reader

Abstract

The invention discloses a parking payment automatic billing method and system for a C-end user, and relates to the technical field of parking management, and the method comprises the steps: obtaining the license plate information of a target vehicle through a license plate recognition unit when a user enters a parking lot for the first time, associating the license plate information with a user registration account, obtaining the user billing information, and transmitting the user billing information to an associated billing unit; after the target vehicle completes parking payment, user payment information is acquired and sent to the associated billing unit; receiving user payment information and user invoicing information, and generating an electronic invoice; and automatically pushing the electronic invoice to the user side through the pushing channel, and carrying out encrypted storage and backup on the user payment information, the user invoicing information and the electronic invoice. The technical problems that in the prior art, the parking payment and invoicing process is tedious, user operation is inconvenient, and invoice errors are frequently issued are solved, and the technical effects that the parking payment and invoicing process is simplified, user operation convenience is improved, and invoice generation accuracy is ensured are achieved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of parking management, and in particular to a method and system for automatic invoicing of parking payments for C-end users. Background Art

[0002] Existing parking payment and invoicing processes are typically separate. Users must manually apply for an electronic invoice after completing their payment and repeatedly enter data such as license plate information and payment amount, making the process cumbersome and time-consuming. Furthermore, the separation of payment and invoicing systems forces users to switch between different applications or interfaces, increasing operational inconvenience. Manual or semi-automated invoicing methods in existing systems are also prone to errors in information entry, inaccurate amounts, and duplicate invoicing, compromising invoice accuracy. Summary of the Invention

[0003] This application provides a method and system for automatic invoicing of parking payments for C-end users, which is used to solve the technical problems of the existing technology such as complicated parking payment and invoicing processes, inconvenient user operations, and frequent invoice errors.

[0004] In view of the above problems, this application provides an automatic invoicing method and system for parking payment for C-end users.

[0005] In a first aspect, the present application provides a method for automatically issuing parking invoices for C-end users, the method comprising:

[0006] When a user enters a parking lot for the first time, the license plate information of the target vehicle is obtained through the license plate recognition unit, and the license plate information is associated with the user's registered account, and the user's billing information is obtained and sent to the associated billing unit; when the target vehicle completes the parking payment, the user's payment information is obtained and sent to the associated billing unit; the associated billing unit receives the user's payment information and the user's billing information, and automatically generates an electronic invoice according to a preset invoice format; the electronic invoice is automatically pushed to the user end through the user's preset push channel, and the user's payment information, user's billing information and electronic invoice are encrypted, stored and backed up.

[0007] A second aspect of the present application provides an automatic parking payment invoicing system for C-end users, the system comprising:

[0008] The license plate information acquisition module is used to obtain the license plate information of the target vehicle through the license plate recognition unit when the user enters the parking lot for the first time, and associate the license plate information with the user's registered account, obtain the user's billing information and send it to the associated billing unit; the payment information acquisition module is used to obtain the user's payment information and send it to the associated billing unit after the target vehicle completes the parking payment; the electronic invoice generation module is used for the associated billing unit to receive the user payment information and the user billing information, and automatically generate an electronic invoice according to the preset invoice format; the information sending module is used to automatically push the electronic invoice to the user end through the user's preset push channel, and encrypt and store and back up the user payment information, user billing information and electronic invoice.

[0009] One or more technical solutions provided in this application have at least the following technical effects or advantages:

[0010] When a user enters a parking lot for the first time, the present application obtains the license plate information of the target vehicle through the license plate recognition unit, associates the license plate information with the user's registered account, obtains the user's invoicing information and sends it to the associated invoicing unit; when the target vehicle completes the parking payment, obtains the user's payment information and sends it to the associated invoicing unit; the associated invoicing unit receives the user's payment information and the user's invoicing information, and automatically generates an electronic invoice according to a preset invoice format; the electronic invoice is automatically pushed to the user end through the user's preset push channel, and the user's payment information, user's invoicing information and electronic invoice are encrypted, stored and backed up. The present invention solves the technical problems of the prior art, such as the cumbersome parking payment and invoicing process, inconvenient user operation, and frequent invoice errors. By automating license plate recognition, payment information acquisition, automatic generation and push of invoicing information, and encrypted storage and backup, the present invention achieves the technical effects of simplifying the parking payment and invoicing process, improving user operation convenience, and ensuring the accuracy of invoice generation. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0012] Figure 1 A flow chart of the automatic invoicing method for parking payment for C-end users provided in an embodiment of the present application;

[0013] Figure 2 A schematic diagram of the structure of the automatic ticketing system for parking payment for C-end users provided in an embodiment of the present application.

[0014] Explanation of the reference numerals: license plate information acquisition module 11 , payment information acquisition module 12 , electronic invoice generation module 13 , information sending module 14 . DETAILED DESCRIPTION

[0015] This application provides an automatic invoicing method and system for parking payments for C-end users, aiming to solve the technical problems of the existing technology such as cumbersome parking payment and invoicing processes, inconvenient user operations, and frequent invoice errors. Through automated license plate recognition, payment information acquisition, automatic generation and push of invoicing information, and encrypted storage and backup, the application achieves the technical effect of simplifying the parking payment and invoicing process, improving user operation convenience, and ensuring the accuracy of invoice generation.

[0016] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only some of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0017] It should be noted that any variations of the terms "include" and "have" are intended to cover non-exclusive inclusions. For example, a process, method, system, product or server that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or modules that are not clearly listed or are inherent to these processes, methods, products or devices.

[0018] Example 1, as Figure 1 As shown, the present application provides a parking payment automatic invoicing method for C-end users, the method comprising:

[0019] Step S100: When a user enters a parking lot for the first time, the license plate information of the target vehicle is obtained through the license plate recognition unit, and the license plate information is associated with the user's registered account, and the user's billing information is obtained and sent to the associated billing unit.

[0020] In an embodiment of the present application, when a user enters a parking lot for the first time, the license plate information of the target vehicle is automatically obtained through the license plate recognition unit. Specifically, the image sensing module of the license plate recognition unit captures the license plate image of the vehicle in real time, and inputs the image into the built-in license plate recognizer for processing and converting it into digital license plate information. Then, based on these digital license plate information, the user database of the target parking lot is traversed, and the corresponding user registration account information is automatically identified and matched, thereby completing the preliminary information binding. If the user's account is successfully matched, the user's billing information is automatically obtained, and this information is sent to the associated billing unit for subsequent processing. If the license plate information fails to match the account of a registered user, an account registration instruction is pushed, prompting the user to register an account and fill in the billing-related information. Through this process, users do not need to manually enter billing information, and the license plate information is automatically associated with the user account, simplifying the billing operation.

[0021] Furthermore, in the method provided in the embodiment of the application, the license plate information of the target vehicle is obtained by the license plate recognition unit, and the license plate information is associated with the user's registered account, and further includes:

[0022] The image sensing module of the license plate recognition unit is used to capture the license plate image of the target vehicle in real time, and input it into the built-in license plate recognizer to convert it into digital license plate information; based on the digital license plate information, the user database of the target parking lot is traversed, the user registration account information is automatically identified and matched, and preliminary information binding is performed.

[0023] Furthermore, the method provided in the application embodiment also includes:

[0024] The license plate recognizer comprises an image acquisition module, a license plate positioning module, a character segmentation module, a character recognition module and an output processing module.

[0025] In this embodiment, the license plate recognition unit's image sensor module first captures the target vehicle's license plate image in real time. The image sensor module, comprised of a high-resolution CMOS or CCD sensor, is capable of capturing a clear image of the vehicle's license plate and transmitting the image data to the license plate recognizer for subsequent processing. The license plate recognizer includes an image acquisition module, a license plate location module, a character segmentation module, a character recognition module, and an output processing module.

[0026] When the license plate image of the targeted vehicle is input into the built-in license plate recognition system, the image acquisition module uses an image sensor to capture the license plate image in real time, ensuring image clarity. This image sensor can quickly capture license plate information from passing vehicles, providing an accurate data source. The license plate location module then processes the captured image to identify the specific location of the license plate. This step uses image-based edge detection to determine the license plate area and a geometric feature extraction algorithm to precisely locate the license plate. The character segmentation module then further processes the located license plate area to separate the characters within the license plate. This process uses a binarization method, first converting the image into black and white, then performing horizontal or vertical scanning to identify character boundaries. Each character is extracted individually for independent recognition. The character recognition module then converts the segmented characters into digits and letters. This step uses template matching, which compares the segmented characters against a predefined character library to determine the specific information of each character. The character recognition module accurately converts the license plate characters into their corresponding digits and letters, forming a complete digital license plate.

[0027] After obtaining the digital license plate information, it is used to match it with the parking lot's user database. The user database stores all registered user information, including license plate information, account information, and ticketing information. The database is traversed to search for a matching user account based on the digital license plate information. This process is accomplished through hash lookups or sequential searches, quickly identifying the account associated with the license plate information. If a match is found, the license plate information is bound to the user account. If no user account is matched, an account registration instruction is pushed, prompting the user to register an account, thus completing the account binding. This process completes the initial information binding.

[0028] Furthermore, in the method provided in the embodiment of the application, obtaining the user's invoicing information and sending it to the associated invoicing unit further includes:

[0029] When the license plate information matches a registered user account in the user database, the user billing information is automatically associated and obtained; if the license plate information does not match a registered user account, an account registration instruction is pushed to prompt the user to register and bind the account and fill in the user billing information.

[0030] In an embodiment of the present application, after the license plate information is extracted and converted into digital license plate information, the information is matched with the registered user account in the user database of the parking lot. The user database stores data including license plate numbers, account information, and billing information. If a matching user account is successfully found in the database based on the digital license plate information, the license plate information is automatically associated with the corresponding user account to obtain the user's billing information. At this time, the pre-stored user billing information (such as invoice header, email address, etc.) is used for automated billing processing, without the user having to re-enter the relevant information, thereby improving efficiency and user experience.

[0031] If no registered user account matching the digital license plate information is found in the user database, an account registration instruction is pushed. This instruction is displayed to the user through the interface, prompting them to complete the account registration and binding process. Specifically, the user is guided to fill in the necessary registration information, such as account name, contact information, and billing information. After registration and binding, this new user information is stored in the database and associated with the corresponding license plate information, thus completing the creation of the user account and the entry of billing information, resulting in the user's billing information.

[0032] Step S200: After the target vehicle completes parking payment, the user payment information is obtained and sent to the associated invoicing unit.

[0033] In this embodiment of the present application, after the target vehicle completes the parking payment, the user's payment information is obtained through the payment interface. The parking lot's payment system is connected to a third-party payment platform (such as WeChat Pay, Alipay, or UnionPay) to complete the payment process. After successful payment, the payment interface stores information such as the payment amount, payment time, payment method (such as scan code payment, contactless payment, etc.), and parking duration in real time to obtain the user's payment information. The user's payment information is then sent to the associated invoicing unit.

[0034] Step S300: The associated invoicing unit receives the user payment information and the user invoicing information, and automatically generates an electronic invoice according to a preset invoice format.

[0035] In this embodiment of the present application, after receiving user payment information and user invoicing information, the invoicing association unit first determines the type of data to be captured based on a preset invoice format. Then, based on the determined data capture type, it automatically extracts relevant data from the user payment information and invoicing information to form invoicing association information. Finally, based on this association information, it automatically populates the invoice content and generates an electronic invoice.

[0036] Furthermore, in the method provided in the embodiment of the application, the associated invoicing unit receives the user payment information and the user invoicing information, and automatically generates an electronic invoice according to a preset invoice format, further comprising:

[0037] Based on a preset invoice format, a data capture type is determined; according to the data capture type, associated data of the user payment information and the user invoicing information is captured to obtain invoicing associated information; according to the invoicing associated information, the invoice content is automatically filled in to generate the electronic invoice.

[0038] In this embodiment of the present application, the associated invoicing unit first determines the type of data to be captured based on a pre-set invoice format. This pre-set invoice format is designed according to pre-set standards and defined in XML or JSON format, including all required invoice fields, such as the invoice header, amount, and tax rate. Based on these standard format requirements, the associated invoicing unit identifies the data types to be extracted from the user's payment information and invoicing information. This data includes information such as the payment amount, payment time, parking duration, invoice header, and invoicing address.

[0039] Then, based on the determined data capture type, the system automatically captures related data. Details such as the payment amount, payment time, and parking duration are extracted from the user's payment information. This information is then linked to the user's invoicing information (such as the invoice header, tax number, and receipt method) to form complete invoicing information. This process relies on data mapping technology, matching and extracting relevant information stored in the database to ensure that the captured data is complete and meets invoice requirements.

[0040] Finally, the invoice content is automatically filled in based on the captured invoicing information. During this process, according to the preset invoice format, the data filling algorithm fills the payment amount, tax amount, invoice header and other information into each field of the invoice, ensuring that each information complies with tax requirements and generates an electronic invoice.

[0041] Step S400: The electronic invoice is automatically pushed to the user terminal through the user's preset push channel, and the user payment information, user billing information and electronic invoice are encrypted, stored and backed up.

[0042] In the embodiment of the present application, first, when the user registers a payment account, multiple push methods are configured and the user's preset push channel (such as email, SMS or platform notification) is determined. After the electronic invoice is generated, the electronic invoice is automatically sent to the user terminal according to the push channel selected by the user.

[0043] To ensure data security, we use symmetric encryption algorithms (such as AES) to encrypt user payment information, billing information, and electronic invoices, generating encrypted data. This encrypted data is stored in association with the user's account information and, using time-based identifiers, generates an associated billing sequence to ensure data integrity and traceability. This data is backed up regularly, and a backup data query interface is provided to clients to ensure user data can be restored when needed.

[0044] Furthermore, in the method provided in the embodiment of the application, the electronic invoice is automatically pushed to the user terminal through the user preset push channel, and further includes:

[0045] Configure multiple push methods to the user end, and determine the user's preset push channel when the user registers a payment account; automatically push the electronic invoice based on the user's preset push channel; based on the preset period, continuously collect the preset push channel type selected by the user, analyze the user's commonly used push methods, and perform personalized push configuration.

[0046] In the embodiments of this application, multiple push methods (such as email, SMS, platform notifications, etc.) are configured when the user registers a payment account. A user-preset push channel is also determined when the user registers a payment account. A push method refers to the channel selected by the user for receiving electronic invoices, and a user-preset push channel refers to the preferred method selected by the user during the registration process. For example, a user can select email as the method for receiving electronic invoices, or select SMS to receive an invoice link.

[0047] Once an e-invoice is generated, it is automatically pushed to the user's end-user via the pre-set push channel selected during user registration. This automated process ensures timely and accurate delivery of the invoice to the user's designated channel, such as emailing the e-invoice to the user's mailbox or sending a text message containing the e-invoice link via SMS. Seamless invoice push based on the user's selected channel reduces the complexity and delays of manual operations.

[0048] In addition, based on a preset cycle, the push channel types selected by users are continuously collected, and the push methods commonly used by users are analyzed through data analysis tools. This preset cycle refers to a set regular update cycle (such as monthly, quarterly, etc.), during which users' push channel usage is monitored. Through analysis, the user's commonly used push methods are identified. For example, if a user frequently receives invoices via SMS, SMS will be prioritized as the push method in the future, allowing for personalized push configuration and optimizing the user's receiving experience.

[0049] Furthermore, in the method provided in the embodiment of the application, the user payment information, user billing information and electronic invoice are encrypted, stored and backed up, and further includes:

[0050] A symmetric encryption algorithm is used to encrypt user payment information, user billing information and electronic invoices to generate encrypted invoicing data; the encrypted invoicing data is associated with the corresponding account in the user database and stored, and time nodes are identified to generate an associated invoicing sequence; the associated invoicing sequence is backed up regularly, and a backup data query interface is provided to the client.

[0051] In the embodiments of the present application, a symmetric encryption algorithm (such as the AES algorithm) is first used to encrypt user payment information, user invoicing information, and the generated electronic invoice. The symmetric encryption algorithm uses the same encryption key to encrypt and decrypt data, ensuring the security of the data during transmission and storage. The encrypted data is called encrypted invoicing data, which includes the user's payment details, invoicing information, and the content of the electronic invoice. All of this data is encrypted to prevent unauthorized access or tampering.

[0052] The encrypted invoicing data is then linked to the corresponding account information stored in the user database. The user database is where all user information is stored. By linking the encrypted data with user account information, each user's data is accurately stored and traceable. Furthermore, a time node identifier is added to each record, using a timestamp or version number to identify the time of each operation and generate a linked invoicing sequence. This sequence tracks the chronological order of data generation, ensuring that all invoice information can be retrieved and managed based on time.

[0053] To ensure data security and integrity, associated invoicing sequences are regularly backed up. This backup ensures data recovery even in the event of a system failure or data loss. Backup data is stored in secure storage media, such as cloud storage, ensuring long-term security and reliability. Furthermore, a backup data query interface is provided to clients, allowing users or administrators to query and restore backup data as needed, ensuring data accessibility and recovery capabilities.

[0054] In the embodiments of the present application, in summary, the embodiments of the present application have at least the following technical effects:

[0055] When a user enters a parking lot for the first time, the present application obtains the license plate information of the target vehicle through the license plate recognition unit, associates the license plate information with the user's registered account, obtains the user's invoicing information and sends it to the associated invoicing unit; when the target vehicle completes the parking payment, obtains the user's payment information and sends it to the associated invoicing unit; the associated invoicing unit receives the user's payment information and the user's invoicing information, and automatically generates an electronic invoice according to a preset invoice format; the electronic invoice is automatically pushed to the user end through the user's preset push channel, and the user's payment information, user's invoicing information and electronic invoice are encrypted, stored and backed up. The present invention solves the technical problems of the prior art, such as the cumbersome parking payment and invoicing process, inconvenient user operation, and frequent invoice errors. By automating license plate recognition, payment information acquisition, automatic generation and push of invoicing information, and encrypted storage and backup, the present invention achieves the technical effects of simplifying the parking payment and invoicing process, improving user operation convenience, and ensuring the accuracy of invoice generation.

[0056] Example 2 is based on the same inventive concept as the automatic invoicing method for parking payment for C-end users in the above embodiment. Figure 2 As shown, this application provides an automatic parking payment invoicing system for C-end users. The system and method embodiments in this application are based on the same inventive concept. The system includes:

[0057] The license plate information acquisition module 11 is used to obtain the license plate information of the target vehicle through the license plate recognition unit when the user enters the parking lot for the first time, and associate the license plate information with the user's registered account, obtain the user's billing information and send it to the associated billing unit; the payment information acquisition module 12 is used to obtain the user's payment information and send it to the associated billing unit after the target vehicle completes the parking payment; the electronic invoice generation module 13 is used for the associated billing unit to receive the user payment information and the user billing information, and automatically generate an electronic invoice according to the preset invoice format; the information sending module 14 is used to automatically push the electronic invoice to the user end through the user's preset push channel, and encrypt and store and back up the user payment information, user billing information and electronic invoice.

[0058] Furthermore, the system is also used to implement the following functions:

[0059] The image sensing module of the license plate recognition unit is used to capture the license plate image of the target vehicle in real time, and input it into the built-in license plate recognizer to convert it into digital license plate information; based on the digital license plate information, the user database of the target parking lot is traversed, the user registration account information is automatically identified and matched, and preliminary information binding is performed.

[0060] Furthermore, the system is also used to implement the following functions:

[0061] When the license plate information matches a registered user account in the user database, the user billing information is automatically associated and obtained; if the license plate information does not match a registered user account, an account registration instruction is pushed to prompt the user to register and bind the account and fill in the user billing information.

[0062] Furthermore, the system is also used to implement the following functions:

[0063] The license plate recognizer comprises an image acquisition module, a license plate positioning module, a character segmentation module, a character recognition module and an output processing module.

[0064] Furthermore, the system is also used to implement the following functions:

[0065] Based on a preset invoice format, a data capture type is determined; according to the data capture type, associated data of the user payment information and the user invoicing information is captured to obtain invoicing associated information; according to the invoicing associated information, the invoice content is automatically filled in to generate the electronic invoice.

[0066] Furthermore, the system is also used to implement the following functions:

[0067] Configure multiple push methods to the user end, and determine the user's preset push channel when the user registers a payment account; automatically push the electronic invoice based on the user's preset push channel; based on the preset period, continuously collect the preset push channel type selected by the user, analyze the user's commonly used push methods, and perform personalized push configuration.

[0068] Furthermore, the system is also used to implement the following functions:

[0069] A symmetric encryption algorithm is used to encrypt user payment information, user billing information and electronic invoices to generate encrypted invoicing data; the encrypted invoicing data is associated with the corresponding account in the user database and stored, and time nodes are identified to generate an associated invoicing sequence; the associated invoicing sequence is backed up regularly, and a backup data query interface is provided to the client.

[0070] It should be noted that the order in which the embodiments of the present application are presented is for illustrative purposes only and does not necessarily represent the superiority or inferiority of the embodiments. Furthermore, the foregoing descriptions of specific embodiments of this specification are provided. The processes depicted in the accompanying drawings do not necessarily require the specific order or sequential sequence shown to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0071] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

[0072] This specification and drawings are merely illustrative of the present application and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Obviously, those skilled in the art may make various modifications and variations to this application without departing from the scope of this application. Thus, this application is intended to include such modifications and variations as fall within the scope of this application and its equivalents.

Claims

1. The automatic invoicing method for parking payment for C-end users is characterized by: The method comprises: When a user enters the parking lot for the first time, the license plate information of the target vehicle is obtained through the license plate recognition unit, and the license plate information is associated with the user's registered account, and the user's billing information is obtained and sent to the associated billing unit; When the target vehicle completes the parking payment, the user payment information is obtained and sent to the associated invoicing unit; The associated invoicing unit receives the user payment information and the user invoicing information, and automatically generates an electronic invoice according to a preset invoice format; The electronic invoice is automatically pushed to the user end through the user's preset push channel, and the user payment information, user billing information and electronic invoice are encrypted, stored and backed up.

2. The automatic invoicing method for parking payment for C-end users according to claim 1 is characterized in that: Acquiring the license plate information of the target vehicle through the license plate recognition unit and associating the license plate information with the user's registered account, including: The image sensor module of the license plate recognition unit is used to capture the license plate image of the target vehicle in real time, and input it into the built-in license plate recognizer to convert it into digital license plate information; Based on the digital license plate information, the user database of the target parking lot is traversed, the user registration account information is automatically identified and matched, and preliminary information binding is performed.

3. The automatic invoicing method for parking payment for C-end users according to claim 2 is characterized in that: Obtain user billing information and send it to the associated billing unit, including: When the license plate information matches a registered user account in the user database, automatically associate and obtain the user's ticketing information; If the license plate information does not match a registered user account, an account registration instruction will be pushed to prompt the user to register and bind the account and fill in the user's billing information.

4. The automatic invoicing method for parking payment for C-end users according to claim 2 is characterized in that: The license plate recognizer comprises an image acquisition module, a license plate positioning module, a character segmentation module, a character recognition module and an output processing module.

5. The automatic invoicing method for parking payment for C-end users according to claim 1 is characterized in that: The associated invoicing unit receives the user payment information and the user invoicing information, and automatically generates an electronic invoice according to a preset invoice format, including: Determine the data capture type based on the preset invoice format; According to the data capture type, the user payment information and the user invoicing information are associated with each other to obtain invoicing associated information; According to the invoicing related information, the invoice content is automatically filled in to generate the electronic invoice.

6. The automatic invoicing method for parking payment for C-end users according to claim 1 is characterized in that: Automatically push the electronic invoice to the user terminal through the user's preset push channel, including: Configure multiple push methods to the user end, and determine the user's preset push channel when the user registers a payment account; Automatically push the electronic invoice based on the user's preset push channel; Based on the preset cycle, the preset push channel types selected by users are continuously collected, the user's commonly used push methods are analyzed, and personalized push configuration is performed.

7. The automatic invoicing method for parking payment for C-end users according to claim 2 is characterized in that: Encrypted storage and backup of the user payment information, user billing information and electronic invoices, including: Use symmetric encryption algorithms to encrypt user payment information, user billing information, and electronic invoices to generate encrypted billing data; The encrypted invoicing data is associated with the corresponding account in the user database and stored, and a time node is marked to generate an associated invoicing sequence; The associated invoicing sequence is backed up regularly, and a backup data query interface is provided to the client.

8. The automatic parking payment invoicing system for C-end users is characterized by: The system comprises: The license plate information acquisition module is used to obtain the license plate information of the target vehicle through the license plate recognition unit when the user enters the parking lot for the first time, associate the license plate information with the user's registered account, obtain the user's billing information, and send it to the associated billing unit; A payment information acquisition module, configured to acquire user payment information and send it to the associated invoicing unit after the target vehicle completes parking payment; An electronic invoice generation module, configured for the associated invoicing unit to receive the user payment information and the user invoicing information and automatically generate an electronic invoice according to a preset invoice format; The information sending module is used to automatically push the electronic invoice to the user terminal through the user's preset push channel, and encrypt, store and back up the user payment information, user billing information and electronic invoice.