CN107769939B

CN107769939B - Network element management method, network management, gateway network element and system in data communication network

Info

Publication number: CN107769939B
Application number: CN201610679519.6A
Authority: CN
Inventors: 高峰; 刘作臣
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2016-08-17
Filing date: 2016-08-17
Publication date: 2020-03-20
Anticipated expiration: 2036-08-17
Also published as: CN107769939A

Abstract

The embodiment of the invention relates to a network element management method, a network manager and a gateway network element in a data communication network. The data communication network DCN comprises a network manager, a Gateway network Element (English: Gateway Element, GNE) and a network Element to be registered (English: Net Element, NE), and the method specifically comprises the following steps: the Network management receives the information of the NE to be registered through the GNE, the information of the NE to be registered comprises a Virtual Local Area Network (VLAN) identifier of the NE to be registered, and the VLAN identifier of the NE to be registered is a VLAN identifier corresponding to a subinterface of the GNE connected with the NE to be registered. The network management allocates the first IP address of the same network segment to the NE to be registered according to the VLAN identification of the NE to be registered, and the first IP address represents that the NE to be registered is registered at the network management. Through the embodiment of the invention, the network manager can allocate resources for the NE by allocating the NE to be registered according to the VLAN identifier of the NE, thereby simplifying the NE registration process and improving the network element management efficiency of the network manager.

Description

Network element management method, network management, gateway network element and system in data communication network

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method, a system, and a network element management system for a data communication network.

Background

In a mobile bearer network, the number of base stations is relatively large, and the number of Network Elements (NE) for bearing base station data is also relatively large, and since the registration of each network element device requires not only hardware installation personnel to install the hardware device but also software configuration and debugging of software debugging personnel, the workload is large and the cost is high in the registration process of the network element device.

In order to reduce the debugging and Configuration work of software debugging personnel on site when the network element equipment is registered, a network element plug and play registration method based on a Dynamic Host Configuration Protocol (DHCP) is adopted in the prior art. Specifically, software debugging personnel configure the corresponding relation between the network element equipment position and the IP address on a DHCP Server (English: Server) according to a network planning form, make a configuration script, establish the corresponding relation between the equipment position and the configuration script, and the configuration script comprises the IP address of an interface, routing protocol configuration, service configuration and the like; when a hardware installer installs and powers on a field device, the network element device actively sends a Request (English: Request) to the DHCP Server to obtain an IP address; the DHCPServer determines the position of the registered network element equipment according to the uplink interface name carried in the request, allocates an IP address for the registered network element equipment according to the corresponding relation between the pre-configured network element equipment position and the IP address, and simultaneously issues a configuration script comprising the IP addresses of other interfaces of the registered network element equipment, routing protocol configuration and DHCP Relay (English: Relay) to the registered network element equipment through the allocated IP address so that the network element equipment starts the corresponding routing protocol and DHCP Relay function at each interface according to the configuration script, thereby completing the registration of the current network element equipment.

According to the network element plug-and-play registration method based on the DHCP, the DHCP Relay needs to be configured, planning and configuration need to be carried out on each device from a network manager, the process of modifying script registration step by step is complex, and the efficiency is low.

Disclosure of Invention

The embodiment of the invention provides a Network element management method, a Network manager, a gateway Network element and a system, which can manage the Network element through a Data Communication Network (DCN), allocate an IP address for the Network element to be registered, simplify the process of Network element registration and improve the efficiency of Network element management.

In a first aspect, an embodiment of the present invention provides a method for managing a network element in a DCN. The DCN comprises a network manager, a Gateway Network Element (GNE) and a network Element to be registered (NE), and the method specifically comprises the following steps: the Network management receives the information of the NE to be registered through the GNE, the information of the NE to be registered comprises a Virtual Local Area Network (VLAN) identifier of the NE to be registered, and the VLAN identifier of the NE to be registered is a VLAN identifier corresponding to a subinterface of the GNE connected with the NE to be registered. The network management allocates the first IP address in the VLAN network segment indicated by the VLAN identification to the NE to be registered according to the VLAN identification of the NE to be registered, and the first IP address represents that the NE to be registered is registered at the network management. Through the embodiment of the invention, the network manager can allocate resources for the NE by allocating the NE to be registered according to the VLAN identifier of the NE, thereby simplifying the NE registration process and improving the network element management efficiency of the network manager.

In an optional implementation, the network manager allocates the first IP address in the VLAN network segment indicated by the VLAN identifier to the NE to be registered according to the correspondence between the VLAN identifier and the IP address, and specifically includes: and the network manager determines the IP address section corresponding to the NE to be registered according to the corresponding relation between the VLAN identification and the IP address section. For example, a corresponding relation table between the VLAN identifier and the IP address field may be planned, or the network manager determines a GNE subinterface corresponding to the VLAN identifier of the NE to be registered, where the GNE subinterface is configured with an IP address; and the network manager determines the corresponding relation between the VLAN identification of the NE to be registered and the IP address field according to the IP address configured by the GNE sub-interface. The network manager allocates a first IP address in the VLAN network segment indicated by the VLAN identifier to the NE to be registered, and the first IP address is an unoccupied IP address in the IP address segment corresponding to the NE to be registered. The embodiment of the invention allocates the first IP address for the NE through the corresponding relation between the VLAN identification and the IP address field, simplifies the allocation of the first IP address, reduces the intervention of a network administrator or a user, and improves the efficiency of network element management.

In another optional implementation, the network manager determines link layer discovery protocol LLDP topology information of the NE; and the network manager allocates communication resources (configuration information of protocols such as telnet, SNMP and the like) in the non-DCN for the NE topology according to the VLAN identifier and the LLDP information of the NE. The embodiment of the invention can configure the NE in the DCN by the network management, simplifies the process of NE configuration and improves the efficiency of network element management.

In yet another alternative implementation, the network manager may receive a simple network management protocol SNMP message sent by the GNE, where the SNMP message carries the VLAN id of the NE and the second IP address. The embodiment of the invention can realize the report of the VLAN identification so that a network manager can allocate resources for NE according to the VLAN identification. The embodiment of the invention can realize that the network manager determines the VLAN identification of the NE to be registered through the SNMP message.

In a second aspect, an embodiment of the present invention provides a method for managing a network element in a data communication network. The data communication network comprises a network manager, a gateway network element GNE and a network element NE to be registered, and the method specifically comprises the following steps: the GNE receives a second IP address sent by the NE to be registered, wherein the second IP address is a factory-configured IP address of the NE to be registered; the GNE determines a VLAN identifier corresponding to a sub-interface of the GNE connected with the NE to be registered according to the second IP address, wherein the VLAN identifier is the VLAN identifier of the NE to be registered; and the GNE sends information of the NE to be registered to the network manager, wherein the information of the NE to be registered comprises the VLAN identifier, so that the network manager allocates a first IP address in a VLAN network segment indicated by the VLAN identifier to the NE to be registered according to the VLAN identifier of the NE to be registered, and the first IP address represents that the NE to be registered is registered at the network manager. Through the embodiment of the invention, the network manager can allocate resources for the NE by allocating the NE to be registered according to the VLAN identifier of the NE, thereby simplifying the NE registration process and improving the network element management efficiency of the network manager.

In an optional implementation, the information of the NE to be registered sent by the GNE to the gateway further includes a second IP address, and the method further includes: GNE receives a first IP address of NE to be registered, which is sent by a network manager, wherein the first IP address is sent by the network manager according to a second IP address; the GNE sends the first IP address to the NE to be registered by using the second IP address; and the GNE determines a non-DCN routing table entry corresponding to the NE to be registered according to the first IP address.

In another optional implementation, the GNE receives an open shortest path first protocol OSPF message sent by an NE to be registered, wherein the OSPF message includes a link state LS of the NE, and the LS of the NE includes a second IP address of the NE.

In a third aspect, an embodiment of the present invention provides a network element management apparatus in a data communication network, where the apparatus is capable of implementing the steps executed by the network management in the method in the first aspect and optionally in the implementation. The device can be realized by hardware, and can also be realized by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In a fourth aspect, an embodiment of the present invention provides an apparatus for managing a network element in a data communication network, where the apparatus is capable of implementing the steps performed by the GNE in the method in the second aspect and optionally in the implementation. The device can be realized by hardware, and can also be realized by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In a fifth aspect, an embodiment of the present invention provides a network management system, where the network management system includes a transceiver, a processor, and a memory. The transceiver is used for interacting with the network element and can comprise a receiver and a transmitter; the memory is used for storing programs and data. The processor implements the steps of the network management execution in the foregoing first aspect and optionally in the implementation by executing a program stored in the memory.

In a sixth aspect, embodiments of the present invention provide a GNE. The GNE includes a transceiver, a processor, and a memory. The various modules may be connected by a bus. The transceiver communicates with the NE and the network manager. The memory is used for storing program codes and data. The processor performs the operational steps of GNE in the second aspect and optionally in implementations, in accordance with program instructions stored in the memory.

In a seventh aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for the network manager, which includes a program designed to execute the first aspect and optionally implement the method.

In an eighth aspect, embodiments of the present invention provide a computer storage medium for storing computer software instructions for the GNE, which includes a program designed to perform the second aspect and optionally implement the second aspect.

In a ninth aspect, an embodiment of the present invention provides a DCN system for a data communication network. The DCN system comprises a network manager, a gateway network element GNE and a network element NE to be registered, wherein the network manager is the network manager in the fifth aspect; GNE is the GNE of the sixth aspect.

Drawings

FIG. 1 is a schematic diagram of an application scenario;

FIG. 2 is an example of a network architecture;

fig. 3 is a network element management interaction diagram in a data communication network according to an embodiment of the present invention;

fig. 4 is a message example provided by the embodiment of the present invention;

fig. 5 is a schematic structural diagram of a network element management apparatus in a DCN according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of another network element management device in a DCN according to an embodiment of the present invention;

fig. 7 is a schematic structural diagram of a GNE according to an embodiment of the present invention;

fig. 8 is a schematic structural diagram of a network manager 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 clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention.

Fig. 1 is a schematic diagram of an application scenario. As shown in fig. 1, the network is composed of network managers and NEs, wherein the NEs directly connected to the network managers are generally called GNEs or access network elements, and the NEs in the network can be managed through the network managers. The network may be composed of a service network and a DCN, where the service network and the DCN may include the same network device (network element and network manager), and the same network device may implement communication in the service network and the DCN through different logical interfaces or physical interfaces, respectively. Because there are many core routing tables in the DCN, the DCN is only used to manage the NEs in the network, for example, the NE to be registered is registered through the DCN, and after the registration is completed, the DCN logical interface of the NE to be registered may be deleted or the DCN physical interface of the NE to be registered may be closed. The service network is generally used for carrying service data, and registered network elements can also be managed through the service network.

According to the user requirement or more simply on the aspect of network element management, the IP addresses of all network elements in a subnet identified by a VLAN are generally in the same network segment. Specifically, one or more subinterfaces may be configured on one GNE, each subinterface may correspond to one VLAN, each VLAN corresponds to one IP address segment, and the IP address segments corresponding to the VLANs are different. In other words, a plurality of NEs are connected to the same subinterface, each NE corresponds to one IP address (first IP address), and the IP addresses of all NEs corresponding to one subinterface should belong to the same network segment, that is, all the NEs belong to the IP address segment corresponding to the VLAN corresponding to the subinterface.

The network manager can determine a VLAN (virtual local area network) identifier of the NE to be registered through the GNE, wherein the VLAN identifier of the NE to be registered is a VLAN identifier corresponding to a subinterface of the GNE connected with the NE to be registered; the network manager can allocate the first IP address in the VLAN network segment indicated by the VLAN identifier to the NE to be registered according to the VLAN identifier of the NE to be registered, and the completion of the allocation of the first IP address indicates that the NE to be registered is registered at the network manager. The GNE can determine the VLAN identifier corresponding to the subinterface of the GNE connected with the NE to be registered according to a factory-configured IP address (NEIP) sent by the NE to be registered. Specifically, the GNE may establish a connection between the GNE and the NE to be registered in the DCN according to the NEIP, determine an interconnection relationship between the NE to be registered and other NEs through the connection, and determine a sub-interface of the GNE connected to the NE according to the interconnection relationship, where the VLAN to which the sub-interface belongs is the VLAN to which the NE to be registered belongs.

Specifically, each NE is provided with a unique NEID when it leaves the factory, and a NEIP (second IP address) may be generated according to the NEID, where the NEIP is available for communication in the DCN, the NEIP is not generally within an IP address field corresponding to the GNE subinterface to which the NEIP is connected, and the NEIP may be considered as a temporary IP address, and the network manager may perform initial configuration on a network element corresponding to the NEIP through the NEIP (for example, configure an IP address within an IP address field corresponding to the GNE subinterface to which the network element is connected, that is, configure a first IP address). Specifically, after the NE to be registered is physically connected to other NEs, and the NE to be registered is powered on, the DCN connection between the NE to be registered and the GNE is established according to the NEIP. When the registration is started, the network manager can determine the NEIP and VLAN identification of the NE to be registered, the network manager can allocate a first IP address for the NE to be registered according to the VLAN identification of the NE to be registered, and the first IP address is sent to the network element to be registered through DCN connection. For example, the NE to be registered automatically enables an Open Shortest Path First (OSPF) protocol flow under an interface, and propagates the NEIP of the NE to be registered to the GNE through flooding; after the GNE learns the NEIP of the NE to be registered, reporting the NEIP of the NE to be registered and the VLAN identifier of the NE to be registered to a network manager; or, the network manager may also query the NE to be registered by searching (triggered by a set time or by a network administrator), and obtain the NEIP and VLAN id of the NE to be registered.

After determining the NEIP, the network manager can log in the NE to be registered (requiring GNE proxy) through the DCN, and configure the NE to be registered. For example, the Network manager may configure the first IP address on the NE to be registered, and may also configure a Simple Network Management Protocol (SNMP), a remote terminal Protocol (Telnet), a File Transfer Protocol (Ftp), and the like on the NE to be registered.

It should be noted that, in the embodiment of the present invention, the second IP address is an IP address generated according to NE factory configuration, and is used for DCN communication; the first IP address is used for communication in the service network. The "first" and the "second" are only for distinguishing the two different IP addresses, and the second IP address may be referred to as a first IP address and the first IP address may be referred to as a second IP address in terms of names.

Fig. 2 is an example of a network architecture. The network elements in the network shown in fig. 2 are mainly used for carrying data between the base station 211 and the core network device 250, wherein each network element (e.g., NE221, 223, etc.) and the gateway network element (e.g., GNE231) are managed by the network manager 240. In addition, the network may also include NE 222. If NE221 and NE222 are directly connected to GNE231, then NE221 can be configured to belong to VLAN1 and NE222 can belong to VLAN2 at GNE. NE223 is a network element to be registered, and if NE223 is directly connected to NE221, NE223 is considered to belong to VLAN 1. Here, VLAN1 and VLAN2 are VLANs configured for GNE. The base station 211 and the core network device 250 may be devices in a communication System such as EPS (Evolved Packet System) or UMTS (Universal Mobile Telecommunications System).

In addition, it may be necessary to pass through Network 260 between NE221 and NE222 and GNE231, where Network 260 may be a third-party Network, Network 260 provides a Virtual Private Network (VPN), and NE221 and NE222 may access Network 260 through NE 232. If NE221 belongs to VLAN3 and NE222 belongs to VLAN4 in NE232, NE221 belongs to VLAN1 and NE222 belongs to VLAN2 in GNE. VLAN3 and VLAN4 are mapped by NE232 to VLAN1 and VLAN2, respectively, for data transport over network 260 to GNE.

It should be appreciated that only a simplified network scenario is shown in the figures for ease of description. In practical applications, the number of NEs in the network is very large, and a plurality of NEs may be included in one VLAN. For scenarios involving third party network VPNs, each VPN typically allows 1000 NEs to be connected.

The following describes an embodiment of the present invention with reference to fig. 3, and the network architecture shown in fig. 2 as an example.

Fig. 3 is a network element management interaction diagram in a data communication network according to an embodiment of the present invention. As shown in fig. 3, the method specifically includes:

s310, the GNE receives a second IP address of the NE to be registered, which is sent by the NE to be registered; the second IP address is a factory configured IP address of the NE to be registered, and the second IP address is used for the NE to be registered to communicate with the network management in the DCN through the GNE.

After the NE is powered up, the NE may send a second IP address (NEIP) to the GNE, which may be sent, for example, via OSPF.

For example, the network element is the NE223 shown in fig. 2, when the NE223 needs to be registered, after the hardback engineer completes the physical connection and powers on the device, the NE223 enables the DCN interface. Specifically, the NE223 may perform a negotiation through OSPF with PPPOE (Point to Point Protocol over Ethernet), create a DCN Serial (Serial interface) according to a negotiation result, and establish a DCN connection between the NE to be registered and the GNE. The DCN Serial is a logical interface, and for a physical interface (Eth interface, ethernet interface) of the NE, a negotiation of multiple PPPoE sessions may be successful on one Eth interface, and multiple DCN Serial are created. However, because NEIPs of neighboring devices may not be in the same network segment, connection establishment cannot be achieved by obtaining an ARP entry through an Address Resolution Protocol (ARP). The MAC and IP addresses of the peer network element (GNE) need to be negotiated through PPPoE.

S320, the GNE determines a VLAN identifier corresponding to a sub-interface of the GNE connected with the NE to be registered according to the second IP address; and the VLAN identifier corresponding to the subinterface of the GNE connected with the NE to be registered is the VLAN identifier of the NE to be registered.

The subinterfaces of the GNE connected by the NE to be registered comprise the subinterfaces of the GNE directly connected by the NE to be registered or the subinterfaces of the GNE connected by other NE.

For example, as shown in fig. 2, the connection between the NE223 and GNE for DCN communication is established according to the second IP address by the procedure of the foregoing S310, where the GNE can determine that the NE223 is connected to the NE221 through Link Layer Discovery Protocol (LLDP), and then the VLAN id of the NE223 is the VLAN id corresponding to the NE221 in the NE221 GNE. For the case of a network with a leased third party, the VLAN identification of NE221 is mapped and then the VLAN identification of NE223 is mapped to the VLAN identification of NE 221.

In addition, if the network needs to pass through the third-party network 260, the VLAN information corresponding to the network element is the VLAN information after passing through the network element.

S330, the GNE sends the information of the NE to be registered to the network management, and the information of the NE to be registered comprises the second IP address of the NE to be registered and the VLAN identification to be registered. .

For example, as shown in fig. 2, the GNE231 may send the NE IP and VLAN identification of the network element to be registered (NE223) to the network management 240. For example, the SNMP message carries the second IP address and the VLAN id, and may also be carried by a message in another DCN network.

In one example, as shown in fig. 4, the SNMP message includes: DCN mode (English: IP RAN DCN NE ChangeMode), DCN NEID (English: IP RAN DCN NE Info NE ID), DCN NE IP Type (English: IP RAN DCNNE Info NE IP Type), DCN NEIP (English: IP RAN DCN NE Info NE IP), DCN NEIP Mask (English: IP RAN DCN NE Info NE IP Mask), DCN NE Number (English: IP RAN DCN NE Number) and DCNVLAN tag (English: IP RAN DCN VLAN) (New). Wherein, the DCN NE ID is the identifier of the network element to be registered, the DCN eip is the NEIP of the network element to be registered, and the DCN NE number is the number of NEs connected to the GNE (since the number of network elements connected to each gateway is limited, it can be determined whether there are enough resources for the communication of the network element to be registered according to the DCN NE number).

S340, the network manager allocates the first IP address in the VLAN network segment indicated by the VLAN identifier to the NE to be registered according to the VLAN identifier of the NE to be registered, and the first IP address represents that the NE to be registered is registered at the network manager.

The network manager can determine the IP address field corresponding to the NE to be registered according to the corresponding relation between the VLAN identifier of the NE to be registered and the IP address field; and allocating a first IP address to the NE to be registered, wherein the first IP address is an unoccupied IP address in an IP address field corresponding to the NE to be registered. Specifically, the network manager can determine a GNE subinterface corresponding to the VLAN identifier of the NE to be registered, and the GNE subinterface is configured with an IP address; and the network manager determines the corresponding relation between the VLAN identification of the NE to be registered and the IP address section according to the IP address configured by the GNE sub-interface.

For example, as shown in fig. 2, after the network manager 240 receives the information of the network element of the NE223 sent by the GNE 231. And allocating addresses according to the IP address pool planned by the user. (the user requires a different segment of the IP address for each VLAN). Specifically, allocating an IP address by the NE to be registered may include the following:

in the first way, an IP address is configured for the device (NE221) directly connected to the subinterface at GNE 231. The network management 240 determines the sub-interface corresponding to the VLAN identifier of the NE223, and allocates the first IP address of the device directly connected to the sub-interface to the NE223, for example, the IP address of the NE221 is 128.1.3.1/24, and then may allocate 128.1.3.1 an IP address of the same network segment that is not occupied by other network elements to the NE223, for example, the IP address allocated to the NE223 may be 128.1.3.4/24.

In the second mode, a corresponding relation table of VLAN identifications and address segments can be planned at a network manager, and different IP address segments corresponding to different VLAN identifications are planned. The network manager 240 allocates an IP address to the NE223 according to the correspondence between the IP address segment and the VLAN identifier of the NE223 sent by the GNE 231.

S350, the network manager sends the first IP address to the GNE through the second IP address of the NE to be registered.

S360, the GNE sends the first IP address to the NE to be registered using the second IP address of the NE to be registered.

S370, the GNE determines the non-DCN routing table entry corresponding to the NE to be registered according to the first IP address.

After determining the first IP address, the NE to be registered may notify the first IP address to other NEs, so that the other NEs establish their non-DCN connections with the NE to be registered according to the first IP address. Other NEs herein may include GNEs, among others.

In addition, after determining that the non-DCN connection between the GNE and the NE to be registered is established, the GNE may send a confirmation message to the network manager, so that the network manager manages the NE to be registered according to the first IP address of the NE to be registered. In particular, the NE to be registered may be marked as registered.

By the embodiment of the invention, the network manager can send the VLAN identification of the NE according to the GNE and the corresponding relation between the planned VLAN identification and the resources, so that the resources can be distributed to the NE, the NE registration process is simplified, and the network management efficiency of the network manager is improved.

With reference to the embodiment shown in fig. 3, in another embodiment, the network manager may obtain information, such as LLDP topology information, MAC address, ESN number, and device type, of the network element to be registered through the command line.

The network manager may determine a Link State (LS) of the network element to be registered according to one or more of the above information.

The network manager may configure the NE to be registered according to the LS of the NE to be registered, for example, the configuration of protocols such as telnet and SNMP in the non-DCN. The network manager can configure a non-DCN protocol in the DCN network. The network manager may also log in the NE to be registered through the first IP after the first IP allocation is completed, and further configure the registered network element (for example, configure a non-DCN protocol).

Fig. 5 is a schematic structural diagram of a network element management device in a DCN according to an embodiment of the present invention. The DCN comprises a network manager, a gateway network element GNE and a network element NE to be registered, and the device comprises:

a receiving module 501, configured to receive, by the GNE, information of the NE to be registered, where the information of the NE to be registered includes a VLAN identifier of the NE to be registered, and the VLAN identifier of the NE to be registered is a VLAN identifier corresponding to a sub-interface of the GNE connected to the NE to be registered.

A processing module 502, configured to allocate, according to the VLAN identifier, a first IP address in the VLAN network segment indicated by the VLAN identifier to the NE to be registered, where the first IP address indicates that the registration of the NE to be registered is completed at the network manager.

Optionally, the processing module 502 is further configured to,

determining an IP address field corresponding to the NE to be registered according to the corresponding relation between the VLAN identification and the IP address field;

and allocating the first IP address to the NE to be registered, wherein the first IP address is an unoccupied IP address in an IP address field corresponding to the NE to be registered.

Optionally, the processing module 502 is further configured to,

determining a GNE sub-interface corresponding to the VLAN identifier, wherein the GNE sub-interface is configured with an IP address;

and determining the corresponding relation between the VLAN identification and the IP address field according to the IP address configured by the GNE sub-interface.

Optionally, the information of the NE to be registered further includes a second IP address of the NE to be registered, where the second IP address is a factory-configured IP address of the NE to be registered, and the second IP address is used for the NE to be registered to communicate with the network manager in the DCN through the GNE; the device also includes:

a sending module 503, configured to send the first IP address to the NE to be registered through the GNE by using the second IP address, so that the GNE determines, according to the first IP address, a routing table entry of the non-DCN corresponding to the NE to be registered.

Fig. 6 is a schematic structural diagram of another network element management device in DCN according to an embodiment of the present invention. The DCN comprises a network manager, a gateway network element GNE and a network element NE to be registered, and the device comprises:

a receiving module 601, configured to receive a second IP address of the NE to be registered sent by the NE to be registered, where the second IP address is an IP address configured by the NE to be registered when leaving a factory;

a processing module 602, configured to determine, according to the second IP address, a VLAN identifier corresponding to the subinterface of the GNE connected to the NE to be registered, where the VLAN identifier is a VLAN identifier of the NE to be registered;

a sending module 603, configured to send information of the NE to be registered to the network manager, where the information of the NE to be registered includes the VLAN identifier, so that the network manager allocates, according to the VLAN identifier, a first IP address in a VLAN network segment indicated by the VLAN identifier to the NE to be registered, where the first IP address indicates that the registration of the NE to be registered is completed at the network manager.

Optionally, the information of the NE to be registered further includes the second IP address, and the receiving module 601 is further configured to receive the first IP address sent by the network manager, where the first IP address is sent by the network manager according to the second IP address;

the sending module 603 is further configured to send the first IP address to the NE to be registered by using the second IP address;

the processing module 602 is further configured to determine, according to the first IP address, a routing table entry of the non-DCN corresponding to the NE to be registered.

Fig. 7 is a schematic diagram of a GNE structure according to an embodiment of the present invention. As shown in fig. 7, GNE700 includes a transceiver 701, a processor 702, and a memory 703. The various units may be connected by a bus (not shown, but known to those skilled in the art).

The transceiver 701 may include a receiver and a transmitter, or may be a circuit that integrates receiving and transmitting functions to implement communication between the transceiver 701 and the NE and the network manager, where the transceiver 701 may include a plurality of interfaces, which are respectively connected to the network manager and the gateway. For example, the transceiver may include multiple ethernet interfaces. The memory 703 is used for storing program codes and data, such as routing tables, correspondence of VLAN identification to subinterface, etc. The processor 702 performs the operational steps in GNE in the embodiment shown in fig. 3 according to program instructions stored in the memory 703.

In addition, in the apparatus depicted in fig. 6, the functions of the receiving module and the transceiving module may be implemented by the transceiver in the embodiment of the present invention, and the functions of the processing module are implemented by the processor in the embodiment of the present invention.

Fig. 8 is a schematic structural diagram of a network manager according to an embodiment of the present invention. The network management 800 may include a transceiver 801, a processor 802, and a memory 803. The processor 802, transceiver 801, and memory 803 may be connected by a bus (not shown, but known to those skilled in the art) and communicate with each other. The transceiver 801 is configured to interact with a network element, and may include a receiving unit and a transmitting unit; the memory 803 is used to store programs and data. The processor 802 performs the functions of the network manager in the embodiment shown in fig. 3 by executing programs stored in the memory 803. For example, DCN management, IP address management, routing protocol management, etc., wherein IP address management includes IP address addressing, IP address assignment, etc.; routing protocol management includes routing protocol configuration, etc.

In addition, in the apparatus depicted in fig. 5, the functions of the receiving module and the transceiving module may be implemented by the transceiver in the embodiment of the present invention, and the functions of the processing module are implemented by the processor in the embodiment of the present invention.

It should be noted that the processor described in fig. 7 and fig. 8 may be a single processor, or may be a general term for multiple processing elements. For example, the processor may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement embodiments of the present invention.

The memory may be a storage device or a combination of storage elements, and is used for storing executable program codes or parameters, data, etc. required by the operation of the access network management device. And the memory 603 may include a Random Access Memory (RAM) or a non-volatile memory (non-volatile memory), such as a magnetic disk memory, a Flash memory (Flash), and the like. Wherein the processor-accessible memory may be integrated as processing circuitry.

The embodiment of the invention provides a DCN system, which comprises a network manager, a GNE and an NE to be registered. The network manager, the GNE and the NE to be registered in the system are respectively used for executing the operation steps corresponding to the network manager, the GNE and the NE to be registered in the embodiments shown in fig. 1-3.

Further, the network management in the system may be implemented as the network management in the embodiment shown in fig. 8, and the GNE may be implemented as the GNE in the embodiment shown in fig. 7.

The modules of the examples described in the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. Whether the elements and steps of the various embodiments are implemented in hardware or software in the above description depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied in hardware, a software module executed by a processor, or a combination of the two. The software modules may reside in RAM, ROM, a hard disk, an SSD, a CD-ROM, or any other form of storage medium.

The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention, and it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made on the basis of the present invention should be included in the scope of the present invention.

Claims

1. A network element management method in a data communication network DCN is characterized in that the DCN comprises a network manager, a gateway network element GNE and a network element NE to be registered, and the method comprises the following steps:

the network manager receives the information of the NE to be registered through the GNE, the information of the NE to be registered comprises a Virtual Local Area Network (VLAN) identifier of the NE to be registered, and the VLAN identifier of the NE to be registered is a VLAN identifier corresponding to a subinterface of the GNE connected with the NE to be registered;

and the network manager allocates a first IP address in the VLAN network segment indicated by the VLAN identifier to the NE to be registered according to the corresponding relation between the VLAN identifier and the IP address segment, wherein the first IP address represents that the NE to be registered is registered at the network manager, and the first IP address is an unoccupied IP address in the IP address segment.

2. The method of claim 1, wherein the network manager, according to the VLAN identifier, allocating a first IP address in the VLAN network segment indicated by the VLAN identifier to the NE to be registered comprises:

the network manager determines the IP address field corresponding to the NE to be registered according to the corresponding relation between the VLAN identifier and the IP address field;

and the network manager allocates the first IP address to the NE to be registered, wherein the first IP address is an unoccupied IP address in an IP address field corresponding to the NE to be registered.

3. The method of claim 2, wherein the network manager determines, according to the correspondence between the VLAN identifier and the IP address field, the IP address field corresponding to the NE to be registered, including:

the network manager determines a GNE sub-interface corresponding to the VLAN identifier, and the GNE sub-interface is configured with an IP address;

and the network manager determines the corresponding relation between the VLAN identification and the IP address section according to the IP address configured by the GNE sub-interface.

4. The method according to any of claims 1-3, wherein the information of the NE to be registered further comprises a second IP address of the NE to be registered, the second IP address being a factory configured IP address of the NE to be registered, the second IP address being used for the NE to be registered to communicate with the network manager in the DCN through the GNE; the method further comprises the following steps:

and the network manager uses the second IP address to send the first IP address to the NE to be registered through the GNE, so that the GNE determines the routing table entry of the non-DCN corresponding to the NE to be registered according to the first IP address.

5. A network element management method in a data communication network DCN is characterized in that the DCN comprises a network manager, a gateway network element GNE and a network element NE to be registered, and the method comprises the following steps: the GNE receives a second IP address of the NE to be registered, which is sent by the NE to be registered, wherein the second IP address is a factory-configured IP address of the NE to be registered; the GNE determines a VLAN identifier corresponding to a subinterface of the GNE connected with the NE to be registered according to the second IP address, wherein the VLAN identifier is the VLAN identifier of the NE to be registered;

and the GNE sends the information of the NE to be registered to the network manager, wherein the information of the NE to be registered comprises the VLAN identifier, so that the network manager allocates a first IP address in a VLAN network segment indicated by the VLAN identifier to the NE to be registered according to the corresponding relation between the VLAN identifier and an IP address segment, the first IP address represents that the NE to be registered is registered at the network manager, and the first IP address is an unoccupied IP address in the IP address segment.

6. The method of claim 5, wherein the information of the NE to be registered further comprises the second IP address, and wherein the method further comprises:

the GNE receives a first IP address of the NE to be registered, which is sent by the network manager, wherein the first IP address is sent by the network manager according to the second IP address;

the GNE sends the first IP address to the NE to be registered by using the second IP address;

and the GNE determines a non-DCN routing table entry corresponding to the NE to be registered according to the first IP address.

7. A network element management device in a data communication network DCN is characterized in that the DCN comprises a network manager, a gateway network element GNE and a network element NE to be registered, and the device comprises:

a receiving module, configured to receive, by the GNE, information of the NE to be registered, where the information of the NE to be registered includes a VLAN identifier of the NE to be registered, and the VLAN identifier of the NE to be registered is a VLAN identifier corresponding to a sub-interface of the GNE connected to the NE to be registered;

and the processing module is used for allocating a first IP address in the VLAN network segment indicated by the VLAN identifier to the NE to be registered according to the corresponding relation between the VLAN identifier and the IP address segment, wherein the first IP address represents that the NE to be registered is registered at the network management part, and the first IP address is an unoccupied IP address in the IP address segment.

8. The apparatus of claim 7, wherein the processing module is further configured to,

9. The apparatus of claim 8, the processing module further to,

10. The apparatus according to any of claims 7-9, wherein the information of the NE to be registered further comprises a second IP address of the NE to be registered, the second IP address being a factory configured IP address of the NE to be registered, the second IP address being used for the NE to be registered to communicate with the network manager in the DCN through the GNE; the device further comprises:

a sending module, configured to send the first IP address to the NE to be registered through the GNE by using the second IP address, so that the GNE determines, according to the first IP address, a routing table entry of the non-DCN corresponding to the NE to be registered.

11. A network element management device in a data communication network DCN is characterized in that the DCN comprises a network manager, a gateway network element GNE and a network element NE to be registered, and the device comprises:

a receiving module, configured to receive a second IP address of the NE to be registered, where the second IP address is an IP address configured by the NE to be registered when leaving a factory;

the processing module is used for determining a VLAN identifier corresponding to the subinterface of the GNE connected with the NE to be registered according to the second IP address, wherein the VLAN identifier is the VLAN identifier of the NE to be registered;

a sending module, configured to send information of the NE to be registered to the network manager, where the information of the NE to be registered includes the VLAN identifier, so that the network manager allocates, according to a correspondence between the VLAN identifier and an IP address field, a first IP address in a VLAN network segment indicated by the VLAN identifier to the NE to be registered, where the first IP address indicates that the NE to be registered is registered at the network manager, and the first IP address is an unoccupied IP address in the IP address field.

12. The apparatus according to claim 11, wherein the information of the NE to be registered further includes the second IP address, and the receiving module is further configured to receive the first IP address sent by the network manager, where the first IP address is sent by the network manager according to the second IP address;

the sending module is further configured to send the first IP address to the NE to be registered using the second IP address;

the processing module is further configured to determine, according to the first IP address, a routing table entry of the non-DCN corresponding to the NE to be registered.

13. A network manager, wherein the network manager is used in a data communication network DCN, and the DCN includes a network manager, a gateway network element GNE, and a network element NE to be registered, and the network manager includes:

a transceiver, configured to receive, by the GNE, information of the NE to be registered, where the information of the NE to be registered includes a VLAN identifier of the NE to be registered, and the VLAN identifier of the NE to be registered is a VLAN identifier corresponding to a sub-interface of the GNE connected to the NE to be registered;

and the processor is used for allocating a first IP address in the VLAN network segment indicated by the VLAN identifier to the NE to be registered according to the corresponding relation between the VLAN identifier and the IP address segment, wherein the first IP address represents that the NE to be registered is registered at the network management part, and the first IP address is an unoccupied IP address in the IP address segment.

14. The network manager of claim 13, wherein the processor is further configured to,

determining an IP address field corresponding to the NE to be registered according to the corresponding relation between the VLAN identification and the IP address field of the NE to be registered;

15. The network manager of claim 14, the processor further configured to,

16. The network manager according to any of claims 13-15, wherein the information of the NE to be registered further includes a second IP address of the NE to be registered, the second IP address is a factory configured IP address of the NE to be registered, and the second IP address is used for the NE to be registered to communicate with the network manager in the DCN through the GNE; the transceiver is also configured to,

and sending the first IP address to the NE to be registered through the GNE by using the second IP address, so that the GNE determines a routing table entry of the non-DCN corresponding to the NE to be registered according to the first IP address.

17. A gateway network element GNE, wherein the GNE is used in a data communication network DCN, and the DCN includes a network manager, a gateway network element GNE, and a network element NE to be registered, and the GNE includes:

the transceiver is configured to receive a second IP address of the NE to be registered, where the second IP address is an IP address configured by the NE to be registered when leaving a factory;

a processor, configured to determine, according to the second IP address, a VLAN identifier corresponding to the subinterface of the GNE connected to the NE to be registered, where the VLAN identifier is a VLAN identifier of the NE to be registered;

the transceiver is further configured to send information of the NE to be registered to the network manager, where the information of the NE to be registered includes the VLAN identifier, so that the network manager allocates a first IP address in a VLAN network segment indicated by the VLAN identifier to the NE to be registered according to a correspondence between the VLAN identifier and an IP address segment, where the first IP address indicates that the registration of the NE to be registered at the network manager is completed, and the first IP address is an unoccupied IP address in the IP address segment.

18. The GNE of claim 17, wherein the information of the NE to be registered further comprises the second IP address, and wherein the transceiver is further configured to receive the first IP address sent by the network manager, wherein the first IP address is sent by the network manager according to the second IP address; sending the first IP address to the NE to be registered by using the second IP address;

the processor is further configured to determine, according to the first IP address, a routing table entry of the non-DCN corresponding to the NE to be registered.

19. A DCN system for a data communication network, the DCN system comprising a network manager, a gateway network element GNE and a network element NE to be registered, wherein the network manager is configured to perform the method according to any one of claims 1 to 4; the gateway network element GNE is configured to perform the method of claim 5 or 6.