Cooperative management method for double communication links of charging pile

Abstract

This invention discloses a collaborative management method for dual communication links of charging piles, comprising: configuring a first communication link and a second communication link, wherein the first communication link defaults to carrying operational services and the second communication link defaults to carrying maintenance services; collecting communication quality parameters in the two communication links, and calculating the health score of the first communication link and the health score of the second communication link based on the communication quality parameters; when the health score of either communication link is lower than a first threshold, switching the services carried by that communication link to the other communication link, storing the service data generated by the charging pile during the link switching, and recording the data breakpoint; after a successful switch, retransmitting the service data after the data breakpoint to the corresponding platform, wherein the retransmitted data carries an identifier for deduplication verification.

Description

Technical Field

[0001] This invention relates to the field of charging pile technology, and in particular to a method for collaborative management of dual communication links in charging piles. Background Technology

[0002] Charging piles need to maintain a real-time connection with the operation platform via a wireless communication network to complete tasks such as starting charging, stopping charging, order metering, billing and settlement, status reporting, and remote control. Some charging pile devices are equipped with dual 4G communication modules or dual SIM cards, but in existing solutions, the two communication links usually adopt a fixed division of labor—one link is fixed to carry the operation platform's business, and the other link is fixed to carry the maintenance platform's business. The two links operate independently and lack a unified collaborative scheduling mechanism.

[0003] The existing solutions have the following shortcomings: First, if the communication link carrying the operational business experiences an anomaly—whether it's a module failure, SIM card malfunction, operator network problem, platform address change, or certificate expiration—the charging pile is prone to communication interruption. This results in users being unable to start charging, ongoing charging orders being forced to stop, metering data failing to be reported, and remote control commands failing to be issued, directly impacting the availability of the charging service. Second, when a link anomaly necessitates a switchover, the existing solutions only focus on network reconnection, lacking local caching, retransmission, and deduplication confirmation mechanisms for charging orders, metering records, and settlement data. Metering data being uploaded during the switchover process is easily lost, leading to incomplete billing data on the platform side; confirmed data may also be uploaded repeatedly, causing duplicate billing or inconsistencies between the platform and device status.

[0004] In summary, the existing dual-communication link solution for charging piles, due to its fixed division of labor and lack of coordination, cannot effectively guarantee business continuity and data accuracy when communication is abnormal. Summary of the Invention

[0005] This invention proposes a dual-communication link collaborative management method for charging piles, comprising: Configure a first communication link and a second communication link, wherein the first communication link carries operational services by default, and the second communication link carries maintenance services by default; The communication quality parameters of the two communication links are collected, and the health score of the first communication link and the health score of the second communication link are calculated based on the communication quality parameters. When the health score of any communication link falls below the first threshold, the service carried by that communication link is switched to another communication link, and the service data generated by the charging pile during the link switching is stored, and the data breakpoint is recorded. After a successful switch, the business data from the data breakpoint is retransmitted to the corresponding platform. The retransmitted data carries an identifier for deduplication verification.

[0006] Optionally, the step of calculating the health score of the first communication link and the health score of the second communication link respectively includes: When the health score of any communication link is greater than the first threshold and lower than the second threshold for a preset number of sampling periods, a connection to the platform corresponding to that communication link is established through another communication link.

[0007] Optionally, the dual communication link collaborative management method for charging piles further includes: If the health score of any communication link is greater than the first threshold and lower than the second threshold for a preset number of sampling periods, and the health score rises to be greater than the second threshold, and the duration of the health score being greater than the second threshold is greater than a preset duration, then the communication link is switched back.

[0008] Optionally, the step of calculating the health score of the first communication link and the health score of the second communication link respectively includes: When any of the following events occurs on any communication link: physical connection interruption, no response from the 4G module, or M consecutive failures of the platform heartbeat, the service carried by that communication link is immediately switched to another communication link, and the service data generated by the charging pile during the link switching is stored, and the data breakpoint is recorded; where M is a preset positive integer.

[0009] Optionally, the dual-communication collaborative management method for charging piles further includes: The business is divided into real-time control business, billing key data business, keep-alive and status reporting business, and batch data transmission business. When the health score of any communication link falls below a first threshold, the service carried by that communication link is switched to another communication link, including: If the health score of the first communication link is lower than the first threshold, the second communication link is used to establish a connection with the operation platform, and the real-time control operation business and the billing key data operation business are switched to the second communication link for uploading, while the operation and maintenance business of suspension or rate limit keep-alive and status reporting is suspended. If the health score of the second communication link is lower than the first threshold, the first communication link is used to establish a connection with the operation and maintenance platform, and real-time control operation and maintenance services and / or billing critical data operation and maintenance services are switched to the first communication link for uploading.

[0010] Optionally, real-time control functions include: starting charging, stopping charging, emergency stop, remote control command confirmation, and order key status confirmation; Key billing data includes: order metering records, charging status, billing settlement, payment results, and critical alarms; Keep-alive and status reporting services include: general status reporting, periodic heartbeat, device parameters, non-emergency alarms, and operation and maintenance command results; Batch data transfer services include: log files, diagnostic packages, historical data retransmission, firmware upgrade package download, and file upload.

[0011] Optionally, the service data generated by the charging pile during the storage link switchover, recording data breakpoints, includes: Based on the business data generated by charging piles during link switching, maintain the order cache table, metering flow table, instruction confirmation table, and retransmission team list; When a link switch occurs, record the last sequence number confirmed by the corresponding platform and use the last sequence number as the data breakpoint. The process of retransmitting the business data after the data breakpoint to the corresponding platform includes: Send an order status snapshot to the corresponding platform; Receive missing transaction interval information sent by the platform based on the order status snapshot; The service data is retransmitted in the order of the sequence number in the missing sequence interval information.

[0012] Optionally, the dual communication link collaborative management method for charging piles further includes: Collect radio frequency parameters and transmission status parameters of the two communication links; When it is determined, based on the radio frequency parameters and transmission status parameters, that there is a risk of mutual interference between two communication links, at least one of the following anti-interference operations shall be performed: Perform time-sharing transmission scheduling on non-real-time services on at least one communication link to stagger the services on different communication links in time. Adjust the transmission power of at least one communication link; Control the two communication links to prevent them from performing batch data transmission tasks simultaneously.

[0013] Optionally, the dual communication link collaborative management method for charging piles further includes: Maintain the resource status information of the traffic tariff accounts corresponding to the two communication links respectively; The resource pressure value for each traffic tariff account is determined based on the resource status information. When the resource pressure value of any traffic tariff account exceeds the preset pressure threshold, the non-real-time services on that communication link are rerouted to another communication link for transmission.

[0014] Optionally, the dual communication link collaborative management method for charging piles further includes: Receive configuration update instructions from the operation and maintenance platform through the currently available communication link. The configuration update instructions contain the connection configuration information of the target platform. The configuration update command is subject to security verification. After successful verification, the connection configuration information is stored in a non-currently active configuration storage area; Using the currently available communication link, perform a connection reachability verification on the target platform based on the connection configuration information; When the connection reachability verification meets the preset pass conditions within the preset verification window, the current running configuration is adjusted based on the connection configuration information. The configuration is rolled back when the connection reachability verification fails or a connection anomaly occurs within a preset rollback window starting from when the connection configuration information takes effect. Attached Figure Description

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

[0016] Figure 1 This is a schematic diagram of the steps in the first embodiment of the charging pile dual communication link collaborative management method of the present invention.

[0017] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0018] 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 a part of the embodiments of the present invention, and not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0019] It should be noted that all directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present invention are only used to explain the relative positional relationship and movement of each component in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indication will also change accordingly.

[0020] In this invention, unless otherwise explicitly specified and limited, the terms "connection," "fixed," etc., should be interpreted broadly. For example, "fixed" can mean a fixed connection, a detachable connection, or an integral part; it can mean a mechanical connection or an electrical connection; it can mean a direct connection or an indirect connection through an intermediate medium; it can mean the internal communication of two components or the interaction between two components, unless otherwise explicitly limited. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0021] Furthermore, in this invention, descriptions involving "first," "second," etc., are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of that feature. Additionally, the technical solutions of the various embodiments can be combined with each other, but only on the basis of being achievable by those skilled in the art. When the combination of technical solutions is contradictory or impossible to implement, such a combination of technical solutions should be considered non-existent and not within the scope of protection claimed by this invention.

[0022] like Figure 1 As shown, this invention proposes a dual-communication link collaborative management method for charging piles, comprising: Configure a first communication link and a second communication link, wherein the first communication link carries operational services by default, and the second communication link carries maintenance services by default; The communication quality parameters of the two communication links are collected, and the health score of the first communication link and the health score of the second communication link are calculated based on the communication quality parameters. When the health score of any communication link falls below the first threshold, the service carried by that communication link is switched to another communication link, and the service data generated by the charging pile during the link switching is stored, and the data breakpoint is recorded. After a successful switch, the business data from the data breakpoint is retransmitted to the corresponding platform. The retransmitted data carries an identifier for deduplication verification.

[0023] It's important to clarify that a communication link refers to the logical channel for data communication between the charging pile and an external platform. Each communication link consists of a physical layer communication module (such as a 4G module) and a communication card (such as a SIM card or eSIM). The communication module is responsible for signal transmission and reception, while the communication card provides network access authentication and identity verification information. Operational business refers to the business data that the charging pile needs to interact with the operation platform during normal charging services, including but not limited to charging start requests, charging stop requests, order metering data, billing and settlement data, payment result data, real-time alarm data, and platform control commands. Maintenance business refers to the business data that the charging pile needs to interact with the maintenance platform during equipment maintenance and management, including but not limited to remote diagnostic data, log feedback data, firmware upgrade data, parameter configuration data, and certificate update data.

[0024] In some implementations, the charging pile is equipped with a first communication unit and a second communication unit. The first communication unit forms a first communication link with a first communication card, and the second communication unit forms a second communication link with a second communication card. The two communication links are physically independent of each other, each having its own independent communication module and communication card. Therefore, if one link experiences a hardware failure or network anomaly, the other link can still maintain normal operation.

[0025] In the default operating state, the first communication link carries operational services, acting as the main operational link and maintaining communication with the operational platform; the second communication link carries maintenance services, acting as the maintenance link and maintaining communication with the maintenance platform. This default division of labor ensures that operational and maintenance services do not interfere with each other under normal circumstances—the bandwidth resources required for operational services are guaranteed and will not be consumed by maintenance tasks such as log uploads and firmware upgrades; maintenance services can also run independently in the background without affecting the real-time performance of the charging service. However, this default division of labor is not a fixed binding relationship. Both communication links are capable of carrying both operational and maintenance services. When one link fails, the other link can take over the services it carries. In other words, while the first communication link defaults to carrying operational services, it also has the capability to carry maintenance services; similarly, while the second link defaults to carrying maintenance services, it also has the capability to carry operational services. This "default division of labor, dynamic takeover" mechanism allows the two links to perform their respective functions under normal circumstances and serve as backups for each other in case of failure.

[0026] The health score is a comprehensive quantitative evaluation of the overall quality of the communication link. It doesn't reflect a single indicator, but rather comprehensively considers the performance of the communication link across multiple dimensions, including wireless signal strength, data transmission, and platform connectivity. Specifically, the charging pile's main control unit collects various communication quality parameters of the two communication links according to a preset sampling period (e.g., every 30 seconds or every 60 seconds). Communication quality parameters include, but are not limited to: network registration status (reflecting whether the communication card has been successfully registered to the operator's network), PDP / PDN activation status (reflecting whether the data service channel has been established), IP acquisition status (reflecting whether a valid network address has been obtained), RSSI (Received Signal Strength Indicator), RSRP (Reference Signal Received Power), RSRQ (Reference Signal Received Quality), SINR (Signal-to-Interference-plus-Noise Ratio), cell ID (identifier of the currently accessed base station), frequency band (current operating frequency band), platform heartbeat RTT (round-trip time for sending a heartbeat message to the platform and receiving a response), packet loss rate, retransmission rate, number of consecutive heartbeat failures, DNS resolution time, module temperature, power supply voltage fluctuation, transmit power level, number of abnormal resets, remaining data allowance, daily used data allowance, monthly billing date, and speed limit threshold. These parameters reflect the operational status of the communication link from different perspectives. For example, RSSI, RSRP, RSRQ, and SINR reflect the strength and quality of the wireless signal; heartbeat RTT and packet loss rate reflect the latency and reliability of data transmission; the number of consecutive heartbeat failures reflects the stability of the connection status with the target platform; remaining data allowance and monthly billing date reflect the remaining data allowance of the communication card; and module temperature and power supply voltage fluctuations reflect the hardware operating environment of the communication module.

[0027] In some implementations, the health score can be calculated as follows: The wireless side quality score, transmission side quality score, platform connection quality score, data plan availability score, and module risk item score are calculated separately, and then a weighted sum of these scores is obtained to obtain a comprehensive health score. Specifically, the wireless side quality score is mainly calculated based on parameters such as RSSI, RSRP, RSRQ, SINR, and cell reselection count, reflecting the quality status of the communication link at the wireless access layer; the transmission side quality score is mainly calculated based on parameters such as heartbeat RTT, packet loss rate, and retransmission rate, reflecting the efficiency and reliability of data transmission; the platform connection quality score is mainly calculated based on parameters such as heartbeat success rate, DNS resolution results, and TCP / MQTT / HTTPS connection status, reflecting the effectiveness of the end-to-end connection with the target platform; the data plan availability score is mainly calculated based on parameters such as remaining data, rate limiting risk, and billing date, reflecting the sufficiency of communication card data resources; and the module risk item score is mainly calculated based on parameters such as module temperature, power supply ripple, number of abnormal resets, and dual-module mutual interference status, reflecting the stability and security of the communication module hardware. All the above scores can be normalized to a uniform numerical range (e.g., 0 to 100 points) to facilitate comprehensive comparison and weighted calculation. Each communication link corresponds to a comprehensive health score; for example, the health score of the first communication link is denoted as H1, and the health score of the second communication link is denoted as H2.

[0028] The first threshold is a preset health score threshold used to determine whether a communication link has deteriorated to the point where service switching needs to be triggered. When the health score of a communication link falls below the first threshold, it means that the link has experienced significant degradation in one or more dimensions, such as wireless signal quality, transmission performance, platform connection status, or hardware stability. Continuing to rely on this link to transmit critical services may lead to consequences such as communication interruption, data loss, or command timeouts. In this case, the services carried on this link need to be switched to another communication link. The specific value of the first threshold can be preset by those skilled in the art based on the actual application scenario and communication quality requirements. For example, it can be set to 40 points (out of 100), triggering switching when the health score falls below 40 points.

[0029] The specific process of service switching includes: when the main control unit detects that the health score of a certain communication link is lower than a first threshold, it switches the service carried on that communication link to another communication link for transmission. For example, if the health score of the first communication link (which by default carries operational services) is lower than the first threshold, the operational services are switched to the second communication link for transmission; if the health score of the second communication link (which by default carries maintenance services) is lower than the first threshold, the maintenance services are switched to the first communication link for transmission. The switching operation includes re-establishing the communication connection with the target platform, sending the service data to be sent through the new communication link, and stopping the transmission of service data through the original communication link.

[0030] During link switching, the charging pile's charging control and safety protection functions are still executed independently by the local main control unit, regardless of the communication link's connectivity. The charging pile will continue to perform ongoing charging tasks, including real-time monitoring of parameters such as charging voltage, current, and temperature, and implementing safety measures such as overcurrent protection, overtemperature protection, and leakage protection. The communication link switching will not cause charging output interruption, and the user's charging experience will not be affected.

[0031] During link switching, the charging pile also stores the generated business data in local storage. This is because during the switching process, the original communication link may become unavailable or of poor quality, while the new communication link may not yet be fully established. If the generated business data (such as metering records, status changes, alarm information, etc.) is only stored in memory, it will be lost if the device is powered off or reset. Local storage is preferably non-volatile storage (such as Flash chips) or a cache with power-loss protection, ensuring that the data stored therein will not be lost even if the device is unexpectedly powered off. The stored data includes, but is not limited to: order data, metering record data, control command confirmation data, and alarm data.

[0032] Simultaneously, the charging pile also records data breakpoints. A data breakpoint refers to the identifier of the last piece of data that the platform has confirmed received. Specifically, during normal communication, each time the charging pile sends a piece of business data (such as a metering record) to the platform, the platform typically returns an acknowledgment after successfully receiving and processing it. The charging pile records the sequence number or other unique identifier of the last piece of data confirmed by the platform; this location is the data breakpoint—data before the breakpoint has been confirmed by the platform, while data after the breakpoint has not yet been confirmed. The significance of recording data breakpoints is that after a handover, the charging pile can accurately determine which data needs to be retransmitted—only the data after the breakpoint needs to be retransmitted, without repeating data already confirmed by the platform.

[0033] After a successful link switch, the charging pile establishes a communication connection with the corresponding platform through the new communication link. Here, "corresponding platform" refers to the target platform to which the business data should have been sent—operational business to the operations platform, and maintenance business to the maintenance platform. For example, if the first communication link fails, causing the operational business to switch to the second communication link, then after a successful switch, the charging pile connects to the operations platform through the second communication link to re-transmit data to the operations platform; if the second communication link fails, causing the maintenance business to switch to the first communication link, then after a successful switch, the charging pile connects to the maintenance platform through the first communication link to re-transmit data to the maintenance platform.

[0034] The retransmitted data consists of business data since the data interruption point, i.e., data that the platform has not yet confirmed as received. The charging pile sends this data to the corresponding platform via a new communication link to complete the data that could not be reported in time due to communication interruption during the link switch. The retransmitted data carries an identifier for deduplication verification, which allows the platform to determine whether the received data has already been processed. Specifically, each piece of business data can carry a unique data identifier (such as an identifier generated by combining the charging pile number, business type, timestamp, and serial number). After receiving the retransmitted data, the platform queries its local records based on this identifier: if the data corresponding to the identifier has already been processed, the platform ignores the received data and does not perform duplicate billing or accounting; if the data corresponding to the identifier has not yet been processed, the platform processes it normally. In this way, even if the same data is retransmitted multiple times due to network fluctuations, the platform can accurately identify and avoid duplicate processing through the deduplication verification identifier.

[0035] It should be noted that the identifier used for deduplication verification can also be called an idempotent key. Idempotency is an important concept in distributed systems, referring to the fact that executing the same operation multiple times produces the exact same result as executing it once. In the context of this invention, each piece of business data carries an idempotent key, which the platform uses as a unique index for deduplication. There are various ways to generate idempotent keys. For example, they can be generated by combining hashes based on the charging pile number, order number, serial number, and timestamp, or the serial number combined with the charging pile number can be used directly as a combined unique identifier. Regardless of the specific generation method used, as long as each piece of business data has a globally unique identifier, it is acceptable.

[0036] Through the above technical solution, when a communication link malfunctions, this invention can promptly switch the services on that link to another communication link, avoiding service interruptions caused by single-link failures. Simultaneously, local storage and breakpoint logging ensure that service data generated during the switching process is not lost. Targeted retransmission and deduplication verification after the switch is completed guarantee the integrity and accuracy of platform-side data, preventing duplicate billing or data loss. Therefore, this effectively overcomes the shortcomings of existing charging piles, such as fixed division of labor between dual links and lack of coordination, leading to service interruptions and billing errors.

[0037] In the first embodiment, the step of calculating the health score of the first communication link and the health score of the second communication link respectively includes: When the health score of any communication link is greater than the first threshold and lower than the second threshold for a preset number of sampling periods, a connection to the platform corresponding to that communication link is established through another communication link.

[0038] It should be noted that this embodiment provides a preferred implementation method for performing pre-handover preparation when the communication link health score is within a specific range, so as to further improve the timeliness and smoothness of link handover.

[0039] In real-world operating environments, the health score of a communication link is not always stable but can dynamically change within a certain range due to factors such as signal fluctuations, network congestion, and base station handover. If handover is only triggered when the health score falls below a first threshold, then during the phase where the signal gradually deteriorates but is still within the first threshold, the charging station may already be experiencing quality degradation phenomena such as increased communication latency, higher packet loss rates, and slow heartbeat response, but the handover mechanism has not yet been triggered. In this case, if the handover is only executed after the score further deteriorates to below the first threshold, there may be a delay between the handover decision and the establishment of a new link, affecting service continuity. On the other hand, if a backup connection is established immediately upon a slight drop in the health score, frequent connection establishment and release may occur due to brief signal fluctuations, increasing system overhead.

[0040] To address this, the present invention establishes a second threshold, which is higher than the first threshold. This second threshold corresponds to a more lenient link quality requirement than the first threshold, defining a "range of concern." When the health score of a communication link is greater than the first threshold but lower than the second threshold for a continuously preset number of sampling periods, it means that while the health of the communication link is not yet bad enough to require immediate switching, it is already in a state of continuous decline and below normal levels. In this case, there is a possibility that the communication link may continue to deteriorate to below the first threshold, requiring advance preparation.

[0041] Specifically, a "health score greater than the first threshold and lower than the second threshold" indicates that the communication link's quality score falls within the range between the first and second thresholds. Since the first threshold is lower and the second threshold is higher, this range numerically lies between the two thresholds. When the health score is in this range, the communication link's quality has deviated from the normal level (normal levels are typically higher than the second threshold), but has not yet deteriorated significantly enough to trigger a forced handover (i.e., it has not yet fallen below the first threshold).

[0042] The condition that the score falls within this range requires several consecutive sampling periods, rather than triggering the condition only after a single sampling. The sampling period refers to the time interval at which the charging pile's main control unit periodically collects communication quality parameters and calculates the health score. For example, it can be set to collect and calculate the score every 30 seconds. Continuously setting a preset number of sampling periods is a specific implementation of the anti-jitter mechanism—if the health score only occasionally fluctuates to this range and recovers to above the second threshold in the next sampling, it is considered a short-term fluctuation, requiring no action; only when multiple consecutive sampling periods remain within this range does it indicate a genuine and sustained decline in communication link quality, rather than an occasional fluctuation. The specific value of the preset number can be set by those skilled in the art based on actual application needs, for example, it can be set to 3 consecutive sampling periods or 5 consecutive sampling periods. Continuity is determined when the score meets the range condition in adjacent sampling periods, without any instances of recovering to above the second threshold or falling below the first threshold.

[0043] When the above conditions are met, i.e., when the health score of the communication link is between the first and second thresholds for multiple consecutive sampling periods, this invention pre-establishes a connection with the target platform connected to the first communication link via another communication link. The essence of this operation is "pre-connection" or "early connection establishment," meaning that while the main link is not completely failed and can still be used for communication, another communication link that is still idle or under low load is used to pre-complete the handshake authentication and session establishment with the target platform. Assume that the first communication link defaults to carrying operational services, and its corresponding platform is the operational platform; the second communication link defaults to carrying maintenance services, and its corresponding platform is the maintenance platform. When the health score of the first communication link is between the first and second thresholds, this invention establishes a connection with the operational platform via the second communication link; conversely, when the health score of the second communication link is between the first and second thresholds, this invention establishes a connection with the maintenance platform via the first communication link. In other words, the "corresponding platform" refers to the target platform originally connected to the communication link with the abnormal health score.

[0044] It's important to note that establishing a connection with the target platform via a different communication link does not, at this point, switch the service to the new link. In other words, during this phase, services continue to be transmitted through the existing communication link; the newly established connection remains in standby mode and does not carry service data. This is done to two reasons: firstly, it ensures that if the health score deteriorates further below the first threshold, requiring a true switchover, the connection between the new link and the target platform has already been established, allowing for immediate service transmission switching and significantly reducing switchover latency; secondly, if the health score subsequently recovers to above the second threshold, indicating that the communication link quality has automatically recovered, the established connection can be disconnected as needed or remain in low-power standby mode, without affecting services on the original link.

[0045] Through this pre-switching mechanism, this invention establishes a connection with the target platform in advance using a backup link when the communication link quality experiences a continuous decline but has not yet reached the mandatory switching standard. This allows for a near-seamless service transfer when a switchover is truly needed. This mechanism effectively avoids the switching delays caused by "waiting until the link is completely unusable before starting to establish a connection," further improving the continuity of charging pile communication services and user experience.

[0046] In one example, the dual communication link collaborative management method for charging piles further includes: If the health score of any communication link is greater than the first threshold and lower than the second threshold for a preset number of sampling periods, and the health score rises to be greater than the second threshold, and the duration of the health score being greater than the second threshold is greater than a preset duration, then the communication link is switched back.

[0047] It should be explained that the implementation method provided in this example is used to switch services back to the original link after the communication link quality is restored, thereby restoring the default link division state while ensuring communication stability.

[0048] In actual operation, the health score of a communication link may fluctuate within a certain time range. When the health score of a communication link falls into the pre-switching range between the first and second thresholds due to reasons such as decreased signal quality or network congestion, and triggers a pre-connection operation, the quality status of that communication link does not necessarily continue to deteriorate. In some cases, as signal conditions improve or network load decreases, the health score of that communication link may gradually rise above the second threshold, indicating that its communication quality has returned to normal levels. At this time, if the services carried by this communication link can be switched back from the backup link to this link, the default division of labor between the two communication links under normal conditions can be restored—that is, the first communication link carries operational services, and the second communication link carries maintenance services, allowing the two links to achieve optimal communication performance under their respective default division of labor.

[0049] However, a health score on a communication link rising above the second threshold could signal sustained recovery or be a temporary fluctuation. If a switchback is immediately executed as soon as the health score rises above the second threshold, and then falls below the second threshold or even the first threshold again after the switchback, it will cause frequent switching between the two links, the so-called "ping-pong effect." Frequent switching not only increases system overhead and network signaling burden, but may also cause unnecessary interference with the continuity of charging services. Therefore, this example introduces a duration condition judgment in the switchback mechanism. Specifically, when a communication link previously entered a pre-switching range where the health score was between the first and second thresholds, and its score subsequently rises above the second threshold, a switchback operation is not immediately executed. Instead, the health score of the communication link is continuously monitored, and it is determined whether the duration of the score exceeding the second threshold is greater than a preset duration. Only when the duration exceeds the preset duration will the service be switched back to that communication link.

[0050] "Duration" refers to the continuous period from the moment the health score last rose above the second threshold until the current time, during which the score remains above the second threshold. If the score falls below the second threshold during the timing process, the duration is recalculated; only the time the score remains continuously above the second threshold is counted in the duration. The essence of this mechanism is to verify the stability of the link recovery—only when the recovery status lasts for a sufficiently long time can the interference of temporary fluctuations be eliminated, confirming that the quality of the communication link has indeed substantially improved. The preset duration is a configurable time parameter, and its specific value can be set by those skilled in the art according to the actual application scenario. For example, it can be set to 30 seconds, 60 seconds, or 120 seconds.

[0051] During the switchback operation, the charging station will switch back the services that were previously transferred to the backup link due to the failure of the original link to the original communication link. Taking the example of the first communication link defaulting to carrying operational services and the second communication link defaulting to carrying maintenance services: Assume that the health score of the first communication link previously fell into the pre-switch range and triggered a pre-connection operation. If the score of the first communication link subsequently deteriorates further to below a first threshold, the operational services are switched to the second communication link. When the score of the first communication link rises above the second threshold and remains there for a duration longer than a preset time, the charging station will switch the operational services back from the second communication link to the first communication link. After the switchback is complete, the two communication links return to their initial default division of labor—the first communication link carries operational services, and the second communication link carries maintenance services.

[0052] During the switchback process, ongoing charging orders remain uninterrupted. Charging piles continue charging control and safety protection during the switchback, ensuring that locally cached metering data can continue to be reported normally after the switchback. The data retransmission mechanism during the switchback is similar to the retransmission mechanism after link switching described in the first embodiment—if there is business data generated during the switchback that has not yet been confirmed by the target platform, it will be retransmitted through the link after the switchback. The retransmitted data also carries an identifier for deduplication verification to ensure the consistency and accuracy of data on the platform side.

[0053] Through the aforementioned switchback mechanism, this invention can automatically switch services back to the original link after the communication link quality recovers and stabilizes, restoring the default division of labor between the two communication links. Because a duration threshold is introduced into the switchback condition, service oscillations caused by frequent switchbacks due to brief signal recovery are avoided, further improving system stability and reliability. This switchback mechanism, in conjunction with the pre-switching mechanism, forms a complete closed-loop control link of "degradation warning → pre-connection preparation → recovery confirmation → switchback restoration," enabling smooth and stable transitions between the default division of labor and dynamic takeover states between the two communication links.

[0054] In another example, the calculation of the health score of the first communication link and the health score of the second communication link, respectively, then includes: When any of the following events occurs on any communication link: physical connection interruption, no response from the 4G module, or M consecutive failures of the platform heartbeat, the service carried by that communication link is immediately switched to another communication link, and the service data generated by the charging pile during the link switching is stored, and the data breakpoint is recorded; where M is a preset positive integer.

[0055] It should be explained that this example provides a preferred implementation for performing a forced handover when a sudden, unavailable event occurs in the communication link, in order to ensure the continuity of the charging service.

[0056] In actual operation, communication link failures do not always manifest as a gradual decline in scores below a threshold. In some cases, communication links may completely lose their communication capability within a very short time due to sudden events, resulting in the charging station being unable to collect valid communication quality parameters, or the collected parameters becoming so abnormal that score calculations become meaningless. Specifically, such sudden unavailability events include, but are not limited to, the following three typical scenarios: The first is physical connection interruption. Physical connection interruption means the communication link is completely broken at the physical level, and the charging pile cannot establish any form of wireless connection with the base station. Causes of physical connection interruption may include: loose or disconnected RF connection between the communication module and antenna, poor contact or removal of the communication card, base station shutting down signal coverage in the area due to malfunction or maintenance, or the charging pile being located in a signal dead zone. In these situations, the communication link is completely unusable, with no possibility of signal recovery in the short term; waiting will only delay the service restoration time.

[0057] Secondly, there is the issue of the 4G module becoming unresponsive. The 4G module is the physical layer hardware component that constitutes the communication link, responsible for functions such as signal transmission and reception, protocol stack processing, and interaction with the base station. When the 4G module fails to respond to the main control unit's commands due to hardware failure, firmware abnormalities, power supply problems, or internal deadlock, the charging pile cannot communicate through the module even if an available carrier network signal exists. Unlike a physical connection interruption, the manifestation of a 4G module becoming unresponsive may not be "no signal," but rather the module not responding to AT commands, failing to complete initialization, frequently resetting automatically, or being in a suspended state. In this situation, the main control unit cannot perform any communication operations through the module, and the link has effectively failed.

[0058] Thirdly, the platform heartbeat fails M times consecutively. The heartbeat mechanism is a common method for maintaining connection status between the charging pile and the target platform. The charging pile sends heartbeat messages to the target platform according to a preset heartbeat cycle (e.g., every 30 seconds or every 60 seconds). Upon receiving the message, the platform returns a heartbeat response, thus confirming the connectivity of the communication link at the application layer. If the charging pile sends heartbeat messages multiple times without receiving a response from the platform, it indicates that although the communication link may still exist at the wireless signal layer, end-to-end communication at the application layer has been interrupted. Reasons for heartbeat failure may include: platform server crashes or restarts, network routing changes causing messages to fail to reach the target, platform address or port changes without notifying the device, firewalls or security policies blocking communication, and expired certificates causing TLS handshake failure. Unlike physical layer and module layer failures, heartbeat failure is an application layer connection anomaly—the signal may be normal, the module may be normal, but business data cannot be delivered to the target platform.

[0059] Compared to scenarios where health scores trigger handover, the aforementioned sudden events exhibit significantly different characteristics. In score-triggered handover scenarios, the performance of the communication link typically deteriorates gradually—signal strength gradually weakens, packet loss rate gradually increases, and latency slowly increases—giving the charging station ample time to complete score calculation and execute a controlled handover process. However, in sudden unavailability events, the communication link often transitions from a normal state to complete failure within a very short time, without a transitional phase of performance degradation. In this situation, if handover decisions still rely on health scores, the handover decision will fail to trigger properly because the charging station can no longer collect valid communication quality parameters or calculate a meaningful score, forcing the interruption of business data transmission.

[0060] Therefore, in this example, the charging pile will immediately perform a forced handover when any of the following three scenarios are detected: physical connection interruption, 4G module unresponsiveness, or M consecutive platform heartbeat failures. "Immediately" means that the handover operation is initiated the instant the event is detected, without waiting for the next sampling period or the calculation result of the health score. This differs from handover based on health scores—the latter requires collecting parameters, calculating a score, and comparing it with a threshold, which introduces a certain delay. Once such an event occurs, it indicates that the original link has lost its communication capability. Any delay will directly result in critical business data (such as real-time metering data of charging in progress, new charging requests initiated by users, etc.) being unable to be reported or received, thus affecting the ongoing charging service.

[0061] In a scenario where the platform heartbeat fails M times consecutively, M is a preset positive integer. The value of M can be set by those skilled in the art according to actual application requirements, for example, it can be set to 3 or 5 times. The charging pile sends heartbeat messages sequentially according to the heartbeat cycle, and waits for a preset timeout after each transmission; if no response is received after the timeout, it is counted as a failure; if no response is received for M consecutive times, a handover is triggered. If a heartbeat successfully receives a response during the consecutive failures, the failure count is reset to zero and the counting restarts. This avoids unnecessary handovers triggered by single or occasional network jitter.

[0062] Compared to the pre-switching mechanism, the forced handover in this embodiment does not go through a pre-switching stage, nor does it require verification of whether the event lasts for multiple sampling periods. This reflects a differentiated handling strategy for different types of link anomalies: for gradual degradation (manifested as the score falling into the pre-switching range), a more conservative pre-connection strategy can be adopted, preparing in advance but not rushing to switch; for sudden complete failure (manifested as the above three events), an aggressive forced handover strategy must be adopted, taking immediate action to minimize service interruption time.

[0063] After the forced switch is executed, the charging pile performs the same local storage and data breakpoint recording operations as in the aforementioned implementation. Specifically, the charging pile stores the business data generated during the switch in the local storage area and records the last data breakpoint confirmed by the platform. After a successful switch, the charging pile retransmits the business data after the breakpoint to the corresponding platform via another communication link. The retransmitted data also carries an identifier used for deduplication verification.

[0064] Through the aforementioned forced handover scheme, this invention can immediately switch to another link without relying on scoring judgment when a communication link fails completely due to a sudden event, effectively supplementing the shortcomings of scoring-based handover mechanisms in sudden failure scenarios. The two handover mechanisms complement each other—the scoring-triggered mechanism is suitable for scenarios with gradual link performance degradation, while the event-triggered mechanism is suitable for scenarios with sudden and complete link failure—together forming a complete link handover triggering system, maximizing the continuity of charging services under various link anomaly conditions.

[0065] In the second embodiment, the dual-communication collaborative management method for charging piles further includes: The business is divided into real-time control business, billing key data business, keep-alive and status reporting business, and batch data transmission business. When the health score of any communication link falls below a first threshold, the service carried by that communication link is switched to another communication link, including: If the health score of the first communication link is lower than the first threshold, the second communication link is used to establish a connection with the operation platform, and the real-time control operation business and the billing key data operation business are switched to the second communication link for uploading, while the operation and maintenance business of suspension or rate limit keep-alive and status reporting is suspended. If the health score of the second communication link is lower than the first threshold, the first communication link is used to establish a connection with the operation and maintenance platform, and real-time control operation and maintenance services and / or billing critical data operation and maintenance services are switched to the first communication link for uploading.

[0066] It should be explained that this implementation method is used to perform differentiated transmission scheduling based on service type during link switching to ensure priority transmission of critical services.

[0067] In the actual operation of charging piles, the types of business data that need to interact with the platform are diverse, and different businesses have significant differences in terms of timeliness requirements, data integrity requirements, and bandwidth usage characteristics. Under normal circumstances, operation and maintenance businesses transmit data through their respective default links without interfering with each other. However, in link switching scenarios, all business data that were originally carried by two separate links must compete for transmission opportunities on limited single-link bandwidth resources. If these are not handled uniformly without differentiation, high-traffic businesses such as log uploads and firmware upgrades may crowd out bandwidth resources for critical businesses such as charging start commands and metering records, affecting the availability of core charging service functions. Therefore, it is necessary to classify and process different businesses during link switching, prioritizing businesses directly related to the real-time performance of charging services and the accuracy of billing.

[0068] Therefore, this invention divides charging pile communication services into four levels: real-time control services, billing critical data services, keep-alive and status reporting services, and batch data transmission services. These four categories are classified based on their sensitivity to "real-time performance" and "data integrity." The priority of the four categories decreases from high to low, with real-time control services having the highest priority, followed by billing critical data services, then keep-alive and status reporting services, and finally batch data transmission services having the lowest priority. Real-time control services refer to instruction interaction data involving real-time action control or confirmation of critical status changes of charging equipment, including but not limited to charging start instructions, charging stop instructions, emergency stop instructions, remote control instruction confirmation, and order critical status confirmation. This type of service is characterized by extremely high timeliness requirements (typically needing to be completed within milliseconds or seconds). Delay or loss of this data can lead to direct consequences such as the charging gun failing to start, the charging process failing to stop, or emergency protection instructions failing to execute. Therefore, this type of service should occupy the highest resource priority during transmission to ensure minimal transmission latency and packet loss rate.

[0069] Billing-critical data refers to data involving electricity metering, cost calculation, and financial transactions, including but not limited to order metering logs, charging status data, billing settlement data, payment result data, and critical alarm data. This type of service is characterized by: while its timeliness requirements are not as stringent as real-time control services (allowing for transmission delays of seconds or minutes), it has an absolute requirement for data integrity—the loss of any metering data can lead to inaccurate charging cost calculations, resulting in overcharging, undercharging, or settlement errors. Therefore, this type of service requires ensuring integrity and accuracy during transmission, ensuring that every piece of data is successfully received and acknowledged by the platform. Even if the link is temporarily unavailable, this type of service data needs to be persistently stored locally and delivered completely through a retransmission mechanism once the link is restored.

[0070] Keep-alive and status reporting services refer to auxiliary data used to maintain communication connections and periodically report device operating status, including but not limited to general status reporting, periodic heartbeat messages, device parameter synchronization, non-emergency alarms, and operation and maintenance command execution results. These services are characterized by moderate requirements for timeliness and completeness—occasionally losing one or two heartbeats or status reports will not substantially affect the normal operation of the charging service, and the platform will be aware of the latest status when the device reports again. Therefore, when link resources are strained, these services can be rate-limited or suspended to free up bandwidth for higher-priority services.

[0071] Batch data transfer services refer to background data transfer tasks with large data volumes but minimal timeliness requirements, including but not limited to log files, diagnostic packages, historical data retransmission, firmware upgrade package downloads, and file uploads. These services are characterized by significantly larger data volumes (a single log file or firmware package can reach tens or even hundreds of MB), but almost no timeliness requirements—logs can be uploaded hours or even days later, firmware upgrades can be scheduled for nighttime, and historical data retransmissions can be completed during network downtime. Therefore, in resource-constrained scenarios such as link switching, these services should be the first to be restricted.

[0072] After clarifying the priority division of the four types of services, this embodiment further defines the specific service routing strategies under different scenarios when the health score is lower than the first threshold and a switching is triggered.

[0073] When the health score of the first communication link (the link that defaults to carrying operational services) falls below the first threshold, the charging pile establishes a connection with the operation platform using the second communication link and switches real-time control and billing critical data operations to the second communication link for uploading. This is because, in the event of a deterioration in the first communication link, the second communication link becomes the only available channel for operational services, and real-time control and billing critical data operations are directly related to the availability of charging services and the accuracy of billing, thus requiring priority switching and transmission. Simultaneously, the charging pile suspends or limits the transmission rate of keep-alive and status reporting operations, meaning these operations are not switched to the second communication link or are allowed to be transmitted through the second communication link but their transmission rate is limited. This is done to prevent keep-alive and status reporting operations from consuming the bandwidth resources of the second communication link, thereby ensuring the transmission efficiency of real-time control and billing critical data operations. For batch data transmission operations (such as log back, firmware upgrade downloads, etc.), transmission will naturally not be initiated during the switching scenario.

[0074] It should be noted that, provided the bandwidth resources of the second communication link are sufficient, keep-alive and status reporting maintenance services can continue to be transmitted through the second communication link, but they should be given lower priority in the bandwidth scheduling strategy. When bandwidth resources are scarce, priority should be given to the transmission of real-time control and billing-critical data services, while keep-alive and status reporting services can be appropriately delayed or have their transmission frequency reduced. "Rate limiting" refers to limiting the amount of data transmitted per unit time for this type of service. For example, the bandwidth usage limit for this type of service can be set to 10% of the total bandwidth of the second communication link to avoid it competing for resources with higher-priority services.

[0075] When the health score of the second communication link (i.e., the link that defaults to carrying maintenance services) falls below the first threshold, the charging pile establishes a connection with the maintenance platform using the first communication link and switches real-time control maintenance services and / or billing critical data maintenance services to the first communication link for uploading. The difference from the previous scenario is that the second communication link defaults to carrying maintenance services, and the timeliness requirements of maintenance services are usually lower than those of operational services. Therefore, when the second communication link deteriorates, the types of services that need to be switched to the first communication link are real-time control maintenance services and billing critical data maintenance services—the former may involve remote debugging commands or emergency parameter modifications, and the latter may involve critical data collection in maintenance scenarios (such as recording critical operating parameters before and after a failure). For keep-alive and status reporting maintenance services and batch data transmission maintenance services, due to their lower timeliness and importance, they can wait for the second communication link to recover before sending, without occupying the bandwidth resources of the first communication link.

[0076] Through the aforementioned service tiering and differentiated switching strategies, this invention achieves priority protection for critical services under conditions of limited link resources. Even when bandwidth resources are halved during switching scenarios, charging piles can still ensure the normal transmission of real-time control services and billing-critical data services, without affecting the user's charging experience and billing accuracy. Simultaneously, by pausing or limiting speed to keep services alive, and by handling status reporting and batch data transmission services, non-critical services avoid competing for limited bandwidth resources, further ensuring the transmission quality of core services.

[0077] In the third embodiment, the service data generated by the charging pile during the storage link switching period, recording data breakpoints, includes: Based on the business data generated by charging piles during link switching, maintain the order cache table, metering flow table, instruction confirmation table, and retransmission team list; When a link switch occurs, record the last sequence number confirmed by the corresponding platform and use the last sequence number as the data breakpoint. The process of retransmitting the business data after the data breakpoint to the corresponding platform includes: Send an order status snapshot to the corresponding platform; Receive missing transaction interval information sent by the platform based on the order status snapshot; The service data is retransmitted in the order of the sequence number in the missing sequence interval information.

[0078] It should be explained that, as mentioned earlier, during link switching, the charging pile stores the generated business data in the local storage area and records data breakpoints. To achieve efficient management and accurate execution of this process, this invention maintains multiple structured data tables in the local storage area, including an order cache table, a metering log table, an instruction confirmation table, and a retransmission queue list. The local storage area is preferably a non-volatile storage medium or a cache area with power-loss protection to ensure that the data stored therein is not lost in the event of an abnormal power outage or reset of the device. The purpose and structure of each data table are as follows: The order cache table stores key information about currently executing or incomplete charging orders. Each order record includes at least the following fields: order number, charging pile number, charging session number, most recent metering time, most recent energy consumption, and order status. The order number is a unique identifier assigned to the charging transaction by the platform. The charging pile number identifies the data source device, and the charging session number associates all relevant metering and status data during a single charging session. The most recent metering time and most recent energy consumption reflect the last successfully reported metering time and corresponding energy value from the charging pile. The order status indicates the current stage of the order, such as "charging," "stopped," or "settling." This information ensures that even if a link switch causes a temporary communication interruption, the charging pile can still accurately describe the current status of each order to the platform after communication is restored.

[0079] The metering log is used to store individual metering data generated during the charging process. During charging, the charging station collects electrical parameters such as voltage, current, and power at a preset frequency (e.g., every second or every minute), and calculates incremental and cumulative energy consumption. Each collection and calculation results in a metering log record, containing fields such as log number, order number, timestamp, voltage, current, power, incremental energy consumption, cumulative energy consumption, event type, and transmission status. The log number is a unique, incrementing number for each record in the metering log, used to identify the data generation sequence and locate data breakpoints. The order number associates the metering log with the corresponding charging order. The timestamp records the time the data was collected. The transmission status indicates the current transmission status of the data, such as "not sent," "sent pending confirmation," or "confirmed," used by the charging station to track the reporting progress of each data entry.

[0080] The instruction confirmation table stores remote control instructions from the platform and their execution results. During operation, the charging station may need to receive and execute various instructions issued by the platform, such as remotely starting charging, remotely stopping charging, and setting parameters. Each instruction record includes fields such as platform instruction number, instruction type, reception time, execution time, execution result, and deduplication key. The platform instruction number is a unique identifier assigned to each instruction by the platform, used to provide feedback on the execution result after the instruction is completed. The deduplication key prevents the same instruction from being executed repeatedly—if the platform issues the same instruction repeatedly due to network timeout without receiving confirmation, the charging station can identify that the instruction has already been executed through the deduplication key, thus avoiding errors caused by duplicate execution.

[0081] The retransmission queue list is used to manage business data that needs to be retransmitted to the platform. When a link switch occurs, the charging pile will write the business data that needs to be retransmitted (mainly metering flow data and instruction confirmation data) into the retransmission queue list according to the priority and order of retransmission. The retransmission module will then send the data sequentially according to the queue order. Each record in the retransmission queue list contains at least the following fields: data source table identifier, unique identifier of the data record, and retransmission status, used to track the retransmission progress.

[0082] When a link switch occurs, the charging pile needs to record the data breakpoint. In this implementation, the data breakpoint is specifically represented by the last transaction sequence number confirmed by the corresponding platform. The "corresponding platform" refers to the target platform corresponding to the business affected by the current link switch. For example, if the operation link switches, the last transaction sequence number confirmed by the operation platform is recorded; if the maintenance link switches, the last transaction sequence number confirmed by the maintenance platform is recorded. This transaction sequence number marks the position of the last metering transaction that the platform has successfully received and confirmed—all metering data with a transaction sequence number less than or equal to this value has been confirmed by the platform, while metering data with a transaction sequence number greater than this value has not yet been confirmed by the platform. This breakpoint position will be used to determine the starting position for retransmission after the switch is completed. At the same time, the charging pile writes the new order data added during the link switch into the metering transaction table. Each new record is marked as "not sent" when it is written, waiting to be retransmitted after the new link is established.

[0083] After a successful link switch, the charging station sends an order status snapshot to the corresponding platform via the new link. The order status snapshot is a data packet containing a summary of the currently executing order—including but not limited to the order number, session number, order status, recent battery level, and the last confirmed transaction number on the platform. The purpose of this snapshot is to inform the platform of the current status of the charging station, enabling the platform to compare its own records and determine if there are any data gaps.

[0084] After receiving the order status snapshot, the platform searches for its own record based on the order number and session number in the snapshot, and compares its confirmed transaction sequence number with the last transaction sequence number in the snapshot. If they match, the data is complete and no retransmission is needed. If the last transaction sequence number on the platform side is less than the last transaction sequence number in the snapshot, it means that there is data on the charging pile side that the platform has not yet received. Based on this, the platform determines the start and end positions of the missing transaction interval and sends the missing transaction interval information to the charging pile. The so-called "missing transaction interval information" refers to the continuous interval between the last confirmed transaction sequence number plus one on the platform side and the last transaction sequence number on the charging pile side, such as "transactions from number 1001 to number 1020". After receiving the missing transaction interval information, the charging pile reads the corresponding transaction record from the local metering transaction table in ascending order of transaction sequence number and retransmits it.

[0085] The significance of retransmitting data in sequence according to the serial number is to ensure the temporal consistency and integrity of the data. After receiving the retransmitted serial data, the platform processes it sequentially according to the serial number, avoiding processing logic confusion that might be caused by out-of-order arrival. Each retransmitted serial data carries the deduplication check flag described in the first embodiment when it is sent, and the platform uses this flag to determine if it is duplicated. If a certain serial data has already been processed (for example, due to network issues, although the platform has received it, the confirmation message is lost, and the charging pile retransmits the data), the platform identifies the duplicate data through the deduplication check flag and directly ignores the received data, without performing duplicate billing or duplicate accounting. If a certain serial data has not yet been processed, the platform processes it normally and updates the confirmation status.

[0086] After the retransmission is completed, the charging station updates the sending status of the successfully retransmitted log record to "Confirmed" and updates the "Last Log Sequence Number Confirmed by the Platform" in its local record to the latest value after the retransmission. If a link switch occurs again during the retransmission process, the charging station updates the retransmission cursor and continues the retransmission from the unconfirmed position on the new link, without having to start the retransmission from the beginning. The retransmission cursor records the current retransmission progress, i.e., which log record has been retransmitted to, ensuring the recovery of the retransmission task in case of interruption.

[0087] Through the aforementioned structured data tables and retransmission process, this invention achieves orderly storage, precise location, and reliable retransmission of business data during link switching. The order cache table, metering log table, instruction confirmation table, and retransmission team list each perform their respective functions, carrying order-level information, time-series metering information, instruction execution information, and retransmission task information, collectively forming a complete local data management system. The order status snapshot, combined with the interaction mechanism for missing log segment information, eliminates the need for charging piles to blindly retransmit all data; only the missing segments from the platform need to be accurately retransmitted, significantly reducing the amount of data retransmitted and communication overhead. Simultaneously, the dual guarantee of sequential log number retransmission and deduplication verification ensures the temporal correctness and data uniqueness of the platform-side data. This implementation method, combined with the switching trigger, local storage, and data breakpoint recording mechanism described in the first embodiment, forms a complete data protection chain of "switching—storage—breakpoint recording—status snapshot—missing interval identification—orderly retransmission—deduplication confirmation," effectively avoiding data loss and duplicate billing issues during link switching scenarios.

[0088] In the fourth embodiment, the charging pile dual communication link collaborative management method further includes: Collect radio frequency parameters and transmission status parameters of the two communication links; When it is determined, based on the radio frequency parameters and transmission status parameters, that there is a risk of mutual interference between two communication links, at least one of the following anti-interference operations shall be performed: Perform time-sharing transmission scheduling on non-real-time services on at least one communication link to stagger the services on different communication links in time. Adjust the transmission power of at least one communication link; Control the two communication links to prevent them from performing batch data transmission tasks simultaneously.

[0089] It's important to explain that in charging piles equipped with dual 4G communication units, the two communication modules may operate simultaneously. For example, the first communication link might be exchanging metering data and charging commands with the operation platform, while the second communication link is simultaneously transmitting diagnostic data or log files with the maintenance platform. In this scenario, radio frequency interference (RF interference) may occur between the two 4G modules. RF interference refers to the situation where, when one communication module transmits a signal, its RF energy enters the RF front-end of another communication module through spatial coupling, power conduction, or harmonic radiation. This causes a decrease in the receiving sensitivity and a deterioration in the signal-to-noise ratio of the transmitting module, leading to increased data retransmission rates and unstable connections. Radio frequency interference is usually related to the following factors: when the operating frequency bands of two modules are adjacent or have a frequency doubling relationship, the transmitted signal of one module may fall into the received frequency band of the other module; when two modules transmit signals at high power at the same time, the total radiated energy increases and the intermodulation products increase; when two modules share the same power supply branch, the power supply ripple caused by the instantaneous large current may conduct to each other, affecting the linearity of the RF power amplifier; when the physical spacing between the antennas of the two modules is insufficient, the spatial isolation is not enough, causing the transmitted signal to be directly coupled to the antenna port of the other module.

[0090] To detect potential mutual interference risks, this invention collects radio frequency (RF) parameters and transmission status parameters of two communication links. RF parameters include, but are not limited to, the operating frequency band, bandwidth, transmit power, and signal reception quality parameters (such as reference signal received power, reference signal received quality, and signal-to-interference-plus-noise ratio) of each communication link. Transmission status parameters include, but are not limited to, the retransmission rate, transmit queue length, and power ripple and module temperature reflecting the hardware operating status of each communication link.

[0091] When a risk of mutual interference is determined, the present invention performs at least one of the following anti-interference operations to reduce or eliminate the impact of mutual interference on communication quality.

[0092] The first anti-interference operation is time-division multiplexing (TDM). The core idea of ​​TDM is to divide time into different time periods, allowing two communication links to occupy radio resources during different time periods, thus avoiding mutual interference caused by simultaneous transmission. Specifically, TDM is applied to non-real-time services on at least one communication link, staggering the services on different links in time. For example, the timeline is divided into alternating transmission windows and guard intervals. Real-time control and billing-critical data services are scheduled to be transmitted through one link within one transmission window, while batch data transmission tasks such as logs, diagnostic packets, and firmware upgrade fragments are scheduled to be transmitted through another link within another transmission window. A guard interval is set between the two transmission windows—during which neither link transmits data, serving as a buffer time for transmit / receive switching and interference cancellation. Through this time-division and peak-shifting method, the two links will not be in a transmitting state simultaneously, fundamentally avoiding the superposition and mutual interference of radio frequency signals. The impact of time-sharing transmission scheduling on real-time control and billing-critical data services can be minimized through short window and priority scheduling—the transmission window for real-time control services can be set to be shorter and more frequent to ensure that the transmission delay of real-time instructions is not affected.

[0093] The second anti-interference operation involves adjusting the transmit power of at least one communication link. Transmit power adjustment includes both lowering and raising the power, with lowering the power being the primary anti-interference measure. For low-priority links that only carry heartbeat messages or serve as backup sessions, their upper limit of transmit power can be appropriately lowered to reduce the radiation intensity of their transmitted signals, thereby reducing interference to the other link. When the link quality falls below a preset guarantee threshold—for example, when the signal reception quality parameter (reference signal reception power) is close to the minimum available level—power backoff is canceled and the transmit power is restored to normal, while high-volume concurrent transmission is limited to avoid link disconnection due to power reduction. Power adjustment methods can also include dynamic power control—when one module needs to send critical data, the transmit power of another module is temporarily reduced, and restored after the critical data transmission is completed. By adjusting the transmit power, the source strength of mutual interference is reduced, allowing the two links to coexist at a lower level of mutual interference at the same time.

[0094] The third anti-interference operation involves controlling the two communication links to avoid simultaneous batch data transmission tasks. Batch data transmission tasks refer to large-volume, long-duration transmission tasks such as firmware upgrade package downloads, batch log retransmissions, and large file uploads. These tasks occupy wireless resources for extended periods and maintain high throughput. If two links execute such tasks simultaneously, they will not only remain in a state of mutual interference for a long time but may also exacerbate the problem due to frequent retransmissions caused by mutual interference. Therefore, this invention controls the two communication links to avoid simultaneous batch data transmission tasks—when one link is performing batch data transmission, the batch data transmission task of the other link is postponed until the task is completed or scheduled to be executed at a different time. For real-time control and billing-critical data services, the data volume is usually very small (a single instruction or a single transaction is only tens to hundreds of bytes), and does not belong to batch data transmission tasks. Therefore, it is not affected by this operation and can be transmitted at any time through any available link. The execution of this operation has no impact on the charging service itself because batch data transmission tasks have the lowest timeliness requirements, and their transmission timing can be flexibly scheduled according to the link status.

[0095] The three anti-interference operations described above can be performed individually or in combination. For example, after determining that there is a risk of mutual interference, both time-division transmission scheduling and transmit power adjustment can be used simultaneously, or only one method can be used: controlling batch data transmission tasks to avoid simultaneous occurrence. The choice of these three operations can be flexibly combined according to the severity of interference in the actual application scenario and the communication service requirements. In cases of minor mutual interference risk, simply controlling batch data transmission tasks to avoid simultaneous occurrence is sufficient to eliminate interference; in cases of severe mutual interference risk, both time-division transmission scheduling and power adjustment measures need to be used simultaneously.

[0096] Through the aforementioned anti-interference control scheme, this invention effectively reduces the impact of radio frequency mutual interference on communication quality when two 4G modules operate simultaneously. Specifically, time-division transmission scheduling avoids instantaneous interference caused by simultaneous transmission, isolating the transmission activities of the two links in the time dimension; transmit power adjustment reduces the intensity of interference sources, mitigating the degree of mutual interference in the amplitude dimension; and staggered batch data transmission reduces the duration of long-term mutual interference, compressing the mutual interference window in the time dimension. These three operations suppress mutual interference from the three dimensions of time, amplitude, and duration, respectively, and are independent yet complementary to each other. Thus, while achieving dual-link collaborative management, this invention ensures that the communication quality of each link meets the requirements of service transmission when the two modules operate in parallel, avoiding problems such as communication quality degradation, increased data retransmission rate, and deterioration of link stability caused by mutual interference. This ensures that both the first and second communication links can effectively transmit their respective service data when operating simultaneously.

[0097] In the fifth embodiment, the charging pile dual communication link collaborative management method further includes: Maintain the resource status information of the traffic tariff accounts corresponding to the two communication links respectively; The resource pressure value for each traffic tariff account is determined based on the resource status information. When the resource pressure value of any traffic tariff account exceeds the preset pressure threshold, the non-real-time services on that communication link are rerouted to another communication link for transmission.

[0098] It should be explained that, in the embodiments of this invention, each communication link corresponds to a data tariff account. A data tariff account refers to the billing entity associated with the communication card, recording the data package and usage of the communication card within the current billing cycle. Different communication links may use different operator networks, or they may use the same operator but different tariff packages. Therefore, the data tariff accounts corresponding to two communication links may differ in terms of total package amount, billing date, overage rate, and speed limit rules.

[0099] During operation, the charging station maintains resource status information for the respective data traffic accounts of the two communication links. Resource status information is a data set reflecting the current available resources of the data traffic accounts, and may include one or more of the following: The billing date is the settlement and reset date for each billing cycle of the data traffic account, such as the 15th of each month. On the billing date or the following day, the data traffic allowance in the package is usually reset to the total package amount, and a new billing cycle begins. Billing date information is crucial for data traffic scheduling decisions—if there is still a significant amount of data remaining in the account near the billing date, it can be fully utilized before the billing date to avoid data waste; if there is little data remaining, data usage on that link can be restored after the billing date resets. The total package amount refers to the total data traffic allowance included in each complete billing cycle of the data traffic account, such as 30GB of domestic general data traffic per month. The used data for this cycle refers to the total data traffic consumed by the account from the start of the current billing cycle to the current moment. The remaining data allowance for an account is calculated by subtracting the amount already used in the current period from the total data allowance. The less data remaining, the greater the risk of the SIM card being speed-limited or incurring excessive charges. Reserved data for critical services is a data allowance reserved to ensure real-time control and billing-critical data services. Even if the remaining data is limited, some data needs to be reserved to ensure continuous transmission for critical services. This reserve means that when determining whether data can be used for non-real-time services, the reserved data allowance for critical services needs to be deducted from the remaining data allowance; the remaining data available for non-real-time services is the actual usable portion in scheduling decisions. Excess charge refers to the unit price charged by the operator for data usage exceeding the total data allowance. Differences in excess charge are an important factor in data scheduling—migrating services to links with lower excess charge can reduce additional costs when exceeding the data allowance. Speed ​​limiting rules refer to the restrictions imposed by the operator on the transmission rate after data usage exceeds the total data allowance or a certain threshold, such as reducing it to 128Kbps or 256Kbps. Different operators have different speed-limiting rules. Some operators limit speed without charging extra after exceeding the data plan, while others continue to charge based on data usage on top of the speed limit. Speed-limiting rules affect the actual availability of the link after exceeding the data plan—if a link is already under speed-limiting, even if there is still remaining data, its actual transmission capacity may not be able to meet business needs. Historical daily usage statistics by service type refer to the daily data consumption data over the past several days, statistically analyzed according to service categories (real-time control, billing critical data, keep-alive and status reporting, batch data transmission). Historical daily usage can be used to predict future data demand—for example, by statistically analyzing the average daily data consumption of batch data transmission services over the past week, it is possible to estimate how much data will still be needed for this type of service by the end of the current billing cycle. In this implementation, the resource pressure value of each data tariff account can be determined based on resource status information.The resource stress value is a comprehensive quantitative evaluation of the current resource shortage level of a data traffic account, reflecting whether the account has sufficient remaining resources in the current billing cycle and the cost risks that may result from overuse.

[0100] Resource pressure can be determined as follows: the remaining traffic in the data plan account, estimated consumption, excess charges, days until the billing date, and service priority. Estimated consumption refers to the traffic expected to be consumed by the end of the current billing cycle, calculated based on historical daily usage by service type. It is calculated by multiplying the historical daily average usage for each service type by the sum of the remaining days until the billing date. The difference between remaining traffic and estimated consumption reflects the sufficiency of data resources—if the remaining traffic is significantly greater than the estimated consumption, the resource pressure is low; if the remaining traffic is less than the estimated consumption, the resource pressure is high. Excess charges reflect the additional fees required if all services are transmitted through this link, exceeding the package limit; the higher the excess charges, the greater the resource pressure. Days until the billing date reflects the remaining time window of available resources—the closer to the billing date, the more difficult it is to fully utilize the remaining traffic, and the lower the weight of this factor in the resource pressure assessment; the further away from the billing date, the greater the impact of insufficient remaining traffic, and the higher the weight of this factor in the resource pressure assessment. Business priority is reflected in the reserved traffic for critical businesses—the more reserved traffic high-priority real-time control and billing critical data businesses require, the less remaining traffic can be allocated to non-real-time businesses, and the higher the resource pressure.

[0101] Resource pressure values ​​can be calculated using a weighted summation method. For example, the ratio of remaining traffic to projected consumption can be normalized to a fraction between 0 and 100, excess charges can be normalized to a fraction between 0 and 100, and the number of days until the end of the month can be normalized to a fraction between 0 and 100. These fractions are then assigned different weights and summed to obtain the resource pressure value. Alternatively, a simpler determination method can be used. For instance, if the remaining traffic is lower than a preset traffic reserve threshold, or if the projected consumption is greater than the remaining traffic, the resource pressure value is directly determined to be higher than the preset threshold. Those skilled in the art can choose an appropriate resource pressure value calculation method based on actual application requirements.

[0102] When the resource pressure value of any traffic tariff account exceeds a preset pressure threshold, it indicates that the traffic resources of that account are relatively tight. Continuing to transmit non-real-time services through this communication link may lead to insufficient traffic for critical services or result in high excess charges. In this case, it is necessary to reroute the non-real-time services on this communication link to another communication link for transmission. Rerouting refers to changing the transmission path of specific service data—non-real-time service data originally sent through this communication link is instead sent through another communication link. Unlike the link switching described in the first embodiment, rerouting does not involve the transfer of all services, but only adjusts specific types of services (i.e., non-real-time services). Real-time control services and billing critical data services are still transmitted on the original link or switched to other links for transmission when needed. Taking batch data transmission services as an example, if the traffic tariff account resource pressure of the first communication link is high, the charging pile will transfer batch data transmission tasks such as log files and firmware upgrade packages that were originally planned to be transmitted through the first communication link to the second communication link for transmission, so as to make full use of the potentially more abundant traffic resources of the second communication link.

[0103] For real-time control services and billing-critical data services, the selection of transmission paths should not be based solely on traffic cost considerations, but also comprehensively consider the communication quality of the link. Since these two types of services are directly related to the availability of charging services and the accuracy of billing, even if the traffic account resource pressure on their respective links is high, they should not be migrated to links with poor quality simply to save traffic. Therefore, in this implementation, real-time control services and billing-critical data services preferentially select communication links with low resource pressure values ​​and / or high health scores for transmission. In other words, when determining the transmission links for these two types of critical services, it is necessary to comprehensively consider the link's resource pressure value and health score—when one link has a high health score but also high resource pressure, while another link has a relatively low health score but low resource pressure, it is necessary to weigh communication quality and traffic cost and select the link with the better overall conditions.

[0104] Through the aforementioned traffic scheduling scheme, this invention achieves intelligent management of dual-link traffic resources. Specifically, by maintaining the resource status information of the traffic tariff accounts corresponding to each communication link, dynamically assessing the resource pressure of each account, and migrating non-real-time services to links with sufficient resources when resources are scarce, this invention can maximize the utilization of traffic resources on both links while ensuring the transmission quality of real-time control and billing-critical data services, avoiding the imbalance where one link's traffic is exhausted while the other link still has a large amount of spare capacity.

[0105] In the sixth embodiment, the charging pile dual communication link collaborative management method further includes: Receive configuration update instructions from the operation and maintenance platform through the currently available communication link. The configuration update instructions contain the connection configuration information of the target platform. The configuration update command is subject to security verification. After successful verification, the connection configuration information is stored in a non-currently active configuration storage area; Using the currently available communication link, perform a connection reachability verification on the target platform based on the connection configuration information; When the connection reachability verification meets the preset pass conditions within the preset verification window, the current running configuration is adjusted based on the connection configuration information. The configuration is rolled back when the connection reachability verification fails or a connection anomaly occurs within a preset rollback window starting from when the connection configuration information takes effect.

[0106] It should be noted that this embodiment provides a preferred implementation method for remotely distributing and securely updating the connection configuration of the operation platform through the maintenance channel when the operation channel fails to connect due to configuration failure. This allows the device to restore communication without on-site maintenance in platform migration or configuration change scenarios. In actual operation, communication between the charging pile and the operation platform relies on a series of connection configuration parameters. These parameters include, but are not limited to: the main and backup addresses (IP addresses or domain names) of the operation platform, port number, protocol type (such as MQTT or HTTPS), MQTT topic, HTTPS path, Access Point Name (APN), Domain Name System (DNS) address, whitelist, heartbeat cycle, communication certificate, public key, private platform identifier, and platform switching policy. Among them, the platform address is used to determine the target location of the data packet, the port number is used to identify the target service, the protocol type and topic path are used to standardize the data interaction format, the APN and DNS are used to establish the data link and domain name resolution, and the communication certificate and public key are used for encrypted communication and identity authentication.

[0107] During the long-term operation of charging piles, the above configuration parameters may need to be changed for various reasons. For example, the operating platform service provider may upgrade its system or relocate its data center, resulting in a change of IP address; the platform may replace its communication certificate or update its encryption suite to improve security; charging pile customers may need to switch their devices from the current operating platform to a new operating platform due to business adjustments; or the platform's security policy may be updated, resulting in adjustments to port numbers or whitelist rules. In these scenarios, the new connection configuration parameters need to be updated to the charging pile to enable it to continue establishing a communication connection with the operating platform.

[0108] If the conventional configuration update method—delivering new configuration parameters through the operations channel—is used, this method will fail if the operations channel itself becomes unreachable due to configuration failure (e.g., expired old certificate, unreachable old platform address). In this situation, the charging pile cannot communicate with the operations platform, the operations platform cannot send new configurations, and the device becomes "out of contact." In existing solutions, this situation can only be resolved by sending personnel for on-site maintenance—technicians arrive at the site and reprogram the device via a local interface (such as serial port, USB, or local maintenance network) or manually modify the configuration file. This approach is not only labor-intensive and has a long response time, but the problem is particularly pronounced when charging piles are deployed in remote areas or when a large number of devices experience configuration failures simultaneously.

[0109] To address this issue, this invention utilizes an operation and maintenance (O&M) channel independent of the operational channel for configuration updates. In the dual-link architecture of the charging pile, the O&M link and the operation link are independent of each other. Even if the operation link becomes unreachable due to configuration failure, as long as the O&M link remains available, the charging pile can maintain communication with the O&M platform through the O&M channel. The O&M platform can use this channel to send configuration update commands from the operation platform to the charging pile, thereby completing the configuration update without relying on the operation channel.

[0110] The configuration update command is a data packet generated and issued by the operations and maintenance platform, containing the connection configuration information of the target platform. The target platform refers to the operations platform (or a new operations platform) from which the charging pile needs to re-establish a connection. The connection configuration information is a set of communication parameters required by the target platform, including at least the platform address, port, and communication certificate—essential information for establishing a connection. To ensure the security and integrity of the configuration update command during transmission, and to prevent malicious attackers from tampering with the configuration command to connect the device to a fake platform or cause the device to malfunction, the configuration update command also carries security verification information. This security verification information may include one or more of the following: version number, device number, timestamp, random number, digital signature, and integrity check value.

[0111] After receiving a configuration update command, the charging pile first performs a security verification. The purpose of this verification is to confirm that the command's source is trustworthy, its content is complete, it has not been tampered with, and that the command was indeed sent to this device. The security verification process may include, but is not limited to, the following verification items: verifying whether the version number is higher than the current configuration version to prevent older configurations from overwriting newer ones and causing configuration rollback; verifying whether the device number matches the current device's number to ensure the configuration command only applies to the correct target device and prevent crosstalk between devices; verifying whether the timestamp is within an acceptable time window to prevent replay attacks, i.e., preventing attackers from intercepting previously issued legitimate configuration commands and resending them; verifying the validity of the digital signature, which can be generated by the operations and maintenance platform using its private key to sign the content of the configuration command, and the charging pile uses a pre-stored public key from the operations and maintenance platform to verify the signature, confirming that the command was indeed issued by a legitimate operations and maintenance platform and has not been tampered with during transmission; and verifying the integrity check value (such as a hash value or checksum) to confirm that the configuration command has not suffered data corruption during transmission. If any of the above verifications fails, the security verification is deemed unsuccessful, the charging pile will refuse to accept the configuration update command, and the reason for the failure will be returned to the operation and maintenance platform through the operation and maintenance channel. Only when all verifications pass will the charging pile confirm that the configuration update command is legal and executable.

[0112] After successful security verification, the charging pile writes the connection configuration information to a non-currently effective configuration storage area. A non-currently effective configuration storage area refers to a storage region independent of the currently used operational configuration storage area. In some implementations, three configuration areas can be set in the charging pile's local storage: a current configuration area, a candidate configuration area, and a rollback configuration area. The current configuration area stores the currently used operational configuration, i.e., the configuration parameters that the charging pile is currently using to connect to the operation platform. The candidate configuration area stores newly received but not yet effective connection configuration information. The rollback configuration area stores known correct configuration versions that can be safely rolled back. After successful security verification, the connection configuration information is written to the candidate configuration area, while the configuration parameters in the current configuration area remain unchanged. This design ensures that even if anomalies occur during subsequent verification, the currently used configuration will not be affected, and the charging pile can still maintain the existing communication connection using the old configuration (if the old configuration is still partially available) or roll back to the old configuration when needed.

[0113] After being written to the candidate configuration area, the charging pile uses the currently available communication link to perform a connection reachability verification against the target platform based on the connection configuration information in the candidate configuration area. The currently available communication link is usually the maintenance link (because only the maintenance link remains available when the maintenance link becomes unreachable due to configuration failure). The connection reachability verification is a practical test of whether the new configuration is effective. Its purpose is to confirm whether a successful connection to the target platform can indeed be achieved using the new configuration parameters, and whether the connection can be stably maintained for business communication.

[0114] Connectivity reachability verification may include one or more of the following: performing DNS resolution tests on the target platform address to confirm that the domain name can be correctly resolved into an IP address and that the resolution result is reasonable; establishing a transport layer connection (such as a TCP connection) with the target platform to confirm that the target platform's IP address and port are reachable; performing certificate chain verification to confirm that the communication certificate provided by the target platform is valid, issued by a trusted authority, and within its validity period; completing the platform handshake and charging pile authentication process to confirm that the target platform can recognize the device identity of this charging pile and complete two-way authentication; sending a tentative heartbeat message and receiving a heartbeat response to confirm that the application layer communication function is normal and the round-trip latency is within an acceptable range. The above verification process simulates all the steps of establishing and maintaining a communication connection when the charging pile is actually running. If all verifications pass, it indicates that the new configuration is valid and usable.

[0115] Connectivity reachability verification is performed within a preset verification window. The verification window is a preset time period, such as 60 seconds or 120 seconds from the start of verification. During this time period, the charging station performs the above verification steps and monitors its continuous stability. Connectivity reachability verification is considered successful only if preset passing conditions are met consecutively within the verification window. Preset passing conditions may include: successful DNS resolution, successful TCP connection, successful certificate verification, successful platform authentication, and consecutive successful heartbeat responses without timeouts. Requiring consecutive fulfillment rather than single fulfillment is to avoid misjudgments caused by instantaneous network fluctuations—if a failure occurs during verification and is subsequently recovered, and the number of failures within the window does not exceed the preset threshold, it can still be considered a pass; however, if there are continuous failures or multiple intermittent failures, it is considered a failure.

[0116] When the connectivity reachability verification meets the preset pass conditions within the preset verification window, the charging pile will apply the connection configuration information as the current operating configuration, that is, copy or activate it from the candidate configuration area to the current configuration area. The charging pile will then use this configuration to communicate with the target platform. At this point, the configuration update of the operation link is complete, and communication between the charging pile and the operation platform is restored.

[0117] When connection reachability verification fails—for example, DNS resolution timeout, TCP connection rejection, certificate verification failure, platform authentication failure, or heartbeat response timeout—it indicates a problem with the new configuration or that the target platform is currently unreachable. The charging pile will not promote the candidate configuration to the official configuration. In this case, the charging pile discards the configuration information in the candidate configuration area and rolls back to the configuration in the rollback configuration area, restoring the previously known and correct configuration state before the configuration update. The rollback configuration refers to a configuration version stored in the rollback configuration area that was known to be usable before the current configuration update. Through the rollback operation, even if an incorrect configuration is received or the target platform is unavailable, the charging pile can still restore to a previously functional configuration state, preventing the device from becoming completely unable to connect to any platform due to incorrect configuration. After the rollback is complete, the charging pile reports the reason for the failure to the operations and maintenance platform through the currently available communication link (i.e., the operations and maintenance link), including the specific type of failure (such as DNS resolution failure, certificate verification failure, platform authentication failure, etc.) and the time of the failure, for operations and maintenance personnel to analyze and troubleshoot. The operations and maintenance platform can adjust the configuration parameters based on the reason for the failure and then reissue the configuration.

[0118] This invention is also applicable in platform migration scenarios—that is, when a batch of charging piles needs to be switched from an old operating platform to a new operating platform, or when charging piles need to connect to a customer-specified private platform. During platform migration, ongoing charging orders are not interrupted. The charging pile writes the newly added order metering data and control instructions to its local cache, and waits for a connection to the new operating platform before re-transmitting and reconciling the data through the re-transmission mechanism described in the previous embodiments. If the new operating platform needs to continue the order data from the old operating platform, the charging pile can send an order status snapshot (including order number, session number, most recently confirmed transaction number, and current order status, etc.) to the new platform. The new operating platform then uses this information to complete the order continuation or rebuild the data mapping relationship, thereby achieving continuity of charging services and seamless migration of order data during platform switching.

[0119] Through the above configuration update scheme, even when the operation channel becomes completely unreachable due to configuration failure, the present invention can still remotely distribute and update the connection configuration of the operation platform through an independent operation and maintenance channel. Because the configuration update process incorporates multiple protections, including security verification, candidate storage, connection reachability verification, and rollback mechanisms, even if the distributed configuration contains errors or the target platform is temporarily unavailable, the charging pile will not completely go offline due to incorrect configuration, ensuring the security and reliability of remote equipment maintenance.

[0120] The above description is merely an optional embodiment of the present invention and does not limit the patent scope of the present invention. All equivalent structural transformations made using the contents of the present invention's specification and drawings under the inventive concept of the present invention, or direct / indirect applications in other related technical fields, are included within the patent protection scope of the present invention.

Claims

1. A method for collaborative management of charging piles with dual communication links, characterized in that, include: Configure the first communication link and the second communication link, wherein the first communication link carries the operation service by default, and the second communication link carries the maintenance service by default; The communication quality parameters of the two communication links are collected, and the health score of the first communication link and the health score of the second communication link are calculated based on the communication quality parameters. When the health score of any communication link falls below the first threshold, the service carried by that communication link is switched to another communication link, and the service data generated by the charging pile during the link switching is stored, and the data breakpoint is recorded. After a successful switch, the business data from the data breakpoint is retransmitted to the corresponding platform. The retransmitted data carries an identifier for deduplication verification.

2. The charging pile dual communication link collaborative management method as described in claim 1, characterized in that, The process of calculating the health score of the first communication link and the health score of the second communication link respectively includes: When the health score of any communication link is greater than the first threshold and lower than the second threshold for a preset number of sampling periods, a connection to the platform corresponding to that communication link is established through another communication link.

3. The charging pile dual communication link collaborative management method as described in claim 2, characterized in that, The dual communication link collaborative management method for charging piles also includes: If the health score of any communication link is greater than the first threshold and lower than the second threshold for a preset number of sampling periods, and the health score rises to be greater than the second threshold, and the duration of the health score being greater than the second threshold is greater than a preset duration, then the communication link is switched back.

4. The charging pile dual communication link collaborative management method as described in claim 2, characterized in that, The process of calculating the health score of the first communication link and the health score of the second communication link respectively includes: When any of the following events occurs on any communication link: physical connection interruption, no response from the 4G module, or M consecutive failures of the platform heartbeat, the service carried by that communication link is immediately switched to another communication link, and the service data generated by the charging pile during the link switching is stored, and the data breakpoint is recorded; where M is a preset positive integer.

5. The charging pile dual communication link collaborative management method as described in any one of claims 1 to 4, characterized in that, The dual-communication collaborative management method for charging piles also includes: The business is divided into real-time control business, billing key data business, keep-alive and status reporting business, and batch data transmission business. When the health score of any communication link falls below a first threshold, the service carried by that communication link is switched to another communication link, including: If the health score of the first communication link is lower than the first threshold, the second communication link is used to establish a connection with the operation platform, and real-time control operation business and billing key data operation business are switched to the second communication link for uploading, while the operation and maintenance business of suspension or rate limit keep-alive and status reporting is suspended. If the health score of the second communication link is lower than the first threshold, the first communication link is used to establish a connection with the operation and maintenance platform, and real-time control operation and maintenance services and / or billing critical data operation and maintenance services are switched to the first communication link for uploading.

6. The charging pile dual communication link collaborative management method as described in claim 5, characterized in that, Real-time control functions include: starting charging, stopping charging, emergency stop, remote control command confirmation, and confirmation of critical order status. Key billing data includes: order metering records, charging status, billing settlement, payment results, and critical alarms; Keep-alive and status reporting services include: general status reporting, periodic heartbeat, device parameters, non-emergency alarms, and operation and maintenance command results; Batch data transfer services include: log files, diagnostic packages, historical data retransmission, firmware upgrade package download, and file upload.

7. The charging pile dual communication link collaborative management method as described in any one of claims 1 to 4, characterized in that, The service data generated by the charging pile during the storage link switchover is recorded, including data breakpoints: Based on the business data generated by charging piles during link switching, maintain the order cache table, metering flow table, instruction confirmation table, and retransmission team list; When a link switch occurs, record the last sequence number confirmed by the corresponding platform and use the last sequence number as the data breakpoint. The process of retransmitting the business data after the data breakpoint to the corresponding platform includes: Send an order status snapshot to the corresponding platform; Receive missing transaction interval information sent by the platform based on the order status snapshot; The service data is retransmitted in the order of the sequence number in the missing sequence interval information.

8. The charging pile dual communication link collaborative management method as described in any one of claims 1 to 4, characterized in that, The dual communication link collaborative management method for charging piles also includes: Collect radio frequency parameters and transmission status parameters of the two communication links; When it is determined, based on the radio frequency parameters and transmission status parameters, that there is a risk of mutual interference between two communication links, at least one of the following anti-interference operations shall be performed: Perform time-sharing transmission scheduling on non-real-time services on at least one communication link to stagger the services on different communication links in time. Adjust the transmission power of at least one communication link; Control the two communication links to prevent them from performing batch data transmission tasks simultaneously.

9. The charging pile dual communication link collaborative management method as described in any one of claims 1 to 4, characterized in that, The dual communication link collaborative management method for charging piles also includes: Maintain the resource status information of the traffic tariff accounts corresponding to the two communication links respectively; The resource pressure value for each traffic tariff account is determined based on the resource status information. When the resource pressure value of any traffic tariff account exceeds the preset pressure threshold, the non-real-time services on that communication link are rerouted to another communication link for transmission.

10. The charging pile dual communication link collaborative management method as described in any one of claims 1 to 4, characterized in that, The dual communication link collaborative management method for charging piles also includes: Receive configuration update instructions from the operation and maintenance platform through the currently available communication link. The configuration update instructions contain the connection configuration information of the target platform. Perform security verification on the configuration update command; After successful verification, the connection configuration information is stored in a non-currently active configuration storage area; Using the currently available communication link, perform a connection reachability verification on the target platform based on the connection configuration information; When the connection reachability verification meets the preset pass conditions within the preset verification window, the current running configuration is adjusted based on the connection configuration information. The configuration is rolled back when the connection reachability verification fails or a connection anomaly occurs within a preset rollback window starting from when the connection configuration information takes effect.

Images