Unified consumption linkage service system for highway charging piles

Abstract

The invention relates to the technical field of highway charging piles, in particular to a unified consumption linkage service system for highway charging piles, and the system comprises a user interaction module which is used for receiving user position data and a charging pile operation instruction submitted by a user; the charging pile data acquisition module is used for acquiring real-time operation data of each charging pile in the expressway service area; the scheduling verification module is used for generating a charging scheduling instruction; the order processing module is used for calculating the charging metering data of the charging pile corresponding to the target charging pile identifier; the payment management module is used for updating the payment state of the charging order data based on the payment confirmation information; and the invoice filing module is used for outputting charging pile filing information when the payment state of the target to-be-invoiced order is paid and the invoicing state in the to-be-invoiced order is not invoiced. According to the invention, unified consumption linkage service management can be carried out on a plurality of charging piles in the expressway service area, and the response efficiency to the charging request of the user is improved.

Description

Technical Field

[0001] This invention relates to the field of highway charging pile technology, and in particular to a unified consumption linkage service system for highway charging piles. Background Technology

[0002] In the construction and use of new energy vehicle charging facilities in highway service areas, existing technologies typically employ a decentralized and independent management model. Each charging pile is equipped with an independent billing and control unit, requiring users to interact with each charging pile individually to complete charging operations and payments. Under this model, there is a lack of unified data interaction and coordination mechanisms between different charging piles, and charging pile status information, user account data, and consumption records are isolated. This decentralized and independent management model directly results in the system's inability to provide unified, interconnected service management for multiple charging piles within the service area. Upon arriving at the service area, if a user encounters a faulty or occupied charging pile, they must check the physical interfaces of other charging piles one by one or rely on their personal mobile devices to search for available charging piles. This process consumes user time and effort, reducing the service experience. More importantly, when a user initiates a charging request, the system cannot intelligently allocate the most suitable charging pile resources based on the real-time global status. For example, it cannot prioritize guiding users to idle piles, power-matching piles, or nearby available piles, thus increasing user waiting time and queuing disorder. When a charging pile malfunctions or becomes congested, it cannot promptly guide users to adjacent idle charging piles, leading to prolonged waiting times and delayed responses to charging requests.

[0003] Chinese Patent Publication No. CN111993944A discloses an electric vehicle charging pile with edge computing functionality, comprising: a metering module, a charging module, a charging monitoring module, an edge computing module, a charging control module, a user interaction module, and a communication module. The metering module is connected to both the charging monitoring module and the edge computing module; the charging module is connected to both the charging monitoring module and the charging control module and is used to charge the electric vehicle; the charging monitoring module is connected to the edge computing module; the edge computing module is connected to both the charging control module and the communication module; the charging control module is connected to both the user interaction module and the communication module; the user interaction module is used to receive charging control commands input by the user; and the communication module is connected to a remote control center. This solution only implements charging control, data storage, and basic communication functions for a single charging pile, and cannot provide unified consumption and linkage service management for multiple charging piles in a highway service area, thus reducing the response efficiency to user charging requests. Summary of the Invention

[0004] To address this issue, the present invention provides a unified consumption linkage service system for highway charging piles, which overcomes the problem in the prior art that it is impossible to manage the unified consumption linkage service of multiple charging piles in highway service areas, thus reducing the response efficiency to user charging requests.

[0005] To achieve the above objectives, the present invention provides a unified consumption and linkage service system for highway charging piles, comprising: The user interaction module is used to receive user location data and charging pile operation instructions submitted by the user through the user terminal, and to parse the charging pile operation instructions to generate user request data. The charging pile data acquisition module is used to acquire real-time operating data of each charging pile in the highway service area through the Internet of Things interface, and to standardize the real-time operating data to obtain a charging pile status dataset. The scheduling verification module is used to extract the charging pile record corresponding to the user request data from the charging pile status dataset according to the user request data, and calculate the actual distance between the charging pile location data and the user location data of each charging pile in the charging pile record. When the actual distance is less than the preset distance threshold, and the working status in the charging pile record is idle and the equipment fault mark in the charging pile record is not faulty, a charging scheduling instruction containing the start authorization code and the target charging pile identifier is generated. The order processing module is used to send a charging start signal to the charging pile corresponding to the target charging pile identifier according to the start authorization code, and after receiving the charging end signal, calculate the charging metering data of the charging pile corresponding to the target charging pile identifier to obtain the charging order data. The payment management module is used to send a payment transaction request to the payment terminal based on the unpaid fees in the charging order data, receive payment confirmation information returned by the payment terminal, update the payment status of the charging order data based on the payment confirmation information, and generate order payment information. The invoice archiving module is used to generate a pool of orders to be invoiced based on order payment information, respond to invoicing requests initiated by users through the user interaction module, query the pool of orders to be invoiced that match the invoicing request, verify the target orders to be invoiced, and generate electronic invoice data based on the invoicing request and a preset invoice template when the payment status of the target order to be invoiced is "paid" and the invoicing status of the order to be invoiced is "not invoiced". The module also associates and stores the electronic invoice data and the order corresponding to the electronic invoice data, updates the invoicing status of the order corresponding to the electronic invoice data, and obtains the corresponding charging pile archiving information.

[0006] Compared with the prior art, the beneficial effects of this application are as follows: By generating user request data based on user location data and charging pile operation instructions submitted by the user, and utilizing a standardized charging pile status dataset obtained from an IoT interface, the system can calculate the actual distance based on user location data and charging pile location data. It also comprehensively verifies that the charging pile's working status is idle and its fault marker is not faulty. When the conditions of the actual distance being less than a preset distance threshold, the working status being idle, and the fault marker being not faulty are simultaneously met, a charging scheduling instruction containing a start authorization code and a target charging pile identifier is generated. By integrating and processing the charging pile location data, working status, and fault markers of multiple charging piles in real time, the system achieves unified, automatic filtering and verification of the status of scattered charging piles within the service area. It can match and schedule a charging pile corresponding to a target charging pile identifier that has been verified as available under multiple conditions, significantly improving the response speed and scheduling accuracy to user charging requests.

[0007] By sending a charging start signal to the charging pile corresponding to the target charging pile identifier based on the start authorization code, and generating charging order data based on charging metering data after charging is completed, the system then completes the payment transaction based on the outstanding payment amount and updates the payment status to generate order payment information. It can build a pool of pending invoice orders based on the order payment information, and after verifying that the payment status of the target pending invoice order is paid and the invoicing status is not invoiced, it generates electronic invoice data and performs associated storage and status updates. By linking charging start, charging metering data calculation, charging order data generation, payment status update, order payment information generation, and electronic invoice data generation and archiving into a coherent data processing chain, it ensures traceability and automatic connection throughout the entire process from charging operation instructions to charging pile archiving information. This achieves unified closed-loop management of individual user charging consumption behavior, reduces delays caused by manual intervention and process switching, and thus improves the response efficiency and management effectiveness of user charging requests from the overall service process perspective.

[0008] Furthermore, in the scheduling verification module, the specific process of calculating the actual distance between the charging pile location data and the user location data for each charging pile in the charging pile record includes: The location data of each charging pile and the location data of the user are converted to latitude and longitude coordinates in the geodetic coordinate system to obtain the corresponding coordinates of each charging pile and the user. The spherical distance algorithm is used to calculate the coordinates of each charging station and the user, resulting in the straight-line distance between the user and each charging station. The mathematical expression for the spherical distance algorithm is as follows: In the formula, Indicates user and the The straight-line distance between charging stations This represents the Earth's average radius. Indicates the latitude and longitude of the user's coordinates. Indicates the longitude of the user's location in coordinates. Indicates the first The latitude and longitude of the location of each charging station Indicates the first The longitude of the location of each charging station Indicates the use of the first The longitude difference of each charging station This represents a function used to convert latitude and longitude differences into central angles, and then obtain the straight-line distance by multiplying the central angle by the Earth's radius; A road layout model is established based on the road topology of the highway service area. Based on the road layout model, the geospatial data of the highway service area is extracted to obtain the road layout coefficient. Based on the road layout coefficient, the straight distance is corrected to obtain the actual distance between the user and each charging pile.

[0009] In this solution, charging pile location data and user location data are converted to latitude and longitude coordinates in the geodetic coordinate system. The straight-line distance between the user and each charging pile is calculated based on the spherical distance algorithm. Then, a road layout model is established based on the road topology of the highway service area. The road layout coefficient is extracted from the geospatial data and corrected for the straight-line distance. Finally, the actual distance between the user and each charging pile is accurately obtained, avoiding the error caused by relying solely on the straight-line distance and improving the accuracy of distance judgment in scheduling verification.

[0010] Furthermore, in the order processing module, the specific process of calculating the charging metering data of the charging pile corresponding to the target charging pile identifier to obtain the charging order data includes: Real-time metering parameters of the charging pile corresponding to the target charging pile identification are collected during the charging process. These parameters are preprocessed to output valid metering parameters. The initial total charging energy consumption is then calculated from these valid metering parameters. The mathematical expression is: In the formula, Indicates the charging start time in the valid metering parameters. Indicates the charging end time in the valid metering parameters. Indicates the first Real-time charging power at any given moment Indicates the first Charging efficiency at any given time; Initial total charging energy consumption energy consumption error threshold compared to the preset energy consumption metering standard for charging piles A comparison is performed, and the initial total charging energy consumption is corrected based on the comparison results. The final total charging energy consumption is then integrated into the charging order data. when When the order processing module determines that the initial total charging energy consumption should not be corrected, it outputs the initial total charging energy consumption that is determined not to be corrected as the final total charging energy consumption. when When the order processing module determines that the initial total charging energy consumption needs to be corrected, it performs linear calibration on the initial total charging energy consumption determined to be corrected according to the energy consumption correction coefficient in the preset charging pile energy consumption metering standard, obtains the calibrated total charging energy consumption, and outputs the calibrated total charging energy consumption as the final total charging energy consumption.

[0011] In this solution, real-time metering parameters of the charging pile corresponding to the target charging pile are collected and preprocessed to output effective metering parameters for calculating the initial total charging energy consumption. The energy consumption error threshold in the preset charging pile energy consumption metering standard is used for correction and judgment. The initial total charging energy consumption that needs to be corrected is linearly calibrated according to the energy consumption correction coefficient to obtain the final total charging energy consumption and integrate it into the charging order data. This effectively reduces metering errors, improves the accuracy and reliability of charging energy consumption metering, and ensures the authenticity and compliance of charging order data.

[0012] Furthermore, in the payment management module, the specific process of updating the payment status of the charging order data based on the payment confirmation information and generating order payment information includes: The payment confirmation information is parsed to obtain a payment parsing result, which includes a transaction serial number, a payment amount, and a transaction status flag. The order identifier of the initial charging order associated with the transaction serial number is obtained by querying the preset payment transaction mapping relationship index based on the transaction serial number. Based on the order identifier, retrieve the charging order data to be updated corresponding to the order identifier from the charging order storage area. The charging order data to be updated includes the total amount of fees to be paid and historical payment status records. The payment amount in the parsed result is compared with the total amount of unpaid fees in the charging order data to be updated. Based on the comparison result, the payment status is determined, and the payment status of the charging order data is updated accordingly, generating order payment information. When the payment amount is greater than or equal to the total amount to be paid and the transaction status is marked as successful, the payment management module determines that the payment status is valid, modifies the payment status field value in the charging order data to be updated to the paid status value, calculates the difference between the payment amount and the total amount to be paid as the overpayment amount data item, obtains the updated charging order data, and generates payment success data containing the successful order identifier, final payment status, successful payment time and successful payment voucher number by combining the timestamp and payment channel identifier in the payment confirmation information, and outputs the payment success data as order payment information; When the payment amount is less than the total amount to be paid, or the transaction status is marked as failed, the payment management module determines that the payment status is invalid, does not modify the payment status field value in the charging order data to be updated, generates a payment exception details record containing the abnormal transaction status code, and outputs the payment exception details record as order payment information.

[0013] In this solution, payment confirmation information is parsed to obtain payment parsing results. Based on the transaction serial number, the order identifier is queried in the preset payment transaction mapping relationship index to retrieve the corresponding charging order data to be updated. The payment amount is compared with the total amount of fees to be paid, and the payment status is determined in conjunction with the transaction status flag. The payment status of the charging order data is updated and order payment information is generated. The solution accurately matches orders and payment records, ensuring the accuracy of payment status updates and the integrity of order payment information. It effectively handles overpayment data items and payment anomalies, and improves the standardization of payment management.

[0014] Furthermore, in the invoice archiving module, the specific process of querying the target pending invoice order data pool that matches the invoice request includes: The invoice request is parsed to obtain user identification data and invoice request time data. Based on the user identification data, all candidate orders that match the user identification data are selected from the pending invoice order data pool to generate a first candidate order set. Based on the invoice request time data and the charging end time data of each candidate order in the first candidate order set, the time correlation parameter of each candidate order is calculated, and the candidate orders in the first candidate order set are sorted according to the time correlation parameter to generate a sorted second candidate order set. The candidate order with the highest ranking is extracted from the second candidate order set as the target invoice order.

[0015] In this solution, user identification data and invoice request time data are obtained by parsing the invoice request. Matching candidate orders are selected from the pending invoice order data pool to generate a first candidate order set. A second candidate order set is generated by calculating the time correlation parameter based on the charging end time data and sorting them. The candidate order with the highest ranking is extracted as the target pending invoice order, which accurately locates the matching pending invoice order, improves the targeting and efficiency of order query, ensures the accuracy of invoice request processing, and optimizes the order matching efficiency of the invoice archiving module.

[0016] Furthermore, in the invoice archiving module, the specific process of generating electronic invoice data based on the invoice request and the preset invoice template includes: Based on the invoicing request, extract the user's tax identification data and invoicing item data, and map the invoice structure data defined in the preset invoice template with the invoicing item data to generate structured invoicing data; The structured invoice data is digitally signed using an encryption algorithm to generate anti-counterfeiting identification data. The structured invoice data and the anti-counterfeiting identification data are then integrated into the preset invoice template to obtain electronic invoice data. The expression for the encryption algorithm is: In the formula, This indicates anti-counterfeiting label data. This indicates the structured invoicing data. The result after performing the hash operation, Indicates the preset encryption modulus. This indicates the modulo operation.

[0017] In this solution, user tax identification data and invoice item data are extracted based on the invoice request. The invoice structure data defined in the preset invoice template is mapped to the invoice item data to generate structured invoice data. An encryption algorithm is used to perform digital signature calculation on the structured invoice data to generate anti-counterfeiting identification data. The structured invoice data and anti-counterfeiting identification data are integrated into the preset invoice template to obtain electronic invoice data. This ensures the standardization and anti-counterfeiting security of electronic invoice data, ensures the accuracy and compliance of invoice information, and improves the reliability of electronic invoice generation.

[0018] Furthermore, in the invoice archiving module, the specific process of associating and storing the electronic invoice data and the orders corresponding to the electronic invoice data includes: Extract unique invoice identifier data from the electronic invoice data, extract unique order identifier data from the target order to be invoiced, and pair the unique invoice identifier data with the unique order identifier data according to preset association rules to generate association mapping data; The association mapping data is input into the storage index generation function to generate corresponding distributed storage path data. Based on the distributed storage path data, the electronic invoice data is stored in the corresponding storage node, and the association mapping data is written into the system association database to obtain the association storage result. The expression of the storage index generation function is: In the formula, This represents distributed storage path data. This represents the unique identifier data for the order. The hash operation performed Indicates the first Unique identifier data for each invoice The hash operation performed This indicates the XOR operation. Indicates the total number of storage nodes. Indicates the storage base address.

[0019] In this solution, by extracting the unique identifier data of the invoice and the unique identifier data of the target order to be invoiced, association mapping data is generated according to preset association rules. Combined with the storage index generation function, distributed storage path data is obtained. The electronic invoice data is stored in the corresponding storage node and the association mapping data is written to the system association database. This achieves accurate association storage between electronic invoice data and orders, improves the standardization of data storage and retrieval efficiency, avoids data association chaos, and ensures the accuracy of data retrieval.

[0020] Furthermore, in the invoice archiving module, the specific process of updating the invoicing status of the order corresponding to the electronic invoice data to obtain the corresponding charging pile archiving information includes: Based on the associated storage result, obtain the unique identifier data of the order, query the pending invoice order record corresponding to the unique identifier data of the order in the pending invoice order data pool, and extract the current invoicing status data corresponding to the unique identifier data of the order from the pending invoice order record; The current invoice status data is analyzed according to a preset invoice status transition rule to generate a status update instruction. The expression of the preset invoice status transition rule is as follows: In the formula, This indicates the updated invoice status value. This indicates the current invoicing status data. Indicates the payment verification result; According to the status update instruction, the invoice status field in the order record to be invoiced is modified to the updated invoice status value, and the combined information of the storage path data containing the order record to be invoiced and the electronic invoice data and the updated invoice status value is written into the system archive log as charging pile archive information.

[0021] In this solution, the unique identifier data of the order is obtained by associating the storage results. The corresponding order record to be invoiced is queried in the order data pool and the current invoicing status data is extracted. The status update instruction is generated according to the preset invoicing status conversion rules, the invoicing status field is modified, and the combined information is written as the charging pile archive information into the system archive log. This achieves accurate updates of the invoicing status, ensures the completeness and accuracy of the charging pile archive information, ensures the consistency between the order record to be invoiced and the electronic invoice data, improves the standardization of order management and archiving, and facilitates the traceability of order invoicing status. Attached Figure Description

[0022] Figure 1 This is a schematic diagram of the structure of a unified consumption linkage service system for highway charging piles according to an embodiment of the present invention. Detailed Implementation

[0023] The following detailed description illustrates the specific implementation method: like Figure 1 As shown, it is a structural schematic diagram of a unified consumption linkage service system for highway charging piles according to an embodiment of the present invention, including: The user interaction module is used to receive user location data and charging pile operation instructions submitted by the user through the user terminal, and to parse the charging pile operation instructions to generate user request data. The charging pile data acquisition module is used to acquire real-time operating data of each charging pile in the highway service area through the Internet of Things interface, and to standardize the real-time operating data to obtain a charging pile status dataset. The scheduling verification module is used to extract the charging pile record corresponding to the user request data from the charging pile status dataset according to the user request data, and calculate the actual distance between the charging pile location data and the user location data of each charging pile in the charging pile record. When the actual distance is less than the preset distance threshold, and the working status in the charging pile record is idle and the equipment fault mark in the charging pile record is not faulty, a charging scheduling instruction containing the start authorization code and the target charging pile identifier is generated. The order processing module is used to send a charging start signal to the charging pile corresponding to the target charging pile identifier according to the start authorization code, and after receiving the charging end signal, calculate the charging metering data of the charging pile corresponding to the target charging pile identifier to obtain the charging order data. The payment management module is used to send a payment transaction request to the payment terminal based on the unpaid fees in the charging order data, receive payment confirmation information returned by the payment terminal, update the payment status of the charging order data based on the payment confirmation information, and generate order payment information. The invoice archiving module is used to generate a pool of orders to be invoiced based on order payment information, respond to invoicing requests initiated by users through the user interaction module, query the pool of orders to be invoiced that match the invoicing request, verify the target orders to be invoiced, and generate electronic invoice data based on the invoicing request and a preset invoice template when the payment status of the target order to be invoiced is "paid" and the invoicing status of the order to be invoiced is "not invoiced". The module also associates and stores the electronic invoice data and the order corresponding to the electronic invoice data, updates the invoicing status of the order corresponding to the electronic invoice data, and obtains the corresponding charging pile archiving information.

[0024] In the user interaction module, the specific implementation method for parsing charging pile operation instructions and generating user request data is as follows: The received charging pile operation instructions are syntax and structure validated according to the preset charging pile operation instruction protocol specification. After successful validation, the parsing engine extracts the core operation type and target charging pile identifier from the charging pile operation instructions based on the field separators or key-value pair mapping rules defined in the preset charging pile operation instruction protocol specification. The successfully parsed operation type and target charging pile identifier are bound and encapsulated with the simultaneously received user location data and the user identifier obtained from the user session. Following the user request data format defined internally by the system, a structured user request data object is generated. This user request data object ultimately contains user location data, a clear charging pile operation type, a definite target charging pile identifier, and a user identifier, thus completing the conversion from charging pile operation instructions to a standardized request, resulting in user request data. The structure of the preset charging pile operation instruction protocol specification is a document defining the data structure of charging pile operation instructions. This specification includes an instruction header (identifying the instruction version and type), an instruction body (containing key-value pairs such as operation type, charging pile identifier, and user identifier), and an instruction tail (checksum). It specifies the name, data type, length limit, and whether each field is required. When the user interaction module receives a raw charging pile operation instruction (e.g., "START:CP001,USER123"), the system first checks the instruction header format according to the specification. Then, it parses the instruction body using the key-value pair separators (such as colons and commas) defined in the specification, mapping "START" to the operation type "Start" and "CP001" to the target charging pile identifier, thereby extracting structured information. Specifically, the parsing engine uses a parsing engine based on a parser generator (such as ANTLR).

[0025] In the charging pile data acquisition module, the specific implementation method for standardizing real-time operating data to obtain a charging pile status dataset is as follows: The real-time operating data acquired by the charging pile data acquisition module through the IoT interface comes from charging piles of different manufacturers or models, and the data format, unit, or status code of the real-time operating data are not entirely the same. Standardization processing first converts various status descriptions in the real-time operating data (such as "idle," "busy," and "faulty") into enumerated values ​​defined internally by the system, according to a preset data mapping specification. For example, both "idle" and "available" are mapped to "idle state." Simultaneously, logarithmic data in SI units, such as charging power or voltage, are used. Then, the processed data is assembled into standardized charging pile records, each containing fixed fields such as charging pile identifier, working status, equipment fault marker, and charging pile location data. All standardized records of charging piles are aggregated to form a charging pile status dataset with a unified structure and complete fields. The structure of the preset data mapping specification includes a list of original status values, target standard status values, and a mapping relationship table. For example, the mapping relationship table defines that the original value "available" is mapped to "idle state," and the original value "broken" is mapped to "faulty state." When processing each piece of real-time running data, the system queries the mapping table to find the target standard state value corresponding to the original value, and replaces the original value with the standard value, thereby achieving unified standardization of state information.

[0026] In this embodiment, extracting charging pile records corresponding to user request data from the charging pile status dataset includes: parsing the user request data generated by the user interaction module to obtain key constraints, including but not limited to the target highway service area identifier, desired charging pile type, or charging power range in the user request data; traversing the charging pile status dataset generated by the charging pile data acquisition module, where each record corresponds to standardized real-time operating data of a charging pile; and comparing and filtering the attribute fields of each charging pile record in the charging pile status dataset, such as the service area identifier, charging pile type, and rated power, with the constraints parsed from the user request data. Only when all relevant attributes of a charging pile record satisfy all the key constraints contained in the user request data will the charging pile record be determined to correspond to the user request data and thus be filtered out to form the subset of charging pile records required by the subsequent scheduling verification module for actual distance calculation and status judgment.

[0027] Specifically, in the scheduling verification module, the process of calculating the actual distance between the charging pile location data and the user location data for each charging pile in the charging pile record includes: The location data of each charging pile and the location data of the user are converted to latitude and longitude coordinates in the geodetic coordinate system to obtain the corresponding coordinates of each charging pile and the user. The spherical distance algorithm is used to calculate the coordinates of each charging station and the user, resulting in the straight-line distance between the user and each charging station. The mathematical expression for the spherical distance algorithm is as follows: In the formula, Indicates user and the The straight-line distance between charging stations This represents the Earth's average radius. Indicates the latitude and longitude of the user's coordinates. Indicates the longitude of the user's location in coordinates. Indicates the first The latitude and longitude of the location of each charging station Indicates the first The longitude of the location of each charging station Indicates the use of the first The longitude difference of each charging station This represents a function used to convert latitude and longitude differences into central angles, and then obtain the straight-line distance by multiplying the central angle by the Earth's radius; A road layout model is established based on the road topology of the highway service area. Based on the road layout model, the geospatial data of the highway service area is extracted to obtain the road layout coefficient. Based on the road layout coefficient, the straight distance is corrected to obtain the actual distance between the user and each charging pile.

[0028] In this embodiment, the road layout model is a graph structure model based on the internal road network topology of a highway service area. This model uses the planar layout of the highway service area as its foundation, abstracting all feasible roads within the service area as edges, and road intersections, charging pile access points, and potential user locations (such as parking lot entrances and pedestrian walkways) as nodes, thus constructing a network topology graph composed of nodes and edges. Each edge is accompanied by attribute information, including the actual travel length of the road segment, road type (such as arterial road, auxiliary road, pedestrian walkway), and directional constraints. In the road layout model, charging pile location data is mapped to a specific node directly connected to the physical installation point of the charging pile, while user location data is mapped to a starting node in the road network based on their specific direction of entering the service area.

[0029] Based on the road layout model, geospatial data of highway service areas is extracted to obtain the road layout coefficient. This involves: searching for the optimal travel path from the starting node of the user's coordinate mapping to the target node of each charging pile's coordinate mapping within the road layout model using a shortest path algorithm (such as Dijkstra's algorithm) according to the topological connectivity of the road layout model. The search for this optimal travel path strictly follows the edge connection rules and directional constraints in the road layout model. Subsequently, geospatial data extraction is performed for each calculated shortest path, accumulating the actual travel lengths of all edges on that shortest path to obtain the theoretical shortest road distance for the user to reach the charging pile along the internal roads of the service area. The road layout coefficient is defined as the ratio of this theoretical shortest road distance to the straight-line distance between the user and the charging pile previously calculated using the spherical distance algorithm.

[0030] The straight-line distance is corrected based on the road layout coefficient to obtain the actual distance between the user and each charging pile. This includes: for the i-th charging pile, the road layout coefficient corresponding to the i-th charging pile reflects the scaling ratio of the path length required to actually travel from the user's current location along the service area's internal road network to that charging pile relative to the straight-line distance. Multiplying the straight-line distance of the i-th charging pile by the calculated road layout coefficient yields the corrected actual distance. This actual distance is an estimated value of the actual road mileage the user needs to travel, taking into account spatial constraints such as the specific road alignment, obstacle isolation, and one-way traffic regulations within the highway service area.

[0031] Sending a charging start signal to the charging pile corresponding to the target charging pile identifier based on the start authorization code involves: First, based on the target charging pile identifier specified in the charging scheduling instruction generated by the scheduling verification module, the system-maintained device connection mapping table is consulted to find the network address and communication protocol parameters corresponding to the target charging pile identifier. Then, the order processing module establishes a secure point-to-point data connection with the charging pile corresponding to the target charging pile identifier via a preset IoT communication interface, using the found network address and communication protocol parameters. After establishing the connection, the order processing module constructs a formatted control instruction data packet. The core content of this control instruction data packet includes the start authorization code from the charging scheduling instruction, used to verify the legitimacy of the start request. Finally, the order processing module sends this control instruction data packet to the charging pile corresponding to the target charging pile identifier through the established communication link. Upon receiving the data packet and verifying the validity of the start authorization code, the charging pile initiates the physical power connection and charging process, thus completing the sending and execution of the charging start signal.

[0032] Specifically, in the order processing module, the process of calculating the charging metering data of the charging pile corresponding to the target charging pile identifier to obtain the charging order data includes: Real-time metering parameters of the charging pile corresponding to the target charging pile identification are collected during the charging process. These parameters are preprocessed to output valid metering parameters. The initial total charging energy consumption is then calculated from these valid metering parameters. The mathematical expression is: In the formula, Indicates the charging start time in the valid metering parameters. Indicates the charging end time in the valid metering parameters. Indicates the first Real-time charging power at any given moment Indicates the first Charging efficiency at any given time; Initial total charging energy consumption energy consumption error threshold compared to the preset energy consumption metering standard for charging piles A comparison is performed, and the initial total charging energy consumption is corrected based on the comparison results. The final total charging energy consumption is then integrated into the charging order data. when When the order processing module determines that the initial total charging energy consumption should not be corrected, it outputs the initial total charging energy consumption that is determined not to be corrected as the final total charging energy consumption. when When the order processing module determines that the initial total charging energy consumption needs to be corrected, it performs linear calibration on the initial total charging energy consumption determined to be corrected according to the energy consumption correction coefficient in the preset charging pile energy consumption metering standard, obtains the calibrated total charging energy consumption, and outputs the calibrated total charging energy consumption as the final total charging energy consumption.

[0033] In this embodiment, the real-time metering parameters are preprocessed to output valid metering parameters. This includes: filtering outliers from the real-time metering parameter sequence collected from the charging pile corresponding to the target charging pile identifier; removing data points that clearly exceed the reasonable range based on a preset physical range (e.g., the charging power should not exceed the rated maximum value) to obtain a filtered sequence; subsequently, verifying the continuity of the filtered sequence by checking whether the timestamps are discontinuous or out of order; for missing valid data points caused by brief communication interruptions, data completion is performed using linear interpolation based on adjacent data points to ensure the continuity of the time series; finally, based on the signals at the start and end of charging, extracting a continuous, complete, and compliant segment of real-time metering parameters from the start to the end of charging from the processed complete sequence.

[0034] A pre-defined charging pile energy consumption metering standard is a document or data set defined by a management agency or technical specification. It stipulates the technical requirements, allowable error range, and calibration methods for charging pile energy consumption metering. It includes several key parameters, such as the energy consumption error threshold E0, and energy consumption correction coefficients used to calibrate metering results exceeding the error threshold. A pre-defined charging pile energy consumption metering standard might explicitly state that for a 60 kW DC charging pile, the allowable error threshold E0 for single-charge energy consumption metering is 0.5 kWh. Simultaneously, based on extensive experimental data, this pre-defined standard can define a specific energy consumption correction coefficient table for the 60 kW DC charging pile within a specific operating temperature range or load rate range. For example, 1.02 indicates that when the metered value exceeds the error threshold, the systematic positive deviation is approximately 2%. The energy consumption correction coefficient is a pre-defined numerical coefficient in the pre-defined charging pile energy consumption metering standard. It proportionally adjusts the initial total charging energy consumption exceeding the allowable error range to make the initial total charging energy consumption closer to the actual energy consumption value. This energy consumption correction factor is usually derived from long-term calibration tests and statistical analysis of the same type of charging pile. It is used to compensate for possible systematic deviations in the charging pile metering system. If the preset charging pile energy consumption metering standard is experimentally determined, and the metering module of a certain type of charging pile generally has a systematic error of reading too high under specific operating conditions, with an average over-reading ratio of 3%, then an energy consumption correction factor of 0.97 can be defined for this situation. That is, the initial reading needs to be multiplied by 0.97 to calibrate to a more accurate value.

[0035] The linear calibration of the initial total charging energy consumption, determined to require correction, based on the energy consumption correction coefficient in the preset charging pile energy consumption metering standard includes the following steps: When the order processing module determines that the initial total charging energy consumption E is greater than the energy consumption error threshold E0, the correction process is triggered. The order processing module, based on the charging pile model corresponding to the initial total charging energy consumption and the main operating range of the charging process (such as average power and ambient temperature range), queries the correspondence defined in the preset charging pile energy consumption metering standard to obtain a specific energy consumption correction coefficient k matching the situation. Subsequently, the order processing module performs linear calibration calculations, multiplying the initial total charging energy consumption E by the energy consumption correction coefficient k. The product k×E is the calibrated total charging energy consumption, which is then output as the final total charging energy consumption and integrated into the charging order data.

[0036] Sending a payment transaction request to the payment terminal based on the outstanding amount in the charging order data includes: obtaining complete charging order data from the order processing module, accurately extracting the outstanding amount from the charging order data, and simultaneously extracting core related data such as the order number, target charging pile identifier, and user association information from the charging order data. The integrity and consistency of the core related data are then verified to ensure that the outstanding amount matches the order information correctly. Subsequently, according to the preset payment interface communication protocol, the outstanding amount, order number, and other data are encapsulated into a standardized payment transaction request data packet. A connection is established between the payment management module and the payment terminal via a dedicated communication link, and the payment transaction request is sent to the payment terminal. The payment transaction request includes the outstanding amount and the unique identifier of the corresponding order. Simultaneously, request sending status monitoring is initiated to ensure that the payment terminal can accurately receive the relevant data of the payment transaction request. Specifically, the preset payment interface communication protocol uses HTTPS protocol and data encryption.

[0037] Specifically, in the payment management module, the process of updating the payment status of the charging order data based on the payment confirmation information and generating order payment information includes: The payment confirmation information is parsed to obtain a payment parsing result, which includes a transaction serial number, a payment amount, and a transaction status flag. The order identifier of the initial charging order associated with the transaction serial number is obtained by querying the preset payment transaction mapping relationship index based on the transaction serial number. Based on the order identifier, retrieve the charging order data to be updated corresponding to the order identifier from the charging order storage area. The charging order data to be updated includes the total amount of fees to be paid and historical payment status records. The payment amount in the parsed result is compared with the total amount of unpaid fees in the charging order data to be updated. Based on the comparison result, the payment status is determined, and the payment status of the charging order data is updated accordingly, generating order payment information. When the payment amount is greater than or equal to the total amount to be paid and the transaction status is marked as successful, the payment management module determines that the payment status is valid, modifies the payment status field value in the charging order data to be updated to the paid status value, calculates the difference between the payment amount and the total amount to be paid as the overpayment amount data item, obtains the updated charging order data, and generates payment success data containing the successful order identifier, final payment status, successful payment time and successful payment voucher number by combining the timestamp and payment channel identifier in the payment confirmation information, and outputs the payment success data as order payment information; When the payment amount is less than the total amount to be paid, or the transaction status is marked as failed, the payment management module determines that the payment status is invalid, does not modify the payment status field value in the charging order data to be updated, generates a payment exception details record containing the abnormal transaction status code, and outputs the payment exception details record as order payment information.

[0038] In this embodiment, the specific process of parsing the payment confirmation information to obtain the payment parsing result includes: The payment confirmation information received by the payment management module is usually a structured data message or a data object returned by a standardized interface. The parsing process is based on a preset data format specification, extracting and converting fields from the payment confirmation information. Specifically, by identifying specific data segments in the payment confirmation information, three key data items are extracted: transaction serial number, payment amount, and transaction status flag. The transaction serial number is usually a unique string sequence generated by the payment channel; the payment amount is extracted in numerical data form and converted into the system's internal unit of measurement; and the transaction status flag is mapped to a system-recognizable status enumeration value according to the status code agreed upon in the payment confirmation information, such as "SUCCESS" representing a successful status. After parsing, the data items of transaction serial number, payment amount, and transaction status flag are encapsulated into a payment parsing result data object. Specifically, the preset data format specifications are the basis for parsing payment confirmation information, which refers to the pre-defined field extraction rules, data type conversion standards, and status code mapping rules; for example, specifying the position of the transaction serial number field, the numerical type and conversion ratio of the payment amount, and mapping the status code "00" to "SUCCESS", etc.

[0039] The pre-defined payment transaction mapping index is a relational data structure stored within the system to establish the correspondence between transaction serial numbers and the order identifiers of initial charging orders. The pre-defined payment transaction mapping index typically exists in key-value pair format, where the key is the transaction serial number and the value is the corresponding order identifier. In practice, the pre-defined payment transaction mapping index can be stored through a database table, cache, or dedicated index file. When a charging order is generated and a payment request is initiated, the system associates the order identifier of that order with the transaction serial number returned by the payment channel in real time and persists this association to the pre-defined payment transaction mapping index, ensuring that the corresponding initial charging order can be quickly located using the transaction serial number. The process of using the pre-defined payment transaction mapping index includes: after obtaining the payment parsing result, the payment management module retrieves the transaction serial number from the payment parsing result. Subsequently, the system uses this transaction serial number as the query condition to perform a search in the pre-defined payment transaction mapping index. The search operation is performed according to the storage format of the index, such as querying a database index table or retrieving cached key-value pairs. If a match is found, the system returns the order identifier of the initial charging order associated with that transaction serial number; otherwise, the transaction serial number is considered invalid, and the process terminates. By using a pre-defined payment transaction mapping index, the system achieves a fast and accurate association between payment transactions and charging orders.

[0040] The specific process of generating payment success data by combining the timestamp and payment channel identifier from the payment confirmation information includes: After determining that the payment status is valid and updating the charging order data, the payment management module first extracts the timestamp and payment channel identifier from the payment confirmation information. The timestamp is usually the precise time data of payment completion, and the payment channel identifier is a code that identifies the source of payment. Subsequently, the system obtains the successful order identifier, i.e., the order identifier, from the updated charging order data and sets the final payment status to the paid status value. The successful payment time directly uses the timestamp from the payment confirmation information, and the successful payment voucher number uses the transaction serial number from the payment parsing result. Finally, these data items are combined into a structured data object, i.e., payment success data containing the successful order identifier, final payment status, successful payment time, and successful payment voucher number, which is output as the order payment information.

[0041] The specific process for generating a payment exception details record containing an abnormal transaction status code includes the following steps: After determining that the payment status is invalid, the payment management module first determines the exception type based on the comparison between the transaction status flag and the payment amount value in the payment parsing result and the total amount to be paid. The system internally predefines a series of abnormal transaction status codes, each corresponding to different exception scenarios, such as "insufficient amount" or "transaction failed." Subsequently, the payment management module selects the corresponding abnormal transaction status code based on the specific exception type and combines it with key information such as the transaction serial number, payment amount value, total amount to be paid, and timestamp from the payment confirmation information in the payment parsing result to form a structured log record. This record is the payment exception details record containing the abnormal transaction status code, which serves as the order payment information output for subsequent exception handling and reconciliation.

[0042] Specifically, in the invoice archiving module, the process of querying the target pending invoice order data pool that matches the invoice request includes: The invoice request is parsed to obtain user identification data and invoice request time data. Based on the user identification data, all candidate orders that match the user identification data are selected from the pending invoice order data pool to generate a first candidate order set. Based on the invoice request time data and the charging end time data of each candidate order in the first candidate order set, the time correlation parameter of each candidate order is calculated, and the candidate orders in the first candidate order set are sorted according to the time correlation parameter to generate a sorted second candidate order set. The candidate order with the highest ranking is extracted from the second candidate order set as the target invoice order.

[0043] In this embodiment, the specific process of calculating the time correlation parameter for each candidate order includes the following steps: For each candidate order in the first candidate order set, the invoice archiving module first obtains the charging end time data of the candidate order and parses the invoice request time data, converting the charging end time data and the invoice request time data into a unified and comparable timestamp format (e.g., seconds since the standard epoch). Next, the absolute time difference between the timestamps of the charging end time data and the invoice request time data is calculated. Then, a preset time decay function is applied, which takes the absolute time difference as input and outputs a time correlation parameter value. This time decay function is typically designed so that the output value monotonically decreases as the time difference increases, for example, using a negative exponential function or a reciprocal function, to ensure that for candidate orders whose charging end time is closer to the invoice request time, the larger the time correlation parameter value calculated by the preset time decay function, the higher the correlation.

[0044] The candidate orders in the first candidate order set are sorted according to the time correlation parameter by comparing and ranking the values ​​of the time correlation parameter for each candidate order. After calculating the time correlation parameter for all candidate orders, the invoice archiving module processes these candidate orders and their corresponding time correlation parameter values ​​as a whole dataset. The sorting logic is that candidate orders with larger time correlation parameter values ​​are considered to be more closely related to the current invoicing request in the time dimension and are more likely to be the orders referred to by the user's intent. Therefore, the invoice archiving module rearranges all candidate orders in the first candidate order set according to the rule of descending order of time correlation parameter values; this sorting process generates an ordered list, namely the second candidate order set, in which the first-ranked (i.e., highest-ranked) candidate order is the candidate order with the largest time correlation parameter value and is selected as the target invoice order.

[0045] Specifically, in the invoice archiving module, the process of generating electronic invoice data based on the invoice request and the preset invoice template includes: Based on the invoicing request, extract the user's tax identification data and invoicing item data, and map the invoice structure data defined in the preset invoice template with the invoicing item data to generate structured invoicing data; The structured invoice data is digitally signed using an encryption algorithm to generate anti-counterfeiting identification data. The structured invoice data and the anti-counterfeiting identification data are then integrated into the preset invoice template to obtain electronic invoice data. The expression for the encryption algorithm is: In the formula, This indicates anti-counterfeiting label data. This indicates the structured invoicing data. The result after performing the hash operation, Indicates the preset encryption modulus. This indicates the modulo operation.

[0046] In this embodiment, the preset invoice template refers to a standardized data framework that defines the fixed format, core structural fields, and display style of electronic invoice data. This preset invoice template is typically a structured file or data object containing inherent elements of an invoice, such as the invoice type code, fixed invoice header text, tax supervision stamp information, invoicing unit name and taxpayer identification number, and static or semi-static content like invoice code and number generation rules. It also reserves location identifiers or data binding fields for filling dynamic invoice item data. (Preset encryption module) It is a pre-defined large integer in the encryption algorithm, used for modulo operations to ensure the result is within a certain range; the preset encryption modulus. The value of is usually a chosen, sufficiently large prime number or the product of two large prime numbers to enhance the unpredictability and collision resistance of the anti-counterfeiting data. For example, a preset encryption modulus can be used. It can take the value of a large prime number with 1024 bits.

[0047] Mapping the invoice structure data defined in the preset invoice template to the invoice item data is accomplished by filling the specific numerical content of the invoice item data into the corresponding field positions reserved in the preset invoice template. Invoice item data typically includes the name of the goods or services, quantity, unit price, amount, tax rate, and tax amount. The preset invoice template has already defined field labels such as "name of goods or taxable labor / services," "quantity," "unit price," "amount," "tax rate," and "tax amount." The mapping process involves precisely assigning each item in the invoice item data to the corresponding data field in the preset invoice template based on these field labels, thereby generating a complete and structured draft invoice data, i.e., structured invoice data. Integrating the structured invoice data and the anti-counterfeiting identification data into the preset invoice template includes: First, the structured invoice data, as the main content of the invoice, is completely filled into the core content area of ​​the preset invoice template specifically used to carry variable invoice information. Subsequently, according to the design of the preset invoice template, there will be a specific field or data block (such as a field named "Anti-counterfeiting Mark" or "Digital Signature") to store the anti-counterfeiting mark data. The integration process involves writing the calculated anti-counterfeiting mark data into this designated field of the preset invoice template. After completing these two data injection steps, the preset invoice template transforms from an empty frame into a complete data entity containing specific invoicing content and security verification information, i.e., electronic invoice data.

[0048] Specifically, in the invoice archiving module, the process of associating and storing the electronic invoice data and the orders corresponding to the electronic invoice data includes: Extract unique invoice identifier data from the electronic invoice data, extract unique order identifier data from the target order to be invoiced, and pair the unique invoice identifier data with the unique order identifier data according to preset association rules to generate association mapping data; The association mapping data is input into the storage index generation function to generate corresponding distributed storage path data. Based on the distributed storage path data, the electronic invoice data is stored in the corresponding storage node, and the association mapping data is written into the system association database to obtain the association storage result. The expression of the storage index generation function is: In the formula, This represents distributed storage path data. This represents the unique identifier data for the order. The hash operation performed Indicates the first Unique identifier data for each invoice The hash operation performed This indicates the XOR operation. Indicates the total number of storage nodes. Indicates the storage base address.

[0049] In this embodiment, the preset association rules refer to a set of logical criteria or data matching conditions predefined by the system for establishing a unique link between electronic invoice data and corresponding orders. For example, using the order unique identifier data as the primary key, when generating electronic invoice data, the invoice unique identifier data of the electronic invoice data is used as the foreign key. The two must be recorded in pairs, and one order unique identifier data can only be associated with one valid invoice unique identifier data at the same time.

[0050] Specifically, in the invoice archiving module, the process of updating the invoicing status of the order corresponding to the electronic invoice data to obtain the corresponding charging pile archiving information includes: Based on the associated storage result, obtain the unique identifier data of the order, query the pending invoice order record corresponding to the unique identifier data of the order in the pending invoice order data pool, and extract the current invoicing status data corresponding to the unique identifier data of the order from the pending invoice order record; The current invoice status data is analyzed according to a preset invoice status transition rule to generate a status update instruction. The expression of the preset invoice status transition rule is as follows: In the formula, This indicates the updated invoice status value. This indicates the current invoicing status data. Indicates the payment verification result; According to the status update instruction, the invoice status field in the order record to be invoiced is modified to the updated invoice status value, and the combined information of the storage path data containing the order record to be invoiced and the electronic invoice data and the updated invoice status value is written into the system archive log as charging pile archive information.

[0051] In this embodiment, modifying the invoice status field in the pending invoice order record to the updated invoice status value according to the status update instruction includes: the status update instruction contains the unique identifier data of the order to be updated and the specified updated invoice status value. The invoice archiving module locates the corresponding pending invoice order record in the pending invoice order data pool based on the unique identifier data. Then, the module directly accesses the data structure of the pending invoice order record, finds the "Invoice Status" field, and overwrites its currently stored value (i.e., the current invoice status data) with the updated invoice status value provided in the status update instruction. This operation completes the modification of the invoice status field.

[0052] Writing the combined information of the storage path data containing the order record to be invoiced, the e-invoice data, and the updated invoice status value as charging pile archiving information to the system archive log involves the following steps: First, the invoice archiving module retrieves the key summary information of the order record to be invoiced (such as the unique order identifier) ​​from the associated storage results, the storage location identifier of the e-invoice data from the distributed storage path data, and the recently updated invoice status value. Then, this information is combined and encapsulated according to the predefined structure format of the system archive log (e.g., including fields such as timestamp, operation type, order ID, invoice storage path, and new invoice status) to form a complete log record. Finally, by calling the write interface of the system log service, this log record is appended to the system archive log file or a dedicated archive database, thus becoming a piece of charging pile archive information.

[0053] The above are merely embodiments of the present invention. Commonly known structures and characteristics are not described in detail here. Those skilled in the art are aware of all common technical knowledge in the field prior to the application date or priority date, are aware of all existing technologies in that field, and have the ability to apply conventional experimental methods prior to that date. Those skilled in the art can, under the guidance of this application, improve and implement this solution in combination with their own capabilities. Some typical known structures or methods should not be obstacles for those skilled in the art to implement this application. It should be noted that those skilled in the art can make several modifications and improvements without departing from the structure of the present invention. These should also be considered within the scope of protection of the present invention, and will not affect the effectiveness of the implementation of the present invention or the practicality of the patent. The scope of protection claimed in this application should be determined by the content of its claims, and the specific embodiments described in the specification can be used to interpret the content of the claims.

Claims

1. A unified consumption and linkage service system for highway charging stations, characterized in that: include: The user interaction module is used to receive user location data and charging pile operation instructions submitted by the user through the user terminal, and to parse the charging pile operation instructions to generate user request data. The charging pile data acquisition module is used to acquire real-time operating data of each charging pile in the highway service area through the Internet of Things interface, and to standardize the real-time operating data to obtain a charging pile status dataset. The scheduling verification module is used to extract the charging pile record corresponding to the user request data from the charging pile status dataset according to the user request data, and calculate the actual distance between the charging pile location data and the user location data of each charging pile in the charging pile record. When the actual distance is less than the preset distance threshold, and the working status in the charging pile record is idle and the equipment fault mark in the charging pile record is not faulty, a charging scheduling instruction containing the start authorization code and the target charging pile identifier is generated. The order processing module is used to send a charging start signal to the charging pile corresponding to the target charging pile identifier according to the start authorization code, and after receiving the charging end signal, calculate the charging metering data of the charging pile corresponding to the target charging pile identifier to obtain the charging order data. The payment management module is used to send a payment transaction request to the payment terminal based on the unpaid fees in the charging order data, receive payment confirmation information returned by the payment terminal, update the payment status of the charging order data based on the payment confirmation information, and generate order payment information. The invoice archiving module is used to generate a pool of orders to be invoiced based on order payment information, respond to invoicing requests initiated by users through the user interaction module, query the pool of orders to be invoiced that match the invoicing request, verify the target orders to be invoiced, and generate electronic invoice data based on the invoicing request and a preset invoice template when the payment status of the target order to be invoiced is "paid" and the invoicing status of the order to be invoiced is "not invoiced". The module also associates and stores the electronic invoice data and the order corresponding to the electronic invoice data, updates the invoicing status of the order corresponding to the electronic invoice data, and obtains the corresponding charging pile archiving information.

2. The unified consumption and linkage service system for highway charging piles according to claim 1, characterized in that: In the scheduling verification module, the specific process of calculating the actual distance between the charging pile location data and the user location data for each charging pile in the charging pile record includes: The location data of each charging pile and the location data of the user are converted to latitude and longitude coordinates in the geodetic coordinate system to obtain the corresponding coordinates of each charging pile and the user. The spherical distance algorithm is used to calculate the coordinates of each charging station and the user, resulting in the straight-line distance between the user and each charging station. The mathematical expression for the spherical distance algorithm is as follows: In the formula, Indicates user and the The straight-line distance between charging stations This represents the Earth's average radius. Indicates the latitude and longitude of the user's coordinates. Indicates the longitude of the user's location in coordinates. Indicates the first The latitude and longitude of the location of each charging station Indicates the first The longitude of the location of each charging station Indicates the use of the first The longitude difference of each charging station This represents a function used to convert latitude and longitude differences into central angles, and then obtain the straight-line distance by multiplying the central angle by the Earth's radius; A road layout model is established based on the road topology of the highway service area. Based on the road layout model, the geospatial data of the highway service area is extracted to obtain the road layout coefficient. Based on the road layout coefficient, the straight distance is corrected to obtain the actual distance between the user and each charging pile.

3. The unified consumption and linkage service system for highway charging piles according to claim 1, characterized in that: In the order processing module, the specific process of calculating the charging metering data of the charging pile corresponding to the target charging pile identifier to obtain the charging order data includes: Real-time metering parameters of the charging pile corresponding to the target charging pile identification are collected during the charging process. These parameters are preprocessed to output valid metering parameters. The initial total charging energy consumption is then calculated from these valid metering parameters. The mathematical expression is: In the formula, Indicates the charging start time in the valid metering parameters. Indicates the charging end time in the valid metering parameters. Indicates the first Real-time charging power at any given moment Indicates the first Charging efficiency at any given time; Initial total charging energy consumption energy consumption error threshold compared to the preset energy consumption metering standard for charging piles A comparison is performed, and the initial total charging energy consumption is corrected based on the comparison results. The final total charging energy consumption is then integrated into the charging order data. when When the order processing module determines that the initial total charging energy consumption should not be corrected, it outputs the initial total charging energy consumption that is determined not to be corrected as the final total charging energy consumption. when When the order processing module determines that the initial total charging energy consumption needs to be corrected, it performs linear calibration on the initial total charging energy consumption determined to be corrected according to the energy consumption correction coefficient in the preset charging pile energy consumption metering standard, obtains the calibrated total charging energy consumption, and outputs the calibrated total charging energy consumption as the final total charging energy consumption.

4. The unified consumption and linkage service system for highway charging piles according to claim 1, characterized in that: In the payment management module, the specific process of updating the payment status of the charging order data based on the payment confirmation information and generating order payment information includes: The payment confirmation information is parsed to obtain a payment parsing result, which includes a transaction serial number, a payment amount, and a transaction status flag. The order identifier of the initial charging order associated with the transaction serial number is obtained by querying the preset payment transaction mapping relationship index based on the transaction serial number. Based on the order identifier, retrieve the charging order data to be updated corresponding to the order identifier from the charging order storage area. The charging order data to be updated includes the total amount of fees to be paid and historical payment status records. The payment amount in the parsed result is compared with the total amount of unpaid fees in the charging order data to be updated. Based on the comparison result, the payment status is determined, and the payment status of the charging order data is updated accordingly, generating order payment information. When the payment amount is greater than or equal to the total amount to be paid and the transaction status is marked as successful, the payment management module determines that the payment status is valid, modifies the payment status field value in the charging order data to be updated to the paid status value, calculates the difference between the payment amount and the total amount to be paid as the overpayment amount data item, obtains the updated charging order data, and generates payment success data containing the successful order identifier, final payment status, successful payment time and successful payment voucher number by combining the timestamp and payment channel identifier in the payment confirmation information, and outputs the payment success data as order payment information; When the payment amount is less than the total amount to be paid, or the transaction status is marked as failed, the payment management module determines that the payment status is invalid, does not modify the payment status field value in the charging order data to be updated, generates a payment exception details record containing the abnormal transaction status code, and outputs the payment exception details record as order payment information.

5. The unified consumption and linkage service system for highway charging piles according to claim 1, characterized in that: In the invoice archiving module, the specific process of querying the target pending invoice order data pool that matches the invoice request includes: The invoice request is parsed to obtain user identification data and invoice request time data. Based on the user identification data, all candidate orders that match the user identification data are selected from the pending invoice order data pool to generate a first candidate order set. Based on the invoice request time data and the charging end time data of each candidate order in the first candidate order set, the time correlation parameter of each candidate order is calculated, and the candidate orders in the first candidate order set are sorted according to the time correlation parameter to generate a sorted second candidate order set. The candidate order with the highest ranking is extracted from the second candidate order set as the target invoice order.

6. The unified consumption and linkage service system for highway charging piles according to claim 5, characterized in that, In the invoice archiving module, the specific process of generating electronic invoice data based on the invoice request and the preset invoice template includes: Based on the invoicing request, extract the user's tax identification data and invoicing item data, and map the invoice structure data defined in the preset invoice template with the invoicing item data to generate structured invoicing data; The structured invoice data is digitally signed using an encryption algorithm to generate anti-counterfeiting identification data. The structured invoice data and the anti-counterfeiting identification data are then integrated into the preset invoice template to obtain electronic invoice data. The expression for the encryption algorithm is: In the formula, This indicates anti-counterfeiting label data. This indicates the structured invoicing data. The result after performing the hash operation, Indicates the preset encryption modulus. This indicates the modulo operation.

7. The unified consumption and linkage service system for highway charging piles according to claim 6, characterized in that, In the invoice archiving module, the specific process of associating and storing the electronic invoice data and the orders corresponding to the electronic invoice data includes: Extract unique invoice identifier data from the electronic invoice data, extract unique order identifier data from the target order to be invoiced, and pair the unique invoice identifier data with the unique order identifier data according to preset association rules to generate association mapping data; The association mapping data is input into the storage index generation function to generate corresponding distributed storage path data. Based on the distributed storage path data, the electronic invoice data is stored in the corresponding storage node, and the association mapping data is written into the system association database to obtain the association storage result. The expression of the storage index generation function is: In the formula, This represents distributed storage path data. This represents the unique identifier data for the order. The hash operation performed Indicates the first Unique identifier data for each invoice The hash operation performed This indicates the XOR operation. Indicates the total number of storage nodes. Indicates the storage base address.

8. The unified consumption and linkage service system for highway charging piles according to claim 7, characterized in that, In the invoice archiving module, the specific process of updating the invoicing status of the order corresponding to the electronic invoice data to obtain the corresponding charging pile archiving information includes: Based on the associated storage result, obtain the unique identifier data of the order, query the pending invoice order record corresponding to the unique identifier data of the order in the pending invoice order data pool, and extract the current invoicing status data corresponding to the unique identifier data of the order from the pending invoice order record; The current invoice status data is analyzed according to a preset invoice status transition rule to generate a status update instruction. The expression of the preset invoice status transition rule is as follows: In the formula, This indicates the updated invoice status value. This indicates the current invoicing status data. Indicates the payment verification result; According to the status update instruction, the invoice status field in the order record to be invoiced is modified to the updated invoice status value, and the combined information of the storage path data containing the order record to be invoiced and the electronic invoice data and the updated invoice status value is written into the system archive log as charging pile archive information.

Images