Charging pile communication data interaction method and system supporting network communication interface

Abstract

The application discloses a charging pile communication data interaction method and system supporting a network communication interface, belongs to the technical field of electric vehicle charging pile communication control, and when a recovery connection is performed after an Ethernet link is disconnected, link recovery collision is identified according to a link interruption duration and a first frame arrival interval, cloud platform order messages, energy management messages and metering messages are analyzed and distinguished, messages with the same charging session identifier are written into a temporary interaction queue, and a message logical sequence is generated based on a metering frozen serial number and a power scheduling effective time; when power scheduling should be processed prior to order state processing, a data interaction state is generated, related settlement messages are suspended, a target limited power is executed, and after actual output power and a next metering frozen value are checked, the lock is released and a response message is generated; the application can reduce the risk of message out-of-order after link recovery, power limiting lag and metering settlement mismatch.

Description

Technical Field

[0001] This invention relates to the field of electric vehicle charging pile communication control technology, and more specifically to a charging pile communication data interaction method and system that supports network communication interfaces. Background Technology

[0002] In existing technologies, with the centralized deployment of electric vehicle charging facilities in underground garages, park parking lots, and residential communities, an increasing number of charging piles are equipped with network communication interfaces (such as Ethernet, WiFi, mobile communication, or powerline communication interfaces) for communication and interaction with cloud platforms, energy management systems, and electricity metering devices. The cloud platform is typically used to issue business data such as order initiation, order completion, and payment settlement; the energy management system is used to issue control data such as power limiting, peak-shifting charging, and load scheduling; and the electricity metering device is used to upload metering freeze values, metering serial numbers, and electricity consumption data.

[0003] Existing charging pile communication processing methods typically parse and execute messages in the order they are received via the Ethernet interface, or set a fixed priority based solely on the message service type. However, in practical applications, situations such as underground parking garage switch restarts, poor network cable connections, LAN storm recovery, and re-entry into the network after a DHCP lease renewal failure can cause short-term disconnections of the charging pile's Ethernet link. When the link is restored, the cloud platform, energy management system, and metering device may simultaneously resend the backlogged order messages, power scheduling messages, and metering freeze messages to the charging pile during the link interruption, causing communication messages from multiple sources and with multiple service meanings to arrive in a very short period of time.

[0004] In the above scenarios, if charging piles still process messages according to their arrival order, the actual effective time of the power scheduling message may be earlier than the processing time of the order status message, but its execution may be delayed due to its later arrival order. This could cause the charging pile to continue outputting the original charging power during periods when the power grid or park load has already requested power limiting, resulting in instantaneous overload of local power distribution branches. On the other hand, if the metering freeze message is not associated with the corresponding charging session and order status, the metering value resent after the link is restored may be incorrectly classified into the current order or the completed order, leading to abnormal settlement electricity, untraceable power limiting execution results, and inconsistencies between platform and local metering data.

[0005] Especially when multiple vehicles are connected simultaneously, multiple charging piles are connected to the same switch, and the building energy management system performs dynamic power allocation, the centralized retransmission of messages after link recovery is not continuous but rather sporadic and short-term bursty. Traditional communication timeout reconnection, message retransmission verification, or fixed priority queues are difficult to identify such link recovery collision states in a timely manner, and cannot reconstruct the actual order of business occurrences based on the metering freeze sequence number and power scheduling effective time. Therefore, existing charging pile Ethernet communication interaction methods suffer from inconsistencies between the message processing order after link recovery and the actual business order, delayed power scheduling response, and mismatches between order settlement and metering data, affecting the operational safety, metering accuracy, and communication interaction reliability of charging piles. Summary of the Invention

[0006] The purpose of this invention is to provide a charging pile communication data interaction method and system that supports network communication interfaces, so as to solve the shortcomings in the background technology.

[0007] To achieve the above objectives, the present invention provides the following technical solution: a charging pile communication data interaction method supporting a network communication interface, comprising: Obtain link status change information of the charging pile network communication interface; when the network communication interface is detected to recover from disconnection to connection, record the link interruption duration and collect the first frame arrival interval of a preset number of communication messages after recovery. The communication message is parsed to obtain the message source address, service type, charging session identifier, metering freeze sequence number and power scheduling effective time, and the cloud platform order message, energy management message and metering message are distinguished according to the message source address and the service type. If the link interruption duration is greater than the interruption threshold and the first frame arrival interval is less than the congestion threshold, a link recovery collision flag is generated. According to the link recovery collision identifier, communication messages with the same charging session identifier are written into a temporary interaction queue, and a logical order of messages is generated based on the metering freeze sequence number and the power scheduling effective time. When the message logical sequence indicates that the effective time of the power scheduling message is earlier than the processing time of the order status message, a data interaction status is generated. The data interaction status includes the target limit power, the benchmark metering value, the pending order status, and the interaction lock code. Based on the interaction lock code, the processing of settlement messages related to the pending order status is suspended, and the target limit power is sent to the charging control module so that the charging pile outputs according to the target limit power. The system obtains the actual output power and the next metering freeze value fed back by the charging control module, verifies the data interaction status based on the actual output power and the benchmark metering value, releases the interaction lock code if the verification passes, and generates an order response message and a power scheduling response message based on the next metering freeze value. These messages are then sent to the corresponding source addresses via the network communication interface to complete the charging pile communication data interaction.

[0008] Preferably, the link recovery collision identifier is used to indicate that the cloud platform order message, energy management message and metering message are resent in a concentrated manner after the link is restored.

[0009] Preferably, generating a link recovery collision identifier includes: The interruption threshold is determined based on the normal link jitter recovery time and the service packet backlog time, and the congestion threshold is determined based on the normal service packet arrival interval and the single service packet enqueue processing time. When the duration of the link interruption exceeds the interruption threshold, determine whether the preset number of communication messages after the link is restored simultaneously contain cloud platform order messages, energy management messages, and metering messages; If the cloud platform order message, energy management message, and metering message are included simultaneously, and the maximum first frame arrival interval covering the three types of messages is less than the congestion threshold, then a link recovery collision identifier is generated that includes the link recovery time, the link interruption duration, and a bitmap of the three types of messages.

[0010] Preferably, communication messages with the same charging session identifier are written to a temporary interaction queue, including: Read the link recovery time and the bitmap of the three types of messages in the link recovery collision identifier, and generate a temporary interaction queue that corresponds only to this link recovery collision based on the link recovery time; The charging session identifier of the communication messages within the link recovery collection range is compared with the currently executing charging session identifier. If the comparison is consistent, the communication messages are written into the order message area, energy management message area, or metering message area of ​​the temporary interaction queue according to the service type, and the arrival offset of the corresponding communication message relative to the link recovery time is recorded.

[0011] Preferably, writing to the temporary interaction queue also includes: When the cloud platform order message, energy management message and metering message corresponding to the three message type bitmaps have all been written into the same temporary interaction queue, the temporary interaction queue is marked as locked. In the locked state, communication messages with different charging session identifiers are prohibited from being inserted into the temporary interaction queue. For communication messages with the same charging session identifier but outside the link recovery collection range, they are processed according to the normal communication process so that they do not participate in the generation of the current message logical order.

[0012] Preferably, the logical order of generating messages based on the metering freeze sequence number and the power scheduling effective time includes: Read the metering freeze sequence number in the metering message area, generate the session metering sequence number axis according to the increasing direction of the metering freeze sequence number, and mark the duplicate or backward metering freeze sequence number as the reissue sequence number; The power scheduling effective time in the energy management message is anchored to the session metering sequence number axis, and a scheduling insertion bit is generated between two adjacent valid metering freeze sequences, before the first valid metering freeze sequence number, or after the last valid metering freeze sequence number. The cloud platform order message, energy management message, and metering message are assigned logical processing numbers based on the scheduling insertion bit, and the settlement order message is arranged after the energy management message in the same metering freeze interval.

[0013] Preferably, the data interaction state is generated, including: When the logical processing number of the power scheduling message is less than the logical processing number of the order status message, a valid scheduling message is determined from the power scheduling message, and the target limited power is extracted. Based on the scheduling insertion bit of the valid scheduling message, the frozen electricity corresponding to the valid metering freeze sequence number that is closest to and before the scheduling insertion bit is selected as the benchmark metering value. The target power limit, the reference meter value, and the pending order status extracted from the order status message are bound to the current charging session identifier to generate the data interaction status.

[0014] Preferably, pausing the processing of settlement messages related to the pending order status based on the interaction lock code includes: The interaction lock code is calculated by concatenating the queue identifier of the temporary interaction queue, the current charging session identifier, the logical processing number of the valid scheduling message, the target limit power, the metering freeze sequence number corresponding to the benchmark metering value, and the status of the pending order in a fixed order. Write the settlement message related to the status of the order to be confirmed into the locked sub-area of ​​the order message area, and write the interaction lock code into the data record of the settlement message; Before the interactive lock code is released, it is prohibited to generate settlement electricity confirmation, fee confirmation, order end response or transaction closure confirmation based on the settlement message.

[0015] Preferably, verifying the data interaction status based on the actual output power and the reference measurement value includes: The actual output power is received based on the interactive locking code, and the actual output power between the power scheduling effective time and the time when the next metering freeze value is generated is extracted to form a locked power sequence. The locked power increment is calculated based on the next metering freeze value and the benchmark metering value, and the power integral power is calculated based on the locked power sequence. The difference between the locked power increment and the power integral power is compared to obtain the metered power deviation value. When the actual output power does not exceed the target limit power and the metered power deviation value is within the allowable deviation range, the interactive lock code is released, and an order response message and a power scheduling response message are generated.

[0016] The present invention also provides a charging pile communication data interaction system that supports network communication interfaces, including: a link status monitoring module, a communication message parsing module, a link recovery collision identification module, a temporary interaction queue generation module, a data interaction status control module, and an interaction verification response module.

[0017] The technical effects and advantages provided by the present invention in the above technical solution are as follows: This invention differs from existing technologies that process communication messages according to arrival order or only according to a fixed priority. Its core lies in introducing a link recovery collision identification + temporary interaction queue for the same charging session. Specifically, this invention does not simply increase the priority of energy management messages during arbitrary communication congestion. Instead, after the network communication interface is restored from a disconnection, it generates a link recovery collision identifier by combining the link interruption duration, the arrival interval of the first frame of the restored communication message, and the concentrated occurrence of cloud platform order messages, energy management messages, and metering messages. Only messages with the same charging session identifier are written into the temporary interaction queue. This processing method can accurately identify special scenarios such as the concentrated retransmission of multiple source messages after the underground garage switch restarts, port jitter recovery, or network re-entry, avoiding mistaking normal periodic messages for abnormal retransmission messages, and preventing historical messages from other charging guns or other vehicles from mixing into the current session. Therefore, this invention can solve the problems of complex message sources, mixed sessions, and distorted retransmission order after link recovery at the communication entry point, improving the data attribution accuracy and communication processing reliability of charging piles in abnormal network recovery scenarios.

[0018] This invention further utilizes the metering freeze sequence number and power scheduling effective time to generate the message logical order, and generates a data interaction state containing the target limit power, benchmark metering value, pending order status, and interaction lock code when the power scheduling message should be processed before the order status message. In this way, the charging pile does not passively wait for all order messages to be processed before executing the power limiting command, but instead forms a metering boundary based on the metering freeze sequence number, determines the scheduling insertion position based on the power scheduling effective time, and temporarily locks the relevant settlement message using the interaction lock code, while simultaneously sending the target limit power to the charging control module for execution. Subsequently, this invention also uses the actual output power and the next metering freeze value to verify the data interaction state. Only when the power limit has been executed and the metering increment matches the power integral is the settlement message released and a corresponding response generated. This directly solves the problems of delayed power limiting response, premature order settlement, mismatched frozen power, and inconsistent platform data that may occur in existing charging piles after link recovery, simultaneously improving power scheduling security, metering accuracy, and order response consistency. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this invention. For those skilled in the art, other drawings can be obtained based on these drawings.

[0020] Figure 1 This is a flowchart of the method of the present invention.

[0021] Figure 2 This is a flowchart of the system modules of the present invention. Detailed Implementation

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

[0023] Example 1, please refer to Figure 1 As shown in this embodiment, the charging pile communication data interaction method supporting network communication interface includes: S1. Obtain the link status change information of the charging pile network communication interface. When the network communication interface is detected to recover from the disconnected state to the connected state, record the link interruption duration and collect the first frame arrival interval of a preset number of communication messages after recovery.

[0024] In this embodiment, a network communication module is provided on the charging pile control board. For ease of explanation, this embodiment uses an Ethernet communication interface as an example. The network communication module includes an Ethernet PHY chip, a MAC controller, and a communication processing unit. The network communication module can also be implemented using a WiFi module, a mobile communication module, or a power line communication module. Its link status change information, message acquisition, and message interaction process are consistent with the Ethernet implementation method.

[0025] Specifically, when the communication processing unit detects that the PHY link status changes from connected to disconnected, it reads the current timing of the monotonically increasing timer, records it as the link disconnection time Tdown, and marks the current link status as disconnected. The monotonically increasing timer can be a millisecond-level system clock inside the charging pile controller, which does not change with cloud platform time synchronization or system time modification.

[0026] When the communication processing unit detects that the PHY link status has changed from disconnected to connected again, in order to avoid misjudgment caused by loose network cable or switch port jitter, it first determines whether the connection status has been stable for a preset time, such as 100ms. If the preset time is reached, the current time is read and recorded as the link recovery time Tup, and the link interruption duration ΔT is calculated based on Tup-Tdown.

[0027] After obtaining the link interruption duration, the communication processing unit establishes a link recovery acquisition buffer. This buffer includes at least the link disconnection time, link recovery time, link interruption duration, message sequence number, message arrival time, and first frame arrival interval. From the link recovery time, the communication processing unit enters the recovery message acquisition state and counts the communication messages received through the network communication interface.

[0028] Specifically, the communication processing unit can filter non-service messages such as ARP messages, DHCP messages, and broadcast discovery messages, and only collect service communication messages from the cloud platform, energy management system, or metering device. For the first service communication message received after the link is restored, its arrival time is recorded as T1, and T1-Tup is used as the first frame arrival interval; for the i-th service communication message received subsequently, its arrival time is recorded as Ti, and Ti-T(i-1) is used as the corresponding first frame arrival interval, where i is an integer greater than 1.

[0029] The preset number can be set according to the communication load of the charging pile, for example, to 6, 8 or 10 service communication messages. When the preset number of service communication messages are collected, or when the preset number has not been collected after a preset collection time since the link recovery time, the communication processing unit ends the message collection state and writes the collected link interruption duration and the arrival interval of each first frame into the link recovery record table.

[0030] Therefore, after the network communication interface link is restored, the charging pile can obtain the duration of the link interruption and the concentrated arrival characteristics of communication messages in the early stage of restoration, providing basic data for subsequent determination of whether there is a concentrated resending of cloud platform order messages, energy management messages and metering messages.

[0031] S2. Parse the communication message to obtain the message source address, service type, charging session identifier, metering freeze sequence number and power scheduling effective time, and distinguish cloud platform order message, energy management message and metering message according to the message source address and the service type.

[0032] In this embodiment, after receiving the communication message received after the link is restored, the communication processing unit performs layered parsing on the communication message. Specifically, it first parses the Ethernet frame header, IP header, and transport layer header to obtain the source MAC address, source IP address, source port, destination port, and transport protocol type of the message, and uses at least one of the source MAC address, source IP address, and source port as the message source address.

[0033] The charging pile pre-stores a source address mapping table locally, which includes the cloud platform server address, energy management system address, and metering device address. For example, the IP address and port of the cloud platform server are configured as the first source address group, the IP address and port of the building energy management system or load management controller are configured as the second source address group, and the IP address and port of the MID energy meter, metering gateway, or local metering module are configured as the third source address group. The communication processing unit matches the parsed message source address with the source address mapping table to obtain the source category of the message.

[0034] After determining the message source category, the communication processing unit continues to parse the application layer data fields of the message to obtain the service type. The service type can be determined by the application layer function code, command word, message name, data object identifier, or JSON field name. For example, when the message contains fields for order initiation, order stop, order settlement, transaction confirmation, or bill re-transmission, its service type is identified as order service; when the message contains fields for target power limit, charging current limit, load allocation value, scheduling start time, or scheduling end time, its service type is identified as power scheduling service; when the message contains fields for frozen electricity, frozen time, frozen sequence number, total positive active power, or time-of-use electricity, its service type is identified as metering service.

[0035] Specifically, for communication messages identified as order business, the communication processing unit extracts the order number, transaction number, vehicle connection number or charging gun number from the application layer data of the message, and uses the data that can uniquely represent a charging process as the charging session identifier; if the message contains both the order number and the charging gun number, the order number and the charging gun number are combined to generate the charging session identifier to avoid session confusion when multiple guns on the same charging pile are working.

[0036] For communication messages identified as metering services, the communication processing unit extracts the metering freeze sequence number and the corresponding frozen electricity amount. The metering freeze sequence number can be a freeze serial number uploaded by the electricity meter, a freeze record number, or a sequence number formed by combining the freeze time and the meter address. When the metering message does not directly contain a charging session identifier, the communication processing unit associates the metering freeze sequence number with the corresponding charging session identifier based on the metering device address, charging gun number, and the currently active charging order session.

[0037] For communication messages identified as power scheduling services, the communication processing unit extracts the target power limit and the power scheduling effective time. The power scheduling effective time can be an absolute effective time carried in the message or a delayed effective time relative to the message sending time; when the message carries a delayed effective time, the communication processing unit calculates the power scheduling effective time based on the message receiving time and the delayed effective time.

[0038] In this embodiment, the communication processing unit classifies the communication messages according to the message source address and service type: when the message source address belongs to the first source address group and the service type is order service, the communication message is marked as a cloud platform order message; when the message source address belongs to the second source address group and the service type is power scheduling service, the communication message is marked as an energy management message; when the message source address belongs to the third source address group and the service type is metering service, the communication message is marked as a metering message.

[0039] If there is a discrepancy between the source address and the service type of the message, for example, if the source address belongs to the cloud platform server but the service field is power scheduling service, the communication processing unit will further read the device identifier, digital signature or preset authentication code in the message for secondary confirmation; if the secondary confirmation fails, the communication message will be marked as an abnormal message and temporarily stored, and will not participate in the subsequent message logical sequence generation.

[0040] In this embodiment, the charging pile can accurately obtain the message source address, service type, charging session identifier, metering freeze sequence number and power scheduling effective time from the communication messages received after the link is restored. It can also distinguish messages from different sources and with different service meanings into cloud platform order messages, energy management messages and metering messages, providing a clear data foundation for subsequent link restoration collision identification and message logic rearrangement.

[0041] In this embodiment, the cloud platform order message, energy management message, and metering message can be communication messages carried based on OCPP (Open Charging Point Protocol) or vendor-specific protocols. For example, when using OCPP 1.6, the cloud platform order message can carry messages such as StartTransaction and StopTransaction, and the metering message is reported by the MeterValues ​​message; when using OCPP 2.0.1 or OCPP 2.1, the start, update, and end messages of the transaction are uniformly carried by TransactionEvent (whose event types include Started, Updated, and Ended), and the metering value is embedded in the meterValue field of the TransactionEvent message. Energy management messages can carry the maximum limit or external constraint configurations (such as ChargingStationMaxProfile, ChargingStationExternalConstraints) of charging stations in OCPP 1.6 / 2.0.1 / 2.1's SetChargingProfile and ChargingProfile, as well as power limiting commands directly issued by the energy management system. Metering data can also be local metering frozen data from the electricity meter. The message source / service classification, link recovery collision identification, and message logical rearrangement methods of this invention are not limited by specific protocol types; all communication messages carrying the above-mentioned service semantics are applicable.

[0042] S3. When the link interruption duration is greater than the interruption threshold and the first frame arrival interval is less than the congestion threshold, a link recovery collision flag is generated. The link recovery collision flag is used to indicate that the cloud platform order message, energy management message and metering message are resent in a concentrated manner after the link is restored.

[0043] In this embodiment, after completing the collection and classification of link recovery messages, the communication processing unit determines whether a link recovery collision exists based on the link interruption duration and the first frame arrival interval. The first frame arrival interval refers to the time interval between the first Ethernet frame of each service communication message entering the receiving buffer of the communication processing unit after the link is restored; when the communication message is an application layer message in a TCP data stream, the Ethernet frame containing the start byte of the application layer message is taken as the first frame.

[0044] In this embodiment, the communication processing unit reads the link interruption duration ΔT obtained in step S1 and the classification results of cloud platform order messages, energy management messages, and metering messages obtained in step S2. The communication processing unit traverses the link recovery acquisition buffer according to the message arrival order, searches for the first cloud platform order message, the first energy management message, and the first metering message after the link recovery, and determines the message sequence number range required to cover the above three types of messages. If the above three types of messages are included in a preset number of service communication messages, the maximum first frame arrival interval Dmax within the sequence number range is calculated, for example: Dmax=max(T1-Tup,T2-T1,……,Tk-T(k-1)), where Tup is the link recovery time, T1 to Tk are the first frame arrival times of each service communication message covering the three types of messages, and k is the message sequence number corresponding to the first coverage of cloud platform order messages, energy management messages, and metering messages.

[0045] In this embodiment, the interruption threshold is denoted as Tbreak. This interruption threshold is not arbitrarily set, but determined based on the physical link recovery characteristics and service packet backlog characteristics of the charging pile's on-site network. Specifically, during the charging pile installation and commissioning phase, the time required for multiple ordinary network port jitters or switch port renegotiations can be recorded, and the 95th percentile or maximum value can be taken as the physical recovery reference time Tphy; simultaneously, the minimum value among the cloud platform order packet retransmission cycle, energy management packet distribution cycle, and metering packet upload cycle can be read as the service backlog reference time Tbiz. The interruption threshold can be determined as follows: Tbreak = max(Tphy + Tm, α * Tbiz), where Tm is the anti-jitter margin, which can be taken from 50ms to 500ms, and α is the service backlog coefficient, which can be taken from 0.5 to 1. With this setting, short-term network cable jitter or PHY self-recovery will not be mistakenly judged as a link recovery collision, and when the link failure time is sufficient to cause at least one service packet to be buffered, retransmitted, or resent, further judgment can proceed.

[0046] Herein, the congestion threshold is denoted as Tcrowd, which is used to determine whether multi-source messages belong to centralized arrival after link recovery. This threshold is determined based on the arrival interval between service messages under normal communication conditions and the local message enqueuing processing capability of the charging pile. Specifically, the communication processing unit may count the arrival interval between adjacent service messages within a preset time under a normal networked state to obtain the normal minimum service interval Tnormal; at the same time, the maximum processing time Tproc required for the communication processing unit to receive, identify and enqueue one service message is obtained through local testing. The congestion threshold may be determined as follows: Tcrowd=max(2*Tproc, β*Tnormal), where β may take a value from 0.05 to 0.2. This design makes Tcrowd greater than the device's own normal enqueuing processing time, avoiding misjudgment caused by processing delay; at the same time, it is significantly smaller than the normal service message interval, so that only messages that are centrally retransmitted after link recovery will meet the congestion condition. For example, the arrival intervals of cloud platform order messages, energy management messages and metering messages in the normal state are usually on the order of seconds, while the retransmitted messages after link recovery may arrive continuously within tens of milliseconds, so the above threshold can effectively distinguish normal communication and burst retransmission after recovery.

[0047] When the communication processing unit determines that ΔT>Tbreak and the Dmax<Tcrowd, it is determined that the link disconnection time is sufficient to cause service message backlog, and after link recovery, the three types of service messages centrally enter the charging pile receiving buffer within a very short time, at this time, a link recovery collision identifier is generated. The link recovery collision identifier may include a collision flag bit, a link recovery moment, a link interruption duration, a bitmap of three message types, a first frame arrival interval set covering the three types of messages, and a corresponding charging session identifier. For example, when the cloud platform order message, energy management message and metering message are all identified in the recovery acquisition buffer, the bitmap of the three message types is set to "111" to represent that all three types of messages participate in this link recovery collision.

[0048] Herein, if ΔT≤Tbreak, it indicates that the link disconnection is closer to ordinary physical jitter or instantaneous reconnection, and the communication processing unit does not generate a link recovery collision identifier; If ΔT>Tbreak but Dmax≥Tcrowd, it indicates that although a link disconnection has occurred, the messages after recovery are not centrally retransmitted, but arrive successively at the normal service pace, and no link recovery collision identifier is generated either.

[0049] Accordingly, this embodiment can avoid misjudgment caused by relying solely on a link disconnection event or solely on dense message arrival, so that the link recovery collision identifier accurately represents that the cloud platform order messages, energy management messages and metering messages are centrally retransmitted after link recovery, providing a reliable trigger condition for subsequent logical rearrangement of messages.

[0050] S4. Based on the link recovery collision identifier, write communication messages with the same charging session identifier into a temporary interaction queue, and generate a message logical order based on the metering freeze sequence number and the power scheduling effective time.

[0051] In this embodiment, step S4 is executed after the link recovery collision identifier is generated in step S3. The charging pile's communication processing program reads the link recovery time, link interruption duration, and three types of message type bitmaps from the link recovery collision identifier, and uses the link recovery time as the basis for queue generation to establish a temporary interaction queue that corresponds only to this link recovery collision. The temporary interaction queue includes a queue identifier, a charging session identifier, an order message area, an energy management message area, a metering message area, an arrival offset field, a scheduling insertion bit field, and a logical processing number field. The queue identifier is generated by combining the link recovery time and the charging pile number, and is used to isolate the message generated by this link interruption recovery from messages received at other times.

[0052] The collection scope for this link recovery refers to the range of messages received from the moment the link is restored until a preset number of N service communication messages are collected, or until a preset collection duration Tc is reached. The preset number N is determined based on the coverage requirements of three types of messages: cloud platform order messages, energy management messages, and metering messages. N is not less than 6, ensuring that each type of message has at least one opportunity to be collected, and allowing for duplicate retransmissions after link restoration. The preset collection duration Tc is determined based on the maximum transmission period of the three types of messages under normal communication conditions, taking 1 to 1.5 times the maximum transmission period, ensuring that the collection scope covers the concentrated retransmissions after link restoration, while preventing subsequent normal cycle messages from being merged into this temporary interaction queue.

[0053] The communication processing program reads communication packets within the current link recovery collection range according to the arrival order of the first frame, and extracts the packet source address, service type, charging session identifier, metering freeze sequence number, and power scheduling effective time obtained in step S2. Subsequently, the charging session identifier of each communication packet is compared with the charging session identifier currently being executed by the charging pile. The currently executing charging session identifier is the session identifier saved by the charging pile after the vehicle is plugged in and charging begins. If the two match, the communication packet is allowed to enter the temporary interaction queue; if they do not match, the communication packet is not written to the temporary interaction queue to prevent resend packets from other vehicles or other charging guns from being mixed into the current charging session.

[0054] Upon successful matching, the communication processing program writes the communication message to the corresponding queue position according to the service type: cloud platform order messages are written to the order message area, energy management messages to the energy management message area, and metering messages to the metering message area. Simultaneously, the difference between the arrival time of the first frame of the communication message and the link recovery time is recorded as the arrival offset of the communication message. This arrival offset is only used to preserve the actual receiving order of the retransmission of messages after link recovery and is not directly used as the service execution order.

[0055] When all bits corresponding to cloud platform order messages, energy management messages, and metering messages in the three message type bitmaps are valid, and all three types of messages have been written to the same temporary interaction queue, the communication processing program marks the temporary interaction queue as locked. After locking, communication messages with different charging session identifiers are prohibited from being inserted into this temporary interaction queue; subsequent communication messages with the same charging session identifier are appended to the corresponding message area only if their first frame arrival time falls within the current link recovery acquisition range. Communication messages outside the current link recovery acquisition range are processed according to the normal communication process and do not participate in the generation of the current message logical order.

[0056] After the temporary interactive queue is locked, the communication processing program reads the metering freeze number from the metering message area and generates a session metering sequence number axis according to the increasing direction of the metering freeze number. The session metering sequence number axis is composed of valid metering freeze numbers. If the current metering freeze number is the same as the metering freeze number already written into the session metering sequence number axis, or if the current metering freeze number is less than the previous valid metering freeze number, then the current metering freeze number is marked as a reissue number. The metering message marked as a reissue number is retained in the metering message area for subsequent verification, but is not used as the endpoint of a new metering freeze interval.

[0057] Within this system, a metering freeze interval is formed between two adjacent valid metering freeze sequence numbers. To ensure that the power scheduling effective time corresponds to the session metering sequence number axis, the communication processing program reads the freeze generation time from the metering message. When the metering message does not carry a freeze generation time, the communication processing program uses the arrival time of the first frame of the metering message minus the arrival offset correction value as the alternative freeze generation time for that metering freeze sequence number. The arrival offset correction value is taken as the minimum arrival offset of the metering messages in this temporary interaction queue, used to offset the overall reception delay caused by centralized retransmission after link recovery, ensuring that the order of each metering freeze sequence number is still based on the increasing direction of the metering freeze sequence number.

[0058] The communication processing program reads the power scheduling effective time from the energy management message area and anchors the power scheduling effective time to the session metering sequence number axis. Specifically, when the power scheduling effective time is not later than the freezing generation time of the first valid metering freeze number, a scheduling insertion bit is generated before the first valid metering freeze number; when the power scheduling effective time is later than the freezing generation time of the m-th valid metering freeze number, but not later than the freezing generation time of the (m+1)-th valid metering freeze number, a scheduling insertion bit is generated between the m-th and (m+1)-th valid metering freeze numbers; when the power scheduling effective time is later than the freezing generation time of the last valid metering freeze number, a scheduling insertion bit is generated after the last valid metering freeze number, where m is a positive integer.

[0059] After generating the scheduling insertion bit, the communication processing program reassigns logical processing numbers to cloud platform order messages, energy management messages, and metering messages in the temporary interaction queue. The logical processing numbers represent the message logical order in ascending order. Specifically, metering messages are assigned basic logical processing numbers sequentially according to the session metering sequence number axis; energy management messages are inserted into the corresponding metering freeze interval according to their scheduling insertion bit and assigned a logical processing number located after the previous valid metering freeze sequence number and before the next valid metering freeze sequence number; settlement-related messages in cloud platform order messages are placed after energy management messages within the same metering freeze interval. For initiation or status confirmation order messages, if they do not involve settlement electricity confirmation, they are retained in the order message area according to their charging session identifier and arrival offset, without blocking the generation of logical processing numbers for energy management messages.

[0060] For example, if the temporary interaction queue contains metering freeze numbers 1001, 1002, and 1003, and the power scheduling effective time falls between the freeze times corresponding to metering freeze numbers 1001 and 1002, and there are settlement order messages for the same charging session identifier, then the communication processing program will prioritize the metering message corresponding to metering freeze number 1001, insert the energy management message between metering freeze numbers 1001 and 1002, and prioritize the settlement order message after the energy management message. Therefore, even if the settlement order message arrives before the energy management message after the link is restored, the business logic order can still be restored based on the metering freeze number and the power scheduling effective time.

[0061] Finally, the communication processing program writes the generated message logical order back to the temporary interaction queue and provides the temporary interaction queue for use in the subsequent step S5. Through the above processing, the temporary interaction queue only contains cloud platform order messages, energy management messages, and metering messages involved in this link recovery collision under the same charging session identifier; at the same time, the message logical order no longer simply depends on the order of message arrival, but is generated by combining the metering freeze sequence number and the power scheduling effective time, thereby reducing the risk of power scheduling delay and settlement metering mismatch caused by centralized retransmission after link recovery.

[0062] S5. When the effective time of the power scheduling message, which is represented by the message logical sequence, is earlier than the processing time of the order status message, a data interaction state is generated. The data interaction state includes the target limit power, the benchmark metering value, the pending order status, and the interaction lock code. Based on the interaction lock code, the processing of settlement messages related to the pending order status is suspended, and the target limit power is sent to the charging control module so that the charging pile outputs according to the target limit power.

[0063] In this embodiment, step S5 is executed after step S4 generates the message logical order and writes it back to the temporary interaction queue. The communication processing program reads the logical processing number of each communication message in the temporary interaction queue and identifies the power scheduling message in the energy management message, the order status message in the cloud platform order message, and the settlement message. The power scheduling message is an energy management message that includes the target power limit and the power scheduling effective time; the order status message is a cloud platform order message that includes the order completion status, pending settlement status, settlement confirmation status, or transaction closed status; the settlement message is a cloud platform order message that includes the settlement electricity, settlement amount, end electricity, or transaction completion confirmation fields.

[0064] In this embodiment, the processing time of the order status message does not refer to the actual arrival time of the order status message, but rather to the logical processing order corresponding to the logical processing number assigned to the order status message in step S4. When the logical processing number of the power scheduling message is less than the logical processing number of the order status message, or when the scheduling insertion bit of the power scheduling message is located before the metering freeze interval to which the order status message belongs, the message logical order indicates that the effective time of the power scheduling message is earlier than the processing time of the order status message.

[0065] When the above conditions are met, the communication processing program generates a data interaction state. This data interaction state includes the target power limit, baseline metering value, pending order status, and interaction lock code, and is bound to the queue identifier of the current temporary interaction queue and the current charging session identifier. This data interaction state indicates that in this link recovery collision, the power scheduling message should be executed before the order status message involving settlement confirmation.

[0066] The communication processing program extracts the target power limit from the power scheduling messages. If multiple power scheduling messages exist in the same temporary interaction queue, the message with the smallest logical processing number is selected as the valid scheduling message according to the message logical order. If multiple power scheduling messages have the same logical processing number, the message with the earliest power scheduling effective time is selected as the valid scheduling message. If the power scheduling effective times are still the same, the message with the smallest target power limit value is selected as the valid scheduling message. This order determination method can avoid the problem of uncertain power limit targets when multiple power limiting commands are resent simultaneously after link recovery.

[0067] The communication processing program determines the baseline metering value based on the scheduling insertion bit of the valid scheduling message. Specifically, when the scheduling insertion bit is located between two adjacent valid metering freeze numbers, the frozen electricity corresponding to the valid metering freeze number closest to the scheduling insertion bit is used as the baseline metering value; when the scheduling insertion bit is located before the first valid metering freeze number, the initial electricity saved at the start of the current charging session is used as the baseline metering value; when the scheduling insertion bit is located after the last valid metering freeze number, the frozen electricity corresponding to the last valid metering freeze number is used as the baseline metering value. The baseline metering value is used as the metering boundary for subsequently judging changes in electricity consumption during power scheduling execution.

[0068] The communication processing program extracts the pending order status from the order status message and binds the pending order status to the current charging session identifier. The pending order status includes pending settlement, ended pending confirmation, or settlement confirmed status. The communication processing program further searches the temporary interaction queue for settlement messages related to the pending order status. The correlation is determined by matching order numbers, matching charging session identifiers, and the service type belonging to settlement services.

[0069] The interaction lock code is calculated by concatenating the queue identifier, current charging session identifier, logical processing number of valid scheduling message, target limit power, metering freeze sequence number corresponding to the benchmark metering value, and pending order status in a fixed order. The calculation method can employ one-way hash algorithms such as CRC32 or SHA-256, or message authentication algorithms such as HMAC or HMAC-SHA256. For example, a 32-bit interaction lock code can be obtained using CRC32 verification. When the link is a wireless network such as WiFi or mobile communication, requiring stronger anti-tampering capabilities, the interaction lock code can be calculated using HMAC-SHA256. Since the fields involved in the calculation simultaneously include the current link recovery collision, current charging session, power scheduling location, and metering boundary, the interaction lock code can uniquely identify the current data interaction status.

[0070] After generating the interaction lock code, the communication processing program suspends processing of settlement messages related to the pending order status based on the interaction lock code. Specifically, the suspension involves: storing the settlement message in the lock sub-area of ​​the order message area; writing the interaction lock code into the data record of the settlement message; and prohibiting the generation of settlement electricity confirmation, fee confirmation, order end response, or transaction closure confirmation based on the settlement message. For order query messages, heartbeat messages, or status read messages that do not involve settlement electricity confirmation, no lock sub-area is written, and responses are still processed according to the normal procedure.

[0071] After pausing the settlement message processing, the communication processing program sends the target power limit to the charging control module. The sent content includes the current charging session identifier, charging gun number, target power limit, power scheduling effective time, baseline metering value, and interaction lock code. Upon receiving the data, the charging control module first compares the currently executing charging session identifier with the current charging session identifier in the sent content. If they match, the target power limit is accepted; if they do not match, the communication control module reports the session inconsistency result to the communication processing program. The communication processing program maintains the paused processing state of the settlement message and records the session inconsistency result.

[0072] When the session identifiers match, the charging control module adjusts the charging output according to the target power limit. For AC charging piles, the charging control module calculates the allowable output current based on the target power limit and the current output voltage, and adjusts the allowable current value corresponding to the control guidance signal. For DC charging piles, the charging control module generates a corresponding output voltage limit or output current limit value based on the target power limit, and causes the charging pile to output according to the output voltage limit or output current limit value. After executing the power limit, the charging control module binds and saves the interaction lock code with this power limit action, so that the actual output power obtained in subsequent steps S6 can correspond to the current data interaction state.

[0073] In this embodiment, even if the settlement message arrives before the power scheduling message after the link is restored, the charging pile can still execute the target power limit that has already taken effect based on the message logical order, and use the benchmark metering value as the subsequent verification boundary to avoid delayed power limit response, early order settlement and metering data mismatch caused by concentrated resending of messages.

[0074] S6. Obtain the actual output power and the next metering freeze value fed back by the charging control module, and verify the data interaction status based on the actual output power and the benchmark metering value; if the verification is successful, release the interaction lock code, and generate an order response message and a power scheduling response message based on the next metering freeze value, and send them to the corresponding source address via the network communication interface to complete the charging pile communication data interaction.

[0075] In this embodiment, step S6 is executed after generating the data interaction state and sending the target power limit in step S5. The communication processing program receives the actual output power fed back after power limiting is performed in step S5, based on the interaction lock code in the data interaction state. The actual output power carries the current charging session identifier, sampling time, and interaction lock code. The communication processing program first compares the interaction lock code in the feedback data with the interaction lock code in the data interaction state; if they do not match, the actual output power is not included in this verification; if they match, the current charging session identifier is compared again, and only when both the interaction lock code and the current charging session identifier match is the actual output power written into the power recording area corresponding to this data interaction state.

[0076] The communication processing program reads the power scheduling effective time from the data interaction status and determines the next metering freeze value. The next metering freeze value is the first valid frozen electricity quantity generated after the baseline metering value and whose metering freeze sequence number is greater than the metering freeze sequence number corresponding to the baseline metering value. If the metering freeze sequence number corresponding to the received metering freeze value is the same as or less than the metering freeze sequence number corresponding to the baseline metering value, then this metering freeze value is marked as a supplementary freeze value and is not used as the next metering freeze value. This method ensures that the metering data used for verification is located after the power scheduling execution.

[0077] Specifically, the time for generating the next metering freeze value is preferentially adopted from the freeze generation time carried in the metering message. If the metering message does not carry a freeze generation time, the alternative freeze generation time is obtained by subtracting the minimum arrival offset of metering messages in the current temporary interaction queue from the arrival time of the first frame of the metering message. This process is consistent with the time correction method of the session metering sequence number axis in step S4, and is used to reduce the impact of the reception delay caused by the centralized retransmission after link recovery on the verification interval.

[0078] After determining the time when the next metering freeze value will be generated, the communication processing program extracts the actual output power between the power scheduling effective time and the time when the next metering freeze value will be generated, forming a locked power sequence. The locked power sequence includes multiple actual output powers and corresponding sampling times. The sampling period is denoted as Ts, which is determined based on the maximum response time Tr required for the charging pile to execute power limiting and the metering freeze interval Tf, satisfying the following values: Ts ≤ Tr / 2, and Tf / Ts ≥ 10. Tr can be obtained during factory testing or on-site debugging by sending power limiting commands and recording the maximum time required for the output power to reach the target limit power; Tf is the sending interval of the metering freeze message or the local freeze interval. Using the above value method ensures that each metering freeze interval has no fewer than 10 power sampling values, while also capturing short-term over-limit phenomena in the initial stage of power limiting execution.

[0079] The communication processing program calculates the locked power increment based on the baseline metering value and the next metering freeze value, using the formula: ΔE1 = Enext - Ebase; where Enext is the next metering freeze value and Ebase is the baseline metering value. Subsequently, it calculates the power integral based on the locked power sequence, using the formula: ΔE2 = ΣPi × Δti / 3600; where Pi is the i-th actual output power, and Δti is the time interval between the i-th sampled value and the next sampled value, in seconds. When the time interval between adjacent sampling moments is equal to Ts, Δti is taken as Ts; when there are unequal sampling intervals, Δti is taken as the actual difference between adjacent sampling moments. ΔE1 and ΔE2 use the same power unit.

[0080] The communication processing program compares the difference between the locked power increment ΔE1 and the power integral power ΔE2 to obtain the metering power deviation value δ, calculated as: δ = |ΔE1 - ΔE2|. The allowable deviation range is denoted as δmax, which is determined based on the metering error and power sampling error, calculated as: δmax = Eacc + Pacc × Δt / 3600; where Eacc is the maximum allowable metering error of the metering device within the current freeze interval, Pacc is the maximum allowable error of the actual output power sampling, and Δt is the duration between the power scheduling effective time and the time when the next metering freeze value is generated. Eacc can be determined based on the nominal accuracy class of the metering device and the power volume in the current freeze interval, while Pacc can be determined based on the charging pile power sampling accuracy or calibration records. This allowable deviation range covers normal measurement errors and sampling errors, but does not cover large power deviations caused by order mismatches or misuse of metering freeze values.

[0081] The communication processing program further determines whether the actual output power in the locked power sequence meets the power limit requirements. Specifically, each actual output power Pi is compared with the target limit power Plimit; when each Pi is not greater than Plimit + Pacc, and the metered power deviation value δ is not greater than δmax, the data interaction status verification is deemed successful. If any Pi is greater than Plimit + Pacc, or δ is greater than δmax, the data interaction status verification is deemed unsuccessful.

[0082] If the verification fails, the communication processing program keeps the interactive lock code valid, continues to suspend processing of settlement messages related to the pending order status, and generates an exception record. The exception record includes the current charging session identifier, interactive lock code, target power limit, maximum actual output power, reference metering value, next metering freeze value, and metering power deviation value. This exception record is used to prevent unverified settlement messages from being released prematurely.

[0083] If the verification passes, the communication processing program releases the interaction lock code. The release process includes: restoring the settlement message carrying the interaction lock code in the locked sub-area of ​​the order message area to a processable state, marking the data interaction status as verified, and removing the pause restriction on the pending order status imposed by the interaction lock code. Subsequently, the communication processing program generates an order response message based on the next metering freeze value. The order response message includes the current charging session identifier, order number, next metering freeze value, settlement permission identifier, and interaction lock code release result.

[0084] In addition, the communication processing program generates a power scheduling response message, which includes the current charging session identifier, target limit power, maximum actual output power in the locked power sequence, power scheduling execution result, and metering power deviation value. Finally, based on the message source address obtained in step S2, the communication processing program sends the order response message to the corresponding source address of the cloud platform order message via the network communication interface, and sends the power scheduling response message to the corresponding source address of the energy management message via the network communication interface. This completes the charging pile communication data interaction in the link recovery collision scenario.

[0085] Example 2, please refer to Figure 2 As shown in the figure, the charging pile communication data interaction system supporting network communication interface described in this embodiment includes: Link status monitoring module: acquires link status change information of the charging pile network communication interface, and when the network communication interface is detected to recover from disconnection to connection, records the link interruption duration and collects the first frame arrival interval of a preset number of communication messages after recovery. Communication message parsing module: Parses the communication message to obtain the message source address, service type, charging session identifier, metering freeze sequence number and power scheduling effective time, and distinguishes cloud platform order message, energy management message and metering message according to the message source address and the service type; Link recovery collision identification module: When the link interruption duration is greater than the interruption threshold and the first frame arrival interval is less than the congestion threshold, a link recovery collision identifier is generated; Temporary interaction queue generation module: Based on the link recovery collision identifier, it writes communication messages with the same charging session identifier into the temporary interaction queue, and generates a message logical order based on the metering freeze sequence number and the power scheduling effective time; Data interaction status control module: When the effective time of the power scheduling message, which represents the message logical sequence, is earlier than the processing time of the order status message, a data interaction status is generated. The data interaction status includes the target limit power, the benchmark metering value, the pending order status, and the interaction lock code. Based on the interaction lock code, the processing of settlement messages related to the pending order status is suspended, and the target limit power is sent to the charging control module so that the charging pile outputs according to the target limit power. Interactive verification response module: Obtains the actual output power and the next metering freeze value fed back by the charging control module, verifies the data interaction status based on the actual output power and the benchmark metering value; if the verification passes, releases the interactive lock code, and generates an order response message and a power scheduling response message based on the next metering freeze value, and sends them to the corresponding source address via the network communication interface to complete the charging pile communication data interaction.

[0086] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A method for communication data interaction of charging piles supporting network communication interfaces, characterized in that, include: Obtain link status change information of the charging pile network communication interface; when the network communication interface is detected to recover from disconnection to connection, record the link interruption duration and collect the first frame arrival interval of a preset number of communication messages after recovery. The communication message is parsed to obtain the message source address, service type, charging session identifier, metering freeze sequence number and power scheduling effective time, and the cloud platform order message, energy management message and metering message are distinguished according to the message source address and the service type. If the link interruption duration is greater than the interruption threshold and the first frame arrival interval is less than the congestion threshold, a link recovery collision flag is generated. According to the link recovery collision identifier, communication messages with the same charging session identifier are written into a temporary interaction queue, and a logical order of messages is generated based on the metering freeze sequence number and the power scheduling effective time. When the message logical sequence indicates that the effective time of the power scheduling message is earlier than the processing time of the order status message, a data interaction status is generated. The data interaction status includes the target limit power, the reference metering value, the order status to be confirmed, and the interaction lock code. The processing of settlement messages related to the pending order status is paused according to the interactive lock code, and the target power limit is sent to the charging control module so that the charging pile outputs according to the target power limit. Obtain the actual output power and the next metering freeze value fed back by the charging control module, and verify the data interaction status based on the actual output power and the benchmark metering value; If the verification passes, the interaction lock code is released, and an order response message and a power scheduling response message are generated based on the next metering freeze value. These messages are then sent to the corresponding source addresses via the network communication interface to complete the charging pile communication data interaction.

2. The charging pile communication data interaction method supporting network communication interface according to claim 1, characterized in that, The link recovery collision identifier is used to indicate that the cloud platform order messages, energy management messages and metering messages are centrally resent after the link is restored.

3. The charging pile communication data interaction method supporting network communication interface according to claim 1, characterized in that, Generate link recovery collision flags, including: The interruption threshold is determined based on the normal link jitter recovery time and the service packet backlog time, and the congestion threshold is determined based on the normal service packet arrival interval and the single service packet enqueue processing time. When the duration of the link interruption exceeds the interruption threshold, determine whether the preset number of communication messages after the link is restored simultaneously contain cloud platform order messages, energy management messages, and metering messages; If the cloud platform order message, energy management message, and metering message are included simultaneously, and the maximum first frame arrival interval covering the three types of messages is less than the congestion threshold, then a link recovery collision identifier is generated that includes the link recovery time, the link interruption duration, and a bitmap of the three types of messages.

4. The charging pile communication data interaction method supporting network communication interface according to claim 3, characterized in that, Communication messages with the same charging session identifier are written to a temporary interaction queue, including: Read the link recovery time and the bitmap of the three types of messages in the link recovery collision identifier, and generate a temporary interaction queue that corresponds only to this link recovery collision based on the link recovery time; The charging session identifier of the communication messages within the link recovery collection range is compared with the currently executing charging session identifier. If the comparison is consistent, the communication messages are written into the order message area, energy management message area, or metering message area of ​​the temporary interaction queue according to the service type, and the arrival offset of the corresponding communication message relative to the link recovery time is recorded.

5. The charging pile communication data interaction method supporting network communication interface according to claim 4, characterized in that, Writing to the temporary interactive queue also includes: When the cloud platform order message, energy management message and metering message corresponding to the three message type bitmaps have all been written into the same temporary interaction queue, the temporary interaction queue is marked as locked. In the locked state, communication messages with different charging session identifiers are prohibited from being inserted into the temporary interaction queue. For communication messages with the same charging session identifier but outside the link recovery collection range, they are processed according to the normal communication process so that they do not participate in the generation of the current message logical order.

6. The charging pile communication data interaction method supporting network communication interface according to claim 1, characterized in that, The message logical sequence is generated based on the metering freeze sequence number and the power scheduling effective time, including: Read the metering freeze sequence number in the metering message area, generate the session metering sequence number axis according to the increasing direction of the metering freeze sequence number, and mark the duplicate or backward metering freeze sequence number as the reissue sequence number; The power scheduling effective time in the energy management message is anchored to the session metering sequence number axis, and a scheduling insertion bit is generated between two adjacent valid metering freeze sequences, before the first valid metering freeze sequence number, or after the last valid metering freeze sequence number. The cloud platform order message, energy management message, and metering message are assigned logical processing numbers based on the scheduling insertion bit, and the settlement order message is arranged after the energy management message in the same metering freeze interval.

7. The charging pile communication data interaction method supporting network communication interface according to claim 6, characterized in that, Generate data interaction states, including: When the logical processing number of the power scheduling message is less than the logical processing number of the order status message, a valid scheduling message is determined from the power scheduling message, and the target limited power is extracted. Based on the scheduling insertion bit of the valid scheduling message, the frozen electricity corresponding to the valid metering freeze sequence number that is closest to and before the scheduling insertion bit is selected as the benchmark metering value. The target power limit, the reference meter value, and the pending order status extracted from the order status message are bound to the current charging session identifier to generate the data interaction status.

8. The charging pile communication data interaction method supporting network communication interface according to claim 1, characterized in that, The processing of settlement messages related to the pending order status is suspended based on the interaction lock code, including: The interaction lock code is calculated by concatenating the queue identifier of the temporary interaction queue, the current charging session identifier, the logical processing number of the valid scheduling message, the target limit power, the metering freeze sequence number corresponding to the benchmark metering value, and the status of the pending order in a fixed order. Write the settlement message related to the status of the order to be confirmed into the locked sub-area of ​​the order message area, and write the interaction lock code into the data record of the settlement message; Before the interactive lock code is released, it is prohibited to generate settlement electricity confirmation, fee confirmation, order end response or transaction closure confirmation based on the settlement message.

9. The charging pile communication data interaction method supporting network communication interface according to claim 8, characterized in that, Verifying the data interaction status based on the actual output power and the reference measurement value includes: The actual output power is received based on the interactive locking code, and the actual output power between the power scheduling effective time and the time when the next metering freeze value is generated is extracted to form a locked power sequence. The locked power increment is calculated based on the next metering freeze value and the benchmark metering value, and the power integral power is calculated based on the locked power sequence. The difference between the locked power increment and the power integral power is compared to obtain the metered power deviation value. When the actual output power does not exceed the target limit power and the metered power deviation value is within the allowable deviation range, the interactive lock code is released, and an order response message and a power scheduling response message are generated.

10. A charging pile communication data interaction system supporting a network communication interface, used to implement the charging pile communication data interaction method supporting a network communication interface as described in any one of claims 1-9, characterized in that, include: The module includes a link status monitoring module, a communication message parsing module, a link recovery collision identification module, a temporary interaction queue generation module, a data interaction status control module, and an interaction verification response module.

Images