An MQTT-based SNMP management method, apparatus, and system

Abstract

This disclosure relates to the field of centralized network management, and discloses an SNMP management method, apparatus, and system based on MQTT. The method includes: extending the SNMP protocol community to support tagging that carries information including link resources, communication resources, and the enterprise private network OLT device ID; encapsulating the extended SNMP protocol into the MQTT protocol; and extending the MQTT protocol by adding layers to the published topic to support information exchange. This disclosure, by extending the MQTT protocol, can realize SNMP management in various networking environments, such as private-to-public and private-to-private.

Description

Technical Field

[0001] This disclosure relates to the field of centralized network management technology, specifically to an SNMP management method, device, and system based on MQTT. Background Technology

[0002] Currently, in POL (Passive Optical LAN) campuses and FTTR-B (Fiber to the Room-Business) scenarios, operators want centralized network management of OLT (Optical Line Terminal) devices deployed across different enterprise networks. Existing OLT remote management methods use SNMP (Simple Network Management Protocol) technology, which is a C / S (Client / Server) architecture and does not support NAT (Network Address Translation) traversal between private and public networks or between private networks. OLT devices located on enterprise private networks cannot be uniformly managed by the operator's network management system. A complete overhaul of the OLT management protocol would be costly and difficult to implement.

[0003] In summary, due to the requirements of different scenarios, the cost of modification, and the difficulty involved, there is an urgent need for a method to extend SNMP to support private-to-public and private-to-private network management technologies. Summary of the Invention

[0004] This disclosure provides an MQTT-based SNMP management method, apparatus, and system to solve or alleviate one or more of the above-mentioned technical problems in the prior art.

[0005] According to one aspect of this disclosure, an MQTT-based SNMP management method is provided, comprising:

[0006] By extending the SNMP protocol community, it can support tagging that carries information including link resources, communication resources, and the enterprise private network OLT device ID;

[0007] The extended SNMP protocol is encapsulated into the MQTT protocol;

[0008] The MQTT protocol can be extended by adding layers to the published topics to support message exchange.

[0009] In one possible implementation, the hierarchical tag format for publishing topics is: / snmp / channel / request;

[0010] The data format carried by the hierarchical value of the published topic includes the request ID, product key, device name, device ID, and timestamp information.

[0011] In one possible implementation, the above-described MQTT-based SNMP management method is applicable to the OLT side, including establishing a data transmission link between the client functional entity and the server functional entity:

[0012] The client functional entity on the enterprise private network OLT device side initiates a chain establishment request to the server functional entity on the network management side through the extended MQTT protocol. The chain establishment request is used to establish a data processing link between the client functional entity and the server functional entity.

[0013] One possible implementation involves bringing enterprise private network OLT devices online:

[0014] The client function entity on the enterprise private network OLT device side obtains the online request sent by the SNMP Agent of the enterprise private network OLT device;

[0015] The client functional entity on the enterprise private network OLT device side tags the link resources and communication resources to the SNMP community of the online request, forming the first online request data packet;

[0016] The client functional entity on the enterprise private network OLT device side, based on the extended MQTT protocol, sends the online request data packet to the server functional entity through the data processing link. The online request data packet is used to identify the enterprise private network OLT device after stripping the MQTT packet header, and complete the online of the enterprise private network OLT device.

[0017] One possible implementation includes configuring and querying the functions of the enterprise's private network OLT devices:

[0018] The client functional entity on the enterprise private network OLT device side obtains the functional configuration and query data packets sent by the server functional entity through the link target;

[0019] The client functional entity on the enterprise private network OLT device side forwards the extended SNMP message label to the SNMP Agent after removing it from the function configuration and query data packets.

[0020] In one possible implementation, the above-mentioned MQTT-based SNMP management method is applicable to the network management side, including:

[0021] The server-side functional entity on the network management side interacts with the client-side functional entity on the enterprise private network OLT device side by extending the MQTT protocol;

[0022] The server-side functional entity on the network management side operates on the client-side functional entity on the online enterprise private network OLT device side.

[0023] One possible implementation involves establishing a data transmission link between the client-side functional entity and the server-side functional entity:

[0024] The server-side functional entity on the network management side obtains the chain establishment request initiated by the client functional entity through the extended MQTT protocol;

[0025] The server-side functional entity on the network management side authenticates the link establishment request. After successful authentication, it allocates link resources and communication resources to the client functional entity to complete the establishment of the data processing link.

[0026] One possible implementation involves bringing the enterprise private network OLT device online on the network management side:

[0027] The server-side functional entity on the network management side obtains the online request data packet sent by the client functional entity through the data processing link based on the extended MQTT protocol;

[0028] The server-side functional entity on the network management side forwards the online request data packet to the network management system after stripping the MQTT header. The online request data packet after stripping the MQTT header is used to identify the enterprise private network OLT device and complete the online process of the enterprise private network OLT device.

[0029] In one possible implementation, configuring and querying the functions of the enterprise private network OLT device on the network management side includes:

[0030] The server-side functional entity on the network management side obtains the functional configuration and query data packets sent by the network management system.

[0031] The server-side functional entity on the network management side identifies the link target to be forwarded based on extended SNMP;

[0032] The server-side functional entity on the network management side forwards the functional configuration and query data packets to the client-side functional entity through the link target.

[0033] According to one aspect of this disclosure, an OLT-side information interaction device is provided for implementing the above-described MQTT-based SNMP management method.

[0034] According to one aspect of this disclosure, a network management side information interaction device is provided for the above-mentioned MQTT-based SNMP management method.

[0035] According to one aspect of this disclosure, an information interaction system is provided, including the aforementioned OLT-side information interaction device and network management-side information interaction device.

[0036] This disclosure has the following beneficial effects:

[0037] This disclosure enables SNMP management in various network environments, such as private-to-public and private-to-private, by extending the MQTT protocol; it allows for low-cost network traversal management using existing MQTT channels and is easy to deploy quickly; and by extending the SNMP protocol to enable shared port link forwarding, it avoids performance bottlenecks caused by server port limitations.

[0038] Details of one or more embodiments of this application are set forth in the following drawings and description. Other features and advantages of this application will become apparent from the accompanying drawings. It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not intended to limit this disclosure. Attached Figure Description

[0039] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0040] Figure 1 This is one of the flowcharts of an MQTT-based SNMP management method in this exemplary embodiment;

[0041] Figure 2 This is the second flowchart of an MQTT-based SNMP management method in this exemplary embodiment;

[0042] Figure 3 This is a schematic diagram of the link establishment, device discovery, and packet forwarding path in this exemplary embodiment. Detailed Implementation

[0043] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this disclosure more comprehensive and complete, and to fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a full understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced with one or more of the specific details omitted, or other methods, components, apparatus, steps, etc., can be employed. In other instances, well-known technical solutions are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0044] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware units or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0045] The flowchart shown in the attached diagram is merely an illustrative example and does not necessarily include all steps. For example, some steps may be broken down, while others may be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0046] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein.

[0047] Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion, such that a process, method, system, product, or device that includes a series of steps or sub-modules is not necessarily limited to those steps or sub-modules that are explicitly listed, but may include other steps or sub-modules that are not explicitly listed or that are inherent to such process, method, product, or device.

[0048] Figure 1 This is one of the flowcharts of an MQTT-based SNMP management method in this exemplary embodiment, such as... Figure 1 As shown, an exemplary embodiment of this disclosure provides an MQTT-based SNMP management method, including:

[0049] By extending the SNMP protocol community, it can support tagging that carries information including link resources, communication resources, and the enterprise private network OLT device ID;

[0050] The extended SNMP protocol is encapsulated into the MQTT protocol;

[0051] The MQTT protocol can be extended by adding layers to the published topics to support message exchange.

[0052] This embodiment addresses the bottlenecks in existing technologies by providing an SNMP management method for public-to-private and private-to-private network configurations in large-scale POL (Pool of Networks) campuses. By extending the MQTT and SNMP protocols, it overcomes the technical barriers of existing management solutions. This embodiment adds a client-side functional entity on the enterprise private network OLT side and a server-side functional entity on the network management side to process MQTT protocol messages and tag and modify SNMP protocol messages.

[0053] Specifically, the hierarchical tag format for publishing topics is: / snmp / channel / request;

[0054] The data format carried by the hierarchical value of the published topic includes the request ID, product key, device name, device ID, and timestamp information.

[0055] It is worth noting that the client and server functional entities communicate via the MQTT protocol. The original MQTT protocol is the standard MQTT protocol. In this embodiment, the MQTT protocol is extended by adding a Publish topic (PubTopic) level. The hierarchical tag format of the MQTT protocol's Publish Topic is: / SNMP / channel / request; the data format carried by the hierarchical value of the MQTT protocol's Publish Topic includes request ID, product key, device name, device ID, and timestamp information.

[0056] Specifically, the above-mentioned MQTT-based SNMP management method is applicable to the OLT side, including establishing a data transmission link between the client functional entity and the server functional entity:

[0057] The client functional entity on the enterprise private network OLT device side initiates a chain establishment request to the server functional entity on the network management side through the extended MQTT protocol. The chain establishment request is used to establish a data processing link between the client functional entity and the server functional entity.

[0058] Specifically, this includes the deployment of enterprise private network OLT devices:

[0059] The client function entity on the enterprise private network OLT device side obtains the online request sent by the SNMP Agent of the enterprise private network OLT device;

[0060] The client functional entity on the enterprise private network OLT device side tags the link resources and communication resources to the SNMP community of the online request, forming the first online request data packet;

[0061] The client functional entity on the enterprise private network OLT device side, based on the extended MQTT protocol, sends the online request data packet to the server functional entity through the data processing link. The online request data packet is used to identify the enterprise private network OLT device after stripping the MQTT packet header, and complete the online of the enterprise private network OLT device.

[0062] Specifically, this includes configuring and querying the functions of enterprise private network OLT devices:

[0063] The client functional entity on the enterprise private network OLT device side obtains the functional configuration and query data packets sent by the server functional entity through the link target;

[0064] The client functional entity on the enterprise private network OLT device side forwards the extended SNMP message label to the SNMP Agent after removing it from the function configuration and query data packets.

[0065] Specifically, the above-mentioned MQTT-based SNMP management method is applicable to the network management side, including:

[0066] The server-side functional entity on the network management side interacts with the client-side functional entity on the enterprise private network OLT device side by extending the MQTT protocol;

[0067] The server-side functional entity on the network management side operates on the client-side functional entity on the online enterprise private network OLT device side.

[0068] Specifically, this includes establishing a data transmission link between the client-side functional entity and the server-side functional entity:

[0069] The server-side functional entity on the network management side obtains the chain establishment request initiated by the client functional entity through the extended MQTT protocol;

[0070] The server-side functional entity on the network management side authenticates the link establishment request. After successful authentication, it allocates link resources and communication resources to the client functional entity to complete the establishment of the data processing link.

[0071] Specifically, this includes bringing enterprise private network OLT devices online on the network management side:

[0072] The server-side functional entity on the network management side obtains the online request data packet sent by the client functional entity through the data processing link based on the extended MQTT protocol;

[0073] The server-side functional entity on the network management side forwards the online request data packet to the network management system after stripping the MQTT header. The online request data packet after stripping the MQTT header is used to identify the enterprise private network OLT device and complete the online process of the enterprise private network OLT device.

[0074] Specifically, configuring and querying the functions of enterprise private network OLT devices on the network management side includes:

[0075] The server-side functional entity on the network management side obtains the functional configuration and query data packets sent by the network management system.

[0076] The server-side functional entity on the network management side identifies the link target to be forwarded based on extended SNMP;

[0077] The server-side functional entity on the network management side forwards the functional configuration and query data packets to the client-side functional entity through the link target.

[0078] It is worth noting that the client functional entity initiates a connection request to the server functional entity by extending the publication topic of the MQTT protocol. The client functional entity can include a username and password in the connection request. After receiving the connection request, the server functional entity checks the validity of the request and verifies whether the username or password provided by the client is correct according to the pre-configured authentication information. If the request is valid, the authentication is successful, the connection is established, and the server functional entity allocates link resources and communication information (IP + port resources for communication) to the client functional entity and informs the client functional entity of the authentication result.

[0079] After the link is established, the OLT device's online status will trigger the device's first online process. The OLT's SNMP agent sends a TRAP message for the first online status to the client functional entity through the local loopback address (127.0.0.1:162). The client functional entity marks the allocated link resources and communication information to the SNMP community through the extended SNMP protocol, and forwards the device online message to the server functional entity through the extended MQTT protocol using the allocated link information. The server functional entity then removes the MQTT header from the message and forwards it to the network management system, which identifies the newly added device online.

[0080] After the OLT device comes online, when the network management system configures various functions of the device (such as configuring the network management interface) or issues query commands, it sends an extended SNMP packet to the server-side functional entity, which then forwards the message to the device-side client functional entity. The client then removes the extended SNMP packet label and forwards it to the SNMP Agent to take effect. This message process is called the SNMPDOWN message.

[0081] When the SNMP Agent receives a configuration or query command from the network management system, it sends it to the server-side functional entity, which then forwards it to the device-side client-side functional entity. Finally, the SNMP Agent forwards the command to the SNMP Agent. Upon receiving the configuration or query command from the network management system, the SNMP Agent processes the command based on the Object Identifier (OID) and corresponding value contained in the SNMP Data Protocol Unit (PDU). It first uses the OID to locate the corresponding configuration function, then unpacks the corresponding value and calls the service interface to execute the command. The execution result is then sent to the client-side functional entity. The client-side functional entity extends the SNMP protocol to tag the link allocation information into the SNMP community and forwards it to the server-side functional entity using the allocated link information. The server-side functional entity then removes the MQTT header from the message and forwards it to the network management system for message processing. This message process is the SNMP UP message, which is the same as the OLT device online process.

[0082] The following is combined Figure 2 and Figure 3 This disclosure provides a detailed explanation. Figure 3 In NAT (Network Address Translation), when a device on the internal network sends a data packet to the external network, the NAT device translates the source IP address in the packet to a public IP address and records this translation. When the external network responds with a data packet, the NAT device, based on the previously recorded translation, translates the destination IP address back from the public IP address to the internal private IP address, and then forwards the packet to the device on the internal network. The MQTT broker is a key component of the MQTT protocol (responsible for message relay and connection management).

[0083] Figure 3 When the network management system is on a public network, in OLT device discovery or SNMP uplink messages, OLT devices on the private network publish messages to Mqtt_Broker through the client function entity, and the server function entity on the network management side on the public network subscribes to this topic and can directly and promptly obtain the message. In SNMP downlink messages, the server function entity on the network management side on the public network publishes messages to Mqtt_Broker, and OLT devices on the private network subscribe to this message through the client function entity, and can directly and promptly obtain the message.

[0084] Figure 3In a private network environment, during OLT device discovery or SNMP uplink messages, the OLT device in the private network publishes a message to the Mqtt_Broker through the client function entity. The server function entity on the network management side in the private network first needs to establish a connection with the Mqtt Broker on the public network. After the connection is established, it can subscribe to the topic and obtain the message in a timely manner. In SNMP downlink messages, the server function entity on the network management side in the public network publishes a message to the Mqtt_Broker. The OLT device in the private network subscribes to the message through the client function entity and can directly obtain the message in a timely manner.

[0085] Example: This disclosure provides an implementation method for SNMP management based on MQTT, including the following steps:

[0086] Step 1: Establish the link. The client functional entity initiates a link establishment request through the extended MQTT protocol. This request is identified by adding a hierarchical label and hierarchical value to the extended MQTT publication topic. The format of this publication topic is as follows:

[0087] The hierarchical tag format for MQTT publish topics is: / SNMP / channel / request;

[0088] The following is an example of the data format for hierarchical values ​​in an MQTT Pub Topic:

[0089] {

[0090] Request ID: 11111

[0091] Product key: xxx

[0092] Equipment Name: xxx

[0093] Device ID: xxxx

[0094] Timestamp: xxxxx

[0095] }

[0096] Step 2: The server-side functional entity authenticates the request and allocates link resources and communication resources (IP + port resources for communication);

[0097] Step 3: The server-side functional entity informs the client-side functional entity of the authentication result.

[0098] After the server-side functional entity successfully authenticates, it sends the authentication result message to the client-side functional entity. This is achieved by extending the MQTT publish topic to add hierarchical tags and values. The format of this publish topic is as follows:

[0099] The hierarchical tag format for MQTT publish topics is: / SNMP / channel / {device ID} / reply;

[0100] The following is an example of the data format for hierarchical values ​​in an MQTT Pub Topic:

[0101] {

[0102] Request ID: 1111

[0103] channel ID:xxxxxx

[0104] IP address: 1.1.1.1

[0105] port:444

[0106] }

[0107] Step 4: When the OLT device comes online for the first time, the OLT's SNMP agent sends a TRAP message to the client functional entity via the local loopback address (127.0.0.1:162) or internal message communication.

[0108] Step 5: After receiving the device online message, the client functional entity tags the link allocation information into the SNMP community by extending the SNMP protocol, thereby extending the SNMP protocol stack community field. The extended SNMP protocol stack community field supports information formats such as IP port and link ID, which are used by network management to discover devices. The extended community format is as follows: {community}@{ip}@{port}@{channel ID}@{device ID}.

[0109] For example, the community field in the original SNMP protocol stack is: community:adsl;

[0110] The expanded version is: community:adsl@172.169.1.1@8990@123456@fhtt123456.

[0111] Step 6: The client functional entity, using the allocated link information, adds a layer label and layer value to the extended MQTT publish topic and forwards the device online data packet to the server functional entity. This device online data packet carries an Extended SNMP PDU (device discover) message. The server functional entity, after stripping the MQTT header from the message, forwards the message carrying the Extended SNMP to the network management system.

[0112] The format for this posting topic is as follows:

[0113] The hierarchical tag format for MQTT publish topics is: / SNMP / channel / {channel ID} / Up message;

[0114] The data content carried by the hierarchical value of the MQTT Public Topic is a binary extended SNMP PDU packet.

[0115] Step 7: Extract key information of the device based on the extended SNMP protocol to identify newly added devices.

[0116] Step 8: When the network administrator operates the device, it sends data packets to the server functional entity via extended SNMP.

[0117] Step 9: After receiving the message, the server-side functional entity identifies the link target to be forwarded based on the extended SNMP community information.

[0118] Step 10: The server-side functional entity forwards the message to the device-side client functional entity using the MQTT extended Publish Topic Down message, which identifies the link target to be forwarded in step 9.

[0119] Extend MQTT's Publish Topic support for / SNMP / channel / {channel ID} / Down messages.

[0120] The data carried is an extended SNMP PDU message in binary format.

[0121] Step 11: The client functional entity removes the extended SNMP message label and forwards it to the SNMP Agent for it to take effect.

[0122] Step 12: The SNMP Agent receives the configuration or query command forwarded by the client functional entity on the device side, processes the command, and reuses the SNMP UP message flow for the execution result, consistent with the device discovery process, and forwards the message to the network management system for processing.

[0123] An exemplary embodiment of this disclosure provides an OLT-side information interaction device for implementing an MQTT-based SNMP management method.

[0124] An exemplary embodiment of this disclosure provides a network management side information interaction device for the aforementioned MQTT-based SNMP management method.

[0125] An exemplary embodiment of this disclosure provides an information interaction system, including the aforementioned OLT-side information interaction device and network management-side information interaction device.

[0126] The above are merely preferred embodiments of this disclosure. The scope of protection of this disclosure is not limited to the above embodiments. All technical solutions falling within the scope of this disclosure are protected. It should be noted that for those skilled in the art, any improvements and modifications made without departing from the principles of this disclosure should be considered within the scope of protection of this disclosure.

Claims

1. An SNMP management method based on MQTT, characterized in that, include: By extending the SNMP protocol community, it can support tagging that carries information including link ID, communication IP and port, as well as the enterprise private network OLT device ID; The extended SNMP protocol is encapsulated into the MQTT protocol; The MQTT protocol can be extended by adding layers to the published topics to support message exchange.

2. The SNMP management method based on MQTT according to claim 1, characterized in that, The hierarchical tag format for publishing topics is: / snmp / channel / request; The data format carried by the hierarchical value of the published topic includes the request ID, product key, device name, device ID, and timestamp information.

3. The SNMP management method based on MQTT according to claim 1 or 2, characterized in that, Applicable to the OLT side, including establishing a data transmission link between client functional entities and server functional entities: The client functional entity on the enterprise private network OLT device side initiates a chain establishment request to the server functional entity on the network management side through the extended MQTT protocol. The chain establishment request is used to establish a data processing link between the client functional entity and the server functional entity.

4. The SNMP management method based on MQTT according to claim 3, characterized in that, Including the deployment of enterprise private network OLT devices: The client function entity on the enterprise private network OLT device side obtains the online request sent by the SNMP Agent of the enterprise private network OLT device; The client functional entity on the enterprise private network OLT device side tags the link ID, communication IP and port to the SNMP community of the online request, forming the first online request data packet; The client function entity on the enterprise private network OLT device side sends the online request data packet to the server function entity through the data processing link based on the extended MQTT protocol; The online request data packet is used to identify the enterprise private network OLT device after stripping the MQTT packet header, and to complete the online process of the enterprise private network OLT device.

5. The SNMP management method based on MQTT according to claim 3, characterized in that, This includes configuring and querying the functions of enterprise private network OLT devices: The client functional entity on the enterprise private network OLT device side obtains the functional configuration and query data packets sent by the server functional entity through the link target; The client functional entity on the enterprise private network OLT device side forwards the extended SNMP message label to the SNMP Agent after removing it from the function configuration and query data packets.

6. The SNMP management method based on MQTT according to claim 1 or 2, characterized in that, Applicable to the network management side, including: The server-side functional entity on the network management side interacts with the client-side functional entity on the enterprise private network OLT device side by extending the MQTT protocol; The server-side functional entity on the network management side operates on the client-side functional entity on the online enterprise private network OLT device side.

7. The SNMP management method based on MQTT according to claim 6, characterized in that, This includes establishing a data transmission link between the client-side functional entity and the server-side functional entity: The server-side functional entity on the network management side obtains the chain establishment request initiated by the client functional entity through the extended MQTT protocol; The server-side functional entity on the network management side authenticates the link establishment request. After successful authentication, it assigns the link ID, communication IP, and port to the client functional entity, thus completing the establishment of the data processing link.

8. The SNMP management method based on MQTT according to claim 6, characterized in that, This includes bringing enterprise private network OLT devices online on the network management side: The server-side functional entity on the network management side obtains the online request data packet sent by the client functional entity through the data processing link based on the extended MQTT protocol; The server-side functional entity on the network management side forwards the online request data packet to the network management system after stripping the MQTT header. The online request data packet after stripping the MQTT header is used to identify the enterprise private network OLT device and complete the online process of the enterprise private network OLT device.

9. The SNMP management method based on MQTT according to claim 6, characterized in that, On the network management side, configuring and querying functions for enterprise private network OLT devices includes: The server-side functional entity on the network management side obtains the functional configuration and query data packets sent by the network management system. The server-side functional entity on the network management side identifies the link target to be forwarded based on extended SNMP; The server-side functional entity on the network management side forwards the functional configuration and query data packets to the client-side functional entity through the link target.

10. An information interaction system, comprising an OLT-side information interaction device and a network management-side information interaction device, wherein the OLT-side information interaction device is used to implement the MQTT-based SNMP management method according to any one of claims 3-5; and the network management-side information interaction device is used to implement the MQTT-based SNMP management method according to any one of claims 6-9.

Images