Charging protocol loading method, charging equipment and computer readable storage medium

Abstract

The invention provides a charging protocol loading method, charging equipment and a computer readable storage medium, and belongs to the technical field of automobile charging. Wherein the configuration information of the charging management cloud platform is acquired, and the configuration information at least comprises a cloud platform identifier, a cloud platform protocol, a cloud platform domain name and a cloud platform port; validity verification is conducted on the configuration information, communication protocol parameters to be loaded are determined based on the verification result of the configuration information and a preset protocol mapping list, the communication protocol parameters to be loaded comprise protocol loading functions and network parameters, and the protocol loading functions comprise target / reference protocol loading functions; the network parameters comprise target / reference network parameters; loading a target communication protocol according to the to-be-loaded communication protocol parameter, and creating a protocol instance based on the target communication protocol; and communicating with a charging management cloud platform based on the protocol instance. According to the application, the effects of realizing automatic identification and compatibility of various communication protocols and reducing the deployment cost of the charging pile can be achieved.

Description

Technical Field

[0001] This application relates to the field of automotive charging technology, and more specifically, to a charging protocol loading method, a charging device, and a computer-readable storage medium. Background Technology

[0002] With the rapid development of the electric vehicle industry, charging piles, as key infrastructure, have received much attention for their intelligence and network communication capabilities. However, in practical applications, charging management cloud platforms used by different regions and operators often follow different communication protocol standards. This situation of multiple protocols coexisting places higher demands on the protocol compatibility of charging piles.

[0003] In related technologies, the protocol compatibility problem of charging piles is often solved in the following two ways. The first way is to deploy a protocol adapter in the charging management cloud platform to achieve unified management of different communication protocols. The second way is to open multiple transmission control protocol (TCP) ports on the charging management cloud platform, and charging piles compatible with different communication protocols can choose to connect to different TCP ports to achieve information interaction between the charging pile and the charging management cloud platform.

[0004] However, when addressing protocol compatibility issues with charging piles using relevant technologies, if the protocols supported by the charging management cloud platform malfunction, the charging piles, lacking the ability to autonomously identify and switch protocols, cannot respond promptly, rendering them unusable and severely impacting the user's charging experience. Furthermore, as the variety of communication protocols increases, the deployment cost and maintenance complexity of the charging management cloud platform also rise significantly. Moreover, if the charging management cloud platform suspends support for a particular communication protocol when the charging pile lacks autonomous protocol identification capabilities, all charging piles relying on that protocol will immediately become unusable. Therefore, the solutions mentioned in the relevant technologies suffer from over-reliance on the charging management cloud platform. Summary of the Invention

[0005] The purpose of this application is to provide a charging protocol loading method, a charging device, and a computer-readable storage medium, which can achieve automatic identification and compatibility of multiple communication protocols and reduce the deployment cost of charging piles.

[0006] The embodiments of this application are implemented as follows: A first aspect of this application provides a charging protocol loading method, which is applied to a charging device, and the method includes: Obtain the configuration information of the charging management cloud platform. The configuration information includes at least: cloud platform identifier, cloud platform protocol, cloud platform domain name, and cloud platform port. The configuration information is validated, and based on the validation results and the preset protocol mapping list, the communication protocol parameters to be loaded are determined. The communication protocol parameters to be loaded include: protocol loading function and network parameters. The protocol loading function includes: target protocol loading function or reference protocol loading function, and the network parameters include: reference network parameters or target network parameters. Load the target communication protocol based on the parameters of the communication protocol to be loaded, and create a protocol instance based on the target communication protocol; It communicates with the charging management cloud platform based on protocol instances.

[0007] As one possible implementation, the configuration information is validated, including: Determine if the cloud platform identifier in the configuration information is valid; If not, then determine whether the cloud platform protocol in the configuration information is valid, and whether the cloud platform domain name and cloud platform port in the configuration information are valid.

[0008] As one possible implementation, based on the verification results of the configuration information and a preset protocol mapping list, the parameters of the communication protocol to be loaded are determined, including: If the verification result of the cloud platform identifier in the configuration information is valid, the target protocol mapping relationship is searched in the preset protocol mapping list based on the cloud platform identifier, and the target protocol loading function and reference network parameters are determined according to the target protocol mapping relationship. The reference network parameters include: reference domain name and reference port. If the verification result of the cloud platform identifier in the configuration information is invalid, then based on the verification results of the cloud platform protocol, cloud platform domain name and cloud platform port in the configuration information, the target protocol mapping relationship is searched in the preset protocol mapping list, and the protocol loading function and network parameters are determined according to the target protocol mapping relationship.

[0009] As one possible implementation, based on the verification results of the cloud platform protocol, cloud platform domain name, and cloud platform port in the configuration information, the target protocol mapping relationship is searched in a preset protocol mapping list. Then, based on the target protocol mapping relationship, the protocol loading function and network parameters are determined, including: If the cloud platform protocol in the configuration information is valid, the target protocol mapping relationship is searched in the preset protocol mapping list based on the cloud platform protocol, and the target protocol loading function and network parameters are determined according to the target protocol mapping relationship and the verification results of the cloud platform domain name and cloud platform port in the configuration information. If the cloud platform protocol in the configuration information is invalid, the target protocol mapping relationship is searched in the preset protocol mapping list based on the verification results of the cloud platform domain name and cloud platform port in the configuration information, and the protocol loading function and network parameters are determined according to the target protocol mapping relationship.

[0010] As one possible implementation, based on the target protocol mapping relationship and the verification results of the cloud platform domain name and cloud platform port in the configuration information, the target protocol loading function and network parameters are determined, including: If the cloud platform domain name and cloud platform port in the configuration information are valid, then the target protocol loading function and target network parameters are determined according to the target protocol mapping relationship. The target network parameters include: cloud platform domain name and cloud platform port. If the cloud platform domain name and cloud platform port in the configuration information are invalid, then the target protocol loading function and reference network parameters are determined according to the target protocol mapping relationship.

[0011] As one possible implementation, based on the verification results of the cloud platform domain name and cloud platform port in the configuration information, the target protocol mapping relationship is searched in a preset protocol mapping list, and the protocol loading function and network parameters are determined according to the target protocol mapping relationship, including: If the cloud platform domain name and cloud platform port in the configuration information are valid, then based on the cloud platform domain name and cloud platform port, the target protocol mapping relationship is searched in the preset protocol mapping list, and the target protocol loading function and target network parameters are determined according to the target protocol mapping relationship. If the cloud platform domain name and cloud platform port in the configuration information are invalid, the reference protocol mapping relationship will be searched in the preset protocol mapping list, and the reference protocol loading function and reference network parameters will be determined based on the reference protocol mapping relationship.

[0012] As one possible implementation, the above protocol mapping list includes: multiple protocol mapping relationships, each represented by structured data, and each protocol mapping relationship includes: cloud platform identifier, communication protocol type, reference domain name, reference port, and corresponding protocol loading function.

[0013] As one possible implementation, the above charging protocol loading method also includes: Add protocol instances to the protocol instance pool so that charging devices can communicate in parallel with multiple charging management cloud platforms based on the protocol instances in the pool.

[0014] A second aspect of this application provides a charging device, the charging device comprising: The configuration acquisition module is used to obtain the configuration information of the charging management cloud platform. The configuration information includes at least: cloud platform identifier, cloud platform protocol, cloud platform domain name, and cloud platform port. The automatic identification module is used to verify the validity of the configuration information and, based on the verification result of the configuration information and the preset protocol mapping list, determine the communication protocol parameters to be loaded. The communication protocol parameters to be loaded include: protocol loading function and network parameters. The protocol loading function includes: target protocol loading function and reference protocol loading function. The network parameters include: reference network parameters or target network parameters. The protocol loading module is used to load the target communication protocol according to the parameters of the communication protocol to be loaded, and to create a protocol instance based on the target communication protocol; The protocol execution module is used to communicate with the charging management cloud platform based on the protocol instance.

[0015] A third aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the charging protocol loading method described in the first aspect.

[0016] The beneficial effects of the embodiments of this application include: This application provides a charging protocol loading method. It obtains the configuration information of a charging management cloud platform and verifies the validity of the cloud platform identifier, cloud platform protocol, cloud platform domain name, and cloud platform port. Based on the verification result, it searches for the communication protocol parameters to be loaded from a pre-written protocol mapping list in the charging device. Based on these parameters, it loads the corresponding target communication protocol and creates a protocol instance. The charging device then communicates with the charging management cloud platform using the protocol instance. The charging device can autonomously read the basic configuration information of the charging management cloud platform it communicates with and actively verify the validity of this information. Based on the verification result, it flexibly selects appropriate protocol loading functions and network parameters. Therefore, the communication protocol switching of the charging device no longer depends on the hardware of the charging management cloud platform. Even if the charging management cloud platform stops supporting a certain type of communication protocol, the charging device can adaptively call the corresponding communication protocol for communication. This achieves automatic identification and compatibility of multiple communication protocols and reduces the deployment cost of charging piles. Attached Figure Description

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

[0018] Figure 1 This application provides a communication scenario diagram for a charging device. Figure 2 A flowchart illustrating the first charging protocol loading method provided in this application embodiment; Figure 3 A flowchart illustrating the second charging protocol loading method provided in this application embodiment; Figure 4 A flowchart illustrating the third charging protocol loading method provided in this application embodiment; Figure 5 A flowchart illustrating the fourth charging protocol loading method provided in this application embodiment; Figure 6 A flowchart illustrating the fifth charging protocol loading method provided in this application embodiment; Figure 7 A flowchart of the sixth charging protocol loading method provided in the embodiments of this application; Figure 8 This is a schematic diagram of the structure of a protocol mapping list provided in an embodiment of this application; Figure 9 This is a schematic diagram of a protocol mapping relationship provided in an embodiment of this application; Figure 10 This is a schematic diagram of the structure of a charging device provided in an embodiment of this application.

[0019] Reference numerals: 10: Charging equipment; 20: Charging management cloud platform; 101: Configuration acquisition module; 102: Automatic identification module; 103: Protocol loading module; 104: Protocol execution module. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0021] Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0022] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0023] Currently, the protocol compatibility issue of charging piles is typically addressed in two ways. The first is to deploy protocol adapters within the charging management cloud platform to achieve unified management of different communication protocols. The second is to set up multiple TCP ports within the charging management cloud platform, allowing charging piles supporting different communication protocols to connect to the corresponding TCP port, thus enabling information exchange between charging piles using different communication protocols and the charging management cloud platform. However, both of these solutions suffer from over-reliance on the charging management cloud platform and its high deployment cost.

[0024] To address this, this application provides a charging protocol loading method. The method involves the charging device actively acquiring configuration information from a charging management cloud platform with which it communicates, and verifying the validity of the acquired configuration information. Based on the verification result of the configuration information and a preset protocol mapping list, the method automatically identifies the parameters of the communication protocol to be loaded. Based on these parameters, the method loads the target communication protocol and creates a protocol instance. The device then engages in bidirectional communication with the charging management cloud platform based on this protocol instance. Specifically, the charging device automatically identifies the configuration information of the charging management cloud platform and adaptively adjusts the communication protocol and network parameters between the charging device and the charging management cloud platform to ensure continuous and normal communication. This approach achieves automatic identification and compatibility of multiple communication protocols and reduces the deployment cost of charging piles.

[0025] The charging protocol loading method provided in the embodiments of this application will be explained in detail below with reference to the accompanying drawings.

[0026] Figure 1 A communication scenario diagram of a charging device provided in this application is shown in the attached diagram. Figure 1 The charging device 10 provided in this application embodiment can communicate with multiple charging management cloud platforms 20 simultaneously, and the information interaction between the charging device 10 and each charging management cloud platform 20 is independent of each other.

[0027] The communication protocol types supported by each charging management cloud platform 20 may differ due to differences in manufacturers or operators. However, the charging device 10 provided in this application has an automatic protocol identification function, which can autonomously read the configuration information of each charging management cloud platform 20 with which it communicates, and autonomously determine whether the configuration information of each charging management cloud platform 20 is valid. Based on the determination result of the configuration information of each charging management cloud platform 20, the charging device 10 determines the communication protocol parameters between the charging device 10 and each charging management cloud platform 20. The charging device 10 autonomously loads the corresponding communication protocol based on the communication protocol parameters and creates a corresponding communication instance to realize communication between the charging device 10 and the charging management cloud platform 20.

[0028] It should be noted that the communication between the charging management cloud platform 20 and the charging device 10 is the foundation for the construction of the intelligent charging network. Specifically, the charging management cloud platform 20 can obtain real-time data on the charging device 10's operating status (such as idle status, charging status, online status, offline status, etc.), operating parameters (such as voltage, current, power, temperature, etc.), and alarm information (such as overload, emergency stop, network interruption, etc.) through remote wireless communication, enabling operators to remotely monitor the health status of the charging device 10. The charging management cloud platform 20 can also send control commands to the charging device 10 via remote wireless communication to control actions such as starting, stopping, or restarting charging. It can also adjust the output power of the charging device 10 through control commands and control the charging device 10 to perform firmware upgrades, etc., though this application does not specifically limit these actions.

[0029] Furthermore, the charging device 10 can also wirelessly upload data such as the amount of electricity generated during its charging process, charging time, and charging rate to the charging management cloud platform 20 connected to it in real time. The charging management cloud platform 20 then performs services such as billing and order generation. The charging management cloud platform 20 is also connected to the payment gateway so that it can interact with the payment gateway based on the charging order to complete the user's charging payment.

[0030] In addition, during peak grid load periods, the charging management cloud platform 20 can uniformly schedule multiple charging devices 10 connected to it according to grid instructions or preset charging strategies, so as to reduce the charging power of the charging devices 10 and achieve "peak shaving and valley filling".

[0031] It should also be noted that the charging management cloud platform 20 can upload all data generated by the charging devices 10 (charging usage time, power consumption, user charging habits, and fault records, etc.) to the cloud. The cloud analyzes this data to optimize the address and utilization of the charging devices 10.

[0032] Optionally, the charging device 10 is a basic physical device used to realize power conversion and on-site interaction. Specifically, it converts the AC power from the power grid into the charging signal required by the battery in the electric vehicle to charge the electric vehicle safely and stably. The controller built into the charging device 10 is used to realize local control and safety protection. Specifically, it is responsible for executing the charging process, monitoring electrical parameters in real time, and immediately executing local power-off protection in case of abnormalities such as overcurrent, overvoltage, leakage, and overheating to achieve safety protection.

[0033] Furthermore, as an IoT terminal, the charging device 10 can collect its own status data, charging data, alarm information, etc., and upload them to the charging management cloud platform 20 via wireless communication technology. Simultaneously, the charging device 10 can also receive and execute control commands issued by the charging management cloud platform 20.

[0034] Figure 2 A flowchart of a charging protocol loading method provided in this application is provided. This method can be applied to... Figure 1 The charging device 10 shown can be either a DC charging pile or an AC charging pile; this application does not specifically limit its use. See also Figure 2 This application provides a charging protocol loading method, including: S201. Obtain the configuration information of the charging management cloud platform. The configuration information shall include at least the cloud platform identifier, cloud platform protocol, cloud platform domain name, and cloud platform port.

[0035] Optionally, the configuration information of the charging management cloud platform refers to the communication parameters preset for the charging management cloud platform itself and the charging devices it manages. Specifically, the configuration information includes: cloud platform identifier, cloud platform protocol, cloud platform domain name, and cloud platform port. The cloud platform identifier is the identity identifier of the charging management cloud platform. Each charging management cloud platform has a unique and definite identifier. Specifically, the cloud platform identifier can be the name of the charging management cloud platform or its identification number; this application does not impose specific limitations on this.

[0036] Furthermore, the cloud platform protocol refers to the communication protocol supported by the charging management cloud platform. Specifically, the cloud platform protocol refers to the name or type of the communication protocol supported by the charging management cloud platform; the cloud platform domain name refers to the server address of the charging management cloud platform; and the cloud platform port refers to the virtual channel number for communication between the charging management cloud platform and the charging equipment. Each charging management cloud platform can provide different service protocols through different ports.

[0037] It is worth noting that the configuration information determines the communication method and communication strategy of the charging management cloud platform.

[0038] Specifically, the charging device obtains the pre-set configuration information from the storage medium of the charging management cloud platform via wireless communication technology.

[0039] S202. Verify the validity of the configuration information, and based on the verification result of the configuration information and the preset protocol mapping list, determine the communication protocol parameters to be loaded. The communication protocol parameters to be loaded include: protocol loading function and network parameters. The protocol loading function includes: target protocol loading function or reference protocol loading function, and the network parameters include: reference network parameters or target network parameters.

[0040] Optionally, the charging device verifies the validity of the collected configuration information of the charging management cloud platform to determine whether the cloud platform identifier, the communication protocols supported by the cloud platform, the cloud platform domain name, and the cloud platform port are valid. Specifically, the verification result of the charging management cloud platform configuration information indicates whether the cloud platform identifier, the communication protocols supported by the cloud platform, the cloud platform domain name, and the cloud platform port are valid.

[0041] Optionally, the preset protocol mapping list is a communication protocol mapping list pre-set by the user. The preset protocol mapping list is specifically used to indicate the mapping relationship between the charging management cloud platform and various types of communication protocols, server domain names, and ports.

[0042] Optionally, based on the validity verification result of the configuration information of the charging management cloud platform with which it communicates, the charging device searches for list parameters that match the validity verification result from a preset protocol mapping list, thereby determining the communication protocol required for reliable communication between the charging management cloud platform and the charging device, and thus determining the communication protocol parameters to be loaded.

[0043] Among them, the communication protocol parameters to be loaded refer to the parameters corresponding to the communication protocol that the charging device finds from the preset protocol mapping table based on the validity verification result of the configuration information of the charging management cloud platform with which it communicates.

[0044] Optionally, the communication protocol parameters to be loaded include a protocol loading function, which is a software call function that loads a specific communication protocol. This protocol loading function can be either a target protocol loading function or a reference protocol loading function, determined by the validity verification result of the charging management cloud platform's configuration information. When any one of the cloud platform identifier, cloud platform protocol, cloud platform domain name, and port in the charging management cloud platform's configuration information is valid, the protocol loading function is the target protocol loading function configured by the charging management cloud platform. Conversely, when all three are invalid, the protocol loading function is the reference protocol loading function configured by the charging management cloud platform.

[0045] It is worth noting that the target protocol loading function refers to the software loading function of the cloud platform protocol pre-written in the storage medium of the charging management cloud platform, while the reference protocol loading function refers to the software loading function of the default communication protocol of the charging device to ensure stable communication with the charging management cloud platform.

[0046] Optionally, the communication protocol parameters to be loaded also include network parameters. Network parameters refer to basic communication parameters such as the server address and network port used by the charging management cloud platform to communicate with the charging device. These network parameters can be target network parameters or reference network parameters, determined by the validity verification result of the charging management cloud platform's configuration information. When the cloud platform domain name and port in the charging management cloud platform's configuration information are valid, the network parameters are the target network parameters pre-written by the charging management cloud platform; conversely, when the cloud platform domain name and port in the charging management cloud platform's configuration information are invalid, the network parameters are the reference network parameters pre-configured by the charging device for the charging management cloud platform.

[0047] It is worth noting that the target network parameters refer to the cloud platform domain name and cloud platform port pre-written in the storage medium of the charging management cloud platform, while the reference network parameters refer to the default server domain name and default network port of the charging device to ensure stable communication with the charging management cloud platform.

[0048] It should be noted that when all configuration information of the charging management cloud platform is valid, that is, when the cloud platform identifier, cloud platform protocol, cloud platform domain name, and cloud platform port of the charging management cloud platform are all valid, the communication protocol parameters to be loaded by the charging device from the preset protocol mapping list will be completely consistent with the cloud platform protocols supported by the charging management cloud platform; when all configuration information of the charging management cloud platform is invalid, that is, when the cloud platform identifier, cloud platform protocol, cloud platform domain name, and cloud platform port of the charging management cloud platform are all invalid, the communication protocol parameters to be loaded by the charging device from the preset protocol mapping list will be the default protocol parameters.

[0049] It should also be noted that the purpose of the charging device verifying the configuration information of the charging management cloud platform is to determine whether the current firmware of the charging device supports the basic configuration of the charging management cloud platform. At the same time, it is also used to determine whether the domain name and port of the charging management cloud platform conform to the communication standard of the cloud platform protocol, thereby ensuring the reliability of communication between the charging management cloud platform and the charging device.

[0050] S203. Load the target communication protocol according to the parameters of the communication protocol to be loaded, and create a protocol instance based on the target communication protocol.

[0051] Optionally, the charging device invokes the target communication protocol based on the found communication protocol parameters to be loaded, and creates a protocol instance based on the target communication protocol. The target communication protocol can be either a cloud platform protocol or the charging device's default communication protocol; this application does not impose any specific limitations on this.

[0052] Specifically, a protocol instance refers to an independent running object created by a charging device according to the target communication protocol to carry specific charging status, session data, and business logic. Each charging device connected to the charging management cloud platform corresponds to an independent protocol instance to enable normal communication between the charging device and the charging management cloud platform.

[0053] S204. Communicate with the charging management cloud platform based on protocol instances.

[0054] Optionally, the charging device communicates with the charging management cloud platform via a protocol instance under the action of the target communication protocol.

[0055] In this embodiment, the configuration information of the charging management cloud platform is obtained, and the validity of the cloud platform identifier, cloud platform protocol, cloud platform domain name, and cloud platform port in the configuration information is verified. Based on the validity verification result of the charging management cloud platform's configuration information, the communication protocol parameters to be loaded are searched from the protocol mapping list pre-written in the charging device. Based on the communication protocol parameters to be loaded, the corresponding target communication protocol is loaded, and a protocol instance is created based on the target communication protocol. The charging device communicates with the charging management cloud platform based on the protocol instance. The charging device can autonomously read the basic configuration information of the charging management cloud platform it communicates with, and actively judge the validity of the configuration information of the charging management cloud platform. Based on the verification result of the configuration information of the charging management cloud platform, it flexibly selects the appropriate protocol loading function and network parameters. Therefore, the communication protocol switching of the charging device no longer depends on the hardware facilities of the charging management cloud platform. Even if the charging management cloud platform stops supporting a certain type of communication protocol, the charging device can adaptively call the corresponding communication protocol for communication. This achieves the effect of automatic identification and compatibility of multiple communication protocols and reduces the deployment cost of charging piles.

[0056] In one alternative implementation, see [link to implementation details]. Figure 3 The operation of "validating the configuration information" in step S202 above can be specifically as follows: S301. Determine whether the cloud platform identifier in the configuration information is valid.

[0057] Optionally, it can be determined whether the pre-allocated unique identifier in the storage medium of the charging management cloud platform is valid, so as to determine whether the current firmware of the charging device can support the communication of the charging management cloud platform.

[0058] S302. If not, determine whether the cloud platform protocol in the configuration information is valid, and determine whether the cloud platform domain name and cloud platform port in the configuration information are valid.

[0059] Optionally, when the charging device determines that the cloud platform identifier in the configuration information of the charging management cloud platform is invalid, it further determines whether the cloud platform protocol in the configuration information of the charging management cloud platform is valid. At the same time, it is also necessary to determine whether the cloud platform domain name and cloud platform port in the configuration information of the charging management cloud platform are valid.

[0060] In one alternative implementation, see [link to implementation details]. Figure 4 The operation of "determining the communication protocol parameters to be loaded based on the verification results of the configuration information and the preset protocol mapping list" in step S202 above can be specifically as follows: S401. If the verification result of the cloud platform identifier in the configuration information is valid, then the target protocol mapping relationship is searched in the preset protocol mapping list based on the cloud platform identifier, and the target protocol loading function and reference network parameters are determined according to the target protocol mapping relationship. The reference network parameters include: reference domain name and reference port.

[0061] The verification result of the cloud platform identifier being valid means that the identifier of the charging management cloud platform has existed and been enabled in the cloud platform database, the key or token provided by the charging management cloud platform is correct and has not expired, and the device status of the charging management cloud platform corresponding to the cloud platform identifier is that it allows access to the charging device, etc. This application does not make specific limitations on this.

[0062] Optionally, if the charging device determines that the cloud platform identifier in the configuration information of the charging management cloud platform is valid, it means that the charging device can communicate with the charging management cloud platform based on the cloud platform identifier. The charging device searches for the target protocol mapping relationship corresponding to the cloud platform identifier in the protocol mapping list built into the charging device, and determines the target protocol loading function and reference network parameters based on the target protocol mapping relationship. The reference network parameters include: a default server domain name and a default communication port.

[0063] It is worth noting that the target protocol mapping relationship refers to the protocol mapping relationship that matches the cloud platform identifier of the charging management cloud platform. The target protocol loading function in the target protocol mapping relationship refers to the communication protocol supported by the charging management cloud platform corresponding to the identifier.

[0064] S402. If the verification result of the cloud platform identifier in the configuration information is invalid, then based on the verification results of the cloud platform protocol, cloud platform domain name and cloud platform port in the configuration information, the target protocol mapping relationship is searched in the preset protocol mapping list, and the protocol loading function and network parameters are determined according to the target protocol mapping relationship.

[0065] The invalid verification result of the cloud platform identifier means that the identifier of the charging management cloud platform is not used or registered, the cloud platform identifier is disabled on the charging management cloud platform, or the password or key provided by the charging management cloud platform is incorrect. In this case, although the charging management cloud platform can successfully establish a network connection and protocol handshake with the charging device, it is rejected by the charging management cloud platform during the identity authentication stage, and the charging management cloud platform actively disconnects from the charging device.

[0066] Optionally, if the charging device determines that the cloud platform identifier in the configuration information of the charging management cloud platform is invalid, it means that the charging device cannot communicate with the charging management cloud platform based on the cloud platform identifier. The charging device needs to further determine whether the cloud platform protocol, cloud platform domain name and cloud platform port of the charging management cloud platform are valid, and based on the verification results of the cloud platform protocol, cloud platform domain name and cloud platform port, search for the target protocol mapping relationship corresponding to the cloud platform protocol and / or cloud platform domain name and port in the protocol mapping list built into the charging device, and determine the protocol loading function and network parameters based on the target protocol mapping relationship.

[0067] In one alternative implementation, see [link to implementation details]. Figure 5 The operation in step S402 above, which involves "based on the verification results of the cloud platform protocol, cloud platform domain name, and cloud platform port in the configuration information, searching for the target protocol mapping relationship in the preset protocol mapping list, and determining the protocol loading function and network parameters according to the target protocol mapping relationship," can be specifically described as follows: S501. If the cloud platform protocol in the configuration information is valid, then search for the target protocol mapping relationship in the preset protocol mapping list based on the cloud platform protocol, and determine the target protocol loading function and network parameters according to the target protocol mapping relationship and the verification results of the cloud platform domain name and cloud platform port in the configuration information.

[0068] The verification result of the cloud platform protocol being valid means that the communication protocol built into the charging management cloud platform is completely matched with the communication protocol expected and supported by the charging device on the cloud platform port, and the charging device and the charging management cloud platform can successfully handshake on the cloud platform port in accordance with the cloud platform protocol.

[0069] Optionally, if the charging device determines that the cloud platform identifier in the configuration information of the charging management cloud platform is invalid, but the cloud platform protocol in the configuration information of the charging management cloud platform is valid, it means that the charging device can communicate with the charging management cloud platform based on the cloud platform protocol. The charging device searches for the target protocol mapping relationship corresponding to the cloud platform protocol in the protocol mapping list built into the charging device according to the cloud platform protocol, and selects the target protocol loading function and network parameters from the target protocol mapping relationship based on the validity verification results of the cloud platform domain name and cloud platform port in the configuration information of the charging management cloud platform.

[0070] S502. If the cloud platform protocol in the configuration information is invalid, then based on the verification results of the cloud platform domain name and cloud platform port in the configuration information, the target protocol mapping relationship is searched in the preset protocol mapping list, and the protocol loading function and network parameters are determined according to the target protocol mapping relationship.

[0071] The invalid verification result of the cloud platform protocol refers to situations where the communication protocol supported by the cloud platform port provided by the charging management cloud platform to the charging device is incompatible with the cloud platform protocol pre-written by the charging management cloud platform, the version of the cloud platform protocol built into the charging management cloud platform is incompatible with the communication protocol used by the charging device, or the data format of the cloud platform protocol built into the charging management cloud platform is incorrect. These situations will lead to handshake failure or data interaction failure between the charging device and the charging management cloud platform. This application does not make specific limitations on these situations.

[0072] Optionally, if the charging device determines that the cloud platform identifier in the configuration information of the charging management cloud platform is valid, but the cloud platform protocol in the configuration information of the charging management cloud platform is invalid, then it continues to determine whether the cloud platform domain name and cloud platform port in the configuration information of the charging management cloud platform are valid. Based on the verification results of the cloud platform domain name and cloud platform port in the configuration information of the charging management cloud platform, it searches for the target protocol mapping relationship corresponding to the cloud platform identifier in the protocol mapping list built into the charging device, and determines the protocol loading function and network parameters based on the target protocol mapping relationship.

[0073] In one alternative implementation, see [link to implementation details]. Figure 6 The operation in step S501 above, "determining the target protocol loading function and network parameters based on the target protocol mapping relationship and the verification results of the cloud platform domain name and cloud platform port in the configuration information," can be specifically described as follows: S601. If the cloud platform domain name and cloud platform port in the configuration information are valid, then determine the target protocol loading function and target network parameters according to the target protocol mapping relationship. The target network parameters include: cloud platform domain name and cloud platform port.

[0074] The verification result of the cloud platform domain name being valid means that the cloud platform domain name can be correctly resolved to the public Internet Protocol (IP) address of one or more servers, and the server corresponding to the IP address is running and the network is reachable. In other words, the charging device can successfully initiate a TCP / IP connection to the charging management cloud platform. This application does not make specific limitations on this.

[0075] Furthermore, a valid verification result for the cloud platform port means that the port number of the charging management cloud platform is within a legal range (usually between 1 and 65535, with fixed ports for common services), and the charging management cloud platform can listen to the expected service between the charging device and the charging management cloud platform on this port.

[0076] Optionally, if the charging device determines that the cloud platform identifier in the configuration information of the charging management cloud platform is invalid, but the cloud platform protocol in the configuration information of the charging management cloud platform is valid, and the cloud platform domain name and cloud platform port in the configuration information of the charging management cloud platform are also valid, then the charging device searches for the target protocol mapping relationship corresponding to the configuration information in the protocol mapping list built into the charging device according to the cloud platform identifier, cloud platform protocol, cloud platform domain name and cloud platform port, so as to select the target protocol loading function and target network parameters according to the target protocol mapping relationship.

[0077] S602. If the cloud platform domain name and cloud platform port in the configuration information are invalid, then determine the target protocol loading function and reference network parameters according to the target protocol mapping relationship.

[0078] The invalid verification result of the cloud platform domain name means that the cloud platform domain name resolution failed (such as the cloud platform domain name is misspelled, the domain name service provider is malfunctioning, the domain name record is deleted, etc.). In other words, the internal network IP configured by the charging management cloud platform is incorrect, has been reclaimed, or has been blocked by the firewall of the network where the server is located. Specifically, it manifests as connection timeout or network unreachable. At this time, the charging device cannot establish a communication connection with the charging management cloud platform.

[0079] Furthermore, an invalid verification result for the cloud platform port means that the port number of the charging management cloud platform is incorrect (e.g., the charging management cloud platform is configured with a port that the server does not provide services for) or that the cloud platform port is closed or blocked. This application does not make specific limitations on this.

[0080] Optionally, if the charging device determines that the cloud platform identifier in the configuration information of the charging management cloud platform is invalid, but the cloud platform protocol in the configuration information of the charging management cloud platform is valid, and the cloud platform domain name and cloud platform port in the configuration information of the charging management cloud platform are both invalid, then the charging device searches for the target protocol mapping relationship corresponding to the configuration information in the protocol mapping list built into the charging device according to the cloud platform protocol, so as to select the target protocol loading function and reference network parameters according to the target protocol mapping relationship.

[0081] In one alternative implementation, see [link to implementation details]. Figure 7 The operation in step S502 above, which involves "finding the target protocol mapping relationship in the preset protocol mapping list based on the verification results of the cloud platform domain name and cloud platform port in the configuration information, and determining the protocol loading function and network parameters according to the target protocol mapping relationship," can be specifically described as follows: S701. If the cloud platform domain name and cloud platform port in the configuration information are valid, then based on the cloud platform domain name and cloud platform port, search for the target protocol mapping relationship in the preset protocol mapping list, and determine the target protocol loading function and target network parameters according to the target protocol mapping relationship.

[0082] Optionally, if the charging device determines that the cloud platform identifier in the configuration information of the charging management cloud platform is invalid, and the cloud platform protocol in the configuration information of the charging management cloud platform is invalid, but the cloud platform domain name and cloud platform port in the configuration information of the charging management cloud platform are both valid, then the charging device searches for the target protocol mapping relationship corresponding to the cloud platform domain name and cloud platform port in the protocol mapping list built into the charging device according to the cloud platform domain name and cloud platform port, and determines the target protocol loading function and target network parameters based on the target protocol mapping relationship.

[0083] S702. If the cloud platform domain name and cloud platform port in the configuration information are invalid, then search for the reference protocol mapping relationship in the preset protocol mapping list, and determine the reference protocol loading function and reference network parameters based on the reference protocol mapping relationship.

[0084] Optionally, if the charging device determines that the cloud platform identifier in the configuration information of the charging management cloud platform is invalid, the cloud platform protocol in the configuration information of the charging management cloud platform is invalid, and the cloud platform domain name and cloud platform port in the configuration information of the charging management cloud platform are both invalid, then the charging device directly calls the reference protocol mapping relationship in the protocol mapping list built into the charging device, and determines the reference protocol loading function and reference network parameters based on the reference protocol mapping relationship.

[0085] In one alternative implementation, see [link to implementation details]. Figure 8 and Figure 9 The protocol mapping list provided in this application includes multiple protocol mapping relationships. Each protocol mapping relationship is represented by structured data and includes: cloud platform identifier, communication protocol type, reference domain name, reference port and corresponding protocol loading function.

[0086] Optionally, the protocol mapping list provided in this application includes multiple protocol mapping relationships. Each protocol mapping relationship is used to characterize the communication relationship between the charging management cloud platform and the charging device. Each protocol mapping relationship includes: cloud platform identifier, communication protocol type, reference domain name, reference port, and corresponding protocol loading function. Here, the cloud platform identifier refers to the name of the charging management cloud platform that communicates with the charging device; the communication protocol type refers to the type of communication protocol currently supported by the charging management cloud platform corresponding to the cloud platform identifier; the reference domain name refers to the default server domain name of the charging management cloud platform; the reference port refers to the default communication port of the charging management cloud platform; and the corresponding protocol loading function indicates the software loading function of the communication protocol in the protocol mapping relationship.

[0087] In an optional implementation, the charging protocol loading method provided in this application further includes: Add protocol instances to the protocol instance pool so that charging devices can communicate in parallel with multiple charging management cloud platforms based on the protocol instances in the pool.

[0088] Optionally, after creating a protocol instance, the charging device adds the protocol instance to a protocol instance pool. The charging device can then communicate in parallel with multiple charging management cloud platforms based on multiple protocol instances in the protocol instance pool.

[0089] Furthermore, by deploying the automatic protocol identification algorithm provided in this application into the equipment operation and maintenance management platform, the charging device will proactively connect to the platform upon power-on. The platform will then retrieve the protocol and network parameter matching results from the cloud and use these results to establish communication with the platform. This eliminates the need for parameter configuration on the charging device side, enabling the switching between the charging device and the operation and maintenance management platform.

[0090] Furthermore, machine learning algorithms can be introduced into the equipment operation and maintenance management platform to analyze equipment operation and improve operational efficiency.

[0091] It should also be noted that this application designs such standardized protocol plugin interfaces to support the dynamic loading of third-party protocols as plugins. Adding a new protocol only requires implementing the standard interface functions and registering them in the protocol mapping table; no modification to the core code is needed, thus achieving true "hot-swappable" protocol support.

[0092] The following describes the charging device and computer-readable storage medium used to implement the charging protocol loading method provided in this application. The specific implementation process and technical effects are described above and will not be repeated below.

[0093] Figure 10 This is a schematic diagram of the structure of a charging device provided in this application. See also: Figure 10 The charging device includes: The configuration acquisition module 101 is used to acquire the configuration information of the charging management cloud platform. The configuration information includes at least the cloud platform identifier, cloud platform protocol, cloud platform domain name, and cloud platform port. The automatic identification module 102 is used to verify the validity of the configuration information and, based on the verification result of the configuration information and the preset protocol mapping list, determine the communication protocol parameters to be loaded. The communication protocol parameters to be loaded include: protocol loading function and network parameters. The protocol loading function includes: target protocol loading function and reference protocol loading function. The network parameters include: reference network parameters or target network parameters. The protocol loading module 103 is used to load the target communication protocol according to the parameters of the communication protocol to be loaded, and to create a protocol instance based on the target communication protocol; The protocol execution module 104 is used to communicate with the charging management cloud platform based on the protocol instance.

[0094] Optionally, the automatic identification module 102 is specifically used to: determine whether the cloud platform identifier in the configuration information is valid; if not, determine whether the cloud platform protocol in the configuration information is valid, and determine whether the cloud platform domain name and cloud platform port in the configuration information are valid.

[0095] Optionally, the aforementioned automatic identification module 102 is further configured to: if the verification result of the cloud platform identifier in the configuration information is valid, then search for the target protocol mapping relationship in the preset protocol mapping list based on the cloud platform identifier, and determine the target protocol loading function and reference network parameters according to the target protocol mapping relationship, wherein the reference network parameters include: reference domain name and reference port; if the verification result of the cloud platform identifier in the configuration information is invalid, then search for the target protocol mapping relationship in the preset protocol mapping list based on the verification results of the cloud platform protocol, cloud platform domain name and cloud platform port in the configuration information, and determine the protocol loading function and network parameters according to the target protocol mapping relationship.

[0096] Optionally, the aforementioned automatic identification module 102 is further configured to: if the cloud platform protocol in the configuration information is valid, then search for the target protocol mapping relationship in a preset protocol mapping list based on the cloud platform protocol, and determine the target protocol loading function and network parameters according to the target protocol mapping relationship and the verification results of the cloud platform domain name and cloud platform port in the configuration information; if the cloud platform protocol in the configuration information is invalid, then search for the target protocol mapping relationship in a preset protocol mapping list based on the verification results of the cloud platform domain name and cloud platform port in the configuration information, and determine the protocol loading function and network parameters according to the target protocol mapping relationship.

[0097] Optionally, the aforementioned automatic identification module 102 is further configured to: if the cloud platform domain name and cloud platform port in the configuration information are valid, determine the target protocol loading function and target network parameters according to the target protocol mapping relationship, wherein the target network parameters include: cloud platform domain name and cloud platform port; if the cloud platform domain name and cloud platform port in the configuration information are invalid, determine the target protocol loading function and reference network parameters according to the target protocol mapping relationship.

[0098] Optionally, the aforementioned automatic identification module 102 is further configured to: if the cloud platform domain name and cloud platform port in the configuration information are valid, then search for the target protocol mapping relationship in the preset protocol mapping list based on the cloud platform domain name and cloud platform port, and determine the target protocol loading function and target network parameters based on the target protocol mapping relationship; if the cloud platform domain name and cloud platform port in the configuration information are invalid, then search for the reference protocol mapping relationship in the preset protocol mapping list, and determine the reference protocol loading function and reference network parameters based on the reference protocol mapping relationship.

[0099] Optionally, the protocol execution module 104 is further configured to: add the protocol instance to the protocol instance pool so that the charging device can communicate in parallel with multiple charging management cloud platforms based on the protocol instances in the protocol instance pool.

[0100] The charging device described above is used to perform the method provided in the foregoing embodiments, and its implementation principle and technical effect are similar, so they will not be described again here.

[0101] These modules can be one or more integrated circuits configured to implement the above methods, such as one or more Application Specific Integrated Circuits (ASICs), one or more microprocessors, or one or more Field Programmable Gate Arrays (FPGAs). Alternatively, when a module is implemented using processing element scheduler code, the processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. Furthermore, these modules can be integrated together as a system-on-a-chip (SOC).

[0102] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the steps in the various method embodiments described above.

[0103] Optionally, this application also provides a program product, such as a computer-readable storage medium, including a program that, when executed by a processor, performs any of the above-described charging protocol loading method embodiments.

[0104] In the several embodiments provided by this invention, it should be understood that the disclosed charging devices and methods can be implemented in other ways. For example, the charging device embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

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

[0106] The integrated unit implemented as a software functional unit described above can be stored in a computer-readable storage medium. This software functional unit, stored in a storage medium, includes several instructions to cause a charging device to execute some steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0107] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0108] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A charging protocol loading method, characterized in that, The method is applied to a charging device, and the method includes: Obtain the configuration information of the charging management cloud platform, which includes at least: cloud platform identifier, cloud platform protocol, cloud platform domain name, and cloud platform port; The configuration information is validated for validity, and based on the validation result of the configuration information and the preset protocol mapping list, the communication protocol parameters to be loaded are determined. The communication protocol parameters to be loaded include: protocol loading function and network parameters. The protocol loading function includes: target protocol loading function or reference protocol loading function. The network parameters include: reference network parameters or target network parameters. Based on the parameters of the communication protocol to be loaded, load the target communication protocol and create a protocol instance based on the target communication protocol; The system communicates with the charging management cloud platform based on the protocol instance.

2. The charging protocol loading method according to claim 1, characterized in that, The validity verification of the configuration information includes: Determine whether the cloud platform identifier in the configuration information is valid; If not, determine whether the cloud platform protocol in the configuration information is valid, and determine whether the cloud platform domain name and cloud platform port in the configuration information are valid.

3. The charging protocol loading method according to claim 1, characterized in that, The verification results based on the configuration information and the preset protocol mapping list determine the parameters of the communication protocol to be loaded, including: If the verification result of the cloud platform identifier in the configuration information is valid, then the target protocol mapping relationship is searched in the preset protocol mapping list based on the cloud platform identifier, and the target protocol loading function and reference network parameters are determined according to the target protocol mapping relationship. The reference network parameters include: reference domain name and reference port. If the verification result of the cloud platform identifier in the configuration information is invalid, then based on the verification results of the cloud platform protocol, cloud platform domain name and cloud platform port in the configuration information, the target protocol mapping relationship is searched in the preset protocol mapping list, and the protocol loading function and network parameters are determined according to the target protocol mapping relationship.

4. The charging protocol loading method according to claim 3, characterized in that, Based on the verification results of the cloud platform protocol, cloud platform domain name, and cloud platform port in the configuration information, the target protocol mapping relationship is searched in a preset protocol mapping list, and the protocol loading function and network parameters are determined according to the target protocol mapping relationship, including: If the cloud platform protocol in the configuration information is valid, then the target protocol mapping relationship is searched in the preset protocol mapping list based on the cloud platform protocol, and the target protocol loading function and network parameters are determined according to the target protocol mapping relationship and the verification results of the cloud platform domain name and cloud platform port in the configuration information. If the cloud platform protocol in the configuration information is invalid, then based on the verification results of the cloud platform domain name and cloud platform port in the configuration information, the target protocol mapping relationship is searched in the preset protocol mapping list, and the protocol loading function and network parameters are determined according to the target protocol mapping relationship.

5. The charging protocol loading method according to claim 4, characterized in that, The step of determining the target protocol loading function and network parameters based on the target protocol mapping relationship and the verification results of the cloud platform domain name and cloud platform port in the configuration information includes: If the cloud platform domain name and cloud platform port in the configuration information are valid, then the target protocol loading function and target network parameters are determined according to the target protocol mapping relationship. The target network parameters include: cloud platform domain name and cloud platform port. If the cloud platform domain name and cloud platform port in the configuration information are invalid, then the target protocol loading function and reference network parameters are determined according to the target protocol mapping relationship.

6. The charging protocol loading method according to claim 4, characterized in that, Based on the verification results of the cloud platform domain name and cloud platform port in the configuration information, the target protocol mapping relationship is searched in a preset protocol mapping list, and the protocol loading function and network parameters are determined according to the target protocol mapping relationship, including: If the cloud platform domain name and cloud platform port in the configuration information are valid, then based on the cloud platform domain name and cloud platform port, the target protocol mapping relationship is searched in the preset protocol mapping list, and the target protocol loading function and target network parameters are determined according to the target protocol mapping relationship. If the cloud platform domain name and cloud platform port in the configuration information are invalid, then the reference protocol mapping relationship is searched in the preset protocol mapping list, and the reference protocol loading function and reference network parameters are determined based on the reference protocol mapping relationship.

7. The charging protocol loading method according to any one of claims 1 to 6, characterized in that, The protocol mapping list includes multiple protocol mapping relationships, each represented by structured data. Each protocol mapping relationship includes: cloud platform identifier, communication protocol type, reference domain name, reference port, and corresponding protocol loading function.

8. The charging protocol loading method according to claim 1, characterized in that, The method further includes: The protocol instance is added to the protocol instance pool so that the charging device can communicate in parallel with multiple charging management cloud platforms based on the protocol instances in the protocol instance pool.

9. A charging device, characterized in that, The charging device includes: The configuration acquisition module is used to obtain the configuration information of the charging management cloud platform. The configuration information includes at least: cloud platform identifier, cloud platform protocol, cloud platform domain name, and cloud platform port. An automatic identification module is used to verify the validity of the configuration information and, based on the verification result of the configuration information and a preset protocol mapping list, determine the communication protocol parameters to be loaded. The communication protocol parameters to be loaded include: a protocol loading function and network parameters. The protocol loading function includes: a target protocol loading function or a reference protocol loading function. The network parameters include: a reference network parameter or a target network parameter. The protocol loading module is used to load the target communication protocol according to the parameters of the communication protocol to be loaded, and to create a protocol instance based on the target communication protocol; The protocol execution module is used to communicate with the charging management cloud platform based on the protocol instance.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 1 to 8.

Images