Government affair service platform-oriented parking information processing method and system

Abstract

The invention discloses a parking information processing method and system for a government affair service platform, and the method comprises the steps: obtaining license plate recognition data uploaded by a parking lot entrance hardware device, determining an associated parking user ID based on the license plate recognition data, and calling the associated designated user data based on the parking user ID; the specified user data is verified, and a channel opening instruction is sent to a parking lot execution device after verification is passed, so that the execution device controls a lifting rod; the parking lot exit license plate data uploaded by the parking lot exit hardware device is received, and the deduction logic of the amount payable is triggered, and the deduction logic of the amount payable comprises the steps of determining a parking fee; and calling payment logic, generating a payment voucher and updating the credit performance state of the user after the user completes payment, and synchronizing the payment voucher and the updated credit performance state of the user to the government affair service platform. And intelligent parking facing the government affair platform is realized.

Description

Technical Field

[0001] This invention relates to the field of information processing technology, specifically to a method and system for processing parking information for government service platforms. Background Technology

[0002] Currently, the technical solutions related to "government affairs + parking" in the industry mainly focus on "data integration" and "basic service integration," specifically including the following three categories: (a) A shallow linking scheme between government service platforms and parking platforms The API interface enables a "jump link" between government apps and parking platforms: when users click the "Parking Service" module in government apps such as "Su Zhoudao," they are redirected to a third-party parking app or H5 page; parking data (such as payment records) is only synchronized to the government platform in one direction to display "My Bills," without achieving interoperability of the user system—users need to re-register accounts and bind vehicles on the parking platform, and the identity information of the government account (such as ID card number and real-name authentication status) is not reused, resulting in problems such as "one person, multiple accounts" and "duplicate information entry."

[0003] (ii) Seamless payment solution based on a single platform Some parking platforms achieve seamless payment through "license plate binding + password-free payment": users bind their license plate to Alipay / WeChat for password-free payment within the parking app, and the system automatically recognizes the license plate, calculates the fee, and deducts it upon exiting. However, this solution has two major limitations: First, it is not linked to the government credit system, requiring all users to enable password-free payment, making it impossible to provide differentiated services based on government credit scores (such as allowing high-credit users to park first and pay later without enabling password-free payment); second, the payment chain is isolated and not linked to government-related preferential policies (such as requiring manual verification for disabled people to enjoy parking discounts based on government-certified status, which cannot be automatically deducted).

[0004] (III) Multi-lane parking service plan The system provides multi-terminal services through "APP + Mini Program + Roadside Screen": the APP supports full functionality (vehicle binding / payment / invoice), the Mini Program only supports payment and parking location, and the Roadside Screen only displays available parking spaces; however, data is not synchronized in real time between multiple channels: for example, a vehicle bound to a user's Mini Program cannot be found in the APP; parking coupons obtained in the APP cannot be used at roadside self-service payment machines; and it is not integrated with government service channels (such as government APPs with built-in Mini Programs, government service hall terminals), so users still need to switch between government and parking channels.

[0005] The above method has the following problems: 1. Fragmented user system with poor reusability: Government accounts and parking accounts are independent, failing to achieve "one-time real-name authentication, universal applicability across multiple platforms"—Users have completed real-name authentication on government platforms such as "Suzhou Zhoudao", but when using parking services, they still need to resubmit their identity information and bind their vehicles. This not only increases the user's operational costs, but also prevents government data (such as credit scores and special identity authentication) from empowering parking services (e.g., military personnel and disabled persons need to submit proof repeatedly for parking discounts).

[0006] 2. The seamless payment process is isolated and has weak scenario adaptability: The existing seamless payment only relies on "license plate + password-free payment" and does not link government data to form a "credit-payment" closed loop: On the one hand, government credit scores are not reused, resulting in insufficient service differentiation; on the other hand, government scenario tags are not associated.

[0007] 3. Fragmented multi-channel services and inconsistent user experience: The channels for parking services (APP, mini-program, offline terminals, and government service platforms, such as government service APP and self-service machines in government service halls) have not achieved "data interoperability and functional complementarity": First, the data is not synchronized (e.g., the availability information queried in the government service APP deviates by more than 10% from the real-time availability information in the parking mini-program); second, the functions are not unified (e.g., the government service hall terminal only supports payment and does not support invoice issuance, requiring users to switch to the parking APP); third, the services are not linked (it cannot automatically push parking guidance information around the corresponding government service). Summary of the Invention

[0008] The main objective of this invention is to provide a parking information processing method for government service platforms, in order to address the shortcomings of related technologies.

[0009] To achieve the above objectives, according to a first aspect of the present invention, a parking information processing method for a government service platform is provided, comprising: acquiring license plate recognition data uploaded by hardware devices at the parking lot entrance; determining a parking user ID associated with the license plate recognition data; calling specified user data associated with the parking user ID; verifying the specified user data; and, upon successful verification, sending an opening channel instruction to the parking lot execution device for the execution device to control the gate to open; receiving exit license plate data uploaded by hardware devices at the parking lot exit; and triggering a deduction logic for the amount due. The deduction logic includes: determining the parking fee; invoking payment logic; generating a payment voucher and updating the user's credit performance status after the user completes payment; and synchronizing the payment voucher and the updated user credit performance status to the government service platform.

[0010] According to a second aspect of the present invention, a parking information processing system for a government service platform is provided, comprising: an entry verification unit, which acquires license plate recognition data uploaded by hardware devices at the parking lot entrance, determines a parking user ID associated with the license plate recognition data, and calls associated specified user data based on the parking user ID; verifies the specified user data, and sends an opening channel instruction to the parking lot execution device after successful verification, so that the execution device can control the gate to be raised; and an exit processing unit, which receives exit license plate data uploaded by hardware devices at the parking lot exit, and triggers a deduction logic for the amount due, wherein the deduction logic includes: determining the parking fee; calling payment logic, and generating a payment voucher and updating the user's credit performance status after the user completes payment, and synchronizing the payment voucher and the updated user credit performance status to the government service platform.

[0011] This embodiment relates to a parking information processing method and system for a government service platform. The method includes: acquiring license plate recognition data uploaded by hardware devices at the parking lot entrance; determining the associated parking user ID based on the license plate recognition data; retrieving the associated specified user data based on the parking user ID; verifying the specified user data; and, upon successful verification, sending an opening command to the parking lot execution device for control of the barrier gate; receiving exit license plate data uploaded by hardware devices at the parking lot exit; and triggering a deduction logic for the outstanding amount. This deduction logic includes: determining the parking fee; invoking payment logic; generating a payment voucher and updating the user's credit performance status after payment is completed; and synchronizing the payment voucher and the updated user credit performance status to the government service platform. This achieves smart parking for the government service platform. Attached Figure Description

[0012] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0013] Figure 1 This is a flowchart of a parking information processing method for a government service platform according to an embodiment of the present invention. Detailed Implementation

[0014] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0015] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate for the embodiments of the invention described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0016] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0017] According to embodiments of the present invention, a method for processing parking information for government service platforms is provided, such as... Figure 1 As shown, steps 101 to 102 are included below: Step 101: Obtain license plate recognition data uploaded by the hardware device at the parking lot entrance; determine the associated parking user ID based on the license plate recognition data; call the associated specified user data based on the parking user ID; verify the specified user data; and after successful verification, send the channel opening command to the parking lot execution device so that the execution device can control the gate to be raised.

[0018] Step 102: Receive the exit license plate data uploaded by the parking lot exit hardware device and trigger the payable amount deduction logic. The payable amount deduction logic includes: determining the parking fee; calling the payment logic, and generating a payment voucher and updating the user's credit performance status after the user completes the payment, and synchronizing the payment voucher and the updated user credit performance status to the government service platform.

[0019] As an optional implementation of this embodiment, before obtaining the license plate recognition data uploaded by the parking lot entrance hardware device, the method includes: receiving a parking service authorization request initiated by a user through any service channel; calling the open interface of the government service platform to obtain the user's specified information, wherein the specified information includes the user's unique identity identifier, real-name authentication status, government credit rating, and government authentication identity label; generating a parking user ID based on a hash algorithm and the user's specified information; and synchronizing the parking user ID to the database of all service channels through an MQ message queue component, wherein the parking user ID is associated with the license plate.

[0020] In this implementation, a user initiates a smart parking service authorization request through any service channel (government service platform APP / mini-program, parking APP / mini-program, vehicle system), which calls the government service platform's open interface to obtain the user's unique identifier (hash value of the user's ID card number), real-name authentication status, government credit score, and government-certified identity tag (a special identity identifier verified by the government service platform). A parking user ID (a government-parking universal identity code generated by a computer using a hash algorithm) is generated based on a hash algorithm and established in a one-to-one correspondence with the user's unique identifier (the user's unique identifier is the hash value of the user's ID card number on the government platform, i.e., your identity identifier encrypted by the government system). This "universal identity code" parking user ID is bound one-to-one with your "government-specific ID card"—for example, if the government identifier is "hash ID card number A," the corresponding cross-domain mapping ID is "XYZ123," ensuring a permanent one-to-one connection and preventing confusion with others. To address the issue of "government accounts and parking accounts being two different things," the parking system can identify you as a verified user on the government platform using a "universal identity code." This links your parking service account (for example, automatically creating / binding a parking service account using this "universal identity code" without requiring manual registration of a parking app account). Because your government identity has already undergone real-name authentication (the government platform verifies "you are you"), the parking system directly reuses this authentication result, linking the parking account through the "universal identity code," eliminating the need for repeated ID card and facial verification. The system uses an MQ message queue component to synchronize user-bound data (vehicle information, permission level) to the databases of all service channels (core data such as the bound license plate and your permission level: Class A (deposit-free) / Class C (deposit required), synchronized to the databases of all service channels you might use (government app, parking mini-program, government service hall self-service machine, vehicle system, etc.)). This completes the binding of the entire user system across all channels, forming a user data foundation of "one-time authentication, universal access across multiple platforms."

[0021] For example, the classification rules for the A / B / C permission levels are as follows: a government credit score ≥ 90 points is classified as Class A, 80 points ≤ government credit score < 90 points is classified as Class B, and a government credit score < 80 points is classified as Class C; the user binding data is synchronized through the MQ message queue with a delay of ≤ 1 second to ensure that the vehicle information, permission level, and payment channel information queried by the user in any service channel are consistent.

[0022] As an optional implementation of this embodiment, the method further includes determining the parking lot to be recommended: pulling government service scenario dimension data from the interface of the government service platform, extracting user attribute dimension data from the parking user ID binding data, obtaining parking resource dimension data from the parking management system and roadside sensing devices, and obtaining spatiotemporal dynamic dimension data from the designated business system. The government service scenario dimension data includes a scenario tag (Tag_scene), tag validity period (T_valid), and scenario priority (P_scene); the user attribute dimension data includes a government credit rating (Grade_credit), identity tag (Tag_iden), and bound license plate (Plate_set); the parking resource dimension data includes parking lot location (Loc_park), availability rate (Rate_remain), charging rule (Rule_fee), and discount adaptation tag (Tag_park); the spatiotemporal dynamic dimension data includes the user's real-time location (Loc_user), the estimated scenario duration (T_scene), and the traffic congestion index (Index_c). The process involves: first, filtering expired tags based on the current date and tag validity period (T_valid); second, calculating the comprehensive tag weight (W_tag) based on scene priority (P_scene) and user identity tag (Tag_iden); third, sorting by W_tag in descending order to determine the first-ranked scene; fourth, dynamically determining and filtering initial parking lots using the location information within the scene as the center and a preset radius, and removing parking lots from the initial parking lots whose vacancy rate does not meet a preset value to obtain a candidate set (Park_candidate); fifth, calculating the scene fit (S_fit) for each candidate parking lot in the candidate set; sixth, determining the resource weight (W_park) based on the scene's estimated time (T_scene), charging rule (Rule_fee), and vacancy rate (Rate_remain); seventh, calculating the comprehensive matching score (S_total) for each candidate parking lot based on the comprehensive tag weight (W_tag), scene fit (S_fit), and resource weight (W_park); and finally, sorting by S_total in descending order and selecting the top k parking lots as recommended parking lots.

[0023] Collect multi-dimensional input parameters: Pull government service scenario dimension data (scenario tag Tag_scene, tag validity period T_valid, scenario priority P_scene) from the government service platform interface. Government service scenario tags include scenario types such as medical appointment, education registration, and government affairs. The scenario tag data comes from business modules such as the medical appointment system and education registration system of the government service platform.

[0024] Extract user attribute dimension data (Government credit rating Grade_credit, identity tag Tag_iden, bound vehicle Plate_set) from user binding data; obtain parking resource dimension data (parking lot location Loc_park, vacancy rate Rate_remain, charging rule Rule_fee, discount adaptation tag Tag_park) from parking management system and roadside sensing equipment; and obtain spatiotemporal dynamic dimension data (real-time user location Loc_user, estimated scene time T_scene, traffic congestion index Index_congest) from GPS / base station positioning, government scenario system and traffic control platform. The computer system performs scene tag cleaning and priority sorting through algorithms: filtering out expired tags (T_current>T_valid), calculating the comprehensive weight of tags according to the formula W_tag=P_scene×(1+0.3×I(Tag_iden)) (I(Tag_iden) is the identity weight coefficient, I=1 for special identities such as "disabled persons" and "military personnel", and I=0 for ordinary users), and taking the top 1 core scene tag as the service matching benchmark by sorting W_tag in descending order; The computer system performs parking resource screening and suitability calculations using algorithms: Using the target location corresponding to the core scene label as the center, a screening range is dynamically determined with a radius R = 3km + Index_congest × 2km; parking lots with a vacancy rate <10% are filtered to obtain a candidate set Park_candidate; the scene suitability of each candidate parking lot is calculated. S_fit = 1 - [|Loc_parkj - Loc_scene| / R] × (1 - Match(Tag_parkj, Tag_scene)) (Match is the tag matching function, exact match = 1, no match = 0), and the resource weight is calculated by combining the remaining space ratio and the discount strength: W_park = Rate_remain × (1 + 0.5 × Discount(Tag_scene, Rule_fee)), where Discount is the discount coefficient: first 2 hours free = 1, discount rate ≥ 50% = 0.8, discount rate < 50% = 0.5, no discount = 0). The computer system uses algorithms to perform service matching and scoring.

[0025] Calculation and recommendation generation: S_total = W_tag × S_fit × W_park + 0.2 × (1 / Time_cost) (Time_cost is the estimated time for the user to reach the parking lot, in minutes). Calculate the comprehensive matching score and select the top 3 parking lots as recommended resources. Generate a scenario-based service package, where basic services include parking lot navigation (including real-time traffic conditions), real-time availability synchronization, and reservation (reservation duration = T_scene × 1.2). Differentiated services are configured according to user attributes (Category A users → no deposit + pay later; disabled users → dedicated parking space + 50% fee reduction; medical users → first 2 hours free + outpatient building shuttle guidance). e. The computer system executes service triggering and resource reservation through algorithms: the push timing is determined according to the formula T_push=T_start-Time_cost-15 minutes (T_start is the expected start time of the scenario), and a reservation instruction (including the user's bound vehicle Plate_set, the exclusive parking space number assigned based on the identity tag Tag_iden, and the reservation validity period = T_valid_end+30 minutes) is sent to the Top1 recommended parking lot through the MQ message queue; at the T_push time, the scenario-based service package is pushed synchronously through the user's currently used service channel and the backup channel (SMS), supporting one-click navigation triggering.

[0026] This embodiment can achieve unified access to multi-source parking resources in the following way: Through standardized interfaces (cascading mode for connecting to district / county parking platforms, and direct connection mode for connecting to commercial / public parking systems), resource data from urban road parking spaces (geomagnetic and high-position video data collection), commercial parking lots (gate barriers and management systems), and public parking lots (dedicated parking spaces and payment systems) can be integrated to achieve a "unified network for parking resources across the entire region." For all parking scenarios, core data such as location (Loc_park), availability rate (Rate_remain), charging rules (Rule_fee), and adaptation tags (Tag_park) are collected synchronously to eliminate data format differences between different parking lots.

[0027] This embodiment's full-scenario resource filtering logic includes filtering all types of parking lots within a dynamic radius, regardless of road, commercial, or public attributes. The filtering criteria are "reservation rate ≥ 10%" and "scenario adaptability ≥ 0.3," ensuring that all scenario resources are included in the scheduling pool. Differentiated adaptation to full-scenario needs includes adjusting scheduling priorities based on the different characteristics of on-street parking (short-term parking), commercial parking lots (consumption-related), and public parking lots (government / public service scenarios) through "preferential adaptation tags (Tag_park)" and "resource weights (W_park)." For example, government scenarios prioritize matching public parking lots, while consumption scenarios prioritize matching commercial parking lots. For instance, urban on-street parking accesses resource data through roadside sensing devices (geomagnetic sensors, high-position video). The SSWMA-V2 algorithm schedules parking based on "short-term parking + high availability priority," while the CPVCA-V2 algorithm adapts to "hourly billing + government preferential treatment (such as discounts for disabled persons)." Commercial parking lots can connect to the management system via direct connection, with the algorithm prioritizing scheduling based on "consumption scenario tags," supporting the combined deduction of commercial and government preferential treatments. Public parking lots can be connected to the public service platform through a cascading mode. The algorithm prioritizes matching government service scenarios (medical treatment, business handling), reserves dedicated parking spaces, and implements scenario-based discounts (such as free for the first 2 hours).

[0028] The full-scenario data synchronization process based on MQ message queues enables real-time synchronization of parking space availability, order, and discount data across all types of parking lots via government apps, parking mini-programs, and roadside screens (with a latency of ≤1 second), avoiding scheduling fragmentation issues such as "inconsistent roadside parking space availability" and "incompatibility of discounts for commercial parking lots." The cross-scenario user data reuse process, with a unified user system (user ID), eliminates the need for users to be repeatedly bound to different types of parking lots. During scheduling, government credit and vehicle information can be directly reused, ensuring the continuity of scheduling across all scenarios.

[0029] The unified billing and payment rules apply to urban roads (time-based billing), commercial areas (consumer-linked discounts), and public parking lots (government-related fee reductions), employing a unified calculation logic of "basic fee + tiered discounts" to adapt to the charging characteristics of different scenarios. Full-scenario credit and permission adaptation is implemented, based on government credit ratings (A / B / C categories), uniformly enforcing the "deposit-free / pre-deposit" rule for all types of parking lots. High-credit users can enjoy "park first, pay later" permissions in roads, commercial areas, and public parking lots, ensuring service consistency after dispatch.

[0030] It is applicable to the scheduling of parking resources in all scenarios such as urban road parking, commercial parking lots, and public parking lots. It can realize cross-domain collaboration between "government users - parking services - public resources" and form a smart service model of "one-time registration, multi-terminal universality, one-time binding, and seamless access". At the same time, it links government public service resources such as transportation, medical care, and education to provide citizens with an integrated solution of "parking + government services".

[0031] As an optional implementation method in this embodiment, the verification of the specified user data includes verifying the specified user data to determine whether a deposit needs to be prepaid: if the user's government credit rating is the first specified level, then the deposit is calculated; a deposit payment reminder is pushed, and a deposit payment voucher Voucher_deposit is generated after the user completes the payment; if the user's government credit rating is the second specified level, then a deposit exemption voucher Voucher_deposit is generated.

[0032] As an optional implementation of this embodiment, after successful verification, the channel opening command is sent to the parking lot execution device for the execution device to control the gate to lift the barrier, including: generating an entry voucher_in based on an asymmetric encryption algorithm; and synchronizing the entry voucher_in and the gate lifting control command to the parking lot barrier device and the user's current service channel.

[0033] In this optional implementation, the system receives the license plate number Plate_no uploaded by the parking lot entrance hardware devices (license plate capture camera, ground loop coil), associates Plate_no with the user ID (ID_map), retrieves user binding data and resource reservation information generated by the SSWMA-V2 algorithm, and completes license plate matching and reservation eligibility verification; it then calls the government credit interface to verify the user's government credit rating Grade_credit and credit validity period T_credit, and determines whether a deposit needs to be prepaid. If Grade_credit is A / B: deposit waiver, generate a "deposit waiver voucher" (Voucher_deposit="none"); If Grade_credit is Class C: Calculate the deposit amount using the formula Deposit=Rule_deposit×(1-Rate_remain / 100) (Rule_deposit is the preset deposit rule; the deposit amount is increased when the remaining balance is low), send a deposit payment reminder, and generate a "deposit voucher" (Voucher_deposit, containing ID_map hash value, deposit amount, payment serial number, and deposit status) after the user completes the payment; c. The computer system executes the RSA-2048 asymmetric encryption algorithm to generate input... The entry voucher (Voucher_in) has the following data structure: {ID_map hash value, Plate_no desensitization, Grade_credit, entry time T_in, parking space Code_park, government signature}. The government signature is used to prevent data tampering. d. The computer system synchronizes the entry voucher (Voucher_in) and the barrier lifting control command to the parking lot gate equipment and the user's current service channel. After receiving the command, the gate equipment lifts the barrier to allow passage, and the user service channel simultaneously displays a "successful entry" reminder, reserved parking space information, and deposit status (if any).

[0034] For example, the government signature generation logic of the admission voucher Voucher_in is as follows: the computer system extracts the core fields of Voucher_in (ID_map hash value, T_in, Code_park), encrypts the core fields using the RSA-2048 asymmetric encryption algorithm, and generates a unique government signature to ensure that the admission data (such as credit rating, parking space number) is not tampered with.

[0035] For example, the allocation logic of parking space Code_park is as follows: priority is given to matching the exclusive parking spaces reserved by the SSWMA-V2 algorithm (such as parking spaces for disabled people and parking spaces for medical treatment). If there are no reserved parking spaces, ordinary parking spaces are allocated according to the principle of "parking nearby + best remaining space". The allocation result is synchronized to the entry voucher Voucher_in and the user service channel.

[0036] As an optional implementation in this embodiment, determining the parking fee includes: retrieving the entry voucher (Voucher_in), deposit voucher (Voucher_deposit), scene tag (Tag_scene), and identity tag (Tag_iden), and initiating the fee calculation logic; wherein, the fee calculation logic includes determining the basic fee based on the exit time, entry time, and parking fee standard; determining the tiered discount fee, including: matching discount rules based on the scene tag (Tag_scene), determining the first-level discount value based on the discount rules; determining the second-level discount value based on the discount rules corresponding to the identity tag (Tag_iden); determining the parking fee based on the basic fee and the tiered discount fee; generating a fee voucher (Voucher_fee) based on the parking fee and associating it with the entry voucher; and synchronizing the parking fee details to all service channels through an MQ message queue so that users can view it in real time through any channel, ensuring data consistency across all channels.

[0037] In this optional implementation, the system receives the exit license plate data uploaded by the parking lot exit hardware device, retrieves the entry voucher Voucher_in, deposit voucher Voucher_deposit (if any), and core scene tag Tag_scene and identity tag Tag_iden determined by the SSWMA-V2 algorithm, and starts the fee calculation logic.

[0038] Basic parking fee calculation: The basic fee is calculated using the formula Fee_base=ceil((exit time T_out-entry time T_in) / 30)×Rule_fee_30min (30 minutes is the billing unit, ceil is the rounding function, and Rule_fee_30min is the 30-minute fee standard). Tiered discount calculation: Level 1 Discount (Scenario Tag): Fee_discount1 = Discount Duration × Rule_fee_hour (Discount rules based on Tag_scene matching, such as free treatment for the first 2 hours); Secondary discount (identity tag): Fee_discount2=(Fee_base-Fee_discount1)×Discount_rate (Discount_rate is the discount rate corresponding to Tag_iden, such as 50% discount for disabled persons); Total discount amount: Fee_discount = Fee_discount1 + Fee_discount2, and Fee_discount ≤ Fee_base (the discount does not exceed the base fee). Calculation of payable amount: Fee_pay = Fee_base - Fee_discount - prepaid deposit (if any). If Fee_pay < 0, then take 0; The computer system generates a fee voucher Voucher_fee, whose data structure is {Voucher_in_ID, Fee_base, Fee_discount, Fee_pay, Rule_discount_ID, timestamp}, and forms a link association with the admission voucher through Voucher_in_ID; Rule_discount_ID is the unique identifier of the preferential rule, which associates with the specific terms in the government service rule library (such as "the first 2 hours are free for medical treatment users" and "the disabled are additionally exempted by 50%"). The fee voucher Voucher_fee can trace the source of the preferential rule through Rule_discount_ID, which is convenient for subsequent data verification and rule optimization.

[0039] Synchronize the fee details to all service channels through the MQ message queue, support users to view in real time through any channel, and ensure the consistency of data across all channels.

[0040] As an optional implementation of this embodiment, call the payment logic, generate a payment voucher and update the user's credit performance status after the user completes the payment. Synchronizing the payment voucher and the updated user's credit performance status to the government service platform includes: querying the balance Bal_pay of the payment channel Channel_pay bound by the user, and verifying whether the balance meets the payable amount Fee_pay: if Bal_pay ≥ Fee_pay, trigger automatic deduction and obtain the transaction serial number Trade_no; if Bal_pay < Fee_pay, push a reminder of insufficient balance for users of the second specified level; freeze the prepaid deposit for users of the first specified level and push a reminder of arrears; synchronize the payment result to the government credit platform, where a successful deduction records credit performance and the user's government credit score is increased; if the payment is not made up within the specified time, record credit default, the user's government credit score is decreased, and the user's permission level is lowered.

[0041] In this optional implementation, the process of contactless payment execution and voucher generation (executing Step 3 of the CPVCA-V2 algorithm) includes: a. The computer system queries the balance Bal_pay of the payment channel Channel_pay bound by the user, and verifies whether the balance meets the payable amount Fee_pay: If Bal_pay ≥ Fee_pay: trigger automatic deduction and obtain the transaction serial number Trade_no; If Bal_pay < Fee_pay: For type A / B users, a "balance insufficient" reminder is pushed, and补缴 deduction is supported after binding a new payment channel (bank card, Alipay); for type C users, the prepaid deposit is frozen, a "due payment reminder" is pushed, and payment is required within 24 hours; b. The computer system generates a payment voucher Voucher_pay, whose data structure is {Voucher_fee_ID, Channel_pay desensitized, Fee_pay, payment time T_pay, Trade_no, deduction status}; c. The computer system synchronizes the payment result to the government credit platform: successful deduction → record "credit fulfillment", user government credit score Score_credit + 0.5 points; failure to pay within 24 hours overdue → record "credit default", Score_credit - 5 points, and the user's permission level is downgraded to type D; d. The computer system synchronizes the payment status (success / under payment) to all service channels and parking lot gate devices. The gate device raises the pole immediately after receiving the "payment successful" signal.

[0042] Furthermore, it also includes electronic invoice push and data feedback (executed in Step 4 of CPVCA-V2 algorithm): a. Extract the fee information from the payment voucher Voucher_pay, call the tax system interface to generate an electronic invoice (including invoice code, invoice number, tax amount), and generate an invoice voucher Voucher_invoice, whose data structure is {Voucher_pay_ID, invoice information, push status, user receiving address}; Push the electronic invoice through multiple channels: The message center of the "Suzhou Service" APP, the parking applet, and the self-service terminal in the government affairs hall are the main channels, and SMS is the backup channel. It supports users to view, download, print online, or print a paper invoice by scanning the order QR code through the self-service terminal; Feed back two types of data to the data center of the government service platform: Service data: scene label Tag_scene, payment amount Fee_pay, parking lot utilization rate Rate_use, preferential usage frequency; Decision-making data: Statistics of parking flow by region / scene (such as the daily medical parking volume in a certain hospital), preferential usage rate of special identity users (such as the preferential usage rate of disabled people), to support the optimization of the layout of government public service resources (such as increasing the supply of parking lots around the hospital); Furthermore, the full-link data optimization includes integrating the scene label-service matching results, user service click-through rate, resource reservation utilization rate of the SSWMA-V2 algorithm, and the transaction closed-loop data of the CPVCA-V2 algorithm, and synchronizing them to the data center of the government service platform for optimizing the scene priority weight, parking lot preferential rules, government credit scoring adaptation strategy, and deposit rules.

[0043] For example, taking the scenario of "parking for medical treatment at a hospital" as an example, the implementation steps of the present invention are described in detail to ensure that those skilled in the art can reproduce it: (a) User system binding When a user opens a government service platform app such as "Su Zhoudao" and enters the "Smart Parking" service module, the system will display an "Authorization Binding" prompt. The system will then call the "Su Zhoudao" user center interface to obtain the user's real-name authentication status (authenticated), credit score (95 points, Category A), and identity tag (disabled person, with the tag "Today 10:00 outpatient appointment at a certain hospital"). A unique "Parking User Mapping ID" will be generated. The user will be prompted to bind their vehicle. After binding, the information will be synchronized to the user permission management module and marked with "Permission: No deposit required + unlimited parking and payment, Scenario tag: Medical treatment".

[0044] (ii) Credit verification and automatic gate lifting At 9:30, the user arrives at the parking lot entrance by car, and the license plate recognition device captures the vehicle. The system associates the license plate with the "parking user mapping ID", calls the government credit interface, confirms that the user is a Class A credit user (no deposit required) and has a "medical treatment" scenario tag. The verification is completed within 3 seconds, the barrier gate automatically opens, and an entry reminder is pushed to the "Su Zhoudao" APP ("Entered, you can enjoy free parking for the first 2 hours for medical treatment").

[0045] (III) Real-time calculation of scenario-based discounts The system uses a multi-channel data synchronization module to read parking space data in real time (such as "Parking Space No. 3 in Zone B" parked by a user) and synchronize it to the "My Parking" page of the "Su Zhoudao" APP; it calls the "Su Zhoudao" appointment interface to confirm the user's outpatient appointment time (10:00-11:00) and matches it with the hospital parking lot's preferential rule of "the first 2 hours are free for medical users, and the excess time is 5 yuan / hour"; it calculates the parking time in real time (such as 1 hour has been parked at 10:30, and 1 hour of free time remains), and displays "Current amount due: 0 yuan" in the "Su Zhoudao" APP in real time.

[0046] (iv) Seamless payment and invoice delivery At 11:40, the user drove to the exit, the license plate recognition device captured the license plate, and the system calculated the parking time (2 hours and 10 minutes). Automatic deduction of discount (first 2 hours free), the amount payable = 10 minutes × (5 yuan / 60 minutes) ≈ 0.83 yuan, rounded to 1 yuan; calling the "Suzhoudao" wallet interface (the user has already linked a bank card), automatically deducting 1 yuan, the barrier gate will open after successful deduction, taking ≤3 seconds; after the deduction is completed, the system will automatically generate an electronic invoice (including parking lot name, time, and amount), and push it to the user through the "Suzhoudao" message center; the user can view / download the invoice by clicking on the message, without being redirected to other platforms.

[0047] (v) Multi-channel service collaborative verification Government Service Hall Terminal: After processing medical insurance reimbursement at the hospital's government service hall, users can check their "Parking Orders" through the self-service machine in the hall. The machine will display "Paid 1 yuan, invoice available for printing". Click "Print" to obtain a paper invoice. Roadside guidance screens: When users return, the roadside guidance screens around the hospital display "20 parking spaces available at the target parking lot, and medical users can enjoy discounts", which is completely consistent with the parking space information in the "Su Zhoudao" APP; In-vehicle navigation system: If the user uses the in-vehicle navigation system, the system will call system data through API to automatically plan the route from "parking lot to home" and simultaneously display "Parking fee of 1 yuan, invoice has been sent to 'Suzhou Zhoudao'".

[0048] (vi) Handling Abnormal Scenarios If a user's "Suzhoudao" wallet balance is insufficient (e.g., only 0.5 yuan): the system will automatically push an "insufficient balance" reminder to the "Suzhoudao" APP, prompting "you need to pay 0.5 yuan to complete the exit"; after the user completes the payment in the APP, the system will update the payment status and the gate will open; after the payment is completed, it will not affect the user's government credit score (credit score will only be deducted if the payment is not made within 24 hours of the due date).

[0049] To address the three core problems in existing technologies—"fragmented user systems, isolated seamless payment, and fragmented multi-channel systems"—specific goals include: 1. Construct a unified user system for the "Su Zhoudao" government account and parking services: realize the reuse of government real-name authentication, credit scoring, and identity tags (such as disability) for parking services, eliminate the problems of "multiple account registration" and "repeated submission of proof", and form a user base of "one person, one account, universally applicable".

[0050] 2. Create a seamless payment link empowered by government data: link government credit data with scenario tags (such as medical treatment and schooling) to achieve a closed-loop transaction of "credit-based access (such as deposit waiver for high credit), scenario-based discounts (such as automatic parking fee reduction for medical treatment), and seamless process (entry recognition - fee calculation - automatic deduction - invoice push)", thereby reducing parking time for car owners.

[0051] 3. Achieve multi-channel service integration of "government services + parking": Connect multiple channels such as "Su Zhoudao" APP / mini-program, parking APP / mini-program, roadside guidance screens, government service hall terminals, and vehicle-mounted systems to ensure "real-time data synchronization, on-demand function adaptation, and proactive service linkage," forming a full-scenario coverage of "wherever the user is, the service is there."

[0052] The ultimate goal is to improve the efficiency of urban parking services (reducing the average parking time for car owners by more than 30%), strengthen the synergy between government services and public services, and provide support for the "Su Zhoudao" platform to build an integrated "government + public services" service ecosystem.

[0053] Compared with existing technologies, the core advantages of this invention are reflected in three dimensions: user experience, service efficiency, and ecosystem collaboration. (i) User experience is significantly improved and operating costs are greatly reduced. 1. No registration or duplicate authentication required: Based on the "same user system", users do not need to register again on the parking platform. Parking discounts for people with disabilities, military personnel and other special statuses do not need to submit proof repeatedly (government certification data is directly reused), reducing the operation steps by 70%. 2. Seamless passage throughout the entire process: From entry recognition to invoice delivery, car owners do not need to get out of the car or open the APP to operate. The average parking time has been reduced from 15 minutes to less than 10 minutes, especially solving the pain point of "queuing for payment during peak hours". 3. Proactive Service Adaptation: Based on government service scenario tags (such as medical treatment and schooling), the system automatically pushes preferential and guidance information, avoiding the cumbersome process of "manual inquiry-filtering-appointment" for users, and improving service accuracy by 80%.

[0054] (II) Improved Service Efficiency and Security 1. Optimized payment efficiency: The response time of the contactless payment link is ≤3 seconds (the average time for traditional manual payment is 3 minutes), and the passage efficiency of parking lot exits is improved by 5 times; 2. Credit risk is controllable: By reusing government credit data, the default rate of high-credit users (such as evasion of payment) is reduced to below 0.5% (the default rate of traditional parking platforms exceeds 5%), while the risk of low-credit users is controlled through the "pre-payment deposit" mechanism; 3. Data security and compliance: User data (such as ID card number and credit score) is only accessed through the official "Suzhoudao" interface and is not stored locally, which complies with the Personal Information Protection Law and government data security regulations, thus avoiding the risk of data leakage.

[0055] (III) Strengthening the ability to coordinate government affairs with people's livelihood and ecological environment 1. Extending the value of the government affairs platform: Adding high-frequency public services (parking) to "Su Zhoudao" increases user stickiness by more than 30%, while using parking data to support government decision-making (e.g., parking traffic reflects the number of patients received by the hospital). 2. Multi-channel resource integration: Streamline service channels between government services and parking to avoid "switching between multiple platforms." For example, the government service hall terminal enables one-stop operation of "social security processing + parking payment," reducing the time users spend in the government service hall by 20%. 3. Significant social benefits: Through functions such as "discounted parking for disabled persons," the government services are made more inclusive, while reducing parking circle behavior (guidance accuracy improved by 70%), thus alleviating urban traffic congestion.

[0056] It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be executed in a different order than that shown here.

[0057] According to an embodiment of the present invention, a parking information processing system for a government service platform is also provided, including an entry verification unit that acquires license plate recognition data uploaded by the hardware device at the parking lot entrance, determines the associated parking user ID based on the license plate recognition data, and calls the associated designated user data based on the parking user ID; verifies the designated user data, and sends an opening channel instruction to the parking lot execution device after successful verification, so that the execution device can control the gate to be raised; and an exit processing unit that receives exit license plate data uploaded by the hardware device at the parking lot exit, triggers the payable amount deduction logic, wherein the payable amount deduction logic includes: determining the parking fee; calling the payment logic, and generating a payment voucher and updating the user's credit performance status after the user completes the payment, and synchronizing the payment voucher and the updated user credit performance status to the government service platform.

Claims

1. A method for processing parking information for a government service platform, characterized in that, include: The system acquires license plate recognition data uploaded by the hardware device at the parking lot entrance, determines the associated parking user ID based on the license plate recognition data, and retrieves the associated specified user data based on the parking user ID. The system verifies the specified user data and, upon successful verification, sends an opening channel command to the parking lot execution device for the execution device to control the barrier to lift. The system receives exit license plate data uploaded by the parking lot exit hardware device and triggers the deduction logic for the amount due. The deduction logic includes: determining the parking fee; calling the payment logic; generating a payment voucher and updating the user's credit performance status after the user completes the payment; and synchronizing the payment voucher and the updated user credit performance status to the government service platform.

2. The parking information processing method for government service platforms according to claim 1, characterized in that, Before obtaining the license plate recognition data uploaded by the parking lot entrance hardware equipment, the methods include: The system receives parking service authorization requests initiated by users through any service channel, calls the open interface of the government service platform, and obtains the user's specified information, including the user's unique identity identifier, real-name authentication status, government credit rating, and government authentication identity label. A parking user ID is generated based on a hash algorithm and the user's specified information. The parking user ID is then synchronized to the database of all service channels via an MQ message queue component. The parking user ID is associated with the license plate.

3. The parking information processing method for government service platforms according to claim 2, characterized in that, The method also includes identifying parking lots to be recommended: The system retrieves government service scenario-level data from the government service platform's interface, extracts user attribute-level data from parking user ID binding data, obtains parking resource-level data from the parking management system and roadside sensing devices, and acquires spatiotemporal dynamic-level data from designated business systems. The government service scenario-level data includes scenario tag (Tag_scene), tag validity period (T_valid), and scenario priority (P_scene); user attribute-level data includes government credit rating (Grade_credit), identity tag (Tag_iden), and bound license plate (Plate_set); parking resource-level data includes parking lot location (Loc_park), availability rate (Rate_remain), charging rule (Rule_fee), and discount adaptation tag (Tag_park); and the spatiotemporal dynamic-level data includes real-time user location (Loc_user), estimated scenario duration (T_scene), and traffic congestion index (Index_congest). Filter expired tags based on the current date and tag validity period T_valid; The comprehensive weight W_tag of the tag is calculated based on the scenario priority P_scene and the user identity tag Tag_iden; Sort by W_tag in descending order to determine the scenario that ranks first; Using the location information in the scenario as the center, the initial parking lots are dynamically determined and filtered according to a preset radius, and parking lots whose vacancy rate does not meet the preset value are removed from the initial parking lots to obtain a candidate set Park_candidate; Calculate the scene fit S_fit for each candidate parking lot in the candidate set; Determine the resource weight W_park based on the expected time consumption T_scene of the scenario, the charging rule Rule_fee, and the remaining space rate Rate_remain; Calculate the comprehensive matching score S_total for each candidate parking lot based on the comprehensive weight W_tag of the label, the scenario suitability S_fit, and the resource weight W_park; Sort in descending order according to S_total, and select the top k parking lots as the recommended parking lots.

4. The parking information processing method for government service platforms according to claim 3, characterized in that, The method further includes: Send a reservation instruction to the terminal of the target recommended parking lot selected by the user from the recommended parking lots through the MQ message queue; At the T_push moment, synchronously push the scenario-based service package through the service channel currently used by the user.

5. The parking information processing method for government service platforms according to claim 1 or 3, characterized in that, Verifying the specified user data includes verifying the specified user data to determine whether a prepayment of the deposit is required: If the user's government affairs credit level is the first specified level, calculate the deposit; push a deposit payment reminder, and generate a deposit payment voucher Voucher_deposit after the user completes the payment; If the user's government affairs credit level is the second specified level, generate a deposit-free voucher Voucher_deposit.

6. The parking information processing method for government service platforms according to claim 3, characterized in that, After passing the verification, send an open-channel instruction to the parking lot execution device for the execution device to control the lifting of the rod, including: Generate an entry voucher Voucher_in based on the asymmetric encryption algorithm; Synchronize the entry voucher Voucher_in and the lifting rod control instruction to the parking lot gate device and the user's current service channel.

7. The parking information processing method for government service platforms according to claim 3, characterized in that, Determine the parking fee, including: Retrieve the entry voucher Voucher_in, the deposit voucher Voucher_deposit, the scenario label Tag_scene, and the identity label Tag_iden, and start the fee calculation logic; Among them, the fee calculation logic includes determining the basic fee according to the exit time, the entry time, and the parking lot charging standard; determining the hierarchical preferential fee, including: matching the preferential rule based on the scenario label Tag_scene, and determining the first-level preferential value based on the preferential rule; determining the second-level preferential value based on the preferential rule corresponding to the identity label Tag_iden; Determine the parking fee based on the basic fee and the hierarchical preferential fee; generate a fee voucher Voucher_fee based on the parking fee; and form an association with the entry voucher; Synchronize the parking fee details to all service channels through the MQ message queue for the user to view in real time through any channel, ensuring data consistency across all channels.

8. The parking information processing method for government service platforms according to claim 7, characterized in that, Invoke the payment logic, and generate a payment voucher and update the user's credit fulfillment status after the user completes the payment, and synchronize the payment voucher and the updated user's credit fulfillment status to the government service platform, including: Query the balance Bal_pay of the payment channel Channel_pay bound by the user, and verify whether the balance meets the payable amount Fee_pay: If Bal_pay ≥ Fee_pay, trigger automatic deduction and obtain the transaction serial number Trade_no; If Bal_pay < Fee_pay, push a balance insufficient reminder for users of the second specified level; freeze the prepayment deposit for users of the first specified level and push an overdue reminder; The payment results are synchronized to the government credit platform. Successful deductions are recorded as credit fulfillment, and the user's government credit score is increased. If the payment is not made up within the specified time, it will be recorded as a credit default, the user's government credit score will be reduced, and the user's privilege level will be lowered.

9. A parking information processing system for a government service platform, characterized in that, include: The entry verification unit acquires license plate recognition data uploaded by the hardware device at the parking lot entrance, determines the associated parking user ID based on the license plate recognition data, and retrieves the associated specified user data based on the parking user ID; verifies the specified user data, and sends an opening channel command to the parking lot execution device after successful verification, so that the execution device can control the barrier to lift. The exit processing unit is used to receive exit license plate data uploaded by the parking lot exit hardware equipment and trigger the payable amount deduction logic. The payable amount deduction logic includes: determining the parking fee; calling the payment logic, and generating a payment voucher and updating the user's credit performance status after the user completes the payment, and synchronizing the payment voucher and the updated user credit performance status to the government service platform.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing the computer to perform the method according to any one of claims 1-8.

Images