A link encapsulation method and device based on unified equipment monitoring modeling encapsulation

Abstract

This invention discloses a link encapsulation method and apparatus based on unified device monitoring modeling encapsulation. The method includes: acquiring link information between various types of devices to be monitored; determining a graphical monitoring interface, preset link algorithms, and communication interfaces based on the link information; constructing a device graphical model, a backup switching model, a combined usage model, a batch control model, a southbound communication interface model, a northbound communication interface model, and an external call interface model based on the graphical monitoring interface, preset link algorithms, and communication interfaces; and encapsulating the device graphical model, backup switching model, combined usage model, batch control model, southbound communication interface model, northbound communication interface model, and external call interface model into a link driver file based on object-oriented programming encapsulation and polymorphism techniques. This invention can greatly simplify the complexity of device monitoring construction, shorten the construction cycle, reduce investment costs, and provide customized device monitoring functions.

Description

Technical Field

[0001] The present invention relates to the technical field of information systems, and in particular to a link encapsulation method and device based on unified equipment monitoring modeling encapsulation. Background Art

[0002] At present, the traditional equipment monitoring system is based on different business functions, using a set of equipment to build a set of equipment monitoring systems. There are problems such as long system construction cycle, large number of equipment, and high management difficulty. The monitored equipment in the system is tightly bound to the system, and the type of monitoring equipment can only be selected in the early design stage. Once put into use, the old equipment cannot be updated, increasing operation and management costs. It is also very easy to have no spare parts for old equipment or the replacement process requires the redevelopment of the system, which brings many inconveniences. Summary of the invention

[0003] The technical problem solved by the present invention is to overcome the deficiencies of the prior art and provide a link encapsulation method and device based on unified device monitoring modeling encapsulation.

[0004] The technical solution of the present invention is:

[0005] In a first aspect, an embodiment of the present invention provides a link encapsulation method based on unified device monitoring modeling encapsulation, including:

[0006] Obtain link information between various types of devices that need to be monitored;

[0007] Determine a graphical monitoring interface, a preset link algorithm and a communication interface according to the link information;

[0008] According to the graphical monitoring interface, the preset link algorithm and the communication interface, a device graphical model, a backup switching model, a combined use model, a batch control model, a southbound communication interface model, a northbound communication interface model and an external call interface model are constructed;

[0009] Based on the encapsulation and polymorphism technology of object-oriented programming, the device graphic model, the backup switching model, the combined use model, the batch control model, the southbound communication interface model, the northbound communication interface model and the external call interface model are encapsulated into a link driver file.

[0010] Optionally, the link information includes: device type information, device quantity information, device connection relationship, device backup relationship, device combination use logic and device batch control logic within the link.

[0011] Determining a graphical monitoring interface, a preset link algorithm and a communication interface according to the link information includes:

[0012] According to the device type information, the device quantity information, the device connection relationship and the device backup relationship in the link, a graphical monitoring interface corresponding to the link is designed;

[0013] According to the device connection relationship and the device backup relationship, a backup switching algorithm corresponding to the backup switching mechanism of the monitored device is designed;

[0014] According to the device combination use logic, a combined use algorithm of the device linkage relationship and the device control sequence logic when the devices are used in combination is designed;

[0015] According to the equipment batch control logic, a batch control algorithm corresponding to the simultaneous control mechanism of multiple equipments is designed;

[0016] Based on the logic of collecting all device information in the link and the logic of issuing device control instructions, the southbound communication interface between the link and the device is designed;

[0017] According to the link combination use logic and device batch control logic, the northbound communication interface is designed;

[0018] According to the type and purpose of the device in the link, an external call interface corresponding to the external call interface mechanism of the driver file is designed.

[0019] Optionally, the device graphic model, the backup switching model, the combined use model, the batch control model, the southbound communication interface model, the northbound communication interface model and the external call interface model are constructed according to the graphical monitoring interface, the preset link algorithm and the communication interface, including:

[0020] According to the graphical monitoring interface, backup switching algorithm, combined use algorithm, batch control algorithm, southbound communication interface, northbound communication interface and external call interface, the device graphic model, backup switching model, combined use model, batch control model, southbound communication interface model, northbound communication interface model and external call interface model are constructed in sequence.

[0021] Optionally, all devices in the link and their connection relationships are displayed in the main interface area, with icons representing devices and solid lines representing connection relationships between devices;

[0022] In the parameter monitoring area, the key parameter point information of all devices in the link is displayed;

[0023] The batch command area displays options for combining logic and batch control logic for all devices in the link.

[0024] Optionally, both the southbound communication interface and the northbound communication interface use the UDP protocol, wherein the network communication port number of the southbound communication interface is information automatically generated by the system, and the network communication port number of the northbound communication interface is fixed information.

[0025] Optionally, the encapsulation and polymorphism technology based on object-oriented programming encapsulates the device graphic model, the backup switching model, the combined use model, the batch control model, the southbound communication interface model, the northbound communication interface model and the external call interface model into a link driver file, including:

[0026] Encapsulating the device graphic model, the backup switching model, the combined use model, the batch control model, the southbound communication interface model, the northbound communication interface model and the external call interface model into a form dynamic link library file;

[0027] The form dynamic link library file is used as the link driver file.

[0028] In a second aspect, an embodiment of the present invention provides a link encapsulation device based on unified device monitoring modeling encapsulation, including:

[0029] The link information acquisition module is used to obtain the link information between various types of devices that need to be monitored;

[0030] A communication interface determination module, used to determine a graphical monitoring interface, a preset link algorithm and a communication interface according to the link information;

[0031] A model building module, used to build a device graphic model, a backup switching model, a combined use model, a batch control model, a southbound communication interface model, a northbound communication interface model and an external call interface model according to the graphical monitoring interface, the preset link algorithm and the communication interface;

[0032] A driver file acquisition module is used to encapsulate the device graphic model, the backup switching model, the combined use model, the batch control model, the southbound communication interface model, the northbound communication interface model and the external call interface model into a link driver file based on the encapsulation and polymorphism technology of object-oriented programming.

[0033] Optionally, the link information includes: device type information, device quantity information, device connection relationship, device backup relationship, device combination use logic and device batch control logic within the link.

[0034] The communication interface determination module comprises:

[0035] A monitoring interface design unit, configured to design a graphical monitoring interface corresponding to the link according to the device type information, the device quantity information, the device connection relationship and the device backup relationship in the link;

[0036] A backup switching algorithm design unit, used to design a backup switching algorithm corresponding to the backup switching mechanism of the monitored device according to the device connection relationship and the device backup relationship;

[0037] A combined use algorithm design unit, used to design a combined use algorithm for obtaining a device linkage relationship and a device control sequence logic when the devices are used in combination according to the device combined use logic;

[0038] A batch control algorithm design unit, used to design a batch control algorithm corresponding to a simultaneous control mechanism of multiple devices according to the device batch control logic;

[0039] The southbound communication interface design unit is used to design the southbound communication interface between the link and the device according to the collection logic of all device information in the link and the logic of issuing device control instructions;

[0040] A northbound communication interface design unit, used for designing a northbound communication interface according to link combination use logic and device batch control logic;

[0041] The external call interface design unit is used to design an external call interface corresponding to the external call interface mechanism of the driver file according to the type and purpose of the device in the link.

[0042] Optionally, the model building module includes:

[0043] A model building unit is used to construct a device graphic model, a backup switching model, a combined use model, a batch control model, a southbound communication interface model, a northbound communication interface model and an external call interface model in sequence according to the graphical monitoring interface, the backup switching algorithm, the combined use algorithm, the batch control algorithm, the southbound communication interface, the northbound communication interface and the external call interface.

[0044] Optionally, all devices in the link and their connection relationships are displayed in the main interface area, with icons representing devices and solid lines representing connection relationships between devices;

[0045] In the parameter monitoring area, the key parameter point information of all devices in the link is displayed;

[0046] The batch command area displays options for combining logic and batch control logic for all devices in the link.

[0047] Optionally, both the southbound communication interface and the northbound communication interface use the UDP protocol, wherein the network communication port number of the southbound communication interface is information automatically generated by the system, and the network communication port number of the northbound communication interface is fixed information.

[0048] Optionally, the drive file acquisition module includes:

[0049] A link library file acquisition unit, used to encapsulate the device graphic model, the backup switching model, the combined use model, the batch control model, the southbound communication interface model, the northbound communication interface model and the external call interface model into a form dynamic link library file;

[0050] The driver file acquisition unit is used to use the form dynamic link library file as the link driver file.

[0051] The advantages of the present invention compared with the prior art are:

[0052] The link encapsulation method and device based on unified equipment monitoring modeling encapsulation provided by the embodiment of the present invention are suitable for the unified construction of equipment monitoring of multiple business types, and can realize the rapid construction and intelligent evolution of the monitoring system. The method is based on the .net platform, and the interface information of the business link composed of different devices is unified and abstracted, the interface information is modeled and processed, and encapsulated into a link driver file in the form of a dynamic link library with a unique identifier. The unique calling interface of the link driver file is called by the reflection mechanism, and the dynamic loading of the link driver file can be realized. The present invention has the characteristics of strong scalability, high reliability, simple operation, and easy maintenance. The link interfaces of different business types are unified into northbound interfaces and southbound interfaces of the same format, which greatly simplifies the complexity of equipment monitoring construction, shortens the construction period, reduces investment costs, can provide customized equipment monitoring functions, and has a good interface that can be secondary developed. It is particularly suitable for the field of large-scale station network-level equipment monitoring. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 A flowchart of a link encapsulation method based on unified device monitoring modeling encapsulation provided by an embodiment of the present invention;

[0054] Figure 2 A schematic diagram of a link driver file creation process provided by an embodiment of the present invention;

[0055] Figure 3 A schematic structural diagram of a link encapsulation device based on unified device monitoring modeling encapsulation provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0056] In order to solve the problems of quickly establishing and transforming a device monitoring system, uniformly encapsulating northbound interfaces of devices of different types and models, and being compatible with the monitoring of multiple types of devices, the embodiment of the present invention provides a link encapsulation method based on unified device monitoring modeling encapsulation. Next, the technical solution of the embodiment of the present invention is described in detail in combination with the following embodiments.

[0057] Embodiment 1

[0058] Reference Figure 1 , shows a flowchart of the steps of a link encapsulation method based on unified device monitoring modeling encapsulation provided by an embodiment of the present invention, such as Figure 1 As shown, the link encapsulation method based on unified device monitoring modeling encapsulation may include the following steps:

[0059] Step 101: Obtain link information between various types of devices that need to be monitored.

[0060] In an embodiment of the present invention, first, various types of devices that need to be monitored can be obtained, and then the link information between various types of devices can be obtained, wherein the link information may include: device type information within the link, device quantity information, device connection relationship, device backup relationship, device combination use logic, and device batch control logic.

[0061] After obtaining the link information between the various types of devices that need to be monitored, step 102 is executed.

[0062] Step 102: Determine a graphical monitoring interface, a preset link algorithm and a communication interface according to the link information.

[0063] After obtaining the link information between various types of devices that need to be monitored, a graphical monitoring interface, a preset link algorithm and a communication interface can be determined according to the link information. Specifically, it can be described in detail in combination with the following specific implementation method.

[0064] In a specific implementation of the embodiment of the present invention, the link information includes: device type information, device quantity information, device connection relationship, device backup relationship, device combination use logic and device batch control logic in the link, and the above step 102 may include:

[0065] Sub-step A1: designing a graphical monitoring interface corresponding to the link according to the device type information, the device quantity information, the device connection relationship and the device backup relationship in the link;

[0066] Sub-step A2: designing a backup switching algorithm corresponding to the backup switching mechanism of the monitored device according to the device connection relationship and the device backup relationship;

[0067] Sub-step A3: according to the device combination use logic, design a combination use algorithm for obtaining the device linkage relationship and device control sequence logic when the devices are used in combination;

[0068] Sub-step A4: designing a batch control algorithm corresponding to the simultaneous control mechanism of multiple devices according to the device batch control logic;

[0069] Sub-step A5: According to the collection logic of all device information in the link and the logic of issuing device control instructions, a southbound communication interface between the link and the device is designed;

[0070] Sub-step A6: designing a northbound communication interface according to the link combination use logic and the device batch control logic;

[0071] Sub-step A7: According to the type and purpose of the device in the link, an external call interface corresponding to the external call interface mechanism of the driver file is designed.

[0072] In the embodiment of the present invention, after the link information is acquired, a graphical monitoring interface design can be performed on the link according to the device type information, device quantity information, device connection relationship, and device backup relationship in the link.

[0073] The backup switching algorithm can be designed for the backup switching mechanism of the monitored device according to the device connection relationship and the device backup relationship.

[0074] According to the logic of device combination use, the device linkage relationship and device control sequence logic when the devices are used in combination can be designed as a combination use algorithm.

[0075] Based on the equipment batch control logic, batch control algorithm design can be performed for the simultaneous control mechanism of multiple devices.

[0076] The southbound communication interface design between the link and the device can be carried out based on the collection logic of all device information in the link and the logic of issuing device control instructions.

[0077] The northbound communication interface design can be performed based on the link combination logic and device batch control logic.

[0078] The external calling interface mechanism of the driver file may be designed according to the type and purpose of the device in the link.

[0079] After the graphical monitoring interface, the preset link algorithm and the communication interface are determined according to the link information, step 103 is executed.

[0080] Step 103: According to the graphical monitoring interface, the preset link algorithm and the communication interface, a device graphic model, a backup switching model, a combination use model, a batch control model, a southbound communication interface model, a northbound communication interface model and an external call interface model are constructed.

[0081] After determining the graphical monitoring interface, preset link algorithm and communication interface according to the link information, a device graphic model, a backup switching model, a combination use model, a batch control model, a southbound communication interface model, a northbound communication interface model and an external call interface model can be constructed based on the graphical monitoring interface, the preset link algorithm and the communication interface. Specifically, it can be described in detail as follows in combination with the following specific implementation method.

[0082] In another specific implementation of the embodiment of the present invention, the above step 103 may include:

[0083] Sub-step B1: According to the graphical monitoring interface, backup switching algorithm, combined use algorithm, batch control algorithm, southbound communication interface, northbound communication interface and external call interface, construct the device graphic model, backup switching model, combined use model, batch control model, southbound communication interface model, northbound communication interface model and external call interface model in sequence.

[0084] In an embodiment of the present invention, according to the design ideas of the graphical monitoring interface backup switching algorithm, combined use algorithm, batch control algorithm, southbound communication interface, northbound communication interface and external call interface, a device graphic model, a backup switching model, a combined use model, a batch control model, a southbound communication interface model, a northbound communication interface model and an external call interface model can be constructed in sequence.

[0085] Step 104: Based on the encapsulation and polymorphism technology of object-oriented programming, the device graphic model, the backup switching model, the combined use model, the batch control model, the southbound communication interface model, the northbound communication interface model and the external call interface model are encapsulated into a link driver file.

[0086] After obtaining the above model, the three types of information, file type, link type, and link number, can be used as references to mark the unique external call identifier of the link driver file, and the device graphic model, backup switching model, combination model, batch control model, southbound communication interface model, northbound communication interface model, and external call interface model can be encapsulated into a link driver file using object-oriented programming encapsulation and polymorphism technology.

[0087] In a specific implementation of an embodiment of the present invention, the device type information specifically refers to the division of device usage in different fields, such as in the field of satellite measurement and control, antenna radio frequency equipment, intermediate frequency equipment and auxiliary equipment (such as air conditioners, de-icing controllers, temperature and humidity sensors, etc.) used in the process of signal modulation and demodulation; the device connection relationship specifically refers to the connection relationship between the device and other devices during operation, such as the connection relationship between up and down converters and power amplifiers between devices during signal modulation and demodulation; the device backup relationship specifically refers to the relationship between devices with the same function that can replace each other when the device is in operation; the device combination use logic specifically refers to the order in which different devices change their working states in order to complete a specific function; the device batch control logic specifically refers to the order in which devices of the same type change their working states in order to complete a specific function;

[0088] In a specific implementation of the embodiment of the present invention, a graphical monitoring interface is designed for the link according to the device type information, device quantity information, device connection relationship, and device backup relationship in the link, specifically designing the main interface area, parameter monitoring area, and batch instruction area;

[0089] In a specific implementation of an embodiment of the present invention, the main interface area displays all devices in the link and their connection relationships, with icons representing devices and line segments representing the connection relationships between devices; the parameter monitoring area is a display area for key parameter point information of all devices in the link; and the batch instruction area displays options for combined use logic and batch control logic for all devices in this link.

[0090] In a specific implementation of the embodiment of the present invention, the design of the combined use algorithm must strictly control the order of changing the working state of the equipment to prevent the normal working state of the equipment from being damaged.

[0091] In a specific implementation of an embodiment of the present invention, both the southbound communication interface and the northbound communication interface use the UDP protocol, wherein the network communication port number of the southbound interface is information automatically generated according to the system, and the network communication port number of the northbound communication interface is fixed information;

[0092] In a specific implementation of the embodiment of the present invention, when the external call interface is called, the link name information, link number information, and network IP address need to be passed into the link driver file as parameters;

[0093] In a specific implementation of the embodiment of the present invention, the link number is automatically generated by the system according to the actual use of the link when the link driver file is called;

[0094] In a specific implementation of an embodiment of the present invention, the unique external call identifier of the link driver file is marked with reference to three types of information: file type, link type, and link number. The link driver file type is the link file, and the link type is determined based on the device composition and actual use in the link.

[0095] In a specific implementation of an embodiment of the present invention, an object-oriented programming device graphics model, a backup switching model, a combined use model, a batch control model, a southbound communication interface model, a northbound communication interface model, and an external call interface model are used as callable methods or instance classes, and all methods and instance classes are encapsulated into a form dynamic link library file, that is, encapsulated into a device driver file.

[0096] The device monitoring system link driver creation process of the present invention is as follows Figure 2 As shown, the specific process is as follows:

[0097] (1) Obtain link information between various types of devices to be monitored, including device type information, device quantity information, device connection relationship, device backup relationship, device combination use logic, and device batch control logic within the link;

[0098] (2) According to the equipment monitoring information, the backup switching algorithm design, combined use algorithm design, batch control algorithm design, and monitoring interface graphical design are carried out in sequence. The backup switching algorithm constructs the equipment backup switching mechanism, the combined use algorithm constructs the equipment linkage relationship and equipment control sequence logic, the batch control algorithm constructs the simultaneous control mechanism of multiple devices, and the monitoring interface graphically constructs the human-computer interaction interface.

[0099] (3) Design the southbound communication interface between the link and the device based on the logic of collecting all device information in the link and the logic of issuing device control instructions;

[0100] (4) Design the northbound communication interface based on the link combination logic and device batch control logic;

[0101] (5) Designing an external call interface for the external call interface mechanism of the driver file according to the link information;

[0102] (6) According to the design ideas of the monitoring interface, backup switching algorithm, combined use algorithm, batch control algorithm, southbound communication interface, northbound communication interface and external call interface, the device graphic model, backup switching model, combined use model, batch control model, southbound communication interface model, northbound communication interface model and external call interface model are sequentially constructed;

[0103] (7) Using the file type, link type, and link number as references, mark the unique external call identifier of the link driver file;

[0104] (8) Using object-oriented programming encapsulation and polymorphism technology, encapsulate the device graphic model, backup switching model, combination use model, batch control model, southbound communication interface model, northbound communication interface model, and external call interface model into a link driver file;

[0105] (9)The process ends.

[0106] Embodiment 2

[0107] Reference Figure 3 , shows a schematic diagram of the structure of a link encapsulation device based on unified device monitoring modeling encapsulation provided by an embodiment of the present invention, such as Figure 3 As shown, the link encapsulation device based on unified device monitoring modeling encapsulation may include the following modules:

[0108] The link information acquisition module 310 is used to acquire link information between various types of devices that need to be monitored;

[0109] The communication interface determination module 320 is used to determine the graphical monitoring interface, the preset link algorithm and the communication interface according to the link information;

[0110] A model building module 330 is used to build a device graphic model, a backup switching model, a combination use model, a batch control model, a southbound communication interface model, a northbound communication interface model and an external call interface model according to the graphical monitoring interface, the preset link algorithm and the communication interface;

[0111] The driver file acquisition module 340 is used to encapsulate the device graphic model, the backup switching model, the combined use model, the batch control model, the southbound communication interface model, the northbound communication interface model and the external call interface model into a link driver file based on the encapsulation and polymorphism technology of object-oriented programming.

[0112] Optionally, the link information includes: device type information, device quantity information, device connection relationship, device backup relationship, device combination use logic and device batch control logic within the link.

[0113] The communication interface determination module comprises:

[0114] A monitoring interface design unit, configured to design a graphical monitoring interface corresponding to the link according to the device type information, the device quantity information, the device connection relationship and the device backup relationship in the link;

[0115] A backup switching algorithm design unit, used to design a backup switching algorithm corresponding to the backup switching mechanism of the monitored device according to the device connection relationship and the device backup relationship;

[0116] A combined use algorithm design unit, used to design a combined use algorithm for obtaining a device linkage relationship and a device control sequence logic when the devices are used in combination according to the device combined use logic;

[0117] A batch control algorithm design unit, used to design a batch control algorithm corresponding to a simultaneous control mechanism of multiple devices according to the device batch control logic;

[0118] The southbound communication interface design unit is used to design the southbound communication interface between the link and the device according to the collection logic of all device information in the link and the logic of issuing device control instructions;

[0119] A northbound communication interface design unit, used for designing a northbound communication interface according to link combination use logic and device batch control logic;

[0120] The external call interface design unit is used to design an external call interface corresponding to the external call interface mechanism of the driver file according to the type and purpose of the device in the link.

[0121] Optionally, the model building module includes:

[0122] A model building unit is used to construct a device graphic model, a backup switching model, a combined use model, a batch control model, a southbound communication interface model, a northbound communication interface model and an external call interface model in sequence according to the graphical monitoring interface, the backup switching algorithm, the combined use algorithm, the batch control algorithm, the southbound communication interface, the northbound communication interface and the external call interface.

[0123] Optionally, all devices in the link and their connection relationships are displayed in the main interface area, with icons representing devices and solid lines representing connection relationships between devices;

[0124] In the parameter monitoring area, the key parameter point information of all devices in the link is displayed;

[0125] The batch command area displays options for combining logic and batch control logic for all devices in the link.

[0126] Optionally, both the southbound communication interface and the northbound communication interface use the UDP protocol, wherein the network communication port number of the southbound communication interface is information automatically generated by the system, and the network communication port number of the northbound communication interface is fixed information.

[0127] Optionally, the drive file acquisition module includes:

[0128] A link library file acquisition unit, used to encapsulate the device graphic model, the backup switching model, the combined use model, the batch control model, the southbound communication interface model, the northbound communication interface model and the external call interface model into a form dynamic link library file;

[0129] The driver file acquisition unit is used to use the form dynamic link library file as the link driver file.

[0130] The specific implementation methods described in this application can enable those skilled in the art to understand this application more comprehensively, but do not limit this application in any way. Therefore, those skilled in the art should understand that this application can still be modified or replaced by equivalents; and all technical solutions and improvements that do not deviate from the spirit and technical essence of this application should be included in the protection scope of the patent of this application.

[0131] The contents not described in detail in the specification of the present invention belong to the common knowledge of those skilled in the art.

Claims

1. A link encapsulation method based on unified device monitoring modeling encapsulation, characterized in that: include: Obtain link information between various types of devices that need to be monitored; Determine a graphical monitoring interface, a preset link algorithm and a communication interface according to the link information; According to the graphical monitoring interface, the preset link algorithm and the communication interface, a device graphical model, a backup switching model, a combined use model, a batch control model, a southbound communication interface model, a northbound communication interface model and an external call interface model are constructed; Based on the encapsulation and polymorphism technology of object-oriented programming, the device graphic model, the backup switching model, the combined use model, the batch control model, the southbound communication interface model, the northbound communication interface model and the external call interface model are encapsulated into a link driver file, including: Encapsulating the device graphic model, the backup switching model, the combined use model, the batch control model, the southbound communication interface model, the northbound communication interface model and the external call interface model into a form dynamic link library file; Using the form dynamic link library file as the link driver file; The link information includes: device type information, device quantity information, device connection relationship, device backup relationship, device combination use logic and device batch control logic within the link. Determining a graphical monitoring interface, a preset link algorithm and a communication interface according to the link information includes: According to the device type information, the device quantity information, the device connection relationship and the device backup relationship in the link, a graphical monitoring interface corresponding to the link is designed; According to the device connection relationship and the device backup relationship, a backup switching algorithm corresponding to the backup switching mechanism of the monitored device is designed; According to the device combination use logic, a combined use algorithm of the device linkage relationship and the device control sequence logic when the devices are used in combination is designed; According to the equipment batch control logic, a batch control algorithm corresponding to the simultaneous control mechanism of multiple equipments is designed; Based on the logic of collecting all device information in the link and the logic of issuing device control instructions, the southbound communication interface between the link and the device is designed; According to the link combination use logic and device batch control logic, the northbound communication interface is designed; According to the type and purpose of the device in the link, an external call interface corresponding to the external call interface mechanism of the driver file is designed.

2. The method according to claim 1, characterized in that The device graphic model, the backup switching model, the combined use model, the batch control model, the southbound communication interface model, the northbound communication interface model and the external call interface model are constructed according to the graphical monitoring interface, the preset link algorithm and the communication interface, including: According to the graphical monitoring interface, backup switching algorithm, combined use algorithm, batch control algorithm, southbound communication interface, northbound communication interface and external call interface, the device graphic model, backup switching model, combined use model, batch control model, southbound communication interface model, northbound communication interface model and external call interface model are constructed in sequence.

3. The method according to claim 1, characterized in that The main interface area displays all devices in the link and their connection relationships, with icons representing devices and solid lines representing the connection relationships between devices; In the parameter monitoring area, the key parameter point information of all devices in the link is displayed; The batch command area displays options for combining logic and batch control logic for all devices in the link.

4. The method according to claim 1, characterized in that: The southbound communication interface and the northbound communication interface both use the UDP protocol, wherein the network communication port number of the southbound communication interface is information automatically generated according to the system, and the network communication port number of the northbound communication interface is fixed information.

5. A link encapsulation device based on unified device monitoring modeling encapsulation, characterized in that: include: The link information acquisition module is used to obtain the link information between various types of devices that need to be monitored; A communication interface determination module, used to determine a graphical monitoring interface, a preset link algorithm and a communication interface according to the link information; A model building module, used to build a device graphic model, a backup switching model, a combined use model, a batch control model, a southbound communication interface model, a northbound communication interface model and an external call interface model according to the graphical monitoring interface, the preset link algorithm and the communication interface; A driver file acquisition module, for encapsulating the device graphic model, the backup switching model, the combined use model, the batch control model, the southbound communication interface model, the northbound communication interface model and the external call interface model into a link driver file based on encapsulation and polymorphism technology of object-oriented programming; The link information includes: device type information, device quantity information, device connection relationship, device backup relationship, device combination use logic and device batch control logic within the link. The communication interface determination module comprises: A monitoring interface design unit, configured to design a graphical monitoring interface corresponding to the link according to the device type information, the device quantity information, the device connection relationship and the device backup relationship in the link; A backup switching algorithm design unit, used to design a backup switching algorithm corresponding to the backup switching mechanism of the monitored device according to the device connection relationship and the device backup relationship; A combined use algorithm design unit, used to design a combined use algorithm for obtaining a device linkage relationship and a device control sequence logic when the devices are used in combination according to the device combined use logic; A batch control algorithm design unit, used to design a batch control algorithm corresponding to a simultaneous control mechanism of multiple devices according to the device batch control logic; The southbound communication interface design unit is used to design the southbound communication interface between the link and the device according to the collection logic of all device information in the link and the logic of issuing device control instructions; A northbound communication interface design unit, used for designing a northbound communication interface according to link combination use logic and device batch control logic; The external call interface design unit is used to design an external call interface corresponding to the external call interface mechanism of the driver file according to the type and purpose of the device in the link; The model building module includes: A model building unit, used to sequentially build a device graphic model, a backup switching model, a combined use model, a batch control model, a southbound communication interface model, a northbound communication interface model and an external call interface model according to the graphical monitoring interface, the backup switching algorithm, the combined use algorithm, the batch control algorithm, the southbound communication interface, the northbound communication interface and the external call interface; The drive file acquisition module includes: A link library file acquisition unit, used to encapsulate the device graphic model, the backup switching model, the combined use model, the batch control model, the southbound communication interface model, the northbound communication interface model and the external call interface model into a form dynamic link library file; The driver file acquisition unit is used to use the form dynamic link library file as the link driver file.

6. The device according to claim 5, characterized in that The main interface area displays all devices in the link and their connection relationships, with icons representing devices and solid lines representing the connection relationships between devices; In the parameter monitoring area, the key parameter point information of all devices in the link is displayed; The batch command area displays options for combining logic and batch control logic for all devices in the link.

7. The device according to claim 5, characterized in that The southbound communication interface and the northbound communication interface both use the UDP protocol, wherein the network communication port number of the southbound communication interface is information automatically generated according to the system, and the network communication port number of the northbound communication interface is fixed information.

Images