A heterogeneous device's object system

Abstract

The application discloses a kind of heterogeneous equipment's internet of things systems, and relates to the field of power system.Heterogeneous equipment's internet of things systems, comprising: at least one internet of things device, internet of things device includes the device model of the device information of the power device, the first adapter for receiving the call of power processing system to interface and the second adapter of the operation corresponding to interface to power device is executed;Each internet of things device is used to assist one type of power device access power processing system, realizes the compatibility and intercommunication of heterogeneous equipment in power system, greatly improves the integration efficiency and operation consistency of system.

Description

Technical Field

[0001] This invention relates to the field of power system technology, and more particularly to an Internet of Things (IoT) system for heterogeneous devices. Background Technology

[0002] With the rapid development of IoT technology, various devices are connected through networks, forming a vast IoT ecosystem. In the power system, the application of IoT technology is becoming increasingly widespread, involving various types of equipment such as smart meters, substation equipment, distribution automation equipment, and sensors. However, these devices typically use different communication protocols and data formats, leading to increasingly prominent interoperability and compatibility issues between them.

[0003] In the process of developing this invention, it was discovered that the prior art has at least the following technical problems: In traditional power systems, the communication protocols and data formats of different devices are often highly customized and lack a unified standard. Devices from different manufacturers and in different application scenarios employ their own independent communication protocols, which differ significantly in data transmission formats, communication methods, and data encoding, making it difficult for different devices to directly interoperate. Summary of the Invention

[0004] This invention provides an IoT system for heterogeneous devices to solve the problems of low compatibility and poor interoperability of heterogeneous devices in power systems.

[0005] According to one aspect of the present invention, an Internet of Things (IoT) system for heterogeneous devices is provided, comprising:

[0006] At least one IoT device, the IoT device including a device model, a first adapter and a second adapter; each IoT device is used to assist a type of power device in accessing the power processing system;

[0007] The equipment model contains equipment information for power equipment;

[0008] The first end of the first adapter is connected to the power processing system, and the second end of the first adapter is connected to the power equipment. The first adapter includes multiple interfaces, each of which is obtained by encapsulating an operation of a certain type. The first adapter is used to receive calls from the power processing system to the interfaces and to perform the corresponding operations on the power equipment.

[0009] The first end of the second adapter is connected to the power processing system, and the second end of the second adapter is connected to the power equipment. The second adapter uses a protocol abstract interface as its base class and inherits from the base class to execute the following methods: receiving a first data packet transmitted by the power equipment, parsing the first data packet, extracting the data fields from the first data packet, converting the extracted data fields into standard format data adapted to the power processing system, and transmitting it to the power processing system; and receiving a second data packet from the power processing system, extracting the data fields from the second data packet, encapsulating it into a protocol packet adapted to the power equipment, and transmitting it to the power equipment.

[0010] The technical solution of this invention, through at least one IoT device, includes a device model configured with device information of power equipment, a first adapter for receiving calls to the interface from the power processing system and performing operations corresponding to the interface on the power equipment, and a second adapter based on a protocol abstract interface. Each IoT device is used to assist a type of power equipment in accessing the power processing system. This solves the interoperability and compatibility problems between different devices caused by different communication protocols and data formats in traditional power systems, realizes the compatibility and interoperability of heterogeneous devices in the power system, and significantly improves the system integration efficiency and operational consistency.

[0011] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

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

[0013] Figure 1 This is a schematic diagram of the structure of an IoT system for heterogeneous devices provided in Embodiment 1 of the present invention;

[0014] Figure 2 This is a schematic diagram of the structure of another heterogeneous device IoT system provided in Embodiment 2 of the present invention. Detailed Implementation

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

[0016] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0017] Example 1

[0018] Figure 1 This is a schematic diagram of a heterogeneous device Internet of Things system provided in Embodiment 1 of the present invention. This embodiment is applicable to situations where different power devices using different communication protocols and data formats directly communicate with each other. Figure 1 As shown, the IoT system includes at least one IoT device 100. Each IoT device 100 includes a device model 110, a first adapter 120, and a second adapter 130; each IoT device 100 is used to assist a type of electrical equipment in accessing the power processing system; wherein,

[0019] Equipment model 110 contains equipment information for power equipment;

[0020] The first adapter 120 has its first end connected to the power processing system and its second end connected to the power equipment. The first adapter 120 includes multiple interfaces, each encapsulated as an operation of a certain type. The first adapter 120 receives calls from the power processing system to these interfaces and executes the corresponding operations on the power equipment. The second adapter 130 has its first end connected to the power processing system and its second end connected to the power equipment. The second adapter 130 uses a protocol abstract interface as its base class and inherits from this base class to execute the following methods: receiving a first data packet transmitted by the power equipment; parsing the first data packet; extracting data fields from the first data packet; converting the extracted data fields into standard format data adapted to the power processing system and transmitting it to the power processing system; and receiving a second data packet from the power processing system; extracting data fields from the second data packet; encapsulating them into a protocol packet adapted to the power equipment and transmitting it to the power equipment.

[0021] In this embodiment, power equipment can be understood as equipment that performs power generation, power conversion, power distribution, and other power services in a power system. For example, power equipment may include, but is not limited to, smart meters, substation equipment, distribution automation equipment, sensors, etc. Different power devices may use different communication protocols and data formats. For example, different power devices may use the following communication protocols: Modbus, IEC, 61850, DNP3, and Zigbee, etc.

[0022] A power processing system can be understood as an Internet of Things (IoT) system that manages, collects, and processes data from heterogeneous power devices. By connecting with different power devices, it can send control commands to the power devices and transmit data with them.

[0023] Since heterogeneous power devices use different communication protocols and data formats, making them incompatible and unable to communicate with each other, this embodiment sets up an Internet of Things (IoT) system between the power devices and the power processing system. Different power devices are connected to the power processing system through the IoT system, thus achieving compatible IoT between heterogeneous power devices and the power processing system.

[0024] The IoT system includes multiple IoT devices 100. Optionally, each power device can be configured with an IoT device 100, and the power device can be connected to the power processing system through the IoT device 100.

[0025] Based on the above embodiments, power devices of the same type use the same communication protocol and data format. In order to reduce the cost of the Internet of Things system, the power devices to be connected to the power processing system are classified and processed. One Internet of Things device 100 is configured for power devices of the same type. By reusing one Internet of Things device 100 for multiple power devices of the same type, the equipment cost is reduced while realizing the access of power devices to the power processing system.

[0026] Optionally, power equipment can be classified based on the communication protocols and data formats used, identifying equipment with the same communication protocols and data formats as belonging to the same type. It is understandable that, for the same type of power equipment, taking smart meters as an example, smart meters from different manufacturers may use different communication protocols and / or data formats. Classifying power equipment based on communication protocols and data formats can improve the accuracy of classification.

[0027] In this embodiment, each IoT device 100 includes a device model 110, which is a model configured with device information of power devices. Here, the device information of the power devices can be understood as the device information of a certain type of power device corresponding to the IoT device 100. Optionally, the device information configured in the device model 110 includes one or more of the following: device identifier, device type, device attributes, device function, and data format. The device identifier is a unique identifier assigned to each power device, such as a power device ID. It can be understood that if there are multiple power devices of a certain type, the device model 110 can be configured with separate device identifiers for each of those power devices. The device type is used to classify different types of power devices, such as a smart meter. Device attributes contain some basic information about the power device, such as, but not limited to, one or more of the following: power device name, manufacturer, model, communication interface type, and protocol type. Device function includes the functions supported by the power device and the operations it can perform; for example, a smart meter can accurately measure energy consumption and provide accurate electricity usage data. The data format is used to record and store various data related to the operation of the power system. The equipment information configured in equipment model 110 is beneficial for providing data support for the connection of power equipment to the power processing system.

[0028] The first end of the first adapter 120 is connected to the power processing system, and the second end of the first adapter 120 communicates with the power equipment. The first adapter 120 receives instructions from the power processing system and performs corresponding operations on the power equipment. The first adapter 120 completes the above operations through interfaces. Specifically, the first adapter 120 includes multiple interfaces. One interface can be obtained by encapsulating operations of the same type, and multiple interfaces can be obtained by encapsulating operations of different types of power equipment, to meet the needs of the power processing system for operating different types of power equipment. For example, the operation encapsulation of a smart meter includes one or more functions such as reading electricity consumption, setting time, and restarting the device. These operations are encapsulated as interfaces, and the power processing system can directly call the functions of the smart meter through these interfaces without needing to understand its underlying implementation details.

[0029] In this embodiment, the first adapter 120 is used to assist in realizing the control operations of the power processing system on the power equipment during the process of the power equipment being connected to the power processing system. For example, the control operations of the power processing system on the power equipment include, but are not limited to, data reading, data writing, equipment restart, starting or stopping a certain device or function.

[0030] The first adapter 120 includes multiple pre-encapsulated interfaces, each encapsulated by a type of operation. The power processing system sends relevant commands to the power equipment by calling the relevant interfaces. The connection method between the first adapter 120 and the power processing system and the power equipment can be determined according to the interfaces used by the power processing system and the power equipment. For example, if the power equipment is equipped with a serial port, the first adapter 120 can connect to the power equipment via the serial port; if the power equipment is equipped with a wireless communication interface, the first adapter 120 can connect to the power equipment wirelessly. Different power equipment can access the corresponding first adapter 120 through different methods. Similarly, the first adapter 120 can be connected to the power processing system wirelessly or via a wired connection.

[0031] The encapsulation method for multiple interfaces in the first adapter 120 can be: a pre-configured initialization method, which defines the device initialization method and sets the communication parameters and basic configuration of the power equipment through the initialization method. For example, the settings of a smart meter include the communication port (such as COM3 port), baud rate (such as 9600bps), and communication timeout (such as 5 seconds).

[0032] A pre-defined communication method is used to define the communication interface of the power equipment. This method configures the communication interface, which is used for data exchange between the power equipment and the system. Taking a smart meter as an example, the communication interface may include interfaces for sending commands and receiving data. Through these interfaces, the power processing system can send commands such as reading electricity consumption to the smart meter and receive the returned electricity consumption data, enabling effective bidirectional communication between the power equipment and the power processing system in a heterogeneous environment.

[0033] By encapsulating operations, the specific operations of power equipment are converted into a standard system interface, enabling the power processing system to interact with different types of equipment in a unified manner. Optionally, the interfaces in the first adapter 120 include a data read interface, a data write interface, and a command execution interface. Specifically, the data read interface is used to read data from the power equipment; the data write interface is used by the power processing system to write relevant information or instructions, such as configuration information and control commands, to the power equipment; the command execution interface is used to execute specific operations of the power equipment, such as restarting the power equipment or activating a certain function. The command execution interface standardizes the operating methods of different power equipment, allowing the power processing system to execute commands from different power equipment through a unified interface.

[0034] In this embodiment, the first end of the second adapter 130 is connected to the power processing system, and the second end of the second adapter 130 is connected to the power equipment. The second adapter 130 is used to assist in the transmission of data packets between the power processing system and the power equipment during the process of the power equipment accessing the power processing system. The second adapter 130 can assist in the transmission of data packets from the power equipment to the power processing system, and the transmission of data packets from the power processing system to the power equipment.

[0035] During the transmission of data packets from the power equipment to the power processing system, the second adapter 130 receives the first data packet transmitted by the power equipment, parses the first data packet, extracts the data fields in the first data packet, converts the extracted data fields into standard format data adapted to the power processing system, and transmits them to the power processing system.

[0036] The first data packet is the data packet transmitted by the power equipment received by the second adapter 130. The data fields are the data fields extracted from the first data packet after parsing. For example, the second adapter 130 can be configured with a parser submodule. Different parser submodules can correspond to different communication protocols. The parser submodule configured in the second adapter 130 is suitable for the communication protocol of the power equipment corresponding to the IoT device 100 and can be used to parse the first data packet sent by the power equipment. Based on the characteristics of the power equipment protocol, the parser submodule can be constructed using regular expressions or protocol parsing libraries, etc.

[0037] The data fields parsed from the first data packet may include, but are not limited to, device ID, data timestamp, and measurement value. Standard format data is data adapted to the format required by the power processing system. The second adapter 130 receives a first data packet using the Modbus protocol. The content of the first data packet is: 01 03 00 00 00 02C4 0B. By parsing the first data packet, address 0000 and data length 2 are extracted, and this information is converted into standard format data for the IoT system, such as {"address": "0000", "data length": "2"}.

[0038] Converting the parsed data fields into the standard format of the power processing system may involve, but is not limited to, data type conversion, unit conversion (e.g., Celsius to Fahrenheit), and data format adjustment. For different data types, converter classes and function libraries can be used to perform data conversion, ensuring that all data conforms to the format and units required by the IoT system. For example, floating-point numbers, integers, or strings can be converted to a unified numeric type.

[0039] In the process of converting the data sent by the power system into standard format data required by the power processing system, the second adapter 130 parses the first data message transmitted by the power equipment, extracts the data fields in the first data message, and maps the extracted data in the first data message into data suitable for the power processing system according to the corresponding mapping rules.

[0040] Optionally, the second adapter 130 is further configured to map the data fields in the first data message to standard fields of the power processing system after extracting the data fields; wherein, the second adapter 130 pre-stores field mapping rules corresponding to the power equipment, and the field mapping rules include the mapping relationship between the data fields in the power equipment and the standard fields of the power processing system.

[0041] In this embodiment, the field mapping rules represent the mapping relationship between data fields in the first data message and standard fields of the power processing system, and are pre-stored in the second adapter 130. For example, a set of field mapping rule tables is established for each type of power equipment, representing the mapping relationship between the data fields of the power equipment and the standard fields of the power processing system. For example, for a temperature sensor, the temp_value field of the power equipment may be mapped to the temperature field of the power processing system. If different power equipment have different data units, a unit conversion rule needs to be defined in the mapping rules, such as converting Fahrenheit to Celsius, or converting inches to centimeters. For example, for a temperature sensor, the data field in the power equipment is temp_value, and the standard field required by the power processing system is temperature. Through data unit conversion, Fahrenheit is converted to Celsius, and the conversion formula is temperature = (temp_value - 32) * 5 / 9. For example, for a pressure sensor, the data field in the power equipment is pressure_value, and the standard field required by the power processing system is pressure. Through data unit conversion, pounds per square inch is converted to Pascals, and the conversion formula is pressure = pressure_value * 6894.76.

[0042] Field mapping rules can be dynamically adjusted based on IoT system configuration or real-time parameters. For example, some power devices may have different operating modes, and the meaning of data may change in different modes. The IoT system should adjust the mapping rules according to the current mode.

[0043] Optionally, the second adapter 130 is also used to extract data fields from the first data message, standardize the data fields, and convert the extracted data fields into standard format data adapted to the power processing system.

[0044] Specifically, standard format data is data adapted to the power processing system and is obtained by standardizing the data fields in the first data message. For example, if the data fields in the extracted first data message are in Fahrenheit, while the data in the power processing system is in Celsius, the Fahrenheit data is converted to Celsius by standardizing the data fields in the first data message.

[0045] During the transmission of data packets from the power processing system to the power equipment, the second adapter 130 has an encapsulation function. The second adapter 130 receives the second data packet from the power processing system, extracts the data fields from the second data packet, encapsulates it into a protocol message adapted to the power equipment, and transmits it to the power equipment. The second data packet is the data information received by the second adapter 130 from the power processing system. The protocol message is generated by converting the system's standard fields into the message required by the power equipment according to the requirements of different protocols. For example, in the Modbus protocol, the function code, address, and data value are encapsulated into a byte stream conforming to the relevant protocol format. If the IoT system needs to send a Modbus protocol write register instruction, the corresponding fields for the IoT system are {"address": "0001", "value": "03E8"}, which is encapsulated into a corresponding protocol message, such as 0106 00 01 03E8 48 9A, and then sent to the power equipment.

[0046] In the process of parsing and encapsulating the second adapter 130 as described above, the corresponding operations are implemented based on the protocol abstraction interface. Optionally, the protocol abstraction interface includes a data transmission interface, a data reception interface, and a protocol initialization interface; wherein, the data transmission interface is a predefined first abstract method, which is used to send data to the power equipment, and the input parameters of the first abstract method include the data content and the target device address; the data reception interface is a predefined second abstract method, which is used to receive data from the power equipment, and the input parameters of the second abstract method include the expected length and / or an identifier; the protocol initialization interface is a predefined third abstract method, which is used to initialize the configuration parameters of the communication protocol.

[0047] In this embodiment, the protocol abstract interface is a base class or interface used to define abstract methods for operations related to the communication protocol, such as sending data, receiving data, and initializing the protocol. These methods do not have concrete implementations; the concrete implementations are left to subclasses that inherit the relevant interface. Each subclass implements the corresponding data sending and receiving methods according to the characteristics of the specific protocol, ensuring the flexibility and scalability of the IoT system. The second adapter 130 is a concrete class that inherits and implements the protocol abstract interface. According to the requirements of a specific communication protocol, it implements these abstract methods to communicate with power equipment or the IoT system. The data content is the data to be sent, such as instructions and configuration parameters; the target device address is the communication address of the power equipment, such as an IP address, port number, and physical address. The expected length is a parameter of the IoT system used to tell the receiving logic how many bytes of data can be received before stopping reception; it is a parameter set according to the requirements of the protocol; the identifier is used to identify a specific type of data or power equipment. For example, if the power processing system needs to receive sensor measurement data from the power equipment, through the data receiving interface, the power processing system provides the expected length and / or the identifier. The data receiving interface retrieves data from the power equipment and returns it to the power processing system, ensuring the integrity and correctness of the data. For example, the power processing system can send a control command to a device with IP address 192.168.1.100 through the sending data interface, wait for the power device to return the execution result of the control command through the receiving data interface, receive the returned status information, and set the IP address and port number of the power device through the protocol initialization interface to ensure the establishment of the communication link.

[0048] In this embodiment, the first abstraction method is a predefined abstraction method for sending data to power equipment, unifying the data reception methods of different protocols, enabling the power processing system to obtain feedback or data from power equipment in a standardized manner. The second abstraction method is a predefined abstraction method for receiving data from power equipment, unifying the sending operations of different communication protocols, enabling the power processing system to send commands or data to power equipment through a consistent interface. The third abstraction method is a predefined abstraction method for initializing the configuration parameters of the communication protocol, unifying the different initialization steps that different protocols may require, ensuring that the necessary configuration is completed before using the protocol. The output of the data sending interface is the status or feedback information of the sending operation, such as success, failure, and error codes. The output of the data receiving interface is the received data content, such as sensor data and device status information. The output of the protocol initialization interface is the status of the initialization operation, indicating whether the communication protocol has been successfully configured.

[0049] The configuration parameters of the communication protocol need to be initialized in the following situations:

[0050] (1) When the IoT system starts up. When the IoT system starts up or the power equipment is powered on, the protocol is usually initialized first. At this time, the IoT system will configure all the parameters required by the communication protocol to ensure that subsequent communication operations can be carried out smoothly. For example, one or more of the parameters such as the baud rate, parity method and timeout of the serial port can be configured.

[0051] (2) Before connection establishment. Protocol initialization is required before establishing a communication connection with power equipment. Especially in connection-based protocols, such as TCP / IP, the initialization configuration steps are usually completed before connection establishment to ensure that the connection parameters are correct.

[0052] (3) Before the start of a communication session. If the communication between the IoT system and the device is session-based, such as requiring a handshake or authentication before each communication, the protocol initialization can be performed before the start of each session to ensure that the configuration in the current session is up-to-date and correct.

[0053] (4) Configuration Changes. If the communication configuration needs to be changed in the system, such as adjusting the baud rate or modifying the timeout, the protocol needs to be re-initialized. This may happen when the IoT system detects that the configuration needs to be adjusted to adapt to the new communication conditions during runtime. During the above data transmission process, transmission anomalies may occur. To address potential transmission anomalies, the second adapter 130 is also used to detect and process anomaly information.

[0054] Optionally, the second adapter 130 is also used to detect abnormal information during data transmission between the power equipment and the power processing system, and to perform the corresponding abnormal handling operation when abnormal information is detected. In this embodiment, different abnormal information corresponding to different abnormal information can be preset, and the corresponding abnormal handling method can be executed according to the detected abnormal information.

[0055] For example, when a communication timeout is detected, it may attempt to resend the data or log the information for subsequent analysis; or, for possible communication timeouts, a timeout detection mechanism can be implemented in the first adapter and the second adapter respectively. When a timeout occurs, in addition to logging the information, the following options can be selected: (1) Abandon the current operation. If the retry fails, the current operation can be abandoned and other tasks can be continued to avoid blocking the entire IoT system. (2) Switch to a backup device or channel. If the IoT system supports multiple communication channels or backup devices, it can attempt to switch to a backup channel after the timeout.

[0056] The technical solution of this embodiment, through the device information configured in the device model 110, allows the IoT system to use the first adapter 120 to receive the power processing system's call to the interface, perform the corresponding operation on the power device, and use the second adapter 130 to receive the second data message from the power processing system, extract the data fields from the second data message, encapsulate it into a protocol message adapted to the power device, and transmit it to the power device. This solves the interoperability and compatibility problems between different devices caused by different communication protocols and data formats in traditional power systems, realizes the compatibility and interoperability of heterogeneous devices in the power system, and greatly improves the system's integration efficiency and operational consistency.

[0057] Example 2

[0058] Figure 2 This is a schematic diagram of another IoT system with heterogeneous devices provided in Embodiment 2 of the present invention. This embodiment is an optimization of the above embodiment. Figure 2 As shown, the IoT system includes at least one IoT device 100. Each IoT device 100 includes a device model 110, a first adapter 120, and a second adapter 130; each IoT device 100 is used to assist a type of electrical equipment in accessing the power processing system.

[0059] Equipment model 110 contains equipment information for power equipment;

[0060] The first end of the first adapter 120 is connected to the power processing system, and the second end of the first adapter 120 is connected to the power equipment. The first adapter 120 includes multiple interfaces, each of which is obtained by encapsulating an operation of a certain type. The first adapter 120 is used to receive calls from the power processing system to the interfaces and to perform the corresponding operations on the power equipment.

[0061] The first end of the second adapter 130 is connected to the power processing system, and the second end of the second adapter 130 is connected to the power equipment. The second adapter 130 uses a protocol abstract interface as its base class and inherits from the base class to execute the following methods: receiving a first data packet transmitted by the power equipment, parsing the first data packet, extracting data fields from the first data packet, converting the extracted data fields into standard format data adapted to the power processing system, and transmitting it to the power processing system; and receiving a second data packet from the power processing system, extracting data fields from the second data packet, encapsulating it into a protocol packet adapted to the power equipment, and transmitting it to the power equipment.

[0062] The device management module 200 is used to read the description file of the power equipment when the power equipment is connected to the system, assign an identifier to the power equipment based on the description file, register the power equipment, load the corresponding adapter identifier and communication protocol according to the configuration file of the power equipment, and configure the communication parameters of the power equipment.

[0063] Specifically, the device management module 200 automatically loads the corresponding adapter and communication protocol based on the power device's description file and dynamically configures the power device's communication parameters. Its workflow is roughly as follows: a new power device connects to the IoT system via network, serial port, or other communication methods; the device management module detects the new power device and reads its description file; the IoT system assigns a unique identifier to the power device based on the description file and registers it; the corresponding adapter and communication protocol are automatically loaded based on the description file, and the power device's communication parameters are configured; the IoT system continuously monitors the power device's operating status to ensure it functions normally. Optionally, the device management module 240 can add new adapters and protocol support to the IoT system via plugins.

[0064] Optionally, the device management module 200 also performs compatibility testing on the power equipment, wherein the data items for compatibility testing include one or more of the following: communication protocol, data format, functional interface, and configuration interface.

[0065] Specifically, communication protocol detection can be performed by analyzing the protocol fields in the description file of the power equipment to check whether the communication protocol used by the new power equipment is already supported by the IoT system. If the communication protocol is incompatible, the IoT system will prompt the user to manually configure it or develop a new second adapter. Data format detection can be performed by the IoT system to check whether the data format of the new power equipment conforms to standardization requirements, including but not limited to data types, units, and field structures. If incompatible formats are found, the IoT system will prompt the user to make configuration adjustments. Functional interface detection can be performed by the IoT system to check whether the functional interfaces of the new power equipment are compatible with the existing IoT system. For example, this could be read / write commands, control instructions, etc. If the functional interfaces are incompatible, the IoT system will prompt the user to update the first adapter or develop a new interface adapter. The configuration interface can be developed to provide a user-friendly configuration interface, allowing users to manually configure device parameters or choose to upload new first adapter code when incompatible devices are detected. Optional configuration interfaces support visual operation and real-time feedback.

[0066] Optionally, the system also includes a test module 300 for simulating multiple types of electronic devices and / or multiple protocols to perform compatibility testing on the IoT system.

[0067] Specifically, based on test module 300, the operation of various power devices and protocols is simulated to conduct comprehensive compatibility testing of the IoT system. For example, test cases and results of different power devices and protocols can be collected and archived through a compatibility test library for subsequent analysis and system optimization. The testing process is roughly as follows: Based on the power device description files and protocols, automated test cases suitable for the IoT system are generated; the communication protocols in the test cases are simulated to generate test data streams that conform to the specifications; the data streams and behaviors of the simulated devices are generated to test the device compatibility of the IoT system; the simulated operations are run according to the test cases, the response behavior of the IoT system is recorded, and a test report is generated; the test results are collected and stored in the compatibility test library for subsequent analysis and system optimization.

[0068] The technical solution of this embodiment utilizes the device information configured in the device model 110. The IoT system uses the first adapter 120 to receive calls from the power processing system to the interface, performs operations corresponding to the interface on the power equipment, and uses the second adapter 130 to receive the second data message from the power processing system. The data fields in the second data message are extracted, encapsulated into a protocol message adapted to the power equipment, and transmitted to the power equipment. Data from different protocols is converted into a format common to the IoT system, thereby achieving data compatibility and interoperability between heterogeneous protocols. The device management module 140 automatically loads the corresponding adapter and communication protocol through the description file of the power equipment and dynamically configures the communication parameters of the power equipment. Based on the testing module, the operation of various power equipment and protocols is simulated to conduct a comprehensive test of the compatibility of the IoT system for subsequent analysis and system optimization. This achieves compatibility and interoperability of heterogeneous devices in the power system, significantly improving the system integration efficiency and operational consistency.

[0069] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. An IoT system for heterogeneous devices, characterized in that, At least one IoT device, the IoT device including a device model, a first adapter and a second adapter; each IoT device is used to assist a type of power device in accessing a power processing system; The equipment model contains the equipment information of the power equipment; The first end of the first adapter is connected to the power processing system, and the second end of the first adapter is connected to the power equipment. The first adapter includes multiple interfaces, each of which is obtained by encapsulating an operation of a certain type. The first adapter is used to receive calls from the power processing system to the interfaces and to perform the operations corresponding to the interfaces on the power equipment. The first end of the second adapter is connected to the power processing system, and the second end of the second adapter is connected to the power equipment. The second adapter uses a protocol abstract interface as its base class and inherits the base class to perform the following methods: receiving a first data packet transmitted by the power equipment, parsing the first data packet, extracting data fields from the first data packet, converting the extracted data fields into standard format data adapted to the power processing system, and transmitting them to the power processing system. In addition, the system receives a second data message from the power processing system, extracts the data fields from the second data message, encapsulates them into a protocol message adapted to the power equipment, and transmits it to the power equipment.

2. The system according to claim 1, characterized in that, The interfaces in the first adapter include a data read interface, a data write interface, and a command execution interface.

3. The system according to claim 1, characterized in that, The protocol abstraction interface includes a data sending interface, a data receiving interface, and a protocol initialization interface; The data transmission interface is a predefined first abstract method, which is used to send data to the power equipment. The input parameters of the first abstract method include the data content and the target device address. The data receiving interface is a predefined second abstract method, which is used to receive data from the power equipment. The input parameters of the second abstract method include expected length and / or identifier. The protocol initialization interface is a predefined third abstract method used to initialize the configuration parameters of the communication protocol.

4. The system according to claim 1, characterized in that, The second adapter is further configured to, after extracting the data fields from the first data message, map the data fields to the standard fields of the power processing system; The second adapter pre-stores field mapping rules corresponding to the power equipment, and the field mapping rules include the mapping relationship between the data dictionary of the power equipment and the standard fields of the power processing system.

5. The system according to claim 1, characterized in that, The second adapter is also used to extract data fields from the first data message, standardize the data fields, and convert the extracted data fields into standard format data adapted to the power processing system.

6. The system according to claim 1, characterized in that, The second adapter is also used to detect abnormal information during the data transmission process between the power equipment and the power processing system, and to perform the abnormal handling operation corresponding to the abnormal information when abnormal information is detected.

7. The system according to claim 1, characterized in that, The device information configured in the device model includes one or more of the following: device identifier, device type, device attributes, device function, and data format.

8. The system according to claim 1, characterized in that, The system also includes a device management module, which, when the power equipment is connected to the system, reads the description file of the power equipment, assigns an identifier to the power equipment based on the description file, registers the power equipment, loads the corresponding adapter identifier and communication protocol according to the configuration file of the power equipment, and configures the communication parameters of the power equipment.

9. The system according to claim 8, characterized in that, The device management module also performs compatibility testing on the power equipment, wherein the data items for compatibility testing include one or more of the following: communication protocol, data format, functional interface, and configuration interface.

10. The system according to claim 1, characterized in that, The system also includes a testing module for simulating multiple types of electronic devices and / or multiple protocols to perform compatibility testing on the IoT system.

Images