A protocol compatible architecture for dynamic environment monitoring system

By designing the protocol compatibility architecture of the dynamic ring monitoring system, the access complexity caused by the different protocols of the dynamic ring equipment and the monitoring host is solved, fast compatibility and high compatibility are achieved, and user configuration complexity is reduced.

CN119363842BActive Publication Date: 2025-04-01BEIJING ZHONGYI YUETAI SCI & TECH

Patent Information

Application Number
CN202411925569.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-12-25
Publication Date
2025-04-01
Estimated Expiration
2044-12-25

AI Technical Summary

Technical Problem

In the existing dynamic ring monitoring system, due to the different transmission methods and communication protocols of dynamic ring equipment and monitoring hosts, access to new devices is complicated and rapid compatibility cannot be achieved.

Method used

A protocol compatibility architecture for dynamic ring monitoring system is designed, including device base class, data transmission base class, sending base class, receiving base class, transmission implementation class and device implementation class. Through these base classes and implementation classes, private protocols and standard protocols are uniformly processed to achieve protocol compatibility.

Benefits of technology

It realizes fast compatibility between the dynamic ring equipment and the monitoring host, and is not restricted by the protocol type, reduces the complexity and difficulty of user configuration, and improves the compatibility and ease of use of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119363842B_ABST
    Figure CN119363842B_ABST
Patent Text Reader

Abstract

The present application discloses a protocol-compatible architecture for a dynamic environment monitoring system. The embodiment of the present application defines the conditions required for dynamic environment devices to collect data by including a device base class, and further includes a data transmission base class that handles data transmission processing for a predetermined protocol type, a sending base class and a receiving base class that provide a sending encapsulation coding abstract method and a receiving coding abstract method for a predetermined protocol type, a transmission implementation class that implements the data transmission base class for a protocol type, and a device implementation class that implements the corresponding device for a device type, thereby unifying the processing methods of private protocols and standard protocols, and is not constrained by protocol types. For newly added protocol types, it is only necessary to make specific implementations of the newly added types for the transmission base class, request base class, and response base class, thereby achieving higher compatibility.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the technical field of dynamic environment monitoring, and in particular to a protocol compatible architecture of a dynamic environment monitoring system. Background Art

[0002] With the development of science and technology, the rapid expansion of the Internet and big data, the importance of data centers is also increasing. At present, one of the biggest challenges facing the dynamic environment monitoring system of data centers is how to quickly access new dynamic environment equipment. This is mainly because there are many types of dynamic environment equipment and monitoring hosts in data centers, involving multiple brands and models. Even for the same type of equipment, different manufacturers may use different transmission methods and communication protocols, which further increases the complexity of access.

[0003] Therefore, a technical solution is needed that can achieve compatibility of different protocols. Summary of the invention

[0004] The embodiment of the present application provides a protocol compatible architecture of a dynamic environment monitoring system to solve the defect of complex access between dynamic environment devices and hosts in the dynamic environment monitoring system in the prior art due to different transmission methods and communication protocols.

[0005] To achieve the above objectives, the present application provides a protocol compatible architecture of a dynamic environment monitoring system, including:

[0006] A device base class, which is used to define the conditions required for the dynamic environment device used in the dynamic environment monitoring system to collect data;

[0007] A data transmission base class, which is used to process data transmission processing oriented to a predetermined protocol type;

[0008] A sending base class, the sending base class is used to provide an abstract method for sending encapsulation encoding oriented to the predetermined protocol type;

[0009] A receiving base class, the receiving base class is used to provide a receiving encoding abstract method for the predetermined protocol type;

[0010] A transmission implementation class, the transmission implementation class is used to implement the data transmission base class for one of the multiple protocol types;

[0011] A device implementation class is used to implement a device corresponding to a device type among multiple device types.

[0012] According to a protocol compatible architecture of a dynamic environment monitoring system of an embodiment of the present application, the conditions required for dynamic environment devices to collect data are defined by including a device base class, which further includes a data transmission base class that handles data transmission processing for a predetermined protocol type, a sending base class and a receiving base class that provide a sending encapsulation coding abstract method and a receiving coding abstract method for a predetermined protocol type, a transmission implementation class that implements the data transmission base class for a protocol type, and a device implementation class that implements the corresponding device for a device type, thereby unifying the processing methods of private protocols and standard protocols, and is not restricted by protocol types. For newly added protocol types, only the specific implementation of the newly added types needs to be done for the transmission base class, request base class, and response base class, achieving higher compatibility.

[0013] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present application. Also, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0015] Figure 1 It is a flowchart showing an embodiment of a protocol compatible architecture of a dynamic environment monitoring system provided by the present application. DETAILED DESCRIPTION

[0016] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0017] One of the biggest challenges facing the dynamic environment monitoring system in data centers is how to quickly access new dynamic environment equipment. This is mainly because there are many types of dynamic environment equipment and monitoring hosts in data centers, involving multiple brands and models. Even for the same type of equipment, different manufacturers may use different transmission methods and communication protocols, further increasing the complexity of access.

[0018] In order to solve this problem, manufacturers of dynamic environment monitoring systems usually adopt standardized protocol encapsulation to avoid customized development every time according to the actual configuration scenario of the data center. Common standard protocols include Modbus, total power protocol and SNMP. Based on these standard protocols, manufacturers will parse the protocol content of the equipment, split the measurement points to be collected into collection locations and measurement point names, and configure them into the system. In this way, from the perspective of software development, the system can avoid confusion in the program structure to a large extent. Since the system only needs to process its own logic according to different standard protocols, and the types of standard protocols are relatively limited, the architecture of the entire system can be kept simple and clear.

[0019] However, in the prior art, for standard protocols, system users need to perform a lot of configuration work in the early stage of use. This is not only time-consuming, but also requires a high level of professionalism from users, who at least need to be able to read and understand communication protocols. This is undoubtedly a big challenge for many users.

[0020] In addition, due to the limitations of the system architecture, when dealing with non-standard protocol devices, it is impossible to develop separately according to the specific characteristics of the device. Therefore, most manufacturers will provide a "universal protocol configuration" function. The so-called universal protocol means that the parsing and sending rules are configured by the application layer according to the protocol specifications provided by the device manufacturer. This function makes up for the shortcoming that the system cannot directly parse non-standard protocols and improves the system's compatibility with diverse devices.

[0021] Although this system structure provides configuration parsing functions for non-standard protocols, the configuration is still difficult. From the perspective of software development, no matter how the configuration method is optimized, it is essentially still a preset - that is, the software needs to be pre-made in advance before the user can configure it based on it. However, if the target device uses protocols such as WebSocket, HTTP, MQTT, etc., it is almost impossible to complete the complete protocol specification through byte-by-byte configuration. For example, if the device uses a private encapsulation protocol based on TCP / IP at the application layer, its verification method, data transmission and reception mechanism, etc. are difficult to predict, and it is impossible to achieve compatibility through simple configuration. Therefore, this so-called "universal protocol" function is actually difficult to achieve the expected effect, and the access problem of non-standard protocols is still a major problem.

[0022] In this regard, the present application proposes a protocol compatible architecture for a dynamic environment monitoring system. Figure 1As shown in , the protocol compatible architecture of the dynamic environment monitoring system according to the embodiment of the present application may include: a device base class 101, a data transmission base class 102, a sending base class 103, a receiving base class 104, a transmission implementation class 105, and a device implementation class 106. The device base class 101 can communicate with the data transmission base class 102 and can receive data sent by the device implementation class 106. The data transmission base class 102 can further communicate with the receiving base class 104 and the sending base class 103, and can receive data sent by the transmission implementation class 105. The receiving base class 104 can receive data sent by the receiving implementation class 1041, and the sending base class 103 can receive data sent by the sending implementation class 1031. Both the receiving implementation class 1041 and the sending implementation class 1031 can communicate with the transmission implementation class 105. The transmission implementation class 105 can communicate with the device implementation class 106.

[0023] In the embodiment of the present application, the device base class 101 can be used to define the conditions required for the dynamic environment device used in the dynamic environment monitoring system to collect data. For example, the device base class 101 may include a data transmission module 1011, a data analysis module 1012, and a data cache module 1013. The data transmission module 1011 can be used to perform data transmission and reception processing, the data analysis module 1012 can be used to perform measurement point splitting processing, and the data cache module 1013 can be used to perform device measurement point data storage.

[0024] The data transmission base class 102 can be used to process data transmission processing for a predetermined protocol type. For example, the data transmission base class 102 may include data transmission attributes, data reception attributes, and protocol type attributes, and the data transmission attributes are used to process data transmission encapsulation for a predetermined protocol type, and the data reception attributes can be used to process data reception parsing for a predetermined protocol type. In particular, the data transmission base class 102 can be combined with the device base class 101 as an important attribute, and three main attributes of data transmission (request), data reception (response), and protocol type (protocol) are provided respectively. In an embodiment of the present application, the predetermined protocol type for which the data transmission attribute and the data reception attribute are targeted can be a private protocol based on TCP or UDP, standard protocols such as websocket, http, mqtt, modbus, etc.), and therefore data transmission encapsulation and data reception preliminary parsing can be performed for this type of protocol respectively.

[0025] The sending base class 103 can be used to provide an abstract method for sending encapsulation coding for a predetermined protocol type, and the receiving base class 104 can be used to provide an abstract method for receiving coding for a predetermined protocol type. And in use, the inheritors can implement them specifically according to their respective transmission modes. In the embodiment of the present application, the protocol type used by the sending base class 103 and the receiving base class 104 is an enumeration of the currently implemented protocols, which is used to identify the specific protocol type used by the subclass.

[0026] The transmission implementation class 105 can be used to implement a data transmission base class for one of the multiple protocol types. For example, the transmission implementation class 105 can include a request implementation class 1051 for the current transmission mode of a protocol type and a response implementation class 1052 for the current transmission mode of a protocol type. In the request implementation class 1051, an encoding method for connecting to the computer transmission layer for data transmission can be added, and in the response implementation class 1052, a decoding method for receiving and parsing valid data information fed back by the dynamic environment device can be added.

[0027] For example, as a transmission implementation class 105 that is a specific implementation of a data transmission base class for a protocol type, it combines a request implementation class for the current transmission mode, aggregates the corresponding implementation class for the current transmission mode, and adds an encoding method in the request implementation class 1051 for connecting to the computer transmission layer for data transmission, and adds a decoding method in the response implementation class 1052 for receiving and parsing the valid data information fed back by the device. In the embodiment of the present application, the request implementation class 1051 of the transmission implementation class 105 contains at least one of the slave station address, function code, starting position, and length as an attribute, and is used to form such attributes into a byte array according to the specification of a protocol type, and encode using an encoding method. The response implementation class 1052 may contain an attribute corresponding to at least one of the slave station address, function code, starting position, and length, and is used to reverse the received byte array to obtain the data part. For example, in the embodiment of the present application, the current transmission implementation class 105 is oriented to the modbus-rtu protocol, then in the request implementation class 1051, there will be attributes such as slave address, function code, starting position, length, etc., and the specific implementation of the decoding implementation method will form these unique attributes into a byte array according to the protocol specification to complete the transmission encoding; and in the response implementation class 1052, there will also be corresponding response packet attributes, and the received byte array will be reversed to obtain the data part, that is, the valid data information. Therefore, in the embodiment of the present application, when a new protocol needs to be compatible, it is only necessary to perform the above processing again and add the sending and receiving methods of the protocol to the transmission implementation class.

[0028] The device implementation class 106 can be used to implement a device corresponding to a device type among multiple device types. For example, in an embodiment of the present application, the device implementation class 106 is a specific implementation for a type of device, combining the transmission mode used by the device, that is, one of the transmission implementation classes 105. Therefore, when adding a new device, it is only necessary to implement the parsing module to assign a value to the device according to the rules given by the device measurement point to the data part in the response implementation class 1052 in the transmission mode of this class, that is, to set the value to the data cache, so that the dynamic environment data can be finally obtained. Therefore, in an embodiment of the present application, when a new device needs to be added, that is, it has not been added to the dynamic environment monitoring system before, it is only necessary to execute the above-mentioned processing in the device implementation class again to add the device to the device implementation class 106.

[0029] Therefore, the protocol-compatible architecture of the dynamic environment monitoring system according to the embodiment of the present application is used to unify the processing methods of private protocols and standard protocols, without being restricted by the protocol type. For newly added protocol types, new protocol types can be added by simply implementing the transmission base class, request base class, and response base class, thereby greatly improving compatibility. The degree of coupling between modules is low and is not constrained by other modules. Whether it is between transmission protocols or devices, each implements the top-level strategy, and the isolation between modules is strong. When a module has a problem, other modules can still operate normally and are not affected. The system is easy to deploy, and users do not need to perform a lot of configuration according to specific devices and protocols after deployment. You only need to know the communication address of the device (such as IP, port, etc.) to enter the device through the device implementation class to achieve plug-and-play.

[0030] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0031] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A protocol compatible architecture of a dynamic environment monitoring system, characterized in that: include: A device base class, which is used to define the conditions required for the dynamic environment device used in the dynamic environment monitoring system to collect data; A data transmission base class, which is used to process data transmission processing oriented to a predetermined protocol type; A sending base class, the sending base class is used to provide an abstract method for sending encapsulation encoding oriented to the predetermined protocol type; A receiving base class, the receiving base class is used to provide a receiving encoding abstract method for the predetermined protocol type; A transmission implementation class, the transmission implementation class is used to implement the data transmission base class for one of the multiple protocol types; a device implementation class, the device implementation class being used to implement a device corresponding to a device type among multiple device types, The device base class includes a data transmission module, a data analysis module and a data cache module, wherein the data transmission module is used to perform data transmission and reception processing, the data analysis module is used to perform measurement point splitting processing, and the data cache module is used to perform device measurement point data storage, The data transmission base class includes data transmission attributes, data reception attributes and protocol type attributes, and the data transmission attributes are used to process data transmission encapsulation for a predetermined protocol type, and the data reception attributes are used to process data reception parsing for a predetermined protocol type. The transmission implementation class includes a request implementation class for the current transmission mode of the one protocol type and a response implementation class for the current transmission mode of the one protocol type. The request implementation class is added with a coding method for connecting to the computer transport layer to send data, and A decoding method for receiving and parsing valid data information fed back by the dynamic environment device is added to the response implementation class. The device implementation class includes an analysis module, which is used to respond to the data part obtained by inverse analysis in the implementation class in the transmission mode of the device type corresponding to the device implementation class, and set the value to the data cache module in the device base class as dynamic loop data according to the rules provided by the device measurement point.

2. The protocol compatible architecture of the dynamic environment monitoring system according to claim 1 is characterized in that: The request implementation class of the transmission implementation class includes at least one of a slave station address, a function code, a starting position, and a length as an attribute, and is used to form a byte array of the attribute according to the specification of the protocol type, and encode it using the encoding method, The response implementation class includes an attribute corresponding to at least one of a slave station address, a function code, a starting position, and a length, and is used to decrypt the received byte array to obtain a data portion.

Citation Information

Patent Citations

  • Alarm method and system, electronic equipment, storage medium and chip

    CN118900228A

  • Data center dynamic environment monitoring system communication protocol optimization method

    CN119030897A

Cited By

  • Protocol processing system supporting dynamic compatibility

    CN121078147A