Adaptive interface adaptation method and device for communication machine room

Abstract

The invention provides an adaptive interface adaptation method and device for a communication machine room, and the method comprises the following steps: automatically selecting a corresponding interface protocol plug-in based on the protocol type of communication machine room twin or machine room infrastructure; wherein the protocol types at least comprise a parent protocol type, and the parent protocol type at least comprises a sub protocol type; obtaining a loading instruction based on the interface protocol standard of the selected interface protocol plug-in; and loading the data integration plug-in based on the loading instruction. Diversified protocols and differentiated data formats supported by equipment facilities and system platforms of different manufacturers are met, and the method adapts to demand changes and adaptive changes of interface protocols brought by different applications; the protocol conversion between the communication machine room twin and the infrastructure equipment is realized, the high efficiency of protocol processing is ensured, the configuration information distribution is accurate and executable, and the complexity of protocol processing is reduced.

Description

Technical Field

[0001] The invention belongs to the technical field of communication rooms, and in particular relates to an adaptive interface adaptation method and device for a communication room. Background Art

[0002] When the digital twin visualization operation and maintenance system in the communication room communicates with the basic equipment and subsystems of the room, the protocols of different equipment and systems are different. The digital twin of the communication room visualization operation and maintenance system needs to perform multi-protocol collaboration and data format conversion to meet the diverse protocols and differentiated data formats supported by equipment facilities and system platforms from different manufacturers, while adapting to the changes in requirements and adaptation changes in interface protocols brought about by different applications.

[0003] When the computer room communication visualization operation and maintenance system is connected to different devices and system protocols, it is necessary to manually modify and configure these protocol matching and data format conversion rules. This has low flexibility, is troublesome and time-consuming, increases the complexity of analysis and matching, and improves the complexity of protocol processing. Summary of the invention

[0004] The purpose of the present invention is to overcome the above problems and provide an adaptive interface adaptation method and device for a communication room.

[0005] In order to achieve the above purpose, the technical solution adopted by the present invention is: An adaptive interface adaptation method for a communication room comprises the following steps: Automatically select the corresponding interface protocol plug-in based on the protocol type of the communication room twin or the basic equipment in the room; wherein the protocol type includes at least one parent protocol type, and the parent protocol type includes at least one child protocol type; Based on the interface protocol standard of the selected interface protocol plug-in, obtaining a loading instruction; Based on the loading instruction, the data integration plug-in is loaded.

[0006] As a further improvement, the interface protocol plug-in at least includes: Professional system integration plug-in, OPC DA access plug-in, HTTP access plug-in, MQTT access plug-in, Modbus access plug-in, CORBA access plug-in and custom access plug-in.

[0007] As a further improvement, the protocol type based on the communication room twin or the room basic equipment automatically selects the corresponding interface protocol plug-in. When the protocol type is the OPC DA interface protocol, the OPC-DARead client is installed to connect the OPC data to the ActiveMQ, MQTT or Kafka interface protocol plug-in. A JS script is written through the data integration plug-in, and the JS script is loaded in the data integration plug-in to read the data transmitted by the ActiveMQ, MQTT or Kafka interface protocol plug-in.

[0008] As a further improvement, the protocol type based on the communication room twin or the room basic equipment automatically selects the corresponding interface protocol plug-in. When the protocol type is the MQTT interface protocol, a protocol interface plug-in of the MQTT protocol is created in the MQTT-JavaScript data integration plug-in by modifying the function code encapsulated by the MQTT-JavaScript data integration plug-in instance to receive data transmitted by the MQTT protocol.

[0009] As a further improvement, the automatic selection of the corresponding interface protocol plug-in based on the protocol type of the communication room twin or the room basic equipment includes: When the protocol type is HTTP protocol, automatically select the HTTP access plug-in matching of the corresponding data integration plug-in; wherein the HTTP protocol includes HTTP / 1.1 protocol and HTTP / 2 protocol; When the protocol type is the MQTT protocol, the corresponding MQTT access plug-in of the data integration plug-in is automatically selected to match; wherein, the MQTT protocol includes the MQTT3.1.1 protocol and the MQTT5.0 protocol, and supports topic filtering and message retention.

[0010] As a further improvement, in the automatic selection of the corresponding interface protocol plug-in, the protocol type is analyzed to determine whether the protocol type is a parent protocol type or a sub-protocol type under the parent protocol type; if the protocol type is a sub-protocol type under the parent protocol type, the shared data transmitted under the sub-protocol type is stored in the shared data storage module of the data integration plug-in, and the non-shared data transmitted under the sub-protocol type is stored in the non-shared data storage module of the data integration plug-in.

[0011] As a further improvement, if the protocol type is a sub-protocol type under the parent protocol type, the shared data transmitted under the sub-protocol type is stored in the shared data storage module of the data integration plug-in, and the non-shared data transmitted under the sub-protocol type is stored in the non-shared data storage module of the data integration plug-in, including: When the protocol type is OPC, install the OPC-DARead client, analyze the OPC protocol type, connect the shared data of the OPC protocol subtype to the shared data storage module of the data integration plug-in in ActiveMQ, MQTT or Kafka, and connect the non-shared data of the OPC protocol subtype to the non-shared data storage module in the data integration plug-in in ActiveMQ, MQTT or Kafka respectively; Write JS scripts through the data integration plug-in to read data from the shared data storage module and / or non-shared data storage module of the data integration plug-in in ActiveMQ, MQTT or Kafka for data docking.

[0012] As a further improvement, the automatic selection of the corresponding interface protocol plug-in based on the protocol type of the communication room twin or the room basic equipment also includes: When the protocol type of the communication room twin or the room basic equipment is updated, it is determined whether the updated protocol type and the protocol type before the update are derivative protocols of sub-protocols of the same protocol, or unknown protocols; if the updated protocol type is a derivative protocol of a sub-protocol of the same protocol, first search and match the closest one or more access plug-ins from the initial sub-protocol access plug-ins, and if there is no closest access plug-in, use a custom access protocol plug-in for data docking; if the updated protocol type is the unknown protocol, use a custom access protocol plug-in for data docking.

[0013] As a further improvement, if the updated protocol type is a derivative protocol of a sub-protocol of the same protocol, one or more access plug-ins that are closest are first searched and matched from the initial sub-protocol access plug-in, and multiple sub-protocol access plug-ins of the same protocol can be used to access the same protocol.

[0014] On the other hand, the present invention also provides an adaptive interface adaptation device for a communication room, the device comprising at least one processor and a memory storing instructions, and when the instructions are executed by at least one processor, the adaptive interface adaptation method for a communication room described in the above technical solution is implemented.

[0015] The beneficial effects of the present invention are: It meets the diverse protocols and differentiated data formats supported by equipment, facilities and system platforms of different manufacturers, and adapts to the changes in requirements and adaptation changes of interface protocols brought about by different applications; it realizes the conversion of protocols between the communication room twin and infrastructure equipment, ensures the efficiency of protocol processing, the accurate and executable distribution of configuration information, and reduces the complexity of protocol processing; it realizes the transformation according to different protocols, and the system automatically matches different access plug-ins to receive the corresponding protocols. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The present invention has the following accompanying drawings: Figure 1 It is a principle block diagram of an adaptive interface adaptation method for a communication room according to some specific embodiments of the present invention; Figure 2 is a schematic diagram of the adaptive interface design of some specific embodiments of the present invention; Figure 3 A schematic diagram of an adaptive interface adaptation system for a communication room of the present invention. DETAILED DESCRIPTION

[0017] The following examples further illustrate the content of the present invention, but should not be construed as limiting the present invention. Without departing from the spirit and substance of the present invention, modifications or substitutions made to the methods, steps or conditions of the present invention all fall within the scope of the present invention.

[0018] like Figure 1 As shown, the present invention provides an adaptive interface adaptation method for a communication room, comprising the following steps: Automatically select the corresponding interface protocol plug-in based on the protocol type of the communication room twin or the basic equipment in the room; wherein the protocol type includes at least one parent protocol type, and the parent protocol type includes at least one child protocol type; Based on the interface protocol standard of the selected interface protocol plug-in, obtaining a loading instruction; Based on the loading instruction, the data integration plug-in is loaded. Based on the protocol type of the communication room twin or the basic equipment in the room, the corresponding interface protocol plug-in is automatically selected, including the following steps: Based on different protocol types, the data integration system management unit controls the data integration plug-in to automatically establish a connection with different protocols; wherein, when the protocol type changes, the interface protocol plug-in in the data integration plug-in automatically changes to an interface protocol plug-in corresponding to the protocol of the changed type.

[0019] For example, when the initial connection protocol is HTTP / 1.1, when the protocol changes to HTTP / 2, the data integration plug-in will automatically follow the protocol change and become an interface that receives the HTTP / 2 protocol.

[0020] In some embodiments of the present invention, the interface protocol plug-in includes at least: Professional system integration plug-in, OPC DA access plug-in, HTTP access plug-in, MQTT access plug-in, Modbus access plug-in, CORBA access plug-in and custom access plug-in, etc. In addition to these, it also includes WebSocket access plug-in, OPC access plug-in, SNMP access plug-in and other access plug-ins.

[0021] Based on the protocol type of the communication room twin or the basic equipment in the room, the corresponding interface protocol plug-in is automatically selected, including: When the protocol type is HTTP protocol, automatically select the HTTP access plug-in matching of the corresponding data integration plug-in; wherein the HTTP protocol includes HTTP / 1.1 protocol and HTTP / 2 protocol; When the protocol type is the MQTT protocol, the corresponding MQTT access plug-in of the data integration plug-in is automatically selected to match; wherein, the MQTT protocol includes the MQTT3.1.1 protocol and the MQTT5.0 protocol, and supports topic filtering and message retention.

[0022] For example, when the protocol changes to OPC, the data integration plug-in will automatically change to using the OPC access plug-in to receive data. At this time, the data integration system supports the OPC UA protocol and adapts to different versions of OPC servers. When the protocol changes to the SNMP protocol, the data integration plug-in will automatically change to using the SNMP access plug-in to receive data. At this time, the data integration system adapts to different versions of the SNMP protocol and supports multiple authentication and encryption methods. When the protocol changes to WebSocket, the data integration plug-in will automatically change to using the WebSocket access plug-in to receive data. At this time, the data integration system supports the WebSocket protocol and can process text and binary messages.

[0023] Based on the loading instruction, loading the data integration plug-in includes the following steps: Based on the loading instruction, the read data source type, data processing task type and object type are determined, and the data source plug-in, management plug-in and object plug-in in the selected data integration plug-in are loaded in sequence.

[0024] Loading the selected data source plug-in, the management plug-in and the object plug-in in sequence comprises the following steps: According to the data source type, a corresponding data source plug-in is selected to pre-process the original data to obtain first data; According to the data processing task type, selecting a corresponding management plug-in to further process the first data to obtain second data; According to the object type, a corresponding object plug-in is selected to further process the second data to obtain the format and content of the data.

[0025] In some embodiments of the present invention, the protocol type based on the communication room twin or the room basic equipment automatically selects the corresponding interface protocol plug-in. When the protocol type is the MQTT interface protocol, a protocol interface plug-in of the MQTT protocol is created in the MQTT-JavaScript data integration plug-in by modifying the function code encapsulated by the MQTT-JavaScript data integration plug-in instance to receive data transmitted by the MQTT protocol.

[0026] For example, the MQTT-JavaScript data integration plug-in instance can create an MQTT access plug-in for the MQTT protocol to receive messages sent by the MQTT protocol. Simply write the function code block encapsulated by the data integration plug-in instance to implement the parsing and conversion of the data sent by the MQTT protocol, and output the result data to MySQL, ES or MQ, etc., for various applications to use the data.

[0027] In some embodiments of the present invention, the protocol type based on the communication room twin or the room basic equipment automatically selects the corresponding interface protocol plug-in. When the protocol type is the OPC DA interface protocol, the OPC-DARead client is installed to connect the OPC data to the ActiveMQ, MQTT or Kafka interface protocol plug-in. A JS script is written through the data integration plug-in, and the script is loaded in the data integration plug-in to read the data transmitted by the ActiveMQ, MQTT or Kafka interface protocol plug-in.

[0028] In some embodiments of the present invention, the automatic selection of the corresponding interface protocol plug-in based on the protocol type of the communication room twin or the room basic equipment also includes: When the protocol type of the communication room twin or the room infrastructure equipment is updated, the protocol is judged to be a derivative protocol of a sub-protocol of the same protocol, or an unknown protocol; if it is a derivative protocol of the sub-protocol, first search and match the closest one or more access plug-ins from the initial sub-protocol access plug-in, if there is no such closest access plug-in, then use a custom access protocol plug-in for docking; if the updated protocol is the unknown protocol, then use a custom access protocol plug-in for docking.

[0029] In some embodiments of the present invention, loading the data integration plug-in based on the loading instruction includes: Step 1: Protocol identification and configuration. First, according to the protocol type of the monitoring management subsystem, select the corresponding data integration plug-in interface protocol plug-in. Then, the plug-in manager obtains the loading instruction according to the selected protocol type standard, and determines the starting type, management type and object type that the user needs to read according to the loading instruction. Finally, select the corresponding starting plug-in according to the starting type, select the corresponding management plug-in according to the management type, select the corresponding object plug-in according to the purpose type, and load the selected starting plug-in, management plug-in and object plug-in.

[0030] Step 2: Starter plug-in configuration. The starter plug-in is a framework code template used to define the starter data format. By connecting to the infrastructure monitoring system, it can parse and identify the raw data of the infrastructure monitoring system and convert it into a format that the system can process. By entering the code template, you can specify how to parse the input data, identify different fields, and pre-process the data.

[0031] Step 3: Manage plug-in configuration. After the data is pre-processed by the data source plug-in, you can configure the data processing method in the module through the data processing template to ensure data quality and accuracy.

[0032] Step 4: Object plug-in configuration. After the processed data is accessed, the format and content of the output data can be specified through the configuration of the object plug-in, including the data structure, field mapping, data conversion, etc. required by the target end. The output code template determines the form of the final data output to ensure compatibility with the target system and correct transmission.

[0033] In some embodiments of the present invention, when external data is connected to the data integration plug-in (DIP) for transmission, when the connection fails at the beginning or the data transmission is interrupted, an integrated interface plug-in or a corresponding interface protocol plug-in is used for replacement. When the connection fails or is interrupted within a certain threshold time (where the threshold can be set according to actual needs and is not limited here), the emergency connection integrated interface plug-in or the corresponding interface protocol plug-in is started, and the connection can be replaced; when the repair is completed, the integrated interface plug-in or the corresponding interface protocol plug-in is automatically disconnected, and the transmission continues. This avoids interruptions in the middle, data loss, and time delays. In the integrated device, multiple storage devices are set. When there is a problem with data transmission, data can be stored for a short time, and it will be released after a certain time. In this way, the content can be released, the rate can be increased, and data loss can be achieved at the same time. When there is a need, data is extracted from it or when the device is operating normally, if there is data in this device, data can be extracted from it. Because the distance is short, the time for extraction from the central database is saved.

[0034] In some embodiments of the present invention, if the updated protocol type is a derivative protocol of a sub-protocol of the same protocol, one or more access plug-ins that are closest are first searched and matched from the initial sub-protocol access plug-in, and multiple sub-protocol access plug-ins of the same protocol can be used to access the same protocol.

[0035] For example, when the system adaptively accesses data transmitted by HTTP / 1.1 and HTTP / 2 protocols, because HTTP / 1.1 and HTTP / 2 access plug-ins are both HTTP access plug-ins, which are sub-protocols under the same category, when a protocol named HTTP / 3 is updated, the system will automatically determine whether these two HTTP / 1.1 and HTTP / 2 access plug-ins can receive the data of HTTP / 3 protocol. When the data that can be received by HTTP / 1.1 and HTTP / 2 access plug-ins include data of HTTP / 3 protocol, these two HTTP / 1.1 and HTTP / 2 access plug-ins can be used to automatically connect the data of HTTP / 3 protocol, and there is no need to customize new access plug-ins. This is applicable in the same category and also in different categories. If two or more access plug-ins can receive all the data of a certain protocol, there is no need to redefine new access plug-ins, and existing ones can be used for access, which can reduce the memory for storing the defined plug-ins and reduce the system memory space; of course, new access plug-ins can also be defined, which is not limited in the present invention.

[0036] In some embodiments of the present invention, the protocol type based on the communication room twin or the room basic equipment automatically selects the corresponding interface protocol plug-in. When the protocol type is the MQTT interface protocol, a protocol interface plug-in of the MQTT protocol is created in the MQTT-JavaScript data integration plug-in by modifying the function code encapsulated by the MQTT-JavaScript data integration plug-in instance to receive data transmitted by the MQTT protocol.

[0037] For example, the MQTT-JavaScript DIP instance can create an MQTT consumer to receive messages produced by the MQTT producer. Simply writing the function code block encapsulated by the DIP instance can implement the parsing and conversion of MQTT data, and output the result data to databases such as MySQL, ES or MQ for various applications to use the data.

[0038] In some embodiments of the present invention, when the monitoring data is transmitted to the computer room infrastructure equipment, the running status of the data integration instance of the data integration plug-in is monitored in real time, including: the progress of task execution, performance indicators and running logs.

[0039] Selecting the data integration system management unit to control the corresponding data integration plug-in to start, includes the following steps: based on the interface protocol standard of the unified interface protocol plug-in, selecting the data integration system management unit to control the corresponding data integration plug-in to start.

[0040] For example, the interface protocol standard of the unified interface protocol plug-in can cover multiple interface communication protocols such as HTTP, OPC, SNMP, WebSocket, MQTT, etc., to ensure that the interface protocol plug-in can realize the data integration communication of various computer room monitoring and management subsystems and ensure the accurate transmission of data. When the corresponding transmission protocol is received, the data integration system management unit will control the corresponding data integration plug-in to start.

[0041] In some embodiments of the present invention, in the automatically selected corresponding interface protocol plug-in, the protocol type is analyzed to determine whether it is a parent protocol type or a sub-protocol type under the parent protocol type; if it is a sub-protocol type under the parent protocol type, the shared data transmitted under the sub-protocol type is stored in the shared data storage module of the data integration plug-in, and the non-shared data transmitted under the sub-protocol type is stored in the non-shared data storage module of the data integration plug-in.

[0042] For example, when the received protocols are HTTP / 1.1 and HTTP / 2, you must first distinguish whether a shared data change module and a shared data storage module are set in the data integration plug-in. In this way, when the protocol is HTTP / 1.1 at the beginning, when the protocol changes to HTTP / 2, the HTTP / 2 access plug-in in the data integration plug-in can be automatically used to receive data transmitted by the HTTP / 2 protocol. At this time, the HTTP / 2 access plug-in can be set to be further subdivided into smaller sub-protocol access plug-ins, which only receive data from different parts of HTTP / 2. The shared data is still received by the original access plug-in or obtained from the data platform in the data integration plug-in. This can improve the receiving and transmission efficiency and increase the transmission speed.

[0043] In some embodiments of the present invention, if it is a sub-protocol type under the parent protocol type, storing the shared data transmitted under the sub-protocol type in the shared data storage module of the data integration plug-in, and storing the non-shared data transmitted under the sub-protocol type in the non-shared data storage module of the data integration plug-in, includes: When the protocol type is OPC, install the OPC-DARead client, analyze the OPC protocol type, connect the shared data of the OPC protocol subtype to the shared data storage module of the data integration plug-in in ActiveMQ, MQTT or Kafka, and connect the non-shared data of the OPC protocol subtype to the non-shared data storage module in the data integration plug-in in ActiveMQ, MQTT or Kafka respectively; Write JS scripts through the data integration plug-in to read data from the shared data storage module and / or non-shared data storage module of the data integration plug-in in ActiveMQ, MQTT or Kafka for data docking.

[0044] Specifically, if Figure 2 As shown, the adaptive interface designed by the present invention has highly flexible data interface docking and adaptation capabilities. In the present invention, multiple communication protocol plug-ins are built-in, which can be used as a server to implement data integration communication interfaces such as HTTP, HTTPS, Syslog, Socket, SNMP, WebService, etc. Among them, the data integration system management unit (DISM) can start and stop the data integration instance of the data integration plug-in (DIP), can manage and control the running status of multiple DIP data integration tasks, and can start, stop or restart these integration tasks when necessary, and can monitor the running status of the DIP data integration instance in real time, including the progress of task execution, performance indicators, operation logs, etc. The data integration plug-in (DIP) includes multiple data interface types, such as Syslog, HTTP, WebService, JDBC, SNMP, ModBus Tcp and other communication protocols. The data integration plug-in is responsible for interface docking and data collection with various monitoring systems in the computer room. It mainly includes two aspects.

[0045] The first is the formulation of data integration plug-in (DIP) standards. Define a unified data integration plug-in (DIP) standard that can cover multiple interface communication protocols such as HTTP, OPC, SNMP, WebSocket, MQTT, etc., to ensure that the interface protocol plug-in can realize data integration communication of various computer room monitoring and management subsystems and ensure accurate data transmission.

[0046] The unified Data Integration Plug-in (DIP) standards are shown in the following table: Table 1 Interface protocol specification table

[0047]

[0048] The second is the design of data integration plug-in (DIP). Design data integration plug-ins suitable for various operation and maintenance management system platforms, support multiple communication protocols such as TCP / IP, HTTP, MQTT, etc., and have functional modules such as automatic adaptation of various interface protocols, data access reception, and data loading. It can realize the access, processing and forwarding of computer room monitoring system data, and reduce the complexity of interface protocol processing for building digital twins of communication computer rooms. Based on the multi-protocol DIP plug-in, there is no need to modify the protocol conversion, data format, etc. of the underlying facilities and equipment. The multi-protocol DIP plug-in can complete the interface docking and protocol adaptation of different system platforms. Interface test results and analysis, the interface test is designed to evaluate the protocol adaptability of the data integration system under various interface protocols. The test covers a variety of commonly used interface protocols, including HTTP, OPC, SNMP, WebSocket, and MQTT.

[0049] Table 2 System test specifications

[0050] 1. Test environment 2. Test objectives (1) Verify the system's ability to establish connections under different protocols.

[0051] (2) Verify the system’s data transmission capabilities under different protocols.

[0052] 3. Test results Table 3 Protocol test results

[0053] 4. Test conclusion The data integration system showed good protocol adaptability under the five tested interface protocols. The data integration system can stably establish connections between different protocols and efficiently transmit data. The test results show that the data integration system has strong compatibility and flexibility and can meet the data integration needs of diverse protocols.

[0054] In the present invention, based on the characteristics of various data sources and interface types of the communication room monitoring management or intelligent operation and maintenance system, the communication room visualization operation and maintenance system needs to perform multi-protocol collaboration and data format conversion to meet the diverse protocols and differentiated data formats supported by equipment facilities and system platforms of different manufacturers, while adapting to the changes in requirements and adaptation changes of interface protocols brought about by different applications. In order to realize the conversion of protocols between the communication room twin and infrastructure equipment, ensure the efficiency of protocol processing, accurately and executably distribute configuration information, and reduce the complexity of protocol processing as much as possible, the present invention designs an adaptive interface adaptation method for the communication room at the data integration layer of the communication room visualization operation and maintenance system.

[0055] It meets the diverse protocols and differentiated data formats supported by equipment, facilities and system platforms of different manufacturers, and adapts to the changes in requirements and adaptation changes of interface protocols brought about by different applications; it realizes the conversion of protocols between the communication room twin and infrastructure equipment, ensures the efficiency of protocol processing, the accuracy and executable distribution of configuration information, and reduces the complexity of protocol processing.

[0056] In some specific embodiments, Figure 3 The adaptive interface adaptation device for a communication room shown in the figure includes at least one processor and a memory storing instructions. When the instructions are executed by at least one processor, the adaptive interface adaptation method for a communication room in any of the above-mentioned embodiments is implemented.

[0057] The embodiments and functional operations of the subject matter described in this specification may be implemented in: digital electronic circuitry, tangibly implemented computer software or firmware, computer hardware, including the structures disclosed in this specification and their structural equivalents, or a combination of more than one of the above. The embodiments of the subject matter described in this specification may be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on one or more tangible non-transitory program carriers, for execution by a data processing device or to control the operation of a data processing device.

[0058] Alternatively or additionally, the program instructions may be encoded on an artificially generated propagation signal, such as a machine-generated electrical, optical, or electromagnetic signal, which is generated to encode information for transmission to an appropriate receiver device for execution by a data processing device. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of the above devices.

[0059] A computer program (which may also be referred to or described as a program, software, software application, module, software module, script or code) may be written in any form of programming language, including compiled or interpreted languages ​​or declarative or procedural languages, and the computer program may be deployed in any form, including as a stand-alone program or as a module, component, subroutine or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program may be stored in a portion of a file that stores other programs or data, for example, one or more scripts stored in the following: in a markup language document; in a single file dedicated to a related program; or in multiple collaborative files, for example, files storing one or more modules, subroutines or code portions. A computer program may be deployed to execute on one or more computers, the computers being located in one place or distributed to multiple locations and interconnected by a communication network.

[0060] The contents not described in detail in this specification belong to the prior art known to professional and technical personnel in this field.

[0061] Although the present invention has been described in detail above by general description, specific implementation methods and experiments, it is obvious to those skilled in the art that some modifications or improvements can be made to the present invention. Therefore, these modifications or improvements made without departing from the spirit of the present invention all belong to the scope of protection claimed by the present invention.

Claims

1. An adaptive interface adaptation method for a communication room, characterized in that: The following steps are involved: Automatically select the corresponding interface protocol plug-in based on the protocol type of the communication room twin or the basic equipment in the room; wherein the protocol type includes at least one parent protocol type, and the parent protocol type includes at least one child protocol type; Based on the interface protocol standard of the selected interface protocol plug-in, obtaining a loading instruction; Based on the loading instruction, the data integration plug-in is loaded.

2. The adaptive interface adaptation method for a communication room according to claim 1, characterized in that: The interface protocol plug-in at least includes: Professional system integration plug-in, OPC DA access plug-in, HTTP access plug-in, MQTT access plug-in, Modbus access plug-in, CORBA access plug-in and custom access plug-in.

3. The adaptive interface adaptation method for a communication room according to claim 1, characterized in that: The protocol type based on the communication room twin or the room basic equipment automatically selects the corresponding interface protocol plug-in. When the protocol type is the OPC DA interface protocol, the OPC-DARead client is installed to connect the OPC data to the ActiveMQ, MQTT or Kafka interface protocol plug-in. A JS script is written through the data integration plug-in, and the JS script is loaded in the data integration plug-in based on the script to read the data transmitted by the ActiveMQ, MQTT or Kafka interface protocol plug-in.

4. The adaptive interface adaptation method for a communication room according to claim 1, characterized in that: The protocol type based on the communication room twin or the room basic equipment automatically selects the corresponding interface protocol plug-in. When the protocol type is the MQTT interface protocol, a protocol interface plug-in of the MQTT protocol is created in the MQTT-JavaScript data integration plug-in by modifying the function code encapsulated by the MQTT-JavaScript data integration plug-in instance to receive data transmitted by the MQTT protocol.

5. The adaptive interface adaptation method for a communication room according to claim 1, characterized in that: The automatic selection of the corresponding interface protocol plug-in based on the protocol type of the communication room twin or the room basic equipment includes: When the protocol type is HTTP protocol, automatically select the HTTP access plug-in matching of the corresponding data integration plug-in; wherein the HTTP protocol includes HTTP / 1.1 protocol and HTTP / 2 protocol; When the protocol type is the MQTT protocol, the corresponding MQTT access plug-in of the data integration plug-in is automatically selected to match; wherein, the MQTT protocol includes the MQTT3.1.1 protocol and the MQTT5.0 protocol, and supports topic filtering and message retention.

6. The adaptive interface adaptation method for a communication room according to claim 1, characterized in that: In the automatically selected corresponding interface protocol plug-in, the protocol type is analyzed to determine whether the protocol type is a parent protocol type or a sub-protocol type under the parent protocol type; if the protocol type is a sub-protocol type under the parent protocol type, the shared data transmitted under the sub-protocol type is stored in the shared data storage module of the data integration plug-in, and the non-shared data transmitted under the sub-protocol type is stored in the non-shared data storage module of the data integration plug-in.

7. The adaptive interface adaptation method for a communication room according to claim 6, characterized in that: If the protocol type is a sub-protocol type under the parent protocol type, storing the shared data transmitted under the sub-protocol type in the shared data storage module of the data integration plug-in, and storing the non-shared data transmitted under the sub-protocol type in the non-shared data storage module of the data integration plug-in, including: When the protocol type is OPC, install the OPC-DARead client, analyze the OPC protocol type, connect the shared data of the OPC protocol subtype to the shared data storage module of the data integration plug-in in ActiveMQ, MQTT or Kafka, and connect the non-shared data of the OPC protocol subtype to the non-shared data storage module in the data integration plug-in in ActiveMQ, MQTT or Kafka respectively; Write JS scripts through the data integration plug-in to read data from the shared data storage module and / or non-shared data storage module of the data integration plug-in in ActiveMQ, MQTT or Kafka for data docking.

8. The adaptive interface adaptation method for a communication room according to claim 1, characterized in that: The automatic selection of the corresponding interface protocol plug-in based on the protocol type of the communication room twin or the room basic equipment also includes: When the protocol type of the communication room twin or the room basic equipment is updated, it is determined whether the updated protocol type and the protocol type before the update are derivative protocols of sub-protocols of the same protocol, or unknown protocols; if the updated protocol type is a derivative protocol of a sub-protocol of the same protocol, first search and match the closest one or more access plug-ins from the initial sub-protocol access plug-ins, and if there is no closest access plug-in, use a custom access protocol plug-in for data docking; if the updated protocol type is the unknown protocol, use a custom access protocol plug-in for data docking.

9. The adaptive interface adaptation method for a communication room according to claim 8, characterized in that: If the updated protocol type is a derivative protocol of a sub-protocol of the same protocol, first search and match the closest one or more access plug-ins from the initial sub-protocol access plug-in, and multiple sub-protocol access plug-ins of the same protocol can be used to access the same protocol.

10. An adaptive interface adapter device for a communication room, the device comprising at least one processor and a memory storing instructions, characterized in that: When the instruction is executed by at least one processor, the adaptive interface adaptation method for a communication room as described in any one of claims 1 to 9 is implemented.

Images