SNMP management method, device and system based on MQTT

Abstract

The invention relates to the field of intensive network management, and discloses an SNMP management method, device and system based on MQTT, and the method comprises the steps: supporting the marking of information carrying a link resource, a communication resource and an enterprise private network OLT equipment ID through expanding a community of an SNMP protocol; the expanded SNMP protocol is packaged into an MQTT (Message Queuing Telemetry Transport) protocol; the MQTT protocol is expanded by increasing the hierarchy of publishing the theme so as to support information interaction. According to the invention, by expanding the MQTT protocol, SNMP management of multiple networking environments such as private-to-public and private-to-private can be realized.

Description

Technical Field

[0001] The present disclosure relates to the technical field of intensive network management, and in particular to an MQTT-based SNMP management method, device and system. Background Art

[0002] Currently, in scenarios such as POL (Passive Optical LAN) campuses and FTTR-B (Fiber to the Room-Business), operators hope to centrally manage OLT (Optical Line Terminal) devices deployed in different enterprise networks. The existing OLT remote management method uses SNMP (Simple Network Management Protocol) technology, which belongs to the C / S (Client / Server) architecture and does not support private-to-public and private-to-private NAT (Network Address Translation) traversal networking. OLT devices located in the enterprise private network cannot be uniformly managed on the operator's network management. If the management protocol of OLT is fully modified, the modification cost will be high and the implementation will be difficult.

[0003] In summary, due to the scenario requirements, transformation costs and difficulty, there is an urgent need for a method to implement a technology to expand SNMP to support private-to-public and private-to-private networking management. Summary of the invention

[0004] The embodiments of the present disclosure provide a SNMP management method, device and system based on MQTT to solve or alleviate one or more of the above technical problems in the prior art.

[0005] According to one aspect of the present disclosure, there is provided a SNMP management method based on MQTT, comprising:

[0006] By extending the SNMP protocol community, it supports tagging to carry information including link resources, communication resources, and enterprise private network OLT device ID;

[0007] Encapsulate the extended SNMP protocol into the MQTT protocol;

[0008] The MQTT protocol is extended by adding a level of publishing topics to support information exchange.

[0009] In a possible implementation, the hierarchical tag format of the publishing topic is: / snmp / channel / request;

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

[0011] In a possible implementation, the above 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 link establishment request to the server functional entity on the network management side through the extended MQTT protocol. The link establishment request is used to establish a data processing link between the client functional entity and the server functional entity.

[0013] In one possible implementation, the enterprise private network OLT equipment is online:

[0014] The client functional 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 marks the link resources and communication resources to the SNMP community of the online request to form the first online request data packet;

[0016] The client functional entity on the enterprise private network OLT device side sends the online request data packet to the server functional 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 header, and complete the online of the enterprise private network OLT device.

[0017] In a possible implementation, the function of the enterprise private network OLT device is configured and queried:

[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 removes the extended SNMP message tag in the function configuration and query data packets and forwards them to the SNMP Agent for implementation.

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

[0021] The server functional entity on the network management side exchanges information with the client functional entity on the enterprise private network OLT device side through the extended MQTT protocol;

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

[0023] In a possible implementation, a data transmission link is established between a client functional entity and a server functional entity:

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

[0025] The server 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] In one possible implementation, the enterprise private network OLT equipment is online on the network management side:

[0027] The server 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 functional entity on the network management side strips the MQTT header from the online request data packet and forwards it to the network management; the online request data packet after stripping the MQTT header is used to identify the enterprise private network OLT device and complete the online of the enterprise private network OLT device.

[0029] In a possible implementation, function configuration and query of the enterprise private network OLT device on the network management side includes:

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

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

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

[0033] According to one aspect of the present disclosure, an OLT-side information interaction device is provided, which is used to implement the above-mentioned MQTT-based SNMP management method.

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

[0035] According to one aspect of the present disclosure, there is provided an information interaction system, comprising the above-mentioned OLT side information interaction device and network management side information interaction device.

[0036] The present disclosure has the following beneficial effects:

[0037] By extending the MQTT protocol, the present invention can realize SNMP management in various networking environments such as private to public and private to private. By utilizing the existing MQTT channel, cross-network management can be realized at a low cost, which is easy and quick to deploy. By extending the SNMP protocol to realize shared port link forwarding, the performance bottleneck caused by the limitation of the number of server ports can be avoided.

[0038] The details of one or more embodiments of the present application are presented in the following drawings and descriptions. Other features and advantages of the present application will become apparent from the accompanying drawings. It should be understood that the above general description and the detailed descriptions below are only exemplary and explanatory and cannot limit the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

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

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

[0042] Figure 3 It is a schematic diagram of link establishment, device discovery and message forwarding path of this exemplary embodiment. DETAILED DESCRIPTION

[0043] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as being limited to the examples set forth herein; on the contrary, these embodiments are provided so that the present disclosure will be more comprehensive and complete, and the concepts of the example embodiments are fully conveyed to those skilled in the art. The described features, structures, or characteristics may be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present disclosure. However, those skilled in the art will appreciate that the technical solutions of the present disclosure may be practiced while omitting one or more of the specific details, or other methods, components, devices, steps, etc. may be adopted. In other cases, known technical solutions are not shown or described in detail to avoid obscuring various aspects of the present disclosure.

[0044] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and thus their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware units or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0045] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the steps. For example, some steps may be decomposed, while some steps may be combined or partially combined, so the actual execution order may change according to the actual situation.

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

[0047] In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or sub-modules is not necessarily limited to those steps or sub-modules explicitly listed, but may include other steps or sub-modules not explicitly listed or inherent to these processes, methods, products, or apparatuses.

[0048] Figure 1 is one of the flow charts of an MQTT-based SNMP management method of this exemplary embodiment, such as Figure 1 As shown, an exemplary embodiment of the present disclosure provides an SNMP management method based on MQTT, including:

[0049] By extending the SNMP protocol community, it supports tagging to carry information including link resources, communication resources, and enterprise private network OLT device ID;

[0050] Encapsulate the extended SNMP protocol into the MQTT protocol;

[0051] The MQTT protocol is extended by adding a level of publishing topics to support information exchange.

[0052] This embodiment aims at the bottleneck existing in the prior art, and provides a method for implementing SNMP management for public-to-private and private-to-private networking in a large POL park, and breaks through the technical barriers of the existing management solutions by extending the MQTT protocol and the SNMP protocol. This embodiment adds a client functional entity on the enterprise private network OLT side, and adds a server functional entity on the network management side, which is used to process MQTT protocol messages and mark and transform SNMP protocol messages.

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

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

[0055] It is worth noting that the client functional entity and the server functional entity communicate through the MQTT protocol. The MQTT protocol before extension is the standard MQTT protocol. In this embodiment, the MQTT protocol is extended by adding a hierarchy of the publishing topic Publish topic (referred to as PubTopic). The hierarchical label format of the publishing topic Pub Topic of the MQTT protocol is: / SNMP / channel / request; the data format carried by the hierarchical value of the publishing topic Pub Topic of the MQTT protocol includes request ID, product key, device name, device ID, and timestamp information.

[0056] Specifically, the above 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 link establishment request to the server functional entity on the network management side through the extended MQTT protocol. The link establishment request is used to establish a data processing link between the client functional entity and the server functional entity.

[0058] Specifically, the online operation of enterprise private network OLT equipment includes:

[0059] The client functional 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 marks the link resources and communication resources to the SNMP community of the online request to form the first online request data packet;

[0061] The client functional entity on the enterprise private network OLT device side sends the online request data packet to the server functional 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 header, and complete the online of the enterprise private network OLT device.

[0062] Specifically, it includes function configuration and query 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 removes the extended SNMP message tag in the function configuration and query data packets and forwards them to the SNMP Agent for implementation.

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

[0066] The server functional entity on the network management side exchanges information with the client functional entity on the enterprise private network OLT device side through the extended MQTT protocol;

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

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

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

[0070] The server 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, it includes the online operation of enterprise private network OLT equipment on the network management side:

[0072] The server 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 functional entity on the network management side strips the MQTT header from the online request data packet and forwards it to the network management; the online request data packet after stripping the MQTT header is used to identify the enterprise private network OLT device and complete the online of the enterprise private network OLT device.

[0074] Specifically, the function configuration and query of the enterprise private network OLT device on the network management side includes:

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

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

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

[0078] It is worth noting that the client functional entity initiates a link establishment request to the server functional entity by extending the publishing topic of the MQTT protocol. The client functional entity can carry a username and password in the link establishment request. After receiving the link establishment request, the server functional entity checks the legitimacy of the request and verifies whether the username or password provided by the client is correct based on the pre-configured authentication information. If the request is legitimate, the authentication is successful, and the connection is established, link resources and communication information (IP+port resources for communication) are allocated to the client functional entity, and the authentication result is notified to the client functional entity.

[0079] After the link is established, the online operation of the OLT device will trigger the first online process of the device. The SNMP agent of the OLT sends the TRAP message of the first online operation 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 through the allocated link information, so that it strips the MQTT header from the message and forwards it to the network management, so that the network management can identify the newly added device online.

[0080] After the OLT device is online, when the network manager configures various functions of the device (such as the configuration of the network management interface) or issues query commands, it extends the SNMP packet to the server functional entity, which forwards the message to the device-side client functional entity, which removes the extended SNMP message tag and forwards it to the SNMP Agent for implementation. This message process is the SNMP DOWN message.

[0081] SNMP Agent receives the configuration or query command issued by the network management, sends it to the server functional entity, which then sends it to the client functional entity on the device side, and finally forwards it to the SNMP Agent. The SNMP Agent receives the configuration or query command issued by the network management side, and processes the command according to the object identifier (OID) and the corresponding value (value) contained in the data protocol unit (PDU) in SNMP. It first uses the object identifier (OID) to find the corresponding configuration function, then unpacks the corresponding value (value) to call the interface of the service to execute and take effect, and sends the execution result of the command to the client functional entity. The client functional entity marks the link allocation information into the SNMP community by extending the SNMP protocol, and forwards the allocated link information to the server functional entity, allowing it to strip the MQTT header from the message and forward it to the network management for message processing. This message process is the SNMP UP message, which is the same as the online process of the OLT equipment.

[0082] Combine the following Figure 2 and Figure 3 A detailed description of the present disclosure is given ( Figure 3 In the NAT network, NAT is a network address translation. Its working principle is that when a device in the internal network sends a data packet to the external network, the NAT device will convert the source IP address in the data packet to a public IP address and record this conversion relationship. When the external network responds to the data packet, the NAT device will convert the destination IP address from the public IP address back to the internal private IP address according to the previously recorded conversion relationship, and then forward the data packet to the device in the internal network. MQTT broker is a key component in the MQTT protocol, which performs message forwarding and management connections).

[0083] Figure 3 When the network management is in the public network, in the OLT device discovery or SNMP uplink message, the OLT device in the private network publishes a message to Mqtt_Broker through the client functional entity, and the server functional entity on the network management side in the public network subscribes to the topic and can directly and timely obtain the message; in the SNMP downlink message, the server functional entity on the network management side in the public network publishes a message to Mqtt_Broker, and the OLT device in the private network subscribes to the message to Mqtt_Broker through the client functional entity, and can directly and timely obtain the message.

[0084] Figure 3When the network management is in a private network, in the OLT device discovery or SNMP uplink message, the OLT device in the private network publishes a message to the Mqtt_Broker through the client functional entity. The server functional entity on the network management side in the private network first needs to establish a connection with the Mqtt Broker in the public network. After the connection is established, you can subscribe to the topic and obtain the message in time; in the SNMP downlink message, the server functional entity on the network management side in the public network publishes a message to the Mqtt_Broker, and the OLT device in the private network subscribes to the message to the Mqtt_Broker through the client functional entity, so you can directly obtain the message in time.

[0085] Embodiment: The present disclosure provides an implementation method of SNMP management based on MQTT, comprising the following steps:

[0086] Step 1: To establish a link, the client functional entity initiates a link establishment request by extending the MQTT protocol. The request identifies the link establishment request by adding a level tag and a level value to the publishing topic of the extended MQTT. The format of the publishing topic is as follows:

[0087] The hierarchical tag format of the MQTT Pub Topic is: / SNMP / channel / request;

[0088] The data format of the hierarchical value of the MQTT Pub Topic is as follows:

[0089] {

[0090] Request ID:11111

[0091] Product Key:xxx

[0092] Device Name:xxx

[0093] Device ID: xxxx

[0094] Timestamp: xxxxx

[0095] }.

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

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

[0098] After the server functional entity passes the authentication, it sends the authentication result message to the client functional entity, and adds the level tag and level value by extending the MQTT publishing topic. The format of the publishing topic is as follows:

[0099] The hierarchical tag format of the MQTT Pub Topic is: / SNMP / channel / {device ID} / reply;

[0100] The data format of the hierarchical value of the MQTT Pub Topic is as follows:

[0101] {

[0102] Request ID:1111

[0103] channel ID:xxxxxx

[0104] ip:1.1.1.1

[0105] port:444

[0106] }.

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

[0108] Step 5: After receiving the device online message, the client functional entity extends the SNMP protocol by marking the link allocation information into the SNMP community to extend the SNMP protocol stack community field. The extended SNMP protocol stack community field supports information formats such as IP port and link ID, which is used for 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 of the original SNMP protocol stack is: community: adsl;

[0110] After expansion: community:adsl@172.169.1.1@8990@123456@fhtt123456.

[0111] Step 6: The client functional entity uses the allocated link information to extend the MQTT publishing topic to add the level tag and level value, and forwards the device online data packet to the server functional entity. The device online data packet carries the extended SNMP message (Extend SNMP PDU (device discover)). After the server functional entity strips the MQTT header from the message, it forwards the message carrying the extended SNMP to the network management.

[0112] The format of the published topic is as follows:

[0113] The hierarchical tag format of the MQTT Pub Topic is: / SNMP / channel / {channel ID} / Up message;

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

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

[0116] Step 8: When the network manager operates the device, it sends the data packet to the server functional entity through the extended SNMP.

[0117] Step 9: After receiving the message, the server 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 Publish Topic Down message extended by MQTT, according to the link target to be forwarded identified in step 9.

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

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

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

[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, executes the result, continues to reuse the SNMP UP message process, consistent with the device discovery process, and forwards the message to the network management for processing.

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

[0124] An exemplary embodiment of the present disclosure provides a network management side information interaction device, which is used in the above-mentioned MQTT-based SNMP management method.

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

[0126] The above are only preferred implementations of the present disclosure, and the protection scope of the present disclosure is not limited to the above embodiments. All technical solutions under the concept of the present disclosure belong to the protection scope of the present disclosure. It should be pointed out that for ordinary technicians in this technical field, some improvements and modifications without departing from the principle of the present disclosure should be regarded as the protection scope of the present disclosure.

Claims

1. A SNMP management method based on MQTT, characterized in that: include: By extending the SNMP protocol community, it supports tagging to carry information including link resources, communication resources, and enterprise private network OLT device ID; Encapsulate the extended SNMP protocol into the MQTT protocol; The MQTT protocol is extended by adding a level of publishing topics to support information exchange.

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

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

4. The MQTT-based SNMP management method according to claim 3, characterized in that: Including the online launch of enterprise private network OLT equipment: The client functional 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 marks the link resources and communication resources to the SNMP community of the online request to form the first online request data packet; The client functional entity on the enterprise private network OLT device side sends the online request data packet to the server functional 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 header, and complete the online operation of the enterprise private network OLT device.

5. The MQTT-based SNMP management method according to claim 3, characterized in that: Including function configuration and query of enterprise private network OLT equipment: The client functional entity on the enterprise private network OLT device side obtains the function 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 removes the extended SNMP message tag in the function configuration and query data packets and forwards them to the SNMP Agent for implementation.

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

7. The MQTT-based SNMP management method according to claim 6, characterized in that: It includes establishing a data transmission link between the client functional entity and the server functional entity: The server functional entity on the network management side obtains the link establishment request initiated by the client functional entity through the extended MQTT protocol; The server 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.

8. The MQTT-based SNMP management method according to claim 6, characterized in that: This includes online operation of enterprise private network OLT equipment on the network management side: The server 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 functional entity on the network management side strips the MQTT header from the online request data packet and forwards it to the network management; the online request data packet after stripping the MQTT header is used to identify the enterprise private network OLT device and complete the online of the enterprise private network OLT device.

9. The SNMP management method based on MQTT according to claim 6, characterized in that: Function configuration and query of enterprise private network OLT devices on the network management side include: The server functional entity on the network management side obtains the function configuration and query data packets sent by the network management; The server functional entity on the network management side identifies the link target to be forwarded based on the extended SNMP; The server functional entity on the network management side forwards the function configuration and query data packets to the client functional entity through the link target.

10. An OLT-side information interaction device, used to implement the MQTT-based SNMP management method according to any one of claims 3 to 5.

11. A network management side information interaction device, used to implement the MQTT-based SNMP management method described in any one of claims 6 to 9.

12. An information interaction system, comprising the OLT side information interaction device according to claim 10 and the network management side information interaction device according to claim 11.

Images