Adaptive interface adaptation method and device for communication room

Abstract

The present invention provides an adaptive interface adaptation method and device for a communication room, the method comprising the following steps: automatically selecting a corresponding interface protocol plug-in based on the protocol type of the communication room twin or the room's basic equipment; wherein the protocol type includes at least one parent protocol type, and the parent protocol type includes at least one child protocol type; obtaining a loading instruction based on the interface protocol standard of the selected interface protocol plug-in; and loading a data integration plug-in based on the loading instruction. This method satisfies the diversified protocols and differentiated data formats supported by equipment facilities and system platforms from different manufacturers, and adapts to changes in requirements and adaptation changes in interface protocols brought about by different applications; it realizes protocol conversion 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.

Description

Technical Field

[0001] The present 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 of different manufacturers, and at the same time adapt to the changes in requirements and adaptation changes of 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, these protocol matching and data format conversion rules need to be manually modified and configured. This has low flexibility, is cumbersome and time-consuming, increases the complexity of analysis and matching, and increases 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:

[0006] An adaptive interface adaptation method for a communication room comprises the following steps:

[0007] 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;

[0008] Obtaining a loading instruction based on the interface protocol standard of the selected interface protocol plug-in;

[0009] Based on the loading instruction, the data integration plug-in is loaded.

[0010] As a further improvement, the interface protocol plug-in at least includes:

[0011] Professional system integration plug-ins, OPC DA access plug-ins, HTTP access plug-ins, MQTT access plug-ins, Modbus access plug-ins, CORBA access plug-ins and custom access plug-ins.

[0012] 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.

[0013] 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, the function code encapsulated by the MQTT-JavaScript data integration plug-in instance is modified in the MQTT-JavaScript data integration plug-in to create an MQTT protocol protocol interface plug-in to receive data transmitted by the MQTT protocol.

[0014] 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 infrastructure equipment includes:

[0015] When the protocol type is HTTP, the HTTP access plug-in of the corresponding data integration plug-in is automatically selected to match; wherein the HTTP protocol includes HTTP / 1.1 protocol and HTTP / 2 protocol;

[0016] 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.

[0017] As a further improvement, the automatically selected corresponding interface protocol plug-in analyzes the protocol type 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.

[0018] As a further improvement, if the protocol type is a sub-protocol type under a 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:

[0019] 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 of the data integration plug-in in ActiveMQ, MQTT, or Kafka respectively;

[0020] 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.

[0021] 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 infrastructure equipment also includes:

[0022] When the protocol type of the communication room twin or the room infrastructure 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-in. If there is no closest access plug-in, then use a custom access protocol plug-in for data docking; if the updated protocol type is the unknown protocol, then use a custom access protocol plug-in for data docking.

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

[0024] On the other hand, the present invention also provides an adaptive interface adaptation device for a communication room, which 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 described in the above technical solution is implemented.

[0025] The beneficial effects of the present invention are:

[0026] 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

[0027] The present invention has the following accompanying drawings:

[0028] 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;

[0029] Figure 2 is a schematic diagram of the adaptive interface design of some specific embodiments of the present invention;

[0030] Figure 3 A schematic diagram of an adaptive interface adaptation system for a communication room according to the present invention. DETAILED DESCRIPTION

[0031] The following examples further illustrate 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 are within the scope of the present invention.

[0032] like Figure 1 As shown, the present invention provides an adaptive interface adaptation method for a communication room, comprising the following steps:

[0033] 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;

[0034] Obtaining a loading instruction based on the interface protocol standard of the selected interface protocol plug-in;

[0035] Based on the loading instruction, the data integration plug-in is loaded.

[0036] 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, including the following steps:

[0037] 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 the interface protocol plug-in corresponding to the changed type of protocol.

[0038] 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.

[0039] In some embodiments of the present invention, the interface protocol plug-in includes at least:

[0040] Professional system integration plug-ins, OPC DA access plug-ins, HTTP access plug-ins, MQTT access plug-ins, Modbus access plug-ins, CORBA access plug-ins, and custom access plug-ins, etc. In addition to these, it also includes WebSocket access plug-ins, OPC access plug-ins, SNMP access plug-ins and other access plug-ins.

[0041] 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, including:

[0042] When the protocol type is HTTP, the HTTP access plug-in of the corresponding data integration plug-in is automatically selected to match; wherein the HTTP protocol includes HTTP / 1.1 protocol and HTTP / 2 protocol;

[0043] 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.

[0044] For example, when the protocol changes to OPC, the data integration plug-in automatically switches to using the OPC access plug-in to receive data. The data integration system now supports the OPC UA protocol and adapts to different OPC server versions. When the protocol changes to SNMP, the data integration plug-in automatically switches to using the SNMP access plug-in to receive data. The data integration system now adapts to different SNMP protocol versions and supports multiple authentication and encryption methods. When the protocol changes to WebSocket, the data integration plug-in automatically switches to using the WebSocket access plug-in to receive data. The data integration system now supports the WebSocket protocol and can handle both text and binary messages.

[0045] Loading the data integration plug-in based on the loading instruction includes the following steps:

[0046] 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.

[0047] Loading the selected data source plug-in, the management plug-in, and the object plug-in in sequence includes the following steps:

[0048] According to the data source type, a corresponding data source plug-in is selected to pre-process the original data to obtain first data;

[0049] According to the data processing task type, selecting a corresponding management plug-in to further process the first data to obtain second data;

[0050] 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.

[0051] 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, the function code encapsulated by the MQTT-JavaScript data integration plug-in instance is modified in the MQTT-JavaScript data integration plug-in to create an MQTT protocol protocol interface plug-in to receive data transmitted by the MQTT protocol.

[0052] For example, the MQTT-JavaScript data integration plug-in instance can create an MQTT access plug-in that receives MQTT messages. Simply writing the function code block encapsulated by this data integration plug-in instance parses and converts MQTT data and outputs the resulting data to MySQL, ES, or MQ for use by various applications.

[0053] 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.

[0054] In some embodiments of the present invention, automatically selecting a corresponding interface protocol plug-in based on the protocol type of the communication room twin or the room infrastructure equipment further includes:

[0055] 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 closest access plug-in, then use the custom access protocol plug-in for docking; if the updated protocol is the unknown protocol, then use the custom access protocol plug-in for docking.

[0056] In some embodiments of the present invention, loading the data integration plug-in based on the loading instruction includes:

[0057] Step 1: Protocol Identification and Configuration. First, select the corresponding data integration plug-in interface protocol plug-in based on the protocol type of the monitoring and management subsystem. Then, the plug-in manager obtains loading instructions based on the selected protocol type standard and determines the starting type, management type, and object type that the user needs to read based on these loading instructions. Finally, select the corresponding starting plug-in based on the starting type, the corresponding management plug-in based on the management type, and the corresponding object plug-in based on the target type. The selected starting plug-in, management plug-in, and object plug-in are loaded.

[0058] Step 2: Configure the Starter Plug-in. The Starter Plug-in is a framework code template that defines the starter data format. By connecting to the infrastructure monitoring system, it can parse and identify the system's raw data 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.

[0059] Step 3: Manage plug-in configuration. Connect to the data source plug-in pre-processed data. Through the data processing template, you can configure the data processing method within the module to ensure data quality and accuracy.

[0060] Step 4: Object Plugin Configuration. After receiving processed data, you can configure the output data format and content through object plugin configuration, including the target end's required data structure, field mapping, and data conversion. The output code template determines the final data output format, ensuring compatibility with the target system and correct transmission.

[0061] In some embodiments of the present invention, when external data is connected to a data integration plug-in (DIP) for transmission, if the connection fails initially or the data transmission process is interrupted, a replacement integrated interface plug-in or a corresponding alternative interface protocol plug-in is switched. If the connection fails or is interrupted within a certain threshold (the threshold can be set according to actual needs and is not limited here), an emergency integrated interface plug-in or a corresponding alternative interface protocol plug-in is activated to replace the connection. Once the repair is complete, the integrated interface plug-in or the corresponding alternative interface protocol plug-in is automatically disconnected, and the transmission continues. This avoids interruptions, data loss, and time delays. Multiple storage devices are provided within the integrated device. When data transmission issues arise, data can be stored for a short period of time and then released after a certain period of time. This releases content, improves transmission speed, and reduces data loss. When needed, data can be retrieved from these devices, or when the device is operating normally, if data exists in these devices, data can be retrieved from them. Because the distance is short, the time required to retrieve data from the central database is saved.

[0062] 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 closest to the initial sub-protocol access plug-in are first searched and matched, and multiple sub-protocol access plug-ins of the same type of protocol can be used to access the same type of protocol.

[0063] For example, when the system adaptively accesses data transmitted by HTTP / 1.1 and HTTP / 2 protocols, because both HTTP / 1.1 and HTTP / 2 access plug-ins belong to the HTTP access plug-in category and are sub-protocols of the same category, when a new 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 HTTP / 3 protocol data. When the data that the HTTP / 1.1 and HTTP / 2 access plug-ins can receive includes HTTP / 3 protocol data, these two HTTP / 1.1 and HTTP / 2 access plug-ins can be used to automatically connect to the HTTP / 3 protocol data, eliminating the need to customize new access plug-ins. This applies both within the same category and across different categories. If two or more access plug-ins can receive all data for a particular protocol, there's no need to redefine new access plug-ins; existing ones can be used for access. This reduces the memory required to store defined plug-ins and reduces system memory space. New access plug-ins can also be defined, but this is not a limitation in the present invention.

[0064] 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, the function code encapsulated by the MQTT-JavaScript data integration plug-in instance is modified in the MQTT-JavaScript data integration plug-in to create an MQTT protocol protocol interface plug-in to receive data transmitted by the MQTT protocol.

[0065] For example, the MQTT-JavaScript DIP instance can create an MQTT consumer to receive messages from an MQTT producer. Simply writing the function code blocks encapsulated by this DIP instance can parse and convert MQTT data and output the resulting data to databases such as MySQL, ES, or MQ for use by various applications.

[0066] 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: task execution progress, performance indicators and running logs.

[0067] 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.

[0068] For example, a unified interface protocol standard for interface protocol plug-ins can cover multiple interface communication protocols such as HTTP, OPC, SNMP, WebSocket, and MQTT. This ensures that the interface protocol plug-ins can implement data integration communication for various computer room monitoring and management subsystems, ensuring accurate data transmission. Upon receiving the corresponding transmission protocol, the data integration system management unit will control the corresponding data integration plug-in to start.

[0069] In some embodiments of the present invention, the corresponding interface protocol plug-in is automatically selected, and 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.

[0070] For example, when receiving protocols 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 initially HTTP / 1.1 and 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.

[0071] In some embodiments of the present invention, 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, includes:

[0072] 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 of the data integration plug-in in ActiveMQ, MQTT, or Kafka respectively;

[0073] 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.

[0074] Specifically, if Figure 2As shown, the adaptive interface designed in this invention boasts highly flexible data interface docking and adaptation capabilities. It incorporates multiple communication protocol plug-ins, acting as a server to implement data integration communication interfaces such as HTTP, HTTPS, Syslog, Socket, SNMP, and WebService. The Data Integration System Management Unit (DISM) enables the start and stop of data integration instances within the Data Integration Plug-in (DIP), manages and controls the operational status of multiple DIP data integration tasks, and can start, stop, or restart these tasks as needed. It also provides real-time monitoring of the operational status of DIP data integration instances, including task execution progress, performance metrics, and operational logs. The Data Integration Plug-in (DIP) includes various data interface types, including Syslog, HTTP, WebService, JDBC, SNMP, ModBus TCP, and other communication protocols. These plug-ins are responsible for interfacing with various monitoring systems in the computer room and collecting data. This system primarily encompasses two aspects.

[0075] The first is the development of Data Integration Plug-in (DIP) standards. This defines a unified Data Integration Plug-in (DIP) standard that covers multiple interface communication protocols, including HTTP, OPC, SNMP, WebSocket, and MQTT. This ensures that the interface protocol plug-in can implement data integration and communication for various computer room monitoring and management subsystems, ensuring accurate data transmission.

[0076] The unified Data Integration Plug-in (DIP) standards are shown in the following table:

[0077] Table 1 Interface protocol specifications

[0078]

[0079]

[0080] The second is the design of the data integration plug-in (DIP). Design a data integration plug-in suitable for various operation and maintenance management system platforms, support multiple communication protocols such as TCP / IP, HTTP, MQTT, and have functional modules such as automatic adaptation of various interface protocols, data access and 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 a digital twin of the communication computer room. 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.

[0081] Table 2 System test specifications

[0082]

[0083] 1. Test environment

[0084] 2. Test Objectives

[0085] (1) Verify the system's ability to establish connections under different protocols.

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

[0087] 3. Test results

[0088] Table 3 Protocol test results

[0089]

[0090] 4. Test Conclusion

[0091] The data integration system demonstrated excellent protocol adaptability across all five tested interface protocols. It was able to establish stable connections across different protocols and efficiently transmit data. Test results demonstrate the system's strong compatibility and flexibility, enabling it to meet the data integration needs of diverse protocols.

[0092] In the present invention, based on the characteristics of various data sources and interface types of the communication room monitoring and 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, the accurate and executable distribution of 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.

[0093] 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.

[0094] In some specific embodiments, Figure 3The adaptive interface adaptation device for a communication room shown 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.

[0095] 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 foregoing. 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, or to control the operation of, a data processing apparatus.

[0096] Alternatively or additionally, the program instructions may be encoded on an artificially generated propagated 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 foregoing.

[0097] 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 as part of a file that stores other programs or data, for example, as one or more scripts in a markup language document, in a single file dedicated to the program in question, or in multiple collaborative files, for example, files storing one or more modules, subroutines, or portions of code. A computer program may be deployed to execute on one or more computers, located in one location or distributed across multiple locations and interconnected by a communications network.

[0098] The contents not described in detail in this specification belong to the prior art known to those skilled in the art.

[0099] Although the present invention has been described in detail above using general explanations, specific embodiments, and experiments, it will be apparent to those skilled in the art that modifications and improvements may be made based on the present invention. Therefore, such modifications and improvements, which do not depart from the spirit of the present invention, are intended to be within the scope of protection claimed herein.

Claims

1. An adaptive interface adaptation method for a communication room, characterized in that: The following steps are involved: Based on the protocol type of the communication room twin or the room basic equipment, the corresponding interface protocol plug-in is automatically selected; wherein, the protocol type includes at least one parent protocol type, and the parent protocol type includes at least one child protocol type; wherein, 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; Obtaining a loading instruction based on the interface protocol standard of the selected interface protocol plug-in; Based on the loading instruction, the data integration plug-in is loaded; wherein, 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, 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 is changed, the interface protocol plug-in in the data integration plug-in is automatically changed to an interface protocol plug-in corresponding to the changed protocol type; The method of automatically selecting a corresponding interface protocol plug-in based on the protocol type of the communication room twin or the room infrastructure equipment further includes: When the protocol type of the communication room twin or the room infrastructure 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, the closest one or more access plug-ins are first searched and matched from the initial sub-protocol access plug-in. If there is no such closest access plug-in, a custom access protocol plug-in is used for data docking; if the updated protocol type is the unknown protocol, a custom access protocol plug-in is used for data docking; Among them, if the updated protocol type is a derivative protocol of a sub-protocol of the same protocol, the closest one or more access plug-ins are first searched and matched from the initial sub-protocol access plug-in, and multiple sub-protocol access plug-ins of the same type of protocol can be used to access the same type of protocol.

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-ins, OPC DA access plug-ins, HTTP access plug-ins, MQTT access plug-ins, Modbus access plug-ins, CORBA access plug-ins and custom access plug-ins.

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, the function code encapsulated by the MQTT-JavaScript data integration plug-in instance is modified in the MQTT-JavaScript data integration plug-in to create an MQTT protocol protocol interface plug-in 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, the HTTP access plug-in of the corresponding data integration plug-in is automatically selected to match; 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: If the protocol type is a sub-protocol type under a 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 of 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.

7. An adaptive interface adapter device for a communication room, 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 according to any one of claims 1 to 6 is implemented.

Images