WO2021000713A1 - Network element management apparatus and message processing method - Google Patents

Abstract

Provided are a network element management apparatus and a message processing method. The network element management apparatus comprises: a physical interface, a global namespace, a private namespace and a softswitch module, wherein the global namespace is used for managing routing of an upper-level network element; the private namespace is used for managing routing of a lower-level network element; and the softswitch module is used for connecting the global namespace, the private namespace and the physical interface.

Description

Network element management device and message processing method

Cross references to related applications

This application is based on a Chinese patent application with an application number of 201910601817.7 and an application date of July 4, 2019, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby incorporated into this application by way of introduction.

Technical field

This application relates to the field of communication technology, and in particular to a network element management device and a message processing method.

Background technique

In the actual deployment of microwave products, the network scale may be very large, and there may be tens of thousands of devices in the network at the same time, and the microwave network usually has a chain or tree network topology. The IP (Internet protocol) resources that customers can provide are limited and precious. The problem of insufficient global IP resources often occurs, and each device cannot be assigned a global IP address for network management. Especially for the expansion of existing networks, customers are usually not allowed to change the topology of the existing network or add other equipment on the network management side.

If IP In IP (an IP tunneling protocol that encapsulates an IP data packet into another IP data packet) is used to manage equipment using LAN IP, the network management server needs to have a route to each LAN IP segment to use IP in IP technology communicates with devices that use LAN IP addresses. When the network scale is large, the routing scale is also huge. Establishing tunnels in the global network namespace will also generate a large number of virtual network interfaces (for example, a type of virtual network interface named "GRE"), which affects some commands and system calls that depend on the network interface. If it is configured directly in the global space of the network management server, it is likely to affect the functioning of the network management software. For example, the network management software may query the network card information of the device.

Summary of the invention

The embodiment of the present application provides a network element management device and a message processing method.

According to the network element management device of the present application, it is assumed that the network element using the global IP address is the upper-level network element, and the network element using the local area network IP or the private IP is the lower-level network element. The network element management device includes: a physical interface for supply The network element management device interacts with the upper-level network element and the lower-level network element respectively through the physical interface; a global namespace is used to manage the routes of the upper-level network element; and a private namespace is used to Manage the routing of the lower-level network elements; a soft switch module, used to connect the global namespace, the private namespace and the physical interface.

According to the method for processing a downlink packet by a network element management apparatus according to an embodiment of the present application, the network element management apparatus is the above-mentioned network element management apparatus, and the method includes: When sending a message, the message is a downlink message; if the target network element is an upper-level network element, the downlink message is sent from the physical interface to the target network element through the softswitch module; if the target If the network element is a lower-level network element, the downlink message enters the private namespace through the softswitch module, and after the downlink message is encapsulated in the private namespace, it is sent from the private namespace through the softswitch module. The physical interface is sent to the target network element.

According to the method for processing uplink packets by a network element management device according to an embodiment of the present application, the network element management device is the aforementioned network element management device, and the method includes: when the network element sends a report to the network element management device When sending the message, the message is an uplink message; if the network element that sends the uplink message is an upper-level network element, the network element sends the uplink message to the physical interface and passes it through the software The switching module is sent to the network management software; if the network element sending the uplink message is a lower-level network element, the lower-level network element sends the uplink message to the gateway network element, and the uplink message passes through the gateway network element. After the meta is encapsulated, it enters the private namespace through the softswitch module, and the uplink message is decapsulated in the private namespace and then sent to the network management software through the softswitch module.

According to the computer-readable storage medium of the embodiment of the present application, a program for implementing information transmission is stored on the computer-readable storage medium, and when the program is executed by a processor, the network element management apparatus as described above can perform message processing Method steps.

Description of the drawings

Fig. 1 is a schematic structural diagram of a network element management apparatus according to an embodiment of the present application.

Figure 2 is a network topology diagram inside a network element management device according to an embodiment of the present application;

Figure 3 is a network topology diagram inside a network element management device according to an embodiment of the present application;

Fig. 4 shows the trend of packets when the network element management device according to the embodiment of the present application uses the topology diagram in Fig. 2 when communicating with the upper-level network element and the lower-level network element.

Fig. 5 shows the trend of messages when the network element management device according to an embodiment of the present application uses the topology diagram in Fig. 3 when communicating with the upper-level network element and the lower-level network element.

Fig. 6 shows the message flow of the entire network when the upper-level network element and the lower-level network element communicate with the network element management apparatus according to an embodiment of the present application.

Fig. 7 is a processing flow of a downlink message performed by the network element management apparatus according to an embodiment of the present application.

Fig. 8 is a detailed flowchart of downlink message processing performed by the network element management apparatus according to an embodiment of the present application.

Fig. 9 is a processing flow of an uplink message performed by a network element management apparatus according to an embodiment of the present application.

Fig. 10 is a detailed flowchart of uplink message processing performed by the network element management apparatus according to an embodiment of the present application.

Description of the drawings:

Network element management device 100, physical interface 10, global name space 20, global routing table 210, private name space 30, private routing table 310, soft switch module 40, network management software 50,

Gateway network element 600, tunnel routing and forwarding module 610, upper-level network element 700, and lower-level network element 800.

Detailed ways

In order to further illustrate the technical means and effects adopted by the application to achieve the predetermined purpose, the application will be described in detail below with reference to the accompanying drawings and preferred embodiments.

As shown in FIGS. 1-3, according to the network element management device 100 of the present application, the network element management device 100 includes: a physical interface 10, a global namespace 20, a private namespace 30, and a softswitch module 40.

It is assumed that the network element using the global IP address is the upper network element 700, and the network element using the LAN IP or the private IP is the lower network element 800.

Among them, as shown in FIGS. 1 to 3, the physical interface 10 is used for the network element management apparatus 100 to interact with the upper-level network element 700 and the lower-level network element 800 through the physical interface 10, respectively.

The global namespace 20 is used to manage the routes of the upper-level network element 700, and the private namespace 30 is used to manage the routes of the lower-level network element 800. It should be noted that Linux can be used to create a network namespace to isolate the routes of the upper-level network element 700 and the lower-level network element 800. Among them, the global namespace 20 manages the routes of the upper-level network element 700, and the private namespace 30 manages the routes of the lower-level network element 800.

The soft switch module 40 is used to connect the global namespace 20, the private namespace 30 and the physical interface 10. It should be noted that the global namespace 20 and the private namespace 30 can be connected to the physical interface 10 through the soft switch module 40. Thus, it can be realized that the global namespace 20 and the private namespace 30 share one physical interface 10.

According to the network element management device 100 of the present application, the global namespace 20 and the private namespace 30 are used to manage the routes of the upper-level network element 700 and the routes of the lower-level network element 800, respectively, so that the routes of the upper-level network element 700 and the lower-level network element 800 The routing isolation realizes the routing isolation of the global IP address and the LAN IP address and private IP address, so that the private network routing will not affect the existing functions of the network element manager. Moreover, there is no need to deploy additional hardware equipment, nor to modify the customer's network topology and router configuration, which will not affect the existing network topology.

According to some embodiments of the present application, as shown in FIGS. 2-6, a GRE tunnel connecting the gateway network element 600 is provided in the private namespace 30. As shown in FIGS. 2-6, the private namespace 30 can create multiple A GRE tunnel: gref1, gref2, gref3, and gref4, etc. The routes of the lower-level network element 800 all point to the GRE tunnel interface of the corresponding gateway network element 600. Therefore, the lower-level network element 800 behind the gateway network element 600 can be managed through the configured GRE tunnel, so that the IP address of the lower-level network element 800 is not exposed to the outside. The IP address of the lower-level network element 800 is invisible to other devices in the global network, and is only visible to the network element management apparatus 100, thereby saving IP address resources.

In some embodiments of the present application, both the global namespace 20 and the private namespace 30 are connected to the soft switch module 40 through virtual links. The "virtual link" mentioned here may be a veth (Linux virtual Ethernet interface) link. As shown in FIG. 2, the global namespace 20 and the softswitch module 40 may be connected through a veth link, and the private namespace 30 may be connected through a veth link.

According to some embodiments of the present application, the global namespace 20 and the private namespace 30 are connected through a virtual link. As shown in FIG. 2, the global namespace 20 and the private namespace 30 are both connected to the softswitch module 40 through a veth link, and the global namespace 20 and the private namespace 30 can interact with each other through the softswitch module 40. As shown in Figure 3, another veth can be set between the global namespace 20 and the private namespace 30. One end of the veth link veth5 is connected to the global namespace 20, and the other end of the veth link veth6 is connected to the private The namespace 30 is connected. The global namespace 20 and the private namespace 30 can transmit messages through this link.

It should be noted that the private namespace 30 in this application can separately establish routes and GRE tunnels for each network segment of the lower-level network element 800. Each segment of the packet of the lower-level network element 800 can be forwarded to a designated tunnel, and the GRE tunnel can be decapsulated and forwarded to the global namespace 20. At the same time, the private namespace 30 can play a role in isolating private (Private) routing, GRE tunnels and global routing. The network management software 50 and the operating system global namespace 20 are not affected by private routing and GRE tunnels.

The function of the global namespace 20 is to distinguish between private routing and global routing. Transfer packets in the private address segment into and out of the private namespace 30.

The function of the soft switch module 40 is to connect the global namespace 20, the private namespace 30 and the physical interface 10. Provide a path for message forwarding between these modules.

The function of the gateway network element 600 is to provide tunnels and routes to the network management server for the lower-level network element 800. At the same time, the address of the lower-level network element 800 is isolated in the global network space. The communication between itself and the network element management apparatus 100 does not need to pass through a tunnel.

As shown in FIG. 7, according to the method for processing a downlink packet by the network element management apparatus 100 according to the embodiment of the present application, the network element management apparatus 100 is the above-mentioned network element management apparatus 100, wherein, when the network element management apparatus 100 points to the target When a network element sends a message, the message is a downlink message, and the method includes:

As shown in FIG. 7, if the target network element is an upper-level network element 700, the downlink message is sent from the physical interface 10 to the target network element via the soft switch module 40. In other words, if the target network element is an upper-level network element 700 that uses a global IP address, the network element manager may directly send the downlink message from the physical interface 10 to the target network element via the softswitch module 40.

If the target network element is a lower-level network element 800, the downlink message enters the private namespace 30 through the softswitch module 40. After the downlink message is encapsulated in the private namespace 30, it is sent to the target from the physical interface 10 through the softswitch module 40 Network element. It should be noted that by encapsulating the downlink message, the downlink message can be accurately and reliably sent to the corresponding gateway network element 600. After the gateway network element 600 performs decapsulation processing, the downlink message can be sent to the corresponding 800 of the lower-level network elements.

According to the method for processing a downlink message by the network element management apparatus 100 of the embodiment of the present application, corresponding processing is performed on different situations where the target network element is the upper-level network element 700 and the lower-level network element 800 respectively. If the target network element is the upper-level network element 700, the downlink message is sent directly from the physical interface 10 to the target network element through the softswitch module 40; if the target network element is the lower-level network element 800, the downlink message is encapsulated in the private namespace 30 Then, it is sent to the target network element via the soft switch module 40.

According to some embodiments of the present application, the step of determining the target network element includes:

Look up the global routing table 210 in the global namespace 20 to obtain the IP of the target network element;

If the IP of the target network element is a local area network IP or a private IP, it is determined that the target network element is a lower-level network element 800, and if the IP of the target network element is a global IP, it is determined that the target network element is an upper-level network element 700. Therefore, it is possible to determine whether the target network element is the upper-level network element 700 or the lower-level network element 800 by searching the global routing table 210 according to the IP address of the network element.

In some embodiments of the present application, the packet is encapsulated in the private namespace 30, including:

By searching the private space routing table in the private namespace 30, the GRE tunnel interface corresponding to the downlink packet is determined, and the downlink packet is encapsulated with the outer IP header based on the IP of the gateway network element 600 corresponding to the GRE tunnel interface.

It should be noted that the downlink packet can be encapsulated with the outer IP header and the GRE header through the GRE tunnel. Among them, the outer IP header is the global IP of the gateway network element 600. Therefore, the encapsulated downlink message can be accurately and reliably delivered to the gateway network element 600. After the gateway network element 600 receives the downlink message, it decapsulates the outer IP header and GRE header, and sends the downlink message to the corresponding lower-level network element 800 according to the inner-layer IP of the downlink message to complete the target network element as the lower-level network Yuan 800 downlink message is sent.

The following describes in detail the processing method of the downlink packet of the network element management apparatus 100 according to the embodiment of the present application with reference to FIG. 8:

Determine whether the destination IP address of the message is a private IP address:

For the PrivateIP address message, the next hop address of the message is set to the IP address of veth4 in the private namespace;

Packets with the destination address of the privateIP address enter the private namespace through the softswitch;

For packets whose destination address is the private IP address, look up the route in the private namespace, and determine that the outbound interface of the route is the corresponding GRE tunnel interface;

Encapsulate the GRE outer IP header and send it back to the global namespace (globalnamespace);

Sent through the softswitch to the physical interface 10 of the network element management device 100;

When the message reaches the gateway network element 600, the outer IP is decapsulated, and the inner IP is used for forwarding, and the message is forwarded to the lower-level network element 800;

For packets whose destination IP is globalIP:

For the packet whose destination address is the globalIP address, search the global route and set the next hop to the gateway IP address of the network management server;

The message is sent to the softswitch module 40, the softswitch module 40 is directly forwarded to the physical interface 10 for sending, and the message is directly sent to the destination network element.

As shown in FIG. 9, according to the method for processing uplink packets by the network element management apparatus 100 of the embodiment of the present application, the network element management apparatus 100 is the above-mentioned network element management apparatus 100, wherein, when the network element sends to the network element management When the device 100 sends a message, the message is an uplink message, and the method includes:

As shown in FIG. 9, if the network element that sends the uplink message is the upper-level network element 700, the network element sends the uplink message to the physical interface 10, and sends the uplink message to the network management software 50 via the soft switch module 40. In other words, if the network element that sends the uplink message is the upper-level network element 700 that uses the global IP address, the upper-level network element 700 sends the uplink message to the physical interface 10 of the network element manager, and forwards it via the softswitch module 40 To the network management software 50.

If the network element that sends the uplink message is the subordinate network element 800, the subordinate network element 800 sends the uplink message to the gateway network element 600. After the uplink message is encapsulated by the gateway network element 600, it enters the private network via the softswitch module 40. Name space 30, after the uplink message is unsealed in the private name space 30, it is sent to the network management software 50 via the soft switch module 40. It should be noted that by encapsulating the uplink message, the uplink message can be sent to the private namespace 30 of the network element management device 100, and after the decapsulation process is performed in the private namespace 30, it passes through the softswitch module 40 Send to network management software 50.

According to the method for processing uplink packets by the network element management apparatus 100 of the embodiment of the present application, different situations in which the upper-level network element 700 and the lower-level network element 800 send uplink packets are respectively processed accordingly. If the network element sending the message is the upper-level network element 700, the uplink message is sent from the physical interface 10 through the softswitch module 40 directly to the network management software 50; if the network element sending the upper-level message is the lower-level network element 800, the downlink message is After the gateway network element 600 performs the encapsulation process, it is sent to the private namespace 30 via the softswitch module 40 for decapsulation processing and sent to the network management software 50.

According to some embodiments of the present application, the uplink packet is encapsulated in the gateway network element 600, including:

The gateway network element 600 performs IP header encapsulation on the uplink message based on the IP of the private namespace 30. That is to say, the gateway network element 600 encapsulates an outer IP header for the uplink packet, where the outer IP header is the IP of the private namespace 30. In this way, the uplink message can be transmitted to the private namespace 30.

In some embodiments of the present application, the decapsulation processing of uplink packets in the private namespace 30 includes:

The uplink packet is transmitted to the GRE tunnel corresponding to the gateway network element 600 in the private namespace 30, and the outer IP header is decapsulated on the uplink packet. It should be noted that after the uplink packet is transmitted to the private namespace 30, it passes through the GRE tunnel corresponding to the gateway network element 600, and the outer IP header of the uplink packet can be decapsulated. The private routing table 310 is searched to find the connection with the inner layer. For the route corresponding to the IP header, the uplink message is transmitted to the network management software 50 via the soft switch module 40.

The following describes in detail the processing method of the uplink message of the network element management apparatus 100 according to the embodiment of the present application with reference to FIG. 10:

When the network element sending the uplink message is the lower-level network element 800, the lower-level network element 800 sends the message to the gateway network element 600;

The gateway network element 600 receives the message sent by the lower-level network element 800, and encapsulates the GRE header and the outer IP header;

The message is forwarded to the network element management device 100 via the gateway network element 600;

The network element management device 100 determines that the destination IP address of the message is the IP address of private namespace (private namespace 30) veth4, and forwards the message to the private namespace via the softswitch module 30;

The message is sent to the corresponding GRE tunnel interface on the private namespace, the outer IP header is decapsulated, and the inner IP is judged to be the IP address of the network element management device 100. The message is sent to the global veth1 through the softswitch module 40, and finally sent to the network management Software 50.

If the network element sending the uplink message is the upper-level network element 700, the message sent by the non-upper-level network element 700 is directly sent to the veth1 via the softswitch module 40, and finally sent to the network management software 50.

It should be noted that, in a scenario where there are many devices in the network and the IP addresses that can be provided to the devices are limited, the network element management apparatus 100 and the message processing method of the network element management apparatus 100 according to the embodiments of the present application are performed in the network management The server (network element management device 100) uses linux network namespace for routing isolation to isolate the routing of the LAN device (lower NE 800) from the routing of the global space (global namespace 20), so that the network management software 50 cannot perceive the LAN Thousands of routes and GRE tunnel virtual network interfaces. In addition, messages that communicate with devices using LAN IP addresses can be correctly sent out of the network management server (network element management device 100) through IP in IP, and communicate normally with devices on the network using LAN IP addresses through the global network. This application only configures the global IP address on the upstream device (upper network element 700). The downstream device (the lower-level network element 800) uses the LAN IP address or the private network IP address, and the IP address of the downstream device is not visible in the global network. The network management software 50 uses the global IP address and the LAN IP address to manage the upstream and downstream devices respectively.

The global name space of the network management server (network element management device 100) points to another private name space 30 for all routes using the private network IP. Only the message of the device using the global IP address directly searches the global routing table 210 of the global namespace 20, and sends it in the form of ordinary IP message from the physical interface 10 of the network management server. For a device using a LAN IP address, when the network management server communicates with it, the message must first enter the private namespace (private namespace 30) through routing, and enter the corresponding GRE tunnel (GRE tunnel) interface through the private routing table 310 of the private namespace. , Encapsulate the GRE header, and on the outer encapsulation, the message whose destination IP is the IP address of the gateway network element 600 is returned to the global namespace 20 for sending.

In this way, from the perspective of equipment deployment, multiple devices on a link only need the first device to manage IP addresses globally, which greatly saves IP addresses used on the network. From the perspective of network management equipment. The route and GRE tunnel to the LAN IP address of each gateway network element 600 and the lower-level network element 800 are invisible to the network management software 50, and private network routes are not exposed to the outside, and will not affect the normal operation of various functions of the network management software 50. The commands and system calls of the Linux operating system are not affected. Moreover, there is no need to add new hardware resources and modify the network topology, real-time cost is low, and maintenance is convenient. There is no need to deploy additional equipment to route the equipment using LAN IP, saving costs. Greatly solve the cost of IP address resources and equipment deployment.

Among them, the network element management device 100 according to the present application has two methods for the network topology. The first method is shown in FIG. 2. There is only one method between the global namespace (global namespace 20) and the private namespace (private namespace 30). A veth link is connected. One end of the veth link has the veth4 interface in the private namespace (private namespace 30), and the other end veth3 interface is directly connected to the soft switch module 40 of the global namespace (global namespace 20), the soft switch module 40 can be linux bridge or openvswitch. The veth4 interface in the private namespace (private namespace 30) needs to have a global IP address. Linux connects the physical network ports to veth3 of the global namespace (global namespace 20), and connects to veth4 of the private namesapce (private namespace 30) through a Linux bridge or openvswitch, so that the global namespace and private namespace share the physical Network port. When the network element management software communicates with a device using a private IP address, the message must enter the private namespace through the only veth link, and then return to the global network namespace through the original path after the GRE header and the external IP header are added. Send to the physical port.

The second method is shown in Figure 3, in which a veth link is established between the global namespace and the private space for packet transmission without GRE header. When the network element management device 100 communicates with a device using a LAN IP, the device first passes this veth link to the private namespace, GRE header, encapsulates the external IP header, and then passes another veth link to linux bridge or openvswitch after soft forwarding issue. The processing of upstream messages is the opposite of that of downstream messages, and will not be repeated here.

According to the network element management device 100 of the present application, the network management software 50 manages the management of common network elements and gateway network elements 600 through a global IP. The ordinary network element and the gateway network element 600 described here can be understood as the "upper network element 700" described above. The route to the upper-level network element 700 is stored in the global namespace 20, and the message direction is shown as the solid line in Figure 4. After the message is sent to find the route, it is connected to linux Bridge or openvswitch through veth, and sent through the soft switch module 40. To the physical network port. The message is a common single-layer IP header message. The management of the lower-level network element 800 of the gateway network element 600 is shown by the mixed line of dashed and solid lines in the figure. First, it searches for a private IP-specific route in the global namespace 20. The route is a route to the private network namespace. veth route, after the message enters the private network namespace, find the route of the namesapce, and the route will point the route to the IP address of the downstream network element of the gateway network element 600 to the corresponding GRE tunnel, put the GRE header, and encapsulate the outer IP (destination IP The address is the IP of the gateway network element 600, and the message becomes a GRE message, indicated by the dotted line.) Then, the message is sent to the linux bridge or openswitch by connecting the veth between the private namespace and the linux bridge, and then forwarded to the physical network port by soft forwarding Send out the network management server. The message is an IP in IP GRE message, the destination address of the outer IP is the IP of the gateway network element 600, and the destination address of the inner IP is the private network IP address used by the downstream device.

When the GRE message of the management subordinate network element 800 reaches the gateway network element 600, the gateway network element 600 deletes the GRE header and the outer IP header, and delivers the message to the subordinate network element 800 according to the inner IP. When the gateway network element 600 receives the message sent from the lower-level network element 800 to the network management server, it encapsulates the message into the GRE tunnel according to the policy routing, and the outer destination IP address is the global IP address of the network management server. Use the outer IP address to deliver the message to the network management server.

According to the computer-readable storage medium of the embodiment of the present application, a program for implementing information transmission is stored on the computer-readable storage medium, and when the program is executed by a processor, the steps of the method for processing a message performed by the network element management apparatus 100 as described above are realized.

According to the computer-readable storage medium of the embodiment of the present application, the GRE tunnel and name space isolation technology are adopted, which saves IP addresses and does not require additional equipment. The upper-level network element 700 and the lower-level network element 800 are processed accordingly. Reliable and stable operation.

Through the description of the specific implementation manners, it should be possible to gain a more in-depth and specific understanding of the technical means and effects adopted by the application to achieve the intended purpose. However, the attached drawings are only for reference and explanation purposes, and are not used to describe the application. limit.

Claims (11)

A network element management device, wherein a network element using a global IP address is an upper-level network element, and a network element using a LAN IP or a private IP is a lower-level network element, and the network element management device includes: A physical interface for the network element management device to interact with the upper-level network element and the lower-level network element through the physical interface; The global namespace is used to manage the routing of the upper-level network element; Private namespace, used to manage the routes of the lower-level network elements; The soft switch module is used to connect the global name space, the private name space and the physical interface. The network element management device according to claim 1, wherein a GRE tunnel connecting a gateway network element is provided in the private namespace, and routes of the lower-level network elements all point to the GRE of the corresponding gateway network element Tunnel interface. The network element management device according to claim 1, wherein the global namespace and the private namespace are both connected to the soft switch module through a virtual link. The network element management device according to claim 1, wherein the global namespace and the private namespace are connected by a virtual link. A method for processing a downlink message using the network element management device according to any one of claims 1-4, wherein the method includes: When the network element management apparatus sends a message to the target network element, the message is a downlink message, If the target network element is an upper-level network element, the downlink message is sent from the physical interface to the target network element via the softswitch module; If the target network element is a lower-level network element, the downlink message enters the private namespace through the softswitch module, and after the downlink message is encapsulated in the private namespace, it passes through the softswitch module From the physical interface to the target network element. The downlink message processing method of the network element management device according to claim 5, wherein the step of determining the target network element comprises: Searching the global routing table in the global namespace to obtain the IP of the target network element; If the IP of the target network element is a local area network IP or a private IP, it is determined that the target network element is a lower-level network element, and if the IP of the target network element is a global IP, it is determined that the target network element is an upper-level network element . The method for processing a downlink message of a network element management device according to claim 5, wherein the encapsulation of the message in the private namespace includes: By searching the private space routing table in the private namespace, the GRE tunnel interface corresponding to the downlink message is determined, and the downlink message is encapsulated with the outer IP header based on the IP of the gateway network element corresponding to the GRE tunnel interface . A method for processing an uplink message by using the network element management device according to any one of claims 1-4, wherein the method includes: When a network element sends a message to the network element management apparatus, the message is an uplink message, If the network element that sends the uplink message is an upper-level network element, the network element sends the uplink message to the physical interface, and sends the uplink message to the network management software via the soft switch module; If the network element sending the uplink message is a lower-level network element, the lower-level network element sends the uplink message to a gateway network element, and the uplink message is encapsulated by the gateway network element and then The softswitch module enters the private name space, and the uplink message is sent to the network management software through the softswitch module after unsealing processing in the private name space. The uplink packet processing method of the network element management device according to claim 8, wherein the encapsulation processing of the uplink packet in the gateway network element comprises: The gateway network element performs IP header encapsulation on the uplink message based on the IP of the private namespace. The method for processing an uplink packet of a network element management device according to claim 8, wherein the decapsulation processing of the uplink packet in the private namespace includes: The uplink message is transmitted to the GRE tunnel corresponding to the gateway network element in the private namespace, and the outer IP header is decapsulated on the uplink message. A computer-readable storage medium, wherein a program for implementing information transmission is stored on the computer-readable storage medium, and when the program is executed by a processor, the network element according to any one of claims 5 to 10 is realized The management device performs the steps of the message processing method.

Images