CN115996170A

CN115996170A - Network management system and network element communication method, device and system

Info

Publication number: CN115996170A
Application number: CN202111213783.8A
Authority: CN
Inventors: 刘斌; 孙小康; 邹知能
Original assignee: Beijing Huawei Digital Technologies Co Ltd
Current assignee: Beijing Huawei Digital Technologies Co Ltd
Priority date: 2021-10-19
Filing date: 2021-10-19
Publication date: 2023-04-21

Abstract

The embodiment of the application provides a network management system, a network element communication method, a network management device and a network element communication system. The method comprises the following steps: the network management system sends a query message to a gateway network element GNE in a second routing domain, wherein the query message is used for acquiring the routing information of a first non-gateway network element NGNE, the first NGNE is an NGNE to be registered, the routing domain where the network management system is located is a first routing domain, and the first routing domain is different from the second routing domain; the network management system receives a response message sent by the GNE in the second routing domain, wherein the response message indicates the routing information of the GNE in the second routing domain and the first NGNE communication; the network management system establishes communication connection with the first NGNE according to the response message. The method is also beneficial to improving the efficiency of establishing connection between the network management system and the network element on the premise of ensuring that the network management system can access the network element through a proper path.

Description

Network management system and network element communication method, device and system

Technical Field

The embodiments of the present application relate to network communication technology, and more particularly, to a network management system and a method, an apparatus, and a system for network element communication.

Background

The data communication network (data communication network, DCN) system is capable of providing communication functions for managing access, management control information for network devices, so that remote deployment and management of individual devices can be accomplished at the network management system (network management system, NMS) center. A DCN system is formed by NMS, gateway network elements (gateway network element, GNE) and non-gateway network elements (non gateway network element, NGNE) and the connection lines or networks between them. Wherein, the NMS and the GNE are connected and can be directly accessed with each other; the GNE and a plurality of NGNEs directly or indirectly connected with the GNE form a DCN routing domain, the GNE and the plurality of NGNEs in the DCN routing domain can directly access each other, and the GNE and the plurality of NGNEs in the DCN routing domain can realize message transmission based on a routing protocol.

In the current network application, a corresponding GNE is designated for each NGNE by means of manual planning, so that each NGNE communicates with the NMS through the corresponding GNE. As the network scale increases gradually, when an NGNE to be registered is newly added in the existing network, it is difficult to configure an appropriate GNE for the network element to be registered based on a manual planning method, so that a path of the NMS accessing the network element is not an optimal path, and there is a problem that the efficiency of establishing connection between the network management system and the network element is low. In addition, when a GNE fails (e.g., a pipe-out occurs), it is necessary to manually reselect the GNE for the NGNE to which the failed GNE corresponds. The existing network structure and the scale are generally complex, once faults occur, the faults are difficult to recover and manage for affected NGNE in a short time, the GNE is out of the management, the faults cannot be accurately reported in the first time, and the actual service recovery time is affected.

Disclosure of Invention

The embodiment of the application provides a network management system, a network element and a system thereof, and the method is beneficial to improving the efficiency of establishing connection between the network management system and the network element on the premise of ensuring that the network management system can access the network element through a proper path.

In a first aspect, a method for communicating between a network management system and a network element is provided, the method comprising: the network management system sends a query message to a gateway network element GNE in a second routing domain, wherein the query message is used for acquiring the routing information of a first non-gateway network element NGNE, the first NGNE is an NGNE to be registered, the routing domain where the network management system is located is a first routing domain, and the first routing domain is different from the second routing domain; the network management system receives a response message sent by the GNE in the second routing domain, wherein the response message indicates the routing information of the GNE in the second routing domain and the first NGNE communication; the network management system establishes communication connection with the first NGNE according to the response message.

In the above technical solution, the network management system in the first routing domain may actively query the GNE in the second routing domain for the routing information of the first NGNE to be registered, and establish a communication connection with the first NGNE according to the obtained routing information of the first NGNE to be registered. The routing information of the first NGNE to be registered includes routing information of each GNE communication in the first NGNE to be registered and the second routing domain. When the network management system determines to establish communication connection with the first NGNE, the network management system fully considers the route information of each GNE communication in the first NGNE and the second routing domain, so that the network management system can access the network element through a proper path. In addition, in the implementation manner, the determination of the GNE for the first NGNE to be registered based on a manual mode is avoided, and the connection efficiency between the network management system and the network element is improved. That is, the method is also beneficial to improving the efficiency of establishing connection between the network management system and the network element on the premise of ensuring that the network management system can access the network element through a proper path.

In one possible design, the query message includes a first internet protocol IP address, the first IP address being a preset IP address of the first NGNE, the first IP address being used for the first NGNE to establish a communication connection with the GNE in the second routing domain.

In one example, the preset IP address of the first NGNE may refer to a factory configured IP address of the first NGNE, where in this implementation, the preset IP address of the first NGNE is the factory configured IP address of the first NGNE. In another example, the preset IP address of the first NGNE may also refer to an IP address set by the user for the first NGNE according to the IP address of the factory configuration of the first NGNE, where in this implementation, the preset IP address of the first NGNE is different from the IP address of the factory configuration of the first NGNE. That is, in the present application, the preset IP address of the first NGNE is not particularly limited.

In another possible design, the second routing domain includes a first GNE, the response message includes a first response message, the first response message is used to indicate first routing information of the first GNE for communication with the first NGNE, the first routing information includes an identification of a first port, a first network element identifier NEID and the first IP address, the first port is a port of the first GNE to which the first NGNE is connected, the first NEID corresponds to the first IP address, the first NEID is used to uniquely identify the first NGNE, and the network management system establishes a communication connection with the first NGNE according to the response message, including: the network management system generates second routing information according to the second IP address, the first NEID and the identification of the first port, the second IP address is used for uniquely identifying the first GNE, the second IP address is an IP address utilized when the first GNE establishes communication connection with the network management system, the second routing information indicates that the first NGNE is registered in the network management system, the second routing information comprises the second IP address, and the mapping relation between the first NEID and the first port is achieved.

In another possible design, the second routing domain further includes a second GNE, the response message further includes a second response message indicating third routing information of the second GNE for communication with the first NGNE, the third routing information including a second routing overhead, and before the network management system establishes a communication connection with the first NGNE according to the response message, the method further includes: the network management system determines that the first GNE is a primary GNE of the first NGNE and determines that the second GNE is a standby GNE of the first NGNE according to a first routing overhead and the second routing overhead, and the first routing information further includes the first routing overhead.

In the above technical solution, the network management system determines that the first GNE is the active GNE of the first NGNE and determines that the second GNE is the standby GNE of the first NGNE by comparing the first routing overhead with the second routing overhead, so that the network management system can access the network element through a suitable path.

In another possible design, the third routing information further includes an identification of a second port and the first NEID, the second port is a port of the second GNE connected to the first NGNE, and the network management system establishes a communication connection with the first NGNE according to the response message, including: in the case that the first GNE fails, the network management system generates fourth routing information according to a third IP address, the first NEID, the identification of the second port, and the second routing overhead, where the third IP address is used to uniquely identify the second GNE, the third IP address is an IP address that is used when the second GNE establishes a communication connection with the network management system, the fourth routing information indicates that the first GNE is registered at the network management system, and the fourth routing information includes a mapping relationship between the third IP address, the first NEID, the second port, and the second routing overhead.

Wherein the third IP address is different from the second IP address.

In the above technical solution, under the condition that the first GNE fails, the network management system can establish communication connection with the first NGNE through the standby GNE (i.e., the second GNE) of the first NGNE, which is beneficial to improving the efficiency of establishing connection between the network management system and the network element.

In another possible design, the first routing overhead is determined based on at least one of: the path information from the first GNE to the first NGNE, the loading condition of the first GNE, or the delay information from the first GNE to the first NGNE; the second routing overhead is determined from at least one of the following information: the path information from the second GNE to the first NGNE, the loading condition of the second GNE, or the delay information from the second GNE to the first NGNE.

In the above technical solution, the first routing overhead and the second routing overhead may be determined according to actual requirements, so that the network management system may access the network element through a suitable path. For example, if the path length of the network management system accessing the first NGNE needs to be minimized, the first routing overhead may be determined only according to the path information from the first GNE to the first NGNE, and the second routing overhead may be determined only according to the path information from the second GNE to the first NGNE.

In a second aspect, there is provided a method of communicating between a network management system and a network element, the method comprising: after a first gateway network element GNE and a first non-gateway network element NGNE establish communication connection, the first GNE receives a query message sent by a network management system, the query message is used for acquiring routing information of the first NGNE, the first NGNE is an NGNE to be registered, a routing domain where the network management system is located is a first routing domain, a second routing domain comprises the first GNE and the first NGNE, and the first routing domain is different from the second routing domain; the first GNE generates a first response message according to the query message and the routing table of the first GNE, where the first response message indicates first routing information of the first GNE to communicate with the first NGNE. The first GNE sends the first response message to the network management system.

In the above technical solution, after receiving the query message sent by the network management system in the first routing domain, the first GNE in the second routing domain may send the first routing information that the first GNE communicates with the first NGNE to the network management system, so that the network management system can determine a suitable path for the network management system to access the first NGNE based on the first routing information. In addition, in the implementation manner, manual participation is avoided, and the efficiency of establishing connection between the network management system and the network element is improved.

In one possible design, the query message includes a first internet protocol IP address, the first IP address being a preset IP address of the first NGNE, the first IP address being used for establishing a communication connection with GNEs in the second routing domain, the GNEs in the second routing domain including the first GNE.

In another possible design, a first correspondence is recorded in a routing table of the first GNE, where the first correspondence is a correspondence between a first network element identifier NEID and the first IP address, the first NEID is used to uniquely identify the first NGNE, and the first GNE generates a first response message according to the query message and the routing table of the first GNE, and includes: the first GNE determines the first NEID according to the first IP address and the first corresponding relation; the first GNE determines the communication path information of the first GNE and the first NGNE according to a second IP address and the first NEID, wherein the second IP address is used for uniquely identifying the first GNE, and is an IP address utilized when the first GNE establishes communication connection with the network management system; the first GNE generates the first response message according to the path information.

In another possible design, the first routing information includes an identification of a first port, a first routing overhead, the first NEID and the first IP address, the first port being a port of the first GNE to which the first NGNE is connected, the first routing overhead being a routing overhead for the first GNE to communicate with the first NGNE.

In another possible design, the first routing overhead is determined based on at least one of: the path information from the first GNE to the first NGNE, the loading condition of the first GNE, or the delay information from the first GNE to the first NGNE.

In a third aspect, there is provided a first communication device for use in a network management system, the device comprising: a transceiver unit, configured to send a query message to a gateway network element GNE in a second routing domain, where the query message is used to obtain routing information of a first non-gateway network element NGNE, the first NGNE is an NGNE to be registered, and a routing domain where the network management system is located is a first routing domain, where the first routing domain is different from the second routing domain; the transceiver unit is further configured to receive a response message sent by the GNE in the second routing domain, where the response message indicates routing information of the GNE in the second routing domain to communicate with the first NGNE; and the processing unit is used for establishing communication connection with the first NGNE according to the response message.

In another possible design, the second routing domain further includes a second GNE, the response message further includes a second response message indicating third routing information for the second GNE to communicate with the first NGNE, the third routing information including a second routing overhead, and the processing unit is further configured to: according to the first routing overhead and the second routing overhead, determining that the first GNE is a primary GNE of the first NGNE, and determining that the second GNE is a standby GNE of the first NGNE, wherein the first routing information further includes the first routing overhead.

In another possible design, the third routing information further includes an identification of a second port and the first NEID, the second port being a port of the second GNE to which the first NGNE is connected, the processing unit further configured to: in the case that the first GNE fails, generating fourth routing information according to a third IP address, the first NEID, the identification of the second port, and the second routing overhead, where the third IP address is used to uniquely identify the second GNE, the third IP address is an IP address that is used when the second GNE establishes a communication connection with the network management system, and the fourth routing information indicates that the first NGNE is registered in the network management system, and the fourth routing information includes a mapping relationship among the third IP address, the first NEID, the second port, and the second routing overhead.

In a fourth aspect, a second communication device is provided, where the second communication device is applied in a first gateway network element GNE, the device includes: a transceiver unit, configured to receive, after the first GNE establishes a communication connection with a first non-gateway network element NGNE, a query message sent by a network management system, where the query message is used to obtain routing information of the first NGNE, the first NGNE is an NGNE to be registered, a routing domain where the network management system is located is a first routing domain, and a second routing domain includes the first GNE and the first NGNE, where the first routing domain is different from the second routing domain; a processing unit, configured to generate a first response message according to the query message and the routing table of the first GNE, where the first response message indicates first routing information of the first GNE to communicate with the first NGNE; the transceiver unit is further configured to send the first response message to the network management system.

In another possible design, a first correspondence is recorded in the routing table of the first GNE, where the first correspondence is a correspondence between a first network element identifier NEID and the first IP address, where the first NEID is used to uniquely identify the first nne, and the processing unit is further configured to: determining the first NEID according to the first IP address and the first corresponding relation; determining the communication path information of the first GNE and the first NGNE according to a second IP address and the first NEID, where the second IP address is used to uniquely identify the first GNE, and the second IP address is an IP address utilized when the first GNE establishes communication connection with the network management system; and generating the first response message according to the path information.

In another possible design, the first routing information includes an identification of a first port, a first routing overhead, the first NEID, and the first IP address, the first port being a port of the first GNE to which the first NGNE is connected, the first routing overhead being a routing overhead for the first GNE to communicate with the first NGNE.

In a fifth aspect, there is provided a first communication apparatus having a function of implementing the first communication device described in the third aspect. The functions can be realized on the basis of hardware, and can also be realized on the basis of hardware by executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In one possible design, the first communication device includes a processor in its structure configured to support the first communication device to perform the corresponding functions of the above-described method.

The first communication device may also include a memory for coupling with the processor that holds the program instructions and data necessary for the first communication device.

In another possible design, the first communication device includes: processor, transmitter, receiver, random access memory, read only memory, and bus. The processor is coupled to the transmitter, the receiver, the random access memory and the read-only memory through buses, respectively. When the first communication equipment needs to be operated, the first communication equipment is guided to enter a normal operation state by starting a basic input/output system solidified in a read-only memory or a bootloader guiding system in an embedded system. After the first communication device enters a normal operating state, the application and the operating system are run in random access memory, causing the processor to perform the method of the first aspect or any of the possible implementations of the first aspect.

In a sixth aspect, there is provided a second communication apparatus having a function of implementing the second communication device described in the fourth aspect. The functions can be realized on the basis of hardware, and can also be realized on the basis of hardware by executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In one possible design, the structure of the second communication device includes a processor configured to support the second communication device to perform the corresponding functions of the above-described method.

The second communication device may also include a memory for coupling with the processor that holds the program instructions and data necessary for the second communication device.

In another possible design, the second communication device includes: processor, transmitter, receiver, random access memory, read only memory, and bus. The processor is coupled to the transmitter, the receiver, the random access memory and the read-only memory through buses, respectively. When the second communication equipment needs to be operated, the second communication equipment is guided to enter a normal operation state by starting a basic input/output system solidified in a read-only memory or a bootloader guiding system in an embedded system. After the second communication device enters a normal operating state, the application and the operating system are run in random access memory, causing the processor to perform the method of the second aspect or any of the possible implementations of the second aspect.

In a seventh aspect, there is provided a computer program product comprising: computer program code which, when run on a computer, causes the computer to perform the above-described first aspect or any one of the possible methods of the first aspect.

In an eighth aspect, there is provided a computer program product comprising: computer program code which, when run on a computer, causes the computer to perform the second aspect or any of the possible methods of the second aspect described above.

In a ninth aspect, there is provided a computer readable medium having stored thereon a program code which, when run on a computer, causes the computer to perform the above-described first aspect or any one of the possible methods of the first aspect. These computer-readable stores include, but are not limited to, one or more of the following: read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), flash memory, electrically EPROM (EEPROM), and hard disk drive (hard drive).

In a tenth aspect, there is provided a computer readable medium having stored thereon a program code which, when run on a computer, causes the computer to perform the second aspect or any one of the possible methods of the second aspect described above. These computer-readable stores include, but are not limited to, one or more of the following: read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), flash memory, electrically EPROM (EEPROM), and hard disk drive (hard drive).

In an eleventh aspect, a chip system is provided, the chip system comprising a processor and a data interface, wherein the processor reads instructions stored on a memory through the data interface to perform the method of the first aspect or any one of the possible implementation manners of the first aspect. In particular implementations, the system-on-chip may be implemented in the form of a central processing unit (central processing unit, CPU), microcontroller (micro controller unit, MCU), microprocessor (micro processing unit, MPU), digital signal processor (digital signal processing, DSP), system-on-chip (SoC), application-specific integrated circuit (ASIC), field programmable gate array (field programmable gate array, FPGA), or programmable logic device (programmable logic device, PLD).

In a twelfth aspect, a chip system is provided, the chip system comprising a processor and a data interface, wherein the processor reads instructions stored on a memory through the data interface to perform the method of the second aspect or any one of the possible implementation manners of the second aspect. In particular implementations, the system-on-chip may be implemented in the form of a central processing unit (central processing unit, CPU), microcontroller (micro controller unit, MCU), microprocessor (micro processing unit, MPU), digital signal processor (digital signal processing, DSP), system-on-chip (SoC), application-specific integrated circuit (ASIC), field programmable gate array (field programmable gate array, FPGA), or programmable logic device (programmable logic device, PLD).

In a thirteenth aspect, there is provided a system comprising the first communication device according to the third aspect and the second communication device according to the fourth aspect.

Drawings

Fig. 1 is a schematic block diagram of a system architecture 100 provided by an embodiment of the present application.

Fig. 2 is a schematic flow chart of a method 200 for communication between a network management system and a network element according to an embodiment of the present application.

Fig. 3 is a schematic interaction diagram of a method for communication between a network management system and a network element according to an embodiment of the present application.

Fig. 4 is a schematic interaction diagram of another method for communication between a network management system and a network element according to an embodiment of the present application.

Fig. 5 is a schematic diagram of a specific embodiment of a method for communication between a network management system and a network element according to an embodiment of the present application.

Fig. 6 is a schematic diagram of a specific embodiment of a method for communication between a network management system and a network element according to an embodiment of the present application.

Fig. 7 is a schematic structural diagram of a first communication device 700 provided in an embodiment of the present application.

Fig. 8 is a schematic structural diagram of a second communication device 800 provided in an embodiment of the present application.

Fig. 9 is a schematic hardware structure of a communication device 900 according to an embodiment of the present application.

Fig. 10 is a schematic block diagram of a system 1000 provided in an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

The terminology used in the description section of the present application is for the purpose of describing particular embodiments of the present application only and is not intended to be limiting of the present application.

The terms "first," "second," "third," and the like in this application are used for distinguishing between similar elements or similar elements having substantially the same function and function, and not necessarily for describing a logical or chronological relationship between the terms "first," "second," and "third," and not necessarily for limiting the number or order of execution.

The present application will present various aspects, embodiments, or features about a system that may include multiple devices, components, modules, etc. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. Furthermore, combinations of these schemes may also be used.

In addition, in the embodiments of the present application, words such as "exemplary," "for example," and the like are used to indicate an example, instance, or illustration. Any embodiment or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, the term use of an example is intended to present concepts in a concrete fashion.

The network architecture and the service scenario described in the embodiments of the present application are for more clearly describing the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided in the embodiments of the present application, and those skilled in the art can know that, with the evolution of the network architecture and the appearance of the new service scenario, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.

Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.

In the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural.

The following specifically describes the related art of the embodiments of the present application:

first, a system architecture applicable to the embodiment of the present application is described with reference to fig. 1.

Fig. 1 is a schematic block diagram of a system architecture 100 provided by an embodiment of the present application. As shown in fig. 1, the system architecture 100 includes, but is not limited to, a plurality of routing domains, fig. 1 is illustrated by taking a routing domain 1 and a routing domain 2 as an example, wherein the system architecture 100 includes: routing domain 1, internetworking protocol (internet protocol, IP) carries network 120 and routing domain 2. Network devices in any one routing domain can diffuse routes of the network devices except the network devices in any one routing domain in a route forwarding mode.

The routing domain 1 includes, but is not limited to, a network management system (network management system, NMS), also known as a network management system. The NMS may provide sophisticated network element and network level alarms, security, performance, topology, logging, inventory, reporting, database management functions in the manner of graphical user interface (graphical user interface, GUI) operations. The NMS supports batch configuration of network element services by means of configuration templates, importing data tables and loading configuration files, and supports operations such as backup, recovery and synchronization of network management and network element data, so that quick service distribution can be conveniently and rapidly realized in a GUI (graphical user interface) mode. Illustratively, only one NMS110 is included within the routing domain 1 shown in fig. 1. Optionally, a plurality of NMSs may also be included in the routing domain 1. NMS within routing domain 1 may implement communication with gateway network elements (gateway network element, GNE) within routing domain 2 via IP bearer network 120. The NMS within routing domain 1 and the GNE within routing domain 2 may communicate, but are not limited to, via a transmission control protocol (transmission control protocol, TCP), the communication between the NMS and gateway network elements also being referred to as external DCN communication. Optionally, when a plurality of NMSs are included within the routing domain 1, the external DCN communications also include communications between the plurality of NMSs.

Included within routing domain 2 are, but not limited to, GNE, DCN140, and NGNE, which may be collectively referred to as network elements. GNE refers to a network element directly connected to a network management system, or refers to a network element application layer directly communicating with a network management system application layer. NGNE refers to a network element that communicates with GNEs and satisfies GNE management. The GNE and NGNE communicate based on DCN140 using an ethernet-based point-to-point protocol over ethernet (PPPoE) protocol, and communications between network elements are also referred to as internal DCN communications. By way of example, 2 GNEs (i.e., gne.a130 and gne.b 131) are shown in fig. 1, and 2 NGNEs (i.e., ngne.a151 and ngne.b 152) that may all be in communication with ngne.a151 or ngne.b152, or only one GNE of the 2 GNEs may be in communication with ngne.a151 or ngne.b 152. Alternatively, fewer (e.g., 1) or greater (e.g., 3, 4, or 10, etc.) numbers of GNEs and NGNEs may also be included within routing domain 2.

Based on the system architecture 100 shown in fig. 1 above, nms110 may access NGNEs (e.g., NGNE. A151 or NGNE. B152) through GNEs (e.g., GNE. A130 or GNE. B131). Wherein the NMS110 may access the NGNE through the IP address of the GNE and the network element identifier (network element identifier, NEID) of the NGNE. The NEID of one NGNE corresponds to the factory-configured IP address of the one NGNE, the one NGNE can establish a communication connection with the GNE by using the factory-configured IP address of the one NGNE, and then a correspondence is recorded in the routing table of the GNE, where the correspondence is between the NEID of the one NGNE and the factory-configured IP address of the one NGNE. When the NMS110 accesses the NGNE through the GNE, the NMS110 finds the GNE by using the IP address of the GNE, then the GNE determines the destination IP corresponding to the destination NEID according to the destination NEID carried in the message sent by the NMS110 and the correspondence between the NEID and the IP address recorded in the routing table, and then the GNE successfully finds the destination NGNE based on the destination IP, so as to realize that the NMS110 accesses the NGNE through the GNE.

It should be understood that fig. 1 is merely illustrative, and does not constitute any limitation on the system architecture applicable to the embodiments of the present application. For example, a greater number of GNEs or NGNEs may also be included within routing domain 2 in fig. 1. As another example, a greater number of NMSs may also be included within routing domain 1 in fig. 1. As another example, ngne.a 151 and/or ngne.b 152 in fig. 1 may also be an NGNE to be registered.

Fig. 2 is a schematic flow chart of a method 200 for communication between a network management system and a network element according to an embodiment of the present application. The method 200 may be applied, but is not limited to, to the system architecture 100 shown in fig. 1 and described above. When the method 200 is applied to the system architecture 100, the network management system in the method 200 may be the NMS110 in the system architecture 100, the first GNE in the method 200 may be the gne.a 130 in the system architecture 100, the second GNE in the method 200 may be the gne.b 140 in the system architecture 100, and the first NGNE in the method 200 may be the ngne.b 152 in the system architecture 100 (at this time, the ngne.b 152 in the system architecture 100 is the NGNE to be registered). As shown in fig. 2, the method 200 includes steps 210 through 230. Next, steps 210 to 230 are described.

Step 210, the network management system sends a query message to the gateway network element GNE in the second routing domain, where the query message is used to obtain routing information of the first non-gateway network element NGNE, the first NGNE is an NGNE to be registered, and a routing domain where the network management system is located is a first routing domain, where the first routing domain is different from the second routing domain.

In step 210, the network management system may periodically send a query message to the GNE in the second routing domain to obtain the routing information of the first NGNE. The time length of the cycle is not particularly limited, and may be, for example, 1 hour, 2 hours, 5 hours, or the like.

In step 220, the network management system receives a response message sent by the GNE in the second routing domain, where the response message indicates routing information for the GNE in the second routing domain to communicate with the first NGNE.

In step 230, the network management system establishes a communication connection with the first NGNE according to the response message.

In some implementations, the second routing domain in the above method 200 may include only one GNE (i.e., the first GNE) in communication with the first NGNE, and for convenience of description, such an implementation will be referred to as implementation one hereinafter. The method of the first implementation will be specifically described with reference to fig. 3, and will not be described in detail herein.

In other implementations, the second routing domain in the method 200 may include a plurality of GNEs in communication with the first NGNE, and for convenience of description, such an implementation will be hereinafter referred to as implementation two. The method of implementation two will be specifically described with reference to fig. 4, and will not be described in detail here.

The following describes the method of implementation one and implementation two in detail.

The implementation mode is as follows:

as shown in fig. 3, when the second routing domain may include only one GNE (i.e., the first GNE) in communication with the first NGNE, implementation one may include steps 310 through 340. Optionally, an implementation may further include step 350 and step 360. Next, there are introduced steps 310 to 360.

In step 310, the network management system sends a query message to the first GNE, where the query message is used to obtain routing information of a first non-gateway network element NGNE, the first NGNE is an NGNE to be registered, and a routing domain where the network management system is located is a first routing domain, where the first routing domain is different from the second routing domain.

The query message in step 310 includes a first IP address, where the first IP address is a preset IP address of the first NGNE, and the first IP address is used to establish a communication connection between the first NGNE and the first GNE.

Optionally, step 350 and step 360 may also be included before step 310. The execution sequence of steps 350 and 360 is not particularly limited. For example, step 350 may be performed prior to step 360. As another example, step 360 may be performed prior to step 350. Steps 350 and 360 are described below.

In this embodiment of the present application, the preset IP address of the first NGNE may refer to an IP address of the first NGNE in factory configuration, where in this implementation manner, the preset IP address of the first NGNE is the IP address of the first NGNE in factory configuration. In another example, the preset IP address of the first NGNE may also refer to an IP address set by the user for the first NGNE according to the IP address of the factory configuration of the first NGNE, where in this implementation, the preset IP address of the first NGNE is different from the IP address of the factory configuration of the first NGNE. That is, in the present application, the preset IP address of the first NGNE is not particularly limited.

In step 350, the first GNE establishes a communication connection with the first NGNE using a first IP address, where the first IP address is a preset IP address of the first NGNE.

Wherein, the establishing the communication connection with the first NGNE by the first GNE using the first IP address may include the following steps: the first NGNE accesses the DCN in the second routing domain by using the first IP address, and the first NGNE learns the first IP address through the communication port of the first NGNE and the GNE in the second routing domain and/or the NGNE runs the routing protocol (such as but not limited to an open shortest path first (open shortest path first, OSPF) protocol, and the first IP address is distributed outwards, and the first NGNE learns the route from the GNE and/or the NGNE in the second routing domain, but the first NGNE does not sense the role and the position of the first GNE in the second routing domain, and simultaneously the first GNE in the second routing domain learns the first IP address through the route distribution, and thereafter, the first GNE can access the first NGNE by using the first IP address, namely the first GNE and the first NGNE establish communication connection with the first NGNE.

In step 360, the network management system establishes a communication connection with the first GNE using a second IP address, where the second IP address is used to uniquely identify the first GNE.

Wherein the second IP address is used to uniquely identify the first GNE. The manner in which the network management system establishes a communication connection with the first GNE using the second IP address is not particularly limited. In some implementations, the network management system establishing a communication connection with the first GNE using the second IP address may include the steps of: the network management system receives an access request message sent by the first GNE, wherein the access request message is used for requesting to establish communication connection with the network management system by using a second IP address, and the access request message comprises the second IP address; the network management system establishes a communication connection with the first GNE through the second IP address. Optionally, the access request message may further carry a port identifier of the first GNE. Based on this, the network management system may establish a communication connection with the first GNE through the second IP address and the port identification of the first GNE. It will be appreciated that after the network management system establishes a connection with the first GNE, the network management system records information for establishing a communication connection with the first GNE, where the information includes at least the second IP address. Optionally, the information may further include a port identification of the first GNE. It will be appreciated that the network management system is in communication with the first GNE, and the network management system is configured to manage the first GNE.

In step 320, the first GNE generates a first response message according to the query message and the routing table of the first GNE, where the first response message indicates the first routing information of the first GNE to communicate with the first NGNE.

In the step 320, the first GNE generates a first response message according to the query message and the routing table of the first GNE, and may include the following steps: the first GNE determines a first NEID according to the first IP address and the first corresponding relation; the first GNE determines the communication path information of the first GNE and the first NGNE according to a second IP address and a first NEID, wherein the second IP address is used for uniquely identifying the first GNE, and is an IP address utilized when the first GNE establishes communication connection with the network management system; the first GNE generates a first response message according to the path information.

Wherein the first routing information includes an identification of the first port, a first routing cost (cost), a first NEID, and a first IP address, the first routing cost being a routing cost of the first GNE to the first NGNE communication. The first routing overhead is determined from at least one of the following information: the path information from the first GNE to the first NGNE, the loading condition of the first GNE, or the delay information from the first GNE to the first NGNE. The loading situation of the first GNE may be understood as the number of NGNEs communicating with the first GNE, and may also be understood as the number of NGNEs managed by the first GNE. It will be appreciated that the first GNE communicates with one NGNE, and that the first GNE is then used to manage the one NGNE.

Alternatively, in other implementations, when the first GNE does not successfully establish communication with the first NGNE, i.e., the first correspondence is not recorded in the routing table of the first GNE. In this implementation, the first GNE generates a first response message according to the query message and the routing table of the first GNE, where the first response message is used to indicate that the routing domain where the first GNE and the first NGNE are located are different.

In step 330, the network management system receives the first response message sent by the first GNE.

In step 340, the network management system establishes a communication connection with the first NGNE according to the first response message.

In the step 340, the network management system establishes a communication connection with the first NGNE according to the response message, including: the network management system generates second routing information according to the second IP address, the first NEID and the identification of the first port, wherein the second routing information indicates that the first NGNE is registered in the network management system, and the second routing information comprises the second IP address and the mapping relation between the first NEID and the first port.

Optionally, after the step 340, the following steps may be further included: the network management system creates a management instance of the first NGNE. The network management system creates a management instance of the first NGNE, which can be understood as a software behavior. In particular, the network management system allocates a memory for the first NGNE, where the memory is used to store information about the communication of the first NGNE, and content such as a current presentable state configuration, and presents the content in a visual manner.

Optionally, after the step 340, the following steps may be further included: the network management system may also determine, based on the first routing information, whether the network management system is reachable to the first NGNE via the first GNE. For example, the network management system may generate a probe packet according to the first routing information, and periodically send the probe packet to the first GNE and the first NGNE, where the probe packet may include the second IP address and/or the first NEID; the network management system receives the responses of the first GNE and the first NGNE within a preset time, and determines that the first NGNE is reachable through the first GNE. Optionally, the network management system does not receive the responses of the first GNE and the first NGNE within a preset time, and determines that the first NGNE is not reachable through the first GNE, where the network management system may consider that the first GNE and the first NGNE take out of management.

The implementation mode II is as follows:

in implementation two, the second routing domain may include a plurality of GNEs in communication with the first NGNE. As shown in fig. 4, it is shown that all 2 GNEs (i.e., a first GNE and a second GNE) within the second routing domain can communicate with the first NGNE. Referring to fig. 4, implementation two may include steps 410 to 450. Optionally, implementation two may further include steps 460 to 480. Steps 410 to 480 are described in detail below.

In this embodiment of the present application, the routing domain where the network management system is located is a first routing domain, the routing domain where the first GNE, the second GNE, and the first NGNE are located is a second routing domain, and the first routing domain is different from the second routing domain.

In step 410, the network management system sends a query message to the first GNE, where the query message is used to obtain routing information of the first NGNE, and the first NGNE is an NGNE to be registered.

The query message in step 410 includes a first IP address, where the first IP address is a preset IP address of the first NGNE, and the first IP address is used to establish a communication connection between the first NGNE and the first GNE.

Optionally, step 460, step 461 and step 470 may also be performed before step 410 described above. The execution sequence of step 460, step 461 and step 470 is not particularly limited. For example, step 470 may be performed before step 460. As another example, step 460 may be performed prior to step 470. Steps 460 and 470 are described below.

In step 460, the first GNE establishes a communication connection with the first NGNE using a first IP address, where the first IP address is a preset IP address of the first NGNE.

It can be understood that, after the first GNE establishes a communication connection with the first NGNE, a first correspondence is recorded in the routing table of the first GNE, where the first correspondence is a correspondence between the first network element identifier NEID and the first IP address, and the first NEID is used to uniquely identify the first NGNE. The first NEID refers to a device identification of the first NGNE.

In step 461, the second GNE establishes a communication connection with the first NGNE using the first IP address.

It will be appreciated that after the second GNE establishes a communication connection with the first NGNE, the first correspondence is recorded in the routing table of the second GNE.

The method for establishing a communication connection in the step 460 and the step 461 are the same as the method for establishing a communication connection in the step 350, and specifically, reference may be made to the description related to the step 350, which is not repeated here in detail.

In step 470, the network management system establishes a communication connection with the first GNE using a second IP address, and the network management system establishes a communication connection with the second GNE using a third IP address, where the second IP address is used to uniquely identify the first GNE and the third IP address is used to uniquely identify the second GNE.

Wherein the third IP address is different from the second IP address.

The method for establishing the communication connection in step 470 is the same as the method for establishing the communication connection in step 360, and specifically, reference may be made to the description related to step 360, which is not repeated here in detail.

In step 411, the network management system sends a query message to the second GNE.

In step 420, the first GNE generates a first response message according to the query message and the routing table of the first GNE, where the first response message indicates the first routing information of the first GNE to communicate with the first NGNE.

The method described in step 420 is the same as the method described in step 320, and specific reference may be made to the description related to step 320, which is not repeated here in detail.

In step 421, the second GNE generates a second response message according to the query message and the routing table of the second GNE, where the second response message indicates third routing information of the second GNE for communicating with the first NGNE.

In step 421, the second GNE generates a second response message according to the query message and the routing table of the first GNE, and may include the following steps: the second GNE determines a first NEID according to the first IP address and the first corresponding relation; the second GNE determines the communication path information of the second GNE and the first NGNE according to a third IP address and a first NEID, wherein the third IP address is used for uniquely identifying the second GNE, and is an IP address utilized when the second GNE establishes communication connection with the network management system; the second GNE generates a second response message according to the path information.

Wherein the second response message indicates third routing information of the second GNE communicating with the first NGNE, the third routing information including second routing overhead, i.e., the second routing overhead is the routing overhead of the second GNE communicating with the first NGNE. The second routing overhead may be determined based on at least one of: path information from the second GNE to the first NGNE, loading condition of the second GNE, or delay information from the second GNE to the first NGNE.

Optionally, the third routing information further includes an identification of a second port and the first NEID, and the second port is a port of a second GNE connected by the first NGNE.

In the embodiment of the present application, the execution sequence of the steps 410 to 421 is not specifically limited, but it is required to ensure that the step 410 is executed before the step 420 and the step 411 is executed before the step 421.

In step 430, the first GNE sends a first response message to the network management system.

In step 431, the second GNE sends a second response message to the network management system.

In step 440, the network management system determines that the first GNE is a primary GNE of the first NGNE and determines that the second GNE is a standby GNE of the first NGNE according to a response message, where the response message includes the first response message and the second response message.

The network management system determines that the first GNE is a primary GNE of the first NGNE and determines that the second GNE is a standby GNE of the first NGNE according to the response message, including: the network management system determines that the first GNE is a primary GNE of the first NGNE and determines that the second GNE is a standby GNE of the first NGNE according to the first routing overhead and the second routing overhead, and the first routing information further includes the first routing overhead.

For example, the network management system determines that the first GNE is a primary GNE of the first NGNE and determines that the second GNE is a backup GNE of the first NGNE based on the first routing overhead and the second routing overhead. For example, in the case where the first routing overhead is determined from the first GNE to the path information of the first NGNE and the second routing overhead is determined from the second GNE to the path information of the first NGNE, the network management system determines that the first GNE is the primary GNE of the first NGNE and that the second GNE is the backup GNE of the first NGNE by comparing the values of the first routing overhead determined to be smaller than the values of the second routing overhead. The value of the first routing overhead is smaller than the value of the second routing overhead, which is understood as that the path length from the first GNE indicated by the value of the first routing overhead to the first NGNE is smaller than the path length from the second GNE indicated by the value of the second routing overhead to the first NGNE. For another example, where the first routing overhead is determined based on a loading condition of the first GNE and the second routing overhead is determined based on a loading condition of the second GNE, the network management system determines that the first GNE is a primary GNE of the first GNE and that the second GNE is a backup GNE of the first GNE by comparing the values of the first routing overhead and the second routing overhead. Wherein the value of the first routing overhead is smaller than the value of the second routing overhead, it is understood that the load of the first GNE indicated by the value of the first routing overhead is smaller than the load of the second GNE indicated by the value of the second routing overhead. For another example, in the case where the first routing overhead is determined based on the delay information of the first GNE to the first NGNE and the second routing overhead is determined based on the delay information of the second GNE to the first NGNE, the network management system determines that the first GNE is the primary GNE of the first NGNE and that the second GNE is the backup GNE of the first NGNE by comparing the values of the first routing overhead and the second routing overhead. The value of the first routing overhead is smaller than the value of the second routing overhead, which is understood to be that the delay from the first GNE indicated by the value of the first routing overhead to the first NGNE is smaller than the delay from the second GNE indicated by the value of the second routing overhead to the first NGNE.

In step 450, the network management system establishes a communication connection with the first NGNE through the first GNE.

The method for establishing the communication connection in the step 450 is the same as the method for establishing the communication connection in the step 340, and specifically, reference may be made to the description related to the step 340, which is not repeated herein.

Optionally, after the step 450, the following steps may be further included: the network management system creates a management instance of the first NGNE. The network management system creates a management instance of the first NGNE, which can be understood as a software behavior. In particular, the network management system allocates a memory for the first NGNE, where the memory is used to store information about the communication of the first NGNE, and content such as a current presentable state configuration, and presents the content in a visual manner.

Optionally, after the step 450, the following steps may be further included: the network management system may also determine, based on the first routing information, whether the network management system is reachable to the first NGNE via the first GNE. For example, the network management system may generate a probe packet according to the first routing information, and periodically send the probe packet to the first GNE and the first NGNE, where the probe packet may include the second IP address and/or the first NEID; the network management system receives the responses of the first GNE and the first NGNE within a preset time, and determines that the first NGNE is reachable through the first GNE. Optionally, the network management system does not receive the responses of the first GNE and the first NGNE within a preset time, and determines that the first NGNE is not reachable through the first GNE, where the network management system may consider that the first GNE and the first NGNE take out of management.

Optionally, step 480 may be further included after step 450 described above.

In step 480, in the event of a failure of the first GNE, the network management system establishes a communication connection with the first NGNE through the second GNE.

Under the condition that the first GNE fails, the network management system establishes communication connection with the first NGNE through the second GNE, and the network management system comprises: under the condition that the first GNE fails, the network management system generates fourth routing information according to a third IP address, a first NEID, an identification of the second port and second routing overhead, wherein the third IP address is used for uniquely identifying the second GNE, the third IP address is an IP address utilized when the second GNE establishes communication connection with the network management system, the fourth routing information indicates that the first NGNE is registered in the network management system, and the fourth routing information comprises the third IP address, the first NEID, the mapping relation between the second port and the second routing overhead.

Optionally, after the step 480, the following steps may be further included: the network management system may also determine, based on the first routing information, whether the network management system is reachable to the first NGNE via the second GNE. For example, the network management system may generate a probe packet according to the first routing information, and periodically send the probe packet to the second GNE and the first NGNE, where the probe packet may include a third IP address and/or the first NEID; the network management system receives the responses of the second GNE and the first NGNE within a preset time, determines that the first NGNE is reachable through the second GNE, and then switches from the state of accessing the first NGNE through the first GNE to the state of accessing the second NGNE through the second GNE. Optionally, the network management system does not receive the responses of the second GNE and the first NGNE within a preset time, and determines that the first NGNE is not reachable through the second GNE, and at this time, the network management system may consider that the second GNE and the first NGNE take out of management.

Optionally, after the step 480, the following steps may be further included: the network management system updates the information of the first GNE recorded in the network management system, and the updated information of the first GNE indicates that the first GNE fails. Similarly, the network management system may update the information of the second GNE recorded in the network management system, that is, the updated information of the second GNE indicates that the second GNE is the active GNE of the first NGNE.

In the embodiment of the application, the network management system in the first routing domain can actively query the route information of the first NGNE to be registered from the GNE in the second routing domain, and determine the appropriate GNE for the first NGNE to be registered according to the acquired route information of the first NGNE to be registered. The network management system inquires the route of the first NGNE to be registered from each GNE communicated with the network management system, and the network management system can obtain the optimal path for accessing the first NGNE to be registered by comparing the route cost of each GNE and the first NGNE to be registered. In the implementation process, the network management system can periodically query the GNE communicated with the network management system for the route information of the first NGNE to be registered, and determine the optimal route information of the first NGNE to be registered accessed through the network management system according to the queried route information of the first NGNE to be registered, so that the whole process does not need participation of operation and maintenance personnel, and the connection establishment efficiency between the network management system and the network element is improved. In addition, when the network management system determines the load condition of the GNE in the process of determining the active GNE for the first NGNE to be registered according to the acquired routing information of the first NGNE to be registered, the configuration of normal service can be prevented from being influenced by excessive number of GNE management NGNEs.

In the above, the method for network management system and network element communication provided in the embodiments of the present application is described in connection with fig. 2 to fig. 4. Next, a specific embodiment of a method for communication between a network management system and a network element according to an embodiment of the present application will be described with reference to fig. 5 and fig. 6. The examples of fig. 5 and 6 are merely intended to aid one skilled in the art in understanding the present embodiments and are not intended to limit the present embodiments to the specific values or particular scenarios illustrated. Various equivalent modifications and variations will be apparent to those skilled in the art from the examples of fig. 5 and 6 given below, and such modifications and variations are intended to be within the scope of the embodiments of the present application.

Referring to fig. 5, ngne.b is shown with a dotted line, and ngne.b is an NGNE to be registered in the routing domain 2. Based on the scenario shown in fig. 5, the method for network management system and network element communication provided in the embodiments of the present application may include steps 510 to 570. Steps 510 to 570 are specifically described below.

In step 510, ngne.b accesses DCN using IP1 and establishes a communication connection with gne.a.

The IP1 may refer to an IP address of ngne.b factory configuration, and as shown in fig. 5, IP1 is specifically 1.1.1.11. In one possible implementation, the establishment of the communication connection between ngne.b and gne.a may include the following steps: the ngne.b uses IP1 to access DCN, the ngne.b uses communication ports (i.e., ng.b-1 ports) to run routing protocols (e.g., but not limited to, the open shortest path first (open shortest path first, OSPF) protocols) with network elements (i.e., GNE.A, GNE.B, NGNE.A and ngne.b) in routing domain 2, the ngne.b also learns the route from network elements (i.e., GNE.A, GNE.B, NGNE.A and ngne.b) in routing domain 2, but ngne.b itself does not sense the role and location of GNEs (i.e., gne.a and gne.b), while GNEs (i.e., gne.a and gne.b) in routing domain 2 learn IP1 through routing diffusion, thereafter GNE (i.e., gne.a and gne.b) in routing domain 2 can use IP1 to establish a communication connection with ngne.b, since GNE and NMS are not in the same routing domain, the active diffusion of GNE is not in the same routing domain, and gne.b is in the same IP1, and the relationship between gne.5 and gne.1 is shown as shown in fig. 35.1 and fig. 1, and the corresponding relationship between gne.1.b and ng.1 is shown in fig. 1, and an IP1 is shown, and an IP-1, an IP-1 is shown, and an IP-35, a connection is shown, and a table is shown between the ne.35.1.

At step 520, the nms establishes a communication connection with the GNE in routing domain 2.

Wherein the NMS establishes a communication connection with the GNE in the routing domain 2, comprising: the NMS establishes a communication connection with gne.a in routing domain 2 and the NMS establishes a communication connection with gne.b in routing domain 2. In the following, a communication connection is established between the NMS and the gne.a in the routing domain 2. The NMS establishes a communication connection with gne.a in routing domain 2, and may include the steps of: the NMS receives an access request message 1 sent by the gne.a, where the access request message 1 is used to request to establish a communication connection with the NMS using IP2, and IP2 is used to uniquely identify the gne.a, as shown in fig. 5, and IP2 is specifically 1.1.10.11. The access request message 1 may include IP2; the NMS establishes a communication connection with gne.a through IP2. Optionally, the access request message 1 may also carry the port identifier of gne.a. Based on this, the NMS can establish a communication connection with gne.a through IP2 and the port identification of gne.a. It will be appreciated that after the NMS establishes a connection with gne.a, the NMS records information on the establishment of a communication connection with gne.a, including at least IP2. Optionally, the information may also include the port identification of gne.a. Likewise, based on similar principles as described above, the NMS may establish a communication connection with the gne.b in the routing domain 2 via IP3, IP3 being used to uniquely identify the gne.b, as shown in fig. 5, IP3 being specifically 1.1.11.11.

In step 530, the operator inputs IP1 at the NMS side, triggers the NMS to send a query message to the GNE in the routing domain 2, where the query message is used to obtain routing information of ngne.b, and the query message includes IP1.

In step 530, triggering the NMS to send a query message to the GNE in the routing domain 2 includes: the NMS sends a query message to gne.a in routing domain 2 and a query message to gne.b in routing domain 2. After the NMS establishes a communication connection with the GNE in the routing domain 2, the routing table of the NMS records information of the GNE in the routing domain 2 (for example, but not limited to, an IP address of the GNE in the routing domain 2), so the NMS may send a query message to the GNE in the routing domain 2 based on the routing table of the NMS.

In step 540, the GNE in routing domain 2 sends a response message to the NMS indicating the routing information for the GNE in routing domain 2 to communicate with ngne.b.

The response message comprises a response message 1 and a response message 2, wherein the response message 1 indicates the route information of the communication between the GNE.A and the NGNE.B in the routing domain 2, and the response message 2 indicates the route information of the communication between the GNE.B and the NGNE.B in the routing domain 2.

Before the step 540, the method may further include the following steps: after receiving the query message, gne.a queries whether IP1 is recorded in the routing table of gne.a. If the correlation between IP1 and NEID1 is recorded in the gne.a routing table. Thereafter, the gne.a sends a response message 1 to the NMS, the response message 1 indicating routing information 1 for the gne.a to ngne.b communication, the routing information 1 may include routing overhead (cost) 1 and identification of G.A-1 ports, and the overhead a indicates the routing overhead of gne.a to ngne.b. Optionally, if IP1 is not recorded in the routing table of gne.a, gne.a sends a response message 1 to NMS, and query response message 1 indicates that ngne.b corresponding to IP1 and gne.a are not in the same routing domain. Based on the same principle, the following steps may be further included before the step 540: after receiving the query message, the gne.b queries whether IP1 is recorded in the routing table of gne.b. If the correlation between IP1 and NEID1 is recorded in the gne.b routing table. Thereafter, the gne.b sends a response message 2 to the NMS, the response message 2 indicating routing information 2 for gne.b to ngne.b communications, the routing information 2 may include an identification of an overhead B and G.B-1 port, the overhead B indicating the routing overhead of gne.b to ngne.b. Optionally, if IP1 is not recorded in the routing table of gne.b, gne.b sends a response message 2 to NMS, and query response message 2 indicates that ngne.b corresponding to IP1 and gne.b are not in the same routing domain.

The routing overhead may be determined based on one or more of the following: path information from GNE to NGNE, loading conditions of GNE (i.e., number of NGNEs communicating with GNE), or latency information from GNE to NGNE.

In step 550, the nms determines that the active GNE of ngne.b is gne.a and determines that the standby GNE of ngne.b is gne.b according to the response message.

Wherein, the NMS determines that the active GNE of the NGNE.B is GNE.A and determines that the standby GNE of the NGNE.B is GNE.B according to the response message, comprising: the NMS determines the active GNE of NGNE.B as GNE.A and determines the standby GNE of NGNE.B as GNE.B according to the overhead A and the overhead B. In one possible implementation, when the NMS determines that overhead a of gne.a is less than overhead B of gne.b, the NMS determines that the active GNE of gne.b is gne.a and determines that the standby GNE of gne.b is gne.b.

In step 560, the nms establishes a communication connection with ngne.b through gne.a.

Wherein, the NMS establishes communication connection with NGNE.B through GNE.A, comprising: the NMS generates routing information 3 according to the response message 1, the routing information 3 indicates that ngne.b is registered at the NMS, and the routing information 3 includes mapping relations among NEID1:1-11, ip2:1.1.10.11, overhead a, and G.A ports, as shown in fig. 6, and the mapping relations are recorded in the routing table of the NMS. That is, the NMS generates the routing information 3, and it is understood that the NMS establishes a communication connection with ngne.b through gne.a.

Optionally, after the step 560, the following steps may be further included: the NMS creates a management instance of ngne.b. The NMS creates a management instance of ngne.b, which can be understood as a software behavior. In particular, the NMS allocates a piece of memory for the ngne.b, where the memory is used to store information about ngne.b communications, and content such as current presentable status configuration, and presents the content in a visual manner.

Optionally, after the step 560, the following steps may be further included: the NMS may also determine from the routing information 1 whether the NMS is reachable by ngne.b through gne.a. Illustratively, the NMS may generate a probe packet according to the routing information 1, and periodically send the probe packet to gne.a and ngne.b, where the probe packet may include IP2 and/or NEID1; the NMS receives responses of GNE.A and NGNE.B within a preset time, and determines that the NGNE.B is reachable through the GNE.A. Optionally, the NMS does not receive the responses of gne.a and ngne.b within a preset time, and determines that ngne.b is not reachable through gne.a, where the NMS may consider that gne.a and ngne.b take place a tube-out phenomenon.

In step 570, in the event of a failure of gne.a, the NMS establishes a communication connection with ngne.b through gne.b.

Wherein the NMS establishes communication connection with NGNE.B through GNE.B, comprising: the NMS generates routing information 4 according to the response message 2, where the routing information 4 indicates that ngne.b is registered at the NMS, and the routing information 4 includes mapping relationships between NEID1:1-11, ip3:1.1.11.11, overhead B, and G.B ports, as shown in fig. 6, and the mapping relationships are recorded in the routing table of the NMS. That is, the NMS generates the routing information 4, and it is understood that the NMS establishes a communication connection with ngne.b through gne.b.

Illustratively, the NMS may determine that gne.a fails by: the NMS can send a detection message to the GNE communicated with the NMS at fixed time intervals, and if the NMS receives a response of the GNE within preset time, the GNE is determined to not have faults; if the NMS does not receive the response of the GNE within the preset time, determining that the GNE fails.

In the above, a method suitable for the network management system and the network element communication provided in the embodiments of the present application is described in detail with reference to fig. 1 to 6. The following describes in detail the apparatus and system provided in the embodiments of the present application with reference to fig. 7 to 10. It should be understood that the descriptions of the apparatus and system embodiments and the descriptions of the method embodiments correspond to each other, and thus, descriptions of details that are not described above may be referred to the method embodiments, which are not repeated herein for brevity.

Fig. 7 is a schematic structural diagram of a first communication device 700 provided in an embodiment of the present application. The first communication device 700 shown in fig. 7 may perform the corresponding steps performed by the network management system in the above-described method embodiment.

As shown in fig. 7, the first communication apparatus 700 may include: a transceiver unit 710 and a processing unit 720. The transceiver unit 710 may be configured to perform

steps

210, 220, 310, 330, 410, 411, 430 and 431 in the above method. Processing unit 720 may be configured to perform step 230, step 340, step 360, step 440, step 450, step 470, and step 480 above. These steps are specifically referred to above as related steps, and will not be described in detail herein.

It should be appreciated that the apparatus 700 of the embodiments of the present application may be implemented by a central processing unit (central processing unit, CPU), or by an application-specific integrated circuit (application-specific integrated circuit, ASIC), or by a programmable logic device (programmable logic device, PLD), which may be a complex program logic device (complex programmable logical device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), a general-purpose array logic (generic array logic, GAL), or any combination thereof. When the method described in the above method embodiments is implemented by software, the apparatus 700 and its respective modules may also be software modules.

Fig. 8 is a schematic structural diagram of a data transmission apparatus 800 provided in an embodiment of the present application. The second communication device 800 shown in fig. 8 may perform the corresponding steps performed by the GNE in the method embodiment described above. As shown in fig. 8, the second communication apparatus 800 may include: a transceiver unit 810 and a processing unit 820.

In some implementations, the second communication device 800 may perform the corresponding steps performed by the first GNE in the method embodiments described above. Wherein the transceiver unit 810 may be configured to receive the query message in step 310 above and the query message in step 410 above, and perform step 330 above, step 430 above. Processing unit 820 may be used to perform steps 420 and 460 above. These steps are specifically referred to above as related steps, and will not be described in detail herein.

In other implementations, the second communication device 800 may perform the corresponding steps performed by the second GNE in the method embodiments described above. Wherein the transceiver unit 810 may be configured to receive the query message in step 411 above, and perform step 431 above. The processing unit 820 may be configured to perform steps 421 and 461 hereinabove. These steps are specifically referred to above as related steps, and will not be described in detail herein.

It should be appreciated that the apparatus 800 of the embodiments of the present application may be implemented by a central processing unit (central processing unit, CPU), or by an application-specific integrated circuit (application-specific integrated circuit, ASIC), or by a programmable logic device (programmable logic device, PLD), which may be a complex program logic device (complex programmable logical device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), a general-purpose array logic (generic array logic, GAL), or any combination thereof. When the method described in the above method embodiments is implemented by software, the apparatus 800 and its respective modules may also be software modules.

As shown in fig. 9, the communication device 900 includes a processor 901, a memory 902, an interface 903, and a bus 904. The interface 903 may be implemented by a wireless or wired manner, and may specifically be a network card. The processor 901, memory 902, and interface 903 are connected by a bus 904. The interface 903 may specifically include a transmitter and a receiver, which are used by the data transmission device to implement the foregoing transceiving. The processor 901 is configured to perform the processing performed by the data transmission apparatus in the above-described embodiment. The memory 902 includes an operating system 9021 and application programs 9022 for storing programs, code or instructions that when executed by a processor or hardware device perform the processes of the method embodiments involving BFIR. Alternatively, the memory 902 may include read-only memory (ROM) and random access memory (random access memory, RAM). Wherein the ROM comprises a basic input/output system (BIOS) or an embedded system; the RAM includes application programs and an operating system. When the communication device 900 needs to be operated, the BIOS cured in the ROM or bootloader booting system in the embedded system is used to start, and the communication device 900 is guided to enter a normal operation state. After the communication apparatus 900 enters the normal operation state, the application programs and the operating system running in the RAM, and thus, the processing procedure involving the communication apparatus 900 in the method embodiment is completed. Fig. 9 shows only a simplified design of a communication device 900. In practice, communication device 900 may include any number of interfaces, processors, or memories.

Alternatively, in some implementations, the communication device 900 may be a schematic hardware structure of the first communication device 700. At this time, the processor 901 has the same function as the processing unit 720, and the interface 903 has the same function as the transceiver unit 710.

Alternatively, in other implementations, the communication device 900 may be a schematic hardware structure of the second communication device 800. At this time, the processor 901 has the same function as the processing unit 820, and the interface 903 has the same function as the transceiver unit 810.

Fig. 10 is a schematic block diagram of a system 1000 provided in an embodiment of the present application. As shown in fig. 10, the system 1100 may include: the first communication device 700 and the second communication device 800.

Embodiments of the present application also provide a computer readable medium storing program code that, when executed on a computer, causes the computer to perform a method performed by a network management system or by the GNE (i.e., the first GNE or the second GNE) in the method embodiments described above. These computer-readable stores include, but are not limited to, one or more of the following: read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), flash memory, electrically EPROM (EEPROM), and hard disk drive (hard drive).

The embodiment of the application also provides a chip system, which comprises: the system comprises at least one processor, at least one memory and an interface circuit, wherein the interface circuit is responsible for information interaction between the chip system and the outside, the at least one memory, the interface circuit and the at least one processor are interconnected through a circuit, and instructions are stored in the at least one memory; the instructions are executed by the at least one processor to perform operations related to the network management system or GNE (i.e., the first GNE or the second GNE) in the methods of the various aspects described above. In particular implementations, the system-on-chip may be implemented in the form of a central processing unit (central processing unit, CPU), microcontroller (micro controller unit, MCU), microprocessor (micro processing unit, MPU), digital signal processor (digital signal processing, DSP), system-on-chip (SoC), application-specific integrated circuit (ASIC), field programmable gate array (field programmable gate array, FPGA), or programmable logic device (programmable logic device, PLD).

Embodiments of the present application also provide a computer program product for use in a network management system, the computer program product comprising a series of instructions which, when executed, perform the operations of the network management system in the methods of the above aspects.

Embodiments of the present application also provide a computer program product for use in a GNE (i.e., a first GNE or a second GNE), the computer program product comprising a series of instructions that, when executed, perform the operations of the GNE (i.e., the first GNE or the second GNE) in the methods of the above aspects.

As used in this specification, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between 2 or more computers. Furthermore, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from two components interacting with one another in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal).

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for communication between a network management system and a network element, the method comprising:

the network management system sends a query message to a gateway network element GNE in a second routing domain, wherein the query message is used for acquiring routing information of a first non-gateway network element NGNE, the first NGNE is an NGNE to be registered, the routing domain where the network management system is located is a first routing domain, and the first routing domain is different from the second routing domain;

the network management system receives a response message sent by the GNE in the second routing domain, wherein the response message indicates the routing information of the communication between the GNE in the second routing domain and the first NGNE;

and the network management system establishes communication connection with the first NGNE according to the response message.

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

The query message includes a first internet protocol IP address, where the first IP address is a preset IP address of the first NGNE, and the first IP address is used to establish a communication connection between the first NGNE and a GNE in the second routing domain.

3. The method of claim 2, wherein the second routing domain includes a first GNE, wherein the response message includes a first response message, wherein the first response message is used to indicate first routing information for the first GNE to communicate with the first NGNE, wherein the first routing information includes an identification of a first port, wherein the first port is a port of the first GNE to which the first NGNE is connected, wherein the first NEID corresponds to the first IP address, wherein the first NEID is used to uniquely identify the first NGNE,

the network management system establishes communication connection with the first NGNE according to the response message, and comprises:

the network management system generates second routing information according to the second IP address, the first NEID and the identification of the first port, the second IP address is used for uniquely identifying the first GNE, the second IP address is an IP address utilized when the first GNE and the network management system establish communication connection, the second routing information indicates that the first NGNE is registered in the network management system, the second routing information comprises the second IP address, and the mapping relation between the first NEID and the first port is achieved.

4. The method of claim 3, wherein the second routing domain further comprises a second GNE, wherein the response message further comprises a second response message indicating third routing information for the second GNE to communicate with the first NGNE, wherein the third routing information comprises a second routing overhead,

before the network management system establishes a communication connection with the first NGNE according to the response message, the method further includes:

the network management system determines that the first GNE is a primary GNE of the first NGNE and determines that the second GNE is a standby GNE of the first NGNE according to a first routing overhead and the second routing overhead, and the first routing information further includes the first routing overhead.

5. The method of claim 4, wherein the third routing information further includes an identification of a second port and the first NEID, the second port being a port of the second GNE to which the first NGNE is connected,

in the case that the first GNE fails, the network management system generates fourth routing information according to a third IP address, the first NEID, the identifier of the second port and the second routing overhead, where the third IP address is used to uniquely identify the second GNE, the third IP address is an IP address that is used when the second GNE establishes a communication connection with the network management system, the fourth routing information indicates that the first GNE is registered in the network management system, and the fourth routing information includes a mapping relationship between the third IP address, the first NEID, the second port and the second routing overhead.

6. The method according to claim 4 or 5, wherein,

the first routing overhead is determined from at least one of the following information: the path information from the first GNE to the first NGNE, the load condition of the first GNE, or the delay information from the first GNE to the first NGNE;

the second routing overhead is determined from at least one of the following information: the path information from the second GNE to the first NGNE, the loading condition of the second GNE, or the delay information from the second GNE to the first NGNE.

7. A method for communication between a network management system and a network element, the method comprising:

after a first Gateway Network Element (GNE) and a first non-gateway network element (NGNE) are in communication connection, the first GNE receives a query message sent by a network management system, wherein the query message is used for acquiring routing information of the first NGNE, the first NGNE is an NGNE to be registered, a routing domain where the network management system is located is a first routing domain, a second routing domain comprises the first GNE and the first NGNE, and the first routing domain is different from the second routing domain;

and the first GNE generates a first response message according to the query message and the routing table of the first GNE, and the first response message indicates first routing information of the first GNE and the first NGNE communication.

The first GNE sends the first response message to the network management system.

8. The method of claim 7, wherein the step of determining the position of the probe is performed,

the query message includes a first internet protocol IP address, where the first IP address is a preset IP address of the first NGNE, the first IP address is used to establish communication connection between the first NGNE and a GNE in the second routing domain, and the GNE in the second routing domain includes the first GNE.

9. The method of claim 8, wherein a first correspondence is recorded in the routing table of the first GNE, the first correspondence being between a first network element identifier NEID and the first IP address, the first NEID being used to uniquely identify the first NGNE,

the first GNE generates a first response message according to the query message and the routing table of the first GNE, including:

the first GNE determines the first NEID according to the first IP address and the first corresponding relation;

the first GNE determines the communication path information of the first GNE and the first NGNE according to a second IP address and the first NEID, wherein the second IP address is used for uniquely identifying the first GNE, and is an IP address utilized when the first GNE establishes communication connection with the network management system;

And the first GNE generates the first response message according to the path information.

10. The method of claim 9, wherein the step of determining the position of the substrate comprises,

the first routing information includes an identifier of a first port, a first routing overhead, the first NEID and the first IP address, the first port is a port of the first GNE connected to the first NGNE, and the first routing overhead is a routing overhead of communication between the first GNE and the first NGNE.

11. The method of claim 10, wherein the step of determining the position of the first electrode is performed,

the first routing overhead is determined from at least one of the following information: the path information from the first GNE to the first NGNE, the loading condition of the first GNE, or the delay information from the first GNE to the first NGNE.

12. A first communication device for use in a network management system, the device comprising:

a transceiver unit, configured to send a query message to a gateway network element GNE in a second routing domain, where the query message is used to obtain routing information of a first non-gateway network element NGNE, the first NGNE is an NGNE to be registered, and a routing domain where the network management system is located is a first routing domain, where the first routing domain is different from the second routing domain;

The transceiver unit is further configured to receive a response message sent by the GNE in the second routing domain, where the response message indicates routing information of the GNE in the second routing domain to communicate with the first NGNE;

and the processing unit is used for establishing communication connection with the first NGNE according to the response message.

13. The apparatus of claim 12, wherein the device comprises a plurality of sensors,

14. The apparatus of claim 13, wherein the second routing domain comprises a first GNE, wherein the response message comprises a first response message, wherein the first response message is configured to indicate first routing information for the first GNE to communicate with the first NGNE, wherein the first routing information comprises an identification of a first port, wherein the first port is a port of the first GNE to which the first NGNE is connected, wherein the first NEID corresponds to the first IP address, wherein the first NEID is configured to uniquely identify the first NGNE,

The processing unit is further configured to:

generating second routing information according to the second IP address, wherein the first NEID and the identification of the first port are used for uniquely identifying the first GNE, the second IP address is an IP address utilized when the first GNE is in communication connection with the network management system, the second routing information indicates that the first NGNE is registered in the network management system, and the second routing information comprises the second IP address, and the mapping relation between the first NEID and the first port is achieved.

15. The apparatus of claim 14, wherein the second routing domain further comprises a second GNE, wherein the response message further comprises a second response message indicating third routing information for the second GNE to communicate with the first NGNE, wherein the third routing information comprises a second routing overhead,

the processing unit is further configured to:

according to the first routing overhead and the second routing overhead, determining that the first GNE is a primary GNE of the first NGNE, and determining that the second GNE is a standby GNE of the first NGNE, wherein the first routing information further includes the first routing overhead.

16. The apparatus of claim 15, wherein the third routing information further includes an identification of a second port and the first NEID, the second port being a port of the second GNE to which the first NGNE is connected,

the processing unit is further configured to:

under the condition that the first GNE fails, generating fourth routing information according to a third IP address, the first NEID, the identification of the second port and the second routing overhead, wherein the third IP address is used for uniquely identifying the second GNE, the third IP address is an IP address utilized when the second GNE establishes communication connection with the network management system, the fourth routing information indicates that the first NGNE is registered at the network management system, and the fourth routing information comprises the third IP address, the first NEID, and the mapping relation between the second port and the second routing overhead.

17. The apparatus according to claim 15 or 16, wherein,

18. A second communication device, wherein the second communication device is applied in a first gateway network element GNE, the device comprising:

a transceiver unit, configured to receive, after the first GNE establishes a communication connection with a first non-gateway network element NGNE, a query message sent by a network management system, where the query message is used to obtain routing information of the first NGNE, the first NGNE is an NGNE to be registered, a routing domain where the network management system is located is a first routing domain, and a second routing domain includes the first GNE and the first NGNE, where the first routing domain is different from the second routing domain;

the processing unit is used for generating a first response message according to the query message and the routing table of the first GNE, wherein the first response message indicates first routing information of the first GNE and the first NGNE communication;

the receiving and transmitting unit is further configured to send the first response message to the network management system.

19. The apparatus of claim 18, wherein the device comprises a plurality of sensors,

20. The apparatus of claim 19, wherein a first correspondence is recorded in a routing table of the first GNE, the first correspondence being between a first network element identifier NEID and the first IP address, the first NEID being used to uniquely identify the first NGNE,

the processing unit is further configured to:

determining the first NEID according to the first IP address and the first corresponding relation;

determining the communication path information of the first GNE and the first NGNE according to a second IP address and the first NEID, wherein the second IP address is used for uniquely identifying the first GNE, and is an IP address utilized when the first GNE and the network management system are in communication connection;

and generating the first response message according to the path information.

21. The apparatus of claim 20, wherein the device comprises a plurality of sensors,

22. The apparatus of claim 21, wherein the device comprises a plurality of sensors,

23. A first communication device for use in a network management system, the device comprising at least one processor and a communication interface, the at least one processor being configured to execute a computer program or instructions to cause the device to perform the method of any one of claims 1 to 6.

24. A second communication device, characterized in that it is applied in a first gateway network element GNE, the device comprising at least one processor and a communication interface, the at least one processor being adapted to execute a computer program or instructions to cause the device to perform the method according to any of claims 7 to 11.

25. A computer readable storage medium comprising a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 6.

26. A computer readable storage medium comprising a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 7 to 11.

27. A system comprising a first communication device according to claim 23 and a second communication device according to claim 24.