A method and system for aggregate processing of multiple IoT terminal protocols for DCIM

Abstract

The embodiment of the present invention discloses an aggregation processing method and system for multiple IoT terminal protocols for DCIM. After receiving a connection request from at least one IoT terminal at the DCIM server end, the embodiment of the present invention registers each IoT terminal to obtain a corresponding registration identifier; allocates a channel and a buffer register to each IoT terminal; loads the inbound and outbound rules corresponding to the allocated channel from the inbound and outbound rule library for each IoT terminal; for each connection request, establishes a mapping relationship between the registration identifier, the allocated channel and the buffer register, and the loaded inbound and outbound rules; uses the mapping relationship to perform unified data encapsulation and establish a unified external connection interface. In this way, when connecting different IoT terminals, the use of third-party components is avoided, and encapsulated data in a unified format is output, which reduces the coupling degree of the system and improves the compatibility of the system.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of Internet of Things communication technology, and in particular to a method and system for aggregating and processing multiple Internet of Things terminal protocols for DCIM. Background Art

[0002] The Internet of Things (IoT) technology refers to the real-time collection of any object that needs to be monitored, connected, and interacted with through various devices and technologies such as information sensors, radio frequency identification technology, global positioning system, infrared sensors, laser scanners, etc., and the collection of various required information such as sound, light, heat, electricity, mechanics, chemistry, biology, and location. Through various possible network access, it realizes ubiquitous connection between objects and objects, and objects and people, and realizes intelligent perception, identification, and management of objects and processes.

[0003] In actual use, use DCIM (Data Center Infrastructure Management) to connect to IoT terminal devices. At this time, it is often necessary to access terminal devices of different modes and protocols. In order to access terminal devices of different modes and protocols, it is necessary to access the SDK (Software Development Kit) of each manufacturer in different forms or use different data ports and third-party open source components to connect to the network, manage devices and parse data for different forms of devices. Due to the inconsistency of the environment and version of each component, it is easy to cause the inability to control the parsing process during the connection process, which is a technical problem of low compatibility. Summary of the invention

[0004] To this end, an embodiment of the present invention provides an aggregation processing method and system for multiple IoT terminal protocols for DCIM, so as to solve the technical problems of high coupling and low compatibility caused by inconsistent environments and versions of various components in the existing data center infrastructure management system.

[0005] In order to achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0006] According to a first aspect of an embodiment of the present invention, a method for aggregating and processing multiple IoT terminal protocols for DCIM is provided. The method is applied to a DCIM server and includes:

[0007] Receiving a connection request from at least one IoT terminal;

[0008] Register each IoT terminal and obtain the corresponding registration ID;

[0009] Allocate channels and buffer registers to each IoT terminal;

[0010] Loading the inbound and outbound rules corresponding to the assigned channels for each IoT terminal from the inbound and outbound rule library;

[0011] For each connection request, a mapping relationship is established between the registration identifier, the allocated channel and the buffer register, and the loaded inbound and outbound rules;

[0012] The mapping relationship is used to perform unified data encapsulation and establish a unified external connection interface.

[0013] Preferably, before allocating a channel to each IoT terminal, the method further comprises:

[0014] Real-time detection of whether at least one communication channel is in a readable or writable state;

[0015] If the communication channel is in a readable and writable state, determining the communication channel as the first channel;

[0016] If the communication channel is not in a readable and writable state, determining the communication channel as a second channel;

[0017] The first channel is selected as the channel to be allocated.

[0018] Preferably, the method further comprises:

[0019] Building a unified data link monitoring channel to monitor the unified external connection interface in real time;

[0020] Select and load corresponding data verification rules from the data verification rule library according to the protocol type of the allocated channel;

[0021] Using the data verification rule, abnormal data link detection is performed on the transmission data of the current communication channel;

[0022] A response operation is performed on the abnormal data link based on a preset abnormal response rule corresponding to the data verification rule.

[0023] Furthermore, using the data verification rule, abnormal data link detection is performed on the transmission data of the current communication channel, including:

[0024] Determine whether there is any transmission anomaly in the data link layer;

[0025] If a transmission anomaly occurs in the data link layer, it is determined that an abnormal data link is detected;

[0026] If there is no transmission anomaly in the data link layer, determine whether the current communication channel is abnormal;

[0027] If the current communication channel is normal, continue to monitor the unified external connection interface;

[0028] If the current communication channel is abnormal, it is determined that an abnormal data link is detected.

[0029] Further, performing a response operation on the abnormal data link based on a preset abnormal response rule corresponding to the data verification rule includes:

[0030] Determining the abnormal type of the abnormal data link;

[0031] If the abnormality type is a communication connection abnormality, reconnect according to the preset abnormal response rule and provide abnormal response information feedback;

[0032] If the abnormality type is a communication environment interference abnormality, the interference source is shielded according to the preset abnormality response rule, and abnormal response information is fed back.

[0033] Furthermore, the mapping relationship is used to perform unified data encapsulation and establish a unified external connection interface, including:

[0034] By utilizing the mapping relationship and using a unified data encapsulation, different types of communication protocol data are encapsulated into a unified format according to the inbound and outbound rules, so that other modules can uniformly process and use the communication protocol data.

[0035] According to a second aspect of an embodiment of the present invention, a system for aggregate processing of multiple IoT terminal protocols for DCIM is provided, the system comprising at least one IoT terminal and a DCIM server, including:

[0036] A receiving module, used to receive a connection request from at least one IoT terminal;

[0037] The registration module is used to register each IoT terminal and obtain the corresponding registration identifier;

[0038] An allocation module, used to allocate channels and buffer registers to each IoT terminal;

[0039] An inbound and outbound rule loading module, used to load the inbound and outbound rules corresponding to the allocated channels for each IoT terminal from the inbound and outbound rule library;

[0040] A mapping relationship establishment module, used for establishing a mapping relationship between the registration identifier, the allocated channel and the buffer register, and the loaded inbound and outbound rules for each connection request;

[0041] The encapsulation module is used to perform unified data encapsulation using the mapping relationship and establish a unified external connection interface.

[0042] Preferably, the system further comprises a multiplexer for performing the following steps before allocating a channel to each IoT terminal:

[0043] Real-time detection of whether at least one communication channel is in a readable or writable state;

[0044] If the communication channel is in a readable and writable state, determining the communication channel as the first channel;

[0045] If the communication channel is not in a readable and writable state, determining the communication channel as a second channel;

[0046] The first channel is selected as the channel to be allocated.

[0047] Preferably, the method further comprises:

[0048] A monitoring module, used to build a unified data link monitoring channel and monitor the unified external connection interface in real time;

[0049] A data verification rule loading module is used to select and load corresponding data verification rules from a data verification rule library according to the protocol type of the allocated channel;

[0050] A detection module, used to perform abnormal data link detection on the transmission data of the current communication channel by using the data verification rule;

[0051] The abnormal data processing module is used to respond to the abnormal data link based on the preset abnormal response rule corresponding to the data verification rule.

[0052] The embodiments of the present invention have the following advantages:

[0053] After receiving a connection request from at least one IoT terminal at the DCIM server end, the embodiment of the present invention registers each IoT terminal to obtain a corresponding registration identifier; allocates a channel and a buffer register to each IoT terminal; loads the inbound and outbound rules corresponding to the allocated channel from the inbound and outbound rule library for each IoT terminal; for each connection request, establishes a mapping relationship between the registration identifier, the allocated channel and the buffer register, and the loaded inbound and outbound rules; uses the mapping relationship to perform unified data encapsulation and establish a unified external connection interface. In this way, when connecting different IoT terminals, the use of third-party components is avoided, and encapsulated data in a unified format is output, thereby reducing the coupling degree of the system and improving the compatibility of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] In order to more clearly illustrate the implementation methods of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for the implementation methods or the description of the prior art. Obviously, the drawings in the following description are only exemplary, and for ordinary technicians in this field, other implementation drawings can be derived from the provided drawings without creative work.

[0055] The structures, proportions, sizes, etc. illustrated in this specification are only used to match the contents disclosed in the specification so as to facilitate understanding and reading by persons familiar with the technology. They are not used to limit the conditions under which the present invention can be implemented, and therefore have no substantial technical significance. Any structural modification, change in proportion or adjustment of size shall still fall within the scope of the technical contents disclosed in the present invention without affecting the effects and purposes that can be achieved by the present invention.

[0056] Figure 1 A schematic diagram of the module structure of a system for aggregate processing of multiple IoT terminal protocols for DCIM provided by an embodiment of the present invention;

[0057] Figure 2 A schematic flow chart of a method for aggregating and processing multiple IoT terminal protocols for DCIM provided by an embodiment of the present invention;

[0058] Figure 3 A schematic diagram of a flow chart of detecting the communication channel status in a method for aggregate processing of multiple IoT terminal protocols for DCIM provided by an embodiment of the present invention;

[0059] Figure 4 A schematic diagram of a flow chart of anomaly detection in a method for aggregate processing of multiple IoT terminal protocols for DCIM provided by an embodiment of the present invention;

[0060] Figure 5 A schematic diagram of a flow chart of determining whether a transmission anomaly occurs in a method for aggregate processing of multiple IoT terminal protocols for DCIM provided by an embodiment of the present invention;

[0061] Figure 6 A flowchart of determining anomaly types and performing corresponding processing in an aggregation processing method for multiple IoT terminal protocols for DCIM provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0062] The following is a description of the implementation of the present invention by specific embodiments. People familiar with the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0063] At present, DCIM (Data Center Infrastructure Management) is mainly used to connect with IoT terminal devices. At this time, terminal devices of different modes and protocols are often connected. In order to access terminal devices of different modes and protocols, the monitoring system platform needs to access the SDK (Software Development Kit) of each manufacturer in different forms or use different data ports and third-party open source components to connect to the network, manage devices and analyze data for different forms of devices.

[0064] In order to solve the technical problems of high coupling and low compatibility caused by the use of uncontrollable third-party SDKs and open source components.

[0065] refer to Figure 1 The embodiment of the present invention discloses an aggregation processing system for multiple IoT terminal protocols for DCIM, the system comprising: at least one IoT terminal, a DCIM server, a receiving module 1, a registration module 2, an allocation module 3, an inbound and outbound rule loading module 4, a mapping relationship establishment module 5, an encapsulation module 6, a multiplexer 7, a monitoring module 8, a data verification rule loading module 9, a detection module 10, and an abnormal data processing module 11.

[0066] refer to Figure 2 After the receiving module 1 receives the connection request of at least one IoT terminal; the registration module 2 registers each IoT terminal and obtains the corresponding registration identifier; the allocation module 3 allocates a channel and a buffer register to each IoT terminal; the inbound and outbound rule loading module 4 loads the inbound and outbound rules corresponding to the allocated channels for each IoT terminal from the inbound and outbound rule library; the mapping relationship establishment module 5 establishes a mapping relationship between the registration identifier, the allocated channel and the buffer register, and the loaded inbound and outbound rules for each connection request; the encapsulation module 6 uses the mapping relationship to perform unified data encapsulation and establish a unified external connection interface.

[0067] refer to Figure 3The multiplexer 7 detects in real time whether at least one communication channel is in a readable and writable state; if the communication channel is in a readable and writable state, the communication channel is determined as the first channel; if the communication channel is not in a readable and writable state, the communication channel is determined as the second channel; the first channel is selected as the channel to be allocated.

[0068] refer to Figure 4 The monitoring module 8 builds a unified data link monitoring channel to monitor the unified external connection interface in real time; the data verification rule loading module 9 selects and loads the corresponding data verification rule from the data verification rule library according to the protocol type of the allocated channel; the detection module 10 uses the data verification rule to perform abnormal data link detection on the transmission data of the current communication channel; the abnormal data processing module 11 responds to the abnormal data link based on the corresponding preset abnormal response rule in the data verification rule.

[0069] Compared with the prior art, the embodiment of the present invention discloses an aggregation processing method and system for multiple IoT terminal protocols for DCIM. After receiving a connection request from a peripheral IoT terminal, the embodiment of the present invention registers the peripheral IoT terminal in a multiplexer, allocates a communication channel and a buffer register, establishes a full-duplex non-blocking network communication channel, loads inbound and outbound rules according to the protocol type of the communication channel, builds a data link monitoring channel, monitors the communication channel and the data link layer, loads data verification rules according to the protocol type of the communication channel and performs data verification detection, processes abnormal data according to the verification result, and encapsulates the protocol data of the communication channel to generate a data interface in a unified format. When connecting IoT terminals of different protocols, the coupling degree is reduced and the compatibility is improved.

[0070] Corresponding to the above-disclosed system for aggregating and processing multiple IoT terminal protocols for DCIM, an embodiment of the present invention further discloses a method for aggregating and processing multiple IoT terminal protocols for DCIM. The following describes in detail the method for aggregating and processing multiple IoT terminal protocols for DCIM disclosed in an embodiment of the present invention in combination with the above-described system for aggregating and processing multiple IoT terminal protocols for DCIM.

[0071] refer to Figure 2 , receiving a connection request from at least one IoT terminal; registering each IoT terminal to obtain a corresponding registration identifier; allocating a channel and a buffer register to each IoT terminal; loading an inbound and outbound rule corresponding to the allocated channel for each IoT terminal from an inbound and outbound rule library; for each connection request, establishing a mapping relationship between the registration identifier, the allocated channel and the buffer register, and the loaded inbound and outbound rules; using the mapping relationship to perform unified data encapsulation and establish a unified external connection interface.

[0072] Among them, the inbound and outbound rules are used to parse / encapsulate data packets of different protocols and generate a data interface in a unified format; the buffer register is used to temporarily store input / output data, a storage device that makes up for the difference in different data processing rates, and is a bidirectional queue data cache.

[0073] refer to Figure 3 Before allocating a channel to each IoT terminal, detect in real time whether at least one communication channel is in a readable and writable state; if the communication channel is in a readable and writable state, determine the communication channel as a first channel; if the communication channel is not in a readable and writable state, determine the communication channel as a second channel; select the first channel as the channel to be allocated.

[0074] The multiplexer is used to detect in real time whether one or more communication channels are in a readable or writable state, thereby realizing single-threaded management of multiple communication channels.

[0075] Preferably, reference Figure 4 , build a unified data link monitoring channel to monitor the unified external connection interface in real time; select and load corresponding data verification rules from the data verification rule library according to the protocol type of the allocated channel; use the data verification rules to perform abnormal data link detection on the transmission data of the current communication channel; respond to the abnormal data link based on the corresponding preset abnormal response rules in the data verification rules.

[0076] Specifically, refer to Figure 5 , determine whether there is a transmission anomaly in the data link layer; if there is a transmission anomaly in the data link layer, determine that an abnormal data link is detected; if there is no transmission anomaly in the data link layer, determine whether the current communication channel is abnormal; if the current communication channel is normal, continue to monitor the unified external connection interface; if the current communication channel is abnormal, determine that an abnormal data link is detected.

[0077] refer to Figure 6 , determine the abnormal type of the abnormal data link; if the abnormal type is a communication connection abnormality, reconnect according to the preset abnormal response rule, and provide abnormal response information feedback; if the abnormal type is a communication environment interference abnormality, shield the interference source according to the preset abnormal response rule, and provide abnormal response information feedback.

[0078] Furthermore, by utilizing the mapping relationship, different types of communication protocol data are encapsulated into a unified format using unified data encapsulation according to the inbound and outbound rules, so that other modules can uniformly process and use the communication protocol data.

[0079] Specifically, the communication protocol types include standard protocols and non-standard protocols. The standard protocols include: MODBUS communication protocol, SNMP (Simple Network Management Protocol), IPMI (Intelligent Platform Management Interface), power supply protocol, etc.; the non-standard protocols are private protocols.

[0080] Among them, each protocol has corresponding inbound and outbound rules for parsing / encapsulating data, and corresponding data verification rules are used to perform data verification detection on the transmitted data.

[0081] After the DCIM server successfully establishes a connection with the IoT terminal, the embodiment of the present invention sets up a unified data link monitoring channel to monitor the unified external connection interface in real time; selects and loads corresponding data verification rules from the data verification rule library according to the protocol type of the allocated channel; uses the data verification rules to perform abnormal data link detection on the transmission data of the current communication channel; and responds to the abnormal data link based on the corresponding preset abnormal response rules in the data verification rules. In this way, when connecting different IoT terminals, the data parsing process is controllable.

[0082] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the present invention can be implemented using a combination of hardware and software. When software is used, the corresponding functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. Storage media can be any available media that can be accessed by general or special-purpose computers.

[0083] Although the present invention has been described in detail above by general description and specific embodiments, 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. A method for aggregate processing of multiple IoT terminal protocols for DCIM, characterized in that: The method is applied to a DCIM server, and includes: Receiving a connection request from at least one IoT terminal; Register each IoT terminal and obtain the corresponding registration ID; Allocate channels and buffer registers to each IoT terminal; Loading the inbound and outbound rules corresponding to the assigned channels for each IoT terminal from the inbound and outbound rule library; For each connection request, a mapping relationship is established between the registration identifier, the allocated channel and the buffer register, and the loaded inbound and outbound rules; Using the mapping relationship to perform unified data encapsulation and establish a unified external connection interface; The inbound and outbound rules are used to parse / encapsulate data packets of different protocols and generate a data interface in a unified format. Each protocol has a corresponding inbound and outbound rule for parsing / encapsulating data; The communication protocol types include standard protocols and non-standard protocols. The standard protocols include: MODBUS communication protocol, SNMP (Simple Network Management Protocol), IPMI (Intelligent Platform Management Interface), and power supply protocol; the non-standard protocols are private protocols.

2. The method for aggregating and processing multiple IoT terminal protocols for DCIM according to claim 1, characterized in that: Before allocating a channel to each IoT terminal, the method further includes: Real-time detection of whether at least one communication channel is in a readable or writable state; If the communication channel is in a readable and writable state, determining the communication channel as the first channel; If the communication channel is not in a readable and writable state, determining the communication channel as a second channel; The first channel is selected as the channel to be allocated.

3. The method for aggregating and processing multiple IoT terminal protocols for DCIM according to claim 1, characterized in that: The method further comprises: Building a unified data link monitoring channel to monitor the unified external connection interface in real time; Select and load corresponding data verification rules from the data verification rule library according to the protocol type of the allocated channel; Using the data verification rule, abnormal data link detection is performed on the transmission data of the current communication channel; A response operation is performed on the abnormal data link based on a preset abnormal response rule corresponding to the data verification rule.

4. The method for aggregating and processing multiple IoT terminal protocols for DCIM according to claim 3, characterized in that: Using the data verification rule, abnormal data link detection is performed on the transmission data of the current communication channel, including: Determine whether there is any transmission anomaly in the data link layer; If a transmission anomaly occurs in the data link layer, it is determined that an abnormal data link is detected; If there is no transmission anomaly in the data link layer, determine whether the current communication channel is abnormal; If the current communication channel is normal, continue to monitor the unified external connection interface; If the current communication channel is abnormal, it is determined that an abnormal data link is detected.

5. The method for aggregating and processing multiple IoT terminal protocols for DCIM according to claim 4, characterized in that: Performing a response operation on the abnormal data link based on a preset abnormal response rule corresponding to the data verification rule includes: Determining the abnormal type of the abnormal data link; If the abnormality type is a communication connection abnormality, reconnect according to the preset abnormal response rule and provide abnormal response information feedback; If the abnormality type is a communication environment interference abnormality, the interference source is shielded according to the preset abnormality response rule, and abnormal response information is fed back.

6. The method for aggregating and processing multiple IoT terminal protocols for DCIM according to claim 5, characterized in that: The mapping relationship is used to perform unified data encapsulation and establish a unified external connection interface, including: By utilizing the mapping relationship and using a unified data encapsulation, different types of communication protocol data are encapsulated into a unified format according to the inbound and outbound rules, so that other modules can uniformly process and use the communication protocol data.

7. An aggregation processing system for multiple IoT terminal protocols for DCIM, characterized in that: The system comprises: A receiving module, used to receive a connection request from at least one IoT terminal; The registration module is used to register each IoT terminal and obtain the corresponding registration identifier; An allocation module, used to allocate channels and buffer registers to each IoT terminal; An inbound and outbound rule loading module, used to load the inbound and outbound rules corresponding to the allocated channels for each IoT terminal from the inbound and outbound rule library; A mapping relationship establishment module, used for establishing a mapping relationship between the registration identifier, the allocated channel and the buffer register, and the loaded inbound and outbound rules for each connection request; An encapsulation module, used to perform unified data encapsulation using the mapping relationship and establish a unified external connection interface; The inbound and outbound rules are used to parse / encapsulate data packets of different protocols and generate a data interface in a unified format. Each protocol has a corresponding inbound and outbound rule for parsing / encapsulating data; The communication protocol types include standard protocols and non-standard protocols. The standard protocols include: MODBUS communication protocol, SNMP (Simple Network Management Protocol), IPMI (Intelligent Platform Management Interface), and power supply protocol; the non-standard protocols are private protocols.

8. The aggregation processing system for multiple IoT terminal protocols for DCIM according to claim 7, characterized in that: The system also includes a multiplexer for performing the following steps before allocating a channel to each IoT terminal: Real-time detection of whether at least one communication channel is in a readable or writable state; If the communication channel is in a readable and writable state, determining the communication channel as the first channel; If the communication channel is not in a readable and writable state, determining the communication channel as a second channel; The first channel is selected as the channel to be allocated.

9. The aggregation processing system for multiple IoT terminal protocols for DCIM according to claim 7, characterized in that: The system further comprises: A monitoring module, used to build a unified data link monitoring channel and monitor the unified external connection interface in real time; A data verification rule loading module is used to select and load corresponding data verification rules from a data verification rule library according to the protocol type of the allocated channel; A detection module, used to perform abnormal data link detection on the transmission data of the current communication channel by using the data verification rule; The abnormal data processing module is used to respond to the abnormal data link based on the preset abnormal response rule corresponding to the data verification rule.

Images