A charging information processing method and device, computer equipment and readable storage medium

Abstract

The application provides a charging information processing method and device, computer equipment and a readable storage medium, comprising: when a settlement instruction triggered by a consumption order is detected, obtaining a basic consumption record and a charging rule of the consumption order; based on the basic consumption record and the charging rule, the consumption order is divided into multiple charging partitions, and the cost of each charging partition and the total cost are calculated; when a payment success record of the total cost is received, an order end process of the consumption order is executed. By using the above scheme, the refinement of the charging information processing can be effectively improved, the charging accuracy can be improved, and the user experience can be improved.

Description

Technical Field

[0001] This application relates to the field of smart parking billing technology, and more specifically, to a billing information processing method, apparatus, computer equipment, and readable storage medium. Background Technology

[0002] This invention relates to the field of billing information processing technology, and is particularly applicable to smart parking scenarios. With the large-scale development of the smart parking industry, contactless entry, automatic billing, and online payment have become the mainstream operating models for parking lots. As a core component of the charging system, billing information processing directly affects the operational efficiency of parking lots and the service experience of car owners.

[0003] Existing billing information processing methods typically retrieve the entry record and billing rules corresponding to the order when a consumption order triggers a settlement instruction, calculate the total cost of the order, and push it to the user for payment. After receiving the payment success record of the total cost, the order end process is executed to complete the entire billing and settlement process.

[0004] This processing method only outputs the final total billing amount to the user. The user cannot intuitively know the specific composition and calculation basis of the fee, which makes it easy to question the charging result, thus causing fee disputes and increasing the parking lot's customer complaint handling costs. Summary of the Invention

[0005] In view of this, the purpose of this application is to provide a billing information processing method, apparatus, computer equipment and readable storage medium, which can effectively improve the overall efficiency and reliability of billing information processing.

[0006] In a first aspect, embodiments of this application provide a billing information processing method, the method comprising: When a settlement instruction is triggered by a consumption order, the basic consumption record and billing rules of the consumption order are obtained; Based on the basic consumption records and the billing rules, the consumption order is divided into multiple billing partitions, and the cost generated by each billing partition and the total cost are calculated. Upon receiving a successful payment record for the total amount, the order completion process for the consumption order is executed.

[0007] Optionally, the basic consumption record includes at least one of the following: order start time, order consumption target, order consumption items, and order end time.

[0008] Optionally, the billing rules include time-zone billing rules and / or project-zone billing rules; The time-segment billing rules include time-segment billing thresholds and rate standards corresponding to each time segment; the time-segment billing thresholds include at least one of the first segment threshold, the subsequent segment threshold, and the fee cap threshold; The project zoning billing rules include billing standards corresponding to different consumption item categories.

[0009] Optionally, dividing the consumption order into multiple billing segments includes: When the billing rule is time-based billing, the usage duration of the consumption order is divided into continuous billing partitions corresponding to each threshold interval according to the time-based billing threshold. When the billing rule is project-based billing, the consumption order is divided into corresponding project-based billing zones according to the consumption project category; When the billing rules include both time-based billing and item-based billing, continuous billing zones are divided according to the segmented billing thresholds and item-based billing zones are divided according to the consumption item category, and the fees are calculated separately for each billing zone.

[0010] Optionally, after calculating the costs generated by each billing zone and the total cost, the method further includes: The billing partitions, their corresponding fees, and the total fees are pushed to the order display page.

[0011] Optionally, after receiving the payment success record for the total fee, the method further includes: Each billing partition, its corresponding fee, and the total fee are bound and stored with the consumption order.

[0012] Optionally, the order completion process for executing the consumption order includes: The payment success record is sent to the corresponding billing device so that the billing device can perform a release operation based on the payment success record.

[0013] Secondly, embodiments of this application provide a billing information processing apparatus, the apparatus comprising: The detection module is used to detect whether a consumer order has triggered a settlement instruction; The acquisition module is used to acquire the basic consumption records and billing rules of the consumption order when the detection module detects the settlement instruction; The processing module is used to divide the consumption order into multiple billing partitions based on the basic consumption record and the billing rules, and calculate the cost generated by each billing partition and the total cost. The execution module is used to execute the order termination process of the consumption order when a successful payment record of the total fee is received.

[0014] Optionally, the basic consumption record includes at least one of the following: order start time, order consumption target, order consumption items, and order end time.

[0015] Optionally, the billing rules include time-zone billing rules and / or project-zone billing rules; The time-segment billing rules include time-segment billing thresholds and rate standards corresponding to each time segment; the time-segment billing thresholds include at least one of the first segment threshold, the subsequent segment threshold, and the fee cap threshold; The project zoning billing rules include billing standards corresponding to different consumption item categories.

[0016] Optionally, when the processing module divides the consumption order into multiple billing segments, it is specifically used for: When the billing rule is time-based billing, the usage duration of the consumption order is divided into continuous billing partitions corresponding to each threshold interval according to the time-based billing threshold. When the billing rule is project-based billing, the consumption order is divided into corresponding project-based billing zones according to the consumption project category; When the billing rules include both time-based billing and item-based billing, continuous billing zones are divided according to the segmented billing thresholds and item-based billing zones are divided according to the consumption item category, and the fees are calculated separately for each billing zone.

[0017] Optionally, the device further includes a push module, which, after calculating the cost of each billing partition and the total cost, pushes each billing partition and its corresponding cost and the total cost to the order display page.

[0018] Optionally, the device further includes a storage module for binding and storing each billing partition and its corresponding fee, along with the total fee, to the consumption order after receiving a successful payment record of the total fee.

[0019] Optionally, when executing the order completion process of the consumption order, the execution module is specifically used for: The payment success record is sent to the corresponding billing device so that the billing device can perform a release operation based on the payment success record.

[0020] Thirdly, embodiments of this application provide a computer device, including: a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the computer device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, the steps of the billing information processing method described in any of the optional embodiments of the first aspect are performed.

[0021] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the billing information processing method described in any of the optional embodiments of the first aspect.

[0022] This application provides a billing information processing method, apparatus, computer equipment, and readable storage medium that acquires basic consumption records and billing rules when a consumption order triggers a settlement instruction. This unifies the settlement trigger timing and billing data source, ensuring that the accounting for each order is based on unified official billing rules and real consumption records. It avoids billing standard deviations caused by manual intervention, provides an accurate and consistent data foundation for subsequent cost accounting, and guarantees the standardization and uniformity of billing processing.

[0023] Based on basic consumption records and billing rules, consumption orders are divided into multiple billing partitions, and the costs of each partition and the total cost are calculated. This breaks down the overall billing process into independent structured billing units, so that each part of the cost corresponds to a clear billing range and billing standard, making the billing logic traceable and verifiable, effectively improving the accuracy of cost accounting, and providing structured data support for a clear presentation of cost composition.

[0024] Upon receiving a successful payment record for the total fee, the order termination process for the consumption order is executed. This strongly correlates the payment status with the order status, forming a complete billing and settlement business loop. This ensures the complete closure of the order lifecycle, guarantees the orderliness and integrity of the settlement process, and avoids inconsistencies between the order status and the payment status.

[0025] In summary, by ensuring the orderly connection of the three stages of settlement triggering and data acquisition, structured regional billing, and post-payment order closure, the entire billing and settlement process is standardized and structured. This not only ensures the accuracy and traceability of billing and accounting, but also guarantees the closed-loop control of the settlement process, effectively improving the overall efficiency and reliability of billing information processing.

[0026] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0027] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0028] Figure 1 A flowchart of a billing information processing method provided in Embodiment 1 of this application is shown; Figure 2 This paper illustrates a backend processing flowchart for parking fee billing details generation and intelligent verification provided in Embodiment 1 of this application; Figure 3 This document illustrates a flowchart of a billing details display and archiving process provided in Embodiment 1 of this application. Figure 4 This illustration shows a schematic diagram of the structure of a billing information processing device provided in Embodiment 2 of this application; Figure 5 A schematic diagram of the structure of a computer device provided in Embodiment 3 of this application is shown. Detailed Implementation

[0029] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0030] Example 1 To facilitate understanding of this application, the following is combined with... Figure 1 The flowchart illustrating a billing information processing method provided in Embodiment 1 of this application will be used to describe Embodiment 1 of this application in detail.

[0031] See Figure 1 As shown, Figure 1 A flowchart of a billing information processing method provided in Embodiment 1 of this application is shown, wherein the method includes steps S101 to S103: S101: When a settlement instruction is triggered by a consumption order, the basic consumption record and billing rules of the consumption order are obtained.

[0032] Specifically, in smart parking application scenarios, the consumption order corresponds to the vehicle temporary parking service order, and the settlement instruction is triggered by the vehicle departure recognition action.

[0033] Specifically, the smart parking industry has been implemented on a large scale. Seamless entry, automatic billing, online payment, charging services, supermarket services, and car detailing services are gradually being introduced into parking lots and have gradually become the mainstream application model in the industry. When a vehicle leaves the parking lot entrance or exit, the intelligent capture equipment at the entrance or exit recognizes the departure information, and the background smart parking billing management system automatically triggers the settlement process for the order and simultaneously initiates the basic data retrieval operation.

[0034] Specifically, the basic consumption records obtained by the system come from real traffic data collected at the entrances and exits of the parking lot and the probability of consumption for other items in the parking lot. The billing rules come from the official charging standards, charging fee standards, and commodity pricing standards that the corresponding parking lot has pre-configured and filed in the system.

[0035] Specifically, the billing rules include core parameters such as the initial time period charging standard, the unit price for subsequent time, the free parking period, the daily fee cap, the rules for calculating insufficient time, and the fee deduction rules, as well as charging fee rules, time period division rules, billing rules for different products, and billing discount rules. This step is a prerequisite for realizing the structured breakdown of billing details, which can ensure that the data source for subsequent billing and accounting is accurate and traceable, and avoid user doubts and fee disputes caused by the lack of public and transparent billing basis from the source.

[0036] S102: Based on the basic consumption records and the billing rules, the consumption order is divided into multiple billing partitions, and the costs generated by each billing partition and the total cost are calculated.

[0037] Specifically, the system first accurately calculates the total consumption duration based on the start and end times in the basic consumption records, and then automatically divides the overall duration into multiple continuous and independent segmented billing units according to the segmentation thresholds in the billing rules, thus completing the division of billing zones.

[0038] Specifically, for smart parking scenarios, this process involves calculating and segmenting the total parking time. The system automatically divides the overall parking time into multiple continuous and independent segmented billing units, collecting and recording the start and end parking time, effective parking duration, corresponding tiered pricing standard, and segmented actual amount collected for each billing unit. For charging fees, the system collects and records the billing standard, charging kilowatt-hours, and charging cost for different fee periods. For other goods, the system collects the type, quantity, price, and discount rules of each goods and calculates the price and total price of different goods.

[0039] Specifically, the system integrates all segmented billing unit data to generate a standardized, callable, and displayable structured billing detail dataset, providing data support for subsequent front-end display and data retention.

[0040] Specifically, taking a parking lot in a commercial complex as an example, its charging rules are as follows: free for the first 15 minutes, 15 yuan for the first 60 minutes, and 3 yuan for every 60 minutes thereafter, with any time less than 60 minutes counted as 60 minutes; if a vehicle enters the parking lot at 15:35 on March 1, 2026 and leaves at 17:29, the total parking time is 1 hour and 54 minutes.

[0041] Specifically, the backend system will break down the billing into three segments: Segment 1 corresponds to the free period from 15:35 to 15:50; Segment 2 corresponds to the first period from 15:35 to 16:35, lasting 60 minutes and costing 15 yuan, with the rule being "charged for the first period, with the first 60 minutes charged at 15 yuan per 60 minutes"; Segment 3 corresponds to the subsequent period from 16:35 to 17:29, with an actual duration of 54 minutes but counted as 60 minutes and costing 3 yuan, with the rule being "charged 3 yuan per 60 minutes"; the total amount due is 18 yuan, generating structured detailed data.

[0042] S103: Upon receiving a successful payment record for the total amount, execute the order termination process for the consumption order.

[0043] Specifically, when a car owner completes parking fee payment through online channels such as C-end mini-programs and apps or offline payment machines, the system officially initiates the order completion process after receiving a payment success callback notification from the payment channel.

[0044] Specifically, the process includes multiple steps such as order status updates, on-site equipment linkage, and billing data archiving. It is the core step to complete the parking payment business loop and can ensure that vehicles leave normally and order data is completely retained.

[0045] In one alternative implementation, the basic consumption record includes at least one of the following: order start time, order consumption target, order consumption items, and order end time.

[0046] Specifically, in the context of smart parking scenarios, the order start time is the precise time the vehicle enters the parking lot, which is automatically collected by the entrance camera; the charging start time is automatically collected by the charging pile; and the shop entry time is automatically collected by the shop's monitoring or access control system.

[0047] Specifically, the order consumption target is the identification of the corresponding parked vehicle, usually the license plate number and vehicle characteristic information.

[0048] Specifically, the order consumption items include temporary parking services, charging services, and other consumption services, which can be further subdivided according to the actual service type.

[0049] Specifically, the order completion time is the precise time the vehicle leaves the site, which is automatically collected by the exit capture equipment; the charging completion time is automatically collected by the charging pile; and the shop entry time is automatically collected by the shop's monitoring or access control system.

[0050] Specifically, the above data is automatically collected and synchronized by the equipment or manually entered by the administrator. Once entered, it cannot be modified at will, which can ensure the authenticity and traceability of the billing data.

[0051] The billing rules include time-zone billing rules and / or project-zone billing rules.

[0052] Specifically, the time-zone billing rule corresponds to a tiered pricing model based on the duration of consumption, which is the mainstream billing method for parking lots.

[0053] Specifically, the project-specific billing rules correspond to differentiated pricing models for different service types and service recipients.

[0054] Specifically, the two types of rules can be configured and effective individually or in combination, adapting to the diverse charging needs of parking lots in different scenarios such as commercial complexes, residential communities, and roadside parking.

[0055] The time-segment billing rules include time-segment billing thresholds and rate standards corresponding to each time segment; the time-segment billing thresholds include at least one of the first segment threshold, the subsequent segment threshold, and the fee cap threshold.

[0056] Specifically, the first threshold corresponds to the duration of the first period of charging or free parking, and is used to define the initial billing interval.

[0057] Specifically, the continuation threshold corresponds to the duration of the billing unit after the initial time period, and is used to divide the subsequent tiered billing intervals.

[0058] Specifically, the fee cap threshold corresponds to the maximum charge for a single parking session or a single day, and is used to control the upper limit of parking fees.

[0059] Specifically, each threshold is matched with a corresponding unit price and a rule for calculating insufficient time, which together constitute a complete time-based tiered billing system.

[0060] The project zoning billing rules include billing standards corresponding to different consumption item categories.

[0061] Specifically, in smart parking scenarios, consumption items can be categorized into different vehicle types such as small cars, medium cars, and large cars, or into different parking services such as temporary parking, reserved parking, and dedicated parking space services, or into different service categories such as charging and merchandise consumption.

[0062] Specifically, different project categories correspond to independent billing standards, which can realize differentiated charging management and meet the needs of refined parking lot operation.

[0063] In an optional implementation, dividing the consumption order into multiple billing segments includes: When the billing rule is time-based billing, the usage duration of the consumption order is divided into continuous billing partitions corresponding to each threshold interval according to the time-based billing threshold.

[0064] Specifically, for parking lots with pure time-based tiered billing, the system takes the entry time as the starting point and divides the total parking time into continuous billing intervals, such as the first time period and several subsequent time periods, according to the first segment threshold and the subsequent segment threshold.

[0065] Specifically, all billing zones are continuous and without overlap or omission, fully covering the entire parking duration. Each zone is independently matched with the corresponding rate standard, ensuring that the billing split logic and charging rules are completely consistent.

[0066] When the billing rule is project-based billing, the consumption order is divided into corresponding project billing zones according to the consumption project category.

[0067] Specifically, if an order includes multiple parking services, the system will split the billing into separate sections based on the service type, calculate the fees for each service separately, and achieve independent statistics and detailed display of fees for multiple services.

[0068] Specifically, this classification method can be adapted to complex order scenarios that include multiple parking services, ensuring that the billing logic for different service items is clear and traceable.

[0069] When the billing rules include both time-based billing and item-based billing, continuous billing zones are divided according to the time-based billing threshold and item-based billing zones are divided according to the consumption item category, and the fees are calculated separately for each billing zone.

[0070] Specifically, for parking lots that have both vehicle type differences and time-based tiered pricing, the system first matches the corresponding base rate system according to vehicle type classification, and then splits the billing units under each vehicle type classification according to time-based thresholds, and calculates the detailed fees for each subdivided billing zone through cross-dimensional calculation.

[0071] Specifically, this method can be adapted to complex billing rule scenarios, ensuring that the details of each billing dimension can be independently traced and clearly displayed.

[0072] In an optional implementation, after calculating the costs generated by each billing zone and the total cost, the method further includes: The billing partitions, their corresponding fees, and the total fees are pushed to the order display page.

[0073] Specifically, after the system generates structured billing details, it will push the data to the payment page of the C-end car owner's client. A separate entry point for viewing billing details will be added to the online payment page of the Jietingche mini-program, APP and other car owner terminals.

[0074] Specifically, after the car owner clicks on the entry point, the front end will render and display the total parking time, the precise entry and exit time, the parking time segment for each time period, the corresponding unit price, the segmented billing amount, the amount of fee deduction, and the final total amount payable.

[0075] Specifically, the page also includes a simplified explanation module for the rules, which transforms professional pricing terms into easy-to-understand, conversational explanations. This covers complex rules such as tiered pricing, capped pricing, overtime pricing, and short-duration billing, allowing car owners to quickly understand the billing logic and lowering the barrier to understanding for users.

[0076] Specifically, the system also optimizes the layout, font hierarchy, and information arrangement of the details page, simplifies redundant content, and improves readability and ease of use on mobile devices.

[0077] Specifically, the backend will also be equipped with an automatic billing compliance verification engine, which will compare the segmented billing amount, total cost, and time conversion rules with the official parking lot charging standards in real time, and automatically identify problems such as abnormal time statistics, incorrect billing levels, incorrect matching of charging standards, duplicate billing, and deviations in amount calculation.

[0078] Specifically, once abnormal billing data is detected, the abnormal information will be highlighted on the details display page, and a quick access point for one-click online appeal and manual reconciliation will be embedded.

[0079] Specifically, this pre-payment detailed visualization method breaks away from the traditional system's model of only displaying the total cost, allowing car owners to clearly understand the entire cost composition before making a payment decision, completely eliminating doubts about costs and resistance to payment.

[0080] Specifically, this model can effectively increase online payment willingness and order payment conversion rate, while reducing customer complaints related to fees at the source, reducing the repetitive workload of manual customer service in answering questions and reconciling accounts, and reducing parking lot operating costs.

[0081] In an optional implementation, after receiving the payment success record for the total fee, the method further includes: Each billing partition, its corresponding fee, and the total fee are bound and stored with the consumption order.

[0082] Specifically, after payment is completed, the system will forcibly bind the complete segmented billing details, charging rules, time conversion records, and parking order number, and simultaneously store them in the cloud database for permanent encrypted retention.

[0083] Specifically, the system provides a detailed traceability query channel on the personal center's historical order details page, allowing car owners to retrieve, view, and verify the complete billing process details of any historical parking order anytime, anywhere.

[0084] Specifically, this structured archiving and permanent binding storage mechanism enables electronic archiving of parking billing details throughout the entire process and allows for traceability at any time, fully meeting the control requirements of traffic management and market supervision departments regarding the openness and transparency of parking fees.

[0085] Specifically, this mechanism can standardize the platform's charging operation model, avoid compliance risks such as opaque charging and untraceable accounts, and also provide complete data basis for subsequent fee dispute verification.

[0086] In an optional implementation, the order completion process for executing the consumption order includes: The payment success record is sent to the corresponding billing device so that the billing device can perform a release operation based on the payment success record.

[0087] Specifically, the system will synchronize the payment success status information to the gate control equipment at the entrance and exit of the parking lot. After the gate equipment recognizes the payment completion status of the corresponding vehicle, it will automatically raise the barrier to allow the vehicle to leave, thus completing the entire parking payment business loop.

[0088] Specifically, the system will update the order status to "completed" and trigger the subsequent permanent archiving process of billing details, ensuring a complete and closed loop of data throughout the entire order process.

[0089] To more intuitively demonstrate the complete execution chain of the above-mentioned billing information processing method, this application provides two accompanying flowcharts.

[0090] Specifically, the two attached diagrams correspond to the backend billing verification process and the C-end interaction archiving process, respectively, and can completely correspond to the entire execution logic of the method steps. The specific explanations of the two attached diagrams are as follows: See Figure 2 As shown, Figure 2 This document illustrates a backend processing flowchart for parking fee billing details generation and intelligent verification provided in Embodiment 1 of this application. The flowchart corresponds to the core processes of settlement instruction triggering, billing zone division and fee calculation, and anomaly verification in the billing information processing method of this application, and fully presents the backend full-link logic from vehicle entry to billing data verification and correction.

[0091] The process begins with the vehicle entering the parking lot.

[0092] Specifically, the system synchronously executes the system record entry time + parking lot charging rules operation, collects vehicle entry time data and binds it to the corresponding parking lot's preset charging rules, corresponding to the preliminary data preparation process for obtaining basic consumption records and billing rules of consumption orders in this application.

[0093] When a vehicle leaves the parking lot, the order settlement instruction is automatically triggered. Specifically, the backend first generates a basic parking order, completing the initial creation of the parking order.

[0094] The total parking time is then calculated by the back-end billing module. Specifically, the billing module calculates the complete total parking time based on the precise entry and exit times of the vehicle, providing the basic data for subsequent segmented billing.

[0095] Next, the system splits the parking time into multiple billing units according to the charging rules. Specifically, based on the parking lot's preset charging rules, the system divides the total parking time into multiple consecutive billing zones, corresponding to the core step of dividing the parking time into multiple billing zones in this application.

[0096] The system synchronously records the start and end times, duration, pricing standards, and segmented amounts for each segment. Specifically, the system collects comprehensive billing information for each billing zone, ensuring that each fee segment has a clear time and rule basis, and guaranteeing billing traceability.

[0097] Finally, a structured billing detail data package is generated. Specifically, the system calculates the cost of each partition and the total cost, and integrates them into standardized, callable, and displayable billing detail data, providing support for subsequent front-end display and data verification.

[0098] After generating the structured billing details data package, the system proceeds to the background intelligent automatic billing verification stage. Specifically, the system uses an automatic verification engine to compare the billing data with the official charging standards to determine if the billing data is abnormal, resulting in two processing branches.

[0099] If the judgment result is "no", the details will be displayed normally without any prompts. Specifically, the system will push the billing details data to the front end according to the usual logic for the car owner to view and verify.

[0100] If the judgment result is "yes", the system will highlight the anomaly on the front-end details page and display a one-click appeal portal. Specifically, the system will proactively identify billing anomalies to vehicle owners and embed an appeal channel to facilitate quick feedback from vehicle owners.

[0101] The subsequent process involves the vehicle owner initiating an appeal and manual verification. Specifically, after receiving the appeal, staff will manually verify and confirm the abnormal billing data.

[0102] After verification, the backend will correct the billing data and regenerate the details. Specifically, the corrected details will be fed back to the structured billing details data package stage to complete the verification process again, corresponding to the technical solution of automatic billing compliance verification and abnormal interaction optimization in this application.

[0103] See Figure 3 As shown, Figure 3 This diagram illustrates a flowchart of a billing details display and archiving process for end users, as provided in Embodiment 1 of this application. The flowchart connects... Figure 1 The back-end processing flow corresponds to the implementation details of billing details push display, payment settlement, and data binding storage in this application, and fully presents the entire process from data push to C-end to permanent traceability of details.

[0104] After the billing data is verified in the backend, the execution data is synchronously pushed to the C-end vehicle owner's client. Specifically, the backend synchronizes the verified structured detailed data to the vehicle owner's client to provide data support for the frontend display.

[0105] The system then prompts the driver to select a branch node. Specifically, the system executes the corresponding process branch based on the driver's chosen action.

[0106] Option one allows car owners to choose to postpone payment and delay processing. Specifically, the corresponding process is temporarily suspended, and the billing data is retained in the system until the car owner initiates payment later.

[0107] Branch two allows car owners to access the "Pending Payment" page. Specifically, on this page, car owners can view the total order cost and click the "Billing Details" entry to see the complete cost breakdown.

[0108] Vehicle owners can click on the "Billing Details" entry to view the details. Specifically, this entry corresponds to the details viewing function added to the C-end pending payment page in this application, and is the core entry point for achieving transparent display before payment.

[0109] After the car owner clicks on the details entry, the front end performs rendering and display operations. Specifically, the displayed content includes segmented time periods, unit price, segmented amount, simple explanation of the rules, and total cost, fully presenting the information of each billing segment, corresponding cost, and simplified explanation of the rules, which corresponds to the technical solution in this application that pushes each billing segment, corresponding cost, and total cost to the order display page.

[0110] After the vehicle owner verifies that the fees are correct, the online payment process will be completed. Specifically, once the vehicle owner confirms that there are no objections to the fee breakdown, the parking fee payment will be completed online.

[0111] After payment is completed, the system enters the payment success status. Specifically, the system receives a payment success callback message, corresponding to the node in this application that receives the total fee payment success record.

[0112] After successful payment, the detailed billing data is permanently stored in the cloud along with the order. Specifically, the system will forcibly bind and encrypt all segmented billing details with the parking order, corresponding to the technical solution in this application that binds and stores billing zones, fees, and consumption orders.

[0113] The order data is then stored in the historical order database. Specifically, the system completes the structured archiving of billing data to ensure that the data is permanently retained and not lost.

[0114] Ultimately, this allows car owners to access order details and query complete billing information at any time. Specifically, car owners can retrieve complete billing information for any order from their personal center's order history, enabling traceability and verification of billing details throughout the entire order lifecycle. This meets regulatory traceability requirements and enhances the car owner service experience.

[0115] Example 2 See Figure 4 As shown, Figure 4 This illustration shows a schematic diagram of a billing information processing device according to Embodiment 2 of this application, wherein the device includes: Detection module 401 is used to detect whether a consumer order has triggered a settlement instruction; The acquisition module 402 is used to acquire the basic consumption record and billing rules of the consumption order when the detection module detects the settlement instruction; The processing module 403 is used to divide the consumption order into multiple billing partitions based on the basic consumption record and the billing rules, and calculate the cost generated by each billing partition and the total cost. The execution module 404 is used to execute the order termination process of the consumption order when a payment success record of the total fee is received.

[0116] In one alternative implementation, the basic consumption record includes at least one of the following: order start time, order consumption target, order consumption items, and order end time.

[0117] Optionally, the billing rules include time-zone billing rules and / or project-zone billing rules; The time-zone billing rules include segmented billing thresholds and corresponding rate standards for each segment; the segmented billing thresholds include at least one of the following: first segment threshold, subsequent segment threshold, and fee capping threshold; The project zoning billing rules include billing standards corresponding to different consumption item categories.

[0118] Optionally, when the processing module divides the consumption order into multiple billing segments, it is specifically used for: When the billing rule is time-based billing, the usage duration of the consumption order is divided into continuous billing partitions corresponding to each threshold interval according to the segmented billing threshold. When the billing rule is project-based billing, the consumption order is divided into corresponding project-based billing zones according to the consumption project category; When the billing rules include both time-based billing and item-based billing, continuous billing zones are divided according to the segmented billing thresholds and item-based billing zones are divided according to the consumption item category, and the fees are calculated separately for each billing zone.

[0119] Optionally, the device further includes a push module, which, after calculating the cost of each billing partition and the total cost, pushes each billing partition and its corresponding cost and the total cost to the order display page.

[0120] Optionally, the device further includes a storage module for binding and storing each billing partition and its corresponding fee, along with the total fee, to the consumption order after receiving a successful payment record of the total fee.

[0121] Optionally, when executing the order completion process of the consumption order, the execution module is specifically used for: The payment success record is sent to the corresponding billing device so that the billing device can perform a release operation based on the payment success record.

[0122] Example 3 Based on the same application concept, see [link / reference] Figure 5 As shown, Figure 5 This illustration shows a structural schematic diagram of a computer device provided in Embodiment 3 of this application, wherein, as shown... Figure 5 As shown, the computer device 500 provided in Embodiment 3 of this application includes: The computer device 500 includes a processor 501, a memory 502, and a bus 503. The memory 502 stores machine-readable instructions that can be executed by the processor 501. When the computer device 500 is running, the processor 501 communicates with the memory 502 through the bus 503. When the machine-readable instructions are executed by the processor 501, the steps of the billing information processing method shown in Embodiment 1 are performed.

[0123] Example 4 Based on the same concept, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the billing information processing method described in any of the above embodiments.

[0124] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the system and apparatus described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0125] The computer program product for processing billing information provided in this application includes a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the methods described in the preceding method embodiments. For specific implementation details, please refer to the method embodiments, which will not be repeated here.

[0126] The billing information processing device provided in this application embodiment can be specific hardware on a device or software or firmware installed on the device. The implementation principle and technical effects of the device provided in this application embodiment are the same as those in the foregoing method embodiments. For the sake of brevity, any parts not mentioned in the device embodiment can be referred to the corresponding content in the foregoing method embodiments. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can all be referred to the corresponding processes in the above method embodiments, and will not be repeated here.

[0127] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some communication interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

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

[0129] In addition, the functional units in the embodiments provided in this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0130] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0131] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. In addition, the terms "first", "second", "third", etc. are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0132] Finally, it should be noted that the above-described embodiments are merely specific implementations of this application, used to illustrate the technical solutions of this application, and not to limit them. The protection scope of this application is not limited thereto. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this application; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application. All should be covered within the protection scope of this application. Therefore, the protection scope of this application should be determined by the protection scope of the claims.

Claims

1. A method for processing billing information, characterized in that, include: When a settlement instruction is triggered by a consumption order, the basic consumption record and billing rules of the consumption order are obtained; Based on the basic consumption records and the billing rules, the consumption order is divided into multiple billing partitions, and the cost generated by each billing partition and the total cost are calculated. Upon receiving a successful payment record for the total amount, the order completion process for the consumption order is executed.

2. The method according to claim 1, characterized in that, The basic consumption record includes at least one of the following: order start time, order consumption target, order consumption items, and order end time.

3. The method according to claim 1, characterized in that, The billing rules include time-zone billing rules and / or project-zone billing rules; The time-segment billing rules include time-segment billing thresholds and rate standards corresponding to each time segment; the time-segment billing thresholds include at least one of the first segment threshold, the subsequent segment threshold, and the fee cap threshold; The project zoning billing rules include billing standards corresponding to different consumption item categories.

4. The method according to claim 3, characterized in that, The process of dividing the consumption order into multiple billing segments includes: When the billing rule is time-based billing, the usage duration of the consumption order is divided into continuous billing partitions corresponding to each threshold interval according to the time-based billing threshold. When the billing rule is project-based billing, the consumption order is divided into corresponding project-based billing zones according to the consumption project category; When the billing rules include both time-based billing and item-based billing, continuous billing zones are divided according to the segmented billing thresholds and item-based billing zones are divided according to the consumption item category, and the fees are calculated separately for each billing zone.

5. The method according to any one of claims 1-4, characterized in that, After calculating the costs generated by each billing zone and the total cost, the process also includes: The billing partitions, their corresponding fees, and the total fees are pushed to the order display page.

6. The method according to claim 1, characterized in that, After receiving the payment success record for the total fee, the process also includes: Each billing partition, its corresponding fee, and the total fee are bound and stored with the consumption order.

7. The method according to claim 1, characterized in that, The order completion process for executing the consumption order includes: The payment success record is sent to the corresponding billing device so that the billing device can perform a release operation based on the payment success record.

8. A billing information processing device, characterized in that, include: The detection module is used to detect whether a consumer order has triggered a settlement instruction; The acquisition module is used to acquire the basic consumption records and billing rules of the consumption order when the detection module detects the settlement instruction; The processing module is used to divide the consumption order into multiple billing partitions based on the basic consumption record and the billing rules, and calculate the cost generated by each billing partition and the total cost. The execution module is used to execute the order termination process of the consumption order when a successful payment record of the total fee is received.

9. A computer device, characterized in that, include: The computer device includes a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the computer device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, they perform the steps of the billing information processing method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the billing information processing method as described in any one of claims 1 to 7.

Images