Photovoltaic protocol converter, data transmission method and distributed photovoltaic power generation system

Abstract

The invention discloses a photovoltaic protocol converter, a data transmission method, a distributed photovoltaic power generation system and a program product, and belongs to the technical field of data transmission. The photovoltaic protocol converter comprises a multi-communication interface module, a local protocol library, a protocol identification module and a main control module. Wherein the multi-communication interface module is used for being connected with a photovoltaic inverter so as to establish communication connection with the photovoltaic inverter. And the local protocol library is used for storing different protocol types corresponding to communication protocols adopted by different photovoltaic inverters. The protocol identification module is used for automatically identifying the target protocol type of the communication protocol adopted by the photovoltaic inverter, the protocol does not need to be manually configured, and the problem that the communication protocol is not compatible can be solved. And the main control module is used for performing format conversion on the transmission data according to the identified target protocol type and realizing OTA upgrading of a protocol version in a local protocol library based on interaction with a cloud server, namely, performing remote updating on the local protocol library so as to ensure the accuracy of an identification result.

Description

Technical Field

[0001] The present application belongs to the field of data transmission technology, and in particular relates to a photovoltaic protocol converter, a data transmission method, a distributed photovoltaic power generation system, and a program product. Background Art

[0002] In order to solve the problems of rapid growth in energy demand in substations, difficulty in local photovoltaic consumption, and uneven load distribution, continuously improve resource allocation capabilities and intelligence levels, and better adapt to the needs of large-scale grid access such as distributed energy, energy storage, and interactive energy facilities, State Grid has proposed a low-voltage distributed photovoltaic metering and collection solution.

[0003] Currently, because different brands of photovoltaic inverters have customized sets or even multiple sets of MODBUS protocols, even inverters of the same brand and different models may have multiple versions of the communication protocol. The default communication address, register address, naming, control accuracy, and message response time of the four remote information vary greatly. Even the use of a communication protocol conversion module cannot avoid the heavy configuration workload and difficult engineering debugging in actual engineering application and promotion. Currently, for different brands of photovoltaic inverters, construction personnel need to use data acquisition sticks with different interfaces and then manually search for the corresponding communication protocol based on the brand and model. However, some brands of inverters are cooperated with other manufacturers, which increases the workload of finding the communication protocol. Therefore, construction personnel need to adjust the communication protocol with the photovoltaic inverter on site, which also increases the difficulty of subsequent control of the photovoltaic inverter, which is time-consuming and labor-intensive. Summary of the Invention

[0004] The embodiments of the present application provide a photovoltaic protocol converter, a data transmission method, a distributed photovoltaic power generation system, and a program product, which can dynamically identify the communication protocol of a photovoltaic inverter, realize automatic conversion of the protocol format and communication adaptation, and solve the problems of grid connection difficulties and low operation and maintenance efficiency of photovoltaic systems due to protocol incompatibility.

[0005] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by practice of the present application.

[0006] According to a first aspect of an embodiment of the present application, a photovoltaic protocol converter is provided, comprising:

[0007] a multi-communication interface module, configured to connect to a photovoltaic inverter to establish a communication connection with the photovoltaic inverter;

[0008] Local protocol library, used to store different types of communication protocols used by different photovoltaic inverters;

[0009] A protocol identification module, configured to identify a target protocol type of a communication protocol adopted by the photovoltaic inverter;

[0010] A main control module, connected to the protocol identification module, and configured to convert the data format of the data to be transmitted according to the target protocol type;

[0011] The main control module is also used to interact with the cloud server to achieve remote OTA upgrade of the protocol version in the local protocol library.

[0012] In some embodiments of the present application, based on the aforementioned solution, the protocol identification module is configured to identify the target protocol type of the communication protocol adopted by the photovoltaic inverter by combining protocol feature matching and machine learning, including:

[0013] Extracting protocol features of the communication protocol adopted by the photovoltaic inverter, and matching the protocol features with the local protocol library to identify a target protocol type of the communication protocol adopted by the photovoltaic inverter;

[0014] When the protocol feature fails to match the local protocol library, the communication protocol adopted by the photovoltaic inverter is processed by a pre-trained long short-term memory network model to predict the target protocol type of the communication protocol adopted by the photovoltaic inverter.

[0015] In some embodiments of the present application, based on the aforementioned solution, the main control module is further configured to interact with a cloud server to implement remote OTA upgrade of the protocol version in the local protocol library, including:

[0016] When the protocol feature fails to match the local protocol library, the main control module requests the cloud server for the latest version number of the communication protocol used by the photovoltaic inverter to perform a remote OTA upgrade on the corresponding protocol version in the local protocol library.

[0017] In some embodiments of the present application, based on the aforementioned solution, after performing a remote OTA upgrade on the corresponding protocol version in the local protocol library, the control module is further configured to:

[0018] The protocol identification module is controlled to extract again the protocol features of the communication protocol adopted by the photovoltaic inverter, and the protocol features are matched with the local protocol library to identify the target protocol type of the communication protocol adopted by the photovoltaic inverter.

[0019] In some embodiments of the present application, based on the aforementioned solution, the photovoltaic protocol converter further includes a priority scheduling module, which is used to dynamically allocate communication resources based on bandwidth occupancy and protocol type priority.

[0020] In some embodiments of the present application, based on the aforementioned solution, the priority scheduling module is configured to dynamically allocate communication resources based on bandwidth occupancy and protocol type priority, including:

[0021] According to the priority levels corresponding to different protocol types and the bandwidth occupancy rate monitored in real time, communication resources are dynamically allocated to multiple communication protocols of different protocol types processed in parallel.

[0022] In some embodiments of the present application, based on the aforementioned solution, the photovoltaic protocol converter further includes an encryption module, which is used to encrypt the data to be transmitted and store the key data on a chain.

[0023] According to a second aspect of an embodiment of the present application, a data transmission method is provided, which is performed by the photovoltaic protocol converter described in any embodiment of the present application, and the method includes:

[0024] Establish a communication connection with the photovoltaic inverter;

[0025] Extracting protocol features of the communication protocol adopted by the photovoltaic inverter, and matching the protocol features with the local protocol library to identify a target protocol type of the communication protocol adopted by the photovoltaic inverter;

[0026] Convert the data format of the data to be transmitted according to the target protocol type;

[0027] The data after transmission format conversion.

[0028] According to a third aspect of an embodiment of the present application, there is provided a distributed photovoltaic power generation system, comprising:

[0029] The photovoltaic protocol converter described in any embodiment of the present application;

[0030] A plurality of photovoltaic inverters, wherein the plurality of photovoltaic inverters are communicatively connected to the photovoltaic protocol converter;

[0031] The power grid master station system is communicatively connected to the photovoltaic protocol converter.

[0032] According to a fourth aspect of an embodiment of the present application, a computer program product is provided, which includes computer instructions, which are stored in a computer-readable storage medium and are suitable for being read and executed by a processor, so that a computer device having the processor executes the method described in the embodiment of the present application.

[0033] Based on the technical solution proposed in this application, the photovoltaic protocol converter includes a multi-communication interface module, a local protocol library, a protocol identification module and a main control module. Among them, the multi-communication interface module is used to connect to the photovoltaic inverter to establish a communication connection with the photovoltaic inverter, support intelligent switching of multiple communication interfaces, and improve the robustness of the system. The local protocol library is used to store different types of communication protocols adopted by different photovoltaic inverters. The protocol identification module is used to automatically identify the target protocol type of the communication protocol adopted by the photovoltaic inverter, without the need for manual configuration of the protocol, to solve the problem of communication protocol incompatibility. The main control module is used to convert the format of the data to be transmitted according to the identified target protocol type. The main control module is also used to realize OTA upgrade of the protocol version in the local protocol library based on interaction with the cloud server, that is, to remotely update the local protocol library to ensure the accuracy of the identification result.

[0034] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The accompanying drawings are incorporated into and constitute a part of the specification, illustrating embodiments consistent with the present application and, together with the specification, explaining the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and those skilled in the art can derive other drawings based on these drawings without inventive effort. In the drawings:

[0036] Figure 1 This is a first structural block diagram of a photovoltaic protocol converter provided in one embodiment of the present application.

[0037] Figure 2 This is a second structural block diagram of a photovoltaic protocol converter provided in one embodiment of the present application.

[0038] Figure 3 This is a third structural block diagram of a photovoltaic protocol converter provided in one embodiment of the present application.

[0039] Figure 4 This is a flowchart of the steps of a data transmission method provided by an embodiment of the present application.

[0040] Figure 5 Schematic diagram of a distributed photovoltaic power generation system provided in one embodiment of the present application.

[0041] Figure 6 It is a structural diagram of the computer program product provided in the embodiment of the present application.

[0042] Reference numerals:

[0043] Photovoltaic protocol converter 100, multi-communication interface module 110, local protocol library 120, protocol identification module 130, main control module 140, priority scheduling module 150, encryption module 160, photovoltaic inverter 200, power grid master station system 300;

[0044] Processor 601 , memory 602 , input / output interface 603 , communication interface 604 , bus 605 . DETAILED DESCRIPTION

[0045] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0046] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner.In the following description, many specific details are provided so as to provide a full understanding of the embodiments of the present application. However, it will be appreciated by those skilled in the art that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps etc. can be adopted. In other cases, known methods, devices, implementations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0047] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0048] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, while others may be combined or partially combined. Therefore, the actual execution order may vary depending on the actual situation.

[0049] In the description of this application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of the technical features indicated. Therefore, a feature specified as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this application, unless otherwise specified, "plurality" means two or more.

[0050] In order to enable those skilled in the art to better understand the present application, the application scenarios involved in the present application are first briefly described.

[0051] In order to solve the problems of rapid growth in energy demand in substations, difficulty in local photovoltaic consumption, and uneven load distribution, continuously improve resource allocation capabilities and intelligence levels, and better adapt to the needs of large-scale grid access such as distributed energy, energy storage, and interactive energy facilities, State Grid has proposed a low-voltage distributed photovoltaic metering and collection solution.

[0052] Currently, because different brands of PV inverters all have their own custom MODBUS protocols, and even different models of inverters within the same brand have multiple versions of the communication protocol, the default communication addresses, register addresses, naming, control accuracy, and message response times of the four remote control information vary significantly. Even with the use of a communication protocol conversion module, the heavy configuration workload and engineering commissioning difficulties in actual engineering applications and promotion cannot be avoided, which increases commissioning costs. Currently, for different brands of PV inverters, construction workers need to use data acquisition sticks with different interfaces and then manually search for the corresponding communication protocol based on the brand and model. However, some brands of inverters are produced in collaboration with other manufacturers, which increases the workload of finding the communication protocol. Therefore, construction workers need to adjust the communication protocol with the PV inverter on-site, which also increases the difficulty of subsequent control of the PV inverter, which is time-consuming and labor-intensive.

[0053] Example 1

[0054] Reference Figure 1 , Figure 1 This is a first structural block diagram of a photovoltaic protocol converter provided by an embodiment of the present application. Figure 1 As shown, the photovoltaic protocol converter 100 includes a multi-communication interface module 110, a local protocol library 120, a protocol identification module 130, and a main control module 140. The protocol identification module 130 can be integrated into the main control module 140.

[0055] The multi-communication interface module 110 is used to connect to the photovoltaic inverter to establish a communication connection with the photovoltaic inverter. The multi-communication interface module 110 can integrate multiple RS485, Controller Area Network (CAN) buses, HPLC carriers, wired (Ethernet), and wireless (LoRa / 5G) hybrid networks. This supports intelligent switching of multiple communication interfaces, which can improve system robustness. The photovoltaic protocol converter 100 can also connect to the photovoltaic inverter by connecting to the photovoltaic inverter's data acquisition stick. The photovoltaic protocol converter 100 can also establish a communication connection with the power grid master station system through the multi-communication interface module 110. For example, the photovoltaic protocol converter 100 can directly connect to the photovoltaic inverter via RS485 to collect data in real time. The photovoltaic protocol converter 100 can also interact with manufacturer-specific "communication sticks" through wireless communication and is compatible with proprietary protocol extensions. The photovoltaic protocol converter 100 can also communicate with the power grid master station system via 4G / 5G wireless networks to upload data to the power grid master station system.

[0056] The local protocol library 120 is used to store different types of communication protocols used by different photovoltaic inverters. Among them, the local protocol library 120 can store the protocols in layers according to the brand of the photovoltaic inverter. Specifically, for each mainstream manufacturer, an independent protocol sub-library can be established to store its private protocol features (such as Modbus function code definition, IEC 61850 logical node mapping rules). At the same time, a protocol type index can also be constructed, that is, a global index table is established based on standardized protocols (Modbus, IEC 61850, DNP3, etc.), and the register address, data format and verification rules corresponding to each photovoltaic inverter brand are associated (such as the 5000-5024 address segment of Modbus is used for inverter operation data acquisition). The embodiment of the present application can also realize offline deployment of the local protocol library through an SD card or a USB flash drive, and can use the FPGA on-chip Block RAM to cache high-frequency protocol rules (such as IEC 61850 service type templates) to achieve rapid loading of protocol features.

[0057] In some embodiments, the local protocol library 120 may support remote updating of protocol parsing rules (such as adding new IEC62351 protocol features), and may achieve compatibility with new protocol formats by sending rule files from the cloud or loading extension packages locally.

[0058] The protocol identification module 130 is used to identify the target protocol type of the communication protocol used by the photovoltaic inverter. Specifically, the protocol identification module 130 can extract the protocol features of the communication protocol used by the photovoltaic inverter and match the protocol features with the local protocol library 120 to identify the target protocol type of the communication protocol used by the photovoltaic inverter. Specifically, the protocol identification module 130 can analyze static features such as message header length and CRC checksum, and then quickly match them with the local protocol library 120 to identify the protocol type of the communication protocol used by the photovoltaic inverter. For example, the protocol identification module 130 can lock the protocol type by reading special address data (such as the device model code) in the photovoltaic inverter response message. As an embodiment, the local protocol library 120 can store protocol feature vectors corresponding to different protocol types. After extracting the protocol features of the communication protocol used by the photovoltaic inverter, the protocol identification module 130 can convert the protocol features into feature vectors and then compare the feature vectors with the protocol feature vectors corresponding to each protocol type stored in the local protocol library 120 to identify the protocol type.

[0059] In some embodiments, after the protocol identification module 130 extracts and matches the protocol features, there are two situations: successful matching and failed matching. For the case of failed matching, there may be two reasons: one is that the version of the communication protocol used by the photovoltaic inverter has been upgraded, but the corresponding protocol type stored in the local protocol library 120 has not been upgraded and updated in time; the other is that the communication protocol used by the photovoltaic inverter is a new protocol type. For the first reason, when the protocol feature fails to match the local protocol library 120, the main control module 140 can request the latest version number of the communication protocol used by the photovoltaic inverter from the cloud server to perform a remote OTA upgrade on the corresponding protocol version in the local protocol library 120. After the upgrade, the control module 140 can control the protocol identification module 130 to extract the protocol features of the communication protocol used by the photovoltaic inverter again, and match the protocol features with the local protocol library 120, so as to identify the target protocol type of the communication protocol used by the photovoltaic inverter. For the second reason, when the protocol features fail to match the local protocol library, the communication protocol adopted by the photovoltaic inverter can be processed through a pre-trained long short-term memory network model to predict the target protocol type of the communication protocol adopted by the photovoltaic inverter.

[0060] Specifically, a long short-term memory (LSTM) network can be used to perform time series modeling on unknown protocol messages, and the protocol type can be predicted by analyzing dynamic features such as message length and field distribution. For example, for private protocols that are not stored in the local protocol library 120, a long short-term memory network model can be trained based on historical communication data to improve the recognition accuracy of unknown protocols. Specifically, the original message can be standardized and cleaned (such as removing redundant fields and unifying the encoding format), key feature vectors can be extracted, and the pre-processed data can be input into the long short-term memory network model for training or real-time reasoning to output the protocol type probability distribution. The embodiment of the present application can also compare the model recognition results with the actual communication verification results. If there is a deviation, the local protocol library 120 is triggered to dynamically update. For example, a new type of protocol is added to the local protocol library 120 or the LSTM network weight parameters are adjusted to continuously optimize the recognition accuracy.

[0061] Specifically, during model training, protocol templates issued by the power grid master system (such as the DNP3 control instruction format) and locally collected PV inverter operating data can be combined to generate a hybrid training dataset, enhancing the model's generalization capabilities. Combining feature matching with an LSTM network for protocol recognition addresses the inability of traditional rule engines to cover unknown protocols, improving protocol recognition rates. Through machine learning and rule expansion, dynamic iteration of the protocol library is achieved, reducing manual maintenance costs.

[0062] The embodiment of the present application can automatically identify the target protocol type of the communication protocol adopted by the photovoltaic inverter through the protocol identification module 130, without the need for manual configuration of the protocol, and can solve the problem of communication protocol incompatibility. At the same time, the main control module 140 can convert the format of the data to be transmitted according to the identified target protocol type, such as converting the photovoltaic inverter data into the protocol format required by the power grid master station system, or converting the control instruction data issued by the power grid master station system into the photovoltaic inverter private protocol format. The main control module 140 can also realize OTA upgrade of the protocol version in the local protocol library 120 based on the interaction with the cloud server, that is, remotely update the local protocol library 120 to ensure the accuracy of the identification result.

[0063] Example 2

[0064] Reference Figure 2 , Figure 2 This is a second structural block diagram of a photovoltaic protocol converter provided by an embodiment of the present application. Figure 2 As shown, the photovoltaic protocol converter 100 includes a multi-communication interface module 110 , a local protocol library 120 , a protocol identification module 130 , a main control module 140 and a priority scheduling module 150 .

[0065] Priority scheduling module 150 dynamically allocates communication resources based on bandwidth utilization and protocol priority. Specifically, priority scheduling module 150 dynamically allocates communication resources for multiple communication protocols of different types being processed in parallel, based on their corresponding priority levels and real-time bandwidth utilization. By dynamically balancing grid connections based on grid-issued instructions and user device-side instructions, the priority scheduling module can address grid connection and capacity constraints.

[0066] For example, the priority levels corresponding to different protocol types can be divided according to the degree of urgency. As shown in Table 1, different protocol types can be divided into four levels, namely P0, P1, P2 and P3, among which P0 is the highest level, P1 is the second, P2 is the third, and P3 is the lowest level.

[0067] Table 1

[0068]

[0069]

[0070] Furthermore, communication bandwidth can be dynamically allocated based on priority weights. For example, the total bandwidth can be allocated in a ratio of P0:P1:P2:P3 = 4:3:2:1. For example, if the total bandwidth is 10 Gbps, P0 will occupy 4 Gbps, P1 will occupy 3 Gbps, P2 will occupy 2 Gbps, and P3 will occupy 1 Gbps. This ensures that high-priority tasks (such as emergency shutdown commands) have exclusive access to high-bandwidth resources. Furthermore, bandwidth reallocation can be automatically triggered based on the real-time status of the power grid (e.g., reverse power transmission penetration rate >80%), prioritizing the communication needs of the P0-P1 queue. Furthermore, the command queue can be dynamically adjusted based on real-time bandwidth utilization monitoring. For example, when bandwidth utilization ≥80%, the transmission of low-priority commands is automatically suspended, prioritizing the transmission of high-priority commands. Furthermore, protocols with P0 and P1 priorities can adopt a real-time queue mechanism with round-robin (RR) scheduling and a time slice of 2 ms, supporting rapid switching of high-priority tasks (such as IEC61850 control commands). Protocol types with P2 and P3 priorities can use non-real-time queues and first-in-first-out (FIFO) scheduling, allowing tasks to be queued. They are suitable for low-real-time services such as equipment status monitoring and historical data reporting.

[0071] Specifically, if it is detected that the frequency of the current device control instructions deviates from the frequency of the instructions sent to the device by the power grid in real time. For example: the instruction currently executed by the device is a peak-shaving instruction, but the instruction given by the power grid is an emergency shutdown instruction, then the device should automatically increase the instruction level and give priority to executing the emergency shutdown instruction issued by the power grid to ensure the stability of the power grid frequency of the entire power grid. For periodic data (such as P2 level), if the waiting timeout occurs, the priority can be temporarily increased by one level. The CPU utilization and queue depth can also be monitored in real time. If resources are tight (such as CPU>80%), the P3 level task quota will be reduced.

[0072] In the embodiment of the present application, the priority scheduling module 150 dynamically allocates communication resources based on bandwidth occupancy and protocol type priority, can quickly respond to scheduling instructions, and improve communication efficiency.

[0073] Example 3

[0074] Reference Figure 3 , Figure 3 This is the third structural block diagram of the photovoltaic protocol converter provided by an embodiment of the present application. Figure 3 As shown, the photovoltaic protocol converter 100 includes a multi-communication interface module 110 , a local protocol library 120 , a protocol identification module 130 , a main control module 140 , a priority scheduling module 150 and an encryption module 160 .

[0075] Among them, the encryption module 160 is used to encrypt the data to be transmitted and store key data (such as protocol version upgrade logs) on the chain. Specifically, the encryption module 160 (such as the ESAM chip) can encrypt the group adjustment and group control instructions issued by the power grid with AES-256 or SM4 national encryption algorithm to prevent man-in-the-middle attacks and illegal tampering, and ensure that the power adjustment instructions received by the photovoltaic inverter are safe and reliable. When the photovoltaic protocol converter 100 communicates with the power grid master station, the encryption module 160 can also use digital certificates or key pairs to complete device identity authentication to prevent unauthorized devices from accessing the power grid control system. During the OTA remote upgrade of the protocol version in the local protocol library, the encryption module 160 can also encrypt the interactive data to ensure the security of the transmitted data, thereby improving the security of the remote upgrade of the protocol version.

[0076] That is, the present application encrypts the communication data and protocol through the encryption module 160, which can resist man-in-the-middle attacks and data tampering, and ensure the stability of the power grid.

[0077] In some embodiments, the photovoltaic protocol converter 100 may also include a cache management module for partitioning and managing caches for different data types. For example, an emergency cache, a regular cache, and a batch cache may be configured. The emergency cache may have a capacity of 64KB, with an elimination rule that overwrites the oldest data to prioritize the latest instructions. The regular cache may have a capacity of 512KB, with an elimination rule that eliminates the least recently used data. The batch cache may have a capacity of 2MB, with an elimination rule that periodically writes to the hard drive to prevent memory overflow.

[0078] Reference Figure 4 , the embodiment of the present application further proposes a data transmission method, which is executed by the photovoltaic protocol converter 100 provided by any embodiment of the present application, including but not limited to steps S410 to S440.

[0079] Step S410, establishing a communication connection with the photovoltaic inverter;

[0080] Step S420: extracting protocol features of the communication protocol used by the photovoltaic inverter, and matching the protocol features with the local protocol library to identify the target protocol type of the communication protocol used by the photovoltaic inverter;

[0081] Step S430, converting the data format to be transmitted according to the target protocol type;

[0082] Step S440: Transmit the data after format conversion.

[0083] In the embodiment of the present application, by automatically identifying the target protocol type of the communication protocol adopted by the photovoltaic inverter, automatic conversion of the protocol format and communication adaptation can be achieved, thereby solving the problems of grid connection difficulties and low operation and maintenance efficiency of the photovoltaic system due to protocol incompatibility.

[0084] Reference Figure 5 , the embodiment of the present application further proposes a distributed photovoltaic power generation system, comprising:

[0085] The photovoltaic protocol converter 100 provided in any embodiment of the present application;

[0086] A plurality of photovoltaic inverters 200, wherein the plurality of photovoltaic inverters 200 are communicatively connected to the photovoltaic protocol converter 100;

[0087] The power grid master station system 300 is communicatively connected to the photovoltaic protocol converter 100 .

[0088] In the embodiment of the present application, the photovoltaic protocol converter 100 can realize automatic conversion of the protocol format and communication adaptation by automatically identifying the target protocol type of the communication protocol adopted by the photovoltaic inverter, thereby solving the problems of difficulty in grid connection and low operation and maintenance efficiency of the photovoltaic system due to protocol incompatibility. At the same time, the photovoltaic protocol converter 100 can dynamically complete the protocol format conversion by automatically identifying the communication protocol of the photovoltaic inverter 200 (such as Modbus, private protocol, etc.), and realize data interaction between devices of different manufacturers. The photovoltaic protocol converter 100 can also convert the direct current output of the power grid master station system 300 into alternating current that meets the requirements of the power grid, and monitor the parameters such as the grid voltage, current, and frequency in real time to ensure grid connection safety. At the same time, it supports flexible adjustment of the active output of the photovoltaic inverter 200 to cope with fluctuations in the power quality of the power grid.

[0089] Based on the same inventive concept, an embodiment of the present application also provides a computer program product, which includes computer instructions, which are stored in a computer-readable storage medium and are suitable for being read and executed by a processor, so that a computer device with the processor executes the method provided in any of the above embodiments.

[0090] See also Figure 6 , Figure 6 The hardware structure of the computer program product of the embodiment of the present application is illustrated. The computer program product includes:

[0091] The processor 601 may be implemented as a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application.

[0092] The memory 602 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 602 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 602 and is called by the processor 601 to execute the methods provided in the embodiments of this application.

[0093] Input / output interface 603, used to implement information input and output;

[0094] Communication interface 604, used to implement communication interaction between this device and other devices, which can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WiFi, Bluetooth, etc.);

[0095] Bus 605 , which transmits information between various components of the device (e.g., processor 601 , memory 602 , input / output interface 603 , and communication interface 604 );

[0096] The processor 601 , the memory 602 , the input / output interface 603 and the communication interface 604 are connected to each other in communication within the device via a bus 605 .

[0097] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on or transmitted via a computer-readable medium. Other examples and implementations are within the scope and spirit of this application and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hardwiring, or a combination of any of these. Furthermore, the functional units may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit.

[0098] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0099] The units described as separate components may or may not be physically separate, and the components of the control device may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0100] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk, etc. Various media that can store computer program instructions.

[0101] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. Various modifications and variations are possible for those skilled in the art. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present application shall be included within the scope of the claims of the present application.

Claims

1. A photovoltaic protocol converter, characterized in that: include: a multi-communication interface module, configured to connect to a photovoltaic inverter to establish a communication connection with the photovoltaic inverter; Local protocol library, used to store different types of communication protocols used by different photovoltaic inverters; A protocol identification module, configured to identify a target protocol type of a communication protocol adopted by the photovoltaic inverter; A main control module, connected to the protocol identification module, and configured to convert the data format of the data to be transmitted according to the target protocol type; The main control module is also used to interact with the cloud server to achieve remote OTA upgrade of the protocol version in the local protocol library.

2. The photovoltaic protocol converter according to claim 1, characterized in that: The protocol identification module is used to identify the target protocol type of the communication protocol adopted by the photovoltaic inverter, including: Extracting protocol features of the communication protocol adopted by the photovoltaic inverter, and matching the protocol features with the local protocol library to identify a target protocol type of the communication protocol adopted by the photovoltaic inverter; When the protocol feature fails to match the local protocol library, the communication protocol adopted by the photovoltaic inverter is processed by a pre-trained long short-term memory network model to predict the target protocol type of the communication protocol adopted by the photovoltaic inverter.

3. The photovoltaic protocol converter according to claim 2, characterized in that: The main control module is also used to interact with the cloud server to implement remote OTA upgrade of the protocol version in the local protocol library, including: When the protocol feature fails to match the local protocol library, the main control module requests the cloud server for the latest version number of the communication protocol used by the photovoltaic inverter to perform a remote OTA upgrade on the corresponding protocol version in the local protocol library.

4. The photovoltaic protocol converter according to claim 3, characterized in that: After performing remote OTA upgrade on the corresponding protocol version in the local protocol library, the control module is further configured to: The protocol identification module is controlled to extract again the protocol features of the communication protocol adopted by the photovoltaic inverter, and the protocol features are matched with the local protocol library to identify the target protocol type of the communication protocol adopted by the photovoltaic inverter.

5. The photovoltaic protocol converter according to claim 1, characterized in that: The photovoltaic protocol converter further includes a priority scheduling module, which is used to dynamically allocate communication resources based on bandwidth occupancy and protocol type priorities.

6. The photovoltaic protocol converter according to claim 5, characterized in that: The priority scheduling module is used to dynamically allocate communication resources based on bandwidth occupancy and protocol type priority, including: According to the priority levels corresponding to different protocol types and the bandwidth occupancy rate monitored in real time, communication resources are dynamically allocated to multiple communication protocols of different protocol types processed in parallel.

7. The photovoltaic protocol converter according to claim 1, characterized in that: The photovoltaic protocol converter also includes an encryption module, which is used to encrypt the data to be transmitted and store the key data on the chain.

8. A data transmission method, characterized in that: The method is performed by the photovoltaic protocol converter according to any one of claims 1 to 7, and includes: Establish a communication connection with the photovoltaic inverter; Extracting protocol features of the communication protocol adopted by the photovoltaic inverter, and matching the protocol features with the local protocol library to identify a target protocol type of the communication protocol adopted by the photovoltaic inverter; Convert the data format of the data to be transmitted according to the target protocol type; Transmit data after format conversion.

9. A distributed photovoltaic power generation system, characterized in that: include: The photovoltaic protocol converter according to any one of claims 1 to 7; A plurality of photovoltaic inverters, wherein the plurality of photovoltaic inverters are communicatively connected to the photovoltaic protocol converter; The power grid master station system is communicatively connected to the photovoltaic protocol converter.

10. A computer program product, characterized in that The computer program product includes computer instructions stored in a computer-readable storage medium and adapted to be read and executed by a processor, so as to cause a computer device having the processor to perform the method according to claim 8 .

Images