WO2014110737A1

WO2014110737A1 - Method, device, and system for configuring device in network

Info

Publication number: WO2014110737A1
Application number: PCT/CN2013/070547
Authority: WO
Inventors: 王玉容; 胡仲怀
Original assignee: 华为技术有限公司
Priority date: 2013-01-16
Filing date: 2013-01-16
Publication date: 2014-07-24
Also published as: CN104205729B; CN104205729A

Abstract

The present invention relates to a method, a device, and a system for configuring a device in a network. The method comprises: an LLDP main device receiving an IP packet of an OSS, and extracting a Simple Network Management Protocol (SNMP) packet in the IP packet; the LLDP main device querying a local neighbor list according to identification information of an LLDP target device to be configured, to obtain forwarding information to the target device and SNMP information; and the LLDP main device completing SNMP packet format conversion and LLDP encapsulation according to the SNMP information, and forwarding the information from an obtained outbound interface to a specific LLDP target device, so that the LLDP target device is enabled to perform configuration by using the configuration information. Therefore, in the present invention, communication is performed in a manner of encapsulating an SNMP packet into an LLDP packet, which reduces the operation complexity of remote management by an OSS, and enables remote management of the OSS without acquiring an IP address.

Description

Device configuration method, device and system in network

The present invention relates to the field of communications, and in particular, to a device configuration method, device, and system in a network. Background technique

With the development of communication technologies, the types of network devices are increasingly numerous and their respective configurations are complicated. The plug-and-play technology of network devices makes it very easy for users to add new network devices to the system. This technology can be applied to various fields and brings great convenience.

Currently, the plug-and-play technology of network devices performs device configuration through a protocol (Internet Protocol, IP) interconnected between networks. When the device is configured with IP, you need to configure the IP forwarding path, including the Virtual Office Area (VLAN), IP address, and routing.

FIG. 1 is a schematic structural diagram of a remote management system in the prior art. As shown in Figure 1, in the remote management system, the network device and the Dynamic Host Configuration Protocol (DHCP) server need to be configured. The configuration of the network device includes traffic and DHCP configuration. The purpose of configuring the DHCP server is to assign an IP address to the plug-and-play device. When a plug-and-play device is inserted into the configuration system, the network device records the acquired IP address, and the Operation Support System (OSS) configures the plug-and-play device according to the obtained IP address.

2 is a schematic structural diagram of another remote management system in the prior art. As shown in FIG. 2, in the remote management system, it is also necessary to configure the network device and the DHCP server. After the plug-and-play device is inserted into the configuration system, the network device records the IP address obtained by the plug-and-play device, that is, The plug-and-play device 2 and the network device mutually sense each other through the Link Layer Discovery Protocol (LLDP), and send the device information of the Plug and Play device 2 to the 0SS in the manner of LLDP neighbor information. . The OSS senses the location of the plug-and-play device according to the neighbor information, and delivers the configuration information according to the location information of the plug-and-play device.

However, in the above two types of remote management systems, the network device and the DHCP server need to be configured. In addition, whether the LLDP protocol is used or not, the IP address needs to be configured for the plug-and-play device. The configuration process is complicated. Summary of the invention

The present invention provides a device configuration method, device, and system in a network, which solves the problem that the network device and the DHCP server need to be configured in the prior art, and the IP address is configured for the plug and play device, and the extended LLDP is utilized. The protocol reduces the operational complexity of remote management and enables remote management via 0SS without obtaining an IP address.

In a first aspect, the present invention provides a device configuration method in a network, where the network includes an operation support system OSS, a link layer discovery protocol LLDP master device, and one or more LLDP target devices, the one or more The LLDP target device connects to the 0SS by using the LLDP master device, and the method includes:

The LLDP master device receives the IP packet of the 0SS, and extracts a simple network management protocol, the awake P packet, from the IP packet, where the awake P packet carries the identifier information of the LLDP target device to be configured. And configuration information required by the LLDP target device to be configured;

And the LLDP master device is configured to query the correspondence between the identifier information of the LLDP target device and the forwarding information of the LLDP target device according to the identifier information of the LLDP target device to be configured, so as to obtain the forwarding information of the LLDP target device to be configured.

The LLDP master device encapsulates the S匪P packet into an LLDP packet, and sends the LLDP packet to the LLDP target device to be configured according to the obtained forwarding information, so that the LLDP target device uses the The configuration file is configured. The obtained forwarding information includes an outbound interface that is connected to the LLDP target device to be configured on the LLDP master device.

Further, the LLDP master device encapsulates the S-uppertext into an LLDP file, and the LLDP master device encapsulates the SNMP packet into the LLDP packet in the form of a type length value TLV. . The LLDP packet further carries a TLV for identifying the LLDP target device to be configured, and the TLV for identifying the LLDP target device to be configured carries the identifier information of the LLDP target device to be configured.

In a first possible implementation manner, before the receiving, by the LLDP master device, the IP packet of the 0SS, the method further includes: acquiring a topology structure of the one or more LLDP target devices, and reporting the obtained topology structure to The neighboring-topology entry is generated locally, and the entry includes a neighbor device identifier, a neighboring awake P version number, and an awake P identifier, and network topology information of the neighboring neighbor.

In a second possible implementation manner, the one or more LLDP target devices and the LLDP master device form a ring network structure, and acquiring the topology structure of the one or more LLDP target devices specifically includes: The LLDP master device sends the neighbor advertisement message to the one or more LLDP target devices, so that the LLDP target device that receives the neighbor advertisement message adds its own identity information and interface information of the received neighbor advertisement message to the neighbor. The advertisement packet is sent to the LLDP target device to the next hop. The LLDP master device receives the neighbor advertisement packet, and obtains the topology structure of the one or more LLDP target devices from the received neighbor advertisement packet.

With the second possible implementation of the first aspect, in a third possible implementation, the LLDP master device connects the first LLDP target device on one side and the second LLDP target device on the other side. The sending, by the LLDP master device, the neighbor advertisement message to the one or more LLDP target devices includes: sending, by the LLDP master device, the first neighbor advertisement message to the first LLDP target device, so that the first The LLDP target device of the neighbor advertisement packet adds its own identity information and the interface information of the first neighbor advertisement packet to the first neighbor advertisement packet, and forwards it to the LLDP target device to the next hop; the LLDP master device Sending a second neighbor advertisement message to the second LLDP target device, so that the LLDP target device that receives the second neighbor advertisement message is self- The identification information of the body and the interface information of the second neighbor advertisement message are added to the second neighbor advertisement message, and are forwarded to the LLDP target device to the next hop; the LLDP master device receives the first neighbor advertisement message and the first And obtaining, by the second neighbor advertisement message, the topology structure of the one or more LLDP target devices according to the received first neighbor advertisement message and the second neighbor advertisement message.

Further, the LLDP master device encapsulates the S awake P ^ 艮 text into the LLDP 艮 text, and the method further includes:

The LLDP master device is further configured to acquire, according to the identifier information of the LLDP target device to be configured, the W-up P version information that can be identified by the LLDP target device to be configured, according to the S-up P version information. The configuration information required for the LLDP target device to be configured is translated.

In a second aspect, the present invention provides a link layer discovery protocol LLDP device, where the device includes:

The first interface is used to connect the operation support system 0SS;

a second interface, configured to connect to one or more LLDP target devices;

a data receiver, configured to receive the IP packet of the 0SS, and extract a simple network management protocol, the awake P packet, from the IP packet, where the awake P packet carries the identifier of the LLDP target device to be configured. Information and configuration information required by the LLDP target device to be configured;

a processor, configured to query, according to the identifier information of the LLDP target device to be configured, a correspondence between the identifier information of the LLDP target device and the forwarding information of the LLDP target device, to obtain the forwarding information of the LLDP target device to be configured; The awake P packet is encapsulated into the LLDP packet, and the data transmitter is configured to send the LLDP packet to the LLDP target device to be configured according to the obtained forwarding information, so that the LLDP target is obtained. The device is configured with the configuration file.

In a first possible implementation, the processor is further configured to acquire a topology of the one or more LLDP target devices, where the data transmitter is further configured to report the acquired topology to the 0SS.

In conjunction with the first possible implementation of the second aspect, in a second possible implementation, The one or more LLDP target devices and the LLDP master device form a ring network structure, and the data transmitter is further configured to send a neighbor advertisement message to the one or more LLDP target devices, so as to receive the The LLDP target device of the neighbor advertisement packet adds its own identification information and the interface information of the neighbor advertisement packet to the next hop LLDP target device in the neighbor advertisement packet. The data receiver is also used to receive the neighbor. And the processor is configured to obtain the topology of the one or more LLDP target devices from the received neighbor advertisement message.

In a third aspect, the present invention provides a device configuration system, where the system includes a link layer discovery protocol LLDP master device and one or more LLDP target devices, and the one or more LLDP target devices pass the LLDP master The device connects to the 0SS,

The LLDP master device is configured to receive an IP packet of the operation support system 0SS, and extract a simple network management protocol S wakeup P packet from the IP packet, where the S wakeup P packet carries the LLDP target to be configured. The identifier information of the device and the configuration information required by the LLDP target device to be configured; the corresponding relationship between the identifier information of the LLDP target device and the forwarding information of the LLDP target device is queried according to the identifier information of the LLDP target device to be configured, thereby Acquiring the forwarding information of the LLDP target device to be configured; and the SWT packet is encapsulated into the LLDP packet, and the LLDP packet is sent to the LLDP target to be configured according to the obtained forwarding information. a device, such that the LLDP target device is configured with the configuration file.

In a first possible implementation manner, the LLDP master device is further configured to obtain a topology structure of the one or more LLDP target devices, and report the obtained topology structure to the 0SS.

With reference to the first possible implementation manner of the third aspect, in the second possible implementation manner, the one or more LLDP target devices and the LLDP master device form a ring network structure, and the LLDP master device is specific And sending, to the one or more LLDP target devices, a neighbor advertisement message, receiving a neighbor advertisement message, and acquiring a topological structure of the one or more LLDP target devices from the received neighbor advertisement message; The LLDP target device is configured to receive the neighbor advertisement packet, and add the identity information and the interface information of the neighbor advertisement packet to the next hop LLDP target device in the neighbor advertisement packet. By applying the device configuration method, device, and system provided above, the LLDP master device receives the IP packet of the 0SS, and extracts the simple network management protocol S awake P packet from the IP packet. The S ping P packet carries the LLDP to be configured. The identification information of the target device and the configuration file required by the LLDP target device to be configured; the LLDP master device queries the local neighbor table according to the identification information of the LLDP target device to be configured, and obtains the forwarding information and the wake-up P information of the target device. The forwarding information includes the outbound interface to the target device, and the SNMP information includes the SNMP version and the identifier of the target. The LLDP master device completes the wakeup P packet format conversion and LLDP encapsulation based on the S awake P information. The LLDP target device is forwarded to the LLDP target device, so that the LLDP target device is configured with the configuration file, and the extended LLDP protocol is used to encapsulate the LLDP packet with the LLDP device. Communication, which reduces the operational complexity of remote management of 0SS, and can realize remote remote 0SS without obtaining an IP address. Management. DRAWINGS

1 is a schematic structural diagram of a remote management system in the prior art;

2 is a schematic structural diagram of another remote management system in the prior art;

3 is a flowchart of a device configuration method in a network according to an embodiment of the present invention;

4 is a schematic structural diagram of a management system according to an embodiment of the present invention;

FIG. 5 is a flowchart of a device configuration method in a network according to an embodiment of the present invention;

FIG. 6 is a flowchart of a device configuration method in a network according to an embodiment of the present invention;

Figure Ί is an information interaction diagram of a device configuration method according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a link layer discovery protocol LLDP master device according to an embodiment of the present invention; FIG. 9 is a schematic structural diagram of a device configuration system according to an embodiment of the present invention. detailed description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. It is to be understood that the described embodiments are a part of the embodiments of the invention, rather than all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

An embodiment of the present invention provides a device configuration method. As shown in FIG. 3, the method provided includes:

In the step S300, the LLDP master device receives the IP packet of the 0SS, and extracts the simple network management protocol, the awake P packet, from the IP packet, and the awake P packet carries the identifier information of the LLDP target device to be configured and the LLDP to be configured. Configuration information required by the target device;

The identifier information of the LLDP target device to be configured may be the MAC address of the LLDP target device to be configured, the media access control address, the device identifier of the LLDP target device to be configured, or other identifiers. ID information of the LLDP target device to be configured.

The configuration information may be a parameter that needs to be configured, a value of a related parameter, and the like.

Step 310: The LLDP master device searches the mapping between the identifier information of the LLDP target device and the forwarding information of the LLDP target device according to the identifier information of the LLDP target device to be configured, so as to obtain the forwarding information of the LLDP target device to be configured.

Specifically, the forwarding information may be an outgoing interface of the LLDP target device connected to the LLDP target device, and the LLDP master device's neighbor table stores the mapping between the LLDP target device's identification information and the LLDP target device's forwarding information. The master device can query the neighbor table by using the identification information of the LLDP target device to be configured to obtain the corresponding outbound interface.

Step 320: The LLDP master device encapsulates the SNMP packet into an LLDP packet, and forwards the packet to the LLDP target device to be configured, so that the LLDP target device to be configured uses the configuration information to configure.

Specifically, the LLDP master device can encapsulate the configuration information into the LLDP packet in the form of a TLV (Type-Length-Va lve, type length value), and the LLDP master device can also set the identifier information of the LLDP target device to be configured. The form of the TLV is encapsulated in the LLDP packet, so that the LLDP target device that receives the LLDP packet can determine whether the identifier information in the TLV is consistent with its own. If the packet is inconsistent, the local neighbor table is refreshed, and the corresponding outbound interface is obtained from the neighbor table, and then forwarded.

The method provided in this embodiment implements the use of the extended LLDP protocol, and communicates between the LLDP master device and the LLDP target device through the W P P ^ 封装封装到到到到到到到封装 , , 降低降低降低降低降低降低The operation complexity, and the remote management of the LLDP target device by the 0SS can be realized without obtaining an IP address.

Specifically, FIG. 4 is a schematic structural diagram of a management system according to an embodiment of the present invention. As shown in Figure 4, the system includes an OSS 41, an LLDP master device 42, and one or more LLDP target devices. One or more LLDP target devices are connected to the LLDP master device. For example, the LLDP master device 42 has multiple interfaces for connecting LLDP plug-and-play devices, such as interface 1, interface 1 interface m. Each LLDP master device 42 can be connected to one or more LLDP target devices. For example, multiple LLDP plug-and-play devices connected to interface 1 are LLDP target device 1, LLDP target device 2, LLDP target device n-1, and LLDP target device n.

In addition, the names of the customized messages and the format of the tables involved in all embodiments of the present invention are described in detail.

First, the full name is Type-Leng th - Va lue. Where Type is the label, Leng th ^7 length, and Va lue is the value. The lengths of the T and L fields are often fixed. The most common Τ is 8 bits, L is also 8 bits, and the V field is variable in length. As the name suggests, the Τ field indicates the packet type, the L field indicates the packet length, and the V field is used to store the contents of the packet.

(1) LLDP (TLDP proxy TLV): The Type in the packet is not specific. You can use 32, that is, Type is equal to 32, and the proxy priority is recorded. The priority is mainly used to select the primary proxy device from the device. Different proxy devices can implement redundant backup. The TLV indicates that the device has the capability of agent management. Generally, it is an LLDP master device. The format is shown in Table 1.

Table 1

7 bits 9 bits 8 bits

Type 32 length priority (2) Target device TLV (LLDP Destination TLV): The Type in the packet is not specific. You can use 33, that is, Type is equal to 33, and record the specified target device identifier. It is mainly used to specify the target device when requesting or responding. The format is shown in Table 2.

Table 2

(3) TLV (LLDP topo query TLV): The Type in the packet is not specific. You can use 34, that is, Type is equal to 34. The TLV is used to indicate that the packet is a device topology query request. The format of the message is shown in Table 3.

table 3

(4) TLV (LLDP topo answer TLV): The Type in the packet is not specific. You can use 35, that is, Type is equal to 35. The TLV is used to indicate that the packet is a device topology query response. The format of the message is shown in Table 4.

Table 4

(5) Link topology TLV (LLDP topo TLV): The Type in the packet is not specific. You can use 36, that is, Type is equal to 36. In the device topology response packet, the TLV carries the link topology information, which is generally composed of the device identifier and the interface identifier. The device identifier TLV and the interface identifier TLV are defined in the LLDP standard protocol. The format of the message is shown in Table 5.

table 5 7-bit 9-bit m*8-bit

Type 36 Length (mbytes) Device Identification 1 (TLV), Device Identification n (TLV), Interface Identification 1 (TLV) Interface Identification n (TLV)

(6) Simple Network Management Protocol packet TLV (S awake P TLV): It is a custom function name, which means that the S-Weep packet is encapsulated into an LLDP packet. In the embodiment of the present invention, the LLDP master device or the target device encapsulates all the original Simple Network Management Protocol (SCDMA) packets into the LLDP packets, including the messages sent by the OSS and the LLDP. The target device response packet and the active notification packet sent when the LLDP target device fails or changes. This TLV is not specific to Type, you can use 37, that is, Type is equal to 37. The message format is shown in Table 6.

Table 6

(7) Simple Network Management Protocol (TLV): Use the custom TLV type Type in the LLDP standard. Here, the Type is not specific. You can use 38, that is, Type is equal to 38. The S-up P identifier of the LLDP device is used to identify the target device that is configured by the 0SS. V can contain the version number and identifier of the wakeup P (S wake up P V1/V2 version can use the group name, V3 version can use USM USER and key information), as shown in Table 7.

Table 7

Second, the forwarding table definition.

(1) Neighbor table of the LLDP master device: used to find information about maintaining neighbors. Neighbors include direct connections. And the indirect connection, and can find the interface when forwarding the message, only the necessary information is listed here, and the description and other information can also be added. The LLDP neighbor table is shown in Table 8.

Table 8

(2) Neighbor table of the LLDP target device: After receiving the LLDP packet, the LLDP device records or refreshes the table. It is mainly used for the intermediate device in the networking to find the forwarding exit, and the target device actively reports the information to the 0SS. The primary device is selected according to the proxy priority. If the neighbor does not have the proxy capability, the proxy priority 0 can be used. The LLDP neighbor table is shown in Table 9.

Table 9

Based on the above-mentioned packets and forwarding entries, the following describes the functions of the LLDP master and LLDP target devices in detail.

(1) LLDP master function: The proxy LLDP target device communicates with the 0SS (mainly, the S-up P-LLDP packet and the S-awake P-over IP packet are mutually converted, and then the packet is forwarded to the corresponding device and 0SS. The information about the neighbors that need to be reported to the 0SS is included. The LLDP master device information is periodically or manually notified to other LLDP target devices. The neighbor topology is learned and sent to the 0SS system, including the directly connected neighbors and the non-directly connected neighbors.

Specifically, after receiving the configuration of the wakeup P configuration or the query sent by the 0SS, the LLDP master device determines whether the device is configured according to the identifier in the wakeup P packet, and if yes, hands it over to the W agent. If the configuration is not complete, the neighboring entry is queried according to the identifier. After the version of the pinged P-type packet and the identifier are translated, the packet is encapsulated into an LLDP packet. After the target device is added to the destination device, the destination device is sent from the outbound interface. Give the next hop neighbor, and finally forward it to the specified target device. After receiving the P-over P-LLDP packet from the target device, the LLDP master device sends the IP packet to the 0SS system.

When the LLDP master learns the neighbor, the device topology query is sent by the device topology query TLV, and is sent to the target device by the target device TLV. After receiving the request, the target device responds to the device topology response message. The LLDP master device obtains the complete link topology information of the target device from the device TLV and the receiving interface TLV added by the intermediate devices in the packet, and the link topology TLV, and the information and the neighbor notification S匪The P information is reported to the 0SS system, which facilitates the configuration of the 0SS system.

(2) LLDP target device function: Forward LLDP packets and process LLDP topology query requests, process SNMP over LLDP configuration or query requests, and use SNMP over LLDP to actively send information to the 0SS system.

Specifically, after the LLDP target device receives the LLDP packet, if the packet does not carry the TLV, the TLV and the receiving interface TLV are inserted into the device and sent to all the directly connected neighbors of the non-receiving interface. The target device TLV determines whether it is the local device according to the TLV. If not, the neighboring entry is forwarded to the next hop device.

If it is determined by the target device TLV, the device determines whether the topology query request is based on whether the link topology query TLV is included. If yes, the link topology information is obtained from the packet, and the link topology TLV is obtained. After the method is encapsulated, the device topology response TLV and the specified target device TLV are added, and the source device that responds to the originating neighbor query is specified.

If it is determined by the target device TLV that the device is the device, it is also required to determine whether to wake up the P over LLDP configuration or the query request according to whether the packet carries a simple network management protocol >3⁄4 text TLV, and if yes, hand it over to the S-up P agent. The request is processed, and the wakeup P response message is constructed according to the processing result, and the response message is also encapsulated in a simple network management protocol and a TLV manner, and the response is specified by the target device TLV to the source requesting device, generally LLDP. Master device.

When the target device needs to report the information to the 0SS, it is also encapsulated in the P-over LLDP mode. The LLDP master device is selected according to the neighbor's proxy priority. Then, the target device TLV is specified. The mode is sent to the LLDP master device.

Based on FIG. 4, an embodiment of the present invention provides a device configuration method in a network. As shown in FIG. 5, the method provided may specifically include:

Step 51 0: The LLDP master device receives the IP packet of the 0SS, and extracts the Simple Network Management Protocol (SWP) packet from the IP packet. The S-Weep packet carries the identifier information of the LLDP target device to be configured and the to-be-configured Configuration information required by the LLDP target device.

Specifically, 0SS is a comprehensive business operation and management platform that can manage LLDP master devices. The LLDP master device receives the S-up P capability of the LLDP target device, such as the supported S-up P version information. The LLDP master device converts the S-up ability of the LLDP to the 0SS. The conversion process is mainly based on the fact that the S-up P version supported by the LLDP master device and the S-wake P version supported by the LLDP target device may be inconsistent. Generally, the S-up P flag carried by the LLDP target device may be used to wake up the S-supported by the LLDP target device. The version is converted to the LLDP master device and the WSS P version supported by the 0SS. Different S wakeup P versions identify devices in different ways. For example, some versions identify LLDP target devices by community name. Some versions identify LLDP target devices by user name. The specific conversion content can be converted between community name and user name. . The LLDP master device also receives the LLDP target device identification management request information delivered by the 0SS, such as query request information or configuration request information. The management request information is received by the LLDP target device corresponding to the LLDP target device identifier. The LLDP master device acting as a proxy is responsible for sending the management request information to the LLDP target device.

The configuration information can include the parameters to be configured and related values of the LLDP target device to be configured.

The device management method provided by the embodiment of the present invention, before the step 510, further includes: Step 500, the LLDP master device also needs to obtain the topology structure of the LLDP target device, and report the topology structure of the LLDP target device to the 0SS.

If the LLDP target device connected to the LLDP device is a ring network, the topology of the LLDP device can be:

The LLDP master sends neighbor advertisement packets to the LLDP target device. The LLDP target device adds its own identification information and interface information of the neighbor advertisement packet to the next hop LLDP target device in the neighbor advertisement packet. The LLDP target device can add its own identification information and the interface information of the received neighbor advertisement message to the neighbor advertisement message in the manner of the device identifier TLV and the interface identifier TLV. The LLDP target device can also support the SNMP version number supported by itself. The identifier is added to the neighbor advertisement, and the wakeup P version number and the wakeup P identifier supported by the LLDP target device can be added to the neighbor advertisement in the form of the TLV shown in Table 7.

As a ring network structure, the neighbor advertisements sent by the LLDP master device will eventually return to the LLDP master device. The neighbor advertisement packets received by the LLDP master device will carry the device identifier TLV of the LLDP target device in one direction. And the interface identifies the TLV, so that the LLDP master can know the topology in one direction.

In order to obtain a two-way topology, the LLDP master device can send a neighbor advertisement packet in two different directions. The LLDP master device receives two neighbor advertisement packets from the two neighbor advertisement packets. Get the topology in both directions.

Assume that the LLDP master device is connected to the first LLDP target device on one side and the second LLDP target device on the other side. The process of obtaining the topology structure of the LLDP master device in two directions may include:

(1) The LLDP master sends a first neighbor advertisement packet to the first LLDP target device. The LLDP target device that receives the first neighbor advertisement message adds its own identity information and the interface information of the first neighbor advertisement message to the first neighbor advertisement message, and forwards the LLDP target device to the next hop; The neighbor advertisement packet may also carry the hop count information. The LLDP target device that receives the first neighbor advertisement packet may modify the hop count information, for example, adding 1 or the like.

(2) The LLDP master sends a second neighbor advertisement message to the second LLDP target device. The LLDP target device that receives the second neighbor advertisement and the suffix adds its own identification information and the interface information of the second neighbor advertisement message to the second neighbor advertisement message, and forwards the LLDP target device to the next hop. The second neighbor advertisement message may also carry the hop count information, and the LLDP target device that receives the second neighbor advertisement message may increase the hop count by one.

(3) The LLDP master device receives the first neighbor advertisement message and the second neighbor advertisement message according to the reception. The first neighbor advertisement and the second neighbor advertisement obtain the topology of the one or more LLDP target devices.

The first neighbor advertisement and the second neighbor advertisement received by the LLDP master device carry the device identifier TLV and the interface identifier TLV of the LLDP target device. The two ring directions of the entire ring network can be obtained from the device identifier TLV and the interface identifier TLV. The topological structure on it.

In order to enable the LLDP target device to identify the LLDP master device, the LLDP master device can also carry the proxy identifier in the sent neighbor advertisement packet, so that the LLDP target device can identify the LLDP master device that can communicate with the 0SS according to the proxy identifier.

After the LLDP master device obtains the topology of the two directions, the neighboring entry can be generated locally. The neighboring entry can include the neighboring device identification information, and the network topology information of the neighbor, such as the outbound interface. It may also include the neighbor's wake-up P version number and the wake-up P identifier. The neighbor table can also include the hop count of the LLDP master device to each LLDP target device.

If the LLDP target device connected to the LLDP device is configured as an acyclic network, the topology of the LLDP target device can be:

(1) The LLDP master device receives the neighbor advertisement packet, and the neighbor advertisement packet carries the device identifier.

The TLV and the interface identifier TLV. The LLDP master device identifies the LLDP target device at the end of the link from the device identification TLV and the interface identifier TLV, and obtains the LLDP target device identification information at the end of the link and the LLDP target from the end of the link. Network topology of the device to the LLDP master device;

(2) The LLDP master device sends a topology query request to the LLDP target device at the end of the link. The topology query request carries the TLV shown in Table 3. The LLDP target device that receives the topology query request can TLV recognition is a topology query request.

(3) After receiving the topology query request, the LLDP target device identifies the topology query request and adds its own identity information and the interface information received by the topology query request to the topology query request, and the next hop LLDP target device forwarding. The LLDP target device may add its own identification information and interface information received by the topology query request to the topology query request in the form of the device identification TLV and the interface identification TLV. The topology query request may carry the hop count information. After receiving the topology query request, the LLDP target device in the middle may reduce the hop count by one, and the LLDP target device that is 0 after the link may be the LLDP target device at the end of the link. Of course, the LLDP target device can also identify whether it is an LLDP target device of the link meter based on the identifier information of the LLDP target device in the topology query request.

(4) After receiving the topology query request, the LLDP target device at the end of the link encapsulates the topology information of other LLDP target devices carried in the topology query request by the link topology TLV (see Table 5). The information of the LLDP master device is forwarded to the LLDP master device. The identifier information of the LLDP master device can be carried in the response packet in the form of the target option TLV shown in Table 2. During the response packet forwarding process, other target devices continue. Add link topology information. In this way, the response packet received by the LLDP master device carries the topology structure from the LLDP master device to the LLDP target device at the end of the link and the topology structure from the LLDP target device at the end of the link to the LLDP master device. The LLDP master device can A bidirectional link topology between the LLDP master device and the LLDP target device to be configured is found in the response packet.

After obtaining the topology of the LLDP target device, the LLDP master device can also generate a neighbor entry locally. The neighbor entry can include the identifier information of the neighbor device and the network topology information of the neighbor, such as the outbound interface. It may also include the neighbor's wake-up P version number and the wake-up P identifier. The neighbor table can also include the hop count of the LLDP master device to each LLDP target device.

Step 520: The LLDP master device searches the mapping between the LLDP target device identification information and the LLDP target device forwarding information according to the LLDP target device identification information to obtain the forwarding information of the LLDP target device to be configured.

Specifically, the forwarding information obtained by the LLDP master device may be the outbound interface information of the LLDP target device to be configured on the LLDP master device. The process of obtaining the forwarding information is performed by the LLDP master device to query the neighbor table, and the LLDP target device is stored in the neighbor table. Identification information and forwarding information of the LLDP target device Correspondence.

After receiving the management request information carrying the LLDP target device identifier, the LLDP master device queries the LLDP master device neighbor table for the forwarding information corresponding to the LLDP target device identifier. The LLDP master neighbor table is shown in Table 8.

In addition, the LLDP master interface changes from open up to down, and the neighbor entry that passes the interface is deleted. When the status of a neighboring device changes, the LLDP target device encapsulates the neighbor information that is maintained by the LLDP device into an LLDP master device. The LLDP master device encapsulates the packet into an IP packet and reports it to the 0SS.

Step 53 G: The LLDP master device encapsulates the awake P-type packet into an LLDP packet, and forwards the LLDP packet to the LLDP target device to be configured according to the obtained forwarding information, so that the LLDP target device to be configured is configured by using the configuration information. .

The LLDP master device may encapsulate the S-uppertext into the LLDP file in the form of a TLV. Before the encapsulation, the LLDP master device may obtain the LLDP to be configured according to the identifier information of the LLDP target device to be configured. And the configuration information required by the LLDP target device to be configured is converted according to the SNMP version information.

The SNMP packet carries the configuration information. The LLDP target device to be configured can be configured according to the parameters and corresponding values in the configuration information.

Therefore, the device configuration method in the network provided by the embodiment of the present invention, the LLDP master device receives the management request information of the LLDP target device identifier that is sent by the WSS in the form of the wakeup P packet, and obtains the LLDP target device according to the LLDP target device identifier. Forwarding information, according to the forwarding information of the LLDP target device, the management request information is sent to the LLDP target device in the form of an LLDP >3⁄4 message, and the LLDP target device is encapsulated into the LLDP packet by using the wakeup P packet. After the management request response information is sent in the form, the management request response information is decapsulated into the wakeup P message and sent to the 0SS, so that the remote management of the LLDP target device by the 0SS can be realized without obtaining the IP address.

FIG. 6 is a flowchart of a device configuration method in a network according to an embodiment of the present invention. As shown in the figure, the embodiment of the present invention specifically includes: Step 610: The LLDP target device receives the management request information that is sent by the LLDP master device and is sent in the form of the LLDP target device, and is sent by the LLDP master device. The management request information includes query request information or configuration request information.

Step 620: When the LLDP target device identifier is the same as the LLDP target device identifier, the management request information is decapsulated into a wakeup P packet, and processing corresponding to the management request information is performed, thereby obtaining management request response information.

Further, the step 620 further includes: when the target device identifier is different from the LLDP target device identifier, querying, in the LLDP target device forwarding table, the forwarding information corresponding to the target device identifier in the packet; and inserting the device according to the forwarding information. After the TLV and the interface TLV, the S wake-up P over LLDP packet is forwarded to the LLDP target device or the LLDP master device.

Further, before the step 62 G, the LLDP target device actively sends the neighbor advertisement, so that the intermediate target device and the LLDP master device learn the neighbor entry. In addition to the standard capabilities defined by the LLDP protocol, the notification information includes the S-up P version number and the S-wake P flag.

The LLDP target device establishes the LLDP target device neighbor table. The neighbor forwarding table results are shown in Table 9. When the LLDP target device receives the LLDP packet sent by the neighbor, it learns or refreshes the neighbor entry. In addition to the neighbor identifier, the LLDP learns the hop count of the neighbor, the receiving interface, and the proxy priority of the neighbor. The interface is usually The outbound interface of the packet is forwarded, and the priority is used to identify whether the neighbor has the agent management capability and the priority of the agent management. In general, the LLDP master device is capable of proxy management. When the network size is large or the reliability requirements are high, two or more LLDP master devices can be configured. Different LLDP master devices should be indicated by Proxy. The priority of agent management.

When the LLDP target device interface is changed from open up to down, the neighbor entries learned by the interface are deleted, including direct neighbors and indirect neighbors. When the neighboring state changes, the LLDP target device encapsulates the neighbor information that is maintained by the LLDP device into an LLDP master device, and the LLDP master device encapsulates the packet into an IP packet and reports it to the 0SS.

In step 630, the management request response information is encapsulated into an LLDP packet by using the wakeup P packet. The LLDP master device is sent to the LLDP master device to forward the management request response information to the operation support system 0SS through the wakeup P.

Further, the step 630 further includes: when using the S-up P over LLDP to send the response to the LLDP master device, using the target device TLV to specify the LLDP master device, where the LLDP master device can be identified according to the source MAC in the management request message. The proxy priority of the LLDP master device is not considered. Before forwarding the packet, the LLDP target device also needs to learn the forwarding information to the LLDP master device. The forwarding information can be learned or refreshed when receiving the S-up P L LLDP management request.

Therefore, the device configuration method in the network provided by the embodiment of the present invention, the LLDP target device receives the management request information that the LLDP master device carries the LLDP target device identifier and is sent in the form of the LLDP 艮封装封装When the target device identifier in the file is the same as the LLDP target device identifier, the management request information is decapsulated into an SNMP message, and processing corresponding to the management request information is performed, thereby obtaining management request response information, and the management request is obtained. The response information is sent to the LLDP master device through the S-up packet, and is sent to the LLDP master device. The LLDP master device forwards the management request response message to the operation support system 0SS through the wake-up P packet, so that the IP address does not need to be obtained. It can also realize remote management of LLDP target devices by 0SS.

FIG. 7 is an information interaction diagram of a device configuration method in a network according to an embodiment of the present invention. As shown in the figure, the embodiment of the present invention specifically includes:

Step 701: The 0SS sends the management request information carrying the LLDP target device identifier to the LLDP master device through the S-up P4 message. The management request information includes query request information or configuration request information.

Step 702: After receiving the management request information carrying the LLDP target device identifier, the LLDP master device determines the target device to be configured. If the target setting is consistent with the LLDP master device, the configuration or the query request is directly processed; if the other LLDP target device is configured as a proxy, the neighbor table is queried, and step 703 is performed.

Step 703: The LLDP master device completes the wakeup P version and the identifier conversion according to the wakeup P version and the S wakeup P identifier that are queried in the neighbor table, and adds the LLDP encapsulation, and the target device TLV is used in the encapsulation. Specifies the target device to be configured, and uses the wake-up P TLV to encapsulate the original S-P-P message. The packet does not contain IP and UDP headers.

Step 704: After receiving the awake P over LLDP packet sent by the LLDP master device, the LLDP target device 1 learns or refreshes the neighbor entry, and compares the LLDP target device identifier carried in the packet with the device identifier of the device. If the target device identifier is the same as the LLDP target device 1 identifier, step 707 is performed. If the target device identifier in the packet is different from the LLDP target device 1 identifier, step 705 is performed.

Step 705: The LLDP target device 1 queries the neighbor table and forwards the management configuration request according to the outbound interface in the neighbor table. Before the forwarding, the TLV and the interface TLV that receives the packet are inserted to learn or refresh the neighbor entry.

Step 706: After receiving the management configuration request packet forwarded by the LLDP target device 1, the LLDP target device 2 learns or refreshes the neighbor entry, and compares the target device identifier carried by the device query packet with its own device identifier. When the target device identifier is the same as the LLDP target device 1 identifier, step 707 is performed; when the target device identifier is different from the LLDP target device 1 identifier, the neighbor entry is queried and forwarded to the next hop LLDP target according to the outbound interface in the neighbor entry. The device inserts the device TLV and the interface TLV that receives the packet before forwarding.

Step 707: The LLDP target device 2 decapsulates the management request information into a wakeup P message, and performs processing corresponding to the management request information, thereby obtaining management request response information. Then step 708 is performed.

Step 708: The LLDP target device 2 encapsulates the management request response information in the form of a wake-up P-over LLDP packet, and encapsulates the wake-up P-request and the 艮-text with the wake-up P TLV, and sends the information to the LLDP master device through the target device TLV. The neighbor table is queried before being sent from the outbound interface in the neighbor table.

Step 709: After receiving the management request response information of the P-over LLDP encapsulation, the LLDP target device 1 learns or refreshes the neighbor table, and queries the neighbor table through the target device TLV to obtain an interface. Then step 710 is performed.

Step 710: The LLDP target device 1 forwards the LLDP packet according to the outbound interface queried by the neighbor table. The device TLV and the interface TLV that receives the message are inserted before forwarding.

Step 711: After the management request response information received by the LLDP master device, the target device TLV identifies that the message should be processed, and the original S wakeup P message is taken out from the wakeup P TLV, and the wakeup P format and the identifier are completed. After the conversion, the standard S is awake to the operation support system 0SS, that is, step 712, and the standard S is awake.

Therefore, the device configuration method in the network provided by the embodiment of the present invention, the LLDP master device receives the management request information of the LLDP target device identifier that is sent by the SSS in the form of the wake-up P packet, and obtains the LLDP according to the target device identifier in the packet. Forwarding information of the target device, and forwarding the management request information to the LLDP target device 1 or the LLDP target device 2 according to the forwarding information, and the LLDP target device 1 or the LLDP target device 1 receives the management request information, and the target device identifier in the packet When the LLDP target device identifier is the same, the management request information is decapsulated into a wakeup P packet, and processing corresponding to the management request information is performed, thereby obtaining management request response information, and the management request response information is awake through P^. The encapsulation is sent to the LLDP master device in the form of an LLDP packet, and the LLDP master device receives the management request response information sent by the LLDP target device 1 or the LLDP target device 2 in the form of an LLDP packet. Decapsulating the management request response information into a wakeup P message, and converting the wakeup P version and After identifying the standard S P wake packet format is transmitted to 0SS, eliminating the need to obtain an IP address can be realized 0SS LLDP remote management target device.

FIG. 8 is a schematic structural diagram of a link layer discovery protocol LLDP device according to an embodiment of the present invention. The LLDP device is used to perform the device configuration method in the networks provided in Figures 3 through 7. As shown in the figure, the embodiment of the present invention specifically includes: a first interface 81, a second interface 82, a data receiver 83, a processor 84, and a data transmitter 85.

The first interface 81 is used to connect the operational support system 0SS;

The second interface 82 is configured to connect to one or more LLDP target devices.

The data receiver 83 is configured to receive the IP packet of the 0SS, and extract the simple network management protocol, the awake P packet, from the IP packet, and the awake P packet carries the identifier information of the LLDP target device to be configured and the LLDP to be configured. Configuration information required by the target device; The processor 84 is configured to query the correspondence between the identifier information of the LLDP target device and the forwarding information of the LLDP target device according to the identifier information of the LLDP target device to be configured, so as to obtain the forwarding information of the LLDP target device to be configured; The packet is encapsulated into an LLDP packet.

The data transmitter 85 is configured to send the LLDP packet to the LLDP target device to be configured according to the obtained forwarding information, so that the LLDP target device uses the configuration information to configure.

In one embodiment, the processor 84 is further configured to acquire a topology of one or more LLDP target devices; the data transmitter is further configured to report the acquired topology to the 0SS.

In another embodiment, the one or more LLDP target devices and the LLDP master device form a ring network structure, and the data transmitter 85 is further configured to send a neighbor advertisement message to one or more LLDP target devices, so that the neighbor is received. The LLDP target device of the advertisement packet adds its own identification information and the interface information of the received neighbor advertisement message to the next hop LLDP target device in the neighbor advertisement message. The data receiver 83 is also used to receive the neighbor advertisement report. The processor 84 is further configured to obtain a topology of one or more LLDP target devices from the received neighbor advertisement message.

Therefore, the LLDP device provided by the embodiment of the present invention receives the management request information of the LLDP target device identifier that is sent by the SSS in the form of the wakeup P packet, and obtains the forwarding information of the LLDP target device according to the LLDP target device identifier, according to the LLDP target device. The forwarding information is sent to the LLDP target device in the form of the LLDP packet, and is sent to the LLDP target device through the S-up packet, and the management request response is sent in the form of the LLDP packet. After the information is obtained, the management request response information is decapsulated into a wakeup P message and sent to the 0SS, so that the remote management of the LLDP target device by the 0SS can be realized without obtaining the IP address.

FIG. 9 is a schematic structural diagram of a device configuration system according to an embodiment of the present invention. As shown, the device configures the system link layer discovery protocol LLDP master device 91 and one or more LLDP target devices 92, and one or more LLDP target devices 92 connect to the 0SS through the LLDP master device 91.

The LLDP master device 91 is configured to receive an IP packet of the OSS of the operation support system, and extract a simple network management protocol, the awake P packet, from the IP packet, and the S-wrap packet carries the identifier information of the LLDP target device to be configured and Configuration information required for the LLDP target device to be configured; according to the LLDP to be configured The identifier information of the target device is used to query the mapping between the LLDP target device and the forwarding information of the LLDP target device, so as to obtain the forwarding information of the LLDP target device to be configured, and encapsulate the W ping P-packet into the LLDP packet. The forwarding information is sent to the LLDP target device to be configured, so that the LLDP target device uses the configuration information for configuration.

In an embodiment, the LLDP master device 91 is further configured to acquire the topology of the one or more LLDP target devices, and report the acquired topology to the oss.

In another embodiment, the one or more LLDP target devices 92 and the LLDP master device 91 form a ring network structure, and the LLDP master device 91 is specifically configured to send neighbor advertisement packets to one or more LLDP target devices; The packet obtains the topology of one or more LLDP target devices from the received neighbor advertisement message. The LLDP target device is configured to receive the neighbor advertisement message, and set its own identity information and the interface that receives the neighbor advertisement message. The information is added to the neighbor advertisement packet and sent to the next hop LLDP target device. A person skilled in the art should further appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both, in order to clearly illustrate hardware and software. Interchangeability, the composition and steps of the various examples have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

The steps of a method or algorithm described in connection with the embodiments disclosed herein can be implemented in hardware, a software module executed by a processor, or a combination of both. Software modules can be placed in random access memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or technical field Any other form of storage medium known.

The specific embodiments described above carry out the objects, technical solutions and beneficial effects of the present invention. It is to be understood that the foregoing description is only illustrative of the embodiments of the invention, and is not intended to limit the scope of the invention And equivalent replacements, improvements, etc., are all included in the scope of the present invention.

Claims

1. A device configuration method in a network. The network includes an operation support system OSS, a link layer discovery protocol LLDP master device, and one or more LLDP target devices. The one or more LLDP target devices pass the LLDP The main device connects to the OSS, and the methods include:

The LLDP master device receives the IP message of the OSS and extracts the Simple Network Management Protocol Wake-up message from the IP message. The Wake-up message carries the identification information of the LLDP target device to be configured. and the configuration information required by the LLDP target device to be configured;

The LLDP master device queries the corresponding relationship between the identification information of the LLDP target device and the forwarding information of the LLDP target device according to the identification information of the LLDP target device to be configured, thereby obtaining the forwarding information of the LLDP target device to be configured;

The LLDP master device encapsulates the SNMP message into an LLDP message, and sends the LLDP message to the LLDP target device to be configured according to the obtained forwarding information, so that the LLDP target device uses all Configure the configuration information described above.

2. The device configuration method in the network according to claim 1, wherein the obtained forwarding information includes an outbound interface on the LLDP master device connected to the LLDP target device to be configured.

3. The device configuration method in the network according to claim 1, characterized in that the LLDP master device encapsulates the Wakeup message into an LLDP message, which specifically includes:

The LLDP master device encapsulates the SNMP message into the

in LLDP packets.

4. The device configuration method in the network according to claim 3, wherein the LLDP message also carries a TLV used to identify the LLDP target device to be configured, and the TLV is used to identify the LLDP target device to be configured. The TLV of the target device carries identification information of the LLDP target device to be configured.

5. The device configuration method in the network according to claim 1, characterized in that before the LLDP master device receives the IP message of the OSS, it further includes: Obtain the topology structure of the one or more LLDP target devices, and report the obtained topology structure to the OSS.

6. The device configuration method in the network according to claim 5, wherein the one or more LLDP target devices and the LLDP master device form a ring network structure, then the one or more LLDP targets are obtained The topology structure of the device specifically includes:

The LLDP master device sends a neighbor advertisement message to the one or more LLDP target devices, so that the LLDP target device that receives the neighbor advertisement message adds its own identification information and the interface information that received the neighbor advertisement message to The neighbor advertisement message is sent to the next-hop LLDP target device; the LLDP master device receives the neighbor advertisement message, and obtains the topology structure of the one or more LLDP target devices from the received neighbor advertisement message.

7. The device configuration method in the network according to claim 6, wherein the LLDP master device is connected to a first LLDP target device on one side and a second LLDP target device on the other side. The device sends a neighbor advertisement message to the one or more LLDP target devices, which specifically includes:

The LLDP master device sends a first neighbor advertisement message to the first LLDP target device, so that the LLDP target device that receives the first neighbor advertisement message sends its own identification information and the first neighbor advertisement report to the first neighbor advertisement message. The interface information of the message is added to the first neighbor advertisement message and forwarded to the next-hop LLDP target device;

The LLDP master device sends a second neighbor advertisement message to the second LLDP target device, so that the LLDP target device that receives the second neighbor advertisement message combines its own identification information with the received second neighbor advertisement message. The interface information is added to the second neighbor advertisement message and forwarded to the next-hop LLDP target device;

The LLDP master device receives the first neighbor advertisement message and the second neighbor advertisement message, and obtains the topology structure of the one or more LLDP target devices according to the received first neighbor advertisement message and the second neighbor advertisement message. .

8. The device configuration method in the network according to claim 7, characterized in that: the first A neighbor advertisement message and the second neighbor advertisement message also carry a proxy Proxy identifier, so that the LLDP target device that receives the first neighbor advertisement message or the second neighbor advertisement message learns the Identification information of the LLDP master device.

9. The device configuration method in the network according to claim 5, wherein the one or more LLDP target devices and the LLDP master device form a non-ring network structure, then the one or more LLDP devices are obtained. The topology structure of the target device specifically includes:

The LLDP master device receives the neighbor advertisement message of the LLDP target device, and obtains the identification information of the LLDP target device at the end of the link and the topology to reach the LLDP target device at the end of the link from the neighbor advertisement message. information;

The LLDP master device sends a topology query request to the LLDP target device at the link end according to the topology information of the LLDP target device arriving at the link end, so that the LLDP target device receiving the topology query request will Its own identification information and the interface information that received the topology query request are added to the topology query request, and forwarded to the next-hop LLDP target device;

Receive a response message for the topology query request from the LLDP target device at the end of the link. The response message carries the topology structure from the LLDP master device to the LLDP target device at the end of the link and the slave The topology structure from the LLDP target device at the end of the link to the LLDP master device;

The LLDP master device carries the topology structure from the LLDP master device to the LLDP target device at the link end, and from the LLDP target device at the link end to the LLDP The complete link topology is calculated from the master's topology.

10. The device configuration method in the network according to claim 9, characterized in that the topology query request also carries a Proxy identifier, so that the LLDP target device receiving the topology query request learns the LLDP Identification information of the main device.

11. The device configuration method in the network according to any one of claims 1-10, characterized in that, before the LLDP master device encapsulates the wake-up message into an LLDP message, the method further include: The LLDP master device is also configured to obtain the Spark version information that can be recognized by the LLDP target device to be configured according to the identification information of the LLDP target device to be configured, and configure the Spark version information according to the Spark version information. Convert the configuration information required by the LLDP target device to be configured.

12. A link layer discovery protocol LLDP device, characterized in that the device includes: a first interface used to connect to the operation support system OSS;

The second interface is used to connect one or more LLDP target devices;

A data receiver, configured to receive the IP message of the OSS, and extract the Simple Network Management Protocol Wake-up message from the IP message. The Wake-up message carries the identification of the LLDP target device to be configured. information and the configuration information required by the LLDP target device to be configured;

A processor configured to query the corresponding relationship between the identification information of the LLDP target device and the forwarding information of the LLDP target device based on the identification information of the LLDP target device to be configured, thereby obtaining the forwarding information of the LLDP target device to be configured; and encapsulating the STEP message into an LLDP message; a data sender, configured to send the LLDP message to the LLDP target device to be configured according to the obtained forwarding information, so that the The LLDP target device uses the configuration information to perform configuration.

13. The LLDP device according to claim 12, characterized in that,

The processor is also used to obtain the topology structure of the one or more LLDP target devices; the data sender is also used to report the obtained topology structure to the OSS.

14. The LLDP device according to claim 13, wherein the one or more LLDP target devices and the LLDP master device form a ring network structure, then

The data sender is also configured to send a neighbor advertisement message to the one or more LLDP target devices, so that the LLDP target device that receives the neighbor advertisement message sends its own identification information and the name of the neighbor advertisement message that it received. The interface information is added to the neighbor advertisement message and sent to the next-hop LLDP target device;

The data receiver is also used to receive neighbor advertisement messages;

The processor is also configured to obtain the one or more LLDP messages from the received neighbor advertisement. The topology of the target device.

15. A device configuration system, characterized in that the system includes a link layer discovery protocol LLDP master device and one or more LLDP target devices, and the one or more LLDP target devices are connected to all the devices through the LLDP master device. Said0SS,

The LLDP master device is used to receive IP packets from the operation support system OSS, and extract Simple Network Management Protocol Wake-up messages from the IP packets. The Wake-up packets carry LLDP targets to be configured. The identification information of the device and the configuration information required by the LLDP target device to be configured; Query the corresponding relationship between the identification information of the LLDP target device and the forwarding information of the LLDP target device according to the identification information of the LLDP target device to be configured, thereby Obtain the forwarding information of the LLDP target device to be configured; and encapsulate the Wake-up message into an LLDP message, and send the LLDP message to the LLDP target to be configured according to the obtained forwarding information. device, so that the LLDP target device uses the configuration information to configure.

16. The device configuration system according to claim 15, characterized in that, the LLDP master device is also used to obtain the topology structure of the one or more LLDP target devices, and report the obtained topology structure to the 0SS.

17. The device configuration system according to claim 16, wherein the one or more LLDP target devices and the LLDP master device form a ring network structure, then

The LLDP master device is specifically configured to: send a neighbor advertisement message to the one or more LLDP target devices; receive the neighbor advertisement message, and obtain the information of the one or more LLDP target devices from the received neighbor advertisement message. topological structure;

The LLDP target device is configured to receive the neighbor advertisement message, add its own identification information and the interface information that received the neighbor advertisement message to the neighbor advertisement message and send it to the next hop LLDP target device.