WO2012106935A1

WO2012106935A1 - Data communication network configuration method, gateway element and data communication system

Info

Publication number: WO2012106935A1
Application number: PCT/CN2011/077665
Authority: WO
Inventors: 李洪广
Original assignee: 华为技术有限公司
Priority date: 2011-07-27
Filing date: 2011-07-27
Publication date: 2012-08-16
Also published as: CN102308523B; CN102308523A

Abstract

Disclosed in the embodiments of the invention are a data communication network (DCN) configuration method, gateway element and data communication system. The gateway element sends the non-gateway element in a management domain a broadcast message carrying the IP address of a network management server; the gateway element obtains the element identifier register information, which is transmitted by the non-gateway element after the non-gateway element receives the broadcast message; the gateway element allocates for the non-gateway element a public network IP address and a private network IP address which is used for device management, generates and stores a network address translation (NAT) mapping table; the gateway element registers the NAT mapping table on the network management server; the gateway element enables the message exchange between the non-gateway element and network management server according to the NAT mapping table. When the message interaction is performed between the network management server and the non-gateway element, the gateway element only needs to perform NAT on the message, which therefore lightens the burden of the Central Processing Unit (CPU) of the gateway element, effectively increases the number of the elements in the management domain and improves the efficiency of forwarding the message in the management domain.

Description

Data communication network configuration method, gateway network element and data communication system

The present invention relates to the field of communication technologies, and more particularly to a data communication network configuration method, a gateway network element, and a data communication system. Background technique

The backhaul bearer between the mobile base station and the wireless core device is carried by the fixed network device. In order to realize remote deployment of wireless backhaul, the prior art adopts a Data Communication Network (DCN) system to provide network devices with communication functions for managing access and managing control information, so that each network management server center can complete each Remote deployment and management of devices.

A DCN system network is composed of a network management server, a gateway network element and a non-gateway network element and a connection line or network between them; wherein the network management server and the gateway network element are connected and directly accessible to each other; the gateway network element A plurality of non-gateway network elements directly or indirectly connected to each other form an administrative domain, and the gateway network element and the plurality of non-gateway network elements in the management domain can directly access each other.

On the physical link that directly interconnects devices in the DCN management domain, the PPP protocol is used to establish a point-to-point logical link channel, and the private network IP addresses of the same network segment are allocated on the directly connected ports, and then The point link channel obtains the routing information of the management plane through the routing protocol, and the routing information is a host route formed by the PPP link and the private network address allocated in the PPP process. The routing information between the gateway NE and the non-gateway NE in the DCN management domain is used to implement DCN packet transmission.

In the prior art, the specific workflow of the DCN system includes:

In the downlink direction, when the network management server sends an IP packet to the network element in the management domain, the IP packet includes the destination IP address. Because the network management server only directly contacts the gateway network element in the management domain, these purposes are The IP address is the IP address of the gateway NE. After receiving the IP packet, the gateway NE needs to determine the NE ID in the IP packet. If the NE ID in the IP packet is the NE ID of the gateway NE, the IP packet is forwarded to the upper layer. The protocol/application continues to process. If the network element ID in the IP packet is not the network element ID of the gateway network element, the IP address of the destination network element is converted according to the network element ID, and then forwarded through the management plane route. , the destination network element is a non-gateway network element; the non-gateway network After receiving the IP address, the device determines whether the IP address of the destination network element is the IP address of the network element. If yes, the non-gateway network element delivers the IP packet to the upper layer for further processing. If not, the management plane is based on the management plane. The routing information forwards the IP packet.

In the uplink direction, when the non-gateway network element in the management domain sends an IP packet to the network management server, the IP packet is sent to the gateway network element according to the routing information of the management plane, and the gateway network element is configured according to the non-gateway network element. The IP address information is obtained by the network element ID of the non-gateway network element, and the gateway network element adds the network element ID to the IP address information of the gateway network element, and finally adds the IP address information of the non-gateway network element to the IP address information of the gateway network element. The gateway network element sends an IP packet including the network element ID of the non-gateway network element and the IP address information of the gateway network element to the network management server.

The inventor has found that at least the following defects exist in the prior art: Since all management messages must be analyzed by the application layer through the gateway network element, the CPU load of the gateway network element is too large, so the network element of the management domain is The number of packets is limited. The forwarding of IP packets in the management domain is not efficient. Summary of the invention

In view of this, the embodiment of the present invention provides a DCN configuration method, a gateway network element, and a data communication network DCN to reduce the CPU load of the gateway network element.

An embodiment of the present invention provides a data communication network DCN configuration method, including: sending a broadcast packet carrying an IP address of a network management server to a non-gateway network element in a management domain in which it is located;

Acquiring the network element identifier registration information that is sent by the non-gateway network element after receiving the broadcast packet, where the network element identifier registration information includes the network element identifier of the non-gateway network element;

Allocating a non-gateway network element including a public network IP address and a private network IP address for device management, generating and storing a network identifier including the non-gateway network element, a public network IP address, and a private device for device management NAT mapping table of the network IP address;

Registering the NAT mapping table with the network management server.

Another aspect of the embodiment provides a gateway network element, including:

a transmitter, configured to send, to the non-gateway network element in the management domain to which the gateway network element belongs, a broadcast packet carrying an IP address of the network management server;

The acquiring unit is configured to obtain the network element identifier registration information that is sent by the non-gateway network element after the broadcast message is received, where the network element identifier registration information includes the network element identifier of the non-gateway network element; a generating unit, configured to allocate a public network IP address and a private network IP address for device management, and generate a network element identifier including the non-gateway network element, a public network IP address, and a device management NAT mapping table of the private network IP address;

a memory, configured to store a NAT mapping table generated by the generating unit;

And a registration unit, configured to register, by the network management server, the NAT mapping table generated by the generating unit. A further aspect of the present invention provides a data communication system, including a network management server, the foregoing gateway network element, and at least one non-gateway network element; the gateway network element and the at least one non-gateway network element belong to the same An administrative domain, the at least one non-gateway network element communicating with the network management server by the gateway network element.

According to the foregoing technical solution, in the embodiment, when receiving the network element identifier registration information sent by the non-gateway network element, the non-gateway network element is allocated a public network IP address and a private network for device management. The IP address is generated and stored in the NAT mapping table, and then the gateway network element registers the NAT mapping table in the network management server, so that when the network management server interacts with the non-gateway network element, the gateway network element only needs to be The packet can be NAT-transformed, so the load of the gateway network element CPU is reduced, so that the gateway network element is no longer the performance bottleneck of the entire DCN, effectively increasing the number of network elements in the management domain, and improving management. Forwarding efficiency of packets in the domain. DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any inventive labor.

1 is a schematic diagram of steps of a DCN configuration method according to an embodiment of the present invention;

2 is a schematic structural diagram of a NAT mapping table according to an embodiment of the present invention;

FIG. 3 is a schematic structural diagram of a data communication system according to an embodiment of the present invention. detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, one of ordinary skill in the art does not create All other embodiments obtained under the premise of sexual labor are within the scope of protection of the present invention. The inventor has found through research that in the prior art, the CPU load of the gateway network element is too large because the gateway network element needs to function as an application layer gateway for managing maintenance messages, that is, the gateway network element receives management and maintenance^ After the essay, the load part of the suffix must be parsed, the network element identifier is identified, and then the packet is encapsulated. In this manner, all management and maintenance messages must be sent to the CPU of the gateway network element for processing. The CPU of the gateway network element needs to process the management and maintenance packets sent by the non-gateway NEs in the management domain. The CPU of the gateway network element increases the load, which makes the gateway network element become the performance bottleneck of the entire DCN, resulting in the management domain. The number of NEs is limited, and the forwarding efficiency of packets in the management domain is not high.

Based on the above research, in order to solve the problem that the number of network elements in the management domain is limited in the prior art, and the forwarding efficiency of the packets in the management domain is not high, this embodiment provides a DCN configuration method, as shown in FIG. 1 . As shown, including the steps:

S11. The gateway network element sends a broadcast packet carrying the IP address of the network management server to the non-gateway network element in the management domain. The broadcast packet is used to enable the non-gateway network element in the management domain to register the network element identifier with the gateway network element.

In this embodiment, in the same management domain, the public network IP address of the gateway network element is first configured, the address of the network management server, and the routing path of the gateway network element to the network management server are obtained.

Then, a PPP connection is established between any two directly connected NEs in the management domain, and then each NE initiates an IGP routing protocol.

Then, the gateway network element sends a broadcast packet to all non-gateway network elements in the management domain, and broadcasts the IP address information of the packet packet network management server. If the IP address information of the gateway NE is not configured in the non-gateway NE, the broadcast text should also include the IP address information of the gateway NE.

Specifically, the gateway network element sends a broadcast packet to all the non-gateway network elements directly connected to the gateway through the PPP link; after receiving the broadcast packet, the non-gateway network element directly connected to the gateway network element sends the broadcast packet to the other The directly connected non-gateway network element forwards the broadcast message. And so on, until the broadcast arrives at all non-gateway network elements in the entire management domain.

The gateway network element can send the broadcast packet, so that the non-gateway network element in the management domain can obtain the IP address information of the gateway network element and the IP address information of the network management server, and then the non-gateway network element can implement the gateway network element or the network. Manage data transfer between servers.

Specifically, in this embodiment, the broadcast and the text can be sent through a newly defined protocol. The broadcast message can also be sent by extending the standard protocol, for example, by extending the routing protocol. Send the broadcast message.

The information carried in the broadcast packet includes an IP address of the network management server, and may also include an IP address of the gateway network element, and a virtual local area network (VLAN) to which the gateway network element belongs. Logo.

S12. Obtain the network element identification registration information that is sent by the non-gateway network element in the management domain after receiving the broadcast>3⁄4 text, and the network element identifier registration information includes the network element identifier of the non-gateway network element. Optionally, the network element identifier registration information may further include a management protocol supported by the non-gateway network element (hereinafter referred to as a communication protocol) and a port for the non-gateway network element to send the network element identifier registration information (hereinafter referred to as the first port).

The communication protocol can be an IP based management protocol such as SNMP, NETCONF or HTTP. Non-gateway network elements in the same management domain use the same communication protocol.

In order to enable the gateway network element to directly forward the management and maintenance messages between the non-gateway network element and the network management server, the non-gateway network element needs to send its own network element identification information to the gateway network element.

In an actual application, the network element identifier may be a character, a string, a digit, a digit string, or a numeric string stored in the device memory when the non-gateway network element device is shipped from the factory. Preferably, when the network element identifier is a numeric string, Specifically, it may be the MAC address of the non-gateway network element device.

S13. The non-gateway network element that sends the network element identifier registration information is assigned a public network IP address and a private network IP address used for device management, and generates and stores a network element identifier including the non-gateway network element, and a public network IP address. And a NAT mapping table for the private network IP address used for device management. When the network element identification information includes a communication protocol and/or a first port, the NAT mapping table may further include the communication protocol and/or the first port.

After the gateway network element receives the registration information of the network element identifier sent by the non-gateway network element, in order to enable the non-gateway network element to communicate with the network management server outside the management domain, the gateway network element first needs to assign a public network IP address to the non-gateway network element. And a private network IP address used for device management, and then, a public network address including a non-gateway network element, a private network IP address, and a NAT mapping table of the network element identifier are generated.

In an actual application, the NAT mapping table may further include a port number (hereinafter referred to as a second port number) of a port on which the gateway network element receives the network element registration information sent by the non-gateway network element.

Specifically, the configuration of the NAT mapping table may refer to FIG. 2. FIG. 2 shows a NAT mapping table composed of related information of four non-gateway network elements, and the network element identifiers of the four non-gateway network elements are NE10 and NE11, respectively. NE20, NE21; The network element identifier of each non-gateway network element also corresponds to the private network of the non-gateway network element. Network IP address / first port, IP address of the public network / second port and communication protocol.

S14. The gateway network element registers a NAT mapping table with the network management server.

After establishing the NAT mapping table of the non-gateway network element, the public network IP address, and the private network IP address, the gateway network element registers the NAT mapping table with the network management server.

After the configuration process is complete, the network management server may send a management and maintenance message of the non-gateway network element to the gateway network element according to the NAT mapping table, and the gateway network element sends the management and maintenance message to the non-gateway network element according to the NAT mapping table.

Specifically, after obtaining the NAT mapping table, the network management server may obtain the public network IP address or IP address of the non-gateway network element and the first port, so that the non-gateway network element and the network management server pass the IP-based management. When a protocol communication protocol, such as SNMP or HTTP protocol, performs packet exchange, if the gateway network element receives a packet whose destination address is a public network IP address of a non-gateway network element, the gateway network element stores the packet according to the storage in the memory. The NAT mapping table is configured to modify the destination IP address of the packet to be the private network IP address allocated by the non-gateway network element for device management, and send the modified packet to the non-gateway network element; or, the gateway network element When receiving the packet whose non-gateway network element is the private network IP address of the non-gateway network element for the device management and the destination address is the IP address of the network management server, according to the NAT mapping table stored in the memory The source IP address of the packet is modified to be the public IP address of the non-gateway network element, and the modified packet is sent to the network management server.

When the communication protocol is included in the network element registration information, the network management server encapsulates the message sent to the non-gateway network element according to a protocol supported by the non-gateway network element.

When the network element identifier registration information includes the first port, the destination address of the network management server sent to the non-gateway network element is the public network IP address of the non-gateway network element, and the destination port is the first port, and the gateway is the gateway. The network element modifies the destination address of the packet to the private network for device management of the non-gateway network element.

After the IP address, the modified packet is sent to the first port.

In this embodiment, the gateway network element first allocates a public network address and a private network IP address for management to the non-gateway network element, and then uses the network element identification information of the non-gateway network element to manage the private network IP. The NAT information mapping table is established between the address information and the public network address information, and then the gateway network element registers the NAT mapping table in the network management server, so that when the network management server exchanges packets with the non-gateway network element, the gateway network element only The NAT of the packet needs to be converted, so that the load of the gateway network element CPU is reduced, so that the gateway network element is no longer the performance bottleneck of the entire DCN, and the number of network elements in the management domain can be increased, and the management domain is improved. The forwarding efficiency of the medium message. As a result of the network management policy, the management plane needs to be restricted to a certain VLAN. Therefore, in this embodiment, the broadcast VLAN identifier may also include the management VLAN identifier. Specifically, if a broadcast packet carries a management The VLAN is identified. The non-gateway NE that receives the broadcast packet re-establishes a PPP connection according to the management VLAN, and performs route refresh according to the newly established PPP connection. In this embodiment, the default VLAN is replaced by the method of actively broadcasting the management VLAN. Therefore, the scenario can be used to reduce the flexibility of the system.

In addition, this embodiment further provides a data communication network for implementing the foregoing method of the present invention. Therefore, where the description of the embodiment is not exhaustive, reference may be made to the description of the method embodiment. As shown in FIG. 3, the data communication network includes a gateway network element, at least one non-gateway network element (three are shown in the figure), and a network management server, and the gateway network element and the at least one non-gateway network element belong to The same management domain, the at least one non-gateway network element communicates with the network management server by the gateway network element. The gateway network element includes: a transmitter 1, an obtaining unit 2, a generating unit 3, a memory 4, and a registration unit 5.

In this embodiment, a PPP connection is established on all directly connected physical links in the management domain to which the gateway network element belongs, and after each network element starts the IGP routing protocol, the sender 1 sends the management domain to which the gateway network element belongs. The non-gateway network element sends a broadcast message carrying the IP address of the network management server.

Specifically, the transmitter 1 sends the broadcast packet to all non-gateway network elements directly connected to the gateway network element in the management domain to which the gateway network element belongs.

The broadcast message includes the IP address of the network management server. Optionally, the broadcast message may further include an IP address of the gateway network element. In this way, the broadcast network message is sent by the gateway network element, so that the non-gateway network element in the management domain can obtain the IP address of the gateway network element and the IP address of the network management server, thereby implementing communication with the gateway network element or the network management server. .

Specifically, in this embodiment, the broadcast may be sent through a newly defined protocol. The broadcast message may also be sent by extending the standard protocol. For example, the broadcast message may be sent by using an extended routing protocol.

In order to enable the packet to be forwarded between the non-gateway network element and the network management server through the gateway network element, the non-gateway network element needs to send its own network element identification information to the gateway network element.

The obtaining unit 2 obtains the network element identifier registration information that is sent by the non-gateway network element after receiving the broadcast message, and the network element identifier registration information includes the network element identifier of the non-gateway network element, and the network element identifier registration letter The information may further include a communication protocol and a first port that the non-gateway network element communicates with the network management server.

The generating unit 3 is configured to allocate a public network IP address and a private network IP address for device management, and generate a network element identifier including the non-gateway network element, and a public network IP address, for the non-gateway network element that sends the network element identification information. And a NAT mapping table for the private network IP address used for device management. Optionally, the NAT mapping table may further include a communication protocol and/or a first port.

After the gateway network element receives the registration information of the network element identifier from the non-gateway network element, in order to enable the non-gateway network element to communicate with the network management server outside the management domain, the gateway network element first needs to assign a public network IP address to the non-gateway network element. And the private network IP address used for device management. Next, a NAT mapping table including a public network IP address of the non-gateway network element, a private network IP address for device management, and a network element identifier is established.

In an actual application, the NAT mapping table may further include a port number (ie, a second port number) of the port on which the gateway network element receives the network element registration information sent by the non-gateway network element.

The network element identifier registration information may be a character, a string, a digit, a digit string, or a numeric string stored in the device memory when the non-gateway network element device is shipped from the factory. Preferably, when the network element identifier registration information is a numeric string, the specific It may be the MAC address of the non-gateway network element device. The network element registration information may also be the IP address of the non-gateway network element, or the IP address plus the port number of the communication protocol; wherein the IP address of the non-gateway network element may be the private address of the non-gateway network element in the management domain. The IP address of the network. Specifically, the IP address of the private network can be generated when a PPP connection is established.

The memory 4 is configured to store a NAT mapping table generated by the generating unit.

The registration unit 5 is configured to register a NAT mapping table generated by the generating unit with the network management server. After the gateway network element establishes a NAT mapping table including the network element identifier of the non-gateway network element, the public network IP address, and the private network IP address allocated for the non-gateway network element, the network element registers the NAT with the network management server. The mapping table; in this way, after the network management server obtains the NAT mapping table, the network management server sends the IP packet header of the management maintenance message to the non-gateway network element, and the destination address is the public network IP address of the non-gateway network element. . After receiving the message, the gateway network element performs NAT translation, and replaces the public network IP address of the non-gateway network element in the IP header with the private network IP address used for non-gateway network element management, and then performs normal operation in the management domain. IP routing forwarding process.

In addition, the gateway network element may further include a NAT converting unit 6 configured to: when receiving the packet sent by the network management server to the non-gateway network element, according to the NAT mapping table stored in the memory, the destination IP address of the packet Modify to become the private network IP address for device management assigned by the non-gateway network element. Transmitting the modified packet to the non-gateway network element; and/or, when receiving the packet sent by the non-gateway network element to the network management server, according to the NAT mapping table stored in the memory, the packet is sent The source IP address is modified to become the public network IP address allocated by the non-gateway network element, and the modified packet is sent to the network management server; and/or, when the non-gateway network element sends the network element identifier registration information, including the first port. The destination address of the packet sent by the network management server is a non-gateway network element and the destination port number is the packet of the first port, and the destination address of the packet is modified to be the non-gateway network element. The private network IP address used for device management, and the modified packet is sent to the first port.

The network management server in the data communication system receives and stores the NAT mapping table sent by the gateway network element, and encapsulates the packet according to the NAT mapping table, and sends the encapsulated packet to the gateway network element. The packet is forwarded by the gateway network element to the corresponding non-gateway network element.

The non-gateway network element in the data communication system receives the broadcast packet sent by the gateway network element, and sends its own network element identifier registration information to the gateway network element, so that the gateway network element generates a NAT mapping table according to the network element identifier registration information. Receiving the packet after the gateway network element performs NAT conversion.

In this embodiment, the gateway network element first allocates public network address information and a private network IP address for device management, a NAT mapping table for the non-gateway network element, and then the gateway network element registers the NAT mapping table in the network management server. Since the network management server can obtain the public network IP address of the non-gateway network element after obtaining the NAT mapping table, the non-gateway network element and the network management server pass a communication protocol such as an IP-based management protocol, such as SNMP or HTTP. When the protocol is used for packet exchange, the gateway network element only needs to perform NAT translation on the packet, thereby avoiding the need for the gateway network element to perform application layer parsing in the prior art. For example, the payload part of the packet needs to be parsed, and the packet is identified. The network element identifier, and then the encapsulation of the message, etc., consumes the operation of the gateway network element CPU, so the load of the gateway network element CPU is reduced, thereby making the gateway network element no longer the performance bottleneck of the entire DCN, effectively increasing the management domain. The number of network elements in the network, and improves the forwarding efficiency of packets in the management domain.

The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments are obvious to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention is not to be limited to the embodiments shown herein, but is to be accorded to the broadest scope of the principles and novel features disclosed herein.

+

Claims

A data communication network DCN configuration method, which is characterized in that:

Sending a broadcast packet carrying the IP address of the network management server to the non-gateway network element in the management domain in which it is located;

Obtaining the network element identifier registration information that is sent by the non-gateway network element after receiving the broadcast message, where the network element identifier registration information includes the network element identifier of the non-gateway network element;

Registering the NAT mapping table with the network management server.

The configuration method according to claim 1, wherein the method further comprises: receiving a packet sent by the network management server, where the destination address of the packet is a public network IP address of the non-gateway network element;

Transmitting the destination address of the packet to the private network IP address of the non-gateway network element for device management according to the stored NAT mapping table, and sending the packet with the modified destination address to the non-gateway Gateway network element.

The method according to claim 2, wherein the method further comprises: receiving a packet sent by a non-gateway network element, where a source address of the packet is used by the non-gateway network element for device management Private network IP address;

According to the stored NAT mapping table, the source address of the packet is modified to be the public network IP address of the non-gateway network element, and the packet whose source address is modified is sent to the network management server.

The method according to any one of claims 1 to 3, wherein the broadcast message further includes an IP address of the gateway network element and/or a management virtual local area network as described by the gateway network element. Logo.

The method according to any one of claims 1-3, wherein the network element registration information further includes a communication protocol and/or a first port supported by the non-gateway network element; The first NAT mapping table also includes the communication protocol and/or the first port.

6. The method of claim 5, wherein

When the first port is included in the NAT mapping table, the method further includes: Receiving, by the network management server, a public network IP address whose destination address is a non-gateway network element, and a destination port being the first port of the first port;

Modifying the destination address of the packet to a private network IP address used by the non-gateway network element for device management;

The modified message is sent to the first port.

7. A gateway network element, comprising:

The acquiring unit is configured to obtain the network element identifier registration information that is sent by the non-gateway network element after the broadcast message is received, where the network element identifier registration information includes the network element identifier of the non-gateway network element;

a generating unit, configured to allocate a public network IP address and a private network IP address for device management, and generate a network element identifier including the non-gateway network element, a public network IP address, and a device management NAT mapping table of the private network IP address;

And a registration unit, configured to register, by the network management server, the NAT mapping table generated by the generating unit.

The gateway network element according to claim 7, further comprising:

a NAT conversion unit, configured to: when receiving a packet sent by the network management server to the non-gateway network element, modify the destination IP address of the packet to the non-gateway network according to the NAT mapping table stored in the memory The private network IP address allocated for the device management, and the modified packet is sent to the non-gateway network element.

The gateway network element according to claim 8, wherein the NAT converting unit is further configured to: according to the memory, when receiving the packet sent by the non-gateway network element to the network management server The NAT mapping table is configured to modify the source IP address of the packet to be the public network IP address allocated by the non-gateway network element, and send the modified packet to the network management server.

The gateway network element according to claim 8 or 9, wherein the NAT conversion unit is further configured to: receive a public network IP address and a destination port of the non-gateway network element, where the destination address sent by the network management server is Transmitting, by the first port, the destination address of the packet to the private network IP address of the non-gateway network element for device management, and sending the modified packet to the first port; The port of the information.

A data communication system, comprising: a network management server, the gateway network element according to any one of claims 6-10, and at least one non-gateway network element; the gateway network element and the at least A non-gateway network element belongs to the same management domain, and the at least one non-gateway network element communicates with the network management server by using the gateway network element.

+